SIST EN 301 129 V1.1.1:2003

SLOVENSKI STANDARD
01-december-2003
Prenos in multipleksiranje (TM) – Digitalni radiorelejni sistemi (DRRS) – Sinhrona
digitalna hierarhija (SDH) – Parametri za nadzorovanje lastnosti sistemov SDH
DRRS
Transmission and Multiplexing (TM); Digital Radio Relay Systems (DRRS); Synchronous
Digital Hierarchy (SDH); System performance monitoring parameters of SDH DRRS
Ta slovenski standard je istoveten z: EN 301 129 Version 1.1.1
ICS:
33.040.20 Prenosni sistem Transmission systems
33.060.30 Radiorelejni in fiksni satelitski Radio relay and fixed satellite
komunikacijski sistemi communications systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 301 129 V1.1.1 (1998-09)
European Standard (Telecommunications series)
Transmission and Multiplexing (TM);
Digital Radio Relay Systems (DRRS);
Synchronous Digital Hierarchy (SDH);
System performance monitoring parameters of SDH DRRS

2 EN 301 129 V1.1.1 (1998-09)
Reference
DEN/TM-04037 (agc00ico.PDF)
Keywords
SDH, DRRS, transmission, performance
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
secretariat@etsi.fr
http://www.etsi.fr
http://www.etsi.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998.
All rights reserved.
ETSI
3 EN 301 129 V1.1.1 (1998-09)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.7
3 Symbols and abbreviations .8
3.1 Symbols . 8
3.2 Abbreviations. 8
4 Introduction.9
5 Functional architecture.10
6 Radio specific maintenance parameters.10
6.1 Radio Synchronous Physical Interface (RSPI) performance management. 10
6.1.1 Performance primitives . 10
6.1.1.1 Received Level (RL). 10
6.1.1.2 Transmitted Level (TL) . 11
6.1.2 Performance events . 12
6.1.2.1 Received Level Threshold Second (RLTS) . 12
6.1.2.2 Received Level Tide Mark (RLTM). 12
6.1.2.3 Transmitted Level Threshold Second (TLTS). 12
6.1.2.4 Transmitted Level Tide Mark (TLTM) . 13
6.1.3 Performance data collection and history treatment. 13
6.1.4 Performance data threshold treatment . 13
6.2 Radio Protection Switching (RPS) performance management. 14
6.2.1 Performance primitives . 14
6.2.1.1 Protection Switch Actual (PSA) . 14
6.2.1.2 Protection Switch Request (PSR) . 14
6.2.2 Performance events . 14
6.2.2.1 Protection Switch Actual Count (PSAC) . 14
6.2.2.2 Failed Switch Request Count (FSRC) . 15
6.2.2.3 Protection Switch Actual Duration (PSAD) . 15
6.2.2.4 Failed Switch Request Duration (FSRD). 16
6.2.3 Performance data collection and history treatment. 16
6.2.4 Performance data threshold treatment . 17
6.3 Radio OverHead Access (ROHA) performance management . 17
7 Radio specific transmission quality monitoring .17
Annex A (informative): Description of radio specific performance monitoring at reference
point XT dependent on the allocation of RPS functional block.18
Annex B (informative): Application of additional performance parameters for fault
management and error performance management .21
B.1 Examples of RSPI and RPS events and counters behaviours .21
B.1.1 Received Level (RL) performance primitive, Received Level Tide Mark (RLTD) and Received Level
Threshold Second (RLTS) performance events. 21
B.1.2 RPS performance events . 23
B.2 Example of usage of additional performance parameters in case of fading phenomena and
equipment fault .25
B.2.1 Rain induced fading event. 25
B.2.1.1 DRSS without ATPC. 25
B.2.1.2 Rain induced fading event: DRRS with the ATPC. 26
B.2.2 Far end equipment failure at Tx side. 27
ETSI
4 EN 301 129 V1.1.1 (1998-09)
B.2.3 Unexpected bad quality in a high frequency SDH DRRS. 28
B.2.3.1 Interference . 28
B.2.3.2 Additional signal loss . 28
B.2.3.3 Equipment degradation . 29
B.2.4 Fading effects in a low frequency SDH DRRS . 29
B.2.5 Unexpected bad quality in a low frequency SDH DRRS. 30
B.2.5.1 Single hop . 30
B.2.5.2 Protected section . 30
B.3 Example of maintenance principles .31
B.3.1 High frequency DRRS in configuration without protection switching. 31
B.3.1.1 DRRS implemented as a Regenerator Section (RS). 31
B.3.1.1.1 Fault detection and fault analysis. 32
B.3.1.1.2 Maintenance procedure based on error performance parameters. 33
B.3.1.2 DRRS implemented as a Multiplex Section . 34
B.3.1.2.1 Fault detection and fault analysis. 35
B.3.1.2.2 Maintenance procedure based on error performance parameters. 35
B.3.2 DRRS with 1+1 protection switching . 35
B.3.2.1 DRRS implementing protection type C. 35
B.3.2.1.1 Maintenance procedure based on error performance parameters. 37
Annex C (informative): Performance monitoring functional architecture .38
C.1 Performance primitive and event generation. .38
C.2 Data collection, history and threshold treatment architecture .38
C.2.1 15 minute register . 39
C.2.2 24 hour register. 40
C.2.3 Threshold crossing notification. 40
C.2.4 History register . 40
Bibliography.41
History.42
ETSI
5 EN 301 129 V1.1.1 (1998-09)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Transmission
and Multiplexing (TM).
The present document describes the performance monitoring functional architecture and requirements which are specific
to the Digital Radio Relay System (DRRS) Network Elements (NE) that use the Synchronous Digital Hierarchy (SDH)
multiplexing structure.
National transposition dates
Date of adoption of this EN: 18 September 1998
Date of latest announcement of this EN (doa): 31 December 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 June 1999
Date of withdrawal of any conflicting National Standard (dow): 30 June 1999
ETSI
6 EN 301 129 V1.1.1 (1998-09)
1 Scope
The present document defines the additional specific performance monitoring functional architecture and requirements
to be used for management of Digital Radio Relay Systems (DRRS) which use the Synchronous Digital Hierarchy
(SDH).
Considering that:
- ETS 300 635 [4] and ITU-R Recommendation F.750 [3] define the SDH radio specific functional blocks for
transmission at STM-n data rate;
- ETS 300 785 [5] and ITU-R Recommendation F.750 [3] define the SDH radio specific functional blocks for
transmission at Synchronous Transport Module 0 (STM-0) data rate;
- EN 301 167 [6], ETS 300 417 [7], ITU-T Recommendations G.783 [1] and G.784 [2] define the performance
monitoring architecture and requirements for generic functional blocks used on SDH DRRS and other SDH
equipment;
- ITU-T Recommendation M.3010 [8] defines the standardized logical and functional Telecommunication
Management Network (TMN) architecture.
The present document defines:
- the specific performance primitives and events to be used for performance management of radio specific
functional blocks;
- the general requirements for history treatment associated to each performance event;
- the general requirements for thresholding treatment associated to each performance event;
- the specific transmission quality information which is required for maintenance purpose.
The present document does not define:
- the F interface performance monitoring;
- the performance monitoring related to non radio specific functional blocks;
- the information model to be used on Q interface which is on the study in TC TMN, (work item DEN/TMN-0006,
see bibliography).
- the protocol stack to be used for the message communication function;
- any radio specific additional performance parameter to be used at network level management.
The present document applies on each SDH DRRS independently of the transmission data rate supplied (STM-n or
STM-0).
The parameters defined in the present document are only intended to be used for radio equipment maintenance.
The present document should provide guidance and supporting information for the definition of object-oriented models
within SDH DRRS.
It is not required for that equipment developed prior to the present document to be fully compliant with the present
document.
ETSI
7 EN 301 129 V1.1.1 (1998-09)
2 References
References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply; or
b) all versions up to and including the identified version (identified by "up to and including" before the version
identity); or
c) all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d) publications without mention of a specific version, in which case the latest version applies.
A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ITU-T Recommendation G.783 (1994): "Characteristics of synchronous digital hierarchy (SDH)
equipment functional blocks".
[2] ITU-T Recommendation G.784 (1994): "Synchronous digital hierarchy (SDH) management".
[3] ITU-R Recommendation F.750: "Architectural and functional aspects of radio-relay systems for
SDH-based networks".
[4] ETS 300 635: "Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH); SDH
Radio specific functional blocks for transmission of M x STM-N".
[5] ETS 300 785: "Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH); SDH
Radio specific functional blocks for transmission of M x sub-STM-1".
[6] EN 301 167: "Transmission and Multiplexing (TM); Management of Synchronous Digital
Hierarchy (SDH) transmission equipment; Fault management and performance monitoring;
Functional description".
[7] ETS 300 417: "Transmission and Multiplexing (TM); Generic functional requirements for
Synchronous Digital Hierarchy (SDH) equipment".
[8] ITU-T Recommendation M.3010: "Principles for a Telecommunications management network".
[9] ITU-T Recommendation G.826: "Error performance parameters and objectives for international
constant bit rate digital paths at or above the primary rate".
[10] ITU-T Recommendation G.EPMRS: "Error Performance Events for SDH Multiplex Sections".
[11] ETS 300 411: "Performance monitoring information model for the Network Element (NE) view".
[12] ITU-T Recommendation G.774.01: "Synchronous Digital Hierarchy (SDH) performance
monitoring for the network element view".
[13] ITU-T Recommendation G.707 (1996): "Network node interface for the synchronous digital
hierarchy (SDH)".
[14] Void.
[15] TR 101 035: "Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH) aspects
regarding Digital Radio Relay Systems (DRRS)".
[16] ITU-T Recommendation M.20: "Maintenance philosophy for telecommunications networks".
[17] ITU-T Recommendation G.861: "Principles and guidelines for the integration of satellite and radio
systems in SDH transport networks".
ETSI
8 EN 301 129 V1.1.1 (1998-09)
3 Symbols and abbreviations
3.1 Symbols
For the purposes of the present document, the following symbols apply:
dB decibel
dBm decibel relative to 1 milliWatt
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATPC Automatic Transmit Power Control
BBE Background Block Error
DRRS Digital Radio Relay System
ES Errored Second
EW Early Warning
FEC Forward Error Correction
FSRD Failed Switch Request Duration
FSRC Failed Switch Request Count
HBER High Bit Error Rate
HO High Order
IF Intermediate Frequency
LBER Low Bit Error Rate
LOS Loss of Signal
MCF Message Communication Function
MS Multiplex Section
MSA Multiplex Section Adaptation
MST Multiplex Section Termination
NE Network Element
OS Operating System
POH Path OverHead
PM Performance Monitoring
PSA Protection Switch Actual
PSAC Protection Switch Actual Count
PSAD Protection Switch Actual Duration
PSR Protection Switch Request
RF Radio Frequency
RL Received Level
RLTD Received Level Tide Mark
RLTM Received Level Tide Mark
RLTS Received Level Threshold Second
ROHA Radio OverHead Access
RPS Radio Protection Switching
RRR Radio Relay Regenerator
RRT Radio Relay Terminal
RS Regenerator Section
RSOH Regenerator Section OverHead
RSPI Radio Synchronous Physical Interface
RST Regenerator Section Termination
SDH Synchronous Digital Hierarchy
SES Severely Erorred Second
SEMF Synchronous Element Management Function
SF Signal Fail
STM-n Synchronous Transport Module n
Sub-STM-1 Sub-Synchronous Transport Module 1 (also defined as STM-0 in
ITU-T Recommendation G.861 [17])
TL Transmitted Level
ETSI
9 EN 301 129 V1.1.1 (1998-09)
TLTD Transmitted Level Tide Mark
TLTM Transmitted Level Tide Mark
TLTS Transmitted Level Threshold Second
TMN Telecommunication Management Network
UAS UnAvailable Second
UAT UnAvailable Time
VC-n Virtual Container n
4 Introduction
The SDH multiplexing frame structure allows in-service quality transmission monitoring at different levels such as
regenerator and multiplex sections and low/high order paths.
SDH Performance Monitoring (PM) is described starting from the definition of the performance primitives, events and
parameters and defining the PM data collection and history treatment together with the way to present PM information
to a managing system at a Q3 interface.
The whole matter is covered by several ITU-T Recommendations and ETSI standards e.g. ITU-T Recommendations
G.783 [1], G.784 [2], G.826 [9], G.EPMRS [10], and G.774.01 [12]; EN 301 167 [6], ETS 300 411 [11] and
ETS 300 417 [7].
SDH radio Network Elements (NE) may terminate, depending on applications, regenerator and multiplex sections and
also high/low order paths. For each one of the above SDH layers implemented inside a SDH radio NE, the associated
standardized PM shall be implemented.
Signal transmission on microwave radios may be affected by mid-air propagation phenomena that may result in
transmission quality degradation. In order to counteract such typical radio feature several counter measures are or may
be implemented inside radio transmission equipment.
The close relationship between transmission quality and radio link propagation cannot be well understood if the PM is
limited only to quality of service.
In particular it is not possible, for a given measured quality, to discriminate among errors due to equipment
degradations, countermeasure unefficiency and unusual or unpredicted bad propagation.
From such a reason the present document covers the need to have radio specific performance parameters to be used in
close conjunction with the ordinary ones related to quality transmission: Severely Errored Second (SES), Errored
Second (ES), Background Block Error (BBE) and UnAvailable Second (UAS).
Radio specific PM defines new radio specific performance primitives, events and parameters with associated
requirements for data collection, threshold and history treatment.
Radio specific PM deals with monitoring of the radio specific functional blocks Radio Synchronous Physical Interface
(RSPI) and Radio Protection Switching (RPS) as defined in ETS 300 635 [4], ETS 300 785 [5] and
ITU-R Recommendation F.750 [3].
Clause 5 describes the general architecture of the radio specific PM process.
All the radio specific performance parameters defined in the present document are not required to meet quality
objectives. Their meaning is consistent only in the hops or link which they refer to. Comparisons among different hops
or links are not meaningful. A true performance comparison among different hops or links can be done only on the base
of the generic SDH quality of service parameters like ES, SES, BBE and UAS.
ETSI
10 EN 301 129 V1.1.1 (1998-09)
From a management point of view the following applications may be envisaged:
- maintenance application:
The presence of the 15 minutes register counters with associated threshold crossing control may be used to
trigger threshold crossing notifications to a managing system. This process may be helpful to indirectly localize
possible degradations of hardware devices like ATPC devices, feeders and antennas for example.
- SDH transmission quality parameters qualification:
The presence of the 15 minutes and 24 hours current register counters like SES, ES, BBE and UAS associated
for each regenerator and multiplex sections terminated in a Radio NE allows to have transmission quality
monitoring of the same sections. The association of radio specific counters on registers of the same period allows
to qualify them.
In particular the values of radio specific counters may give indications on occurrence of propagation fading and
switching activity during these periods helping in the distinction between quality degradation due to equipment or
propagation.
- long term statistics:
The presence of 24 hours history register radio specific counters together with the possibility to transfer their
associated values to a managing system allows the collection at OS level of long term statistics.
This information may also be used to verify the existing propagation prediction methods which are usually used
for link design or develop new ones.
5 Functional architecture
The functional architecture of the radio specific PM (data collection, history and threshold treatment) is compliant to
ITU-T Recommendation G.784 [2] and EN 301 167 [6].
This clause does not define any additional functional architecture requirements.
The functional architecture is reported in the informative annex C for the reader convenience.
6 Radio specific maintenance parameters
6.1 Radio Synchronous Physical Interface (RSPI) performance
management
6.1.1 Performance primitives
6.1.1.1 Received Level (RL)
The RL is the level of the estimated received power at the input of the receiver and may be used to understand if a
predefined period has been affected by fading activity. It may be also used to identify some permanent loss of received
power due to hardware failures.
It must be outlined that this level is an estimation of the received power and that it may be affected by a certain amount
of inaccuracy that is system dependent.
ETSI
11 EN 301 129 V1.1.1 (1998-09)
Moreover the interpretation of the associated values depends on several factors:
- the type of transmission used, i.e. bi-carriers, mono carrier systems;
- the fact that it is usually associated to a wide-band measure;
- the employed frequency.
The RL shall be a performance primitive available at the S50 reference point of the RSPI functional block.
This level shall be readable by a managing system on request.
The parameter unit shall be expressed in dBm and represented by the rounded nearest integer.
In the case that an Intermediate Frequency (IF) combiner is used as a fading countermeasure, only one performance
primitive is required.
In this case this performance primitive is represented by either the level of the combined signal or by the level of the
best single received input signals according to their availability.
In the case that STM-4 reception is implemented be several receivers (even if it is modelled by one single RSPI
functional block) then one RL shall be monitored per each receiver implementing the block. On the consequence the
S50 reference point may provide a multiple RL performance data table.
6.1.1.2 Transmitted Level (TL)
This subclause applies only when the Automatic Transmit Power Control (ATPC) is present. There are no requirements
on TL when the ATPC is not present.
The TL is the level of the estimated transmitted power at the transmitter output. It may be used to monitor the ATPC of
a transmitter.
It may also be used to identify periods of fading activity.
NOTE: Currently implemented ATPC controls are of two kinds:
Continuous power tracking where a control loop keeps the receiver level constant from the activation
threshold down to a fading attenuation equal to the ATPC range, in this case the TL may assume any
value within the ATPC range.
Step control power where only one or few power steps may be activated by the receiver level thresholds
without any control loop, in the latter case the TL assumes discrete values within the ATPC range.
Similar considerations can be done for the TL as reported in subclause 6.1.1.1 for the RL.
The TL shall be a performance primitive available at S50 reference point of the RSPI functional block.
This level shall be readable by a managing system on request.
The TL level is represented by two values:
- an integer fixed value expressed in dBm defining the nominal i.e. the maximum transmitted power value which is
equipment dependent;
- an integer offset value expressed in dB representing the variation with respect to the nominal value.
In the case that STM-4 transmission is implemented by several transmitters (even if it is modelled by one single RSPI
functional block) then one TL shall be monitored per each transmitter implementing the block. On the consequence the
S50 reference point may provide a multiple TL performance data table.
ETSI
12 EN 301 129 V1.1.1 (1998-09)
6.1.2 Performance events
6.1.2.1 Received Level Threshold Second (RLTS)
The RLTS event is defined as a one second period during which the detected RL value is below a predefined threshold.
The associated predefined threshold shall be given in dBm and it is a characteristic of the event definition. The facility
of assigning the threshold value by the managing system shall be mandatory and may also be settable locally.
For any RL performance primitive at least two RLTS events are required corresponding to two different threshold
values. A number n of RLTS events with n greater than two is optional.
The current value of the counter associated with a RLTS shall be readable by a managing system on request.
In the case that a threshold associated to a RLTS counter is changed then the current value of the counter shall be reset
to zero.
6.1.2.2 Received Level Tide Mark (RLTM)
The RLTM is a mechanism that records the maximum and the minimum value reached by the RL during a measurement
period. The tide mark values are automatically reset to the RL current value assumed at the beginning of each
measurement period.
The RLTM is therefore composed by two values: the RL for the maximum value and the RL for the minimum
max min
value.
The comparison between the RL current value and the RL and RL values shall be performed on a second basis.
max min
When the current RL value is greater than the RL value then the RL value is updated equal to the RL current
max max
value. When the current RL value is lower than the RL value then the RL value is updated equal to the RL current
min min
value.
The RLTM is an optional feature.
6.1.2.3 Transmitted Level Threshold Second (TLTS)
This subclause applies only when the ATPC is present.
The TLTS event is defined as a one second period during which the detected TL value is greater than a predefined
threshold.
The associated predefined threshold shall be given in dB and it is a characteristic of the event definition. The facility of
assigning the threshold value by the managing system shall be mandatory and may also be settable locally.
NOTE: When ATPC is supplied by one ore more transmitter power steps (see note in subclause 6.1.1.2) the
threshold assignment to any value within one power step will give the same results. For example, in the
case of one step, the result is the activation time of the ATPC.
For any TL performance primitive one TLTS event is required.
One additional TLTS event is optional.
The current value of the counter associated with a TLTS shall be readable by a managing system on request
In the case that a threshold associated to a TLTS counter is changed then the current value of the counter shall be reset
to zero.
ETSI
13 EN 301 129 V1.1.1 (1998-09)
6.1.2.4 Transmitted Level Tide Mark (TLTM)
The TLTM is a mechanism that records the maximum or minimum value reached by the TL during a measurement
period. The tide mark values are automatically reset to the TL current value assumed at the beginning of each
measurement period.
The TLTM is therefore composed by two values: the TL for the maximum value and the TL for the minimum
max min
value.
The comparison between the TL current value and the TL and TL values shall be performed on a second basis.
max min
When the current TL value is greater than the TL value then the TL value is updated equal to the TL current
max max
value. When the current TL value is lower than the TL value then the TL value is updated equal to the TL current
min min
value.
The TLTM is an optional feature.
6.1.3 Performance data collection and history treatment
Storage requirements of RSPI performance events in the 15 minutes and 24 hours current and history registers are
reported in table 1.
Table 1: Storage requirements for RSPI performance events
Performance Current 15 minute current 15 minute history 24 hour current 24 hour history
event value register registers register register
RL R- - - NR
-R R R R
RLTS-1
RLTS-2 -R R R R
- O R* R* R*
RLTS-n
RLTM - O R* R* R*
R- - - NR
TL
TLTS-1 -R R R R
- O R* R* R*
TLTS-2
TLTM - O R* R*
NOTE: R = Required - = Not Applicable O = Optional NR = Not Required
R* = Required only if supported in the 15 minutes current register.
6.1.4 Performance data threshold treatment
Threshold treatment requirements for performance events are reported in table 2.
Table 2: Threshold control requirement for RSPI performance events
Performance event 15 minute threshold 24 hour threshold
control control
NR NR
RL
RLTS-1RR
NR NR
RLTS-2
RLTS-n NR NR
NR NR
RLTM
TL NR NR
RR
TLTS-1
TLTS-2 NR NR
NR NR
TLTM
NOTE: R = Required NR = Not required
ETSI
14 EN 301 129 V1.1.1 (1998-09)
6.2 Radio Protection Switching (RPS) performance
management
6.2.1 Performance primitives
6.2.1.1 Protection Switch Actual (PSA)
APSA represents any actual switch from a protected (working) channel to a protecting (stand-by) channel.
This performance primitive shall be reported to the Synchronous Element Management Function (SEMF) at reference
point S 51 of the RPS functional block.
6.2.1.2 Protection Switch Request (PSR)
A PSR represents any activation of a switch initiation criteria which may lead to automatic switches from a working
channel to a stand-by channel and vice-versa.
This performance primitive shall be reported to the SEMF at reference point S 51 of the RPS functional block.
6.2.2 Performance events
6.2.2.1 Protection Switch Actual Count (PSAC)
A PSAC represents the number of PSA occurrences in a time period.
This time period can vary between zero and 15 minutes or 24 hours for the 15 minute or 24 hour current register
respectively and represents the elapsed time since the last reset of the count.
This time period is 15 minutes or 24 hours for 15 minute or 24 hour history registers respectively.
A PSAC is defined for any protected or protecting channel involved in a M: N protection scheme where M is the
number of the protecting channels and N is the number of the protected ones.
For a protected channel the PSAC is the number of any actual switch from this channel to any protecting channel. For a
protecting channel the PSAC is the number of any actual switch from any protected channel to this channel.
For 1+1 and 1:N protection scheme this event is only required for the protected channel.
The current value of the counter associated with a PSAC shall be readable by a managing system on request.
Table 3 summarizes the required conditions for generating the PSAC event of the RPS functional block.
Table 3: PSAC event generation requirements
Channel Protection scheme
1+1 1:n m(m>1):n
protected (working) RR R
NR O R
protecting (stand-by)
NOTE: R = Required NR = Not required O = Optional
ETSI
15 EN 301 129 V1.1.1 (1998-09)
6.2.2.2 Failed Switch Request Count (FSRC)
A FSRC represents the number of the occurrences in a time period of the following events:
- A: a PSR is activated on a working channel and the protecting channels are not available.
- B: a working channel is restored from a protecting channel while a PSR is still active on the channel.
This time period can vary between zero and 15 minutes or 24 hours for the 15 minute or 24 hour current register
respectively and represents the elapsed time since the last reset of the count.
This time period is 15 minutes or 24 hours for 15 minute or 24 hour history registers respectively.
A FSRC is defined only for working channels.
For 1+1 protection scheme this event is optional.
When an activation criterion is already present on a channel, the activation of another one will not increment the
counter.
The current value of the counter associated with a FSRC shall be readable by a managing system on request.
Table 4 summarizes the required conditions for generating the FSRC event of the RPS functional block.
Table 4: FSRC event generation requirements
Channel Protection scheme
1+1 m:n
OR
protected (working)
protecting (stand-by) NR NR
NOTE: R = Required NR = Not required O = Optional
6.2.2.3 Protection Switch Actual Duration (PSAD)
A PSAD event count is the number of seconds, in a time period, for which a channel is in the switched status for at least
a fraction of one second.
For a protected channel the switched status means that its associated traffic is carried on a protecting channel.
For a protecting channel the switched status means that it is carrying traffic from a protected channel.
This time period can vary between zero and 15 minutes or 24 hours for the 15 minute or 24 hour current register
respectively and represents the elapsed time since the last reset of the count.
This time period is 15 minutes or 24 hours for 15 minute or 24 hour history registers respectively.
A PSAD event is defined for any protected or protecting channel involved in a M:N protection scheme.
For 1+1 protection scheme this event is optional.
In the case of fixed 1+1 non-revertive switching schemes this event has no meaning and is not required.
In the case of selectable revertive/non-revertive 1+1 switching schemes this event is optional.
However, if the non-revertive mode is active, an output for this event shall not be generated.
In case of switches arising from management operations an output of this event shall not be generated.
The current value of the counter associated with a PSAD shall be readable by a managing system on request.
Table 5 summarizes the required conditions for generating the PSAD event of the RPS functional block.
ETSI
16 EN 301 129 V1.1.1 (1998-09)
Table 5: PSAD event generation requirements
Channel Protection scheme
1+1 revertive 1+1 non-revertive m:n
ONR R
protected (working)
protecting (stand-by) ONR R
NOTE: R = Required NR = Not required O = Optional
6.2.2.4 Failed Switch Request Duration (FSRD)
A FSRD event is the count of the number of seconds in a time period for which, at least for a fraction of one second, a
protection switch request is detected active on a channel carrying regular traffic and the request cannot be serviced.
This time period can vary between zero and 15 minutes or 24 hours for the 15 minute or 24 hour current register
respectively and represents the elapsed time since the last reset of the count.
This time period is 15 minutes or 24 hours for 15 minute or 24 hour history registers respectively.
A FSRD event is defined only for working channels.
For 1+1 protection scheme this event is optional.
The current value of the counter associated with a FSRD shall be readable by a managing system on request.
Table 6 summarizes the required conditions for generating the FSRD event of the RPS functional block.
Table 6: FSRD event generation requirements
Channel Protection scheme
1+1 m:n
OR
protected (working)
protecting (stand-by) NR NR
NOTE: R = Required NR = Not required O = Optional
6.2.3 Performance data collection and history treatment
Performance data collection and history treatment principles are described in annex C.
Storage requirements of RPS performance events in the 15 minutes and 24 hours current and history registers are
reported in table 7.
Storage requirements apply only for those events that are generated according to tables 3, 4, 5 and 6.
Table 7: Storage requirements for RPS performance events
Performance 15 minute current 15 minute history 24 hour current 24 hour history
event register registers register register
RR R R
PSAC
FSRC RR R R
RR R R
PSAD
FSRD RR R R
NOTE: R = Required
ETSI
17 EN 301 129 V1.1.1 (1998-09)
6.2.4 Performance data threshold treatment
Threshold treatment requirements for performance events are reported in table 8.
Threshold treatment requirements apply only for those events that are generated according to tables 3, 4, 5 and 6.
Table 8: Threshold control requirements for RPS performance events
Performance event 15 minute threshold 24 hour threshold
control control
OO
PSAC
PSAD (working) OO
RR
PSAD (stand-by)
FSRC OO
OO
FSRD
NOTE: R = Required O = Optional
6.3 Radio OverHead Access (ROHA) performance
management
There are no performance requirements for the ROHA functional block.
7 Radio specific transmission quality monitoring
SDH DRRS are parts of the SDH network and may be used to implement Regenerator Section (RS) and Multiplex
Section (MS) functions.
One necessity is to provide the performance of the radio link section in order to compare the performance of different
sections of the network (for example radio link and optical link). The information derived for each type of section shall
be comparable, therefore the parameters and the methodology used to evaluate them shall be consistent and shall be the
results of similar calculation processes.
For the RS and MSs implemented by DRRS the parameters and the methodology used to provide performance
monitoring are defined in EN 301 167 [6]. The evaluation of these parameters is required for RS and MS.
The RS and MS shall be implemented as defined in ETS 300 635 [4] and ETS 300 785 [5].
To monitor the performance of a protected section it may be useful to have a radio specific performance monitoring on
reference point XT of the RPS functional block as an option. Due to the fact that the allocation of the RPS functional
block can be different according to ETS 300 635 [4], the use and implementation of this performance monitoring
functionality can also be different.
Figure 1 shows the location of reference point XT, not depending on the allocation of the RPS functional block.
U51 U51 K51K51K51
K51K51K51 K50 K50
B
R
B R XLXLXL XTXTXT
XTXTXT XLXLXL
RSPI RPRPRPSSS
RSPI
RPRPRPSSS
RF
S50 S51S51S51
S50 T1
S51S51S51 T1
Figure 1: Location of reference point XL at the RPS functional block
The parameters and methodology used to provide this performance monitoring shall be the same as for RS and MS.
The possible allocation of RPS functional block according to ETS 300 635 [4] and possible implementations of
...