Rule configuration method, terminal equipment and computer readable storage medium

Abstract

The invention discloses a rule configuration method, terminal equipment and a computer readable storage medium, and relates to the technical field of data processing, and the rule configuration method comprises the following steps: receiving a to-be-verified field identifier and an application field to which the to-be-verified field identifier is to be applied; determining a first verification rule corresponding to the to-be-verified field identifier according to the attribute of the to-be-verified field identifier; determining a second verification rule corresponding to the to-be-verified field identifier according to the application field of the to-be-verified field identifier; according to the first verification rule and the second verification rule, generating a target verification rule of the to-be-verified field identifier; and when to-be-verified data is received, verifying the to-be-verified data by adopting the target verification rule, and outputting a verification result. The target verification rule can be automatically generated according to the to-be-verified field identifier, a user does not need to configure the target verification rule by himself, and the verification rule configuration efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a rule configuration method, a terminal device, and a computer-readable storage medium. Background Art

[0002] In the financial field, such as banks and securities companies, a large amount of transaction data is generated every day, including stock transactions, bond transactions, foreign exchange transactions, etc. In order to ensure the integrity, accuracy and compliance of transaction data, it is necessary to perform rule verification on the transaction data.

[0003] At present, rule configuration is usually done by staff configuring the verification rules for corresponding data fields one by one according to the verification requirements. However, when faced with large amounts of data, configuring the verification rules for corresponding data fields one by one takes a lot of time, making the rule configuration inefficient.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a rule configuration method, a terminal device and a computer-readable storage medium, aiming to solve the technical problem of low rule configuration efficiency.

[0006] To achieve the above purpose, the present application proposes a rule configuration method, which includes:

[0007] Receive a field identifier to be checked and an application field to which the field identifier to be checked is to be applied;

[0008] Determine, according to the attribute of the field identifier to be checked, a first checking rule corresponding to the field identifier to be checked;

[0009] Determine a second verification rule corresponding to the field identifier to be verified according to the application field of the field identifier to be verified;

[0010] Generate a target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule;

[0011] When the data to be verified is received, the target verification rule is used to verify the data to be verified, and the verification result is output.

[0012] In some embodiments, before the step of generating the target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule, the step further includes:

[0013] Displaying the first verification rule and the second verification rule on the rule configuration interface;

[0014] When a confirmation action of the rule configuration interface is received, the target verification rule of the to-be-verified field identifier is generated according to the rule configuration interface.

[0015] In some embodiments, the step of generating the target verification rule for the field identifier to be verified includes:

[0016] Compare the first verification rule and the second verification rule corresponding to each of the to-be-verified field identifiers in the target verification rule to determine the conflicting first target verification rule and second target verification rule;

[0017] Selecting a third target verification rule from the first target verification rule and the second target verification rule according to the verification reference value and the verification operator in the first target verification rule and the second target verification rule;

[0018] Deleting unselected verification rules from among the first target verification rule and the second target verification rule.

[0019] In some embodiments, before the step of receiving the field identifier to be checked and the application field to which the field identifier to be checked is to be applied, the step includes:

[0020] Obtaining standard documents corresponding to the application field;

[0021] Identify the standard file and determine the information to be verified;

[0022] The second verification rule corresponding to the application field is generated according to the information to be verified.

[0023] In some embodiments, the step of generating a target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule includes:

[0024] Comparing the first verification rule with the second verification rule, and determining a verification rule in the second verification rule that is the same as the first verification rule;

[0025] Deleting the same verification rules;

[0026] The step of generating a target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule is performed.

[0027] In some embodiments, the method further comprises:

[0028] When receiving a trigger action of a rule management interface, displaying the rule management interface and displaying optional verification rules on the rule management interface;

[0029] When receiving the selected action of the rule management interface, obtaining the verification rule corresponding to the selected action;

[0030] Generate the target verification rule according to the verification rule;

[0031] The step of executing the step of, when receiving the data to be verified, using the target verification rule to verify the data to be verified, and outputting the verification result.

[0032] In some embodiments, when the data to be verified is received, the target verification rule is used to verify the data to be verified, and before the step of outputting the verification result, the step includes:

[0033] Determine a maximum load value according to the application field, and operate at the maximum load value;

[0034] Receive test data, verify the test data using the target verification rule, and output the test verification result of the test data;

[0035] If the test verification result is passed, the step of performing verification on the data to be verified by using the target verification rule when receiving the data to be verified and outputting the verification result is executed.

[0036] In some embodiments, when receiving the data to be verified, the step of verifying the data to be verified using the target verification rule and outputting the verification result includes:

[0037] When the data to be verified is received, the data format of the verification data corresponding to each verification field identifier in the data to be verified is obtained;

[0038] When the data format of the verification data corresponding to the verification field identifier in the data to be verified is different from the data format corresponding to the field identifier to be verified in the target verification rule, converting the data format of the verification data corresponding to the verification field identifier into the data format corresponding to the field identifier to be verified in the target verification rule;

[0039] The target verification rule is used to verify the data to be verified, and the verification result is output.

[0040] In addition, to achieve the above-mentioned purpose, the present application also proposes a terminal device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the rule configuration method described above.

[0041] In addition, to achieve the above objectives, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the rule configuration method described above are implemented.

[0042] The present application proposes a rule configuration method, which receives a field identifier to be checked and an application field to be applied to the field identifier to be checked, and then determines a first verification rule corresponding to the field identifier to be checked according to the attribute of the field identifier to be checked, and determines a second verification rule corresponding to the field identifier to be checked according to the application field of the field identifier to be checked, and finally generates a target verification rule for the field identifier to be checked according to the first verification rule and the second verification rule, and then when receiving the data to be checked, uses the target verification rule to verify the data to be checked, and outputs the verification result. The present application can automatically generate a target verification rule according to the field identifier to be checked without the need for user configuration, which can improve the configuration efficiency of the verification rule. Moreover, the target verification rule generated by the present application covers the second verification rule required for the application field to be applied, and can perform a comprehensive verification on the data to be checked, so that the verified data to be checked can be directly applied to the corresponding application field without the need for secondary verification, which can improve the verification efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0045] Figure 1 A flowchart of the first embodiment of the rule configuration method of this application is provided;

[0046] Figure 2 A flowchart of the second embodiment of the rule configuration method of this application is provided;

[0047] Figure 3 A flowchart of the third embodiment of the rule configuration method of this application is provided;

[0048] Figure 4 A flowchart of the fourth embodiment of the rule configuration method of this application is provided;

[0049] Figure 5 A schematic diagram of the device structure of the hardware operating environment involved in the rule configuration method in the embodiment of the present application.

[0050] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0051] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0052] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0053] The main solution of the embodiment of the present application is: by receiving the field identifier to be checked and the application field to which the field identifier to be checked is to be applied, then according to the attribute of the field identifier to be checked, the first verification rule corresponding to the field identifier to be checked is determined, according to the application field of the field identifier to be checked, the second verification rule corresponding to the field identifier to be checked is determined, and finally according to the first verification rule and the second verification rule, the target verification rule of the field identifier to be checked is generated, and then when the data to be checked is received, the target verification rule is used to verify the data to be checked, and the verification result is output. The present application can automatically generate the target verification rule according to the field identifier to be checked without the need for the user to configure it, which can improve the configuration efficiency of the verification rule. And the target verification rule generated by the present application covers the second verification rule required for the application field to be applied, and can perform a comprehensive verification on the data to be checked, so that the verified data to be checked can be directly applied to the corresponding application field without the need for a second verification, which can improve the verification efficiency.

[0054] In this embodiment, for the convenience of description, the following description is made by taking the identification terminal device as the execution subject.

[0055] Since rule configuration is usually performed by staff members to configure the verification rules for corresponding data fields one by one according to verification requirements, however, when faced with large amounts of data, configuring the verification rules for corresponding data fields one by one takes a lot of time.

[0056] This application can automatically generate target verification rules according to the identifier of the field to be verified without the need for user configuration, which can improve the configuration efficiency of the verification rules. In addition, the target verification rules generated by this application cover the second verification rules required for the application field to be applied, and can perform a comprehensive verification on the data to be verified, so that the verified data to be verified can be directly applied to the corresponding application field without the need for secondary verification, which can improve the verification efficiency.

[0057] Based on this, the present application embodiment provides a rule configuration method, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the rule configuration method of the present application.

[0058] In this embodiment, the rule configuration method includes steps S10 to S50:

[0059] Step S10: receiving a field identifier to be checked and an application field to which the field identifier to be checked is to be applied;

[0060] In this embodiment, the user can directly input the field identifier to be checked for which the verification rule needs to be configured and the application field to which the field identifier to be checked is to be applied. The application field to which the field identifier to be checked is to be applied refers to the application field to which the data to be checked corresponding to the field identifier to be checked is to be applied after the data to be checked is checked by the verification rule. The field identifier to be checked can be the name of the field to be checked.

[0061] In a feasible implementation manner, if the user does not know which fields in the to-be-verified data need to be verified, the user may input all the field identifiers involved in the verification data as the to-be-verified field identifiers.

[0062] Step S20: determining a first verification rule corresponding to the field identifier to be verified according to the attribute of the field identifier to be verified;

[0063] It should be noted that the attribute of a field identifier refers to the attribute used to describe the characteristics or properties of the verification data corresponding to the field identifier. The attributes corresponding to different field identifiers may be the same or different, and the attribute corresponding to a field identifier may correspond to one or more attributes.

[0064] In this embodiment, after receiving the field identifier to be checked and the application field to be applied of the field identifier to be checked input by the user, the attribute of the field identifier to be checked can be determined based on the field identifier to be checked, so that the check rule corresponding to the target check field identifier that is the same as the field identifier to be checked in the check field identifier associated with the attribute is determined as the first check rule corresponding to the field identifier to be checked.

[0065] In a feasible implementation, by collecting historical verification rules corresponding to various types of historical verification data of the system, the verification rules corresponding to each verification field identifier in the historical verification rules are obtained. Then, by clustering the verification rules, the verification rules belonging to the same cluster are determined. The verification field identifier corresponding to the verification rules of the same cluster is then defined as the same attribute, and the verification field identifier belonging to the same attribute and the verification rules corresponding to the verification field identifier are associated with the attribute and saved. When the field identifier to be verified input by the user is received, the attribute associated with the field identifier to be verified can be determined, so that the verification rule corresponding to the target verification field identifier that is the same as the field identifier to be verified in the verification field identifier associated with the attribute is determined as the first verification rule corresponding to the field identifier to be verified.

[0066] In a feasible implementation, cluster analysis can be performed based on the verification type of the historical verification rules, which can be divided into data format, logical relationship, range restriction, etc., which is not specifically limited in this embodiment. Verification rules belonging to different verification types can be divided into different attributes.

[0067] It should be noted that the data format check type refers to the check of the data length, data type, etc. of the check data corresponding to the check field identifier. The logical relationship check type refers to the check of the relationship between the check field identifier and other check field identifiers. This relationship can be the size, equality or other relationship between them. For example, whether the check field identifier A is greater than the check field identifier B. The range restriction check type refers to the check of the range of the check field. For example, whether the check field identifier S is greater than 20.

[0068] Step S30: Determine a second verification rule corresponding to the field identifier to be verified according to the application field of the field identifier to be verified;

[0069] In this embodiment, by searching the database to which the application field belongs for the same check field identifier as the field identifier to be checked, the check rule corresponding to the same check field identifier is determined as the second check rule corresponding to the field identifier to be checked.

[0070] In a feasible implementation, standard files corresponding to different application fields may be obtained in advance, and then the standard files may be identified to determine the information to be verified, and then a second verification rule corresponding to the verification field in the application field may be generated according to the information to be verified.

[0071] It should be noted that standard documents refer to documents developed and issued by standardization departments, institutions or units in different application fields, which are used to regulate and guide the work, products or services in related fields. Standard documents contain a series of specifications, requirements and guidelines, aiming to provide unified standards and guidelines to ensure the quality, safety and interoperability of products, services or work.

[0072] In this embodiment, the present application collects standard files of different application fields and identifies the contents of the standard files to filter out the information to be verified from the standard files. The information to be verified includes the verification field identifier and the relevant information of the verification rule corresponding to the verification field identifier, so as to further organize the information to be verified, generate the verification field identifier and the verification rule corresponding to the verification field identifier, and then associate the verification field identifier and the verification rule corresponding to the verification field identifier and save them in a database of the corresponding application field.

[0073] In a feasible implementation, the standardization departments, institutions or units corresponding to each application field generally have official websites that publish standard documents. Therefore, the official websites corresponding to each application field can be monitored by setting corresponding interfaces. When a new document is released by the official website, the title of the new document is parsed to determine whether it is a standard document. If it is a standard document, the steps of identifying the standard document and determining the information to be verified are executed.

[0074] In another feasible implementation, the official website of the standardization department, institution or unit corresponding to each application field can be subscribed to so that when the official website releases the standard file, the standard file released can be automatically sent to the official website. Then, when the standard file sent by the official website is received, the steps of identifying the standard file and determining the information to be verified are performed.

[0075] Step S40: generating a target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule;

[0076] In this embodiment, since the first verification rule is obtained based on the historical verification rules of the system, and the historical verification rules are set by the user in the past according to their own needs, and the second verification rule is generated according to the standard file of the application field, the two may have the same verification rules. Therefore, this application identifies the first verification rule and the second verification rule corresponding to each field identifier to be verified, deletes one of the same verification rules, and the remaining verification rule after deletion is the target verification rule for the field identifier to be verified.

[0077] It should be noted that the target verification rules corresponding to the field identifier to be verified automatically generated by this application not only include the verification rules required by the user himself, but also include the verification rules required in the corresponding application field, so that when the data to be verified is verified, the data to be verified can be comprehensively verified, so that the verified data can be well applied to the corresponding application field without the need for secondary verification.

[0078] Since the target verification rule is generated according to the first verification rule and the second verification rule, and the first verification rule and the second verification rule are determined based on different principles. Therefore, there may be a conflict between the first verification rule and the second verification rule corresponding to the same field identifier to be verified in the target verification rule corresponding to the field identifier to be verified. This will cause the data to be verified corresponding to the same field identifier to be verified to never meet the first verification rule and the second verification rule at the same time, and thus the data to be verified will never pass the verification. For example, the first verification rule corresponding to the field identifier A to be verified is A greater than 20, and the second verification rule is A<18.

[0079] In another feasible implementation manner, the step of generating the target verification rule for the field identifier to be verified includes: comparing the first verification rule and the second verification rule corresponding to each field identifier to be verified in the target verification rule, determining the first target verification rule and the second target verification rule with conflicts, and selecting the third target verification rule from the first target verification rule and the second target verification rule according to the verification reference values and verification operators in the first target verification rule and the second target verification rule, so as to delete the verification rules not selected in the first target verification rule and the second target verification rule, so that there are no conflicting verification rules in the target verification rule.

[0080] It should be noted that the first target verification rule is the verification rule in the first verification rule, and the second target verification rule is the verification rule in the second verification rule. The verification reference value refers to the fixed value compared with the field identifier to be verified in the verification rule. For example, if the verification rule is A < 200, 200 is the verification reference value. The verification operator refers to the operator used to determine whether the field to be verified meets specific conditions in the verification rule. Verification operators include comparison operators, logical operators, etc. For example, if the verification rule is A < 200, < is the verification operator.

[0081] In addition, it should also be noted that since the second target verification rule is determined according to the standard document, the first target verification rule needs to meet the second target verification rule. That is, the first target verification rule should be a specific refinement or further limitation under the condition of meeting the second target verification rule. For example, the second target verification rule is that the data type of the field identifier A to be verified is a string or an integer. Therefore, the first target verification rule is that the data type of the field identifier A to be verified is a string, or the data type of the field identifier A to be verified is an integer, or the data type of the field identifier A to be verified is a string or an integer, then it meets the second target verification rule. Another example, the second target verification rule is that the field identifier A < 200. Therefore, the first target verification rule is that the field identifier A < s, s should be a value less than or equal to 200 to meet the second target verification rule, or the first target verification rule is that s1 < A < s2, s2 should be a value less than or equal to 200 to meet the second target verification rule.

[0082] In this embodiment, the present application obtains the check operator and check reference value of the first target check rule and the second target check rule, and then respectively determines the first range composed of the check operator and the check reference value corresponding to the first target check rule, and the second range composed of the check operator and the check reference value corresponding to the second target check rule. If the first range is within the second range, the first target check rule is selected as the third target check rule, and the second target check rule is deleted. If the first range exceeds the second range, the second target check rule is selected as the third target check rule, and the first target check rule is deleted.

[0083] In another feasible implementation, if the first range is within the second range, the third target verification rule can be selected according to the priority of the first verification rule and the second verification rule. Specifically, if the priority of the first verification rule is higher than the second verification rule, and the first range is within the second range, the first target verification rule is selected as the third target verification rule. If the priority of the second verification rule is higher than the second verification rule, the second target verification rule can be directly selected as the third target verification rule without determining whether the first target verification rule is within the range of the second target verification rule. The priority of the first verification rule and the second verification rule can be set by the user.

[0084] Step S50: When receiving the data to be verified, the data to be verified is verified using the target verification rule, and a verification result is output.

[0085] In this embodiment, when the data to be verified is received, the pre-generated target verification rules are used to verify the data to be verified, and the verification results are output so that the user can make targeted modifications to the data to be verified according to the verification results, and then verify it again until the data to be verified passes the verification, which can improve the verification efficiency of the data to be verified.

[0086] In a feasible implementation, while outputting the verification result, the unverified data to be verified and / or the verification rules corresponding to the data to be verified can also be output in a preset display mode. The preset display mode can be a chart, text prompt, etc., which is not specifically limited in this embodiment.

[0087] In the technical solution provided in this embodiment, by receiving the field identifier to be checked and the application field to be applied of the field identifier to be checked, then according to the attribute of the field identifier to be checked, the first verification rule corresponding to the field identifier to be checked is determined, according to the application field of the field identifier to be checked, the second verification rule corresponding to the field identifier to be checked is determined, and finally according to the first verification rule and the second verification rule, the target verification rule of the field identifier to be checked is generated, and then when the data to be checked is received, the target verification rule is used to verify the data to be checked, and the verification result is output. The present application can automatically generate the target verification rule according to the field identifier to be checked without the need for the user to configure it, which can improve the configuration efficiency of the verification rule. And the target verification rule generated by the present application covers the second verification rule required for the application field to be applied, and can perform a comprehensive verification on the data to be checked, so that the verified data to be checked can be directly applied to the corresponding application field without the need for secondary verification, which can improve the verification efficiency.

[0088] Reference Figure 2 In the second embodiment, based on the first embodiment, before step S40, the steps include:

[0089] In this embodiment, the rule configuration method includes steps S60 to S70:

[0090] Step S60: displaying the first verification rule and the second verification rule on the rule configuration interface;

[0091] In this embodiment, by displaying the first verification rule and the second verification rule in the rule configuration interface, the user can modify the first verification rule and the second verification rule according to current needs, or add a new verification rule. It can be understood that the verification rule newly added by the user in the rule configuration interface is regarded as the first verification rule.

[0092] Step S70: upon receiving a confirmation action of the rule configuration interface, generating the target verification rule for the field identifier to be verified according to the rule configuration interface.

[0093] In this embodiment, after the user completes the configuration of the rule configuration interface, the confirmation action in the rule configuration interface can be triggered. When the system receives the confirmation action of the rule configuration interface, it generates target verification rules for the field identifier to be verified according to the verification rules in the rule configuration interface, so that the generated target verification rules are more in line with the verification requirements of the data to be verified, thereby improving the user experience.

[0094] In another feasible implementation, after the system receives the field identifier to be checked and the application field to be applied of the field identifier to be checked input by the user, it can output a prompt message whether it is necessary to automatically generate a verification rule. If a confirmation reply is received, the step of determining the first verification rule corresponding to the field identifier to be checked according to the attribute of the field identifier to be checked is executed. If a negative reply is received, the field identifier to be checked input by the user is directly displayed in the rule configuration interface, and / or the entry of the standard file corresponding to the application field or the information to be checked corresponding to the standard file is displayed at the corresponding position in the rule configuration interface. This allows the user to configure the target verification rule for each field identifier to be checked in the rule configuration interface. And / or view the standard file or the information to be checked corresponding to the standard file through the entry, so as to configure the target verification rule for each field identifier to be checked in the rule configuration interface according to the standard file or the information to be checked corresponding to the standard file.

[0095] In another feasible implementation, the rule configuration method also includes: when a trigger action of the rule management interface is received, the rule management interface is displayed, and optional verification rules are displayed on the rule management interface; when a selected action of the rule management interface is received, the verification rules corresponding to the selected action are obtained, and a target verification rule is generated according to the verification rule, and then when the data to be verified is received, the target verification rule is used to verify the data to be verified, and the step of outputting the verification result is executed.

[0096] In this embodiment, the present application provides a rule management interface for managing historical first verification rules, so the optional verification rules displayed in the rule management interface are all the first verification rules configured by the user. The user can select the optional verification rules in the rule management interface, and after the selection is completed, the selected action can be triggered. Then, when the rule management interface receives the selected action of the rule management interface, it will obtain the verification rules selected by the user, so as to combine the verification rules into the target verification rules.

[0097] It is understandable that the user can click the enter button of the rule management interface, so that the system can receive the trigger action of the rule management interface. The user can click the confirm selection button of the rule management interface, so that the system can receive the selected action of the rule management interface.

[0098] In another feasible implementation, after obtaining the verification rule corresponding to the selected action and generating the target verification rule according to the verification rule, the target verification rule can be displayed in the rule configuration interface, so that the user can modify the target verification rule in the rule configuration interface, or add a new verification rule. When receiving the confirmation action of the rule configuration interface, the target verification rule for the field to be verified is regenerated according to the rule configuration interface. It can be understood that the newly added verification rule in the rule configuration interface is regarded as the first verification rule.

[0099] It should be noted that the rule management interface also supports updating of verification rules, for example, editing, modifying, deleting, etc. the verification rules in the rule management interface.

[0100] In the technical solution provided in this embodiment, by displaying the first verification rule and the second verification rule on the rule configuration interface, when receiving the confirmation action of the rule configuration interface, the target verification rule for the field identifier to be verified is generated according to the rule configuration interface, so that the generated target verification rule is more in line with the verification requirements of the data to be verified, thereby improving the user experience.

[0101] Reference Figure 3 In a third embodiment, based on any of the above embodiments, step S50 includes:

[0102] In this embodiment, the rule configuration method includes steps S80 to S100:

[0103] Step S80: upon receiving the data to be verified, obtaining the data format of the verification data corresponding to each verification field identifier in the data to be verified;

[0104] Step S90: when the data format of the verification data corresponding to the verification field identifier in the to-be-verified data is different from the data format corresponding to the verification field identifier in the target verification rule, converting the data format of the verification data corresponding to the verification field identifier into the data format corresponding to the to-be-verified field identifier in the target verification rule;

[0105] In this embodiment, when receiving the data to be verified, in order to avoid the data format of the data to be verified being different from the data format corresponding to the verification field identifier, which results in failure to verify or an erroneous verification result when the target verification rule is used to verify the data to be verified. Before verifying the data to be verified, the application converts the data format of the data to be verified into the data format corresponding to the field identifier to be verified in the target verification rule, so that the target verification rule can verify the data to be verified, thereby improving the accuracy of the verification result.

[0106] For example, the data format corresponding to the field identifier A to be checked is in the year-month-day format, and the data format of the received data to be checked corresponding to the field identifier A to be checked is a timestamp. This application will convert the data format of the data to be checked in the timestamp format into the year-month-day data format.

[0107] In a feasible implementation, the present application is provided with a preprocessing configuration interface for input data. The preprocessing configuration interface supports setting processing rules for input data in different ways. The input data of the present application refers to the received data to be verified. That is, when the data to be verified is received, the processing rules configured by the user based on the preprocessing configuration interface will be used to process the data to be verified, so as to compare the data format of the received data to be verified with the data format of the verification field identifier in the target verification rule. If the data format of the data to be verified is different from the data format of the verification field identifier in the target verification rule, the processing rule will convert the data format of the verification data into the data format of the corresponding field identifier to be verified in the target verification rule, and then use the target verification rule to verify the processed data to be verified.

[0108] In this embodiment, the preprocessing configuration interface sets the processing rules of input data in at least one of the following ways: setting based on regular expressions; setting based on code programming; setting based on Jseigne (js). It should be noted that JsEngine is an interpreter that runs JavaScript. Its processing process is to parse and convert it into an AST syntax tree first, and then the interpreter mainly does two things. The first is to convert it into machine language bytecode, and the second is to hand it over to the editor (optimizting compiler) for optimization. There is also a data analysis process (profilling data) in the middle, the main purpose of which is to optimize the operation of JS. The optimized code is then converted into machine language.

[0109] Step S100: using the target verification rule to verify the data to be verified, and outputting the verification result.

[0110] In this embodiment, after the data format of the data to be verified is converted into a data format corresponding to the field identifier to be verified, the data to be verified is verified using a target verification rule, thereby improving the accuracy of the output verification result.

[0111] In another feasible implementation manner, the data format corresponding to the to-be-checked field identifier in the target rule may be converted to be consistent with the data format of the to-be-checked data, which is not specifically limited in this embodiment.

[0112] In the technical solution provided in the present embodiment, when the data to be verified is received, the data format of the verification data corresponding to each verification field identifier in the data to be verified is obtained, and when the data format of the verification data corresponding to the verification field identifier in the data to be verified is different from the data format corresponding to the field identifier to be verified in the target verification rule, the data format of the verification data corresponding to the verification field identifier is converted into the data format corresponding to the field identifier to be verified in the target verification rule, and then the target verification rule is used to verify the data to be verified, and the verification result is output, so that the target verification rule can correctly verify the data to be verified, thereby improving the accuracy of the verification result.

[0113] Reference Figure 4 In a fourth embodiment, based on any of the above embodiments, before step S50, the steps include:

[0114] In this embodiment, the rule configuration method includes steps S200 to S400:

[0115] Step S200: determining a maximum load value according to the application field, and operating at the maximum load value;

[0116] In this embodiment, the present application determines the maximum load value in advance according to the maximum data volume of data generated in different application fields, that is, the maximum load value is the load value of the system when the data corresponding to the maximum data volume flows into the system. It can be understood that the larger the maximum data volume, the larger the load value of the system when the data corresponding to the maximum data volume flows into the system. The control system of the present application runs at the maximum load value.

[0117] Step S300: receiving test data, verifying the test data using the target verification rule, and outputting the test verification result of the test data;

[0118] In this embodiment, after the system runs at the maximum load value, it receives test data, verifies the test data using target verification rules, and outputs test verification results of the test data.

[0119] It should be noted that after the system runs at the maximum load, it can simulate the load situation when the system receives data corresponding to the maximum data volume, thereby reducing the data volume requirement for the test data. It can also test the system when receiving a large amount of data to be verified, and the verification accuracy of the target verification rules for the data to be verified can be achieved.

[0120] In a feasible implementation, the test data can be input by the user. In addition, the present application also provides a test module, which can be used to generate test data corresponding to the identifiers of each field to be checked in the target verification rule. This embodiment does not specifically limit this.

[0121] Step S400: If the test verification result is passed, the step of verifying the data to be verified by using the target verification rule when receiving the data to be verified is executed, and outputting the verification result.

[0122] In this embodiment, by comparing the test verification result with the actual verification result of the test data, if the test verification result is the same as the actual verification result of the test data, the test verification result is determined to be passed.

[0123] In the technical solution provided in this embodiment, the maximum load value is determined according to the application field, and the system is operated at the maximum load value, and then test data is received, the test data is verified by using the target verification rule, and the test verification result of the test data is output. If the test verification result is passed, the step of verifying the data to be verified by using the target verification rule when receiving the data to be verified and outputting the verification result is executed. Before the target verification rule is put into use, the application can improve the verification accuracy of the target verification rule by running the target verification rule at the maximum load value and using a small amount of test data to test the target verification rule.

[0124] The present application provides a terminal device, which includes: at least one processor; and a memory that is communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the rule configuration method in the above-mentioned embodiment one.

[0125] Reference below Figure 5 , which shows a schematic diagram of the structure of a terminal device suitable for implementing the embodiment of the present application. The terminal device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0126] like Figure 5As shown, the terminal device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the terminal device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the terminal device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a terminal device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0127] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0128] The terminal device provided by the present application adopts the rule configuration method in the above embodiment to solve the technical problem of low rule configuration efficiency. Compared with the prior art, the beneficial effects of the terminal device provided by the present application are the same as the beneficial effects of the rule configuration method provided by the above embodiment, and other technical features in the terminal device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0129] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0130] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0131] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the rule configuration method in the above-mentioned embodiment.

[0132] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0133] The computer-readable storage medium may be included in the terminal device; or may exist independently without being installed in the terminal device.

[0134] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the terminal device, the terminal device: receives the field identifier to be checked and the application field to be applied of the field identifier to be checked, and then determines the first verification rule corresponding to the field identifier to be checked according to the attribute of the field identifier to be checked, determines the second verification rule corresponding to the field identifier to be checked according to the application field of the field identifier to be checked, and finally generates the target verification rule for the field identifier to be checked according to the first verification rule and the second verification rule, and then when receiving the data to be checked, uses the target verification rule to verify the data to be checked and outputs the verification result.

[0135] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0136] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0137] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0138] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned rule configuration method, and can solve the technical problem of low efficiency of rule configuration. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the rule configuration method provided by the above-mentioned embodiment, and will not be repeated here.

[0139] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A rule configuration method, characterized in that: The method comprises: Receive a field identifier to be checked and an application field to which the field identifier to be checked is to be applied; Determine, according to the attribute of the field identifier to be checked, a first checking rule corresponding to the field identifier to be checked; Determine a second verification rule corresponding to the field identifier to be verified according to the application field of the field identifier to be verified; Generate a target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule; When the data to be verified is received, the target verification rule is used to verify the data to be verified, and the verification result is output.

2. The method according to claim 1, characterized in that Before the step of generating the target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule, the step further includes: Displaying the first verification rule and the second verification rule on the rule configuration interface; When a confirmation action of the rule configuration interface is received, the target verification rule of the to-be-verified field identifier is generated according to the rule configuration interface.

3. The method according to claim 1, characterized in that The step of generating the target verification rule for the field identifier to be verified includes: Compare the first verification rule and the second verification rule corresponding to each of the to-be-verified field identifiers in the target verification rule to determine the conflicting first target verification rule and second target verification rule; Selecting a third target verification rule from the first target verification rule and the second target verification rule according to the verification reference value and the verification operator in the first target verification rule and the second target verification rule; Deleting unselected verification rules from among the first target verification rule and the second target verification rule.

4. The method according to claim 1, characterized in that Before the step of receiving the to-be-checked field identifier and the application field to which the to-be-checked field identifier is to be applied, the method includes: Obtaining standard documents corresponding to the application field; Identify the standard file and determine the information to be verified; The second verification rule corresponding to the application field is generated according to the information to be verified.

5. The method according to claim 1, characterized in that The step of generating a target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule comprises: Comparing the first verification rule with the second verification rule, and determining a verification rule in the second verification rule that is the same as the first verification rule; Deleting the same verification rules; The step of generating a target verification rule for the field identifier to be verified according to the first verification rule and the second verification rule is performed.

6. The method according to claim 1, characterized in that The method further comprises: When receiving a trigger action of a rule management interface, displaying the rule management interface and displaying optional verification rules on the rule management interface; When receiving the selected action of the rule management interface, obtaining the verification rule corresponding to the selected action; Generate the target verification rule according to the verification rule; The step of executing the step of, when receiving the data to be verified, using the target verification rule to verify the data to be verified, and outputting the verification result.

7. The method according to any one of claims 1 to 6, characterized in that When receiving the data to be verified, the target verification rule is used to verify the data to be verified, and before the step of outputting the verification result, the method includes: Determine a maximum load value according to the application field, and operate at the maximum load value; Receive test data, verify the test data using the target verification rule, and output the test verification result of the test data; If the test verification result is passed, the step of performing verification on the data to be verified by using the target verification rule when receiving the data to be verified and outputting the verification result is executed.

8. The method according to claim 1, characterized in that When the data to be verified is received, the step of verifying the data to be verified using the target verification rule and outputting the verification result comprises: When the data to be verified is received, the data format of the verification data corresponding to each verification field identifier in the data to be verified is obtained; When the data format of the verification data corresponding to the verification field identifier in the data to be verified is different from the data format corresponding to the field identifier to be verified in the target verification rule, converting the data format of the verification data corresponding to the verification field identifier into the data format corresponding to the field identifier to be verified in the target verification rule; The target verification rule is used to verify the data to be verified, and the verification result is output.

9. A terminal device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the rule configuration method according to any one of claims 1 to 8.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the rule configuration method according to any one of claims 1 to 8 are implemented.

Images