Simulation-based network system reliability evaluation method, device and computer equipment

Abstract

The application relates to a simulation-based network system reliability evaluation method, device and computer equipment. The method comprises the following steps: obtaining a network system reliability model of a target network system; determining total task time of the target network system and task parameters of each task, wherein the task parameters comprise a start time, an end time, corresponding system activities / functions, and corresponding logical units, each logical unit corresponds to a physical component, and the physical component comprises a hardware device or a software component; performing reliability simulation on the network system reliability model of the target network system to obtain a simulation result; and evaluating the reliability of the target network system based on the simulation result. The method can more accurately evaluate the network system reliability.

Description

Technical Field

[0001] This application relates to the field of network system technology, and in particular to a simulation-based network system reliability assessment method, apparatus, and computer equipment. Background Technology

[0002] From large-scale power grid systems to global transportation networks, from telephone communication networks to integrated air-space-ground networks, network systems are ubiquitous. However, network system failures can have catastrophic consequences, making reliability assessments crucial.

[0003] Assessing the reliability of a network system first requires building a model of the network system, and then using this model to conduct reliability assessments. However, traditional methods of using constructed network system models for reliability assessment suffer from inaccuracies. Summary of the Invention

[0004] Therefore, it is necessary to provide a simulation-based network system reliability assessment method, apparatus, and computer equipment that can more accurately evaluate the reliability of network systems, addressing the aforementioned technical problems.

[0005] Firstly, this application provides a simulation-based method for evaluating the reliability of network systems. The method includes:

[0006] Obtain the network system reliability model of the target network system;

[0007] Determine the total task time of the target network system and the task parameters of each task. The task parameters include start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, and the physical component includes hardware devices or software components.

[0008] A reliability simulation is performed on the network system reliability model of the target network system to obtain simulation results. In each simulation, faulty physical components that fail during the execution of each task of the target network system are randomly identified to form fault events during the use of the target network system. Based on the occurrence of the fault events, fault handling is performed and the fault handling results are recorded. The fault handling results include: fault start time, fault handling completion time, and whether the fault affects the execution of the tasks of the target network system.

[0009] The reliability of the target network system is evaluated based on the simulation results.

[0010] In one embodiment, the fault handling based on the occurrence of the fault event includes:

[0011] Determine if a redundant backup component for the faulty physical component is available;

[0012] If redundant backup components exist, activate the redundant backup components for fault handling.

[0013] If there are no redundant backup components, determine whether the current network topology of the target network system can meet the basic connectivity requirements for the implementation of various system activities / functions, obtain the basic connectivity requirement determination result, and perform fault handling based on the basic connectivity requirement determination result.

[0014] In one embodiment, the fault handling based on the basic connectivity requirement determination result includes:

[0015] If the basic connectivity requirement determination result is that the basic connectivity requirement is not met, it is determined that the activity / function of the target network system is interrupted by a fault event, the start time of the activity / function interruption is recorded, and the end time of the activity / function interruption is recorded when the network topology of the target network system meets the basic connectivity requirement.

[0016] If the basic connectivity requirement determination result is that the basic connectivity requirement is met, determine whether the faulty physical component affects the critical activity / function, obtain the critical activity / function determination result, and perform fault handling based on the critical activity / function determination result.

[0017] In one embodiment, the fault handling based on the key activity / function determination result includes:

[0018] If the determination result of the critical activity / function is that it does not affect the critical activity / function, record the start time of the activity / function interruption, and record the end time of the activity / function interruption when the network topology of the target network system reaches the basic connectivity requirements.

[0019] If the determination result of the critical activity / function is that it affects the critical activity / function, determine whether there are other physical components that can replace the function of the faulty physical component, obtain the substitutability judgment result, and perform fault handling based on the substitutability judgment result.

[0020] In one embodiment, the fault handling based on the substitutability determination result includes:

[0021] If the substitutability determination result is that there is no other physical component that can replace the function of the faulty physical component, record the start time of the activity / function interruption, and record the system activity / function recovery time when the interrupted system activity / function is restored.

[0022] If the substitutability determination result indicates the existence of other physical components that can replace the function of the faulty physical component, system function reconstruction is performed, and the network topology is updated based on the network system function reconstruction result. If the updated network topology cannot meet the basic connectivity requirements for the implementation of various system activities / functions, the start time of the activity / function interruption is recorded, and the end time of the activity / function interruption is recorded when the network topology of the target network system meets the basic connectivity requirements.

[0023] In one embodiment, evaluating the reliability of the target network system based on the simulation results includes:

[0024] The number of interruptions for each task during the cyclic simulation process is counted, with each task corresponding to one interruption count;

[0025] Based on the recorded start time, end time, and recovery time of the activity / function interruption, the normal operating time and failure time of each function during the cyclic simulation are statistically analyzed.

[0026] The reliability of each task is determined based on the number of interruptions for each task.

[0027] The reliability of the target network system is evaluated based on the uptime, the downtime, and the reliability of each task.

[0028] In one embodiment, evaluating the reliability of the target network system based on the uptime, the downtime, and the task reliability of each task includes:

[0029] The functional availability of each function of the target network system is determined based on the ratio of the normal uptime to the sum of the normal uptime and the downtime.

[0030] The system task reliability of the target network system is determined based on the task reliability of each task.

[0031] Secondly, this application also provides a simulation-based network system reliability assessment device. The device includes:

[0032] The model acquisition module is used to acquire the network system reliability model of the target network system.

[0033] The parameter determination module is used to determine the total task time of the target network system and the task parameters of each task. The task parameters include start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, and the physical component includes hardware devices or software components.

[0034] The model simulation module is used to perform reliability simulation on the network system reliability model of the target network system and obtain simulation results. In each simulation process, the failed physical components that fail during the task execution of each task of the target network system are randomly identified, forming failure events during the use of the target network system. Based on the failure events, failure handling is performed, and the failure handling results are recorded. The failure handling results include: failure start time, failure handling completion time, and whether the failure affects the execution of the tasks of the target network system.

[0035] The reliability assessment module is used to assess the reliability of the target network system based on the simulation results.

[0036] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of any of the methods described above.

[0037] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of any of the methods described above.

[0038] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of any of the methods described above.

[0039] The aforementioned simulation-based network system reliability assessment method, apparatus, and computer equipment acquire a network system reliability model of the target network system, determine the total task time and task parameters of each task, including start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, which includes hardware devices or software components. Reliability simulation is performed on the network system reliability model of the target network system to obtain simulation results, and the reliability of the target network system is assessed based on these results. Compared to traditional techniques that rely on constructed network system models for reliability assessment, which are often inaccurate, this embodiment considers both hardware devices and software components in the target network system, allowing for more accurate network system reliability assessment and solving the problem of inaccurate network system reliability assessment. Attached Figure Description

[0040] Figure 1 This is a flowchart illustrating the simulation-based network system reliability assessment method provided in the embodiments of this application;

[0041] Figure 2 This is a flowchart illustrating the process of obtaining a network system reliability model for a target network system in one embodiment.

[0042] Figure 3 This is a flowchart illustrating the process of establishing mapping relationships in one embodiment;

[0043] Figure 4 This is a schematic diagram illustrating the establishment of a mapping relationship provided in an embodiment of this application;

[0044] Figure 5 This is a schematic diagram illustrating the process of performing system reliability modeling on the target network in one embodiment;

[0045] Figure 6 This is a schematic diagram of a hardware device maintenance and support strategy provided in an embodiment of this application;

[0046] Figure 7 This is a schematic diagram of a network topology provided in an embodiment of this application;

[0047] Figure 8 This is a schematic diagram of a fault handling process based on an occurrence of a fault event in one embodiment.

[0048] Figure 9 This is a schematic diagram of a fault handling process based on the basic connectivity requirement determination result in one embodiment.

[0049] Figure 10This is a flowchart illustrating fault handling based on the determination results of key activities / functions in one embodiment.

[0050] Figure 11 This is a schematic diagram of a fault handling process based on the substitutability judgment result in one embodiment;

[0051] Figure 12 This is a flowchart illustrating a reliability simulation process provided in an embodiment of this application;

[0052] Figure 13 This is a flowchart illustrating the process of evaluating the reliability of a target network system based on simulation results in one embodiment.

[0053] Figure 14 This is a flowchart illustrating the process of evaluating the reliability of a target network system in one embodiment;

[0054] Figure 15 This is a structural block diagram of a simulation-based network system reliability assessment device provided in the embodiments of this application;

[0055] Figure 16 This is a diagram showing the internal structure of a computer device in an embodiment of this application. Detailed Implementation

[0056] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0057] This embodiment provides a simulation-based network system reliability assessment method. This embodiment uses the application of this method to computer equipment as an example for illustration. It can be understood that this method can also be applied to servers, and can also be applied to systems including computer equipment and servers, and can be implemented through the interaction between computer equipment and servers.

[0058] Figure 1 This is a flowchart illustrating a simulation-based network system reliability assessment method provided in this application embodiment. The method is applied to computer equipment or servers. In one embodiment, such as... Figure 1 As shown, it includes the following steps:

[0059] S101, Obtain the network system reliability model of the target network system.

[0060] The target network system refers to the network system for which a reliability assessment is required. The network system reliability model is used to describe various parameters of the target network system. The network system can be a large-scale power grid system or a global transportation network system; there is no limitation here.

[0061] S102, determine the total task time of the target network system and the task parameters of each task. The task parameters include start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, and the physical component includes hardware devices or software components.

[0062] In this context, system activities / functions refer to the functional parts actually executed in a network system when a certain system task is completed. A network system establishes connections with physical components through logical units, and the physical components are arranged according to certain logic within the logical units to implement a specific system activity / function.

[0063] S103, perform reliability simulation on the network system reliability model of the target network system and obtain simulation results. In each simulation, randomly determine the physical components that fail during the task execution of each task of the target network system, forming fault events during the use of the target network system. Based on the fault events, perform fault handling and record the fault handling results, including: fault start time, fault handling completion time, and whether the fault affects the execution of tasks of the target network system.

[0064] The fault events are generated randomly, and a fault event can correspond to one or more physical components that have failed.

[0065] S104. Evaluate the reliability of the target network system based on simulation results.

[0066] This embodiment provides a simulation-based network system reliability assessment method. By acquiring a network system reliability model of the target network system, it determines the total task time and task parameters for each task. The task parameters include start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, which includes hardware devices or software components. Reliability simulation is performed on the network system reliability model of the target network system to obtain simulation results. The reliability of the target network system is then assessed based on these simulation results. Compared to traditional techniques that rely on constructed network system models for reliability assessment, which are often inaccurate, this embodiment considers both hardware devices and software components in the target network system, allowing for a more accurate network system reliability assessment and solving the problem of inaccurate network system reliability assessment.

[0067] The process of constructing the network system reliability model for the target network system in S101 above is described in detail here. See [link to documentation]. Figure 2 , Figure 2 This is a flowchart illustrating the process of obtaining a network system reliability model for a target network system in one embodiment. This embodiment relates to one implementation method for constructing a network system reliability model for a target network system. Based on the above embodiment, S101 includes:

[0068] S201, decompose the system tasks and system functions of the target network system. Starting from the system tasks, establish the mapping relationship between the target network system tasks, system activities / functions, logical units and physical components. Physical components include hardware devices or software components.

[0069] In this embodiment, the target network system can be used to perform multiple tasks, that is, it contains multiple task profiles. Here, an example is given to decompose a certain task profile in the target network system to illustrate the way to establish the mapping relationship between the target network system tasks, system activities / functions, logical units, and physical components.

[0070] refer to Figure 3 and Figure 4 As shown, in one embodiment, the method for establishing the mapping relationship in S201 above includes:

[0071] S301, Determine the system task profile based on the application scenario of the target network system.

[0072] In this embodiment, the application scenario of the target network system can be video or document editing; any application scenario that can be implemented through a network system is acceptable and is not limited here. The system task profile can be, for example, a video task profile.

[0073] S302, Based on the system task profile, determine each system task and the system task information of each system task. The system task information includes: the start and end time of the system task.

[0074] Among them, system tasks refer to multiple subtasks under the system task profile.

[0075] In this embodiment, reference Figure 4 As shown, in a specific example, m system tasks are identified under a certain task profile, and these m system tasks are labeled as (M... s1 M s2 ,…,M sm ), and determine the start and end times of each system task, respectively ((t 10 ,t 11 ),(t 20 ,t 21 ),…,(t m0 ,t m1 )).

[0076] S303, analyze the system activities / functions included in each system task, and establish the mapping relationship between each system task and system activities / functions.

[0077] In this embodiment, each system task includes at least one system activity / function, and the system task is associated with its corresponding system activity / function.

[0078] See Figure 4 With system task M S2 For example, system task M S2 It contains K system activities / functions, labeled (LM1, LM2, ..., LM3). k This establishes a mapping relationship between system tasks and system activities / functions.

[0079] S304, determine the corresponding logic units for each system activity / function, and the physical components that make up each logic unit.

[0080] exist Figure 4 In the example shown, the target network system has j logical units, labeled as (LU1, LU2, ..., LU3). j Each system activity / function requires at least one logical unit to implement the corresponding activity / function, and a mapping relationship is established between each system activity / function and its required logical unit. Furthermore, the target network system has n physical components, and each logical unit is composed of at least one physical component with a certain logical structure, establishing a mapping relationship between each logical unit and its corresponding physical component.

[0081] After establishing the mapping relationship, it is also necessary to deploy the corresponding attribute information for each physical component in the target network system. The deployed physical component attribute information is reflected in the specific implementation. The attribute information of the physical components is shown in Table 1 below.

[0082] Table 1 Physical Component Attribute Information

[0083]

[0084]

[0085] S202, Based on the established mapping relationship, perform system reliability modeling on the target network system to obtain the network system reliability model of the target network system.

[0086] In this embodiment, based on the established mapping relationship, system reliability modeling is performed on the target network system. See [link / reference]. Figure 5 , Figure 5This is a flowchart illustrating the process of performing system reliability modeling on a target network in one embodiment. This embodiment relates to an implementation method for performing system reliability modeling on a target network system. Based on the above embodiment, S202 includes:

[0087] S501 analyzes each physical component in the target network system to determine the maintenance and support activities triggered by the failure of each physical component, as well as the maintenance and support strategies.

[0088] In this embodiment, each physical component in the target network system is analyzed separately. If the physical component is a software component and the software component can self-recover, then a maintenance and support activity to enable the software component to self-recover is triggered.

[0089] If the physical component is a hardware device, and that hardware device is repairable, then a maintenance support activity is triggered, and a corresponding maintenance support strategy is formulated. Figure 6 This is a schematic diagram illustrating a maintenance and support strategy for a hardware device provided in an embodiment of this application. The maintenance and support strategy can be as follows: Figure 6 The process begins with using tools from the spare parts and tool libraries to analyze and confirm the fault. After analysis and confirmation, the tools are returned to the spare parts and tool libraries. Next, the faulty component is disassembled using tools from the spare parts and tool libraries, and then returned to the spare parts and tool libraries. Then, the faulty component is repaired or replaced using tools from the spare parts and tool libraries, and then returned to the spare parts and tool libraries. Finally, assembly and testing are performed using tools from the spare parts and tool libraries. After testing, the tools are returned to the spare parts and tool libraries, and the process is checked again to see if the requirements are met. If they are met, the repair is complete; otherwise, the process returns to the fault analysis and confirmation steps for further analysis and confirmation.

[0090] S502, determine the dynamic topology of the network based on the number of physical components constituting the target network system and the connectivity between the physical components.

[0091] The connectivity between physical components is determined by the connectivity distance and connectable physical components in the aforementioned physical component attribute information.

[0092] In this embodiment, the network topology can be represented in matrix form based on the number of physical components constituting the target network system and the connectivity between different physical components. Taking 12 different physical components as an example... Figure 7 This is a schematic diagram of a network topology provided in an embodiment of this application. Figure 7 The dynamic network topology determined by the 12 different physical components at a certain moment is a 12×12 matrix, as follows:

[0093]

[0094] Where i represents the number of the 12 physical components, j represents the number of the 12 physical components, and Q... ij (t) represents the connectivity between the i-th physical component and the j-th physical component at time t. 1 indicates that the two physical components can be directly connected, and 0 indicates that the two physical components cannot be directly connected.

[0095] S503 constructs a network system reliability model based on the integration of software and hardware, various maintenance and support strategies, and dynamic changes in topology.

[0096] In this embodiment, the constructed network system reliability model can be denoted as S(t) = F(P). ro (t),M ap (t),H tr (t),T op (t)), where P ro (t) represents the network system task description function, which describes the system task profile at time t, the time of the system task profile, each system task, and the start and end times of each system task.

[0097] M ap (t) represents the network task-structure mapping function, which is used to characterize the mapping relationship between target network system tasks, system activities / functions, logical units and physical components;

[0098] H tr (t) represents the network system maintenance and support function, which is used to characterize the maintenance and support model of each physical component in the target network system, and to determine whether the physical component is a software component or a hardware device, whether it is self-recoverable or repairable.

[0099] T op (t) represents the network system topology function, which is the representation of the network topology at time t.

[0100] The reliability model of this network system is based on the network system task description function P. ro (t) serves as a constraint, establishing a mapping function M between network tasks and structure. ap (t) During the operation of the network system, fault events are generated based on the mean time between failures (MTBF) or mean time to repair (MTTF) of the physical components of the network system. A network system maintenance support function H is constructed based on the maintenance support strategy determined by the product user (including maintenance levels, maintenance methods for different components, main maintenance activities, required maintenance tools and spare parts, etc.). tr (t), and perform the corresponding maintenance and support activities, while updating the network system topology function T. op(t), and based on the updated network system topology function T op (t) determines whether the network system can execute the task normally at the current moment.

[0101] In this embodiment, the constructed network system reliability model takes into account the relationship between network system tasks, activities / functions, and physical hardware and software components. It also comprehensively considers the impact of hardware and software failures and the dynamic changes in network connectivity caused by dynamic changes in network topology on the network system reliability model. Therefore, the network system reliability model constructed in this embodiment is more comprehensive.

[0102] See Figure 8 , Figure 8 This is a flowchart illustrating fault handling based on an occurred fault event in one embodiment. This embodiment relates to an implementation method for fault handling based on an occurred fault event. Based on the above embodiment, S103 includes:

[0103] S801, determine whether there is a redundant backup component for the available faulty physical component.

[0104] S802, if a redundant backup component exists, activate the redundant backup component for fault handling.

[0105] S803 If there are no redundant backup components, determine whether the current network topology of the target network system can meet the basic connectivity requirements for the implementation of various system activities / functions, obtain the basic connectivity requirement determination result, and perform fault handling based on the basic connectivity requirement determination result.

[0106] In this embodiment, it is determined whether there is a redundant backup component. If so, the redundant backup component is directly used to replace the faulty physical component, which can save time in handling fault events and improve the reliability of the target network system.

[0107] See Figure 9 , Figure 9 This is a flowchart illustrating fault handling based on basic connectivity requirement determination results in one embodiment. This embodiment relates to an implementation method for fault handling based on basic connectivity requirement determination results. Based on the above embodiment, S803 further includes:

[0108] S901, if the basic connectivity requirement determination result is that the basic connectivity requirement is not met, determine that the activity / function of the target network system is interrupted by a fault event, record the start time of the activity / function interruption, and record the end time of the activity / function interruption when the network topology of the target network system meets the basic connectivity requirement.

[0109] S902, if the basic connectivity requirement determination result is that the basic connectivity requirement is met, determine whether the faulty physical component affects the critical activity / function, obtain the critical activity / function determination result, and perform fault handling based on the critical activity / function determination result.

[0110] In this embodiment, key activities / functions refer to at least one critical step in completing each system task. These steps can be pre-set manually or determined by the target network system itself. This embodiment takes into account the basic connectivity requirements of the target network system, enabling a more comprehensive assessment of its reliability.

[0111] See Figure 10 , Figure 10 This is a flowchart illustrating fault handling based on the determination results of key activities / functions in one embodiment. This embodiment relates to an implementation method for fault handling based on the determination results of key activities / functions. Based on the above embodiment, S803 further includes:

[0112] S1001, if the determination result of the critical activity / function is that it does not affect the critical activity / function, record the start time of the activity / function interruption, and record the end time of the activity / function interruption when the network topology of the target network system reaches the basic connectivity requirements.

[0113] S1002, if the critical activity / function determination result is that it affects the critical activity / function, determine whether there are other physical components that can replace the function of the faulty physical component, obtain the substitutability judgment result, and perform fault handling based on the substitutability judgment result.

[0114] In this embodiment, it is determined whether the faulty physical component affects the critical activity / function. The critical activity / function is an important part of realizing a certain system task, so it is necessary to determine whether it affects the critical activity / function, which can improve the reliability of fault handling.

[0115] See Figure 11 , Figure 11 This is a flowchart illustrating fault handling based on substitutability judgment results in one embodiment. This embodiment relates to an implementation method for fault handling based on substitutability judgment results. Based on the above embodiment, S803 further includes:

[0116] S1101, if the substitutability judgment result is that there are no other physical components that can replace the function of the faulty physical component, record the start time of the activity / function interruption, and record the system activity / function recovery time when the interrupted system activity / function is restored.

[0117] S1102, if the substitutability judgment result is that there are other physical components that can replace the functions of the faulty physical component, perform system function reconstruction, and update the network topology based on the network system function reconstruction result. If the updated network topology cannot meet the basic connectivity requirements for the implementation of various system activities / functions, record the start time of the activity / function interruption, and record the end time of the activity / function interruption when the network topology of the target network system meets the basic connectivity requirements.

[0118] In this embodiment, determining whether there are any replaceable faulty physical components can save time in handling fault events and improve the reliability of the target network system.

[0119] This section describes the complete process of reliability simulation of the target network system's network system reliability model. (See [link to documentation]). Figure 12 , Figure 12 This is a flowchart illustrating a reliability simulation process provided in an embodiment of this application. Before performing the reliability simulation, various parameters in the network system reliability model and simulation parameters are defined, and the total task time T and total number of simulations N for the target network system's task profile are determined. The simulation process is as follows:

[0120] S1201, record the simulation time t and the number of simulations n, and determine the fault event.

[0121] One method for identifying fault events is to randomly determine the faulty physical components that fail during the execution of each task in the target network system according to the MTBF or MTTF of the physical components, thus forming fault events during the use of the target network system.

[0122] S1202, troubleshooting.

[0123] S1203, determine whether there is a redundant backup component for the available faulty physical component. If it exists, proceed to S1204; otherwise, proceed to S1205.

[0124] S1204, Enable redundant backup components for fault handling.

[0125] S1205, determine whether the current network topology of the target network system meets the basic connectivity requirements for the implementation of various system activities / functions. If it does, execute S1206; otherwise, execute S1210.

[0126] S1206: Determine whether the faulty physical component affects critical activities / functions. If it does not affect them, proceed to S1210; if it does affect them, proceed to S1207.

[0127] S1207: Determine if there are other physical components that can replace the function of the faulty physical component. If not, execute S1210; if so, execute S1208.

[0128] S1208, System function reconfiguration, and update the network topology based on the network system function reconfiguration results.

[0129] S1209: Determine whether the updated network topology meets the basic connectivity requirements for the implementation of various system activities / functions. If it does not meet the requirements, proceed to S1210; if it does meet the requirements, proceed to S1211.

[0130] S1210, record the start time of the activity / function interruption, and when the network topology of the target network system reaches the basic connectivity requirements, record the end time of the activity / function interruption, or when the interrupted system activity / function is restored, record the system activity / function restoration time.

[0131] S1211 checks if the simulation time t is greater than T. If it is, S1212 is executed; otherwise, S1201 is executed, and the process repeats.

[0132] S1212, count the number of interruptions for each task in this loop, as well as the normal uptime and failure time of each system activity / function.

[0133] For example, analyze whether a fault occurs in the loop that causes a system task to be interrupted. If a fault occurs that causes a system task to be interrupted, then that system task is recorded as interrupted once (each system task is counted separately); count the time during which each system activity / function cannot operate normally in the loop. (A fault occurs where there is no other self-recovery or backup equipment to directly switch over, causing a short or long interruption of system function, the time interval from the start of the fault to the recovery time), and uptime.

[0134] S1203 checks if the number of simulations n is greater than N. If it is, the simulation ends; otherwise, S1201 is executed to loop.

[0135] See Figure 13 , Figure 13 This is a flowchart illustrating a process for evaluating the reliability of a target network system based on simulation results in one embodiment. This embodiment relates to an implementation method for evaluating the reliability of a target network system based on simulation results. Based on the above embodiment, S104 includes:

[0136] S1301, count the number of interruptions for each task during the cyclic simulation process, where each task corresponds to one interruption count.

[0137] In this embodiment, the number of times each task is interrupted during n iterations of the simulation is counted.

[0138] S1302, based on the recorded start time, end time, and recovery time of the activity / function interruption, and the system activity / function recovery time, calculates the normal operation time of each function and the fault time during the cyclic simulation.

[0139] In this embodiment, the normal operation time and failure time of each activity / function are statistically analyzed during n cyclic simulations. The failure time refers to the time when the network topology of the target network system cannot meet the basic connectivity requirements or when there are no other physical components that can replace the faulty physical components, resulting in the interruption of system activities / functions.

[0140] S1303 determines the reliability of each task based on the number of interrupts for each task.

[0141] In this embodiment, the task reliability of each task is calculated using the following formula (1):

[0142]

[0143] in, Indicates system task M Sm The task reliability is given by n, where n represents the number of simulation iterations. Indicates system task M Sm The number of times the task is interrupted during n iterations of the simulation.

[0144] S1304 assesses the reliability of the target network system based on uptime, downtime, and the reliability of each task.

[0145] See Figure 14 , Figure 14 This is a flowchart illustrating the process of evaluating the reliability of a target network system in one embodiment. This embodiment relates to an implementation method for quantitatively evaluating the reliability of a target network system. Based on the above embodiment, S1304 includes:

[0146] S1401, determine the functional availability of each function of the target network system based on the ratio of normal uptime to the sum of normal uptime and downtime.

[0147] In this embodiment, the functional availability of each function is calculated using the following formula (2):

[0148]

[0149] in, Indicates system activity / function LMk Functional availability Indicates system activity / function LM k Normal uptime Indicates system activity / function LM k The downtime.

[0150] S1402, Determine the system task reliability of the target network system based on the task reliability of each task.

[0151] In this embodiment, if the system task of the target network system is a simple serial task, the system task reliability can be calculated by the following formula (3):

[0152]

[0153] Where P represents the system task reliability. Indicates system task M Sm The reliability of the task is denoted by m, where m represents the number of tasks in the system.

[0154] If the system tasks of the target network system are parallel tasks without task overlap, the system task reliability can be calculated using the following equations (4) and (5):

[0155]

[0156]

[0157] Where P represents the system task reliability. Indicates system task M Sm Task reliability, Indicates system task M Sm The weighting coefficients are the system task M. Sm The importance of the task is indicated by m, which represents the number of system tasks.

[0158] In this embodiment, the reliability of the target network system is quantitatively assessed by evaluating the functional availability of its various functions and the system task reliability, which enables a more accurate assessment of the target network system's reliability.

[0159] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0160] Based on the same inventive concept, this application also provides a simulation-based network system reliability assessment device for implementing the simulation-based network system reliability assessment method described above. The solution provided by this device is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more network system reliability assessment device embodiments provided below can be found in the limitations of the simulation-based network system reliability assessment method described above, and will not be repeated here.

[0161] Reference Figure 15 , Figure 15 This is a structural block diagram of a simulation-based network system reliability assessment device provided in this application embodiment. The device 1500 includes: a model acquisition module 1501, a parameter determination module 1502, a model simulation module 1503, and a reliability assessment module 1504, wherein:

[0162] The model acquisition module 1501 is used to acquire the network system reliability model of the target network system.

[0163] The parameter determination module 1502 is used to determine the total task time of the target network system and the task parameters of each task. The task parameters include start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, and the physical component includes hardware devices or software components.

[0164] The model simulation module 1503 is used to perform reliability simulation on the network system reliability model of the target network system and obtain simulation results. In each simulation process, the physical components that fail during the task execution of each task of the target network system are randomly identified, forming failure events during the use of the target network system. Based on the failure events, failure handling is performed and the failure handling results are recorded. The failure handling results include: failure start time, failure handling completion time, and whether the failure affects the execution of tasks of the target network system.

[0165] The reliability assessment module 1504 is used to assess the reliability of the target network system based on simulation results.

[0166] The simulation-based network system reliability assessment device provided in this embodiment acquires the network system reliability model of the target network system through a model acquisition module, and determines the total task time and task parameters of each task through a parameter determination module. The task parameters of each task include start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, which includes hardware devices or software components. The model simulation module performs reliability simulation on the network system reliability model of the target network system to obtain simulation results. The reliability assessment module assesses the reliability of the target network system based on the simulation results. Compared to the inaccurate network system reliability assessments using constructed network system models in traditional technologies, this embodiment considers both hardware devices and software components in the target network system, allowing for more accurate network system reliability assessments and solving the problem of inaccurate network system reliability assessments.

[0167] Optionally, the model simulation module 1503 includes:

[0168] Redundancy determination unit, used to determine whether there is a redundant backup unit for the available faulty physical component;

[0169] The first processing unit is used to activate the redundant backup components for fault handling if redundant backup components exist.

[0170] The second processing unit is used to determine whether the current network topology of the target network system can meet the basic connectivity requirements for the implementation of various system activities / functions if there are no redundant backup components, obtain the basic connectivity requirement determination result, and perform fault handling based on the basic connectivity requirement determination result.

[0171] Optionally, the second processing unit is also used to determine that the activity / function of the target network system is interrupted by a fault event if the basic connectivity requirement determination result is that the basic connectivity requirement is not met, record the start time of the activity / function interruption, and record the end time of the activity / function interruption when the network topology of the target network system meets the basic connectivity requirement.

[0172] If the basic connectivity requirement determination result is met, it is used to determine whether the faulty physical component affects the critical activity / function, obtain the critical activity / function determination result, and perform fault handling based on the critical activity / function determination result.

[0173] Optionally, the second processing unit is also used to record the start time of the activity / function interruption if the determination result of the critical activity / function is that it does not affect the critical activity / function, and to record the end time of the activity / function interruption when the network topology of the target network system reaches the basic connectivity requirements.

[0174] This is used to determine whether there are other physical components that can replace the faulty physical component if the determination result of the critical activity / function is that it affects the critical activity / function, obtain the substitutability judgment result, and perform fault handling based on the substitutability judgment result.

[0175] Optionally, the second processing unit is also used to record the start time of the activity / function interruption if the substitutability judgment result is that there are no other physical components that can replace the function of the faulty physical component, and to record the system activity / function recovery time when the interrupted system activity / function is restored.

[0176] If the substitutability assessment result indicates the existence of a substitute for the faulty physical component, the system function is reconfigured, and the network topology is updated based on the network system function reconfiguration result. If the updated network topology cannot meet the basic connectivity requirements for the implementation of various system activities / functions, the start time of the activity / function interruption is recorded, and the end time of the activity / function interruption is recorded when the network topology of the target network system meets the basic connectivity requirements.

[0177] Optionally, the reliability assessment module 1504 includes:

[0178] The interrupt statistics unit is used to count the number of interrupts of each task during the cyclic simulation process, where each task corresponds to one interrupt count;

[0179] The time statistics unit is used to calculate the normal operating time of each function and the fault time that cannot operate normally during the cyclic simulation based on the recorded start time, end time, and recovery time of the activity / function interruption.

[0180] The task reliability determination unit is used to determine the task reliability of each task based on the number of interruptions of each task;

[0181] The system reliability assessment unit is used to assess the reliability of the target network system based on uptime, downtime, and the reliability of each task.

[0182] Optionally, the system reliability assessment unit includes:

[0183] The Functional Availability Determination Subunit is used to determine the functional availability of each function of the target network system based on the ratio of uptime to the sum of uptime and downtime.

[0184] The task reliability determination subunit is used to determine the system task reliability of the target network system based on the task reliability of each task.

[0185] Each module in the aforementioned simulation-based network system reliability assessment device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the computer device's memory as software, so that the processor can call and execute the corresponding operations of each module.

[0186] Figure 16 This is an internal structural diagram of a computer device according to an embodiment of this application. In this embodiment, a computer device is provided, and its internal structural diagram can be as follows: Figure 16 As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a simulation-based network system reliability assessment method. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0187] Those skilled in the art will understand that Figure 16 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0188] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps of the simulation-based network system reliability assessment method provided in the above embodiments. Its implementation principle and technical effects are similar to those of the above method embodiments, and will not be repeated here.

[0189] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When executed by a processor, the computer program implements the steps of the simulation-based network system reliability assessment method provided in the above embodiments. Its implementation principle and technical effects are similar to those of the above method embodiments, and will not be repeated here.

[0190] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the simulation-based network system reliability assessment method provided in the above embodiments. Its implementation principle and technical effects are similar to those of the above method embodiments, and will not be repeated here.

[0191] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

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

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

Claims

1. A simulation-based network system reliability assessment method, characterized in that, The method includes: Obtain the network system reliability model of the target network system; the target network system is a large-scale power network system or a global transportation network system; the network system reliability model is: in, For network system task description functions, This is a function that maps network tasks to their structure. For network system maintenance and support functions, The network system topology function is used to describe the system task profile at time t, the time of the system task profile, the start and end times of each system task, the network task and structure mapping function is used to characterize the mapping relationship between the target network system tasks, system activities / functions, logical units and physical components, the network system maintenance and support function is used to characterize the maintenance and support model of each physical component in the target network system, determine whether the physical component is a software component or a hardware device, whether it is self-recoverable or repairable, and the network system topology function is used to characterize the network topology at time t. Determine the total task time of the target network system and the task parameters of each task. The task parameters include start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, and the physical component includes hardware devices or software components. A reliability simulation is performed on the network system reliability model of the target network system to obtain simulation results. In each simulation, faulty physical components that fail during the execution of each task of the target network system are randomly identified to form fault events during the use of the target network system. Based on the occurrence of the fault events, fault handling is performed and the fault handling results are recorded. The fault handling results include: fault start time, fault handling completion time, and whether the fault affects the execution of the tasks of the target network system. The reliability of the target network system is evaluated based on the simulation results. The fault handling based on the occurrence of the fault event includes: Determine if a redundant backup component for the faulty physical component is available; If redundant backup components exist, activate the redundant backup components for fault handling. If there are no redundant backup components, determine whether the current network topology of the target network system can meet the basic connectivity requirements for the implementation of various system activities / functions, obtain the basic connectivity requirement determination result, and perform fault handling based on the basic connectivity requirement determination result.

2. The method according to claim 1, characterized in that, The fault handling based on the basic connectivity requirement determination result includes: If the basic connectivity requirement determination result is that the basic connectivity requirement is not met, it is determined that the activity / function of the target network system is interrupted by a fault event, the start time of the activity / function interruption is recorded, and the end time of the activity / function interruption is recorded when the network topology of the target network system meets the basic connectivity requirement. If the basic connectivity requirement determination result is that the basic connectivity requirement is met, determine whether the faulty physical component affects the critical activity / function, obtain the critical activity / function determination result, and perform fault handling based on the critical activity / function determination result.

3. The method according to claim 2, characterized in that, The fault handling based on the key activity / function determination results includes: If the determination result of the critical activity / function is that it does not affect the critical activity / function, record the start time of the activity / function interruption, and record the end time of the activity / function interruption when the network topology of the target network system reaches the basic connectivity requirements. If the determination result of the critical activity / function is that it affects the critical activity / function, determine whether there are other physical components that can replace the function of the faulty physical component, obtain the substitutability judgment result, and perform fault handling based on the substitutability judgment result.

4. The method according to claim 3, characterized in that, The fault handling based on the substitutability determination result includes: If the substitutability determination result is that there is no other physical component that can replace the function of the faulty physical component, record the start time of the activity / function interruption, and record the system activity / function recovery time when the interrupted system activity / function is restored. If the substitutability determination result indicates the existence of other physical components that can replace the function of the faulty physical component, system function reconstruction is performed, and the network topology is updated based on the network system function reconstruction result. If the updated network topology cannot meet the basic connectivity requirements for the implementation of various system activities / functions, the start time of the activity / function interruption is recorded, and the end time of the activity / function interruption is recorded when the network topology of the target network system meets the basic connectivity requirements.

5. The method according to claim 1, characterized in that, The evaluation of the reliability of the target network system based on the simulation results includes: The number of interruptions for each task during the cyclic simulation is counted, with each task corresponding to one interruption count; Based on the recorded start time, end time, and recovery time of the activity / function interruption, the normal operating time and failure time of each function during the cyclic simulation are statistically analyzed. The reliability of each task is determined based on the number of interruptions for each task. The reliability of the target network system is evaluated based on the uptime, the downtime, and the reliability of each task.

6. The method according to claim 5, characterized in that, The step of evaluating the reliability of the target network system based on the uptime, the downtime, and the task reliability of each task includes: The functional availability of each function of the target network system is determined based on the ratio of the normal uptime to the sum of the normal uptime and the downtime. The system task reliability of the target network system is determined based on the task reliability of each task.

7. A simulation-based network system reliability assessment device, characterized in that, The device includes: The model acquisition module is used to acquire the network system reliability model of the target network system; the target network system is a large-scale power network system or a global transportation network system; the network system reliability model is: in, For network system task description functions, This is a function that maps network tasks to their structure. For network system maintenance and support functions, The network system topology function is used to describe the system task profile at time t, the time of the system task profile, the start and end times of each system task, the network task and structure mapping function is used to characterize the mapping relationship between the target network system tasks, system activities / functions, logical units and physical components, the network system maintenance and support function is used to characterize the maintenance and support model of each physical component in the target network system, determine whether the physical component is a software component or a hardware device, whether it is self-recoverable or repairable, and the network system topology function is used to characterize the network topology at time t. The parameter determination module is used to determine the total task time of the target network system and the task parameters of each task. The task parameters include start time, end time, corresponding system activity / function, and corresponding logical unit. Each logical unit corresponds to a physical component, and the physical component includes hardware devices or software components. The model simulation module is used to perform reliability simulation on the network system reliability model of the target network system and obtain simulation results. In each simulation process, the failed physical components that fail during the task execution of each task of the target network system are randomly identified, forming failure events during the use of the target network system. Based on the failure events, failure handling is performed, and the failure handling results are recorded. The failure handling results include: failure start time, failure handling completion time, and whether the failure affects the execution of the tasks of the target network system. A reliability assessment module is used to assess the reliability of the target network system based on the simulation results. The model simulation module includes: A redundancy determination unit is used to determine whether there is a redundant backup component available for the faulty physical component; The first processing unit is used to activate the redundant backup components for fault handling if redundant backup components exist. The second processing unit is used to determine whether the current network topology of the target network system can meet the basic connectivity requirements for the implementation of various system activities / functions if there are no redundant backup components, obtain the basic connectivity requirement determination result, and perform fault handling based on the basic connectivity requirement determination result.

8. The apparatus according to claim 7, characterized in that, The second processing unit is further configured to: If the basic connectivity requirement determination result is that the basic connectivity requirement is not met, it is determined that the activity / function of the target network system is interrupted by a fault event, the start time of the activity / function interruption is recorded, and the end time of the activity / function interruption is recorded when the network topology of the target network system meets the basic connectivity requirement. If the basic connectivity requirement determination result is that the basic connectivity requirement is met, determine whether the faulty physical component affects the critical activity / function, obtain the critical activity / function determination result, and perform fault handling based on the critical activity / function determination result.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images