MVB network fault identification method and device

By generating a list of faulty equipment and network segments, and identifying the faulty repeater based on the MVB repeater data link list, the problems of cumbersome and insufficient flexibility in MVB network fault diagnosis are solved, and efficient and accurate fault identification is achieved.

CN119071138APending Publication Date: 2024-12-03CHINA ACADEMY OF RAILWAY SCI CORP LTD +3
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411208975.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-30
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In the high-speed EMU network, the existing MVB network is complicated to diagnose A/B road faults, is not flexible, and is prone to errors.

Method used

By generating a list of fault devices, a list of fault segments of some equipment, and a list of fault segments of all equipment, and generating a list of fault repeaters based on the MVB repeater data link list, the repeater corresponds one by one to the current network segment of fault identification, to achieve Efficient and accurate fault identification.

Benefits of technology

It improves the efficiency and accuracy of MVB network fault identification, reduces the workload of manual programming, and reduces the error rate.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071138A_ABST
    Figure CN119071138A_ABST
Patent Text Reader

Abstract

The invention provides an MVB network fault identification method and device, and relates to the technical field of fault diagnosis. The method comprises the following steps: generating a fault equipment list according to an MVB equipment activation list and an MVB equipment state list; generating a partial equipment fault network segment list and an all equipment fault network segment list according to the fault equipment list and the MVB equipment data chain table; generating a fault repeater list according to an MVB repeater data chain table, the partial equipment fault network segment list, the all equipment fault network segment list and a network segment where a bus manager is located; wherein the repeaters are in one-to-one correspondence with the current network segments of the fault identification. The device executes the method. According to the MVB network fault identification method and device provided by the embodiment of the invention, MVB network fault identification can be efficiently and accurately realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of fault diagnosis, and in particular to an MVB network fault identification method and device. Background Art

[0002] like Figure 1 As shown in FIG. 1 , an MVB network usually includes one or more MVB segments, and MVB segments are connected to each other through MVB repeaters. In actual use, the most typical MVB topology is a backbone segment connected to several sub-segments.

[0003] MVB network A / B line faults mainly include three aspects: MVB device A / B line faults, MVB network segment A / B line faults and MVB repeater A / B line faults. At present, in the network control system of high-speed EMU trains, the A / B line fault diagnosis of MVB networks is basically implemented by manual programming in the train control system software based on a fixed network topology. This is cumbersome, inflexible, and has a large workload and is prone to errors. Summary of the invention

[0004] In view of the problems in the prior art, an embodiment of the present invention provides an MVB network fault identification method and device, which can at least partially solve the problems in the prior art.

[0005] On the one hand, the present invention provides an MVB network fault identification method, comprising:

[0006] Generate a faulty device list based on the MVB device activation list and the MVB device status list;

[0007] Generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list;

[0008] Generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0009] Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

[0010] The generating of the faulty device list according to the MVB device activation list and the MVB device status list includes:

[0011] If it is determined that the MVB device is in the MVB device activation list, and if it is determined that the MVB device is offline according to the MVB device status list, the MVB device is added to the faulty device list.

[0012] Wherein, generating a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list includes:

[0013] Determine the network segment where the MVB device is located according to the faulty device list and the MVB device data linked list;

[0014] According to the network segment where each MVB device is located, determine the faulty devices contained in each network segment, compare the number of faulty devices contained in each network segment with the number of MVB devices in the corresponding network segment, and add each network segment to the partial device faulty network segment list or the all device faulty network segment list according to the comparison result.

[0015] The generating of the faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located includes:

[0016] Go through the current network segments one by one. If it is determined according to the MVB repeater data linked list that the network segment where the bus manager is located is the same as the current network segment, then generate the faulty repeater list according to the current network segment, the partial device faulty network segment list and the all device faulty network segment list.

[0017] The generating of the faulty repeater list according to the current network segment, the partial device faulty network segment list and the all device faulty network segment list includes:

[0018] If the current network segment is in the list of partial device faulty network segments, and other network segments in the MVB backbone network segment except the current network segment are in the list of all device faulty network segments, the repeater corresponding to the current network segment is added to the list of faulty repeaters.

[0019] Wherein, the MVB network fault identification method further includes:

[0020] If it is determined according to the MVB repeater data linked list that the network segment where the bus manager is located is different from the current network segment, the faulty repeater list is generated according to the current network segment, the network segment where the bus manager is located, the partial device faulty network segment list and the all device faulty network segment list.

[0021] The generating of the faulty repeater list according to the current network segment, the network segment where the bus manager is located, the partial device faulty network segment list and the all device faulty network segment list includes:

[0022] If it is determined that the current network segment is in the list of all device faulty network segments, and the network segment where the bus manager is located is neither in the list of some device faulty network segments nor in the list of all device faulty network segments, the repeater corresponding to the current network segment is added to the list of faulty repeaters.

[0023] On the one hand, the present invention provides an MVB network fault identification device, comprising:

[0024] A first generating unit, configured to generate a faulty device list according to the MVB device activation list and the MVB device status list;

[0025] A second generating unit is used to generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list;

[0026] A third generating unit is used to generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0027] Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

[0028] In another aspect, an embodiment of the present invention provides an electronic device, including: a processor, a memory, and a bus, wherein:

[0029] The processor and the memory communicate with each other via the bus;

[0030] The memory stores program instructions that can be executed by the processor, and the processor calls the program instructions to execute the following method:

[0031] Generate a faulty device list based on the MVB device activation list and the MVB device status list;

[0032] Generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list;

[0033] Generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0034] Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

[0035] An embodiment of the present invention provides a non-transitory computer-readable storage medium, including:

[0036] The non-transitory computer-readable storage medium stores computer instructions, which cause the computer to execute the following method:

[0037] Generate a faulty device list based on the MVB device activation list and the MVB device status list;

[0038] Generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list;

[0039] Generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0040] Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

[0041] The MVB network fault identification method and device provided by the embodiment of the present invention generate a faulty device list based on the MVB device activation list and the MVB device status list; generate a partial device faulty network segment list and a full device faulty network segment list based on the faulty device list and the MVB device data linked list; generate a faulty repeater list based on the MVB repeater data linked list, the partial device faulty network segment list, the full device faulty network segment list and the network segment where the bus manager is located; wherein the repeater corresponds one-to-one to the current network segment of the fault identification, and can efficiently and accurately implement MVB network fault identification. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0043] Figure 1 It is a schematic diagram of the MVB network topology structure in the prior art.

[0044] Figure 2 It is a flowchart of an MVB network fault identification method provided by an embodiment of the present invention.

[0045] Figure 3 It is a schematic diagram illustrating the conversion of network topology into a data linked list provided by an embodiment of the present invention.

[0046] Figure 4 It is a schematic diagram illustrating a network topology transformation algorithm provided by an embodiment of the present invention.

[0047] Figure 5It is a schematic diagram for explaining fault diagnosis of the MVB device and network segment A / B provided by an embodiment of the present invention.

[0048] Figure 6 It is a schematic diagram illustrating an algorithm for diagnosing faults of MVB equipment and network segment A / B provided in an embodiment of the present invention.

[0049] Figure 7 It is a schematic diagram for explaining the fault diagnosis of the A / B path of the MVB repeater provided by an embodiment of the present invention.

[0050] Figure 8 It is a schematic diagram illustrating a repeater A / B path fault diagnosis algorithm provided by an embodiment of the present invention.

[0051] Fig. 9 It is a structural diagram of an MVB network fault identification device provided by an embodiment of the present invention.

[0052] Fig.10 A schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical scheme and advantages of the embodiments of the present invention more clear, the embodiments of the present invention are further described in detail below in conjunction with the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention. It should be noted that, in the absence of conflict, the embodiments in this application and the features in the embodiments can be combined with each other arbitrarily.

[0054] Figure 2 FIG. 1 is a flow chart of a method for identifying an MVB network fault according to an embodiment of the present invention. Figure 2 As shown, the MVB network fault identification method provided by the embodiment of the present invention includes:

[0055] Step S1: Generate a faulty device list according to the MVB device activation list and the MVB device status list.

[0056] Step S2: Generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list.

[0057] Step S3: Generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0058] Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

[0059] In the above step S1, the device generates a list of faulty devices according to the MVB device activation list and the MVB device status list. The device may be a computer device that executes the method. It should be noted that the acquisition and analysis of data related to user privacy in the embodiment of the present invention is authorized by the user. The MVB device in the embodiment of the present invention refers to an ordinary MVB device, which is different from an MVB repeater that acts as a relay.

[0060] Before this step, you can first obtain the MVB device data link list and the MVB repeater data link list, such as Figure 3 As shown, it can be Figure 1 The actual network topology shown is converted into an MVB device data linked list and an MVB repeater data linked list.

[0061] like Figure 4 As shown, Figure 3 The implementation of the network topology transformation algorithm in is described as follows:

[0062] You can follow Figure 1 The order of MVB segment 1, MVB segment 2, MVB segment 3 and MVB segment 4 traverses each segment in the network topology in turn.

[0063] Taking MVB network segment 1 as an example, each device information may be traversed in sequence according to the device number sequence of MVB repeater 1, MVB device 1, MVB device 2 ... MVB device 6.

[0064] It is understandable that the MVB device data linked list records the link relationship between each MVB device and the network segment each MVB device is in. The MVB repeater data linked list records the link relationship between each MVB repeater and the network segment each MVB repeater is in, and the link relationship between the network segment and other network segments.

[0065] The MVB device activation list may record whether each MVB device is activated, and the MVB device status list may record the device status of each MVB device, specifically including an online status and an offline status.

[0066] like Figure 5 As shown, the MVB device activation list, MVB device status list and MVB device data link list can be used to obtain a list of faulty devices, a list of faulty network segments of some devices and a list of faulty network segments of all devices. According to the fault type, the fault identification of this application can be further performed, specifically identifying A-line faults and B-line faults.

[0067] Specifically, the MVB device activation list and the MVB device status list may be used to generate a faulty device list, and the faulty device list and the MVB device data linked list may be used to generate a partial device faulty network segment list and a full device faulty network segment list.

[0068] like Figure 6 As shown, Figure 5 The implementation of the MVB device and network segment A / B fault diagnosis algorithm is described as follows:

[0069] The generating of the faulty device list according to the MVB device activation list and the MVB device status list includes:

[0070] If it is determined that the MVB device is in the MVB device activation list, and the MVB device is judged to be offline according to the MVB device status list, the MVB device is added to the faulty device list. If the MVB device is in the MVB device activation list, it means that the device is activated. If the MVB device is not in the MVB device activation list, it means that the device is not activated, and the corresponding MVB device and network segment A / B path fault diagnosis algorithm can be terminated in advance.

[0071] The flag bit can be used to determine whether the MVB device is offline (flag bit 0) or online (flag bit 1). If the MVB device is online, it means that the device is normal, and the corresponding MVB device and network segment A / B fault diagnosis algorithm can be terminated in advance. Each MVB device executes the above judgment process, so the fault device list records all fault device information.

[0072] In the above step S2, the device generates a partial device fault segment list and a full device fault segment list according to the fault device list and the MVB device data linked list. The generating of a partial device fault segment list and a full device fault segment list according to the fault device list and the MVB device data linked list includes:

[0073] Determine the network segment where the MVB device is located according to the faulty device list and the MVB device data linked list;

[0074] According to the network segment where each MVB device is located, determine the faulty devices contained in each network segment, compare the number of faulty devices contained in each network segment with the number of MVB devices in the corresponding network segment, and add each network segment to the partial device faulty network segment list or the all device faulty network segment list according to the comparison result. Since the MVB device data link table records the link relationship between each MVB device and the network segment where each MVB device is located, the network segment where each device is located can be obtained. Figure 1As shown, taking MVB segment 1 as an example, if MVB devices 1 to 5 are faulty devices, they are all in MVB segment 1, that is, the number of faulty devices in MVB segment 1 is 5. Since the number of MVB devices in MVB segment 1 is 6, that is, not all devices in MVB segment 1 are faulty, MVB segment 1 can be added to the list of faulty segments for some devices. If the number of faulty devices in MVB segment 2 is 5, since the number of MVB devices in MVB segment 2 is 5, that is, all devices in MVB segment 2 are faulty, MVB segment 2 can be added to the list of faulty segments for all devices.

[0075] In the above step S3, the device generates a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0076] The repeater corresponds to the current network segment of the fault identification. Figure 1 As shown, MVB repeater 1 corresponds to MVB network segment 1, and other corresponding relationships are similar and will not be described in detail.

[0077] The generating of the faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located comprises:

[0078] The current network segment is traversed one by one. If it is determined according to the MVB repeater data linked list that the network segment where the bus manager is located is the same as the current network segment, the faulty repeater list is generated according to the current network segment, the partial device faulty network segment list and the all device faulty network segment list. Before traversing the current network segment one by one, the MVB repeater activation list can also be used to determine whether the repeater is activated. For activated repeaters, subsequent method steps can be executed, and for unactivated repeaters, the termination method execution can be extracted.

[0079] like Figure 7 As shown, you can use the MVB repeater activation list, MVB repeater data link list, some device fault segment list, all device fault segment list and bus manager segment ( Figure 7 (not shown) to obtain a list of faulty repeaters.

[0080] like Figure 8 As shown, Figure 7 The implementation of the repeater A / B fault diagnosis algorithm is described as follows:

[0081] Take the bus manager's network segment in MVB network segment 1 as an example, and traverse each current network segment in the order of MVB network segment 1 to MVB network segment 4. For the current MVB network segment 1, which is the same as the network segment where the bus manager is located, if MVB network segment 1 is in the list of some device failure network segments, it means that some devices in MVB network segment 1 are faulty. Since the bus manager mainly plays a management and scheduling role, if MVB repeater 1 corresponding to MVB network segment 1 fails, the bus manager cannot schedule MVB devices in other network segments, so all devices in other network segments will fail, which is reflected in the fact that other network segments in the MVB backbone network segment except the current network segment are in the list of all device failure network segments. Therefore, MVB repeater 1 is added to the list of faulty repeaters.

[0082] The MVB network fault identification method further includes:

[0083] If it is determined according to the MVB repeater data linked list that the network segment where the bus manager is located is different from the current network segment, the fault repeater list is generated according to the current network segment, the network segment where the bus manager is located, the partial device fault network segment list and the all device fault network segment list. Figure 8 As shown, when the current network segment traversed is MVB network segment 2, since the network segment where the bus manager is located is MVB network segment 1, which is different from MVB network segment 2, if MVB network segment 2 is in the list of all device failure network segments, it means that all devices in MVB network segment 2 are faulty, and if there are no faults in the devices in MVB network segment 1, it is reflected in that MVB network segment 1 is neither in the list of some device failure network segments nor in the list of all device failure network segments.

[0084] Since the bus manager mainly plays a management and scheduling role, all devices in the MVB segment 1 where the bus manager is located are normal, and all devices in the MVB segment 2 are faulty devices. Therefore, it can only be that the MVB repeater 2 corresponding to the MVB segment 2 has a fault. Therefore, MVB repeater 2 is added to the faulty repeater list. The corresponding situation where the current segment is different from the segment where the bus manager is located is the same as the situation where the current segment is the MVB segment 2, and will not be repeated.

[0085] The MVB network fault identification method provided by the embodiment of the present invention generates a faulty device list based on the MVB device activation list and the MVB device status list; generates a partial device faulty network segment list and a full device faulty network segment list based on the faulty device list and the MVB device data linked list; generates a faulty repeater list based on the MVB repeater data linked list, the partial device faulty network segment list, the full device faulty network segment list and the network segment where the bus manager is located; wherein the repeater corresponds one-to-one to the current network segment of the fault identification, and can efficiently and accurately implement MVB network fault identification.

[0086] Further, generating a faulty device list according to the MVB device activation list and the MVB device status list includes:

[0087] If it is determined that the MVB device is in the MVB device activation list, and the MVB device is judged to be offline according to the MVB device status list, the MVB device is added to the faulty device list.

[0088] Further, generating a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list includes:

[0089] According to the faulty device list and the MVB device data linked list, the network segment where the MVB device is located is determined; the above-mentioned embodiment can be referred to for description and will not be repeated here.

[0090] According to the network segment where each MVB device is located, the faulty devices contained in each network segment are determined, the number of faulty devices contained in each network segment is compared with the number of MVB devices in the corresponding network segment, and each network segment is added to the partial device faulty network segment list or the all device faulty network segment list according to the comparison result. Please refer to the above embodiment for description and no further details will be given.

[0091] Further, generating a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located includes:

[0092] The current network segment is traversed one by one, and if it is determined according to the MVB repeater data linked list that the network segment where the bus manager is located is the same as the current network segment, then the fault repeater list is generated according to the current network segment, the partial device fault network segment list and the all device fault network segment list. The above embodiment can be referred to for explanation and will not be repeated here.

[0093] Further, generating the faulty repeater list according to the current network segment, the partial device faulty network segment list and the all device faulty network segment list includes:

[0094] If the current network segment is in the partial device fault network segment list, and other network segments in the MVB backbone network segment except the current network segment are in the all device fault network segment list, then the repeater corresponding to the current network segment is added to the fault repeater list.

[0095] Furthermore, the MVB network fault identification method further includes:

[0096] If it is determined according to the MVB repeater data linked list that the network segment where the bus manager is located is different from the current network segment, the fault repeater list is generated according to the current network segment, the network segment where the bus manager is located, the partial device fault network segment list and the all device fault network segment list. The above-mentioned embodiment can be referred to for explanation and will not be repeated here.

[0097] Further, generating the faulty repeater list according to the current network segment, the network segment where the bus manager is located, the partial device faulty network segment list and the all device faulty network segment list includes:

[0098] If it is determined that the current network segment is in the list of all device fault network segments, and the network segment where the bus manager is located is neither in the list of some device fault network segments nor in the list of all device fault network segments, then the repeater corresponding to the current network segment is added to the fault repeater list. The above embodiment can be referred to for explanation and will not be repeated here.

[0099] Fig. 9 FIG. 1 is a schematic diagram of the structure of an MVB network fault identification device provided by an embodiment of the present invention. Fig. 9 As shown, the MVB network fault identification device provided by the embodiment of the present invention includes a first generation unit 901, a second generation unit 902 and a third generation unit 903, wherein:

[0100] The first generation unit 901 is used to generate a faulty device list based on the MVB device activation list and the MVB device status list; the second generation unit 902 is used to generate a partial device faulty network segment list and a full device faulty network segment list based on the faulty device list and the MVB device data linked list; the third generation unit 903 is used to generate a faulty repeater list based on the MVB repeater data linked list, the partial device faulty network segment list, the full device faulty network segment list and the network segment where the bus manager is located; wherein the repeater corresponds one-to-one to the current network segment identified by the fault.

[0101] Specifically, the first generation unit 901 in the device is used to generate a faulty device list based on the MVB device activation list and the MVB device status list; the second generation unit 902 is used to generate a partial device faulty network segment list and a full device faulty network segment list based on the faulty device list and the MVB device data linked list; the third generation unit 903 is used to generate a faulty repeater list based on the MVB repeater data linked list, the partial device faulty network segment list, the full device faulty network segment list and the network segment where the bus manager is located; wherein the repeater corresponds one-to-one to the current network segment identified by the fault.

[0102] The MVB network fault identification device provided by the embodiment of the present invention generates a faulty device list based on the MVB device activation list and the MVB device status list; generates a partial device faulty network segment list and a full device faulty network segment list based on the faulty device list and the MVB device data linked list; generates a faulty repeater list based on the MVB repeater data linked list, the partial device faulty network segment list, the full device faulty network segment list and the network segment where the bus manager is located; wherein the repeater corresponds one-to-one to the current network segment of the fault identification, and can efficiently and accurately implement MVB network fault identification.

[0103] The embodiment of the MVB network fault identification device provided in the embodiment of the present invention can be specifically used to execute the processing flow of the above-mentioned method embodiments. Its functions are not repeated here, and reference can be made to the detailed description of the above-mentioned method embodiments.

[0104] Fig.10 A schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention, such as Fig.10 As shown, the electronic device includes: a processor (processor) 1001, a memory (memory) 1002 and a bus 1003;

[0105] The processor 1001 and the memory 1002 communicate with each other via a bus 1003;

[0106] The processor 1001 is used to call the program instructions in the memory 1002 to execute the methods provided by the above method embodiments, for example, including:

[0107] Generate a faulty device list based on the MVB device activation list and the MVB device status list;

[0108] Generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list;

[0109] Generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0110] Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

[0111] This embodiment discloses a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, the computer can perform the methods provided by the above method embodiments, for example, including:

[0112] Generate a faulty device list based on the MVB device activation list and the MVB device status list;

[0113] Generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list;

[0114] Generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0115] Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

[0116] This embodiment provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program enables the computer to execute the methods provided by the above method embodiments, for example, including:

[0117] Generate a faulty device list based on the MVB device activation list and the MVB device status list;

[0118] Generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list;

[0119] Generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located;

[0120] Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

[0121] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0122] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0123] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0124] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0125] In the description of this specification, the description with reference to the terms "one embodiment", "a specific embodiment", "some embodiments", "for example", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0126] The specific embodiments described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for identifying MVB network faults, characterized in that: include: Generate a faulty device list based on the MVB device activation list and the MVB device status list; Generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list; Generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located; Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

2. The MVB network fault identification method according to claim 1, characterized in that: The generating of the faulty device list according to the MVB device activation list and the MVB device status list includes: If it is determined that the MVB device is in the MVB device activation list, and if it is determined that the MVB device is offline according to the MVB device status list, the MVB device is added to the faulty device list.

3. The MVB network fault identification method according to claim 1, characterized in that: The generating of a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data chain list includes: Determine the network segment where the MVB device is located according to the faulty device list and the MVB device data linked list; According to the network segment where each MVB device is located, determine the faulty devices contained in each network segment, compare the number of faulty devices contained in each network segment with the number of MVB devices in the corresponding network segment, and add each network segment to the partial device faulty network segment list or the all device faulty network segment list according to the comparison result.

4. The MVB network fault identification method according to claim 1, characterized in that: The generating of the faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located comprises: Go through the current network segments one by one. If it is determined according to the MVB repeater data linked list that the network segment where the bus manager is located is the same as the current network segment, then generate the faulty repeater list according to the current network segment, the partial device faulty network segment list and the all device faulty network segment list.

5. The MVB network fault identification method according to claim 4, characterized in that: The generating the faulty repeater list according to the current network segment, the partial device faulty network segment list and the all device faulty network segment list comprises: If the current network segment is in the list of partial device faulty network segments, and other network segments in the MVB backbone network segment except the current network segment are in the list of all device faulty network segments, the repeater corresponding to the current network segment is added to the list of faulty repeaters.

6. The MVB network fault identification method according to any one of claims 1 to 5, characterized in that: The MVB network fault identification method further includes: If it is determined according to the MVB repeater data linked list that the network segment where the bus manager is located is different from the current network segment, the faulty repeater list is generated according to the current network segment, the network segment where the bus manager is located, the partial device faulty network segment list and the all device faulty network segment list.

7. The MVB network fault identification method according to claim 6, characterized in that: The generating the faulty repeater list according to the current network segment, the network segment where the bus manager is located, the partial device faulty network segment list and the all device faulty network segment list comprises: If it is determined that the current network segment is in the list of all device faulty network segments, and the network segment where the bus manager is located is neither in the list of some device faulty network segments nor in the list of all device faulty network segments, the repeater corresponding to the current network segment is added to the list of faulty repeaters.

8. An MVB network fault identification device, characterized in that: include: A first generating unit, configured to generate a faulty device list according to the MVB device activation list and the MVB device status list; A second generating unit is used to generate a partial device fault network segment list and a full device fault network segment list according to the fault device list and the MVB device data linked list; A third generating unit is used to generate a faulty repeater list according to the MVB repeater data linked list, the partial device faulty network segment list, the all device faulty network segment list and the network segment where the bus manager is located; Among them, the repeater corresponds one-to-one to the current network segment of the fault identification.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

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