Processing method and device of insurance service database, electronic equipment and storage medium

Abstract

The invention discloses an insurance service database processing method and device, electronic equipment and a storage medium, and relates to the technical field of databases. According to the method, each service module is divided into a plurality of service groups, and the limited connection number is set for each monitoring port corresponding to the service groups, so that the insurance service database is connected with the service modules in different service groups through different monitoring ports; the isolation between the service modules in different service groups and the insurance service database is realized. When the number of access requests of the service module of one service group to the insurance service database is greater than the limited connection number of the monitoring port corresponding to the service group, a large number of requests of the service module cannot be responded or released in time, and the monitoring port corresponding to the service group fails; and only the connection between the service module in the service group and the insurance service database is influenced, so that the stability of the insurance service database can be improved.

Description

Technical Field

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

[0002] With the development and popularization of Internet marketing models, the financial insurance industry has also kept pace with the Internet, launching various promotional activities on certain activity days, resulting in a burst of system access to a single activity node. At this time, the number of insurance business orders will increase sharply, so the insurance business database will see a large number of access requests. When a large number of requests from a certain business module cannot be responded to or released in time, it will cause a database connection storm in the insurance business database, resulting in all business modules being unable to access the insurance business database normally. Summary of the invention

[0003] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a method, device, electronic device and storage medium for processing an insurance business database, so that even if a large number of requests from a certain business module cannot be responded to or released in time, the remaining business modules can still access the insurance business database normally.

[0004] To achieve the above-mentioned purpose, a first aspect of the present application provides a method for processing an insurance business database, comprising:

[0005] Acquiring historical access data of the insurance business database;

[0006] Determine the historical number of accesses per second to the insurance business database by the business module based on the historical access data;

[0007] Obtaining the business attributes of the business module;

[0008] Dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second; wherein each of the business groups includes at least one of the business modules;

[0009] A connection limit is set for each listening port corresponding to the business group; the listening ports are multiple ports configured in the insurance business database for connecting to the business modules in the business group.

[0010] According to some embodiments of the first aspect of the present application, the service grouping includes a first grouping;

[0011] The dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second includes:

[0012] Determine, from the plurality of business modules, a first business module whose business attribute is foreign-related insurance business;

[0013] The first group is constructed based on each of the first service modules.

[0014] According to some embodiments of the first aspect of the present application, the service grouping includes a second grouping;

[0015] The dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second includes:

[0016] Determine, from the plurality of business modules, a second business module whose business attribute is an internal insurance business and whose historical number of visits per second is greater than a preset threshold;

[0017] The second groups are constructed based on each of the second service modules.

[0018] According to some embodiments of the first aspect of the present application, the service grouping includes a third grouping;

[0019] The dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second includes:

[0020] Determine, from the plurality of the business modules, a third business module whose business attribute is the internal insurance business and whose historical number of visits per second is less than the preset threshold;

[0021] The third group is constructed, and the third group includes each of the third service modules.

[0022] According to some embodiments of the first aspect of the present application, the limiting number of connections is obtained by the following steps:

[0023] Based on the historical number of visits per second of the business module of the business group, a group weight of the business group is calculated;

[0024] The maximum number of connections of the insurance business database is obtained, and based on the group weight of the business group and the maximum number of connections, the limited number of connections of the listening port corresponding to the business group is obtained.

[0025] According to some embodiments of the first aspect of the present application, the calculating the grouping weight of the business group based on the historical number of visits per second of the business module of the business group includes:

[0026] Calculate the number of group accesses per second of the business group based on the historical number of accesses per second of each business module of the business group;

[0027] The group weight of the business group is obtained based on the number of group accesses per second of each business group.

[0028] According to some embodiments of the first aspect of the present application, determining the historical number of accesses per second of the insurance business database by the business module based on the historical access data includes:

[0029] Divide the preset historical time period corresponding to the historical access data into a plurality of subdivided historical time periods, and determine the subdivided number of accesses per second of the insurance business database by the business module in each of the subdivided historical time periods;

[0030] Based on the number of visits per second of the segment, calculate the time weight of the segmented historical time period;

[0031] The historical number of visits per second of the business module is calculated based on the segmented number of visits per second of each segmented historical time period and the time weight.

[0032] To achieve the above-mentioned purpose, a second embodiment of the present application provides a processing device for an insurance business database, including:

[0033] A first acquisition module, used to acquire historical access data of the insurance business database;

[0034] A request quantity determination module, used to determine the historical number of accesses per second by the business module to the insurance business database based on the historical access data;

[0035] A second acquisition module, used to acquire the service attributes of the service module;

[0036] A grouping module, used for dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second; wherein each of the business groups includes at least one of the business modules;

[0037] The port configuration module is used to set a limit on the number of connections for each listening port corresponding to the business group; the listening ports are multiple ports configured in the insurance business database for connecting to the business modules in the business group.

[0038] To achieve the above-mentioned purpose, an embodiment of the third aspect of the present application provides an electronic device, which includes a memory and a processor, and the memory stores a computer program. When the processor executes the computer program, it implements the method for processing the insurance business database described in any one of the embodiments of the first aspect of the present application.

[0039] To achieve the above-mentioned purpose, the fourth aspect of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the method for processing the insurance business database described in any one of the embodiments of the first aspect of the present application.

[0040] The processing method, device, electronic device and storage medium of the insurance business database of the embodiment of the present application divide each business module into multiple business groups, and set a limit on the number of connections for each listening port corresponding to the business group, so that the insurance business database is connected to the business modules in different business groups through different listening ports, and the isolation between the business modules in different business groups and the insurance business database is achieved. When the number of access requests of the business module of one business group to the insurance business database is greater than the limit on the number of connections of the listening port corresponding to the business group, resulting in a large number of requests of the business module being unable to be responded or released in time, and then causing the listening port corresponding to the business group to fail, only the connection between the business module in the business group and the insurance business database is affected; because other business groups use different listening ports, the business modules in other business groups can still access the insurance business database normally. In addition, setting the limit on the number of connections for different listening ports can disperse the connection pressure of the insurance business database. When one listening port fails, the remaining listening ports can still connect to the business module normally, which can improve the stability of the insurance business database. Therefore, the present application can avoid the situation where all business modules cannot normally access the insurance business database due to a large number of requests from one business module failing to respond in time, and can improve the stability of the insurance business database.

[0041] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The present application is further described below with reference to the accompanying drawings and embodiments, wherein:

[0043] Figure 1 A schematic diagram of the steps of the method for processing the insurance business database according to an embodiment of the present application;

[0044] Figure 2 for Figure 1 A specific flow chart of step S140;

[0045] Figure 3 for Figure 1 Another specific flow chart of step S140;

[0046] Figure 4 for Figure 1A schematic flow chart of step S140 in other embodiments;

[0047] Figure 5 A flowchart of the generation steps for limiting the number of connections;

[0048] Figure 6 for Figure 5 A specific flow chart of step S510;

[0049] Figure 7 for Figure 1 A specific flow chart of step S120;

[0050] Figure 8 A schematic diagram of the structure of a processing device for an insurance business database according to an embodiment of the present application;

[0051] Fig. 9 A schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0052] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be understood as limiting the present application.

[0053] In the description of the present application, it should be understood that descriptions involving orientation, such as up, down, front, back, left, right, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present application.

[0054] In the description of this application, "several" means more than one, "more" means more than two, "greater than", "less than", "exceed", etc. are understood to exclude the number itself, and "above", "below", "within", etc. are understood to include the number itself. If there is a description of "first" or "second", it is only used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0055] In the description of this application, unless otherwise clearly defined, terms such as setting, installing, connecting, etc. should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in this application based on the specific content of the technical solution.

[0056] In the description of the present application, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0057] In the related art, the insurance business database is connected to all business modules through one listening port by configuring only one listening port. In this case, when the access requests of a certain business module to the insurance business database increase sharply, and a large number of requests of the business module cannot be responded to or released by the insurance business database in time, it will cause the listening port to fail, and the insurance business database will generate a database connection storm, and all business modules will be unable to access the insurance business database through the listening port.

[0058] Based on this, the present application proposes a method, device, electronic device and storage medium for processing an insurance business database. Even if a large number of requests from a certain business module cannot be responded to or released in time, the remaining business modules can still access the insurance business database normally.

[0059] The processing method of the insurance business database provided in the embodiment of the present application relates to the field of database technology. The processing method of the insurance business database provided in the embodiment of the present application can be applied to the terminal, can also be applied to the server side, and can also be software running in the terminal or the 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 it 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 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 and other basic cloud computing services; the software can be an application that implements the processing method of the insurance business database, 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] Reference Figure 1 , Figure 1 The process flow diagram of the method for processing the insurance business database of the embodiment of the present application is as follows: The method for processing the insurance business database of the embodiment of the first aspect of the present application may include but is not limited to steps S110 to S150.

[0062] Step S110, obtaining historical access data of the insurance business database;

[0063] In some embodiments, the insurance business database refers to data used to store insurance business related data. For example, the insurance business database can store customer data, which can include basic information of the customer, the customer's insurance history, information about the products purchased by the customer, and risk assessment information of the customer; the basic information of the customer includes name, gender, age, contact information, address, etc.; the risk assessment information of the customer includes the health status and occupation information of the customer. The insurance business database can store policy data, which includes information such as policy number, policy effective date, insurance period, premium payment record, policy change record, etc. The policy payment record includes information such as payment amount, payment time, payment method, etc.; the policy change record includes beneficiary change information and insurance amount adjustment information. The insurance business database can also store claim records, which include information such as claim application time, claim applicant, claim reason, claim auditor, claim investigation record, claim related evidence, claim review result, etc. The insurance business database can also store insurance sales data, which includes salesperson information, sales volume, and sales product information. The insurance business database can also store other information related to insurance business, which is not specifically limited in this application.

[0064] It should be noted that in various specific implementations of the present application, for example, when storing data in an insurance business database, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, 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 by jumping 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.

[0065] In some embodiments, the insurance business database uses an Oracle database, which is a relational database management system that supports the storage, management, and analysis of large-scale data. Oracle database uses advanced query optimizer, concurrency control, and cache management technology, which can handle large-scale data and high concurrent access, and provide efficient query and transaction processing capabilities. Oracle database supports parallel processing technology, which divides large tasks into multiple small tasks for parallel execution, further improving system performance. Oracle listener supports multi-instance configuration and multiple listening ports, and can improve the reliability of the database through load balancing and fault tolerance mechanisms.

[0066] In some embodiments, the insurance business database uses the MySQL database, which is a popular open source relational database management system. The MySQL database can run on a variety of operating systems, including Linux, Windows, macOS, etc. MySQL is known for its high performance and reliability, and is suitable for processing large amounts of data and high concurrent requests. MySQL supports multi-user access, allowing multiple users to access the database at the same time. MySQL supports transaction processing to ensure data integrity and consistency. The MySQL database supports multi-instance configuration and supports multiple listening ports.

[0067] In some embodiments, relevant users interact with the insurance business database through the insurance system. The insurance system is configured with multiple applications, each of which serves as a business module. Relevant users access the insurance business database through the application. The business module can be an insurance product query module, an insurance reporting module, a loss assessment module, a claim application module, a claim progress query module, etc. The business module can also be a module of other insurance businesses, which is not limited in this application. Relevant users can refer to internal personnel of the insurance company or customers of the insurance company, such as people who purchase insurance.

[0068] In some embodiments, the insurance business database is configured with a log system. When a business module accesses the insurance business database, the log system generates a log record, which stores information about the business module and a timestamp when the business module accesses the insurance business database. When acquiring historical access data of the insurance business database in step S110, first determine a preset historical time period to be acquired, and then acquire all log records with timestamps within the preset historical time period from the log system to obtain historical access data.

[0069] Step S120, determining the historical number of accesses per second of the business module to the insurance business database based on the historical access data;

[0070] In some embodiments, each business module is provided with a business identifier, and the business identifier corresponds to the business module one-to-one, and the business identifier is used to indicate the business module. When the business module accesses the insurance business database, the request sent by the business module to the insurance business database includes the business identifier, and the log record in the log system includes the business identifier and the timestamp of the business module. Therefore, based on the business identifier, the number of log records corresponding to each business identifier within a preset historical time period can be determined from the historical access data, and the number of log records divided by the preset historical time period is the historical number of visits per second to the business module corresponding to the business identifier. In this way, the historical number of visits per second to the insurance business database by each business module can be obtained.

[0071] Step S130, obtaining the service attributes of the service module;

[0072] In one embodiment, each business module is provided with business attributes, for example, the business attributes may be foreign-related insurance business or internal insurance business.

[0073] Step S140, dividing each business module into a plurality of business groups based on business attributes and historical access numbers per second; wherein each business group includes at least one business module;

[0074] Step S150, setting a connection limit for each listening port corresponding to the business group; the listening port is a plurality of ports configured in the insurance business database for connecting to the business modules in the business group.

[0075] It is worth noting that the listening ports correspond one-to-one to the business groups, and the limited number of connections for each listening port is less than the maximum number of connections of the insurance business database. Therefore, when the number of access requests to the business module of the business group corresponding to only one listening port increases sharply and causes a failure, it will not affect the remaining listening ports, and the remaining listening ports of the insurance business database can operate normally.

[0076] It should be noted that the maximum number of connections to a database refers to the maximum number of connections that a database server can handle simultaneously. Each connection represents a session established with a database server for performing queries, updates, and other database operations. The maximum number of connections to a database is an important indicator of database performance and affects the concurrent processing capabilities of the database.

[0077] The processing method of the insurance business database of the embodiment of the present application is through steps S110 to S150, by dividing each business module into multiple business groups, and setting a limit on the number of connections for each listening port corresponding to the business group, so that the insurance business database is connected to the business modules in different business groups through different listening ports, and the isolation between the business modules in different business groups and the insurance business database connection is realized. When the number of access requests of the business module of one of the business groups to the insurance business database is greater than the limit on the number of connections of the listening port corresponding to the business group, resulting in a large number of requests of the business module being unable to be responded or released in time, and then causing the listening port corresponding to the business group to fail, only the connection between the business module in the business group and the insurance business database is affected; because other business groups use different listening ports, the business modules in other business groups can still access the insurance business database normally. In addition, setting the limit on the number of connections for different listening ports can disperse the connection pressure of the insurance business database. When one listening port fails, the remaining listening ports can still be connected to the business module normally, which can improve the stability of the insurance business database. Therefore, the present application can avoid the situation where all business modules cannot normally access the insurance business database due to a large number of requests from one business module failing to respond in time, and can improve the stability of the insurance business database.

[0078] In some embodiments, the service group includes a first group. Figure 2 , Figure 2 for Figure 1 A specific flow chart of step S140 in FIG. 1 is a flow chart of step S140 in FIG. 1. Step S140 may include but is not limited to step S210 and step S220.

[0079] Step S210, determining a first business module whose business attribute is foreign-related insurance business from among multiple business modules;

[0080] Step S220: construct a first group based on each first service module.

[0081] It is worth noting that the business attribute of the first business module is foreign-related insurance business, which means that the first business module is directly related to the customers of the insurance company. Compared with the business module whose business attribute is internal insurance business, the first business module is very important. Therefore, it is necessary to independently construct a first group for each first business module, and the business group corresponds to the listening port one by one. Therefore, each first group corresponds to a listening port, so that each first business module is configured with a listening port to access the insurance business database, which can reduce the risk of the first business module being unable to access the insurance business database due to a sharp increase in the number of visits to other business modules.

[0082] In some embodiments, the service group includes a second group. Figure 3 , Figure 3 for Figure 1 Another specific flow chart of step S140 in FIG. Step S140 may include but is not limited to step S310 and step S320.

[0083] Step S310, determining, from the plurality of business modules, a second business module whose business attribute is internal insurance business and whose historical number of visits per second is greater than a preset threshold;

[0084] Step S320: construct a second group based on each second service module.

[0085] It is worth noting that although the business attribute of the second business module is internal insurance business, and its importance is lower than that of the first business module, the historical number of visits per second of the second business module is greater than the preset threshold, so the second business module is more likely to experience a sharp increase in the number of access requests. Therefore, it is necessary to independently construct a second group for each second business module, and the business group corresponds to the listening port one by one, so each second group corresponds to a listening port, so that each second business module is configured with a listening port to access the insurance business database. This can reduce the risk of other business modules being unable to access the insurance business database due to a sharp increase in the number of access requests from the second business module, and can reduce the risk of the second business module being unable to access the insurance business database due to a sharp increase in the number of visits from other business modules.

[0086] In some embodiments, the preset threshold is determined by:

[0087] Determine an internal business module whose business attribute is internal insurance business from among multiple business modules;

[0088] Calculate the average historical number of visits per second for each internal business module to obtain the preset threshold.

[0089] It is worth noting that the average value of the historical number of visits per second of each internal business module is used as the preset threshold. Therefore, compared with the internal business modules whose historical number of visits per second is lower than the preset threshold, the second business module whose historical number of visits per second is greater than the preset threshold is more likely to experience a sharp increase in the number of access requests.

[0090] It is understandable that the business group includes the third group. Figure 4 , Figure 4 for Figure 1 A flowchart of step S140 in some other embodiments. Step S140 may also include but is not limited to step S410 and step S420.

[0091] Step S410, determining, from the plurality of business modules, a third business module whose business attribute is internal insurance business and whose historical number of visits per second is less than a preset threshold;

[0092] Step S420: construct a third group, where the third group includes each third service module.

[0093] It is worth noting that the business attribute of the third business module is internal insurance business, which is less important than the first business module, and the historical number of accesses per second of the third business module is less than the preset threshold, so there is no need to build a business group for each third business module. Building a third group, which includes all third business modules, that is, all third business modules share a listening port, can reduce the risk that other business modules cannot normally access the insurance business database due to a sharp increase in the number of access requests from the third business module.

[0094] For example, in the auto insurance claim settlement system, the business modules include a reporting module, an investigation module, a damage assessment processing module, a claim settlement processing module, and a claim settlement payment module. The business attributes of the reporting module and the claim settlement payment module are foreign-related insurance business, which is of high importance. Therefore, the reporting module and the claim settlement payment module are the first business modules, and the reporting module and the claim settlement payment module are respectively a business group, namely the first group. The business attributes of the survey module, damage assessment processing module, and claim processing module are internal insurance business. The historical access numbers per second of the survey module, damage assessment processing module, and claim processing module are 4000, 1000, and 1000 respectively. The average value of the historical access numbers per second of the survey module, damage assessment processing module, and claim processing module is 2000, and the preset threshold is 2000. The historical access numbers per second of the survey module are greater than 2000, so the survey module is the second business module, and the second group is constructed for the survey module; while the historical access numbers per second of the damage assessment processing module and the claim processing module are less than 2000, so the damage assessment processing module and the claim processing module are the third business modules, and the third group is constructed, and the third group includes the damage assessment processing module and the claim processing module. Therefore, in this example, 4 listening ports are set in the insurance business database, one of which is used to listen to the access requests of the damage assessment processing module and the claim processing module, and the other three listening ports correspond to the reporting module, the survey module, and the claim payment module.

[0095] In some embodiments, reference Figure 5 , Figure 5 The flowchart of the steps for generating the limited number of connections is shown below. The limited number of connections is obtained by the following steps:

[0096] Step S510, calculating the group weight of the service group based on the historical number of visits per second of the service module of the service group;

[0097] Step S520, obtaining the maximum number of connections of the insurance business database, and obtaining the limited number of connections of the listening port corresponding to the business group based on the group weight of the business group and the maximum number of connections.

[0098] It is worth noting that the limited number of connections of the listening port refers to the number of concurrent connections that can be processed simultaneously on the listening port. The higher the group weight of the business group, the more important the business group is, and the larger the limited number of connections. In some embodiments, the group weight of each business group is less than 1, and the sum of the group weights of each business group is 1. The limited number of connections of the listening port = the group weight of the business group corresponding to the listening port * the maximum number of connections.

[0099] Exemplarily, in the auto insurance claims system, the business groups include 2 first groups, 1 second group and 1 third group. The group weight of the first group constructed based on the reporting module is 0.4, the group weight of the first group constructed based on the claims payment module is 0.2, the group weight of the second group is 0.3, and the group weight of the third group is 0.1; the maximum number of connections of the insurance business database is 10,000, therefore, the limited number of connections of the listening port corresponding to the first group constructed based on the reporting module is 0.4*10,000=4,000; the limited number of connections of the listening port corresponding to the first group constructed based on the claims payment module is 0.2*10,000=2,000; the limited number of connections of the listening port corresponding to the second group is 0.3*10,000=3,000; the limited number of connections of the listening port corresponding to the third group is 0.1*10,000=1,000.

[0100] In some embodiments, reference Figure 6 , Figure 6 for Figure 5 A specific flow chart of step S510 in FIG. 5 . Step S510 may include but is not limited to step S610 and step S620.

[0101] Step S610, calculating the number of group visits per second of the service group based on the historical number of visits per second of each service module of the service group;

[0102] Step S620: obtaining the group weight of the service group based on the number of group accesses per second of each service group.

[0103] It is worth noting that in step S610, the number of group accesses per second of each business group is calculated, the number of group accesses per second of the first group is the historical number of accesses per second of the first business module in the first group; the number of group accesses per second of the second group is the historical number of accesses per second of the second business module in the second group; the number of group accesses per second of the third group is the sum of the historical number of accesses per second of all third business modules in the third group.

[0104] In some embodiments, after calculating the number of group accesses per second of each business group, the sum of the number of group accesses per second of all groups is calculated to obtain the total number of accesses per second. The group weight of each business group is the ratio of the number of group accesses per second of the business group to the total number of accesses. Exemplarily, in the auto insurance claim system, the number of group accesses per second of the first group constructed based on the reporting module is 2000, the number of group accesses per second of the first group constructed based on the claim payment module is 1000, the number of group accesses per second of the second group is 1500, and the number of group accesses per second of the third group is 500. Then the total number of accesses per second is 2000+1000+1500+500=5000. The grouping weight of the first group constructed based on the report module is 2000 / 5000=0.4, the grouping weight of the first group constructed based on the claim payment module is 1000 / 5000=0.1, the grouping weight of the second group is 1500 / 5000=0.3, and the grouping weight of the third group is 500 / 5000=0.1.

[0105] In some embodiments, reference Figure 7 , Figure 7 for Figure 1 A specific flow chart of step S120 in FIG. 1 is a flow chart of step S120 in FIG. 1. Step S120 may include but is not limited to steps S710 to S730.

[0106] Step S710, dividing the preset historical time period corresponding to the historical access data into a plurality of subdivided historical time periods, and determining the subdivided number of accesses per second of the business module to the insurance business database in each subdivided historical time period;

[0107] Based on the preset division rules, the preset historical time period is divided into multiple subdivided historical time periods. For example, the preset historical time period is a festival on which the insurance company launches discounts. The period from 00:00 to 06:00 of the festival is divided into the first subdivided historical time period, the period from 06:01 to 12:00 of the festival is divided into the second subdivided historical time period, the period from 12:01 to 18:00 of the festival is divided into the third subdivided historical time period, and the period from 18:01 to 24:00 of the festival is divided into the fourth subdivided historical time period. The log records with timestamps within the subdivided historical time period are determined from the historical access data, and based on the business identifier of the business module, the subdivided number of visits per second for each subdivided historical time period of each business module can be obtained.

[0108] Step S720, calculating the time weight of the segmented historical time period based on the segmented number of visits per second;

[0109] Step S730, based on the segmented number of visits per second in each segmented historical time period and the time weight, calculate the historical number of visits per second of the business module.

[0110] In some embodiments, the sum of the subdivided access numbers per second of each subdivided historical time period is calculated to obtain the sum of the subdivided access numbers; the time weight of each subdivided historical time period is the ratio between the subdivided access numbers per second of the subdivided historical time period and the sum of the subdivided access numbers. Exemplarily, the subdivided access numbers per second of the first subdivided historical time period of a certain business module is 1000; the subdivided access numbers per second of the second subdivided historical time period is 1000; the subdivided access numbers per second of the third subdivided historical time period is 3000; the subdivided access numbers per second of the fourth subdivided historical time period is 5000; then the sum of the subdivided access numbers is 1000+1000+3000+5000=10000. Then the time weight of the first subdivided historical time period is 1000 / 10000=0.1; the time weight of the second subdivided historical time period is 1000 / 10000=0.1; the time weight of the third subdivided historical time period is 3000 / 10000=0.3; the time weight of the fourth subdivided historical time period is 5000 / 10000=0.5. The weighted average sum of the subdivided visits per second and the time weight of each subdivided historical time period is performed to obtain the historical visits per second of the business module. Specifically, the historical visits per second of the business module is (0.1*1000+0.1*1000+0.3*3000+0.5*5000) / 1=3600.

[0111] The embodiment of the present application calculates the historical number of visits per second for each business module through steps S710 to S730, and combines the weights of different historical time periods in the calculation process, which can better reflect the actual distribution and importance of the data, and facilitate the subsequent setting of connection limits for each listening port corresponding to the business group.

[0112] The second aspect of the present application provides a processing device for an insurance business database. Figure 8 , Figure 8 The structure diagram of the processing device of the insurance business database of the embodiment of the present application is as follows. The processing device of the insurance business database includes:

[0113] A first acquisition module 810 is used to acquire historical access data of an insurance business database;

[0114] A request quantity determination module 820, for determining the historical number of accesses per second of the business module to the insurance business database based on the historical access data;

[0115] The second acquisition module 830 is used to acquire the service attributes of the service module;

[0116] A grouping module 840, for dividing each business module into a plurality of business groups based on business attributes and historical access numbers per second; wherein each business group includes at least one business module;

[0117] The port configuration module 850 is used to set a limit on the number of connections for each listening port corresponding to the business group; the listening ports are multiple ports configured in the insurance business database for connecting to the business modules in the business group.

[0118] The processing device of the insurance business database is used to execute the processing method of the insurance business database of the embodiment of the first aspect. When executing the processing method of the insurance business database, by dividing each business module into multiple business groups, and setting a limit on the number of connections for each listening port corresponding to the business group, the insurance business database is connected to the business modules in different business groups through different listening ports, and the isolation between the connection between the business modules in different business groups and the insurance business database is realized. When the number of access requests of the business module of one of the business groups to the insurance business database is greater than the limit on the number of connections of the listening port corresponding to the business group, resulting in a large number of requests of the business module being unable to be responded or released in time, and then causing the listening port corresponding to the business group to fail, only the connection between the business module in the business group and the insurance business database is affected; because other business groups use different listening ports, the business modules in other business groups can still access the insurance business database normally. In addition, setting the limit on the number of connections for different listening ports can disperse the connection pressure of the insurance business database. When one listening port fails, the remaining listening ports can still connect to the business module normally, which can improve the stability of the insurance business database. Therefore, the present application can avoid the situation where all business modules cannot normally access the insurance business database due to a large number of requests from one business module failing to respond in time, and can improve the stability of the insurance business database.

[0119] In some embodiments, the grouping module 840 includes a first grouping unit and a first construction unit;

[0120] The first grouping unit is used to determine a first business module whose business attribute is foreign-related insurance business from multiple business modules;

[0121] The first constructing unit is used to construct a first group based on each first service module.

[0122] In some embodiments, the grouping module 840 includes a second grouping unit and a second building unit;

[0123] The second grouping unit is used to determine, from the plurality of business modules, a second business module whose business attribute is internal insurance business and whose historical number of visits per second is greater than a preset threshold;

[0124] The second constructing unit is used to construct the second grouping based on each second service module.

[0125] In some embodiments, the grouping module 840 includes a third grouping unit and a third construction unit;

[0126] The third grouping unit is used to determine, from the multiple business modules, a third business module whose business attribute is internal insurance business and whose historical number of visits per second is less than a preset threshold;

[0127] The third construction unit is used to construct a third group, and the third group includes various third service modules.

[0128] In some embodiments, the processing device of the insurance business database further includes a connection number determination module, and the connection number determination module includes a first weight calculation unit and a connection number calculation unit.

[0129] The first weight calculation unit is used to calculate the group weight of the service group based on the historical number of visits per second of the service module of the service group;

[0130] The connection number calculation unit is used to obtain the maximum number of connections of the insurance business database, and based on the group weight and the maximum number of connections of the business group, obtain the limited number of connections of the listening port corresponding to the business group.

[0131] In some embodiments, the first weight calculation unit includes a group access number calculation subunit and a group weight calculation subunit.

[0132] The group access number calculation subunit is used to calculate the group access number per second of the service group based on the historical number of accesses per second of each service module of the service group;

[0133] The group weight calculation subunit is used to obtain the group weight of the business group based on the number of group visits per second of each business group.

[0134] In some embodiments, the request quantity determination module 820 includes a partitioning unit, a second weight calculation unit, and a historical access count per second calculation unit.

[0135] The division unit is used to divide the preset historical time period corresponding to the historical access data into a plurality of subdivided historical time periods, and determine the subdivided number of accesses per second of the business module to the insurance business database in each subdivided historical time period;

[0136] The second weight calculation unit is used to calculate the time weight of the segmented historical time period based on the segmented number of visits per second;

[0137] The historical number of visits per second calculation unit is used to calculate the historical number of visits per second of the business module based on the segmented number of visits per second of each segmented historical time period and the time weight.

[0138] The third aspect of the present application provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the insurance business database processing method of the above embodiment when executing the computer program. The electronic device can be any smart terminal including a tablet computer, a car computer, etc.

[0139] When the processor implements the processing method of the insurance business database of the above embodiment when executing the computer program, by dividing each business module into multiple business groups, and setting a limit on the number of connections for each listening port corresponding to the business group, the insurance business database is connected to the business modules in different business groups through different listening ports, and the isolation between the connection between the business modules in different business groups and the insurance business database is achieved. When the number of access requests to the insurance business database by the business module of one of the business groups is greater than the limit on the number of connections of the listening port corresponding to the business group, resulting in a large number of requests of the business module being unable to be responded or released in time, and then causing the listening port corresponding to the business group to fail, only the connection between the business module in the business group and the insurance business database is affected; because other business groups use different listening ports, the business modules in other business groups can still access the insurance business database normally. In addition, setting the limit on the number of connections for different listening ports can disperse the connection pressure of the insurance business database. When one listening port fails, the remaining listening ports can still connect to the business module normally, which can improve the stability of the insurance business database. Therefore, the present application can avoid the situation where all business modules cannot normally access the insurance business database due to a large number of requests from one business module failing to respond in time, and can improve the stability of the insurance business database.

[0140] In some embodiments, reference Fig. 9 , Fig. 9 The hardware structure of the electronic device of the embodiment of the present application is illustrated, and the electronic device includes:

[0141] The processor 901 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (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;

[0142] 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 an operating system and other application programs. When the technical solution provided in the embodiment 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 processing method of the insurance business database in the embodiment of this application;

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

[0144] 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.);

[0145] 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);

[0146] 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 .

[0147] The fourth aspect of the present application is a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the method for processing the insurance business database of the first aspect of the present application.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] 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.

[0154] 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.

[0155] In the several embodiments provided in the present application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely 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. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0156] 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.

[0157] 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.

[0158] 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, 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.

[0159] 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 processing an insurance business database, characterized in that: include: Acquiring historical access data of the insurance business database; Determine the historical number of accesses per second to the insurance business database by the business module based on the historical access data; Obtaining the business attributes of the business module; Dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second; wherein each of the business groups includes at least one of the business modules; A connection limit is set for each listening port corresponding to the business group; the listening ports are multiple ports configured in the insurance business database for connecting to the business modules in the business group.

2. The method for processing an insurance business database according to claim 1, characterized in that: The service grouping includes a first grouping; The dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second includes: Determine, from the plurality of business modules, a first business module whose business attribute is foreign-related insurance business; The first group is constructed based on each of the first service modules.

3. The method for processing the insurance business database according to claim 2, characterized in that: The service grouping includes a second grouping; The dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second includes: Determine, from the plurality of business modules, a second business module whose business attribute is an internal insurance business and whose historical number of visits per second is greater than a preset threshold; The second groups are constructed based on each of the second service modules.

4. The method for processing an insurance business database according to claim 3, characterized in that: The service grouping includes a third grouping; The dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second includes: Determine, from the plurality of the business modules, a third business module whose business attribute is the internal insurance business and whose historical number of visits per second is less than the preset threshold; The third group is constructed, and the third group includes each of the third service modules.

5. The method for processing an insurance business database according to claim 1, characterized in that: The limit on the number of connections is obtained by the following steps: Based on the historical number of visits per second of the business module of the business group, a group weight of the business group is calculated; The maximum number of connections of the insurance business database is obtained, and based on the group weight of the business group and the maximum number of connections, the limited number of connections of the listening port corresponding to the business group is obtained.

6. The method for processing the insurance business database according to claim 5, characterized in that: The calculating the grouping weight of the business group based on the historical number of visits per second of the business module of the business group includes: Calculate the number of group accesses per second of the business group based on the historical number of accesses per second of each business module of the business group; The group weight of the business group is obtained based on the number of group accesses per second of each business group.

7. The method for processing an insurance business database according to claim 1, characterized in that: The determining, based on the historical access data, the historical number of accesses per second of the insurance business database by the business module comprises: Divide the preset historical time period corresponding to the historical access data into a plurality of subdivided historical time periods, and determine the subdivided number of accesses per second of the insurance business database by the business module in each of the subdivided historical time periods; Based on the number of visits per second of the segment, calculate the time weight of the segmented historical time period; The historical number of visits per second of the business module is calculated based on the segmented number of visits per second of each segmented historical time period and the time weight.

8. A processing device for an insurance business database, characterized in that: include: A first acquisition module, used to acquire historical access data of the insurance business database; A request quantity determination module, used to determine the historical number of accesses per second by the business module to the insurance business database based on the historical access data; A second acquisition module, used to acquire the service attributes of the service module; A grouping module, used for dividing each of the business modules into a plurality of business groups based on the business attributes and the historical number of visits per second; wherein each of the business groups includes at least one of the business modules; The port configuration module is used to set a limit on the number of connections for each listening port corresponding to the business group; the listening ports are multiple ports configured in the insurance business database for connecting to the business modules in the business group.

9. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the method for processing the insurance business database 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 processing the insurance business database according to any one of claims 1 to 7 is implemented.

Images