Product data checking method, device and equipment and storage medium

Abstract

The invention discloses a product data checking method, device and equipment and a storage medium, and relates to the technical field of big data, the method comprises the steps that when current product data is received, target incoming parameters are determined in preset parameters according to the current product data, and the preset parameters are obtained based on data ready time configuration corresponding to a standard checking rule; a target check rule corresponding to the target incoming parameter is inquired in a preset check rule table, the preset check rule table comprises a plurality of sub check rules, and each sub check rule is obtained by splitting the standard check rule according to an associated data block corresponding to the standard check rule; and the current product data is checked according to the target checking rule, so that the checking rule can be executed to obtain the current checking result without waiting for all the data blocks to be ready, and the checking timeliness is improved.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a product data verification method, device, equipment and storage medium. Background Art

[0002] Banks and financial institutions are required to submit various data reports to regulatory agencies daily. To ensure the accuracy and completeness of these reports, they can undergo data verification before submission. These reports often involve data blocks from multiple data sources, and the generation and availability of these data blocks from different sources can vary. Therefore, traditionally, companies typically perform verification based on standard verification rules specified by regulators after all data blocks involved in the report are ready.

[0003] However, due to the diversity of data sources and data blocks, it is necessary to execute relevant standard verification rules for data blocks in different data sources separately. Therefore, the system executes a large number of verification rules at the same time, resulting in high utilization of the system's computing resources, affecting the execution time of the verification work, making it impossible for enterprises to obtain verification results in a timely manner, and thus affecting the timely submission of data reports. Summary of the Invention

[0004] The main purpose of this application is to provide a product data verification method, device, equipment and storage medium, aiming to solve the technical problems that the existing methods take a long time to perform data verification operations and the timeliness of the verification results is low.

[0005] To achieve the above objectives, the present application proposes a product data verification method, which includes:

[0006] Upon receiving the current product data, determining the target input parameter from each preset parameter according to the current product data, each preset parameter being configured based on the data ready time corresponding to the standard verification rule;

[0007] Querying a target verification rule corresponding to the target input parameter in a preset verification rule table, wherein the preset verification rule table includes a plurality of sub-verification rules, each of which is obtained by splitting the standard verification rule according to the associated data block corresponding to the standard verification rule;

[0008] The current product data is checked according to the target checking rules to generate a current checking result.

[0009] In one embodiment, before the step of determining the target input parameter from among the preset parameters according to the current product data upon receiving the current product data, the following steps are included:

[0010] Obtaining a standard verification rule, and determining a number of associated data blocks according to the standard verification rule;

[0011] Splitting the standard check rule based on each of the associated data blocks to obtain a plurality of sub-check rules;

[0012] The sub-check rules are grouped according to the data ready time of each associated data block, and a plurality of preset parameters are generated according to the grouping result.

[0013] In one embodiment, the step of grouping the sub-check rules according to the data ready time of each associated data block and generating a plurality of preset parameters according to the grouping result includes:

[0014] Labeling each of the sub-check rules according to the data ready time of each of the associated data blocks;

[0015] Grouping the marked sub-check rules according to preset time interval conditions to obtain a number of scheduling groups;

[0016] Parameter configuration is performed based on each of the scheduling groups to generate corresponding preset parameters.

[0017] In one embodiment, after the step of performing parameter configuration based on each of the scheduling groups and generating corresponding preset parameters, the following steps are included:

[0018] The preset parameters and the corresponding sub-check rules are integrated to obtain a preset check rule table.

[0019] In one embodiment, upon receiving the current product data, the step of determining the target input parameter from among the preset parameters according to the current product data includes:

[0020] Upon receiving the current product data, determining whether the current product data satisfies a data-ready condition of at least one preset parameter;

[0021] If so, the preset parameters that meet the data ready condition are determined as target input parameters.

[0022] In one embodiment, upon receiving the current product data, determining whether the current product data satisfies a data readiness condition of at least one preset parameter includes:

[0023] Upon receiving the current product data, determining whether there are any unexecuted preset parameters;

[0024] If so, it is determined whether a data readiness condition of at least one of the unexecuted preset parameters is satisfied by combining the current product data and the cached product data.

[0025] In one embodiment, the step of performing a verification operation on the current product data according to the target verification rule to generate a current verification result includes:

[0026] The target checking rule is called by the dynamic script executor to generate the current execution script;

[0027] A verification operation is performed on the current product data based on the current execution script, and the previous verification result table is updated according to the operation result to generate a current verification result table.

[0028] In addition, to achieve the above-mentioned purpose, the present application also proposes a product data verification device, which includes:

[0029] A parameter trigger module, configured to, upon receiving current product data, determine target input parameters from among various preset parameters based on the current product data, wherein each of the preset parameters is configured based on a data ready time corresponding to a standard verification rule;

[0030] a rule response module, configured to query a preset verification rule table for a target verification rule corresponding to the target input parameter, wherein the preset verification rule table includes a plurality of sub-verification rules, each of which is obtained by splitting the standard verification rule according to the associated data block corresponding to the standard verification rule;

[0031] The real-time verification module is used to perform a verification operation on the current product data according to the target verification rules to generate a current verification result.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a product data verification device, which includes: a memory, a processor, and a product data verification program stored on the memory and runnable on the processor, and the product data verification program is configured to implement the steps of the product data verification method described above.

[0033] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and stores a product data verification program on the storage medium. When the product data verification program is executed by the processor, the steps of the product data verification method described above are implemented.

[0034] The present application discloses a product data verification method, which determines the target input parameter in each preset parameter according to the current product data when receiving the current product data, and each preset parameter is configured based on the data ready time corresponding to the standard verification rule; queries the target verification rule corresponding to the target input parameter in the preset verification rule table, and the preset verification rule table includes a plurality of sub-verification rules, and each sub-verification rule is obtained by splitting the standard verification rule according to the associated data block corresponding to the standard verification rule; performs a verification operation on the current product data according to the target verification rule to generate a current verification result.

[0035] This application configures preset parameters based on the data readiness time and determines the target input parameters when receiving product data. This allows the corresponding verification rules to be activated in a timely manner, avoiding the need to wait for all data to be ready, thereby obtaining partial verification results in advance and significantly improving the timeliness of verification work. Furthermore, the standard verification rules are split into multiple sub-verification rules and stored in a preset verification rule table, enabling refined management of verification rules. This avoids the problem of excessive computing resources caused by executing a large number of verification rules at the same time in traditional methods, reduces the system burden, and effectively shortens the execution time of verification operations. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0038] Figure 1 This is a flowchart of the first embodiment of the product data verification method of this application;

[0039] Figure 2 This is a flow chart of a second embodiment of the product data verification method of this application;

[0040] Figure 3 This is a schematic diagram of the data block granularity splitting of the standard verification rule;

[0041] Figure 4 A schematic diagram of labeling for sub-check rules;

[0042] Figure 5 This is a flowchart of a third embodiment of the product data verification method of this application;

[0043] Figure 6 This is a schematic diagram of the verification process based on the currently executed script;

[0044] Figure 7 This is a schematic diagram of the module structure of the first embodiment of the product data verification device of this application;

[0045] Figure 8 This is a structural diagram of the product data verification equipment for this application.

[0046] The purpose, features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0047] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.

[0048] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0049] This application embodiment provides a product data verification method, referring to Figure 1 , Figure 1 This is a flowchart of a first embodiment of the product data verification method of this application. In this embodiment, the method includes steps S10 to S30:

[0050] Step S10: upon receiving the current product data, determining target input parameters from various preset parameters according to the current product data, wherein each of the preset parameters is configured based on a data ready time corresponding to a standard checking rule.

[0051] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, mobile phone, verification server, etc., or an electronic device that can achieve the above functions and is connected to the verification system. The following uses the verification system server (hereinafter referred to as the "system") as an example to illustrate this embodiment and the following embodiments.

[0052] It is understandable that the current product data may be the latest data related to the currently submitted product received by the system. The current product data may come from multiple different data sources and include different data blocks.

[0053] Data blocks can be created by dividing related data into different data sources and business types. Because the data sources—and, therefore, the data generation logic—of related data vary, data blocks can be divided based on different data sources. From a business perspective, data generated by different business types within the same data source also differ. To facilitate more precise identification of data issues later, data blocks can also be divided based on different business types.

[0054] It should be understood that the preset parameters may be parameters for triggering a verification operation, and a dynamic script executor may be pre-configured in the system, which can automatically trigger a corresponding verification operation when the preset parameters are obtained.

[0055] Standard verification rules can be a number of rules given by regulatory agencies or defined by the enterprise itself for testing data integrity and accuracy. Current product data can only be used to generate data reports for submission to regulatory agencies when it meets the standard verification rules.

[0056] Since the number of standard check rules is not unique, different standard check rules can be marked as different check master tables. For example, standard check rule A can correspond to check master table A, and standard check rule B can correspond to check master table B.

[0057] It should also be noted that a standard check rule may involve one or more data blocks, and the data-ready time of different data blocks may vary. Therefore, the data-ready time of each standard check rule may also vary. Standard check rules with similar data-ready times can be configured in the same preset parameters, and the number of preset parameters configured can be determined based on the different data-ready times. The data-ready time is the time it takes for all data in a data block to arrive at the system.

[0058] It should be understood that, given that different data blocks may have different data readiness times under the same standard verification rule, each standard verification rule can be split at the data block granularity to obtain several sub-verification rules. For example, if the standard verification rule is: perform consistency check on personal basic data, and the personal basic data comes from data block A and data block B; the resulting sub-verification rules are: perform consistency check on data block A and perform consistency check on data block B.

[0059] Accordingly, sub-check rules with similar data-ready times may be configured in the same preset parameter, and the number of configured preset parameters may be determined according to different data-ready times.

[0060] In a specific implementation, when the current product data arrives at the system, if all data blocks involved in the standard check rule corresponding to a preset parameter are ready, then the preset parameter becomes the target input parameter.

[0061] Step S20: querying the target check rule corresponding to the target input parameter in the preset check rule table, wherein the preset check rule table includes a plurality of sub-check rules, each of which is obtained by splitting the standard check rule according to the associated data block corresponding to the standard check rule.

[0062] It should be noted that the preset check rule table may include all standard check rules and their sub-check rules. Since sub-check rules with similar data ready time can be configured in the same preset parameters, each sub-check rule can be marked with its corresponding preset parameters in the preset check rule table.

[0063] In a specific implementation, the system may perform a match in a preset verification rule table according to the determined target input parameters, obtain a sub-verification rule that is consistent with the target input parameters, and determine it as the target verification rule.

[0064] Step S30: performing a verification operation on the current product data according to the target verification rule to generate a current verification result.

[0065] It should be understood that after determining the target check rule, the system can call the target check rule through the dynamic script executor to generate the current execution script. The dynamic script executor can be constructed based on a programming language such as Python, which is not limited in this embodiment.

[0066] The system can perform a verification operation on the current product data based on the currently executed script, and output the verification result in the form of a table, that is, the current verification result table.

[0067] It should also be noted that if the current product data is the relevant data of the currently submitted product that is input for the first time, the verification result table can be generated for the first time based on the operation results; if the current product data is not the relevant data of the currently submitted product that is input for the first time, the result of this operation can be inserted into the verification result table generated last time in an incremental manner to realize the table update, generate the current verification result table and output it.

[0068] In the specific implementation, if the data block A data and data block B data related to the currently submitted product are transmitted to the system at 5:00 and 12:00 respectively; the verification results of the data block A data can be viewed at 5:00, and the verification results of the data block A data and data block B data can be viewed at 12:00.

[0069] This embodiment configures preset parameters based on data readiness time and determines target input parameters upon receiving product data. This allows for timely activation of corresponding verification rules, avoiding the need to wait for all data to be ready, thereby obtaining partial verification results in advance and significantly improving the timeliness of verification work. Furthermore, by splitting standard verification rules into multiple sub-verification rules and storing them in a preset verification rule table, this enables refined management of verification rules, avoiding the problem of excessive computing resources caused by executing a large number of verification rules simultaneously in traditional methods, reducing system burden, and effectively shortening the execution time of verification operations.

[0070] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above embodiment 1 can be referred to the above introduction and will not be described in detail later. Figure 2 , Figure 2 This is a flow chart of the second embodiment of the product data verification method of this application.

[0071] In this embodiment, in order to specifically illustrate how to configure preset parameters according to different data ready times, before step S10, the following steps are also included: Steps S001 to S003:

[0072] Step S001: Acquire standard checking rules, and determine a number of associated data blocks according to the standard checking rules.

[0073] Step S002: splitting the standard check rule based on each of the associated data blocks to obtain a plurality of sub-check rules.

[0074] It should be understood that the standard verification rules given by the regulatory authorities can be broken down into the granularity of each data block. For example, if the standard verification rules are: Verify the main table A: the deposit account code + deposit serial number in the personal deposit basic information table should be unique.

[0075] The personal deposit basic information table involves three related data blocks. The main verification table A can be divided into sub-verification rules A1, sub-verification rules A2 and sub-verification rules A3, which correspond to the verification rules of data block A, data block B and data block C respectively. Figure 3 As shown, Figure 3 This is a schematic diagram of the data block granularity splitting of standard verification rules.

[0076] By analogy, for a single standard check rule, the number of data blocks involved is the number of sub-check rules obtained by splitting.

[0077] Step S003: grouping the sub-check rules according to the data ready time of each associated data block, and generating a plurality of preset parameters according to the grouping result.

[0078] It should be noted that here, a standard verification rule (the deposit account code + deposit serial number in the above-mentioned verification main table A: personal deposit basic information table should be unique) can be split into several sub-verification rules (sub-verification rule A1, sub-verification rule A2 and sub-verification rule A3) to illustrate the process:

[0079] For example, if the data ready time for data block A is 5:00, the data ready time for data block B is 12:00, and the data ready time for data block C is 16:00, then the earliest batch run start time for sub-check rule A1 is after 5:00, the earliest batch run start time for sub-check rule A2 is after 12:00, and the earliest batch run start time for sub-check rule A3 is after 16:00.

[0080] Therefore, each sub-check rule can be labeled based on the estimated earliest batch run start time (i.e. the data ready time of the data block). The labeled label information includes: sub-check rule name, the name of the standard check rule to which it belongs, and the batch run start time. Figure 4 Explain the labeling of sub-check rules. Figure 4 A diagram showing the labels for the sub-check rules.

[0081] In addition, considering that the data source to which the data block belongs may have multiple time zone characteristics, for data blocks from other time zones (non-system time zones), time zone sensitive identification can be performed and corresponding time zone conversion mapping relationships can be configured to ensure the time zone consistency of the time in each tag information.

[0082] After labeling each sub-check rule, you can aggregate the sub-check rules to gather the number of different data-ready times corresponding to each standard check rule. Then, based on enterprise needs or the system's parallel processing capabilities, you can group the sub-check rules by data-ready time. For example, sub-check rules with a data-ready time within one hour can be grouped into the same scheduling group.

[0083] Finally, the number of preset parameters required is determined based on the number of dispatch groups obtained. The same preset parameters are configured for the sub-check rules of the same dispatch group. This means that the same preset parameters can include multiple sub-check rules belonging to the same dispatch group. The preset parameters can take the form of a standard check rule + partial identifier. For example, the preset parameters can be configured as: GRCKJCXX-PART1, GRCKJCXX-PART2.

[0084] Furthermore, in order to facilitate the subsequent matching of preset parameters with sub-check rules, after step S003, the following further steps are included: step S004:

[0085] Step S004: Integrate the preset parameters and the corresponding sub-check rules to obtain a preset check rule table.

[0086] It should be noted that, for ease of management, the system may integrate the sub-check rules and the preset parameters generated thereon and store them in a table as a preset check rule table, so as to facilitate subsequent matching of target check rules based on target input parameters.

[0087] In this embodiment, verification rules are refined to the data block granularity, and parameter configuration enables multiple scheduled batch jobs to mutually exclusive execute all sub-verification rules. This, through rule splitting and parameter configuration, avoids the simultaneous execution of a large number of verification rules, reducing system computing resource utilization and verification time. The use of a pre-set verification rule table improves the flexibility and adaptability of the verification process, reducing development and maintenance costs.

[0088] Based on the first and second embodiments of the present application, in the third embodiment of the present application, the same or similar contents as those in the first and second embodiments can be referred to above and will not be described in detail. Figure 5 , Figure 5 This is a flow chart of the third embodiment of the product data verification method of this application.

[0089] In this embodiment, to specifically illustrate how to trigger the verification operation, step 10 specifically includes: steps S101 to S102:

[0090] Step S101: upon receiving current product data, determining whether the current product data satisfies a data-ready condition of at least one preset parameter.

[0091] It should be noted that the data ready condition is used to determine whether all data blocks of the sub-check rule corresponding to the preset parameters are ready.

[0092] It should be understood that the number of sub-check rules corresponding to the same preset parameter may not be unique. That is, some sub-check rules may correspond to data blocks that have already been transferred to the system in a previous transfer process, some sub-check rules may correspond to data blocks that are in the current product data, and some sub-check rules may correspond to data blocks that have not yet been transferred to the system. The system can combine the current product data and the cached product data to determine the data readiness condition.

[0093] Specifically, when receiving the current product data, it is possible to first determine whether there are any unexecuted preset parameters in the system; if not, an error warning is generated to prompt the user; if so, it is determined whether the current product data and the cached product data include all associated data blocks corresponding to at least one unexecuted preset parameter.

[0094] Step S102: If yes, the preset parameters that meet the data ready condition are determined as target input parameters.

[0095] It should be understood that if the data-ready condition of at least one preset parameter is met, then the preset parameter can be determined as the target incoming parameter; if the data-ready condition of more than one preset parameter is met, then all the preset parameters that meet the data-ready condition can be determined as the target incoming parameter.

[0096] Furthermore, this can be combined with Figure 6 This chapter describes the dynamic generation process of the currently executed script based on the target input parameters. Figure 6 The figure is a flowchart of the verification process based on the currently executed script.

[0097] like Figure 6 As shown, after determining the target input parameters, each sub-check rule in the preset check rule table can be traversed to determine whether the preset parameters of each sub-check rule are consistent with the target input parameters;

[0098] When a sub-check rule corresponding to a preset parameter consistent with the target input parameter is matched, it can be determined as the target check rule, and the rule is called through the dynamic script executor to generate the current execution script to perform the check operation.

[0099] If the sub-check rule corresponding to the preset parameters consistent with the target input parameters is not matched, the preset check rule table is traversed again until a matching item is found; if no matching item is found after the re-traversal, an error warning is generated based on the current product data to prompt the user.

[0100] Based on the dynamic generation process of the above-mentioned current execution script, the corresponding verification rules can be flexibly queried and executed according to the readiness of different data blocks. There is no need to develop customized scripts for each standard verification rule, which reduces development costs and maintenance difficulties and improves the scalability and maintainability of the system.

[0101] Furthermore, during verification, the duration of each verification operation can be monitored in real time and compared against a pre-set threshold. If the duration of a verification operation triggered by a target input parameter exceeds the threshold, or if the verification result output contains errors such as garbled characters or missing information, an abnormality alert can be generated to alert the user.

[0102] It should also be noted that a verification log can be generated based on each verification operation, so as to determine the target input parameters that take a long time or frequently report errors based on the verification log, and then determine the number of sub-verification rules corresponding to the target input parameters and the size of the data blocks involved, generate data block partitioning optimization strategies and parallel sub-verification rule restrictions, etc.

[0103] The data block partitioning optimization strategy may be: for a single data block with a large amount of data and a data block with frequent check anomalies, preset parameters may be directly configured for the corresponding sub-check rules so that only a unique sub-check rule is included under the preset parameters.

[0104] The restriction condition of the parallel sub-check rules can be: when dividing the same scheduling group for each sub-check rule, if the interval condition set is 1 hour, and the number of sub-check rules in a scheduling group obtained based on the interval condition is large (exceeding the preset parallel rule number threshold), then this scheduling group can be divided based on a smaller interval condition, for example, the sub-check rules in the scheduling group can be further divided according to the interval condition of 0.5 hours.

[0105] It should be understood that after each verification result is generated based on the relevant data of the currently submitted product each time, the data blocks with abnormalities can be determined based on the verification result, thereby facilitating the enterprise to handle abnormal data in a timely manner.

[0106] Finally, if the current product data is the last data transmitted to the system within a regulatory cycle, and the verification result generated by the verification job triggered based on the target input parameters shows no abnormal data blocks, the system's cached product data now contains all the relevant data for the currently submitted product that has passed verification. This means that data reports can be generated based on the system's cached product data.

[0107] This embodiment updates cached product data based on the current product data upon receipt; determines whether the updated cached product data includes all associated data blocks corresponding to at least one preset parameter; and if so, determines the preset parameter that meets the data readiness condition as the target input parameter. This allows for automated invocation of verification scripts based on a dynamic script executor, enabling execution of different verification rules at different time periods and phased generation of verification results. This helps companies respond to abnormal data in a timely manner, avoids the traditional problem of excessive computing resource usage caused by executing numerous verification rules simultaneously, reduces system burden, and effectively shortens the execution time of verification operations, thereby ensuring that data reports are submitted to regulatory authorities on time.

[0108] It should be noted that the above examples are only used to understand this application and do not constitute a limitation on the product data verification method of this application. More simple transformations based on this technical concept are all within the scope of protection of this application.

[0109] In addition, this application also provides a product data verification device, referring to Figure 7 , Figure 7 This is a structural block diagram of the first embodiment of the product data verification device of this application; Figure 7 As shown, the device includes:

[0110] The parameter trigger module 701 is configured to determine, upon receiving current product data, target input parameters from among various preset parameters according to the current product data, wherein each of the preset parameters is configured based on a data ready time corresponding to a standard verification rule;

[0111] A rule response module 702 is configured to query a preset verification rule table for a target verification rule corresponding to the target input parameter. The preset verification rule table includes a plurality of sub-verification rules, each of which is obtained by splitting the standard verification rule according to the associated data block corresponding to the standard verification rule;

[0112] The real-time verification module 703 is configured to perform a verification operation on the current product data according to the target verification rule to generate a current verification result.

[0113] Furthermore, the apparatus further comprises: a parameter configuration module 704;

[0114] The parameter configuration module 704 is used to obtain standard verification rules and determine a number of related data blocks based on the standard verification rules; split the standard verification rules based on each of the related data blocks to obtain a number of sub-verification rules; group each of the sub-verification rules according to the data ready time of each of the related data blocks, and generate a number of preset parameters based on the grouping results.

[0115] The parameter configuration module 704 is also used to label each of the sub-check rules according to the data ready time of each associated data block; group the labeled sub-check rules according to the preset time interval conditions to obtain a number of scheduling groups; and perform parameter configuration based on each of the scheduling groups to generate corresponding preset parameters.

[0116] The parameter configuration module 704 is further configured to integrate the preset parameters and the corresponding sub-check rules to obtain a preset check rule table.

[0117] Furthermore, the parameter trigger module 701 is also used to determine whether the current product data meets the data readiness condition of at least one preset parameter when receiving the current product data; if so, determine the preset parameter that meets the data readiness condition as the target input parameter.

[0118] Furthermore, the parameter trigger module 701 is also used to determine whether there are any unexecuted preset parameters when receiving the current product data; if so, it is used to determine whether the data readiness condition of at least one unexecuted preset parameter is met in combination with the current product data and the cached product data.

[0119] Furthermore, the real-time verification module 703 is used to call the target verification rules through the dynamic script executor to generate the current execution script; perform a verification operation on the current product data based on the current execution script, and update the last verification result table according to the operation result to generate the current verification result table.

[0120] This embodiment configures preset parameters based on data readiness time and determines target input parameters upon receiving product data. This allows for timely activation of corresponding verification rules, avoiding the need to wait for all data to be ready, thereby obtaining partial verification results in advance and significantly improving the timeliness of verification work. Furthermore, by splitting standard verification rules into multiple sub-verification rules and storing them in a preset verification rule table, this enables refined management of verification rules, avoiding the problem of excessive computing resources caused by executing a large number of verification rules simultaneously in traditional methods, reducing system burden, and effectively shortening the execution time of verification operations.

[0121] Other embodiments or specific implementations of the product data verification device described in this application can refer to the above-mentioned method embodiments and will not be repeated here.

[0122] The present application also provides a product data verification device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the product data verification method in the above-mentioned embodiment one.

[0123] Reference below Figure 8 , Figure 8 The product data verification device of the present application is a schematic diagram of its structure. The product data verification device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), and fixed terminals such as digital TVs and desktop computers. Figure 8 The product data verification device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0124] like Figure 8As shown, the product data verification device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 1002 or programs loaded from a storage device 1003 into a random access memory (RAM) 1004. RAM 1004 also stores various programs and data required for the operation of the product data verification device. Processing device 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to I / O interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage device 1003 including, for example, a magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 can allow the product data verification device to communicate with other devices wirelessly or wired to exchange data. Although the figure shows a product data verification device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented or provided instead.

[0125] The product data verification device provided in this application utilizes the product data verification method described in the above-mentioned embodiment to solve the technical problem of product data verification. Compared with the prior art, the beneficial effects of the product data verification device provided in this application are the same as those of the product data verification method described in the above-mentioned embodiment. The other technical features of the product data verification device are the same as those disclosed in the above-mentioned embodiment and are not further described here.

[0126] The present application also provides a computer-readable storage medium having computer-readable program instructions (ie, a computer program) stored thereon, wherein the computer-readable program instructions are used to execute the product data verification method in the above embodiment.

[0127] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0128] The computer-readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the aforementioned product data verification method, thereby resolving the technical issues surrounding product data verification. Compared to the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the product data verification method provided in the aforementioned embodiments, and are not further elaborated here.

[0129] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional elements in the process, method, article, or system comprising the element.

[0130] The serial numbers of the above-mentioned embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments. Moreover, they are only some embodiments of the present application and do not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the description and drawings of the present application under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A product data verification method, characterized in that: The method comprises: Upon receiving the current product data, determining the target input parameter from each preset parameter according to the current product data, each preset parameter being configured based on the data ready time corresponding to the standard verification rule; Querying a target verification rule corresponding to the target input parameter in a preset verification rule table, wherein the preset verification rule table includes a plurality of sub-verification rules, each of which is obtained by splitting the standard verification rule according to the associated data block corresponding to the standard verification rule; The current product data is checked according to the target checking rules to generate a current checking result.

2. The method according to claim 1, wherein Before the step of determining the target input parameter from among the preset parameters according to the current product data upon receiving the current product data, the method includes: Obtaining a standard verification rule, and determining a number of associated data blocks according to the standard verification rule; Splitting the standard check rule based on each of the associated data blocks to obtain a plurality of sub-check rules; The sub-check rules are grouped according to the data ready time of each associated data block, and a plurality of preset parameters are generated according to the grouping result.

3. The method according to claim 2, wherein The step of grouping the sub-check rules according to the data ready time of each associated data block and generating a plurality of preset parameters according to the grouping result includes: Labeling each of the sub-check rules according to the data ready time of each of the associated data blocks; Grouping the marked sub-check rules according to preset time interval conditions to obtain a number of scheduling groups; Parameter configuration is performed based on each of the scheduling groups to generate corresponding preset parameters.

4. The method according to claim 3, wherein After the step of configuring parameters based on each of the scheduling groups and generating corresponding preset parameters, the method further includes: The preset parameters and the corresponding sub-check rules are integrated to obtain a preset check rule table.

5. The method according to claim 1, wherein The step of determining the target input parameter from among the preset parameters according to the current product data when the current product data is received includes: Upon receiving the current product data, determining whether the current product data satisfies a data-ready condition of at least one preset parameter; If so, the preset parameters that meet the data ready condition are determined as target input parameters.

6. The method according to claim 5, wherein The step of determining whether the current product data satisfies a data-ready condition of at least one preset parameter upon receiving the current product data includes: Upon receiving the current product data, determining whether there are any unexecuted preset parameters; If so, it is determined whether a data readiness condition of at least one of the unexecuted preset parameters is satisfied by combining the current product data and the cached product data.

7. The method according to claim 1, wherein The step of performing a verification operation on the current product data according to the target verification rule to generate a current verification result includes: The target checking rule is called by the dynamic script executor to generate the current execution script; A verification operation is performed on the current product data based on the current execution script, and the previous verification result table is updated according to the operation result to generate a current verification result table.

8. A product data checking device, characterized in that: The device comprises: A parameter trigger module, configured to, upon receiving current product data, determine target input parameters from among various preset parameters based on the current product data, wherein each of the preset parameters is configured based on a data ready time corresponding to a standard verification rule; a rule response module, configured to query a preset verification rule table for a target verification rule corresponding to the target input parameter, wherein the preset verification rule table includes a plurality of sub-verification rules, each of which is obtained by splitting the standard verification rule according to the associated data block corresponding to the standard verification rule; The real-time verification module is used to perform a verification operation on the current product data according to the target verification rules to generate a current verification result.

9. A product data checking device, characterized in that: The device includes a memory, a processor, and a product data verification program stored in the memory and executable on the processor. When the product data verification program is executed by the processor, the steps of the product data verification method according to any one of claims 1 to 7 are implemented.

10. A storage medium, characterized in that: The storage medium stores a product data verification program, which, when executed by a processor, implements the steps of the product data verification method according to any one of claims 1 to 7.

Images