Insurance policy data management system
By building a policy data management system, parsing and storing JSON and XML data, the problems of low timeliness and low resource utilization in policy data management were solved, realizing full-process control and localized storage, and improving data management efficiency and resource utilization.
Patent Information
- Application Number
- CN202410941175.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-12
- Publication Date
- 2024-11-08
AI Technical Summary
Policy data management is slow, inefficient, and has low resource utilization. Furthermore, the data is not uniformly distributed across different systems, and some data is missing or relies on external systems, which raises copyright issues.
Build a policy data management system, including data receiving service, printing center, logistics center, message queue service, object storage service, etc. By parsing and storing JSON data and XML data, it can achieve full-process control and localized storage, reducing dependence on third-party systems.
It improved the timeliness and efficiency of policy data management, realized localized data storage and unified management, met the statistical and post-analysis requirements of data from various channels, and reduced dependence on external systems.
Smart Images

Figure CN118917951A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of insurance technology, and in particular to an insurance policy data management system. Background Art
[0002] In the related technologies, the printing process data and logistics data of the insurance policy are usually distributed in different systems, the data is not unified, the data utilization rate is low, and some data may even be missing because it has never been saved. In addition, many data rely on external systems and have copyright issues. Therefore, if you want to query all the information of the insurance policy, you need to query the data of different stages of the insurance policy one by one, which will reduce the timeliness, efficiency and resource utilization of the insurance policy data management. Summary of the invention
[0003] The present disclosure provides a policy data management system to at least solve the technical problems of low timeliness, low efficiency and low resource utilization of policy data management in related technologies. The technical solution of the present disclosure is as follows:
[0004] According to an embodiment of the present disclosure, a policy data management system is provided, including a data receiving service, a printing center, a logistics center, a message queue service, and an object storage service, wherein:
[0005] The data receiving service is used to receive the logistics data pushed by the logistics center and the printing data pushed by the printing center; parse the logistics data and the printing data to obtain the parsed logistics data and printing data, wherein the parsed logistics data and printing data are Json data and XML data; and push the Json data and XML data to the message queue service;
[0006] The message queue service is used to store the Json data and XML data in the object storage service.
[0007] In a possible implementation, it also includes a read-write database, a read-only database, and an API service, wherein:
[0008] The message queue service is further used to store the original data of the logistics data and the printing data into the read-write database;
[0009] The read-write database is used to synchronize the original data of the logistics data and the printing data to the read-only database;
[0010] The read-only database is used to encapsulate monitoring data into the API service.
[0011] In a possible implementation, it further includes a data report service for generating a data report based on the data in the read-only database.
[0012] In a possible implementation, it also includes data analysis services and data distribution services, wherein:
[0013] The data distribution service is used to read the original data stored in the read-write database; and transmit different business data to the corresponding data analysis service;
[0014] The data analysis service is used to perform preliminary analysis on the original data; and to store the analyzed data in the read-write database.
[0015] In a possible implementation, monitoring services and SMS services are also included, wherein:
[0016] The monitoring service is used to monitor the service status of the data receiving service, the message queue service, the read-write database, the data distribution service, and the data parsing service; and to perform quality detection on the data in the read-write database;
[0017] The SMS service is used to output SMS to a preset device when the data quality in the read-write database does not meet the preset requirements.
[0018] In one possible implementation, the data receiving service is also used to perform heartbeat detection on the message queue service, the data analysis service, the read-write database, and the data distribution service; and, if there is a problem with the heartbeat detection result, stop the service corresponding to the problematic heartbeat detection result.
[0019] In a possible implementation, the SMS service is further used to generate SMS information based on the service corresponding to the problematic heartbeat detection result, and output the SMS information to a management device.
[0020] In a possible implementation, the data receiving service is further used to parse the printing data and return the parsing status of the printing data to the printing center; and to parse the logistics data and return the parsing status of the logistics data to the logistics center.
[0021] In a possible implementation, the API service is used to connect to a system other than the insurance policy data management system.
[0022] In a possible implementation manner, the read-only database is further used to receive a data query request; and output target data in response to the data query request.
[0023] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:
[0024] In the embodiment of the present disclosure, in the insurance policy data management system, the data receiving service receives the logistics data pushed by the logistics center and the printing data pushed by the printing center, parses the logistics data and printing data to obtain the parsed Json data and XML data, and pushes the Json data and XML data to the message queue service; the message queue service stores the Json data and XML data in the object storage service. In this way, an insurance policy data management system can be built to reduce dependence on third-party systems, and realize the full process control of insurance policy self-generation, printing, issuance, logistics, etc. At the same time, the data is parsed into Json data and XML data for local storage, which is more convenient for insurance policy data management, meets the statistics of various channel data and the requirements of later data mining and analysis, and does not need to query the data of different stages of the insurance policy one by one, thereby improving the timeliness of insurance policy data management, improving resource utilization and insurance policy data management efficiency.
[0025] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.
[0027] Figure 1 It is a block diagram of an insurance policy data management system provided by an embodiment of the present disclosure.
[0028] Figure 2 It is a block diagram of an insurance policy data management system provided by an embodiment of the present disclosure. DETAILED DESCRIPTION
[0029] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.
[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0031] As can be seen from the background technology, in the related technology, since the printing process data (i.e., printing data) and logistics data of the insurance policy are in different systems, the data is not unified, the data utilization rate is low, and even some data have never been saved, resulting in data loss. Many data even need to rely on external systems and have copyright issues. At present, if you want to query all the information of the insurance policy, you must query the data of different stages of the insurance policy one system at a time. This will lead to low timeliness, low efficiency, low resource utilization, and inability to achieve local storage of all data and later data reuse. Therefore, build a full ecosystem for insurance policy management (i.e., insurance policy data management system) to achieve the full process control of the company's insurance policy self-generation, printing, issuance, archiving, etc., meet the needs of digital, professional and refined operation of insurance policies, and provide customers with a full range of insurance policy services. In addition, the data can be parsed and stored locally, a local database can be built, and customized reports and intelligent report functions can be provided to meet the statistical and later data mining and analysis requirements of data from various channels.
[0032] The insurance policy is referred to as the "policy". It is a written proof of the insurance contract signed between the insurer and the policyholder. The main contents of the insurance policy include: (1) the explanation of the parties on matters related to the subject matter of insurance, including the name of the insured, the name of the subject matter of insurance and its storage place or status, the insurance amount, the insurance period, the insurance premium, etc. (2) the rights and obligations of both parties, such as the responsibilities to be assumed and the responsibilities not to be assumed. (3) Annotated conditions, which refer to the insurance terms or other conditions agreed upon by both parties and matters such as policy changes, transfers and cancellations. The insurance policy is the main form of insurance contract. To simplify the form, legally binding reservation insurance policies, insurance certificates or temporary insurance policies can also be used.
[0033] The insurance policy data management system provided by the embodiment of the present disclosure is described in detail below with reference to the accompanying drawings.
[0034] Figure 1 FIG. 1 is a block diagram of an insurance policy data management system according to an exemplary embodiment. Figure 1 As shown, the policy data management system may include a data receiving service, a printing center, a logistics center, a message queue service, and an object storage service, wherein:
[0035] Data receiving service, used to receive logistics data pushed by the logistics center and print data pushed by the print center; parse the logistics data and print data to obtain parsed logistics data and print data, wherein the parsed logistics data and print data are Json data and XML data; and push the Json data and XML data to the message queue service;
[0036] Message queue service, used to store Json data and XML data in object storage service.
[0037] In an embodiment of the present disclosure, the policy data management system may include a data receiving service, which may be connected to a printing center and a logistics center. The printing center may be a service for uniformly distributing printed paper documents, such as printing, printing, binding and other operations; the logistics center may be a service for distributing and delivering paper documents, and all original logistics information passes through the logistics center. The printing center may push printing data to the data receiving service, and the logistics center may push logistics data to the data receiving service. After the data receiving service receives the logistics data pushed by the logistics center and the printing data pushed by the printing center, the logistics data and the printing data may be parsed, and the parsed logistics data and the printing data may be Json (JavaScript Object Notation, JS object notation) data and XML (Extensible Markup Language, Extensible Markup Language) data. A message queue service is provided to store Json data and XML data in an object storage service. Since some of the printing data and logistics data are in semi-structured format data and cannot be used directly, parsing the printing data and logistics data into Json data and XML data is more convenient for data management.
[0038] In the embodiment of the present disclosure, in the insurance policy data management system, the data receiving service receives the logistics data pushed by the logistics center and the printing data pushed by the printing center, parses the logistics data and printing data to obtain the parsed Json data and XML data, and pushes the Json data and XML data to the message queue service; the message queue service stores the Json data and XML data in the object storage service. In this way, an insurance policy data management system can be built to reduce dependence on third-party systems, and realize the full process control of insurance policy self-generation, printing, issuance, logistics, etc. At the same time, the data is parsed into Json data and XML data for local storage, which is more convenient for insurance policy data management, meets the statistics of various channel data and the requirements of later data mining and analysis, and does not need to query the data of different stages of the insurance policy one by one, thereby improving the timeliness of insurance policy data management, improving resource utilization and insurance policy data management efficiency.
[0039] In a possible implementation, the policy data management system further includes a read-write database, a read-only database, and an API service, wherein:
[0040] The message queue service is also used to store the original data of logistics data and printing data into the read-write database;
[0041] Read-write database, used to synchronize the original data of logistics data and printing data to the read-only database;
[0042] A read-only database used to encapsulate monitoring data into the API service.
[0043] In an embodiment of the present disclosure, the insurance policy data management system also includes a read-write database and a read-only database. The read-write database and the read-only database can be implemented using the same physical machine, or two physical machines can be used to achieve data synchronization and read-write separation. Among them, the read-write database is the main database and the business database. The read-only database is a disaster recovery database, a database backup, and provides read-only services. The message queue service can communicate with the read-write database and the read-only database, and store the original data of logistics data and printing data in the read-write database. The read-write database can synchronize the original data of logistics data and printing data to the read-only database. The read-only database can encapsulate monitoring data into the API service, and the monitoring data can be data stored in the read-only database.
[0044] In a further possible implementation, the API service can be used to connect to systems other than the policy data management system. That is, the API (Application Programming Interface) service can connect to third-party systems to help centrally manage internal and external APIs, such as API creation, document generation, version control, access control, subscription management, billing and metering, etc.
[0045] In a possible implementation, the policy data management system further includes a data report service. The data report service can be used to generate data reports based on data in the read-only database. Exemplarily, the data report service can customize reports based on data from the printing center and the material center such as the paper insurance contract printing process, and can also output and display reports to facilitate business analysis.
[0046] In a possible implementation, the insurance policy data management system further includes a data analysis service and a data distribution service; wherein:
[0047] Data distribution service, used to read the original data stored in the read-write database; and transmit different business data to the corresponding data analysis service;
[0048] The data analysis service is used to perform preliminary analysis on the original data; and to save the analyzed data in the read-write database.
[0049] In an embodiment of the present disclosure, a data distribution service may be connected to a read-write database and a data analysis service. The data distribution service may read the original data stored in the read-write database and transmit different business data to the corresponding data analysis service. The data distribution service may also perform a preliminary analysis on the read original data and transmit it to the corresponding data analysis service according to different business data, and may increase or decrease the data according to the business scale.
[0050] After receiving the data transmitted by the data distribution service, the data analysis service can perform preliminary analysis on the original data and save the analyzed data in the read-write database. Exemplarily, the data analysis service can be a service responsible for business processing, which can be increased or decreased according to the scale of the business and data. For example, when the load utilization is high, the data analysis service can be increased, and when the load utilization is low, the data analysis service can be reduced. Improve resource utilization. It is understandable that multiple businesses can use one server, or one business can use multiple servers (middleware or containers). The data analysis service can save the analyzed data in the business database (also known as the read-write database).
[0051] In a possible implementation, the policy data management system also includes a monitoring service and a text message service, wherein:
[0052] Monitoring service, used to monitor the service status of data receiving service, message queue service, read-write database, data distribution service, and data analysis service; and to perform quality inspection on data in the read-write database;
[0053] The SMS service is used to output SMS to the preset device when the data quality in the read and write database does not meet the preset requirements.
[0054] In an embodiment of the present disclosure, the policy data management system also includes a monitoring service, which can be connected to the data receiving service, the message queue service, the read-write database, the data distribution service, and the data analysis service for communication, and is used to monitor the service status of the data receiving service, the message queue service, the read-write database, the data distribution service, and the data analysis service, and the service status can be, for example, normal, abnormal, etc. The monitoring service can also perform quality detection on the data in the read-write database, and detect the data quality of the data stored in the read-write database, for example, it can be one or more of the accuracy, consistency, real-time, relevance, etc. of the data, or it can also be set according to actual needs. If it is detected that the data quality in the read-write database does not meet the preset requirements, the preset requirements can be set according to actual needs, and a prompt SMS message can be generated and output to a preset device, which can be, for example, an electronic device used by an administrator, such as a mobile phone, a tablet computer, etc., so that the administrator can promptly understand the situation of the policy data and the policy data management system and perform maintenance in a timely manner.
[0055] In one possible implementation, the data receiving service can also be used to perform heartbeat detection on the message queue service, data analysis service, read-write database, and data distribution service; and, if there is a problem with the heartbeat detection result, stop the service corresponding to the problematic heartbeat detection result.
[0056] In an embodiment of the present disclosure, the data receiving service can also perform heartbeat detection, for example, the heartbeat detection can be performed on the message queue service, the data analysis service, the read-write database, and the data distribution service to obtain the heartbeat detection results of the aforementioned services. If the heartbeat detection result shows a problem, such as heartbeat stop, the service corresponding to the heartbeat detection result of heartbeat stop can be stopped. For example, assuming that the heartbeat detection result of the data analysis service is heartbeat stop, the data analysis service can be stopped, and the data analysis service will no longer receive data or perform analysis processing.
[0057] In a further possible implementation, the SMS service is further used to generate SMS messages based on the service corresponding to the problematic heartbeat detection result, and output the SMS messages to the management device.
[0058] In an embodiment of the present disclosure, once a problematic heartbeat detection result is detected, the service corresponding to the problematic heartbeat detection result can be determined, and a text message can be generated based on the service whose heartbeat has stopped. The text message can be output to a management device, such as an electronic device of a manager, to prompt the manager that one or several services have stopped heartbeating.
[0059] In a possible implementation, the data receiving service may also be used to parse the printing data and return the parsing status of the printing data to the printing center; and to parse the logistics data and return the parsing status of the logistics data to the logistics center.
[0060] In an embodiment of the present disclosure, the data receiving service may also parse the print data and logistics data, and return the parsing status to the print center and the logistics center. For example, the data receiving service parses the print data, and returns the parsing status of the print data to the print center; the data receiving service parses the logistics data, and returns the parsing status of the logistics data to the logistics center. For example, the data receiving service parses the print data and logistics data, and may perform a simple data verification on the data pushed by the logistics center and the print center, and return the verification result to the corresponding response. It is understandable that the verification result may be, for example, a successful preliminary parsing or a failed step parsing.
[0061] In a possible implementation, the read-only database may also be used to receive a data query request; and output target data in response to the data query request.
[0062] In an embodiment of the present disclosure, a read-only database may provide a query service. For example, a data query request may be received, and the data query request may be input by a user or an administrator. In response to the data query request, corresponding target data may be searched from the read-only database, and the target data may be retrieved.
[0063] In order to make the insurance policy data management system provided by the embodiment of the present disclosure clearer, the following is combined with Figure 2 Provide detailed explanation.
[0064] Based on the characteristics of real-time data transmission, large data volume, and rapid response, the following solutions and functions are designed to ensure system stability, scalability, high availability, data security, and consistency:
[0065] Figure 2 FIG. 1 is a schematic diagram of an insurance policy data management system provided by an embodiment of the present disclosure. Figure 2 As shown, the policy data management system may include data receiving service, printing center, logistics center, message queue service, object storage service, read-write database, read-only database, API service, data report service, data analysis service, data distribution service, monitoring service and SMS service. Among them:
[0066] (1) Hardware load balancing data receiving service high availability cluster
[0067] The data receiving service can use two high-availability cluster F5s for data receiving, with the servers configured as master and slave. When a server fails, the data receiving service is immediately transferred to another server to ensure uninterrupted real-time data transmission 24 hours a day. The dual-machine function is realized through load balancing hardware devices. This service performs heartbeat detection on the message queue server, data analysis database (read-write database), data distribution server, and data analysis service. Once the heartbeat of the service stops, the data receiving service will no longer receive data and return a failure response to the logistics center and the printing center. At the same time, the SMS service is called to send a text message to the administrator.
[0068] (2) Data reception service, which can be used to:
[0069] Data validity check: simple data verification is performed on the data pushed by the logistics center and the printing center, and the corresponding response is returned for the verification result. The pushed data is saved to the database. For abnormal data or original data reconciliation during analysis, it can be further processed through backup. The data is pushed to the business processing service. The data transmission volume is large, and the analysis is complex and time-consuming. In order to quickly receive, respond in time and reduce unnecessary IO and service memory consumption. No processing is done on the data, and it is directly put into the message queue after receiving.
[0070] (3) Message Queue Service
[0071] The custom thread-safe Queue cache achieves high availability and concurrent processing of services. This embodiment directly uses the Zbus technology message queue to provide data queuing processing services, and the data that enters the queue first is processed first.
[0072] (4)Data distribution service
[0073] The data distribution service is used to read cached data (raw data stored in the database). After preliminary analysis, it is transmitted to the corresponding data analysis service according to different business data. It can be increased or decreased according to the business scale. It includes heartbeat registration, data distribution, log recording and other functions.
[0074] (5) Cluster data analysis service (data analysis service)
[0075] The service responsible for business processing can be increased or decreased at any time according to the scale of business and data. When the load utilization is high, the service can be increased, and when the load utilization is low, the service can be reduced accordingly. Improve resource utilization. Multiple businesses can use one server, or one business can use multiple servers (middleware or containers). After the data is parsed, it is saved in the business database (read-write database). The business server and the distribution server (data distribution service) are connected by heartbeat packets. Every time a business server is turned on, it will register with one or more data distribution services and start immediately after registration. It includes functions such as heartbeat registration and logging.
[0076] (6) Data reporting service
[0077] Customized reports can be created based on the data from the printing center and logistics center of the paper insurance contract printing process to facilitate business analysis.
[0078] (7) Database (including read-write database and read-only database)
[0079] Through two physical machines, data synchronization and read-write separation can be carried out, and a domestic database can be used. Among them, the read-write database is the main database and the business database. The read-only database is the disaster recovery database, which is the database backup and provides read-only services.
[0080] (8) Monitoring Service
[0081] This service monitors the data receiving service, message queue service, read-write database, data distribution service, data analysis service, monitors the server status, and performs quality inspection on the data in the read-write database. Once an abnormality occurs, the SMS service is called to send a text message to the administrator.
[0082] (9) Object storage service: used to store files.
[0083] (10) Printing Center: Provides services for the unified distribution of printed paper documents, such as printing, printing, binding, etc.
[0084] (11) Logistics Center: Distributes paper delivery documents. All original logistics information passes through the logistics center.
[0085] (12) API service: It can help organizations centrally manage internal and external APIs, including API creation, document generation, version control, access control, subscription management, metering and billing, etc.
[0086] (13) SMS service: If the system encounters any abnormality, an alarm will be sent to the designated administrator via SMS.
[0087] Based on the above insurance policy data management system, its data flow can be as follows:
[0088] (1) The printing center pushes the completed print data to the logistics center and pushes the print data to the data receiving service. The data receiving service returns the preliminary parsing status to the printing center.
[0089] (2) The logistics center pushes logistics data to the data receiving service. The data receiving service returns the initial parsing status to the logistics center.
[0090] (3) After the data receiving service successfully analyzes the printing data and logistics data, it pushes the Json data and XML data to the message queue service. If the heartbeat detection fails, the service is stopped and the customized negotiation information of the upstream system is returned. The information is sent to the administrator via the SMS service.
[0091] (4) After receiving the Json or XML service, the message queue service saves it in the object storage service in the form of a file. The original print data and logistics data are stored in the main database, which is also the read-write database.
[0092] (5) The read-write database synchronizes data in real time to the read-only database, which is also the disaster recovery database. After this read-only database goes online, the operation and maintenance personnel can view the data. At the same time, the read-only database encapsulates the monitoring data to the API service for other system calls; in addition, it provides data to the data report service, collects various data to generate various reports, and provides reports to analysts.
[0093] (6) The data distribution service mainly reads the original data stored in the read-write database, and after preliminary analysis, transmits it to the corresponding data analysis service according to different business data.
[0094] (7) The data analysis service analyzes the data and saves it in the read-write database.
[0095] (8) The monitoring service monitors the data receiving service, message queue service, read-write database, data distribution service, and data analysis service, monitors the server status, and performs quality inspection on the data in the read-write database. Once an abnormality occurs, the SMS service is called to send a text message to the administrator.
[0096] (9) API services and data reporting services only use parsed data, not raw data.
[0097] As a specific example, the basic information of the data structure after the data parsing service is parsed can be shown in Table 1.
[0098] Table 1
[0099]
[0100]
[0101] Based on the above insurance policy data management system, examples of specific usage scenarios can be as follows:
[0102] (1) Query the delivery list
[0103] The delivery list query displays the delivery information of the policy that matches the query result. Click the express number to view the express information of the number. Click the total number to view the detailed information of the specific quantity. See Table 2.
[0104] Table 2
[0105] Query information illustrate Secondary institutions Display style: XX Provincial Branch Print Point Display style: YET-GZ Courier Display style: YET-SF Tracking number Display style: XXXXXXXXXXXXXXX total Display style: 1 state Display style: Delivered recipient Display style: XX Telephone Display style: 1XXXXXXXXX Phone number Display style: 1XXXXXXXXX Shipping address The display style is: Floor X, XX Building, No. XX, XX Road, XX District, XX City, XX Province Delivery time The display format is: YYYY-MM-DD HH:MM:SS Contract time The display format is: YYYY-MM-DD HH:MM:SS Delivery time The display format is: YYYY-MM-DD HH:MM:SS
[0106] Click the express number to display the express logistics information. Click the total number to display the content information, as shown in Table 3.
[0107] Table 3
[0108] Query information illustrate Third-level institutions Display style: 1440899 Four-level institution The display style is;-- Category Display style: Policy Business Type Display style: Personal insurance SET_KEY The display style is: 202310090369090321 Reprint serial number Display style: 0 state Display style: Delivered time The display format is: YYYY-MM-DD HH:MM:SS Product Readiness Time The display format is: YYYY-MM-DD HH:MM:SS Product planning time The display format is: YYYY-MM-DD HH:MM:SS Product completion time The display format is: YYYY-MM-DD HH:MM:SS Packaging ready time The display format is: YYYY-MM-DD HH:MM:SS Packing plan time The display format is: YYYY-MM-DD HH:MM:SS Packing completion time The display format is: YYYY-MM-DD HH:MM:SS Parcel pickup time The display format is: YYYY-MM-DD HH:MM:SS Package receipt time The display format is: YYYY-MM-DD HH:MM:SS Level 5 institutions The display style is:-- First-level institution Display style: China People's Insurance Secondary institutions Display style: Handong Branch Policy Number The display style is: 370694777584008
[0109] (2) Business progress
[0110] Query conditions: The query condition function is to view the corresponding relevant insurance policy business progress information based on the institution, business company, business type, and data time as query conditions.
[0111] Query progress list: The query business progress list is to display the business progress information of different business types of each institution that meets the query results. Click the total number or the number of issued numbers to view the business progress list information of the corresponding business type of a certain institution. See Table 4. Table 4
[0112] Query information illustrate Data date Display format: YYYY-MM-DD First-level institution The display style is; XXXX insurance Secondary institutions Display style: XX branch Business Type Display style: Personal insurance total Display style: 4 Number of issued Display style: 4 (100%) Number of pending releases Display style: 0
[0113] Click the total number to view the business progress list information of the corresponding business type of a certain institution. Click the number of issued items to view the business progress list information of the corresponding business type of a certain institution. See Table 5.
[0114] Table 5
[0115] Query information illustrate Secondary institutions Display style: XX branch Category Display style: Policy Business Type Display style: Personal insurance UUID The display style is: B216EBC6-C6F5-82E0-8C7C-0C5D478AEF7F Policy Number The display style is: 12012345678008 Print Point Display style: LRX-BJ Current Status Display style: Package Pickup Data time The display format is: YYYY-MM-DD HH:MM:SS Issue time The display format is: YYYY-MM-DD HH:MM:SS
[0116] Click the pending number to view the business progress list information of the corresponding business type of a certain institution. See Table 6.
[0117] Table 6
[0118] Query information illustrate Secondary institutions Display style: XX branch Category Display style: Policy Business Type Display style: Personal insurance UUID The display style is: B216EBC6-C6F5-82E0-8C7C-0C5D478AEF7F Policy Number The display style is: 120123456789008 Data time The display format is: YYYY-MM-DD HH:MM:SS
[0119] (3) Task progress
[0120] Query conditions: The query condition function is to view the corresponding relevant policy task progress information based on the institution, business type, outsourcer, and task date as query conditions.
[0121] Query progress list: Query task progress list is to display the task progress information related to different business types of each organization that meets the query results. Click the number of dispatches, plans, productions, packaging, contracts and deliveries to view the task progress list information for the corresponding business type of an organization.
[0122] Click the number of dispatched, planned, produced, packaged, contracted and delivered items to view the task progress list information of the corresponding business type of an organization. The titles displayed on the page are different (number of dispatched, planned, produced, packaged, contracted and delivered items), but the content displayed in the list title is the same. See Table 7.
[0123] Table 7
[0124] Query information illustrate Third-level institutions The display style is:-- Four-level institution The display style is:-- Business Type Display style: Personal insurance policy SET_KEY The display style is: 2023101123456789041 Print Point Display style: LRX-BJ Current Status Display style: Delivered Data time The display format is: YYYY-MM-DD HH:MM:SS Issue time The display format is: YYYY-MM-DD HH:MM:SS Plan time The display format is: YYYY-MM-DD HH:MM:SS Production time The display format is: YYYY-MM-DD HH:MM:SS Packaging ready time The display format is: YYYY-MM-DD HH:MM:SS Packing plan time The display format is: YYYY-MM-DD HH:MM:SS Packing completion time The display format is: YYYY-MM-DD HH:MM:SS Contract time The display format is: YYYY-MM-DD HH:MM:SS Delivery time The display format is: YYYY-MM-DD HH:MM:SS First-level institution The display style is; XXXX insurance Secondary institutions Display style: XX branch Level 5 institutions Display style: XX branch Policy Number The display style is: 37012347774008
[0125] \(4) Receipt management
[0126] Query conditions: The query condition function is to use the express number, insurance policy number, and delivery time as query conditions to view the corresponding relevant insurance policy task progress information.
[0127] Query result display: The query receipt progress list displays the progress information of the relevant receipt tasks for each express number that matches the query result. Click the express number to view the corresponding express information of the express number, click the total number of receipts to view the corresponding receipt task progress list information of the express number, and click to be signed for operation (sign for button). See Table 8.
[0128] Table 8
[0129] Query information illustrate Logistics Company The display styles are: Tracking number Display style: xxxxxxxxxxxxxxxxxxxx Delivery time The display format is: YYYY-MM-DD HH:MM:SS recipient Display style: XX Recipient's phone number Display style: 1xxxxxxxxxx Shipping address The display style is: No. xxxx, xx Street, xx District, xx City Total number of items received Display style: 1 Waiting for signature Display style: 1 Signed for Display style: 0
[0130] Click the express number to display the express information. Click the total number of received items to view the progress list of the receiving task corresponding to the express number, see Table 9.
[0131] Table 9
[0132]
[0133] 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).
[0134] 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.
[0135] 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.
[0136] 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.
[0137] 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. An insurance policy data management system, characterized in that: It includes data receiving service, printing center, logistics center, message queue service, and object storage service, among which: The data receiving service is used to receive the logistics data pushed by the logistics center and the printing data pushed by the printing center; parse the logistics data and the printing data to obtain the parsed logistics data and printing data, wherein the parsed logistics data and printing data are Json data and XML data; and push the Json data and XML data to the message queue service; The message queue service is used to store the Json data and XML data in the object storage service.
2. The insurance policy data management system according to claim 1, characterized in that: It also includes read-write database, read-only database and API services, among which, The message queue service is further used to store the original data of the logistics data and the printing data into the read-write database; The read-write database is used to synchronize the original data of the logistics data and the printing data to the read-only database; The read-only database is used to encapsulate monitoring data into the API service.
3. The insurance policy data management system according to claim 2, characterized in that: It also includes a data report service for generating a data report based on the data in the read-only database.
4. The insurance policy data management system according to claim 2, characterized in that: It also includes data analysis services and data distribution services, among which, The data distribution service is used to read the original data stored in the read-write database; and transmit different business data to the corresponding data analysis service; The data analysis service is used to perform preliminary analysis on the original data; and to store the analyzed data in the read-write database.
5. The insurance policy data management system according to claim 4, characterized in that: It also includes monitoring services and SMS services, among which, The monitoring service is used to monitor the service status of the data receiving service, the message queue service, the read-write database, the data distribution service, and the data parsing service; and to perform quality detection on the data in the read-write database; The SMS service is used to output SMS to a preset device when the data quality in the read-write database does not meet the preset requirements.
6. The insurance policy data management system according to claim 4, characterized in that: The data receiving service is further used to perform heartbeat detection on the message queue service, the data parsing service, the read-write database, and the data distribution service; And, when there is a problem with the heartbeat detection result, it is used to stop the service corresponding to the problematic heartbeat detection result.
7. The insurance policy data management system according to claim 6, characterized in that: The SMS service is further used to generate SMS information based on the service corresponding to the problematic heartbeat detection result, and output the SMS information to the management device.
8. The insurance policy data management system according to any one of claims 1 to 7, characterized in that: The data receiving service is also used to parse the printing data and return the parsing status of the printing data to the printing center; and to parse the logistics data and return the parsing status of the logistics data to the logistics center.
9. The insurance policy data management system according to claim 2, characterized in that: The API service is used to connect to systems other than the insurance policy data management system.
10. The insurance policy data management system according to claim 2, characterized in that: The read-only database is also used to receive a data query request; and output target data in response to the data query request.
