A distributed data verification method and device, computer equipment and storage medium

Abstract

The application discloses a distributed data verification method and device, computer equipment and a storage medium, and belongs to the technical field of big data and the field of production line finance. The application obtains a plurality of business sub-processes by disassembling a business process, encapsulates each business sub-process and a matching verification program corresponding to each business sub-process into a microservice to obtain a plurality of microservices, constructs a message queue, and monitors the message queue. When it is monitored that there is a data verification request in the message queue, each microservice is instructed to perform data verification based on the data verification request, a plurality of data verification results are obtained, and the plurality of data verification results are stored and output. The application also relates to the technical field of blockchains. The data to be verified can be stored in a blockchain network. The application disassembles a business process into a plurality of microservices, and performs data verification through the plurality of microservices, thereby improving the efficiency of data verification.

Description

Technical Field

[0001] This application belongs to the fields of big data technology and industrial finance, and specifically relates to a distributed data verification method, device, computer equipment and storage medium. Background Technology

[0002] In practice, complex business processes typically involve multiple steps. For example, an insurance claims process includes steps such as reporting the claim, loss assessment, verification, settlement, and payment. Each step relies on data from the previous step, and a large amount of data is transferred and processed throughout the process. If a problem occurs in the reporting step—for example, missing or incorrect information—this error will propagate to subsequent steps, such as loss assessment, verification, and settlement, causing errors throughout the entire claims process. Troubleshooting these issues requires significant manpower, especially when errors occur at the initial steps. As the complexity of the business scenario increases, the number of steps also increases, leading to a greater likelihood of errors. This forces developers to spend more time on maintenance, reducing their time available for developing new business applications. Summary of the Invention

[0003] The purpose of this application is to propose a distributed data verification method, apparatus, computer equipment, and storage medium to solve the technical problem that existing data verification schemes require a large investment of human and material resources when the business scenario is highly complex.

[0004] To address the aforementioned technical problems, this application provides a distributed data verification method, employing the following technical solution:

[0005] A distributed data verification method, comprising:

[0006] Obtain the business process and break it down into several sub-business processes;

[0007] Obtain the data verification program matching each business sub-process to obtain the matching verification program;

[0008] Each business sub-process and its corresponding matching and verification program are encapsulated into a microservice, resulting in several microservices.

[0009] Build a message queue and use the message queue to establish the first communication between microservices;

[0010] Monitor the message queue, and when a data verification request is detected in the message queue, send the data verification request to each microservice.

[0011] Based on the data verification request, each microservice is instructed to perform data verification, obtain several data verification results, and store and output these results.

[0012] Furthermore, the business process is obtained and broken down into several sub-processes, specifically including:

[0013] Obtain the business process, parse the business process, and identify the process nodes in the business process;

[0014] The business process is broken down into several sub-processes based on the process nodes.

[0015] Furthermore, after encapsulating each business sub-process and its corresponding matching and verification program into microservices, resulting in several microservices, the process also includes:

[0016] Obtain the business functions and data interaction requirements for each business sub-process;

[0017] Define the data interface of the microservice corresponding to each business sub-process based on the business function and data interaction requirements of each business sub-process, and define several data interfaces of the microservices.

[0018] Construct a second communication mechanism between microservices based on the data interfaces of several microservices;

[0019] After completing the construction of the second communication, several microservices are deployed into the microservice framework.

[0020] Furthermore, the message queue is monitored. When a data verification request is detected in the message queue, the data verification request is sent to each microservice. Specifically, this includes:

[0021] Monitor the message queue, and when a data verification request is detected in the message queue, retrieve the data verification request in sequence;

[0022] Identify the microservice that matches the data validation request and send the data validation request to the matching microservice.

[0023] Furthermore, after building the message queue and establishing the first communication between microservices through the message queue, it also includes:

[0024] Define the message format of the message queue, wherein the message format includes at least the business sub-process identifier, the verification program identifier, and the data to be verified;

[0025] Identify the microservice that matches the data validation request and send the data validation request to the matching microservice. This includes:

[0026] The obtained data verification request is parsed to obtain the business sub-process identifier, verification program identifier, and data to be verified from the data verification request.

[0027] Identify the microservice that matches the business subprocess identifier, and send the verification program identifier and the data to be verified to the matching microservice.

[0028] Furthermore, based on the data verification request, each microservice is instructed to perform data verification, resulting in several data verification results. These results are then stored and output, specifically including:

[0029] Each microservice is instructed to call its corresponding matching verification procedure based on its verification procedure identifier.

[0030] Each microservice is instructed to execute its corresponding matching and verification procedure to perform data verification on the data to be verified for each microservice, and to obtain several data verification results.

[0031] The system integrates several data verification results, stores the integrated data verification results in a preset database, and outputs the integrated data verification results.

[0032] Furthermore, after instructing each microservice to perform data verification based on the data verification request, obtaining several data verification results, and storing and outputting these results, the process also includes:

[0033] Data verification and integration results are retrieved from the database according to a preset time period;

[0034] Visualize the results of data verification and integration.

[0035] To address the aforementioned technical problems, this application also provides a distributed data verification device, which employs the following technical solution:

[0036] A distributed data verification device, comprising:

[0037] The process decomposition module is used to obtain the business process and decompose it into several business sub-processes.

[0038] The program matching module is used to obtain the data verification program for each business sub-process and obtain the matching verification program.

[0039] The process encapsulation module is used to encapsulate each business sub-process and the matching and verification program corresponding to each business sub-process into a microservice, resulting in several microservices.

[0040] The message queue module is used to build message queues and establish the first communication between microservices through message queues;

[0041] The request monitoring module is used to monitor the message queue. When a data verification request is detected in the message queue, the data verification request is sent to each microservice.

[0042] The data verification module is used to instruct each microservice to perform data verification based on the data verification request, obtain several data verification results, and store and output the several data verification results.

[0043] To address the aforementioned technical problems, this application also provides a computer device that employs the following technical solution:

[0044] A computer device includes a memory and a processor, the memory storing computer-readable instructions, the processor executing the computer-readable instructions to implement the steps of the distributed data verification method as described in any of the preceding claims.

[0045] To address the aforementioned technical problems, this application also provides a computer-readable storage medium, employing the technical solution described below:

[0046] A computer-readable storage medium storing computer-readable instructions, which, when executed by a processor, implement the steps of the distributed data verification method as described in any one of the preceding descriptions.

[0047] Compared with the prior art, the embodiments of this application have the following main advantages:

[0048] This application discloses a distributed data verification method, apparatus, computer equipment, and storage medium, belonging to the fields of big data technology and production line finance. This application obtains a business process and decomposes it into several sub-processes. For each sub-process, a matching data verification program is obtained. Each sub-process and its corresponding matching verification program are encapsulated into microservices, resulting in several microservices. A message queue is constructed, and the first communication between the microservices is established through the message queue. The message queue is monitored, and when a data verification request is detected, it is sent to each microservice. Based on the data verification request, each microservice is instructed to perform data verification, resulting in several data verification results, which are then stored and output. By decomposing the business process into multiple microservices and performing data verification through these microservices, combined with message queues and database storage, this application achieves an efficient, decoupled, and asynchronous data verification process, improving the data quality of insurance claims processes, reducing the transmission of erroneous data, and saving manpower and time costs. Attached Figure Description

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

[0050] Figure 1 An exemplary system architecture diagram is shown, in which this application can be applied;

[0051] Figure 2 A flowchart of one embodiment of the distributed data verification method according to this application is shown;

[0052] Figure 3 A schematic diagram of the structure of one embodiment of the distributed data verification device according to this application is shown;

[0053] Figure 4 A schematic diagram of the structure of one embodiment of a computer device according to this application is shown. Detailed Implementation

[0054] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein in the specification of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings of this application, are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings of this application are used to distinguish different objects, not to describe a particular order.

[0055] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0056] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0057] like Figure 1As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0058] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social media platform software, etc.

[0059] Terminal devices 101, 102, and 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 players (Moving Picture Experts Group Audio Layer IV), laptops, and desktop computers, etc.

[0060] Server 105 can be a server that provides various services, such as a backend server that supports the pages displayed on terminal devices 101, 102, and 103. The server can be a standalone server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0061] It should be noted that the distributed data verification method provided in this application embodiment is generally executed by a server, and correspondingly, the distributed data verification device is generally set in the server.

[0062] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0063] Continue to refer to Figure 2The diagram illustrates a flowchart of an embodiment of the distributed data verification method according to this application. Embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence (AI) refers to the theories, methods, technologies, and application systems that utilize digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0064] Foundational technologies for artificial intelligence generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interactive systems, and mechatronics. AI software technologies mainly encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0065] In the property and casualty insurance financial sector, complex business processes are common. For example, consider an insurance claims process that involves multiple steps, such as reporting the incident, assessing the damage, verifying the loss, calculating the settlement, and making the payment. Each step depends on the data from the previous step, and a large amount of data is transferred and processed throughout the entire process.

[0066] Suppose that there is a problem with the data in the reporting step of this business process, such as missing or incorrect information. This error will be passed on to subsequent steps, such as loss assessment, loss verification and settlement, causing errors in the entire claims process. In order to investigate and fix this problem, a lot of manpower and resources need to be invested to track and analyze the data problems in each step step by step.

[0067] As business scenarios become more complex, the number of steps in the claims process also increases, such as adding anti-fraud verification and image review. This increases the likelihood of errors because each step has potential data problems. Developers need to invest more time and effort to investigate and fix these errors, thereby reducing the time they can spend developing new businesses.

[0068] To address the aforementioned technical issues, this application discloses a distributed data verification method, apparatus, computer equipment, and storage medium, belonging to the fields of big data technology and production line finance. This application decomposes business processes into multiple microservices and performs data verification through these microservices, combined with message queues and database storage, to achieve an efficient, decoupled, and asynchronous data verification process. This improves the data quality of insurance claims business processes, reduces the transmission of erroneous data, and saves manpower and time costs.

[0069] The distributed data verification method includes the following steps:

[0070] S201: Obtain the business process and break it down into several sub-business processes.

[0071] In this embodiment, the conventional business process is first analyzed and decomposed to identify each independent step, i.e., the business sub-process. By decomposing the insurance claims business process into business sub-processes, it is convenient to encapsulate the business sub-processes into microservices in subsequent steps, thereby achieving the independence and flexibility of each business sub-process.

[0072] Furthermore, the business process is obtained and broken down into several sub-processes, specifically including:

[0073] Obtain the business process, parse the business process, and identify the process nodes in the business process;

[0074] The business process is broken down into several sub-processes based on the process nodes.

[0075] In this embodiment, by acquiring the business process, parsing the business process, identifying the process nodes in the business process, and splitting the business process according to the process nodes, several business sub-processes are obtained.

[0076] In a specific embodiment of this application, breaking down a conventional business process into multiple microservices requires a deep understanding of the structure and function of the business process and the determination of the process nodes. The following is an example of the insurance claims business process. In the insurance claims business process, there are multiple process nodes such as reporting the incident, loss assessment, loss verification, settlement calculation, payment, and archiving. The insurance claims business process can be broken down through these process nodes to obtain multiple business sub-processes that can independently complete the tasks of the process nodes.

[0077] S202, obtain the data verification program matching each business sub-process, and obtain the matching verification program.

[0078] In this embodiment, each business sub-process has its specific data validation requirements, necessitating the identification of a suitable validation program to perform the data validation operation. These validation programs are pre-defined by the developers and constitute a set of validation programs used to perform data validation and verify the accuracy and integrity of the data in the business sub-process. Before microservice encapsulation, a matching data validation program needs to be found for each business sub-process.

[0079] S203 encapsulates each business sub-process and its corresponding matching and verification program into a microservice, resulting in several microservices.

[0080] In this embodiment, each business sub-process and its corresponding matching and verification program are encapsulated to construct a set of microservices. Each microservice in this set carries a business sub-process and its corresponding data verification function, and provides an independent service interface for other components or systems to call and use. The microservice encapsulation method can improve the maintainability, scalability and flexibility of the system.

[0081] In the specific embodiments described above, the business sub-processes of insurance claims are encapsulated to obtain the following microservice example:

[0082] Claim Reporting Service: This microservice handles the claim reporting process for insurance claims. It provides an interface for insured individuals or their agents to report claims and input / verify basic information, including insured information, accident description, and relevant evidence.

[0083] Estimation Service: This microservice handles the claims assessment process. After receiving the claim information, it calculates the estimated loss amount based on the insurance terms and assessment rules, and generates an assessment report.

[0084] Damage Assessment Service: This microservice handles the claims assessment process. It receives loss assessment reports, reviews them, verifies the reasonableness of the assessed amount, and confirms whether it falls within the scope of compensation stipulated in the insurance contract.

[0085] Claim Settlement Service: This microservice handles the claims settlement process. It receives approved loss assessment reports, performs settlement calculations, determines the final compensation amount, and generates a settlement statement.

[0086] Claim Payment Service: This microservice handles the claims payment process. It receives claim requests, processes payments based on the payment method and channel, and generates payment vouchers.

[0087] The Archiving Service is responsible for handling the claims archiving process. This microservice is responsible for archiving and preserving claims-related documents and data for future auditing and retrieval.

[0088] In the above embodiments, by decomposing the insurance claims business process into the above microservices, the independence and flexibility of each step can be achieved. Each microservice focuses on its own responsibilities and functions. Through clearly defined interfaces and data interaction methods, the collaboration between microservices can be realized, thereby improving the maintainability and scalability of the system.

[0089] Furthermore, after encapsulating each business sub-process and its corresponding matching and verification program into microservices, resulting in several microservices, the process also includes:

[0090] Obtain the business functions and data interaction requirements for each business sub-process;

[0091] Define the data interface of the microservice corresponding to each business sub-process based on the business function and data interaction requirements of each business sub-process, and define several data interfaces of the microservices.

[0092] Construct a second communication mechanism between microservices based on the data interfaces of several microservices;

[0093] After completing the construction of the second communication, several microservices are deployed into the microservice framework.

[0094] In this embodiment, after analyzing and decomposing the conventional business process and identifying each independent business sub-process, a suitable programming language and microservice framework are determined based on the business functions and data interaction requirements of each business sub-process. This is to encapsulate the business sub-process into a microservice and to deploy the microservice subsequently. In addition, appropriate interfaces need to be defined for each microservice so that other microservices can call and communicate with it.

[0095] S204, build a message queue, and use the message queue to establish the first communication between microservices.

[0096] Message Queues (MQ) are middleware technologies used for message passing in distributed systems. They allow different applications or components to communicate asynchronously by sending and receiving messages, decoupling the direct dependencies between senders and receivers. In a message queue, the sender puts a message into the queue, and the receiver retrieves the message from the queue for processing. The message queue acts as an intermediary, reliably storing and delivering messages, ensuring message reliability and durability. Message queues provide an asynchronous communication model where senders and receivers do not need to be online simultaneously and can work independently.

[0097] In this embodiment, a message queue is constructed and configured, including creating topics or queues and setting access permissions. A corresponding message queue client library is integrated into each microservice to communicate with the message queue, thereby enabling the first communication between microservices.

[0098] Furthermore, after building the message queue and establishing the first communication between microservices through the message queue, it also includes:

[0099] Define the message format of the message queue, wherein the message format includes at least the business sub-process identifier, the verification program identifier, and the data to be verified.

[0100] In this embodiment, a consistent message format is defined, including business sub-process identifiers, verification program identifiers, and data to be verified, to ensure that microservices can correctly parse and process messages. Common data exchange formats, such as JSON or XML, are used to represent the structure and content of messages. Clear verification task execution specifications are defined to ensure that each microservice can execute the corresponding verification task according to the instructions in the message.

[0101] In a specific embodiment of this application, a message queue (MQ) is selected to send and receive data verification information. Each microservice subscribes to the MQ using its own service-related tags. Developers use the MQ to send and call specified tasks sequentially through a public service, waiting for each service to consume the data.

[0102] In the above embodiments, message queues are used as a communication mechanism between microservices to achieve asynchronous data transmission. Each microservice can receive the data to be processed by subscribing to the relevant message queue, then execute the corresponding verification logic, and send the result to the message queue of the next step.

[0103] S205 monitors the message queue. When a data verification request is detected in the message queue, the data verification request is sent to each microservice.

[0104] In this embodiment, developers send a series of messages, namely data verification requests, sequentially in the message queue (MQ) through public services. The status of messages in the message queue is monitored in real time through monitoring tools or custom monitoring mechanisms. Monitoring can include detecting the number of messages in the queue, message attributes, message status, etc. Once data verification requests are detected in the message queue, the system will identify these requests and send them to the corresponding microservices.

[0105] In this embodiment, the distributed data verification method runs on an electronic device (e.g., Figure 1 The server shown can receive data verification requests via wired or wireless connection. It should be noted that the aforementioned wireless connection methods may include, but are not limited to, 3G / 4G connections, WiFi connections, Bluetooth connections, WiMAX connections, Zigbee connections, UWB (ultra-wideband) connections, and other currently known or future wireless connection methods.

[0106] Furthermore, the message queue is monitored. When a data verification request is detected in the message queue, the data verification request is sent to each microservice. Specifically, this includes:

[0107] Monitor the message queue, and when a data verification request is detected in the message queue, retrieve the data verification request in sequence;

[0108] Identify the microservice that matches the data validation request and send the data validation request to the matching microservice.

[0109] In this embodiment, the message queue is monitored. When a data verification request is detected in the message queue, the data verification request is obtained sequentially. The microservice that matches the data verification request is determined by the request identifier, and the data verification request is sent to the matching microservice.

[0110] Identify the microservice that matches the data validation request and send the data validation request to the matching microservice. This includes:

[0111] The obtained data verification request is parsed to obtain the business sub-process identifier, verification program identifier, and data to be verified from the data verification request.

[0112] Identify the microservice that matches the business subprocess identifier, and send the verification program identifier and the data to be verified to the matching microservice.

[0113] In this embodiment, the business subprocess identifier in the data verification request is obtained by parsing the data verification request. The microservice that matches the business subprocess identifier is determined by the business subprocess identifier. The parsed verification program identifier and the data to be verified are sent to the matching microservice for subsequent data verification.

[0114] S206 instructs each microservice to perform data verification based on the data verification request, obtains several data verification results, and stores and outputs these results.

[0115] In this embodiment, after each microservice receives a data verification request, it starts its own data verification program to verify the data to be verified contained in the data verification request. Each microservice outputs a data verification result, integrates all data verification results, and stores and visualizes the data verification results.

[0116] Furthermore, based on the data verification request, each microservice is instructed to perform data verification, resulting in several data verification results. These results are then stored and output, specifically including:

[0117] Each microservice is instructed to call its corresponding matching verification procedure based on its verification procedure identifier.

[0118] Each microservice is instructed to execute its corresponding matching and verification procedure to perform data verification on the data to be verified for each microservice, and to obtain several data verification results.

[0119] The system integrates several data verification results, stores the integrated data verification results in a preset database, and outputs the integrated data verification results.

[0120] In this embodiment, each microservice is instructed to call the corresponding matching verification program according to the verification program identifier of each microservice, and each microservice is instructed to execute the corresponding matching verification program to perform data verification on the data to be verified of each microservice, so as to obtain several data verification results, integrate the several data verification results, store the integrated data verification results in a preset database, and output the integrated data verification results.

[0121] Furthermore, after instructing each microservice to perform data verification based on the data verification request, obtaining several data verification results, and storing and outputting these results, the process also includes:

[0122] Data verification and integration results are retrieved from the database according to a preset time period;

[0123] Visualize the results of data verification and integration.

[0124] In this embodiment, data verification and integration results are retrieved from the database according to a preset time period, such as 24h, 48h, etc. The data verification and integration results are then visualized, for example, rendered into a visual chart and sent via email, so that analysts can more intuitively monitor the data status of process nodes.

[0125] In the above embodiments, this application discloses a distributed data verification method, belonging to the fields of big data technology and production line finance. This application obtains a business process and decomposes it into several sub-processes. It obtains a matching data verification program for each sub-process, encapsulates each sub-process and its corresponding matching verification program into microservices, resulting in several microservices. A message queue is constructed, and first communication between the microservices is established through the message queue. The message queue is monitored, and when a data verification request is detected, it is sent to each microservice. Based on the data verification request, each microservice is instructed to perform data verification, resulting in several data verification results, which are then stored and output. By decomposing the business process into multiple microservices and performing data verification through these microservices, combined with message queues and database storage, this application achieves an efficient, decoupled, and asynchronous data verification process, improving the data quality of the insurance claims business process, reducing the transmission of erroneous data, and saving manpower and time costs.

[0126] It should be emphasized that, in order to further ensure the privacy and security of the data to be verified, the data to be verified can also be stored in a node of a blockchain.

[0127] The blockchain referred to in this application is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include an underlying blockchain platform, a platform product service layer, and an application service layer.

[0128] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware through computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium. When executed, the computer-readable instructions can include the processes of the embodiments of the above methods. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, optical disk, or read-only memory (ROM), or random access memory (RAM).

[0129] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0130] Further reference Figure 3 As a response to the above Figure 2 To implement the method shown, this application provides an embodiment of a distributed data verification device, which is similar to... Figure 2 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0131] like Figure 3 As shown, the distributed data verification device 300 described in this embodiment includes:

[0132] The process decomposition module 301 is used to obtain the business process and decompose the business process into several business sub-processes.

[0133] The program matching module 302 is used to obtain the data verification program for each business sub-process and obtain the matching verification program.

[0134] The process encapsulation module 303 is used to encapsulate each business sub-process and the matching and verification program corresponding to each business sub-process into a microservice, resulting in several microservices.

[0135] Message queue module 304 is used to build message queues and establish the first communication between microservices through message queues;

[0136] The monitoring module 305 is used to monitor the message queue. When a data verification request is detected in the message queue, the data verification request is sent to each microservice.

[0137] The data verification module 306 is used to instruct each microservice to perform data verification based on the data verification request, obtain several data verification results, and store and output the several data verification results.

[0138] Furthermore, the process decomposition module 301 specifically includes:

[0139] The node identification unit is used to acquire the business process, parse the business process, and identify the process nodes in the business process.

[0140] The process decomposition unit is used to break down a business process into several business sub-processes based on process nodes.

[0141] Furthermore, the distributed data verification device 300 also includes:

[0142] The functional requirements module is used to obtain the business functions and data interaction requirements of each business sub-process.

[0143] The interface definition module is used to define the data interface of the microservice corresponding to each business sub-process according to the business function and data interaction requirements of each business sub-process, and several microservice data interfaces.

[0144] The communication building module is used to build a second communication between microservices based on the data interfaces of several microservices;

[0145] The microservice deployment module is used to deploy several microservices into the microservice framework after the second communication is completed.

[0146] Furthermore, the monitoring module 305 specifically includes:

[0147] The message monitoring unit is used to monitor the message queue. When a data verification request is detected in the message queue, the data verification request is retrieved sequentially.

[0148] The request sending unit is used to determine the microservice that matches the data verification request and send the data verification request to the matching microservice.

[0149] Furthermore, the distributed data verification device 300 also includes:

[0150] The format definition module is used to define the message format of the message queue. The message format includes at least the business sub-process identifier, the verification program identifier, and the data to be verified.

[0151] The request sending unit specifically includes:

[0152] The request parsing subunit is used to parse the acquired data verification request to obtain the business subprocess identifier, verification program identifier, and data to be verified in the data verification request;

[0153] The data sending subunit is used to determine the microservice that matches the business subprocess identifier and send the verification program identifier and the data to be verified to the matching microservice.

[0154] Furthermore, the data verification module 306 specifically includes:

[0155] The program invocation unit is used to instruct each microservice to invoke the corresponding matching verification program based on the verification program identifier of each microservice.

[0156] The data verification unit is used to instruct each microservice to execute the corresponding matching verification program to verify the data to be verified in each microservice and obtain several data verification results.

[0157] The result output unit is used to integrate several data verification results, store the integrated data verification results in a preset database, and output the integrated data verification results.

[0158] Furthermore, the distributed data verification device 300 also includes:

[0159] The result acquisition module is used to retrieve data verification and integration results from the database according to a preset time period.

[0160] The visualization output module is used to visualize the results of data verification and integration.

[0161] In the above embodiments, this application discloses a distributed data verification device, belonging to the fields of big data technology and production line finance. This application acquires a business process and decomposes it into several sub-processes. It acquires a matching data verification program for each sub-process, and encapsulates each sub-process and its corresponding matching verification program into microservices, resulting in several microservices. A message queue is constructed, and first communication between the microservices is established through the message queue. The message queue is monitored, and when a data verification request is detected, it is sent to each microservice. Based on the data verification request, each microservice is instructed to perform data verification, resulting in several data verification results, which are then stored and output. By decomposing the business process into multiple microservices and performing data verification through these microservices, combined with message queues and database storage, this application achieves an efficient, decoupled, and asynchronous data verification process, improving the data quality of the insurance claims business process, reducing the transmission of erroneous data, and saving manpower and time costs.

[0162] To address the aforementioned technical problems, embodiments of this application also provide a computer device. Please refer to [link / reference needed]. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0163] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected via a system bus. It should be noted that only the computer device 4 with components 41-43 is shown in the figure; however, it should be understood that it is not required to implement all the shown components, and more or fewer components can be implemented alternatively. Those skilled in the art will understand that the computer device described here is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0164] The computer device can be a desktop computer, laptop, handheld computer, or cloud server, etc. The computer device can interact with the user via a keyboard, mouse, remote control, touchpad, or voice control.

[0165] The memory 41 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 41 may be an internal storage unit of the computer device 4, such as the hard disk or memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 4. Of course, the memory 41 may also include both the internal storage unit and its external storage device of the computer device 4. In this embodiment, the memory 41 is typically used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions for distributed data verification methods. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or will be output.

[0166] In some embodiments, the processor 42 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. The processor 42 is typically used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to execute computer-readable instructions stored in the memory 41 or to process data, for example, to execute computer-readable instructions of the distributed data verification method.

[0167] The network interface 43 may include a wireless network interface or a wired network interface, which is typically used to establish communication connections between the computer device 4 and other electronic devices.

[0168] In the above embodiments, this application discloses a computer device belonging to the fields of big data technology and production line finance. This application acquires a business process and decomposes it into several sub-processes. It acquires a data verification program matching each sub-process, and encapsulates each sub-process and its corresponding matching program into microservices, resulting in several microservices. A message queue is constructed, and first communication between the microservices is established through the message queue. The message queue is monitored, and when a data verification request is detected, it is sent to each microservice. Based on the data verification request, each microservice is instructed to perform data verification, resulting in several data verification results, which are then stored and output. By decomposing the business process into multiple microservices and performing data verification through these microservices, combined with message queues and database storage, this application achieves an efficient, decoupled, and asynchronous data verification process, improving the data quality of the insurance claims business process, reducing the transmission of erroneous data, and saving manpower and time costs.

[0169] This application also provides another embodiment, namely, providing a computer-readable storage medium storing computer-readable instructions that can be executed by at least one processor to cause the at least one processor to perform the steps of the distributed data verification method described above.

[0170] In the above embodiments, this application discloses a computer-readable storage medium, belonging to the fields of big data technology and production line finance. This application acquires a business process and decomposes it into several sub-processes. It acquires a data verification program matching each sub-process, and encapsulates each sub-process and its corresponding matching program into microservices, resulting in several microservices. A message queue is constructed, and first communication between the microservices is established through the message queue. The message queue is monitored, and when a data verification request is detected, it is sent to each microservice. Based on the data verification request, each microservice is instructed to perform data verification, resulting in several data verification results, which are then stored and output. By decomposing the business process into multiple microservices and performing data verification through these microservices, combined with message queues and database storage, this application achieves an efficient, decoupled, and asynchronous data verification process, improving the data quality of the insurance claims business process, reducing the transmission of erroneous data, and saving manpower and time costs.

[0171] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0172] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0173] Obviously, the embodiments described above are only some embodiments of this application, not all embodiments. The accompanying drawings show preferred embodiments of this application, but do not limit the patent scope of this application. This application can be implemented in many different forms; rather, the purpose of providing these embodiments is to provide a more thorough and comprehensive understanding of the disclosure of this application. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this application's specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the scope of patent protection of this application.

Claims

1. A distributed data verification method, characterized in that, include: Obtain the business process and break it down into several sub-business processes; Obtain the data verification program matching each business sub-process to obtain the matching verification program; Each business sub-process and its corresponding matching and verification program are encapsulated into a microservice, resulting in several microservices. These microservices constitute a set of microservices. Each microservice in the set of microservices carries a business sub-process and its corresponding data verification function. Each microservice provides an independent service interface for other components or systems to call and use. Construct a message queue, and use the message queue to establish the first communication between the microservices; Monitor the message queue, and when a data verification request is detected in the message queue, send the data verification request to each microservice; Based on the data verification request, each microservice is instructed to perform data verification, resulting in several data verification results, which are then stored and output. After encapsulating each business sub-process and its corresponding matching and verification program into microservices to obtain several microservices, the process further includes: Obtain the business functions and data interaction requirements for each business sub-process; Based on the business functions and data interaction requirements of each business sub-process, define the data interface of the microservice corresponding to each business sub-process, and obtain several data interfaces of microservices. A second communication mechanism between the microservices is constructed based on the data interfaces of several microservices; After completing the construction of the second communication, several microservices are deployed into the microservice framework.

2. The distributed data verification method as described in claim 1, characterized in that, The process of obtaining the business process and breaking it down into several sub-processes specifically includes: Obtain the business process, parse the business process, and identify the process nodes in the business process; The business process is divided into several sub-processes based on the process nodes.

3. The distributed data verification method as described in claim 1 or 2, characterized in that, The monitoring of the message queue, upon detecting a data verification request in the message queue, involves sending the data verification request to each microservice, specifically including: Monitor the message queue, and when a data verification request is detected in the message queue, retrieve the data verification request sequentially. Identify the microservice that matches the data verification request and send the data verification request to the matching microservice.

4. The distributed data verification method as described in claim 3, characterized in that, After constructing the message queue and establishing the first communication between the microservices through the message queue, the method further includes: Define the message format of the message queue, wherein the message format includes at least a business sub-process identifier, a verification program identifier, and data to be verified; The step of determining the microservice that matches the data verification request and sending the data verification request to the matching microservice specifically includes: The obtained data verification request is parsed to obtain the business sub-process identifier, verification program identifier, and data to be verified in the data verification request; Identify the microservice that matches the business subprocess identifier, and send the verification program identifier and the data to be verified to the matching microservice.

5. The distributed data verification method as described in claim 4, characterized in that, The process of instructing each microservice to perform data verification based on the data verification request, obtaining several data verification results, and storing and outputting these results specifically includes: Each microservice is instructed to call its corresponding matching verification procedure based on its verification procedure identifier. Each microservice is instructed to execute its corresponding matching and verification procedure to perform data verification on the data to be verified for each microservice, and to obtain several data verification results. The data verification results are integrated, and the integrated data verification results are stored in a preset database, and the integrated data verification results are output.

6. The distributed data verification method as described in claim 5, characterized in that, After instructing each microservice to perform data verification based on the data verification request, obtaining several data verification results, and storing and outputting the several data verification results, the method further includes: Data verification and integration results are retrieved from the database according to a preset time period; The results of the data verification and integration are then visualized and output.

7. A distributed data verification device, characterized in that, include: The process decomposition module is used to acquire the business process and decompose the business process into several business sub-processes. The program matching module is used to obtain the data verification program for each business sub-process and obtain the matching verification program. The process encapsulation module is used to encapsulate each business sub-process and the matching and verification program corresponding to each business sub-process into a microservice, resulting in several microservices. The several microservices constitute a set of microservices. Each microservice in the set of microservices carries a business sub-process and its corresponding data verification function. Each microservice provides an independent service interface for other components or systems to call and use. The message queue module is used to build message queues and establish the first communication between the microservices through the message queues; The request monitoring module is used to monitor the message queue. When a data verification request is detected in the message queue, the data verification request is sent to each microservice. The data verification module is used to instruct each microservice to perform data verification based on the data verification request, obtain several data verification results, and store and output the several data verification results. The distributed data verification device further includes: The functional requirements module is used to obtain the business functions and data interaction requirements of each business sub-process. The interface definition module is used to define the data interface of the microservice corresponding to each business subprocess based on the business function and data interaction requirements of each business subprocess, resulting in several microservice data interfaces. A communication construction module is used to construct a second communication between the microservices based on the data interfaces of several microservices; The microservice deployment module is used to deploy several microservices into the microservice framework after the second communication is completed.

8. A computer device, characterized in that, The method includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the distributed data verification method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the distributed data verification method as described in any one of claims 1 to 6.

Images