Insurance product meta-attribute management method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of business evaluation and the field of insurance business science and technology, and provides an insurance product meta-attribute management method and device, electronic equipment and a computer readable storage medium, and the method comprises the steps: obtaining an insurance product meta-attribute set; traversing each insurance product meta-attribute in the insurance product meta-attribute set to obtain an attribute name, an attribute type, an attribute rule and an attribute identifier; generating an attribute configuration dictionary according to the attribute name, the attribute type, the attribute rule and the attribute identifier; performing component mapping processing according to the attribute configuration dictionary to obtain an insurance policy component; and performing rule injection processing according to the attribute configuration dictionary to obtain an insurance policy rule, and performing data formatting processing according to the insurance policy component, the insurance policy rule and the received user parameters to obtain an insurance insurance policy. By means of the technical scheme, traditional static attribute design can be broken through, dynamic adding, modifying and deleting of meta attributes are supported, and code adjustment is not needed.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of data management technology, and in particular to a method, apparatus, electronic device, and computer-readable storage medium for managing the meta-attributes of insurance products. Background Technology

[0002] As people's living standards continue to improve, the insurance business has also been well promoted and developed. Within the insurance industry, there are medical insurance for physical health protection, property insurance for personal property protection, and life insurance for personal life insurance. For each type of insurance product, its attributes typically need to be dynamically adjusted based on market changes, policy adjustments, or customer needs. However, traditional insurance product management systems often employ static attribute design. Adding, modifying, and deleting attributes requires adjustments at the code level, resulting in long development cycles, high maintenance costs, and difficulty in quickly responding to market changes. Summary of the Invention

[0003] The following is an overview of the subject matter described in detail herein. This overview is not intended to limit the scope of the claims.

[0004] To address the problems mentioned in the background section, this application provides a method, apparatus, electronic device, and computer-readable storage medium for managing the meta-attributes of insurance products. This method breaks through the limitations of traditional static attribute design, supports the dynamic addition, modification, and deletion of meta-attributes, eliminates the need for code adjustments, improves flexibility and response speed, shortens the development cycle, and reduces maintenance costs.

[0005] In a first aspect, embodiments of this application provide a method for managing the meta-attributes of insurance products, including: Obtain the set of meta-attributes of insurance products, wherein the set of meta-attributes of insurance products includes multiple meta-attributes of insurance products; Each of the insurance product meta-attributes in the set of insurance product meta-attributes is traversed to obtain the attribute name, attribute type, attribute rule, and attribute identifier; Generate an attribute configuration dictionary based on the attribute name, the attribute type, the attribute rule, and the attribute identifier; The component mapping process is performed based on the attribute configuration dictionary to obtain the policy component; and the rule injection process is performed based on the attribute configuration dictionary to obtain the policy rule. The insurance policy is obtained by formatting data based on the policy component, the policy rules, and the received user parameters.

[0006] Secondly, embodiments of this application also provide an insurance product meta-attribute management device, the device comprising: The acquisition unit is used to acquire a set of insurance product meta-attributes, wherein the set of insurance product meta-attributes includes multiple insurance product meta-attributes; The traversal unit is used to traverse each of the insurance product meta-attributes in the set of insurance product meta-attributes to obtain the attribute name, attribute type, attribute rule and attribute identifier; The construction unit is used to generate an attribute configuration dictionary based on the attribute name, the attribute type, the attribute rule, and the attribute identifier; An execution unit is configured to perform component mapping processing based on the attribute configuration dictionary to obtain a policy component; and to perform rule injection processing based on the attribute configuration dictionary to obtain policy rules. The conversion unit is used to perform data formatting processing based on the policy component, the policy rules, and the received user parameters to obtain an insurance policy.

[0007] Thirdly, embodiments of this application also provide an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the insurance product meta-attribute management method described in the first aspect above.

[0008] Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for performing the insurance product meta-attribute management method as described in the first aspect above.

[0009] The insurance product meta-attribute management method according to the embodiments provided in this application has at least the following beneficial effects: In the process of managing insurance product meta-attributes, firstly, an insurance product meta-attribute set is obtained, wherein the insurance product meta-attribute set includes multiple insurance product meta-attributes; then, each insurance product meta-attribute in the set is traversed to obtain the attribute name, attribute type, attribute rule, and attribute identifier; next, an attribute configuration dictionary is generated based on the attribute name, attribute type, attribute rule, and attribute identifier; then, component mapping is performed based on the attribute configuration dictionary to obtain the policy component, and rule injection is performed based on the attribute configuration dictionary to obtain the policy rule; finally, data formatting is performed based on the policy component, policy rule, and received user parameters to obtain the corresponding insurance policy. Through the above technical solution, the traditional static attribute design can be broken through, supporting the dynamic addition, modification, and deletion of meta-attributes without code adjustments, improving flexibility and response speed, shortening the development cycle, and reducing maintenance costs. Attached Figure Description

[0010] The accompanying drawings are used to provide a further understanding of the technical solutions of this application and constitute a part of the specification. They are used together with the embodiments of this application to explain the technical solutions of this application and do not constitute a limitation on the technical solutions of this application.

[0011] Figure 1 This is a flowchart illustrating an embodiment of the method for managing the meta-attributes of an insurance product provided in this application; Figure 2 yes Figure 1 A schematic diagram of a specific implementation method of step S200; Figure 3 yes Figure 1 A schematic diagram of a specific implementation of step S300; Figure 4 yes Figure 1 A schematic diagram of a specific implementation of step S400; Figure 5 yes Figure 1 A flowchart illustrating another specific implementation of step S400; Figure 6 Is it completed? Figure 1 A flowchart illustrating a specific implementation method following step S500; Figure 7 Is it completed? Figure 1 A flowchart illustrating another specific implementation method following step S500; Figure 8 This is a schematic diagram of an insurance product meta-attribute management device provided in one embodiment of this application; Figure 9 This is a schematic diagram of an electronic device provided in one embodiment of this application. Detailed Implementation

[0012] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

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

[0014] It should be noted that, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0015] The embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence (AI) refers to the theories, methods, technologies, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0016] AI is a new technical science that studies and develops theories, methods, technologies, and application systems for simulating, extending, and expanding human intelligence. Artificial intelligence is a branch of computer science that attempts to understand the essence of intelligence and produce new intelligent machines that can react in a way similar to human intelligence. Research in this field includes robotics, speech recognition, image recognition, natural language processing, and expert systems. Artificial intelligence can simulate the information processes of human consciousness and thought. Furthermore, artificial intelligence utilizes digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceiving the environment, acquiring knowledge, and using that knowledge to achieve optimal results—the theories, methods, technologies, and application systems available for use.

[0017] Foundational technologies for artificial intelligence generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interactive systems, and mechatronics. AI software technologies mainly encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0018] Artificial intelligence, or AI, is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0019] The servers involved in artificial intelligence technology can be standalone servers or cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0020] This application provides a method, apparatus, electronic device, and computer-readable storage medium for managing the meta-attributes of insurance products. In the process of managing the meta-attributes of insurance products, firstly, a set of meta-attributes of insurance products is obtained, which includes multiple meta-attributes. Then, each meta-attribute in the set is traversed to obtain its attribute name, attribute type, attribute rule, and attribute identifier. Next, an attribute configuration dictionary is generated based on the attribute name, attribute type, attribute rule, and attribute identifier. Then, component mapping is performed based on the attribute configuration dictionary to obtain a policy component, and rule injection is performed based on the attribute configuration dictionary to obtain policy rules. Finally, data formatting is performed based on the policy component, policy rules, and received user parameters to obtain the corresponding insurance policy. This technical solution overcomes the limitations of traditional static attribute design, supports dynamic addition, modification, and deletion of meta-attributes without code adjustments, improves flexibility and response speed, shortens the development cycle, and reduces maintenance costs.

[0021] The method for managing the metadata attributes of insurance products provided in this application relates to the field of data management technology. This method can be applied to a terminal, a server, or software running on either a terminal or a server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, etc.; the server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0022] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: 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, and distributed computing environments including any of the above systems or devices. This 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. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0023] It should be noted that in all specific embodiments of this application, when processing data related to user identity or characteristics, such as user information, user behavior data, user historical data, and user location information, user permission or consent is obtained first. Furthermore, the collection, use, and processing of this data comply with relevant laws, regulations, and standards. In addition, when embodiments of this application require access to sensitive personal information of users, separate permission or consent from the user is obtained through pop-ups or redirection to confirmation pages. Only after obtaining the user's separate permission or consent is the necessary user-related data required for the proper functioning of these embodiments acquired.

[0024] The embodiments of this application will be further described below with reference to the accompanying drawings.

[0025] like Figure 1 As shown, Figure 1 This is a flowchart illustrating an embodiment of an insurance product metadata management method provided in this application. The insurance product metadata management method includes the following steps: Step S100: Obtain the set of insurance product meta-attributes, wherein the set of insurance product meta-attributes includes multiple insurance product meta-attributes.

[0026] The insurance product meta-attribute management method provided in this application first obtains a set of insurance product meta-attributes during the management process. This set includes multiple insurance product meta-attributes, providing a data foundation for subsequent meta-attribute management. After obtaining the set, each meta-attribute is iterated through to obtain its name, type, rule, and identifier, thus preparing for subsequent meta-attribute management.

[0027] It is worth noting that meta-attributes are the meta-attributes that allow administrators to dynamically define insurance products. Meta-attributes include attribute name, type, description, and rules. During the process of meta-attribute changes, dynamic addition, modification, and deletion of meta-attributes are supported, and the changed attributes can take effect in real time without redeploying the system.

[0028] It is worth noting that the set of core attributes of an insurance product includes multiple core attributes. For example, in medical and health insurance, core attributes may include basic product attributes, coverage attributes, underwriting rules attributes, premium and term attributes, medical-specific attributes, and risk control and compliance attributes; in life insurance, core attributes may include basic product attributes, coverage attributes, underwriting rules attributes, premium and term attributes, cash value and account attributes, policy maintenance and functional attributes, and risk control and compliance attributes; in property insurance, core attributes may include basic product attributes, insured object attributes, coverage attributes, premium and term attributes, underwriting and underwriting rules, claims service attributes, and risk control and compliance attributes.

[0029] It is worth noting that relevant laws, regulations, and standards are followed in the process of obtaining the set of meta-attributes of insurance products. Furthermore, when this application embodiment needs to obtain sensitive personal information of users, it will obtain the user's individual permission or consent through pop-ups or redirection to a confirmation page. Only after explicitly obtaining the user's individual permission or consent will it obtain the necessary user-related data required for the normal operation of this application embodiment.

[0030] Step S200: Iterate through each insurance product meta-attribute in the set of insurance product meta-attributes to obtain the attribute name, attribute type, attribute rule, and attribute identifier.

[0031] The insurance product meta-attribute management method provided in this application involves obtaining a set of insurance product meta-attributes, which includes multiple insurance product meta-attributes. Then, each insurance product meta-attribute in the set can be traversed to obtain the attribute name, attribute type, attribute rule, and attribute identifier. Subsequently, an attribute configuration dictionary can be generated based on the attribute name, attribute type, attribute rule, and attribute identifier to prepare for the subsequent generation of insurance policies.

[0032] It is worth noting that the set of meta-attributes for insurance products includes multiple meta-attributes. By iterating through each meta-attribute in this set, we can obtain the attribute name, attribute type, attribute rule, and attribute identifier. For example, in healthcare insurance, the attribute name can include product class, liability class, rule class, and management class; the attribute type can include enumeration, string, numeric, Boolean, date, and composite types; the attribute rule can include mandatory rules, range rules, linkage rules, format rules, calculation rules, and regulatory rules; and the attribute identifier can include system fields, coding rules, business identifiers, and rule identifiers. These meta-attributes collectively constitute the digital configuration foundation for healthcare insurance products, supporting intelligent underwriting, dynamic pricing, and automated claims processing.

[0033] It is worth noting that in the process of traversing each insurance product meta-attribute in the set of insurance product meta-attributes to obtain the attribute name, attribute type, attribute rule, and attribute identifier, the process first involves identifying each insurance product meta-attribute to obtain its attribute identifier. Then, matching the attribute identifier with a pre-defined historical attribute database determines the attribute name and its corresponding attribute type. Finally, the corresponding attribute rule is loaded from a pre-defined historical attribute rule database based on the attribute type. This technical solution enables more convenient and accurate traversal of insurance product meta-attributes using both historical attribute and historical attribute rule databases.

[0034] like Figure 2 As shown, iterating through each insurance product meta-attribute in the set of insurance product meta-attributes to obtain the attribute name, attribute type, attribute rule, and attribute identifier can include the following steps: Step S210: Perform identity identification processing on each insurance product meta-attribute in the insurance product meta-attribute set to obtain the attribute identifier; Step S220: Match the attribute identifier with the preset historical attribute database to determine the attribute name and the attribute type corresponding to the attribute name; Step S230: Load attribute rules from the preset historical attribute rule database according to the attribute type.

[0035] For steps S210 to S230, in the process of traversing each insurance product meta-attribute in the insurance product meta-attribute set to obtain the attribute name, attribute type, attribute rule, and attribute identifier, firstly, each insurance product meta-attribute in the set undergoes an identification process to obtain the attribute identifier; then, the attribute identifier is matched with a pre-defined historical attribute database to determine the attribute name and the corresponding attribute type; finally, the corresponding attribute rule is loaded from a pre-defined historical attribute rule database based on the attribute type. Through this technical solution, the traversal of insurance product meta-attributes can be performed using a historical attribute database and a historical attribute rule database, making the traversal of insurance product meta-attributes more convenient and accurate.

[0036] It is worth noting that in the process of traversing the meta-attributes of an insurance product, the first step is to identify each meta-attribute in the set of insurance product meta-attributes to obtain an attribute identifier. Then, the attribute identifier is matched with a pre-defined historical attribute database to determine the attribute name and attribute type, where the attribute name and attribute type correspond one-to-one. Finally, the corresponding attribute rules can be loaded from a pre-defined historical attribute rule database based on the attribute type. Through the above technical solution, the traversal of insurance product meta-attributes can be made simpler and more accurate.

[0037] It is worth noting that the historical attribute database includes multiple attribute names, each corresponding to a unique attribute identifier. Therefore, based on the attribute identifier, the attribute name and attribute type can be determined from the historical attribute database. Subsequently, the corresponding attribute rules can be directly loaded from the pre-defined historical attribute rule database using the attribute type. Among these, meta-attributes are the core basic data fields of insurance products and represent the essential definition of attributes; meta-attribute configuration is a set of management parameters for meta-attributes, which are the management rules for meta-attributes; and meta-attribute rules are the business logic constraints of meta-attributes and the business application rules for meta-attributes. The meta-attribute rules adopt a structured configuration of "condition-action" (e.g., condition: insured age > 50 years old; action: premium increase of 20%), supporting numerical comparison, enumeration matching, and logical operations (AND / OR / NOT). The calculation logic is dynamically adjusted (taking premium calculation as an example): a preset basic calculation template: premium = basic premium × adjustment coefficient; meta-attribute rules are associated with adjustment coefficients: meta-attributes such as "age, occupation, and sum insured" are bound to adjustment coefficients (e.g., occupation is "high-altitude work" → coefficient 1.5); real-time calculation: after the user fills in the insurance information, the rule engine parses the meta-attribute rules, matches the corresponding adjustment coefficients, and substitutes them into the template to calculate the final premium. Underwriting rules are dynamically adjusted: underwriting rules are configured according to meta-attribute categories (e.g., age rules, health declaration rules, occupation rules); the rule engine executes according to priority: first verifying basic rules (e.g., whether the age is met), then verifying advanced rules (e.g., whether the health declaration meets the standards); result feedback: after triggering a rule, a preset conclusion is returned (e.g., "can be insured normally," "requires manual underwriting," "rejected"), and the "reason for rejection" field in the meta-attribute is displayed.

[0038] Step S300: Generate an attribute configuration dictionary based on the attribute name, attribute type, attribute rule, and attribute identifier.

[0039] The insurance product meta-attribute management method provided in this application, after traversing each insurance product meta-attribute in the insurance product meta-attribute set to obtain the attribute name, attribute type, attribute rule, and attribute identifier, can generate an attribute configuration dictionary based on the attribute name, attribute type, attribute rule, and attribute identifier, in preparation for the subsequent generation of insurance policies.

[0040] It is worth noting that in the process of generating an attribute configuration dictionary based on attribute name, attribute type, attribute rule, and attribute identifier, the data format of the attribute name, attribute type, attribute rule, and attribute identifier is first converted. This yields name conversion information for the attribute name, type conversion information for the attribute type, rule conversion information for the attribute rule, and identifier conversion information for the attribute identifier. Then, mapping is performed based on the name conversion information, type conversion information, and identifier conversion information to obtain the corresponding dictionary structure. Finally, rule compilation is performed on the dictionary structure based on the rule conversion information to obtain the final attribute configuration dictionary. This technical solution makes the construction of the attribute configuration dictionary more convenient, faster, and more reliable.

[0041] like Figure 3 As shown, generating an attribute configuration dictionary based on attribute name, attribute type, attribute rule, and attribute identifier can include the following steps: Step S310: Perform data format conversion processing on attribute name, attribute type, attribute rule and attribute identifier to obtain name conversion information corresponding to attribute name, type conversion information corresponding to attribute type, rule conversion information corresponding to attribute rule and identifier conversion information corresponding to attribute identifier; Step S320: Perform mapping processing based on name conversion information, type conversion information, and identifier conversion information to obtain the dictionary schema; Step S330: Based on the rule transformation information, perform rule compilation processing on the dictionary architecture to obtain the attribute configuration dictionary.

[0042] For steps S310 to S330, in the process of generating the attribute configuration dictionary based on the attribute name, attribute type, attribute rule, and attribute identifier, the data format conversion processing of the attribute name, attribute type, attribute rule, and attribute identifier is first performed to obtain name conversion information corresponding to the attribute name, type conversion information corresponding to the attribute type, rule conversion information corresponding to the attribute rule, and identifier conversion information corresponding to the attribute identifier. Then, the corresponding dictionary structure can be obtained by mapping the name conversion information, type conversion information, and identifier conversion information. Finally, the dictionary structure can be compiled based on the rule conversion information to obtain the final attribute configuration dictionary. Through the above technical solution, the construction of the attribute configuration dictionary can be made more convenient, faster, and more reliable.

[0043] It is worth noting that in the process of generating the attribute configuration dictionary based on attribute name, attribute type, attribute rule, and attribute identifier, the attribute name, attribute type, attribute rule, and attribute identifier first need to be format-converted to ensure that the data format of the attribute name, attribute type, attribute rule, and attribute identifier is unified. After the data format conversion, mapping can be performed based on the name conversion information, type conversion information, and identifier conversion information to obtain the dictionary structure. Finally, rule compilation processing is performed on the dictionary structure based on the rule conversion information to obtain the corresponding attribute configuration dictionary.

[0044] Step S400: Perform component mapping processing based on the attribute configuration dictionary to obtain the policy component; and perform rule injection processing based on the attribute configuration dictionary to obtain the policy rules.

[0045] The insurance product meta-attribute management method provided in this application traverses each insurance product meta-attribute in the insurance product meta-attribute set to obtain the attribute name, attribute type, attribute rule, and attribute identifier. After generating an attribute configuration dictionary based on the attribute name, attribute type, attribute rule, and attribute identifier, the method can perform component mapping based on the attribute configuration dictionary to obtain policy components, and perform rule injection based on the attribute configuration dictionary to obtain policy rules, thus preparing for the subsequent construction of insurance policies.

[0046] It is worth noting that in the process of obtaining policy components through component mapping based on the attribute configuration dictionary, the component template is loaded according to the attribute configuration dictionary; then, the component template is instantiated according to the attribute name, attribute type, and attribute identifier to obtain the corresponding policy component. This technical solution makes the determination of policy components more accurate. Furthermore, in the process of obtaining policy rules through rule injection based on the attribute configuration dictionary, the enumeration rules, format rules, and association rules are first determined from the attribute configuration dictionary based on the attribute rules; finally, the enumeration rules, format rules, and association rules are integrated to obtain the corresponding policy rules. This technical solution makes the determination of policy rules simpler and faster.

[0047] like Figure 4 As shown, the policy component is obtained by mapping components based on the attribute configuration dictionary, which may include the following steps: Step S410: Load the component template according to the attribute configuration dictionary; Step S420: Instantiate the component template according to the attribute name, attribute type and attribute identifier to obtain the policy component.

[0048] For steps S410 to S420, in the process of obtaining the policy component by performing component mapping processing based on the attribute configuration dictionary, the component template is loaded according to the attribute configuration dictionary; then, the component template is instantiated according to the attribute name, attribute type and attribute identifier to obtain the corresponding policy component. Through the above technical solution, the determination of the policy component can be more accurate.

[0049] It is worth noting that during the process of determining the policy component, the component template can be loaded according to the attribute configuration dictionary. The component template is a pre-defined template used to present the component. Subsequently, the component template can be instantiated according to the attribute name, attribute type and attribute identifier, and the corresponding policy component can be obtained, which is to prepare for the subsequent construction of insurance policies.

[0050] like Figure 5 As shown, rule injection based on the attribute configuration dictionary yields policy rules, which may include the following steps: Step S430: Determine the enumeration rules, format rules, and association rules from the attribute configuration dictionary according to the attribute rules; Step S440: Integrate the enumeration rules, format rules, and association rules to obtain the policy rules.

[0051] For steps S430 to S440, in the process of obtaining policy rules by rule injection based on the attribute configuration dictionary, firstly, enumeration rules, format rules, and association rules are determined from the attribute configuration dictionary based on the attribute rules. Finally, the enumeration rules, format rules, and association rules are integrated to obtain the corresponding policy rules. Through the above technical solution, the determination of policy rules can be made simpler and faster.

[0052] It is worth noting that enumeration rules can generate a drop-down list of options by parsing the list of enumeration values ​​in the rules; formatting rules can bind input validation according to the regular expressions in the rules (such as mobile phone number, ID card number); association rules can establish associations through the parent node identifier key and inject display control logic if there are dependencies between attributes (such as "whether or not there is social security" determines the visibility of the subsequent "social security type" field).

[0053] Step S500: Perform data formatting processing based on the policy components, policy rules, and received user parameters to obtain the insurance policy.

[0054] The insurance product meta-attribute management method provided in this application generates an attribute configuration dictionary based on attribute name, attribute type, attribute rule, and attribute identifier; performs component mapping processing based on the attribute configuration dictionary to obtain a policy component; and performs rule injection processing based on the attribute configuration dictionary to obtain policy rules. After that, data formatting processing can be performed based on the policy component, policy rules, and received user parameters to obtain the corresponding insurance policy, making the generation of insurance policies simpler and faster.

[0055] It is worth noting that after the user inputs relevant user parameters, the data format is converted according to the attribute type to generate standardized form data. The standardized form data is a lightweight data exchange format used for subsequent calculations and storage.

[0056] It is worth noting that the embodiments of this application add configuration conflict detection (such as duplicate attribute names and dependency loop verification) and support configuration version management (saving historical versions and supporting rollback), which can effectively avoid system abnormalities caused by configuration errors and make configuration changes traceable.

[0057] like Figure 6 As shown, after formatting the data according to the policy components, policy rules, and received user parameters to obtain the insurance policy, the following steps may also be included: Step S610: Perform meta-attribute classification mapping on the insurance policy to obtain text-type attributes, rich text attributes, and interactive attributes; Step S620: Dynamically render the preset page template according to the text type attributes, rich text attributes, and interactive type attributes to obtain the insurance product details page.

[0058] For steps S610 to S620, after obtaining the insurance application policy by formatting data according to the policy component, policy rules, and received user parameters, the insurance application policy can be processed by meta-attribute classification mapping to obtain text attributes, rich text attributes, and interactive attributes. Subsequently, the preset page template can be dynamically rendered according to the text attributes, rich text attributes, and interactive attributes, thereby easily and quickly obtaining the insurance product details page, making the generation of the insurance product details page simpler and faster.

[0059] Specifically, the pre-defined details page template defines a fixed layout (e.g., product header, core coverage area, attribute description area, and application entry), and reserves placeholders for dynamic attribute rendering. Meta-attribute classification mapping categorizes meta-attributes according to business scenarios (e.g., basic attributes: sum assured / premium / coverage period; coverage liability attributes: payout ratio / exclusion clauses; rule attributes: age limit for application) and binds them to template placeholders. Dynamic rendering logic: text-based attributes (e.g., sum assured, coverage period) directly fill placeholders and are displayed according to the format requirements in the rules (e.g., "500,000 yuan" "30 years"); rich text attributes (e.g., product description, exclusion clauses) are rendered after parsing Hypertext Markup Language tags; interactive attributes (e.g., premium calculation entry) are bound to meta-attribute rules, triggering the calculation logic upon clicking and displaying the results in real time; style adaptation: CSS variables are used to associate the "display style" configuration (e.g., color, icon) in the meta-attributes to achieve style differentiation for different products.

[0060] In this embodiment, meta-attributes serve as the data hub, forming a closed loop of "display-input-calculation-validation". The product details page displays the "static information" of meta-attributes (such as the sum insured and coverage), guiding users to the application form; the application form collects the "dynamic information" (such as age and occupation) input by the user, simultaneously triggering the calculation logic; the calculation logic, based on meta-attribute rules, generates results (such as premium) according to the form input and displays them back on the form; the underwriting rules validate the form input against meta-attribute constraints (such as whether the age exceeds the limit), deciding whether to allow the application to be submitted; the display format is not a single page, but a process-oriented linked page; the product details page (independent page): displays static attributes and the application entry point; the application form (independent page / pop-up): inputs dynamic information and displays the calculation results (such as premium) in real time; the underwriting result page (redirected after form submission): displays the underwriting conclusion and associates the meta-attribute rule explanation (such as "rejected due to age over 60").

[0061] It is worth noting that this application's embodiments introduce a component library and custom style configuration (supporting custom colors and layouts for different products), adapting to responsive rendering on mobile / PC devices. Based on the above settings, product page styles are differentiated, adapting to multiple terminals and reducing development costs. Furthermore, this application can improve synchronization reliability, quickly locating the root cause if data inconsistency occurs; and its permission control is more precise, security auditing is more comprehensive, and compliance requirements are met.

[0062] like Figure 7 As shown, after formatting the data according to the policy components, policy rules, and received user parameters to obtain the insurance policy, the following steps may also be included: Step S630: Perform meta-attribute classification processing on the insurance application policy according to the preset underwriting rules to obtain the policy underwriting terms; Step S640: Verify the policy underwriting conditions according to the underwriting rules to obtain the policy underwriting result.

[0063] For steps S630 to S640, after data formatting processing based on the policy components, policy rules, and received user parameters to obtain the insurance application policy, the policy application policy can be classified according to pre-set underwriting rules to obtain the policy underwriting terms. Then, the policy underwriting conditions are verified according to the underwriting rules to obtain the corresponding policy underwriting result. This technical solution makes underwriting simpler and more reliable.

[0064] It is worth noting that the underwriting rules are dynamically adjusted: the underwriting rules are configured according to the meta-attribute categories (such as age rules, health declaration rules, occupation rules); the rule engine executes according to priority: first, it checks the basic rules (such as whether the age is met), and then checks the advanced rules (such as whether the health declaration meets the standards); the result feedback: after the rule is triggered, a preset conclusion is returned (such as "can be insured normally", "requires manual underwriting", "rejected"), and the "reason for rejection" field in the meta-attribute is displayed.

[0065] Furthermore, in the process of managing the meta-attributes of insurance products, it is first necessary to clarify the business scenario (such as supported insurance types and upstream and downstream system interfaces) and design the system architecture (rule engine, message queue, permission module, rendering module). Define the meta-attribute table (stores core meta-attribute information), meta-attribute configuration table (stores management parameters), meta-attribute rule table (stores business rules), permission table, and audit log table. Core module development: Meta-attribute management module: develop attribute CRUD (Create, Read, Update, Delete) functionality, version management, and conflict detection functionality; Rule engine module: develop rule parsing, condition matching, and logic execution functionality; Page rendering module: develop form / detail page templates, attribute category mapping, and dynamic rendering functionality; Data synchronization module: integrate message queue and develop real-time / batch synchronization, retry, and reconciliation functionality; Permission module: develop role definition, permission allocation, and audit log recording functionality. Interface development and integration testing: integrate with upstream and downstream systems (such as underwriting and payment systems) to verify the accuracy of data synchronization. Testing Phase: Unit Testing: Testing core algorithms (e.g., form generation, premium calculation); Integration Testing: Testing inter-module linkage (e.g., attribute change → page synchronization → data synchronization); Stress Testing: Verifying the stability of message queue synchronization under high concurrency; Compliance Testing: Verifying that access control and audit logs meet regulatory requirements. Deployment and Launch: Adopting a canary release approach, first launching a subset of products to verify functionality, and then releasing to the full rollout after confirming no issues. Operations and Iteration: Monitoring system operation status (synchronization success rate, page rendering speed), collecting business feedback, and iteratively optimizing functionality (e.g., adding new meta-attribute types, expanding the scope of rule support).

[0066] In addition, such as Figure 8 As shown, one embodiment of this application also provides an insurance product meta-attribute management device 10, the device comprising: The acquisition unit 100 is used to acquire the set of insurance product meta-attributes, wherein the set of insurance product meta-attributes includes multiple insurance product meta-attributes; Traversal unit 200 is used to traverse each insurance product meta-attribute in the set of insurance product meta-attributes to obtain the attribute name, attribute type, attribute rule and attribute identifier; Building unit 300 is used to generate an attribute configuration dictionary based on attribute name, attribute type, attribute rule, and attribute identifier; Execution unit 400 is used to perform component mapping processing based on the attribute configuration dictionary to obtain the policy component; and to perform rule injection processing based on the attribute configuration dictionary to obtain the policy rule. The conversion unit 500 is used to perform data formatting processing based on the policy components, policy rules and received user parameters to obtain the insurance policy.

[0067] The specific implementation of the insurance product element attribute management device 10 is basically the same as the specific implementation of the above-mentioned insurance product element attribute management method, and will not be repeated here.

[0068] In addition, such as Figure 9 As shown, one embodiment of this application also provides an electronic device 700, which includes: a memory 720, a processor 710, and a computer program stored on the memory 720 and executable on the processor 710.

[0069] The processor 710 and memory 720 can be connected via a bus or other means.

[0070] The non-transient software program and instructions required to implement the insurance product meta-attribute management method of the above embodiments are stored in the memory 720. When executed by the processor 710, the insurance product meta-attribute management method of the above embodiments is executed.

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

[0072] Furthermore, one embodiment of this application provides a computer-readable storage medium storing computer-executable instructions that are executed by a processor 710 or a controller, for example, by a processor 710 in the above-described device embodiment, enabling the processor 710 to execute the insurance product meta-attribute management method in the above-described embodiment.

[0073] The above embodiments can be used in combination, and modules with the same name in different embodiments may be the same or different.

[0074] The foregoing has described specific embodiments of this application; other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims may be performed in a different order than those shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily have to follow the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0075] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and computer-readable storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0076] The apparatus, device, computer-readable storage medium and method provided in the embodiments of this application are corresponding. Therefore, the apparatus, device and non-volatile computer storage medium also have similar beneficial technical effects as the corresponding method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the corresponding apparatus, device and computer storage medium will not be described again here.

[0077] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used when writing program development code. The original code before compilation must also be written in a specific programming language, which is called a Hardware Description Language (HDL). There is not just one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using the aforementioned hardware description languages ​​and programming it into an integrated circuit, the hardware circuit that implements the logic method flow can be easily obtained.

[0078] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0079] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0080] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, in implementing the embodiments of this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0081] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0082] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0083] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0084] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0085] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0086] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0087] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0088] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0089] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, A and B simultaneously, or B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0090] The embodiments of this application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The embodiments of this application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules can reside in local and remote computer storage media, including storage devices.

[0091] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0092] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of this application should be included within the scope of the claims of this application.

Claims

1. A method for managing the meta-attributes of insurance products, characterized in that, include: Obtain the set of meta-attributes of insurance products, wherein the set of meta-attributes of insurance products includes multiple meta-attributes of insurance products; Each of the insurance product meta-attributes in the set of insurance product meta-attributes is traversed to obtain the attribute name, attribute type, attribute rule, and attribute identifier; Generate an attribute configuration dictionary based on the attribute name, the attribute type, the attribute rule, and the attribute identifier; The component mapping process is performed based on the attribute configuration dictionary to obtain the policy component; and the rule injection process is performed based on the attribute configuration dictionary to obtain the policy rule. The insurance policy is obtained by formatting data based on the policy component, the policy rules, and the received user parameters.

2. The method for managing the meta-attributes of insurance products according to claim 1, characterized in that, The process of traversing each of the insurance product meta-attributes in the set of insurance product meta-attributes to obtain the attribute name, attribute type, attribute rule, and attribute identifier includes: Each of the insurance product meta-attributes in the set of insurance product meta-attributes is subjected to identity identification processing to obtain the attribute identifier; The attribute identifier is matched with a preset historical attribute database to determine the attribute name and the attribute type corresponding to the attribute name; The attribute rules are loaded from a preset historical attribute rule database based on the attribute type.

3. The method for managing the meta-attributes of insurance products according to claim 1, characterized in that, The step of generating an attribute configuration dictionary based on the attribute name, the attribute type, the attribute rule, and the attribute identifier includes: The attribute name, attribute type, attribute rule, and attribute identifier are subjected to data format conversion processing to obtain name conversion information corresponding to the attribute name, type conversion information corresponding to the attribute type, rule conversion information corresponding to the attribute rule, and identifier conversion information corresponding to the attribute identifier. Based on the name conversion information, the type conversion information, and the identifier conversion information, a mapping process is performed to obtain the dictionary structure; The dictionary architecture is compiled based on the rule transformation information to obtain the attribute configuration dictionary.

4. The method for managing the meta-attributes of insurance products according to claim 1, characterized in that, The step of configuring the component mapping based on the attribute dictionary to obtain the policy component includes: Configure the dictionary to load the component template based on the aforementioned attributes; The component template is instantiated based on the attribute name, the attribute type, and the attribute identifier to obtain the policy component.

5. The method for managing the meta-attributes of insurance products according to claim 1, characterized in that, The rule injection process based on the attribute configuration dictionary to obtain policy rules includes: Based on the attribute rules, enumeration rules, format rules, and association rules are determined from the attribute configuration dictionary; The enumeration rules, format rules, and association rules are integrated to obtain the policy rules.

6. The method for managing the meta-attributes of insurance products according to claim 1, characterized in that, After performing data formatting processing based on the policy component, the policy rules, and the received user parameters to obtain the insurance policy, the method further includes: The insurance policy is subjected to meta-attribute classification mapping to obtain text-type attributes, rich text attributes, and interactive attributes; The preset page template is dynamically rendered based on the text attributes, rich text attributes, and interactive attributes to obtain the insurance product details page.

7. The method for managing the meta-attributes of insurance products according to claim 1, characterized in that, After performing data formatting processing based on the policy component, the policy rules, and the received user parameters to obtain the insurance policy, the method further includes: The insurance application is classified into meta-attributes according to the preset underwriting rules to obtain the policy underwriting terms; The policy underwriting conditions are verified according to the underwriting rules to obtain the policy underwriting result.

8. A device for managing the element attributes of an insurance product, characterized in that, The device includes: The acquisition unit is used to acquire a set of insurance product meta-attributes, wherein the set of insurance product meta-attributes includes multiple insurance product meta-attributes; The traversal unit is used to traverse each of the insurance product meta-attributes in the set of insurance product meta-attributes to obtain the attribute name, attribute type, attribute rule and attribute identifier; The construction unit is used to generate an attribute configuration dictionary based on the attribute name, the attribute type, the attribute rule, and the attribute identifier; An execution unit is configured to perform component mapping processing based on the attribute configuration dictionary to obtain a policy component; and to perform rule injection processing based on the attribute configuration dictionary to obtain policy rules. The conversion unit is used to perform data formatting processing based on the policy component, the policy rules, and the received user parameters to obtain an insurance policy.

9. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the processor executes the computer program, it implements the insurance product meta-attribute management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are used to execute the insurance product meta-attribute management method according to any one of claims 1 to 7.

Images