DE10256466A1 - Communications network transmission path monitoring method using periodic comparison of counts attained by error second counters for both transmission directions with preceding count values - Google Patents

Abstract

The transmission path monitoring method has error second counters for both transmission directions compared periodically with the corresponding counts obtained for the preceding monitoring period. No performance data is transmitted when the compared counts are the same and integration of the comparison results over several monitoring periods. A fault indication is transmitted to a network management center when the value of an integration counter reaches a threshold level.

Description

• 1. What technical problem should your Invention solved become?
• 2. How has this problem been solved so far?
• 3. How does it solve Your invention the specified technical problem (give advantages on)?
• 4. What is the inventive step?
• 5th embodiment [e] the invention.

To 1. The performance of high bit rate lines in the access area with xDSL lines should as simple as possible reliably monitored become the net management center without the very extensive performance data transferred to.

To 2. So far, according to standards (ITU, ETSI, ADSL forum) for this big amount of of data that is then periodically transmitted to a network management center and can be evaluated there. Here arise size delays and there will be a lot of data for good intervals, which is the normal case, are also transmitted. The evaluation of the actual Losses in transmission quality caused a bigger effort.

To 3. The invention uses from the many performance data offered, only those which are suitable for simple, however, accurate quality assessments are relevant, in particular the so-called Error Second (ESZ), Severe Error Second (SESZ) and the unavailable second counter (USZ) on the network side for both Directions and compares them periodically (n minutes) with the corresponding ones Counter readings of previous period. The ESZ is preferably used because of the greatest sensitivity. If there is no difference, the quality is good and only that Restart for a periodic monitoring counter for the interval n.

In the event of an incorrect period on the xDSL route is initially the start is determined by integration with the help of a leaky bucket counter LBZ and to the network management center NetM with little data such as time, existing bit rate for both directions and the status of the ESZ for both transmission directions Directions reported. The end of an error phase is indicated by a Leak counter LZ determined in combination with the LBZ. If the time of the LZ runs out, so the LBZ is checked, whether he's bigger than Is zero.

If this is the case, LBZ decremented; If the LBZ level reaches zero, an error end message is issued sent to the NetM.

• – Die aktuellen Bitraten BR1, BR2 und die Uhrzeit werden gespeichert für die Empfangsseiten beider Richtungen,
• – Die Fehlerzählerstände der vorangegangenen Periode für ESZ, SESZ und USZ werden gespeichert,
• – Ein Leaky-Bucket-Zähler (LBZ) wird inkrementiert und ein
• – Leak-Zähler (LZ) wird gestartet.

Specifically, if the difference (s) of the ESZ / SESZ / USZ is determined, the following steps are carried out for both directions per interval n:
An error start is formed by integrating several error intervals. When the first faulty period is determined, the following activities take place:

• The current bit rates BR1, BR2 and the time are stored for the reception sides of both directions,
• - The error counter values of the previous period for ESZ, SESZ and USZ are saved,
• - A leaky bucket counter (LBZ) is incremented and a
• - Leak counter (LZ) is started.

After another monitoring period n finds a further comparison of the counters between the previous one disturbed Interval and the current, new values of the counter instead.

If there is no difference, so the LBZ is not increased, but leave it. The leak counter LZ will count down until after its time ensure zero of the LBZ; the LZ is restarted until the LBZ has reached zero; this will also end the error in Reported towards NetM.

• – der LBZ wiederum inkrementiert und verglichen mit einer administrierbaren LBZ-Schwelle LBZS; wird dieser Wert erreicht,
• – so erfolgt eine Fehleranfangs-Meldung an das zuständige Netzmanagement-Zentrum NetM mit folgenden Daten:
• – aktuelle Uhrzeit,
• – aktuelle Bitraten für beide Richtungen sowie die zu Beginn des 1. Fehlerhaften Intervalls festgestellten Bitraten beider Richtungen,
• – Differenzen der Fehlerzähler ESZ, SESZ und USZ zwischen aktuellem Stand und Stand zu Beginn (Start des LBZ) für beide Richtungen. Der LBZ wird auf 1 gesetzt, da die Fehlererfassung noch weiter gehen kann.

If a difference is found, then:

• - the LBZ in turn incremented and compared to an administrable LBZ threshold LBZS; if this value is reached
• - This is how an error message is sent to the responsible network management center NetM with the following data:
• - current time,
• Current bit rates for both directions and the bit rates of both directions determined at the beginning of the 1st faulty interval,
• - Differences of the error counters ESZ, SESZ and USZ between the current status and the status at the beginning (start of the LBZ) for both directions. The LBZ is set to 1 because the error detection can go even further.

4.) By periodic comparison from few quality data becomes relatively common a current quality comparison carried out.

The otherwise required periodic transfers from a big one Number of performance data are at the necessary level at the beginning an error interval and reduced at the end.

The remaining frequency of transfers to the network management center through the administrable parameters for the leaky bucket mechanism easily adjust.

6. The following are enclosed as attachments for further explanation:

Claims (1)

Method for monitoring a transmission link in the access area of a communication network, according to which a) the error seconds counter (ESZ) is periodically compared for both transmission directions with the corresponding counter reading of the previous monitoring period, b) if the meter readings are the same, no performance data are sent to a higher-level network management center, c) if the meter readings are not identical, the comparison results are integrated over several monitoring periods in such a way that an integration counter occurs every time the meter readings are not equal is incremented by a certain value in each case, d) an error start message is sent to the network management center when the value of the integration counter reaches a certain threshold value.