A method for online analysis and testing of multiple data sources in a credit scenario

By establishing a unified external data debugging interface and decision flow branch processing in credit scenarios, data source management and coupling problems are solved, and the flexible configuration and cost control of data sources are realized, which improves the convenience of data source debugging and business separation.

CN117785982BActive Publication Date: 2024-11-19SU YIN KAIJI CONSUMER FINANCE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410017928.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-01-05
Publication Date
2024-11-19
Estimated Expiration
2044-01-05

AI Technical Summary

Technical Problem

The existing technology lacks unified management of online data sources in credit scenarios, resulting in coupling of debugging data sources with real-time production decision flow, which easily leads to overspending data costs and lacks flexibility in configuration, and complex operations on and off-line for debugging data sources.

Method used

Establish a unified external data debugging interface in the risk control system, receive and forward external data source access requests through a unified decision flow interface, configure different branch processes according to different scenario coding, and use the message queue to asynchronously fall database query results to achieve the Unified management and separation of data sources.

Benefits of technology

It realizes unified management of online data sources, improves the convenience of debugging data sources, avoids the impact of real-time production of production parts and data source failures due to debugging data sources, reduces data costs and simplifies configuration and operation processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117785982B_ABST
    Figure CN117785982B_ABST
Patent Text Reader

Abstract

The present invention discloses a multi-data source online analysis and testing method in a credit scenario, comprising the following steps: S1: establishing a unified external data debugging interface; S2: when a user initiates a transaction, an additional call is made according to the configured scenario set; S3: the decision flow of the call; S4: according to different scenario codes, go to different decision flow branches; S5: in each different scenario branch, first obtain the configuration of the sample quantity control that needs to be debugged in the scenario; S6: call the data source node in the decision flow; S7: the data source returns the corresponding query result, assigns the result to the decision process, and configures the rule as needed; S8: query results and intermediate variable data asynchronously through the message queue. The present invention manages the data sources that need online debugging in a unified manner, and can quickly count which data sources appear to improve convenience in the debugging stage.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of online data verification, and in particular relates to an online analysis and testing method for multiple data sources in a credit scenario. Background Art

[0002] According to the relevant laws and regulations such as the Law of the People's Republic of China on the Protection of Personal Information, financial institutions shall not engage in commercial cooperation with market institutions that have not obtained legal credit reporting qualifications to obtain credit reporting services. Therefore, when conducting financial credit business, if a new manufacturer's data source is needed, it must be accessed through a credit reporting agency. Therefore, every time a new data source is added, it is necessary to debug and verify online with the manufacturer and the credit reporting agency. Therefore, online verification must meet a certain number of production samples, and the database must store enough data source data samples.

[0003] At present, the existing data source access is to embed the data source module in each real-time production decision flow of the platform. Each decision flow corresponds to its own external data source that needs to be debugged. When the real-time incoming traffic of each channel comes, the decision flow of the corresponding channel scenario is called, and the external data source is called in real time in the decision flow, and then stored in the warehouse together with the incoming data. However, this method has the following problems:

[0004] 1. There is no unified management of data sources that need online debugging. It is necessary to check in the decision flow of the system to count which data sources are in the debugging stage;

[0005] 2. The debugging data source is coupled with the production real-time decision-making flow input business. When the debugging data source fails, the production real-time input will also be affected;

[0006] 3. Lack of monitoring of data source usage can easily lead to data cost overspending;

[0007] 4. The configuration lacks flexibility, and the debugging of data sources is complicated. Summary of the invention

[0008] The main technical problem solved by the present invention is that the current solution does not have a unified management of the data source that needs online debugging. At the same time, the debugging data source is coupled with the production real-time decision-making flow input business, which easily causes data cost overspending, and the configuration lacks flexibility. The online and offline operations of the debugging data source are complicated.

[0009] In order to solve the above technical problems, a technical solution adopted by the present invention is:

[0010] A method for online analysis and testing of multiple data sources in a credit scenario includes the following steps:

[0011] S1): Establish a unified external data debugging interface: In the Controller module of the risk control system, add an interface that can uniformly call the fixed decision flow, receive the external data source access request that needs to be debugged, and forward it to the corresponding decision flow interface;

[0012] S2): When a user initiates a transaction, an additional call is made according to the configured scenario set: In a credit transaction, the user initiates a request on the client side, which is verified by the front-end system and sent to the risk control decision engine system for pre-processing. At the same time, a decision flow interface request for its own execution is sent, calling the unified online data source to debug the decision flow interface;

[0013] S3): Called decision flow: expose the online data source debugging decision flow interface, receive the sent request parameters to the decision flow, where the application module is the engine module, which is called by the Controller module and receives the sent request parameters to the decision flow;

[0014] S4): According to different scenario codes, go to different decision flow branches: The unified online data source debugging decision flow configuration configures different branches according to different scenario codes. The request parameters sent by the Controller contain businessCode. The decision flow enters different business branch processes according to the corresponding businessCode and flows under the current branch;

[0015] S5): In each different scenario branch, obtain the configuration of the number of samples that need to be debugged in the scenario through serial communication in the system process;

[0016] S6): Call the required data source node in the decision flow: call the external data source through the system's own HTTP. In this data source debugging process, only the selected data source will be called through the external data call module;

[0017] S7): The data source returns the corresponding query results, assigns the results to the decision-making process, and configures rules as needed;

[0018] S8): Asynchronously store query results and intermediate variable data in the database through the message queue: After querying the relevant external data source debugging information from DSM, the information will be transmitted through the message queue rocketMQ. The database interaction module used by the consumer end is the DBdata module. After interacting with Oracle through the persistence component mybatis, the fields that need to be stored are structured and stored in the oracle data table.

[0019] Furthermore, in the step S1, the debugging interface can also be provided to the engine module in the application for calling. In the decision flow, the interface can be called to debug external data that has not been verified.

[0020] Furthermore, in the step S2, the verification of the front-end system includes identity information and data legitimacy.

[0021] Furthermore, in the S4 step, businessCode is divided into the following branches:

[0022] Channel 1: Credit granting;

[0023] Channel 2: Use letters;

[0024] Channel 3: Adjustment of quota.

[0025] Furthermore, in the S5 step, after entering the branch process corresponding to the businessCode, the first node is the configuration of the number of external data source samples and the expiration time that the branch needs to debug. When reaching this node, the number of samples and the expiration time and batch information that need to be configured this time can be obtained.

[0026] Furthermore, in the S7 step, when executing the external debugging data source call node, the intelligent decision engine will call the thirdData module. When configured as multiple data sources, the total length of concurrent calls through the thread pool is the data source that consumes the most time.

[0027] Furthermore, the destination address of the external data source call is a unified DSM. After receiving the request from the decision engine, the DSM routes to different external data source interfaces according to the apiCode, and then requests the external data source manufacturer interface based on the transmitted customer information, obtains the interface service information provided by the external data source manufacturer in real time, and assigns the information to the unified format of the external data source and returns it, where the information also includes the sample quantity configuration information passed from the thirdData module.

[0028] Furthermore, in the step S8, the producer is a decision engine, and the message body transmitted includes the queried debugging external data source information and the intermediate variables generated in the decision flow.

[0029] Furthermore, in the step S8, components are applied and table fields are defined, and then a database table is created for structured storage.

[0030] Beneficial effects of the present invention:

[0031] The present invention will uniformly manage the data sources that need online debugging, and can quickly count which data sources appear to improve convenience during the debugging stage. At the same time, the debugging data source and the production real-time decision-making flow input business are turned into branch processing. When any one of them has a problem, it will not affect the others. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0033] Figure 1 It is a schematic diagram of the system module calling flow provided by the present invention;

[0034] Figure 2 It is a schematic diagram of the online data source debugging decision flow provided by the present invention; DETAILED DESCRIPTION

[0035] The preferred embodiments of the present invention are described in detail below in conjunction with the accompanying drawings so that the advantages and features of the present invention can be more easily understood by those skilled in the art, thereby making a clearer and more definite definition of the protection scope of the present invention. Specific embodiments

[0036] like Figure 1 to Figure 2 As shown, a multi-data source online analysis test method in a credit scenario includes the following steps:

[0037] S1): Establish a unified external data debugging interface: In the Controller module (a function in Java syntax) of the risk control system, add an interface that can uniformly call the fixed decision flow, receive the external data source access request that needs to be debugged, and forward it to the corresponding decision flow interface; specifically, the debugging interface can also be provided to the engine module (a function in Java syntax) in the application for calling. In the decision flow, the interface can be called to debug the external data that has not been verified;

[0038] S2): When the user initiates a transaction, an additional call is made according to the configured scenario set: In a credit transaction, the user initiates a request on the client side, which is verified by the front-end system and sent to the risk control decision engine system for pre-processing. At the same time, the decision flow interface request for its own execution is sent, and the unified online data source is called to debug the decision flow interface. Specifically, the verification of the front-end system includes identity information and data legitimacy.

[0039] S3): Called decision flow: expose the online data source debugging decision flow interface, receive the sent request parameters to the decision flow, where the application module is the engine module, which is called by the Controller module and receives the sent request parameters to the decision flow;

[0040] S4): According to different scenario codes, go to different decision flow branches: The unified online data source debugging decision flow configuration configures different branches according to different scenario codes. The request parameters sent by the Controller contain businessCode (unified number). The decision flow enters different business branch processes according to the corresponding businessCode and flows under the current branch; specifically, in the S4 step, the businessCode is divided into the following branches:

[0041] Channel 1: credit granting; Channel 2: credit utilization; Channel 3: credit limit adjustment.

[0042] If the businessCode is channel 1, then the request to debug the external data source will only go to the branch where channel 1 is located and flow to the node next to branch 1;

[0043] S5): In each different scenario branch, first obtain the configuration of the number of samples that need to be debugged in the scenario; specifically, after entering the branch process corresponding to the businessCode, the first node is the configuration of the number of external data source samples and expiration time that need to be debugged in the branch. When you reach this node, you can obtain the number of samples, expiration time and batch information that need to be configured this time;

[0044] For example, apiCode=WS_BR_035, count=50000, expireTime=20230731, batchNum=1, and then pass the data down.

[0045] S6): Call the external data source through the system's own HTTP (a computer protocol). In this process of debugging the data source, only the selected data source will be called through the external data calling module;

[0046] S7): The data source returns the corresponding query result, assigns the result to the decision process, and configures the rules as needed; specifically, when executing the external debugging data source call node, the intelligent decision engine will call the thirdData module (a function of Java syntax). When configured as multiple data sources, the total concurrent call time through the thread pool is the data source that consumes the most time; the destination address of the external data source call is a unified DSM (network server management, DiskStationManager). After receiving the request of the decision engine, the DSM routes to different external data source interfaces according to the apiCode, and then requests the external data source manufacturer interface according to the transmitted customer information, obtains the interface service information provided by the external data source manufacturer in real time, and assigns the information to the unified format of the external data source and returns it, where the information also includes the sample quantity configuration information passed in the thirdData module;

[0047] S8): Asynchronous database query results and intermediate variable data through message queues: After querying the relevant external data source debugging information from DSM, the information will be transmitted through the message queue rocketMQ (a unified message processing engine). The database interaction module used by the consumer end is the DBdata module (a function in Java syntax), and then through the persistence component mybatis (a persistence layer framework) and Oracle (a database), the fields to be stored are structured and stored in the oracle data table. Specifically, the producer is the decision engine, and the message body transmitted includes the query debugging external data source information and the intermediate variables generated in the decision flow, among which, by applying components and defining table fields, a database table is created for structured storage.

[0048] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structural transformations made using the contents of the present invention's specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for online analysis and testing of multiple data sources in a credit scenario, characterized by: The following steps are involved: S1): Establish a unified external data debugging interface: In the Controller module of the risk control system, add an interface that can uniformly call the fixed decision flow, receive the external data source access request that needs to be debugged, and forward it to the corresponding decision flow interface; S2): When a user initiates a transaction, an additional call is made according to the configured scenario set: In a credit transaction, the user initiates a request on the client side, which is verified by the front-end system and sent to the risk control decision engine system for pre-processing. At the same time, a decision flow interface request for its own execution is sent, calling the unified online data source to debug the decision flow interface; S3): Called decision flow: expose the online data source debugging decision flow interface, receive the sent request parameters to the decision flow, where the application module is the engine module, which is called by the Controller module and receives the sent request parameters to the decision flow; S4): According to different scenario codes, go to different decision flow branches: The unified online data source debugging decision flow configuration configures different branches according to different scenario codes. The request parameters sent by the Controller contain businessCode. The decision flow enters different business branch processes according to the corresponding businessCode and flows under the current branch; S5): In each different scenario branch, obtain the configuration of the number of samples that need to be debugged in the scenario through serial communication in the system process; S6): Call the required data source node in the decision flow: call the external data source through the system's own HTTP. In this data source debugging process, only the selected data source will be called through the external data call module; S7): The data source returns the corresponding query results, assigns the results to the decision-making process, and configures rules as needed; S8): Asynchronously store query results and intermediate variable data in the database through the message queue: After querying the relevant external data source debugging information from DSM, the information will be transmitted through the message queue rocketMQ. The database interaction module used by the consumer end is the DBdata module. After interacting with Oracle through the persistence component mybatis, the fields that need to be stored are structured and stored in the oracle data table.

2. According to claim 1, the online analysis and testing method for multiple data sources in a credit scenario is characterized by: In the step S1, the debugging interface can also be provided to the engine module in the application for calling. In the decision flow, the interface can be called to debug external data that has not been verified.

3. The online analysis and testing method for multiple data sources in a credit scenario according to claim 1 is characterized by: In the step S2, the verification of the front-end system includes identity information and data legitimacy.

4. The online analysis and testing method for multiple data sources in a credit scenario according to claim 1 is characterized by: In the S4 step, businessCode is divided into the following branches: Channel 1: Credit granting; Channel 2: Use letters; Channel 3: Adjustment of quota.

5. The online analysis and testing method for multiple data sources in a credit scenario according to claim 1, characterized in that: In the S5 step, after entering the branch process corresponding to the businessCode, the first node is the configuration of the number of external data source samples and the expiration time that the branch needs to debug. When you reach this node, you can obtain the number of samples, expiration time and batch information that need to be configured this time.

6. The online analysis and testing method for multiple data sources in a credit scenario according to claim 1, characterized in that: In the S7 step, when executing the external debugging data source call node, the intelligent decision engine will call the thirdData module. When configured as multiple data sources, the total length of concurrent calls through the thread pool is the data source that consumes the most time.

7. The online analysis and testing method for multiple data sources in a credit scenario according to claim 6, characterized in that: The destination address of the external data source call is a unified DSM. After receiving the request from the decision engine, the DSM routes to different external data source interfaces according to the apiCode, and then requests the external data source manufacturer interface based on the transmitted customer information, obtains the interface service information provided by the external data source manufacturer in real time, and assigns the information to the unified format of the external data source and returns it, where the information also includes the sample quantity configuration information passed from the thirdData module.

8. The online analysis and testing method for multiple data sources in a credit scenario according to claim 1, characterized in that: In the step S8, the producer is the decision engine, and the message body transmitted includes the queried debugging external data source information and the intermediate variables generated in the decision flow.

9. The online analysis and testing method for multiple data sources in a credit scenario according to claim 1, characterized in that: In the step S8, components are applied and table fields are defined, and then a database table is created for structured storage.