A data integrity protection method and system based on standard text
By comparing the technical requirements of the benchmark and the standard text to be verified, changes in the scope of the standard text due to referenced content and exception clauses are identified and verified. This solves the problem of final technical requirement changes that are difficult to identify in the prior art and achieves accurate integrity verification.
Patent Information
- Application Number
- CN202611339723.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-01
- Publication Date
- 2026-11-17
AI Technical Summary
Existing technologies struggle to identify changes in the final technical requirements resulting from changes in execution conditions, referenced content, and exception clauses during the integrity verification of standard texts, leading to erroneous judgments.
By obtaining the technical objects, implementation conditions, and technical requirements from the benchmark standard text, determining the reference relationships and exception clause restrictions, generating the benchmark technical requirements results, and comparing them with the standard text to be verified, the integrity verification results are generated.
It can identify actual changes in technical requirements caused by adjustments to the scope of referenced content and exception clauses, even when the wording of the standard text technical requirements remains unchanged, thus avoiding incorrect judgments.
Smart Images

Figure CN123116356A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data security technology, specifically to a data integrity protection method and system based on standard text. Background Technology
[0002] In the process of compiling, revising and using standard texts such as technical standards, inspection specifications and operating procedures, technical requirements usually need to be determined in conjunction with the technical object, execution conditions, technical parameters, judgment content and related clauses. Therefore, the integrity of standard texts needs to be verified during the process of saving, revising and calling them.
[0003] Existing integrity checks typically rely on hash values, digital signatures, and text comparisons to determine whether the content of a document or clause has changed. However, when the execution conditions, reference relationships, and exception clauses are adjusted, even if the relevant technical requirements themselves have not changed in wording, the final technical requirements adopted may change.
[0004] In this situation, existing methods may still judge the standard text as complete, leading to subsequent testing, production, and judgment being carried out according to the changed technical requirements. Summary of the Invention
[0005] To address the shortcomings of existing technologies, this invention provides a data integrity protection method and system based on standard text, solving the problem that existing integrity checks struggle to identify changes in execution conditions, referenced content, and exception clauses that lead to changes in final technical requirements.
[0006] This invention is achieved through the following technical solution: a data integrity protection method based on standard text, comprising the following steps:
[0007] S1. Obtain the benchmark standard text, extract the technical objects, implementation conditions and technical requirements from the benchmark standard text, and determine the reference relationship and the restriction relationship of the exception clauses according to the reference content and exception clauses between the clauses;
[0008] S2, for each technical object, determine the technical requirements corresponding to each execution condition, obtain the referenced technical requirements along the reference relationship, and adjust the corresponding technical requirements according to the restriction relationship of the exception clause, and determine the technical requirements finally adopted under each execution condition as the benchmark technical requirements result;
[0009] S3, obtain the standard text to be verified, determine the technical objects, execution conditions, technical requirements, reference relationships and exception clauses in the standard text to be verified, and determine the final technical requirements to be adopted under each execution condition according to the execution conditions, reference relationships and exception clauses, and use the determined results as the technical requirements to be verified results;
[0010] S4. Using the same technical object as the corresponding basis, compare the benchmark technical requirement result with the technical requirement result to be verified according to the corresponding execution conditions, and generate the integrity verification result based on the comparison result.
[0011] Preferably, S1 includes:
[0012] S11, Read the chapter number, clause number, table number and appendix number in the benchmark text, determine the content level according to the chapter number, determine the start and end positions of the corresponding content according to the clause number, table number and appendix number, and determine the text content and table content between each start and end position as the clause content;
[0013] S12, determine the technical object, the execution conditions, and the technical requirements from each of the aforementioned clauses, determine the reference relationship based on the reference content between different clauses, and determine the restriction relationship of the exception clauses based on the condition limitation content, restricted content, and redefined content in the exception clauses.
[0014] Preferably, S12 includes:
[0015] S121, Read the object name, condition limitation content, execution action, technical parameters and judgment content in each of the aforementioned clauses, determine the object name to which the execution action, technical parameters and judgment content are targeted as the technical object, determine the condition limitation content that limits the execution scope of the execution action, technical parameters and judgment content as the execution condition, and determine the corresponding execution action, technical parameters and judgment content as the technical requirement;
[0016] S122, Read the reference number recorded in each of the aforementioned clauses, locate the referenced clause according to the reference number, determine the pointing relationship between the clause recording the reference number and the referenced clause as the reference relationship, read the execution conditions limited by the exception clause, the restricted technical requirements, and the redefined technical requirements, and determine the correspondence between the three as the exception clause restriction relationship.
[0017] Preferably, S2 includes:
[0018] S21, for each of the aforementioned technical objects, read the corresponding execution conditions one by one, obtain the technical requirements directly recorded by the clause content under the current execution conditions and the referenced technical requirements obtained along the reference relationship, and form a set of benchmark candidate technical requirements together with the corresponding technical objects and execution conditions;
[0019] S22, determine whether the current execution condition meets the conditions limited by the exception clause based on the restriction relationship of the exception clause. If the current execution condition meets the conditions limited by the exception clause, replace the restricted technical requirement with the technical requirement redefined by the exception clause, and determine the benchmark technical requirement result based on the processed set of benchmark candidate technical requirements.
[0020] Preferably, S21 includes:
[0021] S211, locate the corresponding clause content based on the same technical object and the current execution condition, read the technical requirements directly recorded in the clause content, and add the technical requirements together with the corresponding technical object and the execution condition to the benchmark candidate technical requirements set;
[0022] S212, read the reference relationship corresponding to the current clause content, locate the referenced clause content according to the number pointed to by the reference relationship, add the technical requirements in the referenced clause content that correspond to the current technical object and the current execution condition to the benchmark candidate technical requirement set, when the referenced clause content does not repeatedly record the technical object and the execution condition, add the current technical object and the current execution condition as the technical object and the execution condition corresponding to the referenced technical requirement to the benchmark candidate technical requirement set, continue to read the referenced clause content that continues to record reference content according to the reference relationship, and do not repeat the reading of the clause content that has already been read, until no new referenced clause content is obtained.
[0023] Preferably, S22 includes:
[0024] S221, Read the execution conditions in the exception clause restriction relationship one by one, compare the current execution condition with the execution conditions limited by the exception clause, and when the current execution condition satisfies the execution conditions limited by the exception clause, determine the restricted technical requirement from the benchmark candidate technical requirement set according to the exception clause restriction relationship;
[0025] S222, the restricted technical requirement is removed from the benchmark candidate technical requirement set, the technical requirement redefined by the exception clause, together with the corresponding technical object and the execution condition, is added to the benchmark candidate technical requirement set. After processing the restriction relationship corresponding to the exception clause, the same technical object, the corresponding execution condition, and the technical requirement retained in the benchmark candidate technical requirement set are jointly determined as the benchmark technical requirement result.
[0026] Preferably, S3 includes:
[0027] S31, Read the chapter number, clause number, table number and appendix number in the standard text to be verified and obtain the corresponding clause content, and obtain the technical object, execution conditions, technical requirements, reference relationship and exception clause restriction relationship according to the content determination method in S12;
[0028] S32, for each technical object and the corresponding execution condition, obtain the directly recorded technical requirements and the referenced technical requirements corresponding to the current technical object and the current execution condition obtained along the reference relationship. Combine the obtained technical requirements with the corresponding technical object and the execution condition to form a set of candidate technical requirements to be verified. Replace the restricted technical requirements with the technical requirements redefined by the exception clause according to the exception clause restriction relationship. Determine the technical requirements retained in the same technical object, the corresponding execution condition, and the processed set of candidate technical requirements to be verified as the result of the technical requirements to be verified.
[0029] Preferably, S4 includes:
[0030] S41, establish a correspondence between the benchmark technical requirement result and the technical requirement result to be verified according to the same technical object, and retain the technical objects that have not been correspondingly established respectively; then establish a correspondence between the execution conditions with the same content under the same technical object that have been correspondingly established, and retain the execution conditions that have not been correspondingly established respectively.
[0031] S42, the following are identified as the technical requirement difference content: the technical object and its corresponding execution conditions and technical requirements that have not been established, the technical requirements that have not been established, the technical requirements that exist only on the side of the benchmark technical requirement result under the established execution conditions, the technical requirements that exist only on the side of the technical requirement result to be verified, and the technical requirements that exist on both sides but have inconsistent content. The integrity verification result is generated based on the technical requirement difference content.
[0032] Preferably, S42 includes:
[0033] S421, if the difference in the technical requirements is not obtained, the integrity verification result is determined to be consistent with the result of the benchmark technical requirements and the result of the technical requirements to be verified;
[0034] S422, when the technical requirement difference content is obtained, the integrity verification result is determined to be inconsistent between the benchmark technical requirement result and the technical requirement result to be verified, and the corresponding technical object, execution condition and technical requirement difference content are recorded in the integrity verification result.
[0035] A data integrity protection system based on standard text includes:
[0036] The benchmark standard text processing module is used to acquire the benchmark standard text and determine the technical object, the execution conditions, the technical requirements, the reference relationships, and the exception clause restriction relationships from the benchmark standard text;
[0037] The benchmark technical requirements determination module is used to determine the final technical requirements to be adopted under each of the aforementioned technical objects based on the execution conditions, the reference relationships, and the exception clause restriction relationships, thereby obtaining the benchmark technical requirements result.
[0038] The standard text processing module is used to obtain the standard text to be verified, determine the technical object, execution conditions, technical requirements, reference relationships and exception clause restriction relationships in the standard text to be verified, and determine the technical requirements finally adopted under each execution condition to obtain the technical requirements to be verified result.
[0039] The integrity verification module is used to compare the benchmark technical requirement result with the technical requirement result to be verified according to the same technical object and the corresponding execution conditions, and generate the integrity verification result based on the comparison result. Each module is executed by the processor calling the program instructions stored in the memory to perform the corresponding data processing operation.
[0040] This invention provides a data integrity protection method and system based on standard text, which has the following beneficial effects:
[0041] (1) By comparing the results of the benchmark technical requirements with the results of the technical requirements to be verified, the integrity verification results can be generated. When the text of the technical requirements in the standard text has not changed directly, the actual technical requirements changes caused by the adjustment of the scope of the referenced content, execution conditions and exception clauses can be further identified. For example, when the insulation resistance value remains unchanged but the thickness range limited by the exception clause is adjusted, it can still be determined that the insulation resistance judgment requirement finally adopted in the corresponding thickness range has changed, thereby reducing the situation of incorrect judgment caused by making integrity judgment based solely on changes in the text of the clause. Attached Figure Description
[0042] Figure 1 This is a schematic diagram illustrating the steps of a data integrity protection method based on standard text according to the present invention;
[0043] Figure 2 This is a schematic diagram of a data integrity protection system based on standard text according to the present invention. Detailed Implementation
[0044] The technical solutions of the present invention will now be clearly and completely described with reference to the accompanying drawings in the embodiments of the present invention.
[0045] Example 1
[0046] This method can be used to protect the data integrity of standard texts such as product inspection standards, production process specifications, equipment maintenance procedures, and engineering construction technical specifications. These standard texts usually record the technical objects, implementation conditions, technical requirements, referenced clauses, and exception clauses. After the standard text is revised, imported, or updated, even if some technical requirements themselves have not changed in wording, the final technical requirements may change due to changes in the scope of referenced content and exception clauses.
[0047] Example 1 selects product inspection standards as the application scenario. Taking the inspection standard of a certain type of electrical insulation component as an example, the benchmark standard text records the test temperature, insulation resistance judgment requirements and test methods of the insulation component. The test methods are given through reference clauses, and the exception clauses further specify that insulation components within a certain thickness range adopt another insulation resistance judgment requirement. During the revision of the standard text, if the content pointed to by the reference clauses and the execution conditions limited by the exception clauses change, even if the original insulation resistance value itself is not modified, it may lead to a change in the technical requirements finally adopted by the same technical object under the corresponding execution conditions. Therefore, the standard text before revision is taken as the benchmark standard text, and the revised standard text is taken as the standard text to be verified. The final technical requirements adopted by the two are determined according to S1 to S4.
[0048] This invention provides a data integrity protection method based on standard text. Please refer to [link / reference]. Figure 1 This includes the following steps:
[0049] S1. Obtain the benchmark standard text, extract the technical objects, implementation conditions and technical requirements from the benchmark standard text, and determine the reference relationship and the restriction relationship of the exception clauses according to the reference content and exception clauses between the clauses;
[0050] S2, for each technical object, determine the technical requirements corresponding to each execution condition, obtain the referenced technical requirements along the reference relationship, and adjust the corresponding technical requirements according to the restriction relationship of the exception clause, and determine the technical requirements finally adopted under each execution condition as the benchmark technical requirements result;
[0051] S3, obtain the standard text to be verified, determine the technical objects, execution conditions, technical requirements, reference relationships and exception clauses in the standard text to be verified, and determine the final technical requirements to be adopted under each execution condition according to the execution conditions, reference relationships and exception clauses, and use the determined results as the technical requirements to be verified results;
[0052] S4. Using the same technical object as the corresponding basis, compare the benchmark technical requirement result with the technical requirement result to be verified according to the corresponding execution conditions, and generate the integrity verification result based on the comparison result.
[0053] In this embodiment, a completeness verification result is generated by comparing the benchmark technical requirement result with the technical requirement result to be verified. This allows for further identification of changes in the final technical requirements caused by changes in the referenced content, adjustments to the execution conditions, and changes in the scope of exception clauses, even when the text of the technical requirements in the standard text itself has not changed. For example, if the insulation resistance value of an electrical insulation component has not been modified but the thickness range defined by the exception clause has changed, it can still be determined that the insulation resistance determination requirement finally adopted within the corresponding thickness range has changed. This avoids the situation where the incorrect technical requirements are continued to be adopted based solely on changes in the text of the clauses for completeness judgment.
[0054] Example 2
[0055] Based on the product inspection standard scenario set in Example 1, this embodiment describes the process of reading the clause content in the benchmark standard text, determining the technical object, determining the execution conditions, determining the technical requirements, reading the reference relationship, determining the restriction relationship of the exception clause, and generating the benchmark technical requirements result. In this embodiment, the values such as thickness, temperature, and insulation resistance are only used to illustrate the data processing process. In actual operation, the values, units, and comparison relationships recorded in the benchmark standard text are directly read. This method does not set additional empirical thresholds to replace the content of the standard text.
[0056] Specifically: S1 includes:
[0057] S11, Read the chapter number, clause number, table number and appendix number in the benchmark text, determine the content level according to the chapter number, determine the start and end positions of the corresponding content according to the clause number, table number and appendix number, and determine the text content and table content between each start and end position as the clause content;
[0058] Specifically: When reading the benchmark text, the numbers are read from the beginning of the text in character order. Chapter numbers are identified according to "Chapter ×", first-level numerical numbers, and the original chapter number format of the benchmark text. Clause numbers are identified according to consecutive hierarchical numbers. Table numbers are identified according to "Table + Number". Appendix numbers are identified according to "Appendix + Number". When a number is detected, the character position of the number is recorded as the starting position of the corresponding content. When the next number at the same level is detected, the character position before the next number is taken as the ending position of the current content. When the last item is within the current chapter, the ending position of the current chapter is taken as the ending position. When it is at the end of the entire text, the ending position of the benchmark text is taken as the ending position. The text, values, and table data read from the starting position to the ending position are saved as a single clause.
[0059] It should be noted that when inserting a table into the main text clause, the system first checks whether there is explicit reference content such as "see Table ×" or "implement according to Table ×". If there is explicit reference content, the corresponding table is saved separately as the referenced clause content. If there is no explicit reference content and the table is immediately following the current main text clause, the table is included in the clause content corresponding to the current main text clause, thus ensuring that the same table is not included in two main text clauses at the same time.
[0060] S12, determine the technical object, the execution conditions, and the technical requirements from each of the aforementioned clauses, determine the reference relationship based on the reference content between different clauses, and determine the restriction relationship of the exception clauses based on the condition limitation content, restricted content, and redefined content in the exception clauses.
[0061] Specifically: For each clause, read the nouns, conditional content, action content, numerical values, units, comparison relationships, and judgment content in the order of statements. Among them, the product name, component name, material name, sample name, and equipment name to which the execution action, parameter limitation, and judgment requirement are applied are read as technical objects. The content that limits the execution range after "when", "under the condition of", "for", "thickness is lower than", "temperature reaches" is read as execution conditions. The action content, numerical content, and judgment content controlled by "should", "must not", "adopt", "conduct", "not lower than", "not higher than" are read as technical requirements.
[0062] S12 includes:
[0063] S121, Read the object name, condition limitation content, execution action, technical parameters and judgment content in each of the aforementioned clauses, determine the object name to which the execution action, technical parameters and judgment content are targeted as the technical object, determine the condition limitation content that limits the execution scope of the execution action, technical parameters and judgment content as the execution condition, and determine the corresponding execution action, technical parameters and judgment content as the technical requirement;
[0064] Specifically: For a statement containing multiple contents, first determine the execution object of the action content, and then read the condition and parameter constraints before and after the action content. For example, if the clause states "Class A insulating components are tested at 120℃ for 30 minutes, and the insulation resistance after the test is not less than 100 MΩ", then "Class A insulating components" is determined as the technical object, "temperature equal to 120℃" is determined as an execution condition, "test time equal to 30 minutes" is used as the execution parameter in the technical requirements, and "insulation resistance not less than 100 MΩ" is used as the judgment content in the technical requirements. All of the above contents are written into the same data record.
[0065] During data processing: Numerical execution conditions are saved in the form of "comparison relationship + value + unit". Among them, "lower than" is converted to a less than relationship, "not higher than" is converted to a less than or equal to relationship, "higher than" is converted to a greater than relationship, "not lower than" is converted to a greater than or equal to relationship, and "equal to" is saved as an equal to relationship. The upper and lower boundaries in the range expression are respectively saved as the corresponding comparison relationships. Categorical execution conditions directly save the category name in the standard text. When two or more conditions simultaneously limit the same technical requirement, all conditions are written into the same data record, and the technical requirement in the data record is only adopted after all these conditions are met.
[0066] It should be noted that this embodiment does not use similarity judgment methods such as "basically the same", "highly similar", or "close". For categorical content, the character content is compared by comparing the object name and category name in the standard text. Only when the character sequence is the same after deleting leading and trailing spaces, consecutive spaces, and line breaks that do not affect the text content, are they considered to be in the same category. For numerical content, the judgment is made according to the numerical value, unit, and comparison relationship.
[0067] S122, Read the reference number recorded in each of the aforementioned clauses, locate the referenced clause according to the reference number, determine the pointing relationship between the clause recording the reference number and the referenced clause as the reference relationship, read the execution conditions limited by the exception clause, the restricted technical requirements, and the redefined technical requirements, and determine the correspondence between the three as the exception clause restriction relationship.
[0068] Specifically: When reading referenced content containing "Article ×", "Table ×", or "Appendix ×", extract the number and search for the same number in the already generated clause content record. Write the current clause content number and the found referenced clause content number into the same record. The former serves as the reference starting point and the latter as the reference target. The reference relationship is determined by this record.
[0069] Specifically: When reading the exception clause, first read the execution conditions corresponding to the scope of restriction in the exception clause, then read the original technical requirements targeted by the exception clause, and finally read the action content, technical parameters and judgment content re-recorded in the exception clause. Write the execution conditions, original technical requirements and re-recorded technical requirements into the same record, and determine the restriction relationship of the exception clause by the record.
[0070] It should be noted that: when the exception clause explicitly records the original clause number, the restricted technical requirements are obtained directly from that number. When the exception clause does not repeat the original clause number and is located at a lower level of a certain main clause, the nearest upper-level clause containing the same technical object is read from that lower level. First, the technical requirements involving the same parameters as the exception clause are searched. If the same parameters are not found, the technical requirements with the same execution action are searched, and the found technical requirements are determined as the restricted technical requirements.
[0071] In the scenario set in Example 1: if the basic clause states "the insulation resistance of Class A insulating components shall not be less than 100 MΩ", and the exception clause states "the insulation resistance of Class A insulating components with a thickness of less than 2 mm shall not be less than 80 MΩ", then "thickness less than 2 mm" shall be determined as the execution condition, "insulation resistance not less than 100 MΩ" shall be determined as the restricted technical requirement, and "insulation resistance not less than 80 MΩ" shall be determined as the redefined technical requirement. The above three contents shall be written into the same record of the restriction relationship of the exception clause. Among them, 2 mm, 100 MΩ and 80 MΩ are all from the example standard text itself and are not fixed values preset by this method.
[0072] S2 includes:
[0073] S21, for each of the aforementioned technical objects, read the corresponding execution conditions one by one, obtain the technical requirements directly recorded by the clause content under the current execution conditions and the referenced technical requirements obtained along the reference relationship, and form a set of benchmark candidate technical requirements together with the corresponding technical objects and execution conditions;
[0074] Specifically: Taking a technical object and its set of execution conditions as a processing unit, first read the technical requirements in the clauses that directly record the technical object and the set of execution conditions, then check whether there is a reference relationship with the current clause number as the reference starting point. If there is, continue to read the technical requirements in the referenced clauses, and add each obtained technical requirement, together with the current technical object and the current execution conditions, as a set element to the benchmark candidate technical requirements set.
[0075] It should be noted that when there is an overlap in the numerical ranges of the basic clause and the exception clause, the judgment result is not directly based on "overlap". Instead, all numerical boundaries of the two clauses are read, the boundaries of the same physical quantity are arranged in ascending order of numerical value, and the original condition range is divided into non-overlapping intervals using these boundaries. Then, the technical requirement is determined for each interval. For example, if the basic clause covers the entire thickness and the exception clause limits the thickness to less than 2 mm, then it is divided into at least two intervals: "less than 2 mm" and "greater than or equal to 2 mm".
[0076] S22, determine whether the current execution condition meets the conditions limited by the exception clause based on the restriction relationship of the exception clause. If the current execution condition meets the conditions limited by the exception clause, replace the restricted technical requirement with the technical requirement redefined by the exception clause, and determine the benchmark technical requirement result based on the processed set of benchmark candidate technical requirements.
[0077] Specifically: When judging numerical execution conditions, first read the names of physical quantities on both sides, and compare them only when the names of physical quantities are the same. Then convert the values to the same unit and convert them into information including the upper boundary, lower boundary and whether the boundary is included. When the numerical range corresponding to the current execution condition falls entirely into the numerical range limited by the exception clause, it is determined that the current execution condition meets the condition content limited by the exception clause. When the two ranges only partially intersect, the current execution condition is re-divided according to the boundary value of the intersection position and then processed separately.
[0078] Specifically: When converting units, the units used in the basic clauses of the benchmark standard text are used as the target units. The conversion is performed according to the conversion factors between units of the same physical quantity. For example, 1 mm is converted to 1000 μm and 0.1 GΩ is converted to 100 MΩ. During the conversion, the comparison relationship and whether the boundary is included are retained. Therefore, "≥100 MΩ" still retains the greater than or equal to relationship after conversion. "≥" and ">" are not considered as the same condition.
[0079] It should be noted that the system pre-saves the conversion factors between different units of the same physical quantity. The conversion factors are entered according to the unit conversion relationship clearly defined in the International System of Units and the corresponding standard. When performing unit conversion, the corresponding conversion factor is read according to the source unit and the target unit and the converted value is calculated. If the corresponding conversion factor is not saved, the original unit is retained and the comparison of the value item is stopped.
[0080] It should be noted that: Category-type execution conditions are judged according to the category name. If the character content is the same after removing differences in formatting spaces, line breaks, and full-width and half-width punctuation, the categories are considered the same. When multiple execution conditions jointly limit the same technical requirement, the above judgment is performed on each execution condition separately. The replacement process in the exception clause is only executed after all execution conditions meet the corresponding limit content.
[0081] S21 includes:
[0082] S211, locate the corresponding clause content based on the same technical object and the current execution condition, read the technical requirements directly recorded in the clause content, and add the technical requirements together with the corresponding technical object and the execution condition to the benchmark candidate technical requirements set;
[0083] Specifically: First, use the current technical object name to filter clauses containing the same object name, then read the execution conditions in the filtering results. Categorical execution conditions are compared according to the category name, and numerical execution conditions are compared according to the aforementioned interval rules. Only data records whose current condition range falls within the corresponding clause's limit range are retained. Then, read the technical requirements in these data records and add them to the benchmark candidate technical requirements set.
[0084] It should be noted that the “locating the corresponding clause content” here is not based on semantic similarity inference, but rather on filtering using three pieces of data that have already been read: the name of the technical object, the execution conditions in the clause, and the clause number. Therefore, each piece of content added to the benchmark candidate technical requirement set records the corresponding source clause number.
[0085] S212, read the reference relationship corresponding to the current clause content, locate the referenced clause content according to the number pointed to by the reference relationship, add the technical requirements in the referenced clause content that correspond to the current technical object and the current execution condition to the benchmark candidate technical requirement set, when the referenced clause content does not repeatedly record the technical object and the execution condition, add the current technical object and the current execution condition as the technical object and the execution condition corresponding to the referenced technical requirement to the benchmark candidate technical requirement set, continue to read the referenced clause content that continues to record reference content according to the reference relationship, and do not repeat the reading of the clause content that has already been read, until no new referenced clause content is obtained.
[0086] Specifically: Establish a record of the read clause numbers corresponding to this reference reading; start reading the reference target numbers from the current clause content; add the reference target numbers to the read clause number record and obtain the corresponding referenced clause content; then filter the technical requirements according to the current technical object and current execution conditions and add them to the benchmark candidate technical requirements set; if the referenced clause content still has reference target numbers, continue to perform the same steps; if the reference target number to be read already exists in the read clause number record, skip that reference target number; when all reference target numbers to be read have been read and no new reference target numbers have been generated, terminate this reference reading.
[0087] It should be noted that: when the cited clause explicitly records the technical object and execution conditions, the technical requirements are selected according to the technical object and execution conditions recorded in the cited clause. When the cited clause does not repeat the technical object and execution conditions, the technical object and execution conditions corresponding to the current clause are taken as the technical object and execution conditions corresponding to the cited technical requirements, and then the cited technical requirements are added to the benchmark candidate technical requirements set.
[0088] In the scenario set in Example 1: if the basic clause of the insulation component references the test method in Clause 5.3, and Clause 5.3 in turn references the test temperature in Table 2, then the test method in Clause 5.3 and the test temperature in Table 2 corresponding to the current insulation component and the current execution conditions are added to the benchmark candidate technical requirements set in sequence. Therefore, the final content obtained comes from the basic clause and the clause actually read along the reference relationship, rather than being determined solely based on the text of the basic clause itself.
[0089] S22 includes:
[0090] S221, Read the execution conditions in the exception clause restriction relationship one by one, compare the current execution condition with the execution conditions limited by the exception clause, and when the current execution condition satisfies the execution conditions limited by the exception clause, determine the restricted technical requirement from the benchmark candidate technical requirement set according to the exception clause restriction relationship;
[0091] Specifically: Read the exception clause restriction relationship records one by one, first obtain the corresponding technical object based on the data record where the restricted technical requirement is located in the record, then compare the obtained technical object with the current technical object, and compare the current execution conditions with the execution conditions in the record according to the category judgment rules and the numerical range judgment rules. After all the restriction conditions are met, search for the set element with the same technical object, falls within the current execution condition range and the technical requirement content is the same as the restricted technical requirement in the record from the benchmark candidate technical requirement set, and determine the set element as the content to be deleted.
[0092] It should be noted that when determining whether two technical requirements are identical, the judgment is not based on the overall "complete consistency" of the text. Instead, the execution actions, technical parameters, units, comparison relationships, and judgment content are read separately. After converting the units to the same unit, each item is compared. Only when the execution action names are the same, the converted parameter values are the same, the comparison relationships are the same, and the judgment content is the same, are they considered to be the same technical requirement. Among them, "greater than" and "greater than or equal to", "less than" and "less than or equal to" are handled according to different comparison relationships.
[0093] S222, the restricted technical requirement is removed from the benchmark candidate technical requirement set, the technical requirement redefined by the exception clause, together with the corresponding technical object and the execution condition, is added to the benchmark candidate technical requirement set. After processing the restriction relationship corresponding to the exception clause, the same technical object, the corresponding execution condition, and the technical requirement retained in the benchmark candidate technical requirement set are jointly determined as the benchmark technical requirement result.
[0094] Specifically: After identifying the elements to be deleted from the set, delete those elements. Then, read the execution actions, technical parameters, and judgment content that are redefined in the exception clause. If the exception clause only redefines one item, retain the remaining content in the original technical requirements that has not been modified by the exception clause, and replace the corresponding items with the content redefined in the exception clause. Then, add the obtained technical requirements, along with the current technical object and the current execution conditions, back into the baseline candidate technical requirements set.
[0095] It should be noted that when the same technical object and the same execution condition correspond to two or more exception clauses, the general limitation in the superior clause shall be processed first, and then the specific limitation in the subordinate clause shall be processed. When they are at the same level but have different scopes of limitation, the exception clause with a wider scope of limitation shall be processed first, and then the exception clause with a narrower scope of limitation shall be processed. When they are at the same level and have the same scope of limitation but have different redefined technical requirements, they shall be processed according to the priority order clearly recorded in the standard text. If the priority order is not recorded in the standard text, the benchmark technical requirement result corresponding to the execution condition shall not be generated and the clause number of the conflict shall be recorded.
[0096] In the scenario set in Example 1: For Class A insulating components with a thickness greater than or equal to 2 mm, the exception replacement corresponding to a thickness less than 2 mm is not performed, so "insulation resistance not less than 100 MΩ" is retained. For Class A insulating components with a thickness less than 2 mm, "insulation resistance not less than 100 MΩ" is deleted and "insulation resistance not less than 80 MΩ" is added. At the same time, the test temperature, test time and test method that have not been modified by the exception clause are retained. Finally, the technical object, the execution conditions and all the technical requirements retained at this time are jointly determined as the benchmark technical requirement result.
[0097] In this embodiment, by reading the technical objects, execution conditions, technical requirements, reference relationships, and exception clause restrictions in the benchmark standard text item by item to form a set of benchmark candidate technical requirements, and then filtering the referenced technical requirements according to the execution conditions and replacing the corresponding content according to the exception clause restrictions, it is possible to avoid the omission and misuse of technical requirements for the same technical object under different execution conditions. For example, when the basic clause of electrical insulation components references test methods and test parameters, and the exception clause stipulates that a different insulation resistance judgment requirement is used when the thickness is less than 2 mm, the test methods, test parameters, and insulation resistance judgment requirements corresponding to each thickness range can be determined separately, and a benchmark technical requirement result with clear source and complete content can be formed, providing an accurate comparison basis for subsequent integrity verification.
[0098] Example 3
[0099] This embodiment describes the process of reading the standard text to be verified, generating the technical requirements to be verified, and determining the integrity verification results, based on the product inspection standard scenario set in Embodiment 1 and the benchmark technical requirements results determined in Embodiment 2. The standard text to be verified is a standard text that has been revised, republished, and re-imported and requires integrity verification. Data reading, condition judgment, unit conversion, reference reading, and exception clause processing all follow the processing rules already described in Embodiment 2 to ensure that the benchmark standard text and the standard text to be verified use the same data processing basis.
[0100] Specifically: S3 includes:
[0101] S31, Read the chapter number, clause number, table number and appendix number in the standard text to be verified and obtain the corresponding clause content, and obtain the technical object, execution conditions, technical requirements, reference relationship and exception clause restriction relationship according to the content determination method in S12;
[0102] Specifically: following the numbering rules used for the benchmark text in Example 2, the chapter number, clause number, table number, and appendix number are read sequentially from the starting position of the standard text to be verified. The starting and ending positions of the corresponding content are determined based on the position of each number, and the clause content is formed. Then, the object name, condition limitation content, execution action, technical parameters, unit, comparison relationship, judgment content, and reference number in each clause content are read item by item. The technical object, execution condition, technical requirement, reference relationship, and exception clause restriction relationship are obtained respectively using the judgment method determined in Example 2, thereby ensuring that similar content in the two standard texts is extracted according to the same rule.
[0103] It should be noted that when reading the category names in the standard text to be verified, the category names are saved after removing leading and trailing spaces, consecutive spaces, line breaks, and differences in full-width and half-width punctuation. Numerical content is saved in the form of "comparison relationship + value + unit". Referenced content is saved according to the reference starting point number and reference target number. Exception clauses are saved according to the corresponding execution conditions, restricted technical requirements, and redefined technical requirements. Therefore, subsequent comparisons do not use semantic similarity, manual scoring, or empirical thresholds.
[0104] S32, for each technical object and the corresponding execution condition, obtain the directly recorded technical requirements and the referenced technical requirements corresponding to the current technical object and the current execution condition obtained along the reference relationship. Combine the obtained technical requirements with the corresponding technical object and the execution condition to form a set of candidate technical requirements to be verified. Replace the restricted technical requirements with the technical requirements redefined by the exception clause according to the exception clause restriction relationship. Determine the technical requirements retained in the same technical object, the corresponding execution condition, and the processed set of candidate technical requirements to be verified as the result of the technical requirements to be verified.
[0105] Specifically: taking a technical object and a set of execution conditions as a processing unit, first obtain the corresponding technical requirements from the clauses that directly record the current technical object and the current execution conditions, then read the referenced clauses in sequence according to the reference relationship corresponding to the current clause content, only obtain the technical requirements corresponding to the current technical object and the current execution conditions, and add each obtained technical requirement, together with the corresponding technical object and execution conditions, as an element to the set of candidate technical requirements to be verified.
[0106] During data processing: the reference reading uses the same read clause number record as in Example 2. Each time a reference target number is read, the reference target number is added to the read clause number record. When a subsequent reference points to a number that already exists in the read clause number record, it will not be read again. When all the reference target numbers to be read have been read and no new reference target numbers have been generated, the current reference reading process ends. Therefore, it can avoid the repeated processing caused by circular references.
[0107] It should be noted that when the referenced clause in the standard text to be verified does not repeatedly record the technical object and execution conditions, the technical object and execution conditions corresponding to the current clause content shall be taken as the technical object and execution conditions corresponding to the referenced technical requirements, in accordance with the inheritance rules in Example 2.
[0108] Specifically: After forming a set of candidate technical requirements to be verified, the corresponding exception clause restriction relationship is read item by item. First, the recorded technical object is compared with the current technical object. Then, the execution conditions limited by the exception clause are compared with the current execution conditions. For category-type execution conditions, the character content is compared according to the category name. For numerical execution conditions, they are first converted to the unit used by the corresponding technical content in the benchmark standard text according to the fixed conversion relationship of the same physical quantity. Then, the upper and lower boundaries, boundary inclusion relationships and comparison relationships are compared. When multiple execution conditions jointly limit the same technical requirement, the corresponding replacement process is only performed after all execution conditions meet the limit content.
[0109] It should be noted that when the exception clause only redefines part of the original technical requirements, only that part is replaced with the content rewritten in the exception clause. The execution actions, technical parameters, and judgment contents that were not redefined in the original technical requirements are retained. For example, if the original technical requirements include test temperature, test time, and insulation resistance judgment requirements, but the exception clause only redefines the insulation resistance judgment requirements, the original test temperature and test time are retained after the replacement. This results in all the technical requirements that are ultimately retained under the current technical object and current execution conditions.
[0110] In the scenario set in Example 1: if the standard text to be verified still specifies that the basic insulation resistance requirement for Class A insulating components is not less than 100 MΩ, but the thickness condition in the exception clause is adjusted from "less than 2 mm" to "less than 3 mm", then 3 mm is read as the new condition boundary and the thickness condition is divided into "less than 3 mm" and "greater than or equal to 3 mm" according to the numerical range. For Class A insulating components with a thickness of 2.5 mm, the processing result corresponding to the benchmark standard text still adopts the technical requirement of not less than 100 MΩ, while the processing result corresponding to the standard text to be verified adopts the insulation resistance technical requirement redefined in the exception clause. Thus, different results of the technical requirements to be verified can be obtained without changing the original insulation resistance value itself.
[0111] Specifically: S4 includes:
[0112] S41, establish a correspondence between the benchmark technical requirement result and the technical requirement result to be verified according to the same technical object, and retain the technical objects that have not been correspondingly established respectively; then establish a correspondence between the execution conditions with the same content under the same technical object that have been correspondingly established, and retain the execution conditions that have not been correspondingly established respectively.
[0113] Specifically: First, read the technical objects in the benchmark technical requirements results and the technical requirements to be verified results respectively. After the category name is cleaned up as described above, establish a correspondence between two technical objects with the same character content. Technical objects without a correspondence are retained along with their execution conditions and technical requirements. Then, read the execution conditions under the same technical object with a correspondence. For category-type execution conditions, compare them item by item according to the category name. For numerical execution conditions, after converting to the same unit, compare the physical quantity name, comparison relationship, boundary value, and boundary inclusion relationship. If all the above are the same, establish a correspondence. The remaining execution conditions are retained in the benchmark technical requirements results and the technical requirements to be verified results respectively as input for subsequent difference judgment.
[0114] It should be noted that when there are interval boundary changes in numerical execution conditions, all boundary values in the two results are first summarized and divided into non-overlapping condition intervals according to the numerical order. Then, the technical requirements corresponding to each condition interval in the benchmark technical requirement result and the technical requirement result to be verified are determined separately. For example, when comparing "less than 2 mm" and "less than 3 mm", 2 mm and 3 mm are used as boundaries to form three condition intervals: "less than 2 mm", "greater than or equal to 2 mm and less than 3 mm", and "greater than or equal to 3 mm". This can clearly determine the range of conditions in which the actual technical requirements change.
[0115] S42, the following are identified as the technical requirement difference content: the technical object and its corresponding execution conditions and technical requirements that have not been established, the technical requirements that have not been established, the technical requirements that exist only on the side of the benchmark technical requirement result under the established execution conditions, the technical requirements that exist only on the side of the technical requirement result to be verified, and the technical requirements that exist on both sides but have inconsistent content. The integrity verification result is generated based on the technical requirement difference content.
[0116] Specifically: After establishing the correspondence in S41, check each item of the data. Record the technical objects that do not have a corresponding counterpart, along with their corresponding execution conditions and technical requirements, as technical requirement difference content. Record the execution conditions that only exist in one result as technical requirement difference content. For the execution conditions that have a corresponding counterpart, read the execution actions, technical parameters, units, comparison relationships, and judgment contents from the technical requirements on both sides respectively. After converting the units to the same unit, compare each item. When a technical requirement only exists in the benchmark technical requirement result, record the missing content. When a technical requirement only exists in the technical requirement result to be verified, record the added content. When both sides have corresponding technical requirements but the execution actions, converted parameter values, comparison relationships, and judgment contents are different, record the specific different items. The above records together constitute the technical requirement difference content.
[0117] It should be noted that "approximately identical", "basically identical" and similarity thresholds are not used as the criteria for judgment. The action is to first remove leading and trailing spaces, consecutive spaces, newlines, and differences in full-width and half-width punctuation. Then, the characters are compared according to the processed character sequences. If the character sequences are the same, the actions are considered to be the same; if the character sequences are different, the actions are considered to be different. The numerical values are compared using the actual values after unit conversion. The comparison relationships are distinguished by greater than, greater than or equal to, less than, less than or equal to, and equal to. The judgment content is based on the comparison of the character sequences after removing leading and trailing spaces, consecutive spaces, newlines, and differences in full-width and half-width punctuation. Therefore, each technical requirement difference can be clearly mapped to a specific data item.
[0118] S42 includes:
[0119] S421, if the difference in the technical requirements is not obtained, the integrity verification result is determined to be consistent with the result of the benchmark technical requirements and the result of the technical requirements to be verified;
[0120] Specifically: After comparing all technical objects, all execution conditions and all technical requirements, check whether any technical requirement difference is formed. If no technical requirement difference is formed, it means that all technical requirements finally determined by the two standard texts under the same technical objects and corresponding execution conditions have passed the above item-by-item comparison. Therefore, the integrity verification result is recorded as the result of the benchmark technical requirement being consistent with the result of the technical requirement to be verified.
[0121] S422, when the technical requirement difference content is obtained, the integrity verification result is determined to be inconsistent between the benchmark technical requirement result and the technical requirement result to be verified, and the corresponding technical object, execution condition and technical requirement difference content are recorded in the integrity verification result.
[0122] Specifically: When at least one technical requirement difference is formed, the integrity verification result is recorded as the inconsistency between the baseline technical requirement result and the technical requirement to be verified. At the same time, for each technical requirement difference, the corresponding technical object, execution conditions, clause number where the difference is located, and the specific technical requirement that has changed are saved. This allows it to be determined directly based on the integrity verification result which object, under which conditions, and which technical content has changed.
[0123] In this embodiment, by using the same reading and processing rules as the benchmark standard text to form the technical requirements to be verified, the technical objects, execution conditions and technical requirements in the standard text to be verified are used to form the technical requirements to be verified. Then, the technical requirements differences are determined according to the same technical objects and corresponding execution conditions, and the integrity verification results are generated. This can directly determine the actual impact range and corresponding technical requirements caused by the adjustment of local conditions in the standard text. For example, when the thickness boundary in the exception clause is adjusted from 2 mm to 3 mm, it can be further determined that the insulation resistance judgment requirements of the electrical insulation components in the range of 2 mm to 3 mm have changed. This avoids the situation where only the text of the clause is modified but the specific affected objects, condition range and technical requirements cannot be determined.
[0124] Example 4
[0125] Based on the product inspection standard application scenario set in Example 1 and the data processing process in Examples 2 and 3, this embodiment further explains the data input, processing actions, data transmission between modules, and processing results of each module in the system. The system is deployed on existing servers and computer equipment. The processor reads the program instructions stored in the memory to complete the standard text reading, clause content processing, technical requirement determination, and integrity verification, without the need to add dedicated hardware equipment.
[0126] A data integrity protection system based on standard text, please refer to... Figure 2 Specifically, including:
[0127] The benchmark standard text processing module is used to acquire the benchmark standard text and determine the technical object, the execution conditions, the technical requirements, the reference relationships, and the exception clause restriction relationships from the benchmark standard text;
[0128] Specifically: The benchmark text processing module receives the standard text file as the basis for integrity comparison, obtains the chapter number, clause number, table number, and appendix number according to the numbering method described in Embodiment 2, obtains the clause content according to the start and end positions corresponding to each number, and then reads the object name, condition limitation content, execution action, technical parameters, judgment content, and reference number from each clause content. According to the content determination rules in Embodiment 2, the technical object, execution condition, and technical requirement are formed, and the reference relationship is determined according to the clause pointing to the reference number. The restriction relationship of the exception clause is determined according to the execution condition, the restricted technical requirement, and the redefined technical requirement in the exception clause. The processed data is stored in the memory according to the clause number and provided to the benchmark technical requirement determination module for calling.
[0129] It should be noted that when the benchmark text processing module reads Word documents, PDFs, and standard texts that have already been converted into readable character content, it uses the original clause numbers, text content, numerical values, units, and comparison relationships in the standard text as the processing basis. For PDFs and scanned documents that only contain images, they are first converted into text files containing readable character content before being input into the benchmark text processing module. For numerical content, it saves the comparison relationships, numerical values, and units separately. For categorical content, it saves the corresponding category name. For cited content, it saves the citation start number and citation target number, thereby ensuring that all subsequent data can be traced back to the specific source location in the benchmark text.
[0130] The benchmark technical requirements determination module is used to determine the final technical requirements to be adopted under each of the aforementioned technical objects based on the execution conditions, the reference relationships, and the exception clause restriction relationships, thereby obtaining the benchmark technical requirements result.
[0131] Specifically: The benchmark technical requirement determination module sequentially reads a technical object and its corresponding execution condition. First, it obtains the technical requirement directly recorded in the corresponding clause content. Then, it reads the technical requirement corresponding to the current technical object and the current execution condition in the referenced clause content along the reference relationship. The obtained technical requirement, together with the technical object and the execution condition, is added to the benchmark candidate technical requirement set. Subsequently, it reads the corresponding exception clause restriction relationship and determines whether the current execution condition meets the exception clause restriction content according to the condition comparison rule in Embodiment 2. If it does, the restricted technical requirement is deleted and the technical requirement redefined by the exception clause is added. After all reference content and exception clauses are processed, the current technical object, the corresponding execution condition, and all the technical requirements retained in the benchmark candidate technical requirement set are saved together as the benchmark technical requirement result.
[0132] In the scenario set in Example 1: when the technical object is a Class A insulating component and the execution condition is a thickness of less than 2 mm, the benchmark technical requirement determination module reads the test method in the basic clause, obtains the corresponding test temperature and test time along the reference relationship, and replaces the basic insulation resistance determination requirement with the insulation resistance determination requirement specified in the exception clause according to the exception clause restriction relationship, thereby obtaining the benchmark technical requirement result for subsequent comparison under this thickness condition.
[0133] The standard text processing module is used to obtain the standard text to be verified, determine the technical object, execution conditions, technical requirements, reference relationships and exception clause restriction relationships in the standard text to be verified, and determine the technical requirements finally adopted under each execution condition to obtain the technical requirements to be verified result.
[0134] Specifically: The standard text processing module receives the revised, re-imported, and version-updated standard text to be verified. It uses the same numbering, clause division, content determination, unit conversion, and condition judgment rules as the benchmark standard text processing module to obtain the technical object, the execution condition, the technical requirement, the reference relationship, and the exception clause restriction relationship. Then, it forms the candidate technical requirement set to be verified according to the same direct technical requirement reading, reference content reading, and exception clause replacement process as the benchmark technical requirement determination module. Finally, it saves the same technical object, the corresponding execution condition, and the technical requirement finally retained in the candidate technical requirement set to be verified as the technical requirement result to be verified.
[0135] It should be noted that the benchmark technical requirement results and the technical requirement results to be verified are stored in the same data composition format. Each result contains at least one technical object, a corresponding set of execution conditions, and all the technical requirements ultimately retained under the set of execution conditions, thereby avoiding the situation where the two sides cannot be directly compared due to different data structures and processing rules.
[0136] In the scenario set in Example 1: if the thickness condition in the exception clause of the standard text to be verified is changed from less than 2 mm to less than 3 mm, the standard text processing module to be verified will redetermine the technical requirements corresponding to each thickness range according to the new condition boundary. Therefore, Class A insulating components with a thickness in the range of 2 mm to 3 mm will form a technical requirement result to be verified that is different from the benchmark technical requirement result.
[0137] The integrity verification module is used to compare the benchmark technical requirement result with the technical requirement result to be verified according to the same technical object and the corresponding execution conditions, and generate the integrity verification result based on the comparison result. Each module is executed by the processor calling the program instructions stored in the memory to perform the corresponding data processing operation.
[0138] Specifically: The integrity verification module first establishes a correspondence between the benchmark technical requirement result and the technical requirement result to be verified according to the technical object name, and retains the technical objects that have not established a correspondence. Then, it reads the execution conditions under the same technical object that have established a correspondence. The categorical execution conditions are compared according to the category name. The numerical execution conditions are compared by physical quantity name, boundary value, comparison relationship and boundary inclusion method after being converted to the same unit. The module handles the case where the boundary of the two sides of the conditions is different according to the interval division method in Example 3. Then, it compares the execution action, technical parameter, unit, comparison relationship and judgment content under the corresponding execution conditions item by item, and records the technical objects that have not established a correspondence and their corresponding execution conditions and technical requirements, the execution conditions that have not established a correspondence, the technical requirements that exist on one side, and the technical requirements whose corresponding contents on both sides are different as the technical requirement difference content.
[0139] Specifically: when no technical requirement difference is generated after comparing all the technical objects, execution conditions, and technical requirements, the integrity verification module records the integrity verification result as consistent with the baseline technical requirement result and the technical requirement to be verified result. When at least one technical requirement difference is generated, the integrity verification result is recorded as inconsistent with the baseline technical requirement result and the technical requirement to be verified result, and the corresponding technical object, execution condition, clause number, and technical requirement difference are saved at the same time, so as to directly determine the specific technical content that has changed and its corresponding condition range based on the integrity verification result.
[0140] In the scenario set in Example 1: when the basic insulation resistance determination value itself is not modified but the thickness range of the exception clause changes from less than 2 mm to less than 3 mm, the integrity verification module can determine the thickness of 2 mm to 3 mm as the changed execution condition range, and further determine that the insulation resistance determination requirement in the benchmark technical requirement result within this range is different from the insulation resistance determination requirement in the technical requirement result to be verified, thereby generating the integrity verification result containing the differences between the corresponding technical object, the execution condition and the technical requirement.
[0141] During system operation, the processor calls program instructions in the memory in the data processing order of the benchmark standard text processing module, the benchmark technical requirements determination module, the standard text to be verified processing module, and the integrity verification module. The memory respectively stores the original standard text, the parsed clause content, the reference relationship, the exception clause restriction relationship, the benchmark technical requirements result, the technical requirements to be verified result, and the integrity verification result. The data generated by the previous module serves as the input of the next module. Therefore, the complete data processing process from reading the standard text to outputting the integrity result can be completed in the existing computer and server environment.
[0142] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.
Claims
1. A method for data integrity protection based on a standard text, characterized by, Includes the following steps: S1. Obtain the benchmark standard text, extract the technical objects, implementation conditions and technical requirements from the benchmark standard text, and determine the reference relationship and the restriction relationship of the exception clauses according to the reference content and exception clauses between the clauses; S2, for each technical object, determine the technical requirements corresponding to each execution condition, obtain the referenced technical requirements along the reference relationship, and adjust the corresponding technical requirements according to the restriction relationship of the exception clause, and determine the technical requirements finally adopted under each execution condition as the benchmark technical requirements result; S3, obtain the standard text to be verified, determine the technical objects, execution conditions, technical requirements, reference relationships and exception clauses in the standard text to be verified, and determine the final technical requirements to be adopted under each execution condition according to the execution conditions, reference relationships and exception clauses, and use the determined results as the technical requirements to be verified results; S4. Using the same technical object as the corresponding basis, compare the benchmark technical requirement result with the technical requirement result to be verified according to the corresponding execution conditions, and generate the integrity verification result based on the comparison result.
2. The method of claim 1, wherein, S1 includes: S11, Read the chapter number, clause number, table number and appendix number in the benchmark text, determine the content level according to the chapter number, determine the start and end positions of the corresponding content according to the clause number, table number and appendix number, and determine the text content and table content between each start and end position as the clause content; S12, determine the technical object, the execution conditions, and the technical requirements from each of the aforementioned clauses, determine the reference relationship based on the reference content between different clauses, and determine the restriction relationship of the exception clauses based on the condition limitation content, restricted content, and redefined content in the exception clauses.
3. The method of claim 2, wherein, S12 includes: S121, Read the object name, condition limitation content, execution action, technical parameters and judgment content in each of the aforementioned clauses, determine the object name to which the execution action, technical parameters and judgment content are targeted as the technical object, determine the condition limitation content that limits the execution scope of the execution action, technical parameters and judgment content as the execution condition, and determine the corresponding execution action, technical parameters and judgment content as the technical requirement; S122, Read the reference number recorded in each of the aforementioned clauses, locate the referenced clause according to the reference number, determine the pointing relationship between the clause recording the reference number and the referenced clause as the reference relationship, read the execution conditions limited by the exception clause, the restricted technical requirements, and the redefined technical requirements, and determine the correspondence between the three as the exception clause restriction relationship.
4. The method of claim 3, wherein, S2 includes: S21, for each of the aforementioned technical objects, read the corresponding execution conditions one by one, obtain the technical requirements directly recorded by the clause content under the current execution conditions and the referenced technical requirements obtained along the reference relationship, and form a set of benchmark candidate technical requirements together with the corresponding technical objects and execution conditions; S22, determine whether the current execution condition meets the conditions limited by the exception clause based on the restriction relationship of the exception clause. If the current execution condition meets the conditions limited by the exception clause, replace the restricted technical requirement with the technical requirement redefined by the exception clause, and determine the benchmark technical requirement result based on the processed set of benchmark candidate technical requirements.
5. A data integrity protection method based on standard text according to claim 4, characterized in that, S21 includes: S211, locate the corresponding clause content based on the same technical object and the current execution condition, read the technical requirements directly recorded in the clause content, and add the technical requirements together with the corresponding technical object and the execution condition to the benchmark candidate technical requirements set; S212, read the reference relationship corresponding to the current clause content, locate the referenced clause content according to the number pointed to by the reference relationship, add the technical requirements in the referenced clause content that correspond to the current technical object and the current execution condition to the benchmark candidate technical requirement set, when the referenced clause content does not repeatedly record the technical object and the execution condition, add the current technical object and the current execution condition as the technical object and the execution condition corresponding to the referenced technical requirement to the benchmark candidate technical requirement set, continue to read the referenced clause content that continues to record reference content according to the reference relationship, and do not repeat the reading of the clause content that has already been read, until no new referenced clause content is obtained.
6. A data integrity protection method based on standard text according to claim 5, characterized in that, S22 includes: S221, Read the execution conditions in the exception clause restriction relationship one by one, compare the current execution condition with the execution conditions limited by the exception clause, and when the current execution condition satisfies the execution conditions limited by the exception clause, determine the restricted technical requirement from the benchmark candidate technical requirement set according to the exception clause restriction relationship; S222, the restricted technical requirement is removed from the benchmark candidate technical requirement set, the technical requirement redefined by the exception clause, together with the corresponding technical object and the execution condition, is added to the benchmark candidate technical requirement set. After processing the restriction relationship corresponding to the exception clause, the same technical object, the corresponding execution condition, and the technical requirement retained in the benchmark candidate technical requirement set are jointly determined as the benchmark technical requirement result.
7. A data integrity protection method based on standard text according to claim 6, characterized in that, S3 includes: S31, Read the chapter number, clause number, table number and appendix number in the standard text to be verified and obtain the corresponding clause content, and obtain the technical object, execution conditions, technical requirements, reference relationship and exception clause restriction relationship according to the content determination method in S12; S32, for each technical object and the corresponding execution condition, obtain the directly recorded technical requirements and the referenced technical requirements corresponding to the current technical object and the current execution condition obtained along the reference relationship. Combine the obtained technical requirements with the corresponding technical object and the execution condition to form a set of candidate technical requirements to be verified. Replace the restricted technical requirements with the technical requirements redefined by the exception clause according to the exception clause restriction relationship. Determine the technical requirements retained in the same technical object, the corresponding execution condition, and the processed set of candidate technical requirements to be verified as the result of the technical requirements to be verified.
8. A data integrity protection method based on standard text according to claim 7, characterized in that, S4 includes: S41, establish a correspondence between the benchmark technical requirement result and the technical requirement result to be verified according to the same technical object, and retain the technical objects that have not been correspondingly established respectively; then establish a correspondence between the execution conditions with the same content under the same technical object that have been correspondingly established, and retain the execution conditions that have not been correspondingly established respectively. S42, the following are identified as the technical requirement difference content: the technical object and its corresponding execution conditions and technical requirements that have not been established, the technical requirements that have not been established, the technical requirements that exist only on the side of the benchmark technical requirement result under the established execution conditions, the technical requirements that exist only on the side of the technical requirement result to be verified, and the technical requirements that exist on both sides but have inconsistent content. The integrity verification result is generated based on the technical requirement difference content.
9. The method of claim 8, wherein, S42 includes: S421, if the difference in the technical requirements is not obtained, the integrity verification result is determined to be consistent with the result of the benchmark technical requirements and the result of the technical requirements to be verified; S422, when the technical requirement difference content is obtained, the integrity verification result is determined to be inconsistent between the benchmark technical requirement result and the technical requirement result to be verified, and the corresponding technical object, execution condition and technical requirement difference content are recorded in the integrity verification result.
10. A standard text-based data integrity protection system applied to the standard text-based data integrity protection method of any one of claims 1 to 9, characterized in that, include: The benchmark standard text processing module is used to acquire the benchmark standard text and determine the technical object, the execution conditions, the technical requirements, the reference relationships, and the exception clause restriction relationships from the benchmark standard text; The benchmark technical requirements determination module is used to determine the final technical requirements to be adopted under each of the aforementioned technical objects based on the execution conditions, the reference relationships, and the exception clause restriction relationships, thereby obtaining the benchmark technical requirements result. The standard text processing module is used to obtain the standard text to be verified, determine the technical object, execution conditions, technical requirements, reference relationships and exception clause restriction relationships in the standard text to be verified, and determine the technical requirements finally adopted under each execution condition to obtain the technical requirements to be verified result. The integrity verification module is used to compare the benchmark technical requirement result with the technical requirement result to be verified according to the same technical object and the corresponding execution conditions, and generate the integrity verification result based on the comparison result. Each module is executed by the processor calling the program instructions stored in the memory to perform the corresponding data processing operation.
