Data checking method, electronic equipment, device and storage medium

Abstract

The invention provides a data checking method, and relates to the technical field of communication. According to the specific implementation scheme, after a target type of a current to-be-checked data file set is determined, checking files associated with the target type are firstly obtained, then each data file is checked on the basis of the checking files to obtain a first checking result of each data file, and finally the data files are checked on the basis of the multiple first checking results to obtain a second checking result of each data file. And generating a checking result of the data file set. Therefore, the to-be-checked data file is checked based on the checking file, so that the data checking efficiency is improved, conditions are provided for improving the efficiency of locating the northbound data problem, the cost is reduced, and the resource waste is reduced.

Description

Technical Field

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

[0002] In the communication system, the existing technology usually requires manual verification of resource data and performance data to locate the problem data. However, this method is cumbersome, inefficient, and costly when locating the problem, and cannot guarantee the accuracy of the data. Summary of the invention

[0003] The first embodiment of the present application proposes a data verification method, which is characterized by comprising:

[0004] Determine a target type of a data file set to be checked, wherein the data file set includes a plurality of data files;

[0005] obtaining a verification document associated with the target type;

[0006] Based on the verification file, verify each of the data files to obtain a first verification result of each of the data files;

[0007] Based on the plurality of first verification results, a verification result of the data file set is generated.

[0008] Optionally, the acquiring a verification file associated with the target type includes:

[0009] The verification file is generated according to the data specification associated with the target type data.

[0010] Optionally, verifying each of the data files based on the verification file to obtain a first verification result of each of the data files includes:

[0011] Determine, based on the parent-child relationship between the files in the verification file, a first data file corresponding to the parent node in the data file set;

[0012] Based on the first target information associated with the first data file in the verification file, verifying the first data file to obtain a first verification result of the first data file;

[0013] Based on the parent-child relationship, determining a second data file corresponding to the first-level child node of the parent node;

[0014] Based on the second target information associated with the second data file in the verification file, verifying the second data file to obtain a first verification result of the second data file;

[0015] Return to executing the operation of determining the data files to be verified based on the parent-child relationship until a first verification result of each of the data files is obtained.

[0016] Optionally, the process of verifying the data file includes:

[0017] Parsing the target data file to obtain the hierarchical relationship and actual attribute information of each field in the target data file;

[0018] Based on the parent-child relationship between the files in the verification file, the hierarchical relationship of the target data file is verified to obtain a hierarchical verification result of the target data file;

[0019] Based on the target attribute information of each field in the verification file, verify the actual attribute information of the corresponding field in the target data file to obtain the verification result of the field in the target data file;

[0020] Based on the level verification result and the field verification result, a first verification result of the data file is determined.

[0021] Optionally, generating a verification result of the data file set based on the plurality of first verification results includes:

[0022] Each verification item in the plurality of first verification results is traversed to obtain a verification result of the data file set under each verification item.

[0023] The second aspect of the present application provides an electronic device, characterized in that the electronic device includes a memory, a transceiver, and a processor; the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:

[0024] Determine a target type of a data file set to be checked, wherein the data file set includes a plurality of data files;

[0025] obtaining a verification document associated with the target type;

[0026] Based on the verification file, verify each of the data files to obtain a first verification result of each of the data files;

[0027] Based on the plurality of first verification results, a verification result of the data file set is generated.

[0028] Optionally, the processor is further configured to:

[0029] The verification file is generated according to the data specification associated with the target type data.

[0030] Optionally, the processor is specifically configured to:

[0031] Determine, based on the parent-child relationship between the files in the verification file, a first data file corresponding to the parent node in the data file set;

[0032] Based on the first target information associated with the first data file in the verification file, verifying the first data file to obtain a first verification result of the first data file;

[0033] Based on the parent-child relationship, determining a second data file corresponding to the first-level child node of the parent node;

[0034] Based on the second target information associated with the second data file in the verification file, verifying the second data file to obtain a first verification result of the second data file;

[0035] Return to executing the operation of determining the data files to be verified based on the parent-child relationship until a first verification result of each of the data files is obtained.

[0036] Optionally, the processor is specifically configured to:

[0037] Parsing the target data file to obtain the hierarchical relationship and actual attribute information of each field in the target data file;

[0038] Based on the parent-child relationship between the files in the verification file, the hierarchical relationship of the target data file is verified to obtain a hierarchical verification result of the target data file;

[0039] Based on the target attribute information of each field in the verification file, verify the actual attribute information of the corresponding field in the target data file to obtain the verification result of the field in the target data file;

[0040] Based on the level verification result and the field verification result, a first verification result of the target data file is determined.

[0041] Optionally, the processor is specifically configured to:

[0042] Each verification item in the plurality of first verification results is traversed to obtain a verification result of the data file set under each verification item.

[0043] The third aspect of the present application provides a data verification device, which is characterized by comprising:

[0044] A determination module, used to determine a target type of a data file set to be checked, wherein the data file set includes a plurality of data files;

[0045] A first acquisition module, used to acquire a verification file associated with the target type;

[0046] A second acquisition module, configured to verify each of the data files based on the verification file to obtain a first verification result of each of the data files;

[0047] A generation module is used to generate a verification result of the data file set based on multiple first verification results.

[0048] Optionally, the first acquisition module is specifically configured to:

[0049] The verification file is generated according to the data specification associated with the target type data.

[0050] Optionally, the second acquisition module is specifically used to:

[0051] Determine, based on the parent-child relationship between the files in the verification file, a first data file corresponding to the parent node in the data file set;

[0052] Based on the first target information associated with the first data file in the verification file, verifying the first data file to obtain a first verification result of the first data file;

[0053] Based on the parent-child relationship, determining a second data file corresponding to the first-level child node of the parent node;

[0054] Based on the second target information associated with the second data file in the verification file, verifying the second data file to obtain a first verification result of the second data file;

[0055] Return to executing the operation of determining the data files to be verified based on the parent-child relationship until a first verification result of each of the data files is obtained.

[0056] Optionally, the second acquisition module is further used to:

[0057] Parsing the target data file to obtain the hierarchical relationship and actual attribute information of each field in the target data file;

[0058] Based on the parent-child relationship between the files in the verification file, the hierarchical relationship of the target data file is verified to obtain a hierarchical verification result of the target data file;

[0059] Based on the target attribute information of each field in the verification file, verify the actual attribute information of the corresponding field in the target data file to obtain the verification result of the field in the target data file;

[0060] Based on the level verification result and the field verification result, a first verification result of the target data file is determined.

[0061] Optionally, the generating module is specifically used to:

[0062] Each verification item in the plurality of first verification results is traversed to obtain a verification result of the data file set under each verification item.

[0063] The fourth aspect of the present application provides a processor-readable storage medium, which stores a computer program, and the computer program is used to enable the processor to execute the data verification method described in the above embodiment.

[0064] The fifth aspect of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the data verification method described in the above embodiment.

[0065] This application has the following technical effects:

[0066] In the embodiment of the present application, after determining the target type of the current data file set to be verified, first obtain the verification file associated with the target type, then verify each data file based on the verification file to obtain the first verification result of each data file, and finally generate the verification result of the data file set based on multiple first verification results. Thus, by verifying the data files to be verified based on the verification file, the efficiency of data verification is improved, which provides conditions for improving the efficiency of northbound data location problems, reduces costs, and reduces resource waste.

[0067] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0069] Figure 1 A flowchart of a data verification method provided in an embodiment of the present application;

[0070] Figure 2A flowchart of another data verification method provided in an embodiment of the present application;

[0071] Figure 3 A schematic diagram of the parent-child relationship between the files in the verification file provided in the embodiment of the present application;

[0072] Figure 4 A flowchart of another data verification method provided in an embodiment of the present application;

[0073] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0074] Figure 6 A schematic diagram of the structure of a data verification device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0075] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0076] The data verification method, electronic device, apparatus and storage medium of the embodiments of the present application are described below with reference to the accompanying drawings.

[0077] The data verification method provided in the embodiment of the present application can be used for verification of any type of data. The data verification method provided in the embodiment of the present application is described in detail below using northbound data verification as an example.

[0078] In the prior art, northbound data is usually checked manually, but this method cannot guarantee the accuracy of the data. In addition, when problems occur in northbound data, it is necessary to locate the problematic data manually, which leads to cumbersome processes, low efficiency, and a waste of a lot of manpower and material resources.

[0079] In response to the above problems, the present application proposes a data verification method, which generates a corresponding verification file based on the data specification associated with the northbound data type, and then verifies the northbound data file based on the verification file, thereby improving the efficiency of locating problems in the northbound data file, reducing resource waste, and ensuring data accuracy.

[0080] Figure 1 A flowchart of a data verification method provided in an embodiment of the present application.

[0081] The data verification method provided in the embodiment of the present application can be applied to a network management system, for example, a network management system (Network Management System, NMS), an operation and maintenance center (Operations Maintenance Center, OMC), etc.

[0082] like Figure 1 As shown, the data verification method comprises:

[0083] Step 101 : determining the target type of the data file set to be checked, wherein the data file set includes a plurality of data files.

[0084] That is, for northbound data, the target type of the northbound data file set to be checked can be determined, wherein the northbound data file set includes multiple northbound data files.

[0085] The target type of the northbound data file set is the type to which the northbound data file set belongs, which is determined according to the northbound data files included in the northbound data file set. For example, the target type of the northbound data file set may be a northbound resource data file set, or may also be a northbound performance data file set, etc., which is not limited in this application.

[0086] It should be noted that the type of a northbound data file can be determined based on the type of data it contains. If the data contained in the northbound data file is resource data, the corresponding northbound data file can be considered to be a northbound resource data file. If the data contained in the northbound data file is performance data, the corresponding northbound data file can be considered to be a northbound performance data file. This application does not limit this.

[0087] Step 102, obtaining a verification file associated with the target type.

[0088] Among them, the verification file is a file used to verify the northbound data file, which may include any type of file such as table files, graphic files, etc., and this application does not limit this.

[0089] In some possible implementation forms, a verification file may be generated according to a data specification associated with the target type data.

[0090] It should be noted that data specifications are defined standard requirements for regulating northbound data, and this application does not limit this.

[0091] In this application, when the target type of the northbound data file set is a resource data file set, a resource data verification file can be generated based on the data specification associated with the resource data. When the target type of the northbound data file set is a performance data file set, a performance data verification file can be generated based on the data specification associated with the performance data.

[0092] For example, if the northbound data file set is a resource data file set, then a resource data verification file can be generated based on data specifications associated with the resource data, as shown in Table 1, which is a table in the northbound resource data verification file.

[0093] Table 1

[0094]

[0095] In Table 1, the attribute code is the number corresponding to the attribute defined in the template. Importance is the importance level of the field in each resource data specification, which is divided into Class A, Class B, Class C, Class CA, Class CB, and Class CC. For example, according to the specification requirements, the integrity of Class A fields or required fields shall not be less than 100%, and the support rate of Class B fields shall not be less than 90%. Data type is the data type defined for the resource field. Object is the resource of the wireless network, which is the name of the spatial granularity defined in the resource data specification, such as NRCellDUPhysical (NR wireless physical cell DU resource object). Value range is the value range defined for the resource field. Unit is the unit defined for the resource field.

[0096] If the northbound data file set is a performance data file set, then a performance data verification file can be generated based on the data specification associated with the performance data and the northbound derived counter formula, as shown in Table 2 and Table 3, respectively. Table 2 is a table of northbound derived counter formulas, and Table 3 is a table in the northbound performance data verification file.

[0097] Table 2

[0098]

[0099] Table 3

[0100]

[0101] In Table 3, importance refers to the importance level of the fields in each performance indicator specification, which is divided into Class A, Class B, Class C, Class CA, Class CB, and Class CC. For example, according to the specification requirements, the integrity of Class A fields or mandatory fields shall not be less than 100%, and the support rate of Class B fields shall not be less than 90%. Data type refers to the data type defined by the performance indicator. Object refers to the network element subclass of performance data, which is the name of the spatial granularity defined in the performance data specification, such as NRCellDUPhysical (NR wireless physical cell DU resource object). Value range refers to the value range defined by the performance indicator. Unit refers to the unit defined by the performance indicator. Time granularity refers to the period of the reporting file of the spatial granularity name to which the performance indicator belongs.

[0102] In this application, based on the northbound derived counter mapping formula, the northbound performance indicator can be calculated and the standard value can be generated through the mapping formula. The value range in the performance data verification file table is the only standard for measuring whether the standard value reporting is accurate.

[0103] Step 103: verify each data file based on the verification file to obtain a first verification result of each data file.

[0104] That is, for northbound data, each northbound data file may be verified based on the verification file to obtain a first verification result of each northbound data file.

[0105] The first verification result is a result obtained after verifying the data contained in each northbound data file.

[0106] In this application, based on the verification file, when verifying each northbound data file, different types of content such as the file content, file format, file naming, hierarchical relationship between files, integrity, compliance, value range, etc. of the northbound data file can be verified, and this application does not limit this.

[0107] Among them, field integrity is to check whether the field is missing, whether the field name is correct, and whether all fields are reported according to the fields in the data specification. Field compliance is to check whether the value of the field meets the data type defined in the data specification, whether the value is empty, and whether the value is 0. If any of them is not met, the corresponding field can be considered non-compliant.

[0108] Step 104: Generate a verification result of the data file set based on the multiple first verification results.

[0109] That is to say, for the northbound data, a verification result of the northbound data file set can be generated based on multiple first verification results.

[0110] The verification result is the verification result obtained after verifying the northbound data file set.

[0111] In some possible implementation forms, each verification item in the plurality of first verification results may be traversed to obtain the verification result of the northbound data file set under each verification item.

[0112] The verification items are items included in the verification results of the northbound data file. For example, the verification items can be any items such as the number of missing fields, field completeness rate, field compliance rate, field anomaly, etc. in the northbound data file, and this application does not limit this.

[0113] In the present application, when the verification results of the northbound data file set are generated based on multiple first verification results, a verification report for the northbound data file set can be generated, and the verification results corresponding to each verification item can be stored in the corresponding 6 sheet pages in the Excel table.

[0114] For example, the first sheet 1 is the overall pass rate page of the verification results. The results record the test pass status of each type of field attribute in the northbound data file set, as shown in Table 4, which is the overall pass rate table of the verification results of the northbound data file.

[0115] Table 4

[0116]

[0117] In Table 4, the number of missing fields includes situations such as incorrect field names and non-existent fields. Field completeness rate = 1-number of missing fields / total number of test fields. Number of non-compliant fields: If the field value data type is inconsistent with that in the verification file, the field value is empty, or the field value is 0, the field can be considered non-compliant if any of these situations occurs. If the same field is non-compliant in multiple situations, deduplication is required. Field compliance rate = 1-number of non-compliant fields / total number of test fields. Number of inaccurate fields: Check whether the values ​​of attributes and indicators in the northbound resource data file and the northbound performance data file meet the value range defined in the data specification. If they are not within the value range, the field is judged to be inaccurate. Field accuracy rate = 1-number of inaccurate fields / total number of test fields.

[0118] The second sheet 2 is the missing field number page. The number of fields for each type of data in the statistical data specification is checked. The actual number of fields in the northbound data file is checked. If the number of fields is inconsistent with the number of fields specified in the data specification, if there is a missing field, the specific missing field is on the field exception details sheet 3 page. As shown in Table 5, Table 5 is a table of missing fields in the northbound data file. Among them, the files with the file name suffix ".xml" in Table 5 are resource data files, and the files with the file name suffix ".csv" are performance data files.

[0119] Table 5

[0120]

[0121] The third sheet 3 is the abnormal details page of the field. The detailed error information will be output in the field verification column. In addition, there are also file name verification results, file format verification results, object name verification results, time format in the public field, and rmUID format verification results for each file. As shown in Table 6, Table 6 is a table of abnormal details of the fields of the northbound data file. Among them, rmUID is the network-wide unique identifier (Resource Management Universal Identifier, rmUID) of the network resource object.

[0122] Table 6

[0123]

[0124] The fourth sheet 4 page is the field 0 value verification status page. It searches for the value of the same field in all records of the northbound data file. If all records of the field have a value of 0, it can be marked in red, indicating that there is a problem with the field. The number of files can be files of multiple time granularities. As shown in Table 7, Table 7 is a table of field 0 value verification status of the northbound data file.

[0125] Table 7

[0126]

[0127] In Table 7, SCSSpecificCarrierListDL is a resource field, and RRU.RachPreambleRcvd is a performance indicator.

[0128] The fifth sheet 5 page is the field null value verification page, which can include the actual value and the number of non-null values. If a value of a field is null, it can be marked in red, indicating that there is a problem with the field. As shown in Table 8, Table 8 is the field null value verification table of the northbound data file.

[0129] Table 8

[0130]

[0131] In Table 8, the performance file NRCellDUPhysical, the counter number R4100_001 in the mapping formula is the northbound derived counter, the corresponding formula R1051_001 is the original counter indicator, and the data reported to the network management system (NMS) is the standard value generated after calculation. The indicator name RRU.RachPreambleRcvd reported by the NMS is RRU.RachPreambleRcvd=0, which does not meet the value range in the performance data verification file. Therefore, the number of inaccurate field statistics is 1, which can be marked as failed.

[0132] In the resource file NRCellDUPhysical, the data type of the field SCSSpecificCarrierListDL defined in the resource data verification file is a structure, which consists of three fields. See the corresponding value ranges in Table 1 for details. Therefore, the actual value of the field SCSSpecificCarrierListDL={(0,KHZ40,60)} reported by the NMS meets the definition of the structure. Then, the value ranges of the three field values ​​in the structure are checked. If the definition of the value range is met, it can be marked as passed.

[0133] The sixth sheet 6 page is a page for checking file resources and performance object information, which may include information such as file size, object name, number of fields, number of file records, etc. As shown in Table 9, Table 9 is a table of file resources and performance object information for northbound data file verification.

[0134] Table 9

[0135]

[0136] Usually, when checking the northbound performance data file, it is currently necessary to manually check the northbound performance data. However, this method is cumbersome and inefficient when locating problems. It is not suitable as a positioning method in daily maintenance. Every time a problem occurs, it is necessary to first check the data on the network element side, then check the data in the operation and maintenance center database, and then compare the parameter values, which increases the operating cost and wastes a lot of manpower and material resources.

[0137] In response to the above problems, this application generates a performance data verification file based on the data specification associated with the performance data and the northbound derived counter formula. The data to be verified can be directly verified based on the data verification file to determine whether the indicators tested by the network management system are correct based on the verification results. In addition, the verification results can also be used as a standard for reference when the network management system and the operation and maintenance center locate problems, thereby improving the efficiency of locating problems in the northbound data file and reducing operating costs and resource waste.

[0138] In the embodiment of the present application, after determining the target type of the current data file set to be verified, first obtain the verification file associated with the target type, then verify each data file based on the verification file to obtain the first verification result of each data file, and finally generate the verification result of the data file set based on multiple first verification results. Thus, by verifying the data files to be verified based on the verification file, the efficiency of data verification is improved, which provides conditions for improving the efficiency of locating northbound data positioning problems, reduces costs, and reduces resource waste.

[0139] Figure 2 A flowchart of a data verification method provided in an embodiment of the present application.

[0140] like Figure 2 As shown, the data verification method includes:

[0141] Step 201 : determining a target type of a northbound data file set to be checked, wherein the northbound data file set includes a plurality of northbound data files.

[0142] Step 202, obtaining a verification file associated with the target type.

[0143] Among them, the specific implementation forms of steps 201 to 202 can refer to the detailed description of other embodiments of the present application and will not be repeated here.

[0144] Step 203: Based on the parent-child relationship between the files in the verification file, determine the first northbound data file corresponding to the parent node in the northbound data file set.

[0145] In this application, the parent-child relationship between the files in the verification file can be presented in the form of a graph, such as Figure 3 As shown, Figure 3 This is a schematic diagram of the parent-child relationship between the files in the verification file provided in the embodiment of the present application. Figure 3 As shown, the node corresponding to file A is the parent node, and file A 11 Corresponding nodes and files A 12 The corresponding nodes are all first-level child nodes of the parent node. File A 111 、File A 112 、File A 113 , and file A 114 The corresponding nodes are all second-level child nodes of the parent node.

[0146] It should be noted that in Figure 3 The file names corresponding to the files shown in A, A 11The above are all schematic illustrations. The specific file name can be determined according to the actual file name corresponding to the northbound data file to be verified, and this application does not limit this.

[0147] The first northbound data file is a parent northbound data file in the northbound data file set.

[0148] In the present application, after obtaining the verification file associated with the target type, the parent northbound data file in the northbound data file set can be determined based on the parent-child relationship between the northbound data files in the verification file.

[0149] Step 204: verify the first northbound data file based on the first target information associated with the first northbound data file in the verification file to obtain a first verification result of the first northbound data file.

[0150] The first target information is the target information in the verification file used to verify the first northbound data file. For example, the first target information can be the target attribute of a field in the first northbound data file, the target parent-child relationship associated with the first northbound data file, etc., which is not limited in this application.

[0151] In the present application, after the first target information associated with the first northbound data file is obtained, the first northbound data file may be verified to obtain a first verification result of the first northbound data file.

[0152] Step 205: Based on the parent-child relationship, determine the second northbound data file corresponding to the first-level child node of the parent node.

[0153] The first-level child node is a node that has a parent-child inheritance relationship with the parent node.

[0154] The second northbound data file is a northbound data file having a parent-child inheritance relationship with the first northbound data file.

[0155] In the present application, based on the parent-child relationship between the files in the verification file, the corresponding first-level child node can be determined based on the parent node, thereby determining the second northbound data file.

[0156] Step 206: Verify the second northbound data file based on the second target information associated with the second northbound data file in the verification file to obtain a first verification result of the second northbound data file.

[0157] The second target information is the target information in the verification file used to verify the second northbound data file. For example, the second target information can be the target attribute of the field in the second northbound data file, the target parent-child relationship associated with the second northbound data file, etc., which is not limited in this application.

[0158] In the present application, after determining the second target information associated with the second northbound data file, the second northbound data file may be verified based on the second target information to obtain a first verification result of the second northbound data file.

[0159] Step 207 , returning to perform the operation of determining the northbound data file to be verified based on the parent-child relationship, until a first verification result of each northbound data file is obtained.

[0160] In the present application, after obtaining the verification results corresponding to the first northbound data file and the second northbound data file respectively, if there are still northbound data files to be verified in the current northbound data file set to be verified, the northbound data files to be verified can continue to be verified based on the parent-child relationship until the verification results of each northbound data file in the northbound data file set are obtained.

[0161] Step 208: Generate a verification result of the northbound data file set based on the multiple first verification results.

[0162] The specific implementation form of step 208 can refer to the detailed description of other embodiments of the present application and will not be repeated here.

[0163] In an embodiment of the present application, after determining the target type of the current northbound data file set to be verified, first obtain the verification file associated with the target type, and based on the parent-child relationship between each file in the verification file, determine the first northbound data file corresponding to the parent node in the northbound data file set, then verify the first northbound data file based on the first target information associated with the first northbound data file in the verification file to obtain the first verification result of the first northbound data file, then determine the second northbound data file corresponding to the first-level child node of the parent node based on the parent-child relationship, verify the second northbound data file based on the second target information associated with the second northbound data file in the verification file to obtain the first verification result of the second northbound data file, and finally return to perform the operation of determining the northbound data file to be verified based on the parent-child relationship until the first verification result of each northbound data file is obtained. Thus, based on the target information associated with the northbound data file to be verified in the verification file, the northbound data file to be verified is verified, thereby reducing the cost of data verification and improving efficiency.

[0164] Figure 4 A flowchart of a data verification method provided in an embodiment of the present application.

[0165] like Figure 4 As shown, the process of verifying the data file in the data verification method includes:

[0166] Step 401 , parse the target northbound data file to obtain the hierarchical relationship and actual attribute information of each field in the target northbound data file.

[0167] The target northbound data file is a northbound data file to be verified in the northbound data file set.

[0168] The hierarchical relationship is the parent-child relationship between the target northbound data file and other northbound data files.

[0169] In this application, the corresponding hierarchical relationship can be obtained by parsing the device identification name (Distinguished Name, Dn) information of the target northbound data file. Among them, the Dn information usually includes parent class objects and child class objects. By parsing the Dn information, the corresponding hierarchical relationship can be determined. This application does not limit this process.

[0170] The actual attribute information of the field is the actual value of any attribute such as the type, name, and value of the field contained in the target northbound data file.

[0171] Step 402 , based on the parent-child relationship between the files in the verification file, the hierarchical relationship of the target northbound data file is verified to obtain a hierarchical verification result of the target northbound data file.

[0172] The hierarchical verification result is the result of the hierarchical relationship verification of the target northbound data file, and the hierarchical verification result can be represented in any implementation form. For example, the hierarchical verification result can be "passed" or "failed", etc., and this application does not limit this.

[0173] In the present application, based on the parent-child relationship between each file in the verification file, when verifying the hierarchical relationship of the target northbound data file, first determine the node corresponding to the target northbound data file. If the node corresponding to the target northbound data file is a parent node, the target information of the target data file can be read and the corresponding hierarchical relationship information can be saved. If the node corresponding to the target northbound data file is a child node, it can be verified whether there is a parent data file for the target northbound data file. If not, the hierarchical verification result of the target northbound data file is failed. If it exists, the hierarchical relationship corresponding to the target northbound data file is recorded.

[0174] It should be noted that after verifying the hierarchical relationship of the target northbound data file, the target northbound data file and the hierarchical verification result may be associated and stored in sheet 3 of the exception details page.

[0175] Step 403 , based on the target attribute information of each field in the verification file, the actual attribute information of the corresponding field in the target northbound data file is verified to obtain the verification result of the field in the target northbound data file.

[0176] The target attribute information of the field is any attribute such as the type, name, value range, etc. of the field defined in the verification file, and this application does not limit this.

[0177] It should be noted that the types of fields defined in the verification file may include any type such as Boolean, enumeration, integer, structure list, string, string list, etc., and this application does not limit this. Among them, for fields of Boolean type, it is possible to check whether the field value is correct; for fields of enumeration type, it is possible to check whether the field is within the value range defined in the mapping formula; for fields of real number type, it is possible to check whether the field value is within the value range defined in the mapping formula; for fields of integer type, it is possible to check whether the field value is within the value range defined in the mapping formula; for fields of structure list type, it is possible to check whether the field value conforms to the structure type definition, and whether the value attribute is the attribute defined in the mapping formula, and check the attribute value according to the value type; for fields of string type, it is possible to check the length of the string and the special characters it contains; for fields of string list type, it is possible to check whether the field value conforms to the string list type definition, and the attribute value satisfies the string.

[0178] In the present application, based on the target attribute information of each field in the verification file, when verifying the actual attribute information of the corresponding field in the target northbound data file, the target northbound data file can be analyzed line by line, and the actual attribute value of the corresponding field in the target northbound data file can be compared and verified with the target attribute value of the corresponding field in the verification file. If the actual attribute value of the field passes the verification, the actual attribute value of the corresponding field can be written into the object, and the status is set to "passed". Then the data stored in the object is written into the sheet5 table and can be marked as passed. Attribute values ​​that do not meet the value range are written and marked as failed, and field exception information is given.

[0179] Step 404: Determine a first verification result of the target northbound data file based on the level verification result and the field verification result.

[0180] In the present application, after obtaining the level verification result and the field verification result of the target northbound data file, the first verification result of the target northbound data file can be determined based on the level verification result and the field verification result.

[0181] In an embodiment of the present application, after determining the target type of the current northbound data file set to be verified, first obtain a verification file associated with the target type, parse the target northbound data file, obtain the hierarchical relationship in the target northbound data file and the actual attribute information of each field, then verify the hierarchical relationship of the target northbound data file based on the parent-child relationship between the files in the verification file to obtain the hierarchical verification result of the target northbound data file, and verify the actual attribute information of the corresponding field in the target northbound data file based on the target attribute information of each field in the verification file to obtain the verification result of the field in the target northbound data file, and finally determine the first verification result of the target northbound data file based on the hierarchical verification result and the verification result of the field. Thus, by verifying the target northbound data file based on the parent-child relationship between the files in the verification file and the target attribute relationship of each field, the verification result of the target northbound data file is determined, thereby improving the accuracy of data verification.

[0182] In order to implement the above embodiment, the present application also provides an electronic device, Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0183] like Figure 5 As shown, the electronic device 500 includes: a transceiver 501, a processor 502, and a memory 503;

[0184] The transceiver 501 is used to send and receive data under the control of the processor 502.

[0185] Among them, Figure 5 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 502 and memory represented by memory 503. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 501 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 502 is responsible for managing the bus architecture and general processing, and the memory 503 may store data used by the processor 502 when performing operations.

[0186] The processor 502 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0187] The processor 502 is used to call the computer program stored in the memory and perform the following operations:

[0188] Determine a target type of a data file set to be checked, wherein the data file set includes a plurality of data files;

[0189] Get the verification file associated with the target type;

[0190] Based on the verification file, verify each data file to obtain a first verification result of each data file;

[0191] Based on the plurality of first verification results, a verification result of the data file set is generated.

[0192] Optionally, the processor 502 is further configured to:

[0193] Generate verification files based on the data specifications associated with the target type data.

[0194] Optionally, the processor 502 is specifically configured to:

[0195] Determine the first data file in the data file set corresponding to the parent node based on the parent-child relationship between the files in the verification file;

[0196] Based on first target information associated with the first data file in the verification file, verifying the first data file to obtain a first verification result of the first data file;

[0197] Based on the parent-child relationship, determine the second data file corresponding to the first-level child node of the parent node;

[0198] Based on the second target information associated with the second data file in the verification file, verifying the second data file to obtain a first verification result of the second data file;

[0199] Return to perform the operation of determining the data file to be verified based on the parent-child relationship until the first verification result of each data file is obtained.

[0200] Optionally, the processor 502 is specifically configured to:

[0201] Parse the target data file to obtain the hierarchical relationship and actual attribute information of each field in the target data file;

[0202] Based on the parent-child relationship between each file in the verification file, the hierarchical relationship of the target data file is verified to obtain the hierarchical verification result of the target data file;

[0203] Based on the target attribute information of each field in the verification file, the actual attribute information of the corresponding field in the target data file is verified to obtain the verification result of the field in the target data file;

[0204] Based on the level verification result and the field verification result, a first verification result of the target data file is determined.

[0205] Optionally, the processor 502 is specifically configured to:

[0206] Each verification item in the plurality of first verification results is traversed to obtain a verification result of the data file set under each verification item.

[0207] It should be noted that the electronic device provided in the embodiment of the present application can achieve the above Figure 1 , Figure 2 , Figure 4 All the method steps implemented in the method embodiment can achieve the same technical effect, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0208] In order to implement the above embodiment, the present application also proposes a data verification device. Figure 6 A schematic diagram of the structure of a data verification device provided in an embodiment of the present application.

[0209] like Figure 6 As shown, the data verification device 600 includes:

[0210] A determination module 601 is used to determine a target type of a data file set to be checked, wherein the data file set includes a plurality of data files;

[0211] A first acquisition module 602 is used to acquire a verification file associated with a target type;

[0212] A second acquisition module 603 is used to verify each data file based on the verification file to obtain a first verification result of each data file;

[0213] The generating module 604 is used to generate a verification result of the data file set based on the multiple first verification results.

[0214] Optionally, the first acquisition module 602 is specifically configured to:

[0215] Generate verification files based on the data specifications associated with the target type data.

[0216] Optionally, the second acquisition module 603 is specifically configured to:

[0217] Determine the first data file in the data file set corresponding to the parent node based on the parent-child relationship between the files in the verification file;

[0218] Based on first target information associated with the first data file in the verification file, verifying the first data file to obtain a first verification result of the first data file;

[0219] Based on the parent-child relationship, determine the second data file corresponding to the first-level child node of the parent node;

[0220] Based on the second target information associated with the second data file in the verification file, verifying the second data file to obtain a first verification result of the second data file;

[0221] Return to perform the operation of determining the data file to be verified based on the parent-child relationship until the first verification result of each data file is obtained.

[0222] Optionally, the second acquisition module 603 is further configured to:

[0223] Parse the target data file to obtain the hierarchical relationship and actual attribute information of each field in the target data file;

[0224] Based on the parent-child relationship between the files in the verification file, the hierarchical relationship of the target data file is verified to obtain the hierarchical verification result of the target data file;

[0225] Based on the target attribute information of each field in the verification file, the actual attribute information of the corresponding field in the target data file is verified to obtain the verification result of the field in the target data file;

[0226] Based on the level verification result and the field verification result, a first verification result of the target data file is determined.

[0227] Optionally, the generating module 604 is specifically configured to:

[0228] Each verification item in the plurality of first verification results is traversed to obtain a verification result of the data file set under each verification item.

[0229] It should be noted that the data verification device provided in the embodiment of the present application can achieve the above Figure 1 , Figure 2 , Figure 4 All the method steps implemented in the method embodiment can achieve the same technical effect, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0230] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0231] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network side device, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0232] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0233] On the other hand, an embodiment of the present application further provides a processor-readable storage medium, which stores a computer program, and the computer program is used to enable the processor to execute the steps of all method embodiments of the present application.

[0234] Among them, the above-mentioned processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0235] On the other hand, an embodiment of the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of all the method embodiments of the present application.

[0236] In the description of this specification, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0237] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A data verification method, characterized in that: include: Determine a target type of a data file set to be checked, wherein the data file set includes a plurality of data files; obtaining a verification document associated with the target type; Based on the verification file, verify each of the data files to obtain a first verification result of each of the data files; Based on the plurality of first verification results, a verification result of the data file set is generated.

2. The method according to claim 1, characterized in that The obtaining of the verification file associated with the target type includes: The verification file is generated according to the data specification associated with the target type data.

3. The method according to claim 1, characterized in that The verifying each of the data files based on the verification file to obtain a first verification result of each of the data files includes: Determine, based on the parent-child relationship between the files in the verification file, a first data file corresponding to the parent node in the data file set; Based on the first target information associated with the first data file in the verification file, verifying the first data file to obtain a first verification result of the first data file; Based on the parent-child relationship, determining a second data file corresponding to the first-level child node of the parent node; Based on the second target information associated with the second data file in the verification file, verifying the second data file to obtain a first verification result of the second data file; Return to executing the operation of determining the data files to be verified based on the parent-child relationship until a first verification result of each of the data files is obtained.

4. The method according to any one of claims 1 to 3, characterized in that: The process of verifying data files includes: Parsing the target data file to obtain the hierarchical relationship and actual attribute information of each field in the target data file; Based on the parent-child relationship between the files in the verification file, the hierarchical relationship of the target data file is verified to obtain a hierarchical verification result of the target data file; Based on the target attribute information of each field in the verification file, verify the actual attribute information of the corresponding field in the target data file to obtain the verification result of the field in the target data file; Based on the level verification result and the field verification result, a first verification result of the target data file is determined.

5. The method according to any one of claims 1 to 3, characterized in that: Generating a verification result of the data file set based on the plurality of first verification results includes: Each verification item in the plurality of first verification results is traversed to obtain a verification result of the data file set under each verification item.

6. An electronic device, characterized in that: The electronic device includes a memory, a transceiver, and a processor; the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Determine a target type of a data file set to be checked, wherein the data file set includes a plurality of data files; obtaining a verification document associated with the target type; Based on the verification file, verify each of the data files to obtain a first verification result of each of the data files; Based on the plurality of first verification results, a verification result of the data file set is generated.

7. The electronic device according to claim 6, characterized in that: The processor is further configured to: The verification file is generated according to the data specification associated with the target type data.

8. The electronic device according to claim 6, characterized in that: The processor is specifically used for: Determine, based on the parent-child relationship between the files in the verification file, a first data file corresponding to the parent node in the data file set; Based on the first target information associated with the first data file in the verification file, verifying the first data file to obtain a first verification result of the first data file; Based on the parent-child relationship, determining a second data file corresponding to the first-level child node of the parent node; Based on the second target information associated with the second data file in the verification file, verifying the second data file to obtain a first verification result of the second data file; Return to executing the operation of determining the data files to be verified based on the parent-child relationship until a first verification result of each of the data files is obtained.

9. The electronic device according to any one of claims 6 to 8, characterized in that: The processor is specifically used for: Parsing the target data file to obtain the hierarchical relationship and actual attribute information of each field in the target data file; Based on the parent-child relationship between the files in the verification file, the hierarchical relationship of the target data file is verified to obtain a hierarchical verification result of the target data file; Based on the target attribute information of each field in the verification file, verify the actual attribute information of the corresponding field in the target data file to obtain the verification result of the field in the target data file; Based on the level verification result and the field verification result, a first verification result of the target data file is determined.

10. The electronic device according to any one of claims 6 to 8, characterized in that: The processor is specifically used for: Each verification item in the plurality of first verification results is traversed to obtain a verification result of the data file set under each verification item.

11. A data verification device, characterized in that: include: A determination module, used to determine a target type of a data file set to be checked, wherein the data file set includes a plurality of data files; A first acquisition module, used to acquire a verification file associated with the target type; A second acquisition module, configured to verify each of the data files based on the verification file to obtain a first verification result of each of the data files; A generation module is used to generate a verification result of the data file set based on multiple first verification results.

12. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute any one of the methods of claims 1-5.

Images