Method and system for cross-source field alignment verification of new energy vehicle product announcement parameters

Abstract

The application relates to the technical field of data processing, and discloses a new energy automobile product announcement parameter cross-source field alignment verification method and system. The method comprises the following steps: obtaining an object identifier, an object type, a vehicle model identifier, a current rule version identifier, enterprise filling data and a new energy automobile product announcement parameter source file of a to-be-verified object; determining a corresponding compliance rule package according to the object type and the current rule version identifier; determining a target announcement parameter region from the new energy automobile product announcement parameter source file according to the compliance rule package, and extracting an announcement parameter original value; determining a corresponding relationship between the enterprise filling parameter value and the announcement parameter original value, and normalizing the two; and performing consistency comparison on the normalized enterprise filling parameter value and the announcement parameter original value to generate a parameter verification record. The application can reduce parameter verification misjudgment caused by cross-source field and data format differences, and improve the traceability and reviewability of the verification result.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method and system for cross-source field alignment verification of parameters in new energy vehicle product announcements.

[0002] The method can be applied to scenarios involving self-inspection, random inspection, and rectification review of compliance documents submitted by new energy vehicle manufacturers, core component suppliers, or new energy vehicle operators. Background Technology

[0003] Compliance documents for new energy vehicles typically include parameters submitted by the company, scanned documents or PDF files of product announcement parameter pages, test reports, production consistency records, and supporting documents for rectification. Field names, units of measurement, numerical representation formats, and document organization may differ between different data sources, and the same compliance indicator for the same vehicle model may be presented in different locations in different documents.

[0004] When directly comparing field names or raw strings, issues can easily arise such as mismatched fields, unit differences leading to misjudgments, numerical format differences leading to misjudgments, and the inability to trace the target parameter back to its specific location in the source file. Furthermore, when rules are updated, the version of the rule upon which historical verification results were based may become uncertain.

[0005] Therefore, a data processing method is needed that can determine target parameters based on vehicle model identifiers, compliance indicator identifiers, and rule versions, perform field alignment and normalization comparison of parameters from different sources, and generate structured verification records that can be associated with the target area of ​​the source file. Summary of the Invention

[0006] This application provides a method and system for cross-source field alignment verification of parameters in new energy vehicle product announcements. It can perform field alignment, normalization processing, and consistency comparison between parameters submitted by enterprises and those in the announcements, and generate traceable parameter verification records.

[0007] Firstly, this application provides a method for verifying cross-source field alignment of parameters in new energy vehicle product announcements, including: Obtain the object identifier, object type, vehicle model identifier, current rule version identifier, enterprise-submitted data, and source file of new energy vehicle product announcement parameters corresponding to the vehicle model identifier of the object to be verified; Based on the object type and the current rule version identifier, determine the compliance rule package corresponding to the object to be verified from the pre-built compliance knowledge base; According to the compliance rule package, the target announcement parameter area corresponding to the vehicle model identifier and the compliance indicators to be verified is determined from the source file of the new energy vehicle product announcement parameters, and the original value of the announcement parameter is extracted from the target announcement parameter area; The correspondence between the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters in the enterprise-reported data is determined according to the compliance rule package, and the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters are normalized. Based on the compliance rule package, a consistency comparison is performed between the normalized enterprise-reported parameter values ​​and the original normalized announcement parameter values ​​to generate parameter verification records. The parameter verification records include at least the object identifier, vehicle model identifier, compliance indicator identifier, rule version identifier, and comparison status.

[0008] In some examples, the construction of the compliance knowledge base includes: Set up corresponding compliance rule packages according to different object types, and set rule version identifiers for the compliance rule packages; When compliance rules are updated, a new version of the rules is generated based on the updated compliance rules, while the previous version of the compliance rules is retained.

[0009] In some examples, determining the target announcement parameter region corresponding to the vehicle model identifier and the compliance indicators to be verified from the source file of the new energy vehicle product announcement parameters according to the compliance rule package, and extracting the original values ​​of the announcement parameters from the target announcement parameter region, includes: The layout of the source file of the new energy vehicle product announcement parameters is parsed to determine the parameter area containing the vehicle model identifier and the compliance indicators; The parameter region is subjected to OCR recognition to extract the parameter field name, parameter value and unit of measurement, and the page number, coordinates or region identifier of the parameter region in the source file is recorded; The extracted parameter fields are matched according to the compliance indicator identifier to obtain the original value of the announcement parameter and its corresponding source file location information.

[0010] In some examples, determining the correspondence between the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters in the enterprise-reported data according to the compliance rule package, and normalizing the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters, includes: Based on the compliance indicator identifiers, enterprise reporting field identifiers, announcement parameter field identifiers, and field mapping rules stored in the compliance rule package, determine the field correspondence between the enterprise reporting parameter values ​​and the original values ​​of the announcement parameters; According to the field mapping rules, the field name unification, unit of measurement conversion, numerical precision unification and character format standardization are performed on the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters, respectively, to obtain the normalized enterprise-reported parameter values ​​and the normalized original values ​​of the announcement parameters.

[0011] In some examples, the process of performing a consistency comparison between the normalized enterprise-reported parameter values ​​and the original normalized announcement parameter values, based on the compliance rule package, and generating parameter verification records includes: Obtain the comparison method, allowable deviation range, and judgment rule corresponding to the compliance indicator identifier in the compliance rule package; Based on the correspondence between the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters, the normalized enterprise-reported parameter values ​​and the normalized original values ​​of the announcement parameters are compared field by field. When the normalized enterprise-reported parameter value and the normalized announcement parameter original value meet the judgment rule, the verification result of the corresponding compliance indicator is determined to be consistent; when the normalized enterprise-reported parameter value and the normalized announcement parameter original value do not meet the judgment rule, the verification result of the corresponding compliance indicator is determined to be inconsistent. For compliance indicators with inconsistent verification results, a verification record is generated that includes vehicle model identifier, compliance indicator identifier, normalized enterprise-reported parameter value, normalized original value of announcement parameter, difference information, and the page number, coordinates, or area identifier of the target announcement parameter area in the source file of the new energy vehicle product announcement parameter.

[0012] In some examples, before extracting the original values ​​of the announcement parameters from the source file of the new energy vehicle product announcement parameters, the process further includes: Obtain the file attribute information and file content summary of the source file of the new energy vehicle product announcement parameters, and obtain the digital signature information when the source file of the new energy vehicle product announcement parameters has digital signature information; Based on the file attribute information, the file content summary, and the verification result of the digital signature information when it is present, the source credibility and integrity verification of the source file of the new energy vehicle product announcement parameters is performed. If the verification passes, the original value extraction and consistency verification of the announcement parameters in the source file of the new energy vehicle product announcement parameters are allowed; if the verification fails, an abnormal source file identifier is generated and the abnormal source file identifier is associated with the corresponding object identifier and vehicle model identifier.

[0013] In some examples, the data submitted by the enterprise also includes at least one of the product testing report and component testing report corresponding to the vehicle model identifier, production process consistency records, and component access filing documents; the method further includes: The document type is identified and the content is parsed for at least one of the product testing report and component testing report, the production process consistency record and the component access filing document, and at least one verification element is extracted from the organization identifier, product or component model, report number, issuance date, test conclusion, production batch and access filing information. For electronic documents with digital signatures, the digital signature of the electronic documents is verified to obtain a digital signature verification result; for scanned documents or image files without digital signatures, at least one of the source identifier, document content summary, document version information and document association information of the document is obtained, and a document source verification result is generated accordingly. The extracted verification elements are compared with the vehicle model identifier, product or component model, pre-stored inspection and testing agency qualification information, component access filing information and historical reporting data, and combined with the digital signature verification result or the document source verification result to obtain the supporting document verification result. The verification results of the supporting documents are associated with the parameter verification records corresponding to the vehicle model identifier to generate a comprehensive verification result corresponding to the vehicle model identifier.

[0014] Secondly, this application provides a cross-source field alignment verification system for parameters in new energy vehicle product announcements, including: The rule matching module is used to obtain the object identifier, object type, vehicle model identifier, current rule version identifier, enterprise-filled data, and source file of new energy vehicle product announcement parameters corresponding to the vehicle model identifier of the object to be verified, and to determine the compliance rule package corresponding to the object to be verified from the pre-built compliance knowledge base based on the object type and the current rule version identifier. The announcement parameter extraction module is used to determine the target announcement parameter area corresponding to the vehicle model identifier and the compliance indicators to be verified from the source file of the new energy vehicle product announcement parameters according to the compliance rule package, and extract the original value of the announcement parameter from the target announcement parameter area; The field alignment module is used to determine the field correspondence between the enterprise reporting parameter values ​​and the original values ​​of the announcement parameters in the enterprise reporting data according to the compliance rule package, and to normalize the enterprise reporting parameter values ​​and the original values ​​of the announcement parameters. The consistency verification module is used to perform a consistency comparison between the normalized enterprise-reported parameter values ​​and the original normalized announcement parameters according to the compliance rule package, and generate a parameter verification record. The parameter verification record includes at least the object identifier, vehicle model identifier, compliance indicator identifier, rule version identifier, and comparison status.

[0015] In some examples, the cross-source field alignment verification system for parameters in new energy vehicle product announcements also includes a supporting documentation verification module.

[0016] The supporting documentation verification module is used to identify and parse the document type of at least one of the product testing report and component testing report corresponding to the vehicle model identifier, the production process consistency record, and the component access filing document, and extract verification elements; for electronic documents with digital signatures, the module verifies the digital signature of the electronic document; for scanned documents or image files without digital signatures, the module obtains at least one of the document source identifier, document content summary, document version information, and document association information, and generates a document source verification result accordingly; the module compares and correlates the verification elements with the vehicle model identifier, product or component model, pre-stored inspection and testing agency qualification information, component access filing information, and historical reporting data to obtain the supporting documentation verification result; and the module associates the supporting documentation verification result with the parameter verification record generated by the consistency verification module to generate a comprehensive verification result corresponding to the vehicle model identifier.

[0017] Thirdly, this application provides a computer device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the computer program, it implements the cross-source field alignment verification method for new energy vehicle product announcement parameters as described in the first aspect.

[0018] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, it implements the cross-source field alignment verification method for new energy vehicle product announcement parameters as described in the first aspect.

[0019] The embodiments of this application determine the corresponding compliance rule package based on the object type and rule version, enabling different types of objects to be verified to apply the corresponding verification rules and linking the verification results to specific rule versions, facilitating historical result tracing and review. By parsing the layout and performing OCR recognition on the source files of new energy vehicle product announcement parameters, the target announcement parameter area corresponding to the vehicle model identifier and compliance indicators is determined, and the source file location information is recorded, allowing the extracted original values ​​of the announcement parameters to be traced back to their specific locations in the source files. By standardizing field names, converting units of measurement, unifying numerical precision, and standardizing character formats for the parameter values ​​submitted by enterprises and the original values ​​of the announcement parameters based on field mapping rules, verification errors caused by differences in data formats from different sources are reduced. By performing consistency comparison according to the comparison method, allowable deviation range, and judgment rules, and generating verification records including difference information and source file location information, the accuracy, traceability, and reproducibility of the verification results are improved. By parsing and comparing test reports, production process consistency records, and component access filing documents, the parameter verification results can be supplemented with supporting materials, improving the completeness of compliance document verification. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments are briefly described below. It should be understood that the following drawings only show some embodiments of this application and do not constitute a limitation on the scope of protection of this application.

[0021] Figure 1 A flowchart illustrating the method for verifying cross-source field alignment of parameters in new energy vehicle product announcements provided in this application embodiment; Figure 2 A structural block diagram of the cross-source field alignment verification system for new energy vehicle product announcement parameters provided in this application embodiment; Figure 3 This is a structural block diagram of a computer device provided in an embodiment of this application. Detailed Implementation

[0022] The present application will now be described in further detail with reference to the embodiments and accompanying drawings. It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the application. Furthermore, it should be noted that, for ease of description, only the parts relevant to the application are shown in the accompanying drawings.

[0023] It should be noted that, unless otherwise specified, the embodiments and features of the embodiments in this application can be combined with each other. The present application will now be described in detail with reference to the accompanying drawings and embodiments.

[0024] The following describes in detail, with reference to the accompanying drawings, a method and system for cross-source field alignment verification of parameters in new energy vehicle product announcements provided by this application.

[0025] Figure 1 A flowchart illustrating the cross-source field alignment verification method for new energy vehicle product announcement parameters provided in this application embodiment. (For example...) Figure 1 As shown in the embodiments of this application, the method for verifying cross-source field alignment of new energy vehicle product announcement parameters includes the following steps: S101: Obtain the verification data of the object to be verified and determine the corresponding compliance rule package.

[0026] Obtain the object identifier, object type, vehicle model identifier, current rule version identifier, enterprise-submitted data, and source file of new energy vehicle product announcement parameters corresponding to the vehicle model identifier of the object to be verified.

[0027] The entities to be verified can be new energy vehicle manufacturers, core component suppliers, or new energy vehicle operators. The data submitted by the enterprises includes the enterprise-submitted parameter values ​​for the vehicle model to be verified, and may further include at least one of the product testing reports and component testing reports corresponding to the vehicle model identifier, production process consistency records, and component access filing documents.

[0028] Based on the object type and the current rule version identifier, determine the compliance rule package corresponding to the object to be verified from the pre-built compliance knowledge base.

[0029] The compliance knowledge base is configured with corresponding compliance rule packages according to different object types. Each compliance rule package includes at least one or more of the following: compliance indicator identifier, enterprise reporting field identifier, announcement parameter field identifier, field mapping rule, parameter normalization rule, comparison method, allowable deviation range, and judgment rule.

[0030] To achieve version-based management of compliance rules, a rule version identifier is set for the compliance rule package. When a compliance rule is updated, a new rule version is generated based on the updated compliance rule, while the previous compliance rule version is retained. Therefore, when reviewing historical verification records, the compliance rule package used to generate the historical verification record can be determined based on the rule version identifier stored in the historical verification record.

[0031] The compliance knowledge base can adopt a hierarchical structure of "regulatory dimension - compliance category - compliance indicator". Among them, the regulatory dimension is used to represent at least one regulatory direction among production consistency, product safety, operational safety, energy consumption and environmental protection, recycling traceability or after-sales service; the compliance category is used to represent the verification of announcement filing parameters, regulatory custom parameter verification or other verification scenarios; and the compliance indicator is used to represent the specific parameters or data items to be verified.

[0032] In one specific example, the compliance rules package includes announcement parameter verification rules. These rules record the field correspondence between the fields entered by the enterprise and the fields in the announcement parameters, as well as corresponding unit of measurement conversion rules, numerical precision unification rules, character format standardization rules, and consistency judgment rules.

[0033] In another specific example, the rules in the compliance knowledge base can be configured and updated by rule administrators according to regulatory policies, national standards, local reporting requirements, or special verification requirements. After a rule is updated, a new version is created, while the previous version, its scope of application, publication date, and content are retained to ensure the traceability of the verification process.

[0034] Through the above processing, the system can determine the compliance rule package used for subsequent announcement parameter extraction, field alignment, parameter normalization, and consistency comparison based on the object type, vehicle model identifier, and current rule version identifier of the object to be verified.

[0035] S102: Verify the source credibility and completeness of the parameter source files for new energy vehicle product announcements.

[0036] In one embodiment of this application, before extracting the original values ​​of the announcement parameters from the source file of the new energy vehicle product announcement parameters, the source credibility and integrity of the source file of the new energy vehicle product announcement parameters are verified.

[0037] Specifically, the file attribute information and file content summary of the source file of the new energy vehicle product announcement parameters are obtained, and the digital signature information is obtained when the source file of the new energy vehicle product announcement parameters has digital signature information.

[0038] The file attribute information may include at least one of the following: file name, file type, file size, creation time, modification time, source identifier, and file version; the digital signature information may include at least one of the following: signature value, signature certificate, signature subject, and signature time; and the file content summary can be calculated based on the file content of the source file of the new energy vehicle product announcement parameters.

[0039] Based on the file attribute information and the file content summary, and the verification result of the digital signature information when the source file of the new energy vehicle product announcement parameters has digital signature information, the source credibility and integrity of the source file of the new energy vehicle product announcement parameters are verified.

[0040] In a specific example, the currently acquired file content digest is matched with a pre-stored standard file content digest; when the source file of the new energy vehicle product announcement parameters has digital signature information, the digital signature information is verified; based on the file content digest matching result and the verification result when the digital signature information is present, it is determined whether the source file of the new energy vehicle product announcement parameters has passed verification.

[0041] If the verification passes, layout parsing, parameter extraction, and consistency verification are allowed for the source file of the new energy vehicle product announcement parameters; if the verification fails, an anomaly identifier is generated for the source file, and the source file anomaly identifier is associated with the object identifier and the vehicle model identifier.

[0042] By performing the above processing, we can avoid extracting parameters from announcement parameter source files that are of unknown origin, have been tampered with, or are incomplete, thereby improving the credibility of the verification results.

[0043] S103: Determine the target announcement parameter area based on the compliance rule package and extract the original values ​​of the announcement parameters.

[0044] After the source file of the new energy vehicle product announcement parameters is verified, the layout of the source file is parsed according to the compliance rule package.

[0045] Page layout parsing may include at least one of the following processes: page segmentation, table recognition, text block recognition, field position recognition, and page hierarchy recognition, to determine the vehicle information area, parameter field area, and parameter value area in the source file.

[0046] Based on the vehicle model identifier, determine the vehicle model parameter page or vehicle model parameter area corresponding to the vehicle model identifier in the new energy vehicle product announcement parameter source file.

[0047] Furthermore, based on the compliance indicator identifier and announcement parameter field identifier in the compliance rule package, the target announcement parameter area corresponding to the compliance indicator to be verified is determined on the vehicle parameter page or in the vehicle parameter area.

[0048] The target announcement parameter area is subjected to OCR recognition to extract the parameter field name, parameter value and unit of measurement.

[0049] In a specific example, the OCR recognition results undergo character error correction, field segmentation, and numerical format recognition to distinguish parameter field names, parameter values, and units of measurement. For composite parameter regions containing multiple parameter values, the multiple parameter values ​​are split and matched according to the announced parameter field identifier.

[0050] Based on the compliance indicator identifier, the extracted parameter fields are matched to obtain the original values ​​of the announcement parameters corresponding to the compliance indicator to be verified.

[0051] Simultaneously, the source file location information of the target announcement parameter area within the source file of the new energy vehicle product announcement parameters is recorded. The source file location information includes at least one of page numbers, text block identifiers, table row and column information, coordinate information, and region identifiers.

[0052] When no parameter field corresponding to the compliance indicator is matched, a parameter missing identifier is generated, and the parameter missing identifier is associated with the vehicle model identifier, the compliance indicator identifier, and the source file location information.

[0053] Through the above processing, the target announcement parameter area can be determined from the announcement parameter source file with complex layout structure and different field expression methods, and the original value of the announcement parameter can be traced back to the specific location in the source file.

[0054] S104: Determine the field correspondence between the parameter values ​​filled in by the enterprise and the original values ​​of the parameters in the announcement, and perform normalization processing.

[0055] After determining the target announcement parameter region and extracting the original values ​​of the announcement parameters, the field correspondence between the enterprise reporting parameter values ​​in the enterprise reporting data and the original values ​​of the announcement parameters is determined based on the compliance indicator identifier, enterprise reporting field identifier, announcement parameter field identifier and field mapping rules stored in the compliance rule package.

[0056] The field mapping rules include at least one of the following: field name mapping relationship, field alias mapping relationship, field hierarchy mapping relationship, parameter composition relationship, parameter splitting relationship, and field applicable object relationship.

[0057] In a specific example, the names of the enterprise reporting fields, the names of the announcement parameter fields, and the corresponding parameter units and page positions are obtained. Based on the field name mapping relationship and the field alias mapping relationship, it is determined whether the enterprise reporting fields and the announcement parameter fields correspond to the same compliance indicator.

[0058] When multiple candidate announcement parameter fields exist, the target announcement parameter field is determined by filtering the multiple candidate announcement parameter fields based on the field matching relationship, unit of measurement compatibility relationship, vehicle model region consistency relationship and spatial location relationship between the candidate announcement parameter fields and the compliance indicator identifier.

[0059] When a unique target announcement parameter field is not determined, a field matching anomaly identifier is generated, and the field matching anomaly identifier is associated with the object identifier, vehicle model identifier, compliance indicator identifier, and source file location information.

[0060] After determining the field correspondence, normalization processing is performed on the parameter values ​​reported by the enterprise and the original values ​​of the announcement parameters according to the parameter normalization rules in the compliance rule package.

[0061] The normalization process includes at least one of the following: field name unification, unit of measurement conversion, numerical precision unification, character format standardization, space removal, special symbol removal, number format conversion, and parameter value type conversion.

[0062] For enterprises with different units of measurement, the parameter values ​​submitted and the original values ​​of the announced parameters will be converted to the same standard unit of measurement according to the unit of measurement conversion rules; for enterprises with different numerical precision, the parameter values ​​submitted and the original values ​​of the announced parameters will be unified in terms of significant digits or number of digits retained according to the numerical precision unification rules; for parameter values ​​containing full-width characters, half-width characters, thousands separators or other special characters, the format will be unified according to the character format standardization rules.

[0063] For composite parameters consisting of multiple sub-parameters, the parameter values ​​reported by the enterprise and the original values ​​of the announcement parameters are split according to the parameter composition relationship, and corresponding relationships are established according to the sub-parameter field identifiers.

[0064] After normalization, the normalized enterprise reporting parameter values ​​and the normalized original announcement parameter values ​​are obtained, and the field correspondence and normalization processing records are saved.

[0065] S105: Perform a consistency comparison between the normalized enterprise-reported parameter values ​​and the original normalized announcement parameter values, and generate parameter verification records.

[0066] Based on the compliance rule package, obtain the comparison method, allowable deviation range, and judgment rule corresponding to the compliance indicator identifier.

[0067] The comparison method includes at least one of the following: complete consistency comparison, allowable deviation comparison, numerical range comparison, Boolean value comparison, enumeration value comparison, and logical relationship comparison.

[0068] Based on the field correspondence, the normalized enterprise reporting parameter values ​​and the original normalized announcement parameter values ​​are compared field by field.

[0069] When the comparison method is a complete consistency comparison, if the normalized enterprise-reported parameter value is the same as the original value of the normalized announcement parameter, the verification result of the corresponding compliance indicator is determined to be consistent; if the two are different, the verification result of the corresponding compliance indicator is determined to be inconsistent.

[0070] When the comparison method is allowable deviation comparison, the difference value or difference ratio between the normalized enterprise reported parameter value and the normalized announcement parameter original value is calculated, and the verification result is determined to be consistent when the difference value or difference ratio does not exceed the allowable deviation range.

[0071] When the normalized enterprise-reported parameter values ​​and the original normalized announcement parameters do not meet the judgment rules, difference information is generated. The difference information includes at least one of the following: difference value, difference ratio, difference type, and degree of exceeding the allowable deviation range.

[0072] For each compliance indicator to be verified, a parameter verification record is generated. The parameter verification record includes at least one or more of the following: object identifier, object type, vehicle model identifier, compliance indicator identifier, rule version identifier, enterprise-reported parameter value, original value of announcement parameter, normalized enterprise-reported parameter value, normalized original value of announcement parameter, normalization processing record, field correspondence, comparison method, comparison status, difference information, and source file location information.

[0073] If a parameter field is missing, a field matching error occurs, a source file error occurs, or the OCR recognition result does not meet the preset credibility conditions, the comparison status is set to pending review, and the corresponding error identifier is written into the parameter verification record.

[0074] Through the above processing, based on the completion of cross-source field alignment and normalization, an interpretable and traceable consistency comparison can be made between the parameter values ​​filled in by enterprises and the original values ​​of the parameters in the announcement.

[0075] S106: Verify the supporting documents and generate a comprehensive verification result.

[0076] In one embodiment of this application, the data submitted by the enterprise also includes at least one of the product testing report and the component testing report corresponding to the vehicle model identifier, a production process consistency record, and a component access filing document.

[0077] The test report, the production process consistency record, and the component access filing document are identified by document type and parsed by content, and at least one verification element is extracted from the organization identifier, product or component model, report number, issuance date, test conclusion, production batch, and access filing information.

[0078] For electronic documents with digital signatures, the digital signature of the electronic documents is verified to obtain a digital signature verification result; for scanned documents or image files without digital signatures, at least one of the source identifier, document content summary, document version information and document association information of the document is obtained, and a document source verification result is generated accordingly.

[0079] The verification elements are compared and correlated with the vehicle model identifier, product or component model, pre-stored inspection and testing agency qualification information, component access filing information and historical reporting data, and combined with the digital signature verification result or the document source verification result to obtain the supporting document verification result.

[0080] The verification results of the supporting documents are associated with the parameter verification records corresponding to the vehicle model identifier to generate a comprehensive verification result corresponding to the vehicle model identifier.

[0081] The comprehensive verification results include at least one of the following states: consistent parameters, inconsistent parameters, consistent supporting materials, inconsistent supporting materials, missing parameters, abnormal field matching, abnormal source file, and pending manual review.

[0082] Figure 2 This is a structural block diagram of the new energy vehicle product announcement parameter cross-source field alignment verification system provided in this application embodiment. (See diagram below.) Figure 2 As shown, the cross-source field alignment verification system for new energy vehicle product announcement parameters includes a rule matching module 410, an announcement parameter extraction module 420, a field alignment module 430, and a consistency verification module 440.

[0083] In some embodiments, the new energy vehicle product announcement parameter cross-source field alignment verification system further includes a supporting document verification module ( Figure 2 (Not shown in the image).

[0084] The rule matching module 410 is used to obtain the object identifier, object type, vehicle model identifier, current rule version identifier, enterprise-filled data, and new energy vehicle product announcement parameter source file corresponding to the vehicle model identifier of the object to be verified, and to determine the compliance rule package corresponding to the object to be verified from the pre-built compliance knowledge base according to the object type and the current rule version identifier.

[0085] The announcement parameter extraction module 420 is used to parse the layout of the source file of the announcement parameters of the new energy vehicle product according to the compliance rule package, determine the target announcement parameter area corresponding to the vehicle model identifier and the compliance indicators to be verified, extract the original value of the announcement parameter from the target announcement parameter area, and record the source file location information corresponding to the target announcement parameter area.

[0086] The field alignment module 430 is used to determine the field correspondence between the enterprise reporting parameter values ​​and the original values ​​of the announcement parameters in the enterprise reporting data based on the compliance indicator identifier, enterprise reporting field identifier, announcement parameter field identifier and field mapping rules stored in the compliance rule package, and to normalize the enterprise reporting parameter values ​​and the original values ​​of the announcement parameters according to the parameter normalization rules.

[0087] The consistency verification module 440 is used to obtain the comparison method, allowable deviation range and judgment rule corresponding to the compliance indicator identifier according to the compliance rule package, perform consistency comparison between the normalized enterprise-reported parameter value and the normalized announcement parameter original value, and generate parameter verification record. The parameter verification record includes at least object identifier, vehicle model identifier, compliance indicator identifier, rule version identifier and comparison status.

[0088] In some embodiments, the consistency verification module 440 is further configured to: set the comparison status to consistent when the normalized enterprise reporting parameter value and the normalized announcement parameter original value meet the judgment rule; set the comparison status to inconsistent when the normalized enterprise reporting parameter value and the normalized announcement parameter original value do not meet the judgment rule, and generate a difference verification record including the normalized enterprise reporting parameter value, the normalized announcement parameter original value, difference information, and source file location information; and set the comparison status to pending review when there are missing parameter fields, abnormal field matching, abnormal source files, or OCR recognition results that do not meet preset credibility conditions, and write the corresponding abnormal identifier into the parameter verification record.

[0089] The supporting documentation verification module is used to identify and parse the document type of at least one of the product testing reports and component testing reports corresponding to the vehicle model identifier, the production process consistency record, and the component access filing documents. It extracts at least one verification element from the following: organization identifier, product or component model, report number, issuance date, testing conclusion, production batch, and access filing information. For electronic documents with digital signatures, the module verifies the digital signature to obtain a digital signature verification result. For scanned documents or image files without digital signatures, it obtains at least one of the following: document source identifier, document content summary, document version information, and document association information, and generates a document source verification result accordingly. The module then compares and correlates these verification elements with the vehicle model identifier, product or component model, pre-stored inspection and testing organization qualification information, component access filing information, and historical reporting data. Combining this with the digital signature verification result or the document source verification result, it obtains a supporting documentation verification result. Finally, it correlates the supporting documentation verification result with the parameter verification record generated by the consistency verification module 440 to generate a comprehensive verification result corresponding to the vehicle model identifier.

[0090] The aforementioned rule matching module 410, announcement parameter extraction module 420, field alignment module 430, consistency verification module 440, and supporting documentation verification module can be implemented through software, hardware, or a combination of software and hardware. A module can be implemented by one or more program units, and multiple modules can be integrated into the same program unit. Module division is used to describe the functions performed by the system and does not constitute a limitation on the physical deployment of modules. For the specific implementation methods of the operations performed by each module, please refer to the corresponding content in the foregoing method embodiments.

[0091] In one embodiment, a computer device is provided. Figure 3 This is a structural block diagram of the computer device provided in the embodiments of this application, with reference to... Figure 3 The computer device includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements the aforementioned embodiment of the method for cross-source field alignment verification of parameters in new energy vehicle product announcements.

[0092] The method implementation includes: acquiring verification data of the object to be verified and determining the corresponding compliance rule package; verifying the source credibility and integrity of the source files of the new energy vehicle product announcement parameters; determining the target announcement parameter area and extracting the original values ​​of the announcement parameters according to the compliance rule package; determining the field correspondence between the parameter values ​​filled in by the enterprise and the original values ​​of the announcement parameters and performing normalization processing; performing a consistency comparison between the normalized parameter values ​​filled in by the enterprise and the normalized original values ​​of the announcement parameters and generating parameter verification records; and performing correlation verification on supporting materials and generating a comprehensive verification result.

[0093] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the aforementioned method embodiment for cross-source field alignment verification of parameters in new energy vehicle product announcements.

[0094] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by computer program instructions and related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. Any references to memory, storage, database, or other media in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0095] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0096] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for verifying cross-source field alignment of parameters in new energy vehicle product announcements, characterized in that, include: Obtain the object identifier, object type, vehicle model identifier, current rule version identifier, enterprise-submitted data, and source file of new energy vehicle product announcement parameters corresponding to the vehicle model identifier of the object to be verified; Based on the object type and the current rule version identifier, determine the compliance rule package corresponding to the object to be verified from the pre-built compliance knowledge base; According to the compliance rule package, the target announcement parameter area corresponding to the vehicle model identifier and the compliance indicators to be verified is determined from the source file of the new energy vehicle product announcement parameters, and the original value of the announcement parameter is extracted from the target announcement parameter area; The correspondence between the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters in the enterprise-reported data is determined according to the compliance rule package, and the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters are normalized. Based on the compliance rule package, a consistency comparison is performed between the normalized enterprise-reported parameter values ​​and the original normalized announcement parameter values ​​to generate parameter verification records. The parameter verification records include at least the object identifier, vehicle model identifier, compliance indicator identifier, rule version identifier, and comparison status.

2. The method for cross-source field alignment verification of new energy vehicle product announcement parameters according to claim 1, characterized in that, The construction of the compliance knowledge base includes: Set up corresponding compliance rule packages according to different object types, and set rule version identifiers for the compliance rule packages; When compliance rules are updated, a new version of the rules is generated based on the updated compliance rules, while the previous version of the compliance rules is retained.

3. The method for cross-source field alignment verification of new energy vehicle product announcement parameters according to claim 1, characterized in that, The step of determining the target announcement parameter area corresponding to the vehicle model identifier and the compliance indicators to be verified from the source file of the new energy vehicle product announcement parameters according to the compliance rule package, and extracting the original values ​​of the announcement parameters from the target announcement parameter area, includes: The layout of the source file of the new energy vehicle product announcement parameters is parsed to determine the parameter area containing the vehicle model identifier and the compliance indicators; The parameter region is subjected to OCR recognition to extract the parameter field name, parameter value and unit of measurement, and the page number, coordinates or region identifier of the parameter region in the source file is recorded; The extracted parameter fields are matched according to the compliance indicator identifier to obtain the original value of the announcement parameter and its corresponding source file location information.

4. The method for cross-source field alignment verification of new energy vehicle product announcement parameters according to claim 1, characterized in that, The step of determining the correspondence between the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters in the enterprise-reported data according to the compliance rule package, and normalizing the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters, includes: Based on the compliance indicator identifiers, enterprise reporting field identifiers, announcement parameter field identifiers, and field mapping rules stored in the compliance rule package, determine the field correspondence between the enterprise reporting parameter values ​​and the original values ​​of the announcement parameters; According to the field mapping rules, the field name unification, unit of measurement conversion, numerical precision unification and character format standardization are performed on the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters, respectively, to obtain the normalized enterprise-reported parameter values ​​and the normalized original values ​​of the announcement parameters.

5. The method for cross-source field alignment verification of parameters in new energy vehicle product announcements according to claim 1, characterized in that, The step of performing a consistency comparison between the normalized enterprise-reported parameter values ​​and the original normalized announcement parameter values ​​according to the compliance rule package includes: Obtain the comparison method, allowable deviation range, and judgment rule corresponding to the compliance indicator identifier in the compliance rule package; Based on the correspondence between the enterprise-reported parameter values ​​and the original values ​​of the announcement parameters, the normalized enterprise-reported parameter values ​​and the normalized original values ​​of the announcement parameters are compared field by field. When the normalized enterprise-reported parameter value and the normalized announcement parameter original value meet the judgment rule, the verification result of the corresponding compliance indicator is determined to be consistent; when the normalized enterprise-reported parameter value and the normalized announcement parameter original value do not meet the judgment rule, the verification result of the corresponding compliance indicator is determined to be inconsistent. For compliance indicators with inconsistent verification results, a verification record is generated that includes vehicle model identifier, compliance indicator identifier, normalized enterprise-reported parameter value, normalized original value of announcement parameter, difference information, and the page number, coordinates, or area identifier of the target announcement parameter area in the source file of the new energy vehicle product announcement parameter.

6. The method for cross-source field alignment verification of new energy vehicle product announcement parameters according to claim 1, characterized in that, Before extracting the original values ​​of the announcement parameters from the source file of the new energy vehicle product announcement parameters, the process also includes: Obtain the file attribute information and file content summary of the source file of the new energy vehicle product announcement parameters, and obtain the digital signature information when the source file of the new energy vehicle product announcement parameters has digital signature information; Based on the file attribute information, the file content summary, and the verification result of the digital signature information when it is present, the source credibility and integrity verification of the source file of the new energy vehicle product announcement parameters is performed. If the verification passes, the original value extraction and consistency verification of the announcement parameters in the source file of the new energy vehicle product announcement parameters are allowed; if the verification fails, an abnormal source file identifier is generated and the abnormal source file identifier is associated with the corresponding object identifier and vehicle model identifier.

7. The method for cross-source field alignment verification of new energy vehicle product announcement parameters according to claim 1, characterized in that, The data submitted by the enterprise also includes at least one of the product testing report and component testing report corresponding to the vehicle model identification, production process consistency records, and component access filing documents; the method further includes: The document type is identified and the content is parsed for at least one of the product testing report and component testing report, the production process consistency record and the component access filing document, and at least one verification element is extracted from the organization identifier, product or component model, report number, issuance date, test conclusion, production batch and access filing information. For electronic documents with digital signatures, the digital signature of the electronic documents is verified to obtain a digital signature verification result; for scanned documents or image files without digital signatures, at least one of the source identifier, document content summary, document version information and document association information of the document is obtained, and a document source verification result is generated accordingly. The extracted verification elements are compared with the vehicle model identifier, product or component model, pre-stored inspection and testing agency qualification information, component access filing information and historical reporting data, and combined with the digital signature verification result or the document source verification result to obtain the supporting document verification result. The verification results of the supporting documents are associated with the parameter verification records corresponding to the vehicle model identifier to generate a comprehensive verification result corresponding to the vehicle model identifier.

8. A system for verifying cross-source field alignment of parameters in new energy vehicle product announcements, characterized in that, include: The rule matching module is used to obtain the object identifier, object type, vehicle model identifier, current rule version identifier, enterprise-filled data, and source file of new energy vehicle product announcement parameters corresponding to the vehicle model identifier of the object to be verified, and to determine the compliance rule package corresponding to the object to be verified from the pre-built compliance knowledge base based on the object type and the current rule version identifier. The announcement parameter extraction module is used to determine the target announcement parameter area corresponding to the vehicle model identifier and the compliance indicators to be verified from the source file of the new energy vehicle product announcement parameters according to the compliance rule package, and extract the original value of the announcement parameter from the target announcement parameter area; The field alignment module is used to determine the field correspondence between the enterprise reporting parameter values ​​and the original values ​​of the announcement parameters in the enterprise reporting data according to the compliance rule package, and to normalize the enterprise reporting parameter values ​​and the original values ​​of the announcement parameters. The consistency verification module is used to perform a consistency comparison between the normalized enterprise-reported parameter values ​​and the original normalized announcement parameters according to the compliance rule package, and generate a parameter verification record. The parameter verification record includes at least the object identifier, vehicle model identifier, compliance indicator identifier, rule version identifier, and comparison status.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, characterized in that, When the processor executes the computer program, it implements the method for cross-source field alignment verification of new energy vehicle product announcement parameters as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the method for cross-source field alignment verification of new energy vehicle product announcement parameters as described in any one of claims 1 to 7.

Images