Insurance product issuing method and device based on target release package, equipment and medium

Abstract

The invention discloses an insurance product issuing method and device based on a target release package, equipment and a medium. The method comprises the following steps: a product configuration subsystem analyzes an insurance product to obtain at least one release package demand matched with the insurance product; judging whether target production deployment matched with each release package demand exists in the touch surface subsystem or not; after determining that each release package demand has matched target production deployment through the touch surface subsystem, obtaining a target release package matched with each target production deployment and sending the target release package to a product configuration subsystem; and obtaining a target issuing page based on each target issuing package and the insurance product through the product configuration subsystem. Through the technical scheme of the invention, the issuing operation for the insurance product can be realized, and the issuing efficiency and the disaster recovery capability of the issuing operation are improved.

Description

Technical Field

[0001] This invention relates to the field of data processing, and in particular to a method, apparatus, device, and medium for issuing insurance products based on target release packages. Background Technology

[0002] From the completion of product configuration to the final issuance of an insurance policy, the process involves three core areas: product configuration, channel issuance configuration, and touch-screen sales, forming a complete insurance policy issuance business chain. The specific process is as follows: In the product configuration area, the system needs to meet the requirements of the upstream product development platform and complete the full-dimensional configuration of insurance product parameters and related information to ultimately form a complete insurance product with comprehensive information. After entering the channel issuance configuration area, each channel's issuance system builds its own issuance process based on the configured insurance product information. In the touch-screen sales area, each channel's touch-screen system executes the insurance application and issuance operation according to the corresponding sales strategy and archives the issuance data in the database.

[0003] Under the existing insurance product issuance technology solution, the process heavily relies on collaborative releases by multiple teams, including product configuration teams, channel issuance teams, and sales teams. The connections between these teams are cumbersome and highly interconnected, significantly reducing the efficiency of insurance product issuance. Furthermore, the issuance process generally relies on manual intervention, and document transfer between stages largely depends on offline transmission or manual synchronization, further lowering efficiency. More importantly, the product configuration system is highly coupled with the various sales systems, with multiple systems generally depending on the same core issuance service, creating a significant single point of failure risk: if this core service fails, it will directly paralyze the issuance functions of all dependent systems, rendering insurance issuance unavailable on a large scale and resulting in extremely poor system disaster recovery capabilities. This not only interrupts normal insurance sales and issuance operations but also leads to significant premium income losses for insurance companies.

[0004] In summary, existing insurance product issuance methods suffer from poor issuance efficiency and inadequate disaster recovery capabilities. Summary of the Invention

[0005] This invention provides a method, apparatus, equipment, and medium for issuing insurance products based on target release packages, which can solve the problems of poor issuance efficiency and disaster recovery capability in existing insurance product issuance methods.

[0006] In a first aspect, embodiments of the present invention provide a method for issuing insurance products based on a target release package, executed by an issuance system configured with a product configuration subsystem and a touch interface subsystem, the method comprising:

[0007] The product configuration subsystem parses the insurance product to obtain at least one release package requirement that matches the insurance product;

[0008] In the touch surface subsystem, it is determined whether there is a target production deployment that matches the requirements of each release package. The target production deployment is a pre-configured business execution unit adapted to the target release package.

[0009] After determining that there is a matching target production deployment for each release package requirement through the touch surface subsystem, the target release package that matches each target production deployment is obtained and sent to the product configuration subsystem;

[0010] The product configuration subsystem generates the target order page based on each target release package and the insurance product.

[0011] Secondly, embodiments of the present invention provide an insurance product issuance device based on a target release package, executed by an issuance system configured with a product configuration subsystem and a touch interface subsystem. The device includes:

[0012] The order page parsing module is used by the product configuration subsystem to parse insurance products and obtain at least one release package requirement that matches the insurance product.

[0013] The production deployment matching module is used to determine in the touch surface subsystem whether there is a target production deployment that matches the requirements of each release package. The target production deployment is a pre-configured business execution unit adapted to the target release package.

[0014] The target release package acquisition module is used to acquire the target release package that matches each target production deployment after the touch surface subsystem determines that there is a matching target production deployment for each release package requirement and send it to the product configuration subsystem.

[0015] The order generation module is used to obtain the target order generation page based on each target release package and the insurance product through the product configuration subsystem.

[0016] Thirdly, embodiments of the present invention provide an electronic device, the electronic device comprising:

[0017] At least one processor; and

[0018] A memory communicatively connected to the at least one processor; wherein,

[0019] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform an insurance product issuance method based on a target release package as described in any embodiment of the present invention.

[0020] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing computer instructions, which are used to cause a processor to execute and implement a method for issuing insurance products based on a target release package as described in any embodiment of the present invention.

[0021] The technical solution of this invention involves parsing an insurance product through a product configuration subsystem to obtain at least one release package requirement matching the insurance product. Then, in the touch interface subsystem, it is determined whether there is a target production deployment matching each release package requirement. After confirming that each release package requirement has a matching target production deployment, the touch interface subsystem obtains the target release package matching each target production deployment and sends it to the product configuration subsystem. Finally, the product configuration subsystem obtains the target policy page based on each target release package and the insurance product. This solves the problems of poor policy issuance efficiency and disaster recovery capability in existing insurance product policy issuance methods, realizing policy issuance operations for insurance products and improving the policy issuance efficiency and disaster recovery capability.

[0022] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a flowchart of an insurance product issuance method based on a target release package according to Embodiment 1 of the present invention;

[0025] Figure 2 This is a flowchart of an insurance product issuance method based on a target release package according to Embodiment 2 of the present invention;

[0026] Figure 3 This is a schematic diagram of the structure of an insurance product issuance device based on a target release package according to Embodiment 3 of the present invention;

[0027] Figure 4 This is a schematic diagram of the structure of an electronic device that implements an insurance product issuance method based on a target release package according to an embodiment of the present invention. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, any variations of the terms "comprising" and "having" are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] Example 1

[0031] Figure 1 This is a flowchart of an insurance product issuance method based on a target release package provided in Embodiment 1 of the present invention. This embodiment is applicable to the situation of issuing insurance products based on target release packages. The method can be executed by an insurance product issuance device based on a target release package. The insurance product issuance device based on a target release package can be implemented in hardware and / or software. The insurance product issuance device based on a target release package can be configured in an issuance system consisting of a product configuration subsystem and a touch interface subsystem.

[0032] like Figure 1 As shown, the method includes:

[0033] S110. The product configuration subsystem parses the insurance product and obtains at least one release package requirement that matches the insurance product.

[0034] Specifically, after receiving an insurance product, the product configuration subsystem first initiates a structured parsing process to extract and verify core information contained in the insurance product, including: insurance product type (e.g., life insurance, property insurance, health insurance), business scenario (e.g., individual insurance application, group insurance underwriting, renewal issuance), customer insurance requirement parameters (e.g., coverage amount, coverage period, insured population, payment method), and transaction attributes (e.g., premium amount, payment method, application channel identifier). The type and specific data of this core information can be set and adjusted by the insurance company according to actual business needs (e.g., different product line rules, regulatory requirements). Then, a comparative analysis is performed based on preset release package requirement matching rules to ultimately obtain at least one release package requirement matching the insurance product. These preset release package requirement matching rules can be set by the user according to the actual implementation scenario and can be based on keyword filtering, file format filtering, or other matching rules. The release package requirement is defined as: rules specifying the functional scope, applicable scenarios, and data specifications of the required release package to meet the business processing requirements corresponding to the insurance product.

[0035] S120. In the touch surface subsystem, determine whether there is a target production deployment that matches the requirements of each release package.

[0036] The target production deployment is a pre-configured business execution unit adapted to the insurance target release package, specifically designed to carry out business implementation in specific stages of the entire insurance policy issuance process; furthermore, the target release package includes: business function information, rule configuration files, H5 function pages, and core interactive data.

[0037] Furthermore, the business function information is used to clarify the specific operations to be performed in the business process, such as obtaining insured customer information, querying insurance product underwriting rules, verifying insured qualifications, calculating premiums, verifying payment information, and generating electronic policies; the rule configuration file is used to define the execution specifications and data processing requirements of the business functions, such as filling data into the specified position of the template in A format; the H5 function page is used to provide a visual interface for business interaction; and the core interaction data is used to support the specific data for the implementation of business functions.

[0038] Specifically, determining whether there is a target production deployment that matches the requirements of each release package in the touch surface subsystem includes: obtaining at least one pre-configured production deployment in the touch surface subsystem, and obtaining the business function information of the release package that matches each production deployment; determining whether there is a production deployment whose business function information matches the requirements of the release package; if they match, determining that the production deployment that matches the requirements of the release package is the target production deployment.

[0039] Specifically, determining whether a target production deployment matching the requirements of each release package exists within the touch surface subsystem includes the following steps: First, the touch surface subsystem obtains at least one pre-configured production deployment within the system. Each production deployment integrates the interface adaptation logic of its corresponding dedicated sample project, i.e., standardized interface adaptation for the product configuration system and interface adaptation for the touch surface system itself. Simultaneously, the business function information of the release package matched by each production deployment is extracted. Second, the business function information contained in the current release package requirements is compared with the extracted business function information associated with each production deployment to determine consistency. Third, if the business function information of a certain production deployment is completely consistent with the business function of the release package requirements, then the production deployment is determined to be the target production deployment matching the release package requirements. It can independently carry out the execution of the corresponding business function without relying on the collaboration of other systems.

[0040] S130. After determining that there is a matching target production deployment for each release package requirement through the touch surface subsystem, the target release package that matches each target production deployment is obtained and sent to the product configuration subsystem.

[0041] The process of obtaining a target release package that matches each target production deployment and sending it to the product configuration subsystem includes: triggering the target production deployment to obtain a production target release package that matches the target production deployment; performing an integrity check on the production target release package; and, after the check passes, determining the production target release package as the target release package and sending it to the product configuration subsystem.

[0042] S140. The product configuration subsystem obtains the target order page based on each target release package and the insurance product.

[0043] The process of obtaining the target policy page through the product configuration subsystem based on each target release package and the insurance product includes: parsing each target release package to obtain the H5 functional page, core interactive data, business function information, and rule configuration file of each target release package; filling the core interactive data and business function information of the target release package into the H5 functional page of the target release package based on the rule configuration file of the target release package to obtain the target result page matching each target release package; and encapsulating each target result page based on the insurance product to obtain the target policy page.

[0044] In one specific implementation of this embodiment, the product configuration subsystem generates a target order page based on each target release package and the insurance product. This includes: first, performing structured parsing on each target release package to extract the corresponding H5 functional page, core interactive data, business function information, and rule configuration file. Then, according to the rule configuration file of the target release package, and following preset format requirements and field mapping logic, filling the execution results corresponding to the core interactive data and business function information into designated locations on the H5 functional page, completing the integration of data and interface, and forming a target result page adapted to the functions of each target release package, ensuring the accuracy and standardization of page data display. Finally, based on the core information in the insurance product, each target result page undergoes unified encapsulation, integrating page layout, standardizing data presentation, and supplementing necessary metadata for the order page, ultimately forming a target order page that meets business scenario requirements and can be directly used for subsequent processing. The entire process requires no multi-team collaboration, relying on independent deployment and standardized configuration to achieve efficient order page generation.

[0045] The technical solution of this invention involves parsing an insurance product through a product configuration subsystem to obtain at least one release package requirement matching the insurance product. Then, in the touch interface subsystem, it is determined whether there is a target production deployment that matches each release package requirement. After confirming that each release package requirement has a matching target production deployment, the touch interface subsystem obtains the target release package matching each target production deployment and sends it to the product configuration subsystem. Finally, the product configuration subsystem obtains the target order page based on each target release package and the insurance product, thus realizing the order issuance operation for the insurance product and improving the order issuance efficiency and disaster recovery capability.

[0046] Example 2

[0047] Figure 2 This is a flowchart of an insurance product issuance method based on a target release package, provided in Embodiment 2 of the present invention. This embodiment is a refinement based on the above embodiment. Specifically, this embodiment supplements the method for determining whether there is a target production deployment that matches the requirements of each release package in the touch surface subsystem.

[0048] like Figure 2 As shown, the method includes:

[0049] S210. The product configuration subsystem analyzes the insurance product and obtains at least one release package requirement that matches the insurance product.

[0050] S220. In the touch surface subsystem, determine whether there is a target production deployment that matches the requirements of each release package.

[0051] If at least one release package requirement does not have a matching target production deployment, then execute S230;

[0052] If the touch surface subsystem determines that there is a matching target production deployment for each release package requirement, then execute S250.

[0053] S230. The release package requirements are parsed through the touch surface subsystem to obtain the requirement port, requirement sample and requirement touch surface that match the release package requirements, and then S240 is executed.

[0054] The demand port is used to define the standardized interface port configuration for the interaction between the release package demand and the system. It is a key entry point for realizing cross-system data transmission, such as the API port for obtaining data and the communication port for submitting requests. The demand sample refers to the basic function sample template corresponding to the release package demand. The demand touchpoint refers to the specific business channel touchpoint corresponding to the release package demand, such as the online channel touchpoint for customers and the offline touchpoint for partners.

[0055] S240. The touch surface subsystem performs a production deployment creation operation based on the demand port, demand sample and demand touch surface to obtain a target production deployment that matches the release package demand, and then executes S250.

[0056] Specifically, the process of creating a production deployment based on the requirement port, requirement sample, and requirement interface by the interface subsystem to obtain a target production deployment matching the release package requirements includes: obtaining a pre-configured sample project corresponding to the requirement sample, processing the requirement interface and requirement port through the sample project to obtain an interface configuration result; performing a fusion verification on the interface configuration result and requirement sample, and, after passing the verification, performing a production deployment creation operation based on the interface configuration result, requirement sample, and requirement interface to obtain a target production deployment matching the release package requirements.

[0057] Furthermore, the sample project is used to connect the requirement sample, requirement interface, and requirement port, integrate the adaptation logic of the three and perform standardization processing to generate an interface configuration result that can support the creation of production deployment. For example, if there is a requirement sample for querying product inventory, the sample project corresponding to the requirement sample can be: first, receive the requirement interface for offline contact with partners corresponding to the requirement sample, and the requirement port for querying inventory, and then integrate the interaction rules of the offline interface and the communication protocol of the API port through built-in adaptation logic, match them with the function template for querying product inventory, and finally generate an interface configuration result that meets the requirements of the release package.

[0058] It should be noted that in this embodiment, the sample project can be pre-set by the user in a pre-configured sample project library and obtained by the system through matching based on keywords or sample numbers, or it can be edited and generated by the user in real time according to the requirements of the release package. This embodiment does not restrict the source of the sample project.

[0059] The fusion verification includes: whether the interface configuration result fully covers the requirement sample, whether it is fully compatible with the interaction rules of the requirement interface, and whether it meets the communication standards of the requirement port.

[0060] Based on the above steps, after the verification is passed, the touch surface subsystem starts the automated production deployment creation process, which deeply integrates the interface configuration results, the functional template of the requirement sample, and the adaptation characteristics of the requirement touch surface, builds an independent operating environment, encapsulates the core business modules, configures the interface interaction channel, and finally generates a production deployment unit that can independently carry the corresponding business functions. This unit is the target production deployment that is precisely matched with the requirements of the release package and can seamlessly respond to subsequent business call requests.

[0061] Those skilled in the art should understand that the technology of building a pre-configured business execution unit to adapt to the requirements of the release package, given the known requirements port, requirements sample, requirements interface and sample project, is a mature existing technology. This embodiment will not elaborate on its building principle and process.

[0062] S250: Obtain the target release package that matches the production deployment of each target and send it to the product configuration subsystem.

[0063] S260. The product configuration subsystem obtains the target order page based on each target release package and the insurance product.

[0064] The technical solution of this invention involves parsing an insurance product through a product configuration subsystem to obtain at least one release package requirement matching the insurance product. Then, in the touch surface subsystem, it is determined whether there is a target production deployment matching each release package requirement. If at least one release package requirement does not have a matching target production deployment, the touch surface subsystem parses the release package requirement to obtain a requirement port, requirement sample, and requirement touch surface matching the release package requirement. Then, the touch surface subsystem performs a production deployment creation operation based on the requirement port, requirement sample, and requirement touch surface to obtain a target production deployment matching the release package requirement. After confirming that each release package requirement has a matching target production deployment, the touch surface subsystem obtains the target release package matching each target production deployment and sends it to the product configuration subsystem. Finally, the product configuration subsystem obtains the target order page based on each target release package and the insurance product, thus realizing the order issuance operation for the insurance product and improving the order issuance efficiency and disaster recovery capability.

[0065] Example 3

[0066] Figure 3 This is a schematic diagram of an insurance product issuance device based on a target release package, provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes:

[0067] The order page parsing module 310 is used by the product configuration subsystem to parse the insurance product and obtain at least one release package requirement that matches the insurance product.

[0068] The production deployment matching module 320 is used to determine in the touch surface subsystem whether there is a target production deployment that matches the requirements of each release package. The target production deployment is a pre-configured business execution unit adapted to the target release package.

[0069] The target release package acquisition module 330 is used to acquire the target release package that matches each target production deployment after the touch surface subsystem determines that there is a matching target production deployment for each release package requirement and send it to the product configuration subsystem.

[0070] The order generation module 340 is used to obtain the target order generation page based on each target release package and the insurance product through the product configuration subsystem.

[0071] The technical solution of this invention involves parsing an insurance product through a product configuration subsystem to obtain at least one release package requirement matching the insurance product. Then, in the touch interface subsystem, it is determined whether there is a target production deployment that matches each release package requirement. After confirming that each release package requirement has a matching target production deployment, the touch interface subsystem obtains the target release package matching each target production deployment and sends it to the product configuration subsystem. Finally, the product configuration subsystem obtains the target order page based on each target release package and the insurance product, thus realizing the order issuance operation for the insurance product and improving the order issuance efficiency and disaster recovery capability.

[0072] Based on the above embodiments, the production deployment matching module 320 includes:

[0073] The production deployment acquisition unit is used to acquire at least one pre-configured production deployment in the touch surface subsystem and to acquire the business function information of the release package that matches each production deployment.

[0074] The production deployment judgment unit is used to determine whether there is a production deployment that matches the business function information and the requirements of the release package;

[0075] The production deployment determination unit is used to determine, if a match is found, the production deployment that matches the requirements of the release package as the target production deployment.

[0076] Based on the above embodiments, the production deployment matching module 320 is further configured to: after determining in the touch surface subsystem whether there is a target production deployment that matches the requirements of each release package respectively, if there is at least one release package requirement that does not have a matching target production deployment, then the touch surface subsystem parses the release package requirement to obtain the requirement port, requirement sample and requirement touch surface that match the release package requirement; and the touch surface subsystem performs a production deployment creation operation based on the requirement port, requirement sample and requirement touch surface to obtain the target production deployment that matches the release package requirement.

[0077] Based on the above embodiments, the production deployment matching module 320 is further configured to: obtain a pre-configured sample project corresponding to the requirement sample, and process the requirement interface and requirement port through the sample project to obtain the interface configuration result; perform fusion verification on the interface configuration result and the requirement sample, and after the verification is passed, perform a production deployment creation operation based on the interface configuration result, the requirement sample and the requirement interface to obtain the target production deployment that matches the release package requirement.

[0078] Based on the above embodiments, the order module 340 includes:

[0079] The release package parsing unit is used to parse each target release package to obtain the H5 functional pages, core interactive data, business function information and rule configuration files of each target release package;

[0080] The information filling unit is used to fill the core interactive data and business function information of the target release package into the H5 function page of the target release package based on the rule configuration file of the target release package, so as to obtain the target result page matching each target release package;

[0081] The encapsulation unit is used to encapsulate each target result page based on the insurance product to obtain the target order page.

[0082] Based on the above embodiments, the target release package acquisition module 330 includes:

[0083] A triggering unit is used to trigger the target production deployment to obtain a production target release package that matches the target production deployment;

[0084] The release package verification unit is used to perform integrity verification on the production target release package, and after the verification is passed, the production target release package is identified as the target release package and sent to the product configuration subsystem.

[0085] The insurance product issuance device based on a target release package provided in this embodiment of the invention can execute an insurance product issuance method based on a target release package provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method.

[0086] Example 4

[0087] Figure 4 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0088] like Figure 4As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded into the RAM 13 from storage unit 18. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0089] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0090] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, central processing unit (CPU), graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as an insurance product issuance method based on a target release package.

[0091] Accordingly, the method includes:

[0092] The product configuration subsystem parses the insurance product to obtain at least one release package requirement that matches the insurance product;

[0093] In the touch surface subsystem, it is determined whether there is a target production deployment that matches the requirements of each release package. The target production deployment is a pre-configured business execution unit adapted to the target release package.

[0094] After determining that there is a matching target production deployment for each release package requirement through the touch surface subsystem, the target release package that matches each target production deployment is obtained and sent to the product configuration subsystem;

[0095] The product configuration subsystem generates the target order page based on each target release package and the insurance product.

[0096] In some embodiments, a method for issuing insurance products based on a target distribution package can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the method for issuing insurance products based on a target distribution package described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to execute a method for issuing insurance products based on a target distribution package by any other suitable means (e.g., by means of firmware).

[0097] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0098] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0099] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0100] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0101] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0102] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0103] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and no limitation is imposed herein.

Claims

1. A method for issuing insurance products based on target release packages, executed by an issuance system configured with a product configuration subsystem and a touch interface subsystem, characterized in that, include: The product configuration subsystem parses the insurance product to obtain at least one release package requirement that matches the insurance product; In the touch surface subsystem, it is determined whether there is a target production deployment that matches the requirements of each release package. The target production deployment is a pre-configured business execution unit adapted to the target release package. After determining that there is a matching target production deployment for each release package requirement through the touch surface subsystem, the target release package that matches each target production deployment is obtained and sent to the product configuration subsystem; The product configuration subsystem generates the target order page based on each target release package and the insurance product.

2. The method according to claim 1, characterized in that, The target release package includes: business function information, rule configuration files, H5 function pages, and core interactive data.

3. The method according to any one of claims 1-2, characterized in that, The touch interface subsystem determines whether there are target production deployments that match the requirements of each release package, including: Obtain at least one pre-configured production deployment in the touch surface subsystem, and obtain the business function information of the release package that matches each production deployment; Determine if there is a production deployment that matches the requirements of the release package; If a match is found, the production deployment that matches the requirements of the release package is determined as the target production deployment.

4. The method according to claim 1, characterized in that, After determining whether there is a target production deployment that matches the requirements of each release package in the touch surface subsystem, the following steps are also included: If at least one release package requirement does not have a matching target production deployment, the release package requirement is parsed through the touch surface subsystem to obtain the requirement port, requirement sample and requirement touch surface that match the release package requirement; The touch surface subsystem performs a production deployment creation operation based on the requirement port, requirement sample, and requirement touch surface to obtain a target production deployment that matches the release package requirements.

5. The method according to claim 4, characterized in that, The touch surface subsystem performs a production deployment creation operation based on the demand port, demand sample, and demand touch surface to obtain a target production deployment that matches the release package requirements, including: Obtain a pre-configured sample project corresponding to the requirement sample, and process the requirement interface and requirement port through the sample project to obtain the interface configuration result; The interface configuration results and requirement samples are fused and verified. After the verification is passed, the production deployment creation operation is performed based on the interface configuration results, requirement samples and requirement interfaces to obtain the target production deployment that matches the requirements of the release package.

6. The method according to any one of claims 1-2, characterized in that, The product configuration subsystem generates a target policy page based on each target release package and the insurance product, including: Parse each target release package to obtain the H5 functional pages, core interactive data, business function information, and rule configuration files of each target release package; Based on the rule configuration file of the target release package, the core interactive data and business function information of the target release package are filled into the H5 function page of the target release package to obtain the target result page matching each target release package; Based on the insurance product, each target result page is encapsulated to obtain the target order page.

7. The method according to claim 1, characterized in that, Obtain the target release package that matches each target production deployment and send it to the product configuration subsystem, including: Trigger the target production deployment to obtain a production target release package that matches the target production deployment; The production target release package is subjected to integrity verification, and after the verification is passed, the production target release package is identified as the target release package and sent to the product configuration subsystem.

8. An insurance product issuance device based on a target release package, executed by an issuance system configured with a product configuration subsystem and a touch interface subsystem, characterized in that, include: The order page parsing module is used by the product configuration subsystem to parse insurance products and obtain at least one release package requirement that matches the insurance product. The production deployment matching module is used to determine in the touch surface subsystem whether there is a target production deployment that matches the requirements of each release package. The target production deployment is a pre-configured business execution unit adapted to the target release package. The target release package acquisition module is used to acquire the target release package that matches each target production deployment after the touch surface subsystem determines that there is a matching target production deployment for each release package requirement and send it to the product configuration subsystem. The order generation module is used to obtain the target order generation page based on each target release package and the insurance product through the product configuration subsystem.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform a method for issuing insurance products based on a target release package, as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute and implement the insurance product issuance method based on a target release package according to any one of claims 1-7.

Images