Business data verification method, device, computer equipment and storage medium

By generating verification tasks and performing verification tasks in parallel, the problem of low manual verification efficiency in insurance companies in insurance applications and correction applications is solved, automated verification is achieved, efficiency and accuracy are improved, and the risk of malicious insurance is reduced.

CN109359939BInactive Publication Date: 2024-11-08CHINA PING AN LIFE INSURANCE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201811125891.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-09-26
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Insurance companies rely on manual verification in insurance applications and correction applications, resulting in low verification efficiency and error-proneness, and inability to effectively prevent malicious insurance behavior.

Method used

By generating verification tasks and querying the verification process according to the business type, the nodes with the same verification level are marked as parallel verification nodes, and the process conversion is performed to perform verification tasks concurrently to improve verification efficiency and accuracy.

Benefits of technology

Automatic verification is realized, the verification efficiency and accuracy is improved, manual intervention is reduced, the monitoring of insurance applications is enhanced, and the risk of malicious insurance is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN109359939B_ABST
    Figure CN109359939B_ABST
Patent Text Reader

Abstract

The present application relates to a business data verification method, device, computer equipment and storage medium based on big data processing. The method includes: obtaining business data and the business type corresponding to the business data; using the business data to generate a corresponding verification task; querying the corresponding verification process according to the business type; the verification process includes multiple verification nodes and the verification level corresponding to each of the verification nodes; marking the verification nodes with the same verification level in the verification process as parallel verification nodes; converting the verification process through one or more parallel verification nodes; and executing the verification task according to the converted verification process. The use of this method can improve the verification accuracy and improve the verification efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a business data verification method, device, computer equipment and storage medium. Background Art

[0002] With the development of insurance business, more and more people are starting to take out insurance. In order to prevent malicious persons from defrauding insurance through malicious insurance, insurance companies need to verify the insurance application of the insured. After the insurance policy is issued, within the insurance period, if the insured finds that there are errors or omissions in the declaration at the time of insurance, or due to new or unexpected circumstances, the content of the insurance policy is inconsistent with the actual situation, he can apply for correction of the policy data. In order to ensure that the subject of insurance obtains insurance protection that is suitable for the actual situation, the insurance company needs to verify the insured's correction application. In the traditional way, a large amount of verification work still relies on manual completion, which is not only prone to errors, but also reduces the verification efficiency. Summary of the invention

[0003] Based on this, it is necessary to provide a business data verification method, device, computer equipment and storage medium that can not only improve the verification accuracy but also improve the verification efficiency in response to the above technical problems.

[0004] A business data verification method, the method comprising: obtaining business data and a business type corresponding to the business data; generating a corresponding verification task using the business data; querying a corresponding verification process according to the business type; the verification process comprising a plurality of verification nodes and a verification level corresponding to each of the verification nodes; marking the verification nodes with the same verification level in the verification process as parallel verification nodes; converting the verification process through one or more parallel verification nodes; and executing the verification task according to the converted verification process.

[0005] In one embodiment, the business type includes insurance; the business data includes a policyholder identification; the verification node includes a first node and multiple parallel second nodes; and executing the verification task according to the converted verification process includes: when the business type is insurance, splitting the verification task based on the first server corresponding to the first node to obtain multiple verification subtasks; allocating the multiple verification subtasks to the second servers corresponding to the multiple second nodes, so that the second server determines the insurance category corresponding to the received verification subtask, determines the verification scope of the business data according to the insurance category, and queries whether there is an insurance policy corresponding to the policyholder identification within the verification scope, and when the corresponding insurance policy is queried, generates a verification result of verification failure.

[0006] In one embodiment, the business type includes a batch order; the business data includes a policy identification; the verification node includes a third node and a fourth node; the verification task is performed according to the converted verification process, including: when the business type is a batch order, the business data is filtered based on the third server corresponding to the third node to obtain target data; the corresponding policy data is obtained according to the policy identification; the policy data includes a validity period field; the validity of the validity period field and the target data is verified based on the fourth server corresponding to the fourth node to generate a verification result.

[0007] In one embodiment, the business data also includes a JSON string; the third server corresponding to the third node filters the business data to obtain target data, including: splitting the JSON string into multiple node strings based on a preset first regular expression; obtaining a second regular expression, the second regular expression including one or more target strings with correction identifiers; determining a traversal direction of the multiple node strings; traversing the multiple node strings respectively according to the traversal direction, filtering the corresponding modified strings in the multiple node strings according to the target strings in the second regular expression, and using the filtered multiple strings as target data.

[0008] In one embodiment, the validity period field includes an insurance period; the target data includes a batch item; the fourth server corresponding to the fourth node verifies the legitimacy of the validity period field and the target data, including: obtaining the batch application time, and verifying the legitimacy of the validity period field by comparing whether the batch application time is within the insurance period; verifying whether the revision item belongs to a preset allowed revision item; when it belongs to an allowed revision item and the revision item includes time, extracting a first time string from the target data, dividing the first time string into multiple source strings, generating target strings corresponding to the multiple source strings according to preset rules, and verifying the legitimacy of the first time string by comparing the multiple source strings with the corresponding target strings.

[0009] In one of the embodiments, executing the verification task according to the converted verification process includes: sending the verification task to servers corresponding to multiple verification nodes for execution according to the converted verification process, and generating multiple task logs; calling a result merging component to merge the task logs scattered on multiple servers, and generating a business log corresponding to the verification task.

[0010] A business data verification device includes: a task generation module, used to obtain business data and the business type corresponding to the business data; using the business data to generate a corresponding verification task; a process conversion module, used to query the corresponding verification process according to the business type; the verification process includes multiple verification nodes and a verification level corresponding to each of the verification nodes; marking the verification nodes with the same verification level in the verification process as parallel verification nodes; converting the verification process through one or more parallel verification nodes; and a task execution module, used to execute the verification task according to the converted verification process.

[0011] In one of the embodiments, the device also includes a log collection module, which is used to send the verification task to the servers corresponding to the corresponding multiple verification nodes for execution according to the converted verification process, and generate multiple task logs; and call the result merging component to merge the task logs scattered on the multiple servers to generate a business log corresponding to the verification task.

[0012] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the business data verification method provided in any embodiment of the present application are implemented.

[0013] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of a business data verification method provided in any embodiment of the present application.

[0014] The above-mentioned business data verification method, device, computer equipment and storage medium can generate corresponding verification tasks using received business data; can query corresponding verification processes according to the business type corresponding to the business data; can mark the verification nodes with the same verification level in the verification process as parallel verification nodes according to the verification level corresponding to each verification node in the verification process; can convert the verification process through one or more parallel verification nodes, and then can execute the verification task according to the converted verification process. Since the verification nodes with the same verification level are marked as parallel verification nodes, the server can execute the verification nodes with the same verification level concurrently, so that the converted verification process can shorten the verification time as a whole, and then can improve the verification efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 An application scenario diagram of a business data verification method in an embodiment;

[0016] Figure 2 A schematic diagram of a process flow of a business data verification method in an embodiment;

[0017] Figure 3A flowchart of the steps for executing a verification task in one embodiment;

[0018] Figure 4 A flowchart of the steps for executing a verification task in another embodiment;

[0019] Figure 5 A structural block diagram of a service data verification device in an embodiment;

[0020] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0022] The business data verification method provided in this application can be applied to Figure 1In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. Among them, the terminal 102 can be but not limited to various personal computers, laptops, smart phones, tablet computers and portable wearable devices, and the server 104 can be implemented by a server cluster composed of multiple servers. When a user needs to take out insurance or approve a bill, the business data can be submitted to the server 104 for verification through the terminal 102. Different business types have different verification processes. The server 104 generates a verification task based on the business data and identifies the verification process corresponding to the business type. The verification process includes multiple verification nodes and the verification level corresponding to each verification node. The server 104 identifies whether there are verification nodes with the same verification level in the verification process. If so, the verification nodes with the same verification level are marked as parallel verification nodes. The server 104 converts the verification process through one or more parallel verification nodes, so that the converted verification process includes multiple verification stages, each verification stage includes a parallel verification node or a verification node without the same verification level. If the first verification stage contains a parallel verification node, the server sends the verification task in parallel to the servers corresponding to the parallel verification nodes in the first verification stage for synchronous execution. If the first verification stage includes an independent verification node, server 104 sends the verification task to the server corresponding to the verification node for execution. After receiving the verification results returned by one or more servers corresponding to the first verification stage, server 104 identifies whether there is a next verification stage. If so, it sends the verification task to one or more servers corresponding to the next verification stage in the above manner. After receiving the verification results returned by the server corresponding to the next verification stage, it returns to the step of identifying whether there is a next verification stage, and repeats this process until there is no next verification stage, indicating that the verification is over. In the above data verification process, the corresponding verification process is queried according to the business type, and the queried verification process is converted according to the verification level. According to the converted verification process, the verification task can be sent in parallel to multiple servers of the same verification level for synchronous execution, thereby improving the verification efficiency.

[0023] In one embodiment, Figure 2 As shown, a business data verification method is provided, which is applied to Figure 1 The server in the example is used to illustrate the following steps:

[0024] Step 202: Acquire business data and the business type corresponding to the business data.

[0025] Step 204: Generate a corresponding verification task using the business data.

[0026] When a user needs to purchase insurance or approve a bill, the business data of the corresponding business type can be submitted to the server for verification based on the terminal's business system. Business types include purchasing insurance or approving a bill, etc. The server generates corresponding verification tasks based on the business data. The server generates corresponding verification tasks based on the business data.

[0027] Step 206, query the corresponding verification process according to the business type; the verification process includes multiple verification nodes and the verification level corresponding to each verification node.

[0028] The server stores the verification processes corresponding to different business types. For example, the "insurance" business type corresponds to the verification process X1, and the "batch" business type corresponds to the verification process X2. The verification process includes multiple verification nodes and the initial execution order of multiple verification nodes. For example, the verification process X1 can be: integrity verification node A1→task splitting node B1→risk verification node C1→general verification node D1→special verification node E1→result merging node F1. The verification process X2 can be: consistency verification node A2→data screening node B2→legality verification node C2→review confirmation node D2→result merging node E2.

[0029] According to the business type of the received business data, the server queries the corresponding verification process and performs the corresponding verification task according to the verification process. Since the business data is verified automatically, manual participation is reduced, and the verification efficiency can be improved.

[0030] In another embodiment, in order to further improve the verification efficiency, the server converts the verification process. Specifically, the verification node has a corresponding node description. For example, the node description corresponding to the integrity verification node A in the above example can be "initial verification", etc., and the node description corresponding to the legal verification node C2 can be "validation of the screened data". The node description contains the execution order information between the corresponding verification node and other verification nodes. If a verification node does not have a corresponding node description, it means that there is no specific restriction on the execution order of the verification node.

[0031] The server determines the verification levels corresponding to the multiple verification nodes according to the node description. The verification level is used to characterize the execution order of the corresponding verification nodes. For example, the verification level corresponding to each verification node in the above verification process X1 can be: integrity verification node A1 (level 1) → task splitting node B1 (level 1) → risk verification node C1 (level 2) → general verification node D1 (level 2) → special verification node E1 (level 2) → result merging node F1 (level 3). The verification level corresponding to each verification node in the above verification process X2 can be: consistency verification node A2 (level 1) → data screening node B2 (level 1) → legal verification node C2 (level 2) → audit confirmation node D2 (level 2) → result merging node E2 (level 3).

[0032] Step 208: Mark the check nodes with the same check level in the check process as parallel check nodes.

[0033] The server identifies whether there are check nodes of the same check level in the check process. If so, the server marks the check nodes of the same check level as parallel check nodes. For example, in the above example, integrity check node A1 and task split node B1 are marked as parallel check nodes, and risk check node C1, general check node D1 and special check node E1 are marked as parallel check nodes. Check nodes that are not marked as parallel check nodes, such as risk check node F1, can be called independent check nodes.

[0034] Step 210: convert the verification process through one or more parallel verification nodes.

[0035] The server converts the original verification process by marking each independent verification node as a verification stage and marking each parallel verification node as a verification stage, so that the converted verification process includes one or more verification stages, each verification stage includes an independent verification node or a parallel verification node. In other words, each verification stage includes one or more verification nodes.

[0036] For example, the above verification process X1 can be converted into: verification stage 1 (integrity verification node A1, task splitting node B1) → verification stage 2 (risk verification node C1, general verification node D1, special verification node E1) → verification stage 3 (result merging node F1).

[0037] Step 212, executing the verification task according to the converted verification process.

[0038] According to the converted verification process, the server sends the verification task generated according to all business data to the service node corresponding to each verification node in the cluster for execution. Specifically, the server identifies whether the first verification stage contains a parallel verification node. If so, the server sends the verification task in parallel to the service nodes corresponding to the parallel verification nodes in the first verification stage in the cluster. Otherwise, it means that the first verification stage includes an independent verification node, and the server sends the verification task to the service node corresponding to the verification node in the cluster. After receiving the verification results returned by one or more servers corresponding to the first verification stage, the server identifies whether there is a next verification stage. If there is, the server sends the verification task and the verification result to one or more service nodes corresponding to the next verification stage in the above manner. After receiving the verification results returned by one or more service nodes corresponding to the next verification stage, the server returns to the step of identifying whether there is a next verification stage. Repeat this until there is no next verification stage, then the verification ends. The server feeds back all the received verification results to the terminal so that the user can understand the verification results in time.

[0039] In the traditional way, even if the verification nodes have the same verification level, the verification task can only be transferred to the next verification node after the current verification node is executed, which reduces the verification efficiency. This embodiment converts the verification process and automatically identifies one or more verification nodes that need to send verification tasks according to the converted verification process, which can improve the project verification efficiency.

[0040] In this embodiment, the corresponding verification task can be generated by using the received business data; the corresponding verification process can be queried according to the business type corresponding to the business data; the verification nodes with the same verification level in the verification process can be marked as parallel verification nodes according to the verification level corresponding to each verification node in the verification process; the verification process can be converted through one or more parallel verification nodes, and then the verification task can be executed according to the converted verification process. Since the verification nodes with the same verification level are marked as parallel verification nodes, the server can execute the verification nodes with the same verification level concurrently, so that the converted verification process can shorten the verification time as a whole, and thus improve the verification efficiency.

[0041] In one embodiment, the business type includes insurance; the business data includes the insured person identification; and the verification node includes a first node and a plurality of parallel second nodes. Figure 3 As shown, the verification task is executed according to the converted verification process, that is, the steps of executing the verification task include:

[0042] Step 302: When the business type is insurance, the verification task is split based on the first server corresponding to the first node to obtain multiple verification subtasks.

[0043] When the business type is insurance, it is assumed that the corresponding adjusted verification process includes a first node and multiple parallel second nodes. The first node can be the above-mentioned task splitting node B1, and the second node can include the above-mentioned risk verification node C1, general verification node D1 and special verification node E1. The verification task corresponding to the first node is executed based on the first server in the cluster, and the verification task corresponding to the second node is executed based on the second server in the cluster. It is easy to understand that the first server and the second server can be the same service node in the cluster, or they can be different service nodes.

[0044] In order to further improve the execution efficiency of the verification task, the server sends the verification task to the first server corresponding to the first node, and the first server splits the verification task into multiple verification subtasks. Specifically, the first server splits the verification task according to the business data that each verification node needs to process, and obtains the verification subtask corresponding to each verification node.

[0045] Step 304, distributes multiple verification subtasks to the second servers corresponding to the multiple second nodes, so that the second server determines the insurance category corresponding to the received verification subtask, determines the verification scope of the business data according to the insurance category, and queries whether there is an insurance policy corresponding to the insured person identifier within the verification scope. When the corresponding insurance policy is found, a verification result of verification failure is generated.

[0046] The first server distributes multiple verification subtasks to the second servers corresponding to the multiple second nodes in the cluster for execution. In one embodiment, the first server calculates the task amount corresponding to the verification subtask; monitors the current load of the multiple service nodes in the cluster. The first server distributes the verification subtasks according to the preset matching relationship between the current load and the task amount, that is, determines the second server corresponding to each verification subtask.

[0047] When the business type is insurance, the verification subtask includes insurance application data. The second server extracts the insured information carried in the insurance application data. The insurance application data refers to an insurance request for a certain insurance product. The insurance application contains the corresponding insured product information and the insured information carrying the insured product, wherein the insured information includes name, gender, certificate type, certificate number, etc.

[0048] In order to prevent malicious persons from defrauding insurance through malicious insurance, the insurance company needs to verify the user's insurance application, that is, to find out whether the user has had the same or similar insurance behavior before. If so, it means that the user belongs to secondary insurance and the insurance application is rejected. Specifically, the second server finds the customer number corresponding to the insured information, and the customer number is used to uniquely identify a user. In one embodiment, the process of searching for the customer number according to the insured information can adopt a loop traversal algorithm. For example, first filter out the data result set Z1 that meets the "name" condition, and then traverse the data result set Z2 that meets the "gender" condition in the Z1 set, and then traverse the certificate type and certificate number in the Z2 set to obtain the data result set Z3, until a result set that meets all conditions is found, that is, the customer number of the user is obtained. If the customer number of the user is not found, it means that the customer has not been insured before, and there is no secondary insurance behavior.

[0049] Since there are many similar insurance products, if you just search whether the user has previously insured the insurance product applied for this time in the traditional way, such search results are too restrictive and not conducive to controlling the risk of insurance. In order to conduct insurance verification more accurately, the search scope is expanded to insured policies and policies being insured. Specifically, after obtaining the insured product information, the second server determines the corresponding insurance category based on the insured product information. The insurance category to which the insured product belongs can be pre-divided using a multivariate classification algorithm. For example, insurance products can be classified according to product type and product attributes, where product types are divided into two categories: personal type and group type, and product attributes refer to the type of insurance to which the product belongs, such as health insurance, accident insurance or other.

[0050] The second server determines the verification range corresponding to the insured product information according to the insurance category. Specifically, the second server can determine the corresponding product type, product attributes or sales channel according to the insurance category, and use the product type, product attributes and sales channel as search restrictions, and then search for the insurance policy corresponding to the customer number under the restriction. When searching according to the customer number, the sales channel can be screened using a fuzzy matching algorithm. The product type and product attributes are certain, so an exact matching algorithm can be used for screening. According to the customer number, search for the insurance policy corresponding to the customer number within the range restricted by the product type, product attributes and sales channel. If the corresponding insurance policy is searched, the second server generates a verification result of verification failure.

[0051] In this embodiment, the entire insurance verification process is fully automatic, saving time and effort, and the scope of insurance verification is expanded from the original single product to the insurance category to which the product belongs. By expanding the scope of insurance verification, the verification accuracy can be improved and the risk of subsequent underwriting can be reduced.

[0052] In one embodiment, the business type includes a batch order; the business data includes a policy identifier; the check node includes a third node and a fourth node; Figure 4 As shown, the verification task is executed according to the converted verification process, that is, the steps of executing the verification task include:

[0053] Step 402: When the business type is a batch order, the business data is screened based on the third server corresponding to the third node to obtain target data.

[0054] When the business type is a batch order, it is assumed that the corresponding adjusted verification process includes a third node and a fourth node. The third node can be the above-mentioned data screening node B2, and the fourth node can be the above-mentioned legal verification node C2. The verification task corresponding to the third node is executed based on the third server in the cluster, and the verification task corresponding to the fourth node is executed based on the fourth server in the cluster. It is easy to understand that the third server and the fourth server can be the same service node in the cluster, or they can be different service nodes. The verification task includes the batch application data of one or more insurance policies.

[0055] Step 404, obtaining corresponding policy data according to the policy identifier; the policy data includes a validity period field.

[0056] The third server obtains the corresponding original policy data according to the policy identification. The original policy data is all the policy data corresponding to the policy identification before the business personnel request the revision, that is, the data that has not been revised. For example, the policy identification, the validity period field, etc. Among them, the validity period field includes the insurance period, the insurance effective time, etc. The batch application data is the policy data requested for revision by the business personnel. The batch application data records all the fields modified by the user in the form of a string, including both the modified fields and the unmodified fields. In order to improve the inspection efficiency, the third server filters the target data from the batch application data and only performs a legality check on the target data. Among them, the target data refers to the modified field in the batch application data. The target data includes the approval item and the corresponding revision value. The approval item refers to the field name corresponding to the modified field, and the revision value is the corresponding field value.

[0057] Step 406: Verify the validity of the validity period field and the target data based on the fourth server corresponding to the fourth node, and generate a verification result.

[0058] The third server sends the extracted validity period field and target data to the fourth server for legality verification. Specifically, the target data has a corresponding batch order application time. The fourth server identifies whether the batch order application time is within the corresponding insurance period to verify whether the corresponding insurance policy is in an insured state. When the batch order application time is within the corresponding insurance period, it means that the legality check of the validity period field has passed.

[0059] The target data includes multiple modification items. The fourth server also verifies whether the modification items in the target data belong to the preset modification items allowed. The fourth server presets the modification items allowed corresponding to multiple insurance types. For example, the modification items allowed for auto insurance include the policyholder, insurance time, insured, insurance period, premium, insurance subject vehicle information, usage nature, etc. Among them, the insurance period includes the start time of protection and the end time of insurance. Fields such as policy number and insurance type are not allowed to be modified. When the modification items in the target data belong to the modification items allowed, it means that the legitimacy check of the target data has passed. When the validity period field and the legitimacy check of the target data have passed respectively, the fourth server generates a verification result of successful verification.

[0060] In this embodiment, during the entire review process, target data is screened out from the review application data, and only the target data is verified for legitimacy, which can reduce the amount of data to be verified by the server and thus improve verification efficiency.

[0061] In one embodiment, the business data also includes a JSON string; the business data is filtered based on a third server corresponding to the third node to obtain target data, including: splitting the JSON string into multiple node strings based on a preset first regular expression; obtaining a second regular expression, the second regular expression including one or more target strings with revision identifiers; determining a traversal direction of the multiple node strings; traversing the multiple node strings respectively according to the traversal direction, filtering the corresponding revised strings in the multiple node strings according to the target strings in the second regular expression, and using the filtered multiple strings as target data.

[0062] The modification application data includes a JSON (JavaScript Object Notation, JS Object Tag) string. The JSON string can be converted from a JSON (JavaScript Object Notation, JS Object Tag) object by the terminal in order to improve the data transmission rate. The JSON object includes multiple nodes. Each node corresponds to the policy data of an insurance policy, such as the policy ID. Each node includes multiple key-value pairs, and each key-value pair includes two attribute values: a key name and a key value. For example, the JSON object can be:

[0063] {{“new id”:”4628912”,

[0064] “new policy holder”:{“name”:“**Hotel”,“code”:”20929**211”,“business”:“Hotel”}

[0065] "duration of insurance":["2015","03","09","2020","3","09"],

[0066] "premium":"2000",}

[0067] {“new id”:”4628913”,

[0068] “policy holder”:{“name”:“**Bank”,“code”:”34770**286”,“business”:“Bank”}

[0069] "new duration of insurance":["2013","01","01","2018","12","01"],

[0070] "premium":"2000",}}

[0071] The above JSON object includes two nodes, each of which includes 4 key-value pairs. The key name "new policyholder" corresponds to three key values ​​"name": "**hotel", "code": "20929**211" and "business": "hotel". Multiple nodes in the JSON object include the same key name. It should be noted that in actual operation, the number of nodes in the JSON object and the number of key-value pairs in each node are relatively large.

[0072] In order to improve the verification efficiency, the third server filters the target data from the batch application data for verification. In the traditional way, in order to extract the target data, the third server needs to convert the JSON string into a JSON object, and filter the multiple nodes in the JSON object one by one from the beginning to the end to extract the target data. However, when the amount of JSON data is large, the data conversion time is long, and it takes a long time to filter the multiple nodes in the JSON object from the beginning to the end, which reduces the efficiency of filtering the JSON data.

[0073] However, this embodiment does not need to convert the JSON string into a JSON object to instantly filter the target data. Specifically, the third server pre-stores the first regular expression, and the first regular expression includes a start identifier and an end identifier. For example, the first regular expression can be: "\*new id\*\\:.*?\\,\*new policy holder\*\\:.*?\\,\*duration of insurance\*\\:.*?\\,\*premium\*\\:.*?\\,"". Among them, the key name is followed by \*, so that id, new policy holder, duration of insurance and premium are key names respectively; \*\\:.*? indicates the key value corresponding to the key name, and \\, indicates the end of a key-value pair; thus, in the first regular expression, the start identifier is the key name id, and the end identifier is the key-value pair whose key name is premium. The third server uses the first regular expression to split the JSON string into multiple node strings. Each node string corresponds to the batch application data of an insurance policy. For example, one of the node strings could be: ""new id":"4628912","new policy holder":{"name":"**Hotel","code":"2092 9**211","business":"Hotel"}","duration of insurance":["2015","03","09","2020","03","09"],"premium":"2000"".

[0074] The third server also pre-stores a second regular expression. The second regular expression includes one or more target strings with revision marks. For example, the second regular expression may be: "\*new id\*\\:.*?\\,\*new policyholder\*\\:.*?\\," so that the target string includes the key names "new id" and "new policy holder name" and the corresponding key values. The third server obtains a segment of node string, traverses the segment of node string, and determines the traversal direction of multiple segments of node string according to the time when the string matching the second regular expression is traversed, or the position of the string matching the second regular expression in the segment of node string. The traversal direction includes forward traversal and negative traversal. Among them, positive traversal refers to traversal from the first character of the node string to the last character; negative traversal refers to traversal from the last character of the node string to the first character.

[0075] The third server traverses multiple segments of node strings according to the determined traversal direction. When a string matching the corresponding second regular expression is traversed in a node string, the third server stops traversing the segment of the node string, and extracts the string matching the second regular expression as the target data. For example, the target data corresponding to the above node string may be "newpolicyholdername**hotel". The third server traverses each segment of the node string multiple times to find a string matching each second regular expression. It is easy to understand that when a segment of a node string fails to match a second regular expression, it means that the corresponding field in the insurance policy corresponding to the node string has not been revised. The third server uses the string in the node string that matches the target string in the second regular expression as the target data.

[0076] In this embodiment, since the first regular expression directly splits the JSON string into multiple segments, there is no need to convert the JSON string into a JSON object, and the second regular expression can be used directly in the JSON string to extract the target data, thereby improving the efficiency of extracting the target data from the JSON data, and further improving the efficiency of screening the JSON data. Since the traversal direction of the multi-segment node string can be determined according to actual needs, rather than simply traversing the multi-segment node string in order from the beginning to the end, the efficiency of screening the JSON data can be further improved.

[0077] In one embodiment, the validity period field includes the insurance period; the target data includes the approval item; the validity of the validity period field and the target data is verified based on the fourth server corresponding to the fourth node, including: obtaining the approval form application time, and verifying the validity of the validity period field by comparing whether the approval form application time is within the insurance period; verifying whether the approval item belongs to the preset allowed approval item; when it belongs to the allowed approval item and the approval item includes time, extracting the first time string from the target data, dividing the first time string into multiple source strings, generating target strings corresponding to the multiple source strings according to preset rules, and verifying the validity of the first time string by comparing the multiple source strings with the corresponding target strings.

[0078] When the modification item in the target data belongs to the modification-allowed item, if the modification item includes time information such as the insurance time, the insurance effective time or the insurance end time, the fourth server can extract the first time string from the modification value corresponding to the corresponding modification item, such as "2015229" or "15-2-29". The fourth server matches the first time string with the time string template to perform format verification on the first time string. Among them, the time string templates written in different programming languages ​​can be different. For example, the time string template corresponding to the JS language (JavaScript, a literal scripting language) can be "^\d[4][-]\d[1,2][-]\d[1,2]$"; the time string template corresponding to the Java language can be yyyy-MM-dd. The time string template indicates that the "year" in the time string input by the business terminal can be a four-digit number, such as "2015"; the "year" and the "month" can be connected by the "-" character; the "month" and the "day" can be a single digit or a two-digit number, respectively. It is easy to understand that the time character string input by the service terminal may also include "hour", "minute" and "second", such as "2015-2-29 09:20:22", and there is no limitation on this.

[0079] When the format check of the first time string passes, the fourth server uses the time string template to divide the first time string into multiple source strings. Each source string corresponds to a time node such as "year", "month", and "day". For example, in the above example, the multiple source strings can be "2015", "2", and "29".

[0080] The fourth server generates a target string corresponding to a plurality of source strings according to a preset rule, and performs a legality check on the first time string by comparing the plurality of source strings with the corresponding target string. Specifically, the fourth server associates the plurality of source strings as variable values ​​with a preset source variable name, so as to distinguish and store each source string by using the source variable name, such as the source variable name A1 can correspond to the source string "year", A2 can correspond to the source string "month", A3 can correspond to the source string "day", etc. In the above example, A1 can correspond to "2015", A2 can correspond to "2", and A3 can correspond to "29". The fourth server converts the first time string into a date object by using the first system method. The first system method can be string.toDate(), etc. The date object is a data type provided in javascript (a literal scripting language) that can operate date and time. The date object can be the time difference between the input time and the standard time, and the time difference is in ms (milliseconds). The input time refers to the time corresponding to the first time string, such as 201522920:20:00. The standard time is 197011 00:00:00. In the above example, the date object can be T = (2015*A+2*B+29*C+20*D+20*E)-(1970*A+1*B+1*C). Wherein, T is the date object, A = 365*24*60*60*1000, B = 24*60*60*1000, C = 60*60*1000, D = 60*1000. The server converts the unit of the date object using the second system method to obtain the second time string. The second system method can be date.toString(), etc.

[0081] It should be noted that the second time string is a legal string. For ease of understanding, the conversion logic of the second time string can be summarized as follows: if the first time string is an illegal string, the fourth server obtains the legal time corresponding to the input time, calculates the time difference between the legal time and the input time, and linearly superimposes the input time and the time difference to obtain the second time string. For example, in the above example, since 2015 is an ordinary year, the legal time corresponding to the input time 2015229 can be 2015228. The input time is one day more than the legal time, and the second time string can be 201531.

[0082] The fourth server uses the above-mentioned time string template to divide the second time string into multiple target strings. The fourth server associates the multiple target strings as variable values ​​with a preset target variable name respectively, so as to distinguish and store each target string by using the target variable name, such as the target variable name B1 can correspond to the target string "year", B2 can correspond to the target string "month", B3 can correspond to the target string "day", etc. In the above example, B1 can correspond to "2015", B2 can correspond to "3", and B3 can correspond to "1". The fourth server pre-stores the correspondence between each source variable name and the target variable name, such as A1 corresponds to B1, A2 corresponds to B2, and so on. According to the correspondence, the fourth server matches the multiple source strings with the corresponding target strings. When the multiple source strings and the corresponding target strings are matched successfully, it means that the legitimacy check of the first time string has passed, and a successful check result is generated.

[0083] In the traditional method, the year range, month range, day range, hour, minute, second range, leap year or common year, etc. are calculated according to the formula to verify the first time string, and the verification logic is complicated, making the programming code lengthy. In this embodiment, no calculation is required, and only simple string segmentation and matching are required to complete the verification of the first time string, and the verification logic is simple; and the string conversion can be realized by using the system method, so that the code logic is simple, the amount of code can be saved, and the resource overhead of the fourth server can be reduced.

[0084] In one embodiment, a verification task is executed according to a converted verification process, including: according to the converted verification process, the verification task is sent to servers corresponding to multiple verification nodes for execution, and multiple task logs are generated; a result merging component is called to merge the task logs scattered on multiple servers to generate a business log corresponding to the verification task.

[0085] When the server uses distributed task scheduling to process business, it may distribute verification tasks to multiple servers or different virtual machines of the same server for execution, so that the task logs generated by executing different verification tasks are scattered on multiple servers or multiple virtual machines, and users can only see the execution of some tasks in scattered black boxes. However, developers usually only care about the execution of tasks at the business level, which brings great inconvenience to users to check logs.

[0086] In order to solve the above problems, the server of this application pre-stores a log decorator. The log decorator enables the business system to generate logs from the business dimension, that is, to control the centralized display of task logs of multiple verification tasks that implement the same business function. The log decorator can exist in the form of an independent log system to provide an interface to the business system. Specifically, the business system has a corresponding business logic script. The business logic script includes multiple function queues. Different function queues implement different business functions, such as insurance, batch orders, etc. When the user performs business operations on the business system at the terminal, the terminal generates a corresponding business request according to the user's business operation and sends the business request to the server. The business request carries the entry function identifier corresponding to the entry function that implements the corresponding business function. The server queries the corresponding entry function according to the entry function identifier, and then queries the corresponding function queue according to the entry function. It is easy to understand that the same business request needs to implement the same business function, so the corresponding function queues are the same. Each entry function has a corresponding log decorator. It is easy to understand that the same entry function corresponds to multiple business functions in the function queue corresponding to the same log decorator.

[0087] The server distributes the verification task to multiple servers in the cluster for execution in the above manner. When the verification task is executed, a corresponding task log is generated, and the corresponding log decorator is called. The log decorator inserts the task identifier of the corresponding verification task into the task log according to the specified log processing method. When a certain business is completed, the log decorator collects multiple task logs with the same task identifier from multiple servers or multiple virtual machines executing the business, integrates the collected multiple task logs, generates a business log corresponding to each task identifier, and returns the business log to the terminal for display.

[0088] In this embodiment, a log decorator is provided. The log decorator itself provides the ability to collect logs from the business level. After multiple servers execute verification tasks and generate scattered task logs, logs are automatically collected and integrated from the business level, solving the problem of inconvenient log review caused by scattered logs in the business system.

[0089] It should be understood that although Figure 2 to Figure 4 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 to Figure 4At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0090] In one embodiment, Figure 5 As shown, a business data verification device is provided, including: a task generation module 502, a process conversion module 504 and a task execution module 506, wherein:

[0091] The task generation module 502 is used to obtain business data and the business type corresponding to the business data; and generate a corresponding verification task using the business data.

[0092] The process conversion module 504 is used to query the corresponding verification process according to the business type; the verification process includes multiple verification nodes and the verification level corresponding to each verification node; the verification nodes with the same verification level in the verification process are marked as parallel verification nodes; and the verification process is converted through one or more parallel verification nodes.

[0093] The task execution module 506 is used to execute the verification task according to the converted verification process.

[0094] In one embodiment, the business type includes insurance; the business data includes a policyholder identification; the verification node includes a first node and multiple parallel second nodes; the task execution module 506 is also used to split the verification task based on the first server corresponding to the first node when the business type is insurance, to obtain multiple verification subtasks; the multiple verification subtasks are allocated to the second servers corresponding to the multiple second nodes, so that the second server determines the insurance category corresponding to the received verification subtask, determines the verification scope of the business data according to the insurance category, and queries whether there is an insurance policy corresponding to the policyholder identification within the verification scope, and when the corresponding insurance policy is queried, generates a verification result of verification failure.

[0095] In one embodiment, the business type includes a batch order; the business data includes a policy identification; the verification node includes a third node and a fourth node; the task execution module 506 is also used to, when the business type is a batch order, filter the business data based on the third server corresponding to the third node to obtain target data; obtain the corresponding policy data according to the policy identification; the policy data includes a validity period field; verify the legitimacy of the validity period field and the target data based on the fourth server corresponding to the fourth node to generate a verification result.

[0096] In one embodiment, the business data also includes a JSON string; the task execution module 506 is also used to split the JSON string into multiple node strings based on a preset first regular expression; obtain a second regular expression, the second regular expression includes one or more target strings with a correction identifier; determine the traversal direction of the multiple node strings; traverse the multiple node strings respectively according to the traversal direction, and filter the corresponding modified strings in the multiple node strings according to the target strings in the second regular expression, and use the filtered multiple strings as target data.

[0097] In one embodiment, the validity period field includes the insurance period; the target data includes the approval item; the task execution module 506 is also used to obtain the approval form application time, and verify the legitimacy of the validity period field by comparing whether the approval form application time is within the insurance period; verify whether the approval item belongs to the preset allowed approval item; when it belongs to the allowed approval item and the approval item includes time, extract the first time string from the target data, divide the first time string into multiple source strings, generate target strings corresponding to the multiple source strings according to preset rules, and verify the legitimacy of the first time string by comparing the multiple source strings with the corresponding target strings.

[0098] In one embodiment, the device also includes a log collection module 508, which is used to send the verification task to the servers corresponding to the corresponding multiple verification nodes for execution according to the converted verification process, and generate multiple task logs; call the result merging component to merge the task logs scattered on multiple servers to generate a business log corresponding to the verification task.

[0099] For the specific definition of the business data verification device, please refer to the definition of the business data verification method above, which will not be repeated here. Each module in the above-mentioned business data verification device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0100] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 6As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store verification processes corresponding to multiple business types. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a business data verification method is implemented.

[0101] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0102] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the business data verification method provided in any embodiment of the present application.

[0103] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in the present application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0104] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0105] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A business data verification method, the method comprising: Acquire business data and the business type corresponding to the business data; Generate a corresponding verification task using the business data; Query the corresponding verification process according to the business type; The verification process includes a plurality of verification nodes and a verification level corresponding to each of the verification nodes; Marking the check nodes with the same check level in the check process as parallel check nodes; Converting the verification process through one or more parallel verification nodes; The verification task is executed according to the converted verification process, wherein when the business type is insurance, the business data includes an insured person identification, the verification node includes a first node and a plurality of parallel second nodes, the first node is a task splitting node B1, the second node includes a risk verification node C1, a general verification node D1 and a special verification node E1, the verification task is split based on a first server corresponding to the first node to obtain a plurality of verification subtasks, the plurality of verification subtasks are allocated to a plurality of second servers corresponding to the second nodes, the second server determines the insurance category corresponding to the received verification subtask, determines the verification scope of the business data according to the insurance category, queries whether there is an insurance policy corresponding to the insured person identification within the verification scope, and generates a verification result of verification failure when the corresponding insurance policy is found; When the business type is a batch order, the business data includes a policy identification, the verification nodes include a third node and a fourth node, the verification process includes a consistency verification node A2 and a data screening node B2 with a verification level of 1, a legality verification node C2 with a verification level of 2, and an audit confirmation node D2, the third node is the data screening node B2, the fourth node is the legality verification node C2, the business data is screened based on the third server corresponding to the third node to obtain the target data, the corresponding policy data is obtained according to the policy identification, the policy data includes an expiration date field, the validity date field and the legality of the target data are verified based on the fourth server corresponding to the fourth node, and a verification result is generated.

2. The method according to claim 1, characterized in that The converting of the verification process by one or more parallel verification nodes includes: The verification process is converted by marking each independent verification node as a verification stage, and marking each parallel verification node as a verification stage, so that the converted verification process includes one or more verification stages, each verification stage includes an independent verification node or a parallel verification node, and the independent verification node is a verification node that is not marked as a parallel verification node.

3. The method according to claim 1, characterized in that The allocating the plurality of verification subtasks to the second servers corresponding to the plurality of second nodes comprises: Calculate the task volume corresponding to the verification subtask; Monitor the current load of multiple service nodes in the cluster; Determine the second server corresponding to each verification subtask according to the preset matching relationship between the current load and the task amount; Allocate the plurality of verification subtasks to second servers corresponding to the plurality of second nodes.

4. The method according to claim 3, characterized in that The business data also includes a JSON string; the third server corresponding to the third node filters the business data to obtain target data, including: Splitting the JSON string into multiple node strings based on a preset first regular expression; Obtaining a second regular expression, wherein the second regular expression includes one or more target character strings having a revision mark; Determine the traversal direction of a multi-segment node string; The multiple node character strings are traversed respectively according to the traversal direction, and the corresponding modified character strings in the multiple node character strings are screened according to the target character string in the second regular expression, and the screened multiple character strings are used as target data.

5. The method according to claim 3, characterized in that: The validity period field includes an insurance period; the target data includes a revision item; and the fourth server corresponding to the fourth node verifies the legitimacy of the validity period field and the target data, including: Obtain the batch application time, and verify the legitimacy of the validity period field by comparing whether the batch application time is within the insurance period; Verifying whether the modification item belongs to the preset modification-allowed items; When it is an item that allows modification and the modification item includes time, a first time character string is extracted from the target data, the first time character string is divided into multiple source character strings, and target character strings corresponding to the multiple source character strings are generated according to preset rules. The legitimacy of the first time character string is verified by comparing the multiple source character strings with the corresponding target character strings.

6. The method according to claim 1, characterized in that The performing of the verification task according to the converted verification process also includes: According to the converted verification process, the verification task is sent to the servers corresponding to the corresponding multiple verification nodes for execution, and multiple task logs are generated; The call result merging component merges the task logs scattered across the multiple servers to generate a business log corresponding to the verification task.

7. A business data verification device, characterized in that: The device comprises: A task generation module, used to obtain business data and the business type corresponding to the business data; and generate a corresponding verification task using the business data; A process conversion module, used to query the corresponding verification process according to the business type; the verification process includes multiple verification nodes and the verification level corresponding to each of the verification nodes; the verification nodes with the same verification level in the verification process are marked as parallel verification nodes; the verification process is converted through one or more parallel verification nodes; A task execution module is used to execute the verification task according to the converted verification process, wherein when the business type is insurance, the business data includes a policyholder identification, the verification node includes a first node and multiple parallel second nodes, the first node is a task splitting node B1, the second node includes a risk verification node C1, a general verification node D1 and a special verification node E1, the verification task is split based on a first server corresponding to the first node to obtain multiple verification subtasks, the multiple verification subtasks are allocated to multiple second servers corresponding to the second nodes, the second server determines the insurance category corresponding to the received verification subtask, determines the verification scope of the business data according to the insurance category, and queries whether there is a task corresponding to the policyholder identification within the verification scope. Insurance policy, when the corresponding insurance policy is queried, a verification result of verification failure is generated, when the business type is a batch order, the business data includes the insurance policy identification, the verification node includes a third node and a fourth node, the verification process includes a consistency verification node A2 and a data screening node B2 with a verification level of 1, a legality verification node C2 with a verification level of 2, and an audit confirmation node D2, the third node is the data screening node B2, the fourth node is the legality verification node C2, based on the third server corresponding to the third node, the business data is screened to obtain the target data, and the corresponding insurance policy data is obtained according to the insurance policy identification, the insurance policy data includes an expiration date field, and the legality of the expiration date field and the target data is verified based on the fourth server corresponding to the fourth node to generate a verification result.

8. The device according to claim 7, characterized in that It also includes a log collection module, which is used to send the verification task to the servers corresponding to the corresponding multiple verification nodes for execution according to the converted verification process, and generate multiple task logs; The call result merging component merges the task logs scattered across the multiple servers to generate a business log corresponding to the verification task.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.