A data auditing method and related apparatus

Abstract

Embodiments of the present application provide a data auditing method and related device, which are used to realize asynchronous auditing of machine auditing and manual auditing, and prevent business data loss in the process of machine auditing. The method comprises the following steps: storing target business data in a relational database management system by using a message queue; calling the target business data stored in the relational database management system by using the message queue according to a preset frequency; generating a business auditing table according to the target business data, generating an identity ID of the business auditing table, and returning the ID to a business side, wherein the business auditing table is used to describe the target business data and a business auditing strategy corresponding to the target business data; detecting the target business data based on the business auditing strategy to obtain a label result set, wherein the label result set comprises a plurality of label data; and determining an auditing result of the target business data according to the label result set.

Description

Technical Field

[0001] This application relates to the field of computer networks, and more particularly to a data auditing method and related apparatus. Background Technology

[0002] To maintain the compliance and legality of internet information, platforms need to review data from numerous internet products targeting business users (B2B) or individual users (C2C). However, due to the rapid development of the internet and the dramatic increase in internet users, the amount of data requiring review is enormous. If all reviews were conducted by human reviewers, it would require a huge workforce and a lengthy rule training period, resulting in high costs and excessively long review times, impacting operational efficiency and increasing operating costs.

[0003] Currently, the usual practice is to push the review data of different businesses to the corresponding review platform, and then the reviewers will pick up the review forms for review. At the same time, some businesses are also connected to the synchronous machine review logic for filtering.

[0004] Although synchronous access to machine review logic has been added for review, the synchronous access to machine review logic usually requires the machine to pass the review first before the machine review result is pushed to the review platform. Therefore, the review data of different businesses may be lost during the machine review process or the review time may be too long, thus affecting the business response. Summary of the Invention

[0005] This application provides a data auditing method and related apparatus to achieve asynchronous auditing by machine and manual review, thereby preventing the loss of business data during the machine auditing process.

[0006] In view of this, this application provides a data auditing method, comprising: storing target business data in a relational database management system using a message queue; calling the target business data stored in the relational database management system using the message queue at a preset frequency; generating a business auditing table based on the target business data, and generating an identity identifier ID for the business auditing table and returning the identity identifier ID of the business auditing table to the business side, wherein the business auditing table is used to describe the target business data and the business auditing strategy corresponding to the target business data; detecting the target business data based on the business auditing strategy to obtain a tag result set, wherein the tag result set includes multiple tag data; and determining the auditing result of the target business data based on the tag result set.

[0007] This application also provides a data auditing method, comprising: storing target business data in a relational database management system using a message queue; calling the target business data stored in the relational database management system using the message queue at a preset frequency; displaying a business auditing table and its identifier ID on a display interface, wherein the business auditing table is generated based on the target business data and describes the target business data and the corresponding business auditing strategy, and the identifier ID of the business auditing table is returned to the business side; and displaying the auditing result corresponding to the target business data on the display interface, wherein the auditing result is determined based on the tag result set corresponding to the target business data, the tag result set being obtained by detecting the target business data based on the business auditing strategy, and the tag result set including multiple tag data.

[0008] Another aspect of this application provides a data auditing device, including: a storage module for storing target business data in a relational database management system using a message queue;

[0009] The calling module is used to call the target business data stored in the relational database management system using a message queue at a preset frequency;

[0010] The processing module is used to generate a business audit table based on the target business data, generate an identity ID for the business audit table, and return the identity ID of the business audit table to the business side. The business audit table is used to describe the target business data and the business audit strategy corresponding to the target business data. Based on the business audit strategy, the target business data is detected to obtain a tag result set, wherein the tag result set includes multiple tag data.

[0011] The determination module is used to determine the audit result of the target business data based on the tag result set.

[0012] In one possible design, in another implementation of another aspect of the embodiments of this application, the processing module is specifically used to set the detection duration of the target business data and set the status of the business review form corresponding to the target business data to be unavailable; within the detection duration, the target business data is detected based on the business review strategy to obtain multiple tag data; after the detection duration expires, the multiple tag data are aggregated to generate the tag result set.

[0013] In one possible design, in another implementation of another aspect of the embodiments of this application, the processing module is specifically used to set the status of the business review form corresponding to the target business data to be unclaimable.

[0014] Based on this business audit strategy, multiple tag data were obtained by detecting the target business data;

[0015] When the number of multiple tag data equals the number of business review strategies, the multiple tag data are aggregated to generate the tag result set.

[0016] In one possible design, in another implementation of another aspect of the embodiments of this application, the tag data includes tag identity ID, tag name, display mode of the business review form corresponding to the tag, review operation corresponding to the tag, and tag priority.

[0017] In one possible design, in another implementation of another aspect of the embodiments of this application, the display mode of the business review form corresponding to the label includes no highlighting, highlighting the border of the business review form, and requiring a screenshot;

[0018] The review actions corresponding to this label include: no review, pass, reject, human review, and suspension;

[0019] The priority of this tag is determined by its numerical value; the higher the value, the higher the priority level, or the lower the value, the higher the priority level.

[0020] In one possible design, in another implementation of another aspect of the embodiments of this application, the determining module is specifically used to select the highest priority tag data from the tag result set as the tag result corresponding to the target business data; and determine the review result of the target business data based on the tag result.

[0021] In one possible design, in another implementation of another aspect of the embodiments of this application, the determining module is specifically used to determine that the audit result of the target business data is passed if the audit operation indicated by the tag result is passed.

[0022] If the review action indicated by the label result is rejection, then the review result for the target business data is rejection.

[0023] If the review operation indicated by the label result is human review, then the target business data is marked as available for collection.

[0024] If the audit operation indicated by the label result is a no-response, then the label result set of the target business data will be displayed.

[0025] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0026] The processing module is also used to acquire test data; generate a test business audit table based on the test data, which describes the test data and the corresponding test audit strategy; perform testing on the test data according to the test audit strategy to obtain a test tag result set; and update the test audit strategy to the business audit strategy based on the test tag result set.

[0027] In one possible design, in another implementation of another aspect of the embodiments of this application, the processing module is further configured to obtain the hit status of the first review strategy in the business review strategy and information on the business data that hit the first review strategy.

[0028] The device also includes a reporting module for reporting the hit status of the first review strategy and information on the business data that hit the first review strategy.

[0029] In one possible design, in another implementation of another aspect of the embodiments of this application, the processing module is further configured to backtrack the tag result set corresponding to the business data that hits the first review strategy based on the information of the business data that hits the first review strategy.

[0030] This application also provides a computer device, including: a memory, a processor, and a bus system;

[0031] The memory is used to store programs;

[0032] The processor is used to execute programs in memory, and the processor is used to execute the methods mentioned above according to the instructions in the program code;

[0033] Bus systems are used to connect memory and processor to enable communication between them.

[0034] Another aspect of this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described above.

[0035] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the above aspects.

[0036] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: The data auditing device generates a business auditing table based on the target business data, then extracts the business auditing table and performs detection based on the business auditing strategy. This ensures that the target business data is pushed to the auditing platform before the audit begins, thus reducing the possibility of business data loss during the auditing process. Simultaneously, by using a message queue and a relational database management system, the target business data can be stably stored, its storage frequency can be controlled, and it can be retried in case of storage failure. This ensures that the data auditing device does not lose data when acquiring the target business data. Furthermore, by linking the target business data with the corresponding business auditing table through an ID number, the idempotency of the auditing request on the business side is guaranteed, and the stability of business data storage is ensured. Attached Figure Description

[0037] Figure 1a This is a schematic diagram of the system architecture in an embodiment of this application;

[0038] Figure 1b This is a flowchart illustrating the data verification method in an embodiment of this application;

[0039] Figure 2 This is a schematic diagram of one embodiment of the data verification method in this application;

[0040] Figure 3 This is a schematic diagram illustrating a business review form in an embodiment of this application;

[0041] Figure 4a This is a schematic diagram of a machine review process in an embodiment of this application;

[0042] Figure 4b This is another schematic diagram of the machine review process in the embodiments of this application;

[0043] Figure 5 This is a schematic diagram illustrating the tag data in an embodiment of this application;

[0044] Figure 6a This is a schematic diagram illustrating the hit count of the first review strategy in this application embodiment;

[0045] Figure 6b This is a schematic diagram of the request volume for the first review strategy in this application embodiment;

[0046] Figure 6c This is a schematic diagram illustrating the execution volume of the first review strategy in an embodiment of this application;

[0047] Figure 7 This is a schematic diagram of one embodiment of the testing process prior to data review in this application.

[0048] Figure 8 This is a schematic diagram of one embodiment of the data verification device in this application.

[0049] Figure 9 This is a schematic diagram of another embodiment of the data verification device in this application;

[0050] Figure 10 This is a schematic diagram of another embodiment of the data verification device in this application;

[0051] Figure 11 This is a schematic diagram of another embodiment of the data verification device in this application. Detailed Implementation

[0052] This application provides a data auditing method and related apparatus to achieve asynchronous auditing by machine and manual review, thereby preventing the loss of business data during the machine auditing process.

[0053] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “corresponding to,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0054] To maintain the compliance and legality of internet information, platforms need to review data from various internet products targeting enterprise users (B2B) or individual users (C2C). Due to the rapid development of the internet and the dramatic increase in internet users, the amount of data requiring review is enormous. If all reviews were conducted by human reviewers, it would require a huge manpower pool and a lengthy rule training period, resulting in high costs and excessively long review times, impacting operational efficiency and increasing operating costs. Currently, the typical approach is to push review data from different business units to their respective review platforms, where reviewers collect review forms and conduct reviews. Simultaneously, some business units are integrated with synchronous machine review logic for filtering. While this synchronous integration with machine review logic is beneficial, it typically requires the machine to pass review first before pushing the results to the review platform. This can lead to data loss during the machine review process or excessively long review times, impacting business responsiveness.

[0055] To address the aforementioned issues, this application provides a data auditing method and related apparatus, comprising: a data auditing apparatus storing target business data in a relational database management system using a message queue; retrieving the target business data stored in the relational database management system using the message queue at a preset frequency; the data auditing apparatus generating a business auditing table based on the target business data, generating an identity identifier ID for the business auditing table, and returning the identity identifier ID of the business auditing table to the business side, the business auditing table describing the target business data and the corresponding business auditing strategy; the data auditing apparatus detecting the target business data based on the business auditing strategy to obtain a tag result set, wherein the tag result set includes multiple tag data; and the data auditing apparatus determining the auditing result of the target business data based on the tag result set.

[0056] The technical solution provided in this application can be applied to, for example... Figure 1aThe system architecture shown includes terminal devices and a data verification device. Both B-end and C-end clients are deployed on the terminal devices. These clients can run on the terminal devices via a browser, a standalone application (APP), or a mini-program; the specific presentation format of the client is not limited here. The data verification device in this application can be a server including a display module, or a terminal device connected to the server corresponding to the client (in which case the data verification operation is performed on the terminal device). When the data verification device is a server, the server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The terminal devices involved in this application can be smartphones, tablets, laptops, PDAs, personal computers, smart TVs, smartwatches, in-vehicle devices, wearable devices, etc., but are not limited to these. Terminal devices and servers can be connected directly or indirectly via wired or wireless communication, and this application does not impose any restrictions on this. The number of servers and terminal devices is also not limited.

[0057] based on Figure 1a The system architecture shown in this application, and the implementation process of the technical solution provided in this application, can be as follows: Figure 1b As shown:

[0058] Business data is pushed to the review platform through a synchronous review process (i.e., ... Figure 1a Data auditing devices in, or those operating in, such as Figure 1aThis is an application of a data auditing device (described below using the data auditing device as an example); the data auditing device then generates a corresponding business auditing form based on the business data, marks the business auditing form as unavailable (here, unavailable status indicates that the auditing form cannot be manually retrieved), and sets callback conditions (here, callback conditions indicate the conditions for aggregating the tag data corresponding to the business data); after the data auditing device completes the above preparations, it calls the business auditing form and checks the business data corresponding to the business auditing form based on the business auditing strategy (that is, the business data passes through a series of business auditing strategies); during the detection process, for each business auditing strategy the business data passes through, it obtains a tag data from the tag system; then, after the callback conditions are met, the tag data of the business data is aggregated to obtain a tag result set; finally, the audit result of the business data is determined based on the tag result set. If the audit result indicates pass or rejection, the data auditing device marks the audit status in the business auditing form corresponding to the business data as pass or rejection; if the audit result indicates that manual review is required, the data auditing device marks the audit status in the business auditing form corresponding to the business data as "manual review".

[0059] For ease of understanding, the following is an explanation of some of the terms used in this application:

[0060] Idempotency: This means that the result of executing any number of requests is the same as the result of executing a single request. For an interface, this means that no matter how many times it is called, the final result will be the same.

[0061] Based on the above introduction, the data verification method in this application will be described below. Please refer to [link / reference]. Figure 2 One embodiment of the data verification method in this application includes:

[0062] 201. The data auditing device uses message queues to store target business data in a relational database management system.

[0063] In this embodiment, the data auditing device receives the target business data and stores it in a database, such as a relational database management system (MySQL), via a message queue (mq). The message queue and the database need to ensure stable storage of the target business data, controllable storage frequency, and the ability to retry in case of storage failure. This ensures that the data auditing device does not lose data when retrieving the target business data.

[0064] 202. The data auditing device uses a message queue to call the target business data stored in the relational database management system at a preset frequency.

[0065] After storing the target business data, the data auditing device will retrieve the target business data again when it needs to audit the data. In this embodiment, to avoid a large number of requests to access the database, the data auditing device can retrieve the target business data from the relational database management system in the form of a message queue at a preset frequency.

[0066] 203. The data auditing device generates a business auditing table based on the target business data, and generates an identity identifier ID for the business auditing table and returns the identity identifier ID of the business auditing table to the business side. The business auditing table is used to describe the target business data and the business auditing strategy corresponding to the target business data.

[0067] After storing the target business data, the data auditing device retrieves the target business data again and generates a corresponding business audit table based on it. This business audit table describes the target business data and the corresponding business audit strategy. In one possible implementation, the business audit table is presented on the display interface of the data auditing device in the following format: Figure 3 As shown, the business review form includes at least the business review form's ID, submission time, review status, review target, review time, review operation, corresponding review strategy ID, penalty operation, malicious type, evidence type, evidence tag, and evidence description. Figure 3As shown, the ID of this business review form is "123456"; the submission time is "2021-12-01 12:02:22"; the review status is "Passed"; the review target is "Zhang San"; the review time is "2021-12-01 13:02:22"; the review operation is "Passed"; the penalty operation is "None"; the malicious type is "None"; the evidence type is "None"; the review strategy ID is "2001112"; and the tag result ID is "422125854". This business review form describes the target business data using evidence type, evidence description, and evidence tag. Additionally, the business review form can also include explanations of the order number and supplier information, which are not detailed here. In this embodiment, in order to ensure the idempotency of the requests on the business side (i.e., to ensure the consistency of the calls to the target business data), when the data auditing device generates the business auditing table based on the target business data, it can generate an identity identifier (ID) for the business auditing table and feed the ID back to the corresponding terminal device on the business side.

[0068] In this embodiment, both the business review table and the target business data can be stored in MySQL. This allows for retrieval of the business review table and the target business data based on fields, thus facilitating the retrieval and retrieval of the business review table and the target business data.

[0069] 204. The data auditing device detects the target business data based on the business auditing strategy and obtains a tag result set, wherein the tag result set includes multiple tag data.

[0070] The data review device detects the target business data based on the corresponding business review strategy, obtaining multiple corresponding tag data. After the review time for the target business data expires or the business review strategy for the target business data completes its detection, the data review device aggregates these multiple tag data to generate a tag result set. Specifically, the data review device can employ the following possible implementation methods when detecting the target business data based on the business review strategy:

[0071] In one possible implementation, after generating the business review form, the data review device sets the form's status to "unavailable" and sets its review duration. The device then retrieves the form and checks if the review duration has expired. If expired, the device aggregates all tag data corresponding to the business review form to generate a tag result set. It is understood that the review duration can be set individually for the target business data or uniformly for all business data. That is, the data review device can generate a review duration specific to the target business data, or it can generate a duration applicable to all business data after statistical analysis. Specific limitations are not specified here.

[0072] Based on this scheme, an exemplary process for the data auditing device to detect the target business data and obtain a tag result set based on the business auditing strategy can be as follows: Figure 4a As shown:

[0073] The data review device acquires the business review form during the polling cycle and checks whether the review time of the business review form has expired. If it has expired, it collects all tag data corresponding to the business data to generate a tag result set. If it has not expired, it skips the business review form and checks the review time of the business review form again in the next polling cycle. After generating the tag result set, it determines whether manual review is required based on the tag result set. If manual review is not required, it determines the review result of the business review form as either passed or rejected and ends the review. If manual review is required, it sets the review status of the business review form to the "available for collection" status (i.e., it can be manually reviewed) and then ends the review.

[0074] In another possible implementation, after generating the business review form, the data review device sets the status of the business review form to "unclaimable." Then, the data review device retrieves the business review form and detects the tag data corresponding to the target business data described in the form. When the number of tag data is equal to the number of business review strategies corresponding to the business review form, the data review device aggregates all tag data corresponding to the business review form to generate the tag result. Based on this scheme, an exemplary process for the data review device to detect the target business data based on the business review strategy and obtain a tag result set can be as follows: Figure 4b As shown:

[0075] The data review device acquires the business review form during the polling cycle and checks whether the number of tag data in the business review form is equal to the number of business strategies. If they are equal, it collects all tag data corresponding to the business data to generate a tag result set. If they are less than the number of tag data, it skips the business review form and checks the review duration of the business review form again in the next polling cycle. After generating the tag result set, it determines whether manual review is required based on the tag result set. If manual review is not required, it determines whether the review result of the business review form is passed or rejected and ends the review. If manual review is required, it sets the review status of the business review form to the "available" status (i.e., it can be manually reviewed) and then ends the review.

[0076] It is understood that in this embodiment, the data review device can review the target business data simultaneously through multiple review strategies, or sequentially through them; the specific approach is not limited here. However, reviewing the target business data simultaneously through multiple review strategies can reduce the review time, thereby improving the responsiveness to business needs.

[0077] In this embodiment, the source and detection method of the business audit strategy can vary. Specifically, the business audit strategy can access the data audit device via remote procedure call (RPC); it can access the data audit device via function call; or it can access the data audit device via application programming interface (API). There is a corresponding relationship between the business audit strategy and the tag data; that is, each business audit strategy is configured with corresponding tag data. In one possible implementation, the tag data can be displayed on the display interface as follows: Figure 5 As shown, the tag data includes at least the tag ID, tag name, display mode of the business review table corresponding to the tag, review operation corresponding to the tag, and tag priority.

[0078] The following is an example illustrating tag data:

[0079] The display modes for the business review form corresponding to this label include no highlighting, highlighted borders on the business review form, and requiring a screenshot, etc. This application does not limit the specific format. (The remaining text appears to be incomplete and requires further context.) Figure 5 In the example scheme shown, the display mode is represented by data, where 0 indicates no highlighting, 1 indicates highlighting the border of the business review table, 2 indicates a screenshot is required, and 3 indicates a screenshot is required with the business review table border highlighted.

[0080] The review operations corresponding to this tag data include no-show, pass, reject, human review, and suspension, etc., and the specific form is not limited in this application. It is understood that "no-show" indicates that this review operation is not output as the final review result, but only displays the tag data when the business data passes each review strategy. "Pass" indicates that no malicious or illegal behavior was found during the review process, thus passing the review, and the business data can be published or made public. "Reject" indicates that malicious or illegal behavior was found during the review process, thus failing the review, and the business data is not allowed to be published or made public. "Human review" indicates that the business data has behaviors that cannot be confirmed by machine review and requires manual review. "Suspended" indicates that the business data is currently under machine review and cannot be retrieved by manual review at this time. Figure 5 In the example scheme shown, the review action is represented by data, where 0 indicates no review, 1 indicates approval, 2 indicates rejection, 3 indicates human review, and 4 indicates suspension.

[0081] The priority of the tags indicated in this tag data can be distinguished using numerical values ​​or other evaluation methods, such as alphabetical ratings, etc. The specific method is not limited here. Figure 5 In the method shown, the priority of the tag is distinguished by a numerical value. The numerical value corresponding to the priority can be a number from 1 to 100. Then, it is defined that the larger the numerical value, the higher the priority. That is, when the priority value is 99 and 59, the tag with a value of 99 has a higher priority than the tag with a value of 59. It can be understood that when the priority is distinguished by numerical value, the definition of priority can be determined by the user in advance. It can be defined as higher priority for higher numerical values, or lower priority for lower numerical values. The specific situation is not limited here.

[0082] 205. The data review device determines the review result of the target business data based on the tag result set.

[0083] In this embodiment, after aggregating the tag result set, the data review device selects the tag data with the highest priority from the tag result set as the tag result corresponding to the target business data; and determines the review result of the target business data based on the tag result. For example, the tag result set of the target business data aggregated by the data review device includes tag data 1, tag data 2, and tag data 3, wherein the priority of tag data 1 is 99, the priority of tag data 2 is 89, and the priority of tag data 3 is 59, and the higher the value of the priority indicator, the higher the priority. Then, the data review device can select tag data 1 as the tag result of the target business data, and finally uses the review operation indicated by tag data 1 as the review result of the target business data.

[0084] The specific method by which the data verification device determines the verification result based on the label result can be as follows:

[0085] If the review operation indicated by the label result is approved, then the review result of the target business data is approved;

[0086] If the review action indicated by the label result is rejection, then the review result for the target business data is rejection.

[0087] If the review operation indicated by the label result is human review, then the target business data is marked as available for collection.

[0088] If the audit operation indicated by the label result is a no-response, then the label result set of the target business data will be displayed.

[0089] Based on the above scheme, in this embodiment, the data auditing device can also monitor and report the hit status of the target business data against the business auditing strategy in real time. That is, the data auditing device obtains the hit status of the first auditing strategy and information on the business data that hit the first auditing strategy; then, the data auditing device reports the hit status of the first auditing strategy and information on the business data that hit the first auditing strategy, thereby promptly identifying the status of the auditing strategy and business data, and increasing the accuracy of business data auditing. In this embodiment, the hit status of the first auditing strategy may include the request volume of the first auditing strategy, the execution volume of the first auditing strategy, and the hit rate of the first auditing strategy. In one possible implementation, the hit status of the first auditing strategy can be expressed as follows: Figures 6a to 6c The chart style shown is used for display. For example... Figure 6a The hit rate of the first review strategy within a certain time period, such as Figure 6b The number of requests for this first review strategy within a certain time period, such as Figure 6c This represents the execution volume of the first audit strategy within a certain time period. The business data that triggers this first audit strategy also needs to be reported. In this way, the data auditing device can trace back the tag result set corresponding to the business data that triggers the first audit strategy based on the information of that business data, thereby verifying the audit results of the business data.

[0090] In this embodiment, before the data auditing device performs data auditing, it can also test the business auditing strategy. Specifically, this can be done as follows: Figure 7 As shown:

[0091] 701. The data auditing device acquires test business data.

[0092] In this embodiment, the data auditing device receives the test business data and stores it in a database, such as a relational database management system (MySQL), via a message queue (mq). The message queue and the database need to ensure stable storage of the test business data, controllable storage frequency, and the ability to retry in case of storage failure. This ensures that the data auditing device does not lose data when retrieving the test business data.

[0093] 702. The data auditing device generates a test business auditing table based on the test business data. The test business auditing table is used to describe the test business data and the test auditing strategy corresponding to the test business data.

[0094] After storing the test service data, the data review device retrieves the test service data again and generates a corresponding test service review table based on it. This test service review table describes the test service data and the corresponding test review strategy. In one possible implementation, the test service review table is presented on the display interface of the data review device in the following format: Figure 3 As shown, the test business review form includes at least the ID of the test business review form, the submission time of the test business review form, the review status of the test business review form, the review object of the test business review form, the review time of the test business review form, the review operation of the test business review form, the review policy ID corresponding to the test business review form, the penalty operation of the test business review form, the malicious type of the test business review form, the evidence type of the test business review form, the evidence label of the test business review form, and the evidence description of the test business review form. Figure 3As shown, the ID of the test business review form is "123456"; the submission time of the test business review form is "2021-12-1 12:02:22"; the review status of the test business review form is "passed"; the review object of the test business review form is "Zhang San"; the review time of the test business review form is "2021-12-1 13:02:22"; the review operation of the test business review form is "passed"; the penalty operation of the test business review form is "none"; the malicious type of the test business review form is "none"; the evidence type of the test business review form is "none"; the review strategy ID corresponding to the test business review form is "2001112"; and the tag result ID corresponding to the review strategy is "422125854"; the test business review form uses evidence type, evidence description, and evidence tag to describe the test business data. Meanwhile, the test service review form can also include descriptions of the order number and supplier information, which will not be detailed here. In this embodiment, to avoid a large number of requests to access the database, the data review device can use a message queue to retrieve the test service data from the database within a preset frequency. Furthermore, to ensure the idempotency of requests on the service side (i.e., to ensure the consistency of test service data retrieval), when generating the test service review form based on the test service data, the data review device can generate an identity identifier (ID) for the test service review form and feed this ID back to the corresponding terminal device on the service side.

[0095] In this embodiment, both the test business audit table and the test business data can be stored in MySQL. This allows for retrieval of the test business audit table and the test business data based on fields, thus facilitating the retrieval and retrieval of the test business audit table and the test business data.

[0096] 703. The data auditing device detects the test business data based on the test auditing strategy and obtains a tag result set, wherein the tag result set includes multiple tag data.

[0097] The data review device detects the test business data based on the corresponding test review strategy, obtaining multiple corresponding tag data. After the review time for the test business data expires or the test review strategy for the test business data completes its detection, the data review device aggregates these multiple tag data to generate the tag result set. Specifically, the data review device can employ the following possible implementation methods when detecting the test business data based on the test review strategy:

[0098] In one possible implementation, after generating the test business review form, the data review device sets the status of the test business review form to "unavailable" and sets the review duration. Then, the data review device retrieves the test business review form and checks if the review duration has expired. If the review duration has expired, the data review device aggregates all tag data corresponding to the test business review form to generate the tag result set. It is understood that the review duration of the test business review form can be set individually for the test business data or uniformly for all business data. That is, the data review device can generate a review duration specific to the test business data; or it can generate a review duration applicable to all business data after statistical analysis. Specific limitations are not specified here.

[0099] Based on this scheme, an exemplary process for the data auditing device to detect the target business data and obtain a tag result set based on the business auditing strategy can be as follows: Figure 4a As shown:

[0100] The data review device acquires the business review form during the polling cycle and checks whether the review time of the business review form has expired. If it has expired, it collects all tag data corresponding to the business data to generate a tag result set. If it has not expired, it skips the business review form and checks the review time of the business review form again in the next polling cycle. After generating the tag result set, it determines whether manual review is required based on the tag result set. If manual review is not required, it determines the review result of the business review form as either passed or rejected and ends the review. If manual review is required, it sets the review status of the business review form to the "available for collection" status (i.e., it can be manually reviewed) and then ends the review.

[0101] In another possible implementation, after the data auditing device generates the test business audit form, it sets the status of the test business audit form to unavailable. Then, the data auditing device obtains the test business audit form and detects the tag data corresponding to the test business data described in the test business audit form. When the number of tag data is the same as the number of test audit strategies corresponding to the test business audit form, the data auditing device aggregates all the tag data corresponding to the test business audit form to generate the tag result.

[0102] Based on this scheme, an exemplary process for the data auditing device to detect the target business data and obtain a tag result set based on the business auditing strategy can be as follows: Figure 4b As shown:

[0103] The data review device acquires the business review form during the polling cycle and checks whether the number of tag data in the business review form is equal to the number of business strategies. If they are equal, it collects all tag data corresponding to the business data to generate a tag result set. If they are less than the number of tag data, it skips the business review form and checks the review duration of the business review form again in the next polling cycle. After generating the tag result set, it determines whether manual review is required based on the tag result set. If manual review is not required, it determines whether the review result of the business review form is passed or rejected and ends the review. If manual review is required, it sets the review status of the business review form to the "available" status (i.e., it can be manually reviewed) and then ends the review.

[0104] It is understood that in this embodiment, the data review device can review the test business data simultaneously through multiple review strategies, or sequentially through them; the specific approach is not limited here. However, reviewing the test business data simultaneously through multiple review strategies can reduce the review time, thereby improving the responsiveness to business needs.

[0105] In this embodiment, the source and detection method of the test audit strategy can vary. Specifically, the test audit strategy can access the data audit device via remote procedure call (RPC); it can access the data audit device via function call; or it can access the data audit device via application programming interface (API). There is a corresponding relationship between the test audit strategy and the tag data, that is, each test audit strategy is configured with corresponding tag data. In one possible implementation, the tag data is displayed on the interface as shown in Figure 4, wherein the tag data includes at least the tag ID, tag name, display mode of the test business audit table corresponding to the tag, audit operation corresponding to the tag, and tag priority.

[0106] The following is an example illustrating tag data:

[0107] The display modes for the test business review form corresponding to this label include no highlighting, highlighted borders on the test business review form, and requiring screenshots, etc. This application does not limit the specific format. Figure 5 In the example scheme shown, the display mode is represented by data, where 0 indicates no highlighting, 1 indicates highlighting the border of the business review table, 2 indicates a screenshot is required, and 3 indicates a screenshot is required with the business review table border highlighted.

[0108] The review operations corresponding to this tag data include no-show, pass, reject, human review, and suspension, etc., and the specific form is not limited in this application. It is understood that "no-show" indicates that this review operation is not output as the final review result, but only displays the tag data when the business data passes each review strategy. "Pass" indicates that no malicious or illegal behavior was found during the review process, thus passing the review, and the business data can be published or made public. "Reject" indicates that malicious or illegal behavior was found during the review process, thus failing the review, and the business data is not allowed to be published or made public. "Human review" indicates that the business data has behaviors that cannot be confirmed by machine review and requires manual review. "Suspended" indicates that the business data is currently under machine review and cannot be retrieved by manual review at this time. Figure 5 In the example scheme shown, the review action is represented by data, where 0 indicates no review, 1 indicates approval, 2 indicates rejection, 3 indicates human review, and 4 indicates suspension.

[0109] The priority of the tags indicated in this tag data can be distinguished using numerical values ​​or other evaluation methods, such as alphabetical ratings, etc. The specific method is not limited here. Figure 5 In the method shown, the priority of the tag is distinguished by a numerical value. The numerical value corresponding to the priority can be a number from 1 to 100. Then, it is defined that the larger the numerical value, the higher the priority. That is, when the priority value is 99 and 59, the tag with a value of 99 has a higher priority than the tag with a value of 59. It can be understood that when the priority is distinguished by numerical value, the definition of priority can be determined by the user in advance. It can be defined as higher priority for higher numerical values, or lower priority for lower numerical values. The specific situation is not limited here.

[0110] Understandably, during the testing process, the review operation corresponding to this tag data can only be marked as a no-go.

[0111] 704. The data review device updates the test review strategy to the business review strategy based on the tag result set.

[0112] In this embodiment, after aggregating the tag result set, the data auditing device modifies its test auditing strategy or adds a new business auditing strategy based on the tag result set to obtain the business auditing strategy of the data auditing device when performing data auditing.

[0113] In this embodiment, the accuracy of the audit strategy is determined by performing a no-load test on the test data.

[0114] The data verification device in this application is described in detail below. Please refer to [link / reference]. Figure 8, Figure 8 This is a schematic diagram of one embodiment of the data verification device in this application. The data verification device 20 includes:

[0115] Storage module 801 is used to store target business data in a relational database management system using a message queue;

[0116] The calling module 802 is used to call the target business data stored in the relational database management system using a message queue at a preset frequency;

[0117] The processing module 803 is used to generate a business audit table based on the target business data. The business audit table describes the target business data and the corresponding business audit strategy. Based on the business audit strategy, the target business data is detected to obtain a tag result set, wherein the tag result set includes multiple tag data.

[0118] The determination module 804 is used to determine the audit result of the target business data based on the tag result set.

[0119] This application provides a data auditing device. Using this device, a business audit table can be generated based on target business data, and then the business audit table can be extracted and tested based on a business audit strategy. This ensures that the target business data is pushed to the auditing platform before the audit begins, reducing the possibility of data loss during the audit process. Simultaneously, by using a message queue and a relational database management system, the target business data can be stably stored, its storage frequency can be controlled, and retrying is possible in case of storage failure. This ensures that the data auditing device does not lose data when acquiring the target business data. Furthermore, by linking the target business data with its corresponding business audit table using an ID number, the idempotency of audit requests from the business side is guaranteed, as well as the stability of business data storage.

[0120] Optionally, in the above Figure 8 Based on the corresponding embodiments, in another embodiment of the data verification device 20 provided in this application,

[0121] The processing module 803 is specifically used to set the detection duration of the target business data and set the status of the business review form corresponding to the target business data to be unavailable; within the detection duration, the target business data is detected based on the business review strategy to obtain multiple tag data; after the detection duration expires, the multiple tag data are aggregated to generate the tag result set.

[0122] This application provides a data auditing device. Using this device, the audit duration is used as the audit callback condition for the business audit table, thereby ensuring the integrity of the business audit strategy applied to the target business data and thus guaranteeing the accuracy of the audit results for the target business data.

[0123] Optionally, in the above Figure 8 Based on the corresponding embodiments, in another embodiment of the data verification device 20 provided in this application,

[0124] The processing module 803 is specifically used to set the status of the business audit form corresponding to the target business data to be unavailable for collection.

[0125] Based on this business audit strategy, multiple tag data were obtained by detecting the target business data;

[0126] When the number of multiple tag data equals the number of business review strategies, the multiple tag data are aggregated to generate the tag result set.

[0127] This application provides a data auditing device. Using this device, the quantity of tag data is used as the audit callback condition for the business audit table, thereby ensuring the integrity of the business audit strategy applied to the target business data and thus guaranteeing the accuracy of the audit results for the target business data.

[0128] Optionally, in the above Figure 8 Based on the corresponding embodiments, in another embodiment of the data review device 20 provided in this application, the tag data includes tag identity ID, tag name, display mode of the business review table corresponding to the tag, review operation corresponding to the tag, and tag priority.

[0129] This application provides a data review device. Using this device, a correspondence between review strategies and tag data is established, thereby creating a tag data management system. This allows for a one-to-one mapping between tag data and review strategies when business data passes through the review process, facilitating the display of the review results for that business data.

[0130] Optionally, in the above Figure 8 Based on the corresponding embodiments, in another embodiment of the data review device 20 provided in this application, the display modes of the business review table corresponding to the label include no highlight, business review table border highlight, and screenshot required;

[0131] The review actions corresponding to this label include: no review, pass, reject, human review, and suspension;

[0132] The priority of this tag is determined by its numerical value; the higher the value, the higher the priority level, or the lower the value, the higher the priority level.

[0133] This application provides a data auditing device. Using this device, various indicator information for the tag data are set according to actual conditions, thereby ensuring a one-to-one correspondence between the auditing strategy and the tag data, facilitating the integration of the auditing strategy with the business auditing table.

[0134] Optionally, in the above Figure 8 Based on the corresponding embodiments, in another embodiment of the data verification device 20 provided in this application,

[0135] The determining module 804 is specifically used to select the highest priority tag data from the tag result set as the tag result corresponding to the target business data; and to determine the audit result of the target business data based on the tag result.

[0136] This application provides a data review device. Using this device, the highest-priority tag data is selected from multiple tag data sets as the tag result for the target business data, thereby ensuring the accuracy of the review result for the target business data.

[0137] Optionally, in the above Figure 8 Based on the corresponding embodiments, in another embodiment of the data verification device 20 provided in this application,

[0138] The determination module 804 is specifically used to determine that if the review operation indicated by the label result is passed, then the review result of the target business data is passed.

[0139] If the review action indicated by the label result is rejection, then the review result for the target business data is rejection.

[0140] If the review operation indicated by the label result is human review, then the target business data is marked as available for collection.

[0141] If the audit operation indicated by the label result is a no-response, then the label result set of the target business data will be displayed.

[0142] This application provides a data review device. Using this device, the review operation of the tag result can be associated with the review result of the target business data, thereby indicating various review statuses of the target business data, making it easy for users to understand.

[0143] Optionally, in the above Figure 8 Based on the corresponding embodiments, in another embodiment of the data verification device 20 provided in this application,

[0144] The processing module 803 is also used to acquire test data; generate a test business audit table based on the test data, the test business audit table being used to describe the test data and the test audit strategy corresponding to the test data; perform testing on the test data according to the test audit strategy to obtain a test tag result set; and update the test audit strategy to the business audit strategy based on the test tag result set.

[0145] This application provides a data auditing device. Using this device, a testing process is conducted to verify the business auditing strategy before data auditing, ensuring the accuracy of the business auditing strategy and thus increasing the accuracy of the audit results for the target business data.

[0146] Optionally, in the above Figure 8 Based on the corresponding embodiments, such as Figure 9 As shown, in another embodiment of the data verification device 20 provided in this application,

[0147] The processing module 803 is also used to obtain the hit status of the first audit strategy in the business audit strategy and the information of the business data that hit the first audit strategy;

[0148] The device also includes a reporting module 805, which is used to report the hit status of the first review strategy and information on the business data that hit the first review strategy.

[0149] This application provides a data auditing device. By employing this device, the monitoring and reporting of the success rate of audit strategies and the business data that has successfully implemented the audit strategies are enhanced. This allows for timely understanding and correction of issues with the audit strategies and the business data, thereby ensuring the accuracy of the audit results for the business data.

[0150] Optionally, in the above Figure 8 Based on the corresponding embodiments, in another embodiment of the data verification device 20 provided in this application,

[0151] The processing module 803 is also used to backtrack the tag result set corresponding to the business data that hits the first review strategy based on the information of the business data that hit the first review strategy.

[0152] This application provides a data auditing device. Using this device, the tagged result set of business data is traced back to promptly understand the audit status of the business data, thereby ensuring the accuracy of the audit results.

[0153] The data verification device provided in this application can be used on a server; please refer to [link / reference]. Figure 10 , Figure 10This is a schematic diagram of a server structure provided in an embodiment of this application. The server 300 can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 322 (e.g., one or more processors) and memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) for storing application programs 342 or data 344. The memory 332 and storage media 330 can be temporary or persistent storage. The program stored in the storage media 330 may include one or more modules (not shown in the diagram), each module may include a series of instruction operations on the server. Furthermore, the CPU 322 may be configured to communicate with the storage media 330 and execute the series of instruction operations stored in the storage media 330 on the server 300.

[0154] Server 300 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input / output interfaces 358, and / or one or more operating systems 341, such as Windows Server. TM Mac OS X TM Unix TM Linux TM FreeBSD TM etc.

[0155] The steps performed by the data verification device in the above embodiments can be based on this. Figure 10 The server structure shown.

[0156] The data verification device provided in this application can be used on terminal devices; please refer to [link / reference]. Figure 11 For ease of explanation, only the parts relevant to the embodiments of this application are shown. For specific technical details not disclosed, please refer to the method section of the embodiments of this application. In the embodiments of this application, a smartphone is used as an example for illustration:

[0157] Figure 11 This is a block diagram illustrating a portion of the structure of a smartphone related to the terminal device provided in the embodiments of this application. (Reference) Figure 11 The smartphone includes components such as a radio frequency (RF) circuit 410, a memory 420, an input unit 430, a display unit 440, a sensor 450, an audio circuit 460, a wireless fidelity (WiFi) module 470, a processor 480, and a power supply 490. Those skilled in the art will understand that... Figure 11The smartphone structure shown does not constitute a limitation on smartphones and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0158] The following is combined with Figure 11 A detailed introduction to the various components of a smartphone:

[0159] RF circuit 410 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with processor 480; additionally, it transmits uplink data to the base station. Typically, RF circuit 410 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, etc. Furthermore, RF circuit 410 can also communicate wirelessly with networks and other devices. The aforementioned wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), etc.

[0160] The memory 420 can be used to store software programs and modules. The processor 480 executes various functions and data processing of the smartphone by running the software programs and modules stored in the memory 420. The memory 420 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the smartphone (such as audio data, phonebook, etc.). In addition, the memory 420 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0161] The input unit 430 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the smartphone. Specifically, the input unit 430 may include a touch panel 431 and other input devices 432. The touch panel 431, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 431), and drive the corresponding connected devices according to a pre-set program. Optionally, the touch panel 431 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 480, and can also receive and execute commands sent by the processor 480. In addition, the touch panel 431 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 431, the input unit 430 may also include other input devices 432. Specifically, other input devices 432 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0162] Display unit 440 can be used to display information input by the user or information provided to the user, as well as various menus of the smartphone. Display unit 440 may include display panel 441, optionally configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar form. Further, touch panel 431 may cover display panel 441. When touch panel 431 detects a touch operation on or near it, it transmits the information to processor 480 to determine the type of touch event. Subsequently, processor 480 provides corresponding visual output on display panel 441 based on the type of touch event. Although in Figure 11 In this embodiment, the touch panel 431 and the display panel 441 are two separate components to realize the input and output functions of the smartphone. However, in some embodiments, the touch panel 431 and the display panel 441 can be integrated to realize the input and output functions of the smartphone.

[0163] The smartphone may also include at least one sensor 450, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 441 according to the ambient light level, and the proximity sensor can turn off the display panel 441 and / or the backlight when the smartphone is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the smartphone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the smartphone, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0164] Audio circuit 460, speaker 461, and microphone 462 provide an audio interface between the user and the smartphone. Audio circuit 460 converts received audio data into electrical signals and transmits them to speaker 461, where speaker 461 converts them into sound signals for output. On the other hand, microphone 462 converts collected sound signals into electrical signals, which are received by audio circuit 460, converted into audio data, and then processed by processor 480 before being transmitted via RF circuit 410 to, for example, another smartphone, or the audio data can be output to memory 420 for further processing.

[0165] WiFi is a short-range wireless transmission technology. Smartphones, through their WiFi modules (470), can help users send and receive emails, browse web pages, and access streaming media, providing wireless broadband internet access. Although Figure 11 WiFi module 470 is shown, but it is understood that it is not an essential component of a smartphone and can be omitted as needed without changing the nature of the invention.

[0166] The processor 480 is the control center of the smartphone, connecting various parts of the smartphone through various interfaces and lines. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 420, and by calling data stored in the memory 420, thereby providing overall monitoring of the smartphone. Optionally, the processor 480 may include one or more processing units; optionally, the processor 480 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the aforementioned modem processor may also not be integrated into the processor 480.

[0167] The smartphone also includes a power supply 490 (such as a battery) that supplies power to various components. Optionally, the power supply can be logically connected to the processor 480 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0168] Although not shown, smartphones may also include a camera, Bluetooth module, etc., which will not be described in detail here.

[0169] The steps performed by the data verification device in the above embodiments can be based on this. Figure 11 The terminal device structure is shown.

[0170] This application also provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the methods described in the foregoing embodiments.

[0171] This application also provides a computer program product including a program, which, when run on a computer, causes the computer to perform the methods described in the foregoing embodiments.

[0172] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0173] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0174] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0175] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0176] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, 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. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0177] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A data auditing method, characterized in that, include: Use message queues to store target business data in a relational database management system; The target business data stored in the relational database management system is retrieved using a message queue at a preset frequency. A business audit table is generated based on the target business data, and an identity identifier ID for the business audit table is generated and returned to the business side. The business audit table is used to describe the target business data and the business audit strategy corresponding to the target business data. The method of detecting the target business data based on the business review strategy to obtain a tag result set includes: setting a detection period for the target business data, setting the status of the business review table corresponding to the target business data to an unclaimable state, detecting the target business data based on the business review strategy within the detection period to obtain multiple tag data, and after the detection period expires, aggregating the multiple tag data to generate the tag result set; or, setting the status of the business review table corresponding to the target business data to an unclaimable state, detecting the target business data based on the business review strategy to obtain multiple tag data, and aggregating the multiple tag data to generate the tag result set when the number of multiple tag data is equal to the number of business review strategies. Select the highest priority tag data from the tag result set as the tag result corresponding to the target business data; The review result of the target business data is determined based on the tag result. If the review operation indicated by the tag result is human review, the target business data is marked as available for collection. The available for collection status indicates that it can be reviewed manually. The unavailable for collection status indicates that it cannot be reviewed manually. The human review status indicates that there are behaviors in the business data that cannot be reviewed and confirmed by the machine during the review process and that human review is required.

2. The method according to claim 1, characterized in that, The tag data includes the tag identity ID, tag name, display mode of the business review form corresponding to the tag, review operation corresponding to the tag, and tag priority.

3. The method according to claim 2, characterized in that, The display modes of the business review form corresponding to the label include no highlight, business review form border highlight, and screenshot required; The review operations corresponding to the label also include running without processing, passing, rejecting, and suspending; The priority of the tags is distinguished by numerical values; the higher the value, the higher the priority level, or the lower the value, the higher the priority level.

4. The method according to claim 1, characterized in that, The step of determining the audit result of the target business data based on the tag result further includes: If the review operation indicated by the label result is passed, then the review result of the target business data is passed; If the review operation indicated by the label result is rejection, then the review result of the target business data is rejection; If the audit operation indicated by the tag result is a no-go, then the tag result set of the target business data will be displayed.

5. The method according to claim 1 or 3, characterized in that, Before acquiring the target business data, the method further includes: Obtain test data; A test business audit form is generated based on the test data. The test business audit form is used to describe the test data and the test audit strategy corresponding to the test data. The test data is tested according to the test review strategy to obtain a test tag result set; The test review strategy is updated to the business review strategy based on the test tag result set.

6. The method according to claim 1 or 3, characterized in that, The method further includes: Obtain the hit status of the first review strategy in the business review strategy and information on the business data that hit the first review strategy; Report the hit status of the first review strategy and the information of the business data that hit the first review strategy.

7. The method according to claim 6, characterized in that, The method further includes: Based on the information of the business data that hit the first review strategy, backtrack the tag result set corresponding to the business data that hit the first review strategy.

8. A data verification device, characterized in that, include: The storage module is used to store target business data in a relational database management system using message queues; The calling module is used to call the target business data stored in the relational database management system using a message queue at a preset frequency; The processing module is used to generate a business audit table based on the target business data, generate an identity identifier ID for the business audit table, and return the identity identifier ID of the business audit table to the business side. The business audit table is used to describe the target business data and the business audit strategy corresponding to the target business data. The process of detecting the target business data and obtaining a tag result set based on the business review strategy includes: setting a detection period for the target business data, setting the status of the business review table corresponding to the target business data to an unclaimable state, detecting the target business data based on the business review strategy within the detection period to obtain multiple tag data, and after the detection period expires, aggregating the multiple tag data to generate the tag result set; or, setting the status of the business review table corresponding to the target business data to an unclaimable state, detecting the target business data based on the business review strategy to obtain multiple tag data, and aggregating the multiple tag data to generate the tag result set when the number of multiple tag data is equal to the number of business review strategies. The determination module is used to select the highest priority tag data from the tag result set as the tag result corresponding to the target business data; The determining module is further configured to determine the review result of the target business data based on the tag result, wherein if the review operation indicated by the tag result is human review, the target business data is marked as available for collection; the available for collection status is used to indicate that it can be reviewed manually; the unavailable for collection status is used to indicate that it cannot be reviewed manually; the human review status is used to indicate that there are behaviors in the business data that cannot be reviewed and confirmed by the machine during the review process and that it needs to be reviewed manually.

9. The apparatus according to claim 8, characterized in that, The tag data includes the tag identity ID, tag name, display mode of the business review form corresponding to the tag, review operation corresponding to the tag, and tag priority.

10. The apparatus according to claim 9, characterized in that, The display modes of the business review form corresponding to the label include no highlight, business review form border highlight, and screenshot required; The review operations corresponding to the label also include running without processing, passing, rejecting, and suspending; The priority of the tags is distinguished by numerical values; the higher the value, the higher the priority level, or the lower the value, the higher the priority level.

11. The apparatus according to claim 8, characterized in that, The determining module is further configured to: If the review operation indicated by the label result is passed, then the review result of the target business data is passed; If the review operation indicated by the label result is rejection, then the review result of the target business data is rejection; If the audit operation indicated by the tag result is a no-go, then the tag result set of the target business data will be displayed.

12. A computer device, characterized in that, include: Memory, processor, and bus system; The memory is used to store programs; The processor is configured to execute a program in the memory, and the processor is configured to execute the method of any one of claims 1 to 7 according to instructions in the program code; The bus system is used to connect the memory and the processor to enable communication between the memory and the processor.

13. A computer-readable storage medium, characterized in that, Includes instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1 to 7.

14. A computer program product, characterized in that, The method includes computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions to cause the computer device to perform the method of any one of claims 1 to 7.

Images