Insurance product generation method and device

Abstract

The invention provides an insurance product generation method and device, and the method comprises the steps: obtaining a target entity relation model in response to a received insurance product generation request sent by a target object; determining an entity relationship sub-model matched with the product demand in the insurance product generation request from the target entity relationship model; in response to the selection operation, selecting target entity data associated with at least one specified entity in the entity relationship sub-model from the configuration data; and generating the target insurance product according to the entity relationship sub-model and the target entity data associated with the at least one specified entity, thereby realizing decoupling between the product definition and the entity data configuration, reducing the workload of repeated development, effectively reducing the development complexity and cost, and improving the development efficiency. And meanwhile, the flexibility and accuracy of insurance product generation are improved.

Description

Technical Field

[0001] The present disclosure relates to the field of insurance technologies, and in particular, to a method and apparatus for generating insurance products. Background Art

[0002] With the rapid development of the global economy and the continuous enhancement of people's risk awareness, the insurance industry has gradually become an indispensable part of the modern financial system. The design and generation of insurance products not only relate to the competitiveness and profitability of insurance companies themselves, but also directly affect whether the risk protection needs of customers can be effectively met. Therefore, how to generate insurance products efficiently and accurately is very important. Summary of the Invention

[0003] The present disclosure provides a method and apparatus for generating insurance products to at least solve one of the technical problems in the related art to some extent. The technical solutions of the present disclosure are as follows:

[0004] According to a first aspect of an embodiment of the present disclosure, there is provided a method for generating an insurance product, including: in response to receiving an insurance product generation request sent by a target object, obtaining a target entity relationship model; wherein the target entity relationship model is used to indicate the data structures of multiple insurance products; determining, from the target entity relationship model, an entity relationship sub-model that matches the product requirements in the insurance product generation request; in response to a selection operation, selecting target entity data associated with at least one specified entity in the entity relationship sub-model from configuration data; and generating the target insurance product according to the entity relationship sub-model and the target entity data associated with the at least one specified entity.

[0005] According to a second aspect of an embodiment of the present disclosure, there is provided an apparatus for generating an insurance product, including: a first obtaining module, configured to obtain a target entity relationship model in response to receiving an insurance product generation request sent by a target object; wherein the target entity relationship model is used to indicate the data structures of multiple insurance products; a first determining module, configured to determine, from the target entity relationship model, an entity relationship sub-model that matches the product requirements in the insurance product generation request; a selection module, configured to select target entity data associated with at least one specified entity in the entity relationship sub-model from configuration data in response to a selection operation; and a generation module, configured to generate the target insurance product according to the entity relationship sub-model and the target entity data associated with the at least one specified entity.

[0006] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, including: a processor; a memory for storing executable instructions of the processor; wherein the processor is configured to execute the instructions to implement the method for generating an insurance product as described in the first aspect embodiment of the present disclosure.

[0007] According to a fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, which, when the instructions stored therein are executed by a processor of an electronic device, enables the electronic device to execute the method for generating an insurance product as described in the first aspect of the embodiments of the present disclosure.

[0008] According to a fifth aspect of the embodiments of the present disclosure, there is provided a computer program product, including: a computer program, which, when executed by a processor, implements the method for generating an insurance product as described in the first aspect of the embodiments of the present disclosure.

[0009] The technical solutions provided by the embodiments of the present disclosure at least bring the following beneficial effects:

[0010] In this technical solution, by screening the entity relationship sub-model that matches the product requirements from the target entity relationship model, it is ensured that the generated insurance product is highly consistent with the actual requirements. Furthermore, according to the product requirements, the target entity data associated with the specified entity in the target entity relationship sub-model is flexibly selected from the configuration data, reducing the coupling degree between product definition and entity data configuration, improving the flexibility of insurance product generation. Finally, by combining the entity relationship sub-model and the target entity data, the target insurance product is automatically generated, which not only simplifies the insurance product design steps but also improves the automation degree of product generation. In addition, by reusing the target entity relationship model and the configuration data, the workload of repeated development is reduced, effectively reducing the development complexity and cost; among them, by determining and displaying at least one candidate entity data of any specified entity from the configuration data of any specified entity; in response to a selection operation, according to the product requirements, the target entity data of any specified entity is selected from at least one candidate entity data, realizing the decoupling of the data configuration of the specified entity and product design, and can quickly screen out the candidate entity data related to the specified entity from a large amount of configuration data, avoiding the cumbersome process of manual search and screening, thus saving a large amount of time and labor costs, improving the flexibility of insurance product generation, and meeting the user requirements at the same time.

[0011] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure, and do not constitute an improper limitation to the present disclosure.

[0013] Figure 1 is a schematic flowchart of the method for generating an insurance product shown in the first embodiment of the present disclosure;

[0014] Figure 2 It is a schematic structural diagram of a target entity model shown in an embodiment of the present disclosure;

[0015] Figure 3 It is a schematic flowchart of a method for generating an insurance product shown in the second embodiment of the present disclosure;

[0016] Figure 4 It is a schematic diagram of the principle of a specified entity definition shown in an embodiment of the present disclosure;

[0017] Figure 5 It is a schematic flowchart of a method for generating an insurance product shown in the third embodiment of the present disclosure;

[0018] Figure 6 It is a schematic structural diagram of a device for generating an insurance product shown in the fourth embodiment of the present disclosure;

[0019] Figure 7 It is a schematic structural diagram of an electronic device shown in an exemplary embodiment of the present disclosure. Detailed implementation manners

[0020] In order to enable those of ordinary skill in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0021] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of the present disclosure described herein can be implemented in an order different from those illustrated or described herein. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present disclosure. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0022] It should be noted that in the technical solutions of the present disclosure, the collection, storage, use, processing, transmission, provision, and disclosure of the user's personal information and other processes are all carried out on the premise of obtaining the user's consent, and all comply with the provisions of relevant laws and regulations and do not violate public order and good customs.

[0023] Currently, the data structure form of insurance products in the insurance company system is relatively simple. The strong coupling relationship between insurance products / protection plans and insurance types makes the reusability of insurance types problematic, and there is also a lack of expression ability for the demand for "different price copies of the same insurance type (i.e., different insured amounts and / or premiums for the same insurance type)".

[0024] In view of the above problems, the present disclosure proposes a method and device for generating an insurance product.

[0025] The method and device for generating insurance products according to the embodiments of the present disclosure will be described below with reference to the accompanying drawings.

[0026] Figure 1 FIG. is a schematic flowchart of the method for generating an insurance product shown in the first embodiment of the present disclosure. It should be noted that the execution subject of the embodiments of the present disclosure can be a device for generating insurance products, and the device for generating insurance products can be applied to any electronic device with computing capabilities, so that the electronic device can execute the function of generating insurance products.

[0027] As Figure 1 shown, the method for generating the insurance product includes the following steps:

[0028] Step 101, in response to receiving an insurance product generation request sent by a target object, obtain a target entity relationship model.

[0029] The target entity relationship model is used to indicate the data structures of multiple insurance products.

[0030] In the embodiments of the present disclosure, when receiving an insurance product generation request sent by a target object, a general entity relationship model, that is, a target entity relationship model, is obtained. The target entity relationship model is an abstract data structure used to characterize the underlying logic and data organization method of multiple insurance products; the target entity relationship model expresses the commonalities and characteristics of different insurance products in a unified form by defining entities, attributes, and entity relationships.

[0031] For example, as Figure 2 shown, the target entity model includes 5 entities, namely: insurance product, insurance subject, protection plan, insurance type, and insurance item. Among them, there are 7 entity relationships between the 5 entities. It should be noted that the combination of entities and entity relationships is distinguished and matched through the model type (ModelMode) in the insurance product in the target entity model.

[0032] Step 102, determine an entity relationship sub-model that matches the product requirements in the insurance product generation request from the target entity relationship model.

[0033] To improve the accuracy and efficiency of insurance product generation, as a possible implementation, find an entity relationship sub-model that matches the product requirements from the target entity relationship model, so as to realize the efficient customized generation of insurance products.

[0034] As an example, according to product requirements, multiple target entities that match the product requirements are determined from multiple candidate entities in the target entity relationship model, that is, the product requirements are parsed to extract key information, such as: customer type (individual / enterprise), insurance type (health insurance, property insurance, life insurance, etc.), specific protection content (such as hospitalization medical treatment, accidental injury, etc.). According to the parsed requirements, relevant entities are filtered out from the target entity relationship model. For example, if "health insurance" is mentioned in the requirements, entities related to "health insurance" are filtered out; furthermore, according to the product requirements, the entity relationships between multiple target entities are determined from the entity relationships in the target entity relationship model. Based on the multiple target entities and the entity relationships between the multiple target entities, at least one entity relationship sub-model is generated, that is, on the basis of filtering out relevant entities, an entity relationship sub-model is further constructed; it should be noted that the entity relationship sub-model is a subset of the target entity relationship model.

[0035] Step 103, in response to the selection operation, select target entity data associated with at least one specified entity in the entity relationship sub-model from the configuration data.

[0036] In order to improve the flexibility and accuracy of insurance product generation, in the embodiments of the present disclosure, based on the user's selection operation, target entity data associated with each specified entity in the entity relationship sub-model is selected from the pre-configured configuration data.

[0037] For example, the specified entities in the entity relationship sub-model include insurance types, insurance items, and insurance objects. The configuration data includes attribute information of each insurance type (such as, health insurance, auto insurance, property insurance, etc.) (such as, insured amount, premium, etc.), attribute information of insurance items adapted to each insurance type (such as, in health insurance, the "hospitalization medical treatment" insurance item may include attributes such as daily subsidy amount, annual compensation limit, etc.), and attribute information of insurance objects (such as, health, vehicle), etc.

[0038] Step 104, generate a target insurance product according to the entity relationship sub-model and the target entity data associated with at least one specified entity.

[0039] In order to improve the efficiency of insurance product generation, in the embodiments of the present disclosure, the structure of the entity relationship sub-model is combined with the content of the target entity data to generate a complete insurance product.

[0040] In summary, by screening the entity relationship sub-model that matches the product requirements from the target entity relationship model, it is ensured that the generated insurance product is highly consistent with the actual requirements. Furthermore, according to the product requirements, the target entity data associated with the specified entity in the target entity relationship sub-model is flexibly selected from the configuration data, reducing the coupling degree between product definition and entity data configuration, improving the flexibility of insurance product generation. Finally, by combining the entity relationship sub-model and the target entity data, the target insurance product is automatically generated, which not only simplifies the insurance product design steps but also improves the automation degree of insurance product generation. In addition, by reusing the target entity relationship model and configuration data, the workload of repeated development is reduced, effectively reducing the development complexity and cost.

[0041] To clearly illustrate how the above embodiments select the target entity data associated with at least one specified entity in the entity relationship sub-model from the configuration data in response to a selection operation, the present disclosure proposes another method for generating an insurance product.

[0042] Figure 3 It is a schematic flowchart of the method for generating an insurance product shown in the second embodiment of the present disclosure.

[0043] As Figure 3 shown, the method for generating an insurance product includes the following steps:

[0044] Step 301, in response to receiving an insurance product generation request sent by a target object, obtain a target entity relationship model.

[0045] Wherein, the target entity relationship model is used to indicate the data structures of multiple insurance products.

[0046] Step 302, determine an entity relationship sub-model that matches the product requirements in the insurance product generation request from the target entity relationship model.

[0047] Step 303, for any specified entity, determine and display at least one candidate entity data associated with the any specified entity from the configuration data of the any specified entity.

[0048] To improve the flexibility of insurance product generation, as a possible implementation manner, according to the product requirements, flexibly select the target entity data associated with the specified entity in the target entity relationship sub-model from the configuration data of the specified entity.

[0049] In the embodiments of the present disclosure, by pre - defining and configuring the entity data of each specified entity, the configuration data of each specified entity is obtained. According to the product requirements, at least one candidate entity data of each specified entity that matches the product requirements is screened and displayed from the configuration data of each specified entity, so as to reduce the coupling degree between product design and entity data definition. Among them, it should be noted that the candidate entity data is used to indicate the business attributes of the corresponding specified entity. For example, taking the specified entity as the insurance type, at least one candidate entity data associated with this insurance type may include, but is not limited to, all information related to "health insurance" (such as rate tables for different age groups, compensation ratios for various diseases, coverage scope, etc.), all information related to "accident insurance" (such as attributes of the insured subject, rate rules, compensation standards, etc.), all information related to "life insurance" (such as protection content, insurance conditions, rate rules, compensation standards, etc.), etc.

[0050] Among them, at least one candidate entity data is generated by the following steps:

[0051] 1. Obtain the business requirements associated with any specified entity;

[0052] In the embodiments of the present disclosure, the business requirements refer to the specific requirements or goals related to the specified entity, which can be determined by querying the business plans of each insurance company, or can be determined by the actual needs of users.

[0053] 2. Determine the configuration data of any specified entity according to the business requirements; among them, the configuration data is used to indicate the business attributes of any specified entity.

[0054] In the embodiments of the present disclosure, the specified entity is the core object in insurance product design, such as insurance type, insurance item or insured subject. The configuration data is a set of specific parameters or rules used to describe the business attributes of the specified entity. The configuration data clarifies the specific manifestation form of the specified entity in a certain business scenario. For example, the rate, compensation standard, applicable population, etc. of health insurance; the rate, compensation standard, compensation ratio, etc. of life insurance; the coverage scope, compensation ratio, etc. of vehicle insurance; the coverage scope, compensation standard, etc. of property insurance.

[0055] In addition, it should be noted that each designated entity can be configured with different price copies. Taking the designated entity as an insurance item as an example, as shown in Table 1, Table 1 is the configuration data of the insurance item. Elements related to the insured amount, premium rate, and premium are configured for the insurance item, and multiple price copies are configured for the insurance item (different insured amounts and / or premiums correspond to different protection contents); when generating an insurance product, at least one candidate entity data adapted to the insurance product to be generated can be determined and displayed from the configuration data of the insurance item, that is, multiple price copies to be displayed are determined from the configuration data of the insurance item. Furthermore, one (or more) of the displayed multiple price copies is selected as the price required for the current insurance product or protection plan (if multiple prices are selected, the confirmation of the final unique price occurs when generating the insurance policy). As shown in Table 2, Table 2 is the price copy of the insurance item selected for the current insurance product or protection plan, and finally, a salable insurance product or protection plan is formed.

[0056] Table 1 Configuration data of the insurance item

[0057]

[0058] Table 2 Price copy of the insurance item selected for the current insurance product or protection plan

[0059]

[0060] As an example, in response to the configuration operation, based on business requirements, business configuration is performed on any designated entity to obtain the configuration data of any designated entity.

[0061] That is to say, business configuration can be directly performed on each designated entity based on business requirements to obtain the configuration data of each designated entity.

[0062] Among them, it should be noted that when the target entity is an insurance type, at least one insurance item under the insurance type is obtained; in the case where multiple business data associated with at least one insurance item are not configured, in response to the configuration operation, based on business requirements, the business data of at least one insurance item are configured; based on the business data of at least one insurance item, at least one candidate entity data of the insurance type is generated.

[0063] In the embodiments of the present disclosure, when the target entity is an insurance type, the business data of the insurance items under each insurance type can be configured, and based on the business data of the insurance items under each insurance type, at least one candidate entity data of each insurance type can be generated.

[0064] For example, such as Figure 4As shown, the specified entity includes insurance types, insurance items, and insurance objects. The configuration data of the insurance type is defined through the insurance type variable, and the configuration data of the insurance item is defined through the insurance item variable. Multiple different protection contents (also known as price copies) can be defined for the insurance type variables under each insurance type, that is, multiple different protection contents can be configured for the same insurance type. Multiple different protection contents can be defined for the insurance item variables under each insurance item, that is, multiple different protection contents can be configured under the same insurance item.

[0065] It should be noted that when generating a target insurance product based on the configuration data of the specified entity, a certain insurance product / protection plan allows only one price copy of the specified entity (insurance type, insurance item, or insurance object) to be mounted; for insurance customers, they can independently fill in the specific insured amount data of a certain clause during the policy sales process, or do not set the price in the configuration data of the specified entity, or ignore the price copy already set in the configuration data of the specified entity, but use the insured amount (and the premium calculated through the rate) data filled in by the insurance customer as the actual insurance type clause price in the policy; regarding the issue of freezing an insurance type that has been sold, when an insurance product is discontinued, mark the insurance product / protection plan or insurance type as "discontinued" in the entity relationship sub-model, which will not affect the available status of the configuration data of the specified entity; on the other hand, when a certain insurance type has been sold, the content of the insurance product / protection plan and the corresponding configuration data of the insurance type need to be marked as "frozen" (that is, the content is not allowed to be modified).

[0066] As another example, obtain the business data associated with any specified entity that has been configured based on business requirements; among them, the business data is used to indicate the business attributes of any specified entity; according to the business data associated with the specified entity, generate at least one candidate entity data associated with any specified entity.

[0067] That is to say, the business data of each specified entity that has been configured based on business requirements in each insurance company can be directly obtained, and based on the business data of each specified entity, at least one candidate entity data associated with each specified entity is generated.

[0068] Step 304, in response to the selection operation, select the target entity data of any specified entity from at least one candidate entity data according to the product requirements.

[0069] For example, taking the specified entity as the insurance type, the candidate entity data under the insurance type includes: health insurance and related information of health insurance, accident insurance and related information of accident insurance, life insurance and related information of life insurance, etc. The target entity data selected by the user includes: health insurance and related information of health insurance, life insurance and related information of life insurance, etc.

[0070] Step 305: Generate a target insurance product according to the entity relationship sub-model and the target entity data associated with at least one specified entity.

[0071] It should be noted that the execution processes of Steps 301 to 302 and Step 305 can be implemented in any of the ways in the various embodiments of the present disclosure. The embodiments of the present disclosure do not make any limitations in this regard and will not be elaborated further.

[0072] In summary, for any specified entity, from the configuration data of any specified entity, determine and display at least one candidate entity data associated with any specified entity; in response to a selection operation, select the target entity data of any specified entity from at least one candidate entity data. Thus, the decoupling of the data configuration of the specified entity and the product design is achieved, and the candidate entity data related to the specified entity can be quickly screened out from a large amount of configuration data, avoiding the cumbersome process of manual search and screening, thereby saving a large amount of time and labor costs and improving the flexibility of insurance product generation; selecting the target entity data from the candidate data based on the product requirements achieves an accurate match for specific requirements, avoiding unnecessary redundancy or deviation; and the entire process is dynamic and flexible, capable of quickly adapting to different business scenarios and user requirements, significantly improving the efficiency and quality of product design.

[0073] To clearly illustrate how to generate a target insurance product according to the entity relationship sub-model and the target entity data associated with at least one specified entity in the above embodiments, the present disclosure proposes another method for generating an insurance product.

[0074] Figure 5 It is a schematic flowchart of the method for generating an insurance product shown in the third embodiment of the present disclosure.

[0075] As Figure 5 shown, the method for generating an insurance product includes the following steps:

[0076] Step 501: In response to receiving an insurance product generation request sent by a target object, obtain a target entity relationship model.

[0077] The target entity relationship model is used to indicate the data structures of multiple insurance products.

[0078] Step 502: Determine an entity relationship sub-model that matches the product requirements in the insurance product generation request from the target entity relationship model.

[0079] Step 503: In response to a selection operation, select target entity data associated with at least one specified entity in the entity relationship sub-model from the configuration data.

[0080] Step 504: Determine the product mode of the target insurance product to be generated according to the entity relationship sub-model.

[0081] In the embodiments of the present disclosure, the entity relationship sub-model includes the underlying logic and data organization method of the insurance product corresponding to the product mode. Therefore, based on the entity relationship model, the product mode of the target insurance product to be generated can be determined. Among them, the product mode may include, but is not limited to: PDU mode (multiple underlying objects can be mounted under the insurance product, and each underlying object can select different protection plans), PSU mode (multiple underlying objects can be mounted under the insurance product, and all underlying objects select the same protection plan), CDU mode (multiple underlying objects can be mounted under the insurance product, and each underlying object can select different insurance type combinations), CSU mode (multiple underlying objects can be mounted under the insurance product, and all underlying objects select the same insurance type combination), PDL mode (multiple protection plans can be mounted under the insurance product, and each protection plan can mount different underlying objects), and PSL mode (multiple protection plans can be mounted under the insurance product, and each protection plan can mount different underlying objects), etc.

[0082] As an example, the entity relationship sub-model includes at least one insurance underlying object. Determine whether there is at least one protection plan in the entity relationship sub-model that has an entity relationship with each insurance underlying object; in response to the existence of at least one protection plan in any entity relationship sub-model that has an entity relationship with each insurance underlying object, determine the mounting relationship between each insurance underlying object and the corresponding at least one protection plan; according to the product requirements, at least one insurance underlying object, and the mounting relationship between the at least one protection plan corresponding to each insurance underlying object, determine the product mode of the target insurance product to be generated.

[0083] In the embodiments of the present disclosure, the entity relationship sub-model includes at least one insurance underlying object, where the insurance underlying object refers to the insured object; for example, in property insurance, the insurance underlying object can be tangible property such as a house, a vehicle, or goods, or intangible property or related interests such as liability or credit; in personal insurance, the insurance underlying object is the life or body of the insured; determine whether there is at least one protection plan in the entity relationship sub-model that has an entity relationship with each insurance underlying object; when there is at least one protection plan in the entity relationship sub-model that has an entity relationship with each insurance underlying object, fixed protection content is provided for each insurance underlying object, and through the entity relationship sub-model, the mounting relationship between the insurance underlying object and the protection plan can also be determined. For example, at least one protection plan is mounted under each insurance underlying object, or the insurance underlying object is mounted under the protection plan. Among them, the protection plan refers to the fixed protection content provided for the insurance underlying object (such as fire protection, personal protection, etc.).

[0084] Furthermore, when determining that the attachment relationship is that at least one protection plan is attached under the insured subject based on the product requirements, it is determined whether at least one protection plan corresponding to each insured subject is the same. When at least one protection plan corresponding to each insured subject is the same, the product mode of the target insurance product to be generated is determined as the PSU mode; when at least one protection plan corresponding to each insured subject is different, the product mode of the target insurance product to be generated is determined as the PDU mode.

[0085] When determining that the attachment relationship is that different insured subjects are attached under the protection plan based on the product requirements, the product mode of the target insurance product to be generated is determined as PDL; when determining that the attachment relationship is that the same insured subject is attached under the protection plan based on the product requirements, the product mode of the target insurance product to be generated is determined as PSL.

[0086] As another example, in response to the non-existence of at least one protection plan having an entity relationship with each insured subject in the entity relationship sub-model, the insurance types corresponding to each insured subject are determined according to the product requirements; according to at least one insured subject and the insurance types corresponding to at least one insured subject, the product mode of the target insurance product to be generated is determined.

[0087] That is to say, when there is no at least one protection plan having an entity relationship with each insured subject in the entity relationship sub-model, when the insurance types corresponding to each insured subject are determined to be the same according to the product requirements, that is, all insured subjects select the same insurance combination, the product mode of the target insurance product to be generated is determined as the CSU mode; when the insurance types corresponding to each insured subject are determined to be different according to the product requirements, that is, each insured subject can select a different insurance type combination, the product mode of the target insurance product to be generated is determined as the CDU mode.

[0088] Step 505: Generate an initial insurance product according to the product mode and the entity relationship sub-model.

[0089] To improve the accuracy of insurance product generation, in the embodiments of the present disclosure, the product mode indicates the overall structure of the target insurance product to be generated, and the entity relationship sub-model indicates the entity relationships between the entities in the overall structure. Thus, the overall structure of the product mode is combined with the specific relationships of the entity relationship sub-model to generate the framework of the initial insurance product.

[0090] Step 506: Fill the target entity data associated with at least one specified entity into at least one specified entity in the initial insurance product to obtain the target insurance product.

[0091] To achieve personalized customization of insurance products, furthermore, the target entity data associated with at least one specified entity is filled into at least one specified entity in the initial insurance product to obtain the target insurance product.

[0092] It should be noted that the execution processes of steps 501 to 503 can be implemented in any one of the embodiments of the present disclosure, and the embodiments of the present disclosure do not limit this and will not elaborate further.

[0093] In summary, according to the entity relationship sub-model, determine the product mode of the target insurance product to be generated; according to the product mode and the entity relationship sub-model, generate an initial insurance product; fill the target entity data associated with at least one specified entity into at least one specified entity in the initial insurance product to obtain the target insurance product. Thus, determining the product mode based on the entity relationship sub-model ensures that the overall structure of the product is clear and logical; furthermore, by generating the initial insurance product and filling it with the target entity data, it realizes the flexible adaptation to specific business requirements or user scenarios while maintaining the integrity of the product framework; finally, accurately filling the target entity data into the specified entity ensures the customization and accuracy of the final product and meets personalized needs.

[0094] Corresponding to the insurance product generation method provided in the above embodiments, the present disclosure also provides an insurance product generation device. Since the insurance product generation device provided in the embodiments of the present disclosure corresponds to the insurance product generation method provided in the above embodiments, the implementation manners of the risk control method are also applicable to the insurance product generation device provided in the embodiments of the present disclosure and will not be described in detail in the embodiments of the present disclosure.

[0095] Figure 6 It is a schematic structural diagram of the insurance product generation device shown in the fourth embodiment of the present disclosure.

[0096] As Figure 6 shown, the insurance product generation device 600 includes: a first acquisition module 610, a first determination module 620, a selection module 630, and a generation module 640.

[0097] Among them, the first acquisition module 610 is configured to obtain a target entity relationship model in response to receiving an insurance product generation request sent by a target object; the target entity relationship model is used to indicate the data structures of multiple insurance products; the first determination module 620 is configured to determine, from the target entity relationship model, an entity relationship sub-model that matches the product requirements in the insurance product generation request; the selection module 630 is configured to select, in response to a selection operation, target entity data associated with at least one specified entity in the entity relationship sub-model; the generation module 640 is configured to generate a target insurance product according to the entity relationship sub-model and the target entity data associated with at least one specified entity.

[0098] As a possible implementation manner of an embodiment of the present disclosure, a selection module 630 is configured to determine and display at least one candidate entity data of any specified entity from the configuration data of any specified entity for any specified entity; in response to a selection operation, select the target entity data of any specified entity from at least one candidate entity data according to product requirements.

[0099] As a possible implementation manner of an embodiment of the present disclosure, the configuration data is generated by the following modules: a second acquisition module and a second determination module.

[0100] Wherein, the second acquisition module is configured to acquire service requirements associated with any specified entity; the second determination module is configured to determine the configuration data of any specified entity according to the service requirements; wherein, the configuration data is used to indicate the service attributes of any specified entity.

[0101] As a possible implementation manner of an embodiment of the present disclosure, the second determination module is configured to, in response to a configuration operation, perform service configuration on any specified entity based on the service requirements to obtain the configuration data of any specified entity; or, acquire service data associated with any specified entity that has been configured based on the service requirements; wherein, the service data is used to indicate the service attributes of any specified entity; generate the configuration data of any specified entity according to the service data associated with the specified entity.

[0102] As a possible implementation manner of an embodiment of the present disclosure, any specified entity is an insurance type, and the second determination module is configured to acquire at least one insurance item under the insurance type; in the case where multiple service data associated with at least one insurance item are not configured, in response to a configuration operation, configure the service data of at least one insurance item based on the service requirements; generate the configuration data of the insurance type based on the service data of at least one insurance item.

[0103] As a possible implementation manner of an embodiment of the present disclosure, a generation module 640 is configured to determine a product mode of a target insurance product to be generated according to an entity relationship sub-model; generate an initial insurance product according to the product mode and the entity relationship sub-model; fill the target entity data associated with at least one specified entity into at least one specified entity in the initial insurance product to obtain the target insurance product.

[0104] As a possible implementation manner of the embodiments of the present disclosure, the entity relationship sub-model includes at least one insured object, and a generation module 640 is configured to determine whether there is at least one protection plan in the entity relationship sub-model that has an entity relationship with each insured object; in response to the existence of at least one protection plan in any entity relationship sub-model that has an entity relationship with each insured object, determine the mounting relationship between each insured object and the corresponding at least one protection plan; and determine the product mode of the target insurance product to be generated according to the product requirements, at least one insured object, and the mounting relationship between the at least one protection plan corresponding to each insured object.

[0105] As a possible implementation manner of the embodiments of the present disclosure, the generation module 640 is further configured to, in response to the non-existence of at least one protection plan in the entity relationship sub-model that has an entity relationship with each insured object, determine the insurance types corresponding to each insured object according to the product requirements; and determine the product mode of the target insurance product to be generated according to the at least one insured object and the insurance types corresponding to the at least one insured object.

[0106] As a possible implementation manner of the embodiments of the present disclosure, a first determination module 620 is configured to determine, according to the product requirements, multiple target entities that match the product requirements from multiple candidate entities of the target entity relationship model; determine the entity relationships between the multiple target entities from the entity relationships of the target entity relationship model according to the product requirements; and generate an entity relationship sub-model according to the multiple target entities and the entity relationships between the multiple target entities.

[0107] The insurance product generation device according to the embodiments of the present disclosure ensures a high degree of consistency between the generated insurance product and the actual requirements by screening the entity relationship sub-model that matches the product requirements from the target entity relationship model. Furthermore, according to the product requirements, the target entity data associated with the specified entities in the target entity relationship sub-model is flexibly selected from the configuration data, reducing the coupling degree between product definition and entity data configuration, improving the flexibility of insurance product generation. Finally, by combining the entity relationship sub-model and the target entity data, the target insurance product is automatically generated, which not only simplifies the insurance product design steps but also improves the automation degree of product generation. In addition, by reusing the target entity relationship model and the configuration data, the workload of repeated development is reduced, effectively reducing the development complexity and cost.

[0108] In an exemplary embodiment, an electronic device is further proposed.

[0109] Wherein, the electronic device includes:

[0110] A processor;

[0111] A memory for storing instructions executable by the processor;

[0112] Wherein, the processor is configured to execute instructions to implement the method for generating an insurance product as proposed in any of the foregoing embodiments.

[0113] As an example, Figure 7 is a schematic structural diagram of an electronic device 700 shown in an exemplary embodiment of the present disclosure. As Figure 7 shown, the above-mentioned electronic device 700 may further include:

[0114] A memory 710 and a processor 720, a bus 730 connecting different components (including the memory 710 and the processor 720). The memory 710 stores a computer program, and when the processor 720 executes the program, it implements the method for generating an insurance product according to the embodiments of the present disclosure.

[0115] The bus 730 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any bus structure in a variety of bus structures. By way of example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0116] The electronic device 700 typically includes a variety of electronic device-readable media. These media can be any available media accessible by the electronic device 700, including volatile and non-volatile media, removable and non-removable media.

[0117] The memory 710 may further include computer system-readable media in the form of volatile memory, such as random access memory (RAM) 740 and / or cache memory 750. The server 700 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, a storage system 760 may be used for reading and writing non-removable, non-volatile magnetic media ( Figure 7 not shown, commonly referred to as a "hard disk drive"). Although Figure 7 not shown in, a disk drive for reading and writing removable non-volatile disks (such as "floppy disks") and an optical disk drive for reading and writing removable non-volatile optical disks (such as CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 730 through one or more data media interfaces. The memory 710 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present disclosure.

[0118] A program / utilities 780 having a set (at least one) of program modules 770 can be stored in, for example, the memory 710. Such program modules 770 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. The program modules 770 generally execute the functions and / or methods in the embodiments described in this disclosure.

[0119] The electronic device 700 can also communicate with one or more external devices 790 (such as a keyboard, a pointing device, a display 791, etc.), and can also communicate with one or more devices that enable a user to interact with the electronic device 700, and / or communicate with any device that enables the electronic device 700 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication can be carried out through the input / output (I / O) interface 792. Moreover, the electronic device 700 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through the network adapter 793. As shown in the figure, the network adapter 793 communicates with other modules of the electronic device 700 through the bus 730. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0120] The processor 720 executes various functional applications and data processing by running programs stored in the memory 710.

[0121] It should be noted that for the implementation process and technical principle of the electronic device in this embodiment, refer to the foregoing explanation of the method for generating an insurance product in the embodiments of the present disclosure, which will not be elaborated here.

[0122] In an exemplary embodiment, there is also provided a computer-readable storage medium including instructions, such as a memory including instructions. The above instructions can be executed by the processor of the electronic device to complete the method for generating an insurance product proposed in any of the foregoing embodiments. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0123] In an exemplary embodiment, there is also provided a computer program product including a computer program / instructions, characterized in that when the computer program / instructions are executed by a processor, the method for generating an insurance product proposed in any of the foregoing embodiments is implemented.

[0124] Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include known common general knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and examples are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the following claims.

[0125] It should be understood that the present disclosure is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.

Claims

1. A method for generating an insurance product, characterized in that: include: In response to receiving an insurance product generation request sent by a target object, a target entity relationship model is acquired; wherein the target entity relationship model is used to indicate a data structure of a plurality of insurance products; Determining, from the target entity relationship model, an entity relationship sub-model that matches the product requirement in the insurance product generation request; In response to a selection operation, selecting target entity data associated with at least one specified entity in the entity-relationship sub-model from the configuration data; The target insurance product is generated according to the entity-relationship sub-model and the target entity data associated with the at least one designated entity.

2. The method according to claim 1, characterized in that In response to the selection operation, selecting target entity data associated with at least one specified entity in the entity-relationship sub-model from the configuration data includes: For any designated entity, determine and display at least one candidate entity data related to the any designated entity from the configuration data of the any designated entity; In response to the selection operation, target entity data of any designated entity is selected from the at least one candidate entity data according to the product requirement.

3. The method according to claim 2, characterized in that The configuration data is generated using the following steps: Obtaining business requirements associated with any of the specified entities; According to the business requirements, configuration data of any designated entity is determined; wherein the configuration data is used to indicate a business attribute of any designated entity.

4. The method according to claim 3, characterized in that The determining, according to the business requirement, the configuration data of any designated entity comprises: In response to the configuration operation, based on the business requirement, performing business configuration on the any designated entity to obtain configuration data of the any designated entity; or, Acquire business data associated with any one of the designated entities that has been configured based on the business requirements; wherein the business data is used to indicate business attributes of any one of the designated entities; Configuration data of any of the designated entities is generated according to the business data associated with the designated entity.

5. The method according to claim 4, characterized in that The any designated entity is a type of insurance, and the response to the configuration operation, based on the business requirements, performs business configuration on the any designated entity to obtain configuration data of the any designated entity, including: Obtain at least one insurance item under the insurance type; In a case where a plurality of business data associated with the at least one insurance item is not configured, in response to a configuration operation, configuring the business data of the at least one insurance item based on the business requirement; Based on the business data of the at least one insurance item, configuration data of the insurance type is generated.

6. The method according to claim 1, characterized in that The generating the target insurance product according to the entity-relationship sub-model and the target entity data associated with the at least one designated entity includes: Determining the product model of the target insurance product to be generated according to the entity-relationship sub-model; generating an initial insurance product according to the product schema and the entity-relationship sub-model; Fill the target entity data associated with the at least one designated entity into the at least one designated entity in the initial insurance product to obtain the target insurance product.

7. The method according to claim 6, characterized in that The entity-relationship sub-model includes at least one insurance subject, and determining the product model of the target insurance product to be generated according to the entity-relationship sub-model includes: Determining whether there is at least one protection plan having an entity relationship with each of the insurance objects in the entity relationship sub-model; In response to the existence of at least one protection plan having an entity relationship with each of the insured objects in any entity-relationship sub-model, determining a mounting relationship between each of the insured objects and the corresponding at least one protection plan; The product model of the target insurance product to be generated is determined according to the product demand, the at least one insurance subject, and the mounting relationship between at least one protection plan corresponding to each insurance subject.

8. The method according to claim 7, characterized in that The method further comprises: In response to the absence of at least one protection plan having an entity relationship with each of the insured objects in the entity-relationship sub-model, determining the insurance type corresponding to each of the insured objects according to the product requirements; The product model of the target insurance product to be generated is determined according to the at least one insurance subject and the insurance type corresponding to the at least one insurance subject.

9. The method according to claim 1, characterized in that: The step of determining, from the target entity relationship model, an entity relationship sub-model that matches the product requirement in the insurance product generation request comprises: According to the product requirements, determining a plurality of target entities matching the product requirements from a plurality of candidate entities of the target entity relationship model; According to the product requirements, determining entity relationships among the plurality of target entities from entity relationships of the target entity relationship model; The entity relationship sub-model is generated according to the multiple target entities and the entity relationships between the multiple target entities.

10. A device for generating an insurance product, characterized in that: include: A first acquisition module is used to acquire a target entity relationship model in response to receiving an insurance product generation request sent by a target object; wherein the target entity relationship model is used to indicate a data structure of a plurality of insurance products; A first determination module, configured to determine, from the target entity relationship model, an entity relationship sub-model that matches the product requirement in the insurance product generation request; A selection module, configured to select, in response to a selection operation, target entity data associated with at least one specified entity in the entity-relationship sub-model from the configuration data; A generation module is used to generate the target insurance product according to the entity-relationship sub-model and the target entity data associated with the at least one designated entity.

Images