Communication methods and related devices

Abstract

This application provides a communication method and related apparatus. The communication method includes: acquiring fault information of a preset fault within a first time window; wherein the first time window is a time window used to monitor the preset fault, and the preset fault is a fault of the same monitored object in the communication device; determining at least one second time based on multiple first times included in the fault information; wherein the first time is the time when the preset fault switches between the state of generation and recovery, and the second time is the first time of the target fault, which is included in the preset fault; determining a second time window based on at least one second time; wherein the second time window is a time window used to monitor the oscillation alarm of the target fault, and the more second times there are, the shorter the length of the second time window. This application can improve the reliability of alarming for faults in communication devices.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and related apparatus. Background Technology

[0002] Communication equipment (such as base stations) may malfunction during operation. Fault states include fault occurrence or fault recovery (return to normal). Alarms will be triggered when a fault occurs or when a fault is recovered. Frequent occurrences or recovery of the same fault within a short period of time will trigger frequent alarms; these alarms are called oscillation alarms.

[0003] To avoid interference with normal maintenance of communication equipment due to oscillation alarms, an alarm can be delayed until a fault occurs or is resolved. If frequent faults occur during this waiting period, an alarm is generated; otherwise, the alarm is deactivated. The waiting time is a pre-configured fixed duration. However, for fault occurrences, an excessively long fixed duration can lead to unexpected alarms, while an excessively short duration may result in delayed alarm generation. For fault recovery, an excessively long fixed duration slows down alarm recovery, while an excessively short duration leads to frequent alarm recovery, resulting in oscillation alarms.

[0004] Therefore, monitoring oscillation alarms based on fault status over a fixed period of time is still not conducive to fault maintenance of communication equipment, and this method of monitoring oscillation alarms has poor reliability. Summary of the Invention

[0005] This application provides a communication method and related apparatus, which aims to improve the reliability of alarm monitoring for faults in communication equipment.

[0006] The first aspect of this application provides a communication method that can be executed by a control device. The control device executes the communication method to issue an alarm for a fault in the communication device. The control device and the communication device can be the same device or different devices. For example, if the communication device is a base station, the control device can be a base station master control device built into the base station. The base station master control device monitors its own various operating states and issues an alarm upon detecting a fault. Alternatively, if the communication device is a network device such as a switch or router, the control device can be a network management system (NMS) connecting these network devices. The network devices send runtime data to the NMS via a communication protocol, and the NMS detects faults and issues alarms based on this data. The control device may include components such as a processor, memory, and a communication interface. The processor can be used to execute programs to implement the communication method, the memory can be used to store programs required by the processor, and the communication interface can communicate with other components or devices to collect fault data or issue alarm information. Based on this structure, the control device can be a device other than those described above, and is not limited thereto.

[0007] In a first aspect of this application, the communication method includes: acquiring fault information of a preset fault within a first time window; wherein the first time window is a time window used to monitor the preset fault, and the preset fault is a fault of the same monitored object in the communication device; determining at least one second time based on multiple first times included in the fault information; wherein the first time is the time when the preset fault switches between the state of generation and recovery, and the second time is the first time of the target fault, which is included in the preset fault; determining a second time window based on at least one second time; wherein the second time window is a time window used to monitor the oscillation alarm of the target fault, and the more second times there are, the shorter the length of the second time window.

[0008] To monitor communication equipment faults, a monitoring period (time window) can be set. To determine fault patterns, faults in the communication equipment can be monitored and statistically analyzed within a certain period (the first time window). Communication equipment contains different functional units, each of which may experience faults. Due to differences in function, the fault patterns of each functional unit differ. Different functional units can be treated as independent monitoring objects, and faults in the same monitoring object can be categorized into a preset fault. Within the first time window, one or more preset faults can be monitored. The fault states of preset faults include "fault occurrence" and "fault recovery." Fault occurrence refers to the state where the fault has just occurred or continues to exist, while fault recovery refers to the instant the fault disappears or the normal state after recovery. The state switches between fault occurrence and fault recovery. For example, after a monitored object experiences a fault, it changes to fault recovery after a period of time, or after fault recovery, it changes back to fault occurrence after a period of time. Faults in some monitored objects may occur multiple times and disappear spontaneously, causing the preset faults to switch between "fault occurrence" and "fault recovery."

[0009] Fault information includes the immediate events during the transition between fault occurrence and recovery. Additionally, fault information may include identification information used to identify which pre-defined fault it is. For example, the base station's power module, used for power supply, may experience a pre-defined fault of power instability. The fault identifier, such as X, could identify this power instability fault. The number of pre-defined faults can be one or more. If there is only one, this single pre-defined fault can be designated as the target fault. If there are multiple pre-defined faults, the target fault can be selected from them. For instance, if a particular pre-defined fault has a high number of occurrences in the immediate event, it suggests that the fault may be frequent and could be designated as the target fault. Alternatively, for a given pre-defined fault, historical data suggests that the fault is likely to occur frequently, and its identifier information can be used to directly designate it as the target fault. Another approach is to combine other information, such as priority, to determine the target fault. Some faults may have extremely high priority, crucial to the operation of communication equipment, requiring immediate alarm upon occurrence without needing to monitor whether certain conditions are met. In such cases, these faults can be excluded, and only lower-priority faults can be selected as the target faults. Other methods can also be used to determine the target fault, which are not limited here.

[0010] The number of target faults can be one or more, and each target fault has a corresponding second time window. The second time windows corresponding to different target faults can be the same or different. The number of first time periods included in the fault information is multiple and corresponds to preset faults. After determining the target fault, the second time period corresponding to the target fault is determined from the multiple first time periods. Within the first time window, a large number of second time periods indicates that the target fault occurs or recovers frequently, and the time required for multiple fault occurrences or recoveries is relatively short. This means that when monitoring the target fault in the future, it should be assumed that multiple faults will occur in a short period of time, and the monitoring time window should be short, i.e., the length of the second time window is small. Conversely, if the number of second time periods within the first time window is small, it indicates that the target fault occurs or recovers infrequently. When monitoring in the future, it should be assumed that multiple faults will occur in a longer period of time, and the length of the second time window is large. In addition, it can also be understood that the length of the second time window is negatively correlated with the number of second time periods, to reflect the actual fault occurrence pattern of the target fault within the first time window.

[0011] In the first aspect mentioned above, the time it takes for the target fault to switch between fault occurrence and fault recovery within a certain period of time (the first time window) reflects the actual pattern of the target fault changing state over a certain period of time. The length of the monitoring time window (the second time window) that is related to the number of the second time is determined. Compared with the fixed time window, the second time window dynamically and flexibly matches the occurrence pattern of the target fault over a period of time. When the second time window is used to monitor the target fault oscillation alarm, it can issue an alarm at an appropriate time, which is conducive to identifying the target fault at an appropriate time. This is further beneficial to the maintenance of communication equipment and can improve the reliability of the alarm.

[0012] In one possible implementation, the target fault is a preset fault that satisfies at least one of the following conditions: the time interval between two consecutive occurrences or recovery of the preset fault is within a first interval; wherein, the first interval is the periodic range of faults that are periodically generated or recovered; the number of times the preset fault switches states is greater than or equal to a first preset number; wherein, the first preset number indicates the number of times the preset fault frequently switches states; or, the total duration accumulated after multiple state switches of the preset fault is greater than or equal to a first preset time; wherein, the first preset time indicates the time accumulated after frequent state switches of the preset fault.

[0013] The time interval between two consecutive occurrences of a preset fault indicates the time required for the preset fault to recur after one occurrence. For preset faults that occur regularly, the time required for each recurrence is stable and falls within a certain range. In this case, it can be assumed that the preset fault will continue to recur stably in the future. Similarly, the time interval between two consecutive recovery periods of a preset fault indicates the time required for the preset fault to recover again after a certain recovery. For preset faults that recover regularly, the time required for each repeated recovery is also stable and falls within a certain range. Fault occurrence or recovery may be periodic, and the period of each recovery is basically consistent. Considering the error range, a certain periodic range group can be set as the first interval. When the period of preset fault reproduction falls within this periodic range, it can be determined that the reproduction of the preset fault has periodic characteristics. Preset faults with periodic characteristics will stably reproduce within the second time window when monitored according to the second time window, so that the second time window can accurately match the reproduction pattern of the fault.

[0014] If a preset fault occurs frequently within the first time window, it indicates that the preset fault occurs frequently over a period of time, which may not be a normal fault state. A certain threshold (first preset number of occurrences) can be set to indicate the number of times the preset fault needs to frequently switch states. This number can be calibrated based on actual testing. Different first preset numbers can be set for different preset faults, or the same first preset number can be set. After a preset fault occurs multiple times within the first time window, its cumulative duration increases. The first preset time can also be set according to the cumulative fault duration when the preset fault frequently switches states to determine the frequent switching state of the preset fault. The conditions for determining the target fault can be one or more of the above conditions. When there are more conditions, the determined target fault is more regular or intermittent. When there are fewer conditions, it is possible to monitor for oscillation alarms for a wider range of target faults.

[0015] In this possible implementation, by setting certain conditions, it is possible to further pinpoint the target fault that needs to be monitored for oscillation alarms, so as to monitor alarms in a targeted manner.

[0016] In one possible implementation, the first interval is the fluctuation range of the time interval between two adjacent preset fault switching states.

[0017] The pre-defined periodic range for fault recurrence can be determined by referring to the fluctuation range of each recurrence of the pre-defined fault. For example, based on the time interval between two adjacent fault occurrences, fluctuation parameters such as standard deviation or variance can be determined. Based on these fluctuation parameters and the error range, the fluctuation range can be determined, and a first interval can be set based on this fluctuation range. This allows for the determination of the periodic range based on the actual state of the pre-defined fault within the first time window, better reflecting its periodic recurrence pattern over a period of time, improving the accuracy of the first interval, and further ensuring the determination of the target...

[0018] In one possible implementation, the second time window includes a fault occurrence time window or a fault recovery time window. After determining the second time window based on at least one second time, the method further includes: generating alarm occurrence information if the target fault meets the alarm occurrence conditions within the fault occurrence time window; and / or generating alarm recovery information if the target fault meets the alarm recovery conditions within the fault recovery time window.

[0019] The oscillation alarm condition is set to avoid oscillation alarms. If the alarm condition is not met within the second time window, no alarm is issued, thus delaying the alarm. Once the oscillation alarm condition is met, an alarm is issued promptly to facilitate timely maintenance. In other words, an alarm is generated promptly when the alarm reporting condition is met; when the oscillation alarm condition is met, oscillation is suppressed by combining it with the fault recovery time window. By combining the second time within the first time window of the target fault, the second time window is determined to conform to the actual pattern of the target fault over a period of time. Compared to monitoring the target fault within a fixed duration, this avoids alarm oscillations and ensures timely alarms for both fault occurrence and recovery.

[0020] For both fault occurrence and fault recovery scenarios, corresponding alarm information needs to be generated, namely alarm generation information (alarm information indicating fault occurrence) and alarm recovery information (alarm information indicating fault recovery). The time windows for monitoring fault occurrence (fault occurrence time window) and fault recovery (fault recovery time window) are different. Each time window has a start time and an end time, describing when monitoring begins and ends, respectively. Preset faults that recur before monitoring begins or after monitoring ends are not considered within the time window. Within the fault occurrence time window, if a fault occurs and certain conditions are met (alarm generation conditions), alarm generation information is generated. If the fault is detected meeting certain conditions before the fault occurrence time window, monitoring can be terminated early, and an alarm can be issued promptly. Within the fault recovery time window, if a fault meets certain conditions (alarm recovery time), alarm recovery information is generated. The second time window (alarm generation time window or alarm recovery time window) can be a sliding window, which is a dynamically moving time range. As time progresses, the start and end times of the second time window move forward simultaneously, creating a "sliding" effect. During the sliding process, the length of the second time window remains constant. In different implementations, monitoring can be performed only on fault occurrence, only on fault recovery, or simultaneously on both.

[0021] In this possible implementation, the occurrence and / or recovery of the fault can be monitored within the corresponding time window so as to issue an alarm at the appropriate time for the specific stage of the fault.

[0022] In one possible implementation, there are multiple second times. Determining a second time window based on at least one second time includes: determining a first generation time and a first recovery time from the multiple second times; wherein the first generation time is the time when the target fault occurs, the first recovery time is the time when the target fault is recovered after the first generation time, and a preset number of target faults are spaced between the first generation time and the first recovery time, the preset number being the number of faults indicating that the target fault occurs frequently; and determining a fault generation time window based on the time interval between the first generation time and the first recovery time.

[0023] The fault occurrence time window indicates when to begin monitoring for fault occurrence and when to appropriately end monitoring. Alarm information is generated only when the target fault within the fault occurrence time window meets the alarm generation conditions; target faults outside the fault occurrence time window are not considered. There are multiple second times corresponding to the target fault, including the fault occurrence time (or the time point from no fault to faulty) and the fault recovery time (or the time point from faulty to fault-free). Any fault occurrence time from among the multiple second times can be taken as the first occurrence time, and the first recovery time is determined from the fault recovery time after the first occurrence time (i.e., later than the first occurrence time). The interval between the first occurrence time and the first recovery time can be used as the length of the second time window, or the length of the second time window can be slightly larger than this interval. The closer the first occurrence time and the first recovery time are temporally, the shorter the length of the second time window, and the fewer target faults may be detected within this time window. Conversely, the farther apart the first occurrence time and the first recovery time are temporally, the longer the length of the second time window, and the more target faults may be detected within this time window. To accurately reflect the frequent occurrence of target faults within the second time window, the number of faults occurring frequently (a preset number) is used as a reference. After the first occurrence time, the first recovery time is determined after an interval of this preset number of target faults. Here, the number of faults refers to the number of times a target fault occurs; each occurrence and recovery of a target fault is considered one fault. Different target faults can correspond to different preset numbers, or they can correspond to the same preset number. The standard for frequent occurrence is not limited here and can be set in conjunction with factors such as fault tolerance, fault severity, and priority. For example, faults with low tolerance, high severity, or high priority occurring in small numbers are considered frequent occurrences, while faults with high tolerance, low severity, or low priority occurring in relatively large numbers are also considered frequent occurrences.

[0024] In this possible implementation, the number of times the target fault occurs frequently is used as a preset number. Within the second time window, a preset number of target faults are spaced out. Based on this second time window, after the fault monitoring starts, the fault monitoring will end when the duration corresponding to the number of frequently occurring faults is reached. This allows for fault monitoring within a suitable time frame, improving the accuracy of the fault occurrence time window.

[0025] In one possible implementation, the alarm generation conditions include at least one of the following conditions: the number of times the target fault switches states is greater than or equal to a second preset number; wherein the second preset number indicates the number of times the target fault occurs frequently; the total duration accumulated after the target fault occurs multiple times is greater than or equal to a second preset time; wherein the second preset time indicates the cumulative duration of the target fault occurring frequently.

[0026] Alarm generation conditions define the prerequisites under which an alarm will be generated to indicate the occurrence of a target fault. If these prerequisites are not met, no alarm will be generated. The prerequisite primarily refers to the frequent occurrence of the target fault. To measure the frequency of target fault occurrence, a second preset number of occurrences or a second preset time can be set. The number of target fault state transitions refers to the number of times the target fault transitions from fault occurrence to fault recovery, or from fault recovery to fault occurrence, or the sum of both. Different implementations can be used as the number of target fault state transitions, and a corresponding second preset number of occurrences can be set. The cumulative duration of frequent target fault occurrences refers to the sum of the lengths of the time periods after the target fault occurs (i.e., excluding the time for recovery). By setting the above alarm generation conditions, the frequency of target fault occurrences can be accurately measured, and alarms can be generated at appropriate times.

[0027] In one possible implementation, there are multiple second times. Determining a second time window based on at least one second time includes: determining a second generation time and a second recovery time from the multiple second times; wherein the second generation time is the time when the target fault occurs, the second recovery time is the recovery time of the target fault adjacent to the second generation time, the time interval between the second generation time and the second recovery time is greater than or equal to a target time interval, and the target time interval is the time interval between any two adjacent target faults within the second time window; and determining a fault recovery time window based on the time interval between the second generation time and the second recovery time.

[0028] The fault recovery time window indicates when monitoring begins upon fault recovery and when it ends. The start time of monitoring within the fault recovery time window is the point in time when a fault recovers (the point from fault occurrence to fault recovery), and the end time depends on the length of the fault recovery time window. The length of the fault recovery time window can be determined based on the interval between the second occurrence time and the second recovery time. The second occurrence time is the time when the target fault occurs, and the second recovery time is the time of the previous recovery of the target fault, adjacent to the time of its occurrence. The interval between the second occurrence time and the second recovery time reflects the time interval between the occurrence and recurrence of the target fault after a recovery. Within the first time window, the target fault occurs and recovers multiple times, and the time interval between each recovery and recurrence may vary. To ensure the second time window is long enough to cover the time between each recovery and the next occurrence of the target fault within the first time window, thus enabling determination of whether the target fault will recur over a longer period, the time interval between the second occurrence time and the second recovery time is greater than or equal to the time interval between any two adjacent target faults within the second time window. In other words, the first time window contains multiple intervals (the interval between the recovery time and the next generation time), and the time interval between the second generation time and the second recovery time is the largest of these. The length of the time interval between the second generation time and the second recovery time can be directly used as the fault recovery time window. Alternatively, the fault recovery time window can be slightly larger than this time interval.

[0029] In this possible implementation, the fault recovery time window is determined based on the second generation time and the second recovery time. The interval between the second generation time and the second recovery time is greater than or equal to the time interval between any two adjacent target faults within the first time window. This allows the fault recovery time window to reflect the longest time required for the target fault to recur after recovery within the first time window. When monitoring whether the fault recovery conditions are met based on the fault recovery time window, the time window can accurately reflect the time from fault recovery to recurrence, and further issue an alarm at an appropriate time.

[0030] In one possible implementation, the alarm recovery conditions include: no target fault occurs within the fault recovery time window.

[0031] If the target fault does not occur within the fault recovery time window, it means the fault has likely stabilized and recovered. In this case, the alarm recovery conditions are met, and an alarm message indicating fault recovery can be generated. If the target fault occurs again within the fault recovery time window, it indicates the fault is still occurring intermittently, and alarm recovery cannot be initiated at this time. This method allows for precise timing of alarm recovery message generation, providing timely indication that the fault has disappeared.

[0032] In one possible implementation, if the target fault meets the alarm recovery conditions within the fault recovery time window, before generating alarm recovery information, the method further includes: if a repair operation of the target fault is detected within the fault recovery time window, then the fault recovery time window is updated to a preset time window; wherein the length of the preset time window is less than the length of the fault recovery time window.

[0033] After a fault is resolved, it may recur shortly. Therefore, monitoring is performed within the fault recovery time window after recovery, and an alarm is generated if fault recovery is confirmed. However, an exception is if a repair operation is detected within the fault recovery time window, indicating that the communication equipment has been repaired by maintenance personnel, potentially fixing the target fault. In cases where the target fault is fixed, the probability of recurrence in a short period is low. To promptly indicate fault recovery, the fault recovery time window can be set to a shorter preset time window. The start monitoring time of the preset time window is the point from fault occurrence to fault recovery, and the end monitoring time depends on the length of the preset time window. This allows for earlier alarm recovery and improves alarm accuracy.

[0034] A second aspect of this application provides a communication device, comprising: an acquisition module, configured to acquire fault information of a preset fault within a first time window; wherein the first time window is a time window for monitoring the preset fault, and the preset fault is a fault of the same monitored object in the communication device; and a determination module, configured to determine at least one second time based on multiple first times included in the fault information, and to determine a second time window based on at least one second time; wherein the first time is the time when the preset fault switches between a state of generation and recovery, the second time is the first time of a target fault, the target fault is included in the preset fault, and the second time window is a time window for monitoring the target fault oscillation alarm; the more second times there are, the shorter the length of the second time window.

[0035] In one possible implementation, the target fault is a preset fault that satisfies at least one of the following conditions: the time interval between two consecutive occurrences or recovery of the preset fault is within a first interval; wherein, the first interval is the periodic range of faults that are periodically generated or recovered; the number of times the preset fault switches states is greater than or equal to a first preset number; wherein, the first preset number indicates the number of times the preset fault frequently switches states; or, the total duration accumulated after multiple state switches of the preset fault is greater than or equal to a first preset time; wherein, the first preset time indicates the time accumulated after frequent state switches of the preset fault.

[0036] In one possible implementation, the first interval is the fluctuation range of the time interval between two adjacent preset fault switching states.

[0037] In one possible implementation, the second time window includes a fault occurrence time window or a fault recovery time window. The device further includes a generation module, which is used to: generate alarm occurrence information if the target fault meets the alarm occurrence conditions within the fault occurrence time window; and / or generate alarm recovery information if the target fault meets the alarm recovery conditions within the fault recovery time window.

[0038] In one possible implementation, the determining module is specifically used to: determine a first generation time and a first recovery time from multiple second times; wherein the first generation time is the time when the target fault is generated, the first recovery time is the time when the target fault is recovered after the first generation time, and a preset number of target faults are spaced between the first generation time and the first recovery time, the preset number being the number of faults indicating that the target fault is frequently generated; and determine a fault generation time window based on the time interval between the first generation time and the first recovery time.

[0039] In one possible implementation, the alarm generation conditions include at least one of the following conditions: the number of times the target fault switches states is greater than or equal to a second preset number; wherein the second preset number indicates the number of times the target fault occurs frequently; the total duration accumulated after the target fault occurs multiple times is greater than or equal to a second preset time; wherein the second preset time indicates the cumulative duration of the target fault occurring frequently.

[0040] In one possible implementation, the determining module is specifically used to: determine a second generation time and a second recovery time from multiple second times; wherein the second generation time is the time when the target fault occurs, the second recovery time is the recovery time of the target fault adjacent to the second generation time, the time interval between the second generation time and the second recovery time is greater than or equal to a target time interval, and the target time interval is the time interval between any two adjacent target faults within the second time window; and determine a fault recovery time window based on the time interval between the second generation time and the second recovery time.

[0041] In one possible implementation, the alarm recovery conditions include: no target fault occurs within the fault recovery time window.

[0042] In one possible implementation, the device further includes an update module, which is used to update the fault recovery time window to a preset time window if a repair operation of the target fault is detected within the fault recovery time window before generating alarm recovery information if the target fault meets the alarm recovery conditions within the fault recovery time window; wherein the length of the preset time window is less than the length of the fault recovery time window.

[0043] A third aspect of this application provides a communication device, including a processor and a memory coupled to the processor. The memory is used to store program instructions, which, when executed on the processor, implement the method of the first aspect of this application or any possible implementation thereof.

[0044] The fourth aspect of this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a processor, implement the first aspect of this application or any possible implementation thereof.

[0045] The fifth aspect of this application provides a computer program product, including a computer program or instructions, which, when executed by a computer, implement the first aspect of this application or any possible implementation of the first aspect.

[0046] The sixth aspect of this application provides a chip or chip system including at least one processor for supporting a communication device to implement the method of the first aspect or any possible implementation of the first aspect. For example, the chip may be a baseband chip, a modem chip, a SoC chip (such as an SoC chip containing a modem core), a SIP chip, or a communication module, etc.

[0047] In one possible implementation, the chip or chip system may further include a memory for storing program instructions and data necessary for the communication device. The chip system may be composed of chips or may include chips and other discrete devices. Optionally, the chip system may also include interface circuitry that provides program instructions and / or data to the at least one processor.

[0048] The seventh aspect of this application provides a communication system, including a network management system and a communication device. The network management system is used to implement the communication method of the first aspect or any possible implementation of the first aspect, and the communication device is used to provide data (e.g., fault information) to the network management system so that the network management system can implement the communication method.

[0049] The technical effects of any of the implementation methods in aspects two through seven can be found in the first aspect or any possible implementation method of the first aspect, and will not be repeated here. Attached Figure Description

[0050] Figure 1 This is a schematic diagram of the communication system provided in an embodiment of this application;

[0051] Figure 2 Another schematic diagram of the communication system provided in the embodiments of this application;

[0052] Figure 3 A flowchart illustrating the communication method provided in an embodiment of this application;

[0053] Figure 4 An exemplary schematic diagram of multiple faults within a first time window provided for embodiments of this application;

[0054] Figure 5 An exemplary schematic diagram of the fault generation time window provided in the embodiments of this application;

[0055] Figure 6 An exemplary schematic diagram of the fault recovery time window provided in the embodiments of this application;

[0056] Figure 7 An exemplary schematic diagram of the fault recovery time window before and after fault repair provided in the embodiments of this application;

[0057] Figure 8 A schematic diagram comparing a fixed time window and a dynamic time window for fault occurrence provided in an embodiment of this application;

[0058] Figure 9 A schematic diagram comparing fixed time windows and dynamic time windows for fault recovery provided in an embodiment of this application;

[0059] Figure 10 A flowchart illustrating a communication method applied to a base station provided in an embodiment of this application;

[0060] Figure 11 A flowchart illustrating a communication method applied to a network management system, as provided in an embodiment of this application;

[0061] Figure 12 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0062] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0063] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0064] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such terms are interchangeable where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0065] It should be understood that the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be single or multiple. Additionally, the character " / " in this document generally indicates that the preceding and following related objects are in an "or" relationship. Furthermore, "at least one of the following" or similar expressions in this document are used to represent any combination of the listed items; for example, at least one of A, B, and / or C can represent the following six situations: A alone, B alone, C alone, A and B simultaneously, B and C simultaneously, A and C simultaneously, and A, B, and C simultaneously, where A, B, and C can be single or multiple.

[0066] Unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various methods / designs / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various methods / designs / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various methods / designs / implementations within each embodiment can be combined to form new embodiments, methods, or implementations based on their inherent logical relationships. The following embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0067] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information (hereinafter referred to as instruction information) is called the information to be instructed. In specific implementation, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is an association between the other information and the information to be instructed; or it can indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction can be implemented by using a pre-agreed (e.g., protocol predefined or pre-configured) arrangement of various information, thereby reducing the instruction overhead to some extent. This application does not limit the specific method of instruction. It is understood that for the sender of the instruction information, the instruction information can be used to indicate the information to be instructed; for the receiver of the instruction information, the instruction information can be used to determine the information to be instructed.

[0068] In the embodiments of this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0069] Frequent alarm bursts refer to the occurrence of frequent faults in communication equipment within a short period of time, leading to frequent alarms, or frequent fault recoveries within a short period of time, leading to frequent alarm recovery. For example, in base station systems, fronthaul, transmission, and equipment-related alarms can all potentially experience frequent alarm bursts. The causes of these bursts are diverse, including peer link failures and optical port contamination. Frequent alarm bursts reduce the processing efficiency of maintenance personnel and make it difficult to ensure timely troubleshooting.

[0070] Compression of oscillation alarms is a method to reduce oscillation alarms. It involves compressing multiple faults occurring within a short period (fixed time window) into a single alarm, or restoring the alarm only if no fault occurs for a relatively long period (fixed time window) after fault recovery. However, a fixed time window, as a statically configured threshold, cannot reflect the dynamic changes in oscillation patterns and cannot be adaptively adjusted. Furthermore, setting a fixed time window requires strong technical expertise; fixed time windows set by ordinary maintenance personnel may not be effective. If the time window is too large, but faults occur irregularly, false alarms may be reported. If the fault recovery time window is too large, the alarm may not be promptly restored after the actual fault is resolved. To avoid one or more of these problems, this application provides the following communication method and related apparatus.

[0071] To facilitate understanding, the communication devices and application scenarios to which the communication method proposed in this application is applicable will be introduced below:

[0072] The technical solutions provided in this application can be applied to communication devices in various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, and future communication systems; or, the technical solutions provided in this application can also be applied to integrated systems of the aforementioned multiple systems. Furthermore, the technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), Internet of Things (IoT) communication systems, or other communication systems.

[0073] Communication equipment: This can be equipment within a wireless network, such as RAN nodes (or devices) that connect terminal devices to the wireless network, also known as base stations. Examples of RAN equipment currently include: base stations, evolved NodeBs (eNodeBs), gNBs (gNodeBs) in 5G communication systems, transmission reception points (TRPs), evolved Node Bs (eNBs), radio network controllers (RNCs), Node Bs (NBs), home base stations (e.g., home-evolved Node Bs, or home Node Bs (HNBs), base band units (BBUs), or wireless fidelity (Wi-Fi) access points (APs). Additionally, in a network architecture, network equipment can include central unit (CU) nodes, distributed unit (DU) nodes, or RAN equipment comprising both CU and DU nodes. RAN nodes can also be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios.

[0074] The communication equipment may also include core network equipment, such as the mobility management entity (MME), home subscriber server (HSS), serving gateway (S-GW), policy and charging rules function (PCRF), public data network gateway (PDN gateway or P-GW) in 4th generation (4G) networks; and access and mobility management function (AMF), user plane function (UPF), or session management function (SMF) in 5G networks. Furthermore, the core network equipment may also include other core network equipment in 5G networks and next-generation networks of 5G networks.

[0075] like Figure 1 As shown, the embodiments of this application can be applied to a communication system, which includes a base station, network equipment, and a network management system. The base station and network equipment are respectively connected to the network management system. Both the base station and network equipment can independently determine a second time window based on fault information within a first time window, or further generate alarm information. Alternatively, they can cooperate with the network management system to migrate some steps to the network management system to determine the second time window or further generate alarm information. The generated alarm information can be notified to maintenance personnel by the network management system.

[0076] like Figure 2 As shown, the communication system includes a network management system 201 and a base station 202. The base station 202 includes an alarm unit 2021 and a fault monitoring unit 2022. The fault monitoring unit 2022 is used to acquire fault information of a preset fault within a first time window, determine at least one second time based on multiple first times included in the fault information, and determine a second time window based on the at least one second time. The alarm unit 2021 is used to generate alarm information and send it to the network management system 201 if the target fault meets the alarm conditions within the second time window. The network management system 201 processes the alarm information, for example, by sending it to the terminal device associated with the maintenance personnel.

[0077] like Figure 3 As shown, this application provides a communication method that can be applied to the aforementioned communication device or a communication system including the communication device. The method includes:

[0078] Step 301. Obtain the fault information of the preset fault within the first time window.

[0079] The first time window is a pre-configured time window used to monitor the patterns of preset faults, such as the time when the preset fault occurs, the duration after it occurs, the recovery time, the frequency of fault occurrence, the frequency of fault recovery, the time interval between different fault occurrences, or the time interval between different fault recoverys. The first time windows corresponding to different preset faults can be the same or different.

[0080] The following is an example of how to configure the first time window:

[0081] Static configuration of the first time window. A statically configured first time window means that its attributes are fixed and do not change over time. First time window attributes include length, position, and number. Length refers to the interval between the start and end times of a first time window. The length of the first time window limits the time period for observing the patterns of preset faults. For rapidly changing preset faults, a shorter first time window can be set, and for slowly changing preset faults, a longer first time window can be set. Alternatively, a first time window of the same length can be set for all preset faults. When configuring this length, a certain upper limit can be considered, such as no more than 24 hours. Position refers to the start and end times of a first time window. The first time window can be a sliding time window, meaning its position on the time axis continuously moves forward. The step size is the length of the first time window; for example, if the length of the first time window is x hours, the start and end times will move forward by x hours as the first time window moves forward. The step size of the first time window can also be set shorter, such as y hours, where y is less than x, thus allowing for more frequent monitoring of the patterns of preset faults. The step size for movement can also be set based on the preset starting position of the next fault occurrence or recovery. Alternatively, the first time window can be a fixed time period, such as time period 'a' every day. The quantity refers to the total number of first time windows that need to be set. Configure one if monitoring is only required once, and configure multiple if continuous monitoring is needed.

[0082] Dynamically configure the first time window. Dynamically configuring the first time window means that the attributes of the first time window may change over time. For example, after monitoring a preset fault based on the previous first time window, the length of the first time window might be too short, resulting in too few occurrences of the preset fault. However, historical data confirms that the preset fault is highly likely to cause an oscillation alarm. In this case, the length of the first time window can be increased for monitoring. Alternatively, after monitoring a preset fault based on the previous first time window, the length of the first time window might be too long, causing the number of occurrences of the preset fault to far exceed the monitoring needs, thus increasing monitoring resources. In this case, the length of the first time window can be decreased. The position of the first time window can also be dynamically adjusted. For example, after monitoring a preset fault with the previous first time window, it might be found that no preset faults occurred at the beginning and middle of the first time window, but multiple faults suddenly appeared at the end of the first time window. In this case, the preset faults might have a time correlation, and the position of the first time window can be moved forward. The number of first time windows can also be dynamically adjusted. If the preset fault is found to no longer occur within the past few first time windows, the number of first time windows can be reduced. For example, if one first time window is originally configured for each day of the week, there will be a total of 7 first time windows in a week. If the preset fault is found to no longer occur within the previous 7 consecutive first time windows, the number of first time windows configured in a week can be reduced from 7 to 1. For example, only the first time window for Sunday can be configured, and no first time windows can be configured from Monday to Saturday. This can save monitoring resources.

[0083] A preset fault is a fault of the same monitored object within a communication device, as illustrated in the example above. The monitored object refers to any object whose fault can be monitored. Various functional modules of a communication device may malfunction, and these modules can be considered monitored objects. Functional modules include hardware modules such as power modules, RF modules, antenna modules, or interface modules, and software modules such as system firmware, communication functions (e.g., handshake, data transmission), or configuration information. When configuring preset faults, any possible and monitorable fault in the communication device can be used as a preset fault. Alternatively, to narrow the monitoring scope, faults that may cause oscillation alarms can be used as preset faults, such as link faults like loose interfaces or poor contact, power faults like voltage fluctuations, or configuration information faults that cause system instability due to improper communication protocol parameter configuration. Alternatively, a fault of interest can be selected as a preset fault. Furthermore, other faults can also be used as preset faults; this is not limited here.

[0084] Fault information includes information related to preset faults. Examples of fault information include: fault name (e.g., link fault); fault identifier (used to distinguish different faults); fault occurrence time (time from fault-free to faulty); fault recovery time (time from faulty to fault-free); fault duration (duration from fault occurrence to fault recovery); state transition count (number of times the fault occurred and recovered, or the number of times the fault occurred and occurred again); and device identifier, such as the device serial number. In addition, fault information may include other information, which is not limited here.

[0085] Fault information can be obtained in the following ways:

[0086] The communication equipment collects data locally. Hardware modules within the communication equipment can have self-testing capabilities; for example, power modules and radio frequency units may have self-testing functions. The controller in the communication equipment connects to these hardware modules and can collect fault information from their self-tests. Furthermore, the control unit of the communication equipment can also actively monitor faults, such as monitoring parameters like temperature and current of components and generating fault information when a fault occurs. Alternatively, the communication equipment can periodically check the stability of connections with other communication devices and generate fault information when the network is unstable. Or, the communication equipment can record its operational status in a log and analyze the log to determine fault information. After collecting fault information locally, the communication equipment can determine a second time window based on this information and monitor the target fault within that second time window.

[0087] The network management system receives fault information sent by communication devices. After collecting fault information locally, the communication devices can send the fault information to the network management system. The network management system receives the fault information, determines a second time window based on the fault information, and monitors the target fault within the second time window.

[0088] Step 302. Based on the multiple first times contained in the fault information, determine at least one second time.

[0089] The first timeframe refers to the time it takes for a preset fault to switch between its occurrence and recovery states. A first timeframe contains multiple first times, meaning the preset fault changes state multiple times within the first timeframe (two or more). To improve efficiency when collecting and analyzing fault information, fault information can be collected for multiple preset faults. Some preset faults may not be those that would trigger an oscillation alarm; in these cases, a second timeframe can be used instead of dynamically determining a second timeframe, and monitoring can proceed according to the default timeframe. Other preset faults are those that might trigger an oscillation alarm; in these cases, a second timeframe can be dynamically determined to monitor for oscillation alarms. Preset faults for which a second timeframe needs to be determined are referred to as target faults in this embodiment. The first timeframe corresponding to the target fault is used as the second timeframe. Furthermore, if there is only one preset fault, this single preset fault can also be used as the target fault.

[0090] When there are multiple preset faults, in order to determine the second time window in a targeted manner, the target fault is a preset fault that meets at least one of the following conditions:

[0091] The preset faults are either generated or recovered periodically. Periodic generation means the interval between two consecutive occurrences of a preset fault falls within a certain periodic range; periodic recovery means the interval between two consecutive recoverys of a preset fault falls within a certain periodic range. The periodic range can be set as a first interval, which can be fixed, or it can be the fluctuation range of the time interval between two consecutive preset fault switching states. The time interval between two consecutive preset fault switching states refers to the time interval between switching from a preset fault to fault generation or to fault recovery. The fluctuation range refers to an interval containing the lengths of different time intervals. The fluctuation range is used to indicate the magnitude of the time interval variation. The variance or standard deviation of multiple time intervals can be calculated, and the fluctuation range can be determined based on the range of variance or standard deviation.

[0092] Preset faults are considered to occur or recover frequently. The frequency of a preset fault can be determined based on its occurrence or duration. Specifically, if the number of times a preset fault switches states is greater than or equal to a first preset number, it can be considered as a frequent occurrence or recovery of the preset fault. The first preset number indicates the number of times the preset fault switches states frequently. Similarly, if the total duration of multiple state switches for a preset fault is greater than or equal to a first preset time, it can also be considered as a frequent occurrence or recovery of the preset fault. The first preset time indicates the accumulated time during the frequent state switches. A state switch refers to switching from fault occurrence to fault recovery (from fault present to fault-free), or from fault recovery to fault occurrence (from fault-free to fault present). The criteria for "frequent" can be set according to actual conditions. Different criteria can also be set for different preset faults to measure frequency. Frequent is a relative concept; the number of times various preset faults occur within a certain time period can be statistically analyzed, and the average value can be calculated. Failures exceeding this average value are considered frequent, and the first preset number and first preset time can be set accordingly. Alternatively, the median can be calculated, and failures exceeding the median value are considered frequent. Alternatively, the probability distribution of the occurrence frequency of various preset faults in historical data can be used to evaluate how many faults constitute frequent occurrence. Furthermore, industry standards can be used to define a first preset number of occurrences or a first preset time. For example, in the actual operation and maintenance of communication equipment, if it is found that three preset faults occurring within a short period are considered frequent, then the first preset number of occurrences can be set directly based on three faults. Correspondingly, the first preset time can be determined by combining the cumulative time of those three faults. Besides the methods described above, other methods can be used to set the first preset number of occurrences or the first preset time, which are not limited here.

[0093] Preset faults have previously caused oscillation alarms. By combining historical data, it is possible to identify which faults have caused oscillation alarms and save the identifiers of the faults that caused oscillation alarms. If the identifier of the preset fault in the first time window matches the saved identifier, it can be determined that the preset fault has caused the oscillation alarm.

[0094] A preset fault is predicted to potentially cause an oscillation alarm. Historical fault data and historical oscillation alarm data can be combined with deep learning to predict whether a fault might cause an oscillation alarm, and the identifiers of faults that may cause oscillation alarms are recorded. If a preset fault matches the identifier, it can be determined that the preset fault is predicted to potentially cause an oscillation alarm.

[0095] Preset faults are not in the whitelist. The whitelist includes faults that are not monitored. For some faults, because their occurrence may have a significant impact on business, an alarm can be triggered immediately when they occur. Without considering potential fluctuation alarms, these faults can be set in the whitelist. Faults in the whitelist can be ignored as target faults.

[0096] In addition to the conditions mentioned above, other conditions may also be applied, which are not limited here.

[0097] like Figure 4 As shown, the horizontal axis represents time, and the vertical axis represents the sequence number of different preset faults. The figure illustrates the states of faults numbered 1, 2, and N at different times when they occur or recover. Each fault state includes both occurrence and recovery. The first time is the point in time when the state changes, such as switching to the occurrence time or the recovery time. Figure 4 The first timeframe is shown in the diagram. Within the first timeframe, fault 1 occurred 3 times with 3 corresponding recoveries, fault 2 occurred 4 times with 4 corresponding recoveries, and fault N occurred once. Outside the first timeframe, fault 1 occurred once with 1 recovery, and fault N recovered once. Figure 4 Within the first time window shown, a fault is considered a target fault if it occurs 3 times or more. Therefore, fault 1 and fault 2 are selected as target faults. In subsequent steps, a second time window can be determined for fault 1 and fault 2. Fault N is not considered for determining the second time window. Furthermore, as the first time window slides, fault N may reach 3 occurrences within a subsequent first time window, and thus may also become a target for determining the second time window.

[0098] Step 303. Determine a second time window based on at least one second time.

[0099] The second time window is used to monitor target faults. The length of the second time window follows a certain pattern with the number of second times: the more second times there are, the shorter the second time window; conversely, the fewer the second times there are, the longer the second time window. The second time corresponding to the target fault refers to the time when the target fault switches states, such as the time point from fault occurrence to fault recovery (from faulty to fault-free), or from fault recovery to fault occurrence (from fault-free to faulty). The number of first times can refer to the first number of time points from fault occurrence to fault recovery, the second number of time points from fault recovery to fault occurrence, or the sum of the first and second numbers. The length of the second time window is negatively correlated with the first number, the second number, or their sum. In other words, within the first time window, the larger the first number, the second number, or their sum, the shorter the determined second time window; conversely, the smaller the first number, the second number, or their sum, the longer the determined second time window.

[0100] A high number of second-time occurrences of the target fault indicates that the target fault occurred or recovered multiple times within the first time window, indicating a high frequency of faults occurring frequently within a short period. Therefore, a shorter second time window is determined. Conversely, a low number of second-time occurrences of the target fault indicates that the target fault occurred or recovered less frequently within the first time window, indicating a lower frequency of faults occurring only frequently over a longer period. Therefore, a longer second time window is determined. In this way, the determined second time window can reflect the pattern of target fault occurrence within the first time window.

[0101] The second time window includes either the fault occurrence time window or the fault recovery time window. The fault occurrence time window is used to monitor the occurrence of the target fault; monitoring can begin when the target fault switches to the point of occurrence. The fault recovery time window is used to monitor the recovery of the target fault; monitoring can begin when the target fault switches from the point of occurrence to the point of recovery.

[0102] The time window for a fault to occur can be determined in the following way:

[0103] The fault occurrence time window is determined based on the duration required for the target fault to occur frequently multiple times. The duration required for frequent occurrence refers to the time interval between the occurrence of the target fault at a certain point in time and the recovery point after several occurrences. This duration reflects how long it takes for the target fault to occur frequently, and based on this, it can be assumed that the target fault will reach a state of frequent occurrence within a similarly long time window in the future, thus allowing the corresponding time window to be used for fault monitoring. Specifically, the time when the target fault occurs among multiple second times is designated as the first occurrence time, and the time after several occurrences of the target fault following the first occurrence time is designated as the first recovery time. A preset number of target faults is spaced between the first occurrence time and the first recovery time; this preset number indicates the number of faults that the target fault occurs frequently. After determining the time interval between the first occurrence time and the first recovery time, the fault occurrence time window is determined based on this time interval. The fault occurrence time window can be equal to this time interval, but it can also have a certain error range, approaching the time interval within this error range.

[0104] like Figure 5 As shown, faults 1 and 2, as target faults, occur and recover multiple times within the first time window. Assuming a frequent occurrence threshold of 3 times (i.e., a preset quantity of 3), the first occurrence time of fault 1 is the time when fault 1 first occurs in the three fault occurrences shown in the figure, and the first recovery time of fault 1 is the time when fault 1 is last recovered in the three fault occurrences shown in the figure. The first occurrence time of fault 2 is the time when fault 2 first occurs in the three preceding fault occurrences, and the first recovery time of fault 2 is the time when fault 2 is last recovered in the three preceding fault occurrences. Therefore, the interval between the first occurrence time and the first recovery time of fault 1 can be defined as the fault occurrence time window for fault 1, and the interval between the first occurrence time and the first recovery time of fault 2 can be defined as the fault occurrence time window for fault 2. When monitoring fault 1 within the fault occurrence time window of fault 1, it effectively includes three occurrences of fault 1. When monitoring fault 2 within the fault occurrence time window of fault 2, it effectively includes three occurrences of fault 2. Thus, the determined fault occurrence time windows reflect the patterns of faults 1 and 2, thereby enabling accurate monitoring of faults 1 and 2.

[0105] The fault occurrence time window is determined based on the quantity at the second time point. If testing reveals a strong correlation between the quantity at the second time point within the first time window and the length of the fault occurrence time window for a specific target fault, a mapping relationship between quantity and time window can be pre-defined for that target fault by statistically analyzing historical data and combining it with the first mapping relationship between the quantity at the second time point and the fault occurrence time window. This first mapping relationship is then saved. After determining the quantity at the second time point, the time window mapped to that quantity within the first mapping relationship is used as the fault occurrence time window. In this mapping relationship, the quantity and the time window length are negatively correlated. This method allows for rapid determination of the fault occurrence time window.

[0106] The fault occurrence time window is obtained by dynamically adjusting the reference time window based on the quantity of the second time. The reference time window is a pre-set time window that serves as the basis for adjustment. If the quantity of the second time is greater than the reference quantity threshold, the length of the reference time window can be decreased to obtain the fault occurrence time window. If the quantity of the second time is less than the reference quantity threshold, the length of the reference time window can be increased to obtain the fault occurrence time window. In this way, the fault occurrence time window can be determined quickly.

[0107] In addition to the methods mentioned above, other methods can be used to determine the time window of fault occurrence, which are not limited here.

[0108] The fault recovery time window can be determined in the following way:

[0109] The fault recovery time window is determined based on the maximum time taken for the target fault to recover and recur. The interval between the time point when the target fault recovers and the time point when it recurs indicates the duration for which the target fault remains in a recovered state. Multiple such intervals exist within the first time window, and the maximum value among these intervals indicates the maximum duration for which the target fault remains in a recovered state. If the target fault continues to oscillate, a target duration slightly longer than this maximum duration is set for the fault recovery time window. Monitoring the target fault within this recovery time window can prevent the alarm corresponding to the target fault from continuously oscillating. Therefore, the fault recovery time window can be determined based on this maximum duration. Among multiple second times, the time when the target fault recovers is taken as the second recovery time, and the time when the adjacent target fault occurs after the second recovery time is taken as the second occurrence time. The time interval between the second occurrence time and the second recovery time is greater than or equal to the target time interval, which is the time interval between any two adjacent target faults within the second time window. The fault recovery time window is determined based on the time interval between the second occurrence time and the second recovery time. The fault recovery time window can be equal to the time interval between the second occurrence time and the second recovery time, or within its error range. This allows for accurate determination of the fault recovery time window.

[0110] like Figure 6 As shown, for fault 1, the second recovery time is the recovery time of the second fault 1 in the three faults illustrated, and the second occurrence time is the occurrence time of the third fault 1 in the three recovery times illustrated. The interval between the two is greater than the interval between the first two faults, reflecting the longest time required for fault recovery to occur within the first time window. For fault 2, the second recovery time is the recovery time of the second fault 2 in the three faults illustrated, and the second occurrence time is the occurrence time of the third fault 2 in the three faults illustrated. The interval between the two is greater than the interval between the first two faults and also greater than the interval between the last two faults, reflecting the longest time required for fault 2 to recover from fault to occur within the first time window. Therefore, the determined fault recovery time window for fault 1 is the interval between the last two faults 1. If the recurrence of fault 1 can be detected within the fault recovery time window of fault 1, no alarm recovery will be triggered. If the occurrence of fault 2 is not detected within the fault recovery time window of fault 2, it can be assumed that the probability of fault 2 recurring is low, and an alarm recovery can be triggered. Thus, the fault recovery time window can accurately detect whether the fault will recur, triggering an alarm recovery at an appropriate time or avoiding oscillation alarms. If the number of failures within the first time window is less than a certain number (e.g., 2 times), a preset time window can be used as the second time window to facilitate early recovery and prevent false alarms.

[0111] The fault recovery time window is determined based on the number of second times. A second mapping relationship can be constructed based on the negative correlation between the number of second times within the first time window in historical data and the length of the fault recovery time window. After determining the number of second times, the fault recovery time window is determined based on this second mapping relationship, which allows for rapid determination of the fault recovery time window.

[0112] In addition to the methods mentioned above, other methods can be used to determine the fault recovery time window, which are not limited here.

[0113] To suppress oscillation alarms, alarms are not triggered immediately after fault recovery. Instead, they are triggered when alarm recovery conditions are met within the fault recovery time window, resulting in a delay between fault recovery and alarm activation. However, if maintenance personnel repair the target fault, it may have been fixed. In this case, an alarm can be triggered earlier to indicate that the target fault has been recovered. This allows the previously determined fault recovery time window to be updated to a preset time window, which is shorter than the previously determined fault recovery time window. Detected fault repairs include optical module insertion / removal, configuration, addition / removal of RF modules, RF module reset, and base station board reset. Therefore, if a repair operation on the target fault is detected within the fault recovery time window before generating alarm recovery information, the fault recovery time window is updated to the preset time window. This shortens the time before alarm activation after the target fault is recovered, accurately reflects the actual return to normal status of the target fault, and facilitates the maintenance of communication equipment.

[0114] like Figure 7 As shown, before the repair operation for fault 2 is detected, fault 1 recurs and recovers within the fault recovery time window, and fault 2 recurs within the fault recovery time window but recovers outside of it. After the repair operation for fault 2 is detected, the fault recovery time window for fault 2 changes to a preset time window. Since no fault is detected within the preset time window, an alarm is triggered and recovery occurs promptly after the preset time window ends. Fault 1 is not repaired, so its original fault recovery time window is maintained, and no alarm is triggered and recovery occurs after the original fault recovery time window ends. Subsequently, as the fault recovery time window slides, alarms can be triggered and recovery can occur when the occurrence and recovery of fault 1 meet certain conditions. This demonstrates that timely alarms and recovery are possible when a fault is repaired, facilitating the presentation of the correct fault status to maintenance personnel and enabling timely troubleshooting.

[0115] Oscillation alarm conditions refer to the conditions set to address potential oscillation alarms. Oscillation alarm conditions include alarm generation conditions set for fault occurrence or alarm recovery conditions set for alarm recovery. If the target fault meets the oscillation alarm conditions within the second time window, an alarm message is generated, including: generating an alarm generation message if the target fault meets the alarm generation conditions within the fault occurrence time window; and / or generating an alarm recovery message if the target fault meets the alarm recovery conditions within the fault recovery time window.

[0116] Alarm generation conditions can be set based on the state when the target fault frequently occurs. For example, if the number of times the target fault switches states is high when it frequently occurs, or if the duration for which the target fault remains in the generated state is long, one of the following conditions can be set: The number of times the target fault switches states is greater than or equal to a second preset number; where the second preset number indicates the number of times the target fault frequently occurs. The total duration accumulated after multiple occurrences of the target fault is greater than or equal to a second preset time; where the second preset time indicates the cumulative duration of frequent occurrences of the target fault. The second preset number and the first preset number can be the same or different. The second preset time and the first preset time can be the same or different.

[0117] Alarm recovery conditions include: no target fault occurs within the fault recovery time window.

[0118] like Figure 8As shown, fault 2 is a fault that occurs frequently within a short period of time. If a fixed time window is used to detect fault 2, the fixed time window may be set too short, only covering two occurrences of fault 2, failing to reach the required three occurrences and thus not triggering an alarm, resulting in a missed alarm. Conversely, if the fixed time is too long, the counted multiple faults may include irregular, sporadic faults, easily leading to false alarms. However, the fault occurrence time window determined by the method described in the embodiment of this application reflects the actual time required for fault 2 to reach three occurrences. It promptly detects and triggers three occurrences of fault 2 near the time when fault 2 reaches three occurrences, triggering an alarm in a timely manner without missing any alarms, thus providing an alarm at the accurate time.

[0119] like Figure 9 As shown, fault 1 and fault 2 are detected using a fixed time window for fault recovery. The recovery patterns of fault 1 and fault 2 differ. Within a very short fixed time window, fault 2 does not recur, indicating that fault recovery occurs and an alarm is triggered for fault 2, with an appropriate alarm timing. However, for fault 1, this short fixed time window is too short to cover the fault 1 that quickly recurs, resulting in an alarm recovery. Shortly after the alarm recovery, the fault recurs, leading to a high probability of repeated alarm generation and recovery, increasing the number of alarms and causing excessively frequent alarms, resulting in oscillating alarms. Conversely, when a very long fixed time window is used, fault 1 is correctly covered, avoiding oscillating alarms for fault 1. However, fault 2 may not recur even when the fault does, resulting in a much longer alarm recovery delay for fault 2. The time window obtained by the method described in the embodiments of this application is a dynamic time window, which serves as the fault recovery time window for dynamically configured fault 1. If fault 2 does not recur, the alarm is recovered in a timely manner. For the fault recovery time window for dynamically configured fault 2, if fault 1 recurs, fault 1 will not be alarmed and recovered, thereby avoiding oscillation alarms.

[0120] like Figure 10 As shown, Figure 10 This is a flowchart of a communication method provided from an embodiment of this application, which is applied to a base station.

[0121] Step 1001. Collect base station fault information within the first time window.

[0122] All functional units within a base station can be used as targets for fault information collection, such as power modules, radio frequency modules, or transmission modules. Base station fault information includes the time information, fault status, and fault identifier of a preset fault. Collection methods can include monitoring the operational status of each functional unit using sensors within the base station, extracting the operational status of each functional module from the base station's operational logs, analyzing the collected operational status, and determining the base station's fault information. Time intervals can be set to collect base station fault information at regular intervals. Here, it is assumed that the first time window is 12 hours, meaning that base station fault information from the past 12 hours is collected every 12 hours.

[0123] Step 1002. Based on base station fault information, determine multiple first moments.

[0124] Multiple first-time events include multiple fault occurrence times (from no fault to fault occurrence time) and multiple fault recovery times (from fault occurrence to fault-free time). If base station fault information includes timestamps, status, and fault type, and the timestamps include multiple time points, such as the following time points in the time format (hour:minute:second): 13:01:00, 13:01:03, 13:10:00, 13:10:05, 13:20:00, 13:20:04, and 13:30:00, the corresponding fault statuses for these multiple time points are: fault occurrence, fault recovery, fault occurrence, fault recovery, fault occurrence, fault recovery, and fault occurrence, with the fault type being voltage anomaly. Based on the fault type of voltage anomaly, it can be determined that it belongs to the same preset fault. Combining the fault status, the fault occurrence time points can be determined to be: 13:01:00, 13:10:00, 13:20:00, and 13:30:00, and the fault recovery time points are: 13:01:03, 13:10:05, and 13:20:04. Pairing the fault occurrence time points with the fault recovery time points, we get pairing 1 (13:01:00-13:01:03), pairing 2 (13:10:00-13:10:05), pairing 3 (13:20:00-13:20:04), and a fault occurrence time point of 13:30:00.

[0125] Step 1003. Based on multiple first-time events, determine the target fault.

[0126] Calculate the standard deviation for multiple historical fault occurrence times. For example, for fault occurrence times of 12:21:00, 12:32:00, 12:41:00, and 12:51:00 within a certain period of historical statistics, since the hours are the same (12 hours), they can be ignored when calculating the standard deviation for ease of calculation. The values ​​are simplified to 21, 32, 41, and 51 minutes. The intervals between two adjacent times are calculated to be 11, 9, and 10 minutes respectively. The standard deviation of 11, 9, and 10 minutes is approximately 0.8. The error range is set to 1, and negative numbers are not taken. The standard deviation interval is set to [0, 1.8]. Furthermore, the standard deviation of the first time of the fault occurrence was calculated. The first times of the fault occurrence were 13:01:00, 13:10:00, 13:20:00, and 13:30:00, all in hours. For ease of calculation, minutes were used, simplifying it to 1, 10, 20, and 30. The time intervals between two adjacent times were calculated to be 9, 10, and 10 minutes, respectively. The standard deviation of 9, 10, and 10 minutes was approximately 0.5, falling within the standard deviation interval [0, 1.8]. This indicates that the time points of the fault occurrence follow a periodic pattern. In addition, the number of fault occurrence time points was 3, meaning the fault occurred 3 times, reaching the frequency threshold (3), and is considered to occur frequently. Therefore, this fault is taken as the target fault.

[0127] Step 1004. Determine multiple second times of the target fault.

[0128] The time corresponding to the target fault among multiple first times is the second time. In the example above, multiple second times include pair 1 being 13:01:00-13:01:03, pair 2 being 13:10:00-13:10:05, and pair 3 being 13:20:00-13:20:04.

[0129] Step 1005. Based on multiple second times, determine the fault occurrence time window and fault recovery time window of the target fault.

[0130] Since three occurrences are considered frequent, we can take three fault occurrence times and three fault recovery times. We select the earliest fault occurrence time (13:01:00) and the latest (13:20:00), calculating the interval between them to be 19 minutes. Rounding up to 20, this indicates that three frequent occurrences require 20 minutes, which can be used as the fault occurrence time window. Based on the three fault recovery times, we can pair them according to their corresponding next fault recovery times to calculate the interval. The three pairs are 13:01:03-13:10:00, 13:10:05-13:20:00, and 13:20:04-13:30:00, with corresponding intervals of 8 minutes 57 seconds, 9 minutes 55 seconds, and 9 minutes 56 seconds, respectively. The largest is 9 minutes 56 seconds, which, rounded up to 10 minutes, allows us to set the fault recovery time window to 10 minutes.

[0131] Step 1006. Configure the fault occurrence time window and fault recovery time window in the base station.

[0132] Step 1006 is optional. After obtaining the fault occurrence time window and fault recovery time window, you can choose to configure only the fault occurrence time window, only the fault recovery time window, or configure both simultaneously. If the base station already has a previously configured fault occurrence time window, then update the previously configured fault occurrence time window to the fault occurrence time window determined in step 1005, which is 20 minutes, and update the previously configured fault recovery time window to 10 minutes. If the fault occurrence time window and fault recovery time window have never been configured before, then they will be configured as new fault occurrence time windows and fault recovery time windows.

[0133] Step 1007. Within the fault occurrence time window, N target faults were detected.

[0134] Steps 1007 to 1009 are optional steps. After obtaining the fault occurrence time window, the base station can choose to issue an alarm in a timely manner when the number of alarms for the target fault is too high within the fault occurrence time window, or it can choose to issue an alarm and restore the fault in a timely manner if no fault is detected within the fault recovery time window.

[0135] The starting point of the fault occurrence time window is the time when the fault is detected. When the base station detects a target fault, it starts timing until the fault occurrence time window ends. In the example above, the fault occurrence time window is 20 minutes. Therefore, timing starts 20 minutes from the first time the target fault is detected, and the number of target fault occurrences within 20 minutes is monitored. Each time the target fault switches from fault recovery (no fault is considered fault recovery) to fault occurrence, it is considered one fault. If the number of faults reaches a threshold within 20 minutes, an alarm is triggered. Assume the number of detected target faults N is 3.

[0136] Step 1008. Determine that the number of occurrences of N target faults is greater than the number threshold, and generate alarm generation information.

[0137] With a threshold of 3 and N equal to 3, the system determines that the target fault occurs frequently within the fault monitoring time window, generating alarm information to indicate the occurrence of the target fault. The alarm information may include the occurrence time, frequency, duration, and fault identifier of the target fault.

[0138] Step 1009. If 0 target faults are detected within the fault recovery time window, generate alarm recovery information.

[0139] The fault recovery time window starts counting from the time the target fault recovers. For example, starting from 10 minutes as in the example above, if a target fault occurs within 10 minutes, no alarm recovery information is generated; if no target fault occurs within 10 minutes, alarm recovery information is generated. The alarm recovery information may include the recovery time of the target fault, the duration of normal operation after recovery, fault identifier, and other information.

[0140] Using the above method, the time window for monitoring faults can be adjusted according to the oscillation pattern, and it does not rely on manual configuration. It can determine when alarms are generated and when alarms are recovered, thereby improving the accuracy of alarms.

[0141] like Figure 11 As shown, Figure 11 This is a flowchart of a communication method provided in an embodiment of this application, which is applied to a network management system.

[0142] Step 1101. The network device sends network device fault information to the network management system, and the network management system receives the network device fault information accordingly.

[0143] Network devices can generate alarms through the network management system. In this case, the network device sends fault information to the network management system. This fault information can include the network device's operational data, which the network management system uses to determine the fault. Operational data includes data generated by each functional module of the network device during operation, such as memory usage, port traffic, port connection status, and power supply status. Based on this operational data, the network management system can determine whether a fault exists and determine fault information such as the fault time and number of faults. Alternatively, the network device can also determine fault information independently and send it to the network management system, which then generates an alarm based on this information.

[0144] Step 1102. The network management system determines multiple first-time events based on network device fault information.

[0145] Step 1103. The network management system determines the target fault based on multiple first-time events.

[0146] Step 1104. The network management system determines the time window of the fault occurrence based on multiple second times of the target fault.

[0147] Step 1105. The network management system obtains the current fault information of the network device within the fault occurrence time window.

[0148] Steps 1105 to 1107 are optional. After determining the fault occurrence time window, the network management system can choose to immediately begin monitoring the target fault within the fault occurrence time window and promptly issue an alarm if the target fault persists for an extended period. Alternatively, the network management system can temporarily store the fault occurrence time window and, when needed, retrieve fault information within a specific time period to monitor for fault occurrence and promptly generate alarm information.

[0149] Step 1106. Based on the current fault information, the network management system determines the duration of the target fault within the fault occurrence time window as T.

[0150] Step 1107. The network management system determines that the duration T is greater than the duration threshold and generates alarm information.

[0151] like Figure 12 As shown, this application embodiment provides a communication device 1200, including:

[0152] The acquisition module 1201 is used to acquire fault information of a preset fault within a first time window; wherein, the first time window is a time window used to monitor the preset fault, and the preset fault is a fault of the same monitored object in the communication equipment;

[0153] The determination module 1202 is used to determine at least one second time based on multiple first times contained in the fault information, and to determine a second time window based on at least one second time; wherein, the first time is the time when the preset fault switches between the state of generation and recovery, the second time is the first time of the target fault, the target fault is included in the preset fault, and the second time window is a time window used to monitor the target fault oscillation alarm. The more second times there are, the shorter the length of the second time window.

[0154] In one possible implementation, the target fault is a preset fault that satisfies at least one of the following conditions:

[0155] The time interval between two consecutive occurrences or recovery of a fault is preset to be within a first interval; where the first interval is the periodic range of faults that occur or recover periodically;

[0156] The number of preset fault switching states is greater than or equal to the first preset number; where the first preset number indicates the number of times the preset fault frequently switches states.

[0157] Alternatively, the total duration accumulated after multiple state switching of the preset fault is greater than or equal to the first preset time; wherein, the first preset time indicates the accumulated time of frequent state switching of the preset fault.

[0158] In one possible implementation, the first interval is the fluctuation range of the time interval between two adjacent preset fault switching states.

[0159] In one possible implementation, the second time window includes a fault occurrence time window or a fault recovery time window, and the device further includes a generation module, which is used for:

[0160] If the target fault meets the alarm generation conditions within the fault generation time window, alarm generation information is generated; and / or, if the target fault meets the alarm recovery conditions within the fault recovery time window, alarm recovery information is generated.

[0161] In one possible implementation, the determining module 1202 is specifically used for:

[0162] From multiple second times, a first generation time and a first recovery time are determined; wherein, the first generation time is the time when the target fault is generated, the first recovery time is the time when the target fault is recovered after the first generation time, and a preset number of target faults are spaced between the first generation time and the first recovery time, the preset number being the number of faults indicating that the target fault is frequently generated;

[0163] The fault occurrence time window is determined based on the time interval between the first occurrence time and the first recovery time.

[0164] In one possible implementation, the alarm generation conditions include at least one of the following conditions:

[0165] The number of times the target fault switching state occurs is greater than or equal to a second preset number; where the second preset number indicates the number of times the target fault occurs frequently.

[0166] The total duration accumulated after the target fault occurs multiple times is greater than or equal to the second preset time; where the second preset time indicates the cumulative duration of the target fault occurring frequently.

[0167] In one possible implementation, the determining module 1202 is specifically used for:

[0168] From multiple second times, determine the second generation time and the second recovery time; wherein, the second generation time is the time when the target fault occurs, the second recovery time is the recovery time of the target fault adjacent to the second generation time, the time interval between the second generation time and the second recovery time is greater than or equal to the target time interval, and the target time interval is the time interval between any two adjacent target faults within the second time window;

[0169] The fault recovery time window is determined based on the time interval between the second generation time and the second recovery time.

[0170] In one possible implementation, the alarm recovery conditions include: no target fault occurs within the fault recovery time window.

[0171] In one possible implementation, the communication device 1200 further includes:

[0172] The update module is used to update the fault recovery time window to a preset time window if a repair operation of the target fault is detected within the fault recovery time window before generating alarm recovery information if the target fault meets the alarm recovery conditions within the fault recovery time window; wherein, the length of the preset time window is less than the length of the fault recovery time window.

[0173] like Figure 13 The diagram shown is a structural schematic of a communication device 130 provided in this embodiment. It should be understood that the aforementioned... Figure 3 The communication device in the corresponding method embodiment can be based on this embodiment. Figure 13 The structure of the communication device 130 shown.

[0174] The communication device 130 includes at least one processor 1301, at least one memory 1302, and at least one transceiver 1303. The processor 1301, memory 1302, and transceiver 1303 are connected together. Optionally, the communication device 130 may further include an input device 1305, an output device 1306, and one or more antennas 1304. The antennas 1304 are connected to the transceiver 1303, and the input device 1305 and output device 1306 are connected to the processor 1301.

[0175] In this embodiment, the memory 1302 is mainly used to store software programs and data. The memory 1302 can exist independently and be connected to the processor 1301. Optionally, the memory 1302 can be integrated with the processor 1301, for example, integrated within one or more chips. The memory 1302 can store program code that executes the technical solutions of this application embodiment, and its execution is controlled by the processor 1301. The various types of computer program code being executed can also be considered as drivers for the processor 1301. It should be understood that in this embodiment... Figure 13 Only one memory and one processor are shown; however, in practical applications, the communication device 130 may have multiple processors or multiple memories, which is not limited here. Furthermore, the memory 1302 may also be referred to as a storage medium or storage device, etc. The memory 1302 may be a storage element located on the same chip as the processor (i.e., an on-chip storage element), or it may be a separate storage element; this embodiment of the application does not limit this.

[0176] In this embodiment, transceiver 1303 can be used to support the reception or transmission of radio frequency signals between communication device 130 and access network device. Transceiver 1303 can be connected to antenna 1304. Transceiver 1303 includes transmitter Tx and receiver Rx. Specifically, one or more antennas 1304 can receive radio frequency signals. The receiver Rx of transceiver 1303 is used to receive radio frequency signals from antenna 1304, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to processor 1301 so that processor 1301 can perform further processing on the digital baseband signals or digital intermediate frequency signals, such as demodulation and decoding. In addition, the transmitter Tx in transceiver 1303 is also used to receive modulated digital baseband signals or digital intermediate frequency signals from processor 1301, convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals through one or more antennas 1304. Specifically, the receiver Rx can selectively perform one or more stages of downmixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency (IF) signal. The order of the downmixing and IF processing is adjustable. The transmitter Tx can selectively perform one or more stages of upmixing and digital-to-analog conversion on the modulated digital baseband signal or digital IF signal to obtain a radio frequency signal. The order of the upmixing and IF processing is also adjustable. The digital baseband signal and the digital IF signal can be collectively referred to as digital signals.

[0177] It should be understood that the aforementioned transceiver 1303 can also be referred to as a transceiver unit, transceiver, transceiver device, etc. Optionally, the device in the transceiver unit used to implement the receiving function can be regarded as the receiving unit, and the device in the transceiver unit used to implement the transmitting function can be regarded as the transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit can also be referred to as a receiver, input port, receiving circuit, etc., and the transmitting unit can be referred to as a transmitter, transmitter, or transmitting circuit, etc.

[0178] Processor 1301 can be a baseband processor or a central processing unit (CPU). The baseband processor and CPU can be integrated together or separate. Processor 1301 can be used to implement various functions for the terminal device, such as processing communication protocols and communication data, or controlling the entire terminal device, executing software programs, and processing data from software programs; or assisting in completing computational processing tasks, such as fault information processing; or processor 1301 can be used to implement one or more of the above functions.

[0179] Furthermore, the output device 1306 communicates with the processor 1301 and can display information in various ways, which are not limited here.

[0180] This application also provides a computer program product (or computer program) that, when executed by the processor, executes the method of the communication device as described above.

[0181] This application also provides a chip system including at least one processor for enabling a communication device to perform the functions described in the possible implementations above. Optionally, the chip system further includes an interface circuit that provides program instructions and / or data to the at least one processor. In one possible design, the chip system may also include a memory for storing necessary program instructions and data for the communication device. The chip system may be composed of chips or may include chips and other discrete devices.

[0182] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms. Whether a function is implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0183] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0184] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a communication device to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A communication method, characterized in that, include: Obtain fault information of a preset fault within a first time window; wherein, the first time window is a time window used to monitor the preset fault, and the preset fault is a fault of the same monitored object in the communication device; Based on the multiple first times included in the fault information, at least one second time is determined; wherein, the first time is the time when the preset fault switches between the state of generation and recovery, and the second time is the first time of the target fault, which is included in the preset fault; A second time window is determined based on the at least one second time; wherein the second time window is a time window used to monitor target fault oscillation alarms, and the more second times there are, the shorter the length of the second time window.

2. The method according to claim 1, characterized in that, The target fault is a preset fault that satisfies at least one of the following conditions: The time interval between two consecutive occurrences or recovery of the preset fault is within a first interval; wherein, the first interval is the periodic range of faults that occur or recover periodically; The number of times the preset fault switching state is greater than or equal to a first preset number; wherein, the first preset number indicates the number of times the preset fault frequently switches states; Alternatively, the total duration accumulated after multiple state switching of the preset fault is greater than or equal to the first preset time; wherein, the first preset time is the time accumulated due to frequent state switching of the preset fault.

3. The method according to claim 2, characterized in that, The first interval is the fluctuation range of the time interval between each two adjacent preset fault switching states.

4. The method according to any one of claims 1-3, characterized in that, The second time window includes a fault occurrence time window or a fault recovery time window. After determining the second time window based on the at least one second time, the method further includes: If the target fault meets the alarm generation conditions within the fault generation time window, then alarm generation information is generated. And / or, if the target fault meets the alarm recovery conditions within the fault recovery time window, alarm recovery information is generated.

5. The method according to claim 4, characterized in that, The number of second times is multiple, and determining the second time window based on the at least one second time includes: From a plurality of second times, a first generation time and a first recovery time are determined; wherein, the first generation time is the time when the target fault occurs, the first recovery time is the time when the target fault is recovered after the first generation time, and a preset number of target faults are spaced between the first generation time and the first recovery time, the preset number being the number of faults that indicate the frequent occurrence of the target fault; The fault occurrence time window is determined based on the time interval between the first occurrence time and the first recovery time.

6. The method according to claim 4 or 5, characterized in that, The alarm generation conditions include at least one of the following conditions: The number of times the target fault switching state is greater than or equal to a second preset number; wherein, the second preset number indicates the number of times the target fault occurs frequently; The total duration of the target fault occurring multiple times is greater than or equal to a second preset time; wherein, the second preset time is the cumulative duration indicating the frequent occurrence of the target fault.

7. The method according to claim 4, characterized in that, The number of second times is multiple, and determining the second time window based on the at least one second time includes: From a plurality of second times, a second generation time and a second recovery time are determined; wherein, the second generation time is the time when the target fault occurs, the second recovery time is the recovery time of the target fault adjacent to the second generation time, the time interval between the second generation time and the second recovery time is greater than or equal to a target time interval, and the target time interval is the time interval between any two adjacent target faults within the second time window; The fault recovery time window is determined based on the time interval between the second generation time and the second recovery time.

8. The method according to claim 4 or 7, characterized in that, The alarm recovery conditions include: no target fault occurs within the fault recovery time window.

9. The method according to claim 4, 7 or 8, characterized in that, Before generating alarm recovery information if the target fault meets the alarm recovery conditions within the fault recovery time window, the method further includes: If a repair operation for the target fault is detected within the fault recovery time window, the fault recovery time window is updated to a preset time window; wherein the length of the preset time window is less than the length of the fault recovery time window before the update.

10. A communication device, characterized in that, include: The acquisition module is used to acquire fault information of a preset fault within a first time window; wherein, the first time window is a time window used to monitor the preset fault, and the preset fault is a fault of the same monitoring object in the communication device; The determination module is used to determine at least one second time based on multiple first times included in the fault information, and to determine a second time window based on the at least one second time; wherein, the first time is the time when the preset fault switches between the state of generation and recovery, the second time is the first time of the target fault, the target fault is included in the preset fault, and the second time window is a time window used to monitor the target fault oscillation alarm; the more second times there are, the shorter the length of the second time window.

11. The apparatus according to claim 10, characterized in that, The target fault is a preset fault that satisfies at least one of the following conditions: The time interval between two consecutive occurrences or recovery of the preset fault is within a first interval; wherein, the first interval is the periodic range of faults that occur or recover periodically; The number of times the preset fault switching state is greater than or equal to a first preset number; wherein, the first preset number indicates the number of times the preset fault frequently switches states; Alternatively, the total duration accumulated after multiple state switching of the preset fault is greater than or equal to the first preset time; wherein, the first preset time is the time accumulated due to frequent state switching of the preset fault.

12. The apparatus according to claim 11, characterized in that, The first interval is the fluctuation range of the time interval between each two adjacent preset fault switching states.

13. The apparatus according to any one of claims 10-12, characterized in that, The second time window includes a fault occurrence time window or a fault recovery time window. The device further includes a generation module, which is used to: If the target fault meets the alarm generation conditions within the fault generation time window, then alarm generation information is generated. And / or, if the target fault meets the alarm recovery conditions within the fault recovery time window, alarm recovery information is generated.

14. The apparatus according to claim 13, characterized in that, The determining module is specifically used for: From a plurality of second times, a first generation time and a first recovery time are determined; wherein, the first generation time is the time when the target fault occurs, the first recovery time is the time when the target fault is recovered after the first generation time, and a preset number of target faults are spaced between the first generation time and the first recovery time, the preset number being the number of faults that indicate the frequent occurrence of the target fault; The fault occurrence time window is determined based on the time interval between the first occurrence time and the first recovery time.

15. The apparatus according to claim 13, characterized in that, The determining module is specifically used for: From a plurality of second times, a second generation time and a second recovery time are determined; wherein, the second generation time is the time when the target fault occurs, the second recovery time is the recovery time of the target fault adjacent to the second generation time, the time interval between the second generation time and the second recovery time is greater than or equal to a target time interval, and the target time interval is the time interval between any two adjacent target faults within the second time window; The fault recovery time window is determined based on the time interval between the second generation time and the second recovery time.

16. A communication device, characterized in that, include: processor; A memory coupled to the processor, the memory being used to store program instructions that, when executed on the processor, implement the method of any one of claims 1-9.

17. A communication system, characterized in that, include: Communication equipment; A network management system connected to the communication device, the network management system being used to implement the steps of the method according to any one of claims 1-9.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a processor, implement the method as described in any one of claims 1-9.

19. A computer program product, characterized in that, It includes a computer program or instructions that, when executed by a computer, implement the method as described in any one of claims 1-9.

Images