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; wherein the target entity relationship model is used for representing data structures of a plurality of insurance products; according to a product demand in the insurance product generation request, determining at least one entity relationship sub-model matched with the product demand from the target entity relationship model; and generating at least one target insurance product based on the at least one entity relationship sub-model and the product demand, thereby realizing flexible generation of the corresponding insurance product according to different product demands through an automatic process, improving the overall efficiency, avoiding the limitation of a traditional fixed template of the product, and improving the user experience. And moreover, diversified requirements of different customer groups can be met, the reusability of the data structure of the product is improved, and the cost of repeated development is reduced.

Description

Technical Field

[0001] The present disclosure relates to the technical field of data processing, 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 are not only related 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 partly solve one of the technical problems in the related art. 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 represent the data structures of multiple insurance products; according to the product requirements in the insurance product generation request, determining at least one entity relationship sub-model that matches the product requirements from the target entity relationship model; and generating at least one target insurance product based on the at least one entity relationship sub-model and the product requirements.

[0005] According to a second aspect of an embodiment of the present disclosure, there is provided an apparatus for generating an insurance product, including: an 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 represent the data structures of multiple insurance products; a first determination module, configured to determine at least one entity relationship sub-model that matches the product requirements from the target entity relationship model according to the product requirements in the insurance product generation request; and a generation module, configured to generate at least one target insurance product based on the at least one entity relationship sub-model and the product requirements.

[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 instructions in the computer-readable storage medium 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 embodiments of the first aspect 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 embodiments of the first aspect 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 entity relationship sub-models that match the product requirements from the target entity relationship model, and generating at least one target insurance product based on at least one entity relationship sub-model and the product requirements, it realizes the flexible generation of corresponding insurance products according to different product requirements through an automated process, improves the overall efficiency, avoids the limitations of traditional fixed product templates, and can meet the diverse needs of different customer groups; in addition, the target entity relationship model decomposes the data structure of the insurance product into multiple entity relationship sub-models, and each entity relationship sub-model can be used independently or in combination, improving the reusability of the data structure and reducing the cost of repeated development; among them, when generating at least one target insurance product based on at least one entity relationship sub-model and the product requirements, it is determined whether there is at least one protection plan in any entity relationship sub-model that has an entity relationship with each insured object. When there is at least one protection plan in any entity relationship sub-model that has an entity relationship with each insured object, the mounting relationship between each insured object and the corresponding at least one protection plan is determined; according to the product requirements, at least one insured object, and the mounting relationship between each insured object and the corresponding at least one protection plan, a target insurance product corresponding to any entity relationship sub-model is generated, realizing the refined design of the insurance product, improving the pertinence and applicability of the product, and dynamically adjusting the combination of the insured object and the protection plan based on the product requirements, improving the flexibility and scalability of the product design; finally, the logical association between the insured object and the protection plan is standardized by using the entity relationship sub-model, reducing the complexity of generating the insurance product and providing clear structured support for subsequent product optimization and iteration; when there is no at least one protection plan in any entity relationship sub-model that has an entity relationship with each insured object, the complexity of generating the insurance product is simplified by determining whether the target insurance types to be selected corresponding to each insured object are the same; when the target insurance types are the same, the target insurance type is accurately determined from the candidate insurance types based on the product requirements, ensuring the effective allocation of resources and the high adaptability of the product; finally, the target insurance product is generated by combining the selected target insurance type, improving the flexibility of product generation.

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

[0012] The drawings herein 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 undue limitation on the present disclosure.

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

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

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

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

[0017] Figure 5 is a schematic structural diagram of an entity relationship sub-model shown in an embodiment of the present disclosure;

[0018] Figure 6 is a schematic product structure diagram of a target insurance product shown in an embodiment of the present disclosure;

[0019] Figure 7 is a schematic structural diagram of another entity relationship sub-model shown in an embodiment of the present disclosure;

[0020] Figure 8 is a schematic product structure diagram of another target insurance product shown in an embodiment of the present disclosure;

[0021] Figure 9 is a schematic flowchart of a method for generating an insurance product shown in the fourth embodiment of the present disclosure;

[0022] Figure 10 is a schematic structural diagram of another entity relationship sub-model provided by an embodiment of the present disclosure;

[0023] Figure 11 is a schematic product structure diagram of another target insurance product shown in an embodiment of the present disclosure;

[0024] Figure 12 is a schematic structural diagram of another entity relationship sub-model provided by an embodiment of the present disclosure;

[0025] Figure 13 It is a schematic structural diagram of another target insurance product shown in the embodiments of the present disclosure;

[0026] Figure 14 It is a schematic flowchart of a method for generating an insurance product shown in the fifth embodiment of the present disclosure;

[0027] Figure 15 It is a schematic structural diagram of another entity relationship sub-model provided by the embodiments of the present disclosure;

[0028] Figure 16 It is a schematic structural diagram of another target insurance product shown in the embodiments of the present disclosure;

[0029] Figure 17 It is a schematic structural diagram of another entity relationship sub-model provided by the embodiments of the present disclosure;

[0030] Figure 18 It is a schematic structural diagram of another target insurance product shown in the embodiments of the present disclosure;

[0031] Figure 19 It is a schematic structural diagram of a device for generating an insurance product shown in the sixth embodiment of the present disclosure;

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

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

[0034] It should be noted that in the specification and claims of the present disclosure and the above-mentioned accompanying drawings, the terms "first", "second", etc. 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 data used can be interchanged under appropriate circumstances so that the embodiments of the present disclosure described herein can be implemented in an order other than 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.

[0035] 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 processing 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.

[0036] Currently, the insurance product systems of each insurance company are all specialized customized systems or deeply customized systems based on a certain benchmark. They are deeply bound to the company's own business, lacking scalability and configuration capabilities. The support for new business and new functions requires coding and customization development. When the existing system's data model (entity relationship model) does not support the expansion of new business functions, system developers usually make random adjustments or modifications to the data model. This also results in no unified or relatively general insurance product data model for each insurance product. Each system has its own data model, which usually only supports the configuration management of one specification of insurance products and can only meet the current business of the department to which the system belongs. Even the insurance product data models among several departments of an insurance company are not the same. The interaction between several systems within the same company requires data structure conversion during interface calls; in the naming of each component in the insurance product model, everyone acts on their own, lacking a standardized unified solution.

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

[0038] The following describes the method and device for generating insurance products according to the embodiments of the present disclosure with reference to the accompanying drawings.

[0039] Figure 1 It is a schematic flowchart of the method for generating insurance products 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 this 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.

[0040] As shown in Figure 1 , the method for generating insurance products includes the following steps:

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

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

[0043] To improve the flexibility and unity of generating insurance products, as a possible implementation, generate insurance products based on product requirements and a general entity relationship model.

[0044] In an embodiment of the present disclosure, when a request for generating an insurance product sent by a target object is received, 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 represent the underlying logic and data organization method of multiple insurance products. It expresses the commonalities and characteristics of different insurance products in a unified form by defining entities, attributes, and entity relationships.

[0045] For example, as Figure 2 shown, the target entity model includes 5 entities, namely: insurance product, insured object, protection plan, insurance type, and insurance item. Among them, there are 7 entity relationships among 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.

[0046] Step 102, according to the product requirements in the insurance product generation request, determine at least one entity relationship sub-model that matches the product requirements from the target entity relationship model.

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

[0048] As an example, according to the product requirements, from multiple candidate entities in the target entity relationship model, determine multiple target entities that match the product requirements, that is, analyze the product requirements, extract key information, such as: customer type (individual / enterprise), insurance type category (health insurance / property insurance / life insurance, etc.), specific protection content (such as hospitalization medical treatment, accidental injury, etc.). According to the analyzed requirements, screen out relevant entities from the target entity relationship model. For example, if "health insurance" is mentioned in the requirements, then screen out entities related to health insurance; furthermore, according to the product requirements, from the entity relationships in the target entity relationship model, determine the entity relationships between multiple target entities. According to the multiple target entities and the entity relationships between the multiple target entities, generate at least one entity relationship sub-model, that is, on the basis of screening out relevant entities, further construct the entity relationship sub-model; among them, the entity relationship sub-model is a subset of the target entity relationship model.

[0049] Step 103, generate at least one target insurance product based on at least one entity relationship sub-model and the product requirements.

[0050] In an embodiment of the present disclosure, the entity relationship sub-model is combined with the product requirements, and through specific logical rules and data filling, a target insurance product that meets the product requirements is finally generated.

[0051] The method for generating an insurance product according to an embodiment of the present disclosure screens out an entity relationship sub-model that matches the product requirements from a target entity relationship model, and generates at least one target insurance product based on at least one entity relationship sub-model and the product requirements. It realizes the flexible generation of corresponding insurance products according to different product requirements through an automated process, improves the overall efficiency, avoids the limitations of the traditional fixed templates of products, and can meet the diverse needs of different customer groups. In addition, the target entity relationship model decomposes the data structure of the insurance product into multiple sub-models, and each sub-model can be used independently or in combination, improving the reusability of the product data structure and reducing the cost of repeated development.

[0052] To clearly illustrate how the above embodiment generates at least one target insurance product based on at least one entity relationship sub-model and the product requirements, the present disclosure proposes another method for generating an insurance product.

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

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

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

[0056] Among them, the target entity relationship model is used to represent the data structures of multiple insurance products.

[0057] Step 302, according to the product requirements in the insurance product generation request, determine at least one entity relationship sub-model that matches the product requirements from the target entity relationship model.

[0058] Step 303, in response to the existence of at least one protection plan having an entity relationship with each insured object in any entity relationship sub-model, determine the mounting relationship between each insured object and the corresponding at least one protection plan.

[0059] To improve the integrity of the insurance product, in the embodiment of the present disclosure, each entity relationship sub-model includes at least one insured object, where the insured object refers to the insured object. For example, in property insurance, the insured 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 insured object is the life or body of the insured.

[0060] In order to provide a clear logical basis for generating insurance products, in the embodiments of the present disclosure, when there is at least one protection plan in any entity relationship sub-model that has an entity relationship with each insurance object, it is an entity that provides fixed protection content for each insurance object. Through any entity relationship sub-model, the mounting relationship between the insurance object and the protection plan can also be determined. For example, at least one protection plan is mounted under each insurance object, or the insurance object is mounted under the protection plan. Among them, the protection plan is used to provide fixed protection content for the insurance object (such as fire protection, personal protection, etc.).

[0061] Step 304, generate a target insurance product corresponding to any entity relationship sub-model according to the product requirements, at least one insurance object, and the mounting relationship between the at least one protection plan corresponding to each insurance object.

[0062] In order to achieve the flexibility and customization of insurance product generation, in the embodiments of the present disclosure, based on the product requirements, the insurance objects to be covered and at least one protection plan corresponding to each insurance object are determined. Furthermore, based on the mounting relationship between the insurance object and the corresponding protection plan in the entity relationship sub-model, the protection plan and the insurance object are associated. Thus, based on the insurance object, at least one protection plan corresponding to each insurance object, and the mounting relationship between the insurance object and the protection plan, the final target insurance product is generated.

[0063] It should be noted that when there is a protection plan in the target insurance product and the sum insured and the premium have been configured in the protection plan, the sum insured and the premium configured in the protection plan shall prevail. If the sum insured and the premium have not been configured in the protection plan, the sum of the sum insured of all insurance types mounted under the protection plan shall be used as the sum insured of the protection plan and the sum of the premiums of all insurance types shall be used as the premium of the protection plan. It should be noted that the sum insured is a mandatory item. The rate can also be configured in the protection plan. At least one of the premium and the rate shall be filled in. Among them, the premium = sum insured * rate. When the premium and the rate do not match, the premium shall prevail. In addition, when there is no protection plan in the target insurance product, the sum of the sum insured configured in all insurance types shall be used as the sum insured of the target insurance product, and at the same time, the sum of the premiums configured in all insurance types shall be used as the premium of the target insurance product.

[0064] In summary, by responding to at least one protection plan in any entity relationship sub-model that has an entity relationship with each insurance object, the mounting relationship between each insurance object and the corresponding at least one protection plan is determined; according to the product requirements, at least one insurance object, and the mounting relationship between each insurance object and the corresponding at least one protection plan, a target insurance product corresponding to any entity relationship sub-model is generated. Thus, the refined design of insurance products is achieved, ensuring that each insurance object can be matched with the most suitable protection plan, improving the pertinence and applicability of the product; secondly, based on the product requirements, the combination of insurance objects and protection plans is dynamically adjusted, improving the flexibility and scalability of product design; finally, the entity relationship sub-model is used to standardize the logical association between insurance objects and protection plans, reducing the complexity of insurance product generation, and providing clear structured support for subsequent product optimization and iteration, thereby not only meeting the diverse market demands but also enhancing the user experience.

[0065] To clearly illustrate how the target insurance product corresponding to any entity relationship sub-model is generated according to the product requirements, at least one insurance object, and the mounting relationship between each insurance object and the corresponding at least one protection plan in the above embodiments, the present disclosure proposes another method for generating an insurance product.

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

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

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

[0069] Among them, the target entity relationship model is used to represent the data structure of multiple insurance products.

[0070] Step 402, according to the product requirements in the insurance product generation request, determine at least one entity relationship sub-model that matches the product requirements from the target entity relationship model.

[0071] Step 403, in response to at least one protection plan in any entity relationship sub-model that has an entity relationship with each insurance object, determine the mounting relationship between each insurance object and the corresponding at least one protection plan.

[0072] Step 404, in response to each mounting relationship indicating that at least one protection plan is mounted under the corresponding insurance object, determine whether the at least one protection plan corresponding to each insurance object is the same.

[0073] In order to improve the accuracy of insurance product generation, in the embodiments of the present disclosure, when at least one protection plan is mounted under an insurance object, it is compared whether the protection plans mounted under different insurance objects are the same.

[0074] For example, if the list of protection plans mounted under insurance object A and insurance object C is both [P1, P2, P3], it indicates that the protection plans mounted under insurance object A and insurance object C are the same; for another example, if the protection plan lists of insurance object A and insurance object B are [P1, P2, P3] and [P2, P4] respectively, it indicates that the protection plans mounted under insurance object A and insurance object B are different.

[0075] Step 405, in response to at least one protection plan corresponding to each insurance object being the same, according to the product requirements, determine the target insurance types under at least one protection plan from multiple candidate insurance types adapted to at least one protection plan.

[0076] Among them, the target insurance types include at least one target insurance item.

[0077] In order to further improve the pertinence and effectiveness of the protection plan, as a possible implementation manner, for each protection plan, determine the target insurance type matching each protection plan from a set of multiple candidate insurance types.

[0078] As an example, when the protection plans mounted under each insurance object are the same, according to the product requirements, determine the target insurance types under each protection plan from multiple candidate insurance types adapted to each protection plan. It should be noted that the multiple candidate insurance types adapted to each protection plan can be pre-configured, and each target insurance type includes at least one target insurance item. Among them, the target insurance item refers to the protection content or clause further subdivided under a specific target insurance type. For example, if the target insurance type is "auto insurance", the target insurance items may include "vehicle damage insurance", "third-party liability insurance", etc.

[0079] For example, for insurance object A and insurance object B, the protection plans mounted under insurance object A and insurance object B are the same. For example, both insurance object A and insurance object B mount protection plan A and protection plan B. For protection plan A, according to the product requirements, determine that the target insurance types matching protection plan A include insurance type 1, insurance type 2, and insurance type 3. For protection plan B, according to the product requirements, determine that the target insurance type matching protection plan B includes insurance type 4.

[0080] Step 406, generate a target insurance product corresponding to any entity relationship sub-model according to each insurance object, at least one protection plan corresponding to each insurance object, and the target insurance types under at least one protection plan.

[0081] In an embodiment of the present disclosure, any one of the entity relationship sub-models defines the logical relationship among the insurance object, the protection plan, and the target insurance type. Based on this logical relationship, the insurance object, the protection plan, and the target insurance type are integrated to generate a target insurance product corresponding to any one of the entity relationship sub-models.

[0082] For example, as Figure 5 shown, Figure 5 is a schematic structural diagram of an entity relationship sub-model provided by an embodiment of the present disclosure. The product structure of the target product corresponding to this entity relationship sub-model is as Figure 6 shown. In Figure 6 , under the target insurance product, insurance object A, insurance object B, and insurance object C are mounted. The protection plans mounted under insurance object A, insurance object B, and insurance object C are the same, that is, protection plan A and protection plan B are mounted under both insurance object A, insurance object B, and insurance object C. Among them, the target insurance types under protection plan A include insurance type 1, insurance type 2, and insurance type 3, and the target insurance types under protection plan B include insurance type 4. The target insurance items under insurance type 1 include: insurance item 1, insurance item 2, and insurance item 3. The target insurance items under insurance type 2 include: insurance item 4 and insurance item 5. The target insurance items under insurance type 3 include: insurance item 6 and insurance item 7. The target insurance items under insurance type 4 include: insurance item 8 and insurance item 9.

[0083] As another example, in response to at least one protection plan corresponding to each insurance object being different, for any one of the insurance objects, according to the product requirements, from multiple candidate insurance types adapted to at least one protection plan corresponding to any one of the insurance objects, determine the target insurance types under at least one protection plan corresponding to any one of the insurance objects; according to each insurance object, at least one protection plan corresponding to each insurance object, and the target insurance types under at least one protection plan corresponding to each insurance object, generate a target insurance product corresponding to any one of the entity relationship sub-models.

[0084] That is to say, when the protection plans mounted under each insurance object are different, for any one of the insurance objects, according to the product requirements, select the target insurance types of each protection plan under any one of the insurance objects. Furthermore, based on the logical relationship of any one of the corresponding entity relationship sub-models, integrate each insurance object, at least one protection plan corresponding to each insurance object, and the target insurance types under each protection plan to generate a target insurance product corresponding to any one of the entity relationship sub-models.

[0085] For example, as Figure 7 shown, Figure 7 is a schematic structural diagram of another entity relationship sub-model provided by an embodiment of the present disclosure. The product structure of the target product corresponding to the entity relationship sub-model is as Figure 8 shown. In Figure 8Among them, insurance object A and insurance object B are mounted under the target insurance product. The protection plans mounted under insurance object A and insurance object B are different. Protection plan A and protection plan B are mounted under insurance object A, protection plan C and protection plan D are mounted under insurance object B. The target insurance types under protection plan A include insurance type 1, insurance type 2, and insurance type 3. The target insurance type under protection plan B includes insurance type 4. The target insurance type under protection plan C includes insurance type 1. The target insurance type under protection plan D includes insurance type 5.

[0086] In summary, by automatically mounting at least one protection plan for the insurance object according to each mounting relationship and efficiently judging the consistency of these protection plans, the flexibility and efficiency of insurance product design are greatly improved. When it is found that multiple insurance objects share the same protection plan, according to the specific product requirements, the optimal target insurance type is selected from multiple adapted candidate insurance types, which not only simplifies the process of insurance type selection but also ensures that the insurance product can meet the diverse market demands. Finally, combining the information of the insurance object, the protection plan, and the target insurance type, the target insurance product that matches the entity relationship sub-model is automatically generated, which not only accelerates the generation speed of the insurance product but also improves the accuracy and consistency of the insurance product generation.

[0087] To clearly illustrate how to generate the target insurance product corresponding to any entity relationship sub-model according to the product requirements, at least one insurance object, and the mounting relationship between each insurance object and the corresponding at least one protection plan in the above embodiments, the present disclosure proposes another method for generating an insurance product.

[0088] Figure 9 It is a schematic flowchart of the method for generating an insurance product shown in the fourth embodiment of the present disclosure.

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

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

[0091] Among them, the target entity relationship model is used to represent the data structure of multiple insurance products.

[0092] Step 902, according to the product requirements in the insurance product generation request, determine at least one entity relationship sub-model that matches the product requirements from the target entity relationship model.

[0093] Step 903, in response to the existence of at least one protection plan having an entity relationship with each insurance object in any entity relationship sub-model, determine the mounting relationship between each insurance object and the corresponding at least one protection plan.

[0094] Step 904: In response to each attachment relationship indicating that at least one insured object is attached under each protection plan, determine whether the target insurance types to be selected corresponding to the insured objects attached under any one protection plan are the same.

[0095] To improve the accuracy of insurance product generation, in the embodiments of the present disclosure, when at least one insured object is attached under a protection plan, compare whether the insured objects attached under different protection plans use the same insurance terms.

[0096] For example, the insured objects attached under protection plan A and protection plan B are both insured object A and insured object B. The insured object A and insured object B under protection plan A share the same insurance terms, that is, the insurance types 1, 2, and 3 corresponding to insured object A and insured object B; the insured object A and insured object B under protection plan B share the same insurance terms, and the insured object A and insured object B under protection plan B correspond to insurance type 4. Another example is that the insured objects attached under protection plan A and protection plan B are both insured object A and insured object B. The insured object A and insured object B under protection plan A correspond to different insurance terms. Insured object A corresponds to insurance types 1, 2, and 3, and insured object B corresponds to insurance type 4. The insured object A and insured object B under protection plan B correspond to different insurance terms. Insured object A corresponds to insurance type 1, and insured object B corresponds to insurance type 5.

[0097] Step 905: In response to the target insurance types corresponding to the insured objects attached under any one protection plan being the same, according to the product requirements, determine the target insurance types corresponding to the at least one insured object attached under any one protection plan from multiple candidate insurance types adapted to the at least one insured object attached under any one protection plan.

[0098] To improve the accuracy and efficiency of insurance product generation, in the embodiments of the present disclosure, when the target insurance types to be selected corresponding to the insured objects attached under any one protection plan are the same, determine the target insurance types corresponding to the at least one insured object from multiple candidate insurance types adapted to the at least one insured object attached under any one protection plan.

[0099] Step 906: Generate a target insurance product corresponding to any entity relationship sub-model according to each protection plan, at least one insured object under each protection plan, and the target insurance types under the at least one insured object attached under each protection plan.

[0100] To improve the accuracy of insurance product generation, in the embodiments of the present disclosure, any one of the entity relationship sub-models defines the logical relationship among the protection plan, the insured object, and the target insurance type. Based on this logical relationship, integrate the protection plan, the insured object, and the target insurance type to generate a target insurance product corresponding to any one of the entity relationship sub-models.

[0101] For example, as Figure 10 shown Figure 10 is a schematic structural diagram of another entity relationship sub-model provided by an embodiment of the present disclosure. The product structure of the target product corresponding to the entity relationship sub-model is as Figure 11 shown. In Figure 11 , the target insurance product includes protection plan A and protection plan B. Under both protection plan A and protection plan B, insurance object A and insurance object B are mounted. The insurance object A and insurance object B under protection plan A share the same insurance terms, that is, the insurance object A and insurance object B under protection plan A share insurance types 1, 2, and 3. The insurance object A and insurance object B under protection plan B share the same insurance terms, that is, the insurance object A and insurance object B under protection plan B share insurance type 4.

[0102] As another example, in response to different target insurance types to be selected corresponding to each insurance object mounted under any protection plan, according to product requirements, from multiple candidate insurance types adapted to any insurance object mounted under any protection plan, determine the target insurance type corresponding to any insurance object mounted under any protection plan; according to each protection plan, at least one insurance object under each protection plan, and the target insurance types corresponding to each insurance object mounted under each protection plan, generate a target insurance product corresponding to any entity relationship sub-model.

[0103] That is to say, when the target insurance types to be selected corresponding to each insurance object mounted under any protection plan are different, for any insurance object mounted under any protection plan, according to product requirements, from multiple candidate scenarios adapted to the any insurance object, determine the target insurance type corresponding to the any insurance object. Furthermore, based on the logical relationship of the protection plan, insurance object, and the target insurance type corresponding to the insurance object indicated in any entity relationship sub-model, integrate the protection plan, insurance object, and target insurance type to generate a target insurance product corresponding to the any entity relationship sub-model.

[0104] For example, as Figure 12 shown Figure 12 is a schematic structural diagram of another entity relationship sub-model provided by an embodiment of the present disclosure. The product structure of the target insurance product corresponding to the entity relationship sub-model is as Figure 13 shown. In Figure 13 , the target insurance product includes protection plan A and protection plan B. Under both protection plan A and protection plan B, insurance object A and insurance object B are mounted. The insurance object A and insurance object B under protection plan A correspond to different insurance terms, that is, the insurance object A under protection plan A corresponds to insurance types 1, 2, and 3, the insurance object B under protection plan A corresponds to insurance type 4, the insurance object A under protection plan B corresponds to insurance type 1, and the insurance object B under protection plan B corresponds to insurance type 5.

[0105] In summary, by determining whether the target insurance types to be selected corresponding to each insured item mounted under the guarantee plan are the same, redundant design can be effectively reduced, ensuring that the product structure is clear and the logic is consistent; when the target insurance types are the same, the target insurance type can be accurately determined from multiple candidate insurance types that are adapted, further optimizing resource allocation and reducing complexity; generating a target insurance product based on the clear mounting relationship and the selected target insurance type not only meets the flexibility of product requirements but also ensures the pertinence and adaptability of the product.

[0106] To clearly illustrate how at least one target insurance product is generated based on the at least one entity relationship sub-model and the product requirements in the above embodiments, the present disclosure proposes another method for generating an insurance product.

[0107] Figure 14 It is a schematic flowchart of the method for generating an insurance product shown in the fifth embodiment of the present disclosure.

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

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

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

[0111] Step 1402, according to the product requirements in the insurance product generation request, determine at least one entity relationship sub-model that matches the product requirements from the target entity relationship model.

[0112] Step 1403, in response to the situation that there is no at least one guarantee plan having an entity relationship with each insured item in any entity relationship sub-model, determine whether the target insurance types to be selected corresponding to each insured item are the same.

[0113] To improve the flexibility of insurance product generation, in the embodiments of the present disclosure, when there is no at least one guarantee plan having a specific entity relationship with each insured item in any entity relationship sub-model, that is, there is no fixed guarantee content corresponding to each insured item, the same or different insurance type combinations can be selected for each insured item.

[0114] Step 1404, in response to the target insurance types to be selected corresponding to each insured item being the same, according to the product requirements, determine the target insurance type corresponding to at least one insured item from multiple candidate insurance types that are adapted to at least one insured item.

[0115] To meet user requirements, as an example, when the target insurance types to be selected for each insured item are the same, according to the product requirements, the target insurance types corresponding to the at least one insured item are determined from multiple candidate scenarios adapted to the at least one insured item.

[0116] Step 1405: Generate a target insurance product corresponding to any entity relationship sub-model according to the at least one insured item and the target insurance types corresponding to the at least one insured item.

[0117] To improve the accuracy of insurance product generation, in the embodiments of the present disclosure, based on the logical relationship between the at least one insured item indicated by any entity relationship sub-model and the target insurance types corresponding to the at least one insured item, the at least one insured item and the target insurance types corresponding to the at least one insured item are integrated to generate a target insurance product corresponding to any entity relationship sub-model.

[0118] For example, as Figure 15 shown, Figure 15 is a structural schematic diagram of another entity relationship sub-model provided by the embodiments of the present disclosure, and the product structure of the target insurance product corresponding to the entity relationship sub-model is as Figure 16 shown. In Figure 16 , insured item A, insured item B, and insured item C are mounted under the target insurance product, and insured item A, insured item B, and insured item C all select the same insurance type combination, that is, insured item A, insured item B, and insured item C all correspond to insurance types 1, 2, 3, and 4.

[0119] As another example, in response to different target insurance types to be selected for each insured item, according to the product requirements, the target insurance type corresponding to any insured item is determined from multiple candidate insurance types adapted to any insured item; according to each insured item and the target insurance types corresponding to each insured item, a target insurance product corresponding to any entity relationship sub-model is generated.

[0120] That is to say, when the target insurance types corresponding to each insured item are different, for each insured item, according to the product requirements, the target insurance type corresponding to each insured item is determined from multiple candidate insurance types adapted to each insured item. Furthermore, based on each insured item indicated by any entity relationship sub-model and the target insurance types corresponding to each insured item, a target insurance product corresponding to any entity relationship sub-model is generated.

[0121] For example, as Figure 17 shown, Figure 17 is a structural schematic diagram of another entity relationship sub-model provided by the embodiments of the present disclosure, and the product structure of the target insurance product corresponding to the entity relationship sub-model is as Figure 18 shown. In Figure 18In it, insurance object A and insurance object B are mounted under the target insurance product, and different insurance type combinations are selected for insurance object A and insurance object B, that is, insurance object A corresponds to insurance types 1, 2, 3, and 4, and insurance object B corresponds to insurance type 1.

[0122] It should be noted that the execution processes of steps 1401 to 1402 can be implemented in any one of the embodiments of the present disclosure respectively. The embodiments of the present disclosure do not make any limitations in this regard and will not be elaborated any further.

[0123] In summary, by responding to the non - existence of at least one guarantee plan having an entity relationship with each insurance object in any entity relationship sub - model, it is judged whether the target insurance types to be selected corresponding to each insurance object are the same; in response to the target insurance types to be selected corresponding to each insurance object being the same, according to the product requirements, at least one target insurance type corresponding to at least one insurance object is determined from multiple candidate insurance types adapted to at least one insurance object; according to at least one insurance object and at least one target insurance type corresponding to at least one insurance object, a target insurance product corresponding to any entity relationship sub - model is generated. Thus, by judging whether the target insurance types to be selected corresponding to each insurance object are the same, the complexity of insurance product generation is simplified; when the target insurance types are the same, the target insurance types are accurately determined from the candidate insurance types based on the product requirements, ensuring the effective allocation of resources and the high adaptability of the product; finally, the target insurance product is generated by combining the selected target insurance types, improving the flexibility of product generation.

[0124] Corresponding to the insurance product generation method provided in the above - mentioned embodiment, 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 - mentioned embodiment, the implementation manners of the insurance product generation 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.

[0125] Figure 19 It is a schematic structural diagram of the insurance product generation device shown in the sixth embodiment of the present disclosure.

[0126] As Figure 19 shown, the insurance product generation device 1900 includes: an acquisition module 1910, a first determination module 1920, and a generation module 1930.

[0127] Among them, an obtaining module 1910 is configured to obtain a target entity relationship model in response to receiving an insurance product generation request sent by a target object, where the target entity relationship model is used to represent the data structures of multiple insurance products; a first determination module 1920 is configured to determine at least one entity relationship sub-model that matches the product requirements from the target entity relationship model according to the product requirements in the insurance product generation request; a generation module 1930 is configured to generate at least one target insurance product based on the at least one entity relationship sub-model and the product requirements.

[0128] As a possible implementation manner of an embodiment of the present disclosure, each entity relationship sub-model includes at least one insured object, and the generation module 1930 is configured to, in response to the existence of at least one protection plan having an entity relationship with each insured object in any one of the entity relationship sub-models, determine the mounting relationship between each insured object and the corresponding at least one protection plan; and generate a target insurance product corresponding to any one of the entity relationship sub-models according to the product requirements, the at least one insured object, and the mounting relationship between the at least one insured object and the corresponding at least one protection plan.

[0129] As a possible implementation manner of an embodiment of the present disclosure, the generation module 1930 is configured to, in response to each mounting relationship indicating that at least one protection plan is mounted under the corresponding insured object, determine whether the at least one protection plan corresponding to each insured object is the same; in response to the at least one protection plan corresponding to each insured object being the same, determine a target insurance type under the at least one protection plan from multiple candidate insurance types adapted to the at least one protection plan according to the product requirements, where the target insurance type includes at least one target insurance item; and generate a target insurance product corresponding to any one of the entity relationship sub-models according to each insured object, the at least one protection plan corresponding to each insured object, and the target insurance type under the at least one protection plan.

[0130] As a possible implementation manner of an embodiment of the present disclosure, the insurance product generation device 1900 further includes: a second determination module.

[0131] Among them, the second determination module is configured to, in response to the at least one protection plan corresponding to each insured object being different, for any one of the insured objects, determine a target insurance type under the at least one protection plan corresponding to the any one of the insured objects from multiple candidate insurance types adapted to the at least one protection plan corresponding to the any one of the insured objects according to the product requirements; and the generation module 1930 is further configured to generate a target insurance product corresponding to any one of the entity relationship sub-models according to each insured object, the at least one protection plan corresponding to each insured object, and the target insurance type under the at least one protection plan corresponding to each insured object.

[0132] As a possible implementation manner of an embodiment of the present disclosure, the generating module 1930 is configured to, in response to each of the mounting relationships indicating that at least one insured object is mounted under each guarantee plan, determine whether the target insurance types to be selected corresponding to the insured objects mounted under any one guarantee plan are the same; in response to the target insurance types corresponding to the insured objects mounted under any one guarantee plan being the same, according to the product requirements, determine the target insurance type corresponding to at least one insured object mounted under any one guarantee plan from a plurality of candidate insurance types adapted to the at least one insured object mounted under any one guarantee plan; and generate a target insurance product corresponding to any one entity relationship sub-model according to each guarantee plan, at least one insured object under each guarantee plan, and the target insurance type corresponding to at least one insured object mounted under each guarantee plan.

[0133] As a possible implementation manner of an embodiment of the present disclosure, the insurance product generating device 1900 further includes: a third determination module.

[0134] Wherein, the third determination module is configured to, in response to the target insurance types to be selected corresponding to the insured objects mounted under any one guarantee plan being different, according to the product requirements, determine the target insurance type corresponding to any one insured object mounted under any one guarantee plan from a plurality of candidate insurance types adapted to any one insured object mounted under any one guarantee plan; and the generating module 1930 is further configured to generate a target insurance product corresponding to any one entity relationship sub-model according to each guarantee plan, at least one insured object under each guarantee plan, and the target insurance type corresponding to each insured object mounted under each guarantee plan.

[0135] As a possible implementation manner of an embodiment of the present disclosure, the generating module 1930 is configured to, in response to at least one guarantee plan having no entity relationship with each insured object not existing in any one entity relationship sub-model, determine whether the target insurance types to be selected corresponding to the insured objects are the same; in response to the target insurance types to be selected corresponding to the insured objects being the same, according to the product requirements, determine the target insurance type corresponding to at least one insured object from a plurality of candidate insurance types adapted to at least one insured object; and generate a target insurance product corresponding to any one entity relationship sub-model according to at least one insured object and the target insurance type corresponding to at least one insured object.

[0136] As a possible implementation manner of an embodiment of the present disclosure, the insurance product generating device 1900 further includes: a fourth determination module.

[0137] Wherein, the fourth determination module is configured to, in response to the target insurance types to be selected corresponding to the insured objects being different, according to the product requirements, determine the target insurance type corresponding to any one insured object from a plurality of candidate insurance types adapted to any one insured object; and generate a target insurance product corresponding to any one entity relationship sub-model according to each insured object and the target insurance type corresponding to each insured object.

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

[0139] The generating device for insurance products according to the embodiments of the present disclosure screens entity relationship sub-models that match product requirements from the target entity relationship model, and generates at least one target insurance product based on at least one entity relationship sub-model and product requirements, thereby realizing the flexible generation of corresponding insurance products according to different product requirements through an automated process, improving the overall efficiency, avoiding the limitations of traditional fixed templates, and meeting the diverse needs of different customer groups; in addition, the target entity relationship model decomposes the data structure of insurance products into multiple entity relationship sub-models, and each entity relationship sub-model can be used independently or in combination, improving the reusability of the data structure and reducing the cost of repeated development.

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

[0141] Wherein, the electronic device includes:

[0142] A processor;

[0143] A memory for storing executable instructions of the processor;

[0144] Wherein, the processor is configured to execute instructions to implement the method for generating insurance products proposed in any of the foregoing embodiments.

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

[0146] A memory 2010 and a processor 2020, a bus 2030 connecting different components (including the memory 2010 and the processor 2020), and the memory 2010 stores a computer program, and when the processor 2020 executes the program, the method for generating insurance products according to the embodiments of the present disclosure is implemented.

[0147] Bus 2030 represents one or more of several types of bus architectures, including a memory bus or memory controller, a peripheral bus, an Accelerated Graphics Port, a processor bus, or a local bus using any of the several bus architectures. By way of example, and not limitation, such architectures can include 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.

[0148] Electronic device 2000 typically includes a variety of computer-readable media. Such media can be any available media that can be accessed by electronic device 2000, including both volatile and nonvolatile media, removable and non-removable media.

[0149] Memory 2010 can also include computer-system-readable media in the form of volatile memory, such as random access memory (RAM) 2040 and / or cache memory 2050. Server 2000 can further include other removable / non-removable, volatile / nonvolatile computer system storage media. By way of example only, storage system 2060 can be used for reading from and writing to non-removable, nonvolatile magnetic media ( Figure 20 not shown and typically called a "hard disk drive"). Although Figure 20 not shown in FIG. 1, a disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from and writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) can be provided. In such cases, each drive can be connected to bus 2030 by one or more data media interfaces. Memory 2010 can include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of the embodiments of the present disclosure.

[0150] A program / utility 2080 having a set (at least one) of program modules 2070 can be stored, for example, in memory 2010. Such program modules 2070 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may include an implementation of a network environment. Program modules 2070 generally carry out the functions and / or methods of the embodiments described herein.

[0151] The electronic device 2000 can also communicate with one or more external devices 2090 (such as a keyboard, a pointing device, a display 2091, etc.), and can also communicate with one or more devices that enable a user to interact with the electronic device 2000, and / or communicate with any device that enables the electronic device 2000 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 2092. Moreover, the electronic device 2000 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 2093. As shown in the figure, the network adapter 2093 communicates with other modules of the electronic device 2000 through the bus 2030. 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 2000, 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.

[0152] The processor 2020 executes various functional applications and data processing by running programs stored in the memory 2010.

[0153] 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, and details are not described herein again.

[0154] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory including instructions, and 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 above 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, an optical data storage device, etc.

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

[0156] Those skilled in the art will readily think 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, which follow the general principles of the present disclosure and include common general knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the following claims.

[0157] 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 limited only 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 obtained; wherein the target entity relationship model is used to represent the data structure of multiple insurance products; According to the product requirements in the insurance product generation request, determining at least one entity relationship sub-model matching the product requirements from the target entity relationship model; At least one target insurance product is generated based on the at least one entity-relationship sub-model and the product requirements.

2. The method according to claim 1, characterized in that Each of the entity-relationship sub-models includes at least one insurance subject, and generating at least one target insurance product based on the at least one entity-relationship sub-model and the product requirements includes: 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; A target insurance product corresponding to any of the entity relationship sub-models is generated according to the product demand, the at least one insurance subject, and the mounting relationship between at least one protection plan corresponding to each of the insurance subjects.

3. The method according to claim 2, characterized in that The generating a target insurance product corresponding to any entity relationship sub-model according to the product demand, the at least one insurance subject, and the mounting relationship between each insurance subject and the corresponding at least one protection plan includes: In response to at least one protection plan being mounted under the corresponding insurance subject indicative of each of the mounting relationships, determining whether the at least one protection plan corresponding to each of the insurance subjects is the same; In response to at least one protection plan corresponding to each of the insurance objects being the same, according to the product requirements, a target insurance type under the at least one protection plan is determined from a plurality of candidate insurance types adapted to the at least one protection plan; wherein the target insurance type includes at least one target insurance item; A target insurance product corresponding to any entity relationship sub-model is generated according to each of the insured objects, at least one protection plan corresponding to each of the insured objects, and a target insurance type under the at least one protection plan.

4. The method according to claim 3, characterized in that The method further comprises: In response to the at least one protection plan corresponding to each of the insured objects being different, for any insured object, according to the product requirements, determining, from a plurality of candidate insurance types adapted to the at least one protection plan corresponding to the any insured object, a target insurance type under the at least one protection plan corresponding to the any insured object; A target insurance product corresponding to any entity relationship sub-model is generated according to each of the insured objects, at least one protection plan corresponding to each of the insured objects, and a target insurance type under at least one protection plan corresponding to each of the insured objects.

5. The method according to claim 2, characterized in that: The generating a target insurance product corresponding to any entity relationship sub-model according to the product demand, the at least one insurance subject, and the mounting relationship between each insurance subject and the corresponding at least one protection plan includes: In response to each of the mounting relationships indicating that at least one insurance subject is mounted under each of the protection plans, determining whether the target insurance types to be selected corresponding to each of the insurance subjects mounted under any of the protection plans are the same; In response to the target insurance types corresponding to the insured objects mounted under any protection plan being the same, according to the product requirements, determining the target insurance type corresponding to the at least one insured object mounted under any protection plan from a plurality of candidate insurance types adapted to the at least one insured object mounted under any protection plan; A target insurance product corresponding to any of the entity relationship sub-models is generated according to each of the protection plans, at least one insurance subject under each of the protection plans, and a target insurance type corresponding to at least one insurance subject attached to each of the protection plans.

6. The method according to claim 5, characterized in that The method further comprises: In response to the different target insurance types to be selected corresponding to the various insurance objects mounted under any protection plan, according to the product requirements, determine the target insurance type corresponding to any insurance object mounted under any protection plan from a plurality of candidate insurance types adapted to any insurance object mounted under any protection plan; A target insurance product corresponding to any entity relationship sub-model is generated according to each of the protection plans, at least one insurance subject under each of the protection plans, and the target insurance types corresponding to each of the insurance subjects attached to each of the protection plans.

7. The method according to claim 2, characterized in that The generating at least one target insurance product based on the at least one entity-relationship sub-model and the product requirement comprises: In response to the absence of at least one protection plan having an entity relationship with each of the insured objects in any entity-relationship sub-model, determining whether the target insurance types to be selected corresponding to each of the insured objects are the same; In response to the target insurance types to be selected corresponding to the respective insurance objects being the same, determining the target insurance type corresponding to the at least one insurance object from a plurality of candidate insurance types adapted to the at least one insurance object according to the product requirements; A target insurance product corresponding to any one of the entity-relationship sub-models is generated according to the at least one insurance subject and the target insurance type corresponding to the at least one insurance subject.

8. The method according to claim 7, characterized in that The method further comprises: In response to the different target insurance types to be selected corresponding to the respective insurance objects, according to the product requirements, the target insurance type corresponding to any insurance object is determined from a plurality of candidate insurance types adapted to any insurance object; According to each of the insured objects and the target insurance types corresponding to each of the insured objects, a target insurance product corresponding to any of the entity relationship sub-models is generated.

9. The method according to any one of claims 1 to 8, characterized in that The step of determining at least one entity relationship sub-model matching the product requirement from the target entity relationship model according to the product requirement in the insurance product generation request includes: 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 at least one 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: An acquisition module, configured 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 represent a data structure of multiple insurance products; A first determination module, configured to determine, according to the product requirements in the insurance product generation request, at least one entity relationship sub-model matching the product requirements from the target entity relationship model; A generation module is used to generate at least one target insurance product based on the at least one entity-relationship sub-model and the product requirements.

Images