Insurance policy life cycle management method and device, electronic equipment and storage medium
By managing the policy lifecycle through asynchronous message queues and unified message formats, the low efficiency and poor reliability of the existing system in high-concurrency scenarios are resolved, and efficient and reliable policy processing is achieved.
Patent Information
- Application Number
- CN202510839733.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-20
- Publication Date
- 2025-10-03
AI Technical Summary
The existing insurance policy management system has low processing efficiency and is prone to crashing in high-concurrency scenarios. It also lacks unified message management, resulting in message loss, duplication, or delays, affecting the accuracy and reliability of insurance policy processing.
Adopting asynchronous message queue technology and unified message format, through message encapsulation and subscription processing of insurance application, underwriting results, underwriting operation and other links, combined with monitoring and alarm mechanism, efficient management of insurance policy life cycle is achieved.
It improves the processing efficiency and accuracy of the policy life cycle, reduces system delays and crash risks, and ensures the reliability of message delivery and system stability.
Smart Images

Figure CN120746728A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data processing technology, and in particular to a policy lifecycle management method, device, electronic device and storage medium. Background Art
[0002] In the insurance industry, both in the financial and healthcare sectors, policy lifecycle management is a core business process, encompassing multiple stages, including application, underwriting, coverage, claims settlement, and renewal. Currently, several policy management systems exist on the market, but these systems commonly suffer from the following issues when handling the policy lifecycle: First, processing efficiency is low. In high-concurrency scenarios, the system may experience delays or crashes due to insufficient processing power. Second, there is often a lack of unified message management, which can lead to message loss, duplication, or delays during delivery. These issues can impact the accuracy and reliability of policy processing. Summary of the Invention
[0003] The purpose of the present invention is to provide a policy lifecycle management method, device, electronic device and storage medium to solve the technical problems of low processing efficiency, low accuracy and poor reliability in the prior art.
[0004] The technical solution of the present invention is as follows, which provides a policy lifecycle management method, comprising:
[0005] After receiving the insurance application submitted by the user, encapsulate the insurance information of the insurance application into a first message in a preset message format, and send the first message to the insurance application topic in the message queue;
[0006] subscribing to the insurance application topic, consuming the first message from the message queue, performing underwriting processing based on the insurance information in the first message to obtain an underwriting result, encapsulating the underwriting result into a second message in the preset message format, and sending the second message to the underwriting result topic in the message queue;
[0007] Subscribe to the underwriting result topic, consume the second message from the message queue, and determine whether to perform an underwriting operation based on the underwriting result in the second message. If an underwriting operation is performed, after the underwriting operation is completed, encapsulate the policy status update message into a third message in a preset message format, and send the third message to the policy status update topic in the message queue.
[0008] Furthermore, the policy lifecycle management method also includes: subscribing to the policy status update topic, consuming the third message from the message queue, and if the policy status update message in the third message includes the policy status being updated from the policy draft to the formal policy, the premium payment process is triggered.
[0009] Furthermore, the policy lifecycle management method also includes: after receiving the claim application information submitted by the user, encapsulating the claim application information into a fourth message in the preset message format, sending the fourth message to the claim application topic in the message queue, subscribing to the claim application topic, consuming the fourth message from the message queue, and reviewing the claim application information in the fourth message. If the review is passed, the claim payment is processed.
[0010] Furthermore, the policy lifecycle management method further includes: triggering a renewal process and generating renewal reminder information at a preset time before the expiration of the policy.
[0011] Furthermore, the preset message format includes a message header and a first message of a message body, the message header includes message ID data, timestamp data, business type data, source system data, target system data, message priority data and retry count data, and the message body includes policy number data, customer information data, insurance amount data, insurance product type data and operation type data.
[0012] Furthermore, the policy lifecycle management method further includes: performing deduplication judgment based on the message ID data and the policy number data.
[0013] Furthermore, the policy lifecycle management method also includes: collecting monitoring data of the message queue, the monitoring data including throughput, delay time, accumulation data, service response time and error rate data, visually displaying the monitoring data in the form of a chart, and issuing an alarm when any indicator in the monitoring data exceeds the corresponding preset threshold; recording the processing status of the first message, the second message, the third message and the fourth message, and providing a query interface for the processing status.
[0014] Another technical solution of the present invention is as follows: a device for managing an insurance policy lifecycle is provided, comprising an application processing unit, an underwriting unit, and an insurance coverage processing unit;
[0015] The insurance processing unit is configured to, upon receiving an insurance application submitted by a user, encapsulate the insurance information of the insurance application into a first message in a preset message format, and send the first message to the insurance application topic in the message queue;
[0016] The underwriting unit is configured to subscribe to the insurance application topic, consume the first message from the message queue, perform underwriting processing based on the insurance information in the first message, obtain an underwriting result, encapsulate the underwriting result into a second message in the preset message format, and send the second message to the underwriting result topic in the message queue;
[0017] The underwriting processing unit is used to subscribe to the underwriting result topic, consume the second message from the message queue, and determine whether to perform an underwriting operation based on the underwriting result in the second message. If an underwriting operation is performed, after the underwriting operation is completed, the policy status update message is encapsulated into a third message in a preset message format, and the third message is sent to the policy status update topic in the message queue.
[0018] Another technical solution of the present invention is as follows: an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program executable by the processor, and when the processor executes the computer program, the policy lifecycle management method as described in any of the above technical solutions is implemented.
[0019] Another technical solution of the present invention is as follows: a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the policy lifecycle management method as described in any of the above technical solutions is implemented.
[0020] The beneficial effects of the present invention are: after receiving an insurance application submitted by a user, the insurance information of the insurance application is encapsulated into a first message in a preset message format, and the first message is sent to the insurance application topic in the message queue; the insurance application topic is subscribed to, the first message is consumed from the message queue, and underwriting processing is performed based on the insurance information in the first message to obtain an underwriting result, and the underwriting result is encapsulated into a second message in the preset message format, and the second message is sent to the underwriting result topic in the message queue; the underwriting result topic is subscribed to, the second message is consumed from the message queue, and it is determined whether to perform an underwriting operation based on the underwriting result in the second message. If an underwriting operation is performed, after the underwriting operation is completed, the policy status update message is encapsulated into a third message in a preset message format, and the third message is sent to the policy status update topic in the message queue; through the above technical solution, the management of the policy life cycle can be realized, the processing efficiency of the policy life cycle can be improved, and the accuracy and reliability of policy processing can be improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Figure 1 A flowchart of the insurance policy lifecycle management method provided by an embodiment of the present invention;
[0022] Figure 2 A schematic diagram of the structure of the insurance policy lifecycle management device provided by an embodiment of the present invention;
[0023] Figure 3 A schematic structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0024] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.
[0025] In the description of this application, words such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating or implying relative importance or order. In this specification, the terms "including," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.
[0026] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present invention. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute a separate or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0027] Figure 1 It is a flow chart of the policy life cycle management method of the embodiment of the present invention. It should be noted that if there is substantially the same result, the policy life cycle management method of the present invention is not based on Figure 1 The process sequence shown is limited. Figure 1 As shown, the policy lifecycle management method mainly includes the following steps:
[0028] S101, after receiving an insurance application submitted by a user, encapsulating the insurance information of the insurance application into a first message in a preset message format, and sending the first message to the insurance application topic in the message queue;
[0029] In some embodiments, asynchronous message queue technology (such as Kafka, RabbitMQ, or RocketMQ) can be used to decouple the various business processes in the policy lifecycle management. After receiving the insurance application submitted by the user, a policy draft can be generated based on the insurance application. Using asynchronous message queue technology, the insurance information in the insurance application can be encapsulated into a first message in a preset message format, and the first message can be sent to the insurance application topic in the message queue.
[0030] In an optional embodiment, the preset message format includes a message header and a first message of a message body, the message header includes message ID data, timestamp data, business type data, source system data, target system data, message priority data and retry count data, and the message body includes policy number data, customer information data, insurance amount data, insurance product type data and operation type data.
[0031] In some embodiments, JSON Schema can be used to define a preset message format, which includes a message header (Header) and a message body (Body). The above-mentioned operation type data includes insurance application, underwriting approval, claim application, etc. When all services consume messages, they are parsed and processed in a unified format. The message parser middleware can be used to standardize the reading and conversion of messages to ensure that the data format is consistent between different services. When message consumption (including the first message, the second message, the third message, and the fourth message) fails, it can retry a preset number of times (determined by the above-mentioned retry number data). If the message is still not successfully processed after multiple failures, the message will be transferred to the dead letter queue for subsequent processing by manual or automated tools. Through a unified preset message format and processing mechanism, various business messages in the policy life cycle can be processed efficiently and reliably, improving overall processing efficiency and system stability.
[0032] In an optional implementation, the policy lifecycle management method further includes: performing deduplication judgment based on the message ID data and the policy number data.
[0033] In some embodiments, message idempotence verification can be used to prevent data errors caused by repeated message consumption. For example, deduplication can be determined based on the policy number and message ID, that is, the policy number and message ID can be used to determine whether the corresponding message is consumed repeatedly.
[0034] S102: Subscribe to the insurance application topic, consume the first message from the message queue, perform underwriting based on the insurance information in the first message, obtain an underwriting result, encapsulate the underwriting result into a second message in the preset message format, and send the second message to the underwriting result topic in the message queue;
[0035] In some embodiments, underwriting is performed based on the insurance information in the first message, that is, risk assessment and approval are performed. The underwriting results include underwriting passed and underwriting failed. If the underwriting is passed, the underwriting operation is performed, otherwise the underwriting operation is not performed.
[0036] S103, subscribe to the underwriting result topic, consume the second message from the message queue, and determine whether to perform an underwriting operation based on the underwriting result in the second message. If an underwriting operation is performed, after the underwriting operation is completed, encapsulate the policy status update message into a third message in a preset message format, and send the third message to the policy status update topic in the message queue.
[0037] In an optional embodiment, the policy lifecycle management method further includes: subscribing to the policy status update topic, consuming the third message from the message queue, and triggering a premium payment process if the policy status update message in the third message includes an update of the policy status from draft to official. After the premium payment process is triggered and the user pays the premium, the policy officially takes effect.
[0038] In an embodiment of the present invention, by subscribing to the policy status update topic, a third message is consumed from the message queue. If the policy status update message in the third message includes that the policy status is updated from a policy draft to a formal policy, the premium payment process is triggered. The triggering of the premium payment process can be realized, thereby improving the reliability of the policy lifecycle management.
[0039] In an optional embodiment, the policy lifecycle management method further includes: after receiving the claim application information submitted by the user, encapsulating the claim application information into a fourth message in the preset message format, sending the fourth message to the claim application topic in the message queue, subscribing to the claim application topic, consuming the fourth message from the message queue, and reviewing the claim application information in the fourth message. If the review is passed, the claim payment is processed.
[0040] In an embodiment of the present invention, after receiving the claim application information submitted by the user, the claim application information is encapsulated into a fourth message in a preset message format, the fourth message is sent to the claim application topic in the message queue, the claim application topic is subscribed to, the fourth message is consumed from the message queue, and the claim application information in the fourth message is reviewed. If the review is passed, the claim is paid, thereby realizing the claim process and improving the reliability of the policy life cycle management.
[0041] In an optional embodiment, the policy lifecycle management method further includes: triggering a renewal process and generating renewal reminder information at a preset time before the expiration of the policy.
[0042] In some embodiments, the preset time may be one month or two months. When the user receives a renewal reminder message, he or she may choose to renew or not. If he or she chooses to renew, the renewal process will be carried out.
[0043] In some embodiments, after each stage of the insurance application stage, underwriting stage, insurance underwriting stage, payment stage, claims stage, and renewal stage is completed, the policy status can be updated through the message queue and pushed to relevant parties (such as users, customer service, risk control systems, etc.) via SMS, email, or App. By dividing the policy lifecycle into multiple independently processable stages and introducing an asynchronous messaging mechanism, an efficient and flexible policy management process can be achieved. Instead of direct calls between business modules, communication is carried out through message queues, achieving loose coupling and high availability.
[0044] In an optional embodiment, the policy lifecycle management method further includes: collecting monitoring data of the message queue, the monitoring data including throughput, delay time, accumulation data, service response time and error rate data, visually displaying the monitoring data in the form of a chart, and issuing an alarm when any indicator in the monitoring data exceeds the corresponding preset threshold; recording the processing status of the first message, the second message, the third message and the fourth message, and providing a query interface for the processing status.
[0045] In some embodiments, key indicators such as throughput, latency, accumulated data, service response time, and error rate of the message queue can be collected through monitoring tools such as Prometheus. The collected monitoring data can be displayed in the form of charts through visualization tools such as Grafana, which makes it easier for operation and maintenance personnel to understand the system operation status in real time. The processing status of each message (such as sent, consumed, processing failure, etc.) is recorded, and a query interface is provided to facilitate problem troubleshooting. When any indicator of the monitoring data exceeds the preset threshold (such as message accumulation exceeding 1,000, service response time exceeding 5 seconds, processing failure rate exceeding 1%, etc.), an alarm will be triggered and the administrator will be notified via email, SMS, enterprise WeChat, etc. Log analysis tools such as ELK (Elasticsearch, Logstash, Kibana) can be integrated to centrally manage and analyze the logs of each service, making it easier to quickly locate problems. Through real-time monitoring and alarm mechanisms, anomalies can be discovered and handled in a timely manner, improving the stability and operation and maintenance efficiency of the system.
[0046] Both the financial and medical fields involve insurance business, and insurance policies are a core component of insurance business. The policy lifecycle management method provided by an embodiment of the present invention encapsulates the insurance information of the insurance application into a first message in a preset message format and sends the first message to the Insurance Application topic in a message queue. The method subscribes to the Insurance Application topic, consumes the first message from the message queue, performs underwriting processing based on the insurance information in the first message, obtains an underwriting result, encapsulates the underwriting result into a second message in the preset message format, and sends the second message to the Underwriting Result topic in the message queue. The method subscribes to the Underwriting Result topic, consumes the second message from the message queue, and determines whether to perform an underwriting operation based on the underwriting result in the second message. If an underwriting operation is performed, after the underwriting operation is completed, encapsulates a policy status update message into a third message in a preset message format and sends the third message to the Policy Status Update topic in the message queue. This method can achieve policy lifecycle management, improve policy lifecycle processing efficiency, and enhance the accuracy and reliability of policy processing.
[0047] The insurance policy lifecycle management method provided by the embodiment of the present invention can independently deploy each module (such as modules corresponding to the insurance, underwriting, claims and other stages), and can dynamically expand the number of instances of a module according to the business load, such as increasing the number of copies of the claims service during the peak period of claims. The modules communicate through message queues, avoiding the coupling problems caused by direct calls between services in traditional systems, and integrating service registration and discovery mechanisms (such as Eureka, Nacos, Consul, etc.) to ensure dynamic discovery and load balancing of services. It can support plug-in extensions. For example, to add a third-party payment service, you only need to develop a payment service plug-in and access it through the message queue. The modular design not only improves the flexibility and maintainability of the system, but also provides a good foundation for future business expansion and system upgrades.
[0048] The insurance policy lifecycle management method provided by the embodiment of the present invention can complete the transaction operation in the local database first, and then send the message to the message queue when each module processes the business logic. The message will be confirmed only after the local transaction is successfully submitted, ensuring the atomicity of the business operation and the message sending. By introducing a distributed transaction management mechanism (such as Seata, TCC mode, etc.), data consistency between multiple systems is ensured in cross-service and cross-database scenarios. For business operations that cannot be rolled back (such as premium payment), the system adopts a compensating transaction mechanism to ensure that data consistency can be restored in abnormal situations by recording transaction logs and rollback strategies. It supports message idempotence verification to prevent data errors caused by repeated message consumption, and ensures that the policy status remains consistent in all related services through the message queue and database status synchronization mechanism. Through the above mechanism, the ultimate consistency of policy data can be guaranteed in a high-concurrency, distributed environment, avoiding business errors or disputes caused by data inconsistency.
[0049] The policy lifecycle management method provided by the embodiment of the present invention provides a unified interface for different message queue technologies, and achieves compatibility with different message middleware through the adapter mode. The system can flexibly select the message queue technology according to actual needs without modifying the core business logic. All modules can adopt RESTful API or gRPC interface, and the interface definition follows a unified specification to facilitate the access of new modules and the replacement of old modules. It supports service modules developed in multiple programming languages (such as Java, Python, Go), and achieves cross-language service compatibility through a unified message format and interface specification. It supports service version control and gray release mechanism to ensure that the normal operation of existing businesses is not affected during the system upgrade process. The system has good scalability and compatibility, can quickly adapt to business changes and the introduction of new technologies, and reduce the cost of system maintenance and upgrades.
[0050] The policy lifecycle management method provided by this embodiment of the present invention utilizes asynchronous message queue technology to effectively handle policy processing requirements in high-concurrency scenarios, reducing system latency and crash risks, and improving user experience. The introduction of a real-time monitoring and alerting system enables timely detection and resolution of system failures, reducing system maintenance costs.
[0051] The policy lifecycle management method provided in embodiments of the present invention can be constructed based on artificial intelligence (AI). This technology acquires and processes relevant data, enabling unattended AI-powered policy lifecycle management. Artificial intelligence (AI) refers to the theories, methods, technologies, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to achieve optimal results.
[0052] Fundamental AI technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interaction systems, and mechatronics. AI software technologies primarily encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.
[0053] Figure 2 FIG. 1 is a schematic diagram of the structure of the insurance policy lifecycle management device according to an embodiment of the present invention. Figure 2 As shown, the policy lifecycle management device 20 includes an insurance application processing unit 21, an underwriting unit 22, and an insurance coverage processing unit 23;
[0054] The insurance processing unit 21 is configured to, upon receiving an insurance application submitted by a user, encapsulate the insurance information of the insurance application into a first message in a preset message format, and send the first message to the insurance application topic in the message queue;
[0055] The underwriting unit 22 is configured to subscribe to the insurance application topic, consume the first message from the message queue, perform underwriting processing based on the insurance information in the first message, obtain an underwriting result, encapsulate the underwriting result into a second message in the preset message format, and send the second message to the underwriting result topic in the message queue;
[0056] The underwriting processing unit 23 is used to subscribe to the underwriting result topic, consume the second message from the message queue, and determine whether to perform an underwriting operation based on the underwriting result in the second message. If an underwriting operation is performed, after the underwriting operation is completed, the policy status update message is encapsulated into a third message in a preset message format, and the third message is sent to the policy status update topic in the message queue.
[0057] In an optional embodiment, the policy lifecycle management device 20 also includes a payment processing unit, which is used to subscribe to the policy status update topic and consume the third message from the message queue. If the policy status update message in the third message includes that the policy status is updated from a policy draft to a formal policy, the premium payment process is triggered.
[0058] In an optional embodiment, the policy lifecycle management device 20 also includes a claims unit, which is used to, after receiving the claim application information submitted by the user, encapsulate the claim application information into a fourth message in the preset message format, send the fourth message to the claim application topic in the message queue, subscribe to the claim application topic, consume the fourth message from the message queue, and review the claim application information in the fourth message. If the review is passed, the claim payment is processed.
[0059] In an optional embodiment, the policy lifecycle management device 20 further includes a renewal processing unit, which is configured to trigger a renewal process and generate renewal reminder information at a preset time before the expiration of the policy.
[0060] In an optional embodiment, the preset message format includes a message header and a first message of a message body, the message header includes message ID data, timestamp data, business type data, source system data, target system data, message priority data and retry count data, and the message body includes policy number data, customer information data, insurance amount data, insurance product type data and operation type data.
[0061] In an optional embodiment, the policy lifecycle management device 20 further includes a deduplication judgment unit, which is configured to perform deduplication judgment based on the message ID data and the policy number data.
[0062] In an optional embodiment, the policy lifecycle management device 20 also includes a monitoring unit, which is used to collect monitoring data of the message queue, and the monitoring data includes throughput, delay time, accumulation data, service response time and error rate data, and visualize the monitoring data in the form of a chart. When any indicator in the monitoring data exceeds the corresponding preset threshold, an alarm is issued; the processing status of the first message, the second message, the third message and the fourth message is recorded, and a query interface for the processing status is provided.
[0063] Figure 3 Schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Figure 3 As shown, the electronic device 30 includes a processor 31 and a memory 32 communicatively connected to the processor 31 .
[0064] The memory 32 stores program instructions for implementing the insurance policy lifecycle management method of any of the above embodiments.
[0065] The processor 31 is used to execute program instructions stored in the memory 32 to perform policy lifecycle management.
[0066] The processor 31 may also be referred to as a CPU (Central Processing Unit). The processor 31 may be an integrated circuit chip having signal processing capabilities. The processor 31 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The general-purpose processor may be a microprocessor or any conventional processor.
[0067] An embodiment of the present invention provides a storage medium, which stores program instructions that can implement all the above methods. The storage medium can be non-volatile or volatile. The program instructions can be stored in the above storage medium in the form of a software product, including several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or terminal devices such as a computer, a server, a mobile phone, and a tablet.
[0068] In the several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of modules is merely a logical function division. In actual implementation, there may be other division methods, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interface, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.
[0069] In addition, the functional modules in the various embodiments of the present invention may be integrated into one processing unit, or each module may exist physically separately, or two or more modules may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit. The above is only an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.
[0070] The above description is only an embodiment of the present invention. It should be pointed out that those skilled in the art can make improvements without departing from the creative concept of the present invention, but these improvements all fall within the scope of protection of the present invention.
Claims
1. A policy lifecycle management method, characterized in that: include: After receiving the insurance application submitted by the user, encapsulate the insurance information of the insurance application into a first message in a preset message format, and send the first message to the insurance application topic in the message queue; subscribing to the insurance application topic, consuming the first message from the message queue, performing underwriting processing based on the insurance information in the first message to obtain an underwriting result, encapsulating the underwriting result into a second message in the preset message format, and sending the second message to the underwriting result topic in the message queue; Subscribe to the underwriting result topic, consume the second message from the message queue, and determine whether to perform an underwriting operation based on the underwriting result in the second message. If an underwriting operation is performed, after the underwriting operation is completed, encapsulate the policy status update message into a third message in a preset message format, and send the third message to the policy status update topic in the message queue.
2. The policy lifecycle management method according to claim 1, characterized in that: The policy lifecycle management method also includes: subscribing to the policy status update topic, consuming the third message from the message queue, and if the policy status update message in the third message includes that the policy status is updated from a policy draft to a formal policy, triggering the premium payment process.
3. The policy lifecycle management method according to claim 2, characterized in that: The policy lifecycle management method also includes: after receiving the claim application information submitted by the user, encapsulating the claim application information into a fourth message in the preset message format, sending the fourth message to the claim application topic in the message queue, subscribing to the claim application topic, consuming the fourth message from the message queue, and reviewing the claim application information in the fourth message. If the review is passed, the claim payment is processed.
4. The policy lifecycle management method according to claim 1, characterized in that: The policy lifecycle management method further includes: triggering a renewal process and generating renewal reminder information at a preset time before the expiration of the policy.
5. The policy lifecycle management method according to claim 1, characterized in that: The preset message format includes a message header and a first message of a message body, the message header includes message ID data, timestamp data, business type data, source system data, target system data, message priority data and retry count data, and the message body includes policy number data, customer information data, insurance amount data, insurance product type data and operation type data.
6. The policy lifecycle management method according to claim 5, characterized in that: The insurance policy lifecycle management method further includes: performing deduplication judgment based on the message ID data and the insurance policy number data.
7. The policy lifecycle management method according to claim 3, characterized in that: The policy lifecycle management method also includes: collecting monitoring data of the message queue, the monitoring data including throughput, delay time, accumulation data, service response time and error rate data, visually displaying the monitoring data in the form of a chart, and issuing an alarm when any indicator in the monitoring data exceeds the corresponding preset threshold; recording the processing status of the first message, the second message, the third message and the fourth message, and providing a query interface for the processing status.
8. A policy lifecycle management device, characterized in that: It includes the insurance application processing unit, underwriting unit and insurance coverage processing unit; The insurance processing unit is configured to, upon receiving an insurance application submitted by a user, encapsulate the insurance information of the insurance application into a first message in a preset message format, and send the first message to the insurance application topic in the message queue; The underwriting unit is configured to subscribe to the insurance application topic, consume the first message from the message queue, perform underwriting processing based on the insurance information in the first message, obtain an underwriting result, encapsulate the underwriting result into a second message in the preset message format, and send the second message to the underwriting result topic in the message queue; The underwriting processing unit is used to subscribe to the underwriting result topic, consume the second message from the message queue, and determine whether to perform an underwriting operation based on the underwriting result in the second message. If an underwriting operation is performed, after the underwriting operation is completed, the policy status update message is encapsulated into a third message in a preset message format, and the third message is sent to the policy status update topic in the message queue.
9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program executable by the processor, wherein: When the processor executes the computer program, the policy lifecycle management method according to any one of claims 1 to 7 is implemented.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the policy lifecycle management method according to any one of claims 1 to 7 is implemented.