Storage method and device of insurance service data, electronic equipment and storage medium

Abstract

The embodiment of the invention provides an insurance service data storage method and device, electronic equipment and a storage medium, and belongs to the technical field of data processing. The method comprises the steps of obtaining a target message category theme from a message queue according to a target insurance service index, and storing a target service data table in the message queue according to the target message category theme; and storing the target business data table into the target database according to the data connection channel between the target business data table and the target database. According to the embodiment of the invention, the target service data table is stored in the message queue according to the target message category theme, the multiple target insurance service indexes are stored in the unified message theme of the concurrent queue, and the insurance service data are stored according to the data connection channel between the target service data table and the target database, so that the security of the insurance service data is improved. Multiple insurance service indexes can be stored in the database without consuming a large number of database performance resources, and the storage efficiency of the insurance service data is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, is applicable to the field of financial technology, and in particular, relates to a storage method and device, electronic device and storage medium for insurance business data. Background Art

[0002] At present, the traditional storage method of insurance business data is usually to synchronize insurance business data from the insurance business system to the message queue, and use the real-time computing engine (such as flink or spark) to clean and convert the insurance business data, so as to process it into insurance business indicators for storage. For example, in the insurance scenario, by obtaining insurance customer information, insurance transaction records, insurance claims applications and other insurance business data from different business systems, and extracting insurance business indicators (such as insurance product loss ratio, insurance premium income, etc.) from the insurance business data, a corresponding JDBC connection is created for each insurance business indicator, and each insurance business indicator is stored in the database based on the JDBC connection. However, this method requires creating a corresponding database connection for each insurance business indicator, which consumes a lot of database performance resources to store multiple insurance business indicators in the database, resulting in low storage efficiency of insurance business data. Therefore, how to improve the storage efficiency of insurance business data has become an urgent problem to be solved. Summary of the invention

[0003] The main purpose of the embodiments of the present application is to provide a storage method and device, electronic device and storage medium for insurance business data, aiming to improve the storage efficiency of insurance business data.

[0004] To achieve the above-mentioned purpose, a first aspect of an embodiment of the present application proposes a method for storing insurance business data, the method comprising:

[0005] Acquire target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data of the insurance business indication information that matches the target insurance business category;

[0006] Generating a target insurance business indicator of the target insurance business data according to the insurance business indication information and the target insurance business category;

[0007] Generate a target business data table according to the target insurance business indicator and the target insurance business category;

[0008] Obtaining a target message category topic from a preset message queue according to the target insurance business indicator, and storing the target business data table in the message queue according to the target message category topic;

[0009] Extracting the target business data table from the message queue, and creating a data connection channel between the target business data table and a preset target database;

[0010] The target business data table is stored in a target database according to the data connection channel.

[0011] In some embodiments, obtaining a target message category topic from a preset message queue according to the target insurance business indicator includes:

[0012] Acquire the indicator category of the target insurance business indicator, and determine the database data format of the target insurance business indicator according to the indicator category;

[0013] Generate a storage task for the target insurance business indicator according to the storage data format;

[0014] Performing unified storage configuration on the storage tasks to obtain unified configuration information of the tasks;

[0015] The initial message category topic of the message queue is obtained, and the target message category topic is filtered out from the initial message category topic based on the unified task configuration information and the warehouse-dropping task.

[0016] In some embodiments, storing the target business data table in the message queue according to the target message category topic includes:

[0017] Obtain the topic storage address of the target message category topic;

[0018] Obtaining the storage mode of the target business data table;

[0019] The target business data table is stored in the message queue according to the subject storage address and the storage mode.

[0020] In some embodiments, storing the target business data table in a target database according to the data connection channel includes:

[0021] Acquire the compiled storage statement of the target business data table according to the data connection channel;

[0022] Performing parameter category configuration on the compilation storage statement to obtain a configuration compilation parameter category;

[0023] The compilation storage statement is executed according to the configuration compilation parameter category and the data connection channel to determine that the target business data table is stored in the target database.

[0024] In some embodiments, the generating the target insurance business indicator of the target insurance business data according to the insurance business indication information and the target insurance business category includes:

[0025] Generating original insurance business indicators of the target insurance business data according to the insurance business indication information;

[0026] Obtaining constraints on the insurance business instruction information;

[0027] The target insurance business indicator of the target insurance business data is generated according to the constraint condition, the target insurance business category and the original insurance business indicator.

[0028] In some embodiments, before obtaining the target insurance business demand data, the method further includes:

[0029] Acquire initial insurance business data from a preset business data source;

[0030] Storing the initial insurance business data in the message queue;

[0031] The initial insurance business data in the message queue is subjected to business analysis to obtain initial insurance business demand data.

[0032] In some embodiments, after storing the target business data table in the target database according to the data connection channel, the method further includes:

[0033] Performing indicator risk detection on the target business data table in the target database to obtain risk indicator data;

[0034] The risk insurance business of the risk indicator data is obtained, and risk identification is performed on the risk insurance business according to the risk indicator data to obtain a target insurance risk level.

[0035] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application provides a storage device for insurance business data, the device comprising:

[0036] An insurance business demand data acquisition module is used to acquire target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data of the insurance business indication information that matches the target insurance business category;

[0037] An insurance business index generating module, used for generating a target insurance business index of the target insurance business data according to the insurance business indication information and the target insurance business category;

[0038] A business data table generating module, used for generating a target business data table according to the target insurance business indicator and the target insurance business category;

[0039] A message queue topic storage module, used to obtain a target message category topic from a preset message queue according to the target insurance business indicator, and store the target business data table in the message queue according to the target message category topic;

[0040] A data connection channel creation module, used to extract the target business data table from the message queue and create a data connection channel between the target business data table and a preset target database;

[0041] The target insurance data storage module is used to store the target business data table into the target database according to the data connection channel.

[0042] To achieve the above-mentioned purpose, the third aspect of an embodiment of the present application proposes an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the method described in the first aspect is implemented.

[0043] To achieve the above objectives, the fourth aspect of an embodiment of the present application proposes a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method of the first aspect is implemented.

[0044] The storage method and device, electronic device and storage medium of insurance business data proposed in the present application obtain target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information and target insurance business data matching the target insurance business category of the insurance business indication information; generate target insurance business indicators of the target insurance business data according to the insurance business indication information and the target insurance business category; generate a target business data table according to the target insurance business indicators and the target insurance business category; obtain a target message category subject from a preset message queue according to the target insurance business indicator, and store the target business data table in the message queue according to the target message category subject; extract the target business data table from the message queue, and create a data connection channel between the target business data table and a preset target database; store the target business data table in the target database according to the data connection channel. The present application firstly generates target insurance business indicators of target insurance business data according to insurance business indication information and target insurance business categories, and can quantify the implementation of insurance business indication information; secondly, according to the target message category subject, the target business data table containing the target insurance business indicators and the target insurance business category is stored in the message queue, thereby realizing the storage of multiple target insurance business indicators in a unified subject of the concurrent queue, so as to facilitate the subsequent data storage through only one data connection channel; finally, according to a data connection channel between the target business data table and the target database, the process of storing the target business data table in the target database is realized, and multiple insurance business indicators can be stored in the database without consuming a large amount of database performance resources, which significantly improves the storage efficiency of insurance business data. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 is a flowchart of a method for storing insurance business data provided by an embodiment of the present application;

[0046] Figure 2 It is a flow chart of a first embodiment of a method for storing insurance business data provided by an embodiment of the present application;

[0047] Figure 3 yes Figure 1 Flow chart of step S102 in FIG.

[0048] Figure 4 yes Figure 1 Flow chart of step S104 in FIG.

[0049] Figure 5 yes Figure 1 Another flow chart of step S104 in FIG. 1 ;

[0050] Figure 6 yes Figure 1 Flow chart of step S106 in FIG.

[0051] Figure 7 is a flow chart of a second embodiment of the method for storing insurance business data provided by an embodiment of the present application;

[0052] Figure 8 It is a schematic diagram of the structure of a storage device for insurance business data provided in an embodiment of the present application;

[0053] Fig. 9 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0055] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0056] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0057] The embodiments of the present application provide a storage method and device for insurance business data, an electronic device, and a storage medium, aiming to improve the storage efficiency of insurance business data.

[0058] The storage method and device, electronic device and storage medium of insurance business data provided in the embodiments of the present application are specifically explained through the following embodiments. First, the storage method of insurance business data in the embodiments of the present application is described.

[0059] The storage method of insurance business data provided in the embodiment of the present application relates to the field of data processing technology. The storage method of insurance business data provided in the embodiment of the present application can be applied to a terminal, can also be applied to a server side, and can also be software running in a terminal or a server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or can be configured as a server cluster or a distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the storage method of insurance business data, etc., but is not limited to the above forms.

[0060] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0061] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to the user's identity or characteristics, the user's permission or consent will be obtained first, and the collection, use and processing of these data will comply with relevant laws, regulations and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or jump to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0062] Figure 1 is an optional flowchart of the method for storing insurance business data provided in an embodiment of the present application. Figure 1 The method may include but is not limited to steps S101 to S106.

[0063] Step S101, obtaining target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data matching the target insurance business category of the insurance business indication information.

[0064] Step S102, generating target insurance business indicators of target insurance business data according to the insurance business indication information and the target insurance business category.

[0065] Step S103, generating a target business data table according to the target insurance business index and the target insurance business category.

[0066] Step S104, obtaining a target message category topic from a preset message queue according to the target insurance business index, and storing the target business data table in the message queue according to the target message category topic.

[0067] Step S105: extract the target business data table from the message queue, and create a data connection channel between the target business data table and a preset target database.

[0068] Step S106: store the target business data table into the target database according to the data connection channel.

[0069] Steps S101 to S106 shown in the embodiment of the present application are performed by acquiring target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data matching the target insurance business category of the insurance business indication information; generating target insurance business indicators of the target insurance business data according to the insurance business indication information and the target insurance business category; generating a target business data table according to the target insurance business indicators and the target insurance business category; acquiring a target message category topic from a preset message queue according to the target insurance business indicator, and storing the target business data table in the message queue according to the target message category topic; extracting the target business data table from the message queue, and creating a data connection channel between the target business data table and a preset target database; storing the target business data table in the target database according to the data connection channel. The present application firstly generates target insurance business indicators of target insurance business data according to insurance business indication information and target insurance business categories, and can quantify the implementation of insurance business indication information; secondly, according to the target message category subject, the target business data table containing the target insurance business indicators and the target insurance business category is stored in the message queue, thereby realizing the storage of multiple target insurance business indicators in a unified subject of the concurrent queue, so as to facilitate the subsequent data storage through only one data connection channel; finally, according to a data connection channel between the target business data table and the target database, the process of storing the target business data table in the target database is realized, and multiple insurance business indicators can be stored in the database without consuming a large amount of database performance resources, which significantly improves the storage efficiency of insurance business data.

[0070] In step S101 of some embodiments, the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data matching the target insurance business category of the insurance business indication information.

[0071] Specifically, insurance business indication information refers to information stored based on business demand purpose indication data.

[0072] For example, in the insurance business, the insurance business indication information may be indication information for obtaining the total premium income of all insurances in the insurance system.

[0073] Specifically, the target insurance business category is a business data category determined based on the insurance business indication information, and can be represented by different business data dimensions.

[0074] For example, in the insurance business, the insurance business indication information is to obtain the total insurance premium income of all insurance systems. The target insurance business category can be determined as the insurance premium category through the insurance type dimension (such as health insurance, property insurance, medical insurance, etc.), regional dimension (such as different insurance branches) and customer dimension (such as customer categories based on assets).

[0075] Specifically, the target insurance business data refers to the original data generated by the insurance business in which the transaction occurs, and the target insurance business data is the data that matches the target insurance business category.

[0076] For example, in the insurance business, if the target insurance business category is all insurance premiums, the target insurance business data can be the transaction volume of each insurance product, the premium income of each insurance, etc.; if the target insurance business category is insurance claims, the target insurance business data can be the claim amount of each insurance, the insurance product policyholders and the insurance product beneficiaries, etc.

[0077] See also Figure 2 In some embodiments, before step S101, the method for storing insurance business data further includes steps S201 to S203:

[0078] Step S201, obtaining initial insurance business data from a preset business data source.

[0079] Step S202, storing the initial insurance business data in a message queue.

[0080] Step S203, performing business analysis on the initial insurance business data in the message queue to obtain initial insurance business demand data.

[0081] In step S201 of some embodiments, specifically, the preset business data source may be data sources such as insurance product transaction systems and customer relationship management systems of different insurance branches.

[0082] Specifically, initial insurance business data refers to original business data extracted from business data sources.

[0083] For example, in the insurance business, the transaction amount, transaction time and account information of both parties to the insurance product transaction can be obtained from the insurance product transaction system, and customer information (such as customer identity information, credit score, customer historical insurance records, customer historical claims records, etc.) can also be obtained from the customer relationship management system.

[0084] In step S202 of some embodiments, specifically, the message queue refers to a channel for receiving information, storing information, and sending information.

[0085] Specifically, obtain the connection information of the business data source (such as interface, user name and host name, etc.) and the message middleware (such as kafka) of the message queue, create a transmission link between the interface of the business data source and the message middleware, and store the initial insurance business data in the message queue through the transmission link and the data synchronization tool (such as DataX). That is, when the data in the business data source changes, the data synchronization tool will encapsulate the changes into messages and send them to the message queue, and the transaction or confirmation mechanism can be used to ensure the reliable delivery of the message to ensure that the message is successfully sent.

[0086] Furthermore, the initial insurance business data is sent to the original message category topic (such as raw-data topic) of the Kafka message queue, which can serve as the original layer of the data warehouse.

[0087] In this embodiment, by storing the initial insurance business data in the message queue, asynchronous processing of the insurance business data can be achieved, which plays a role in buffering and distributing the insurance business data. A large amount of insurance business data generated in a short period of time can be stored in the message queue, thereby achieving asynchronous parallelism of the insurance business data, which is convenient for subsequent improvement of the storage efficiency of the insurance business data.

[0088] In step S203 of some embodiments, specifically, the initial insurance business demand data includes initial insurance business indication information, an initial insurance business category corresponding to the initial insurance business indication information, and initial insurance business data matching the initial insurance business category of the initial insurance business indication information.

[0089] Specifically, firstly, the initial insurance business data in the message queue is converted into data details to obtain the initial insurance business detail data; further, the initial insurance business detail data is aggregated to obtain the initial insurance business aggregated data; finally, the business aggregated data is classified into business indications to determine the initial insurance business demand data.

[0090] Specifically, by using a real-time computing engine (such as Apache Flink or Apache Spark) to read the initial insurance business data from the raw-datatopic, the initial insurance business data is cleaned (such as removing duplicate record data, correcting data format errors, etc.) and converted (such as unit conversion, data format standardization, etc.) to obtain the initial insurance business detailed data.

[0091] Specifically, the initial insurance business detail data is sent to the detail message category topic (such as detail-data topic) of the Kafka message queue, which can be used as the detail layer of the data warehouse.

[0092] Specifically, aggregation processing is the process of aggregating the initial insurance business details according to different data dimensions. For example, the insurance product claim amount can be aggregated according to data dimensions such as insurance transaction time period and customer identity.

[0093] Specifically, the initial insurance business aggregated data is sent to the aggregated message category topic (such as aggregated-data topic) of the Kafka message queue, which can serve as the aggregation layer of the data warehouse.

[0094] Specifically, the initial insurance business demand data is a business demand category determined according to different initial insurance business indication information, for example, obtaining the loss ratio of all insurance products, obtaining the total premium income of all insurance products, or obtaining the renewal rate of all insurance products.

[0095] Furthermore, target insurance business demand data can be obtained from the layered data warehouse.

[0096] See also Figure 3 In some embodiments, step S102 includes but is not limited to steps S301 to S303:

[0097] Step S301, generating original insurance business indicators of target insurance business data according to insurance business indication information.

[0098] Step S302, obtaining constraint conditions of insurance business instruction information.

[0099] Step S303, generating target insurance business indicators of target insurance business data according to the constraint conditions, target insurance business categories and original insurance business indicators.

[0100] In step S301 of some embodiments, specifically, the original insurance business indicator is the most basic data metric, which is usually business indicator data directly obtained from the original insurance business data.

[0101] For example, in the insurance business, the original insurance business indicator may be the transaction volume of insurance products within a historical period of time, etc.

[0102] Specifically, the insurance business instruction information is disassembled into insurance business objectives and insurance business sub-objectives, and the original insurance business indicators are determined according to the insurance business objectives and the insurance business sub-objectives.

[0103] For example, if the insurance business indication information is to collect customer satisfaction with health insurance transactions, then the insurance business goal is to truly and effectively collect the satisfaction of users who purchase health insurance. The insurance business sub-goal is the number of users who purchase health insurance who complete the health insurance questionnaire. The original insurance business indicator is the satisfaction score of each user's evaluation of health insurance.

[0104] In step S302 of some embodiments, specifically, the constraint condition of the insurance business indication information is used to limit the data volume of the insurance business indication information, which is determined based on actual business conditions.

[0105] For example, if we want to collect the satisfaction of users who purchased health insurance in the past year, the constraint condition is within the past year.

[0106] In step S303 of some embodiments, specifically, the target insurance business indicator is data used to measure the target business performance.

[0107] For example, in the insurance business, the insurance business indication information is to collect customer satisfaction with health insurance transactions. The original insurance business indicator is the satisfaction score of each user's evaluation of health insurance. The constraints are within the past year. The target insurance business category is the insurance branch category, the customer category based on asset classification, etc. Then the target insurance business indicator can be the average satisfaction score of all customers who have purchased health insurance in the past year.

[0108] In this embodiment, the target insurance business indicators of the target insurance business data are generated according to the constraints, the target insurance business category and the original insurance business indicators, which can quantify the implementation of the insurance business indication information, provide a more accurate and detailed business view for the insurance business, and help improve the storage accuracy of subsequent insurance business data.

[0109] In step S103 of some embodiments, specifically, the target business data table is a data table storing target insurance business indicators and target insurance business categories.

[0110] Specifically, the target insurance business indicators and target insurance business categories are respectively used as column names of the data table to construct an initial data table, and specific business indicator values ​​and specific insurance business categories are filled into the initial data table to obtain the target business data table.

[0111] For example, in the insurance business, the target insurance business category is all types of insurance and renewal categories, and the target insurance business indicator is the renewal rate of all insurance products. By obtaining all insurance policy data, the number of newly effective insurance policies for each insurance category is counted based on the insurance policy data, and the rate of each insurance category continuing to purchase new insurance after the insurance expires is calculated, so as to determine the renewal rate of each insurance category, and the renewal rate of each insurance category is averaged and summed to determine the final renewal rate of all insurance products.

[0112] See also Figure 4 In some embodiments, step S104 includes but is not limited to steps S401 to S404:

[0113] Step S401, obtaining the indicator category of the target insurance business indicator, and determining the database data format of the target insurance business indicator according to the indicator category.

[0114] Step S402, generating a warehouse-delivery task of a target insurance business indicator according to the warehouse-delivery data format.

[0115] Step S403: uniformly configure the warehouse drop-off tasks to obtain uniform configuration information of the tasks.

[0116] Step S404, obtaining the initial message category topics of the message queue, and filtering out target message category topics from the initial message category topics based on the unified task configuration information and the task to be placed in the library.

[0117] In step S401 of some embodiments, specifically, the indicator category means that each target insurance business indicator is an indicator category, so the indicator category may also include but is not limited to customer insurance satisfaction, total sales volume of insurance products and average claim amount of insurance claims, etc.

[0118] Specifically, the data format for storage refers to converting the target insurance business indicator format into a unified message format that can be written into a message queue. For example, if the target insurance business indicator is the sales volume of all insurance products, the data sequence of the sales volume of all insurance products is converted into the Json data format for storage.

[0119] In step S402 of some embodiments, specifically, the task of storing the target insurance business indicator in the warehouse refers to a task in which the target insurance business indicator needs to be stored in a message queue.

[0120] Specifically, an initial target insurance business indicator storage task can be created based on the storage data format and the target insurance business indicator through a data synchronization tool (such as DataX).

[0121] For example, in the insurance business, the target insurance business indicator storage task can be a Json format insurance product sales data synchronization task, an insurance claim amount synchronization task, etc.

[0122] In step S403 of some embodiments, specifically, the unified task configuration information is used to ensure that subsequent target business data tables can be stored in a unified topic.

[0123] Specifically, the same Sink (data output) parameters can be configured for the warehouse drop task, such as Sink type (file Sink, database Sink, message queue Sink, etc.), Sink version, Sink creation time, data source connection information configuration, message middleware Kafka connection information configuration, message queue Broker address, warehouse drop task synchronization frequency configuration (such as synchronization once a minute) and warehouse drop task synchronization strategy configuration (such as full synchronization or incremental synchronization), etc.

[0124] Specifically, the target business data table can be regarded as a Sink table, which also stores the URL of the data warehouse, the Broker address of the message queue, etc.

[0125] In step S404 of some embodiments, specifically, the initial message category topic refers to all message category topics included in the message queue, and the initial message category topic is used to implement message publishing or subscription, that is, the message producer sends a message to the topic, and the message consumer receives the message by subscribing to the topic.

[0126] For example, in the insurance business, the initial message category topic may be a financial business topic, an insurance business topic, a car insurance business topic, a health insurance business topic, and the like.

[0127] Specifically, the target message category topic user implements storing the target business data table in the message queue.

[0128] For example, if the task of warehousing is the synchronization task of vehicle insurance claim amount, which involves the insurance claim topic, then all claim topics related to insurance claims can be initially screened out from the initial message category topic, and then the target business data can be further matched to the same vehicle insurance claim topic as the target message category topic in combination with the unified configuration information of the task.

[0129] See also Figure 5 In some embodiments, step S104 further includes but is not limited to steps S501 to S503:

[0130] Step S501, obtaining the topic storage address of the target message category topic.

[0131] Step S502: Obtain the storage mode of the target business data table.

[0132] Step S503: store the target business data table in the message queue according to the subject storage address and storage mode.

[0133] In step S501 of some embodiments, specifically, the topic storage address is used to indicate the position of the target message category topic in the message queue to achieve the connection between the target business data table and the target message category topic. The topic storage can be determined based on actual business conditions.

[0134] For example, in the insurance business, the topic storage address can be sxyyb_dws_kafka2es.

[0135] In step S502 of some embodiments, specifically, the storage mode refers to a model for writing a target business data table into a target message category topic, including a batch write mode or a streaming write mode. If it is a batch write mode, the amount of data stored in each batch also needs to be specified.

[0136] In an optional embodiment of the present application, Kafka's acks setting is also added to ensure the data consistency of the subsequent target business data table stored in the target message category topic.

[0137] In step S503 of some embodiments, specifically, the location of the target message category topic is determined according to the address, and the target business data table is stored in the target message category topic in the message queue based on the storage mode.

[0138] For example, in the insurance business, if the target business data table is the insurance premium income table, DataX is used to convert the target business data table into a Json format data table, and the Json format data table is sent as a message to the insurance business topic. The key of the message can be the insurance policy ID, and the value is the total premium income data of each insurance in Json format.

[0139] Furthermore, if the target business data table is the average claim rate of insurance, the target business data table is converted into a data table in Json format through DataX, and the average claim rate is sent to the insurance business Topic.

[0140] In this embodiment, by storing the target business data table in the message queue according to the subject storage address and storage mode, it is possible to store multiple target insurance business indicators in a unified subject of the concurrent queue, which facilitates the subsequent storage of all business data through only one data connection channel, and helps to improve the storage efficiency of subsequent insurance business data.

[0141] In step S105 of some embodiments, specifically, the target business data table is extracted from the message queue through a real-time computing engine (such as Apache Flink).

[0142] Specifically, the target database can be an OLAP engine (such as ClickHouse) or a data service engine (such as Elasticsearch), which supports real-time access, search and analysis of insurance business data, thereby improving the efficiency of subsequent insurance business indicator risk assessment.

[0143] Specifically, add JDBC driver dependency in the real-time computing engine (such as Apache Flink), configure the driver environment of the real-time computing engine, and further use DriverManager to obtain the database connection. The database connection needs to provide the JDBC URL, user name, and database password of the target database, obtain the URL, user name, and password of the business data source, and create a JDBC data connection channel based on the JDBC URL, user name, and password of the target database and the URL, user name, and password of the business data source.

[0144] For example, the creation of a data connection channel JDBC includes the URL, username, and password configuration information of the target database. For ClickHouse, it involves configuring the ClickHouse JDBC driver and connection string; for Elasticsearch, a dedicated JDBC client is required, such as the Jest client, to implement the JDBC driver, thereby realizing the data transmission function of the data connection channel.

[0145] See also Figure 6 In some embodiments, step S106 includes but is not limited to steps S601 to S603:

[0146] Step S601, obtaining a compiled storage statement of a target business data table according to a data connection channel.

[0147] Step S602: configure the parameter category of the compilation storage statement to obtain the configuration compilation parameter category.

[0148] Step S603, executing the compilation storage statement according to the configuration compilation parameter category and the data connection channel, and determining that the target business data table is stored in the target database.

[0149] In step S601 of some embodiments, specifically, the compiled storage statement may be a precompiled SQL statement.

[0150] Specifically, a target interface connected to a target database may be created through a connection object of a data connection channel, and a precompiled SQL statement may be represented through the target interface.

[0151] In this embodiment, by using precompiled SQL statements, there is no need to compile the SQL statements each time they are executed, thereby improving the execution efficiency of the SQL statements.

[0152] In step S602 of some embodiments, specifically, configuring the category of the compilation parameter refers to configuring actual values ​​for parameter placeholders in the compiled storage statement so that the statement placeholders can be correctly replaced when the SQL statement is executed.

[0153] Furthermore, the string parameters, integer parameters, double-precision floating point parameters, date parameters, etc. of the compiled storage statement are configured.

[0154] In this embodiment, by configuring the compiled storage statement by parameter category, flexible configuration of the compiled storage statement is achieved, so that when adapting to different types of data storage, there is no need to modify the compiled storage statement itself each time, thereby improving the storage efficiency of insurance business data.

[0155] In step S603 of some embodiments, specifically, the compiled storage statement is executed through a preset statement execution function (such as the ExecuteUpdate function), wherein the compiled storage statement may be a SQL statement representing insert, update or delete.

[0156] Specifically, if the SQL statement indicates inserting, the return value of executing the SQL statement indicates the number of rows of data in the target business data table inserted into the target database; if the SQL statement indicates updating or deleting, the return value of executing the SQL statement indicates the number of rows of data in the target business data table modified in the target database.

[0157] Furthermore, if the ExecuteUpdate function executes the SQL statement successfully and returns a value of 1, it indicates that a row of data in the target business data table is successfully stored in the target database; if the value of 0 is returned, it indicates that the target database has not received any new stored data.

[0158] See also Figure 7 In some embodiments, after step S106, the method for storing insurance business data further includes but is not limited to steps S701 to 702:

[0159] Step S701: perform an indicator risk detection on a target business data table in a target database to obtain risk indicator data.

[0160] Step S702, obtaining risk indicator data of the risk insurance business, and performing risk identification on the risk insurance business according to the risk indicator data to obtain a target insurance risk level.

[0161] In step S701 of some embodiments, specifically, the risk indicator data refers to target business data with risks.

[0162] Specifically, a target insurance business category is obtained from a target business data table, and indicators of possible business risks are determined based on the target insurance business category.

[0163] For example, in the insurance business, for the health insurance claims of the target branch, the risk indicator data may be the health insurance claims frequency, health insurance claims amount and disease occurrence probability of the target branch.

[0164] In step S702 of some embodiments, specifically, the risk insurance business is determined by risk indicator data.

[0165] For example, in an insurance scenario, if there are risks in the health insurance claim frequency, health insurance claim amount and disease occurrence probability of the target branch's health insurance policies, then the risk insurance business means that there are risks in the health insurance products of the target branch.

[0166] Specifically, the target insurance risk levels include low risk, medium risk and high risk.

[0167] Specifically, risk scoring of risk insurance business can be performed based on risk indicator data to determine the insurance risk level of the risk insurance business.

[0168] For example, the claim frequency of the target branch's health insurance claim product is 3 times a year, the average claim amount is 20,000 yuan, and the probability of disease occurrence is 0.06. The risk score of the claim product is frequency coefficient 0.5x3 + claim amount coefficient 0.8x2 + disease coefficient 0.8x0.06 = 4.65 points, the low risk threshold is 3.5 points, and the medium risk threshold is 6.5 points. Since the risk score of the claim product is 4.65 points, which is between the low risk threshold and the medium risk threshold, the risk level of the claim product is determined to be medium risk level.

[0169] In this embodiment, risk identification is performed on the risk insurance business based on risk indicator data to obtain a target insurance risk level, which can systematically identify and manage risks in the insurance business, thereby ensuring the normal operation of the insurance business and helping to improve the stability of the insurance business.

[0170] In an optional embodiment of the present application, BI tools (such as dashboards) can also be used to monitor risk indicators in real time to display real-time data such as customer credit risk and insurance market risk.

[0171] Furthermore, insurance companies may find that policies in certain regions are at a relatively high risk level due to high claim rates and high average claim costs. Based on this information, insurance companies can increase premiums for policies in these regions or introduce stricter underwriting standards to control risks. At the same time, insurance companies can also design differentiated products based on risk levels, such as providing discounts for low-risk customers and additional risk management services for high-risk customers, to ensure the normal operation of insurance business.

[0172] The embodiment of the present application obtains target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data matching the target insurance business category of the insurance business indication information; generates target insurance business indicators of the target insurance business data according to the insurance business indication information and the target insurance business category; generates a target business data table according to the target insurance business indicators and the target insurance business category; obtains a target message category topic from a preset message queue according to the target insurance business indicator, and stores the target business data table in the message queue according to the target message category topic; extracts the target business data table from the message queue, and creates a data connection channel between the target business data table and a preset target database; stores the target business data table in the target database according to the data connection channel. The present application firstly generates target insurance business indicators of target insurance business data according to insurance business indication information and target insurance business categories, and can quantify the implementation of insurance business indication information; secondly, according to the target message category subject, the target business data table containing the target insurance business indicators and the target insurance business category is stored in the message queue, thereby realizing the storage of multiple target insurance business indicators in a unified subject of the concurrent queue, so as to facilitate the subsequent data storage through only one data connection channel; finally, according to a data connection channel between the target business data table and the target database, the process of storing the target business data table in the target database is realized, and multiple insurance business indicators can be stored in the database without consuming a large amount of database performance resources, which significantly improves the storage efficiency of insurance business data.

[0173] See also Figure 8 The embodiment of the present application further provides a storage device for insurance business data, which can implement the above-mentioned storage method for insurance business data, and the device includes:

[0174] An insurance business demand data acquisition module is used to acquire target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data matching the target insurance business category of the insurance business indication information;

[0175] An insurance business indicator generation module, used to generate target insurance business indicators of target insurance business data according to insurance business indication information and target insurance business categories;

[0176] A business data table generation module is used to generate a target business data table according to target insurance business indicators and target insurance business categories;

[0177] A message queue topic storage module is used to obtain a target message category topic from a preset message queue according to a target insurance business indicator, and store a target business data table in the message queue according to the target message category topic;

[0178] A data connection channel creation module is used to extract a target business data table from a message queue and create a data connection channel between the target business data table and a preset target database;

[0179] The target insurance data storage module is used to store the target business data table into the target database according to the data connection channel.

[0180] The specific implementation of the storage device for insurance business data is substantially the same as the specific implementation of the storage method for insurance business data described above, and will not be described in detail herein.

[0181] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned insurance business data storage method when executing the computer program. The electronic device can be any smart terminal including a tablet computer, a car computer, etc.

[0182] See also Fig. 9 , Fig. 9 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0183] The processor 901 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0184] The memory 902 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM). The memory 902 can store processing systems and other applications. When the technical solution provided in the embodiments of this specification is implemented by software or firmware, the relevant program code is stored in the memory 902, and the processor 901 calls and executes the storage method of the insurance business data in the embodiments of this application;

[0185] Input / output interface 903, used to implement information input and output;

[0186] Communication interface 904, used to realize communication interaction between the device and other devices, which can be realized by wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0187] A bus 905 that transmits information between various components of the device (e.g., the processor 901, the memory 902, the input / output interface 903, and the communication interface 904);

[0188] The processor 901 , the memory 902 , the input / output interface 903 and the communication interface 904 are connected to each other in communication within the device via a bus 905 .

[0189] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned insurance business data storage method is implemented.

[0190] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory 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 embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor 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.

[0191] The embodiments of the present application provide a storage method for insurance business data, a storage device for insurance business data, an electronic device, and a storage medium, which obtain target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, a target insurance business category of the insurance business indication information, and target insurance business data that matches the target insurance business category of the insurance business indication information; generate target insurance business indicators of the target insurance business data according to the insurance business indication information and the target insurance business category; generate a target business data table according to the target insurance business indicators and the target insurance business category; obtain a target message category topic from a preset message queue according to the target insurance business indicator, and store the target business data table in the message queue according to the target message category topic; extract the target business data table from the message queue, and create a data connection channel between the target business data table and a preset target database; and store the target business data table in the target database according to the data connection channel. The present application firstly generates target insurance business indicators of target insurance business data according to insurance business indication information and target insurance business categories, and can quantify the implementation of insurance business indication information; secondly, according to the target message category subject, the target business data table containing the target insurance business indicators and the target insurance business category is stored in the message queue, thereby realizing the storage of multiple target insurance business indicators in a unified subject of the concurrent queue, so as to facilitate the subsequent data storage through only one data connection channel; finally, according to a data connection channel between the target business data table and the target database, the process of storing the target business data table in the target database is realized, and multiple insurance business indicators can be stored in the database without consuming a large amount of database performance resources, which significantly improves the storage efficiency of insurance business data.

[0192] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0193] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0194] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0195] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0196] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0197] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0198] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. The mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0199] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0200] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0201] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0202] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A method for storing insurance business data, characterized in that: The method comprises: Acquire target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data of the insurance business indication information that matches the target insurance business category; Generating a target insurance business indicator of the target insurance business data according to the insurance business indication information and the target insurance business category; Generate a target business data table according to the target insurance business indicator and the target insurance business category; Obtaining a target message category topic from a preset message queue according to the target insurance business indicator, and storing the target business data table in the message queue according to the target message category topic; Extracting the target business data table from the message queue, and creating a data connection channel between the target business data table and a preset target database; The target business data table is stored in a target database according to the data connection channel.

2. The method according to claim 1, characterized in that The step of obtaining a target message category topic from a preset message queue according to the target insurance business indicator includes: Acquire the indicator category of the target insurance business indicator, and determine the database data format of the target insurance business indicator according to the indicator category; Generate a storage task for the target insurance business indicator according to the storage data format; Performing unified storage configuration on the storage tasks to obtain unified configuration information of the tasks; The initial message category topic of the message queue is obtained, and the target message category topic is filtered out from the initial message category topic based on the unified task configuration information and the warehouse-dropping task.

3. The method according to claim 1, characterized in that The storing the target business data table in the message queue according to the target message category topic includes: Obtain the topic storage address of the target message category topic; Obtaining the storage mode of the target business data table; The target business data table is stored in the message queue according to the subject storage address and the storage mode.

4. The method according to claim 1, characterized in that: The storing the target business data table into a target database according to the data connection channel includes: Acquire the compiled storage statement of the target business data table according to the data connection channel; Performing parameter category configuration on the compilation storage statement to obtain a configuration compilation parameter category; The compilation storage statement is executed according to the configuration compilation parameter category and the data connection channel to determine that the target business data table is stored in the target database.

5. The method according to claim 1, characterized in that The step of generating the target insurance business indicator of the target insurance business data according to the insurance business indication information and the target insurance business category includes: Generating original insurance business indicators of the target insurance business data according to the insurance business indication information; Obtaining constraints on the insurance business instruction information; The target insurance business indicator of the target insurance business data is generated according to the constraint condition, the target insurance business category and the original insurance business indicator.

6. The method according to any one of claims 1 to 5, characterized in that: Before obtaining the target insurance business demand data, the method further includes: Acquire initial insurance business data from a preset business data source; Storing the initial insurance business data in the message queue; The initial insurance business data in the message queue is subjected to business analysis to obtain initial insurance business demand data.

7. The method according to any one of claims 1 to 5, characterized in that: After storing the target business data table in the target database according to the data connection channel, the method further includes: Performing indicator risk detection on the target business data table in the target database to obtain risk indicator data; The risk insurance business of the risk indicator data is obtained, and risk identification is performed on the risk insurance business according to the risk indicator data to obtain a target insurance risk level.

8. A storage device for insurance business data, characterized in that: The device comprises: An insurance business demand data acquisition module is used to acquire target insurance business demand data; wherein the target insurance business demand data includes insurance business indication information, target insurance business category of the insurance business indication information, and target insurance business data of the insurance business indication information that matches the target insurance business category; An insurance business index generating module, used for generating a target insurance business index of the target insurance business data according to the insurance business indication information and the target insurance business category; A business data table generating module, used for generating a target business data table according to the target insurance business indicator and the target insurance business category; A message queue topic storage module, used to obtain a target message category topic from a preset message queue according to the target insurance business indicator, and store the target business data table in the message queue according to the target message category topic; A data connection channel creation module, used to extract the target business data table from the message queue and create a data connection channel between the target business data table and a preset target database; The target insurance data storage module is used to store the target business data table into the target database according to the data connection channel.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the insurance business data storage method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method for storing insurance business data according to any one of claims 1 to 7 is implemented.

Images