Fault diagnosis mechanism insertion method and device, electronic equipment and readable medium
By analyzing the logical cone file, failure rate contribution file and endpoint transfer file, determining the fault diagnosis mechanism type and insertion point, the problem of not being able to flexibly identify key areas and endpoints in the existing technology is solved, and a more efficient fault diagnosis mechanism insertion is achieved. Improves system security and reduces failure rates.
Patent Information
- Application Number
- CN202410839151.X
- 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
The prior art has limitations in determining the type of fault diagnosis mechanism and insertion location, and cannot flexibly identify key areas and endpoints in the system, resulting in the inability to determine the optimal fault diagnosis mechanism and insertion location.
By obtaining the logic cone file, failure rate contribution file and endpoint transfer file, analyzing the endpoint distribution, connection status and transmission path of the logic cone, judging the type of the fault diagnosis mechanism (instance level or register level) and determining the insertion point, and then inserting the target fault, and then inserting the target fault Diagnostic mechanism.
It realizes a more flexible and accurate judgment of fault diagnosis mechanism types and insertion locations, improves system security, reduces fault rates, and does not affect overall performance.
Smart Images

Figure CN118897746A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of electronic information science and technology, and in particular to a method, device, electronic device and readable medium for inserting a fault diagnosis mechanism. Background Art
[0002] When designing a system, it is necessary to evaluate and control security, including identifying, evaluating and managing potential risks in the system, and then inserting appropriate fault diagnosis mechanisms to reduce the impact of security threats on the system, so as to ensure that the system can meet security requirements during operation. This requires security analysis of system components, covering the evaluation of logical structure, connection paths, and transmission between elements within the logic cone.
[0003] However, the existing technology has some limitations in determining the type and insertion location of the fault diagnosis mechanism. When faced with multiple data files obtained from different security analyses, it is impossible to comprehensively identify the key areas and endpoints in the system based on the files, resulting in the inability to flexibly determine the optimal fault diagnosis mechanism type and insertion location.
[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention
[0005] The present application provides a method, device, electronic device and readable medium for inserting a fault diagnosis mechanism to solve the above-mentioned technical problem of "inability to flexibly determine the optimal fault diagnosis mechanism type and insertion position".
[0006] According to one aspect of an embodiment of the present application, the present application provides a method for inserting a fault diagnosis mechanism, including: obtaining a logic cone file, a fault rate contribution file, and an endpoint transmission file obtained in the process of executing a safety project, wherein the logic cone file includes endpoint distribution data and endpoint connection data of the logic cone, the fault rate contribution file includes the fault rate contribution value of each endpoint to the overall failure rate value of the system, and the endpoint transmission file includes the transmission path between each endpoint; determining the mechanism type of the fault diagnosis mechanism according to the logic cone file and the fault rate contribution file, and determining the insertion point of the fault diagnosis mechanism according to the endpoint transmission file, wherein the mechanism type includes instance level and register level; obtaining a target fault diagnosis mechanism corresponding to the mechanism type, and inserting the target fault diagnosis mechanism at the insertion point.
[0007] Optionally, the mechanism type of the fault diagnosis mechanism is determined according to the logic cone file and the fault rate contribution file, including: extracting the endpoint distribution data and the endpoint connection data of the logic cone from the logic cone file, and determining the logic cone range; judging whether the logic cone meets the first preset condition according to the endpoint distribution data, the endpoint connection data and the logic cone range; if the logic cone meets the first preset condition, then determining that the mechanism type of the fault diagnosis mechanism is register level, if the logic cone does not meet the first preset condition, then determining the mechanism type of the fault diagnosis mechanism according to the fault rate contribution file.
[0008] Optionally, judging whether the logic cone satisfies a first preset condition is performed based on endpoint distribution data, endpoint connection data and the logic cone range, including: determining whether the endpoints are evenly distributed based on the endpoint distribution data, and determining whether the endpoints are evenly connected based on the endpoint connection data, and determining whether the logic cone range is less than or equal to a preset range; if the endpoints are unevenly distributed and / or the endpoints are unevenly connected and / or the logic cone range is greater than the preset range, then it is determined that the logic cone satisfies the first preset condition.
[0009] Optionally, the mechanism type of the fault diagnosis mechanism is determined according to the fault rate contribution file, including: extracting the fault rate contribution value of each endpoint from the fault rate contribution file; determining whether the contribution distribution of each endpoint is balanced according to the fault rate contribution value; if the contribution distribution of each endpoint is balanced, determining that the mechanism type of the fault diagnosis mechanism is instance level.
[0010] Optionally, the method further includes: if the contribution distribution of each endpoint is uneven, determining whether each endpoint is within the range of the logic cone; if each endpoint is within the range of the logic cone, determining that the mechanism type of the fault diagnosis mechanism is register level.
[0011] Optionally, the insertion point of the fault diagnosis mechanism is determined according to the endpoint transfer file, including: when the mechanism type of the target fault diagnosis mechanism is instance level, obtaining the first transmission path of each endpoint from the endpoint transfer file, and determining the insertion point of the fault diagnosis mechanism according to the first transmission path; when the mechanism type of the target fault diagnosis mechanism is register level, obtaining the second transmission path of the target endpoint from the endpoint transfer file, and determining the insertion point of the fault diagnosis mechanism according to the second transmission path, wherein the target endpoint is an endpoint among each endpoint that is pre-defined as an important endpoint.
[0012] Optionally, after the target fault diagnosis mechanism is inserted at the insertion point, the method further comprises: performing safety verification on the target system into which the target fault diagnosis mechanism is inserted, so as to determine whether the target system has a safety function corresponding to the target fault diagnosis mechanism.
[0013] According to another aspect of an embodiment of the present application, the present application provides an insertion device for a fault diagnosis mechanism, including: an acquisition module, used to acquire a logic cone file, a fault rate contribution file and an endpoint transmission file obtained in the process of executing a safety project, wherein the logic cone file includes endpoint distribution data and endpoint connection data of the logic cone, the fault rate contribution file includes the fault rate contribution value of each endpoint to the overall failure rate value of the system, and the endpoint transmission file includes the transmission path between each endpoint; a determination module, used to determine the mechanism type of the fault diagnosis mechanism according to the logic cone file and the fault rate contribution file, and to determine the insertion point of the fault diagnosis mechanism according to the endpoint transmission file, wherein the mechanism type includes instance level and register level; an insertion module, used to acquire a target fault diagnosis mechanism corresponding to the mechanism type, and insert the target fault diagnosis mechanism at the insertion point.
[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 method for inserting a fault diagnosis mechanism, including: obtaining a logic cone file, a fault rate contribution file and an endpoint transmission file obtained in the process of executing a safety project, wherein the logic cone file includes the endpoint distribution data and the endpoint connection data of the logic cone, the fault rate contribution file includes the fault rate contribution value of each endpoint to the overall fault rate value of the system, and the endpoint transmission file includes the transmission path between each endpoint; determining the mechanism type of the fault diagnosis mechanism according to the logic cone file and the fault rate contribution file, and determining the insertion point of the fault diagnosis mechanism according to the endpoint transmission file, wherein the mechanism type includes the instance level and the register level; obtaining the target fault diagnosis mechanism corresponding to the mechanism type, and inserting the target fault diagnosis mechanism at the insertion point. The fault rate contribution, endpoint distribution and data transmission of each endpoint of the logic cone are analyzed through the logic cone file, the fault rate contribution file and the endpoint transmission file to determine the fault diagnosis mechanism type and the best insertion point that match the analysis result, and complete the insertion of the fault diagnosis mechanism. The problem of not being able to flexibly determine the best fault diagnosis mechanism type and insertion position is solved. 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 method for inserting a fault diagnosis mechanism according to an embodiment of the present application;
[0021] Figure 2 A block diagram of an optional insertion device of a fault diagnosis mechanism 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] When designing a system, it is necessary to evaluate and control security, including identifying, evaluating and managing potential risks in the system, and then inserting appropriate fault diagnosis mechanisms to reduce the impact of security threats on the system, so as to ensure that the system can meet security requirements during operation. This requires security analysis of system components, covering the evaluation of logical structure, connection paths, and transmission between elements within the logic cone.
[0026] However, the existing technology has some limitations in determining the type and insertion location of the fault diagnosis mechanism. When faced with multiple data obtained from different security analyses, it is impossible to fully identify the key areas and endpoints in the system, resulting in the inability to flexibly determine the optimal type and insertion location of the fault diagnosis mechanism.
[0027] In addition, existing technologies may also face the complexity of fault diagnosis mechanism selection and insertion location determination in practical applications. Because in actual systems, safety requirements may show different characteristics in different components or layers, it is necessary to flexibly select and insert fault diagnosis mechanisms according to different situations to maximize the overall safety of the system. Therefore, a more effective method is needed to accurately judge the type and insertion location of the fault diagnosis mechanism based on existing data.
[0028] In order to solve the problem mentioned in the background technology, according to one aspect of the embodiment of the present application, a method for inserting a fault diagnosis mechanism is provided, such as Figure 1 As shown, including:
[0029] Step 101, obtaining a logic cone file, a failure rate contribution file, and an endpoint transmission file obtained in the process of executing the safety engineering, wherein the logic cone file includes endpoint distribution data and endpoint connection data of the logic cone, the failure rate contribution file includes the failure rate contribution value of each endpoint to the overall failure rate value of the system, and the endpoint transmission file includes the transmission path between each endpoint;
[0030] Step 103, determining a mechanism type of the fault diagnosis mechanism according to the logic cone file and the fault rate contribution file, and determining an insertion point of the fault diagnosis mechanism according to the endpoint transfer file, wherein the mechanism type includes an instance level and a register level;
[0031] Step 105 , obtaining a target fault diagnosis mechanism corresponding to the mechanism type, and inserting the target fault diagnosis mechanism at the insertion point.
[0032] ISO26262 is a functional safety standard for automotive electronic systems. Within this standard framework, the system is analyzed for safety and a fault diagnosis mechanism (also known as a safety mechanism) is inserted when necessary to ensure the reliability and safety of the system under various conditions. This application analyzes the data provided by the safety analysis file to obtain the most suitable fault diagnosis mechanism type and its insertion position to meet the needs of system safety.
[0033] In the process of executing safety engineering, different safety analysis files will be obtained at different stages, including logic cone files, failure rate contribution files and endpoint transmission files. These files play a key role in determining the type of fault diagnosis mechanism and the insertion point. Therefore, it is necessary to analyze the logic cone files, failure rate contribution files and endpoint transmission files to obtain the key data of the fault diagnosis mechanism type and the insertion point.
[0034] Logic cone files describe the structure of the logic cones in the system, the distribution of endpoints, and the connection relationship between logic cones. Logic cone files are usually generated by design tools, and they are based on the logical structure and layout information of the design. Logic cone files provide a view of the system hierarchy and help analyze the logical topology of the system.
[0035] The failure rate contribution file is generated based on the design and characteristics of the system. Usually, the file contains the contribution of each logic unit (such as registers, logic blocks, etc.) to the overall FIT (Failures In Time) value of the system, specifically including the name of the endpoint and their contribution percentage to the design FIT. FIT is calculated based on EP (Endpoint), where each EP-FIT consists of the transistors in the EP and the transistors in the cone.
[0036] Endpoint transfer file, which describes the transfer from each start point to the next endpoint, including the name of the start point, the connected endpoints, and the number of fanouts transferred (the number of fanouts from each endpoint to the next endpoint).
[0037] Preferably, the mechanism type of the fault diagnosis mechanism is determined according to the logic cone file and the fault rate contribution file, and then the insertion point of the fault diagnosis mechanism is determined according to the endpoint transmission file, and then the target fault diagnosis mechanism matching the mechanism type is obtained, and the target fault diagnosis mechanism is inserted into the determined insertion point to solve the problem of uneven contribution and endpoint distribution.
[0038] The mechanism types in this application include instance level and register level. The instance level fault diagnosis mechanism is a security measure implemented at a higher level of the system or application. The fault diagnosis mechanism at this level usually involves the behavior and interaction of the entire system or specific components. The register level fault diagnosis mechanism is a security measure implemented at the register level of the processor. The fault diagnosis mechanism at this level is usually very close to the hardware bottom layer and directly affects the operation and instruction execution of the processor.
[0039] Specifically, the differences in the selection of instance-level fault diagnosis mechanism and register-level fault diagnosis mechanism include: when the endpoint distribution is balanced, symmetric and balanced, it is suitable for the application of the fault diagnosis mechanism in the entire instance. When the fault diagnosis mechanism in the design needs to be symmetrically applied to the entire instance and will not cause too much impact on the balance of the design, the instance-level fault diagnosis mechanism is a suitable choice; when the endpoints are unbalanced, it is suitable for the situation where the fault diagnosis mechanism needs to be customized and asymmetric at the register level. When the fault diagnosis mechanism in the design needs to be deployed in a localized and personalized manner, the register-level fault diagnosis mechanism is a better choice.
[0040] When endpoint contributions are relatively balanced, endpoint contributions are relatively balanced in the instance, and the scope of the fault diagnosis mechanism is limited to the entire instance, the instance-level fault diagnosis mechanism is usually more suitable; when endpoint contributions are uneven: when the EP (endpoint) contribution is uneven at the specific register level and the fault diagnosis mechanism needs to be applied more precisely to a specific part, the register-level fault diagnosis mechanism is usually more suitable.
[0041] The embodiment provided in the present application comprehensively considers the distribution of fault rate contributions, the importance of elements inside the logic cone, and the usage path of the endpoints to determine the optimal fault diagnosis mechanism type and insertion location.
[0042] Next, how to determine the mechanism type of the fault diagnosis mechanism based on the logic cone file and the fault rate contribution file is described in detail.
[0043] As an optional embodiment, the mechanism type of the fault diagnosis mechanism is determined according to the logic cone file and the fault rate contribution file, including: extracting the endpoint distribution data and the endpoint connection data of the logic cone from the logic cone file, and determining the logic cone range; judging whether the logic cone meets the first preset condition according to the endpoint distribution data, the endpoint connection data and the logic cone range; if the logic cone meets the first preset condition, then determining that the mechanism type of the fault diagnosis mechanism is register level, if the logic cone does not meet the first preset condition, then determining the mechanism type of the fault diagnosis mechanism according to the fault rate contribution file.
[0044] The format of the logic cone file includes: ① endpoint name + endpoint FIT contribution value to the entire circuit; ② logic cone name + endpoint of the logic cone + endpoint FIT contribution value of the EP as a whole; ③ logic cone name + overall FIT contribution value of the logic cone.
[0045] Specifically, the logic cone file is analyzed, including: determining the contribution and distribution of elements within the logic cone, and confirming the importance and impact of the logic cone in the entire design. This helps to locate local important endpoints and their connection paths.
[0046] The logic cone is a component in the system, usually referring to a level of the logic structure. The endpoints are the input and output ports in the logic cone. They play the role of a bridge connecting the logic cones or connecting the logic cones to the external environment. Endpoints can be registers, input / output interfaces, inputs or outputs of logic units, etc.
[0047] Specifically, the endpoint distribution data and endpoint connection data of the logic cone are extracted from the logic cone file, and the range of the logic cone is determined; whether the logic cone meets the first preset condition is judged according to the endpoint distribution data, the endpoint connection data and the range of the logic cone; if the logic cone meets the first preset condition, the mechanism type of the fault diagnosis mechanism is determined to be register level.
[0048] As an optional embodiment, judging whether the logical cone meets the first preset condition based on the endpoint distribution data, the endpoint connection data and the logical cone range includes: determining whether the endpoints are evenly distributed based on the endpoint distribution data, and determining whether the endpoints are evenly connected based on the endpoint connection data, and determining whether the logical cone range is less than or equal to the preset range; if the endpoints are unevenly distributed and / or the endpoints are unevenly connected and / or the logical cone range is greater than the preset range, then determining that the logical cone meets the first preset condition.
[0049] For example, the endpoint connection data can be used to determine the number of other endpoints or components to which each endpoint is connected, as well as the properties of these connections (such as signal type, data transmission rate, etc.), to comprehensively determine whether the connections are balanced.
[0050] For example, the steps of determining whether the endpoint distribution is uniform include: data collection: collecting the location data of all endpoints in the logic cone; determining the total area of the logic cone and the total number of endpoints; defining the distribution uniformity index: the uniformity index can be defined based on the spatial position, density or relative position of the endpoints to other components. For example, the number of endpoints in each small area can be calculated and compared to see whether these numbers are close to the average value; calculating the endpoint density: dividing the logic cone into several small areas (such as grids or fan-shaped areas), and calculating the number of endpoints in each area. By comparing the number of endpoints in each area, it is possible to evaluate whether the endpoint distribution is uniform; calculating statistical indicators: calculating the average endpoint density and standard deviation to quantify the uniformity of the endpoint distribution. If the standard deviation is small, it means that the endpoint distribution is more uniform; otherwise, there may be an uneven distribution.
[0051] For example, the step of determining the range of the logic cone includes:
[0052] Step 1, identify the starting point: determine the starting point of the logic cone, which is usually a key logic gate, transistor or other circuit component;
[0053] Step 2, trace the signal path: Starting from the starting point, trace the signal's transmission path, which involves looking at all signal lines starting from the starting point and determining the next component they connect to;
[0054] Step 3, analyze dependencies: determine whether each downstream component depends directly or indirectly on the signal from the starting point;
[0055] Step 4, determine the scope of influence: continue to trace the signal path until all components affected by the starting point are found, including components directly connected to the starting point and components indirectly affected through other paths;
[0056] Step 5, consider timing and performance: When analyzing the logic cone, you also need to consider the impact of timing and performance. For example, the delay of a logic gate may affect the performance of the entire path.
[0057] Step 6. Use design tools to determine the scope of the logic cone: Modern integrated circuit design tools generally provide powerful analysis functions to help determine the scope of the logic cone. These tools can automatically trace the signal path and display the affected components.
[0058] When determining the mechanism type of the fault diagnosis mechanism, it is necessary to determine whether the logic cone range is limited, because the logic cone range and the mechanism type also need to be adapted. If the logic cone range is less than or equal to the preset range, the logic cone range is limited. If the logic cone range is greater than the preset range, it means that the logic cone range is not limited. The preset range is set according to the actual situation, and this application does not limit this.
[0059] In the present application, satisfying the first preset condition indicates that the endpoints of the logic cone in the system are unevenly distributed or the FIT contributions of the endpoints are uneven. When the contributions of different endpoints in the system are uneven at a specific register level and the fault diagnosis mechanism needs to be more accurately applied to a specific part, the register-level fault diagnosis mechanism is usually more suitable. At this time, the fault diagnosis mechanism needs to be accurately deployed at the specific register level of the system to cope with the uneven contribution. In this case, the register-level fault diagnosis mechanism can better meet security requirements and ensure more precise control of the security of specific parts of the system.
[0060] There may also be a situation where the logic cone does not meet the first preset condition. If the distribution and connection of the endpoints inside the logic cone are relatively balanced and the range of the logic cone is limited, the mechanism type of the fault diagnosis mechanism will be determined based on the fault rate contribution file. The following will explain how to determine the mechanism type of the fault diagnosis mechanism based on the fault rate contribution file.
[0061] As an optional embodiment, the mechanism type of the fault diagnosis mechanism is determined according to the fault rate contribution file, including: extracting the fault rate contribution value of each endpoint from the fault rate contribution file; determining whether the contribution distribution of each endpoint is balanced according to the fault rate contribution value; if the contribution distribution of each endpoint is balanced, determining that the mechanism type of the fault diagnosis mechanism is instance level.
[0062] The format of the failure rate contribution file includes: endpoint name + endpoint FIT contribution value to the entire design.
[0063] Specifically, the fault rate contribution file needs to be analyzed, including: determining the FIT contribution distribution of each endpoint, being able to determine the imbalance and impact on the entire design. The purpose of analyzing the fault rate contribution file is to determine the key areas and important endpoints of FIT contribution in the system. By analyzing and viewing the proportion of FIT contribution of each element in the logic cone, you can understand its impact on the entire design, and you can also analyze the safety requirements of different elements in the fault rate contribution file.
[0064] For example, the FIT contribution values of all endpoints are counted and a distribution diagram (such as a bar graph, box plot, etc.) is drawn. Then, the shape and dispersion of the distribution diagram are observed to determine whether there is a significant contribution difference, so as to evaluate the balance of the FIT contribution of each endpoint.
[0065] When the endpoints are evenly distributed and the FIT contribution distribution is relatively balanced, the instance-level fault diagnosis mechanism can effectively cover the entire system. Therefore, determining the mechanism type of the fault diagnosis mechanism to be instance-level can improve the overall security of the system.
[0066] As an optional embodiment, the method further includes: if the contribution distribution of each endpoint is uneven, determining whether each endpoint is within the range of the logic cone; if each endpoint is within the range of the logic cone, determining that the mechanism type of the fault diagnosis mechanism is register level.
[0067] Specifically, when the contributions of different endpoints in the system are unbalanced at the level of specific registers, and the fault diagnosis mechanism needs to be more precisely applied to the specific part, the register-level fault diagnosis mechanism is usually more suitable. This means that the fault diagnosis mechanism needs to be precisely deployed at the level of specific registers in the system to cope with the unbalanced contribution situation.
[0068] In the case where the contribution of various endpoints is unevenly distributed, register-level fault diagnosis mechanisms can better meet safety requirements and ensure more precise control over the safety of specific parts of the system.
[0069] As an optional embodiment, the insertion point of the fault diagnosis mechanism is determined according to the endpoint transfer file, including: when the mechanism type of the target fault diagnosis mechanism is instance level, obtaining the first transmission path of each endpoint from the endpoint transfer file, and determining the insertion point of the fault diagnosis mechanism according to the first transmission path; when the mechanism type of the target fault diagnosis mechanism is register level, obtaining the second transmission path of the target endpoint from the endpoint transfer file, and determining the insertion point of the fault diagnosis mechanism according to the second transmission path, wherein the target endpoint is an endpoint pre-defined as an important endpoint among each endpoint.
[0070] The format of the endpoint transfer file includes: the name of the starting endpoint + the number of fanouts to be transferred (the number of fanouts from each endpoint to the next endpoint) + the name of the endpoint connected to the starting endpoint.
[0071] Specifically, by analyzing the endpoint transfer files and examining the transmission conditions and frequencies between elements within the logic cone, we gain in-depth understanding of the endpoint usage and transmission paths, which helps determine where to insert the fault diagnosis mechanism.
[0072] The selection of the injection point of the instance-level fault diagnosis mechanism is mainly based on the endpoint transmission file. When the connection path is simple and small, the injection position of the fault diagnosis mechanism is determined. In other words, it is suitable to insert the fault diagnosis mechanism in places where the connection path is relatively simple and small in number.
[0073] Inserting instance-level fault diagnosis mechanisms at specific locations inside the logic cone can improve the safety of the system.
[0074] For the selection of the injection point of the register-level fault diagnosis mechanism, the transmission path and connection of the local important endpoint (i.e., the target endpoint) are verified according to the endpoint transfer file, and the injection position of the register-level fault diagnosis mechanism is determined. By analyzing the transmission path and connection of the endpoint, it is determined in which registers or register groups the insertion of the fault diagnosis mechanism is most effective.
[0075] Inserting customized register-level fault diagnosis mechanisms at locally important endpoints can improve the safety of critical parts of the system.
[0076] This application can more accurately identify key areas and endpoints in the system, thereby achieving more precise fault diagnosis mechanism insertion, which not only ensures that the injection location selected in the design can effectively reduce the FIT value without affecting the overall performance, but also solves the problem of uneven FIT contribution and endpoint distribution.
[0077] As another optional embodiment, when making instance-level judgments, it is necessary to analyze the contribution of each logic cone through the logic cone file and evaluate the importance of each logic cone in the entire design; use the instance contribution in the fault rate contribution file to evaluate the instance-level FIT distribution: determine the requirements for the fault diagnosis mechanism at the instance level, including the degree of safety enhancement for the instance.
[0078] When adding a fault diagnosis mechanism decision, check the balance of instance contribution and endpoint. If the instance contribution is important and the endpoint is balanced on the instance, specify the duplication or triplication of the instance in the fault diagnosis mechanism file of SafetyScope to take advantage of different safety requirements. If the contribution of the endpoint is not balanced on the instance, it is necessary to add a register-level fault diagnosis mechanism.
[0079] As another optional embodiment, when making a judgment at the register level, it is necessary to understand the distribution of endpoints in each logic cone, especially the contribution of registers, and have a comprehensive understanding of the distribution of registers in different logic cones; evaluate the FIT distribution at the register level based on the contribution of endpoints in the fault rate contribution file, understand the FIT distribution at the register level, and determine the safety requirements at the register level.
[0080] When the contribution of the endpoint is unbalanced at the register level, the most suitable fault diagnosis mechanism type is selected according to the distribution of the endpoint at the register level. For example: If the endpoint is on the data path, you may choose to use Datapath Parity / CRC to achieve end-to-end protection. If the endpoint is part of the state machine: You may choose to use Protocol / Transition Check to protect the state machine.
[0081] It is necessary to select a fault diagnosis mechanism based on reliability requirements and SP usage, including: selecting an appropriate fault diagnosis mechanism based on reliability requirements and usage of the starting point. If the reliability requirement is high and the SP usage is high, End point + Cone Triplication may be selected; if high reliability is not required and the SP usage is high, End point + Cone Duplication may be selected; if high reliability is required and the SP usage is low, Endpoint ECC may be selected; if high reliability is not required and the SP usage is low, Endpoint Parity may be selected.
[0082] As an optional embodiment, after inserting the target fault diagnosis mechanism at the insertion point, the method further includes: performing safety verification on the target system into which the target fault diagnosis mechanism is inserted to determine whether the target system has a safety function corresponding to the target fault diagnosis mechanism.
[0083] The content of safety verification includes but is not limited to verifying that the target system has safety functions corresponding to the target fault diagnosis mechanism.
[0084] For example, after inserting the target fault diagnosis mechanism, new FIT data is collected, including recording any new faults or changes in fault rates. At the same time, data on SP usage after the fault diagnosis mechanism is implemented is collected.
[0085] For example, compare the FIT contribution values before and after adding the fault diagnosis mechanism to determine if there is a significant decrease, which indicates that the fault diagnosis mechanism may help reduce failures. Analyze which endpoints or components have the largest change in FIT contribution values, which can help determine whether the fault diagnosis mechanism has a greater impact on specific parts.
[0086] This application not only provides a method to solve the problems of uneven FIT contribution distribution and local important endpoints, but more importantly, establishes a new and intelligent fault diagnosis mechanism selection and insertion framework that can be applied to safety assessment and control requirements in various system designs.
[0087] For example, the present application also provides a method for injecting and verifying a fault diagnosis mechanism at a register level and / or an instance level, including:
[0088] Step 1, data preparation phase: obtain the logic cone file, failure rate contribution file, and endpoint transmission file.
[0089] Step 2, contribution analysis and connection path check:
[0090] (1) Check the logic cone file and the failure rate contribution file: If the logic cone file indicates that the distribution and connection of the endpoints inside the logic cone are relatively balanced and the range of the logic cone is limited, proceed to step 3;
[0091] (2) If the logic cone file shows that the endpoint contribution distribution is uneven or there are important endpoints inside the logic cone, execute step 4.
[0092] Step 3: Select the instance-level fault diagnosis mechanism:
[0093] (1) Contribute files based on failure rate:
[0094] a. If the failure rate contribution file shows that the FIT contribution distribution of the internal endpoints of the logic cone is relatively balanced, proceed to step 5;
[0095] b. If the failure rate contribution file shows that the endpoint contributions are uneven but within the entire logic cone, proceed to step 4.
[0096] (2) Determine the applicable situation:
[0097] a. If the instance-level fault diagnosis mechanism is applicable, go to step 7.
[0098] b. If the applicability of the instance-level fault diagnosis mechanism cannot be determined, return to the data preparation stage for re-evaluation.
[0099] Step 4: Register-level fault diagnosis mechanism selection:
[0100] (1) Analyze the failure rate contribution file:
[0101] If the failure rate contribution file shows that the endpoint is not balanced within the logic cone and is a locally important endpoint, proceed to step 6.
[0102] (2) Determine the applicable situation:
[0103] If the register-level fault diagnosis mechanism is applicable, go to step 8;
[0104] If the applicability of the register-level fault diagnosis mechanism cannot be determined, return to the data preparation stage for re-evaluation.
[0105] Step 5: Determine the location where the instance-level fault diagnosis mechanism is injected:
[0106] (1) Transfer files based on endpoints:
[0107] If the endpoint transfer file shows that the connection paths of the endpoints inside the logic cone are simple and few, the injection location of the instance-level fault diagnosis mechanism can be determined.
[0108] (2) Determine the applicable situation:
[0109] If the injection location of the instance-level fault diagnosis mechanism can be determined, proceed to step 7;
[0110] If the injection location cannot be determined, return to the instance-level fault diagnosis mechanism selection stage for re-analysis.
[0111] Step 6: Determine the injection location of the register-level fault diagnosis mechanism:
[0112] (1) Analyze endpoint transfer files: If the endpoint transfer files indicate that the transmission paths and connections of important local endpoints are complex, an accurate register-level fault diagnosis mechanism is required.
[0113] (2) Determine the applicable situation:
[0114] If the injection location of the register-level fault diagnosis mechanism can be determined, execute step 8;
[0115] If the injection location cannot be determined, return to the register-level fault diagnosis mechanism selection stage for re-analysis.
[0116] Step 7: Inject and verify the instance-level fault diagnosis mechanism:
[0117] Complete the injection of instance-level fault diagnosis mechanism for verification and testing.
[0118] Step 8: Register-level fault diagnosis mechanism injection and verification:
[0119] Complete the injection of register-level fault diagnosis mechanism for verification and testing.
[0120] Step 9, verify the effect of the fault diagnosis mechanism: Based on the addition of the fault diagnosis mechanism, re-analyze the FIT contribution and endpoint usage to verify the effect of adding the fault diagnosis mechanism.
[0121] This application also provides the difference between the instance-level fault diagnosis mechanism and the register-level fault diagnosis mechanism:
[0122] For situations with good symmetry and balance: Applicable to the application of fault diagnosis mechanism in the entire instance. When the fault diagnosis mechanism in the design needs to be applied symmetrically to the entire instance and will not cause too much impact on the balance of the design, the instance-level fault diagnosis mechanism is a suitable choice.
[0123] For situations where Endpoint contributions are relatively balanced: When EP contributions are relatively balanced in an instance and the scope of the fault diagnosis mechanism is limited to the entire instance, an instance-level fault diagnosis mechanism is usually more appropriate.
[0124] For the case of endpoint imbalance: It is suitable for the situation that the fault diagnosis mechanism needs to be customized and asymmetrically applied at the register level. When the fault diagnosis mechanism in the design needs to be deployed in a localized and personalized manner, the register-level fault diagnosis mechanism is a better choice.
[0125] For the case of uneven endpoint contribution: When the endpoint contribution is uneven at the level of a specific register and the fault diagnosis mechanism needs to be applied more precisely to the specific part, the register-level fault diagnosis mechanism is usually more suitable.
[0126] Regarding adding a logical path to the instance-level fault diagnosis mechanism, the following instructions are added:
[0127] (1) Selection conditions: Condition 1: The distribution and connection of the endpoints inside the logic cone are relatively balanced; Condition 2: The failure rate contribution file shows that the FIT contribution distribution of the endpoints inside the logic cone is relatively balanced.
[0128] (2) Add logic to the fault diagnosis mechanism:
[0129] 1. Determine applicability: If conditions 1 and 2 are met, you can choose the instance-level fault diagnosis mechanism.
[0130] 2. Injection location determination: Based on the endpoint transfer file, verify that the connection path is simple and small, and determine the injection location of the fault diagnosis mechanism.
[0131] 3. Adding fault diagnosis mechanism: Inject instance-level fault diagnosis mechanism into the logic cone that meets the conditions.
[0132] Regarding adding a logical path to the register-level fault diagnosis mechanism, add the following instructions:
[0133] (1) Selection conditions: The failure rate contribution file shows that the endpoints are uneven within the logic cone and are locally important endpoints;
[0134] (2) Add logic to the fault diagnosis mechanism:
[0135] 1. Determine applicability: If the fault rate contribution file shows that the endpoints are uneven and are locally important endpoints, it is appropriate to select a register-level fault diagnosis mechanism.
[0136] 2. Injection location judgment: According to the endpoint transfer file, verify the transmission path and connection status of the local important endpoints, and determine the injection location of the register-level fault diagnosis mechanism.
[0137] (3) Adding fault diagnosis mechanism: Injecting register-level fault diagnosis mechanism at locally important endpoints.
[0138] Optionally, instance-level judgment includes the following two aspects:
[0139] 1. Logic cone and instance contribution: Analyze the contribution of each logic cone through the logic cone file and evaluate the importance of each logic cone in the entire design.
[0140] The instance contribution in the failure rate contribution file is used to evaluate the instance-level FIT distribution and determine the requirements of the fault diagnosis mechanism at the instance level, including the degree of security enhancement for the instance.
[0141] 2. Add decision-making to the fault diagnosis mechanism:
[0142] Check the balance of instance contribution and endpoint: If instance contribution is important and endpoints are balanced on instances, specify instance duplication or triplication in the security-scoped fault diagnosis mechanism file to take advantage of different security requirements; if endpoint contribution is unbalanced on instances, add register-level fault diagnosis mechanisms.
[0143] Optionally, the register level judgment includes the following three aspects:
[0144] 1. Logical cone and endpoint contribution:
[0145] Understand the distribution of endpoints in each logic cone, especially the contribution of registers, to have a comprehensive understanding of the distribution of registers in different logic cones.
[0146] Evaluate the register-level FIT distribution based on the contribution of the endpoints in the fault rate contribution file, understand the register-level FIT distribution, and determine the register-level safety requirements.
[0147] 2. Determine the most appropriate register-level fault diagnosis mechanism:
[0148] When the contribution of the endpoints is unbalanced at the register level, the most suitable fault diagnosis mechanism type is selected according to the distribution of the endpoints at the register level.
[0149] For example, if the endpoint is on the data path, you may choose to use Datapath Parity (data path parity check) / CRC (Cyclic Redundancy Check) to achieve end-to-end protection.
[0150] If the Endpoint is part of a state machine, you may choose to use Protocol / Transition Check to protect the state machine.
[0151] 3. Select the fault diagnosis mechanism based on reliability requirements and starting point usage:
[0152] Select the appropriate fault diagnosis mechanism based on reliability requirements and usage of the starting point.
[0153] If the reliability requirement is high and the utilization rate of the starting point is high, Endpoint+Cone Triplication may be selected; if high reliability is not required and the utilization rate of the starting point is high, Endpoint+ConeDuplication may be selected; if the reliability requirement is high and the utilization rate of the starting point is low, EndpointECC (endpoint error correction code) is selected for situations where high reliability is not required and the utilization rate of the starting point is low; if high reliability is not required and the utilization rate of the starting point is low, Endpoint Parity is selected for situations where high reliability is not required and the utilization rate of the starting point is low.
[0154] In addition, this application also provides the selection of fault diagnosis mechanism and the determination of injection location:
[0155] 1. Endpoint contribution analysis:
[0156] Based on the contribution of each endpoint in the failure rate contribution file, determine the importance of each endpoint, its impact on the entire design, and the possible risk level.
[0157] 2. Injection location decision:
[0158] Combining the structure of the logic cone and the contribution of the elements, the appropriate fault diagnosis mechanism type and the specific injection location are determined.
[0159] Based on the needs and contribution of the elements inside a particular logic cone:
[0160] If the elements inside the logic cone contribute significantly and safety enhancement is required, appropriate fault diagnosis mechanisms are injected into the logic cone to reduce the FIT value.
[0161] If some element contributes little to the overall design, then there may be no need to inject special troubleshooting mechanisms there.
[0162] Determine the injection location of the fault diagnosis mechanism and ensure that the injection location selected in the design can effectively reduce the FIT value and does not affect the overall performance.
[0163] The present application adopts a method for inserting a fault diagnosis mechanism, including: obtaining a logic cone file, a fault rate contribution file and an endpoint transmission file obtained in the process of executing a safety project, wherein the logic cone file includes the endpoint distribution data and the endpoint connection data of the logic cone, the fault rate contribution file includes the fault rate contribution value of each endpoint to the overall fault rate value of the system, and the endpoint transmission file includes the transmission path between each endpoint; determining the mechanism type of the fault diagnosis mechanism according to the logic cone file and the fault rate contribution file, and determining the insertion point of the fault diagnosis mechanism according to the endpoint transmission file, wherein the mechanism type includes the instance level and the register level; obtaining the target fault diagnosis mechanism corresponding to the mechanism type, and inserting the target fault diagnosis mechanism at the insertion point. The fault rate contribution, endpoint distribution and data transmission of each endpoint of the logic cone are analyzed through the logic cone file, the fault rate contribution file and the endpoint transmission file to determine the fault diagnosis mechanism type and the best insertion point that match the analysis result, and complete the insertion of the fault diagnosis mechanism. The problem of not being able to flexibly determine the best fault diagnosis mechanism type and insertion position is solved.
[0164] According to another aspect of the embodiment of the present application, the present application provides an insertion device of a fault diagnosis mechanism, such as Figure 2 As shown, including:
[0165] The acquisition module 202 is used to acquire the logic cone file, the failure rate contribution file and the endpoint transmission file obtained in the process of executing the safety engineering, wherein the logic cone file includes the endpoint distribution data and the endpoint connection data of the logic cone, the failure rate contribution file includes the failure rate contribution value of each endpoint to the overall failure rate value of the system, and the endpoint transmission file includes the transmission path between each endpoint;
[0166] A determination module 204 is used to determine a mechanism type of the fault diagnosis mechanism according to the logic cone file and the fault rate contribution file, and to determine an insertion point of the fault diagnosis mechanism according to the endpoint transfer file, wherein the mechanism type includes an instance level and a register level;
[0167] The insertion module 206 is used to obtain a target fault diagnosis mechanism corresponding to the mechanism type and insert the target fault diagnosis mechanism at an insertion point.
[0168] It should be noted that the acquisition module 202 in this embodiment can be used to execute step 101 in the embodiment of the present application, the determination module 204 in this embodiment can be used to execute step 103 in the embodiment of the present application, and the insertion module 206 in this embodiment can be used to execute step 105 in the embodiment of the present application.
[0169] Optionally, the determination module 204 includes:
[0170] An extraction unit, used for extracting endpoint distribution data and endpoint connection data of a logic cone from a logic cone file, and determining a range of the logic cone;
[0171] A judging unit, configured to judge whether the logic cone meets a first preset condition according to the endpoint distribution data, the endpoint connection data and the logic cone range;
[0172] The determination unit is used to determine that the mechanism type of the fault diagnosis mechanism is register level if the logic cone meets the first preset condition, and to determine the mechanism type of the fault diagnosis mechanism according to the fault rate contribution file if the logic cone does not meet the first preset condition.
[0173] Optionally, the judgment unit is also used to determine whether the endpoints are evenly distributed based on the endpoint distribution data, and determine whether the endpoints are evenly connected based on the endpoint connection data, and determine whether the logic cone range is less than or equal to a preset range; if the endpoints are unevenly distributed and / or the endpoints are unevenly connected and / or the logic cone range is greater than the preset range, then it is determined that the logic cone meets the first preset condition.
[0174] Optionally, the determination unit is also used to extract the failure rate contribution value of each endpoint from the failure rate contribution file; determine whether the contribution distribution of each endpoint is balanced according to the failure rate contribution value; if the contribution distribution of each endpoint is balanced, determine that the mechanism type of the fault diagnosis mechanism is instance level.
[0175] Optionally, the determination unit is further configured to determine whether each endpoint is within the range of a logic cone if the contribution distribution of each endpoint is uneven; if each endpoint is within the range of a logic cone, determine that the mechanism type of the fault diagnosis mechanism is register level.
[0176] Optionally, the determination module 204 is also used to obtain the first transmission path of each endpoint from the endpoint transfer file when the mechanism type of the target fault diagnosis mechanism is at the instance level, and determine the insertion point of the fault diagnosis mechanism based on the first transmission path; when the mechanism type of the target fault diagnosis mechanism is at the register level, obtain the second transmission path of the target endpoint from the endpoint transfer file, and determine the insertion point of the fault diagnosis mechanism based on the second transmission path, wherein the target endpoint is an endpoint among each endpoint that is pre-defined as an important endpoint.
[0177] Optionally, the device further comprises a verification module for performing safety verification on a target system into which the target fault diagnosis mechanism is inserted after the target fault diagnosis mechanism is inserted at the insertion point, so as to determine whether the target system has a safety function corresponding to the target fault diagnosis mechanism.
[0178] 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.
[0179] 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.
[0180] 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.
[0181] 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.
[0182] 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.
[0183] 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.
[0184] 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.
[0185] When the embodiments of the present application are specifically implemented, reference may be made to the above-mentioned embodiments, which have corresponding technical effects.
[0186] 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.
[0187] 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.
[0188] 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.
[0189] 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.
[0190] 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.
[0191] 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.
[0192] 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.
[0193] 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.
[0194] 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 method for inserting a fault diagnosis mechanism, It is characterized in that include: Acquire a logic cone file, a failure rate contribution file, and an endpoint transmission file obtained in the process of executing the safety engineering, wherein the logic cone file includes endpoint distribution data and endpoint connection data of the logic cone, the failure rate contribution file includes the failure rate contribution value of each endpoint to the overall failure rate value of the system, and the endpoint transmission file includes the transmission path between each endpoint; Determining a mechanism type of a fault diagnosis mechanism according to the logic cone file and the fault rate contribution file, and determining an insertion point of the fault diagnosis mechanism according to the endpoint transfer file, wherein the mechanism type includes an instance level and a register level; A target fault diagnosis mechanism corresponding to the mechanism type is acquired, and the target fault diagnosis mechanism is inserted at the insertion point.
2. The method according to claim 1, It is characterized in that The determining the mechanism type of the fault diagnosis mechanism according to the logic cone file and the fault rate contribution file comprises: Extracting the endpoint distribution data and the endpoint connection data of the logic cone from the logic cone file, and determining the logic cone range; Determining whether the logic cone meets a first preset condition according to the endpoint distribution data, the endpoint connection data and the logic cone range; If the logic cone meets the first preset condition, the mechanism type of the fault diagnosis mechanism is determined to be the register level; if the logic cone does not meet the first preset condition, the mechanism type of the fault diagnosis mechanism is determined according to the fault rate contribution file.
3. The method according to claim 2, It is characterized in that The determining whether the logic cone meets a first preset condition according to the endpoint distribution data, the endpoint connection data and the logic cone range includes: Determine whether the endpoints are evenly distributed according to the endpoint distribution data, determine whether the endpoints are evenly connected according to the endpoint connection data, and determine whether the logic cone range is less than or equal to a preset range; If the endpoints are unevenly distributed and / or the endpoints are not evenly connected and / or the range of the logic cone is larger than the preset range, it is determined that the logic cone meets the first preset condition.
4. The method according to claim 2, It is characterized in that The determining the mechanism type of the fault diagnosis mechanism according to the fault rate contribution file includes: Extracting the failure rate contribution value of each endpoint from the failure rate contribution file; Determining whether the contribution distribution of each endpoint is balanced according to the failure rate contribution value; If the contribution distribution of the various endpoints is balanced, it is determined that the mechanism type of the fault diagnosis mechanism is the instance level.
5. The method according to claim 4, It is characterized in that The method further comprises: If the contribution distribution of each endpoint is uneven, determining whether each endpoint is within the range of the logic cone; If the various endpoints are within the range of the logic cone, it is determined that the mechanism type of the fault diagnosis mechanism is the register level.
6. The method according to claim 1, It is characterized in that The step of determining the insertion point of the fault diagnosis mechanism according to the endpoint transmission file comprises: In a case where the mechanism type of the target fault diagnosis mechanism is the instance level, obtaining a first transmission path of each endpoint from the endpoint transmission file, and determining the insertion point of the fault diagnosis mechanism according to the first transmission path; In the case where the mechanism type of the target fault diagnosis mechanism is the register level, a second transmission path of the target endpoint is obtained from the endpoint transmission file, and the insertion point of the fault diagnosis mechanism is determined according to the second transmission path, wherein the target endpoint is an endpoint pre-defined as an important endpoint among the various endpoints.
7. The method according to claim 1, It is characterized in that After the target fault diagnosis mechanism is inserted at the insertion point, the method further includes: A safety verification is performed on the target system into which the target fault diagnosis mechanism is inserted, so as to determine that the target system has a safety function corresponding to the target fault diagnosis mechanism.
8. An insertion device for a fault diagnosis mechanism, It is characterized in that include: an acquisition module, used to acquire a logic cone file, a failure rate contribution file, and an endpoint transmission file obtained in the process of executing the safety engineering, wherein the logic cone file includes endpoint distribution data and endpoint connection data of the logic cone, the failure rate contribution file includes the failure rate contribution value of each endpoint to the overall failure rate value of the system, and the endpoint transmission file includes the transmission path between each endpoint; a determination module, configured to determine a mechanism type of a fault diagnosis mechanism according to the logic cone file and the fault rate contribution file, and to determine an insertion point of the fault diagnosis mechanism according to the endpoint transfer file, wherein the mechanism type includes an instance level and a register level; The insertion module is used to obtain a target fault diagnosis mechanism corresponding to the mechanism type and insert the target fault diagnosis mechanism at the insertion point.
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.
