A fault simulation method, device and computer readable storage medium

Abstract

The application provides a fault simulation method, device and computer readable storage medium. The fault simulation method comprises: automatically creating a data model according to a device identifier and a corresponding measuring point identifier; determining a corresponding fault simulation strategy according to the data model; and performing fault simulation on the data model according to the fault simulation strategy. The device represented by the device identifier comprises at least one measuring point represented by the measuring point identifier, and the data model corresponds to the device. The application no longer requires an operation and maintenance personnel to manually input the device identifier and the corresponding measuring point identifier of each device, and then create a data model of each device in sequence, thereby reducing the configuration of the model in the fault simulation, and further improving the automation degree and efficiency during the fault simulation.

Description

[Technical Field]

[0001] This application relates to the field of fault simulation and modeling technology, and in particular to a fault simulation method, device and computer-readable storage medium. [Background Technology]

[0002] With the continuous improvement of informatization, the amount of information accessed by network communication systems such as monitoring systems is increasing, including fault information and alarm information. Among these, fault information is the foundation for maintenance personnel to diagnose faults. In industries such as power and rail, due to the complexity of their equipment and operations, fault diagnosis is quite difficult, and recovery operations for certain faults are time-sensitive. If we want to be able to quickly and accurately diagnose faults when they occur, then the simulation and modeling of faults in the early stages is an indispensable step.

[0003] In related technologies, fault simulation can only simulate specific fault scenarios. However, actual fault scenarios are incredibly diverse, and the corresponding solutions vary widely, resulting in low comprehensiveness of fault simulation. This significantly reduces the monitoring capabilities of operations and maintenance personnel. Furthermore, fault simulation requires extensive configuration by operations and maintenance personnel (such as data model configuration), leading to low automation and efficiency in the process.

[0004] Therefore, it is necessary to improve the above-mentioned fault simulation process. [Summary of the Invention]

[0005] This application provides a fault simulation method, device, and computer-readable storage medium, aiming to solve the problem that the degree of automation and efficiency in fault simulation in related technologies are both low.

[0006] To address the aforementioned technical problems, the first aspect of this application provides a fault simulation method, comprising:

[0007] A data model is automatically created based on the device identifier and the corresponding measurement point identifier; wherein the device identifier represents a device including at least one measurement point represented by the measurement point identifier, and the data model corresponds to the device;

[0008] Based on the data model, determine the corresponding fault simulation strategy;

[0009] Based on the fault simulation strategy, fault simulation is performed on the data model.

[0010] A second aspect of this application provides an electronic device including a storage device and at least one processor, the storage device being configured to store at least one program, and when the at least one program is executed by the at least one processor, causing the at least one processor to perform the fault simulation method as described in the first aspect of this application.

[0011] A third aspect of this application provides a computer-readable storage medium storing executable instructions, which, when executed, perform the fault simulation method as described in the first aspect of this application.

[0012] As can be seen from the above description, compared with related technologies, the beneficial effects of this application are as follows:

[0013] First, a data model is automatically created based on the equipment identifier and the corresponding measurement point identifier. Then, based on the data model, a corresponding fault simulation strategy is determined. Finally, fault simulation is performed on the data model according to the fault simulation strategy. The equipment represented by the equipment identifier includes at least one measurement point represented by a measurement point identifier, and the data model corresponds to the equipment. In practical applications, taking a power system with multiple devices as an example, when fault simulation of the power system is required—that is, when fault simulation is required for each device separately—the equipment identifier and the corresponding measurement point identifier for each device are first obtained. Then, based on the obtained equipment identifier and corresponding measurement point identifier, the data model for each device is automatically created. Since this process eliminates the need for maintenance personnel to manually input the equipment identifier and corresponding measurement point identifier for each device before sequentially creating the data model for each device, it reduces the configuration of models in fault simulation, thereby improving the automation and efficiency of fault simulation. [Attached Image Description]

[0014] To more clearly illustrate the related technologies or the technical solutions in the embodiments of this application, the drawings used in the description of the related technologies or the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application, and not all embodiments. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 A flowchart illustrating the fault simulation method provided in this application embodiment;

[0016] Figure 2 Provided for the embodiments of this application Figure 1 A flowchart illustrating step 110;

[0017] Figure 3 Provided for the embodiments of this application Figure 2A flowchart illustrating step 112 in the middle section;

[0018] Figure 4 Provided for the embodiments of this application Figure 2 A flowchart following step 112;

[0019] Figure 5 Provided for the embodiments of this application Figure 1 A flowchart illustrating step 120;

[0020] Figure 6 Provided for the embodiments of this application Figure 5 A flowchart illustrating step 122 in the middle section;

[0021] Figure 7 Provided for the embodiments of this application Figure 1 A flowchart illustrating step 130 in the middle section;

[0022] Figure 8 Provided for the embodiments of this application Figure 7 A flowchart illustrating step 132 in the middle section;

[0023] Figure 9 A module block diagram of the electronic device provided in the embodiments of this application;

[0024] Figure 10 A block diagram of a computer-readable storage medium provided in an embodiment of this application.

Detailed Implementation Methods

[0025] To make the objectives, technical solutions, and advantages of this application more apparent and understandable, this application will be clearly and completely described below in conjunction with its embodiments and corresponding drawings. Throughout, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions. It should be understood that the various embodiments of this application described below are merely illustrative and not intended to limit this application. That is, all other embodiments obtained by those skilled in the art based on the various embodiments of this application without creative effort are within the scope of protection of this application. Furthermore, the technical features involved in the various embodiments of this application described below can be combined with each other as long as they do not conflict with each other.

[0026] In related technologies, fault simulation can only simulate specific fault scenarios. However, actual fault scenarios are incredibly diverse, and the corresponding solutions vary widely, resulting in low comprehensiveness of fault simulation. This significantly reduces the monitoring capabilities of maintenance personnel. Furthermore, fault simulation requires extensive configuration by maintenance personnel (such as data model configuration), leading to low automation and efficiency. Therefore, this application provides a fault simulation method applicable to network communication systems such as power systems and rail systems. Taking a power system as an example, a power system may include one or more devices, and each device may include one or more measurement points. In this case, fault simulation of a power system essentially involves simulating faults in each device within the power system.

[0027] Please see Figure 1 , Figure 1 This is a flowchart illustrating the fault simulation method provided in the embodiments of this application; from Figure 1 As can be seen from the embodiments of this application, the fault simulation method includes the following steps 110 to 130.

[0028] Step 110: Automatically create a data model based on the equipment identifier and the corresponding measurement point identifier.

[0029] In this embodiment, when fault simulation is required for systems such as power systems and rail systems, it is necessary to first obtain the equipment identifiers of each device in the power system, rail system, etc., as well as the corresponding measurement point identifiers, so as to subsequently create data models for each device using the obtained equipment identifiers and corresponding measurement point identifiers. For ease of description, this embodiment will use the fault simulation of one device in a power system as an example. The fault simulation of other devices in the power system is the same. Moreover, when the fault simulation of all devices in the power system has been completed, the fault simulation of the power system is also completed accordingly.

[0030] When simulating a fault in a power system device, it is necessary to first obtain the device identifier and corresponding measurement point identifiers. Then, based on the obtained device identifier and corresponding measurement point identifiers, a data model of the device is created. The device identifier represents the corresponding device (e.g., a transformer in a power system), and the measurement point identifier represents the corresponding measurement point of the device (e.g., the relay closing and opening measurement points in a transformer). When the device includes multiple measurement points, the device identifier also includes multiple corresponding measurement point identifiers. It can be understood that the data model corresponds to the device; it is an abstraction of the device. As an example, when the device is a transformer, the transformer includes many components (e.g., relays), and the relays have many measurement points (e.g., relay closing and opening measurement points). In this case, the transformer, relays, relay closing and opening measurement points together constitute the transformer's data model. That is, the device identifier, the identifiers of each component in the device, and the identifiers of the measurement points of each component together constitute the device's data model.

[0031] Step 120: Determine the corresponding fault simulation strategy based on the data model.

[0032] In this embodiment, after automatically creating a data model of the device based on the obtained device identifier and corresponding measurement point identifier, it is also necessary to determine a corresponding fault simulation strategy based on the created data model; wherein, there is a correspondence between the data model and the fault simulation strategy. Here, it is necessary to explain that the fault simulation strategy is associated with the measurement points of the device, and it represents what kind of fault simulation needs to be performed on the corresponding measurement point. For example, the fault simulation strategy for the relay closing measurement point can simulate closing failure, simulation of the time consumed by closing the relay closing measurement point exceeding a preset duration, simulation of the inability to receive closing failure / success messages, etc.

[0033] Step 130: Perform fault simulation on the data model according to the fault simulation strategy.

[0034] In this embodiment, after determining the corresponding fault simulation strategy based on the created data model, it is also necessary to perform fault simulation on the corresponding data model of the equipment according to the determined fault simulation strategy. It can be understood that since the data model corresponds to the equipment, performing fault simulation on the data model is essentially performing fault simulation on the corresponding equipment. Specifically, when performing fault simulation on the data model, it may include, but is not limited to, performing fault simulation on the measurement points corresponding to the measurement point identifiers in the data model.

[0035] Furthermore, after performing fault simulation on the corresponding data model of the equipment in step 130, the obtained fault simulation results can be transmitted to the corresponding monitoring terminal of the power system, enabling operation and maintenance personnel to understand the fault simulation status in real time. The obtained fault simulation results may, but are not limited to, be presented in the form of SOE (Sequence of Events). Specifically, the obtained fault simulation results can be transmitted to the corresponding monitoring terminal of the power system through a communication protocol. The communication protocol used can have dynamic expansion capabilities to avoid the situation where the obtained fault simulation results cannot be transmitted to the corresponding monitoring terminal of the power system due to changes or inconsistencies in the communication protocol.

[0036] This embodiment first automatically creates a data model based on the device identifier and the corresponding measurement point identifier; then, based on the data model, it determines the corresponding fault simulation strategy; finally, it performs fault simulation on the data model according to the fault simulation strategy. The device identifier represents a device that includes at least one measurement point represented by a measurement point identifier, and the data model corresponds to the device. In practical applications, when fault simulation is required for a power system containing multiple devices, i.e., when fault simulation is required for each device in the power system separately, the device identifier and the corresponding measurement point identifier for each device are first obtained. Then, based on the obtained device identifier and corresponding measurement point identifier, the data model for each device is automatically created. Since this process eliminates the need for maintenance personnel to manually input the device identifier and the corresponding measurement point identifier for each device before sequentially creating the data model for each device, it reduces the configuration of the model in fault simulation, thereby improving the automation and efficiency of fault simulation.

[0037] As one possible implementation method, please refer to further information. Figure 2 , Figure 2 Provided for the embodiments of this application Figure 1 A flowchart of step 110; from Figure 2 As can be seen from the above, step 110 may specifically include steps 111 to 113.

[0038] Step 111: Obtain the device identifier.

[0039] In this embodiment, when automatically creating the corresponding data model of the device based on the device identifier and the corresponding measurement point identifier, it is necessary to first obtain the corresponding device identifier.

[0040] Step 112: Determine the corresponding measuring point identifier from the preset identifier set according to the equipment identifier.

[0041] In this embodiment, after obtaining the device identifier and the corresponding measurement point identifier, it is also necessary to determine the corresponding measurement point identifier from a preset identifier set based on the obtained device identifier; wherein, there is a correspondence between the device identifier and the measurement point identifier. It can be understood that this embodiment pre-stores the corresponding measurement point identifiers of the device in an identifier set and establishes an association relationship between each measurement point identifier in the identifier set and the corresponding device, that is, it establishes an association relationship between each measurement point identifier in the identifier set and the corresponding device identifier, so that even with only the device identifier, the corresponding measurement point identifier can be automatically obtained based on the association relationship between the device identifier and the measurement point identifier.

[0042] Step 113: Automatically create a data model based on the equipment identifier and measurement point identifier.

[0043] In this embodiment, after determining the corresponding measurement point identifier from a preset identifier set based on the acquired device identifier, it is also necessary to automatically create a corresponding data model for the device based on the acquired device identifier and the determined measurement point identifier. Furthermore, after automatically creating the corresponding data model, the created data model can be stored in a preset model library. This allows for direct retrieval of the corresponding data model from the model library when encountering the same device in the future, eliminating the need to recreate the data model, thereby further improving the automation and efficiency of fault simulation.

[0044] As one specific implementation of this method, please refer to further details. Figure 3 , Figure 3 Provided for the embodiments of this application Figure 2 A flowchart of step 112; from Figure 3 As can be seen from the above, step 112 may specifically include steps 1121 to 1123.

[0045] Step 1121: Based on the equipment identification, find the corresponding measuring point identification from the preset identification set.

[0046] In this specific implementation, when determining the corresponding measurement point identifier from the preset identifier set based on the acquired device identifier, it is necessary to first search for the corresponding measurement point identifier from the preset identifier set based on the acquired device identifier. At this time, there are two situations: one is that the identifier set contains a measurement point identifier corresponding to the device identifier, and the other is that the identifier set does not contain a measurement point identifier corresponding to the device identifier.

[0047] Step 1122: If the measuring point identifier is found, then call the measuring point identifier.

[0048] In this specific implementation, based on the acquired device identifier, the corresponding measurement point identifier is searched from a preset identifier set. If a measurement point identifier corresponding to the device identifier is found, it is called so that the corresponding measurement point identifier can be used to create the corresponding data model of the device later. The measurement point identifier can be called by copying. It is understandable that if a measurement point identifier is used, there is a high probability that its related information will be corrupted. Therefore, to ensure that the measurement point identifiers in the identifier set can be reused, it is necessary to copy the measurement point identifiers from the identifier set, rather than directly using the measurement point identifiers from the identifier set.

[0049] Step 1123: If no measurement point identifier is found, receive the measurement point identifier associated with the device identifier.

[0050] In this specific implementation, based on the acquired device identifier, the corresponding measurement point identifier is searched from a preset identifier set. If no corresponding measurement point identifier is found, the measurement point identifier associated with the device identifier is received. It can be understood that the measurement point identifier associated with the device identifier is input by the maintenance personnel based on the device identifier. Furthermore, after the maintenance personnel input the measurement point identifier associated with the device identifier, they can store the input measurement point identifier associated with the device identifier into the identifier set to update the identifier set.

[0051] It should be understood that the above implementation methods are only preferred implementations of the embodiments of this application, and are not the only limitation on the specific process of step 110 in the embodiments of this application; those skilled in the art can make flexible settings based on the embodiments of this application and according to the actual application scenario.

[0052] As one possible implementation method, please refer to further information. Figure 4 , Figure 4 Provided for the embodiments of this application Figure 2 A flowchart following step 112; from Figure 4 As can be seen from this, step 112 may be followed by steps 410 to 430.

[0053] Step 410: Based on the measuring point markings and the measuring points, determine whether the measuring point markings are compatible with the measuring points.

[0054] In this embodiment, after determining the corresponding measurement point identifier from the preset identifier set based on the acquired device identifier, it is also necessary to determine whether the determined measurement point identifier is compatible with the measurement points of the device, that is, to determine whether the determined measurement point identifier is consistent with the measurement points of the device. This can be done by comparing the determined measurement point identifier with the measurement points of the device. It is understandable that although the corresponding measurement point identifiers for the equipment identifiers are determined from the preset identifier set, the determined measurement point identifiers may not be consistent with the measurement points that the equipment has. For example, the number of determined measurement point identifiers may be less than the number of measurement points that the equipment has, the number of determined measurement point identifiers may be more than the number of measurement points that the equipment has, or the names of the determined measurement point identifiers may differ from those of the measurement points that the equipment has. Therefore, after determining the corresponding measurement point identifiers for the equipment identifiers from the preset identifier set, it is necessary to determine whether the determined measurement point identifiers are compatible with the measurement points that the equipment has. Furthermore, if the determined measurement point identifiers are not compatible with the measurement points that the equipment has, subsequent steps should be taken to make the determined measurement point identifiers compatible with the measurement points that the equipment has.

[0055] Step 420: If the measuring point identifier and the measuring point are not compatible, receive the adjustment instruction related to the difference index between the measuring point identifier and the measuring point.

[0056] In this embodiment, based on the determined measurement point identifiers and the measurement points possessed by the device, it is determined whether the determined measurement point identifiers are compatible with the measurement points possessed by the device. If the determined measurement point identifiers are not compatible with the measurement points possessed by the device, an adjustment instruction related to the difference index between the determined measurement point identifiers and the measurement points possessed by the device is received. The difference index characterizes the differences between the determined measurement point identifiers and the measurement points possessed by the device, such as which measurement point identifiers are added or removed compared to the measurement points possessed by the device, and which measurement point identifiers have different names from the measurement points possessed by the device. Specifically, the adjustment instruction related to the difference index is input by the user based on the differences between the determined measurement point identifiers and the measurement points possessed by the device.

[0057] Step 430: Adjust the measuring point markings according to the adjustment instructions to make them compatible with the measuring points.

[0058] In this embodiment, after receiving an adjustment instruction related to the difference index between the determined measurement point identifier and the measurement points possessed by the device, it is necessary to adjust the determined measurement point identifier according to the received adjustment instruction to make the determined measurement point identifier compatible with the measurement points possessed by the device. The adjustment to the determined measurement point identifier may include, but is not limited to, adding, deleting, and correcting measurement point identifiers. Furthermore, after adjusting the determined measurement point identifier, the adjusted measurement point identifier can be maintained in the identifier set to update the identifier set.

[0059] It should be understood that the above implementation is only a preferred implementation of the embodiments of this application, and is not the only limitation of the additional process after step 112 in the embodiments of this application; those skilled in the art can make flexible settings based on the embodiments of this application and according to the actual application scenario.

[0060] As one possible implementation method, please refer to further information. Figure 5 , Figure 5 Provided for the embodiments of this application Figure 1 A flowchart of step 120; from Figure 5 As can be seen from the text, step 120 may specifically include steps 121 to 122.

[0061] Step 121: Call the data model from the model library.

[0062] In this embodiment, when determining the corresponding fault simulation strategy based on the created data model, it is necessary to first call the corresponding data model of the device from the preset model library.

[0063] Step 122: Based on the data model, determine the corresponding fault simulation strategy from the preset strategy set.

[0064] In this embodiment, after calling the corresponding data model of the device from the preset model library, it is also necessary to determine the corresponding fault simulation strategy from the preset strategy set based on the called data model. It can be understood that this embodiment pre-stores the corresponding fault simulation strategies of the device in a strategy set and establishes the association between each fault simulation strategy in the strategy set and the corresponding device, that is, it establishes the association between each fault simulation strategy in the strategy set and the corresponding data model. This allows the corresponding fault simulation strategy to be automatically obtained based on the association between the data model and the fault simulation strategy, even when only the data model is available. Specifically, the fault simulation strategies in the strategy set often include multiple strategies, which cover various faults present at each measurement point in the corresponding device. As mentioned earlier, the fault simulation strategy is associated with the measurement points of the device. It should be noted that the fault simulation strategy associated with the same measurement point can include one or multiple strategies.

[0065] As a specific implementation of this embodiment, before determining the corresponding fault simulation strategy from the preset strategy set based on the invoked data model, the method may further include: presetting the corresponding fault simulation strategy of the device into the strategy set using a scripting language. Specifically, the scripting language used may include, but is not limited to, JavaScript, Lua, C Shell, Perl, PHP, Python, Ruby, VBScript, and CSS, or may be a combination of multiple scripting languages.

[0066] As one specific implementation of this method, please refer to further details. Figure 6 , Figure 6 Provided for the embodiments of this application Figure 5 The flowchart for step 122 is shown below; from Figure 6 As can be seen from the text, step 122 may specifically include steps 1221 to 1223.

[0067] Step 1221: Based on the data model, find the corresponding fault simulation strategy from the preset strategy set.

[0068] In this specific implementation, when determining the corresponding fault simulation strategy from the preset strategy set based on the invoked data model, it is necessary to first search for the corresponding fault simulation strategy from the preset strategy set based on the invoked data model. At this point, there are two possibilities: either the strategy set contains a fault simulation strategy corresponding to the data model, or the strategy set does not contain a fault simulation strategy corresponding to the data model.

[0069] Step 1222: If a fault simulation strategy is found, then the fault simulation strategy is invoked.

[0070] In this specific implementation, based on the called data model, a corresponding fault simulation strategy is searched from a preset strategy set. If a fault simulation strategy corresponding to the data model is found, it is called so that the called fault simulation strategy can be used to simulate faults in the corresponding data model later. The fault simulation strategy can be called by copying. It is understood that if a fault simulation strategy is used, there is a high probability that its related information will be corrupted. Therefore, to ensure that the fault simulation strategies in the strategy set can be reused, it is necessary to copy the fault simulation strategies from the strategy set, rather than directly using the fault simulation strategies in the strategy set.

[0071] Step 1223: If no fault simulation strategy is found, then receive the fault simulation strategy associated with the data model.

[0072] In this specific implementation, based on the invoked data model, a corresponding fault simulation strategy is searched from a preset strategy set. If no corresponding fault simulation strategy for the data model is found, the fault simulation strategy associated with the data model is received. It can be understood that the fault simulation strategy associated with the data model is input by operations personnel based on the data model. Furthermore, after operations personnel input the fault simulation strategy associated with the data model, they can store the input strategy in the strategy set to update the strategy set.

[0073] It should be understood that the above-described embodiments are merely preferred implementations of the present application, and are not the only limitation on the specific process of step 120 in the present application. Those skilled in the art can make flexible settings based on the present application embodiments and actual application scenarios.

[0074] As one possible implementation method, please refer to further information. Figure 7 , Figure 7 Provided for the embodiments of this application Figure 1 A flowchart of step 130; from Figure 7 As can be seen from the above, step 130 may specifically include steps 131 to 133.

[0075] Step 131: Based on the measurement points associated with each fault simulation strategy, confirm the duplication among the measurement points associated with each fault simulation strategy.

[0076] In this embodiment, since the equipment typically has multiple measurement points, and the fault simulation strategy is associated with these measurement points, the corresponding fault simulation strategy for the equipment usually also includes multiple strategies. Based on this, when performing fault simulation on the corresponding data model of the equipment according to the determined fault simulation strategy, it is necessary to first confirm the overlap between the measurement points associated with each fault simulation strategy. As mentioned earlier, a fault simulation strategy associated with the same measurement point can include one or more. Therefore, when there are multiple fault simulation strategies associated with the same measurement point, these multiple fault simulation strategies cannot be executed simultaneously; otherwise, conflicts will occur between the execution of the various fault simulation strategies. Therefore, this embodiment needs to confirm the overlap between the measurement points associated with each determined fault simulation strategy.

[0077] Of course, the inability of certain fault simulation strategies to execute simultaneously is not limited to situations where multiple fault simulation strategies are associated with the same measurement point. In fact, if the execution of the first fault simulation strategy leads to the execution of the second fault simulation strategy, then the second fault simulation strategy and the first fault simulation strategy that caused it to be executed cannot be executed simultaneously. In this case, there is a causal relationship between the second fault simulation strategy and the first fault simulation strategy that caused it to be executed (i.e., because the first fault simulation strategy is executed, the second fault simulation strategy is also executed). For example, the execution of fault simulation strategy A leads to the execution of fault simulation strategy B; that is, fault simulation strategy B is executed simultaneously with fault simulation strategy A. If fault simulation strategy A and fault simulation strategy B are executed simultaneously, then fault simulation strategy B will have two execution flows at the same time, resulting in a conflict. Therefore, fault simulation strategy A and fault simulation strategy B cannot be executed simultaneously, which also illustrates that fault simulation strategies with a causal relationship cannot be executed simultaneously.

[0078] Step 132: Determine the execution order of all fault simulation strategies based on the repetition situation.

[0079] In this embodiment, when multiple fault simulation strategies are associated with the same measurement point, these strategies cannot be executed simultaneously. Therefore, determining the execution order of all fault simulation strategies becomes crucial. Thus, after identifying the overlap between the measurement points associated with each fault simulation strategy, this embodiment also needs to determine the execution order of all fault simulation strategies based on this overlap. Alternatively, the execution order can be determined based on the causal relationships between the fault simulation strategies; this method will be explained below.

[0080] Step 133: Based on the execution order, perform fault simulation on the data model according to each fault simulation strategy.

[0081] In this embodiment, after determining the execution order of all fault simulation strategies, it is also necessary to perform fault simulation on the corresponding data model of the device according to the determined execution order and each fault simulation strategy. Since the fault simulation on the corresponding data model of the device is performed according to the execution order of all fault simulation strategies that has been determined, there will be no conflict in this process.

[0082] As a specific implementation of this embodiment, the execution attributes of the fault simulation strategy may include execution mode and execution priority. The execution mode may include serial mode or parallel mode; wherein, serial mode indicates that the target fault simulation strategy needs to be executed independently relative to other fault simulation strategies, and parallel mode indicates that the target fault simulation strategy needs to be executed simultaneously with at least one other fault simulation strategy; for example, fault simulation strategies associated with measurement point 1 include fault simulation strategy C and fault simulation strategy D, and fault simulation strategies associated with measurement point 2 include fault simulation strategy E. Then, fault simulation strategies C and D cannot be executed simultaneously, fault simulation strategies E and C can be executed simultaneously, and fault simulation strategies E and D can be executed simultaneously. That is, the serial mode of fault simulation strategy C indicates that it cannot be executed simultaneously with fault simulation strategy D, and the serial mode of fault simulation strategy D indicates that it cannot be executed simultaneously with fault simulation strategy C. The execution of fault simulation strategy E is characterized by its parallel execution mode, indicating that it can be executed simultaneously with fault simulation strategy C or fault simulation strategy D. For example, the execution of fault simulation strategy M may lead to the execution of fault simulation strategy N, while the execution of fault simulation strategy P may not lead to the execution of other fault simulation strategies. Therefore, fault simulation strategies M and N cannot be executed simultaneously, while fault simulation strategies P and M can be executed simultaneously, and fault simulation strategies P and N can also be executed simultaneously. In other words, the serial execution mode of fault simulation strategy M indicates that it cannot be executed simultaneously with fault simulation strategy N, and the serial execution mode of fault simulation strategy N indicates that it cannot be executed simultaneously with fault simulation strategy M. The parallel execution mode of fault simulation strategy P indicates that it can be executed simultaneously with either fault simulation strategy M or fault simulation strategy N. Execution priority indicates the order in which each fault simulation strategy is executed when there are multiple fault simulation strategies. For example, if the execution priority of fault simulation strategy U is higher than that of fault simulation strategy V, then fault simulation strategy U will be executed first, and fault simulation strategy V will be executed later.

[0083] Based on this, please refer to further reading Figure 8 , Figure 8 Provided for the embodiments of this application Figure 7 A flowchart of step 132; from Figure 8 As can be seen from the above, step 132 may specifically include the following steps 1321 to 1322.

[0084] Step 1321: Based on the repetition situation, obtain the target execution attributes of each fault simulation strategy accordingly.

[0085] In this specific implementation, when determining the execution order of all fault simulation strategies based on the repetition among the measurement points associated with each fault simulation strategy, it is necessary to first obtain the target execution attributes (i.e., execution method and / or execution priority) of each fault simulation strategy according to the repetition among the measurement points associated with each fault simulation strategy. This is so that the execution order of all fault simulation strategies can be determined subsequently using the obtained target execution attributes of each fault simulation strategy. In this case, referring to the example of "fault simulation strategy M, fault simulation strategy N, and fault simulation strategy P" given above, the execution method of each fault simulation strategy can characterize the causal relationship between each fault simulation strategy. Therefore, when determining the execution order of all fault simulation strategies using the execution method of each fault simulation strategy, it is essentially also using the causal relationship between each fault simulation strategy to determine the execution order of all fault simulation strategies.

[0086] It is understandable that the methods for determining the execution order of all fault simulation strategies may differ depending on the different repetition situations among the measurement points associated with each fault simulation strategy. For example, for a certain repetition situation among the measurement points associated with each fault simulation strategy, the execution order of all fault simulation strategies can be determined solely by using the execution method of each fault simulation strategy; or, the execution order of all fault simulation strategies can be determined solely by using the execution priority of each fault simulation strategy; or, in addition to using the execution method of each fault simulation strategy, the execution priority of each fault simulation strategy also needs to be used to determine the execution order of all fault simulation strategies. Therefore, in determining the execution order of all fault simulation strategies, this embodiment needs to obtain the target execution attributes of each fault simulation strategy according to the repetition situation among the measurement points associated with each fault simulation strategy.

[0087] Step 1322: Determine the execution order of all fault simulation strategies based on the target execution attributes of each fault simulation strategy.

[0088] In this specific implementation, after obtaining the target execution attributes of each fault simulation strategy, it is also necessary to determine the execution order of all fault simulation strategies based on these attributes. This ensures that subsequent fault simulations are performed on the corresponding data model of the equipment according to each fault simulation strategy, based on the determined execution order. It can be understood that the target execution attributes of each fault simulation strategy have fully considered the overlap between the measurement points associated with each strategy. Therefore, during the fault simulation of the corresponding data model of the equipment according to the determined execution order, no conflicts will occur.

[0089] In this embodiment, the fault simulation strategy may include at least one of a first simulation strategy and a second simulation strategy; wherein, the first simulation strategy is associated with a single measurement point, and the second simulation strategy is associated with at least two measurement points. It is necessary to explain here that the second simulation strategy being associated with at least two measurement points can be understood as randomly combining multiple measurement points of the device to obtain multiple combined measurement points (each combined measurement point includes at least two measurement points), and then associating these multiple combined measurement points with corresponding fault simulation strategies; for example, if the device has three measurement points, a, b, and c, then randomly combining a, b, and c will result in four combined measurement points, ab, ac, bc, and abc. Then, ab is associated with fault simulation strategy Q, ac with fault simulation strategy R, bc with fault simulation strategy S, and abc with fault simulation strategy T. At this point, since fault simulation strategies Q, R, S, and T are all associated with at least two measurement points, they all belong to the second simulation strategy. It is understood that this embodiment associates the first simulation strategy with a single measurement point and the second simulation strategy with a combination of measurement points, which includes at least two measurement points, obtained by randomly combining the measurement points. This enables the embodiments of this application to cover various different fault scenarios, rather than only being able to simulate faults for specific fault scenarios, thereby effectively improving the comprehensiveness of fault simulation.

[0090] Based on the fault simulation strategy including at least one of the first and second simulation strategies, the corresponding fault simulation strategy for the equipment can be divided into three cases: first, the corresponding fault simulation strategy for the equipment includes only multiple first simulation strategies; second, the corresponding fault simulation strategy for the equipment includes only multiple second simulation strategies; and third, the corresponding fault simulation strategy for the equipment includes multiple first simulation strategies and multiple second simulation strategies. As the situation of the corresponding fault simulation strategy for the equipment differs, the repetition between the measurement points associated with each fault simulation strategy determined in step 131 will also differ. Accordingly, the process of determining the execution order of all fault simulation strategies based on the repetition will differ in step 132. The following will illustrate the process of determining the execution order using the situation of the fault simulation strategy and the repetition between the measurement points associated with each fault simulation strategy as variables.

[0091] Example 1: When a fault simulation strategy includes multiple first simulation strategies, the process for determining the execution order is as follows: Based on the measurement points associated with each first simulation strategy, confirm the duplication among the measurement points associated with each first simulation strategy; if there is no duplication among the measurement points associated with each first simulation strategy, obtain the execution conditions of each first simulation strategy; based on the execution conditions of each first simulation strategy, determine the execution order of all first simulation strategies; if there is duplication among the measurement points associated with each first simulation strategy, obtain the execution priority of each first simulation strategy; based on the execution priority of each first simulation strategy, determine the execution order of all first simulation strategies.

[0092] Example 2: When a fault simulation strategy includes multiple second simulation strategies, the process for determining the execution order is as follows: Based on the measurement points associated with each second simulation strategy, confirm the overlap between the measurement points associated with each second simulation strategy; if there is no overlap between the measurement points associated with each second simulation strategy, obtain the execution conditions of each second simulation strategy; based on the execution conditions of each second simulation strategy, determine the execution order of all second simulation strategies; if there is overlap between the measurement points associated with each second simulation strategy, obtain the execution priority of each second simulation strategy; based on the execution priority of each second simulation strategy, determine the execution order of all second simulation strategies.

[0093] Example 3: When the fault simulation strategy includes multiple first simulation strategies and multiple second simulation strategies, the process for determining the execution order is as follows: Based on the measurement points associated with each first simulation strategy and each second simulation strategy, determine the first repetition situation between the measurement points associated with each first simulation strategy, the second repetition situation between the measurement points associated with each second simulation strategy, and the third repetition situation between the measurement points associated with each first simulation strategy and each second simulation strategy; based on the first repetition situation, the second repetition situation, and the third repetition situation, obtain the target execution attributes of each first simulation strategy and the target execution attributes of each second simulation strategy accordingly; based on the target execution attributes of each first simulation strategy and the target execution attributes of each second simulation strategy, determine the execution order of all first simulation strategies and all second simulation strategies.

[0094] It's understandable that Example 3 is more complex than Examples 1 and 2 because it has three types of repetition, while Examples 1 and 2 each have only one type of repetition. However, regardless of whether it's Example 1, Example 2, or Example 3, the following conditions must be met when determining the execution order: multiple fault simulation strategies related to the same measurement point cannot be executed simultaneously, and multiple fault simulation strategies with causal relationships cannot be executed simultaneously.

[0095] In summary, the embodiments of this application determine the execution order of all fault simulation strategies based on the repetition among the measurement points associated with each fault simulation strategy. However, in practice, it is not limited to this. For example, maintenance personnel can pre-store multiple execution orders corresponding to the device in a sequence set. Then, before performing fault simulation on the corresponding data model of the device according to each fault simulation strategy, a suitable execution order can be selected from the sequence set. This eliminates the need to redetermine the execution order of all fault simulation strategies based on the repetition among the measurement points associated with each fault simulation strategy, thereby further improving the automation and efficiency of fault simulation.

[0096] It should be understood that the above implementation is only a preferred implementation of the embodiments of this application, and is not the only limitation on the specific process of step 130 in the embodiments of this application; those skilled in the art can make flexible settings based on the embodiments of this application and according to the actual application scenario.

[0097] Please see Figure 9 , Figure 9 A block diagram of an electronic device provided in an embodiment of this application.

[0098] like Figure 9 As shown, this application embodiment also provides an electronic device 910, including a storage device 911 and at least one processor 912; wherein, the storage device 911 is used to store at least one program, and when the at least one program is executed by the at least one processor 912, the at least one processor 912 causes the at least one processor 912 to execute the fault simulation method provided in this application embodiment.

[0099] In some embodiments, the electronic device 910 may further include a bus 913 for a communication connection between the storage device 911 and at least one processor 912.

[0100] Please see Figure 10 , Figure 10 A block diagram of a computer-readable storage medium provided in an embodiment of this application.

[0101] like Figure 10 As shown, this application embodiment also provides a computer-readable storage medium 1010, which stores executable instructions 1011. When the executable instructions 1011 are executed, the fault simulation method provided in this application embodiment is executed.

[0102] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0103] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk).

[0104] It should be noted that the various embodiments in this application are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For product-related embodiments, since they are similar to method-related embodiments, the descriptions are relatively simple, and relevant parts can be referred to the descriptions of the method-related embodiments.

[0105] It should also be noted that, in this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0106] The above description of the disclosed embodiments enables those skilled in the art to implement or use the content of this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined in this application may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A fault simulation method, characterized in that, include: Obtain a device identifier; determine corresponding measurement point identifiers from a preset identifier set based on the device identifier; automatically create a data model based on the device identifier and the measurement point identifiers; wherein the device represented by the device identifier includes at least one measurement point represented by the measurement point identifier, and the data model corresponds to the device; the data model includes the identifier of the device, the identifiers of each component in the device, and the identifiers of the measurement points possessed by each component; the device includes a transformer, and the measurement points include relay closing measurement points and relay opening measurement points of the transformer; Based on the data model, a corresponding fault simulation strategy is determined; wherein, the fault simulation strategy is associated with the measuring point and includes the simulation of the relay closing measuring point failing to close and the simulation of the time consumed by the relay closing measuring point to close. When there are multiple fault simulation strategies, the duplication between the measurement points associated with each fault simulation strategy is confirmed based on the measurement points associated with each fault simulation strategy. Based on the repetition situation, the target execution attributes of each of the fault simulation strategies are obtained accordingly; The execution order of all the fault simulation strategies is determined based on the target execution attributes of each of the fault simulation strategies. According to the execution order, fault simulation is performed on the data model according to each of the fault simulation strategies; the fault simulation strategy includes at least one of a first simulation strategy and a second simulation strategy; wherein, the first simulation strategy is associated with a single measurement point, and the second simulation strategy is associated with at least two measurement points; The execution attributes of the fault simulation strategy include execution mode and execution priority; the execution mode includes serial mode or parallel mode, the serial mode indicates that the target fault simulation strategy is executed alone relative to other fault simulation strategies, and the parallel mode indicates that the target fault simulation strategy is executed simultaneously with at least one other fault simulation strategy; The fault simulation strategy includes at least one of a first simulation strategy and a second simulation strategy, wherein the first simulation strategy is associated with a single measurement point and the second simulation strategy is associated with at least two measurement points; The step of determining the corresponding measuring point identifier from a preset identifier set based on the device identifier further includes: Based on the measuring point identifier and the measuring point, determine whether the measuring point identifier is compatible with the measuring point; If the measuring point identifier is not compatible with the measuring point, then an adjustment instruction related to the difference index between the measuring point identifier and the measuring point is received; According to the adjustment instruction, the measuring point identifier is adjusted to be compatible with the measuring point.

2. The fault simulation method as described in claim 1, characterized in that, The step of determining the corresponding measuring point identifier from a preset identifier set based on the device identifier includes: Based on the device identifier, the corresponding measuring point identifier is searched from the preset identifier set; If the measuring point identifier is found, then the measuring point identifier is invoked; If the measurement point identifier is not found, the measurement point identifier associated with the device identifier is received.

3. The fault simulation method as described in claim 1, characterized in that, The step of determining the corresponding fault simulation strategy based on the data model includes: Based on the data model, the corresponding fault simulation strategy is searched from the preset strategy set; If the fault simulation strategy is found, then the fault simulation strategy is invoked; If the fault simulation strategy is not found, the fault simulation strategy associated with the data model is received.

4. An electronic device, characterized in that, The device includes a storage device and at least one processor, the storage device being used to store at least one program, and when the at least one program is executed by the at least one processor, causing the at least one processor to perform the method as described in any one of claims 1 to 3.

5. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores executable instructions that, when executed, perform the method as described in any one of claims 1 to 3.

Images