Credit business processing method and device, equipment and medium

Abstract

The invention relates to the technical field of bank informatization, and discloses a credit and loan business processing method, device and equipment and a medium, the method comprises the following steps: obtaining workflow definition information input by a user, the workflow definition information comprising a calling relationship among a plurality of micro-service components under a target credit and loan business and node information of each micro-service component; generating a local workflow of the micro-service component based on the node information; determining a global workflow of the target credit business based on the calling relationship among the plurality of micro-service components and the local workflow corresponding to each micro-service component, and inputting the global workflow into a workflow engine; when the processing request of the target credit business is received, the target credit business is executed through the workflow engine based on the corresponding global workflow calling component, the global workflow of the target credit business is generated through the definition information, so that the workflow engine calls the business component to execute the corresponding task; therefore, the development process of complex credit business is simplified, and the development efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of banking information technology, and in particular to a credit business processing method, device, equipment and medium. Background Art

[0002] Existing credit systems are often composed of multiple microservices, including customer management, credit approval, contracts, credit use, loan issuance and post-loan. Each microservice is a relatively independent functional unit that completes specific tasks by calling each other.

[0003] The core business of a bank is credit business. The front desk is flexible and adaptable to meet market requirements, while the middle and back offices strictly control risks to ensure the compliance and efficiency of each business process.

[0004] Most of the existing systems in the industry use complex codes to assemble business logic. When the business becomes extremely complex, the development process becomes complicated, the readability of the business logic is extremely poor, and the maintainability is reduced. Summary of the invention

[0005] In view of this, the present invention provides a credit business processing method, device, equipment and medium to solve the problem of extremely poor readability and low maintainability caused by assembling business logic through code when the business is complex.

[0006] In a first aspect, the present invention provides a credit business processing method, the method comprising:

[0007] Acquire workflow definition information input by a user, wherein the workflow definition information includes: a calling relationship between multiple microservice components corresponding to a target credit business and node information corresponding to each microservice component;

[0008] Generate the local workflow corresponding to each microservice component based on the node information corresponding to each microservice component;

[0009] Based on the calling relationship between the multiple microservice components and the local workflows corresponding to the respective microservice components, a global workflow of the target credit business is determined and entered into a workflow engine;

[0010] When a processing request for a target credit business is received, the workflow engine calls a component based on the global workflow corresponding to the target credit business to execute the target credit business.

[0011] The method provided in this aspect generates a local workflow corresponding to each microservice component through the node information under the microservice component input by the user, and generates a global workflow in combination with the calling relationship between the microservice components and enters it into the workflow engine, so that when a processing request for a target credit business is received, the workflow engine can call each business component involved in the corresponding global workflow and execute the corresponding task to complete the target credit business. By defining the workflow, the development process of a specific credit business is simplified, and the readability and maintainability of the overall business logic are improved.

[0012] In an optional implementation, the node information corresponding to the microservice component includes: the business component name, task information and trigger condition corresponding to each process node in the service process of the corresponding microservice component;

[0013] The generating of the local workflow corresponding to each microservice component based on the node information corresponding to each microservice component includes:

[0014] Determine the execution content of each process node according to the business component name, task information and trigger conditions corresponding to each process node under each microservice component;

[0015] A local workflow of the corresponding microservice component is constructed based on the execution content of each process node.

[0016] In this implementation mode, the business component name and task information corresponding to each process node in the corresponding node information of each microservice component, as well as the triggering conditions, are used to determine the execution content of each internal process node of the corresponding microservice component when providing the corresponding microservice, thereby building a local workflow for each microservice component. By building a workflow, the means of implementing the corresponding functions of the microservice component are simplified, and the readability and maintainability of the business logic within the microservice are improved.

[0017] In an optional implementation, determining the execution content of each process node according to the business component name, task information and trigger condition corresponding to each process node under each microservice component includes:

[0018] Determine the component calling interface corresponding to the process node according to the business component name;

[0019] Determine the input parameter field and output parameter field and the business logic corresponding to the process node according to the task information;

[0020] The execution content of the corresponding process node is determined according to the component calling interface, input parameter fields, output parameter fields, business logic and trigger conditions.

[0021] In this implementation mode, the calling interface of the corresponding component is determined by the business component name corresponding to each process node, and the business logic of the input and output parameter fields when executing the corresponding node task is determined according to the task information. Then, the specific execution content is determined in combination with the trigger conditions of each process node, so as to ensure the accuracy of the execution content corresponding to each node, and thus ensure the effective execution of the subsequent target credit business.

[0022] In an optional implementation, the calling relationship of the multiple microservice components includes: the execution order and triggering conditions corresponding to each microservice component;

[0023] Determining the global workflow of the target credit business based on the calling relationship between the multiple microservice components and the local workflows corresponding to the respective microservice components includes:

[0024] The local workflows corresponding to the various microservice components are combined according to the execution order and trigger conditions corresponding to the various microservice components to determine the global workflow of the target credit business.

[0025] In this implementation, the local workflows corresponding to the various microservice components are combined based on the calling order and trigger conditions corresponding to each microservice component to obtain a global workflow for the target credit business, which contains the task information and trigger conditions of the business components corresponding to all process nodes, thereby achieving the splicing between the various microservice components, facilitating maintenance and changes to the target credit business, and simplifying the process of building the global workflow.

[0026] In an optional implementation, calling a component based on the global workflow corresponding to the target credit business by a workflow engine includes:

[0027] The workflow engine sequentially executes the local workflow corresponding to each microservice construction according to the calling relationship between the microservice constructions;

[0028] During the execution of the local workflow, the corresponding process node is started according to the triggering conditions of each process node, and the corresponding business component is called through the component calling interface of the process node;

[0029] Determine the output information of the process node by the business component based on the input parameter field and the output parameter field corresponding to the process node and the business logic;

[0030] The next process node is started based on the output information.

[0031] In this implementation mode, the local workflow corresponding to each microservice component in the global workflow is executed through the workflow engine, and during execution, the corresponding node is started according to the trigger conditions corresponding to each process node in the workflow, and the corresponding business component is called to output the output information of the current process node based on the corresponding input parameter fields and output parameter fields and business logic. The business component is called through the interface to execute the corresponding task, which improves the reuse rate of various business components, reduces the development of duplicate code, and improves the efficiency of business development.

[0032] In an optional implementation, determining the output information of the process node based on the input parameter field and the output parameter field corresponding to the process node and the business logic through the business component includes:

[0033] Call the input parameter field information corresponding to the input parameter field of the process node in the database;

[0034] The input parameter field information is processed through the business component and business logic to obtain the output parameter field information corresponding to the output parameter field of the process node, and the output parameter field information is used as the output information of the current process node.

[0035] In this implementation, when executing corresponding tasks at each process node, the database is called to fill in the input parameter fields, so as to process the corresponding input parameter field information based on the business components and business logic, obtain the specific output parameter field information and output it, thereby ensuring the accuracy of data processing and subsequent trigger condition judgment when processing the corresponding business.

[0036] In an optional implementation, starting the next process node based on the output information includes:

[0037] Compare the output parameter field information of the current process node with the trigger condition of the next process node to determine whether the next process node is triggered;

[0038] When the next process node is triggered, the next process node is started, and the corresponding business component is called through the component calling interface of the next process node.

[0039] This implementation compares the specific output parameter field information of the current process node with the trigger conditions of the subsequent process nodes, so that the process nodes can be accurately triggered based on the actual situation, thereby ensuring the smooth execution of the global process.

[0040] In a second aspect, the present invention provides a credit business processing device, the device comprising:

[0041] A definition information acquisition module is used to acquire workflow definition information input by a user, wherein the workflow definition information includes: a calling relationship between multiple microservice components corresponding to a target credit business and node information corresponding to each microservice component;

[0042] A local workflow generation module is used to generate a local workflow corresponding to each microservice component based on the node information corresponding to each microservice component;

[0043] A global workflow determination module, used to determine the global workflow of the target credit business based on the calling relationship between the multiple microservice components and the local workflows corresponding to the respective microservice components, and input the global workflow into the workflow engine;

[0044] The credit business processing module is used to, when receiving a processing request for a target credit business, call a component based on the global workflow corresponding to the target credit business through a workflow engine to execute the target credit business.

[0045] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the credit business processing method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0046] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the credit business processing method of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0048] Figure 1 is a flow chart of a credit business processing method according to an embodiment of the present invention;

[0049] Figure 2 is a flowchart of another credit business processing method according to an embodiment of the present invention;

[0050] Figure 3 is an example diagram of a local workflow of a microservice component according to an embodiment of the present invention;

[0051] Figure 4is an example diagram of a local workflow of another microservice component according to an embodiment of the present invention;

[0052] Figure 5 is a structural block diagram of a credit business processing device according to an embodiment of the present invention;

[0053] Figure 6 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0055] Existing credit systems are often composed of multiple microservices, including customer management, credit approval, contracts, credit use, loan issuance and post-loan. Each microservice is a relatively independent functional unit that completes specific tasks by calling each other.

[0056] The core business of a bank is credit business. The front desk is flexible and adaptable to meet market requirements, while the middle and back offices strictly control risks to ensure the compliance and efficiency of each business process.

[0057] Most of the existing systems in the industry use complex codes to assemble business logic. When the business becomes extremely complex, the development process becomes complicated, the readability of the business logic is extremely poor, and the maintainability is reduced.

[0058] To this end, an embodiment of the present invention provides a credit business processing method, which generates local workflows corresponding to each microservice component through node information under the microservice component input by the user, and generates a global workflow in combination with the calling relationship between each microservice component and enters it into the workflow engine, so that when a processing request for a target credit business is received, the workflow engine can call each business component involved in the corresponding global workflow and execute corresponding tasks to complete the target credit business. By defining the workflow, the development process of a specific credit business is simplified, and the readability and maintainability of the overall business logic are improved.

[0059] According to an embodiment of the present invention, an embodiment of a method for processing a credit business is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0060] In this embodiment, a credit business processing method is provided, which can be used for processing the above-mentioned bank credit business. Figure 1 is a flow chart of a credit business processing method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0061] Step S101, obtaining workflow definition information input by a user, the workflow definition information including: the calling relationship between multiple microservice components corresponding to the target credit business and the node information corresponding to each microservice component.

[0062] For banking systems, when it comes to different credit products or businesses, when corresponding functional development is needed for some newly launched credit businesses, the execution workflow corresponding to the business can be defined, thereby executing the call splicing of various existing business components to achieve the corresponding target credit business.

[0063] Relevant staff, that is, users can input specific workflow definition information, including the calling relationship between various microservice components under the target credit business, such as the execution order and execution conditions of the microservices corresponding to each microservice component; it also includes the node information corresponding to each microservice component, where the node information can be understood as the process nodes where each existing callable business component is located when each microservice component executes the corresponding function, and the circumstances under which the components of each process node are triggered, the specific execution tasks, etc. can be manually configured information, and in some cases, specific options can also be provided for users to choose to obtain the corresponding default configuration information.

[0064] Specifically, for bank credit business, the microservice components involved may include: customer management, credit, contract, credit use, loan and post-loan management and other microservice components, each of which performs corresponding microservice functions.

[0065] Step S102: Generate a local workflow corresponding to each microservice component based on the node information corresponding to each microservice component.

[0066] After receiving the node information of each microservice component, the internal development system of the bank can generate the corresponding local workflow according to the relevant information of the components in each link under each microservice component. The node information includes the specific component call information, execution tasks, trigger conditions and other component related information of each link manually configured according to the actual situation. By combining the relevant information of the components in each link, the local workflow corresponding to the microservice component can be obtained. In the subsequent actual business processing stage, the workflow engine inside the bank system can call and execute the corresponding components according to the specific configuration information corresponding to each process node.

[0067] Step S103, based on the calling relationship between the multiple microservice components and the local workflow corresponding to each microservice component, determine the global workflow of the target credit business and enter it into the workflow engine.

[0068] For the entire target credit business, multiple microservice components are usually required to jointly implement business processing. Therefore, each microservice component also needs to be combined, called or interacted. The calling relationship input by the user can include information such as the calling order, execution conditions, and interaction timing between each microservice component. By combining the local workflows corresponding to each microservice component through the calling relationship between each microservice component, the global workflow in the execution process of the target credit business can be obtained. The global workflow can include specific configuration information of each involved component, such as trigger kits, task information, etc.

[0069] After obtaining the global workflow corresponding to the target credit business, it can be entered into the workflow engine within the system, so that when the system receives the target credit business, the workflow engine can execute the call and information interaction of each business component according to the global workflow, thereby realizing the response to the target credit business.

[0070] Step S104: when a processing request for a target credit business is received, the workflow engine calls a component based on the global workflow corresponding to the target credit business to execute the target credit business.

[0071] When the banking system receives a processing request for a target credit business actually initiated by a customer, the workflow engine within the system can search for the global workflow corresponding to the target credit business, and call the components involved in the execution system according to the local workflow of each microservice component, thereby completing the processing of the target credit business initiated by the customer.

[0072] The credit business processing method provided in this embodiment generates a local workflow corresponding to each microservice component through the node information under the microservice component input by the user, and generates a global workflow in combination with the calling relationship between each microservice component and enters it into the workflow engine, so that when a processing request for a target credit business is received, the workflow engine can call each business component involved in the corresponding global workflow and execute the corresponding task to complete the target credit business. By defining the workflow, the development process of a specific credit business is simplified, and the readability and maintainability of the overall business logic are improved.

[0073] According to an embodiment of the present invention, another credit business processing method embodiment is provided, which can be used for processing the above-mentioned bank credit business. Figure 2 is a flow chart of another credit business processing method according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0074] Step S201, obtaining workflow definition information input by a user, the workflow definition information including: the calling relationship between multiple microservice components corresponding to the target credit business and the node information corresponding to each microservice component.

[0075] Specifically, in the above step S201, the node information corresponding to the microservice component includes: the business component name, task information and triggering condition corresponding to each process node in the service process of the corresponding microservice component.

[0076] It can be understood that for each microservice component, when executing the corresponding microservice, it is implemented according to the specific process of the configuration. Therefore, developers need to pre-configure the business component name, task information and trigger conditions involved in each process node. The task information can be understood as the specific operation that the corresponding business component needs to perform when executing the task corresponding to the process node. The configuration of the process node can be completed by manually configuring the corresponding business logic, input and output parameter fields and other specific configuration information; the trigger condition can be understood as under what circumstances the corresponding process node will be started. For example, it can be decided whether to start based on the specific information output by the business component corresponding to the previous process node.

[0077] Specifically, in the above step S201, the calling relationship of the multiple microservice components includes: the execution order and triggering conditions corresponding to each microservice component.

[0078] Different microservice components also have their own corresponding execution order and trigger conditions. For example, for the credit system that processes credit business within the bank, its microservice components may include: customer management, credit, contract, credit use, loan and post-loan management. The execution order and trigger conditions of these six microservice components are also different. For example, when executing credit business processing, the customer management component is usually the first component, and its trigger condition is usually receiving a customer request. It is necessary to first call and verify the customer information through the customer management component. When the verification result meets the preset requirements, the specific steps of the subsequent credit component are executed. For different credit businesses, the execution order and trigger conditions corresponding to the specific microservice components can be set according to the actual situation.

[0079] Step S202: Generate a local workflow corresponding to each microservice component based on the node information corresponding to each microservice component.

[0080] Specifically, in the above step S202, it includes:

[0081] Step S202-1, determining the execution content of each process node according to the business component name, task information and triggering condition corresponding to each process node under each microservice component.

[0082] It can be understood that each microservice component has multiple process nodes, and each process node needs to execute the corresponding task through the standard business components within the bank's credit system. When configuring the local workflow according to the node information of each process node input by the staff, it is necessary to determine the specific execution content of each process node according to the specific business component name, task information and trigger conditions of each process node.

[0083] For example, the calling interface of each process node is determined by the business component name, and its specific triggering conditions are configured. The specific execution content of the business component is determined according to the specific task information. For example, the task information includes: the specific task that the node needs to perform. Taking the business component under the customer management component in a certain actual credit business as an example, the business component is an online verification component. The user can configure its specific items to be verified, the location of the verification data and the result output format and select the specific business execution logic, such as which items to verify first, and which operations to perform later if these items are incorrect.

[0084] After configuring the specific trigger conditions, business components and specific task information corresponding to each process node, the specific execution content corresponding to the process node can be obtained.

[0085] Specifically, in the above step S202-1, according to the business component name, task information and trigger condition corresponding to each process node under each microservice component, determining the execution content of each process node includes:

[0086] Step S202-1-1, determine the component call interface corresponding to the process node according to the business component name.

[0087] Step S202-1-2, determine the input parameter fields and output parameter fields and business logic corresponding to the process node according to the task information.

[0088] Step S202-1-3, determine the execution content of the corresponding process node according to the component call interface, input parameter field, output parameter field, business logic and trigger condition.

[0089] It can be understood that when determining the specific execution content in each process node, the business component name corresponding to the process node configured by the staff is matched with the corresponding component call interface in the relevant configuration table within the system, so that when the actual credit business is processed subsequently, the corresponding business component is called to perform the corresponding task.

[0090] According to the specific task information configured by the user, the specific input parameter fields, output parameter fields and specific business logic of the node can be determined. Similarly, taking the online verification component under the customer management component in a certain actual credit business as an example, the task information configured by the user can be: verify and compare the user's Class A information and Class B information, and the verification target database is database B. When Class A information is incorrect, the current process is terminated directly and the user error information is returned. When Class A information and Class B information are both normal, the judgment information is output. In this regard, the system can determine the specific input parameter fields of the process node, field A, and field B, and the output parameter fields are whether the verification result is normal or abnormal; the specific business logic is to fill in the input parameter fields according to the user's current input information, and compare it with the information in database B, so as to determine the field information of the verification result field.

[0091] Finally, the trigger conditions of the business components determined above, the component call interface, the business logic determined by the task information, the output parameter fields, the input parameter fields and other information are determined as the specific execution content of the process node, so as to facilitate the subsequent corresponding call execution according to the local workflow.

[0092] Step S202-2: construct a local workflow of the corresponding microservice component based on the execution content of each process node.

[0093] After determining the execution content of each process node, the currently configured process nodes can be spliced ​​and combined according to specific trigger conditions to obtain the local workflow of the corresponding microservice component.

[0094] Step S203, based on the calling relationship between the multiple microservice components and the local workflow corresponding to each microservice component, determine the global workflow of the target credit business and enter it into the workflow engine.

[0095] Specifically, in step S203, based on the calling relationship between the multiple microservice components and the local workflows corresponding to the various microservice components, determining the global workflow of the target credit business includes:

[0096] According to the execution order and trigger conditions of each microservice component, the local workflows corresponding to each microservice component are combined to determine the global workflow of the target credit business.

[0097] It can be understood that each microservice component has a corresponding execution order and trigger condition. After determining the local workflow of each microservice component, the local workflow can be combined according to the execution order and trigger conditions corresponding to each microservice component to obtain a global workflow, which includes the trigger conditions and specific task information of the business components corresponding to each segmented process node involved in executing the target credit business.

[0098] Step S204: when a processing request for a target credit business is received, the workflow engine calls a component based on the global workflow corresponding to the target credit business to execute the target credit business.

[0099] Specifically, in step S204, the workflow engine calls a component based on the global workflow corresponding to the target credit business, including:

[0100] Step S204-1: The workflow engine executes the local workflow corresponding to each microservice construction in sequence according to the calling relationship between each microservice construction.

[0101] Step S204-2: during the execution of the local workflow, the corresponding process node is started according to the triggering condition of each process node, and the corresponding business component is called through the component calling interface of the process node.

[0102] Step S204-3, determining the output information of the process node through the business component based on the input parameter fields and output parameter fields corresponding to the process node and the business logic.

[0103] It can be understood that after completing the global workflow of the target credit business and entering it into the workflow engine, when the bank credit system receives a processing request for the corresponding credit business, it will select the global workflow corresponding to the credit business, including the local workflows corresponding to each microservice component, and execute the steps in each local workflow in sequence according to the execution order and trigger conditions of each microservice component. After the local workflow corresponding to each microservice component ends, it determines whether to execute the subsequent local workflows of other microservice components based on the final output information.

[0104] During the execution of each local workflow, the trigger conditions of each process node are judged according to the data processing results under the actual credit business. When the corresponding trigger conditions are met, the corresponding business component is called through the component call interface of the process node to perform specific tasks.

[0105] The execution content in the configured local workflow includes specific task information, including the input parameter fields, output parameter fields and business execution logic of the corresponding processing under the process node. The business component can fill in the input parameter fields according to the specific business logic, and perform specific data calculation or judgment operations to obtain the specific output information of the process node.

[0106] Further, in step S204-3, the output information of the process node is determined by the business component based on the input parameter field and the output parameter field corresponding to the process node and the business logic, including:

[0107] Step S204-3-1, calling the input parameter field information corresponding to the input parameter field of the process node in the database;

[0108] Step S204-3-2, process the input parameter field information through business components and business logic, obtain the output parameter field information corresponding to the output parameter field of the process node, and use the output parameter field information as the output information of the current process node.

[0109] It can be understood that when a business component performs a specific operation, the specific input parameter field in the execution content under the node can be filled according to the relevant database to obtain specific input parameter field information. The business component processes the input parameter field information according to the specific configured business logic, such as performing calculations, judgments, and input operations. Then, the field information corresponding to the output parameter field is obtained according to the specific processing results.

[0110] For example, the component corresponding to a certain node is an online verification component, and the operation it needs to perform is to verify the user information online. First, the input parameter fields of the node need to be filled in according to the internal database of the system. For example, the input parameter fields can be user address, assets under the user's name, etc. After filling these fields, specific input parameter field information is obtained; then the input parameter field information is compared with the online data to obtain the verification result information. The specific result can be a match or a mismatch. The verification result can be regarded as the output parameter field. Match or mismatch is the corresponding output parameter field information, which can be regarded as the final output information of the node.

[0111] Step S204-4, starting the next process node based on the output information.

[0112] After the current node outputs information, the next node will determine whether to start according to the corresponding trigger condition. If the output information meets the corresponding trigger condition, the next process node will be started and the corresponding operation will be performed.

[0113] Specifically, in step S204-4, starting the next process node based on the output information includes:

[0114] Compare the output parameter field information of the current process node with the trigger condition of the next process node to determine whether the next process node is triggered;

[0115] When the next process node is triggered, the next process node is started, and the corresponding business component is called through the component calling interface of the next process node.

[0116] It can be understood that for the next process node, it needs to compare its own triggering conditions with the output information of the previous process node to determine whether to start. When the comparison result triggers the start of the next process node, the next process node calls the corresponding component through its corresponding calling interface and performs the corresponding operation. For specific content, please refer to the specific execution steps of the above process nodes, which will not be repeated here.

[0117] The credit business processing method provided by the embodiment of the present invention generates a local workflow corresponding to each microservice component through the node information under the microservice component input by the user, and generates a global workflow in combination with the calling relationship between the microservice components and enters it into the workflow engine, so that when a processing request for a target credit business is received, the workflow engine can call each business component involved in the corresponding global workflow and execute the corresponding task to complete the target credit business. By defining the workflow, the development process of a specific credit business is simplified, and the readability and maintainability of the overall business logic are improved.

[0118] In order to facilitate understanding of the above method embodiment, an example diagram of a local workflow of a microservice component is provided according to an embodiment of the present invention, such as Figure 3 shown.

[0119] The components involved in the credit business include customer management, credit, contract, credit, loan and post-loan management. When calling components through workflow to implement credit business, it mainly relies on independent components pre-written in the system. A component is a relatively independent unit, which is an independent interface or service. Components are divided into basic components and business components. The main function of basic components is to connect the components in series and realize the entire process. Generally, no new components will be added; business components constitute components with corresponding functions, and business components can be expanded as components continue to increase.

[0120] Figure 3 Take the workflow example of credit granting, where the open platform refers to the platform used to interact with customers, and the credit system refers to the system involved in the component calls in the workflow corresponding to the credit business. The business components included in the credit granting component are: credit information verification, credit inquiry, decision call, contract signing, and credit limit generation. These business components are mainly used to be called to execute specific segmented businesses. When generating the local workflow corresponding to the component, the main basic components involved include: process definition, process instance, task, execution, event and gateway. These components are mainly used for users to configure specific workflows.

[0121] When generating a local workflow, first define the credit granting process through the process definition component. For the specific process, see Figure 3First, the credit information is verified. After the verification is passed, the application information is initialized, and then the credit query is called. The results of the credit query and the credit information are passed to the intelligent decision-making engine. Then, based on the results returned by the intelligent decision-making engine, it is determined whether manual approval is required. If the returned result is "Y", no manual approval is required, the contract is automatically signed, and the credit limit is effective. If the returned result is "N", it is a decision rejection, and the reason for rejection is fed back to the channel, and the customer's credit is ended. If the returned result is "R", manual approval is required. Manual approval can define approval nodes. After approval, the contract is automatically signed and the credit limit is effective. If the approval fails, the approval result is returned to the channel.

[0122] Then determine the process instance through the process instance component: establish a common process instance, and subsequent loan products can use this instance.

[0123] Establish corresponding tasks through task components, including information verification, credit inquiry, image upload, calling intelligent decision engine service, initializing manual process, calling Junziqian contract signing, and calling the quota system to make the quota effective.

[0124] The execution component is used to execute the corresponding content according to the context of each process node that has been set. The credit query component is entered only after the credit information is verified. The intelligent decision engine service is called only after the credit query obtains the credit serial number, and then the branch process is determined based on the result returned by the intelligent decision engine.

[0125] Define event triggers to trigger corresponding events when certain conditions are met. For example, you can only query your credit report after completing the credit authorization; and you can upload the credit report to the imaging platform only after downloading it.

[0126] Define a gateway to control the branch process processing of the results returned by the intelligent decision engine.

[0127] The basic components process definition, process instance, task, execution, event and gateway can be understood as process definition: used to describe the definition of business processes, including information such as process nodes, sequence and conditions; process instance: create a specific process instance according to the process definition; task: a work unit in the process instance, used to execute specific business logic; execution component: context information when the process instance is executed, including the currently executed node, process variables, etc.; event: event trigger in the process, which can trigger specific events according to conditions; gateway: branch and merge points in the process, used to control the direction of the process according to conditions.

[0128] The main steps in generating a local workflow are to first determine the credit product business process and the components involved; analyze the input and output parameters and determine the conversion rules; define the product business process and complete the parameter conversion; define the smart form and define the trigger event; complete the determination and review of the process context and save the process; test the product and realize the automatic flow of the process.

[0129] When configuring the workflow of credit business, the business processes related to credit products are determined by working with the product manager. The components involved in the process include: customer management, authorization and agreement, credit inquiry, initial screening, credit granting, credit use, contract signing, decision calling, and loan issuance.

[0130] For example, a complete component process includes: customer registration, authentication, initial screening, authorization and signing of agreements, credit granting, decision calling, obtaining valid credit limit and interest rate and returning them to the customer; the customer then applies for credit, signs the contract and calls the decision, and the loan is released after the decision is passed.

[0131] The entire process is configured in the workflow engine. Each component establishes a standardized service call interface. The input and output fields are saved in the database. When one component calls another component, the input parameter fields of the component are obtained from the database and filled with relevant values. The process engine will convert the called component based on the input and output parameter identifiers, automatically complete the entire loan process, and present the final results to the customer.

[0132] Taking the customer management component as an example, its corresponding local workflow can be as follows: Figure 4 As shown in FIG. 1 , it is an example diagram of a local workflow of another microservice component according to an embodiment of the present invention, such as Figure 4 As shown, the customer management component mainly performs functions such as customer information synchronization, authentication and verification. The business components involved are: basic information verification, OCR recognition, online verification, anti-money laundering verification and synchronization of the user center. The information returned by each component is saved in the database, and the trigger conditions for calling the next component are set. For example, only after the basic customer information verification component passes, the corresponding OCR recognition component will be triggered. The execution will proceed only if the first bit of the returned error code (ret_code) is 0. The trigger conditions of different components may be different.

[0133] In the actual business processing process, when a customer submits a loan application and the customer information is verified, it will automatically trigger the call of the intelligent decision-making engine. The decision-making engine will return the manual transfer mark and enter the manual approval process. First of all, there are many manual approval processes for credit, and the approval positions involved are also relatively complex. Due to the large number of approvals, some positions have low approval efficiency and are prone to errors.

[0134] In order to improve the efficiency of process approval and reduce the problems caused by manual approval, the system adopts the PBFT consensus algorithm, and the asymmetric encryption algorithm is the national secret algorithm SM2+SM3, making the approval process data more secure and forming a corresponding closed loop.

[0135] The PBFT consensus algorithm is a distributed consistency algorithm designed to solve the Byzantine fault tolerance problem in distributed systems. The PBFT algorithm achieves system consistency by ensuring a certain performance with a limited number of nodes and being able to tolerate a certain proportion of faulty or malicious nodes. The core of the algorithm is to ensure that the system can still reach a consistent decision in the presence of faulty or malicious nodes through the collaboration of the primary node and the backup node.

[0136] The main features of the PBFT algorithm include: role definition, view concept, fault tolerance, and communication complexity.

[0137] The role definition refers to the fact that nodes in the system are divided into master nodes and backup nodes. The master node is responsible for receiving client requests and assigning serial numbers before broadcasting to other nodes, while the backup node is responsible for receiving broadcast messages, verifying the legitimacy of requests, voting, and triggering view changes to elect a new master node when necessary.

[0138] A "view" in PBFT describes the current state of a multi-copy system. Each view contains a master node and multiple replica nodes. The system reaches consensus on data within the same view and cannot reach consensus across views.

[0139] The PBFT algorithm can tolerate less than 1 / 3 of invalid or malicious nodes, which may deliberately not respond to requests from other nodes in the cluster, or send erroneous data to different nodes to prevent the system from reaching consensus.

[0140] The communication complexity of the PBFT algorithm is O(n^2), which means that as the number of nodes increases, the number and complexity of communications will increase significantly. In contrast, other algorithms such as Raft have a communication complexity of O(n), which may be more advantageous in large systems.

[0141] The configuration of the global workflow in the above embodiment can be understood as the credit process orchestration. The embodiment of the present invention provides a set of tools and APIs for managing and executing complex business processes, which can realize the orchestration and management of business processes through process definition, task management, event-driven, etc. The core idea is to define the credit business process as a directed acyclic graph (DAG), and describe the sequence and dependency of the process through the connection of nodes and edges.

[0142] In this embodiment, a credit business processing device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0143] This embodiment provides a credit business processing device, such as Figure 5 As shown, including:

[0144] The definition information acquisition module 401 is used to acquire the workflow definition information input by the user. The workflow definition information includes: the calling relationship between multiple microservice components corresponding to the target credit business and the node information corresponding to each microservice component.

[0145] The local workflow generation module 402 is used to generate a local workflow corresponding to each microservice component based on the node information corresponding to each microservice component.

[0146] The global workflow determination module 403 is used to determine the global workflow of the target credit business based on the calling relationship between multiple microservice components and the local workflow corresponding to each microservice component, and enter it into the workflow engine.

[0147] The credit business processing module 404 is used to execute the target credit business by invoking a component based on the global workflow corresponding to the target credit business through the workflow engine when receiving a processing request for the target credit business.

[0148] In some optional implementations, the node information corresponding to the microservice component includes: the business component name, task information, and trigger condition corresponding to each process node in the service process of the corresponding microservice component;

[0149] The local workflow generation module 402, when generating the local workflow corresponding to each microservice component based on the node information corresponding to each microservice component, includes:

[0150] Determine the execution content of each process node according to the business component name, task information and trigger conditions corresponding to each process node under each microservice component;

[0151] Construct the local workflow of the corresponding microservice component based on the execution content of each process node.

[0152] In some optional implementations, the local workflow generation module 402, when determining the execution content of each process node according to the business component name, task information and trigger condition corresponding to each process node under each microservice component, includes:

[0153] Determine the component call interface corresponding to the process node based on the business component name;

[0154] Determine the input parameter fields and output parameter fields and business logic corresponding to the process node based on the task information;

[0155] Determine the execution content of the corresponding process node based on the component call interface, input parameter fields, output parameter fields, business logic and trigger conditions.

[0156] In some optional implementations, the calling relationship of the multiple microservice components includes: the execution order and triggering conditions corresponding to each microservice component;

[0157] The global workflow determination module 403, when determining the global workflow of the target credit business based on the calling relationship between the multiple microservice components and the local workflows corresponding to the respective microservice components, includes:

[0158] According to the execution order and trigger conditions of each microservice component, the local workflows corresponding to each microservice component are combined to determine the global workflow of the target credit business.

[0159] In some optional implementations, the credit business processing module 404, when calling a component based on a global workflow corresponding to a target credit business through a workflow engine, includes:

[0160] The workflow engine executes the local workflow corresponding to each microservice build in sequence according to the calling relationship between each microservice build;

[0161] During the execution of the local workflow, the corresponding process node is started according to the triggering conditions of each process node, and the corresponding business component is called through the component calling interface of the process node;

[0162] Determine the output information of the process node through the business component based on the input parameter fields and output parameter fields corresponding to the process node and the business logic;

[0163] Start the next process node based on the output information.

[0164] In some optional implementations, the credit business processing module 404, when determining the output information of the process node based on the input parameter field and the output parameter field corresponding to the process node and the business logic through the business component, includes:

[0165] Call the input parameter field information corresponding to the input parameter field of the process node in the database;

[0166] The input parameter field information is processed through business components and business logic to obtain the output parameter field information corresponding to the output parameter field of the process node, and the output parameter field information is used as the output information of the current process node.

[0167] In some optional implementations, the credit business processing module 404, when starting the next process node based on the output information, includes:

[0168] Compare the output parameter field information of the current process node with the trigger condition of the next process node to determine whether the next process node is triggered;

[0169] When the next process node is triggered, the next process node is started, and the corresponding business component is called through the component calling interface of the next process node.

[0170] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0171] The credit business processing device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0172] The embodiment of the present invention also provides a computer device having the above Figure 5 The credit business processing device shown.

[0173] See also Figure 6 , Figure 6 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 6 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 6 A processor 10 is taken as an example.

[0174] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0175] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0176] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0177] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0178] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 6 The example of connecting through bus is taken in the following.

[0179] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0180] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0181] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A credit business processing method, characterized in that: The method comprises: Acquire workflow definition information input by a user, wherein the workflow definition information includes: a calling relationship between multiple microservice components corresponding to a target credit business and node information corresponding to each microservice component; Generate the local workflow corresponding to each microservice component based on the node information corresponding to each microservice component; Based on the calling relationship between the multiple microservice components and the local workflows corresponding to the respective microservice components, a global workflow of the target credit business is determined and entered into a workflow engine; When a processing request for a target credit business is received, the workflow engine calls a component based on the global workflow corresponding to the target credit business to execute the target credit business.

2. The method according to claim 1, characterized in that The node information corresponding to the microservice component includes: the business component name, task information and trigger condition corresponding to each process node in the service process of the corresponding microservice component; The generating of the local workflow corresponding to each microservice component based on the node information corresponding to each microservice component includes: Determine the execution content of each process node according to the business component name, task information and trigger conditions corresponding to each process node under each microservice component; A local workflow of the corresponding microservice component is constructed based on the execution content of each process node.

3. The method according to claim 2, characterized in that Determining the execution content of each process node according to the business component name, task information and trigger condition corresponding to each process node under each microservice component includes: Determine the component calling interface corresponding to the process node according to the business component name; Determine the input parameter field and output parameter field and the business logic corresponding to the process node according to the task information; The execution content of the corresponding process node is determined according to the component calling interface, input parameter fields, output parameter fields, business logic and trigger conditions.

4. The method according to claim 1, characterized in that: The calling relationship of the multiple microservice components includes: the execution order and triggering conditions corresponding to each microservice component; Determining the global workflow of the target credit business based on the calling relationship between the multiple microservice components and the local workflows corresponding to the respective microservice components includes: The local workflows corresponding to the various microservice components are combined according to the execution order and trigger conditions corresponding to the various microservice components to determine the global workflow of the target credit business.

5. The method according to claim 3, characterized in that: The calling component based on the global workflow corresponding to the target credit business by the workflow engine includes: The workflow engine sequentially executes the local workflow corresponding to each microservice construction according to the calling relationship between the microservice constructions; During the execution of the local workflow, the corresponding process node is started according to the triggering conditions of each process node, and the corresponding business component is called through the component calling interface of the process node; Determine the output information of the process node by the business component based on the input parameter field and the output parameter field corresponding to the process node and the business logic; The next process node is started based on the output information.

6. The method according to claim 5, characterized in that The determining the output information of the process node based on the input parameter field and the output parameter field corresponding to the process node and the business logic through the business component includes: Call the input parameter field information corresponding to the input parameter field of the process node in the database; The input parameter field information is processed through the business component and business logic to obtain the output parameter field information corresponding to the output parameter field of the process node, and the output parameter field information is used as the output information of the current process node.

7. The method according to claim 6, characterized in that The starting the next process node based on the output information includes: Compare the output parameter field information of the current process node with the trigger condition of the next process node to determine whether the next process node is triggered; When the next process node is triggered, the next process node is started, and the corresponding business component is called through the component calling interface of the next process node.

8. A credit business processing device, characterized in that: The device comprises: A definition information acquisition module is used to acquire workflow definition information input by a user, wherein the workflow definition information includes: a calling relationship between multiple microservice components corresponding to a target credit business and node information corresponding to each microservice component; A local workflow generation module is used to generate a local workflow corresponding to each microservice component based on the node information corresponding to each microservice component; A global workflow determination module, used to determine the global workflow of the target credit business based on the calling relationship between the multiple microservice components and the local workflows corresponding to the respective microservice components, and input the global workflow into the workflow engine; The credit business processing module is used to, when receiving a processing request for a target credit business, call a component based on the global workflow corresponding to the target credit business through a workflow engine to execute the target credit business.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the credit business processing method according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the credit business processing method according to any one of claims 1 to 7.

Images