Data verification method and system based on rule engine

Abstract

The present disclosure provides a data verification method and system based on a rule engine, the method comprising: S1, obtaining a data verification request sent by at least one application system; wherein multiple application systems belong to the same business system; S2, parsing the data verification request to obtain data information to be verified; S3, configuring from a set of rules predefined by the rule engine according to the data verification request to obtain corresponding verification rules; S4, using the corresponding verification rules to perform data verification on the data information to be verified to obtain data verification results. The method disclosed in the present disclosure improves the uniformity and consistency of data within the business system, and also greatly increases the security of the business system.

Description

Technical Field

[0001] The present disclosure relates to the technical field of data analysis, and in particular to a data verification method and system based on a rule engine. Background Art

[0002] In the current development of the Internet, a single system can no longer meet the business needs of users. In the same business environment, multiple business systems are interconnected to form a network system, making the relationship between systems increasingly complex. Due to various reasons, many systems in the same business system have common and highly consistent data. This leads to several major problems. First, in the same application system, the volume of the system is getting larger and larger, the number of modules is increasing, and the consistency of data and data rules of related data in different modules is becoming increasingly difficult to ensure. Second, in different systems under the same application system, due to different development teams, it requires more communication costs to make the data verification rules consistent. Third, when calling data interfaces between systems, if the data verification rules between the two systems are inconsistent, additional logic is required to process the data verification rules. At the same time, developers are required to be familiar with the data verification rules of multiple systems, which also increases the difficulty of system maintenance and development and is not convenient for future maintenance of the system. Fourth, when the data verification rules change, multiple systems need to be modified, which has a large maintenance workload and high risks. Summary of the invention

[0003] In view of this, the first aspect of the present disclosure provides a data verification method based on a rule engine, including: S1, obtaining a data verification request sent by at least one application system; wherein, multiple application systems belong to the same business system; S2, parsing the data verification request to obtain data information to be verified; S3, configuring from a rule set predefined by the rule engine according to the data verification request to obtain corresponding verification rules; S4, performing data verification on the data information to be verified using the corresponding verification rules to obtain data verification results.

[0004] According to an embodiment of the present disclosure, multiple application systems under the same business system in S1 share a predefined rule set.

[0005] According to an embodiment of the present disclosure, before obtaining a data verification request sent by at least one application system in S1, the following step is also included: S101, performing a preliminary verification on the data using the application system; if the preliminary verification passes, sending a data verification request.

[0006] According to an embodiment of the present disclosure, the data information to be verified in S2 includes one or more of a data field name, data content, and additional information.

[0007] According to an embodiment of the present disclosure, the rule set predefined by the rule engine in S3 is compiled before S3, and the compilation method includes: S301, in response to the user's setting operation on the rule engine, displaying an editable operation page; wherein the editable operation page includes a visual editing module of multiple verification logics; S302, in response to the user's compilation operation on the visual editing module, generating multiple verification rules, and the multiple verification rules constitute a predefined rule set; wherein the verification rules are composed of multiple verification logics in a certain order and under restrictions.

[0008] According to an embodiment of the present disclosure, configuring from a rule set predefined by a rule engine according to a data verification request in S3 includes: determining at least one verification logic according to a data field name; and configuring according to at least one verification logic to obtain a corresponding verification rule.

[0009] According to an embodiment of the present disclosure, the verification logic in S301 includes one or more of data format verification, data range verification, data consistency verification, and business rule verification.

[0010] According to an embodiment of the present disclosure, using corresponding verification rules to perform data verification on the data information to be verified in S4 includes: S401, inputting the corresponding verification rules into the rule engine; S402, the rule engine executes the corresponding verification logic in sequence according to the verification rules; S403, recording the results of each verification logic to obtain the data verification result.

[0011] According to an embodiment of the present disclosure, the data verification method further includes: S5, providing corresponding processing opinions according to the results of each verification logic, and feeding back the data verification results and processing opinions to the application system.

[0012] The second aspect of the present disclosure provides a data verification system based on a rule engine, including: an acquisition module, used to obtain a data verification request sent by at least one application system; wherein multiple application systems belong to the same business system; a parsing module, used to parse the data verification request to obtain data information to be verified; a configuration module, used to configure from a rule set predefined by the rule engine according to the data verification request to obtain corresponding verification rules; a data verification module, used to perform data verification on the data information to be verified using the corresponding verification rules to obtain data verification results.

[0013] The present invention extracts the data verification part from each application system and performs unified configuration, maintenance and management, thereby ensuring the consistency of data verification rules of each business system within the business system, improving the uniformity and consistency of data within the business system, and greatly increasing the security of the business system; at the same time, it also fundamentally solves the problems of high communication cost and difficult maintenance caused by inconsistent data verification rules between systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0015] Figure 1 The application scenario diagram of the rule engine-based data verification method and system according to an embodiment of the present disclosure is schematically shown;

[0016] Figure 2 A flowchart of a data verification method based on a rule engine according to an embodiment of the present disclosure is schematically shown;

[0017] Figure 3 The following schematically shows a workflow diagram of the data verification middleware according to an embodiment of the present disclosure;

[0018] Figure 4 A schematic diagram of a data verification system based on a rule engine according to an embodiment of the present disclosure is shown; and

[0019] Figure 5 A block diagram of an electronic device suitable for implementing the method described above according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0020] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0021] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0022] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0023] In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0024] Some block diagrams and / or flow charts are shown in the accompanying drawings. It should be understood that some boxes or combinations thereof in the block diagrams and / or flow charts can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that these instructions can create a device for implementing the functions / operations described in these block diagrams and / or flow charts when executed by the processor. The technology of the present disclosure can be implemented in the form of hardware and / or software (including firmware, microcode, etc.). In addition, the technology of the present disclosure can take the form of a computer program product on a computer-readable storage medium storing instructions, which can be used by an instruction execution system or in combination with an instruction execution system.

[0025] Figure 1 The exemplary system architecture 100 that can be applied to the data verification method based on the rule engine according to the embodiment of the present disclosure is schematically shown. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0026] like Figure 1 As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for a communication link between the terminal device 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

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

[0028] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0029] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0030] It should be noted that the data verification method based on the rule engine provided in the embodiment of the present disclosure can generally be executed by the terminal devices 101, 102, 103 and the server 105. Accordingly, the data verification system based on the rule engine provided in the embodiment of the present disclosure can generally be set in the terminal devices 101, 102, 103 and the server 105. The data verification method based on the rule engine provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the data verification system based on the rule engine provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0031] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0032] The following will be based on Figure 1 The scene described by Figure 2~Figure 5 The data verification method based on the rule engine of the disclosed embodiment is described in detail.

[0033] A rule engine is a component embedded in an application that separates business rules or decisions from application code and uses predefined semantic modules to write business rules, accept data input, interpret business rules, and make business decisions based on business rules.

[0034] Figure 2 The flowchart of the data verification method based on the rule engine according to the embodiment of the present disclosure is schematically shown.

[0035] like Figure 2 As shown, the data verification method based on the rule engine may include operations S1 to S4.

[0036] In operation S1, a data verification request sent by at least one application system is obtained; wherein the multiple application systems belong to the same business system.

[0037] In operation S2, the data verification request is parsed to obtain data information to be verified.

[0038] In operation S3, a configuration is performed from a rule set predefined by a rule engine according to the data verification request to obtain corresponding verification rules.

[0039] In operation S4, the data information to be verified is verified using corresponding verification rules to obtain a data verification result.

[0040] In the disclosed embodiment, the data verification part in each application system is extracted, uniformly configured, maintained and managed, and a unified data verification standard system is provided for the downstream system, so that data verification becomes an independent functional module, which is a common part separated from multiple application systems. This method avoids the problem of inconsistency in the format, range and business requirements of the same business field between application systems due to various reasons such as initial data errors and operational errors when there are multiple application systems under the same business system.

[0041] On the basis of the above embodiment, multiple application systems under the same business system in S1 share a predefined rule set.

[0042] Multiple application systems share predefined rule sets, making data verification an independent functional module. This allows each application system to focus more on processing business operations and business logic, improves the processing efficiency of the application system, simplifies the processing logic of the application system, and unifies the control of data verification to facilitate the management of data consistency.

[0043] There are many scenarios in the same business system, including processing the same data or data with the same verification rules. When the data verification rules change, the data verification rules of each system need to be modified, which results in a large amount of repetitive work and high maintenance costs. The data verification rules between multiple systems are not unified, and there are differences in the verification rules of data in each system. When the system interacts with information, redundant and repeated verification of the data format is required. The present invention unifies the data verification rules in each application system, reduces the system changes and maintenance costs when the verification rules change, and makes the logic of the application system more unified, which is convenient for developers to develop. It also further improves the security of the application system and prevents the risk of inconsistent data at the application layer.

[0044] Based on the above embodiment, before obtaining the data verification request sent by at least one application system in S1, the following step is also included: S101, using the application system to perform a preliminary verification on the data; if the preliminary verification passes, a data verification request is sent.

[0045] When users input data into the application system, the application system can perform a preliminary check on the data to reduce the submission of invalid data. If the preliminary check passes, a data verification request is sent. If the preliminary check fails, the data format, data content, etc. need to be modified to ensure the accuracy of the input data from the initial stage.

[0046] On the basis of the above embodiment, the data information to be verified in S2 includes one or more of data field name, data content and additional information.

[0047] The data verification request sent by the application system contains the data information to be verified, and the data verification process verifies the data information. Among them, data verification is a verification operation performed to ensure the integrity of the data. Usually, a verification value is calculated for the original data using a specified algorithm. The receiver calculates the verification value once using the same algorithm. If the verification values ​​calculated twice are the same, it means that the data is complete.

[0048] On the basis of the above-mentioned embodiment, the rule set predefined by the rule engine in S3 is compiled before S3, and the compilation method includes: S301, in response to the user's setting operation on the rule engine, displaying an editable operation page; wherein the editable operation page includes a visual editing module of multiple verification logics; S302, in response to the user's compilation operation on the visual editing module, generating multiple verification rules, and the multiple verification rules constitute a predefined rule set; wherein the verification rules are composed of multiple verification logics in a certain order and under restrictions.

[0049] In actual implementation, the editable operation page is usually a dedicated graphical user interface for configuring and managing validation rules associated with data information. Each validation rule can be composed of at least one validation logic, which is the smallest unit of validation rules. Each validation logic may include information such as name, description, and scope of application. The editable operation page may also provide one or more editors to allow users to create, modify, or delete validation logic. The editor usually contains a variety of tools and options for defining the conditions and actions of the validation logic.

[0050] Based on the above embodiment, configuration from a rule set predefined by a rule engine according to a data verification request in S3 includes: determining at least one verification logic according to a data field name; and configuring according to at least one verification logic to obtain a corresponding verification rule.

[0051] Verification logic verifies the attributes of data information. The editable operation page allows users to define and modify verification rules according to specific business needs and data structures to ensure the accuracy, consistency and integrity of data. The verification rule configuration is used to configure the rules for data verification, specify the prerequisites for the execution of the verification rule, and configure multiple data verifications performed by the verification rule, including whether it is empty, length, enumeration value, etc.

[0052] The editable operation page provides operations for adding, deleting, and modifying. The configuration can be saved after the operation is completed. If the business system changes, you only need to modify the verification rule content through the editable operation page. The verification rule content is dynamically maintained, and the business requirements can be met without redeploying the environment. At the same time, the visual rule configuration based on the intelligent rule engine ensures the security of the data verification method and its downstream system.

[0053] Based on the above embodiment, the verification logic in S301 includes one or more of data format verification, data range verification, data consistency verification, and business rule verification.

[0054] Data format validation defines the format specifications that data should follow, such as email addresses, phone numbers, dates, etc. Data range validation sets the maximum and minimum values ​​allowed for data, such as age, salary, etc. Data consistency validation ensures that the logical relationship between different data items is correct, such as the consistency of mailing addresses and zip codes. Business rule validation defines specific validation logic based on specific business needs, such as user authority verification, order amount verification, etc. Validation logic can also include, for example, establishing standard business data description information. Establishing standard business data description information means adding business data description information to facilitate rule configuration and system maintenance.

[0055] An intelligent rule engine is an engine that can automatically make decisions and inferences based on a predefined set of rules. It can fully verify and cleanse data through a preset set of rules before it enters the system or database. By defining a series of business rules and data verification rules, the input data can be automatically verified and processed. These rules can include verification of data format, data range, data consistency and other aspects to ensure the accuracy and validity of the data.

[0056] On the basis of the above-mentioned embodiment, the data information to be verified is verified using corresponding verification rules in S4, including: S401, inputting the corresponding verification rules into the rule engine; 402, the rule engine executes the corresponding verification logic in sequence according to the verification rules; S403, recording the results of each verification logic to obtain the data verification result.

[0057] After the verification rules are configured, the rule engine is called in the specific business rule processing logic fragment: when calling, the entry and exit of the rule engine call are added to the original business processing logic; after the rule engine is called, it identifies the current data information to be verified and loads the configured verification rules; the rule engine performs data verification on the data information, checks whether the data information complies with the rules, and obtains the data verification result.

[0058] On the basis of the above embodiment, the data verification method further includes: S5, providing corresponding processing opinions according to the result of each verification logic, and feeding back the data verification result and processing opinions to the application system.

[0059] After all data is loaded and initialized, the rule engine processes all rules configured in the scenario one by one and returns the verification results and processing opinions.

[0060] The data verification method based on the rule engine disclosed in the present invention performs data verification on the data verification request initiated by the downstream business system in the same business system through the visual intelligent rule engine middleware, and by setting a predefined rule set, the accuracy of the data verification of the downstream business system is guaranteed under the data verification configured by the rule engine, and a set of data verification standards is also provided for the downstream business system. The present invention improves the uniformity and consistency of data in the business system, and also greatly increases the security of the business system.

[0061] The present disclosure is further described below through specific implementation methods. The above-mentioned server redundant file cleaning method and system are specifically described in the following embodiments. However, the following embodiments are only used to illustrate the present disclosure, and the scope of the present disclosure is not limited thereto.

[0062] This embodiment provides a data verification method based on a rule engine, such as Figure 3As shown, first, a predefined rule data set of business rules is set through a visual intelligent engine, and multiple verification rules are generated. Then, the user fills in the form data or inputs the interface data, and the application system sends a data verification request to the data verification middleware. The information received by the intelligent rule engine middleware is parsed to obtain the data field name, data content and other additional information that need to be verified. According to the request information, the verification rule corresponding to the request is determined. According to the verification rules in the predefined rule set, it is judged whether the data meets the set data rules, and the request is preliminarily filtered. The corresponding data verification result is encapsulated into the request and forwarded to the target system that initiated the request.

[0063] After receiving the forwarded request, the downstream target system parses the data verification rule result information attached to the request. Finally, the data rendering page is loaded according to each business system, and the verification result is returned to the display layer for display.

[0064] Specifically, the data verification method includes:

[0065] (1) Set up a predefined rule set, which includes a series of rules such as data format verification, data range verification, data consistency verification, and business rule verification.

[0066] (2) Rule engine configuration. Load the defined rules into the intelligent rule engine and configure them accordingly. Configure the triggering conditions, execution order, error handling mechanism, etc. of the rule engine.

[0067] (3) Data input. The user or system inputs data into the system through the interface or API. After preliminary data verification rules are set in the corresponding application system to reduce the submission of invalid data, after the data is initially verified, the data packet is sent to the data verification middleware for verification.

[0068] (4) Rule execution. The rule engine automatically verifies and processes the input data according to the configured rules. For each rule, the rule engine will perform the corresponding logical judgment and give corresponding processing opinions (such as pass, fail, warning, etc.) based on the judgment results.

[0069] (5) Result feedback. The rule engine feeds back the verification results to the user or system. If the verification fails, a specific error message is given and the user or system is prompted to make corresponding modifications.

[0070] The present invention extracts the common data verification parts from various application systems under the same business system, and performs unified configuration, maintenance and management. The downstream business system performs business data verification based on the unified data verification of the data verification middleware, which makes the data verification rules of the business systems in the business system consistent as a whole, fundamentally solving the problem of inconsistent data verification rules between modules and systems.

[0071] The present disclosure combines traditional data verification with a visual intelligent engine, extracts traditional data verification from code implementation, and uses a visual operation page to configure rule data sets, thereby lowering the technical threshold for system management and adjustment. At the same time, the visual rule engine middleware can inherit multiple data sources and platforms, enabling the middleware to achieve unified data verification and management in different business scenarios. The visual intelligent engine middleware can verify data from multiple dimensions and further improve the overall quality of the application system.

[0072] Figure 4 A block diagram of a data verification system based on a rule engine according to an embodiment of the present disclosure is schematically shown.

[0073] like Figure 4 As shown, the rule engine-based data verification system 400 includes: an acquisition module 410, a parsing module 420, a configuration module 430 and a data verification module 440.

[0074] The acquisition module 410 is used to acquire a data verification request sent by at least one application system; wherein the multiple application systems belong to the same business system. According to an embodiment of the present disclosure, the acquisition module 410 can be used to execute the above reference Figure 2 The S1 step described is not repeated here.

[0075] The parsing module 420 is used to parse the data verification request to obtain the data information to be verified. According to the embodiment of the present disclosure, the parsing module 420 can be used to execute the above reference Figure 2 The described S2 step will not be repeated here.

[0076] The configuration module 430 is used to configure from the rule set predefined by the rule engine according to the data verification request to obtain the corresponding verification rules. According to the embodiment of the present disclosure, the configuration module 430 can be used to execute the above reference Figure 2 The S3 step described is not repeated here.

[0077] The data verification module 440 is used to perform data verification on the data information to be verified using the corresponding verification rules to obtain the data verification result. According to the embodiment of the present disclosure, the data verification module 440 can be used to perform the above reference Figure 2The described S4 step will not be repeated here.

[0078] It should be noted that any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure, or at least part of the functions of any one of them, can be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure can be split into multiple modules for implementation. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be performed.

[0079] For example, any multiple of the acquisition module 410, the parsing module 420, the establishment module 430, and the solution module 440 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the acquisition module 410, the parsing module 420, the establishment module 430, and the solution module 440 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, at least one of the acquisition module 410, the parsing module 420, the establishment module 430, and the solution module 440 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be performed.

[0080] Figure 5 A block diagram of an electronic device suitable for implementing the method described above according to an embodiment of the present disclosure is schematically shown. Figure 5 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0081] like Figure 5 As shown, the electronic device 500 according to an embodiment of the present disclosure includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage part 508 to a random access memory (RAM) 503. The processor 501 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 501 may also include an onboard memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0082] In RAM 503, various programs and data required for the operation of electronic device 500 are stored. Processor 501, ROM 502 and RAM 503 are connected to each other via bus 504. Processor 501 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 502 and / or RAM 503. It should be noted that the program can also be stored in one or more memories other than ROM 502 and RAM 503. Processor 501 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0083] According to an embodiment of the present disclosure, the electronic device 500 may further include an input / output (I / O) interface 505, which is also connected to the bus 504. The electronic device 500 may further include one or more of the following components connected to the I / O interface 505: an input portion 506 including a keyboard, a mouse, etc.; an output portion 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 508 including a hard disk, etc.; and a communication portion 509 including a network interface card such as a LAN card, a modem, etc. The communication portion 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed, so that a computer program read therefrom is installed into the storage portion 508 as needed.

[0084] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the data verification method based on the rule engine according to the embodiment of the present disclosure is implemented.

[0085] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: 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), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 502 and / or RAM 503 described above and / or one or more memories other than ROM 502 and RAM 503.

[0086] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the data verification method based on the rule engine provided by the embodiment of the present disclosure.

[0087] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 501. According to the embodiment of the present disclosure, the system, modules, units, etc. described above can be implemented by computer program modules.

[0088] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 509, and / or installed from the removable medium 511. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0089] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the processor 501, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0090] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0091] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a 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 box can also occur in a different order from the order marked in the accompanying drawings. For example, two 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 box in the block diagram or flow chart, and the combination of the boxes in the block diagram 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.

[0092] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0093] Although the present disclosure has been shown and described with reference to specific exemplary embodiments of the present disclosure, it should be understood by those skilled in the art that various changes in form and details may be made to the present disclosure without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. Therefore, the scope of the present disclosure should not be limited to the above-mentioned embodiments, but should be determined not only by the appended claims, but also by the equivalents of the appended claims.

Claims

1. A data verification method based on a rule engine, characterized in that: include: S1, obtaining a data verification request sent by at least one application system; wherein the multiple application systems belong to the same business system; S2, parsing the data verification request to obtain data information to be verified; S3, configuring from a rule set predefined by a rule engine according to the data verification request to obtain a corresponding verification rule; S4, performing data verification on the data information to be verified using the corresponding verification rule to obtain a data verification result.

2. The data verification method based on rule engine according to claim 1, characterized in that: The multiple application systems under the same business system in S1 share the predefined rule set.

3. The data verification method based on rule engine according to claim 1, characterized in that: Before obtaining the data verification request sent by at least one application system in S1, the following step further includes: S101, using the application system to perform a preliminary check on the data; if the preliminary check passes, sending the data check request.

4. The data verification method based on rule engine according to claim 1, characterized in that: The data information to be verified in S2 includes one or more of data field name, data content and additional information.

5. The data verification method based on rule engine according to claim 4 is characterized in that: The rule set predefined by the rule engine in S3 is compiled before S3, and the compilation method includes: S301, in response to a user's setting operation on the rule engine, displaying an editable operation page; wherein the editable operation page includes a visual editing module of multiple verification logics; S302, in response to the user's arrangement operation on the visual editing module, a plurality of the verification rules are generated, and the plurality of the verification rules constitute the predefined rule set; wherein the verification rules are composed of multiple verification logics in a certain order and under restriction conditions.

6. The data verification method based on rule engine according to claim 5, characterized in that: The configuration in S3 from the rule set predefined by the rule engine according to the data verification request includes: Determine at least one verification logic according to the data field name; Configuration is performed according to the at least one verification logic to obtain corresponding verification rules.

7. The data verification method based on rule engine according to claim 5, characterized in that: The verification logic in S301 includes one or more of data format verification, data range verification, data consistency verification, and business rule verification.

8. The data verification method based on rule engine according to claim 1, characterized in that: In S4, performing data verification on the data information to be verified by using the corresponding verification rule includes: S401, inputting the corresponding verification rule to the data information to be verified into the rule engine; S402, the rule engine executes corresponding verification logic in sequence according to the verification rules; S403, recording the result of each verification logic to obtain a data verification result.

9. The data verification method based on rule engine according to claim 1, characterized in that: The data verification method further includes: S5, providing corresponding processing opinions according to the result of each verification logic, and feeding back the data verification result and the processing opinions to the application system.

10. A data verification system based on a rule engine, characterized in that: include: An acquisition module, used to acquire a data verification request sent by at least one application system; wherein the multiple application systems belong to the same business system; A parsing module, used to parse the data verification request to obtain data information to be verified; A configuration module, configured to obtain corresponding verification rules from a rule set predefined by a rule engine according to the data verification request; The data verification module is used to perform data verification on the data information to be verified using the corresponding verification rules to obtain a data verification result.

Images