Fault reason determination method and device and computer readable storage medium

Abstract

The invention discloses a fault cause determination method and device and a computer readable storage medium. The method relates to the field of element universe, and comprises the following steps: obtaining a fault point parameter corresponding to a fault point in equipment assembly; determining M devices corresponding to the fault point according to the fault point parameter; constructing a virtual equipment connection model according to the equipment wiring image; according to the virtual equipment connection model and the fault point parameters, determining Q fault reasons for generating the fault of the fault point and corresponding operations; and sequentially displaying operations corresponding to the Q fault causes and receiving actual detection results until the corresponding actual detection results are fault recovery, and obtaining a target fault cause. According to the method and the device, the technical problem that in the related technology, after simulation training is carried out on equipment assembly, when actual equipment assembly is carried out according to the training content, many faults still occur in the assembly process and the use process after assembly, the fault reasons are difficult to determine, and thus the faults are difficult to solve is solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of metaverse, in particular, to a fault cause determination method and device and computer readable storage medium. BACKGROUND

[0002] In related technologies, there is simulation training for device assembly, which refers to a training method that simulates and teaches the assembly process of a device in a virtual environment. This method usually relies on computer software and virtual reality (VR) technology to create highly realistic device models and assembly scenes, allowing trainees to learn and practice each step and skill of device assembly without actually touching or disassembling the device.

[0003] In simulation training, trainees can observe the internal structure of the device, understand the functions and relationships of each component, and the correct installation order and method. Through interactive operation, they can also practice specific assembly actions such as connecting cables, fixing screws, and installing modules, while avoiding risks that may be encountered in actual operation, such as damaging expensive equipment or causing personal injury. Simulation training for device assembly is widely used in various industries such as electronics manufacturing, aerospace, automotive industry, etc. It not only improves training efficiency and shortens the time for new employees to master skills, but also reduces training costs and improves operation safety and accuracy.

[0004] However, after simulation training for device assembly in related technologies, many faults still occur during assembly and use after assembly when actual device assembly is performed according to the training content, and it is difficult to determine the cause of the fault, thus making it difficult to solve the technical problem of the fault.

[0005] To address the above problems, no effective solutions have been proposed so far. SUMMARY

[0006] The embodiments of the present application provide a fault cause determination method and device and computer readable storage medium to at least solve the technical problem that after simulation training for device assembly in related technologies, many faults still occur during assembly and use after assembly when actual device assembly is performed according to the training content, and it is difficult to determine the cause of the fault, thus making it difficult to solve the fault.

[0007] According to an aspect of an embodiment of the present application, a fault cause determination method is provided, comprising: obtaining a fault point parameter corresponding to a fault point in equipment assembly; determining M devices corresponding to the fault point according to the fault point parameter, wherein the M devices are all devices having a fault probability of the fault point, and M is a positive integer greater than 1; obtaining a device wiring image corresponding to N devices, wherein N is a positive integer greater than 1, and N is less than or equal to M; constructing a virtual device connection model according to the device wiring image, wherein the virtual device connection model is used to simulate a connection relationship between the N devices; determining Q fault causes causing the fault of the fault point and simulation detection operations corresponding to the Q fault causes respectively according to the virtual device connection model and the fault point parameter, wherein Q is a positive integer greater than 1; sequentially displaying the simulation detection operations corresponding to the Q fault causes respectively, and receiving an actual detection result fed back after a target object operates according to a corresponding simulation detection operation until a corresponding actual detection result is fault recovery, and obtaining a target fault cause.

[0008] Optionally, determining Q fault causes causing the fault of the fault point and simulation detection operations corresponding to the Q fault causes respectively according to the virtual device connection model and the fault point parameter comprises: in a case where the device wiring image comprises a socket connection image between a target device socket and other device sockets, simulating a signal transmission process according to a connection relationship between the sockets in the virtual device connection model, detecting a signal transmission result, determining a fault result of whether the socket connection is faulty according to the signal transmission result, and determining the Q fault causes and the simulation detection operations corresponding to the Q fault causes respectively according to the virtual device connection model and the fault point parameter in a case where the fault result is that the socket connection is not faulty.

[0009] Optionally, after determining the fault result of whether the socket connection is faulty according to the signal transmission result, the method further comprises: in a case where the fault result is that the socket connection is faulty, obtaining a socket parameter, wherein the socket parameter comprises at least one of the following: a disabled socket connection detection parameter, and a wiring type parameter between an enabled socket and the disabled socket; and determining the target fault cause according to the socket parameter.

[0010] Optionally, the simulation detection operations corresponding to the Q fault causes are displayed in sequence, and actual detection results fed back by the target object after performing operations according to the corresponding simulation detection operations are received until the corresponding actual detection result is fault recovery, and the target fault cause is obtained, including: determining a generation probability corresponding to each of the Q fault causes and a convenience index corresponding to each of the Q simulation detection operations; determining a first priority corresponding to each of the Q fault causes according to the generation probability corresponding to each of the Q fault causes, and determining a second priority corresponding to each of the Q simulation detection operations according to the convenience index corresponding to each of the Q simulation detection operations; determining a target priority according to the first priority and the second priority; and displaying the simulation detection operations corresponding to the Q fault causes in sequence according to the order of the target priority, and receiving actual detection results fed back by the target object after performing operations according to the corresponding simulation detection operations until the corresponding actual detection result is fault recovery, and obtaining the target fault cause.

[0011] Optionally, after the virtual device connection model is constructed according to the device connection image, the method further includes: obtaining a correct connection of a device connection type corresponding to the N devices; determining a consistency result of whether the current connection is consistent with the correct connection; in the case that the consistency result is inconsistent, determining that the target fault cause is a connection error, and calibrating the connection in the virtual device connection model according to the correct connection to obtain a calibrated connection, and displaying the calibrated connection.

[0012] Optionally, after the simulation detection operations corresponding to the Q fault causes are displayed in sequence, and actual detection results fed back by the target object after performing operations according to the corresponding simulation detection operations are received until the corresponding actual detection result is fault recovery, and the target fault cause is obtained, the method further includes: determining a target service performed by the target object and an unused socket corresponding to the N devices; determining an auxiliary function provided by the unused socket for the target service; determining an auxiliary connection parameter corresponding to the unused socket according to the auxiliary function, so as to connect the auxiliary function provided for the target service according to the auxiliary connection parameter.

[0013] Optionally, the virtual device connection model is constructed according to the device connection image, including: constructing an initial device connection model according to the device connection image; receiving a correction operation sent by the target object; and calibrating the initial device connection model according to the correction operation to obtain the virtual device connection model.

[0014] According to an aspect of an embodiment of the present application, there is provided a fault cause determining apparatus, comprising: a receiving module configured to acquire a fault point parameter corresponding to a fault point in equipment assembly; a first determining module configured to determine M devices corresponding to the fault point according to the fault point parameter, wherein the M devices are all devices having a fault probability of the fault point, and M is a positive integer greater than 1; an acquiring module configured to acquire device connection images corresponding to N devices, wherein N is a positive integer greater than 1, and N is less than or equal to M; a constructing module configured to construct a virtual device connection model according to the device connection images, wherein the virtual device connection model is used to simulate a connection relationship between the N devices; a second determining module configured to determine Q fault causes causing the fault of the fault point and simulation detection operations corresponding to the Q fault causes respectively according to the virtual device connection model and the fault point parameter, wherein Q is a positive integer greater than 1; and a third determining module configured to display the simulation detection operations corresponding to the Q fault causes respectively in sequence, and receive actual detection results fed back after a target object operates according to corresponding simulation detection operations until corresponding actual detection results are fault recovery, and obtain a target fault cause.

[0015] According to an aspect of an embodiment of the present application, there is provided a computer readable storage medium comprising a stored executable program, wherein the computer readable storage medium controls a device where the computer readable storage medium is located to execute any of the above methods when the executable program is run.

[0016] According to an aspect of an embodiment of the present application, there is provided an electronic device comprising: a memory storing an executable program; and a processor configured to run the program, wherein the program executes any of the above methods when run.

[0017] According to an aspect of an embodiment of the present application, there is provided a computer program product comprising computer instructions, wherein the computer instructions are executed by a processor to implement steps of any of the above methods.

[0018] In the embodiment of the present application, the fault point parameters corresponding to the fault point in the equipment assembly are acquired; M devices corresponding to the fault point are determined according to the fault point parameters, wherein the M devices are all devices that cause the fault probability of the fault point, and M is a positive integer greater than 1; the device wiring images corresponding to N devices are acquired, wherein N is a positive integer greater than 1, and N is less than or equal to M; the virtual device connection model is constructed according to the device wiring images, wherein the virtual device connection model is used to simulate the connection relationship between the N devices; Q fault reasons causing the fault of the fault point and the simulation detection operations corresponding to the Q fault reasons are determined according to the virtual device connection model and the fault point parameters; the simulation detection operations corresponding to the Q fault reasons are displayed in sequence, and the actual detection results fed back after the target object operates according to the corresponding simulation detection operation are received until the corresponding actual detection result is fault recovery, and the target fault reason is obtained. It can be known that, by acquiring the fault point parameters, the M potential fault devices are accurately identified, the virtual model is constructed by using the wiring images of the N devices to simulate the real connection state. In combination with the model and the parameters, the Q fault reasons are intelligently analyzed, the simulation detection process is designed in a targeted manner, the user is guided to gradually troubleshoot and repair, until the fault is eliminated, the efficiency and accuracy of the fault diagnosis and solution after the equipment assembly are significantly improved, the limitations of the traditional simulation training ignoring the actual fault processing are overcome, and thus the technical problem that after the simulation training is performed on the equipment assembly in the related art, many faults still occur in the assembly and the use process after the assembly when the actual equipment assembly is performed according to the training content, and the fault reasons are difficult to determine, so that the faults are difficult to solve. BRIEF DESCRIPTION OF DRAWINGS

[0019] The drawings described herein are used to provide further understanding of the present application, constitute a part of the present application, and the illustrative embodiments of the present application and the description thereof are used to explain the present application, and do not constitute an improper limitation on the present application. In the drawings:

[0020] Figure 1 It is a flowchart of a fault reason determination method according to an embodiment of the present application;

[0021] Figure 2 It is a structural block diagram of a fault reason determination device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order for the personnel in the technical field to better understand the present application scheme, the technical solutions in the embodiments of the present application will be clearly and completely described below in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by the personnel in the field without making creative efforts should belong to the protection scope of the present application.

[0023] It is to be understood that the terminology "first", "second", and the like used in the specification and the claims of the application as well as the foregoing drawings is merely used to distinguish similar objects and does not necessarily imply a specific order or chronology. It is to be understood that the use of the terms first, second, and the like in the description is merely to distinguish between two separate objects that can have the same or similar characteristics or functions. It is to be understood that the data thus used can be interchanged, where appropriate, so that the embodiments of the application described herein can be carried out in other than the order shown or described herein. Furthermore, the terms "comprise" and "have" and any variations thereof are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or apparatus that comprises a list of steps or units is not necessarily limited to those steps or units that are clearly listed, but can include other steps or units that are not clearly listed or inherent to such processes, methods, products, or apparatuses.

[0024] It should be noted that the information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for display, analyzed data, etc.) involved in the present application are information and data authorized by the user or authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of related data comply with relevant laws, regulations and standards, necessary security measures are taken, do not violate public order and good customs, and provide corresponding operation portal for user to choose authorization or refusal. For example, interfaces are provided between the system and related users or institutions to provide corresponding operation portals for users to choose to agree or refuse automatic decision results; if the user chooses to refuse, the expert decision process is entered.

[0025] Embodiment 1

[0026] According to the embodiments of the present application, an embodiment of a fault cause determination method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown herein.

[0027] Figure 1 is a flowchart of a fault cause determination method according to an embodiment of the present application, as shown in Figure 1 The method comprises the following steps:

[0028] Step S102, obtaining fault point parameters corresponding to the fault point in the equipment assembly;

[0029] In the present application, the fault point parameters corresponding to the fault point in the equipment assembly are obtained in step S102.

[0030] Among them, it involves device assembly, which refers to the activity of combining multiple hardware components (such as server motherboard, hard disk, memory bar, etc.) into a functional complete system according to a specific order and way. In the IT industry, device assembly is often used to build servers, workstations or personal computers, etc.

[0031] Among them, it involves fault points, which are any links in the device assembly process that may cause the device to run abnormally or fail to start normally. This may include hardware compatibility problems, improper cable connection, driver errors, insufficient power supply, etc.

[0032] Among them, it involves fault point parameters, which are specific numerical values or state information that can describe the characteristics of fault points. For example, if the fault point is the incorrect installation of a memory bar, the fault point parameters may include the model of the memory bar, the slot position, the voltage setting, the frequency setting, etc.; if it is insufficient power supply, the parameters may include power output, current intensity, voltage level, etc.

[0033] When the system detects that a certain link in the device assembly process may have a fault, the next step is to obtain the fault point parameters corresponding to this fault point. This means that the system needs to identify the specific location and nature of the fault, and collect detailed information related to the fault, which may come from device specifications, assembly records, sensor data or user reports, etc.

[0034] Step S104, according to the fault point parameters, determine M devices corresponding to the fault point, wherein the M devices are all devices that exist to cause the fault probability of the fault point, and M is a positive integer greater than 1;

[0035] In step S104 provided in the present application, M devices corresponding to the fault point are determined according to the fault point parameters.

[0036] Among them, it involves M devices, which refers to the set of all potentially associated devices involved in diagnosing the fault point, and M is a positive integer representing the number of devices in the set. These devices may be the direct cause of the fault, or they may be affected by the fault or indirectly related to the fault.

[0037] Among them, it involves fault probability, which exists to cause the fault probability of the fault point, which means that these devices have a certain probability of being the source of the fault. This "probability" is based on historical data, device characteristics, environmental conditions and other factors to quantify the relevance of each device to the current fault.

[0038] In the process of equipment assembly or maintenance, once a fault is found somewhere, the system can determine a series (denoted as M) of possible devices that have faults or cause faults according to the obtained fault point parameters. This process is not simply fault location, but through in-depth analysis of fault point parameters, combined with the interaction and dependency relationship between devices, all devices that may affect the state of the fault point are inferred. For example, if the fault point parameter indicates that the server cannot start, and the system monitors that the power supply voltage is unstable, the system may determine the power adapter, UPS uninterruptible power supply, power circuit module on the server mainboard, etc. as the M group of devices, because these devices have a certain probability to cause power instability, and then affect the start of the server.

[0039] In step S106, device wiring images corresponding to N devices are obtained, where N is a positive integer greater than 1, and N is less than or equal to M.

[0040] In the step S106 provided in the present application, the device wiring images corresponding to the N devices are obtained.

[0041] Among them, N devices are involved, and in this embodiment, N represents the number of devices that need to be checked for wiring conditions from the M devices, because the user may only involve N devices during installation. That is, the fault may be caused by the above-mentioned M devices, but the user only has N devices on site, so only the device wiring images corresponding to the N devices need to be determined, N is a positive integer, and N≤M, which means that the focus is on those devices that are most likely to cause faults due to wiring problems.

[0042] Among them, the device wiring image is involved, which is an image or video obtained by a camera, scanner or other image acquisition device, showing the wiring condition of the N devices. These images can clearly show the wiring state of each port and interface of the device, including whether the cable is correctly inserted, whether it is loose, whether it is misconnected, and other details. Once the wiring error is found, it can be corrected in time, greatly shortening the fault recovery time.

[0043] After the device malfunctions, M devices that may have faults have been determined by the fault point parameters. However, considering that many common faults are caused by wiring errors, the next focus will be on N (N < M) devices that are more likely to malfunction due to wiring problems, and their wiring images will be obtained. The purpose of this process is to visually check the physical connection state of these devices, confirm whether the cables are correctly connected, whether the interfaces are in good contact, whether there are loose or damaged situations, etc. For example, when a server encounters a startup difficulty problem, it may initially judge that the memory stick, power supply unit, motherboard, etc. are the main fault points (M group of devices). But if historical data analysis shows that more than 80% of the startup problems are caused by wiring errors, then the power cord, hard disk data cable, fan cable, etc. (N group of devices) may be focused on, and the connection state is verified through the device wiring image.

[0044] In step S108, a virtual device connection model is constructed according to the device wiring image, wherein the virtual device connection model is used to simulate the connection relationship between the N devices;

[0045] In the present application, in step S108, a virtual device connection model is constructed according to the device wiring image.

[0046] Among them, the virtual device connection model is a 3D model of the simulated device and its connection relationship constructed in the virtual reality (VR) or augmented reality (AR) environment according to the device wiring image. This model contains the connection mode and state between devices.

[0047] After obtaining the wiring images of the N devices in the device maintenance or troubleshooting stage, the next step is to construct a virtual device connection model. This process involves converting the wiring images in reality into a 3D model in a virtual environment, which can accurately display the connection mode and relationship between the N devices, including the direction of the cable, the pairing of the interface, the correctness of the plug, etc. For example, if it is detected that the startup failure of the server may be related to the wiring, first check whether the key cables such as power cord, network cable, hard disk data cable, etc. are incorrectly connected or loose through the wiring image. Then, input these image information into the virtual model construction system to generate a virtual model simulating the connection of the server and its surrounding devices. In this model, users can perform interactive checks, simulate plugging and unplugging cables, adjust interface positions, etc. to further verify whether the wiring state is correct.

[0048] The virtual device connection model presents the complex wiring relationship in a 3D way, allowing users to observe and understand the connection between devices from any angle, greatly enhancing the intuitiveness of troubleshooting. And in the virtual environment, users can safely simulate various wiring operations without worrying about physical damage to the real devices, reducing the risk in the troubleshooting and repair process.

[0049] Step S110, according to the virtual device connection model and the fault point parameters, determine Q fault causes of the fault point failure, and the simulation detection operation corresponding to each of the Q fault causes;

[0050] In step S110 provided in the present application, Q fault causes of the fault point failure are determined, and simulation detection operations corresponding to each of the Q fault causes.

[0051] Wherein, Q fault causes are involved, here Q represents the number of possible fault causes determined after analyzing the virtual device connection model and the fault point parameters, Q is a positive integer greater than 0, representing the number of potential fault points identified by the system, and each fault cause is associated with a specific device or connection state.

[0052] Wherein, simulation detection operations are involved, which are virtual tests or diagnostic steps designed and implemented for each determined fault cause. These operations can be safely performed in a virtual environment to verify the correctness of the fault cause and provide guidance for troubleshooting.

[0053] In the process of troubleshooting, a virtual device connection model is first constructed, and then the fault is analyzed in combination with the fault point parameters. The next step is to determine Q possible causes of the fault point failure according to the virtual device connection model and the fault point parameters, and to design corresponding simulation detection operations for each fault cause. This means that not only can the possible source of the fault be identified, but also these hypotheses can be verified through simulation testing in a virtual environment, while providing specific operation guidelines to help users locate and solve the fault. For example, when a server fails to start, the virtual device connection model shows that the power cord is connected normally, but the fault point parameters show that the power voltage is unstable. The system may determine possible Q fault causes such as power adapter failure (Q1), internal short circuit of power cord (Q2), and server mainboard power circuit failure (Q3). For each fault cause, the system will propose simulation detection operation suggestions, such as simulating the replacement of the power adapter in the virtual environment (for Q1), checking the signal transmission of the power cord (for Q2), or testing the voltage regulation module on the mainboard (for Q3).

[0054] Through the analysis of Q fault causes, the problem can be more accurately located, avoiding blind troubleshooting and saving time and cost. The specific detection operation corresponding to each fault cause provides a clear troubleshooting path and solution for users, enhancing maintenance efficiency.

[0055] Step S112, display the simulation detection operation corresponding to each of the Q fault causes in turn, and receive the actual detection result fed back by the target object after performing the operation according to the corresponding simulation detection operation, until the corresponding actual detection result is fault recovery, and the target fault cause is obtained.

[0056] In step S112 provided in the present application, the process of determining the fault cause is explained.

[0057] Among them, the target object is involved, which is responsible for performing operations in the virtual environment according to the simulation detection operation and feeding back the actual detection result, which can be a user or a student.

[0058] Among them, the actual detection result is involved, which is the result fed back by the target object after performing the corresponding test or operation in the virtual environment according to the simulation detection operation. It can be the change of the device state, the disappearance of the fault phenomenon or other forms of response, which is used to verify whether the hypothesis of the fault cause is correct.

[0059] Among them, the fault recovery is involved, which means that the fault of the device is successfully repaired and returns to the normal operation state through the execution of the corresponding detection operation and solution. Therefore, the fault cause corresponding to the fault recovery is the target fault cause. The target fault cause is the one that is finally determined and really causes the fault after a series of simulation detection operations.

[0060] In the troubleshooting stage, instead of relying on theoretical analysis, the fault cause is verified through actual operation in the virtual environment. The system will display the simulation detection operation instructions corresponding to the Q fault causes to the target object in turn. The target object will follow these operation instructions to perform each test in the virtual device connection model, such as simulating the replacement of the power adapter, resetting the network configuration, checking the installation state of the memory bar, etc. After each operation, the target object will feed back the actual detection result, and the system will judge whether the expected fault recovery state is reached. If the detection result shows that the fault still exists, the system will continue to display the corresponding operation of the next fault cause until the operation that can make the device return to normal operation is found, so as to determine the target fault cause. For example, if the server fails to start, the system first displays the simulation operation of replacing the power adapter, and the target object feeds back that the fault is not solved after performing the operation in the virtual environment. Then, the system displays the instruction of reconfiguring the network settings, and the execution still does not improve. Finally, when the target object checks and re-installs the memory bar according to the instruction, the feedback shows that the server starts normally, so it can be determined that the memory bar installation problem is the target fault cause.

[0061] By the above steps S102-S112, the fault point parameters corresponding to the fault point in the equipment assembly are obtained; according to the fault point parameters, M devices corresponding to the fault point are determined, wherein the M devices are all devices that exist to cause the fault probability of the fault point, and M is a positive integer greater than 1; the device wiring image corresponding to N devices is obtained, wherein N is a positive integer greater than 1, and N is less than or equal to M; according to the device wiring image, a virtual device connection model is constructed, wherein the virtual device connection model is used to simulate the connection relationship between the N devices; according to the virtual device connection model and the fault point parameters, Q fault reasons causing the fault of the fault point and simulation detection operations corresponding to the Q fault reasons are determined; the simulation detection operations corresponding to the Q fault reasons are displayed in turn, and the actual detection results fed back by the target object after operating according to the corresponding simulation detection operation are received until the corresponding actual detection result is fault recovery, and the target fault reason is obtained. It can be known that, by obtaining the fault point parameters, the M potential fault devices are accurately identified, the virtual model is constructed by using the wiring image of the N devices to simulate the real connection state. In combination with the model and the parameters, the Q fault reasons are intelligently analyzed, the simulation detection process is designed in a targeted manner, the user is guided to gradually investigate and repair, until the fault is eliminated, the efficiency and accuracy of the fault diagnosis and solution after the equipment assembly are significantly improved, the limitations of the traditional simulation training ignoring the actual fault handling are overcome, and thus the technical problem that after the simulation training is performed on the equipment assembly in the related art, many faults still occur in the assembly and the use process after the assembly according to the training content, and it is difficult to determine the fault reasons, so that it is difficult to solve the faults is solved.

[0062] As an optional embodiment, according to the virtual device connection model and the fault point parameters, Q fault reasons causing the fault of the fault point and simulation detection operations corresponding to the Q fault reasons are determined, including: in the case that the device wiring image includes the socket connection image between the target device socket and other device sockets, according to the connection relationship between the sockets in the virtual device connection model, the signal transmission process is simulated, and the signal transmission result is detected; according to the signal transmission result, the fault result of whether the socket connection is faulty is determined; in the case that the fault result is that the socket connection is not faulty, according to the virtual device connection model and the fault point parameters, the Q fault reasons are determined, and the simulation detection operations corresponding to the Q fault reasons are determined.

[0063] In this embodiment, the process of determining the fault by simulating the signal transmission is illustrated.

[0064] Among them, the socket connection image refers to the connection state picture between the device socket and other device sockets in the device wiring image, which is used to accurately display the connection mode of the signal cable.

[0065] The signal transmission process is a process of transmitting data or instructions between devices, and through the simulation of signal transmission, the correctness and integrity of data transmission can be checked.

[0066] The fault result is a result obtained from the signal transmission result after the simulation detection operation, and is used to determine whether the connection state of the device socket is normal and whether this state is the fault cause of the current fault point.

[0067] In troubleshooting, especially when dealing with complex faults involving multi-device signal transmission, the virtual device connection model and fault point parameters are first used to determine potential fault causes. When the device wiring image contains a specific socket connection image, the system uses the connection relationship between the sockets in the virtual model to simulate the transmission process of signals between these sockets and detect the signal transmission result to check whether there is any signal transmission anomaly. If the signal transmission result indicates that the socket connection is normal, i.e., the socket connection is not faulty, the system will further determine deeper fault causes based on the virtual model and other parameters of the fault point, and design simulation detection operations for each possible fault cause. For example, if a server cannot communicate with other devices through the network, the system first checks the connection image of the network socket, simulates the transmission of network signals, and detects whether data packets can be normally transmitted and received. If the detection result shows that the network signal transmission is correct, i.e., the socket connection is not faulty, the system will analyze possible Q fault causes, such as server software configuration errors, improper network device settings, and hardware faults, and design corresponding simulation tests for each cause, such as simulating network settings replacement and detecting hardware status.

[0068] Through signal transmission simulation and detection, the socket connection state can be accurately determined, non-connection class faults can be ruled out, and deeper problems can be focused on, thereby improving the efficiency and accuracy of troubleshooting. Performing signal transmission and other operation tests in a virtual environment avoids the risk of physical damage to real devices.

[0069] As an optional embodiment, after determining whether the socket connection is faulty based on the signal transmission result, the fault result also includes: in the case where the fault result is a faulty socket connection, obtaining socket parameters, wherein the socket parameters include at least one of the following: a disabled socket connection detection parameter, a wiring type parameter between enabled sockets and disabled sockets; determining a target fault cause based on the socket parameters.

[0070] In this embodiment, the step of determining the target fault cause based on the socket parameters is described.

[0071] Among them, it involves the socket connection failure, which is to judge the abnormal connection between the device sockets according to the signal transmission result, which may include socket physical damage, signal interference, unstable connection, etc.

[0072] Among them, it involves the socket parameters, which are further collected detailed information directly related to socket fault diagnosis, which may include whether the socket is enabled, the type of socket and cable, the model of the line, etc.

[0073] Among them, it involves the non-enabled socket connection detection parameter, which can be detected in the virtual model whether the socket is set to "non-enabled" state, that is, the socket is not activated and cannot normally transmit signals.

[0074] Among them, it involves the wiring model parameter between enabled and non-enabled sockets, that is, in the device wiring, the type and model of the cable connecting the "enabled" socket and the "non-enabled" socket, which may affect the correctness and stability of signal transmission.

[0075] Among them, it involves the target fault cause in the scenario of socket connection failure, which is the specific reason most likely to cause the current fault determined by socket parameter analysis.

[0076] When the signal transmission result indicates that the socket connection has a fault, the system will further obtain the socket parameters to more accurately locate the fault cause. These parameters may reveal whether the socket is correctly enabled, and whether the cable model used between the enabled and non-enabled sockets is matched, and then judge whether the socket connection failure is caused by hardware damage, software configuration error, cable incompatibility, etc. Specifically, if it is detected that the socket is in the "non-enabled" state, the fault cause may be related to configuration or software problems; if the cable model between the socket and the socket is not matched, the improper hardware selection or wiring method may be the key to causing the fault. For example, when a network device cannot communicate normally, if the signal transmission result shows that the signal transmission of the network socket is abnormal, the system will check the parameters of these sockets, such as whether they are correctly enabled by software, and whether the cable connecting these sockets meets the standard (such as using an old model cable that does not support high-speed transmission to connect a high-speed socket). These detailed information will help determine the target fault cause and guide the subsequent fault solving steps, such as repairing software configuration, replacing cable, etc.

[0077] In-depth analysis using socket parameters can more accurately identify the source of the fault, avoid blind troubleshooting, and improve the efficiency of fault resolution. The determined target fault cause can directly guide specific repair measures, such as replacing cables, adjusting software configurations, to ensure that the fault is fundamentally solved.

[0078] As an optional embodiment, the simulation detection operations corresponding to the Q fault causes are displayed in sequence, and the actual detection results fed back by the target object after operating according to the corresponding simulation detection operation are received until the corresponding actual detection result is fault recovery, and the target fault cause is obtained, comprising: determining the generation probability corresponding to the Q fault causes and the convenience index corresponding to the Q simulation detection operations; determining the first priority corresponding to the Q fault causes according to the generation probability corresponding to the Q fault causes, and determining the second priority corresponding to the Q simulation detection operations according to the convenience index corresponding to the Q simulation detection operations; determining the target priority according to the first priority and the second priority; and displaying the simulation detection operations corresponding to the Q fault causes in sequence according to the order of the target priority, and receiving the actual detection results fed back by the target object after operating according to the corresponding simulation detection operation until the corresponding actual detection result is fault recovery, and obtaining the target fault cause.

[0079] In this embodiment, the order of determining the priority is explained to determine the target fault cause in sequence.

[0080] Among them, the generation probability is involved, that is, the possibility of each fault cause occurring and causing equipment failure, which is obtained based on historical data statistics or fault point parameter analysis.

[0081] Among them, the convenience index is involved, which represents the difficulty and efficiency of executing the simulation detection operation, considering factors such as operation complexity, time consumption, and required resources.

[0082] Among them, the first priority is involved, which is the priority processing order determined according to the generation probability of the fault cause. The fault cause with high probability has higher priority.

[0083] Among them, the second priority is involved, which is the execution order determined based on the convenience index of the simulation detection operation. The higher the convenience index, the simpler and faster the operation, and the higher the priority.

[0084] Among them, the target priority is involved, which is the final fault troubleshooting operation sequence determined by combining the first priority and the second priority, aiming to solve the problem in the most efficient way.

[0085] In order to improve the troubleshooting efficiency, the system analyzes Q possible causes of the fault based on the fault point parameters when troubleshooting the equipment. Each cause is assigned a probability of occurrence. At the same time, the system also designs corresponding simulation detection operations for each fault cause and evaluates the convenience index of these operations, i.e. the difficulty and efficiency of execution. The system then determines the first priority based on the probability of occurrence and the second priority based on the convenience index, and combines the two priorities to form a target priority, i.e. an optimized fault detection operation sequence. According to this sequence, the system displays the simulation detection operations to the target object (usually maintenance personnel or an automated detection system) in turn, and the target object executes the operations according to the instructions and feeds back the actual detection results of each operation. The system continues to monitor until the fault recovery result is detected, thereby determining the target fault cause, i.e. the cause that actually caused the fault.

[0086] Through priority ranking, the most likely fault cause detection is performed first, avoiding ineffective or inefficient troubleshooting steps and significantly improving fault resolution speed. The consideration of convenience index ensures that simple and fast operations are prioritized under limited resources, reducing resource waste and optimizing fault troubleshooting cost. The fault troubleshooting strategy is based on data analysis and intelligent algorithms, reducing the uncertainty of human judgment and improving the accuracy of fault diagnosis.

[0087] As an optional embodiment, after constructing the virtual equipment connection model based on the equipment connection image, the method further includes: obtaining correct connections of equipment connection types corresponding to N equipment; determining a consistency result of whether the current connection is consistent with the correct connection; in the case that the consistency result is inconsistent, determining the target fault cause as a connection error, and calibrating the connection in the virtual equipment connection model according to the correct connection to obtain a calibrated connection, and displaying the calibrated connection.

[0088] In this embodiment, the step of determining the fault cause by calibrating the connection is explained.

[0089] Among them, the equipment connection type refers to the type of connection cable between equipment, such as network cable, power cable, data cable, etc., different cables have different functions and connection standards.

[0090] Among them, the correct connection refers to the correct connection method between equipment according to the design specifications and standard operating procedures of the equipment, including the type of cable and the position of connection.

[0091] Among them, the consistency result is the comparison result between the current actual connection state of the equipment and the correct connection standard, which is used to judge whether there is a connection error.

[0092] Among them, it involves the connection error, such as the cable connection between the devices does not meet the design specification or standard operating procedure, which may be the wrong cable type, improper connection position or cable damage, etc.

[0093] Among them, it involves the calibration connection, that is, after finding the connection error, the connection state of the connection in the virtual device connection model is corrected according to the correct connection standard.

[0094] After the virtual device connection model is constructed, the next step is to check the connection state in the model to ensure that they meet the correct device connection type. This process includes obtaining the standard connection type of N devices, and then comparing the current connection state in the virtual model to obtain consistency results through analysis. If the consistency result shows that the current connection is inconsistent with the correct connection, that is, there is a connection error, the system will automatically locate the target fault cause as the connection error. At this time, the system will further adjust the connection in the virtual model according to the correct device connection type, obtain the calibration connection, and display the connection state after calibration on the interface to guide the user to correct the connection of the real device. For example, if in the virtual model, it is found that a server is connected to a switch using an incorrect type of network cable, the consistency result will point out this problem. The system will immediately calibrate the connection in the model according to the correct device connection type, that is, Cat6 network cable should be used, and display the correct connection method on the interface in a prominent way to prompt the user to replace the cable on the real device to match the calibration connection, thereby solving the fault caused by the connection error.

[0095] Through the comparison of the consistency result, the connection error can be quickly identified, and unnecessary fault diagnosis time caused by the connection problem is avoided. The calibration connection is displayed intuitively in the virtual model, and the user can see the correct connection state at a glance, which is convenient for quick correction. The connection calibration ensures the correct data flow transmission between devices and prevents potential secondary faults caused by incorrect connection.

[0096] As an optional embodiment, the simulation detection operation corresponding to each of the Q fault causes is displayed in sequence, and the actual detection result fed back after the target object is operated according to the corresponding simulation detection operation is received, until the corresponding actual detection result is fault recovery, and the target fault cause is obtained, further comprising: determining the target business executed by the target object, and the unused socket corresponding to the N devices; determining the auxiliary function provided by the unused socket for the target business; determining the auxiliary connection parameter corresponding to the unused socket according to the auxiliary function, so as to connect the auxiliary function for the target business according to the auxiliary connection parameter.

[0097] In this embodiment, it is explained that the auxiliary function is connected for the target business according to the auxiliary connection parameter.

[0098] Among them, the target business is related to the main task or function that the target object needs to perform after the device failure recovery, such as data transmission, online service, network monitoring, etc.

[0099] Among them, the unused socket is related to the socket that is currently not connected to the cable or device among the N devices, but may provide additional functions or services.

[0100] Among them, the auxiliary function is related to some additional or supporting functions that the unused socket can provide for the current target business, such as backup power supply, high-speed data transmission, fault monitoring, etc.

[0101] Among them, the auxiliary connection parameter is related to the specific operation guide that describes how to use the unused socket to achieve the auxiliary function, including cable type, socket number, connection sequence, etc.

[0102] After troubleshooting is completed, when the target object has successfully located and solved the fault, the device returns to normal operation, the system will further focus on the optimization and expansion of the target business. This step involves analyzing the unused sockets on the N devices to determine which auxiliary functions they can provide for the current target business. By tapping the potential of these sockets, the system can guide the target object on how to correctly connect these sockets to maximize their effectiveness and provide more comprehensive support for business operation. For example, assuming that the target business is data processing of a server cluster, the system will identify the unused high-speed data port on the server and determine that it can be used as a high-speed data channel within the cluster to improve processing efficiency. Subsequently, the system will provide auxiliary connection parameters, such as recommending the use of a fiber optic cable to connect to a specific number of high-speed data ports to achieve the best data transmission rate.

[0103] By fully utilizing the unused sockets of the device, additional auxiliary functions are provided for the target business, enhancing business processing capacity and stability. Guide users to reasonably configure unused resources, avoid idle device capacity, maximize hardware investment return.

[0104] As an optional embodiment, a virtual device connection model is constructed according to the device wiring image, including: constructing an initial device connection model according to the device wiring image; receiving a correction operation sent by the target object; calibrating the initial device connection model according to the correction operation to obtain the virtual device connection model.

[0105] In this embodiment, the process of calibrating the virtual device connection model is described.

[0106] Among them, the initial device connection model is related to the virtual model initially constructed according to the device wiring image, used to simulate the connection relationship between devices and data flow transmission.

[0107] Among them, the correction operation is a correction instruction provided by the target object after viewing the initial device connection model, finding that it does not conform to the actual situation or has optimization space, and is used to adjust the model.

[0108] Among them, the virtual device connection model is the device connection model optimized by the correction operation, which more accurately reflects the actual connection state of the device and is the basis for subsequent fault diagnosis and business optimization.

[0109] The process of constructing the virtual device connection model starts with the analysis of the device wiring image to form an initial model that reflects the device connection state. However, due to the limitations of image analysis or changes in the device environment, this initial model may not be completely accurate or deviate from the actual situation. At this time, the target object needs to intervene to correct the model, that is, to adjust or optimize the connection relationship in the model by sending correction operations. The system will update the model according to these correction operations to ensure the consistency of the model with the actual device connection state. After correction and optimization, a more accurate virtual device connection model is formed, providing a solid foundation for subsequent fault diagnosis, business optimization, and resource utilization.

[0110] Through the correction operation, the inaccuracy of the model caused by image analysis error can be reduced, and the practicability of the model can be improved. A more accurate model helps to more accurately locate the fault point and improve the efficiency of fault troubleshooting and repair.

[0111] Based on the above embodiments and optional embodiments, an optional implementation is provided, which is described in detail as follows.

[0112] The present application provides a fault cause determination method in the optional implementation. The following is an introduction:

[0113] S1, obtaining a fault point parameter corresponding to a fault point in device assembly;

[0114] S2, determining M devices corresponding to the fault point according to the fault point parameter;

[0115] At this time, the fault scene can be captured, and the fault device that may cause the fault, such as in the scene of connecting a computer to use the computer, the connection has been completed, but the computer cannot be opened.

[0116] S2, automatically identifying the fault device in the fault scene, and obtaining device wiring images corresponding to N devices;

[0117] For example, in the above scene, the fault device is the computer, the host, the network cable, the router and other related devices.

[0118] S3, constructing a virtual device connection model according to the device wiring image;

[0119] Optionally, the fault model of the fault device can be determined, and in the case where the specific model cannot be determined, a general model or a standard model can be used to determine the virtual three-dimensional fault device; the connection relationship between the virtual three-dimensional fault devices is determined;

[0120] S5, determining Q fault causes of the fault point according to the virtual device connection model and the fault point parameters, and simulation detection operations corresponding to the Q fault causes, respectively;

[0121] Optionally, the possible fault points can be determined through the virtual three-dimensional fault device and the connection relationship therebetween.

[0122] S6, sequentially displaying the simulation detection operations corresponding to the Q fault causes, respectively, and receiving actual detection results fed back after a target object operates according to the corresponding simulation detection operation, until the corresponding actual detection result is fault recovery, and obtaining the target fault cause.

[0123] Optionally, the fault causes can be listed with priorities, and test methods and solutions can be given.

[0124] For example, the first priority is a connection line error or a lack of line connection. At this time, the correct connection method of the line between the three-dimensional devices will be guided. For example, the second priority is that the network interface is not available. At this time, the three-dimensional devices will guide whether the network interface is available. It should be noted that when the general or standard model device is used, special precautions for using some special model devices can be marked beside the device.

[0125] When there are many sockets, such as multiple sockets behind the host, the system can actively analyze the functions corresponding to the sockets in order to guide the subsequent test methods and solutions. If the virtual three-dimensional fault device determined has unnecessary or inconsistent sockets, the user can delete and add sockets on the model to maintain consistency with the real scene.

[0126] For example, the general socket behind the host usually has the following several sockets:

[0127] 1. Power socket: a socket for connecting the host and the power supply.

[0128] 2. Display interface: an interface for connecting a display.

[0129] 3. USB interface: an interface for connecting external devices, which can connect a mouse, a keyboard, a printer, etc.

[0130] 4. Network interface: an interface for connecting a network, which usually has an Ethernet interface.

[0131] 5. Audio interface: interface for connecting audio devices, including microphone and earphone interfaces.

[0132] 6. Expansion slot: slot for inserting expansion cards, such as graphics cards, sound cards, etc.

[0133] The function of these sockets is to connect the host computer with external devices, realizing data transmission and device control functions.

[0134] S7, when it is desired to add a connection device to the above-mentioned three-dimensional model device, or to determine what functions can be added to the above-mentioned three-dimensional model device (by connecting devices), a three-dimensional model of the device to be connected can be built into the above-mentioned three-dimensional model device, it can be determined whether it can be connected, in the case of connection, which connection method is the most appropriate, in the case of not being able to connect, is it because of the lack of sockets that cannot be connected, or is it because the socket does not support that cannot be connected, etc. In the case of not being able to connect, solutions can be proposed, such as the need to set up a switching interface, etc. When determining what functions can be added, it can also be determined according to the functions of the remaining interfaces, so as to add more functions to the entire system and bring higher practicality effect.

[0135] It can be known that the optional embodiment of the application can accurately identify M potential fault devices by acquiring fault point parameters, construct a virtual model by using the wiring image of N devices, simulate the real connection state, intelligently analyze Q fault reasons in combination with the model and the parameters, design a simulation detection process in a targeted manner, guide the user to gradually troubleshoot and repair until the fault is eliminated, and significantly improve the efficiency and accuracy of fault diagnosis and solution after device assembly, overcome the limitations of traditional simulation training ignoring actual fault handling, and thus solve the technical problem that after simulation training is performed on device assembly, many faults still occur in the assembly and use process after assembly, the fault reasons are difficult to determine, and thus the faults are difficult to solve.

[0136] It should be noted that, for the foregoing method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the application is not limited by the action sequence described, because according to the application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions and modules involved are not necessarily necessary for the application.

[0137] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be realized by means of software on a general hardware platform as necessary, and of course, can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product in essence or in the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk), and includes a plurality of instructions for causing a terminal device (which can be a mobile phone, a computer, a server, or a network device) to execute the method of each embodiment of the present application.

[0138] Embodiment 2

[0139] According to the embodiments of the present application, a device for implementing the above fault cause determination method is also provided, Figure 2 is a structural block diagram of the fault cause determination device according to the embodiments of the present application, as Figure 2 shown, the device includes a receiving module 202, a first determination module 204, an acquisition module 206, a construction module 208, a second determination module 210, and a third determination module 212, which are described in detail below.

[0140] The receiving module 202 is configured to acquire fault point parameters corresponding to a fault point in equipment assembly; the first determination module 204 is connected to the receiving module 202 and is configured to determine M devices corresponding to the fault point according to the fault point parameters, wherein the M devices are all devices that have a fault probability of the fault point, and M is a positive integer greater than 1; the acquisition module 206 is connected to the first determination module 204 and is configured to acquire device connection images corresponding to N devices, wherein N is a positive integer greater than 1, and N is less than or equal to M; the construction module 208 is connected to the acquisition module 206 and is configured to construct a virtual device connection model according to the device connection images, wherein the virtual device connection model is used to simulate the connection relationship between the N devices; the second determination module 210 is connected to the construction module 208 and is configured to determine Q fault causes that cause the fault of the fault point and simulation detection operations corresponding to the Q fault causes according to the virtual device connection model and the fault point parameters; and the third determination module 212 is connected to the second determination module 210 and is configured to display the simulation detection operations corresponding to the Q fault causes in sequence, receive actual detection results fed back after a target object operates according to the corresponding simulation detection operation, and obtain a target fault cause until the corresponding actual detection result is fault recovery.

[0141] Optionally, the second determining module 210 is further configured to, in a case where the device connection image comprises a connection image between the target device socket and other device sockets, simulate a signal transmission process according to a connection relationship between the sockets in the virtual device connection model, detect a signal transmission result, determine a fault result of whether the socket connection is faulty according to the signal transmission result, and in a case where the fault result is that the socket connection is not faulty, determine Q fault causes according to the virtual device connection model and the fault point parameters, and perform simulation detection operations corresponding to the Q fault causes, respectively.

[0142] Optionally, the second determining module 210 is further configured to, in a case where the fault result is that the socket connection is faulty, obtain socket parameters, wherein the socket parameters comprise at least one of the following: a non-enabled socket connection detection parameter, and a wiring model parameter between an enabled socket and a non-enabled socket, and determine the target fault cause according to the socket parameters.

[0143] Optionally, the third determining module 212 is further configured to determine a generation probability corresponding to each of the Q fault causes and a convenience index corresponding to each of the Q simulation detection operations, determine a first priority corresponding to each of the Q fault causes according to the generation probability corresponding to each of the Q fault causes, and determine a second priority corresponding to each of the Q simulation detection operations according to the convenience index corresponding to each of the Q simulation detection operations, determine a target priority according to the first priority and the second priority, display the simulation detection operations corresponding to the Q fault causes in a sequence according to the target priority, and receive actual detection results fed back after a target object performs an operation according to a corresponding simulation detection operation until the corresponding actual detection result is that the fault is recovered, and obtain the target fault cause.

[0144] Optionally, the constructing module 208 is further configured to obtain a correct connection of device connection types corresponding to the N devices, determine a consistency result of whether a current connection is consistent with the correct connection, in a case where the consistency result is inconsistent, determine that the target fault cause is a connection error, calibrate the connection in the virtual device connection model according to the correct connection to obtain a calibrated connection, and display the calibrated connection.

[0145] Optionally, the third determining module 212 is further configured to determine a target service performed by a target object and a non-used socket corresponding to the N devices, determine an auxiliary function provided by the non-used socket for the target service, determine an auxiliary connection parameter corresponding to the non-used socket according to the auxiliary function, and connect the auxiliary function provided for the target service according to the auxiliary connection parameter.

[0146] Optionally, the constructing module 208 is further configured to construct an initial device connection model according to the device connection image, receive a correction operation sent by a target object, and calibrate the initial device connection model according to the correction operation to obtain the virtual device connection model.

[0147] It should be noted that the receiving module 202, the first determining module 204, the obtaining module 206, the constructing module 208, the second determining module 210 and the third determining module 212 correspond to steps S102 to S112 in the method for determining a fault cause, and the plurality of modules have the same instances and application scenarios as the corresponding steps, but are not limited to the content disclosed in Embodiment 1.

[0148] Embodiment 3

[0149] Embodiments of the present application can provide an electronic device, which can include one or more processors, memories, storage controllers, and peripheral interfaces, wherein the peripheral interfaces are connected with a radio frequency module, an audio module, and a display, the memories store executable programs, and the processors are configured to run the programs, and the programs perform the method of any one of the above embodiments when running.

[0150] The memory can be used to store software programs and modules, such as program instructions / modules corresponding to the method and device in the embodiments of the present application. The processor performs various functional applications and data processing by running the software programs and modules stored in the memory, that is, implements the above method. The memory can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory can further include a memory remotely arranged with respect to the processor, and the remote memory can be connected to the terminal through a network. Examples of the above network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0151] The processor can call information and application programs stored in the memory through the transmission device to perform the following steps: obtaining a fault point parameter corresponding to a fault point in equipment assembly; determining M devices corresponding to the fault point according to the fault point parameter, wherein the M devices are all devices that exist to cause a fault probability of the fault point, and M is a positive integer greater than 1; obtaining a device wiring image corresponding to N devices, wherein N is a positive integer greater than 1, and N is less than or equal to M; constructing a virtual device connection model according to the device wiring image, wherein the virtual device connection model is used to simulate a connection relationship between the N devices; determining Q fault causes causing the fault of the fault point and simulation detection operations corresponding to the Q fault causes, respectively, according to the virtual device connection model and the fault point parameter; and sequentially displaying the simulation detection operations corresponding to the Q fault causes, respectively, and receiving actual detection results fed back after a target object operates according to the corresponding simulation detection operation until the corresponding actual detection result is fault recovery, and obtaining a target fault cause.

[0152] The processor can call information and application programs stored in the memory through the transmission device to perform the following steps: determining Q fault causes of the fault point fault and simulation detection operations corresponding to the Q fault causes according to the virtual device connection model and the fault point parameters, including: in the case that the device connection image includes a plug connection image between the target device plug and other device plugs, simulating a signal transmission process according to the connection relationship between the plugs in the virtual device connection model, detecting a signal transmission result; determining a fault result of whether the plug connection is faulty according to the signal transmission result; in the case that the fault result is that the plug connection is not faulty, determining the Q fault causes according to the virtual device connection model and the fault point parameters, and performing the simulation detection operations corresponding to the Q fault causes.

[0153] The processor can call information and application programs stored in the memory through the transmission device to perform the following steps: determining Q fault causes of the fault point fault and simulation detection operations corresponding to the Q fault causes according to the virtual device connection model and the fault point parameters, including: in the case that the device connection image includes a plug connection image between the target device plug and other device plugs, simulating a signal transmission process according to the connection relationship between the plugs in the virtual device connection model, detecting a signal transmission result; determining a fault result of whether the plug connection is faulty according to the signal transmission result; in the case that the fault result is that the plug connection is not faulty, determining the Q fault causes according to the virtual device connection model and the fault point parameters, and performing the simulation detection operations corresponding to the Q fault causes.

[0154] The processor can call information and application programs stored in the memory through the transmission device to perform the following steps: sequentially displaying the simulation detection operations corresponding to the Q fault causes and receiving actual detection results fed back by the target object after operating according to the corresponding simulation detection operations until the corresponding actual detection result is fault recovery, and obtaining the target fault cause, including: determining the generation probability corresponding to the Q fault causes and the convenience index corresponding to the Q simulation detection operations; determining the first priority corresponding to the Q fault causes according to the generation probability corresponding to the Q fault causes, and determining the second priority corresponding to the Q simulation detection operations according to the convenience index corresponding to the Q simulation detection operations; determining the target priority according to the first priority and the second priority; sequentially displaying the simulation detection operations corresponding to the Q fault causes according to the order of the target priority, and receiving actual detection results fed back by the target object after operating according to the corresponding simulation detection operations until the corresponding actual detection result is fault recovery, and obtaining the target fault cause.

[0155] The processor can call information and application programs stored in the memory through the transmission device to perform the following steps: after constructing the virtual device connection model according to the device connection image, further comprising: obtaining the correct connection of the device connection type corresponding to the N devices; determining the consistency result of whether the current connection is consistent with the correct connection; in the case of inconsistency of the consistency result, determining that the target fault reason is connection error, and calibrating the connection in the virtual device connection model according to the correct connection to obtain the calibrated connection to display the calibrated connection.

[0156] The processor can call information and application programs stored in the memory through the transmission device to perform the following steps: sequentially display the simulation detection operation corresponding to the Q fault reasons respectively, and receive the actual detection result fed back after the target object operates according to the corresponding simulation detection operation until the corresponding actual detection result is fault recovery to obtain the target fault reason, and further comprising: determining the target service executed by the target object and the unused socket corresponding to the N devices; determining the auxiliary function provided by the unused socket for the target service; determining the auxiliary connection parameter corresponding to the unused socket according to the auxiliary function to connect the auxiliary function provided for the target service according to the auxiliary connection parameter.

[0157] The processor can call information and application programs stored in the memory through the transmission device to perform the following steps: constructing the virtual device connection model according to the device connection image, comprising: constructing the initial device connection model according to the device connection image; receiving the correction operation sent by the target object; calibrating the initial device connection model according to the correction operation to obtain the virtual device connection model.

[0158] The application obtains fault point parameters corresponding to fault points in equipment assembly; determines M devices corresponding to the fault points according to the fault point parameters, wherein the M devices are all devices that cause the fault probability of the fault points, and M is a positive integer greater than 1; obtains device wiring images corresponding to N devices, wherein N is a positive integer greater than 1, and N is less than or equal to M; constructs a virtual device connection model according to the device wiring images, wherein the virtual device connection model is used to simulate the connection relationship between the N devices; determines Q fault causes that cause the fault of the fault points and simulation detection operations corresponding to the Q fault causes according to the virtual device connection model and the fault point parameters; displays the simulation detection operations corresponding to the Q fault causes in sequence, and receives actual detection results fed back after a target object operates according to the corresponding simulation detection operations until the corresponding actual detection results are fault recovery, and obtains a target fault cause. It can be known that the application obtains fault point parameters, accurately identifies M potential fault devices, constructs a virtual model by using the wiring images of the N devices, simulates the real connection state, intelligently analyzes Q fault causes in combination with the model and the parameters, designs simulation detection processes in a targeted manner, guides users to gradually troubleshoot and repair, and finally eliminates the faults, thereby significantly improving the efficiency and accuracy of fault diagnosis and solution after equipment assembly, overcoming the limitation that the traditional simulation training ignores actual fault processing, and further solving the technical problem that many faults still occur in the assembly and use process after actual equipment assembly according to the training content after the simulation training of the equipment assembly in the related art, and it is difficult to determine the fault causes and solve the faults.

[0159] Those skilled in the art can understand that the above structure is only schematic, and the electronic device can also be a terminal device such as a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet Device (MID), a PAD, etc. The above description does not limit the structure of the electronic device. For example, the electronic device can further include more or fewer components (such as a network interface, a display device, etc.) or have a different configuration.

[0160] Those skilled in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the related hardware of the terminal device by a program, and the program can be stored in a computer readable storage medium, and the storage medium can include a flash disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, etc.

[0161] Embodiment 4

[0162] The embodiment of the present application further provides a computer readable storage medium. The computer readable storage medium comprises a stored executable program, wherein the executable program controls the device where the computer readable storage medium is located to perform the method of any one of the above when the executable program is executed.

[0163] Optionally, in the embodiment, the storage medium can be located in any one of the computer terminals in the computer terminal group in the computer network, or in any one of the mobile terminals in the mobile terminal group.

[0164] The present application further provides a computer program product, when executed on a data processing device, the computer instructions are executed by the processor to implement the following steps: obtaining a fault point parameter corresponding to a fault point in device assembly; determining M devices corresponding to the fault point according to the fault point parameter, wherein the M devices are all devices that cause the fault probability of the fault point, and M is a positive integer greater than 1; obtaining a device wiring image corresponding to N devices, wherein N is a positive integer greater than 1, and N is less than or equal to M; constructing a virtual device connection model according to the device wiring image, wherein the virtual device connection model is used to simulate the connection relationship between the N devices; determining Q fault causes that cause the fault of the fault point and simulation detection operations corresponding to the Q fault causes respectively according to the virtual device connection model and the fault point parameter; and displaying the simulation detection operations corresponding to the Q fault causes respectively in sequence, and receiving actual detection results fed back after a target object operates according to the corresponding simulation detection operation until the corresponding actual detection result is fault recovery, and obtaining a target fault cause.

[0165] The serial numbers of the above embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

[0166] In the above embodiments of the present application, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0167] In the several embodiments provided by the present application, it should be understood that the disclosed technology can be implemented in other ways. Of course, the unit division in the above device embodiment is only a logical function division, and there can be another division manner during actual implementation; for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between different units, units or modules can be indirect couplings or communication connections through some interfaces, units or modules, and can be electrical or other forms.

[0168] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e. may be located in one place, or may be distributed to multiple network units. Part or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.

[0169] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0170] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part of the prior art that contributes to the technical solutions or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk, and various program code storage media.

[0171] The above is only the preferred embodiment of the present application, and it should be pointed out that for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, which should be considered as the protection scope of the present application.

Claims

1. A method for determining the cause of a fault, characterized in that, include: Obtain the fault point parameters corresponding to the fault points during equipment assembly; Based on the fault point parameters, M devices corresponding to the fault point are determined, wherein each of the M devices is a device that has a probability of causing the fault point to fail, and M is a positive integer greater than 1; Obtain the device wiring diagrams corresponding to N devices, where N is a positive integer greater than 1, and N is less than or equal to M; Based on the device wiring diagram, a virtual device connection model is constructed, wherein the virtual device connection model is used to simulate the connection relationship between the N devices; Based on the virtual device connection model and the fault point parameters, determine Q fault causes that cause the fault point fault, and simulation detection operations corresponding to the Q fault causes, where Q is a positive integer greater than 1; The simulation detection operations corresponding to the Q fault causes are displayed sequentially, and the actual detection results fed back by the target object after performing the corresponding simulation detection operations are received until the corresponding actual detection result is that the fault is recovered, thus obtaining the target fault cause.

2. The method according to claim 1, characterized in that, Based on the virtual device connection model and the fault point parameters, Q fault causes that lead to the fault point are determined, along with simulation detection operations corresponding to each of the Q fault causes, including: When the device wiring image includes a connection image between the target device socket and other device sockets, the signal transmission process is simulated and the signal transmission result is detected based on the connection relationship between the sockets in the virtual device connection model. Based on the signal transmission results, determine whether the socket connection is faulty; If the fault result is that the socket connection is not faulty, the Q fault causes are determined based on the virtual device connection model and the fault point parameters, and simulation detection operations are performed corresponding to the Q fault causes respectively.

3. The method according to claim 2, characterized in that, After determining whether the socket connection is faulty based on the signal transmission results, the following further steps are included: In the case where the fault result is a socket connection fault, the socket parameters are obtained, wherein the socket parameters include at least one of the following: disabled socket connection detection parameters, and wiring model parameters between the enabled socket and the disabled socket; Based on the socket parameters, determine the cause of the target fault.

4. The method according to claim 1, characterized in that, The simulation detection operations corresponding to the Q fault causes are displayed sequentially, and the actual detection results fed back by the target object after performing the corresponding simulation detection operations are received, until the corresponding actual detection result is fault recovery, thus obtaining the target fault cause, including: Determine the occurrence probability corresponding to each of the Q fault causes, and the convenience index corresponding to each of the Q simulation detection operations; Based on the occurrence probability corresponding to each of the Q fault causes, a first priority corresponding to each of the Q fault causes is determined, and based on the convenience index corresponding to each of the Q simulation detection operations, a second priority corresponding to each of the Q simulation detection operations is determined. The target priority is determined based on the first priority and the second priority. Based on the priority of the target, the simulation detection operations corresponding to the Q fault causes are displayed sequentially, and the actual detection results fed back by the target object after performing the corresponding simulation detection operations are received until the corresponding actual detection result is fault recovery, thus obtaining the target fault cause.

5. The method according to claim 1, characterized in that, After constructing the virtual device connection model based on the device wiring diagram, the process further includes: Obtain the correct connection for the device connection type corresponding to the N devices; Determine the consistency result of whether the current connection is consistent with the correct connection; If the consistency result is inconsistent, the cause of the target fault is determined to be a wiring error. Based on the correct wiring, the wiring in the virtual device connection model is calibrated to obtain calibrated wiring, which is then displayed.

6. The method according to claim 1, characterized in that, The simulation detection operations corresponding to the Q fault causes are displayed sequentially, and the actual detection results fed back by the target object after performing the corresponding simulation detection operations are received, until the corresponding actual detection result is fault recovery. After obtaining the target fault cause, the process also includes: Determine the target service to be performed by the target object, and the unused ports corresponding to the N devices; Determine the auxiliary functions provided by the unused port for the target service; Based on the auxiliary function, auxiliary connection parameters corresponding to the unused port are determined, and the auxiliary function is provided for the target service by connecting according to the auxiliary connection parameters.

7. The method according to any one of claims 1 to 6, characterized in that, Based on the device wiring diagram, a virtual device connection model is constructed, including: Based on the device wiring diagram, an initial device connection model is constructed; Receive the correction operation sent by the target object; Based on the correction operation, the initial device connection model is calibrated to obtain the virtual device connection model.

8. A device for determining the cause of a fault, characterized in that, include: The receiving module is used to acquire the fault point parameters corresponding to the fault point during equipment assembly. The first determining module is used to determine M devices corresponding to the fault point based on the fault point parameters, wherein the M devices are all devices that have a probability of causing the fault point to fail, and M is a positive integer greater than 1. The acquisition module is used to acquire device wiring images corresponding to N devices, where N is a positive integer greater than 1, and N is less than or equal to M; A construction module is used to construct a virtual device connection model based on the device wiring diagram, wherein the virtual device connection model is used to simulate the connection relationship between the N devices; The second determining module is used to determine Q fault causes that cause the fault at the fault point based on the virtual device connection model and the fault point parameters, and simulation detection operations corresponding to the Q fault causes respectively, wherein Q is a positive integer greater than 1. The third determination module is used to sequentially display the simulation detection operations corresponding to the Q fault causes, and receive the actual detection results fed back by the target object after performing the corresponding simulation detection operations, until the corresponding actual detection result is fault recovery, thus obtaining the target fault cause.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the computer-readable storage medium is located to perform the method according to any one of claims 1 to 7.

10. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 7.

11. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the steps of the method described in any one of claims 1 to 7.

Images