Insurance product management system, management method and storage medium
By adopting three-dimensional data structures and JSON format insurance description file analysis in the insurance product management system, the complexity and redundancy problems caused by traditional two-dimensional tables are solved, and efficient and flexible insurance product data management is achieved.
Patent Information
- Application Number
- CN202510519714.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-23
- Publication Date
- 2025-08-15
AI Technical Summary
In the existing insurance product management system, the traditional two-dimensional table structure leads to high complexity and high redundancy in product configuration, which increases the workload and risk of errors of configuration personnel.
A three-dimensional data structure is adopted, including three orthogonal axes of insurance plans, insurance plans and protection of interests. Each data point represents a product configuration, and a JSON data structure and decoder are used to parse insurance description files to achieve efficient data configuration and management.
It reduces the complexity and redundancy of product configuration, reduces the workload and error risks of configuration personnel, improves data access efficiency and system flexibility, and adapts to market changes and product innovation.
Smart Images

Figure CN120494983A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of insurance product management, and in particular to an insurance product management system, an insurance product management method, and a computer-readable storage medium. Background Art
[0002] During the insurance product sales process, insurance terms and benefits as core service content need to be displayed to customers and reflected in the insurance contract after the transaction.
[0003] Currently, insurance product management uses traditional database two-dimensional tables and codes to collect, organize and store insurance information.
[0004] However, as the insurance market develops, insurers are increasingly designing products to make them more attractive by packaging more benefits, expanding pricing dimensions, and offering a wider range of options. This has made the product configuration structure, originally based on two-dimensional tables, extremely complex and redundant, significantly increasing the workload of product configurers. This complexity and redundancy in configuration content also increases the risk of configuration errors. Summary of the Invention
[0005] In response to the defects in the prior art, the present invention provides an insurance product management system that can effectively reduce the complexity of product configuration structure, reduce redundancy, reduce the workload of configuration personnel, and reduce the risk of errors.
[0006] This application provides an insurance product management system, which includes:
[0007] The data storage architecture is a three-dimensional data structure, and the data storage architecture includes a first coordinate axis, a second coordinate axis, and a third coordinate axis that are orthogonal to each other. The first coordinate axis represents the insurance scheme, the second coordinate axis represents the insurance plan, and the third coordinate axis represents the protection benefit. Each data point in the data storage architecture represents a product configuration, and the product configuration includes at least the insurance scheme, the insurance plan, and the protection benefit.
[0008] In one aspect, the insurance scheme of the first coordinate axis includes a basic scheme and an optional scheme.
[0009] In one aspect, the primary and optional solutions of the first coordinate axis are explicitly positioned;
[0010] The insurance plan of the second coordinate axis is explicitly positioned;
[0011] The protection benefits of the third coordinate axis include the insurance amount, which is explicitly located and implicitly located with the associated premium data.
[0012] In one aspect, the insurance product management system further includes a decoder that parses an insurance description file to configure insurance data that conforms to the data storage architecture.
[0013] In one aspect, the data storage architecture is configured as a JSON data structure.
[0014] In addition, in order to solve the above problems, the present application also provides an insurance product management method, which is applied to the insurance product management system as described above, and the insurance product management method includes:
[0015] Acquire insurance data, and configure the insurance data according to the data configuration form of the data storage architecture, and according to representative contents of the first coordinate axis, the second coordinate axis, and the third coordinate axis;
[0016] The data of the data storage architecture is stored in a database.
[0017] In one aspect, the steps before obtaining insurance data include:
[0018] Obtain the description file of the insurance product, parse the description file according to the preset decoding rules, and form insurance data.
[0019] In one aspect, the step of parsing the description file according to a preset decoding rule includes:
[0020] An insurance data object is created for each insurance plan, wherein the insurance data includes the insurance plan name and premium combination data, wherein the premium combination data includes a combination identifier, a billing field identity array, billing field value data and a protection benefit.
[0021] In one aspect, the insurance product management method further comprises:
[0022] The description file is parsed according to the preset decoding rules by the artificial intelligence entity.
[0023] In addition, in order to solve the above problems, the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the insurance product management method described above.
[0024] The beneficial effects of this invention are reflected in the fact that, compared to traditional two-dimensional database tables, the three-dimensional data structure can organize insurance product data more clearly and efficiently. The three-dimensional data structure establishes a clear hierarchical relationship through three coordinate axes: insurance plan, insurance plan, and coverage benefit. Each data point corresponds to a product configuration, making product configuration clear at a glance. This reduces the complexity of the product configuration structure, reduces redundancy, reduces the workload of configuration personnel, and reduces the risk of errors. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly describes the drawings required for the specific embodiments or the description of the prior art. Similar elements or parts are generally identified by similar reference numerals throughout the drawings. Elements or parts in the drawings are not necessarily drawn to scale.
[0026] Figure 1 This is a schematic diagram of the structure of the insurance product management system for this application;
[0027] Figure 2 This is a schematic diagram of the three-dimensional data structure in the insurance product management system of this application;
[0028] Figure 3 A schematic diagram of data points in a three-dimensional data structure in the insurance product management system of this application;
[0029] Figure 4 A schematic diagram of the process steps for applying for the insurance product management method;
[0030] Figure 5 This is a schematic diagram of the process steps for parsing description files in the insurance product management method of this application.
[0031] Description of the accompanying drawings: 100, data storage architecture; 200, decoder; 300, database; 400, artificial intelligence entity. DETAILED DESCRIPTION
[0032] The following embodiments of the technical solution of the present invention will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention and are therefore only examples and are not intended to limit the scope of protection of the present invention.
[0033] It should be noted that, unless otherwise specified, the technical or scientific terms used in this application should have the common meanings understood by those skilled in the art to which the present invention belongs.
[0034] See Figure 1As shown, the present application provides an insurance product management system, which includes: a data storage architecture 100, the data storage architecture 100 is a three-dimensional data structure, the data storage architecture 100 includes a first coordinate axis, a second coordinate axis and a third coordinate axis that are orthogonal to each other, wherein the first coordinate axis represents the insurance scheme, the second coordinate axis represents the insurance plan, and the third coordinate axis represents the protection benefit. Each data point in the data storage architecture 100 represents a product configuration, and the product configuration includes at least an insurance scheme, an insurance plan and a protection benefit.
[0035] In practical applications, these three axes represent different key pieces of information, precisely locating various types of insurance data within a three-dimensional space. The first axis represents the insurance plan, which covers both basic and optional plans. For example, in a health insurance product, the basic plan might provide basic disease coverage, while the optional plan provides additional high-end medical services. The second axis represents the insurance plan, which is based on different plans within the insurance plan. For example, the aforementioned health insurance plan includes affordable plans suitable for young people and comprehensive plans for high-income individuals. The third axis represents the benefits of insurance, such as the critical illness compensation amount in critical illness insurance and the medical reimbursement amount in medical insurance, which are all concrete manifestations of the benefits of insurance.
[0036] Each data point in the data storage architecture 100 represents a product configuration, which includes at least an insurance solution, an insurance plan, and a guaranteed benefit. This one-to-one correspondence allows each product configuration to be accurately located in three-dimensional space, making it easier to manage and query. This three-dimensional data structure of the data storage architecture 100 brings many advantages to insurance product management. For example, in terms of product configuration, it is clear and intuitive, greatly reducing the complexity and redundancy of the configuration, allowing configuration personnel to work more efficiently and reducing the probability of errors. When accessing data, the required data can be quickly located through the three coordinate axes, such as looking for detailed information on a specific benefit under a specific solution or plan, which improves data processing efficiency. At the same time, when an insurance company needs to launch a new product solution, plan, or guaranteed benefit, the good scalability of the data storage architecture 100 can accommodate new data points to adapt to market changes and product innovation needs.
[0037] Furthermore, compared to the 300-dimensional tables in traditional databases, a three-dimensional data structure can organize insurance product data more clearly and efficiently. The three-dimensional data structure establishes a clear hierarchical relationship through three coordinate axes: insurance plan, insurance plan, and coverage benefits. Each data point corresponds to a product configuration, making product configurations clear at a glance. This reduces the complexity of the product configuration structure, reduces redundancy, reduces the workload of configuration personnel, and reduces the risk of errors.
[0038] Furthermore, the three-dimensional data structure enables rapid location and access of insurance data. Using the coordinates of three axes, it is possible to quickly find product configuration data corresponding to specific insurance plans, programs, and benefits. This data access method significantly improves system response speed when processing large amounts of insurance business data, reduces data retrieval and processing time, improves business processing efficiency, and provides customers with faster service.
[0039] Furthermore, the three-dimensional data structure provides insurance product management systems with tremendous flexibility and scalability. When an insurance company launches a new insurance scheme, plan, or benefit, they simply add the corresponding data points in the three-dimensional space without making large-scale changes to the overall data structure. Simply adding benefit data points to the corresponding scheme or plan allows for data expansion to adapt to evolving market demands and product innovations.
[0040] Furthermore, the three-dimensional data structure facilitates slice-and-slice analysis of insurance data from different dimensions. This allows for analysis of configuration differences across all plans and schemes for specific benefits. It also allows for comparative analysis of benefits across different plans and schemes, providing comprehensive and accurate data support for insurance companies' product optimization, pricing strategy adjustments, and market decision-making. Through this data analysis, insurance companies can better understand customer needs, optimize product design, and enhance their market competitiveness.
[0041] In one embodiment of the present application, the basic scheme and optional scheme of the first coordinate axis are explicitly positioned; in the insurance product management system, the first coordinate axis represents the insurance scheme, in which the basic scheme and optional scheme are explicitly positioned. This means that they have clear and direct identification and positioning methods in the data structure. Taking an automobile insurance product as an example, the basic scheme may cover basic protection contents such as vehicle loss insurance and third-party liability insurance, while the optional schemes include additional protections such as glass breakage insurance and car body scratch insurance. These basic schemes and optional schemes are clearly marked in the system data, and the corresponding scheme information can be found directly and quickly through the first coordinate axis, which is convenient for users to select and manage insurance products.
[0042] The second axis represents insurance plans, also explicitly positioned. Insurance plans are further refined and categorized based on insurance options, providing customers with different options. For example, in the aforementioned car insurance, there are economy plans tailored to different customer groups and needs, focusing on basic coverage with lower premiums; and luxury plans, offering more comprehensive coverage and value-added services but with relatively higher premiums. These plans are clearly identified in the system, allowing users to clearly identify specific plans using the second axis, meeting customers' diverse needs.
[0043] The third axis represents the guaranteed benefits, with the guaranteed benefits explicitly located and the associated premium data implicitly located. The third axis represents the guaranteed benefits, with the guaranteed benefits explicitly located and the associated premium data implicitly located. As a key indicator of guaranteed benefits, the guaranteed benefits are clearly identified in the system. For example, in a life insurance policy, the insured's death benefit is 1 million yuan, which can be directly accessed through the third axis. Premium data, however, is associated with the guaranteed benefits but implicitly located. This is because premium calculation typically involves multiple factors, such as the insured's age, health, and policy term. The system uses specific algorithms and rules to determine premiums based on these factors. Therefore, premium data is not displayed directly but is instead retrieved through relevant calculations and logic when needed, ensuring flexibility and accuracy in premium calculation.
[0044] In one embodiment of the present application, the insurance product management system further includes a decoder 200, which parses the insurance description file to configure insurance data that conforms to the data storage architecture 100. The core function of the decoder 200 in the insurance product management system is to parse the insurance description file. The insurance description file usually describes the details of the insurance product, such as the insurance scheme, insurance plan, and protection benefits. The job of the decoder 200 is to interpret these files, extract the key information therein, and configure it to form data that conforms to the requirements of the three-dimensional data structure. With the help of the decoder 200, the configuration efficiency of the insurance product can be greatly improved. The previous manual configuration of insurance product data, which is time-consuming and prone to errors, is reduced. Moreover, the decoder 200 configures the insurance data according to the unified data storage architecture 100, ensuring the consistency and standardization of different insurance product data in the system, and facilitating subsequent data management and analysis.
[0045] In one embodiment of the present application, the data storage architecture 100 is configured as a JSON data structure. JSON (Java Script Object Notation) is a lightweight data exchange format with a concise and clear text format that is easy to read and write. Using the JSON data structure facilitates the clear presentation of the structure and content of data. JSON has a flexible nested structure that corresponds well to the three-dimensional data structure of an insurance product management system. The insurance plan represented by the first coordinate axis, the insurance plan represented by the second coordinate axis, and the insurance benefits represented by the third coordinate axis can be implemented through nested JSON objects and arrays.
[0046] By using the JSON data structure, the insurance product management system can conveniently store insurance data in files or database 300. This allows efficient data query and update operations. For example, to query all insurance plans and benefits under a particular insurance program, the data can be quickly located and retrieved simply by parsing JSON.
[0047] Because JSON is a universal data exchange format, the insurance product management system can easily exchange data with other systems (such as sales systems, claims systems, etc.). Other systems can directly parse JSON data to obtain the required insurance product information, achieving seamless integration between systems.
[0048] When an insurance company launches a new insurance product or adjusts an existing one, it only needs to modify the JSON data. The flexibility of JSON enables the system to quickly adapt to these changes without requiring large-scale modifications to the entire system architecture.
[0049] See Figure 2 As shown in the figure, this is a three-dimensional data structure diagram of an insurance product, which uses coordinate axes to show the relationship between insurance options, insurance plans, and guaranteed benefits:
[0050] The X-axis, or the first axis, represents insurance plans, a macro-classification of insurance products. The chart includes the Basic Plan (BASIC001), the Advanced Plan (OPT001), and the Premium Plan (OPT002). These plans cater to customers with different needs. The Basic Plan provides basic coverage, while the Advanced and Premium Plans offer more comprehensive coverage or higher limits.
[0051] The Y-axis, or secondary axis, represents the insurance plan, a further breakdown of the product within the insurance plan. There are Plan A, Plan B, Plan C, Plan D, and Plan E. Different plans within the same plan vary in coverage, insured amount, and premium, allowing customers to choose based on their needs.
[0052] The Z-axis, or the third axis, represents the guaranteed benefits. These include accidental injury (ACC001), critical illness (CRI001), outpatient medical care (MED002), and inpatient medical care (MED001). Guaranteed benefits are the core of insurance products, and customers primarily purchase insurance to obtain these benefits.
[0053] The various dimensions are combined with each other. For example, the basic plan (BASIC001) can include Plan AE, and Plan A covers benefits such as accidental injury and critical illness protection, forming a complete insurance product system, which makes it easier for insurance companies to manage products and for customers to choose suitable insurance.
[0054] See Figure 3The following figure shows the three-dimensional data structure of insurance products, which uses the X, Y, and Z coordinate axes to present the insurance scheme, insurance plan, and protection benefits, as well as key information such as the insured amount, premium, and rate under their combination:
[0055] Coordinate axis meaning
[0056] The X-axis shows the insurance plan categories, including Basic (BASIC001), Advanced (OPT001), and Premium (OPT002). These plans differ in coverage and service levels. The Basic plan focuses on basic protection, while the Advanced and Premium plans offer more comprehensive coverage and higher limits.
[0057] The Y-axis represents the insurance plans, including Plan A, Plan B, Plan C, Plan D, and Plan E. Different plans under the same plan differ in terms of coverage, premiums, and coverage details to meet the diverse needs of customers.
[0058] The Z-axis represents the protection benefits, that is, the specific protection rights and interests provided by the insurance product to customers, covering accidental injury (ACC001), critical illness protection (CRI001), outpatient medical care (MED002), and inpatient medical care (MED001).
[0059] The data points in the chart represent key figures for specific insurance plans, programs, and benefit combinations:
[0060] (BASIC001, PLAN_A, MED001): Sum assured = 100,000, rate = 0.6%: For Plan A under the basic plan, the sum assured for the hospitalization medical benefit is 100,000, and the rate is 0.6%.
[0061] (OPT001, PLAN_D, ACC001): Sum assured = 2,000,000: For Plan D under the high-end plan, the sum assured for accidental injury benefit is 2,000,000.
[0062] (OPT002, PLAN_E, ACC001): Sum assured = 3,000,000: For Plan E under the Premium Plan, the sum assured for the Accidental Injury Benefit is 3,000,000.
[0063] This three-dimensional structure clearly presents the key data of each dimensional element in the insurance product system and their combination, making it easier for insurance companies to manage products and formulate pricing strategies, and also making it easier for customers to intuitively understand the coverage and costs of different insurance product combinations.
[0064] See Figure 4 As shown, the present application also provides an insurance product management method, which is applied to the insurance product management system as described above, and the insurance product management method includes:
[0065] In step S10, insurance data is acquired and arranged according to the data configuration format of data storage architecture 100, based on the representations of the first, second, and third coordinate axes. Step S10 is a key step in data processing within the insurance product management system. Its purpose is to rationally arrange the acquired insurance data according to data storage architecture 100 for efficient subsequent management and use.
[0066] This insurance product management uses a three-dimensional data structure, a JSON data storage architecture 100, where the first axis represents the insurance plan, the second axis represents the insurance plan, and the third axis represents the insurance benefits. This architecture provides a clear framework for configuring insurance data.
[0067] More specifically, the acquired insurance data is categorized based on the first axis, representing the insurance plan. Within each insurance plan, the data is further broken down based on the second axis, representing the insurance plan. For example, health insurance plans might have basic plans, upgraded plans, and so on, with the relevant data categorized into the corresponding plans. Within each insurance plan, specific data is determined based on the third axis, representing the benefits.
[0068] Based on the above classification and segmentation results, the insurance data is organized into a JSON data structure. Each insurance plan can be represented as a JSON object containing an array of multiple insurance plans; each insurance plan is also a JSON object containing an array of multiple benefits.
[0069] Step S20: storing the data of the data storage architecture 100 into the database 300. This is mainly to store the insurance data organized according to the specific data storage architecture 100 into the database 300 for subsequent management, query and use.
[0070] In one embodiment of the present application, before the step of obtaining insurance data, the following steps are included:
[0071] Step S01: Obtain the insurance product description file and parse it according to pre-set decoding rules to generate insurance data. Step S01 is the initial step in the data processing flow of the insurance product management system, converting the insurance product description file into insurance data for subsequent processing. The insurance product description file is the data source for this step. These files are typically compiled by the insurance company's product design department or relevant business personnel and describe in detail various aspects of the insurance product, such as the insurance plan, insurance plan, and guaranteed benefits.
[0072] More specifically, decoding rules are pre-defined and determined based on the format of the description file and the data requirements of the insurance product management system. The insurance product description file is read and the file contents are loaded into memory. Different file formats require different methods for reading the file. After reading the file, the file format is verified according to the pre-set decoding rules to ensure that it meets the requirements. Once the file format verification passes, the key information is extracted from the file according to the decoding rules. Once the key information is extracted, it is converted into insurance data. Insurance data is typically stored using a unified data structure within the system for subsequent processing and use.
[0073] By parsing description files according to preset decoding rules, insurance product information in different formats and representations can be converted into unified insurance data, achieving data standardization and laying the foundation for subsequent data processing and management. Automatically parsing description files to generate insurance data avoids the tedious process of manual data entry, greatly improving data processing efficiency and reducing the risk of human error.
[0074] See Figure 5 As shown, in one embodiment of the present application, the step of parsing the description file according to the preset decoding rules includes:
[0075] Step S011 creates an insurance data object for each insurance plan. The insurance data includes the insurance plan name and premium combination data. The premium combination data includes a combination identifier, an array of billing field identities, billing field value data, and the guaranteed benefit. Step S011 further refines the insurance data based on step S01. This primarily creates an insurance data object for each insurance plan, which facilitates more detailed management and storage of insurance product information.
[0076] In step S01, the insurance product description files are acquired and parsed to generate insurance data. However, this data is relatively general and needs to be structured for better management and use. Step S011 refines the insurance plans and creates dedicated data objects for each plan to more clearly organize and present relevant information.
[0077] Specifically, identify different insurance plans from the previously parsed insurance data. Create an insurance data object for each identified plan. Object creation methods vary between programming languages. Name the insurance plan to facilitate identification and management, such as "Basic Insurance Plan" in the example above.
[0078] The combination identifier, i.e., combination ID, is used to uniquely identify the premium combination, such as "C001", so that the system can distinguish and reference it.
[0079] The billing field identity array contains identifiers of billing fields related to premium calculation, such as "F001" and "F002", which correspond to specific billing factors.
[0080] The billing field value data stores the specific numerical value corresponding to each billing field, such as the value corresponding to "F001" is 1000, and the value corresponding to "F002" is 20. These values will be used to calculate the premium.
[0081] The benefits included in an insurance plan allow users to clearly understand the coverage provided by the plan. By creating an insurance data object for each insurance plan, the insurance data is structured, making the data organization clearer and easier to query, modify, and analyze.
[0082] Detailed records of premium combination data provide a clear basis for premium calculation. Based on the billing field identity array and billing field value data, combined with a pre-set algorithm, premiums can be accurately calculated. This also facilitates the management and comparison of different premium combinations. The clear insurance data object structure helps present the specific content and features of insurance plans to customers. Customers can intuitively understand the insurance plan name, included benefits, and premium calculation information, improving sales efficiency and customer satisfaction.
[0083] In one embodiment of the present application, the insurance product management method further includes:
[0084] In step S02, the AI 400 parses the description file according to preset decoding rules. This is a key step in the insurance product management system, where AI 400 parses the description file according to preset decoding rules to generate insurance data. The insurance product description file is input into AI 400. AI 400 reads the file contents and converts them into a processable data format. AI 400 analyzes and matches the file contents according to preset decoding rules. For example, if the rule requires extracting the insurance plan name from a specific field in the JSON file, AI 400 will search the corresponding field and extract the information. AI 400 extracts key information from the file, such as the insurance plan, insurance plan, and coverage benefits, and converts this information into a unified data structure within the system. AI 400 outputs the parsed insurance data, which can be used for subsequent processing and management. AI 400 can rapidly process large volumes of description files, significantly improving processing efficiency and shortening data processing cycles compared to manual parsing.
[0085] 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 insurance product management method is implemented.
[0086] The specific embodiments and beneficial effects of the computer-readable storage medium in this application can be found in the above-mentioned insurance product management method, which will not be repeated here.
[0087] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present invention, and they should all be included in the scope of the claims and description of the present invention.
Claims
1. An insurance product management system, characterized in that: The insurance product management system includes: The data storage architecture is a three-dimensional data structure, and the data storage architecture includes a first coordinate axis, a second coordinate axis, and a third coordinate axis that are orthogonal to each other. The first coordinate axis represents the insurance scheme, the second coordinate axis represents the insurance plan, and the third coordinate axis represents the protection benefit. Each data point in the data storage architecture represents a product configuration, and the product configuration includes at least the insurance scheme, the insurance plan, and the protection benefit.
2. The insurance product management system according to claim 1, characterized in that: The insurance scheme of the first coordinate axis includes a basic scheme and an optional scheme.
3. The insurance product management system according to claim 2, characterized in that: The basic scheme and the optional scheme of the first coordinate axis are explicitly positioned; The insurance plan of the second coordinate axis is explicitly positioned; The protection benefits of the third coordinate axis include the insurance amount, which is explicitly located and implicitly located with the associated premium data.
4. The insurance product management system according to claim 1, characterized in that: The insurance product management system further includes a decoder that parses an insurance description file to configure and form insurance data that conforms to the data storage architecture.
5. The insurance product management system according to claim 1, characterized in that: The data storage architecture is set to a JSON data structure.
6. A method for managing insurance products, characterized in that: The insurance product management method is applied to the insurance product management system according to any one of claims 1 to 5, and the insurance product management method includes: Acquire insurance data, and configure the insurance data according to the data configuration form of the data storage architecture, and according to representative contents of the first coordinate axis, the second coordinate axis, and the third coordinate axis; The data of the data storage architecture is stored in a database.
7. The insurance product management method according to claim 6, characterized in that: The steps to obtain insurance data include: Obtain the description file of the insurance product, parse the description file according to the preset decoding rules, and form insurance data.
8. The insurance product management method according to claim 7, characterized in that: The step of parsing the description file according to a preset decoding rule includes: An insurance data object is created for each insurance plan, wherein the insurance data includes the insurance plan name and premium combination data, wherein the premium combination data includes a combination identifier, a billing field identity array, billing field value data and a protection benefit.
9. The insurance product management method according to claim 7, characterized in that: The insurance product management method further includes: The description file is parsed according to the preset decoding rules by the artificial intelligence entity.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the insurance product management method according to any one of claims 6 to 9 is implemented.