Life insurance policy management center system

By adopting microservice architecture and containerization technology in the life insurance policy management center system, the system architecture and business processes are optimized, and the existing system is rigid and poor user experience is solved, achieving higher flexibility and user experience improvement.

CN119027248APending Publication Date: 2024-11-26PICC LIFE INSURANCE CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411197066.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-28
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The existing life insurance policy management center system has a rigid structure and cumbersome processes, resulting in poor user experience.

Method used

A life insurance policy management center system was designed, adopting microservice architecture and containerization technology, including unified development platform, display layer, interface layer, business logic layer, core module center, test system, basic service layer, infrastructure layer and unified The operation and maintenance platform optimizes the system architecture and business processes through microservices and containerized technologies, provides flexible and simple systems, reduces system maintenance costs and improves user experience.

Benefits of technology

Optimizing the life insurance policy management center system through microservices and containerization technology improves the flexibility and scalability of the system, reduces system maintenance costs, improves user experience, and realizes convenient policy management and service interaction.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119027248A_ABST
    Figure CN119027248A_ABST
Patent Text Reader

Abstract

The invention discloses a life insurance policy management center system, and the system comprises a unified development platform which is used for collecting, analyzing and managing life insurance policy management business demands; the business logic layer is used for executing business logic processing and performing insurance policy management; the core module center is used for providing interface services for other service center systems, and other service centers comprise service center systems except the life insurance policy management center system; the basic service layer is used for supporting infrastructures of the life insurance policy management center system; the infrastructure layer is used for data storage and message transmission; the platform service layer is used for basic service support of the life insurance policy management center system; and the unified operation and maintenance platform is used for providing cloud host resources, deploying service instances of the life insurance policy management center system through a containerization technology, and monitoring the life insurance policy management center system. By adopting the system provided by the embodiment of the invention, the flexibility and the expandability of the system are improved, and the user experience is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of insurance technology, and in particular to a life insurance policy management center system. Background Art

[0002] In the related technologies, the life insurance policy management center system is usually used to manage the information, maintenance, query and change of the policy. However, the current life insurance policy management center system has a rigid architecture and cumbersome processes, resulting in a poor user experience. Summary of the invention

[0003] The present invention provides a life insurance policy management center system to at least solve the technical problems in the above-mentioned prior art.

[0004] On the one hand, the present invention provides a life insurance policy management center system, which includes a unified development platform, a display layer, an interface layer, a business logic layer, a core module center, a testing system, a basic service layer, an infrastructure layer, a platform service layer, and a unified operation and maintenance platform, wherein:

[0005] The unified development platform is used to collect, analyze and manage life insurance policy management business needs;

[0006] The presentation layer is used to render the backend data to the frontend page;

[0007] The interface layer is used to provide interface calling services;

[0008] The business logic layer is used to execute insurance business logic processing; and to perform insurance policy management;

[0009] The core module center is used to provide interface services for other service center systems, and the other service centers include service center systems other than the life insurance policy management center system;

[0010] The test system is used to perform interface testing and module testing;

[0011] The basic service layer is used for infrastructure support of the life insurance policy management center system;

[0012] The infrastructure layer is used for data storage and message transmission;

[0013] The platform service layer is used for basic service support of the life insurance policy management center system;

[0014] The unified operation and maintenance platform is used to provide cloud host resources, deploy service instances of the life insurance policy management center system through containerization technology, and monitor the life insurance policy management center system.

[0015] The life insurance policy management center system of the embodiment of the present invention may also have the following additional technical features:

[0016] In one embodiment of the present invention, the business logic layer includes at least one of the following service modules:

[0017] Change services, which are used to process policy change requests;

[0018] Policy query service / interface, used to query policy information;

[0019] Renewal service, used to conduct risk assessment and underwriting decision on insurance policies during renewal;

[0020] Surrender service, used to process surrender application requests;

[0021] Letter service, used to generate and send various letters related to insurance policies;

[0022] Batch processing of preservation, used to process a large number of preservation applications in batches;

[0023] The underwriting service is used to process the business logic related to underwriting and interact with the life insurance policy management center system to generate and manage insurance policies.

[0024] In one embodiment of the present invention, the core module center includes at least one of the following service modules:

[0025] Underwriting center services, used to provide underwriting services;

[0026] Claims center service, used to provide claims processing services;

[0027] Contract center service, used to manage contracts, agreements and contract information related to life insurance business;

[0028] Financial center services, used to process financial operations, including at least one of premium calculation and collection and payment;

[0029] Product factory services, used to define and manage products;

[0030] Group Insurance Center Service, used to handle group insurance business;

[0031] Customer service center services, used to provide customer service functions;

[0032] Data statistics and analysis center services are used to conduct data statistics and analysis.

[0033] In one embodiment of the present invention, the interface layer includes a RESTful interface layer and an API platform, wherein:

[0034] The RESTful interface layer provides an HTTP interface based on the REST architecture for external systems or applications to call the services of the life insurance policy management center system;

[0035] The API platform is used to provide documentation and testing tools for API interfaces;

[0036] The interface layer is also used to distribute the request to at least one service instance through load balancing technology;

[0037] The testing system is also used to perform interface testing on the API interface.

[0038] In one embodiment of the present invention, the basic service layer includes at least one of the following service modules:

[0039] Domain events are used to capture and process specific events that occur in the business domain;

[0040] Domain model, which is used to define business logic and key concepts;

[0041] Log service, which is responsible for recording and managing system logs;

[0042] Distributed transactions are used to keep data consistent across multiple services or databases in a distributed system;

[0043] Mail service, used to provide the functions of sending and receiving mails;

[0044] Message service, used to implement asynchronous message transmission between different components in the system;

[0045] SMS service, used to support the sending of SMS;

[0046] Job scheduling, used to manage the execution of scheduled tasks and jobs;

[0047] Other basic services are used to extract other basic service functions.

[0048] In one embodiment of the present invention, the platform service layer includes at least one of the following service modules:

[0049] Microservice framework, which provides development, deployment and management of microservices;

[0050] Load balancing, used to distribute requests to multiple service instances;

[0051] Message queue, used for asynchronous communication and message delivery between services;

[0052] API Gateway, a single entry point for API requests;

[0053] Cache service, which uses cache technology to cache system data;

[0054] Service governance, which is used for service registration, discovery, configuration management, and health checks;

[0055] Event bus, used to support asynchronous communication between services and event-driven architecture;

[0056] System monitoring, used to monitor the operating status and performance indicators of platform services in real time;

[0057] Log collection and analysis is used to realize centralized collection, storage and visual analysis of logs.

[0058] In one embodiment of the present invention, the system further comprises a code repository for storing codes;

[0059] The testing system is also used to perform code testing on the code in the code repository;

[0060] The unified development platform is also used to manage, scan, repair, and inspect the quality of the codes in the code repository.

[0061] In one embodiment of the present invention, the core module center further includes a client for:

[0062] Provides user interface and interactive functions to enable users to perform life insurance policy management operations.

[0063] In one embodiment of the present invention, the infrastructure layer includes:

[0064] A cloud host instance, used to provide cloud host resources, wherein the cloud host resources are used to support the deployment and operation of the life insurance policy management center system;

[0065] K8s containerized cluster, used to deploy and manage service instances of the life insurance policy management center system through Kubernetes containerized technology;

[0066] The monitoring and log service is used to monitor the life insurance policy management center system in real time and to record the logs of the life insurance policy management center system.

[0067] The life insurance policy management center system of the embodiment of the present invention includes a unified development platform for collecting, analyzing and managing life insurance policy management business needs; a presentation layer for rendering back-end data to a front-end page; an interface layer for providing interface call services; a business logic layer for executing business logic processing and policy management; a core module center for providing interface services for other service center systems, including service center systems other than the life insurance policy management center system; a testing system for interface testing and module testing; a basic service layer for infrastructure support of the life insurance policy management center system; an infrastructure layer for data storage and message transmission; a platform service layer for basic service support of the life insurance policy management center system; a unified operation and maintenance platform for providing cloud host resources, deploying service instances of the life insurance policy management center system through containerization technology, and monitoring the life insurance policy management center system. Therefore, the system architecture and business processes of the life insurance policy management center can be optimized through microservices and containerization technology, making the life insurance policy management center system more flexible and simple, improving the flexibility and scalability of the life insurance policy management center system, reducing system maintenance costs, and improving user experience.

[0068] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] The above and / or additional aspects and advantages of the present invention will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0070] Figure 1 is a block diagram of a life insurance policy management center system shown in an embodiment of the present disclosure;

[0071] Figure 2 It is a block diagram of another life insurance policy management center system shown in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0072] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0073] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0074] The following describes the life insurance policy management center system proposed according to an embodiment of the present invention with reference to the accompanying drawings.

[0075] Figure 1 FIG. 1 is a block diagram of a life insurance policy management center system according to an embodiment of the present invention. Figure 1 As shown, the system may include a unified development platform, a display layer, an interface layer, a business logic layer, a core module center, a test system, a basic service layer, an infrastructure layer, a platform service layer, and a unified operation and maintenance platform, wherein:

[0076] A unified development platform for collecting, analyzing and managing life insurance policy management business needs;

[0077] The presentation layer is used to render backend data to the frontend page;

[0078] The interface layer is used to provide interface call services;

[0079] The business logic layer is used to execute insurance business logic processing and to manage insurance policies;

[0080] The core module center is used to provide interface services for other service center systems, including service center systems other than the life insurance policy management center system;

[0081] Testing system, used for interface testing and module testing;

[0082] The basic service layer is used to support the infrastructure of the life insurance policy management center system;

[0083] The infrastructure layer is used for data storage and message transmission;

[0084] The platform service layer is used to provide basic service support for the life insurance policy management center system;

[0085] The unified operation and maintenance platform is used to provide cloud host resources, deploy service instances of the life insurance policy management center system through containerization technology, and monitor the life insurance policy management center system.

[0086] In the disclosed embodiment, the life insurance policy management center system may include a unified development platform for collecting, analyzing and managing life insurance policy management business requirements. Exemplarily, the unified development platform may be configured to include the following functions: Demand management: responsible for collecting, analyzing and managing business requirements related to life insurance policy management, ensuring the accuracy and completeness of the requirements; Architecture management: designing and maintaining the system architecture of the life insurance policy management center system, ensuring the high availability and scalability of the system. The presentation layer may include a front-end framework, static resources and page rendering. Exemplarily, the front-end framework may use a micro-front-end framework to build the front-end page to achieve modularity and reusability of the page; static resources may be static resources required to manage the front-end page, such as HTML (HyperText Markup Language), CSS (Cascading Style Sheets), JavaScript files, etc.; page rendering may be responsible for rendering the back-end data to the front-end page for display to the user. The interface layer may provide interface call services, for example, providing interfaces for other applications or systems.

[0087] In the disclosed embodiment, the business logic layer is the core of the life insurance policy management center system, responsible for processing various business logics and operations. As an example, the business logic layer may include the following service interfaces and entities: change service, used to process policy change requests, which may include changes to the information of the policyholder or the insured, by reviewing the change information and executing the change after the review is passed; policy query service / interface, used to query policy information, for example, users can query policy information based on policy number or policyholder name and other conditions, and return detailed policy data (including insurance, underwriting and premium); renewal service, used to conduct risk assessment and underwriting decisions on insurance policies during renewal, and execute renewal operations and update policy status based on the underwriting results; cancellation service, used to process cancellation application requests, including review The system meets the cancellation conditions and calculates the refundable premium. After executing the cancellation process, it updates the policy status and refunds the premium to the policyholder. The letter service is used to generate and send various letters related to the policy, such as policy notices or renewal reminders, and provides customization and personalization of letters to meet the needs of different customers. The preservation batch processing is used to batch process a large number of preservation applications, and supports the scheduled execution of preservation batch processing tasks, such as regular cleanup of invalid preservation policies. The underwriting service is used to process the business logic related to underwriting, and interacts with the life insurance policy management center system to generate and manage policies, such as risk assessment and premium calculation, and interacts with the life insurance policy management center system to generate and manage policies. Furthermore, the business logic layer also involves the following entities: application form and policy entity, which are used to manage the information of application form and policy, including application information, underwriting information, premium information, etc.; policyholder and insured entity, which are used to manage the basic information and relationship of policyholder and insured; insured amount and premium entity, which are used to calculate and manage the insured amount and premium information; insurance type and product entity, which are used to manage the information of insurance type and product, including the type, characteristics, premium calculation rules, etc. of insurance type; artificial intelligence and big model entity, which are used to use artificial intelligence and big model technology to optimize business logic, such as risk assessment and premium calculation.

[0088] In the embodiments of the present disclosure, the core module center may be used to provide interface services for other service center systems, including service center systems other than the life insurance policy management center system. Exemplarily, the core module center may include at least one of the following service modules: underwriting center service, which is used to provide underwriting services and provide underwriting service interfaces to the life insurance policy management center and other centers that need underwriting; claims center service, which is used to handle claims services and provide claims service interfaces to the life insurance policy management center system and other centers that need claims; contract center service, which is used to manage contracts, agreements and contract information related to life insurance business and can provide contract service interfaces to the life insurance policy management center system and other centers that need contracts; financial center service, which is used to handle financial business, including premium calculation, payment and collection, etc., and provide financial service interfaces to other centers; product factory service, which is responsible for product definition and management, and provides product-related service interfaces to the life insurance policy management center system and other centers that need products; group insurance center service, which is used to handle group insurance business and provide group insurance service interfaces to other centers; customer service center service, which provides customer service functions, such as consultation and complaints, and provides customer service interfaces to other centers; data statistics and analysis center service, which is responsible for data statistics and analysis, and provides data-related service interfaces to other centers to support business decisions and optimization. In addition, the core module center realizes the interaction and integration with the life insurance policy management center and other centers by providing the above interface services, and together constitutes a complete life insurance policy management center system. The following are some exemplary interfaces that can be called: insurance service interface, which handles the business logic related to insurance, including filling out insurance policies, calculating premiums, submitting insurance policies, etc.; underwriting service interface, which is responsible for the business logic processing of the underwriting process, including risk assessment, application of underwriting rules, generation of underwriting results, etc.; policy service interface, which manages the life cycle of insurance policies, including the generation, change, query, renewal, and cancellation of insurance policies; claim service interface, which handles the business logic related to claim applications, including the submission, review, calculation and payment of claim amounts, etc.; basic service interface, which provides basic service interfaces such as user management, authority management, and log recording, and supports the implementation of upper-level business logic; other business interfaces, such as preservation service interface, underwriting service interface, settlement service interface, financial service interface, risk control service interface, etc., respectively handle corresponding business logic.

[0089] In the embodiments of the present disclosure, the test system can be used to perform interface testing and module testing. Exemplarily, the test system can include integration testing and interface testing. The integration test can test the integration and interaction between different modules to ensure the correctness and stability of the overall function of the system; the interface test can test the API (application programming interface) interface, including functional testing, performance testing, security testing, etc. It can be understood that it can also include automated testing, using automated testing tools to execute test cases to improve test efficiency and accuracy.

[0090] In the disclosed embodiment, the basic service layer can be used for the infrastructure support of the life insurance policy management center system. For example, the basic service layer may include at least one of the following service modules: domain events, which are used to capture and process specific events occurring in the business domain, and promote the decoupling and response of business logic; domain models, which are used to define business logic and key concepts, and are the basis for understanding and designing systems; log services, which are responsible for recording and managing system logs, and provide important basis for problem tracking and performance optimization; distributed transactions, which are used to keep data consistent across multiple services or databases in a distributed system; mail services, which are used to provide mail sending and receiving functions, and support mail notifications and communication in business; message services, which are used to implement asynchronous message delivery between different components in the system, and improve the scalability and reliability of the system; SMS services, which are used to support the sending of SMS, such as the delivery of key information such as verification codes or notifications; job scheduling, which is used to manage the execution of scheduled tasks and jobs, and ensure that the system can automatically complete specific tasks as planned; other basic services, which are used to extract other basic service functions.

[0091] In the disclosed embodiment, the infrastructure layer can be used for data storage and message transmission. Exemplarily, the infrastructure layer may include: a cloud host instance, which is used to provide cloud host resources, and the cloud host resources are used to support the deployment and operation of the life insurance policy management center system; a K8s containerized cluster, which is used to deploy and manage service instances of the life insurance policy management center system through Kubernetes containerization technology; a monitoring and log service, which is used to monitor the life insurance policy management center system in real time, and to log the life insurance policy management center system.

[0092] In the disclosed embodiment, the platform service layer can be used for the basic service support of the life insurance policy management center system. For example, the platform service layer may include at least one of the following service modules: a microservice framework, which is used to provide the development, deployment and management of microservices (Spring Cloud, Dubbo); load balancing, which is used to distribute requests to multiple service instances through Nginx or HAProxy to ensure high availability and good scalability of services; message queues, which are used to perform asynchronous communication and message delivery between services through RabbitMQ or Kafk to improve the decoupling and processing efficiency of the system; API gateways, which are used as a single entry point for all API requests, such as Zuul or Kong, to provide routing, authentication, current limiting, monitoring and other functions, simplifying the interaction between clients and servers; cache services, which are used to cache system data using Redis or Memcached cache technology, reduce database access pressure, increase data access speed, and optimize user experience; service governance, which is used to implement service registration, discovery, configuration management and health checks through Nacos or Consul to ensure stable operation of services; event buses, which are used to support asynchronous communication and event-driven architecture between services, such as Apache Kafka is used to achieve loosely coupled service interactions. System monitoring is used to monitor the operating status and performance indicators of platform services in real time through Prometheus or Grafana tools, so as to promptly discover and solve problems. Log collection and analysis is used to integrate the ELK (Elasticsearch, Logstash, Kibana) stack to achieve centralized collection, storage, and visual analysis of logs, providing strong support for troubleshooting and performance optimization.

[0093] In the disclosed embodiment, the unified operation and maintenance platform is used to provide cloud host resources, deploy service instances of the life insurance policy management center system through containerization technology, and monitor the life insurance policy management center system. Among them, the unified operation and maintenance platform may include at least one of the following modules: a unified log platform and a log data analysis platform, which are used to centrally collect, store and analyze various types of log data, provide a unified interface, and help operation and maintenance personnel quickly locate and solve faults. It is widely used in system monitoring, troubleshooting and security auditing; a full-link monitoring platform, which is used to achieve real-time monitoring of the entire link of the system, provide real-time data and alarm functions, and assist in performance optimization, fault location and capacity planning; CMDB (Configuration Management Database), which is used to centrally manage system configuration information, including hardware, software and network equipment, supports query, update and audit, and is the basis of asset management, dependency management and change management; APM (Application Performance Management), which is used to monitor and analyze application performance in real time, help discover and solve performance bottlenecks, and is suitable for performance optimization, troubleshooting and capacity planning; BPM (Business Process Management (Business Process Management) is used for automation and monitoring of business processes; DPM (Database Performance Monitoring Management) is used for database performance monitoring and management; the alarm center is used to centrally manage various alarm information, including system, performance and security alarms, and provides reception, processing and notification functions. It is the core of troubleshooting, security monitoring and operation and maintenance management; the traffic monitoring platform is used to monitor and analyze network traffic in real time, help understand network usage and anomalies, and is suitable for traffic analysis, network security and performance optimization; the security monitoring platform is used to monitor the security status of the system in real time, including intrusion detection, vulnerability scanning and security incident management. It provides alarm and processing functions to ensure security protection, auditing and emergency response. The grayscale release management platform is used to manage and monitor the grayscale release process, including version management, release strategy and rollback mechanism, to ensure a smooth release process, and supports version management, fault isolation and capacity planning. The unified configuration center is used to centrally manage system configuration information, such as parameters, environment and application configuration, and provides version control, auditing and distribution functions. It is an important tool for configuration management, troubleshooting and capacity planning. The key management platform is used to centrally manage and protect system keys, including generation, storage, distribution and auditing, to ensure that keys are safe and available, and to support security management, data encryption and access control.

[0094] In the embodiments of the present disclosure, NAS (Network Attached Storage) is a storage device connected to a network that provides data storage and file sharing services. Docker is an open source application container engine that allows developers to package applications and their dependencies into a portable container to achieve consistent operation in different environments.

[0095] And, in the embodiment of the present disclosure, CMDB is a core component in IT service management, which stores a database of configuration items (CI) and their relationships in the organization's IT infrastructure. APM is a method of monitoring application performance that uses software tools and telemetry data to ensure that the enterprise maintains the expected service level and that customers have a positive application experience. BPM can also refer to business process management, which is a management method through which organizations can optimize business processes and improve efficiency and effectiveness.

[0096] In a possible implementation, the interface layer includes a RESTful interface layer and an API platform, wherein:

[0097] The RESTful interface layer provides an HTTP interface based on the REST architecture for external systems or applications to call the services of the life insurance policy management center system;

[0098] API platform, which provides documentation and testing tools for API interfaces;

[0099] The interface layer is also used to distribute requests to at least one service instance through load balancing technology;

[0100] The testing system is also used to perform interface testing on API interfaces.

[0101] In the disclosed embodiment, the interface layer may specifically include a RESTful (Representational State Transfer) interface layer, an API (Application Programming Interface) platform, and a load balancing module. Among them, the RESTful interface layer may provide an HTTP (Hypertext Transfer Protocol) interface based on the REST (Representational State Transfer) architecture for external systems or applications to call the services of the life insurance policy management center system. The load balancing module may be used to distribute requests to at least one service instance through load balancing technology to improve the concurrent processing capability and availability of the system. Accordingly, the test system may also be used to test the API interface, including functional testing, performance testing, security testing, etc.

[0102] In a possible implementation, the above-mentioned life insurance policy management center system also includes a code repository for storing codes; a testing system for performing code testing on the codes in the code repository; and a unified development platform for managing, scanning, repairing, and inspecting the code quality of the codes in the code repository.

[0103] In the disclosed embodiment, the above-mentioned life insurance policy management center system may also include a code repository for storing code, such as Git, which is an open source distributed version control system. Correspondingly, the test system can also perform code testing on the code in the code repository, for example, testing the smallest testable unit of the code to ensure the correctness and stability of the code. The unified development platform can also perform code management, such as using a version control system (such as GIT) to manage source code, including operations such as code submission, merging, and rollback; perform security scans, such as static and dynamic security scans of the code to discover and fix potential security vulnerabilities; and perform quality gate detection, for example, you can set a code quality gate to ensure that the code meets certain quality standards before submission, such as code style, test coverage, etc.

[0104] In a possible implementation, the above-mentioned life insurance policy management center system also includes a database for management in cooperation with a unified development platform, for example, the domestic database GaussDB and OB (OceanBase) database can be managed in cooperation with a unified data platform.

[0105] In one possible implementation, the customer service center service may include an intelligent customer service robot, which is implemented based on natural language processing technology and machine learning technology.

[0106] In the disclosed embodiments, the customer service center service can be used to provide customer service functions, such as consultation, complaints, etc., and provide a customer service interface to other centers. Exemplarily, the customer service center service can be implemented through an intelligent customer service robot, which can provide a variety of communication methods such as online chat and voice interaction to meet the different communication needs of users; the intelligent customer service robot can also identify the user's problems and needs, and provide accurate answers and solutions, support automatic replies to common questions and transfer manual services for complex questions. It can be understood that the intelligent customer service robot can be implemented based on natural language processing technology and machine learning technology, and the service quality and user experience of the intelligent customer service robot can be continuously improved through natural language processing and machine learning technologies, including improving the accuracy of problem identification, optimizing the content of answers, etc.; moreover, the accuracy and effect of the recommendation algorithm can be continuously optimized through machine learning technology, and the satisfaction and conversion rate of personalized recommendations can be improved.

[0107] In a possible implementation, the above interface layer may also be used to perform security processing on interface calls, where the security processing includes identity authentication, authorization, and encryption.

[0108] In the disclosed embodiment, the interface layer may also include a security control module for performing security processing such as identity authentication, authorization, and encryption on the interface call to ensure secure transmission and access of data. For example, encryption processing may be performed using encryption algorithms such as AES (Advanced Encryption Standard) and RSA (a public key encryption algorithm).

[0109] In a possible implementation, the core module center may also include a client for providing a user interface and interactive functions to enable users to perform life insurance policy management operations.

[0110] In the disclosed embodiment, the life insurance policy management center system may also include a client for providing a user interface and interactive functions so that the user can perform relevant operations of life insurance policy management through the client. Exemplarily, the client may include a mobile client and a communication software client for providing a user interface and interactive functions on the mobile terminal and the communication software terminal, so that the user can perform relevant operations of life insurance policy management. It is understandable that a core system interface may also be included for interacting and integrating with other core systems (such as an underwriting center system, a claims center system, a customer center system, etc.) to achieve sharing and synchronization of business data.

[0111] The life insurance policy management center system proposed in the present invention includes a unified development platform for collecting, analyzing and managing life insurance policy management business needs; a display layer for rendering back-end data to a front-end page; an interface layer for providing interface call services; a business logic layer for executing business logic processing and policy management; a core module center for providing interface services for other service center systems, wherein the other service centers include service center systems other than the life insurance policy management center system; a testing system for performing interface testing and module testing; a basic service layer for infrastructure support of the life insurance policy management center system; an infrastructure layer for data storage and message transmission; a platform service layer for basic service support of the life insurance policy management center system; a unified operation and maintenance platform for providing cloud host resources, deploying service instances of the life insurance policy management center system through containerization technology, and monitoring the life insurance policy management center system. Therefore, the system architecture and business processes of the life insurance policy management center can be optimized through microservices and containerization technology, making the life insurance policy management center system more flexible and simple, improving the flexibility and scalability of the life insurance policy management center system, reducing system maintenance costs, and improving user experience.

[0112] In order to make the life insurance policy management center system provided by the embodiment of the present disclosure clearer, the following is combined with the attached Figure 2 Provide explanation.

[0113] like Figure 2 As shown, the system architecture of the life insurance policy management center system may include:

[0114] 1. Unified development platform, including:

[0115] Demand Management: Responsible for collecting, analyzing and managing business needs related to life insurance policy management, ensuring the accuracy and completeness of the needs.

[0116] Architecture management: Design and maintain the system architecture of the life insurance policy management center to ensure high availability and scalability of the system.

[0117] Code management: Use a version control system (such as GIT) to manage source code, including code submission, merging, rollback and other operations.

[0118] Security scanning: Perform static and dynamic security scanning on the code to discover and fix potential security vulnerabilities.

[0119] Quality gate: Set code quality gate to ensure that the code meets certain quality standards before submission, such as code style, test coverage, etc.

[0120] Figure 2 In the software development life cycle, CI / CO is the abbreviation of Continuous Integration and Continuous Delivery / Continuous Deployment, which aims to simplify and accelerate the software development life cycle through automated processes.

[0121] 2. Display layer, including:

[0122] Front-end framework: Use the micro-front-end framework to build the front-end page to achieve modularity and reusability of the page.

[0123] Static resources: Manage static resources required for front-end pages, such as HTML, CSS, JavaScript files, etc.

[0124] Page rendering: responsible for rendering the backend data to the frontend page and displaying it to the user.

[0125] 3. Interface layer

[0126] RESTful interface: Provides an HTTP interface based on the REST architecture for external systems or applications to call the services of the life insurance policy management center.

[0127] API platform: Centrally manages API publishing, calling, monitoring, billing and other functions, and provides API documentation and testing tools.

[0128] Load balancing: Load balancing technology is used to distribute requests to multiple service instances to improve the system's concurrent processing capabilities and availability.

[0129] Security control: Implement security measures such as authentication, authorization, and encryption for interface calls to ensure secure transmission and access of data.

[0130] 4. Business logic layer: The business logic layer is the core of the life insurance policy management center and is responsible for processing various business logics and operations. It mainly includes the following service interfaces and entities:

[0131] Change service: Process policy change requests, including updating policyholder or insured information, provide change application submission and review process, and execute the change after review and approval.

[0132] Insurance policy query service / interface: allows users to query insurance policy information based on policy number, policyholder name and other conditions, and returns detailed policy data, covering insurance, underwriting, premium and other related information.

[0133] Renewal service: When renewing a policy, the underwriting center's underwriting service is called to conduct risk assessment and underwriting decisions on the policy. Based on the underwriting results, the renewal operation is executed and the policy status is updated.

[0134] Surrender service: responsible for processing surrender applications, including reviewing surrender conditions and calculating refundable premiums, executing surrender procedures, updating policy status, and refunding premiums to the insured.

[0135] Letter service: Generate and send various letters related to insurance policies, such as policy notices or renewal reminders, and provide customized and personal letters to meet the needs of different customers.

[0136] Batch processing of preservation: Batch processing of a large number of preservation applications to improve processing efficiency, and support for scheduled execution of preservation batch processing tasks, such as regular cleanup of invalid preservation orders.

[0137] Underwriting service: It handles the business logic related to underwriting and interacts with the policy management center to generate and manage policies. This service handles the business logic related to underwriting, including risk assessment and premium calculation. It interacts with the policy management center and is responsible for generating and managing policies.

[0138] In addition, the business logic layer also involves the following entities:

[0139] Application form and insurance policy: manage the information of application form and insurance policy, including application information, underwriting information, premium information, etc.

[0140] Policyholder and insured: manage the basic information and relationship between the policyholder and the insured.

[0141] Insurance coverage, premium: information on calculating and managing insurance coverage and premium.

[0142] Insurance types and products: manage information on insurance types and products, including the types, characteristics, premium calculation rules, etc.

[0143] Artificial intelligence and big models: Use artificial intelligence and big model technologies to optimize business logic, such as risk assessment and premium calculation.

[0144] 6. Core module center, in addition to the life insurance policy management center, there are other core module centers, each independent and providing interface services to other centers. The following is a description of these core module centers:

[0145] Underwriting center services: responsible for underwriting business, providing underwriting service interface to the life insurance policy management center and other centers that need underwriting.

[0146] Claims center service: handles claims business and provides claims service interface to life insurance policy management center and other centers that need claims.

[0147] Contract Center: Responsible for managing all contracts, agreements and contract information related to life insurance business, and providing contract service interface to the life insurance policy management center and other centers that need contracts.

[0148] Financial center services: handle financial operations, including premium calculation, collection and payment, etc., and provide financial service interfaces to other centers.

[0149] Product Factory Service: Responsible for product definition and management, providing product-related service interfaces to the life insurance policy management center and other centers that need products.

[0150] Group Insurance Center Service: handles group insurance business and provides group insurance service interface to other centers.

[0151] Customer Service Center Services: Provide customer service functions, such as consultation, complaints, etc., and provide customer service interfaces to other centers.

[0152] Data Statistics and Analysis Center Service: Responsible for data statistics and analysis, providing data-related service interfaces to other centers to support business decision-making and optimization.

[0153] The above core module center realizes interaction and integration with the life insurance policy management center and other centers by providing interface services, and together constitutes a complete life insurance business system.

[0154] Some callable interfaces:

[0155] Insurance service interface: handles insurance-related business logic, including filling out insurance applications, calculating premiums, submitting insurance applications, etc.

[0156] Underwriting service interface: responsible for the business logic processing of the underwriting process, including risk assessment, application of underwriting rules, generation of underwriting results, etc.

[0157] Insurance policy service interface: manages the life cycle of insurance policies, including policy generation, modification, query, renewal, and cancellation.

[0158] Claim service interface: handles the business logic related to claim applications, including submission, review, calculation and payment of claim amounts, etc.

[0159] Basic service interface: provides basic service interfaces such as user management, permission management, and logging, and supports the implementation of upper-level business logic.

[0160] Other business interfaces: such as security service interface, underwriting service interface, settlement service interface, financial service interface, risk control service interface, etc., handle the corresponding business logic respectively.

[0161] 7. Testing system, including:

[0162] Unit testing: Test the smallest testable unit of the code to ensure the correctness and stability of the code.

[0163] Integration testing: Test the integration and interaction between different modules to ensure the correctness and stability of the overall system functionality.

[0164] Interface testing: Testing of API interfaces, including functional testing, performance testing, security testing, etc.

[0165] Automated testing: Use automated testing tools to execute test cases to improve testing efficiency and accuracy.

[0166] And, the client, including:

[0167] Mobile client and communication software client: Provide user interface and interactive functions for mobile and communication software (such as WeChat) to facilitate users to perform related operations for life insurance policy management.

[0168] Core system interface: interact and integrate with other core systems (such as underwriting center, claims center, customer center, etc.) to achieve sharing and synchronization of business data.

[0169] Among them, the core front-end portal usually refers to the front-end business system in an enterprise or organization that directly faces customers and users. It is mainly responsible for handling tasks such as interaction with customers, marketing promotion, and transaction conversion.

[0170] 8. Infrastructure layer, including:

[0171] Cloud host instance: provides cloud host resources to support the deployment and operation of the life insurance policy management center.

[0172] K8s containerized cluster: Use Kubernetes containerization technology to deploy and manage service instances of the life insurance policy management center to improve the scalability and maintainability of the system.

[0173] Monitoring and logging: Monitor and log the system in real time to promptly detect and handle system anomalies and problems.

[0174] 9. Basic service layer, including:

[0175] Domain events: Capture and process specific events that occur in the business domain to promote the decoupling and response of business logic.

[0176] Domain model: As the core of the business domain, it defines business logic and key concepts and is the basis for understanding and designing the system.

[0177] Log service: responsible for recording and managing system logs, providing important basis for problem tracking and performance optimization.

[0178] Distributed transactions: Ensure that operations across multiple services or databases in a distributed system maintain data consistency and integrity.

[0179] Mail service: provides the functions of sending and receiving mails, and supports mail notifications and communications in business.

[0180] Message service: realize asynchronous message transmission between different components in the system, and improve the scalability and reliability of the system.

[0181] SMS service: supports the sending of SMS messages, which are used to deliver key information such as verification codes and notifications.

[0182] Job scheduling: Manage the execution of scheduled tasks and jobs to ensure that the system can automatically complete specific tasks as planned.

[0183] Other basic services: covers other basic functions besides the above services, providing comprehensive support for the system.

[0184] 10. Platform service layer, including:

[0185] Microservice framework: The cornerstone for building and managing microservices, such as Spring Cloud, Dubbo, etc., provides a complete solution to simplify the development, deployment and management of microservices.

[0186] Load balancing: Through Nginx or HAProxy, effectively distribute requests to multiple service instances to ensure high availability and good scalability of services.

[0187] Message queue: used for asynchronous communication and message delivery between services through RabbitMQ or Kafka to improve the decoupling and processing efficiency of the system.

[0188] API Gateway: A single entry point for all API requests, such as Zuul or Kong, which provides routing, authentication, current limiting, monitoring and other functions to simplify the interaction between clients and servers.

[0189] Cache service: Use Redis or Memcached cache technology to reduce database access pressure, improve data access speed, and optimize user experience.

[0190] Service governance: Use Nacos or Consul tools to implement service registration, discovery, configuration management, and health checks to ensure stable service operation.

[0191] Event bus: supports asynchronous communication between services and event-driven architecture, such as Apache Kafka, to achieve loosely coupled service interactions.

[0192] System monitoring: Use Prometheus or Grafana to monitor the operating status and performance indicators of platform services in real time to identify and solve problems in a timely manner.

[0193] Log collection and analysis: Integrate the ELK (Elasticsearch, Logstash, Kibana) stack to achieve centralized collection, storage, and visual analysis of logs, providing strong support for troubleshooting and performance optimization.

[0194] 11. Unified operation and maintenance platform, including:

[0195] Unified log platform and log data analysis platform: Centrally collect, store and analyze various log data, provide a unified interface, help operation and maintenance personnel quickly locate and solve faults, and are widely used in system monitoring, troubleshooting and security auditing.

[0196] Full-link monitoring platform: Realizes real-time monitoring of the entire system, covering networks, applications, databases, etc., provides real-time data and alarm functions, and assists in performance optimization, fault location, and capacity planning.

[0197] CMDB: Centrally manages system configuration information, including hardware, software, and network equipment, supports query, update, and audit, and is the basis for asset management, dependency management, and change management.

[0198] APM: monitors and analyzes application performance in real time, helps identify and resolve performance bottlenecks, and is suitable for performance optimization, troubleshooting, and capacity planning.

[0199] BPM: Related to operation and maintenance process optimization, responsible for the automation and monitoring of business processes.

[0200] DPM (Database Performance Monitoring and Management): Database performance monitoring and management.

[0201] Alarm Center: Centrally manages various alarm information, including system, performance and security alarms, and provides receiving, processing and notification functions. It is the core of troubleshooting, security monitoring and operation and maintenance management.

[0202] Traffic monitoring platform: monitors and analyzes network traffic in real time to help understand network usage and anomalies. It is suitable for traffic analysis, network security and performance optimization.

[0203] Security monitoring platform: real-time monitoring of system security status, including intrusion detection, vulnerability scanning and security event management, providing alarm and processing functions to ensure security protection, auditing and emergency response.

[0204] Grayscale release management platform: manages and monitors the grayscale release process, including version management, release strategy and rollback mechanism, to ensure a smooth release process, and supports version management, fault isolation and capacity planning.

[0205] Unified Configuration Center: Centrally manages system configuration information, such as parameters, environment, and application configuration, and provides version control, auditing, and distribution functions. It is an important tool for configuration management, troubleshooting, and capacity planning.

[0206] Key management platform: Centrally manage and protect system keys, including generation, storage, distribution and auditing, to ensure key security and availability, and support security management, data encryption and access control.

[0207] 12. Databases, including the domestic database GaussDB and the OB database OceaBase, are managed in conjunction with a unified data platform.

[0208] From the above architecture, we can see that this disclosure proposes a new system architecture and process optimization solution for the life insurance policy management center system, and combines the improvement of user experience and interactive design to achieve a technological breakthrough. For example, some of the optimizations are as follows:

[0209] 1. Optimization of system architecture, including:

[0210] Service splitting: The microservice architecture is adopted to split the life insurance policy management center system into multiple small, independent service modules, such as policy information management, policy change processing, policy query, etc. Each module is responsible for specific business functions.

[0211] Communication mechanism: Modules interact through lightweight communication mechanisms (such as RESTful API) and use standard HTTP protocol for data transmission.

[0212] Data caching: The introduction of distributed database and caching technology enables efficient storage and fast access to policy data, improving the system's response speed and data processing capabilities.

[0213] The security design adopts mechanisms such as encrypted transmission, access control, data backup and recovery to ensure the security and integrity of policy data.

[0214] 2. Process and automation, including:

[0215] Process streamlining and optimization: The business processes of the policy management center have been comprehensively streamlined and optimized. Through automation and intelligent means, manual intervention has been reduced and business processing efficiency has been improved.

[0216] Information synchronization: Real-time updating and synchronization of policy information is achieved, ensuring that users can obtain the latest policy information at any time and any place.

[0217] Policy Changes: Provides a convenient policy change service. Users can quickly submit change applications through online channels and track the progress of changes in real time.

[0218] 3. Improve user experience and interaction design, including:

[0219] User interface redesign: The user interface of the policy management center has been redesigned, adopting a simple and intuitive interaction method, allowing users to easily complete policy inquiries, changes and other operations.

[0220] Personalized service recommendation: Provides personalized service recommendation function to recommend suitable insurance products and service solutions to users based on their policy information and historical behavior.

[0221] Intelligent customer service system: Users can get real-time help and support through online chat, voice interaction, etc., which improves user satisfaction and service quality.

[0222] It can be seen that the life insurance policy management center system provided by the embodiment of the present disclosure, on the one hand, through the combined application of microservice architecture and distributed database, has carried out comprehensive system architecture optimization and process transformation of the life insurance policy management center in the life insurance core system, which can significantly improve the flexibility and scalability of the life insurance policy management center system and reduce system maintenance costs. On the other hand, through intelligent processing and business process reengineering, the automation and intelligence of business processes are realized, manual intervention and error rates are reduced, business processing efficiency is improved, real-time updating and synchronization of policy information are realized, and convenient policy change services are provided. Moreover, through the comprehensive improvement of user experience and interactive design, users are provided with more convenient and personalized insurance services, which improves user satisfaction and service quality.

[0223] Various implementations 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 chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0224] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer 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 can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the 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 acoustic input, voice input, or tactile input).

[0225] The systems and techniques described herein can be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), the Internet, and a blockchain network.

[0226] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services ("Virtual Private Server", or "VPS" for short). The server may also be a server of a distributed system, or a server combined with a blockchain.

[0227] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0228] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A life insurance policy management center system, characterized in that: The system includes a unified development platform, a display layer, an interface layer, a business logic layer, a core module center, a testing system, a basic service layer, an infrastructure layer, a platform service layer, and a unified operation and maintenance platform, among which: The unified development platform is used to collect, analyze and manage life insurance policy management business needs; The presentation layer is used to render the backend data to the frontend page; The interface layer is used to provide interface calling services; The business logic layer is used to execute insurance business logic processing; and to perform insurance policy management; The core module center is used to provide interface services for other service center systems, and the other service centers include service center systems other than the life insurance policy management center system; The test system is used to perform interface testing and module testing; The basic service layer is used for infrastructure support of the life insurance policy management center system; The infrastructure layer is used for data storage and message transmission; The platform service layer is used for basic service support of the life insurance policy management center system; The unified operation and maintenance platform is used to provide cloud host resources, deploy service instances of the life insurance policy management center system through containerization technology, and monitor the life insurance policy management center system.

2. The system according to claim 1, characterized in that The business logic layer includes at least one of the following service modules: Change services, which are used to process policy change requests; Policy query service / interface, used to query policy information; Renewal service, used to conduct risk assessment and underwriting decision on insurance policies during renewal; Surrender service, used to process surrender application requests; Letter service, used to generate and send various letters related to insurance policies; Batch processing of preservation, used to process a large number of preservation applications in batches; The underwriting service is used to process the business logic related to underwriting and interact with the life insurance policy management center system to generate and manage insurance policies.

3. The system according to claim 1, characterized in that The core module center includes at least one of the following service modules: Underwriting center services, used to provide underwriting services; Claims center service, used to provide claims processing services; Contract center service, used to manage contracts, agreements and contract information related to life insurance business; Financial center services, used to process financial operations, including at least one of premium calculation and collection and payment; Product factory services, used to define and manage products; Group Insurance Center Service, used to handle group insurance business; Customer service center services, used to provide customer service functions; Data statistics and analysis center services are used to conduct data statistics and analysis.

4. The system according to claim 1, characterized in that The interface layer includes a RESTful interface layer and an API platform, wherein: The RESTful interface layer provides an HTTP interface based on the REST architecture for external systems or applications to call the services of the life insurance policy management center system; The API platform is used to provide documentation and testing tools for API interfaces; The interface layer is also used to distribute the request to at least one service instance through load balancing technology; The testing system is also used to perform interface testing on the API interface.

5. The system according to claim 1, characterized in that The basic service layer includes at least one of the following service modules: Domain events are used to capture and process specific events that occur in the business domain; Domain model, which is used to define business logic and key concepts; Log service, which is responsible for recording and managing system logs; Distributed transactions are used to keep data consistent across multiple services or databases in a distributed system; Mail service, used to provide the functions of sending and receiving mails; Message service, used to implement asynchronous message transmission between different components in the system; SMS service, used to support the sending of SMS; Job scheduling, used to manage the execution of scheduled tasks and jobs; Other basic services are used to extract other basic service functions.

6. The system according to claim 1, characterized in that The platform service layer includes at least one of the following service modules: Microservice framework, which provides development, deployment and management of microservices; Load balancing, used to distribute requests to multiple service instances; Message queue, used for asynchronous communication and message delivery between services; API Gateway, a single entry point for API requests; Cache service, which uses cache technology to cache system data; Service governance, which is used for service registration, discovery, configuration management, and health checks; Event bus, which is used to support asynchronous communication between services and event-driven architecture; System monitoring, used to monitor the operating status and performance indicators of platform services in real time; Log collection and analysis is used to realize centralized collection, storage and visual analysis of logs.

7. The system according to claim 1, characterized in that The system also includes a code repository for storing codes; The testing system is also used to perform code testing on the code in the code repository; The unified development platform is also used to manage, scan, repair, and inspect the quality of the codes in the code repository.

8. The system according to claim 1, characterized in that The core module center also includes a client for: Provides user interface and interactive functions to enable users to perform life insurance policy management operations.

9. The system according to claim 1, characterized in that The infrastructure layer includes: A cloud host instance, used to provide cloud host resources, wherein the cloud host resources are used to support the deployment and operation of the life insurance policy management center system; K8s containerized cluster, used to deploy and manage service instances of the life insurance policy management center system through Kubernetes containerized technology; The monitoring and log service is used to monitor the life insurance policy management center system in real time and to record the logs of the life insurance policy management center system.

10. The system according to claim 1, characterized in that The unified operation and maintenance platform includes: Unified log platform and log data analysis platform, used to centrally collect, store and analyze various log data, and provide a unified interface; Full-link monitoring platform, used to achieve real-time monitoring of the entire link of the system, providing real-time data and alarm functions; Configuration management database CMDB, used to centrally manage system configuration information; Application Performance Management (APM), used to monitor and analyze application performance in real time; Business process management BPM, used for automation and monitoring of business processes; Database performance monitoring and management DPM, used for database performance monitoring and management; Alarm center, used to centrally manage various alarm information; Traffic monitoring platform, used to monitor and analyze network traffic in real time; Security monitoring platform, used to monitor system security status in real time; Grayscale release management platform, used to manage and monitor the grayscale release process; Unified configuration center, used to centrally manage system configuration information; Key management platform, used to centrally manage and protect system keys.