Insurance product management method and device, equipment and storage medium

Abstract

The invention provides an insurance product management method and device, equipment and a storage medium, and relates to the technical field of insurance product management.The method comprises the steps that an insurance product file list is obtained, insurance product files are used for describing service rules of insurance products, information in the file list is extracted through a large language model, and the extracted information is stored in the file list; and inputting the extracted information into a pre-constructed product model to fill product description, a product dependency relationship, a file list and sales authority, so that the filled product model is used for managing insurance products. Files and users are connected through informatization means through the product model, so that various problems caused by information islands are solved.

Description

Technical Field

[0001] The present application relates to the technical field of insurance product management, and in particular to an insurance product management method, device, equipment and storage medium. Background Art

[0002] Product management is a basic business activity of insurance companies. For example, after an insurance company designs an insurance product based on actuarial data, it is usually presented as an insurance clause, a set of rate tables and a set of cash value tables. These documents stipulate what kind of customers can be insured, how much money they invest, how much risk protection they can get, and what specific protections are included and the conditions for effectiveness.

[0003] In the past, most of the activities of insurance companies were based on these documents. For example, the IT department of an insurance company would develop an insurance system based on these product documents. These systems are presented as a set of operating interfaces and a set of backend modules for customers and agents. On the operating interface, customers and agents can complete operations such as information entry, premium calculation and online payment. The backend module will perform data storage, circulation, reporting, accounting and other activities. The sales support department of the insurance company will produce product promotional materials based on these documents and conduct training and promotion for the front-line business team. The operation department of the insurance company needs to maintain and manage the various underwriting rules of the products, and identify risky customers based on these rules to avoid abnormal claims. In actual business activities, customers may have various questions about the products, which will be answered through a series of roles such as agents, branch sales support positions, head office sales support positions, and head office operations departments.

[0004] Generally speaking, a large number of insurance companies' business activities are carried out based on the product documents mentioned above. In reality, the different levels of informatization of various activities and the different responsible departments of various activities will lead to information islands in actual work, which in turn leads to large manual workload, high communication costs, information asymmetry, etc. Summary of the invention

[0005] In response to the above problems, this application provides an insurance product management method, including the following contents:

[0006] In a first aspect, the present application provides an insurance product management method, the method comprising:

[0007] Obtain a list of insurance product documents, where the insurance product documents are used to describe the business rules of the insurance products;

[0008] Extracting information from the file list using a large language model;

[0009] The extracted information is input into a pre-built product model to fill in product descriptions, product dependencies, document lists, and sales permissions, so that the filled product model can be used to manage insurance products.

[0010] Optionally, the pre-built product model includes an insurance system library, a vector library and a structured database;

[0011] The insurance system library stores product description information and insurance rule information, which is used to generate an interface through a configuration interpreter to implement the insurance operation process, insurance benefit demonstration interface, insurance test cases and process test scripts;

[0012] The vector library stores product description terms and insurance rules terms, which are used to implement product problem consultation, system problem consultation and operation rule consultation functions;

[0013] The structured database stores structured data for displaying data relationships in a visual form, including a product management panel, a sales authority report, and a sales relationship perspective.

[0014] Optionally, the step of inputting the extracted information into a pre-built product model to fill in product description, product dependency, file list and sales authority includes:

[0015] Storing the extracted information in the insurance system library;

[0016] Vectorizing the extracted information, and storing the vectorized information in the vector library;

[0017] The extracted information is structured and stored in the structured database.

[0018] Optionally, the filled product model is used for managing insurance products including:

[0019] Insurance products are managed through the insurance subscription system, sales and payment system, and R&D tool system.

[0020] Optionally, the pre-built product model is used to manage different insurance products, wherein each insurance product includes multiple versions, and the contents of the insurance product file list corresponding to different versions and different types of insurance products are different.

[0021] In a second aspect, the present application provides an insurance product management device, the device comprising:

[0022] An acquisition unit, used to acquire a list of insurance product documents, wherein the insurance product documents are used to describe the business rules of the insurance products;

[0023] An extraction unit, used to extract information from the file list using a large language model;

[0024] The input unit is used to input the extracted information into a pre-built product model to fill in product descriptions, product dependencies, document lists and sales permissions, so that the filled product model can be used for the management of insurance products.

[0025] Optionally, the pre-built product model includes an insurance system library, a vector library and a structured database;

[0026] The insurance system library stores product description information and insurance rule information, which is used to generate an interface through a configuration interpreter to implement the insurance operation process, insurance benefit demonstration interface, insurance test cases and process test scripts;

[0027] The vector library stores product description terms and insurance rules terms, which are used to implement product problem consultation, system problem consultation and operation rule consultation functions;

[0028] The structured database stores structured data for displaying data relationships in a visual form, including a product management panel, a sales authority report, and a sales relationship perspective.

[0029] Optionally, the input unit is specifically used for:

[0030] Storing the extracted information in the insurance system library;

[0031] Vectorizing the extracted information, and storing the vectorized information in the vector library;

[0032] The extracted information is structured and stored in the structured database.

[0033] Optionally, the filled product model is used for managing insurance products including:

[0034] Insurance products are managed through the insurance subscription system, sales and payment system, and R&D tool system.

[0035] Optionally, the pre-built product model is used to manage different insurance products, wherein each insurance product includes multiple versions, and the contents of the insurance product file list corresponding to different versions and different types of insurance products are different.

[0036] In a third aspect, the present application provides a device comprising a memory and a processor, wherein the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the insurance product management method introduced in any implementation of the first aspect.

[0037] In a fourth aspect, the present application provides a computer-readable storage medium, in which a code is stored. When the code is executed, the device executing the code implements the insurance product management method introduced in any implementation of the first aspect.

[0038] The present application provides an insurance product management method. When executing the method, first obtain an insurance product file list, where the insurance product file is used to describe the business rules of the insurance product, use a large language model to extract information from the file list, and input the extracted information into a pre-built product model to fill in product descriptions, product dependencies, file lists, and sales permissions, so that the filled product model can be used to manage insurance products. Through this product model, all files and users are connected through information technology, thereby solving various problems caused by information islands. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0040] Figure 1 An insurance product business model provided for an embodiment of the present application;

[0041] Figure 2 A flowchart of an insurance product management method provided in an embodiment of the present application;

[0042] Figure 3 A schematic diagram of product model data transmission provided in an embodiment of the present application;

[0043] Figure 4 A business function diagram of insurance product management provided in an embodiment of the present application;

[0044] Figure 5 A schematic diagram of a technical architecture provided for an embodiment of the present application;

[0045] Figure 6 A schematic diagram of the structure of an insurance product management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0047] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0048] The present application provides an insurance product management method, wherein the management of insurance products is achieved through a product model. Figure 1 A brief introduction to the scheme of this application is given. Figure 1 An insurance product business model is provided in the embodiment of the present application. The insurance product model in the present application is constructed based on the business model. The business model includes: Document preparation: by compiling and organizing various documents related to insurance product management, it is used to describe business rules, including insurance terms, rate tables, current price tables, plan review tables, insurance rules, sales agreements, etc. This process is used to ensure that the content of the document is accurate and complete, and is saved and distributed in an appropriate format (such as PDF, Word, etc.).

[0049] After obtaining the file list, the product model in this application needs to implement functions such as product listing, benefit demonstration, product analysis, management authority setting, consultation response, and article writing and promotion according to the content in the file list. Finally, the product model can be used by a variety of people, such as customers and insurance agents, managers, business support personnel, etc. Specifically, customers and agents: need to complete operations such as benefit calculation and online insurance, and are the main users of the product. Managers: need to put products on and off the shelves, query and analyze product information, increase or decrease sales permissions, etc., and are the main executors of product management. Support staff: write product promotional materials, respond to internal and external business inquiries, etc., to provide support and guarantee for product management.

[0050] The above briefly introduces the product model used to implement insurance product management in this application. The following is a specific introduction to the management process of specific insurance products through the product model in conjunction with specific embodiments.

[0051] Figure 2A flowchart of an insurance product management method provided in an embodiment of the present application. Figure 2 As shown, the insurance product management method provided in the embodiment of the present application may include:

[0052] S201. Obtain a list of insurance product documents, where the insurance product documents are used to describe the business rules of the insurance products.

[0053] The list of documents for insurance products includes insurance clauses, rate tables, current price tables, plan review tables, insurance rules, and sales agreements. The insurance clauses are specific provisions in the insurance contract regarding the insurance liability, insurance period, insurance premium rate, exemption clauses, etc. of the insurance type. These clauses are an important part of the insurance contract and have important legal binding force on both the insurance company and the policyholder. The strict provisions of the insurance clauses help the insurance company to effectively manage risks, while also protecting the legitimate rights and interests of the policyholder during the insurance period.

[0054] A rate sheet is a detailed list of charges for different insurance products developed by an insurance company. It lists the prices of different products or services, as well as any discounts or surcharges that may apply. The rate sheet provides policyholders with transparent price information, helping them make informed consumer decisions. At the same time, the rate sheet is also an important tool for insurance companies to conduct pricing and sales.

[0055] The current price list usually refers to the price list of insurance products in the current market, which may include price information under different insurance sums, different protection periods, etc. However, not all insurance products provide a current price list, and the specific content and form of the current price list may vary depending on the insurance company and the product. For policyholders, understanding the current price list will help them better compare the prices of different products and make a more appropriate choice.

[0056] A plan review form is a form used to conduct a business review of a specific insurance plan. During the development or sales of insurance products, insurance companies need to conduct a strict business review of insurance plans to ensure that they comply with relevant laws and regulations and the company's business specifications. The plan review form usually contains basic information about the insurance plan, risk assessment, compliance review, etc.

[0057] Insurance rules are a series of regulations and requirements set by insurance companies for policyholders, insured persons and insurance operations. These rules are intended to regulate insurance behaviors, reduce risks, and protect the legitimate rights and interests of insurance companies and policyholders. Insurance rules usually include the policyholder's age range, identity requirements, occupational restrictions, health status notification, etc. The policyholder needs to comply with these rules to ensure the effectiveness and legality of the insurance process.

[0058] A sales agreement is an agreement signed between an insurance company and a sales channel or salesperson regarding the sale of insurance products. The agreement specifies the rights and obligations of both parties, including sales targets, sales channels, sales methods, commission payments, etc. Sales agreements are of great significance in safeguarding the cooperative relationship between insurance companies and sales channels, and also help to regulate sales behavior and improve sales efficiency.

[0059] S202: Extract information from the file list using a large language model.

[0060] Each file in the file list is parsed using a large language model (such as GPT or other natural language processing models). The model reads the file content and attempts to convert it into a series of semantic description sentences. These sentences are designed to capture the key information in the file and present it in a structured way. After parsing, a structured and semantic product description will appear in the model. These descriptions attempt to express the information in the file in a machine-readable way.

[0061] It should be noted that due to the complexity and diversity of natural language, these descriptions may not be completely accurate. Therefore, manual review is required, and the reviewer needs to evaluate the accuracy of the parsing results. By checking the semantic description statements generated by the model, ensure that they correctly reflect the information in the file list. If inaccuracies or omissions are found in the parsing results, the reviewer will correct these deficiencies. This may include adding missing information, correcting erroneous understandings, or adjusting structured expressions. After correction, the model saves usable product descriptions. These descriptions are consistent with the original information in the file list, and are presented in a structured and semantic way, which is convenient for subsequent processing and analysis.

[0062] Through these two steps, the large language model can be used to effectively extract information from the insurance product document list and convert it into a more machine-readable and easy-to-process form. This is of great significance for subsequent insurance product management, sales, risk assessment and other links.

[0063] S203: Input the extracted information into a pre-built product model to fill in product description, product dependency, file list and sales authority.

[0064] The pre-built product model is a structured framework that describes various aspects of an insurance product, including product description, dependencies, document checklists, sales permissions, etc.

[0065] Product description is the key information that conveys the core value and features of the product to users or the market. In the product mockup, the product description section needs to be filled with detailed, accurate and attractive text so that users can quickly understand the functions and benefits of the product.

[0066] Product dependencies refer to the interdependencies between a product and other components, systems, or services. In the product model, it is necessary to clearly list all external and internal components that the product depends on, as well as the connection methods and interaction logic between them.

[0067] The document list includes all documents and materials related to product development, production, sales and maintenance. These documents may include insurance terms, rate tables, current price tables, plan review tables, insurance rules, sales agreements, etc. In the product model, all necessary documents need to be listed and ensure that they are all the latest versions and easy to access.

[0068] Sales permissions refer to the sales permissions and restrictions of products in different regions, markets or sales channels. In the product model, the sales permissions of the products need to be clearly listed to ensure that the sales team can comply with relevant regulations and promote the products effectively.

[0069] In summary, the above steps are a process of integrating the collected information into the product model, which involves filling in multiple aspects to ensure the accuracy of product description, clarity of dependencies, completeness of document list and compliance of sales authority. This process is crucial for the successful development and marketing of products.

[0070] In one implementation of an embodiment of the present application, the pre-built product model includes an insurance system library, a vector library and a structured database; the insurance system library stores product description information and insurance rule information, which is used to generate an interface through a configuration interpreter to implement insurance operation procedures, insurance benefit demonstration interfaces, insurance test cases and process test scripts; the vector library stores product description entries and insurance rule entries, which are used to implement product problem consultation, system problem consultation and operation rule consultation functions; the structured database stores structured data, which is used to display data relationships in a visual form, including product management panels, sales authority reports and sales relationship perspectives.

[0071] Combine the following Figure 3 This paper introduces the data transmission process between product model and insurance system library, vector library and structured database. Figure 3A schematic diagram of product model data transmission provided for an embodiment of the present application, the insurance system library is one of the core components in the product model, which stores descriptive information and insurance rule information related to insurance products. This information is crucial for building insurance operation processes, displaying insurance benefits, and conducting insurance tests. The product description information describes in detail the characteristics, coverage, premiums and other information of the insurance product. This information will be used to generate various parts of the user interface to ensure that users can clearly understand the product. Insurance rule information: including insurance age, occupational restrictions, health status requirements, etc. These rules will guide the design of the insurance operation process to ensure that users can follow the prescribed steps to take out insurance.

[0072] By configuring the interpreter, the information in the insurance system library can be parsed and converted into user interface elements, such as the insurance operation process interface, insurance benefit demonstration interface, etc. At the same time, insurance test cases and process test scripts can also be generated to verify and optimize the insurance process.

[0073] The vector library stores entries related to insurance products, including product description entries and insurance rules entries. These entries are preprocessed and vectorized and can be used to implement various consulting functions. Including product problem consultation, when users ask specific questions about products, the system can provide accurate answers by matching the entries in the vector library. System problem consultation involves institutional issues such as policies and regulations in the insurance industry. The system can also answer them through the entries in the vector library. Operation rule consultation includes the insurance company's operating rules, claims settlement process, etc. This information is also stored in the vector library for user query convenience.

[0074] In addition, by using natural language processing technology, the user's consultation questions are converted into vector form and matched with the entries in the vector library. By calculating the similarity, the system can find the most relevant entry and give an answer.

[0075] The structured database stores organized structured data, which is displayed in the form of tables, charts, etc., so that users can intuitively understand the data relationship. This includes the product management panel, which provides comprehensive management functions for insurance products, including adding, modifying, and deleting product information. The sales authority report shows the authority information of different sales personnel or sales teams, including the types of products they can sell, sales areas, etc. The sales relationship perspective shows the relationship between sales data in the form of charts, such as sales volume, sales channels, customer distribution, etc., to help management better understand sales and make decisions.

[0076] Structured databases use relational database management systems (such as MySQL, PostgreSQL, etc.) for data storage and management. Through SQL query statements or data visualization tools (such as Tableau, Power BI, etc.), users can easily access and analyze data.

[0077] In summary, the product model in the embodiment of the application realizes comprehensive management and support of insurance products by integrating multiple components such as the insurance system library, vector library and structured database. This integrated design not only improves work efficiency, but also provides users with more convenient and accurate consulting and data display services.

[0078] In one implementation of the embodiment of the present application, the inputting of the extracted information into a pre-built product model to fill in the product description, product dependencies, document list and sales permissions includes: storing the extracted information into the insurance system library; vectorizing the extracted information and storing the vectorized information into the vector library; structuring the extracted information and storing the structured information into the structured database.

[0079] The information stored in the insurance system database includes the customer's basic information, detailed information on the insured product, premium calculation parameters, etc.

[0080] Vectorize the extracted information and store the vectorized information in the vector library. Vectorization is the process of converting unstructured text or data into vector form. These vectors are often used in machine learning or natural language processing tasks to perform operations such as similarity calculation, classification, or clustering. In this step, the extracted information (such as product descriptions, customer feedback, etc.) will be vectorized and stored in the vector library. The vector library is a database specifically used to store vector data. The vectorized information can be used in subsequent application scenarios such as product recommendations and customer portrait construction.

[0081] Structuring the extracted information and storing the structured information in a structured database: Structuring is the process of converting unstructured information into a structured data format. This usually involves extracting key information and organizing it into fields and records in a table or database. In this step, the extracted information (such as product dependencies, file lists, etc.) will be structured and stored in a structured database. A structured database is a database that stores data according to a specific data structure, such as a relational database. Structured information can be more easily queried, analyzed, and reported, supporting business processes such as product management and sales authority control.

[0082] In addition, the relevant system document library in the company can also be applied to the product model in the embodiment of the present application. The system document library includes company news and business management methods. The information extracted from the system document library using a large language model is vectorized, and the vectorized information is stored in the vector library, thereby supporting users to provide corresponding answers when consulting questions through AI.

[0083] In summary, these steps together constitute the complete process of inputting the extracted information into the pre-built product model for filling. Through vectorization, structured processing and storage, this information can be effectively used in product description, dependency analysis, file management and sales authority control.

[0084] In one implementation of the embodiment of the present application, the filled product model is used for the management of insurance products, including: managing insurance products through an insurance system, a sales and payment system, and an R&D tool system.

[0085] In the implementation of the embodiment of the present application, the filled product model plays an important role in the management of insurance products. The model realizes the comprehensive management of insurance products through three core systems: the insurance system (mall system), the sales and payment system, and the R&D tool system. Figure 4 As shown, Figure 4 A business function diagram of insurance product management provided for an embodiment of the present application, including an insurance system, also known as a mall system, which is the core interface of the insurance product for users and sales personnel. It involves the following functional points: The insurance system generates an insurance process: According to the product and related information selected by the user, a complete insurance process is automatically generated, including filling in the policyholder information, the insured person information, selecting a protection plan, etc. The insurance system verifies sales authority: During the insurance process, the system will verify whether the salesperson is qualified to sell the product based on the salesperson's authority and the product's sales path. This helps to ensure the compliance of sales activities. Business development tools generate business plans: Business development tools are important tools for sales personnel to show customers the features and advantages of products. Through this system, sales personnel can automatically generate detailed product plans, including coverage, premium calculation, claims process, etc.

[0086] The sales and expenditure system is mainly used for sales management and product display, involving the following functional points: The authority board displays the sales path: The system will display the product path and related information that the salesperson can sell according to his authority, helping the salesperson to better plan sales strategies. The product board displays product information: The product board is a platform that centrally displays product information, including product features, coverage, premium rates, etc. Sales staff and customers can quickly learn about product information through this platform. Auxiliary functions generate promotional materials: The system provides auxiliary functions to help sales staff generate promotional materials and promotional copy to increase product awareness and market share. The dialogue function answers product inquiries: The system has an intelligent dialogue function that can automatically answer customers' inquiries about products and improve customer service efficiency and satisfaction.

[0087] The R&D tool system is mainly used for product testing and development, involving the following functional points: Automatically generate test cases: Based on the information in the product model, the system can automatically generate test cases for the product, including functional testing, performance testing, safety testing, etc. Automatically complete functional testing: The system can automatically execute the generated test cases to verify the various functions of the product to ensure the quality and stability of the product.

[0088] In summary, the product model after filling has achieved comprehensive management of insurance products through the synergy of the insurance system, sales system and R&D tool system. These systems not only improve sales efficiency and service quality, but also ensure product quality and compliance.

[0089] In one implementation of the embodiment of the present application, the pre-built product model can realize cross-product management: that is, the product model can be applied to multiple different insurance products at the same time, such as insurance product A, insurance product B, and insurance product C. This cross-product management capability enables enterprises to maintain and manage product information on a unified platform, greatly reducing management costs and improving work efficiency.

[0090] In addition, the product model can also achieve cross-product management, that is, the product model can be applied to a variety of different insurance products at the same time, such as insurance product A, insurance product B and insurance product C. This cross-product management capability enables enterprises to maintain and manage product information on a unified platform, greatly reducing management costs and improving work efficiency.

[0091] For the same insurance product, the product model can also distinguish and manage its different versions. For example, although the 2020 version and the 2022 version of insurance product A may belong to the same product line, there may be significant differences in coverage, premium rates, claims process, etc. By recording and managing these differences, the product model ensures that sales and customer service staff can accurately understand and convey the latest information about the product.

[0092] In the product model, the contents of the insurance product document list corresponding to different versions and types of insurance products are different. This is mainly reflected in the following aspects: Document types and quantity: Different insurance products and their versions may involve different types and quantities of documents. For example, some products may require detailed protection terms, rate tables, insurance instructions and other documents, while other products may focus more on the preparation of documents such as claims procedures and health notices. As the market environment and laws and regulations change, the content of insurance product documents also needs to be constantly updated. By recording and managing these updates, the product model ensures that sales and customer service staff can obtain the latest product information at any time, thereby providing more accurate and professional services.

[0093] In order to ensure the accuracy and readability of information, the product model also needs to support the import and export of multiple file formats, including common document formats (such as Word, PDF, etc.), image formats (such as JPEG, PNG, etc.) and specific data formats (such as Excel tables, etc.).

[0094] In summary, the product model in the embodiment of the present application can effectively manage different insurance products and their multiple versions through its high flexibility and applicability. At the same time, by recording and managing the differences in the document lists of different insurance products, it ensures that sales personnel and customer service personnel can accurately understand and convey the latest information of the product, thereby providing better services.

[0095] The above are some specific implementations of an insurance product management method provided in the embodiment of the present application. Based on this, the present application also provides a corresponding device. The device provided in the embodiment of the present application will be introduced from the perspective of functional modularization.

[0096] The above embodiments introduce the data transmission of the product model and the functions that can be realized. The specific technical architecture of the product model provided by the present application is introduced below in conjunction with specific drawings. Figure 5 As shown, Figure 5 A schematic diagram of a technical architecture provided for an embodiment of the present application, which includes components such as multiple processing modules, databases, cloud services, and front-end business systems. Figure 5 Detailed introduction of each part:

[0097] The front-end business system, namely the user interface or front-end application, is used to interact with users.

[0098] The core control module is composed of fast API Swagger, controller and Agent. Fast API is used as the framework of the front-end business system. That is, the front-end business system is developed based on Python and takes advantage of the high performance and ease of use of fast API.

[0099] Fast Chat Controller is a component in the Fast Chat framework that is responsible for managing and scheduling multiple working nodes.

[0100] Wordker1 module: This module is connected to the Postgres database (local deployment), indicating that it may be responsible for handling database-related operations such as data query, update, etc.

[0101] Wordker2 module: Wordker2 is connected to a large model such as the ChatGLM2-6B (fine-tuning) model to handle tasks related to ChatGPT, such as text generation, dialogue understanding, etc. At the same time, after fine-tuning, ChatGLM2-6B can better adapt to specific application scenarios.

[0102] Wordker3 module, Wordker3 is connected to an instance on the Azure cloud to handle tasks related to cloud services. This module also uses a large model for generating or processing text, such as gpt-35-turbo-16k as a model.

[0103] The Wordker1 module, Wordker2 module and Wordker3 module are connected to the core control module through FastChat Controller. Fast Chat Controller is a component responsible for managing and scheduling multiple working nodes in the Fast Chat framework. It is responsible for monitoring the status of all working nodes and assigning tasks to appropriate working nodes according to the scheduling strategy.

[0104] PostgreSQL is a powerful open source relational database management system (RDBMS), known for its high performance, scalability, and SQL standard compatibility. It supports advanced database functions such as complex queries, transaction processing, data integrity constraints, and provides a rich set of plug-ins and extension mechanisms to meet the needs of various application scenarios.

[0105] In addition, in the above architecture, the vector library uses PostgreSQL15.4, the word segmentation model uses m3e-base, the deployment framework uses langchain0.2.7, the model uses baichuan2-13B, and the fine-tuning tool uses p-tuningv2.

[0106] Figure 6 A schematic diagram of the structure of an insurance product management device provided in an embodiment of the present application. Figure 6 As shown, the insurance product management device provided in the embodiment of the present application includes:

[0107] An acquisition unit 610 is used to acquire a list of insurance product documents, wherein the insurance product documents are used to describe the business rules of the insurance product;

[0108] An extraction unit 620, configured to extract information from the file list using a large language model;

[0109] The input unit 630 is used to input the extracted information into a pre-built product model to fill in product description, product dependency, document list and sales authority, so that the filled product model can be used for the management of insurance products.

[0110] In one implementation of the embodiment of the present application, the pre-built product model includes an insurance system library, a vector library and a structured database;

[0111] The insurance system library stores product description information and insurance rule information, which is used to generate an interface through a configuration interpreter to implement the insurance operation process, insurance benefit demonstration interface, insurance test cases and process test scripts;

[0112] The vector library stores product description terms and insurance rules terms, which are used to implement product problem consultation, system problem consultation and operation rule consultation functions;

[0113] The structured database stores structured data for displaying data relationships in a visual form, including a product management panel, a sales authority report, and a sales relationship perspective.

[0114] In one implementation of the embodiment of the present application, the input unit is specifically used for:

[0115] Storing the extracted information in the insurance system library;

[0116] Vectorizing the extracted information, and storing the vectorized information in the vector library;

[0117] The extracted information is structured and stored in the structured database.

[0118] In one implementation of the embodiment of the present application, the filled product model is used to manage insurance products, including:

[0119] Insurance products are managed through the insurance subscription system, sales and payment system, and R&D tool system.

[0120] In one implementation of the embodiment of the present application, the pre-built product model is used to manage different insurance products, wherein each insurance product includes multiple versions, and the contents of the insurance product file list corresponding to different versions and different types of insurance products are different.

[0121] The embodiments of the present application also provide corresponding devices and computer storage media for implementing the solutions provided by the embodiments of the present application.

[0122] The device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the method described in any embodiment of the present application.

[0123] The computer storage medium stores codes, and when the codes are executed, a device executing the codes implements the method described in any embodiment of the present application.

[0124] Through the description of the above implementation methods, it can be known that those skilled in the art can clearly understand that all or part of the steps in the above-mentioned embodiment method can be implemented by means of software plus a general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM) / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in each embodiment of the present application or some parts of the embodiments.

[0125] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0126] It should also be noted that the various embodiments in this specification are described in a progressive manner, and the same and similar parts between the various embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and apparatus embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments. The device and apparatus embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components indicated as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0127] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. An insurance product management method, characterized in that: The method comprises: Obtain a list of insurance product documents, where the insurance product documents are used to describe the business rules of the insurance products; Extracting information from the file list using a large language model; The extracted information is input into a pre-built product model to fill in product descriptions, product dependencies, document lists, and sales permissions, so that the filled product model can be used to manage insurance products.

2. The method according to claim 1, characterized in that The pre-built product model includes an insurance system library, a vector library and a structured database; The insurance system library stores product description information and insurance rule information, which is used to generate an interface through a configuration interpreter to implement the insurance operation process, insurance benefit demonstration interface, insurance test cases and process test scripts; The vector library stores product description terms and insurance rules terms, which are used to implement product problem consultation, system problem consultation and operation rule consultation functions; The structured database stores structured data for displaying data relationships in a visual form, including a product management panel, a sales authority report, and a sales relationship perspective.

3. The method according to claim 2, characterized in that The step of inputting the extracted information into the pre-built product model to fill in the product description, product dependency, file list and sales authority includes: Storing the extracted information in the insurance system library; Vectorizing the extracted information, and storing the vectorized information in the vector library; The extracted information is structured and stored in the structured database.

4. The method according to claim 1, characterized in that The filled product model is used to manage insurance products including: Insurance products are managed through the insurance subscription system, sales and payment system, and R&D tool system.

5. The method according to claim 1, characterized in that The pre-built product model is used to manage different insurance products, wherein each insurance product includes multiple versions, and the contents of the insurance product file list corresponding to different versions and different types of insurance products are different.

6. An insurance product management device, characterized in that: The device includes: An acquisition unit, used to acquire a list of insurance product documents, wherein the insurance product documents are used to describe the business rules of the insurance products; An extraction unit, used to extract information from the file list using a large language model; The input unit is used to input the extracted information into a pre-built product model to fill in product descriptions, product dependencies, document lists and sales permissions, so that the filled product model can be used for the management of insurance products.

7. The system according to claim 6, characterized in that The pre-built product model includes an insurance system library, a vector library and a structured database; The insurance system library stores product description information and insurance rule information, which is used to generate an interface through a configuration interpreter to implement the insurance operation process, insurance benefit demonstration interface, insurance test cases and process test scripts; The vector library stores product description terms and insurance rules terms, which are used to implement product problem consultation, system problem consultation and operation rule consultation functions; The structured database stores structured data for displaying data relationships in a visual form, including a product management panel, a sales authority report, and a sales relationship perspective.

8. The system according to claim 7, characterized in that The input unit is specifically used for: Storing the extracted information in the insurance system library; Vectorizing the extracted information, and storing the vectorized information in the vector library; The extracted information is structured and stored in the structured database.

9. A computing device, characterized in that The computing device includes: a memory and a processor; The memory is used to store computer programs; The processor is configured to implement the method according to any one of claims 1 to 5 when executing the computer program.

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 method according to any one of claims 1 to 5 is implemented.

Images