Fault simulation-oriented data preparation method, apparatus and device, and medium

By performing pattern distinction of the fault list and generating the safety mechanism coverage node list before the fault simulation, and determining the fault injection time with the normal distribution model, the problem of inability to flexibly set different fault modes in the fault simulation in the existing technology is solved, and the problem of the inability to flexibly set different fault modes in the fault simulation in the existing technology is improved Accuracy of fault simulation and system security assessment.

CN118897792APending Publication Date: 2024-11-05中科鉴芯(北京)科技有限责任公司
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202410839149.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-06-26
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

Before failure simulation, the existing technology failed to effectively distinguish different fault modes, resulting in the inability to flexibly set up faults in different fault modes during failure simulation, which affected the accuracy and comprehensiveness of the system's safety evaluation and verification.

Method used

Use preset mode to generate a fault list on the target circuit, identify whether the fault covers the safety mechanism, and generate a safety mechanism cover node list based on the identification results, obtain the soft fault rate, and build a normal distribution model to determine the optimal injection time of transient faults. , update the fault list to accurately handle permanent and transient faults in fault simulation.

Benefits of technology

By conducting detailed fault generation and safety mechanism analysis of different fault modes, target data can be generated that can be used for fault simulation, solving the problem that different fault modes cannot be flexibly set during fault simulation, and improving the system's safety evaluation and fault handling Accuracy and effectiveness.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118897792A_ABST
    Figure CN118897792A_ABST
Patent Text Reader

Abstract

The invention relates to a fault simulation-oriented data preparation method and device, equipment and a medium, and the method comprises the steps: carrying out the fault generation on a target circuit through employing a preset mode, obtaining a fault list, enabling the fault modes in the fault list to comprise a transient fault and a permanent fault, and enabling the fault list to comprise the fault time of each fault; identifying whether each fault in the fault list covers a security mechanism, and generating a security mechanism coverage node list according to an identification result; obtaining a soft fault rate, constructing a normal distribution model matched with the soft fault rate to determine the optimal injection time of the transient fault, and updating the fault list by using the optimal injection time; the security mechanism coverage node list and the fault list are determined as target data, and the target data are used for fault simulation. The problem that faults of different fault modes cannot be flexibly and correspondingly set during fault simulation is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of digital circuit technology, and in particular to a data preparation method, device, equipment and medium for fault simulation. Background Art

[0002] Functional safety verification is an important part of the functional safety implementation process. Fault simulation, as the most commonly used functional safety verification method, is to troubleshoot all potential faults in the design and determine whether these faults can be detected. Before fault simulation, a series of data preparation is required. It is necessary to clearly know the possible location of the fault and the fault injection time, so as to accurately simulate the occurrence and impact of the fault during the simulation process.

[0003] At present, in the data preparation stage before fault simulation, different fault modes are often not distinguished, resulting in the inability to flexibly set corresponding faults of different fault modes during fault simulation.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The present application provides a data preparation method, device, equipment and medium for fault simulation to solve the above-mentioned technical problem of "not being able to flexibly set corresponding faults of different fault modes during fault simulation".

[0006] According to one aspect of an embodiment of the present application, the present application provides a data preparation method for fault simulation, including: using a preset mode to generate faults on a target circuit to obtain a fault list, wherein the fault modes in the fault list include transient faults and permanent faults, and the fault list includes the fault time of each fault; identifying whether each fault in the fault list covers a safety mechanism, and generating a safety mechanism coverage node list based on the identification result; obtaining a soft failure rate, and constructing a normal distribution model matching the soft failure rate to determine the optimal injection time for transient faults, and using the optimal injection time to update the fault list; determining the safety mechanism coverage node list and the fault list as target data, wherein the target data is used for fault simulation.

[0007] Optionally, a preset mode is used to generate faults on the target circuit to obtain a fault list, including: when the preset mode is the first mode, counting the first ports corresponding to the unit level of the target circuit, wherein the first ports include input ports, output ports, and bidirectional ports; determining the fault type and fault mode, and generating a fault corresponding to the fault type and fault mode on the first port; recording the fault type, fault mode, fault location, and fault time of the fault to generate a fault list.

[0008] Optionally, a preset mode is used to generate faults on the target circuit to obtain a fault list, including: when the preset mode is the second mode, counting the second ports corresponding to the unit level of the target circuit, wherein the second ports include output ports; determining the fault type and fault mode, and generating a fault corresponding to the fault type and fault mode on the second port; recording the fault type, fault mode, fault location and fault time of the fault to generate a fault list.

[0009] Optionally, identify whether each fault in the fault list covers the safety mechanism, and generate a list of nodes covered by the safety mechanism based on the identification results, including: hierarchically dividing the target circuit to obtain a hierarchical structure corresponding to the target circuit, wherein each hierarchy includes at least one functional module; identifying the input port and output port of each functional module, and determining the propagation path of the signal through the input port and the output port; identifying the first node on the propagation path, wherein the first node includes an intermediate node and a key node; obtaining a safety mechanism file, and determining the second node covered by the safety mechanism in the first node based on the safety mechanism file; integrating the coverage information of each second node to generate a list of nodes covered by the safety mechanism.

[0010] Optionally, the coverage information of each second node is integrated to generate a security mechanism coverage node list, including: determining the name of the security mechanism covering each second node according to the security mechanism file, and determining the alarm information triggered by the second node; mapping the alarm information and the security mechanism name as coverage information and saving them with the second node to obtain a security mechanism coverage node list.

[0011] Optionally, a normal distribution model matching the soft failure rate is constructed to determine the optimal injection time of transient failures, and the optimal injection time is used to update the fault list, including: obtaining a candidate time interval to be tested, wherein the candidate time interval includes multiple test time intervals; constructing a normal distribution model corresponding to the soft failure rate, and using the normal distribution model to respectively determine the optimal injection time in each test time interval; and replacing the failure time of the transient failure in the fault list with the optimal injection time to update the fault list.

[0012] Optionally, a normal distribution model corresponding to the soft failure rate is constructed, and the normal distribution model is used to determine the optimal injection time in each test time interval, including: obtaining a confidence interval and normal distribution parameters that match the soft failure rate; establishing a normal distribution model based on the normal distribution parameters; sampling a random number as an expected value in each test time interval according to the normal distribution model; adding random noise to the expected value to obtain candidate injection times for transient faults; and verifying the candidate injection times within the confidence interval to obtain the optimal injection time.

[0013] According to another aspect of an embodiment of the present application, the present application provides a data preparation device for fault simulation, including: a fault generation module, used to generate faults on a target circuit using a preset mode to obtain a fault list, wherein the fault modes in the fault list include transient faults and permanent faults, and the fault list includes the fault time of each fault; a list generation module, used to identify whether each fault in the fault list covers a safety mechanism, and generate a safety mechanism coverage node list based on the identification result; a list update module, used to obtain a soft failure rate, and construct a normal distribution model matching the soft failure rate to determine the optimal injection time of transient faults, and use the optimal injection time to update the fault list; a data processing module, used to determine the safety mechanism coverage node list and the fault list as target data, wherein the target data is used for fault simulation.

[0014] According to another aspect of an embodiment of the present application, the present application provides an electronic device, including a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, the memory and the processor communicate through the communication bus and the communication interface, and the steps of the above method are implemented when the processor executes the computer program.

[0015] According to another aspect of an embodiment of the present application, the present application also provides a computer-readable medium having a non-volatile program code executable by a processor, and the program code enables the processor to execute the above method.

[0016] The above technical solution provided by the embodiment of the present application has the following advantages compared with the related art:

[0017] The present application adopts a data preparation method for fault simulation, including: using a preset mode to generate faults on a target circuit to obtain a fault list, wherein the fault modes in the fault list include transient faults and permanent faults, and the fault list includes the fault time of each fault; identifying whether each fault in the fault list covers the safety mechanism, and generating a safety mechanism coverage node list according to the identification result; obtaining a soft fault rate, and constructing a normal distribution model matching the soft fault rate to determine the optimal injection time of the transient fault, and using the optimal injection time to update the fault list; determining the safety mechanism coverage node list and the fault list as target data, wherein the target data is used for fault simulation. The fault list and the safety mechanism coverage node list are generated by performing fault generation and safety mechanism analysis on permanent faults and transient faults, and the injection time of transient faults is re-determined separately by a normal distribution model to distinguish the fault injection time of different fault modes, and obtain target data that can be used for fault simulation, solving the problem that the faults of different fault modes cannot be flexibly set accordingly during fault simulation. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0020] Figure 1 A flowchart of an optional data preparation method for fault simulation provided according to an embodiment of the present application;

[0021] Figure 2 A block diagram of an optional data preparation device for fault simulation provided according to an embodiment of the present application;

[0022] Figure 3 A schematic diagram of an optional electronic device structure provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0024] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application and have no specific meaning. Therefore, "module" and "component" can be used interchangeably.

[0025] Functional safety verification is an important part of the functional safety implementation process. Fault simulation, as the most commonly used functional safety verification method, is to troubleshoot all potential faults in the design and determine whether these faults can be detected. Before fault simulation, a series of data preparation is required. It is necessary to clearly know the possible location of the fault and the fault injection time, so as to accurately simulate the occurrence and impact of the fault during the simulation process.

[0026] At present, in the data preparation stage before fault simulation, different fault modes are often not distinguished, resulting in the inability to flexibly set corresponding faults of different fault modes during fault simulation.

[0027] Current technologies have some limitations in handling permanent and transient faults. Although the fault generation points and nodes may be similar in these two types of faults, there are significant differences in the timing and duration of fault injection. This difference leads to challenges in safety analysis requirements, calculation methods, and higher safety requirements. Existing technologies have difficulties in accurately setting and specifying fault generation points, and it is difficult to meet the precise identification and detailed recording of different fault types, which is crucial for system safety assessment and verification.

[0028] When dealing with fault injection, existing technologies are unable to fully meet the analysis and classification requirements of different fault types and fault modes. At the same time, existing methods also have certain limitations in terms of fault duration and processing efficiency under specific fault types, which may affect the accuracy and comprehensiveness of system safety assessments. These limitations greatly reduce the accuracy and effectiveness of safety verification and affect the reliability and stability of the system. Therefore, there is room for improvement in current technologies in terms of fault handling.

[0029] In the process of safety analysis, each fault may not be equivalent, so multiple situations need to be considered in the fault generation mode. In the current fault list generation compensation policy, there is a lack of consideration of such weighting or fault type generation mode. Therefore, the safety analysis after safety verification (fault simulation) may have weak credibility and large errors in the calculation results.

[0030] In order to solve the problems mentioned in the background technology, according to one aspect of the embodiment of the present application, a data preparation method for fault simulation is provided, such as Figure 1 As shown, including:

[0031] Step 101, generating faults on a target circuit using a preset mode to obtain a fault list, wherein the fault modes in the fault list include transient faults and permanent faults, and the fault list includes the fault time of each fault;

[0032] Step 103, identifying whether each fault in the fault list covers the safety mechanism, and generating a safety mechanism coverage node list according to the identification result;

[0033] Step 105, obtaining a soft failure rate, and constructing a normal distribution model matching the soft failure rate to determine an optimal injection time for transient faults, and using the optimal injection time to update a fault list;

[0034] Step 107: determine the safety mechanism coverage node list and the fault list as target data, wherein the target data is used for fault simulation.

[0035] The solution provided in this application is designed to enable the user to provide only a safety mechanism file and a fault type, and this application will be able to generate a target data set for the user that can be used directly for fault simulation. The target data includes detailed information on transient faults and permanent faults, such as the coverage of the safety mechanism, detailed injection locations, and injection times.

[0036] The target data provided in this application can be used for fault simulation, so that permanent faults and transient faults can be accurately and comprehensively handled in fault simulation, and the detailed data and simulation conditions required for system safety assessment are provided.

[0037] By setting a specific fault time (including duration), we can observe the system performance when the fault occurs, as well as the system recovery process after the fault disappears. This is of great significance for optimizing the system's fault handling strategy and improving the system's robustness and reliability.

[0038] The preset modes provided in the present application include a port mode (ie, the first mode of the present application) and a gate-level transistor mapping mode (ie, the first mode of the present application). The two modes are described in turn below.

[0039] As an optional embodiment, a preset mode is used to generate faults on a target circuit to obtain a fault list, including: when the preset mode is a first mode, counting the first ports corresponding to the unit level of the target circuit, wherein the first ports include input ports, output ports, and bidirectional ports; determining the fault type and fault mode, and generating a fault corresponding to the fault type and fault mode on the first port; recording the fault type, fault mode, fault location, and fault time of the fault to generate a fault list.

[0040] The first mode provided by the present application is to generate faults on all ports at the cell level (ie, the unit level of the present application).

[0041] Specifically, the fault mode includes a transient fault and a permanent fault, the fault location indicates the location where the fault is generated, and the fault time indicates the injection time of the fault. For a permanent fault, the fault time also includes the duration.

[0042] Failure types include, but are not limited to, single-point failures, multiple-point failures, residual failures, and safety failures.

[0043] The user will provide a fault type and a fault mode, and the present application will generate a corresponding fault on the first port according to the fault type and the fault mode.

[0044] As an optional embodiment, a preset mode is used to generate faults on a target circuit to obtain a fault list, including: when the preset mode is a second mode, counting the second ports corresponding to the unit level of the target circuit, wherein the second ports include output ports; determining the fault type and fault mode, and generating a fault corresponding to the fault type and fault mode on the second port; recording the fault type, fault mode, fault location and fault time of the fault to generate a fault list.

[0045] The second mode provided by the present application is to generate faults on all output ports at the cell level (ie, the unit level of the present application).

[0046] For example, the information of the output port may be extracted by parsing a cell library file (eg, a lib.tc file).

[0047] After determining the output port generating the fault, the fault generation is performed in a manner similar to that in the first mode, which will not be described in detail here.

[0048] It is necessary to record which cell each fault is associated with, because the fault on each output port will be mapped to the cell in the subsequent safety analysis calculation.

[0049] As an optional embodiment, identifying whether each fault in a fault list covers a safety mechanism, and generating a safety mechanism coverage node list based on the identification result, includes: dividing the target circuit into levels to obtain a hierarchical structure corresponding to the target circuit, wherein each level includes at least one functional module; identifying the input port and output port of each functional module, and the propagation path of the signal through the input port and the output port; identifying the first node on the propagation path, wherein the first node includes an intermediate node and a key node; obtaining a safety mechanism file, and determining the second node in the first node covered by the safety mechanism based on the safety mechanism file; integrating the coverage information of each second node to generate a safety mechanism coverage node list.

[0050] Specifically, the target circuit is hierarchically divided to obtain a hierarchical structure corresponding to the target circuit, including: decomposing the target circuit into different layers or levels based on its structure and function; further dividing each layer into independent modules or components, each module should have clear functions and interfaces to facilitate separate testing and analysis.

[0051] Hierarchical division of the target circuit helps to understand the overall architecture of the circuit and the relationship between its various parts.

[0052] In the process of tracing the logical path, analyze how the security mechanism implements its security functions at each node.

[0053] Specifically, intermediate nodes are points in a circuit that connect two or more components. Critical nodes play an important role in a circuit and they may have a significant impact on the function, performance or safety of the circuit.

[0054] The security mechanism file is a file prepared in advance that meets the user's requirements for inserting the security mechanism.

[0055] Specifically, determining the second node covered by the security mechanism in the first node according to the security mechanism file includes: determining the coverage range of each security mechanism according to the security mechanism file; and determining the second node within the coverage range.

[0056] It is also necessary to record the security mechanism coverage information of each second node in detail. Therefore, after finding the second node covered by the security mechanism, the present application also needs to map and save the coverage information with the second node to obtain a list of nodes covered by the security mechanism.

[0057] As an optional embodiment, the coverage information of each second node is integrated to generate a security mechanism coverage node list, including: determining the name of the security mechanism covering each second node according to the security mechanism file, and determining the alarm information triggered by the second node; mapping the alarm information and the security mechanism name as coverage information and saving them with the second node to obtain a security mechanism coverage node list.

[0058] The security mechanism file will contain the security mechanism name, so we can determine the security mechanism name covered on each second node through the security mechanism file.

[0059] The alarm information triggered by the node covered by the security mechanism can be determined based on the log information in the security mechanism file. The alarm information includes the alarm name and the alarm type.

[0060] The node name of the second node, the name of the covered security mechanism, and the triggered alarm information are associated one by one, and then mapped and saved, so that a list of nodes covered by the security mechanism can be generated.

[0061] It should be noted that, while generating a list of nodes covered by a security mechanism, the present application will also generate a list of nodes not covered by a security mechanism. The nodes not covered by a security mechanism are the nodes in the first node except the second node.

[0062] As an optional embodiment, a normal distribution model matching the soft failure rate is constructed to determine the optimal injection time of transient failures, and the optimal injection time is used to update the fault list, including: obtaining a candidate time interval to be tested, wherein the candidate time interval includes multiple test time intervals; constructing a normal distribution model corresponding to the soft failure rate, and using the normal distribution model to respectively determine the optimal injection time in each test time interval; using the optimal injection time to replace the failure time of the transient failure in the fault list to update the fault list.

[0063] Since a transient fault is a temporary fault with randomness, in order to make the injection time and duration of the transient fault more valuable for simulation, the present application proposes a method for determining the injection time of the transient fault using a normal distribution model.

[0064] The present application proposes to first determine the candidate time interval to be tested, and the candidate time interval includes multiple test time intervals. Considering the requirements of functional testing and the characteristics of the circuit, for the functional test vectors used in safety verification (fault simulation), there will be different test time intervals to test different regional circuits, so the present application directly finds the best injection time in each test interval.

[0065] The present application introduces a soft fault rate, which is the ratio of the number of mismatches to the total number of comparisons when the encryption (decryption) result of a register is compared with a golden reference value after a fault injection attack occurs.

[0066] The JESD89A standard is a test standard for semiconductor device reliability developed by JEDEC (Joint Electron Device Engineering Council). The solution of this application is based on this standard.

[0067] Specifically, calculating the soft failure rate includes: using the method and formula provided by the JESD89A standard, the soft failure rate can be calculated. According to the operating conditions of the equipment (such as operating temperature, power supply voltage, etc.) and environmental characteristics (such as radiation level, particle flow, etc.), the soft failure rate can be calculated by parameterizing. The detailed calculation method can be obtained by querying relevant information and will not be repeated in this application.

[0068] After the normal distribution model is established through the soft fault rate, random noise can be introduced and then transient fault injection can be simulated to determine the optimal injection time.

[0069] The previously generated fault list already includes the injection time of the transient fault, so after obtaining the optimal injection time, the optimal injection time is used to replace the fault time of the transient fault in the fault list to complete the update of the fault list.

[0070] Using the soft failure rate to construct a normal distribution model and further determine the optimal injection point of transient faults is also one of the highlights of this application, which will be described in detail below.

[0071] As an optional embodiment, a normal distribution model corresponding to the soft failure rate is constructed, and the normal distribution model is used to determine the optimal injection time in each test time interval, including: obtaining a confidence interval and normal distribution parameters matching the soft failure rate; establishing a normal distribution model based on the normal distribution parameters; sampling a random number as an expected value in each test time interval according to the normal distribution model; adding random noise to the expected value to obtain candidate injection times for transient faults; and verifying the candidate injection times within the confidence interval to obtain the optimal injection time.

[0072] For example, the normal distribution parameters are determined according to the soft failure rate and the reference values ​​provided by the JESD89A standard. The specific steps include: selecting appropriate normal distribution parameters according to the confidence interval of the soft failure rate and the characteristics of the statistical distribution.

[0073] Normal distribution parameters include mean (μ) and standard deviation (σ). If the JESD89A standard provides standard default values ​​or the manufacturer provides standard deviation values, these values ​​can be used directly. Otherwise, they need to be calculated based on actual test data. The mean (μ) is usually taken as the point estimate of the soft failure rate, that is, the average of the soft failure rates of all test samples. The standard deviation (σ) reflects the degree of dispersion of the soft failure rate data, which can be obtained by calculating the standard deviation of the soft failure rate data.

[0074] Confidence intervals are obtained based on a user-specified confidence level.

[0075] It should be noted that in actual operation, parameters can be adjusted to suit actual conditions based on the working conditions and environmental characteristics of the equipment.

[0076] Normally distributed random numbers refer to random variables that conform to the normal distribution, also called normally distributed random variables.

[0077] After obtaining the normal distribution parameters, a normal distribution model can be established based on the normal distribution parameters. Since adding random noise can simulate the randomness in the real environment when generating normal distribution random numbers, random noise is introduced after the normal distribution model is established, specifically including: selecting a suitable random noise model, such as Gaussian noise or uniform noise; and determining the amplitude and distribution of the noise according to the characteristics of the random noise model.

[0078] The confidence interval is combined with the fluctuations caused by noise to obtain multiple test intervals. In each test time interval, the injection of transient faults is simulated according to the established normal distribution model and the introduced random noise. The specific steps include: for each test time interval, random numbers are sampled from the normal distribution to obtain the expected value of the candidate injection time of the transient fault.

[0079] After obtaining the candidate injection time, use the simulation tool to simulate the transient fault injection time window, observe the distribution of the generated transient faults, compare them with the expected soft failure rate, and verify the accuracy of the simulation results.

[0080] The present application adopts a data preparation method for fault simulation, including: using a preset mode to generate faults on a target circuit to obtain a fault list, wherein the fault modes in the fault list include transient faults and permanent faults, and the fault list includes the fault time of each fault; identifying whether each fault in the fault list covers the safety mechanism, and generating a safety mechanism coverage node list according to the identification result; obtaining a soft fault rate, and constructing a normal distribution model matching the soft fault rate to determine the optimal injection time of the transient fault, and using the optimal injection time to update the fault list; determining the safety mechanism coverage node list and the fault list as target data, wherein the target data is used for fault simulation. The fault list and the safety mechanism coverage node list are generated by performing fault generation and safety mechanism analysis on permanent faults and transient faults, and the injection time of transient faults is re-determined separately by a normal distribution model to distinguish the fault injection time of different fault modes, and obtain target data that can be used for fault simulation, solving the problem that the faults of different fault modes cannot be flexibly set accordingly during fault simulation.

[0081] According to another aspect of the embodiment of the present application, the present application provides a data preparation device for fault simulation, such as Figure 2 As shown, including:

[0082] A fault generation module 202 is used to generate faults on a target circuit using a preset mode to obtain a fault list, wherein the fault modes in the fault list include transient faults and permanent faults, and the fault list includes the fault time of each fault;

[0083] A list generation module 204 is used to identify whether each fault in the fault list covers the safety mechanism, and generate a safety mechanism coverage node list according to the identification result;

[0084] A list updating module 206 is used to obtain a soft failure rate, and construct a normal distribution model matching the soft failure rate to determine an optimal injection time of a transient failure, and update a fault list using the optimal injection time;

[0085] The data processing module 208 is used to determine the safety mechanism coverage node list and the fault list as target data, wherein the target data is used for performing fault simulation.

[0086] It should be noted that the fault generation module 202 in this embodiment can be used to execute step 101 in the embodiment of the present application, the list generation module 204 in this embodiment can be used to execute step 103 in the embodiment of the present application, the list update module 206 in this embodiment can be used to execute step 105 in the embodiment of the present application, and the data processing module 208 in this embodiment can be used to execute step 107 in the embodiment of the present application.

[0087] Optionally, the fault generation module 202 is also used to count the first port corresponding to the unit level of the target circuit when the preset mode is the first mode, wherein the first port includes an input port, an output port and a bidirectional port; determine the fault type and the fault mode, and generate a fault corresponding to the fault type and the fault mode on the first port; record the fault type, fault mode, fault location and fault time of the fault, and generate a fault list.

[0088] Optionally, the fault generation module 202 is also used to count the second port corresponding to the unit level of the target circuit when the preset mode is the second mode, wherein the second port includes an output port; determine the fault type and fault mode, and generate a fault corresponding to the fault type and fault mode on the second port; record the fault type, fault mode, fault location and fault time of the fault, and generate a fault list.

[0089] Optionally, the list generating module 204 includes:

[0090] A division submodule, used to divide the target circuit into levels to obtain a hierarchical structure corresponding to the target circuit, wherein each level includes at least one functional module;

[0091] The first identification submodule is used to identify the input port and output port of each functional module and the propagation path of the signal through the input port and output port;

[0092] A second identification submodule is used to identify a first node on the propagation path, wherein the first node includes an intermediate node and a key node;

[0093] A determination submodule is used to obtain a security mechanism file and determine a second node covered by the security mechanism in the first node according to the security mechanism file;

[0094] The generation submodule is used to integrate the coverage information of each second node and generate a security mechanism coverage node list.

[0095] Optionally, the generation submodule is also used to determine the security mechanism name covering each second node according to the security mechanism file, and determine the alarm information triggered by the second node; the alarm information and the security mechanism name are mapped and saved as coverage information with the second node to obtain a security mechanism coverage node list.

[0096] Optionally, the list updating module 206 includes:

[0097] An acquisition submodule, used to acquire a candidate time interval to be tested, wherein the candidate time interval includes a plurality of test time intervals;

[0098] A construction submodule is used to construct a normal distribution model corresponding to the soft failure rate, and use the normal distribution model to determine the optimal injection time in each test time interval;

[0099] The updating submodule is used to replace the fault time of the transient fault in the fault list with the optimal injection time to update the fault list.

[0100] Optionally, the construction submodule is also used to obtain a confidence interval and normal distribution parameters that match the soft failure rate; establish a normal distribution model based on the normal distribution parameters; sample a random number as an expected value in each test time interval based on the normal distribution model; add random noise to the expected value to obtain a candidate injection time for a transient fault; and verify the candidate injection time within the confidence interval to obtain an optimal injection time.

[0101] It should be noted here that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments.

[0102] According to another aspect of the embodiments of the present application, the present application provides an electronic device, such as Figure 3 As shown, it includes a memory 301, a processor 303, a communication interface 305 and a communication bus 307. The memory 301 stores a computer program that can be run on the processor 303. The memory 301 and the processor 303 communicate through the communication interface 305 and the communication bus 307. When the processor 303 executes the computer program, the steps of the above method are implemented.

[0103] The memory and processor in the above electronic device communicate via a communication bus and a communication interface. The communication bus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus may be divided into an address bus, a data bus, a control bus, etc.

[0104] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0105] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0106] According to another aspect of the embodiments of the present application, a computer-readable medium having a non-volatile program code executable by a processor is provided.

[0107] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0108] When the embodiments of the present application are specifically implemented, reference may be made to the above-mentioned embodiments, which have corresponding technical effects.

[0109] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.

[0110] For software implementation, the technology described herein can be implemented by a unit that performs the functions described herein. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0111] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0112] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0113] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0114] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0115] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0116] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk. It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, article or device. Without more constraints, an element defined by the phrase "comprising a..." does not exclude the existence of other identical elements in the process, method, article or apparatus comprising the element.

[0117] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A data preparation method for fault simulation, It is characterized in that include: Generate faults on the target circuit using a preset mode to obtain a fault list, wherein the fault modes in the fault list include transient faults and permanent faults, and the fault list includes the fault time of each fault; Identify whether each fault in the fault list covers a safety mechanism, and generate a safety mechanism coverage node list according to the identification result; Acquire a soft failure rate, and construct a normal distribution model matching the soft failure rate to determine an optimal injection time of the transient fault, and update the fault list using the optimal injection time; The safety mechanism coverage node list and the fault list are determined as target data, wherein the target data is used for performing fault simulation.

2. The method according to claim 1, It is characterized in that The method of generating faults on the target circuit using a preset mode to obtain a fault list includes: When the preset mode is the first mode, counting first ports corresponding to the unit level of the target circuit, wherein the first ports include input ports, output ports, and bidirectional ports; Determine a fault type and the fault mode, and generate a fault corresponding to the fault type and the fault mode on the first port; The fault type, the fault mode, the fault location and the fault time of the fault are recorded to generate the fault list.

3. The method according to claim 1, It is characterized in that The method of generating faults on the target circuit using a preset mode to obtain a fault list includes: When the preset mode is the second mode, counting second ports corresponding to the unit level of the target circuit, wherein the second ports include output ports; Determine a fault type and the fault mode, and generate a fault corresponding to the fault type and the fault mode on the second port; The fault type, the fault mode, the fault location and the fault time of the fault are recorded to generate the fault list.

4. The method according to claim 1, It is characterized in that The step of identifying whether each fault in the fault list covers a safety mechanism and generating a safety mechanism coverage node list according to the identification result includes: Dividing the target circuit into levels to obtain a hierarchical structure corresponding to the target circuit, wherein each level includes at least one functional module; Identify the input port and the output port of each of the functional modules, and determine the propagation path of the signal through the input port and the output port; Identifying a first node on the propagation path, wherein the first node includes an intermediate node and a key node; Obtain a security mechanism file, and determine a second node in the first node that is covered by the security mechanism according to the security mechanism file; The coverage information of each of the second nodes is integrated to generate a list of nodes covered by the security mechanism.

5. The method according to claim 4, It is characterized in that The integrating the coverage information of each second node to generate the security mechanism coverage node list includes: Determine, according to the security mechanism file, a name of a security mechanism covering each of the second nodes, and determine alarm information triggered by the second node; The alarm information and the security mechanism name are mapped and saved with the second node as the coverage information to obtain the security mechanism coverage node list.

6. The method according to claim 1, It is characterized in that The constructing a normal distribution model matching the soft fault rate to determine the optimal injection time of the transient fault, and updating the fault list using the optimal injection time, comprises: Acquire a candidate time interval to be tested, wherein the candidate time interval includes a plurality of test time intervals; Constructing the normal distribution model corresponding to the soft failure rate, and using the normal distribution model to respectively determine the optimal injection time in each of the test time intervals; The fault list is updated by replacing the fault time of the transient fault in the fault list with the optimal injection time.

7. The method according to claim 6, It is characterized in that The constructing the normal distribution model corresponding to the soft failure rate, and using the normal distribution model to respectively determine the optimal injection time in each of the test time intervals, includes: Obtaining a confidence interval and normal distribution parameters matching the soft failure rate; Establishing the normal distribution model according to the normal distribution parameters; Sampling a random number as an expected value in each test time interval according to the normal distribution model; Adding random noise to the expected value to obtain a candidate injection time of the transient fault; The candidate injection time is verified within the confidence interval to obtain the optimal injection time.

8. A data preparation device for fault simulation, It is characterized in that include: A fault generation module, used to generate faults on a target circuit using a preset mode to obtain a fault list, wherein the fault modes in the fault list include transient faults and permanent faults, and the fault list includes the fault time of each fault; A list generation module, used to identify whether each fault in the fault list covers the safety mechanism, and generate a safety mechanism coverage node list according to the identification result; A list updating module, used for acquiring a soft failure rate, constructing a normal distribution model matching the soft failure rate to determine an optimal injection time of the transient failure, and updating the fault list using the optimal injection time; The data processing module is used to determine the safety mechanism coverage node list and the fault list as target data, wherein the target data is used for fault simulation.

9. An electronic device comprising a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, and the memory and the processor communicate through the communication bus and the communication interface. It is characterized in that When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer readable medium having a non-volatile program code executable by a processor, It is characterized in that The program code enables the processor to execute the method according to any one of claims 1 to 7.

Citation Information

Cited By

  • Fault signal generation method and device, equipment, medium and program product

    CN119892612A