Data audit processing method, device and equipment based on general audit model

Abstract

The present invention relates to big data technology, and provides a data audit processing method, device, equipment and medium based on a general audit model, which first obtains the data to be audited and the audit form configuration table, adds the audit form to the audit form configuration table, generates the audit form code according to the audit form, and then sequentially configures the current audit form module table, the current audit form field table and the current audit personnel table, stores the data to be audited in the audit form detail table corresponding to the audit form, updates the audit form detail table, and finally sends the audit form detail table to the target audit module corresponding to the current audit form module table. It realizes the rapid configuration of the audit form detail table that can store the data to be audited based on the general field table, and automatically completes the configuration of the current audit form module table, the current audit form field table and the current audit personnel table, without creating a storage table with the same structure according to the data to be audited, avoiding the generation of wide tables and improving the efficiency of data storage.

Description

Technical Field

[0001] The present invention relates to the technical field of data storage of big data, and in particular to a data audit processing method, device, computer equipment and storage medium based on a general audit model. Background Art

[0002] At present, most audit systems are coupled with the caller's business system. For example, material audit, credit card approval and review are all based on the audit system based on business logic.

[0003] Moreover, the diversity of existing audit content poses great challenges to the database storage model. The content that each business actually needs to audit and display varies greatly. It is not easy to store it using the entity-relationship structure of the database, which can easily lead to the "wide table" phenomenon and low storage efficiency. Summary of the invention

[0004] The embodiments of the present invention provide a data audit processing method, apparatus, computer equipment and storage medium based on a universal audit model, aiming to solve the problem in the prior art that an existing audit platform and a business system of a caller are coupled together, an existing database storage model of the audit platform cannot meet the storage of various types of audit data, and storing data in the existing database storage model is prone to wide tables and low storage efficiency in the storage results due to the multiple types of audit data.

[0005] In a first aspect, an embodiment of the present invention provides a data audit processing method based on a general audit model, which includes:

[0006] In response to a data audit instruction, obtaining the to-be-audited data and the audit form configuration table corresponding to the data audit instruction, adding the audit form to the audit form configuration table, and generating the audit form code according to the audit form;

[0007] According to the fields included in the data to be reviewed and the pre-stored field table, the field ID of each field in the data to be reviewed is obtained and saved in the initial review form field table to obtain the current review form field table;

[0008] Determine the target audit module of the data to be audited according to the field ID of each field in the data to be audited and the classification type corresponding to each field ID, store the target audit module corresponding to the data to be audited into the initial audit module table, and obtain the current audit module table;

[0009] Obtain the auditor information corresponding to each target audit module in the current audit single module table, store the auditor information corresponding to each target audit module in the initial auditor table, and obtain the current auditor table;

[0010] The data to be audited is stored in the audit form detail table corresponding to the audit form according to the field ID of each field, so as to update the audit form detail table;

[0011] Obtaining important fields from the audit form detail table according to a preset important field extraction strategy to update the audit form; and

[0012] The audit form details list is sent to the receiving end corresponding to each target audit module in the current audit form module list.

[0013] In a second aspect, an embodiment of the present invention provides a data audit processing device based on a general audit model, comprising:

[0014] A first configuration unit is used to respond to a data audit instruction, obtain the to-be-audited data and the audit form configuration table corresponding to the data audit instruction, add the audit form to the audit form configuration table, and generate the audit form code according to the audit form;

[0015] The second configuration unit is used to obtain the field ID of each field in the data to be reviewed and save it to the initial review single field table according to the fields included in the data to be reviewed and the pre-stored field table, so as to obtain the current review single field table;

[0016] A third configuration unit is used to determine the target audit module of the data to be audited according to the field ID of each field in the data to be audited and the classification type corresponding to each field ID, store the target audit module corresponding to the data to be audited into the initial audit module table, and obtain the current audit module table;

[0017] The fourth configuration unit is used to obtain the auditor information corresponding to each target audit module in the current audit single module table, store the auditor information corresponding to each target audit module into the initial auditor table, and obtain the current auditor table;

[0018] A data storage unit, used for storing the data to be audited in the audit form detail table corresponding to the audit form according to the field ID of each field, so as to update the audit form detail table;

[0019] An audit form updating unit, used to obtain important fields from the audit form detail table according to a preset important field extraction strategy to update the audit form; and

[0020] The data sending unit is used to send the audit form detail list to the receiving end corresponding to each target audit module in the current audit form module table.

[0021] In the third aspect, an embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the data audit processing method based on the general audit model described in the first aspect is implemented.

[0022] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor executes the data audit processing method based on the general audit model described in the first aspect above.

[0023] The embodiment of the present invention provides a data audit processing method, device, computer equipment and storage medium based on a general audit model, first obtaining the data to be audited and the audit form configuration table, adding the audit form to the audit form configuration table, generating the audit form code according to the audit form, then sequentially configuring the current audit form module table, the current audit form field table and the current auditor table, storing the data to be audited in the audit form detail table corresponding to the audit form to update the audit form detail table, and finally sending the audit form detail table to the target audit module corresponding to the current audit form module table. It realizes the rapid configuration of the audit form detail table that can store the data to be audited based on the general field table, and automatically completes the configuration of the current audit form module table, the current audit form field table and the current auditor table, without the need to create a storage table with the same structure according to the data to be audited, avoiding the generation of wide tables and improving the efficiency of data storage. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

[0025] Figure 1 A schematic diagram of an application scenario of a data audit processing method based on a general audit model provided by an embodiment of the present invention;

[0026] Figure 2 A schematic diagram of a flow chart of a data audit processing method based on a general audit model provided by an embodiment of the present invention;

[0027] Figure 3 A schematic block diagram of a data audit processing device based on a general audit model provided by an embodiment of the present invention;

[0028] Figure 4 A schematic block diagram of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0029] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0030] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0031] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0032] It should be further understood that the term "and / or" used in the present description and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0033] See also Figure 1 and Figure 2 , Figure 1 A schematic diagram of an application scenario of a data audit processing method based on a general audit model provided by an embodiment of the present invention; Figure 2 A flow chart of a data audit processing method based on a general audit model provided in an embodiment of the present invention is provided. The data audit processing method based on a general audit model is applied in a server and is executed by application software installed in the server.

[0034] like Figure 2 As shown, the method includes steps S101 to S107.

[0035] S101. In response to a data audit instruction, obtain the to-be-audited data and the audit form configuration table corresponding to the data audit instruction, add an audit form to the audit form configuration table, and generate an audit form code according to the audit form.

[0036] In this embodiment, the technical solution is described with the server as the execution subject. When the upload end has uploaded the data to be reviewed to the server for review, it is necessary to add a new review form to the review form configuration table stored locally on the server, and assign a review code to the review form. At this time, the data to be reviewed is not directly stored in the review form configuration table, but the relevant information of the review form is based on the pre-stored field table, review form field table, and review form module table. After the field query and module query, various configuration information is obtained, thereby completing the configuration information of the review form.

[0037] Among them, a field table is pre-stored in the server, which can be understood as a field pool. The reason for setting this field table is that when different uploaders upload audit data to the server, the field names of the audit data will not be exactly the same on each uploader. This requires the field table in the server to be used as a field pool that collects various field names and summarizes the records, and a unique field ID is assigned to each field name. In this way, when the audit form field table is obtained by filtering the target field in the field table, rapid screening and accurate acquisition of the target field can be achieved. In addition, the field table can serve as a general audit model to quickly generate a detailed list of audit forms to be reviewed later.

[0038] In one embodiment, the step S101 of adding an audit form to the audit form configuration table and generating an audit form code according to the audit form includes:

[0039] The audit form configuration code and the audit form creation time corresponding to the data to be audited are obtained, and the audit form is created and the audit form code is generated according to the audit form configuration code and the audit form creation time.

[0040] In this embodiment, when creating corresponding audit form information (such as audit form information composed of audit form name, creation time, creator, modification time, modifier, etc.) in the local audit form configuration table of the server according to the data to be audited and generating the audit form code, the audit form configuration code (the audit form configuration code can be understood as an audit code automatically assigned when the audit form is created, such as 01 represents the audit form configuration code corresponding to the first type of audit form, 02 represents the audit form configuration code corresponding to the second type of audit form, and the first type of audit form refers to the audit form corresponding to the audit data uploaded by the first type upload end, and the second type of audit form refers to the audit form corresponding to the audit data uploaded by the second type upload end) and the audit form creation time are obtained first, and then the audit form configuration code and the audit form creation time are combined to obtain the audit form code, and finally the audit form is created with the audit form code as the key information. Among them, the audit form configuration code refers to a code automatically assigned to the audit form corresponding to the data to be audited. It can be seen that the audit form can be quickly configured and the audit form code can be generated in this way.

[0041] S102: According to the fields included in the data to be reviewed and the pre-stored field table, the field ID of each field in the data to be reviewed is obtained and saved in the initial review single field table to obtain the current review single field table.

[0042] In this embodiment, since the field table is a field pool, and each field in the field table is assigned a unique field ID, when the fields included in the data to be reviewed are known, after each field in the data to be reviewed is retrieved from the field table to obtain the corresponding field ID, all specific field names in the data to be reviewed can be replaced from the field name form to the field ID form, that is, a one-to-one mapping relationship can be established between all specific field names in the data to be reviewed and the corresponding field ID in the field table. Among them, the current review form field table stores the review form configuration code mentioned in step S101 to ensure that a mapping relationship is established with the review form configuration table.

[0043] In one embodiment, the step S102 includes:

[0044] The field ID corresponding to the same field in the field table of each field in the data to be audited is obtained and saved in the initial audit form field table to obtain the current audit form field table; wherein the audit form configuration code of the audit form is stored in the current audit form field table.

[0045] In this embodiment, the purpose of configuring this current audit form field table is to convert the field names of the data to be audited into corresponding field IDs for storage instead of storing them with actual names, so that no matter what field set of data to be audited is uploaded to the server, the audit form field table can be quickly configured based on the field table query. Instead of creating a new data table of the same format in the server for each type of data to be audited uploaded, an audit form field table is quickly configured based on the field ID in the field table, so that the audit form detailed table can be quickly obtained.

[0046] S103, determining the target audit module of the data to be audited according to the field ID of each field in the data to be audited and the classification type corresponding to each field ID, storing the target audit module corresponding to the data to be audited into the initial audit module table, and obtaining the current audit module table.

[0047] In this embodiment, in addition to assigning a unique field ID to each field in the field table, the classification type (also understood as the field classification type) to which each field belongs can also be pre-configured. For example, if the data to be audited includes fields such as user address, user contact information, and user name, these fields are all used to represent user information, so they can all belong to the field classification type of user information. After determining the classification type to which all fields in the field data to be audited belong, it can be queried in the field table to obtain which classification type of field will be sent to which target audit module for audit. Therefore, after determining the target audit modules corresponding to each field of the data to be audited based on the field table, the target audit modules corresponding to the data to be audited are stored in the initial audit module table to obtain the current audit single module table. Among them, the current audit single module table stores the audit single configuration code mentioned in step S101 to ensure that a mapping relationship is established with the audit single configuration table.

[0048] In one embodiment, determining the target audit module of the data to be audited according to the field ID of each field in the data to be audited and the classification type corresponding to each field ID includes:

[0049] Obtain the field ID of each field in the data to be reviewed, and obtain the preset classification type corresponding to each field ID in the field table, determine the classification type corresponding to each field ID in the data to be reviewed according to the classification type to which each field ID belongs in the field table, and determine the target review module according to each classification type in the data to be reviewed.

[0050] In this embodiment, there are three target audit modules corresponding to all fields of the data to be audited, namely target audit module A, target audit module B and target audit module C. At this time, the first field range of the data to be audited that needs to be sent to the target audit module A for audit can be obtained, the second field range of the data to be audited that needs to be sent to the target audit module B for audit can be obtained, and the third field range of the data to be audited that needs to be sent to the target audit module C for audit can be obtained. The data information corresponding to the first field range, the second field range and the third field range are respectively stored in the current audit form module table, thereby realizing the configuration of the audit form module table.

[0051] S104, obtaining the auditor information corresponding to each target audit module in the current audit single module table, storing the auditor information corresponding to each target audit module in the initial audit personnel table, and obtaining the current audit personnel table.

[0052] In this embodiment, after completing the configuration of the audit form module table, it is necessary to determine the auditor information corresponding to each target audit module. At this time, it is only necessary to store the auditor information corresponding to each target audit module into the initial auditor table to obtain the current auditor table, thereby realizing the configuration of the auditor table. Among them, the current auditor table stores the audit form configuration code mentioned in step S101 to ensure that a mapping relationship is established with the audit form configuration table.

[0053] For example, continuing to refer to the above example, the first auditor information corresponding to the target audit module A can be saved in the auditor table, the second auditor information corresponding to the target audit module B can be saved, and the third auditor information corresponding to the target audit module C can be saved. Based on the auditor table, it is possible to query and obtain information about which target audit module data in the data to be audited is specifically assigned to which specific auditor.

[0054] S105 , storing the data to be audited in the audit form detail table corresponding to the audit form according to the field ID of each field, so as to update the audit form detail table.

[0055] In this embodiment, after completing the configuration of the above-mentioned various tables, it is necessary to store the specific data of the data to be reviewed in the review form detail table. Since there may be data such as pictures in the data to be reviewed, directly filling it into the review form detail table will result in failure to fill it normally. This is because the review form detail table can only store data in text form. Therefore, in order to achieve normal filling of the data in the review form detail table, it is necessary to first determine whether there is picture data in the data to be reviewed. If there is picture data, it should be identified as text data and then filled into the review form detail table.

[0056] Furthermore, since the actual field names of the fields in the data to be reviewed have been converted into field IDs, when creating the initial review form details table, the field IDs corresponding to the fields in the data to be reviewed can be used as the field names in the initial review form details table, without the need to use the actual field names as the field names in the initial review form details table. The review form details table stores the review form configuration code mentioned in step S101 to ensure that a mapping relationship is established with the review form configuration table.

[0057] In one embodiment, step S105 includes:

[0058] If it is determined that the field value corresponding to the field ID in the data to be reviewed is picture data, the text data corresponding to the picture data is obtained through OCR recognition model recognition to update the data to be reviewed.

[0059] In this embodiment, OCR (Optical Character Recognition) recognition technology is used to implement image text recognition using general text recognition technology. After the text is recognized, some automatic configuration functions are combined to complete a partial automatic review function.

[0060] S106. Obtain important fields from the audit form detail table according to a preset important field extraction strategy to update the audit form.

[0061] In this embodiment, the important field extraction strategy can also be pre-identified in the field table. In the field table, some important fields can be classified as important field types. Generally, there are field IDs in the audit form detail table that belong to the important field type classification. Then, these target field IDs can be screened out to obtain an audit form that is simplified relative to the audit form detail table. Viewing the audit form is also a preview of the audit form detail table. Among them, the updated audit form also stores the audit form configuration code mentioned in step S101 to ensure that a mapping relationship is established with the audit form configuration table.

[0062] S107, sending the audit form details list to the receiving end corresponding to each target audit module in the current audit form module table.

[0063] In this embodiment, after loading the audit form details of the specific data to be audited, the current audit form module table that has been configured before can be obtained first, and the target audit module included therein can be obtained, and then the audit form details can be sent to the receiving end corresponding to each target audit module for audit. It can be seen that the audit form details are distributed to different target audit modules in a targeted manner for separate audit, and there is no need to conduct audit in one place, which improves the efficiency of data audit.

[0064] In one embodiment, before step S107, the method further includes:

[0065] If it is determined that there is sensitive data corresponding to the sensitive fields in the audit form details list, each sensitive data is encrypted to update the audit form details list.

[0066] In this embodiment, in order to improve data security, when distributing the audit form details to each target module for audit, it is also necessary to detect whether there is sensitive data therein. Generally, the sensitive fields corresponding to sensitive data can be marked in advance through annotations, so that once the specific positions of these annotations are identified and located, the fields with the closest interval can be located as sensitive fields. At this time, encrypting the sensitive fields can improve data security.

[0067] In one embodiment, step S107 includes:

[0068] Obtain the pre-stored national secret SM4 encryption model, encrypt each sensitive data based on the national secret SM4 encryption model to obtain encrypted sensitive data, and replace the corresponding encrypted data with the encrypted sensitive data to update the audit form details table.

[0069] In this embodiment, the sensitive data corresponding to the sensitive fields can be encrypted using the national cryptographic algorithm SM4, wherein the national cryptographic algorithm SM4 (i.e., the national cryptographic SM4 encryption model) is a 32-round iterative unbalanced Feistel structured block encryption algorithm, and its key length and block length are both 128 bits. After the encryption of the sensitive data corresponding to the sensitive fields in the audit form detail list is completed, a more secure audit form detail list can be obtained.

[0070] The embodiment of the present application can acquire and process data in the relevant servers based on artificial intelligence technology. Artificial Intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0071] AI basic technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. AI software technologies mainly include computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0072] The method realizes the rapid configuration of the audit form detail table that can store the data to be audited based on the general field table, and automatically completes the configuration of the current audit form module table, the current audit form field table and the current auditor table. There is no need to create a storage table with the same structure according to the data to be audited, which avoids the generation of wide tables and improves the efficiency of data storage.

[0073] The embodiment of the present invention further provides a data audit processing device based on a general audit model, which is used to execute any embodiment of the data audit processing method based on a general audit model. Figure 3 , Figure 3 It is a schematic block diagram of a data audit processing device 100 based on a general audit model provided in an embodiment of the present invention.

[0074] Among them, Figure 3As shown, the data audit processing device 100 based on the general audit model includes a first configuration unit 101, a second configuration unit 102, a third configuration unit 103, a fourth configuration unit 104, a data storage unit 105, an audit form updating unit 106 and a data sending unit 107.

[0075] The first configuration unit 101 is used to respond to a data audit instruction, obtain the to-be-audited data and the audit form configuration table corresponding to the data audit instruction, add an audit form to the audit form configuration table, and generate an audit form code according to the audit form.

[0076] In this embodiment, the technical solution is described with the server as the execution subject. When the upload end has uploaded the data to be reviewed to the server for review, it is necessary to add a new review form to the review form configuration table stored locally on the server, and assign a review code to the review form. At this time, the data to be reviewed is not directly stored in the review form configuration table, but the relevant information of the review form is based on the pre-stored field table, review form field table, and review form module table. After the field query and module query, various configuration information is obtained, thereby completing the configuration information of the review form.

[0077] Among them, a field table is pre-stored in the server, which can be understood as a field pool. The reason for setting this field table is that when different uploaders upload audit data to the server, the field names of the audit data will not be exactly the same on each uploader. This requires the field table in the server to be used as a field pool that collects various field names and summarizes the records, and a unique field ID is assigned to each field name. In this way, when the audit form field table is obtained by filtering the target field in the field table, rapid screening and accurate acquisition of the target field can be achieved. In addition, the field table can serve as a general audit model to quickly generate a detailed list of audit forms to be reviewed later.

[0078] In one embodiment, the first configuration unit 101 is specifically used for:

[0079] The audit form configuration code and the audit form creation time corresponding to the data to be audited are obtained, and the audit form is created and the audit form code is generated according to the audit form configuration code and the audit form creation time.

[0080] In this embodiment, when creating corresponding audit form information (such as audit form information composed of audit form name, creation time, creator, modification time, modifier, etc.) in the local audit form configuration table of the server according to the data to be audited and generating the audit form code, the audit form configuration code (the audit form configuration code can be understood as an audit code automatically assigned when the audit form is created, such as 01 represents the audit form configuration code corresponding to the first type of audit form, 02 represents the audit form configuration code corresponding to the second type of audit form, and the first type of audit form refers to the audit form corresponding to the audit data uploaded by the first type upload end, and the second type of audit form refers to the audit form corresponding to the audit data uploaded by the second type upload end) and the audit form creation time are obtained first, and then the audit form configuration code and the audit form creation time are combined to obtain the audit form code, and finally the audit form is created with the audit form code as the key information. Among them, the audit form configuration code refers to a code automatically assigned to the audit form corresponding to the data to be audited. It can be seen that the audit form can be quickly configured and the audit form code can be generated in this way.

[0081] The second configuration unit 102 is used to obtain the field ID of each field in the data to be reviewed and save it to the initial review single field table according to the fields included in the data to be reviewed and the pre-stored field table, so as to obtain the current review single field table.

[0082] In this embodiment, since the field table is a field pool, and each field in the field table is assigned a unique field ID, when the fields included in the data to be audited are known, after each field in the data to be audited is retrieved from the field table to obtain the corresponding field ID, all specific field names in the data to be audited can be replaced from the field name form to the field ID form, that is, a one-to-one mapping relationship can be established between all specific field names in the data to be audited and the corresponding field ID in the field table. Among them, the current audit form field table stores the audit form configuration code mentioned in the first configuration unit 101 to ensure that a mapping relationship is established with the audit form configuration table.

[0083] In one embodiment, the second configuration unit 102 is specifically configured to:

[0084] The field ID corresponding to the same field in the field table of each field in the data to be audited is obtained and saved in the initial audit form field table to obtain the current audit form field table; wherein the audit form configuration code of the audit form is stored in the current audit form field table.

[0085] In this embodiment, the purpose of configuring this current audit form field table is to convert the field names of the data to be audited into corresponding field IDs for storage instead of storing them with actual names, so that no matter what field set of data to be audited is uploaded to the server, the audit form field table can be quickly configured based on the field table query. Instead of creating a new data table of the same format in the server for each type of data to be audited uploaded, an audit form field table is quickly configured based on the field ID in the field table, so that the audit form detailed table can be quickly obtained.

[0086] The third configuration unit 103 is used to determine the target audit module of the data to be audited according to the field ID of each field in the data to be audited and the classification type corresponding to each field ID, store the target audit module corresponding to the data to be audited into the initial audit module table, and obtain the current audit module table.

[0087] In this embodiment, in addition to assigning a unique field ID to each field in the field table, the classification type (also understood as the field classification type) to which each field belongs can also be pre-configured. For example, if the data to be audited includes fields such as user address, user contact information, and user name, these fields are all used to represent user information, so they can all belong to the field classification type of user information. After determining the classification type to which all fields in the field data to be audited belong, it can be queried in the field table to obtain which classification type of field will be sent to which target audit module for audit. Therefore, after determining the target audit modules corresponding to each field of the data to be audited based on the field table, the target audit modules corresponding to the data to be audited are stored in the initial audit module table to obtain the current audit single module table. Among them, the current audit single module table stores the audit single configuration code mentioned in the first configuration unit 101 to ensure that a mapping relationship is established with the audit single configuration table.

[0088] In one embodiment, the third configuration unit 103 is specifically used to:

[0089] Obtain the field ID of each field in the data to be reviewed, and obtain the preset classification type corresponding to each field ID in the field table, determine the classification type corresponding to each field ID in the data to be reviewed according to the classification type to which each field ID belongs in the field table, and determine the target review module according to each classification type in the data to be reviewed.

[0090] In this embodiment, there are three target audit modules corresponding to all fields of the data to be audited, namely target audit module A, target audit module B and target audit module C. At this time, the first field range of the data to be audited that needs to be sent to the target audit module A for audit can be obtained, the second field range of the data to be audited that needs to be sent to the target audit module B for audit can be obtained, and the third field range of the data to be audited that needs to be sent to the target audit module C for audit can be obtained. The data information corresponding to the first field range, the second field range and the third field range are respectively stored in the current audit form module table, thereby realizing the configuration of the audit form module table.

[0091] The fourth configuration unit 104 is used to obtain the auditor information corresponding to each target audit module in the current audit single module table, store the auditor information corresponding to each target audit module into the initial auditor table, and obtain the current auditor table.

[0092] In this embodiment, after completing the configuration of the audit form module table, it is necessary to determine the auditor information corresponding to each target audit module. At this time, it is only necessary to store the auditor information corresponding to each target audit module into the initial auditor table to obtain the current auditor table, thereby realizing the configuration of the auditor table. The current auditor table stores the audit form configuration code mentioned in the first configuration unit 101 to ensure that a mapping relationship is established with the audit form configuration table.

[0093] For example, continuing to refer to the above example, the first auditor information corresponding to the target audit module A can be saved in the auditor table, the second auditor information corresponding to the target audit module B can be saved, and the third auditor information corresponding to the target audit module C can be saved. Based on the auditor table, it is possible to query and obtain information about which target audit module data in the data to be audited is specifically assigned to which specific auditor.

[0094] The data storage unit 105 is used to store the data to be reviewed in the review form detail table corresponding to the review form according to the field ID of each field, so as to update the review form detail table.

[0095] In this embodiment, after completing the configuration of the above-mentioned various tables, it is necessary to store the specific data of the data to be reviewed in the review form detail table. Since there may be data such as pictures in the data to be reviewed, directly filling it into the review form detail table will result in failure to fill it normally. This is because the review form detail table can only store data in text form. Therefore, in order to achieve normal filling of the data in the review form detail table, it is necessary to first determine whether there is picture data in the data to be reviewed. If there is picture data, it should be identified as text data and then filled into the review form detail table.

[0096] Furthermore, since the actual field names of the fields in the data to be reviewed have been converted into field IDs, when creating the initial review form details table, the field IDs corresponding to the fields in the data to be reviewed can be used as the field names in the initial review form details table, without the need to use the actual field names as the field names in the initial review form details table. The review form details table stores the review form configuration code mentioned in the first configuration unit 101 to ensure that a mapping relationship is established with the review form configuration table.

[0097] In one embodiment, the data storage unit 105 is specifically used for:

[0098] If it is determined that the field value corresponding to the field ID in the data to be reviewed is picture data, the text data corresponding to the picture data is obtained through OCR recognition model recognition to update the data to be reviewed.

[0099] In this embodiment, OCR (Optical Character Recognition) recognition technology is used to implement image text recognition using general text recognition technology. After the text is recognized, some automatic configuration functions are combined to complete a partial automatic review function.

[0100] The audit form updating unit 106 is used to obtain important fields from the audit form detail table according to a preset important field extraction strategy to update the audit form.

[0101] In this embodiment, the important field extraction strategy can also be pre-identified in the field table. In the field table, some important fields can be classified as important field types. Generally, there are field IDs in the audit form detail table that belong to the important field type classification. Then, these target field IDs can be screened out to obtain an audit form that is simplified relative to the audit form detail table. Viewing the audit form is also a preview of the audit form detail table. Among them, the updated audit form also stores the audit form configuration code mentioned in the first configuration unit 101 to ensure that a mapping relationship is established with the audit form configuration table.

[0102] The data sending unit 107 is used to send the audit form detail list to the receiving end corresponding to each target audit module in the current audit form module table.

[0103] In this embodiment, after loading the audit form details of the specific data to be audited, the current audit form module table that has been configured before can be obtained first, and the target audit module included therein can be obtained, and then the audit form details can be sent to the receiving end corresponding to each target audit module for audit. It can be seen that the audit form details are distributed to different target audit modules in a targeted manner for separate audit, and there is no need to conduct audit in one place, which improves the efficiency of data audit.

[0104] In one embodiment, the data audit processing device 100 based on the general audit model further includes:

[0105] The sensitive data encryption unit is used to encrypt each sensitive data if it is determined that there is sensitive data corresponding to the sensitive field in the audit form detail list, so as to update the audit form detail list.

[0106] In this embodiment, in order to improve data security, when distributing the audit form details to each target module for audit, it is also necessary to detect whether there is sensitive data therein. Generally, the sensitive fields corresponding to sensitive data can be marked in advance through annotations, so that once the specific positions of these annotations are identified and located, the fields with the closest interval can be located as sensitive fields. At this time, encrypting the sensitive fields can improve data security.

[0107] In one embodiment, the sensitive data encryption unit is specifically used to:

[0108] Obtain the pre-stored national secret SM4 encryption model, encrypt each sensitive data based on the national secret SM4 encryption model to obtain encrypted sensitive data, and replace the corresponding encrypted data with the encrypted sensitive data to update the audit form details table.

[0109] In this embodiment, the sensitive data corresponding to the sensitive fields can be encrypted using the national cryptographic algorithm SM4, wherein the national cryptographic algorithm SM4 (i.e., the national cryptographic SM4 encryption model) is a 32-round iterative unbalanced Feistel structured block encryption algorithm, and its key length and block length are both 128 bits. After the encryption of the sensitive data corresponding to the sensitive fields in the audit form detail list is completed, a more secure audit form detail list can be obtained.

[0110] The device realizes the rapid configuration of the audit form detail table that can store the data to be audited based on the general field table, and automatically completes the configuration of the current audit form module table, the current audit form field table and the current auditor table. There is no need to create a storage table with the same structure according to the data to be audited, which avoids the generation of wide tables and improves the efficiency of data storage.

[0111] The above-mentioned data audit processing device based on the general audit model can be implemented in the form of a computer program. The computer program can be used in Figure 4 Runs on the computer device shown.

[0112] See also Figure 4 , Figure 45 is a schematic block diagram of a computer device provided in an embodiment of the present invention. The computer device 500 is a server or a server cluster. The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0113] See also Figure 4 The computer device 500 includes a processor 502 , a memory and a network interface 505 connected via a device bus 501 , wherein the memory may include a storage medium 503 and an internal memory 504 .

[0114] The storage medium 503 can store an operating device 5031 and a computer program 5032. When the computer program 5032 is executed, the processor 502 can execute a data audit processing method based on a general audit model.

[0115] The processor 502 is used to provide computing and control capabilities to support the operation of the entire computer device 500 .

[0116] The internal memory 504 provides an environment for the operation of the computer program 5032 in the storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can execute a data audit processing method based on a general audit model.

[0117] The network interface 505 is used for network communication, such as providing data information transmission, etc. Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present invention, and does not constitute a limitation on the computer device 500 to which the solution of the present invention is applied. The specific computer device 500 may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0118] The processor 502 is used to run the computer program 5032 stored in the memory to implement the data audit processing method based on the general audit model disclosed in the embodiment of the present invention.

[0119] Those skilled in the art will understand that Figure 4The embodiments of the computer device shown in the figure do not constitute a limitation on the specific composition of the computer device. In other embodiments, the computer device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, in some embodiments, the computer device may only include a memory and a processor. In such embodiments, the structure and function of the memory and the processor are the same as those of the embodiment of the present invention. Figure 4 The embodiments shown are consistent and will not be described again here.

[0120] It should be understood that in the embodiment of the present invention, the processor 502 may be a central processing unit (CPU), and the processor 502 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0121] In another embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the data audit processing method based on the general audit model disclosed in the embodiment of the present invention is implemented.

[0122] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the above-described equipment, devices and units can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. Those of ordinary skill in the art can appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to the function. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0123] In the several embodiments provided by the present invention, it should be understood that the disclosed equipment, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. Units with the same function may also be combined into one unit. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices or units, or may be electrical, mechanical or other forms of connection.

[0124] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present invention.

[0125] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0126] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a background server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), disk or CD-ROM and other media that can store program codes.

[0127] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A data audit processing method based on a general audit model, characterized in that: include: In response to a data audit instruction, obtaining the to-be-audited data and the audit form configuration table corresponding to the data audit instruction, adding the audit form to the audit form configuration table, and generating the audit form code according to the audit form; According to the fields included in the data to be reviewed and the pre-stored field table, the field ID of each field in the data to be reviewed is obtained and saved in the initial review form field table to obtain the current review form field table; Determine the target audit module of the data to be audited according to the field ID of each field in the data to be audited and the classification type corresponding to each field ID, store the target audit module corresponding to the data to be audited into the initial audit module table, and obtain the current audit module table; Obtain the auditor information corresponding to each target audit module in the current audit single module table, store the auditor information corresponding to each target audit module in the initial auditor table, and obtain the current auditor table; The data to be audited is stored in the audit form detail table corresponding to the audit form according to the field ID of each field, so as to update the audit form detail table; Obtaining important fields from the audit form detail table according to a preset important field extraction strategy to update the audit form; as well as The audit form details list is sent to the receiving end corresponding to each target audit module in the current audit form module table.

2. The data audit processing method based on the general audit model according to claim 1 is characterized in that: Adding an audit form in the audit form configuration table and generating an audit form code according to the audit form include: The audit form configuration code and the audit form creation time corresponding to the data to be audited are obtained, and the audit form is created and the audit form code is generated according to the audit form configuration code and the audit form creation time.

3. The data audit processing method based on the general audit model according to claim 1 is characterized in that: The field ID of each field in the data to be reviewed is obtained and saved in the initial review form field table to obtain the current review form field table, including: The field ID corresponding to the same field in the field table of each field in the data to be audited is obtained and saved in the initial audit form field table to obtain the current audit form field table; wherein the audit form configuration code of the audit form is stored in the current audit form field table.

4. The data audit processing method based on the general audit model according to claim 1 is characterized in that: The step of determining a target audit module of the data to be audited according to the field ID of each field in the data to be audited and the classification type corresponding to each field ID includes: Obtain the field ID of each field in the data to be reviewed, and obtain the preset classification type corresponding to each field ID in the field table, determine the classification type corresponding to each field ID in the data to be reviewed according to the classification type to which each field ID belongs in the field table, and determine the target review module according to each classification type in the data to be reviewed.

5. The data audit processing method based on the general audit model according to claim 1 is characterized in that: The step of storing the data to be audited in the audit form detail table corresponding to the audit form according to the field ID of each field to update the audit form detail table includes: If it is determined that the field value corresponding to the field ID in the data to be reviewed is picture data, the text data corresponding to the picture data is obtained through OCR recognition model recognition to update the data to be reviewed.

6. The data audit processing method based on the general audit model according to claim 1 is characterized in that: Before sending the audit form detail list to the receiving end corresponding to each target audit module in the current audit form module table, the method further includes: If it is determined that there is sensitive data corresponding to the sensitive fields in the audit form details list, each sensitive data is encrypted to update the audit form details list.

7. The data audit processing method based on the general audit model according to claim 6 is characterized in that: The sensitive data is encrypted to update the audit list, including: Obtain the pre-stored national secret SM4 encryption model, encrypt each sensitive data based on the national secret SM4 encryption model to obtain encrypted sensitive data, and replace the corresponding encrypted data with the encrypted sensitive data to update the audit form details table.

8. A data audit processing device based on a general audit model, characterized in that: include: A first configuration unit is used to respond to a data audit instruction, obtain the to-be-audited data and the audit form configuration table corresponding to the data audit instruction, add the audit form to the audit form configuration table, and generate the audit form code according to the audit form; The second configuration unit is used to obtain the field ID of each field in the data to be reviewed and save it to the initial review single field table according to the fields included in the data to be reviewed and the pre-stored field table, so as to obtain the current review single field table; A third configuration unit is used to determine the target audit module of the data to be audited according to the field ID of each field in the data to be audited and the classification type corresponding to each field ID, store the target audit module corresponding to the data to be audited into the initial audit module table, and obtain the current audit module table; A fourth configuration unit is used to obtain the auditor information corresponding to each target audit module in the current audit single module table, store the auditor information corresponding to each target audit module in the initial audit personnel table, and obtain the current audit personnel table; A data storage unit, used for storing the data to be audited in the audit form detail table corresponding to the audit form according to the field ID of each field, so as to update the audit form detail table; An audit form updating unit, used to obtain important fields from the audit form detail table according to a preset important field extraction strategy to update the audit form; as well as The data sending unit is used to send the audit form detail list to the receiving end corresponding to each target audit module in the current audit form module table.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the data audit processing method based on the general audit model as described in any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, enables the processor to perform the data audit processing method based on a general audit model as described in any one of claims 1 to 7.

Images