CN117453415A

CN117453415A - Data auditing method, device, equipment and storage medium

Info

Publication number: CN117453415A
Application number: CN202311518112.1A
Authority: CN
Inventors: 逯燕芳
Original assignee: Taikang Insurance Group Co Ltd; Taikang Pension Insurance Co Ltd
Current assignee: Taikang Insurance Group Co Ltd; Taikang Pension Insurance Co Ltd
Priority date: 2023-11-14
Filing date: 2023-11-14
Publication date: 2024-01-26

Abstract

The application provides a data auditing method, device, equipment and storage medium, and belongs to the technical field of data processing and finance. Comprising the following steps: reading a data block and a corresponding data block identifier in a task queue, wherein the data block and the corresponding data block identifier are written into the task queue by a management module, and the data block is obtained by the management module responding to the start of an auditing process, reading target data to be audited and splitting the target data to be audited; determining the associated data block in the read data blocks according to the data block identification; splicing the associated data blocks according to the corresponding data block identifiers to obtain target data to be audited; creating an audit task corresponding to the target data to be audited; executing each sub-audit task by adopting a thread corresponding to the task type according to the task type corresponding to each sub-audit task in the audit task to obtain a sub-audit result; and determining a total auditing result according to each sub auditing result. The method solves the problem of low auditing efficiency.

Description

Data auditing method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of data processing and financial technologies, and in particular, to a data auditing method, device, apparatus, and storage medium.

Background

The current number of the old people rises year by year, in order to provide better living conditions for the old people, relevant enterprises provide nursing services, and corresponding nursing money is needed. The elderly also need to apply for corresponding care money while receiving care services.

Currently, in the prior art, when checking the usage way of nursing money, a fixed thread is generally adopted for checking.

However, the inventors found that at least the following technical problems exist in the prior art: the current auditing mode is relatively inefficient.

Disclosure of Invention

The application provides a data auditing method, device, equipment and storage medium, which are used for solving the problem that the efficiency of the current auditing mode is low.

In a first aspect, the present application provides a data auditing method, including: reading a data block and a corresponding data block identifier in a task queue, wherein the data block and the corresponding data block identifier are written into the task queue by a management module, the data block is obtained by reading target data to be checked by the management module in response to the start of the checking flow and splitting the target data to be checked, the target data to be checked is any data to be checked, and the data block identifier corresponding to the data block is generated by the management module; determining the associated data block in the read data blocks according to the data block identification; splicing the associated data blocks according to the corresponding data block identifiers to obtain target data to be audited; creating an audit task corresponding to the target data to be audited, wherein the audit task comprises sub audit tasks of different task types; executing each sub-auditing task by adopting a thread corresponding to the task type according to the task type corresponding to each sub-auditing task to obtain a sub-auditing result; and determining a total auditing result according to each sub auditing result.

In one possible implementation manner, according to a task type corresponding to each sub-audit task, executing each sub-audit task by adopting a thread corresponding to the task type to obtain a sub-audit result, including: searching a corresponding relation between the task type and the thread level according to the task type corresponding to the target sub-audit task to obtain a target thread level corresponding to the target sub-audit task, wherein the target sub-audit task is any sub-audit task; and executing a target sub-auditing task by adopting a target thread of a target thread grade to obtain a target sub-auditing result.

In one possible implementation manner, after searching the corresponding relation between the task type and the thread level according to the task type corresponding to the target sub-audit task to obtain the target thread level corresponding to the target sub-audit task, the method further includes: determining the thread of the target thread level as a thread to be selected; acquiring the use state of each thread to be selected; if each use state is occupied, increasing or decreasing the target thread level by one level to obtain a new target thread level; and executing a target sub-auditing task by adopting a new target thread corresponding to the new target thread level to obtain a target sub-auditing result.

In one possible implementation, determining the total audit result based on each sub-audit result includes: if the target sub-auditing result is not passed, determining a sub-auditing task corresponding to the target sub-auditing result as a target sub-auditing task, wherein the target sub-auditing result is any sub-auditing result; searching deduction values corresponding to task types of target sub-auditing tasks; adding the deduction values corresponding to the target sub-auditing tasks to obtain a total deduction value; if the total deduction value exceeds a preset threshold, the total auditing result is not passed.

In one possible implementation, determining the total audit result based on each sub-audit result includes: if any sub-auditing result is not passed, the total auditing result is not passed.

In one possible implementation, the target data to be checked includes location information; accordingly, after determining the total audit result according to each sub audit result, the method further comprises: and sending the auditing result to a database corresponding to the position information.

In a second aspect, the present application provides a data auditing method, including: reading target data to be audited in response to the start of the auditing process, wherein the target data to be audited is any data to be audited; splitting target data to be checked into at least two data blocks; generating a data block identifier corresponding to each data block; writing each data block and the corresponding data block identifier into a task queue so that an auditing server reads the data blocks and the corresponding data block identifiers in the task queue, determining the associated data blocks in the read data blocks according to the data block identifiers, splicing the associated data blocks according to the corresponding data block identifiers to obtain target data to be audited, creating auditing tasks corresponding to the target data to be audited, executing each sub auditing task by adopting threads corresponding to the task types according to the task types in the auditing tasks to obtain sub auditing results, and determining the total auditing result according to each sub auditing result.

In one possible implementation, writing each data block and a corresponding data block identifier to a task queue includes: and writing each data block and the corresponding data block identifier into a task queue by adopting at least two interfaces.

In a third aspect, the present application provides a data auditing apparatus, including: the data block reading module is used for reading the data block and the corresponding data block identifier in the task queue, wherein the data block and the corresponding data block identifier are written into the task queue by the management module, the data block is obtained by reading target data to be checked by the management module in response to the start of the checking flow and splitting the target data to be checked, the target data to be checked is any data to be checked, and the data block identifier corresponding to the data block is generated by the management module; the data determining module is used for determining the associated data block in the read data blocks according to the data block identification; the data splicing module is used for splicing the associated data blocks according to the corresponding data block identifiers to obtain target data to be audited; the task creation module is used for creating an audit task corresponding to the target data to be audited, wherein the audit task comprises sub audit tasks of different task types; the task execution module is used for executing each sub-auditing task by adopting a thread corresponding to the task type according to the task type corresponding to each sub-auditing task to obtain a sub-auditing result; and the result determining module is used for determining a total auditing result according to each sub auditing result.

In a fourth aspect, the present application provides a data auditing apparatus, comprising: the data reading module is used for responding to the start of the auditing process and reading target data to be audited, wherein the target data to be audited is any data to be audited; the data splitting module is used for splitting the target data to be checked into at least two data blocks; the identifier generation module is used for generating a data block identifier corresponding to each data block; the data writing module is used for writing each data block and the corresponding data block identifier into the task queue so that the auditing server reads the data blocks in the task queue and the corresponding data block identifiers, determines the associated data blocks in the read data blocks according to the data block identifiers, splices the associated data blocks according to the corresponding data block identifiers to obtain target data to be audited, creates auditing tasks corresponding to the target data to be audited, wherein the auditing tasks comprise sub auditing tasks of different task types, executes each sub auditing task by adopting threads corresponding to the task types according to the task types corresponding to each sub auditing task to obtain sub auditing results, and determines the total auditing result according to each sub auditing result.

In a fifth aspect, the present application provides an electronic device, comprising: a processor, a memory communicatively coupled to the processor; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored in the memory to cause the processor to perform the data auditing method as described in the first or second aspect.

In a sixth aspect, the present application provides a computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out a data auditing method as described in the first or second aspects.

According to the data auditing method, device, equipment and storage medium, the data blocks in the task queues and the corresponding data block identifiers are read, the related data blocks are spliced, target data to be audited is restored, the transmission of the target data to be audited is completed through the task queues, the data transmission speed is increased, the auditing tasks corresponding to the target data to be audited are created, different threads are adopted to execute different sub-auditing tasks, sub-auditing results are obtained, the total auditing results are obtained through the sub-auditing results, parallel processing of the sub-auditing tasks is achieved, the completion time of the sub-auditing tasks is close, accordingly, the total auditing results are obtained earlier, the auditing duration is shortened, and the auditing efficiency is increased.

Drawings

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

Fig. 1 is an application scenario schematic diagram of a data auditing method provided in an embodiment of the present application;

fig. 2 is a schematic flow chart of a data auditing method according to an embodiment of the present application;

FIG. 3 is a second flow chart of a data auditing method according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a data auditing apparatus according to an embodiment of the present application;

fig. 5 is a second schematic structural diagram of the data auditing apparatus according to the embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

The current elderly gradually increase in number, in order to improve the quality of life of the elderly, some enterprises provide nursing services, and the elderly also need to consume related money while enjoying the nursing services.

In order to make the consumption of the relevant money within a reasonable way, the relevant usage data of the money needs to be checked. The current auditing mode can adopt a computer for auditing besides manual auditing. However, the auditing efficiency of the current computer is still low.

In order to solve the technical problems, the inventor proposes the following technical ideas: the method comprises the steps that data to be checked are written into a task queue in a blocking mode, a server splices the data blocks in the task queue, sub-checking tasks of different task types corresponding to the data to be checked are created, the sub-checking tasks are processed by threads corresponding to the task types, sub-checking tasks are processed in a multithreading mode in parallel, sub-checking results are obtained, and total checking results are obtained from the sub-checking results.

The method and the device are applied to a scene of data auditing. It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

Fig. 1 is an application scenario schematic diagram of a data auditing method provided in an embodiment of the present application. As in fig. 1, in this scenario, it includes: rule configuration module 101, management module 102, audit server 103, database 104.

Rule configuration module 101, management module 102, which may include computers, servers, tablets, cell phones, palmtops (Personal Digital Assistant, PDA), notebooks, etc., may perform data input and output.

In a specific implementation process, the audit server 103 may be implemented by using a server or a cluster of multiple servers with more powerful processing capability and higher security, and if possible, a computer, a notebook computer, etc. with stronger computing capability may be used instead.

The database 104 may comprise a single database or may be a combination of databases. For example: one or more of Oracle (Oracle) database, mySQL (relational database management system), DRDS (Distribute Relational Database Service, distributed relational database) database, ES (elastic search) database, and the like, to which the present application is not limited in particular.

The connection mode between the rule configuration module 101 and the management module 102, and the connection mode between the auditing server 103, the management module 102 and the database 104 can be wired connection or wireless connection.

The rule configuration module 101 is configured and used for configuring and managing information such as auditing rules, knowledge details of a medical team, rule threshold values and the like, and is used when an auditing server audits data.

The management module 102 is configured to receive the auditing rules sent by the rule configuration module 101, and configure a local city auditing scheme, where the local city auditing scheme includes the number of rules, rule details, threshold information, and an intelligent auditing operation mode, and trigger an auditing server to start an auditing process after configuration is completed. And after receiving the auditing rule, reading the data to be audited, splitting the data to be audited into data blocks, generating data block identifiers corresponding to the data blocks, and writing the data blocks and the data block identifiers into a task queue.

And the auditing server 103 is used for reading the data blocks and the data block identifiers in the task queue, splicing the data blocks according to the data block identifiers, restoring the data to be audited, creating an auditing task by the data to be audited, executing the auditing task by adopting at least one thread, obtaining auditing results, and writing the auditing results into the database 104.

It will be appreciated that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the data auditing method. In other possible embodiments of the present application, the architecture may include more or fewer components than those illustrated, or some components may be combined, some components may be separated, or different component arrangements may be specifically determined according to the actual application scenario, and the present application is not limited herein. The components shown in fig. 1 may be implemented in hardware, software, or a combination of software and hardware.

The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 2 is a flowchart of a data auditing method according to an embodiment of the present application. The execution subject of the embodiment of the present application may be the audit server 103 in fig. 1, or may be a computer and/or a mobile phone, which is not particularly limited in this embodiment. As shown in fig. 2, the method includes:

S201: reading a data block and a corresponding data block identifier in a task queue, wherein the data block and the corresponding data block identifier are written into the task queue by a management module, the data block is obtained by reading target data to be checked by the management module in response to the start of the checking flow and splitting the target data to be checked, the target data to be checked is any data to be checked, and the data block identifier corresponding to the data block is generated by the management module.

In this step, reading the data block and the corresponding data block identifier directly from the task queue; the method also can comprise the steps of reading the data block identifier in the task queue and reading the data block according to the data block identifier; and the management module can read the data block identifier and the data block downloading link in the task queue and download the data block by adopting the downloading link, and correspondingly, the management module can write the data block downloading link and the data block identifier into the task queue.

S202: and determining the associated data block in the read data blocks according to the data block identification.

In this step, the format of the data block identifier may be included, where the data block identifier of the same group is found in all the read data block identifiers, and the data block corresponding to the data block identifier of the same group is determined as the associated data block.

The method for determining the data block identifiers belonging to the same group is that the data block identifiers with the same front N bits are used as the same group of data block identifiers, or that only the last preset data block identifiers with different bits are used as the same group of data block identifiers.

S203: and splicing the associated data blocks according to the corresponding data block identifiers to obtain target data to be audited.

In this step, the method may include splicing the associated data blocks according to the sequence of the corresponding data block identifiers, so as to obtain the target data to be audited. Splicing the associated data may be writing the associated data to the same file in a sequence identified by the data blocks.

S204: and creating an audit task corresponding to the target data to be audited, wherein the audit task comprises sub audit tasks of different task types.

In the step, a preset program or script is adopted to read target data to be audited, and an audit task is generated; the method can also comprise the steps of reading information in target data to be audited, and creating a corresponding audit task according to the read information; and the method can also comprise the steps of reading the position information in the target data to be checked, reading the business data in the database corresponding to the position information, and creating a checking task according to the target data to be checked and the read business data.

S205: and executing each sub-auditing task by adopting a thread corresponding to the task type according to the task type corresponding to each sub-auditing task to obtain a sub-auditing result.

In this step, searching for a corresponding relation between a preset task type and a thread according to a task type of the sub-audit task to obtain a target thread, and executing the sub-audit task by using the target thread to obtain a sub-audit result.

The corresponding relation between the task type and the thread can be calibrated in advance by a worker, and is stored in a form, a key value and the like.

S206: and determining a total auditing result according to each sub auditing result.

In this step, determining that the total audit result is audit-passed if all the sub audit results are audit-passed; and if the sub-auditing result corresponding to the preset sub-auditing task is not passed, the total auditing result is not passed.

As can be seen from the description of the foregoing embodiments, in the embodiments of the present application, by reading the data blocks in the task queue and the corresponding data block identifiers, splicing the associated data blocks, restoring the target data to be audited, completing the transmission of the target data to be audited through the task queue, increasing the transmission speed of the data, creating the audit task corresponding to the target data to be audited, and executing different sub-audit tasks by using different threads, so as to obtain a sub-audit result, and obtaining a total audit result from each sub-audit result, so as to implement parallel processing of the sub-audit tasks, and make the completion time of each sub-audit task close, thereby making the total audit result obtained earlier, reducing the audit duration, and increasing the audit efficiency.

In a possible implementation manner, in step S205, according to a task type corresponding to each sub-audit task, each sub-audit task is executed by using a thread corresponding to the task type, so as to obtain a sub-audit result, including:

s2051: and searching the corresponding relation between the task type and the thread level according to the task type corresponding to the target sub-audit task to obtain the target thread level corresponding to the target sub-audit task, wherein the target sub-audit task is any sub-audit task.

In this step, the corresponding relation between the task type and the thread level may be stored in a form of a table, a key value, or the like, and may be calibrated in advance by a worker.

For example, if the task type corresponding to the sub-audit task a is type a, the thread class corresponding to type a is searched, and if the thread class is 2, the thread class corresponding to the sub-audit task a is 2. For another example, if the task type corresponding to the sub-audit task B is type B, the thread class corresponding to type B is searched, and if the thread class is 1, the thread class corresponding to the sub-audit task B is 1.

S2052: and executing a target sub-auditing task by adopting a target thread of a target thread grade to obtain a target sub-auditing result.

In this step, different threads may correspond to the same or different thread levels, and any thread corresponding to the target thread level may be selected as the target thread. The target sub-audit task can be executed by adopting a target thread to read the target sub-audit task and execute the target sub-audit task, or can be input into the target thread to enable the target thread to execute the target sub-audit task, or can be written into a command line by the target thread identification and the target sub-audit task and executed, so that the target sub-audit task is executed to obtain a target sub-audit result.

As can be seen from the description of the above embodiments, in the embodiments of the present application, by executing the sub-audit task by using the thread with the corresponding level of the task type, the execution speed of the sub-audit task is increased, and the time required for executing each sub-audit task can be also made to be close, so that the waiting time of the subsequent audit task is reduced, and the efficiency of the total audit result is increased.

In one possible implementation manner, in step S2051, according to the task type corresponding to the target sub-audit task, the searching for the corresponding relationship between the task type and the thread level, to obtain the target thread level corresponding to the target sub-audit task further includes:

S210: and determining the thread of the target thread level as the thread to be selected.

In this step, for example, the target thread level is level a, and level a corresponds to threads 1, 2, 3, and 4, and then threads 1, 2, 3, and 4 are determined as threads to be selected. For another example, the target thread level is level B, which corresponds to the thread 1010, 1011, 1012, then the thread 1010, 1011, 1012 is determined to be the thread to be selected.

S211: and acquiring the use state of each thread to be selected.

In this step, writing the thread to be selected into a preset command template to obtain a target command, and obtaining the use state of the thread with selection by using the target command. The method can further comprise the step of acquiring the use state of each thread to be selected by adopting a preset program or script.

S212: if each use state is occupied, the target thread level is increased or decreased by one level, and a new target thread level is obtained.

In this step, for example, there are 4 threads to be selected currently, and the corresponding use states are occupied, and the target thread level "B" is promoted by one level, so as to obtain a new target thread level "a". For another example, when there are currently 5 threads to be selected and the corresponding use states are occupied, the target thread level "2" is lowered by one level, and a new target thread level "3" is obtained.

The increasing or decreasing level may be increased or decreased according to the setting of the worker. The level may be preset by the staff.

S213: and executing a target sub-auditing task by adopting a new target thread corresponding to the new target thread level to obtain a target sub-auditing result.

This step is similar to step S2052 described above, and will not be described again here.

As can be seen from the description of the foregoing embodiments, in the embodiments of the present application, a thread of a target thread level is determined as a thread to be selected, the use state of each thread to be selected is obtained, the target thread level is reduced or increased under the condition that the use states of all threads to be selected are occupied, a new target thread level is obtained, and a thread corresponding to the new target thread level is adopted to execute a target sub-audit task, so that the effect that threads are adjusted under the condition that directly selected threads are occupied, and unoccupied threads are used to execute audit tasks is achieved, so that queuing time of the sub-audit task is reduced, and audit efficiency is increased.

In a possible implementation manner, in step S206, determining the total audit result according to each sub audit result includes:

s2061: if the target sub-auditing result is not passed, determining a sub-auditing task corresponding to the target sub-auditing result as a target sub-auditing task, wherein the target sub-auditing result is any sub-auditing result.

In this step, for example, if the sub-audit result corresponding to the sub-audit task a is failed, the sub-audit task a is determined as the target sub-audit task. And if the sub-auditing results corresponding to any sub-auditing task are different, determining the auditing task as a target sub-auditing task.

S2062: and searching the deduction value corresponding to the task type of the target sub-audit task.

In this step, searching a corresponding relation between a preset task type and a deduction value according to a task type of the target sub-audit task to obtain a corresponding deduction value.

The corresponding relation between the task type and the deduction value can be formulated by staff according to the auditing requirement, and can be stored in a form and key value equivalent format.

S2063: and adding the deduction values corresponding to the target sub-auditing tasks to obtain a total deduction value.

In this step, for example, there are 4 target sub-audit tasks currently, and the corresponding deduction values are 2, 5, 3, and 5 respectively, and the total deduction value is 15; for another example, there are currently 3 target sub-audit tasks, and the corresponding deduction values are 1, 2, and 1 respectively, and the total deduction value is 4.

S2064: if the total deduction value exceeds a preset threshold, the total auditing result is not passed.

In this step, the preset threshold may be set by a worker according to an audit rule, experimental data, history data, or the like.

For example, if the current total deduction value is 6 and the preset threshold is 4, the total auditing result is not passed. For another example, if the current total deduction value is 20 and the preset threshold is 10, the total auditing result is not passed.

As can be seen from the description of the above embodiment, in the embodiment of the present application, accumulation of the audit failure condition is achieved by calculating the sum of deduction values corresponding to the failed sub-audit task, so as to ensure the security of the whole audit process.

s2065: if any sub-auditing result is not passed, the total auditing result is not passed.

In this step, for example, there are currently 5 sub-audit results, where one sub-audit result is failed, and the total audit result is failed. For another example, there are currently 20 sub-audit results, where 2 sub-audit results are failed, and the total audit result is failed.

As can be seen from the description of the above embodiment, in the embodiment of the present application, by determining that the total audit result is failed when any sub audit result is failed, the audit result is strictly controlled, and the audit error probability is reduced.

In one possible implementation, the target pending data includes location information.

Accordingly, after determining the total audit result according to each sub audit result in step S206, the method further includes:

s220: and sending the auditing result to a database corresponding to the position information.

In this step, the method may include obtaining a target database address corresponding to the location information, and transmitting the auditing result to the database by using the target database address; the method can also comprise the steps of writing the auditing result into a message queue and asynchronously storing the auditing result into a database by adopting the message queue, specifically, the method can comprise the steps of writing the auditing result into the message queue and asynchronously storing the auditing result into the database when the auditing result passes or fails, and the method can also comprise the step of writing the auditing result which only passes the auditing result into the message queue and asynchronously storing the auditing result into the database. By writing the message queue, the interfaces of the auditing server and the databases in each region can be fully utilized.

For example, if the position information contained in the target data to be audited is the area A, the auditing result is sent to a database corresponding to the area A; for another example, if the location information included in the target data to be audited is the region B, the auditing result is sent to the database corresponding to the region B.

As can be seen from the description of the above embodiments, according to the embodiment of the present application, by sending the audit result to the database corresponding to the location information, the audit result is stored in different regions, so that users in each region can conveniently query the audit result, and the speed of querying the audit result is increased.

Fig. 3 is a second flowchart of a data auditing method according to an embodiment of the present application. The execution subject of the embodiment of the present application may be the management module 102 in fig. 1, or may be a computer and/or a mobile phone, which is not particularly limited in this embodiment. As shown in fig. 3, the method includes:

s301: and responding to the start of the auditing flow, and reading target data to be audited, wherein the target data to be audited is any data to be audited.

In this step, the starting of the audit process may include starting the audit process after receiving the audit rule sent by the rule management module, or starting the audit process after receiving an audit process starting instruction sent by the staff terminal device. Reading the target data to be audited can include routing to a database query service data corresponding to the location information according to the location information corresponding to the auditing process. Reading the target data to be audited can also comprise reading the target data to be audited according to the data position in the auditing flow. The target data to be audited can also be data corresponding to the auditing flow.

S302: splitting the target data to be checked into at least two data blocks.

In this step, the method may include splitting the target data to be audited into two data blocks with equal or similar sizes, splitting the target data to be audited into at least two data blocks according to the content of the target data to be audited, and splitting the target data to be audited according to the size of the target data to be audited.

S303: and generating a data block identifier corresponding to each data block.

In this step, a preset program or script may be adopted to generate a data block identifier corresponding to each data block, and further may include generating a new data block identifier by using an existing data block identifier. The generated data block identifier corresponding to each data block may include the same field, so that the auditing server can read the associated data block.

S304: writing each data block and the corresponding data block identifier into a task queue so that an auditing server reads the data blocks and the corresponding data block identifiers in the task queue, determining the associated data blocks in the read data blocks according to the data block identifiers, splicing the associated data blocks according to the corresponding data block identifiers to obtain target data to be audited, creating auditing tasks corresponding to the target data to be audited, executing each sub auditing task by adopting threads corresponding to the task types according to the task types in the auditing tasks to obtain sub auditing results, and determining the total auditing result according to each sub auditing result.

In this step, when writing into the task queue, the data block and the corresponding data block identifier may be directly written into the task queue, or the method may further include writing the download link of the data block and the data block identifier into the task queue.

As can be seen from the description of the foregoing embodiments, after the re-auditing process starts, the embodiments of the present application read the target data to be audited, split the target data to be audited into at least two data blocks, generate the data block identifiers corresponding to the data blocks, write the data blocks and the corresponding data block identifiers into the task queue, so that the auditing server reads the data blocks in the task queue and splices the data blocks, restore the target data to be audited, create the auditing task corresponding to the target data to be audited, execute the sub-auditing task by using the thread corresponding to the task type of the sub-auditing task in the auditing task, obtain the sub-auditing result, obtain the total auditing result according to the sub-auditing result, implement parallel writing of the data blocks into the task queue, increase the interface performance, implement parallel processing of the auditing task, and increase the processing efficiency of the auditing task.

In a possible implementation manner, in step S304, writing each data block and the corresponding data block identifier into the task queue includes:

S3041: and writing each data block and the corresponding data block identifier into a task queue by adopting at least two interfaces.

In this step, the interface may include an I/O (input/output) interface. The number of interfaces employed may include the number of interfaces equal to the number of data blocks employed, or the number of interfaces less than the number of data blocks may be employed.

As can be seen from the description of the above embodiments, in the embodiments of the present application, by adopting at least two interfaces to write each data block and the corresponding data block identifier into the task queue, the writing speed of the data block is increased, so as to increase the auditing efficiency.

Fig. 4 is a schematic structural diagram of a data auditing apparatus according to an embodiment of the present application. As shown in fig. 4, the data auditing apparatus 400 includes: a data block reading module 401, a data determining module 402, a data splicing module 403, a task creating module 404, a task executing module 405 and a result determining module 406.

The data block reading module 401 is configured to read a data block and a corresponding data block identifier in the task queue, where the data block and the corresponding data block identifier are written into the task queue by the management module, the data block is obtained by the management module by reading target data to be checked in response to the start of the checking process and splitting the target data to be checked, the target data to be checked is any data to be checked, and the data block identifier corresponding to the data block is generated by the management module;

A data determining module 402, configured to determine, according to the data block identifier, an associated data block in the read data blocks;

the data splicing module 403 is configured to splice the associated data blocks according to the corresponding data block identifiers, so as to obtain target data to be audited;

the task creation module 404 is configured to create an audit task corresponding to the target data to be audited, where the audit task includes sub audit tasks of different task types;

the task execution module 405 is configured to execute each sub-audit task by using a thread corresponding to a task type according to a task type corresponding to each sub-audit task, so as to obtain a sub-audit result;

the result determining module 406 is configured to determine a total audit result according to each sub audit result.

The device provided in this embodiment may be used to implement the technical solution of the foregoing method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein again.

In one possible implementation manner, the task execution module 405 is configured to search, according to a task type corresponding to a target sub-audit task, a corresponding relationship between the task type and a thread level, to obtain a target thread level corresponding to the target sub-audit task, where the target sub-audit task is any sub-audit task; and executing a target sub-auditing task by adopting a target thread of a target thread grade to obtain a target sub-auditing result.

In one possible implementation, the data auditing apparatus 400 further includes: the thread adjustment module 407.

A thread adjustment module 407, configured to determine a thread of the target thread level as a thread to be selected; acquiring the use state of each thread to be selected; if each use state is occupied, increasing or decreasing the target thread level by one level to obtain a new target thread level; and executing a target sub-auditing task by adopting a new target thread corresponding to the new target thread level to obtain a target sub-auditing result.

In a possible implementation manner, the result determining module 406 is configured to determine, if the target sub-audit result is not passed, a sub-audit task corresponding to the target sub-audit result as a target sub-audit task, where the target sub-audit result is any sub-audit result; searching deduction values corresponding to task types of target sub-auditing tasks; adding the deduction values corresponding to the target sub-auditing tasks to obtain a total deduction value; if the total deduction value exceeds a preset threshold, the total auditing result is not passed.

In one possible implementation, the result determining module 406 is specifically configured to determine that if any sub-audit result is failed, the total audit result is failed.

In one possible implementation, the target data to be checked includes location information; the data auditing apparatus 400 further includes: the result is sent to module 408. And the result sending module 408 is configured to send the auditing result to a database corresponding to the location information.

Fig. 5 is a schematic structural diagram of a data auditing apparatus according to an embodiment of the present application. As shown in fig. 5, the data auditing apparatus 500 includes: a data reading module 501, a data splitting module 502, an identification generating module 503 and a data writing module 504.

The data reading module 501 is configured to read target data to be audited in response to starting an audit process, where the target data to be audited is any data to be audited;

a data splitting module 502, configured to split target data to be checked into at least two data blocks;

an identifier generating module 503, configured to generate a data block identifier corresponding to each data block;

the data writing module 504 is configured to write each data block and a corresponding data block identifier into the task queue, so that the auditing server reads the data block in the task queue and the corresponding data block identifier, determines an associated data block in the read data block according to the data block identifier, splices the associated data block according to the corresponding data block identifier, obtains target data to be audited, creates an auditing task corresponding to the target data to be audited, where the auditing task includes sub-auditing tasks of different task types, executes each sub-auditing task by using a thread corresponding to the task type according to the task type corresponding to each sub-auditing task, obtains a sub-auditing result, and determines a total auditing result according to each sub-auditing result.

In one possible implementation, the data writing module 504 is configured to use at least two interfaces to write each data block and the corresponding data block identifier to the task queue.

In order to achieve the above embodiments, the present application further provides an electronic device.

Referring to fig. 6, a schematic structural diagram of an electronic device 600 suitable for implementing embodiments of the present application is shown, where the electronic device 600 may be a terminal device or a server. The terminal device may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a personal digital assistant (Personal Digital Assistant, PDA for short), a tablet (Portable Android Device, PAD for short), a portable multimedia player (Portable Media Player, PMP for short), an in-vehicle terminal (e.g., an in-vehicle navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 6 is only an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present application.

As shown in fig. 6, the electronic device 600 may include a processor (e.g., a central processing unit, a graphics processor, etc.) 601, and a Memory 602 communicatively connected to the processor, which may perform various appropriate actions and processes according to a program stored in the Memory 602, a computer executed instruction, or a program loaded from a storage device 608 into a random access Memory (Random Access Memory, RAM) 603, to implement the data auditing method in any of the above embodiments, where the Memory may be a Read Only Memory (ROM). In the RAM603, various programs and data required for the operation of the electronic apparatus 600 are also stored. The processing device 601, the memory 602, and the RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

In general, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 607 including, for example, a liquid crystal display (Liquid Crystal Display, LCD for short), a speaker, a vibrator, and the like; storage 608 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 shows an electronic device 600 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via communication device 609, or from storage device 608, or from memory 602. The above-described functions defined in the methods of the embodiments of the present application are performed when the computer program is executed by the processing means 601.

It should be noted that the computer readable storage medium described in the present application may be a computer readable signal medium or a computer storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal that propagates in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable storage medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

The computer-readable storage medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer-readable storage medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above-described embodiments.

Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (Local Area Network, LAN for short) or a wide area network (Wide Area Network, WAN for short), or it may be connected to an external computer (e.g., connected via the internet using an internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules involved in the embodiments described in the present application may be implemented by software, or may be implemented by hardware. Where the names of the units do not constitute a limitation of the module itself in some cases, the data determination module may also be described as an "associated data block determination module", for example.

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

The application further provides a computer readable storage medium, in which computer execution instructions are stored, when a processor executes the computer execution instructions, the technical scheme of the data auditing method in any of the above embodiments is implemented, and the implementation principle and beneficial effects are similar to those of the data auditing method, and can be seen, and the detailed description is omitted herein.

In the context of this application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The application further provides a computer program product, which comprises a computer program, when the computer program is executed by a processor, the technical scheme of the data auditing method in any of the above embodiments is implemented, and the implementation principle and beneficial effects are similar to those of the data auditing method, and can be seen from the implementation principle and beneficial effects of the data auditing method, and the detailed description is omitted here.

The foregoing description is only of the preferred embodiments of the present application and is presented as a description of the principles of the technology being utilized. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this application is not limited to the specific combinations of features described above, but it is intended to cover other embodiments in which any combination of features described above or equivalents thereof is possible without departing from the spirit of the disclosure. Such as the above-described features and technical features having similar functions (but not limited to) disclosed in the present application are replaced with each other.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A data auditing method, characterized by being applied to an auditing server, comprising:

reading a data block and a corresponding data block identifier in a task queue, wherein the data block and the corresponding data block identifier are written into the task queue by a management module, the data block is obtained by the management module responding to the start of an auditing process, reading target data to be audited and splitting the target data to be audited, the target data to be audited is any data to be audited, and the data block identifier corresponding to the data block is generated by the management module;

determining the associated data block in the read data blocks according to the data block identification;

splicing the associated data blocks according to the corresponding data block identifiers to obtain the target data to be audited;

creating an audit task corresponding to the target data to be audited, wherein the audit task comprises sub audit tasks of different task types;

Executing each sub-auditing task by adopting a thread corresponding to the task type according to the task type corresponding to each sub-auditing task to obtain a sub-auditing result;

and determining a total auditing result according to each sub auditing result.

2. The method of claim 1, wherein the executing each sub-audit task by using a thread corresponding to a task type according to a task type corresponding to each sub-audit task to obtain a sub-audit result includes:

searching a corresponding relation between a task type and a thread grade according to a task type corresponding to a target sub-audit task to obtain a target thread grade corresponding to the target sub-audit task, wherein the target sub-audit task is any sub-audit task;

and executing the target sub-auditing task by adopting the target thread of the target thread level to obtain a target sub-auditing result.

3. The method according to claim 2, wherein after searching for a corresponding relation between a task type and a thread level according to a task type corresponding to a target sub-audit task to obtain a target thread level corresponding to the target sub-audit task, the method further comprises:

determining the thread of the target thread level as a thread to be selected;

Acquiring the use state of each thread to be selected;

if each use state is occupied, increasing or decreasing the target thread level by one level to obtain a new target thread level;

and executing the target sub-auditing task by adopting the new target thread corresponding to the new target thread level to obtain a target sub-auditing result.

4. The method of claim 1, wherein determining the total audit result based on each sub-audit result comprises:

if the target sub-auditing result is not passed, determining a sub-auditing task corresponding to the target sub-auditing result as a target sub-auditing task, wherein the target sub-auditing result is any sub-auditing result;

searching deduction values corresponding to task types of target sub-auditing tasks;

adding the deduction values corresponding to the target sub-auditing tasks to obtain a total deduction value;

if the total deduction value exceeds a preset threshold, the total auditing result is failed.

5. The method of claim 1, wherein determining the total audit result based on each sub-audit result comprises:

if any sub-auditing result is not passed, the total auditing result is not passed.

6. The method according to any one of claims 1 to 5, wherein the target data to be audited includes location information;

correspondingly, after determining the total auditing result according to each sub auditing result, the method further comprises the following steps:

and sending the auditing result to a database corresponding to the position information.

7. A data auditing method, characterized by being applied to a management module, comprising:

reading target data to be audited in response to the start of an audit process, wherein the target data to be audited is any data to be audited;

splitting the target data to be audited into at least two data blocks;

generating a data block identifier corresponding to each data block;

writing each data block and the corresponding data block identifier into a task queue so that an auditing server reads the data blocks and the corresponding data block identifiers in the task queue, determining the associated data blocks in the read data blocks according to the data block identifiers, splicing the associated data blocks according to the corresponding data block identifiers to obtain the target data to be audited, creating auditing tasks corresponding to the target data to be audited, executing each sub-auditing task by adopting threads corresponding to the task types according to the task types in the auditing tasks to obtain sub auditing results, and determining the total auditing results according to each sub auditing result.

8. The method of claim 7, wherein writing each data block and corresponding data block identification to the task queue comprises:

and writing each data block and the corresponding data block identifier into a task queue by adopting at least two interfaces.

9. A data auditing apparatus, comprising:

the data block reading module is used for reading a data block and a corresponding data block identifier in a task queue, wherein the data block and the corresponding data block identifier are written into the task queue by the management module, the data block is obtained by the management module by responding to the start of an auditing flow, reading target data to be audited and splitting the target data to be audited, the target data to be audited is any data to be audited, and the data block identifier corresponding to the data block is generated by the management module;

the data determining module is used for determining the associated data block in the read data blocks according to the data block identification;

the data splicing module is used for splicing the associated data blocks according to the corresponding data block identifiers to obtain the target data to be audited;

the task creation module is used for creating an audit task corresponding to the target data to be audited, wherein the audit task comprises sub audit tasks of different task types;

The task execution module is used for executing each sub-auditing task by adopting a thread corresponding to the task type according to the task type corresponding to each sub-auditing task to obtain a sub-auditing result;

and the result determining module is used for determining a total auditing result according to each sub auditing result.

10. A data auditing apparatus, comprising:

the data reading module is used for responding to the start of the auditing process and reading target data to be audited, wherein the target data to be audited is any data to be audited;

the data splitting module is used for splitting the target data to be audited into at least two data blocks;

the identifier generation module is used for generating a data block identifier corresponding to each data block;

the data writing module is used for writing each data block and the corresponding data block identifier into the task queue so that the auditing server reads the data blocks in the task queue and the corresponding data block identifiers, determines the associated data blocks in the read data blocks according to the data block identifiers, splices the associated data blocks according to the corresponding data block identifiers to obtain the target data to be audited, creates auditing tasks corresponding to the target data to be audited, wherein the auditing tasks comprise sub auditing tasks of different task types, executes each sub auditing task by adopting threads corresponding to the task types according to the task types corresponding to each sub auditing task to obtain sub auditing results, and determines the total auditing result according to each sub auditing result.