Fault analysis method and device, electronic equipment and storage medium

Abstract

The invention provides a fault analysis method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining a signal association relation snapshot table and an equipment total log corresponding to fault information when the fault information of a fault reported by a monitoring system is received; performing fault analysis based on the signal association relation snapshot table and the equipment total log to obtain a link fault analysis result; and determining a fault condition of the fault information based on the link fault analysis result so as to determine whether fault processing is needed based on the fault condition. According to the embodiment of the invention, fault analysis is carried out on a link where a video playing stream is located by using a signal association relation snapshot table in which a fault is written and a total log of equipment so as to determine a link fault analysis result; and the fault condition of the fault information is analyzed according to a link fault analysis result, so that the fault analysis accuracy is improved, and possible problems are avoided.

Description

Technical Field

[0001] The present invention relates to the technical field of fault data processing, and in particular to a fault analysis method, device, electronic equipment and storage medium. Background Art

[0002] The intelligent broadcast control management system consists of video server groups, broadcast control centers and other equipment, and is an important system for digital TV programs.

[0003] Fault analysis for intelligent broadcast control and management systems often only analyzes the alarm content of a single fault. Due to restrictions on equipment performance and capabilities, it has certain limitations and may lead to misjudgment, resulting in inaccurate analysis of the cause of the fault. Summary of the invention

[0004] In view of this, an embodiment of the present invention provides a fault analysis method, device, electronic device and storage medium to solve the problem of inaccurate analysis of fault causes in the prior art.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] A first aspect of an embodiment of the present invention shows a fault analysis method, the method comprising:

[0007] If fault information of a fault reported by the monitoring system is received, a signal association snapshot table and a device general log corresponding to the fault information are obtained;

[0008] Performing fault analysis based on the signal association snapshot table and the device total log to obtain a link fault analysis result;

[0009] The fault condition of the fault information is determined based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

[0010] Optionally, performing a fault analysis based on the signal association snapshot table and the device total log to obtain a link fault analysis result includes:

[0011] If the fault information is a flow interruption fault, determining a corresponding output fault result based on the signal association relationship snapshot table and the device general log;

[0012] Determine the in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log;

[0013] Determine the device switching result within a preset time period corresponding to the fault occurrence time based on the device general log;

[0014] The output fault result, the in-use fault result and the device switching result are used as the link fault analysis result.

[0015] Optionally, also include:

[0016] Determine whether a non-in-use fault determination is required based on the output fault result, the in-use fault result and the device switching result;

[0017] If so, determining the non-in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log;

[0018] The output fault result, the in-use fault result, the device switching result, and the out-of-use fault result are used as link fault analysis results.

[0019] Optionally, determining a fault condition of the fault information based on the link fault analysis result includes:

[0020] Determine whether there is a fault consistent with the fault information among the output fault result, the in-use fault result and the device switching result of the link fault analysis result;

[0021] If so, determining that the fault condition of the fault information is a real fault;

[0022] If the fault indicated by the output fault result, the in-use fault result and the device switching result is inconsistent with the fault reported by the fault information, it is determined that the fault condition of the fault information is a false alarm fault.

[0023] Optionally, also include:

[0024] If there is a fault consistent with the fault information in the output fault results, the in-use fault results and the device switching results, determining whether the number of faults indicated in the output fault results, the in-use fault results and the device switching results is equal to the number of faults reported in the fault information;

[0025] If it is greater than, determining whether other fault information is received at the fault occurrence time in the fault information;

[0026] If other fault information is received, determining whether the number of faults indicated in the output fault result, the in-use fault result and the device switching result is equal to the number of faults reported in the fault information and the other fault information;

[0027] If it is less than, it is determined that the fault condition of the fault information is a missed report.

[0028] Optionally, also include:

[0029] If the fault information is a non-interruption fault, determining a corresponding output fault result based on the signal association snapshot table and the device general log;

[0030] Determine the in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log;

[0031] The output fault result and the in-use fault result are used as link fault analysis results.

[0032] Optionally, also include:

[0033] If a switching failure reported by the switching cluster is received, a corresponding output failure result is determined based on the signal association snapshot table and the device general log;

[0034] Determine the input fault result within the preset time period corresponding to the fault occurrence time based on the device total log and the signal association relationship snapshot table;

[0035] Using the output fault result and the input fault result as link fault analysis results;

[0036] The fault condition of the switching fault is determined based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

[0037] A second aspect of an embodiment of the present invention shows a fault analysis device, the device comprising:

[0038] The detection unit is used to obtain a signal association relationship snapshot table and a device general log corresponding to the fault information when receiving the fault information reported by the monitoring system;

[0039] An analysis unit, configured to perform fault analysis based on the signal association snapshot table and the device total log to obtain a link fault analysis result;

[0040] A processing unit is used to determine the fault condition of the fault information based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

[0041] A third aspect of an embodiment of the present invention shows an electronic device, which is used to run a program, wherein the program executes the fault analysis method shown in the first aspect of the embodiment of the present invention when running.

[0042] A fourth aspect of an embodiment of the present invention shows a storage medium, which includes a storage program, wherein when the program is running, the device where the storage medium is located is controlled to execute the fault analysis method shown in the first aspect of the embodiment of the present invention.

[0043] Based on the above-mentioned embodiment of the present invention, a fault analysis method, device, electronic device and storage medium are provided. The method includes: if fault information of a fault reported by a monitoring system is received, obtaining a signal association relationship snapshot table and a device general log corresponding to the fault information; performing fault analysis based on the signal association relationship snapshot table and the device general log to obtain a link fault analysis result; determining the fault condition of the fault information based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition. In an embodiment of the present invention, a fault analysis is performed on the link where the video playback stream is located using the signal association relationship snapshot table and the device general log that write the fault to determine the link fault analysis result; then the fault condition of the fault information is analyzed according to the link fault analysis result, thereby improving the accuracy of fault analysis and avoiding possible problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0045] Figure 1 A schematic diagram of a flow chart of a fault analysis method shown in an embodiment of the present invention;

[0046] Figure 2 A schematic diagram of a flow chart of another fault analysis method according to an embodiment of the present invention;

[0047] Figure 3 This is a schematic diagram of an architecture of a real fault shown in an embodiment of the present invention;

[0048] Figure 4 A schematic diagram of the architecture of a false alarm fault shown in an embodiment of the present invention;

[0049] Figure 5 A schematic diagram of an architecture for an underreporting fault according to an embodiment of the present invention;

[0050] Figure 6 A schematic diagram of the architecture of a hidden danger fault shown in an embodiment of the present invention;

[0051] Figure 7 A schematic flow chart of another fault analysis method according to an embodiment of the present invention;

[0052] Figure 8 The present invention is a schematic diagram showing the structure of a fault analysis device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0053] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0054] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0055] It should be noted that the descriptions of "first", "second", etc. in the present invention are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0056] In this application, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0057] See also Figure 1 , is a flow chart of a fault analysis method according to an embodiment of the present invention, the method comprising:

[0058] Step S101: Detect whether the fault information reported by the monitoring system is received. If received, execute step S102; if not, return to continue executing step S101.

[0059] In the process of implementing step S101, it is determined in real time whether fault information reported by monitoring devices set on different input or output devices is received. If received, step S102 is executed; if not, it returns to continue executing step S101.

[0060] It should be noted that the fault information includes the fault ID, fault occurrence time, and fault address.

[0061] Optionally, the fault information and device information of other devices are written into a signal association relationship snapshot table corresponding to the video playback stream.

[0062] It should be noted that the signal association snapshot table of the video playback stream is used to store the main device signal, backup device signal and pad device signal that can be used as input multicast when a fault occurs, and the device signal that can be used as output multicast;

[0063] The signal association snapshot table of the video playback stream is used to store the fault ID when a fault occurs, as well as the main device signal, backup device signal and pad device signal that can be used as input multicast, and the device signal that can be used as output multicast, as well as the in-use relationship of the devices.

[0064] It should be noted that for each video playback stream, each video playback stream corresponds to a signal association relationship snapshot table.

[0065] Each information association relationship table is used to store changes in signals of different devices according to the fault time, as well as the in-use relationship.

[0066] The signal association snapshot table includes the device signals automatically switched by the broadcast control management system, the device signals manually switched, and the device signals recorded during a fault, so that this relationship can be recorded before any adjustment is made. This will help to trace the fault situation later, determine the accuracy of the fault, and have positive significance for emergency handling.

[0067] Input multicast refers to the device inputting the device video playback stream through multicast technology, and output multicast refers to the device outputting the device video playback stream through multicast technology, that is, broadcasting the video.

[0068] Step S102: Obtain a signal association relationship snapshot table and a device general log corresponding to the fault information;

[0069] The equipment total log, namely the fault total data table, includes information such as the fault status signal and switching signal of each equipment.

[0070] In the specific implementation of step S102, after the monitoring system detects a fault, the signal association snapshot table corresponding to the fault and the fault summary table recorded by the intelligent broadcast control management system, ie, the equipment summary log, are first obtained.

[0071] The device total log includes log records of each output multicast, that is, the device, and each input multicast, that is, the entire operation process of the device.

[0072] Step S103: performing fault analysis based on the signal association snapshot table and the device total log to obtain a link fault analysis result;

[0073] It should be noted that the specific implementation process of step S103 is as follows: Figure 2 As shown, the following steps are included:

[0074] Step S201: Determine whether the fault information is a current interruption fault, if so, execute step S202, if not, execute step S206.

[0075] In the process of implementing step S201, it is determined whether there is an interruption in the output signal in the fault information, that is, whether there is an interruption in the video playback stream. If so, it is determined that the current fault is a stream interruption fault, and step S202 is executed; if not, it is determined that the current fault is a non-interruption fault, and step S206 is executed.

[0076] A streaming interruption failure refers to the phenomenon that the video playback stream is interrupted due to various reasons, and the audience will be unable to watch the live video.

[0077] Non-interruption faults refer to other faults in the video playback stream other than the inability to watch the live video, such as the video freezing during playback or no sound.

[0078] Step S202: determining a corresponding output fault result based on the signal association snapshot table and the device general log.

[0079] It should be noted that the specific implementation of step S202 includes the following steps:

[0080] Step S11: query the signal association snapshot table to determine whether the address indicating the output multicast in the signal association snapshot table has an output failure, if yes, execute step S12, if no, execute step S13;

[0081] In the specific implementation of step S11, the signal association snapshot table is queried to first determine the device address as the output multicast, and then the device address is used to traverse the device general log to determine whether there is a field with a fault in the operation field corresponding to the device address within the preset time period corresponding to the fault occurrence time. If so, it indicates that there is a fault in the broadcast of the link where the video playback stream is located, and step 12 is executed. If not, it indicates that there is no output multicast fault in the link where the video playback stream is located, and step S13 is executed;

[0082] It should be noted that the preset time period is set based on multiple experiments or experience, and can generally be one minute before or after the fault occurs.

[0083] Step S12: Determine that the output failure result is that there is a broadcast failure in the playback stream.

[0084] Step S13: Determine that the output fault result is that there is no broadcast fault in the playback stream.

[0085] Step S203: determining the in-use fault results within a preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log.

[0086] It should be noted that the specific implementation of step S203 includes the following steps:

[0087] Step S21: determining the input multicast in use at the time when the fault occurs based on the signal association relationship snapshot table;

[0088] In the specific implementation of step S21, the input multicast signal in the signal association snapshot table is queried to determine the device address of the input multicast in use when the fault occurs.

[0089] Step S22: Determine whether the input multicast in use has a fault within the preset time period corresponding to the fault occurrence time based on the device general log, if yes, execute step S23, if not, execute step S24.

[0090] In the process of implementing step S22, the log field corresponding to the device address of the input multicast in use within the preset time period corresponding to the time when the fault occurred is obtained from the device general log, and it is determined whether there is a field indicating the fault in the log field. If so, the log field indicates that there is a fault in the input multicast in use, and step S23 is executed. If not, it indicates that there is no fault in the output multicast in use, and step S24 is executed.

[0091] The log field refers to the operation log of the device corresponding to the device address.

[0092] Step S23: Determine that the in-use fault result is that the in-use input multicast has a fault.

[0093] In the specific implementation of step S23, it is determined that a fault exists in the input multicast used within a preset time period corresponding to the time when the fault occurs in the link where the video playback stream is located;

[0094] Step S24: Determine that the in-use fault result is that there is no fault in the in-use input multicast.

[0095] In the specific implementation of step S24, it is determined that there is no fault in the input multicast used in the link where the video playback stream is located within the preset time period corresponding to the time when the fault occurs;

[0096] Step S204: determining the device switching result within the preset time period corresponding to the fault occurrence time based on the device general log;

[0097] In the process of implementing step S204, all fields within the preset time period corresponding to the fault occurrence time are obtained from the device general log, and it is determined whether there is a switching field indicating a device switching failure. If so, it is determined that the device switching result is that there is a switching failure. If not, it is determined that the device switching result is that there is no switching failure.

[0098] Optionally, after executing step S204, the method further includes:

[0099] Step S31: Determine whether a non-in-use fault determination is required based on the output fault result and the in-use fault result. If so, execute step S32; if not, execute step S33.

[0100] In the process of implementing step S31, it is determined whether the output fault result is that there is no broadcast fault, whether the in-use fault result is that there is no in-use input multicast fault, and whether the device switching result is that there is no switching. If all of them are yes, execute step S32; if any one of them is no, execute step S205.

[0101] Step S32: determining the non-in-use fault results within a preset time period corresponding to the fault occurrence time based on the equipment general log.

[0102] In the process of implementing step S206, the log field related to the non-in-use device within the preset time period corresponding to the fault occurrence time is obtained from the device general log, and it is determined whether the log field indicates that there is a fault in the non-in-use device. If so, it is determined that the non-in-use fault result is that a fault exists. If not, the non-in-use fault result is that there is no fault.

[0103] Step S33: taking the output fault result, the in-use fault result, the device switching result, and the in-use fault result as the link fault analysis result.

[0104] Step S205: taking the output fault result, the in-use fault result and the device switching result as the link fault analysis result.

[0105] In the process of specifically implementing step S205, the output fault result of whether there is a broadcast fault or not, the in-use fault result of whether there is a fault in the input multicast being used or not, and the device switching result of whether there is a switching fault or not are used as link fault analysis results.

[0106] Step S206: determining a corresponding output fault result based on the signal association snapshot table and the device general log;

[0107] Step S207: determining the in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log;

[0108] It should be noted that the specific implementation process of step S206 to step S207 is the same as the specific implementation process of step S202 and step S203, and they can refer to each other.

[0109] Step S208: taking the output fault result and the in-use fault result as the link fault analysis result.

[0110] In an embodiment of the present invention, if the fault information is a flow interruption fault, the link fault analysis result of the output fault result, the in-use fault result and the equipment switching result is determined through the signal association relationship snapshot table and the device total log; if the fault information is a non-flow interruption fault, the link fault analysis result of the output fault result and the in-use fault result is determined through the signal association relationship snapshot table and the device total log.

[0111] Step S104: determining the fault condition of the fault information based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

[0112] It should be noted that there are different implementation methods according to different link fault analysis results.

[0113] In a first implementation mode, if the link fault analysis result includes an output fault result, an in-use fault result, and a device switching result, the process of specifically implementing step S104 includes the following steps:

[0114] Step S41: Determine whether there is a fault consistent with the fault information in the output fault results, the in-use fault results and the equipment switching results. If there is a fault consistent with the fault information in the output fault results, the in-use fault results and the equipment switching results, execute step S42. Then, obtain the fault signal corresponding to the fault time point of the fault information from the signal association relationship snapshot table. If the fault indicated by the output fault result, the in-use fault result and the equipment switching result is consistent with the fault part indicated by all fault signals, execute step S43; if the fault indicated by the fault information is different from the fault indicated by the link fault analysis result, execute step S44.

[0115] Step S42: determining that the fault condition of the fault information is a real fault, so as to determine whether fault processing is required based on the fault condition;

[0116] Step S43: determining whether the fault condition of the fault information is a real fault or an underreported fault, so as to determine whether fault processing is required based on the fault condition;

[0117] Step S44: determining that the fault condition of the fault information is a false alarm fault, so as to determine whether fault processing is required based on the fault condition.

[0118] Specifically, if the output fault result of the link fault analysis result is that there is a broadcast fault, the in-use fault result is that there is an in-use input multicast fault, and the device switching result is that there is a switching fault, and the faults in the fault information are that there is a broadcast fault, an in-use input multicast fault, and there is a switching fault, it means that there are faults in the link fault analysis result that are consistent with the fault information, such as Figure 3 As shown, it is determined that the fault condition of the fault information is a real fault, that is, step S42 is executed;

[0119] in, Figure 3 In the link fault analysis result shown, the signal of the switching output is red, that is, there is a broadcast fault; and the signal of the main device switched input is also red, that is, there is a fault in the input multicast of the main device in use; when the fault information is a broadcast fault, it means that the link fault analysis result includes the fault indicated by the fault information, indicating that the fault condition of the fault information is a real fault.

[0120] Next, if the output fault result is that there is a broadcast fault, the in-use fault result is that there is no in-use input multicast fault, and the device switching result is that there is a switching fault, at this time, the fault in the fault information is that there is a broadcast fault or a switching fault, it means that the fault condition of the fault information is a real fault; then, obtain the fault signal corresponding to the fault time point of the fault information from the signal association relationship snapshot table. If there is no broadcast fault or switching fault in the faults indicated by all fault signals, it means that the fault condition of the fault information is a missed report, that is, execute step S43.

[0121] If the output fault result is that there is no broadcast fault, the in-use fault result is that there is an in-use input multicast fault, and the device switching result is that there is a switching fault, and the fault in the fault information is an in-use input multicast fault or there is a switching fault, it means that the fault condition of the fault information is a real fault and there is an underreporting, that is, execute step S43.

[0122] If the output fault result is a broadcast fault, the in-use fault result is a non-in-use input multicast fault, and the device switching result is a non-existent switching, and the fault in the fault information is an in-use input multicast fault or a switching, it means that the fault condition of the fault information is a false alarm, that is, step S44 is executed. Figure 4 shown.

[0123] Figure 4 The output fault result described in the link fault analysis result is that there is a broadcast fault, that is, the switching output is red, the in-use fault result is that there is no in-use input multicast fault, and the device switching result is that there is no switching. At this time, if the output fault result described in the fault information is an input multicast failure, it is determined that the fault condition of the fault information is a false alarm fault.

[0124] If the output fault result is that there is no broadcast fault, the in-use fault result is that there is an in-use input multicast fault, and the device switching result is that there is no switching, and the fault in the fault information is an in-use input multicast fault or there is switching, it means that the fault condition of the fault information is a false alarm, that is, execute step S44.

[0125] If the output fault result is a broadcast fault, the in-use fault result is an in-use input multicast fault, and the device switching result is no switching, if the fault in the fault information is neither an in-use input multicast fault nor a broadcast fault, it means that the fault condition of the fault information is a false alarm, and step S44 is executed.

[0126] In order to better understand the existence of underreporting shown above, the following Figure 5 Provide explanation.

[0127] Generally speaking, when the output fault result is that there is a broadcast fault, the in-use fault result is that there is no in-use input multicast fault, and the device switching result is that there is switching; the fault signal corresponding to the fault time point of the fault information is obtained from the signal association relationship snapshot table. If there is no broadcast fault or switching fault in the faults indicated by all fault signals, it means that the fault condition of the fault information is underreported, such as Figure 5 shown.

[0128] In a second implementation manner, if the link fault analysis result includes the output fault result, the in-use fault result, the device switching result, and the out-of-use fault result, the process of specifically implementing step S104 includes:

[0129] Since it is necessary to determine whether both the output fault result and the in-use fault result are fault-free when judging the non-in-use fault result, it is necessary to judge the non-in-use fault result at this time;

[0130] Specifically, it is determined whether the non-in-use fault result is a fault consistent with the fault information. That is, if the non-in-use fault result is that a non-in-use fault exists, and the device switching result is that no switching occurs, and the fault indicated by the fault information is also a non-in-use fault, it is determined that the fault condition of the fault information is a hidden fault, such as Figure 6 shown.

[0131] Figure 6 In the output fault result, there is no broadcast fault, the in-use fault result is no in-use input multicast fault, and the device switching result is no switching, but the signal of the device corresponding to the switching input standby is red, that is, the non-in-use fault result is present; and at this time, the fault indicated by the fault information is also a fault of the device corresponding to the switching input standby, and the fault condition of the fault information is determined to be a hidden fault, such as Figure 6 shown.

[0132] Optionally, if the output fault result is that there is no broadcast fault, the in-use fault result is that there is no in-use input multicast fault, the in-use fault result is that there is a in-use fault, and the device switching result is that there is a switching fault, then the fault in the fault information is that there is a switching fault or a in-use fault, it means that the fault condition of the fault information is a real fault and there is an underreporting, that is, execute step S43.

[0133] Based on the first embodiment and the second embodiment shown above, the specific process of implementing step S104 can be illustrated as shown in Table (1).

[0134] Table (1):

[0135]

[0136] Among them, hidden danger failure refers to the existence of interruption when not in use, no interruption when broadcasting, and no interruption when in use; when the fault is reported, the multicast is not in use, and there is no fault in broadcasting.

[0137] A real failure refers to a broadcast failure or an in-use failure, and a switch occurs within one minute before or after; if the output multicast is disconnected, a switch occurs within one minute before or after; if it is an in-use failure, a switch occurs within one minute before or after.

[0138] A false alarm means that a failure occurred during broadcast, but no failure occurred one minute before or after use, and no switching occurred; a failure occurred during use, but no failure occurred one minute before or after broadcast, and no switching occurred; a failure occurred during broadcast, but a failure occurred one minute before or after use, and no switching occurred; a failure occurred during use, but a failure occurred one minute before or after broadcast, and no switching occurred.

[0139] A missed alarm means that a switch occurs, but no fault is detected one minute before or after the broadcast / in use.

[0140] It should be noted that the one minute before and after refers to a preset time period set according to actual conditions.

[0141] In a third implementation manner, if the link fault analysis result includes the output fault result and the in-use fault result, the process of specifically implementing step S104 includes:

[0142] Step S51: Determine whether there is a fault consistent with the fault information in the output fault result and the in-use fault result. If there is a fault consistent with the fault information in the output fault result and the in-use fault result, execute step S52. If the fault indicated by the output fault result and the in-use fault result is different from the fault reported by the fault information, execute step S53 to obtain the fault signal corresponding to the fault time point of the fault information from the signal association snapshot table. If the faults indicated by all fault signals are less than the faults indicated by the link fault analysis result, it means that the fault condition of the fault information is underreported, and execute step S54.

[0143] It should be noted that the specific implementation process of the specific implementation step S51 is the same as the specific implementation process of the above-mentioned specific implementation step S41, and they can refer to each other.

[0144] Specifically, if the output fault result is a broadcast fault, and the in-use fault result is an in-use input multicast fault, when the fault in the fault information is a broadcast fault or an in-use input multicast fault, it means that the fault condition of the fault information is a real fault, and step S52 is executed.

[0145] If the output fault result is that there is a broadcast fault, and the in-use fault result is that there is no in-use input multicast fault, then the fault signal corresponding to the fault time point of the fault information is obtained in the signal association snapshot table. If the faults indicated by all fault signals do not involve a broadcast fault, it indicates that the fault condition of the fault information is a missed report fault, and step S53 is executed.

[0146] If the output fault result is that there is no broadcast fault, and the in-use fault result is that there is an in-use input multicast fault, and the fault in the fault information is that there is no in-use input multicast fault, it means that the fault condition of the fault information is a false alarm fault, and then execute step S54.

[0147] Step S52: Determine whether the fault condition of the fault information is a real fault;

[0148] Step S53: determining that the fault condition of the fault information is a missed reporting fault;

[0149] Step S54: Determine that the fault condition of the fault information is a false alarm fault.

[0150] Optionally, it is also possible to determine whether the fault information contains a hidden fault by using the second implementation method described above.

[0151] Specifically, determine whether the non-in-use fault result has a fault that is consistent with the fault information. That is, if the non-in-use fault result is that there is a non-in-use fault, and the fault indicated by the fault information is also a non-in-use fault, determine that the fault condition of the fault information is a hidden danger fault.

[0152] Based on the third implementation mode shown above, the specific process of implementing step S104 can be illustrated as shown in Table (2).

[0153] Table (2):

[0154]

[0155] Among them, hidden danger failure means that there is no failure in broadcasting, no failure in use, and failure in non-use. (When the failure is reported, the multicast is not in use and there is no failure in broadcasting);

[0156] A real fault refers to a broadcast fault and an active fault. (If it is not an output fault, the multicast is in use and there is no output fault within one minute before and after; if it is an output fault, it is in use within one minute before and after);

[0157] False alarm means that only one of the broadcast and in-use is faulty. (When the broadcast / in-use fails, the other one does not fail within one minute before and after.

[0158] In an embodiment of the present invention, a fault analysis is performed on the link where the video playback stream is located using a signal association snapshot table written into the fault and the device general log to determine a link fault analysis result; then the fault condition of the fault information is analyzed based on the link fault analysis result, thereby improving the accuracy of the fault analysis and avoiding possible problems.

[0159] In order to better understand the method shown in the above embodiment of the present invention, an example is used below to illustrate.

[0160] If the fault information A reported by the monitoring system at time xx is received, the in-use device signal, device fault signal, etc. indicated in the fault information A are written into the signal association snapshot table a.

[0161] When it is determined that the fault information A is a flow interruption fault, the signal association relationship snapshot table a is queried to determine that the fault address corresponding to the fault information A is an output multicast.

[0162] Next, the output multicast address is determined using the signal association snapshot table a, and it is determined from the device general log that the output multicast address has a fault within a preset time period corresponding to the fault occurrence time, which means that the output fault result is a broadcast fault;

[0163] Then, the address of the input multicast in use is determined by using the signal association snapshot table a; based on the address of the input multicast in use, the corresponding log field in the preset time period corresponding to the fault occurrence time is obtained from the device general log, and it is determined whether there is a field indicating a fault in the log field. If so, it indicates that there is an input multicast fault in use in the link fault analysis result, that is, the fault result in use is that the input multicast in use has a fault;

[0164] Next, all fields within a preset time period corresponding to the fault occurrence time are obtained from the device general log, and it is determined whether there is a switching field indicating a device switching fault. If so, it is determined that the device switching result is that there is a switching fault.

[0165] Based on this, it is determined that the output fault result in the link fault analysis result is that there is a broadcast fault, the in-use fault result is that there is an in-use input multicast fault, and the device switching result is that there is a switching fault; based on the above, it is determined that the fault information A is a broadcast fault, that is, the fault information A is a real fault.

[0166] In an embodiment of the present invention, a fault analysis is performed on the link where the video playback stream is located using a signal association snapshot table written into the fault and the device general log to determine a link fault analysis result; then the fault condition of the fault information is analyzed based on the link fault analysis result, thereby improving the accuracy of the fault analysis and avoiding possible problems.

[0167] Based on the method shown in the above embodiment of the present invention, accordingly, the embodiment of the present invention shows another fault analysis method, such as Figure 7 As shown, the method includes:

[0168] Step S701: Detect whether a switching fault reported by a switching cluster is received. If a switching fault reported by a switching cluster is received, execute step S702; if not, execute step S701 again.

[0169] In the process of implementing step S701, it is determined in real time whether a switching fault reported by the switching cluster is received. If the switching fault reported by the switching cluster is received, step S702 is executed; if not, step S701 is executed again.

[0170] It should be noted that a switching failure refers to a failure that occurs during the device switching process.

[0171] Optionally, the fault information of the switching fault and the device information of other devices are written into a signal association relationship snapshot table corresponding to the video playback stream.

[0172] Step S702: determining a corresponding output fault result based on the signal association snapshot table and the device general log;

[0173] In the process of specifically implementing step S702, first obtain the signal association relationship snapshot table and the device total log corresponding to the fault information, query the signal association relationship snapshot table to determine the device address of the output multicast; use the device address to traverse the device total log to determine the signal change in the first time before and after the output from the device total log, so as to determine whether the signal corresponding to the output multicast is a fault signal. If it is a fault signal, it means that there is a fault in the broadcast, and the output fault result is determined to be that there is a broadcast fault in the playback stream. If not, it means that there is no output multicast fault at present, and the output fault result is determined to be that there is no broadcast fault in the playback stream.

[0174] Step S703: determining the input fault result within the preset time period corresponding to the fault occurrence time based on the device total log and the signal association relationship snapshot table;

[0175] In the process of specifically implementing step 703, the signal association snapshot table is queried to determine the device address of the input multicast; the device total log is traversed using the device address, and whether the input multicast signal within the preset time period corresponding to the time when the switching fault occurs is a fault signal is obtained from the device total log; if so, it is determined that the input fault result is that the input multicast has a fault; if not, it is determined that the input fault result is that the input multicast has no fault.

[0176] Step S704: using the output fault result and the input fault result as the link fault analysis result;

[0177] Step S705: Determine the fault condition of the switching fault based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

[0178] In the process of specifically implementing step S705, if the output fault result is a broadcast fault and the input fault result is an input multicast fault, it means that the switching fault reported by the fault in the switching fault is a real fault, that is, it is determined that the fault condition of the switching fault is a real fault.

[0179] Optionally, the monitored system has also reported the corresponding fault, and the duplicate logic is not processed.

[0180] If the output fault result is that there is a broadcast fault, and the input fault result is that there is no input multicast fault, it is determined that the fault condition of the switching fault is a real fault and a missed report.

[0181] If the output fault result is that there is no broadcast fault, and the input fault result is that there is an input multicast fault, it is determined that the fault condition of the switching fault is a real fault and a missed report.

[0182] If the output fault result is that there is no broadcast fault, and the input fault result is that there is no input multicast fault, it is determined that the fault condition of the switching fault is a real fault and a missed report.

[0183] In an embodiment of the present invention, when a device switches, if a switch reported by a switching cluster is detected, the device general log of the corresponding video playback stream is first obtained; then, a fault analysis is performed on the link where the video playback stream is located through a signal association relationship snapshot table to determine the fault condition of the switching fault; thereby improving the accuracy of the fault analysis and avoiding possible problems.

[0184] Based on the fault analysis method shown in the embodiment of the present invention, correspondingly, the flow chart of the fault analysis device shown in the embodiment of the present invention is as follows: Figure 8 As shown, the device comprises:

[0185] The detection unit 801 is used to obtain a signal association relationship snapshot table and a device general log corresponding to the fault information when receiving the fault information reported by the monitoring system;

[0186] An analysis unit 802 is used to perform fault analysis based on the signal association relationship snapshot table and the device total log to obtain a link fault analysis result;

[0187] The processing unit 803 is configured to determine a fault condition of the fault information based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

[0188] The specific principles and execution processes of each unit in the fault analysis device disclosed in the above embodiment of the present invention are the same as the corresponding contents in the fault analysis method provided in the above embodiment of the present invention. Please refer to the corresponding parts of the fault analysis method disclosed in the above embodiment of the present invention, and will not be repeated here.

[0189] In an embodiment of the present invention, a fault analysis is performed on the link where the video playback stream is located using a signal association snapshot table written into the fault and the device general log to determine a link fault analysis result; then the fault condition of the fault information is analyzed based on the link fault analysis result, thereby improving the accuracy of the fault analysis and avoiding possible problems.

[0190] Optionally, based on the fault analysis device shown in the above embodiment of the present invention, the analysis unit 802 is specifically configured to:

[0191] If the fault information is a flow interruption fault, determining a corresponding output fault result based on the signal association relationship snapshot table and the device general log;

[0192] Determine the in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log;

[0193] Determine the device switching result within a preset time period corresponding to the fault occurrence time based on the device general log;

[0194] The output fault result, the in-use fault result and the device switching result are used as the link fault analysis result.

[0195] Optionally, based on the fault analysis device shown in the above embodiment of the present invention, the analysis unit 802 is further configured to:

[0196] Determine whether a non-in-use fault determination is required based on the output fault result, the in-use fault result and the device switching result;

[0197] If so, determining the non-in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log;

[0198] The output fault result, the in-use fault result, the device switching result, and the out-of-use fault result are used as link fault analysis results.

[0199] Optionally, based on the fault analysis device shown in the above embodiment of the present invention, the processing unit 803 is specifically configured to:

[0200] Determine whether there is a fault consistent with the fault information among the output fault result, the in-use fault result and the device switching result of the link fault analysis result;

[0201] If so, determining that the fault condition of the fault information is a real fault;

[0202] If the fault indicated by the output fault result, the in-use fault result and the device switching result is inconsistent with the fault reported by the fault information, it is determined that the fault condition of the fault information is a false alarm fault.

[0203] Optionally, based on the fault analysis device shown in the above embodiment of the present invention, the processing unit 803 is further configured to:

[0204] If there is a fault consistent with the fault information in the output fault results, the in-use fault results and the device switching results, determining whether the number of faults indicated in the output fault results, the in-use fault results and the device switching results is equal to the number of faults reported in the fault information;

[0205] If it is greater than, determining whether other fault information is received at the fault occurrence time in the fault information;

[0206] If other fault information is received, determining whether the number of faults indicated in the output fault result, the in-use fault result and the device switching result is equal to the number of faults reported in the fault information and the other fault information;

[0207] If it is less than, it is determined that the fault condition of the fault information is a missed report.

[0208] Optionally, based on the fault analysis device shown in the above embodiment of the present invention, the analysis unit 802 is further configured to:

[0209] If the fault information is a non-interruption fault, determining a corresponding output fault result based on the signal association snapshot table and the device general log;

[0210] Determine the in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log;

[0211] The output fault result and the in-use fault result are used as link fault analysis results.

[0212] Optionally, based on the fault analysis device shown in the above embodiment of the present invention, the analysis unit 802 is further configured to:

[0213] If a switching failure reported by the switching cluster is received, a corresponding output failure result is determined based on the signal association snapshot table and the device total log;

[0214] Determine the input fault result within the preset time period corresponding to the fault occurrence time based on the device total log and the signal association relationship snapshot table;

[0215] Using the output fault result and the input fault result as link fault analysis results;

[0216] Accordingly, the processing unit 803 is further configured to:

[0217] The fault condition of the switching fault is determined based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

[0218] An embodiment of the present application provides an electronic device, which includes a processor and a memory, wherein the memory is used to store fault analysis program code and data, and the processor is used to call program instructions in the memory to execute the steps shown in the fault analysis method in the above embodiment.

[0219] An embodiment of the present invention provides a storage medium, which includes the electronic device provided by the above-mentioned embodiment of the present application, and the electronic device is used to execute the fault analysis method disclosed in the embodiment of the present application.

[0220] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.

[0221] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0222] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A fault analysis method, characterized in that: The method comprises: If fault information of a fault reported by the monitoring system is received, a signal association snapshot table and a device general log corresponding to the fault information are obtained; Performing fault analysis based on the signal association snapshot table and the device total log to obtain a link fault analysis result; The fault condition of the fault information is determined based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

2. The method according to claim 1, characterized in that: Performing fault analysis based on the signal association snapshot table and the device total log to obtain a link fault analysis result includes: If the fault information is a flow interruption fault, determining a corresponding output fault result based on the signal association relationship snapshot table and the device general log; Determine the in-use fault result within a preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log; Determine the device switching result within a preset time period corresponding to the fault occurrence time based on the device general log; The output fault result, the in-use fault result and the device switching result are used as the link fault analysis result.

3. The method according to claim 2, characterized in that Also includes: Determine whether a non-in-use fault determination is required based on the output fault result, the in-use fault result and the device switching result; If so, determining the non-in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log; The output fault result, the in-use fault result, the device switching result, and the out-of-use fault result are used as link fault analysis results.

4. The method according to claim 1, characterized in that: Determining the fault condition of the fault information based on the link fault analysis result includes: Determine whether there is a fault consistent with the fault information among the output fault result, the in-use fault result and the device switching result of the link fault analysis result; If so, determining that the fault condition of the fault information is a real fault; If the fault indicated by the output fault result, the in-use fault result and the device switching result is inconsistent with the fault reported by the fault information, it is determined that the fault condition of the fault information is a false alarm fault.

5. The method according to claim 4, characterized in that Also includes: If there is a fault consistent with the fault information in the output fault results, the in-use fault results and the device switching results, determining whether the number of faults indicated in the output fault results, the in-use fault results and the device switching results is equal to the number of faults reported in the fault information; If it is greater than, determining whether other fault information is received at the fault occurrence time in the fault information; If other fault information is received, determining whether the number of faults indicated in the output fault result, the in-use fault result and the device switching result is equal to the number of faults reported in the fault information and the other fault information; If it is less than, it is determined that the fault condition of the fault information is a missed report.

6. The method according to claim 2, characterized in that Also includes: If the fault information is a non-interruption fault, determining a corresponding output fault result based on the signal association snapshot table and the device general log; Determine the in-use fault result within the preset time period corresponding to the fault occurrence time based on the signal association relationship snapshot table and the device general log; The output fault result and the in-use fault result are used as link fault analysis results.

7. The method according to claim 1, characterized in that Also includes: If a switching failure reported by the switching cluster is received, a corresponding output failure result is determined based on the signal association snapshot table and the device total log; Determine the input fault result within the preset time period corresponding to the fault occurrence time based on the device total log and the signal association relationship snapshot table; Using the output fault result and the input fault result as link fault analysis results; The fault condition of the switching fault is determined based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

8. A fault analysis device, characterized in that: The device comprises: The detection unit is used to obtain a signal association relationship snapshot table and a device general log corresponding to the fault information when receiving the fault information reported by the monitoring system; An analysis unit, configured to perform fault analysis based on the signal association snapshot table and the device total log to obtain a link fault analysis result; A processing unit is used to determine the fault condition of the fault information based on the link fault analysis result, so as to determine whether fault processing is required based on the fault condition.

9. An electronic device, characterized in that: The electronic device is used to run a program, wherein the program, when running, executes the fault analysis method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium includes a storage program, wherein when the program is running, the device where the storage medium is located is controlled to execute the fault analysis method according to any one of claims 1 to 7.

Images