Credit investigation data processing system and credit investigation data processing method

Abstract

The invention discloses a credit investigation data processing system and a credit investigation data processing method, and relates to the technical field of data processing, the system comprises a credit investigation visualization low-code construction module used for constructing a code file based on interface form information, and the code file comprises a process engine service package; the credit investigation service front-end module is used for sending a credit investigation data query request to the credit investigation process engine service module when the code file is constructed; the credit investigation process engine service module is used for loading the process engine service package to a target project; and the credit investigation process engine service module is also used for receiving the credit investigation data query request through the target project project, and determining and returning target query credit investigation data according to the credit investigation data query request. By applying the technical scheme, the technical problems of low efficiency, high cost and poor compatibility and expansibility when third-party credit data is accessed by adopting a customized development method in the traditional financial technical field in the prior art are solved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a credit investigation data processing system and a credit investigation data processing method. Background Art

[0002] With the development of economy and the progress of science and technology, the consumer finance industry has undergone profound changes. Driven by the wave of digitalization, financial institutions are constantly innovating and expanding service models to meet the growing and diverse needs of consumers. At present, licensed credit reporting agencies, as credit information service carriers, provide financial institutions with services to assess the credit risk of loan applicants, which helps financial institutions make more accurate judgments when approving loans and reduce bad debt risks.

[0003] When the traditional financial industry faces different credit reporting agencies connecting to different data services, because each product requires different credit data, and the structure, form, and protocol of the docking data interface are different, it usually needs to adopt a customized development method, through which the request object, encrypted data packet, decrypted data, response results, and data storage are customized. However, this method has poor modularity and low reusability, resulting in a long R&D cycle and an inability to respond quickly to business, causing financial institutions to face problems of low efficiency, high cost, poor compatibility, and poor scalability when accessing third-party credit reporting data.

[0004] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a credit data processing system and a credit data processing method, aiming to solve the technical problems in the prior art that when the traditional financial technology field uses customized development methods to access third-party credit data, it is usually inefficient, costly, and has poor compatibility and scalability.

[0006] To achieve the above-mentioned purpose, the present application proposes a credit investigation data processing system, the system comprising: a credit investigation visualization low-code construction module, a credit investigation service front-end module and a credit investigation process engine service module;

[0007] The credit investigation visualization low-code construction module is used to construct a code file based on the interface form information, and the code file includes: a process engine service package;

[0008] The credit reporting service front-end module is used to send a credit reporting data query request to the credit reporting process engine service module when the code file is built;

[0009] The credit investigation process engine service module is used to load the process engine service package into the target project;

[0010] The credit process engine service module is also used to receive the credit data query request through the target project engineering, and determine and return the target query credit data according to the credit data query request.

[0011] In one embodiment, the credit reporting visualization low-code construction module is used to determine the name of the credit reporting agency based on the interface form information, and to build a process engine service package and an offline storage engine package according to the name of the credit reporting agency;

[0012] The credit investigation visualization low-code construction module is also used to determine the interface number according to the interface form information when the construction is completed;

[0013] The credit investigation visualization low-code construction module is also used to determine the entity service connection relationship based on the interface number;

[0014] The credit investigation visualization low-code construction module is also used to associate the entity number with the request response entity class information corresponding to the response message based on the entity service connection relationship;

[0015] The credit investigation visualization low-code construction module is also used to associate the entity attribute number with the entity association attribute in the request response entity class information to build a code file when the association is completed.

[0016] In one embodiment, the credit investigation visualization low-code construction module is also used to generate a database configuration script based on the request message, response message and partner sample message through JSON parsing when the association is completed;

[0017] The credit information visualization low-code construction module is also used to render data based on the database configuration script and the preset data rendering engine to generate a code file;

[0018] The credit investigation visualization low-code construction module is also used to push the process engine service package and the offline storage engine package in the code file to the remote Nexus library.

[0019] In one embodiment, the credit reporting service front-end module is further used to load the code file into the credit reporting service front-end project when the code file is built to update the interface service capability of the request interface, and the code file supports the Kafka protocol, the Dubbo protocol or the Http protocol;

[0020] The credit investigation service front-end module is further used to receive a credit investigation call request through an updated request interface;

[0021] The credit investigation service front-end module is also used to perform compliance verification on the credit investigation call request;

[0022] The credit investigation service front-end module is further used to determine the request function corresponding to the credit investigation call request when the verification is completed, and the request function includes: a cache query function;

[0023] The credit investigation service front-end module is further used to query the credit investigation data required by the credit investigation call request if the request function is the cache query function.

[0024] In one embodiment, the credit service front-end module is further configured to obtain a credit data query condition based on the credit call request if the request function is the cache query function;

[0025] The credit service front-end module is further used to perform cache query according to the credit data query condition;

[0026] The credit service front-end module is also used to determine the cache identifier currently hit when hitting the cache, and store the cache identifier in the current query record.

[0027] In one embodiment, the credit investigation process engine service module is further used to receive all requests sent by the credit investigation service front-end module through the target project;

[0028] The credit investigation process engine service module is further used to desensitize the sensitive data in the request to obtain desensitized request data;

[0029] The credit reporting process engine service module is also used to encrypt and sign the desensitized request data, and send the encrypted and signed request data to the credit reporting agency.

[0030] In one embodiment, the credit process engine service module is further used to receive target credit data returned by the partner;

[0031] The credit process engine service module is further used to perform signature verification and decryption processing on the target credit data to obtain the processed target credit data;

[0032] The credit investigation process engine service module is also used to send the processed target credit investigation data to the credit investigation service front-end module.

[0033] In one embodiment, the system further comprises: a credit investigation offline storage engine module;

[0034] The credit investigation offline storage engine module is used to load the offline storage engine package from the remote Nexus library to the first project;

[0035] The credit investigation offline storage engine module is also used to store offline credit investigation data through the first project.

[0036] In addition, to achieve the above purpose, the present application also proposes a credit investigation data processing method, the method comprising:

[0037] Building a code file based on the interface form information, the code file includes: a process engine service package;

[0038] When the code file is built, the process engine service package is loaded into the target project;

[0039] A credit data query request is received through the target project engineering, and target query credit data is determined and returned according to the credit data query request.

[0040] In one embodiment, the step of constructing a code file based on the interface form information includes:

[0041] Determine the name of the credit reporting agency based on the interface form information, and build a process engine service package and an offline storage engine package according to the name of the credit reporting agency;

[0042] When the construction is completed, the interface number is determined according to the interface form information;

[0043] Determine the entity service connection relationship based on the interface number;

[0044] Associating the entity number with the request response entity class information corresponding to the response message based on the entity service connection relationship;

[0045] The entity attribute number is associated with the entity association attribute in the request response entity class information to construct a code file when the association is completed.

[0046] The present application provides a credit data processing system, which discloses a credit visualization low-code construction module, a credit service front-end module and a credit process engine service module; the credit visualization low-code construction module is used to construct a code file based on the interface form information, and the code file includes: a process engine service package; a credit service front-end module is used to send a credit data query request to the credit process engine service module when the code file is built; the credit process engine service module is used to load the process engine service package into the target project engineering; the credit process engine service module is also used to receive the credit data query request through the target project engineering, and determine according to the credit data query request And returns the target query credit data; compared with the prior art, the traditional financial industry needs to adopt a customized development method when facing different credit agencies to connect with different data services, which leads to the financial institutions facing low efficiency, high cost, poor compatibility and scalability when accessing third-party credit data. The present invention constructs a code file based on interface form information, and loads the process engine service package in the code file to the target project project to receive the credit data query request to return the target query credit data, thereby solving the technical problems of low efficiency, high cost, poor compatibility and scalability when the traditional financial technology field in the prior art adopts a customized development method to access third-party credit data. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0048] In order to more clearly illustrate the embodiments of the present application 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, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0049] Figure 1 A structural block diagram of the first embodiment of the credit investigation data processing system of this application;

[0050] Figure 2 This is a schematic diagram of the component modules of the credit investigation data processing system for this application;

[0051] Figure 3 This is the overall process module diagram of the credit investigation data processing system for this application;

[0052] Figure 4 The interface development flow chart for the credit data processing system for this application;

[0053] Figure 5 This is a schematic diagram of the low-code components of the credit data processing system for this application;

[0054] Figure 6 Build a data modeling diagram for the low-code credit data processing system for this application;

[0055] Figure 7 This is a code template diagram for constructing the credit data processing system for this application;

[0056] Figure 8 This is the structure diagram of the dynamic configuration process engine of the credit data processing system for this application;

[0057] Fig. 9 A structural block diagram provided for the second embodiment of the credit investigation data processing system of this application;

[0058] Fig.10 This is a flow chart of the first embodiment of the credit data processing method provided by the present application based on the above-mentioned credit data processing system.

[0059] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0060] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0061] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0062] The main solution of the embodiment of the present application is: a credit investigation visualization low-code construction module, which is used to construct a code file based on the interface form information, and the code file includes: a process engine service package; a credit investigation service front-end module, which is used to send a credit investigation data query request to the credit investigation process engine service module when the code file is constructed; a credit investigation process engine service module, which is used to load the process engine service package into the target project engineering; the credit investigation process engine service module is also used to receive the credit investigation data query request through the target project engineering, and determine and return the target query credit data according to the credit investigation data query request.

[0063] Because the traditional financial industry in the existing technology needs to adopt customized development methods when connecting different credit reporting agencies with different data services, financial institutions face problems such as low efficiency, high cost, poor compatibility and scalability when accessing third-party credit reporting data.

[0064] The present application provides a solution that can construct a code file based on interface form information, and load the process engine service package in the code file into the target project engineering to receive credit data query requests to return the target query credit data, thereby solving the technical problems in the prior art that the traditional financial technology field uses customized development methods to access third-party credit data, which is usually low in efficiency, high in cost, and poor in compatibility and scalability.

[0065] Reference Figure 1 , Figure 1 This is a structural block diagram provided for Example 1 of the credit investigation data processing system of this application.

[0066] like Figure 1 As shown, the credit data processing system of this embodiment includes: a credit visualization low-code construction module 10, a credit service front-end module 20 and a credit process engine service module 30.

[0067] The credit investigation visualization low-code construction module 10 is used to construct a code file based on interface form information, and the code file includes: a process engine service package.

[0068] It should be noted that the credit data processing system proposed in this embodiment can build low-code interface service development and method execution based on the visual configuration process, refer to Figure 2 , Figure 2 This is a schematic diagram of the component modules of the credit investigation data processing system for this application. Figure 2 As shown, the main modules of the system are divided into a credit investigation visualization low-code construction module 10, a credit investigation low-code component module, a credit investigation service front-end module 20, a credit investigation process engine service module 30, and a credit investigation offline storage engine module 40. Figure 3 , Figure 3 This is the overall process module diagram of the credit investigation data processing system for this application. Figure 3 As shown in the figure, from the data flow, the credit information query requests of the decision center, application center, and third-party channel center in this solution are connected to the system through a unified gateway, and Kafka and Dubbo are used to realize asynchronous message processing and efficient calls between services (such as calling loan balance data). At the same time, Nginx can also be deployed as a reverse proxy server to realize the access proxy of external services and traffic distribution based on load balancing to ensure the high availability and scalability of the system. The credit data service processing layer is used for data processing, and its functions may include: building requests, encrypting requests, decrypting responses, and transaction responses. In addition, it can also process request handlers, encryption handlers, decryption handlers, and response handlers. The credit data offline storage layer is equipped with general storage Oracle and MQ, which can provide services such as monitoring data messages, API services, sending result messages, and ORM.

[0069] It should be noted that, from the implementation method, refer to Figure 4 , Figure 4 This is the interface development flow chart of the credit data processing system for this application. Figure 4 As shown, in this scheme, the credit investigation visualization low-code construction module 10 is operated through a visual interface. According to the form, the interface elements are filled in, and one-click construction is made to abstractly generate the process steps, entities, data storage and other low-code public component modules for requesting the credit investigation agency interface. The specific functions include: providing a visual back-end management platform for R&D personnel to dynamically configure and generate public process code modules. Specifically, the visualization interface provides input and output operations of the interface, so that the partner name (that is, the above-mentioned interface form information) can be customized in the visualization interface. Input, and according to the naming, the process engine service jar (that is, Figure 4 Process code package in ), offline storage engine jar (ie Figure 4 ), and customize the partner's jar release version to build the code file. The visual interface is divided into request messages and response messages. The partner's sample message is copied and pasted, and converted into an SQL script through json parsing to build a low-code original configuration table. In addition, this embodiment can also provide an automatic packaging service for code modules, and upload it to the MAVEN warehouse, while introducing package dependencies. When using it, you only need to synchronize the dependencies back.

[0070] It should be noted that the above-mentioned process engine service package may be a code package for compiling and building a target project engineering, wherein the target project engineering may be a project engineering for receiving a request sent by the credit reporting service front-end module 20 .

[0071] In this embodiment, the credit investigation visualization low-code construction module 10 can build a server-side framework based on Springboot+Mybatis+Shiro+Mybatis+Thymeleaf, and the client module uses the vue front-end and back-end separation design, which can configure the mapping relationship and driver of the response data entity and table (such as Figure 4 The URL configuration and CREATE TABLE (statement for creating a table) shown in the figure are automatically built into the offline listening component and entity database mapping module. In addition, the code module automatic packaging service is also provided and uploaded to the MAVEN warehouse. When using it, you only need to synchronize the dependencies back. Figure 5 , Figure 5 This is a schematic diagram of the low-code components of the credit data processing system for this application. Figure 5As shown, the low-code components in this embodiment may include: SQL script management, Jar package management, Maven management and code module management. Among them, SQL script management includes: building process service DML scripts and building offline data service DML scripts, wherein the process service DML script includes: request processing SQL, encryption processing SQL, sending request processing SQL, decryption processing SQL and response message processing SQL; offline data service DML scripts include: listening request SQL, interface data mapping SQL, entity relationship mapping SQL and database insertion SQL. Jar package management includes: building process engine service Jar and building offline data storage engine Jar, wherein the process engine service Jar includes: request processing Class, encryption processing Class, sending request processing Class, decryption processing Class and response message processing Class; offline data service DML scripts include: listening request Class, interface data mapping Class, entity relationship mapping Class and database insertion Class. Maven management includes the management of Maven warehouses and version numbers (such as 1.0.0), wherein the Maven warehouse can store process service jars and offline data jars. Code module management can include the management of template files and Class, where template files include: request / response entity template files, process step template files, offline listening template files and offline data storage ORM (Object Relational Mapping) template files; Class includes: bean entity class, service class for connecting various beans, listening data class and ORM class.

[0072] Furthermore, the credit reporting visualization low-code construction module 10 is used to determine the name of the credit reporting agency based on the interface form information, and to build a process engine service package and an offline storage engine package according to the name of the credit reporting agency.

[0073] It should be understood that the above-mentioned credit reporting agency name can be the name of the licensed credit reporting agency currently cooperating with the financial institution. In this embodiment, the interface form information filled in the visual interface usually includes the name of the credit reporting agency of this cooperation, so that the name of the credit reporting agency can be directly queried based on the interface form information later.

[0074] It is understandable that the above-mentioned offline storage engine package can be a code package for compiling and building a first project, wherein the first project can be a project for monitoring data storage requests. In this embodiment, the name of the credit reporting agency can formulate a naming rule for building a process engine service package and an offline storage engine package. For example, if the name of the credit reporting agency is abcd, the process engine service package built at this time can be youcash-upmp-abcd-service.jar, and correspondingly, the offline storage engine package can be youcash-upmp-abcd-datastore.jar.

[0075] The credit investigation visualization low-code construction module 10 is also used to determine the interface number according to the interface form information when the construction is completed.

[0076] It should be noted that the above interface number can be a user-defined number for identifying the interface service, and this embodiment does not limit this. In this embodiment, the user can fill in the interface form information in advance through the visual interface to define the interface number, so that the user-defined interface number can be directly determined based on the interface form information later. For example, in this embodiment, the interface number can be defined as apiCode.

[0077] The credit investigation visualization low-code construction module 10 is also used to determine the entity service connection relationship based on the interface number.

[0078] It should be noted that the above entity service connection relationship may be a mapping relationship between entity attributes and tables.

[0079] The credit investigation visualization low-code construction module 10 is also used to associate the entity number with the request response entity class information corresponding to the response message based on the entity service connection relationship.

[0080] The credit investigation visualization low-code construction module 10 is also used to associate the entity attribute number with the entity association attribute in the request response entity class information to construct a code file when the association is completed.

[0081] In this embodiment, refer to Figure 6 , Figure 6 The low-code data modeling diagram for the credit data processing system of this application is constructed. Figure 6As shown, the low-code package in this solution may include: a process engine package and an offline data package, and the basic interface information of the two includes: a table structure and request response definition information, wherein the table structure of the process engine package consists of an interface number, an interface type, a serial service bean, an interface switch, and an interface address; the request response definition information includes: a table structure and request response entity class information, wherein the table structure of the request response definition information consists of an interface number, a basic class, a mapping class, and an entity type; the request response entity class information of the request response definition information includes: a table structure and class attribute information, wherein the table structure consists of the above-mentioned entity number body_id, a class name, and a class type, and the request response entity class information consists of the above-mentioned entity attribute number body_c_id and a field. In addition, the structure of the offline data package is as shown in Figure 6 In actual application, users can customize the interface number apiCode through the visual interface. The apiCode is responsible for the specific interface service identification under the partner package. Through this identification, according to the relationship between the process service engine entity attributes and tables, the apiCode is used to concatenate the request entity to return the entity service (i.e. Figure 6 The request response definition information in upmp_jar_partner_body) connection relationship is associated with the entity corresponding to the response message (i.e. Figure 6 The request response entity class information upmp_jar_partner_body_c in the body_c_id (i.e. the above entity attribute number) is associated with the entity association attribute table corresponding to the response message (i.e. Figure 6 class attribute information in upmp_jar_partner_body_f) to build the code file when the association is completed.

[0082] It should be noted that if Figure 6 As shown, in this embodiment, in order to solve the problem that some partners' requests and responses are all the same object header, the identifier "@" can be added to distinguish and rename the object entity. Regarding the relationship between the offline storage response entity attributes and the table, in the response message module, the identifier "#" + TABLE needs to be appended after the object to be stored in the library, so that the field attributes of the structure object correspond to the table attributes one by one, and the configuration script Sql is generated, corresponding to the mapping association table of the entity (upmp_jar_data_entity), and the entity attribute table (upmp_jar_data_entity_filed) is associated through entity_id.

[0083] Furthermore, the credit investigation visualization low-code construction module 10 is also used to generate a database configuration script based on the request message, response message and partner sample message through JSON parsing when the association is completed.

[0084] In actual applications, the visual interface is divided into request messages and response messages. In this embodiment, the sample message of the partner (i.e., the credit reporting agency) can be copied and pasted, and converted into a Sql script through json parsing to build a low-code original configuration table, i.e., the above-mentioned database configuration script.

[0085] The credit investigation visualization low-code construction module 10 is also used to render data based on the database configuration script and the preset data rendering engine to generate a code file.

[0086] It should be noted that the above-mentioned preset data rendering engine can be a Java-based template engine (templateengine), such as Velocity, wherein Velocity allows anyone to use only a simple template language to reference objects defined by Java code. In actual applications, the credit visualization low-code construction module 10 can combine the template files created by the Velocity template language, execute sequentially and build class files and XML files to the server. Specifically, it can configure the associated information table data according to the script, load the memory, render the data through Velocity, and generate the corresponding files and store them on the remote server, so as to reduce manual code writing, improve R&D efficiency, and allow development to focus more on business code. Reference Figure 7 , Figure 7 This is a code template diagram for the construction of the credit data processing system for this application. Figure 7As shown, the code templates constructed in this solution may include service class code templates, data storage class code templates and domain class code templates, wherein the service class code templates may include: request entity class template (DomainRootRequestStandard.java.vm), response entity class template (DomainRootResponseStandard.java.vm), request header processing class template (StandardizedRequestHeaderHandler.java.ym), request body processing class template (StandardizedRequestBodyHandler.java.vm), request encryption processing class template (StandardizedDataEncr yptHandler.java.vm), decryption processing class template (StandardizedDataDecryptHandler.java.vm); data storage class code templates may include: listening offline data processing class template (KafkaListenerController,java.vm), data parsing processing class template (KafkaEntityServicelmpl.java.vm), data storage processing class template (DomainServicelmpl,java.vm), data entity class template (DomainEntity.java.vm), data storage Dao class template (DomainDao.java.vm), data storage Mybatis XML template (DomainMapper.xml.vm) and Maven pom file template (pom.xml.vm); domain class code templates may include: listening Kafka request processing class template (KafkaRequestListenerController.java.vm), Dubbo request processing class template (DubboRequestController.java.vm) and (HttpRequestController.java.vmHttp receiving processing class template).

[0087] The credit investigation visualization low-code construction module 10 is also used to push the process engine service package and the offline storage engine package in the code file to the remote Nexus library.

[0088] It should be noted that after the code files are generated, the built code can be packaged and pushed to the remote Nexus library through Maven Deploy. At this time, two packages, xxx-service.jar and xxx-datastore.jar, will be pushed. So far, the code has been built. For example, after the code is built, the generated code packages, process engine package youcahs-upmp-abcd-service-1.0.0.jar, and offline data storage engine package youcash-upmp-abcd-datastore-1.0.0.jar, can be pushed to the remote Nexus library.

[0089] The credit investigation service front-end module 20 is used to send a credit investigation data query request to the credit investigation process engine service module 30 when the code file is constructed.

[0090] It should be noted that the above-mentioned credit data query request may be a request for instructing the system to query credit data.

[0091] Furthermore, the credit reporting service front-end module 20 is also used to load the code file into the credit reporting service front-end project when the code file is constructed, so as to update the interface service capability of the request interface, and the code file supports Kafka protocol, Dubbo protocol or Http protocol; the credit reporting service front-end module 20 is also used to receive the credit reporting call request through the updated request interface; the credit reporting service front-end module 20 is also used to perform compliance verification on the credit reporting call request; the credit reporting service front-end module 20 is also used to determine the request function corresponding to the credit reporting call request when the verification is completed, and the request function includes: cache query function; the credit reporting service front-end module 20 is also used to query the credit data required for the credit reporting call request if the request function is the cache query function.

[0092] It should be noted that the above credit reporting service pre-project can be a project constructed in the credit reporting service pre-module 20. In this embodiment, the constructed code files ABCDModelController and ABCDModelListener supporting the class files of Http protocol, Dubbo protocol or Kafka protocol can be loaded into the credit reporting service pre-project to enrich the interface service capabilities.

[0093] It should be understood that the above-mentioned credit investigation call request may be a request for instructing the credit investigation service front-end module 20 to call credit investigation data.

[0094] In practical applications, such as Figure 3As shown, multiple APIs can be set in the credit service front-end module 20, and its core function is to coordinate the functions of each module and provide the following services: First, the credit call request from the internal system is received by exposing the request interface, and the compliance check is performed on the received request data. At the same time, the cache query function is supported for the credit call request received from the internal system, which reduces resource consumption and improves interface query concurrency while reducing query costs. Secondly, the main service remotely calls the third-party request and processing service through the microservice to obtain the required credit data from the specified interface, and after the query is successful, it asynchronously requests the offline data synchronization service through the message queue. In addition, the main service is also responsible for billing management of the query status of the third-party credit interface to avoid the failure of the prepaid interface to call due to insufficient balance. Finally, for all request operations, the main service has a complete logging function, and asynchronously persists the request records to the database to facilitate interface management and problem troubleshooting.

[0095] Furthermore, the credit reporting service front-end module 20 is also used to obtain credit data query conditions based on the credit call request if the request function is the cache query function; the credit reporting service front-end module 20 is also used to perform cache query according to the credit data query conditions; the credit reporting service front-end module 20 is also used to determine the current hit cache identifier when hitting the cache, and store the cache identifier in the current query record.

[0096] It is understandable that the above-mentioned credit data query conditions can be conditions for querying credit data, such as: ID card, name, etc., and this embodiment does not limit this. In this embodiment, the credit service front-end module 20 can take over the traffic entrance, and through the template engine, construct code files based on three protocols: Kafka, Dubbo, and Http, thereby reducing manual code writing, and providing interfaces that support three types of protocols, enriching the interface types. For the cache module, a unified cache design scheme is formulated, with ID card, name, mobile phone number, interface number, and cache days as unified query conditions, traversing the unified transaction history data, and recording the hit cache ID. At the same time. The credit service front module 20 can also perform differential caching, which can be customized and implemented. The unified transaction history record table (upmp_request_trade_reocrd) sets cache_key. If there is a differentiated cache, the cache key of the interface is spliced ​​and assembled to store the entry. The next time it is called, the query cache condition is the ID card, name, mobile phone number, interface number, cache days, and cache key as the query condition. When the cache is hit, the current query record is saved and the cache id is stored in the library; when the cache is not hit, the credit process engine service module is called through a unified standard service. For the result of the credit process engine service module 30 call, when the response is successful, the result is converted to Json and uploaded to swift. In addition, the data is pushed to the credit offline storage engine module 40 through Kafka. The advantage is that the tps processing performance is improved, and offline data is pushed, and a supplementary retry mechanism is added to avoid failure scenarios.

[0097] The credit investigation process engine service module 30 is used to load the process engine service package into the target project.

[0098] The credit investigation process engine service module 30 is further used to receive the credit investigation data query request through the target project engineering, and determine and return the target query credit investigation data according to the credit investigation data query request.

[0099] It should be noted that in this solution, xxx-service.jar can be loaded from the remote Nexus dependency to the above-mentioned target project project through Maven pom.xml. The target project project is responsible for receiving the request of the credit service front-end module 20, assembling request message processing, encryption message processing, requesting partners, decryption message processing, and response result message processing. In this embodiment, youcahs-upmp-abcd-service-1.0.0.jar can be loaded from the remote Nexus dependency to the project project through Maven pom.xml. The project project is responsible for receiving the request of the credit service front-end module 20. Development only needs to implement the business logic in the class files ABCDModelRequestHandler / ABCDModelEncryptHandler / ABCDModelDecryptHandler / ABCDModelResponseHandler.

[0100] It should be noted that the credit process engine service module 30 uses (upmp_partner_api_step) to connect actions, referring to Figure 8 , Figure 8 This is the structure diagram of the dynamic configuration process engine of the credit data processing system for this application. Figure 8 As shown, if a dependent interface, such as a token, is involved, the steps of LOGIN_API can be connected in series through this configuration, and the result data can be persisted in the database; XXX_API can obtain the token through the table, including the identification of the validity period, and if it expires, re-initiate the request. For network timeouts, a unified standard uses a 3-time retry mechanism, and the retry operation can be customized for the field code of the partner's response. Since the dependent interface (such as obtaining a token) in this embodiment is configured through an independent query interface, other interfaces with the same licensed institution are configured in a service-oriented form to form a complete package interface, thereby improving the interface reuse capability.

[0101] Furthermore, the credit investigation process engine service module 30 is also used to receive all requests sent by the credit investigation service front-end module 20 through the target project engineering; the credit investigation process engine service module 30 is also used to desensitize the sensitive data in the request to obtain desensitized request data; the credit investigation process engine service module 30 is also used to encrypt and sign the desensitized request data, and send the encrypted and signed request data to the credit investigation agency.

[0102] In this embodiment, the credit process engine service module 30 mainly provides services for the credit service front-end service call and is responsible for the interaction with the third-party credit reporting agency. The specific functions include: first, desensitizing the sensitive data in the request to the third party and splicing the request body. After that, the desensitized request data is encrypted and signed, and sent to the credit reporting agency.

[0103] Furthermore, the credit investigation process engine service module 30 is also used to receive the target credit investigation data returned by the partner; the credit investigation process engine service module 30 is also used to perform signature verification and decryption processing on the target credit investigation data to obtain the processed target credit investigation data; the credit investigation process engine service module 30 is also used to send the processed target credit investigation data to the credit investigation service front-end module 20.

[0104] It should be noted that after the credit investigation process engine service module 30 sends a request to the credit investigation agency, the credit investigation agency will return the corresponding request data. At this time, the credit investigation process engine service module 30 can verify the signature and decrypt the data returned by the partner, and clean, convert the format and standardize the returned data so that it can be seamlessly connected with the internal system. Finally, the processed data is returned to the credit investigation service front-end module 20.

[0105] It should be noted that the visual configuration process provided by this solution to build low-code interface service development and methods has the characteristics of lowering technical barriers, easy maintenance and modification, automatic code generation, easy integration, unified data structure, increased development speed, improved quality, and focus on business logic. The visualization platform builds low-code modules through a graphical interface, reduces code writing time, speeds up interface development, improves interface reuse capabilities, reduces demand cycles, and provides technical support for the financial industry. In addition, through the visualization solution, the learning threshold can be lowered, allowing development verification to focus on logic with more business attributes. The use of a unified architectural style can reduce maintenance costs and standardize the development standards of developers. The standardized process has been sorted out based on practice, which helps to improve the quality and reliability of the interface.

[0106] The present embodiment provides a credit data processing system, which discloses a credit visualization low-code construction module, a credit service front-end module and a credit process engine service module; the credit visualization low-code construction module is used to construct a code file based on the interface form information, and the code file includes: a process engine service package; a credit service front-end module is used to send a credit data query request to the credit process engine service module when the code file is built; the credit process engine service module is used to load the process engine service package to the target project engineering; the credit process engine service module is also used to receive the credit data query request through the target project engineering, and determine according to the credit data query request And returns the target query credit data; compared with the traditional financial industry in the prior art, when facing different credit agencies connecting to different data services, it needs to adopt a customized development method, which causes financial institutions to face low efficiency, high cost, poor compatibility and scalability when accessing third-party credit data. Problems, since this embodiment constructs a code file based on interface form information, and loads the process engine service package in the code file to the target project project to receive the credit data query request to return the target query credit data, it solves the technical problems of low efficiency, high cost, poor compatibility and scalability when the traditional financial technology field in the prior art adopts a customized development method to access third-party credit data.

[0107] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Fig. 9 , Fig. 9 This is a structural block diagram provided for Example 2 of the credit investigation data processing system of this application.

[0108] Based on the above-mentioned first embodiment of the credit investigation data processing system, a second embodiment of the credit investigation data processing system of the present invention is proposed.

[0109] like Fig. 9 As shown, the system further includes: a credit investigation offline storage engine module 40.

[0110] The credit investigation offline storage engine module 40 is used to load the offline storage engine package from the remote Nexus library to the first project.

[0111] The credit investigation offline storage engine module 40 is also used to store offline credit investigation data through the first project.

[0112] It should be noted that the credit investigation offline storage engine module 40 in this embodiment is mainly responsible for storing the original credit data of licensed institutions. Specific functions include: receiving and parsing the message structure in the message body of the financial data returned by the third-party institution through asynchronous monitoring, and persisting it to the database according to the standard data modeling structure.

[0113] In this embodiment, the credit investigation offline storage engine module 40 can use Kafka+swift distributed object storage technology to store the partner's message data in an asynchronous manner.

[0114] In actual applications, the credit reporting offline storage engine module 40 can load xxx-datastore.jar from the remote Nexus dependency to the project project (i.e. the first project project mentioned above) through Maven pom.xml. The project project is responsible for offline data storage. The developer only needs to create the corresponding data table and repackage the project. Then, the data can be automatically stored in the database by monitoring the Kafka message sent by the credit reporting service front-end module 20. From receiving to the persistent database, the offline storage engine is included in the jar package generated by low code, and no additional manual code is required. For example, youcash-upmp-abcd-datastore-1.0.0.jar is loaded from the remote Nexus dependency to the first project through Mavenpom.xml, and the ABCDModelKafkaListener.java class file is generated according to the KafkaListenerController.java.vm (template file for listening to offline data processing class) template file, which is responsible for listening to data storage requests. In addition, relationship mapping class files such as BaihangRuizhiModelDao.java, BaihangRuizhiModeMapp.xml or BaihangRuizhiMode.java are generated based on this. For details, see Figure 7 .

[0115] In this embodiment, a credit reporting offline storage engine module is disclosed for loading an offline storage engine package from a remote Nexus library to a first project engineering; offline credit reporting data is stored through the first project engineering, thereby realizing offline storage of data. Subsequent development only needs to create the corresponding data table and repackage the project. The Kafka message sent by the credit reporting service front-end module can be monitored and the data can be automatically stored in the database, thereby improving data query efficiency.

[0116] Based on the above-mentioned various embodiments of the credit data processing system, a first embodiment of a credit data processing method based on the credit data processing system of the present invention is proposed.

[0117] refer to Fig.10 , Fig.10 This is a flow chart of the first embodiment of the credit data processing method provided by the present application based on the above-mentioned credit data processing system.

[0118] like Fig.10As shown, in this embodiment, the credit data processing method based on the credit data processing system includes the following steps:

[0119] Step S10: construct a code file based on the interface form information, wherein the code file includes: a process engine service package.

[0120] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a credit data processing device, etc. The following takes the credit data processing device as an example (hereinafter referred to as the device) to illustrate this embodiment and the following embodiments.

[0121] Step S20: When the code file is constructed, the process engine service package is loaded into the target project.

[0122] Step S30: receiving a credit data query request through the target project, and determining and returning target query credit data according to the credit data query request.

[0123] Furthermore, the step S10 includes: determining the name of the credit reporting agency based on the interface form information, and constructing a process engine service package and an offline storage engine package according to the name of the credit reporting agency; when the construction is completed, determining the interface number according to the interface form information; determining the entity service connection relationship based on the interface number; associating the entity number with the request response entity class information corresponding to the response message based on the entity service connection relationship; associating the entity attribute number with the entity association attribute in the request response entity class information to construct a code file when the association is completed.

[0124] In this embodiment, a code file is constructed based on interface form information, and the code file includes: a process engine service package; when the code file is constructed, a credit data query request is sent to the credit process engine service module; the process engine service package is loaded into the target project engineering; the credit data query request is received through the target project engineering, and the target query credit data is determined and returned according to the credit data query request; compared with the prior art, the traditional financial industry needs to adopt a customized development method when facing different credit agencies to connect with different data services, resulting in financial institutions facing low efficiency, high cost, poor compatibility and scalability when accessing third-party credit data. Since this embodiment constructs a code file based on interface form information, and loads the process engine service package in the code file into the target project engineering to receive the credit data query request to return the target query credit data, it solves the technical problems of low efficiency, high cost, poor compatibility and scalability when the traditional financial technology field adopts a customized development method to access third-party credit data in the prior art.

[0125] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the credit data processing method of the credit data processing system of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

Claims

1. A credit investigation data processing system, characterized in that: The system includes: a credit investigation visualization low-code construction module, a credit investigation service front-end module and a credit investigation process engine service module; The credit investigation visualization low-code construction module is used to construct a code file based on the interface form information, and the code file includes: a process engine service package; The credit reporting service front-end module is used to send a credit reporting data query request to the credit reporting process engine service module when the code file is built; The credit investigation process engine service module is used to load the process engine service package into the target project; The credit process engine service module is also used to receive the credit data query request through the target project engineering, and determine and return the target query credit data according to the credit data query request.

2. The system according to claim 1, characterized in that The credit reporting visualization low-code construction module is used to determine the name of the credit reporting agency based on the interface form information, and to build a process engine service package and an offline storage engine package according to the name of the credit reporting agency; The credit investigation visualization low-code construction module is also used to determine the interface number according to the interface form information when the construction is completed; The credit investigation visualization low-code construction module is also used to determine the entity service connection relationship based on the interface number; The credit investigation visualization low-code construction module is also used to associate the entity number with the request response entity class information corresponding to the response message based on the entity service connection relationship; The credit investigation visualization low-code construction module is also used to associate the entity attribute number with the entity association attribute in the request response entity class information to build a code file when the association is completed.

3. The system according to claim 2, characterized in that The credit investigation visualization low-code construction module is also used to generate a database configuration script based on the request message, response message and partner sample message through JSON parsing when the association is completed; The credit information visualization low-code construction module is also used to render data based on the database configuration script and the preset data rendering engine to generate a code file; The credit investigation visualization low-code construction module is also used to push the process engine service package and the offline storage engine package in the code file to the remote Nexus library.

4. The system according to claim 3, characterized in that The credit reporting service front-end module is further used to load the code file into the credit reporting service front-end project when the code file is built, so as to update the interface service capability of the request interface, and the code file supports the Kafka protocol, the Dubbo protocol or the Http protocol; The credit investigation service front-end module is further used to receive a credit investigation call request through an updated request interface; The credit investigation service front-end module is also used to perform compliance verification on the credit investigation call request; The credit investigation service front-end module is further used to determine the request function corresponding to the credit investigation call request when the verification is completed, and the request function includes: a cache query function; The credit investigation service front-end module is further used to query the credit investigation data required by the credit investigation call request if the request function is the cache query function.

5. The system according to claim 4, characterized in that The credit service front-end module is further configured to obtain a credit data query condition based on the credit call request if the request function is the cache query function; The credit service front-end module is further used to perform cache query according to the credit data query condition; The credit service front-end module is also used to determine the cache identifier currently hit when hitting the cache, and store the cache identifier in the current query record.

6. The system according to any one of claims 1 to 5, characterized in that The credit investigation process engine service module is further used to receive all requests sent by the credit investigation service front-end module through the target project; The credit investigation process engine service module is further used to desensitize the sensitive data in the request to obtain desensitized request data; The credit reporting process engine service module is also used to encrypt and sign the desensitized request data, and send the encrypted and signed request data to the credit reporting agency.

7. The system according to claim 6, characterized in that The credit investigation process engine service module is also used to receive target credit investigation data returned by the partner; The credit process engine service module is further used to perform signature verification and decryption processing on the target credit data to obtain the processed target credit data; The credit investigation process engine service module is also used to send the processed target credit investigation data to the credit investigation service front-end module.

8. The system according to claim 3, characterized in that The system also includes: a credit investigation offline storage engine module; The credit investigation offline storage engine module is used to load the offline storage engine package from the remote Nexus library to the first project; The credit investigation offline storage engine module is also used to store offline credit investigation data through the first project.

9. A credit data processing method based on the credit data processing system according to any one of claims 1 to 8, characterized in that: The method includes: Building a code file based on the interface form information, the code file includes: a process engine service package; When the code file is built, the process engine service package is loaded into the target project; A credit data query request is received through the target project engineering, and target query credit data is determined and returned according to the credit data query request.

10. The method according to claim 9, characterized in that The step of constructing a code file based on the interface form information includes: Determine the name of the credit reporting agency based on the interface form information, and build a process engine service package and an offline storage engine package according to the name of the credit reporting agency; When the construction is completed, the interface number is determined according to the interface form information; Determine the entity service connection relationship based on the interface number; Associating the entity number with the request response entity class information corresponding to the response message based on the entity service connection relationship; The entity attribute number is associated with the entity association attribute in the request response entity class information to construct a code file when the association is completed.

Images