CN113986247A

CN113986247A - Service data verification method, device and system

Info

Publication number: CN113986247A
Application number: CN202111286540.7A
Authority: CN
Inventors: 谢帅; 张健; 张贺; 孔令宇
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-11-02
Filing date: 2021-11-02
Publication date: 2022-01-28

Abstract

The invention discloses a business data checking method, a device and a system, which can be applied to the technical field of finance, wherein the method comprises the following steps: obtaining each ticket face element of the service data to be verified in the information system, wherein the ticket face element is generated according to the input of the service data to be verified; determining each ticket element and a corresponding calibrator based on the preset incidence relation between the ticket elements and the calibrator so that the calibrator performs calibration operation on the corresponding ticket elements based on the affiliated program codes; receiving the verification result of each verifier, and generating a verification report according to the verification result of each verifier according to a predetermined rule, wherein the verification report comprises: each ticket element and corresponding verification result. The invention can reduce the workload of the service data verification and improve the verification efficiency.

Description

Service data verification method, device and system

Technical Field

The invention relates to the technical field of finance, in particular to a business data checking method, a device and a system.

Background

In system development, the correctness of data provides great guarantee for the robustness of the system. Therefore, the content of the data is necessary to be checked before the data is processed, and the method is particularly important for bill information in banks, and the operation of the image system can be seriously influenced if the information is illegal.

At present, a common method for developing projects is to write a large number of codes to judge data after user entry or before data submission, and return error information if the data fails.

However, this approach has a number of drawbacks: firstly, the development amount is large, and a large amount of service related codes need to be written for data verification; secondly, code arrangement is not clear, certain data items are easy to miss, and multiple positions need to be modified when updating is needed, so that front and back are not uniform easily; third, it is not friendly to the service personnel, the bill service often has the situation that one service contains many bills, if the error description is not clear, the service personnel can hardly determine the error reason in the first time.

Disclosure of Invention

In view of the above, the present invention provides a method, an apparatus, and a system for verifying service data, so as to solve at least one of the above-mentioned problems.

According to a first aspect of the present invention, a method for verifying service data is provided, the method comprising:

obtaining each ticket face element of the service data to be verified in the information system, wherein the ticket face element is generated according to the input of the service data to be verified;

determining each ticket element and a corresponding calibrator based on the preset incidence relation between the ticket elements and the calibrator so that the calibrator performs calibration operation on the corresponding ticket elements based on the affiliated program codes;

receiving the verification result of each verifier, and generating a verification report according to the verification result of each verifier according to a predetermined rule, wherein the verification report comprises: each ticket element and corresponding verification result.

Preferably, the checker is set by:

setting the verification logic of each ticket face element based on historical service data and a verification rule;

setting a corresponding checker according to each ticket element and the corresponding checking logic, wherein the checker comprises the following types: the system comprises a basic data checker, a logic operation checker, a ticket face element checker and a ticket service checker.

Specifically, generating a verification report according to the verification result of each verifier according to a predetermined rule includes: splicing the check results of each checker according to a preset check logic rule and a splicing rule to generate a check report of the service data to be checked, wherein the check logic rule comprises: each checker checks the logical rule of the and, or, not of the result.

According to a second aspect of the present invention, there is provided a service data checking apparatus, including:

the system comprises a ticket face element acquisition unit, a ticket face element generation unit and a ticket face element verification unit, wherein the ticket face element acquisition unit is used for acquiring each ticket face element of service data to be verified in an information system, and the ticket face element is generated according to the input of the service data to be verified;

the checker determining unit is used for determining each ticket element and a corresponding checker thereof based on the preset incidence relation between the ticket elements and the checkers so that the checkers perform check operation on the corresponding ticket elements based on the affiliated program codes;

a verification report generating unit, configured to receive a verification result of each verifier, and generate a verification report according to the verification result of each verifier according to a predetermined rule, where the verification report includes: each ticket element and corresponding verification result.

Preferably, the apparatus further comprises: a checker setting unit for setting a checker, the checker setting unit including:

the verification logic setting module is used for setting the verification logic of each ticket face element based on the historical service data and the verification rule;

the checker setting module is used for setting a corresponding checker according to each ticket element and the corresponding checking logic, and the checker comprises the following types: the system comprises a basic data checker, a logic operation checker, a ticket face element checker and a ticket service checker.

The verification report generating unit is specifically configured to: splicing the check results of each checker according to a preset check logic rule and a splicing rule to generate a check report of the service data to be checked, wherein the check logic rule comprises: each checker checks the logical rule of the and, or, not of the result.

According to a third aspect of the present invention, there is provided a service data verification system, the system comprising: the service data verifying device and the at least one verifier are used for verifying the ticket elements acquired by the service data verifying device based on the program code.

Specifically, the checker includes:

the preposed checking module is used for carrying out form checking operation and type conversion operation on the ticket face elements;

and the checking module is used for executing checking operation on the ticket face elements after the type conversion based on the program codes.

According to a fourth aspect of the present invention, there is provided an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method when executing the program.

According to a fifth aspect of the invention, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method.

According to the technical scheme, the check method comprises the steps that each ticket element of the to-be-checked service data in the information system is obtained, the corresponding checker is determined according to the association relation between the ticket element and the corresponding checker, so that the corresponding ticket element is checked by the checker according to the program code of the checker, the check result of each checker is received, the check report is generated according to the check result of each checker according to the preset rule, the service data can be checked simply and quickly by presetting the checker, and compared with the prior art, the service data check scheme is small in workload and high in check efficiency.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

Fig. 1 is a block diagram of a service data verification system according to an embodiment of the present invention;

fig. 2 is a block diagram of a structure of a service data verification apparatus according to an embodiment of the present invention;

fig. 3 is a block diagram of a configuration of a checker setting unit according to an embodiment of the present invention;

fig. 4 is a block diagram of the structure of the checker 2 according to the embodiment of the present invention;

FIG. 5 is a flow chart of verification of data to be verified according to an embodiment of the present invention;

FIG. 6 is an exemplary diagram of checkers and their class relationships, according to an embodiment of the invention;

fig. 7 is a flowchart of a service data checking method according to an embodiment of the present invention;

fig. 8 is a schematic block diagram of a system configuration of an electronic apparatus 600 according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

In view of the problems of large workload, low verification efficiency and the like existing in the conventional method for verifying data accuracy by writing a large number of codes, the embodiment of the invention provides a business data verification scheme, which can verify each ticket element of business data by presetting a verifier, can simply and quickly verify the business data, and compared with the prior art, the business data verification scheme of the embodiment of the invention has the advantages of small workload and high verification efficiency. Embodiments of the present invention are described in detail below with reference to the accompanying drawings.

Fig. 1 is a block diagram of a service data verification system according to an embodiment of the present invention, and as shown in fig. 1, the system includes: the system comprises a service data checking device 1 and at least one checker 2, wherein the service data checking device is used for acquiring each ticket element of service data to be checked, which is input into an information system, and the checker is used for checking the ticket element acquired by the service data checking device based on a program code to which the checker belongs.

In the specific implementation process, a plurality of verifiers can be preset, and each verifier respectively verifies corresponding ticket face elements based on the affiliated program code, so that the business data can be verified simply and quickly.

The service data verification apparatus 1 and the verifier 2 are described in detail below.

Service data checking device 1

Fig. 2 is a block diagram of the structure of the service data verification apparatus 1, and as shown in fig. 2, the service data verification apparatus 1 includes: a face element acquisition unit 11, a checker determination unit 12, and a check report generation unit 13, wherein:

the ticket face element acquiring unit 11 is configured to acquire each ticket face element of the to-be-verified service data in the information system, where the ticket face element is generated according to the to-be-verified service data.

The checker determining unit 12 is configured to determine each face element and a corresponding checker based on a preset association relationship between the face element and the checker, so that the checker performs a checking operation on the corresponding face element based on the affiliated program code.

A verification report generating unit 13, configured to receive the verification result of each verifier, and generate a verification report according to the verification result of each verifier according to a predetermined rule, where the verification report includes: each ticket element and corresponding verification result.

Specifically, the verification report generating unit 13 may splice the verification results of each verifier according to a predetermined verification logic rule and a predetermined splicing rule, and generate a verification report of the service data to be verified, where the verification logic rule includes: each checker checks the logical rule of the and, or, not of the result.

The check device comprises a check device determining unit 12, a check report generating unit 13, a check report generating unit and a check device, wherein the check device determining unit 12 determines each check device corresponding to each check device and each check device according to the association relationship between the check device and the check device, so that the check device performs check operation on the corresponding check device based on the corresponding program code, the check report generating unit receives the check result of each check device and generates the check report according to the check result of each check device according to the preset rule.

In practical operation, the above apparatus further comprises: and the calibrator setting unit is used for setting the calibrator. Fig. 3 is a block diagram of a configuration of a checker setting unit, and as shown in fig. 3, the checker setting unit includes: a check logic setting module 41 and a checker setting module 42, wherein:

In practical operation, the checker setting module may set a program code for the checker based on C #, Java, Python, or other languages.

(II) checker 2

Fig. 4 is a block diagram of the structure of the verifier 2, and as shown in fig. 4, the verifier 2 includes: a pre-check module 21 and a check module 22, wherein:

the preposed checking module 21 is used for carrying out form checking operation and type conversion operation on the ticket face elements;

and the checking module 22 is used for performing checking operation on the ticket elements after the type conversion based on the affiliated program codes.

In practical operation, the units and the modules may be combined or may be singly arranged, and the present invention is not limited thereto.

For better understanding of the present invention, the program code of the C # speech construction checker is taken as an example to describe the embodiment of the present invention.

It should be noted that the embodiment of the present invention is also applicable to languages such as Java and Python, and Java annotation, Python decorator, and the like may be used instead of the C # property, which is a term in C # speech and is a declarative tag for transferring behavior information of various elements in a program at runtime.

In this embodiment, an example system for data verification is provided, and includes: the data verification engine, the data verification module and the verification auxiliary module are respectively described below.

Data verification engine

The data check engine is used for calling check logic for specified data (corresponding to the ticket elements) and returning a check report, and also supports a checker for acquiring specific attributes (the attribute is a professional term in C #, is an extension of member variables or methods in a class or a structure, and can be accessed by using the same syntax). The data verification engine can extend the related verification function for all verifiable data.

For specified data, a verifier that can obtain a certain attribute, such as a "GetValidator" method that calls an instance object, can return a verifier associated with the data according to an attribute name, and the association is labeled by a developer when defining a data structure.

In practical operation, the specific workflow of the data verification engine includes the following steps:

1. checking whether the attribute name is a null object or whether the content of the character string is blank, namely checking whether the content of the ticket face element is null;

2. acquiring the data type of the instance object, and acquiring the attribute information by reflection according to the attribute name (the reflection is to reversely obtain a data definition structure in the source code according to the data object in operation);

3. acquiring a characteristic object labeled during data definition, and traversing all the checker types to determine corresponding checkers;

4. the checker type objects corresponding to all the ticket elements are stored as a list as a return value.

In specific implementation, for a specified verifiable data structure, the object may be completely verified by calling a "valid" method extended by the data verification engine according to the following flow shown in fig. 5, and finally a verification report is returned to prompt service personnel of the error location and the reason. As shown in fig. 5, a verification process for data to be verified specifically includes:

1. and acquiring a class definition of the data to be verified by using a reflection mechanism in the C #, then acquiring all characteristic (C # term) objects marked in the class definition, and traversing to extract and verify related objects, namely acquiring the nominal elements of the data to be verified.

2. If the property object marking the module name exists in the property object set related to the verification, a verification item name is generated through the property object (the data verification module (II) is described in detail below), and the name is stored by using a temporary variable for later use.

3. And acquiring a checker list of the data, sequentially executing all the checkers, recording results, and exiting the checking process if the data fails and only checking does not generate a report.

4. All attributes (C # terms) in the class are traversed, and the processing of the steps 2 and 3 is performed in sequence recursively, and the process is skipped directly if the attribute is not labeled with any check-related information.

5. For the ticket surface elements with the attributes of an array, a list and a set, traversing each element in the check array, and simultaneously recording the serial number of data during checking, thereby facilitating the description of the sequence.

6. After the verification is completed, all verification results are synthesized and summarized to generate a complete text description, wherein the steps comprise: the business name, the certificate name, the ticket face element and the verification result thereof. For the data items successfully verified, the verification information can be selected not to be recorded and displayed.

7. The check logic completes recursive traversal, and after returning to the outermost layer, the text description is finally returned as a check report, the user interface is displayed to the service personnel in a user-defined mode, and the service personnel can clearly know whether the content of the input certificate is correct and the corresponding error reason.

(II) data checking module

The data checking module is used for defining the checking logic of the data and is a reusable checking logic class. When developing based on C #, the corresponding relation between the marked data and the check logic can be directly marked on the definition sentences of the classes or the attributes. During verification, the data verification engine processes the objects and realizes specific verification logic. When a checker is acquired, the checker objects in the returned list also belong to the module.

All the verifiers in this module contain a name, a pre-verifier (with the function of the pre-verification module 21) and a data verification interface (with the function of the verification module 22). The name is used for identifying the data item currently being verified, a user-friendly Chinese name is provided, English attribute names in the code are prevented from being directly displayed, and the Chinese name can also be transmitted in during marking; the pre-checker is used for defining the basic check logic of the current checker, each checker comprises a pre-checker and can be used as an independent pre-checker to form a complete data check chain, and the pre-checker is recursively called during check until the pre-checker is empty. In the embodiment of the present invention, the data check interface call parameter may uniformly adopt object type data, and objects in object oriented languages such as C #, Java, Python, and the like all represent base classes of all types.

For the specified data, the check logic of the data check module is as follows:

1. the data is transmitted into the pre-checker, the pre-checker is used for checking, and specifically which kind of checker is used as the pre-checker is defined by the service, for example, when checking the amount of money character string, it is required to check whether the data exceeds the 11-bit character string. For other verifiers, there is a similar definition, and it is necessary to recursively enter this verification flow.

2. And if the pre-check fails, directly returning a result. And after the verification is successful, performing logic processing of the current verifier.

3. And (4) converting the data object into the type required by verification, judging the type of the data object if necessary, and directly returning failure and reasons if the type is wrong. For example, after the pre-check of the amount character string, the data needs to be converted into a character string object, whether the character string contains characters other than numbers is checked, and if not, the check is successful.

4. And checking the data, and recording the failure reason for the data which does not meet the logic requirement.

5. And returning a verification result.

In practical operation, the checkers in the data checking module are mainly classified into four types: a basic data checker, a logic operation checker, a ticket face element checker and a ticket service checker. Fig. 6 is an exemplary diagram of each verifier and its class relationship, and as shown in fig. 6, the basic data verifier (shown as a basic field verifier) and the logical operation verifier (shown as a basic logical verifier) have universality and can be used in various items, and the ticket element verifier and the ticket service verifier (shown as a proposed ticket verifier) are related to the contents of the ticket service and need specific service design.

The four types of checkers described above are described separately below in conjunction with fig. 6.

1. Basic data checker

The basic data verifier defines all basic verification functions, and the specific content is shown in table 1 below, where BaseFeildValidator (basic field verifier) is an abstract class for implementing idatavaalidator (a data verification interface shown in fig. 6), and defines basic verification modules, including a pre-verification module, a verification module name, and verification logic.

TABLE 1

2. Logical operation checker

The logic operation checker defines the operation rule required by the logic, such as: "and", "or", "not", and the like. This type of checker, unlike other checkers, includes one or more sub-checkers that define the logical relationship of a sub-checker without the presence of a pre-checker. The specific function of the logic operation checker is shown in table 2:

TABLE 2

3. Check device for ticket surface elements

The check device for ticket elements also belongs to a basic field check device, which comprises simple business related logic and is mainly used for checking whether each item of content of the ticket is completely recorded, whether the content accords with basic rules and the like, and a table 3 shows the main functions of the check device for ticket elements:

TABLE 3

4. Bill service checker

And the bill service checker is used for checking information closely related to the bill service and ensuring that the service can be handled. Taking the proposed payment-for-delivery service as an example, other services such as proposed collection, proposed payment-for-delivery, proposed collection and the like also belong to the scope of the present invention, and the specific verification function of the bill service verifier is shown in the following table 4:

TABLE 4

(III) checking auxiliary module

The verification auxiliary module contains class definitions which are not logically related and are required by verification, and specifically comprises the following steps: checking an interface, checking item name characteristics and checking result types, wherein:

the check interface is an empty interface which does not contain any method, the data type to be checked needs to realize the interface, and any data type realizing the interface can obtain the check function expanded by the data check engine and the function of the check device;

the verification item name characteristics are used for distinguishing various certificates of the same service, mark certificate names and need to be marked on the definition of classes or attributes, and the specific contents of the verification item name characteristics are shown in table 5:

TABLE 5

And after the check operation is finished through the checker, returning a check result. The checking result is a data structure for storing a checking report, and comprises the detailed reasons that whether the checking is passed or not and the checking is not passed, and the type reloads logical operations such as AND, OR, NOT and the like and splicing of text information. And for the AND operation, whether the verification is successful or not needs to be subjected to the AND operation, and if the result is failed, the description information of the object causing the failure is recorded. For the or operation, the check success or failure needs to be performed with the or operation, and if the result fails, all the description words are spliced. For non-operation, the result is inverted, and if failure occurs, the anti-sense sentence originally described is returned. When information is spliced, characters can be added to the description of the current object, and the state bit of the result is not changed.

The exemplary system provided by the embodiment of the invention can simply and quickly realize the verification of data and the generation of reports, and has the following specific advantages:

when the service is newly added, the code amount is written less, the development workload is reduced, and the project propulsion can be accelerated;

when the code is modified, the code is modified at one position and takes effect globally, so that the asynchronous modification of the content can be avoided;

and a reflection mechanism is adopted to replace a common method calling mode, so that code coupling between data verification logic and a service process is reduced, and code upgrading is facilitated.

The verification result is stored by using a uniform data structure, the verification result is conveniently formatted and displayed to business personnel, and the user experience is improved.

Based on similar inventive concepts, the embodiment of the present invention further provides a service data verification method, which is preferably applicable to the service data verification apparatus 1 described above.

Fig. 7 is a flowchart of the service data checking method, and as shown in fig. 7, the method includes:

step 701, obtaining each ticket face element of the service data to be verified in the information system, wherein the ticket face element is generated according to the service data to be verified.

Step 702, determining each ticket element and a corresponding checker based on the preset association relationship between the ticket elements and the checkers, so that the checkers perform a checking operation on the corresponding ticket elements based on the affiliated program codes.

Step 703, receiving the verification result of each verifier, and generating a verification report according to the verification result of each verifier according to a predetermined rule, where the verification report includes: each ticket element and corresponding verification result.

Specifically, the check results of each checker may be spliced according to a predetermined check logic rule and a splicing rule to generate a check report of the to-be-checked service data, where the check logic rule includes: each checker checks the logical rule of the and, or, not of the result.

The check method comprises the steps of obtaining each ticket element of the business data to be checked in the information system, determining each ticket element and the corresponding checker based on the association relationship between the ticket element and the checker, enabling the checker to perform check operation on the corresponding ticket element based on the affiliated program code, then receiving check results of the checkers, generating check reports according to the check results of the checkers according to preset rules, and simply and quickly checking the business data by presetting the checkers.

In actual operation, the checker may be set up as follows: setting the verification logic of each ticket face element based on historical service data and a verification rule; setting a corresponding checker according to each ticket element and the corresponding checking logic, wherein the checker comprises the following types: the system comprises a basic data checker, a logic operation checker, a ticket face element checker and a ticket service checker. The types of the checker may be referred to the description in the above embodiments.

For the specific execution process of the above steps, reference may be made to the description in the above system embodiment, and details are not described here.

The present embodiment also provides an electronic device, which may be a desktop computer, a tablet computer, a mobile terminal, and the like, but is not limited thereto. In this embodiment, the electronic device may be implemented with reference to the above method embodiment and the embodiment of the service data checking apparatus/system, and the contents thereof are incorporated herein, and repeated descriptions are omitted.

Fig. 8 is a schematic block diagram of a system configuration of an electronic apparatus 600 according to an embodiment of the present invention. As shown in fig. 8, the electronic device 600 may include a central processor 100 and a memory 140; the memory 140 is coupled to the central processor 100. Notably, this diagram is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.

In one embodiment, the service data checking function may be integrated into the central processor 100. The central processor 100 may be configured to control as follows:

As can be seen from the above description, in the electronic device provided in the embodiment of the present application, each ticket element of the service data to be verified in the information system is obtained, and based on the association relationship between the ticket element and the verifier, each ticket element and the corresponding verifier are determined, so that the verifier performs verification operation on the corresponding ticket element based on the affiliated program code, then receives the verification result of each verifier, and generates a verification report according to the verification result of each verifier according to a predetermined rule.

In another embodiment, the service data verification apparatus/system may be configured separately from the central processor 100, for example, the service data verification apparatus/system may be configured as a chip connected to the central processor 100, and the service data verification function is realized by the control of the central processor.

As shown in fig. 8, the electronic device 600 may further include: communication module 110, input unit 120, audio processing unit 130, display 160, power supply 170. It is noted that the electronic device 600 does not necessarily include all of the components shown in FIG. 8; furthermore, the electronic device 600 may also comprise components not shown in fig. 8, which may be referred to in the prior art.

As shown in fig. 8, the central processor 100, sometimes referred to as a controller or operational control, may include a microprocessor or other processor device and/or logic device, the central processor 100 receiving input and controlling the operation of the various components of the electronic device 600.

The memory 140 may be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 100 may execute the program stored in the memory 140 to realize information storage or processing, etc.

The input unit 120 provides input to the cpu 100. The input unit 120 is, for example, a key or a touch input device. The power supply 170 is used to provide power to the electronic device 600. The display 160 is used to display an object to be displayed, such as an image or a character. The display may be, for example, an LCD display, but is not limited thereto.

The memory 140 may be a solid state memory such as Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 140 may also be some other type of device. Memory 140 includes buffer memory 141 (sometimes referred to as a buffer). The memory 140 may include an application/function storage section 142, and the application/function storage section 142 is used to store application programs and function programs or a flow for executing the operation of the electronic device 600 by the central processing unit 100.

The memory 140 may also include a data store 143, the data store 143 for storing data, such as contacts, digital data, pictures, sounds, and/or any other data used by the electronic device. The driver storage portion 144 of the memory 140 may include various drivers of the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging application, address book application, etc.).

The communication module 110 is a transmitter/receiver 110 that transmits and receives signals via an antenna 111. The communication module (transmitter/receiver) 110 is coupled to the central processor 100 to provide an input signal and receive an output signal, which may be the same as in the case of a conventional mobile communication terminal.

Based on different communication technologies, a plurality of communication modules 110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 110 is also coupled to a speaker 131 and a microphone 132 via an audio processor 130 to provide audio output via the speaker 131 and receive audio input from the microphone 132 to implement general telecommunications functions. Audio processor 130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, an audio processor 130 is also coupled to the central processor 100, so that recording on the local can be enabled through a microphone 132, and so that sound stored on the local can be played through a speaker 131.

The embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps of the service data verification method.

In summary, the service data verification scheme provided by the embodiment of the present invention can simplify the workload of user development, improve the definition of the project code, separate the service logic from the data verification, facilitate maintenance and upgrade, and simultaneously, the verification report can clearly return all verification results, thereby providing better experience for the user.

The preferred embodiments of the present invention have been described above with reference to the accompanying drawings. The many features and advantages of the embodiments are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the embodiments which fall within the true spirit and scope thereof. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the embodiments of the invention to the exact construction and operation illustrated and described, and accordingly, all suitable modifications and equivalents may be resorted to, falling within the scope thereof.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A service data verification method is characterized by comprising the following steps:

2. The method of claim 1, wherein the checker is configured by:

3. The method of claim 1, wherein generating a verification report according to the verification result of each verifier according to a predetermined rule comprises:

splicing the check results of each checker according to a preset check logic rule and a splicing rule to generate a check report of the service data to be checked, wherein the check logic rule comprises: each checker checks the logical rule of the and, or, not of the result.

4. A service data verification apparatus, characterized in that the apparatus comprises:

5. The apparatus of claim 4, further comprising: a checker setting unit for setting a checker,

the checker setting unit includes:

6. The apparatus according to claim 4, wherein the verification report generating unit is specifically configured to:

7. A system for verifying business data, the system comprising: the service data verification device and at least one verifier according to any one of claims 4 to 6, wherein the verifier is configured to perform a verification operation on the ticket elements acquired by the service data verification device based on the program code.

8. The system of claim 7, wherein the verifier comprises:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method according to any of claims 1 to 3 are implemented when the processor executes the program.

10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 3.