7.3 Alarm and Recovery Mechanisms

Figure 7 shows how a QoS alarm is triggered and an event is sent to an application. The time line shows that QoS parameters are measured every unTime_Interval. The QoS parameter in this example transitions from Success to Failure which starts the unDebounceOn timer. The QoS parameter transitions to Success and the unDebounceOn timer stops timing and is reset. At this time, the percentage failure rate is less than unPercentFailThreshold so no alarm event is sent. Later, the QoS parameter transitions from Success to Failure and the unDebounceOn timer begins timing again. In this scenario, the unDebounceOn timer expires while the QoS parameter is in Failure period and the percentage failure rate is equal to or greater than unPercentFailThreshold. Both of these situations cause an alarm event to be sent and the unDebounceOn timer to be reset.

Figure 7. Alarm Mechanism

Figure 8 shows how an application recovers from a QoS alarm. The time line shows that QoS parameters are measured every unTime_Interval. The QoS parameter in this example transitions from Failure to Success which starts the unDebounceOff timer. The QoS parameter transitions to Failure and the unDebounceOff timer stops timing and is reset. At this time, the percentage success rate is less than unPercentSuccessThreshold so no alarm recovery event is sent. Later, the QoS parameter transitions from Failure to Success and the unDebounceOff timer begins timing again. In this scenario, the unDebounceOff timer expires while the QoS parameter is in Success period and the percentage success rate is equal to or greater than unPercentSuccessThreshold. Both of these situations cause an alarm recovery event to be sent and the unDebounceOff timer to be reset.

Figure 8. Recovery Mechanism

Click here to contact Telecom Support Resources