UMTS RTWP Troubleshooting Guide

UMTS RTWP Troubleshooting Guide
Prepared by Liu Qiong, Zhang Junjie, Date

2011-10-27
Zhang Qiong, Zou Rong
Reviewed by Date
Reviewed by Date
Approved by Date
Huawei Technologies Co., Ltd.

All rights reserved.
UMTS RTWP Troubleshooting Guide V1.0 INTERNAL
Change History
Date Version Description Author
2011-10-27 V1.0 Completed Zhangjunjie
2019-1-15 Huawei Confidential Page 2 of 87

Contents
1 Overview.........................................................................................................................................9
2 Definition of RTWP....................................................................................................................10
2.1 Definition.........................................................................................................................................................10
2.2 NodeB PN........................................................................................................................................................11
2.2.1 Query and Configuration of PN..............................................................................................................11
2.3 ROT.................................................................................................................................................................13
2.4 RTWP Tracing..................................................................................................................................................15
2.4.1 RNC Performance Measurement Counters(Granularity: Thirty Minutes).............................................15
2.4.2 Real-Time RNC and NodeB Tracing (Granularity: 1s)..........................................................................15
2.4.3 NodeB CDT............................................................................................................................................20
2.4.4 RTWP Routine Test (RTWP Tracing of the Main and Diversity Receivers) and Analysis Tools..........24
3 RTWP Troubleshooting Flow...................................................................................................25

3.1 Criteria for Determining an RTWP Problem...................................................................................................25
3.1.1 RF-related Alarms...................................................................................................................................25
3.1.2 M2000 Threshold Alarms.......................................................................................................................26
3.1.3 Abnormal KPIs and Service Complaint..................................................................................................26
3.2 Methods of Identifying and Analyzing RTWP Problems................................................................................27
3.2.1 Process for Troubleshooting RTWP Problems.......................................................................................27
3.2.2 Method 1: Identifying a Problem Based on the Traffic Measurement Counters....................................28
3.2.3 Method 2: Identifying a Problem Based on the Real-time Cell RTWP Tracing of the Main and
Diversity Receivers or the Tracing of Number of Users.................................................................................39
3.2.4 Method 3: Identifying a Problem by Analyzing Services and Interference Based on the NodeB CDT
Tracing.............................................................................................................................................................42
3.3 Other Product or Algorithm Causes (that Must Be Analyzed by R&D Engineers).........................................42
4 Troubleshooting Procedure.......................................................................................................44
4.1 Checking the RF Channel Parameter Configuration.......................................................................................44
4.2 Alarm Troubleshooting....................................................................................................................................51
4.3 Interference Troubleshooting...........................................................................................................................52
4.3.1 Rules for Identifying Interference..........................................................................................................52
4.3.2 Intermodulation Interference..................................................................................................................54
4.3.3 Inter-RAT Interference............................................................................................................................60
4.4 Network Planning............................................................................................................................................75

4.4.1 Neighboring Cell Interference................................................................................................................75

4.4.2 Strong Coverage.....................................................................................................................................76
4.5 Traffic Measurement Capacity or Service (Such as Product Bugs) Factors....................................................77
5 Improvement Actions for RTWP Problems...........................................................................79

5.1 Improvement Actions on the Feeder System...................................................................................................79
5.1.1 Improvement Actions for Intermodulation Problems.............................................................................79
5.1.2 Improvement Actions on External Interference......................................................................................79
5.2 Improvement Actions for RF-related Configuration Problems.......................................................................80
5.2.1 Improvement Action on RF Channel Parameters...................................................................................80
5.3 Service-level Improvement Actions.................................................................................................................80
5.3.1 Improvement Action to Optimize the Performance Parameters.............................................................80
5.3.2 Improvement Action for Device Capacity..............................................................................................82
6 References.....................................................................................................................................83
6.1 M2000 Threshold Management.......................................................................................................................83
6.2 References........................................................................................................................................................86

Figures
Figure 1-1 Possible causes for RTWP rise..............................................................................................................9
Figure 2-1 Method of measuring RTWP...............................................................................................................10
Figure 2-2 Example of a background noise value queried on the RNC LMT when the Auto-adaptive
background noise update switch is OFF................................................................................................................12
Figure 2-3 Configuration examples when the auto-adaptive background noise update switch is ON.................13
Figure 2-4 ReC of the UL load factor and ROT...................................................................................................14
Figure 2-5 RTWP data collection nodes...............................................................................................................15
Figure 2-6 Real-time RTWP tracing on the RNC LMT........................................................................................16
Figure 2-7 Schematic drawing of real-time RTWP tracing on the RNC LMT.....................................................17
Figure 2-8 Tracing the number of users in a cell on the RNC LMT.....................................................................17
Figure 2-9 Settings on the NodeB LMT for board RTWP tracing (1)..................................................................18
Figure 2-10 Settings on the NodeB LMT for board RTWP tracing (2)................................................................18
Figure 2-11 Schematic drawing of tracing results on the NodeB LMT................................................................19
Figure 2-12 Cell RTWP tracing on the NodeB LMT............................................................................................20
Figure 2-13 Schematic drawings of settings for user tracing................................................................................21
Figure 2-14 Schematic drawing of settings for cell tracing..................................................................................22
Figure 2-15 Schematic drawing of settings for cell CDT tracing on the NodeB LMT (RAN13.0).....................23
Figure 2-16 Schematic drawing of settings for cell CDT tracing on the NodeB LMT (RAN12.0).....................23
Figure 3-1 Symptoms and possible causes for RTWP problems..........................................................................25
Figure 3-2 Procedure for identifying an RTWP problem......................................................................................27
Figure 3-3 Drawing for RNC performance measurement counters (interference at night)..................................29
Figure 3-4 Drawing for RNC performance measurement counters (continuous interference).............................30
Figure 3-5 Drawing one: RNC performance measurement counters (intermittent interference).........................31
Figure 3-6 Drawing two: RNC performance measurement counters (intermittent interference).........................32
Figure 3-7 Performance measurement data for two adjacent cells at the same time segment..............................32
Figure 3-8 Drawing for RNC traffic measurement counters (adjacent cell interference).....................................34

Figure 3-9 Drawing for RNC traffic measurement counters (limited capacity)...................................................35
Figure 3-10 Drawing for RNC traffic measurement counters (a problem in country T)......................................36
Figure 3-11 Drawing for RNC traffic measurement counters (unknown causes).................................................37
Figure 3-12 Schematic drawing of narrowband interfering signals......................................................................38
Figure 3-13 Cell RTWP of the main receiver in busy hours > High cell RTWP of the diversity receiver in busy
hours.......................................................................................................................................................................40
Figure 3-14 Abnormally low cell RTWP of the diversity receiver.......................................................................41
Figure 4-1 Abnormal configuration fault tree.......................................................................................................44
Figure 4-2 Query of initial RTWP calibration values...........................................................................................45
Figure 4-3 Configuration information...................................................................................................................45
Figure 4-4 Query results of receiving channel attenuation values........................................................................46
Figure 4-6 Query results of RF desensitivity........................................................................................................48
Figure 4-8 Query results of cell desensitization intensity.....................................................................................49
Figure 4-9 Query results of desensitization intensity............................................................................................49
Figure 4-10 Configuration information.................................................................................................................50
Figure 4-11 Query results of TMA subunit dynamic information........................................................................50
Figure 4-12 Starting downlink load (step 1).........................................................................................................55
Figure 4-16 Schematic drawing of the traced RTWP and the downlink load power in the cells where
intermodulation interference exists........................................................................................................................57
Figure 4-17 Traced RTWP....................................................................................................................................58
Figure 4-19 Structure of the antenna feeder (left) and the traced RTWP (right)..................................................59
Figure 4-21 Schematic drawing of narrowband interfering signals......................................................................60
Figure 4-22 Schematic drawing of wideband interfering signals.........................................................................61
Figure 4-23 Schematic drawing of using the interference check function of the NodeB LMT (1)......................62
Figure 4-24 Schematic drawing of using the interference check function of the NodeB LMT (interference
check, RWB = 15 kHz)..........................................................................................................................................63
Figure 4-25 Scanned spectrum of analog interfering signals after the monophonic signals are fed into the
diversity receiver....................................................................................................................................................64

Figure 4-26 Typical interfering signals (varying according to the board type and analyzed spectrum)...............65
Figure 4-27 Typical UMTS signals (with double carrier configuration, wherein the RTWP in high frequency
cells rises)..............................................................................................................................................................65
Figure 4-28 Using the AOA method to locate the interference source.................................................................67
Figure 4-29 Location of sites................................................................................................................................68
Figure 4-30 RTWP traced in neighboring cells.....................................................................................................68
Figure 4-32 Traced RTWP in the 45680 site.........................................................................................................70
Figure 4-33 Antenna position (left) and measured RTWP (right).........................................................................71
Figure 4-34 Site location (left) and traced RTWP (right).....................................................................................71
Figure 4-35 Traced RTWP in real time — air conditioner 1.................................................................................72
Figure 4-36 Traced RTWP in real time — air conditioner 2.................................................................................72
Figure 4-37 Traced RTWP in real time — emergency light.................................................................................73
Figure 4-38 Long-term features (left) and short-term features (right) of traced RTWP.......................................73
Figure 4-39 Spectrum when the directional antenna connecting YBT250 is close to the device.........................74
Figure 4-40 Interference generated on a transmission line...................................................................................74
Figure 4-41 Long-term features (left) and short-term features (right) of traced RTWP.......................................74
Figure 4-42 Spectrum features..............................................................................................................................75
Figure 4-43 Relationship between the number of users in a cell and RTWP peaks.............................................78
Figure 6-1 Threshold Setting window...................................................................................................................83
Figure 6-2 Threshold alarm setting.......................................................................................................................84
Figure 6-3 Threshold settings................................................................................................................................85

Tables
Table 3-1 RF-related alarms..................................................................................................................................25
Table 3-2 Counter values.......................................................................................................................................26
Table 3-3 Typical RTWP-related RNC traffic measurement counters..................................................................28
Table 3-4 Abnormal types.....................................................................................................................................28
Table 3-5 RTWP problem categories....................................................................................................................39
Table 3-6 Check items...........................................................................................................................................42
Table 3-7 Information collection items.................................................................................................................43
Table 5-1 The performance parameter optimization may affect the network. Therefore, you are advised to take
the improvement action under the R&D engineers' assistance. RTWP optimization measures............................80

1 Overview
The Received Total Wide band Power (RTWP) usually reflects the interference level in a
NodeB. When the NodeB has no load, the value of RTWP is equal to the NodeB pedestal
noise (PN).
The RTWP may rise due to increased traffic, inter-RAT interference, antenna fault, bugs
inside the system, abnormal terminals, or other causes, as shown in Figure 1.1. Therefore, the
solution to handling the RTWP rise varies according to the causes. Aiming to provide a set of
systematic methods to find out causes for the RTWP rise, this document provides reasonable
explanations to normal RTWP rise and mapping solutions to abnormal RTWP rise.
Figure 1.1 Possible causes for RTWP rise
According to feedback from sites of the UMTS network worldwide, the following RTWP
problems must be solved immediately.
1. The RTWP rise leads to abnormal network KPIs.
2. The actual Mean_RTWP is inconsistent with the estimated RTWP rise in traffic
evaluation.
For a continuous RTWP rise lasting 5 to 20 seconds, causes can be located based on this
guide.
For the RTWP peak lasting about one second, root cause can be found out and reasonable
explanations are available in this guide.

2 Definition of RTWP
2.1 Definition
The RTWP reflects the interference level in a NodeB and indicates the strength of signals
received by the antenna receiving port of the RF module.
Figure 2.1 Method of measuring RTWP
A P_in signal received by the antenna is amplified by a tower mounted amplifier (TMA)
(optional) and a remote radio unit (RRU) in a NodeB and then converted from a digital signal
to an analog one. After that, a P_out signal is output. Therefore, RTWP indicates the power of
a signal received by the antenna receiving port. The formula for calculating RTWP is as
follows:
RTWP = P_in = P_out – G
In the preceding formula, G indicates the total gain of the receiving channel, namely the sum
of TMA gain (optional) and NodeB gain. G is a constant value.
The RTWP is measured at NodeBs and then reported to the radio network controller (RNC)
for access and congestion control. The RTWP on all antennas is measured at NodeBs. In
addition, the RTWP on each receiving channel in all cells is measured at NodeBs. The cell
RTWP that is traced on the RNC LMT, however, usually equals the average RTWP of all
channel RTWPs (average of linear domains) in all cells of the NodeBs.

2.2 NodeB PN
When no signal is input into the receiver (namely, no inter-RAT or intra-RAT interference
exists or no users are served in the system), the RTWP measured in the NodeB equals the
NodeB PN. The formula for calculating NodeB PN is as follows:
PN = KTB + NF
Where,
 K = Boltzmann constant
 T = 290 K (room temperature)
 B = RF carrier bandwidth (Hz) = 3.84 MHz
 NF: noise factor of the RF system
Therefore, the NodeB PN is about –106 dBm at room temperature. The PN is affected by the
analog circuit of the RF system (for example, component performance is affected by external
factors such as frequency and temperature) and changes due to the factor T. Therefore, a
normal PN ranges from –108 dBm to –104 dBm.
Due to certain networking configuration, the NodeB PN rises in the following scenarios:
3. When a TMA or line amplifier (LA) is used without the configuration of RX channel
attenuation, the NodeB PN rises.
Rise volume (X) = TMA gain – Antenna feeder/Jumper attenuation (For details about
baseline configuration, see Setting RX Channel Attenuation in "Causes" in 4.4.2"Strong
Coverage.")
4. A NodeB uses the configuration of multiple RRUs in one cell. Note that the
configuration of multiple RRUs in one cell in RAN13.0 and later versions does not result
in the rise of PN. The rise volume of PN is relevant to the number of RRUs in one cell.
Assume that N RRUs are in one cell, the rise volume N is 10log(N) dBm.
2.2.1 Query and Configuration of PN

To query or set the PN, run LST (SET) UCELLCAC on the RNC LMT. Generally, the PN is
set probably due to the following reasons:
1. Auto-adaptive background noise update switch is OFF.
If Auto-adaptive background noise update switch is OFF, the fixed value of background
noise is used. The default value is 61.

Figure 4.1 Example of a background noise value queried on the RNC LMT when the Auto-
adaptive background noise update switch is OFF
The value 61 is set according to the measurement result in a cell without load. If the RTWP
measured in a cell without load is –106 dBm, the formula is as follows:
(RTWP – (–112) x 10 + 1 = BackgroundNoise
(–106 – (–112)) x 10 + 1 = 61
In fact, the RTWP –106 dBm is not applicable to all scenarios. For example, the RTWP
measured at a site without load is always –106.3 dBm. The value is normal. Based on this
value, the calculated PN must be 58 dBm.
2. Auto-adaptive background noise update switch is ON.
The Auto-adaptive background noise update switch (enclosed in red and marked with 1) is
ON when either of the following conditions is met:
1. The auto-adaptive background noise update switch is triggered only in the time range
between Background noise update start time (enclosed in red and marked with 4) and
Background noise update end time (enclosed in red and marked with 5).
2. In the time range when Auto-adaptive background noise update switch is ON, the
equivalent user number is smaller than the value of Equivalent user number threshold
for background noise and the duration is greater than the value of Background noise
update continuance time (enclosed in red and marked with 2). The changed value is
greater than the value of Background noise update trigger threshold (enclosed in red
and marked with 6).

Figure 2.1 Configuration examples when the auto-adaptive background noise update switch is
ON
2.3 ROT
Rise over thermal (ROT) suggests the proportion of NodeB noise to NodeB PN. The formula
is as follows:
I TOT
ROT 
PN

In the preceding formula, I TOT indicates the total interference. The dB domain of total
interference is RTWP.
In the dB domain, ROT is calculated by using the following formula:
ROT (dB) = RTWP (dBm) – PN (dBm)
The total NodeB noise includes:
 NodeB PN
 Intra-RAT interference: includes the uplink (UL) signal Ior transmitted from a local cell
UE and the UL signal Ioc transmitted from a UE in a neighboring cell.
 RF interference: includes the external RF interference (such as inter-RAT interference
and interference of non-communication systems) and intra-RAT RF interference
(especially the intermodulation interference generated by internal components).
When no RF interference exists, ROT is caused all by intra-RAT interference. In this case, the
value of ROT can be used as the measurement standard of the UL load. The following
formula shows the relationship between the UL load factor and ROT:
I TOT 1
ROT  
PN 1  UL
Figure 2.2 shows the relationship curve (ReC) of UL load factor and ROT.
Figure 2.2 ReC of the UL load factor and ROT

The load factor is used for admission and congestion control. When the baseline of the load
factor is 75%, the mapping ROT is 6 dB. Therefore, in the current traffic situation of the live
network, the ROT of a value smaller than 6 dB is normal. If the value is greater than 6 dB,
abnormal RTWP is determined. In this case, the cause of the problem must be located.
2.4 RTWP Tracing

The cell RTWP of the live network can be obtained based on following data types of different
granularities:
 RNC performance measurement counters (granularity: thirty minutes)
 Real-time RTWP tracing or RTWP routine test task (granularity: 1s)
 Call Detail Trace (CDT) (granularity: 2 ms)
Based on the preceding data tapes, you can trace the RTWP of the main receiver and the
RTWP of the diversity receiver, or trace the average RTWP of the main and diversity
receivers, as shown in Figure 2.3. Therefore, you can solve the RTWP problems gradually
from the data of the largest granularity to the data of the smallest granularity. For details about
the troubleshooting process, see chapter 3"RTWP Troubleshooting Flow."
Figure 2.3 RTWP data collection nodes
2.4.1 RNC Performance Measurement Counters(Granularity:

Thirty Minutes)
The RNC Performance measurement counters usually shows the maximum, mean, and
minimum RTWPs within the statistics period (Half an hour or one hour in general) of each
cell.
2.4.2 Real-Time RNC and NodeB Tracing (Granularity: 1s)

The real-time RTWP tracing can be performed on the RNC LMT. Alternatively, the RTWP on
each receiving antenna can be traced on the NodeB LMT. Through real-time RTWP tracing,

the uplink interference status can be observed in 1s granularity, thereby identifying abnormal
RTWP and locating causes for problems more exactly.
The RTWP values that can be observed by users are categorized into board RTWP and cell
RTWP by the problem source.
3. Real-time RTWP Tracing on the RNC LMT (Average RTWP of the Main and
Diversity Receivers)
The RTWP traced on the RNC LMT is the mean value of the RTWP (granularity: 1s) of the
main receiver and the RTWP of the diversity receiver at a NodeB. After the tracing, the
NodeB reports the average RTWP contained in a common measurement message to the RNC.
If the RTWP of the main receiver and RTWP of the diversity receiver of all cells are
consistent, trace the RTWP on the RNC LMT directly.
The RTWP tracing on the RNC LMT continues without interruption. The difference between
the RTWP of the main receiver and the RTWP of the diversity receiver of different cells,
however, are not distinguished. Therefore, the existence of interference can be determined by
quality.
The number of users in a cell can be traced synchronously for identifying the relationship
between RTWP and services.
Figure 3.1 Real-time RTWP tracing on the RNC LMT
Figure 3.2 shows the RTWP traced in real time (tracing period: 1 second; time span: 10:00–
17:00).

Figure 3.2 Schematic drawing of real-time RTWP tracing on the RNC LMT
Figure 3.3 shows the method of tracing the statistical number of users in a cell on the RNC
LMT (tracing period: 1s).
Figure 3.3 Tracing the number of users in a cell on the RNC LMT
4. Board RTWP Tracing on the NodeB LMT (RTWP of the Main Receiver and RTWP
of the Diversity Receiver)
To view the real-time change to the RTWP of the main receiver and the RTWP of the diversity
receiver in a cell, trace the RTWP on the NodeB LMT based on the RRU ID. By doing this,
you can check the RTWP on all receiving channels in real time. The tracing in a NodeB,
however, may often be interrupted due to the transport problems. If you need to collect
information for analyzing the RTWP of the main receiver and the RTWP of the diversity
receiver in batches in an offline manner, obtain the required information by using the method
described in section 2.4.4"RTWP Routine Test (RTWP Tracing of the Main and Diversity
Receivers) and Analysis Tools."
Step 2 Run LST LOCELL to query the RRU ID of the local cell, as shown in Figure 1.1.

Figure 1.1 Settings on the NodeB LMT for board RTWP tracing (1)
Step 3 Trace the board RTWP based on the obtained RRU ID, as shown in Figure 1.1.
Figure 1.1 Settings on the NodeB LMT for board RTWP tracing (2)

Figure 1.2 Schematic drawing of tracing results on the NodeB LMT
----End

Cell RTWP Tracing on the NodeB LMT (Average RTWP of the Main and
Diversity Receivers)
Figure 1.1 Cell RTWP tracing on the NodeB LMT
The Cell RTWP tracing item is available in RAN13.0 and later versions.
2.4.3 NodeB CDT

The NodeB CDT traces link change, power control, and bit error during the user access
process. In addition, this tool traces the 2-ms RTWP (average RTWP of the main and diversity
receivers). This RTWP directly indicates the user behavior at the physical layer and partially
identifies the interference from an external source. The NodeB CDT includes user tracing and
cell tracing.
1. User Tracing

Figure 1.2 Schematic drawings of settings for user tracing

2. Cell Tracing (2-ms RTWP)

In the Cell ID text box, enter a local cell ID, as shown in Figure 1.3.
Figure 1.3 Schematic drawing of settings for cell tracing

Figure 1.4 Schematic drawing of settings for cell CDT tracing on the NodeB LMT (RAN13.0)
Figure 1.5 Schematic drawing of settings for cell CDT tracing on the NodeB LMT (RAN12.0)
The UMAT and PreStar tools for analyzing the 2-ms RTWP data are accessible to Huawei
R&D engineers only. Therefore, you are advised to ask the R&D engineers to obtain and

analyze the 2-ms RTWP data. The onsite personnel must send the cell CDT tracing logs to
R&D engineers.
2.4.4 RTWP Routine Test (RTWP Tracing of the Main and

Diversity Receivers) and Analysis Tools
The data collection content of an RTWP routine test is the same as the data content for board
RTWP tracing. In this case, you can collect network-wide data.
On the M2000, you can select NodeBs in batches for routine tracing. Note that the routine
tracing data is stored only in the high-end memory of a NodeB. The memory capacity is
limited. Therefore, RTWP data is written into the memory repeatedly when the limited
capacity is fully used. The stored data is safe in the memory even if a NodeB is restarted. In
the case of power failure or system upgrade, the stored data may be lost.
You are advised to select part of NodeBs or all NodeBs for tracing on the M2000. By doing
this, you can obtain the required RTWP data of a certain NodeB for analysis if necessary.
1. Methods of tracing, obtaining, and processing data of an RTWP routine test
For details, see the following reference document:
Guide to Methods of Collecting Data of an RTWP Routine Test and Usage of
RTWPAnalysis.doc
2. Analysis of routine RTWP tracing data and usage of RTWPAnalysis for checking
inverse connection of antenna feeders
Currently, the following functions are provided by RTWPAnalysis:
2. Saving RTWP data of a cell to a TXT file
3. Generating RTWP data of a cell as a PNG image
4. Checking intercrossing connection of RF antenna feeders in a site
5. Checking intermodulation of antenna feeders
6. Analyzing the difference between RTWP of the main receiver and RTWP of the diversity
receiver in a cell
For details, see the following reference documents:
 Analysis of Routine RTWP Tracing Data and Usage of RTWPAnalysis for Checking
intercrossing Connection of Antenna Feeders.rar
 RTWP Analysis Tool.rar

3 RTWP Troubleshooting Flow
3.1 Criteria for Determining an RTWP Problem

Generally, if the problems shown in Figure 6.1 occur, check whether the RTWP is normal.
This figure also shows the causes for RTWP problems.
Figure 6.1 Symptoms and possible causes for RTWP problems
3.1.1 RF-related Alarms

Check for the NodeB alarms on the M2000 client. Obtain the alarms related to the RF module
and the feeder system. The RTWP is directly or indirectly affected if such alarms are reported.
For details about troubleshooting methods, see section 4.2"Alarm Troubleshooting."
Table 1.1 RF-related alarms

No. Alarm Name (RAN12.0)
1 ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced

2 ALM-26521 RF Unit RX Channel RTWP/RSSI Too Low
3 ALM-26532 RF Unit Hardware Fault

No. Alarm Name (RAN12.0)
4 ALM-26752 ALD Hardware Fault

5 ALM-26758 TMA Running Data and Configuration Mismatch
6 ALM-26755 TMA Bypass
7 ALM-26757 RET Antenna Running Data and Configuration Mismatch
8 ALM-26541 ALD Maintenance Link Failure
9 ALM-26529 RF Unit VSWR Threshold Crossed
3.1.2 M2000 Threshold Alarms

Enable the threshold management function provided by the M2000 to monitor the RTWP
traffic measurement data of an RNC cell. Then check whether the cell RTWP is normal based
on the traffic measurement counters VS.MeanRTWP and VS.HSUPA.UE.Mean.Cell. For
details about the threshold setting methods, see section 6.1"M2000 Threshold Management."
For details about the identification methods and traffic measurement-based troubleshooting
methods, see section 3.2.2"Method 1: Identifying a Problem Based on the Traffic
Measurement Counters."
3.1.3 Abnormal KPIs and Service Complaint

If the KPIs such as call drop rate is abnormal or customers complain about low uplink packet
access (UPA) throughput, check whether the RTWP is normal.
During the proper running process of a cell, the sudden degrade of KPIs (for example, the call
drop rate increases and the HSPA rate decreases) may occur if the cell is interfered with due to
an external interference source and the uplink capacity decreases due to intermodulation
interference. In this case, troubleshoot the RTWP problems.
Check whether the RTWP is high due to intermodulation interference, external interference,
or high traffic especially after the site migration, carrier expansion, and a new site
deployment. You are advised to troubleshoot the RTWP problem by referring to section
3.2"Methods of Identifying and Analyzing RTWP Problems." If the KPIs degrade after
upgrade, the service software may be faulty. In this case, ignore the RTWP. You are advised to
identify the fault according to a normal procedure.
Table 1.2 describes the counter values for your reference.
Table 1.2 Counter values

Counter
VS.MeanRTWP
VS.MinRTWP
Cell.RRC.Att.Fail.Rate
VS.PS.Call.Drop.Cell.Rate
VS.CS.AMR.Call.Drop.Cell.Rate

Counter
VS.CS.VP.Call.Drop.Cell.Rate
Cell.Call.Drop.Rate
VS.CellDCHUEs
VS.HSUPA.MeanChThroughput
The traffic measurement counters to be checked are not all listed in Table 1.2. You are advised
to focus on the counters related to the call drop rate in a cell and the HSPA throughput.
3.2 Methods of Identifying and Analyzing RTWP

Problems
3.2.1 Process for Troubleshooting RTWP Problems
For an abnormal cell RTWP, see the following procedure for identifying the problem:
Figure 6.2 Procedure for identifying an RTWP problem
Overall procedure for analyzing RTWP problems

Description:
1. After analyzing the RTWP in the traffic measurement data, determine whether the cell
RTWP rise is caused by the RAT or external interference.
2. After analyzing the cell RTWP of a single site, identify the possible causes for cell
RTWP rise.
3. If the cause analysis of an RTWP rise fails to effectively identify the interference source,
collect the 2-ms RTWP data included in the cell CDT data and determine the interference
source based on the signal features.
Based on the analysis of traffic measurement data, real-time background noise, and RTWP in
idle and busy hours, the abnormal RTWP symptoms are categorized into the following types
which are used as the input of the troubleshooting procedure for RTWP-related problems:
Upper threshold of high RTWP: > –100 dBm in idle hours; > –90 dBm in busy hours

3.2.2 Method 1: Identifying a Problem Based on the Traffic

Measurement Counters
Analyze the traffic measurement counters shown in Table 1.1. Check whether the problem is
caused by internal causes or external causes based on the correlation between RTWP and the
number of users in a cell.
Table 1.1 Typical RTWP-related RNC traffic measurement counters

VS.MinRTWP VS.MeanRTWP VS.CellDCHUEs
Table 1.2 Abnormal types

Category Type Sub-Category Symptom
PN(minimum Traffic High RTWP The Min RTWP in idle hours is

RTWP in idle measurement(Min stably too high and the Min RTWPs in
hours of the RTWP in idle hours different time ranges are
traffic) of the traffic) consistent.
High RTWP The Min RTWP in idle hours is
intermittently too high and the Min RTWPs in
different time ranges are
consistent.
RTWP in idle Traffic High RTWP The Mean RTWP in idle hours is
hours measurement(Mean stably too high and the Mean RTWPs in
RTWP in idle hours different time ranges are
of the traffic) consistent.
High RTWP The Mean RTWP in idle hours too
intermittently high and Mean RTWPs in
different time ranges are
inconsistent.
RTWP in Traffic High RTWP The Mean RTWP is too high and
busy hours measurement stably consistent with traffic volume.
High RTWP The Mean RTWP is too high and
intermittently is irrelevant to the traffic volume
obviously. The mean RTWP
varies greatly in different time
ranges.
Background Noise Rise When No User Is Connected

If the background noise rises by more than 3 dB when no user is connected, the following
problems may occur (in the descending order of priority levels):
A. RRU-based distributed cell networking: In the RRU-based distributed cell networking, the
background noise always rises by N = 10log (N) dB.

B. Incorrect RF channel configuration: If the RTWP (background noise) rises in a relatively

stable manner when no user is connected and the RTWP rises according to the increase of the
number of users, the RF parameters related to the RF channel may be configured incorrectly,
resulting in the abnormal background noise rise.
C. Continuous external interference: With the impacts of a stable external interference source,
the background noise rises abnormally, as shown in Figure 1.1.
Figure 1.1 Drawing for RNC performance measurement counters (interference at night)

 Figure 1.1 shows the performance measurement data for four days. The green line indicates the
MeanRTWP, the yellow line indicates the MinRTWP, and the blue line the CellDCHUEs (number of
users in a cell). This figure shows that the RTWP continuously rises by more than 5 dB when no user
is connected at night. In this case, the cell is affected by continuous external interference. The causes
for the abnormal RTWP rise cannot be the RF channel configuration or the distributed RRU
networking because the minimum RTWP of the background noise in the day decreases to a normal
value.
 Coordinate description: The longitudinal coordinates in Figure 1.1 indicate the absolute value of the
number of users. The RTWP data is a relative value which is obtained based on the difference
between the counter value and –106. The horizontal coordinates indicate the data SN. (All
subsequent figures are drawn based on such a coordinate description.)
Figure 1.2 Drawing for RNC performance measurement counters (continuous interference)
Figure 1.2 shows the performance measurement counters for four days. The green line indicates the
users in a cell). This figure shows that the RTWP continuously rises by more than 15 dB when only a
few users are connected. In this case, the cell is affected by continuous external interference. In this
situation, you cannot determine the relationship between the RTWP and the number of users. Check
whether the RF channel parameters are configured correctly. This figure shows that the problem cannot
be caused due to parameter configuration because the background noise MinRTWP recovers normally at
certain time.
D. Abnormal RTWP reported from software: Check whether the software is upgraded. If the
problem occurs after software upgrade, the cause may be a software fault.
E. Intermodulation problem: For a feeder system featuring poor intermodulation, obvious
intermodulation occurs even if the transmit source power is low. The problem easily occurs in
the U900/U850 frequency bands and may occur in the U2100 frequency band.

No Association Between RTWP Rise and the Number of Users When the
Background Noise Is Normal
The MeanRTWP (indicated in a green line) rise has no association with the number of users
(indicated in a blue line) in a cell, as shown in Figure 1.1, Figure 1.2, and Figure 1.3. In this
case, analyze the problem based on the adjacent cell data or the data about cells with the same
coverage. Generally, the possible causes for the abnormal cell RTWP are as follows:
 External interference: including the continuous external interference and intermittent
interference
Figure 1.1 Drawing one: RNC performance measurement counters (intermittent interference)

Figure 1.2 Drawing two: RNC performance measurement counters (intermittent interference)
Figure 1.3 Performance measurement data for two adjacent cells at the same time segment

Figure 1.3 shows the performance measurement data for four days. The green line indicates the
users in a cell). This figure shows that the RTWP continuously rises by more than 10 dB, similarly to the
rise in the adjacent cells. In this case, the intermittent random disturbance may affect the measured cell.
 Incorrect feeder connection: The cell RTWP fluctuation may indicate the change to the
number of users in the adjacent cells. Check whether the feeder connection is correct by
referring to the methods in section 3.2.3"Method 2: Identifying a Problem Based on the
Real-time Cell RTWP Tracing of the Main and Diversity Receivers or the Tracing of
Number of Users."
 RRU fault: Analyze the data details by referring to the methods in section 3.2.3"Method
2: Identifying a Problem Based on the Real-time Cell RTWP Tracing of the Main and
Diversity Receivers or the Tracing of Number of Users."
 Service problem: Analyze the data details by referring to the methods in section
3.2.3"Method 2: Identifying a Problem Based on the Real-time Cell RTWP Tracing of
the Main and Diversity Receivers or the Tracing of Number of Users."
The RTWP Changing According to the Number of Users (the More the Number
of Users, the Higher the RTWP Is)
The RTWP changes basically with user behaviors. If the RTWP is abnormally high at certain
time segments, the possible causes are as follows:
A. Intermodulation interference: The interference of generated intermodulation signals
increases with the increase of cell TX power.
B. Adjacent cell interference: If the adjacent cell parameters are configured incorrectly, the
local cell RTWP rises when users are switched over.

Figure 1.1 Drawing for RNC traffic measurement counters (adjacent cell interference)
Figure 1.2 shows the performance measurement data of four days covering three cells. The green line
indicates the MeanRTWP, the yellow line indicates the MinRTWP, and the blue line the CellDCHUEs
(number of users in a cell). This figure shows that the RTWP rises by more than 10 dB in cells 2 and 3
where many users are served. Such an RTWP rise may be caused if the air interface capacity is limited.
In cell 1 where only a few users are served, however, if the RTWP rises more than 10 dB, the adjacent
cell interference may exist.
 Limited number of users: If the number of users served in a cell exceeds the designed
capacity, the number of user accesses increases. As a result, the overall cell RTWP rises.
 Switchover problem: Service is affected by the adjacent cell interference due to the
switchover problem.
 Service problem: To identify the service problem, collect the 1-s RTWP tracing data and
the 2-ms RTWP tracing data in busy hours, and use the methods described in sections
3.2.2"Method 1: Identifying a Problem Based on the Traffic Measurement Counters",
3.2.3"Method 2: Identifying a Problem Based on the Real-time Cell RTWP Tracing of
the Main and Diversity Receivers or the Tracing of Number of Users", and 3.2.4"Method
3: Identifying a Problem by Analyzing Services and Interference Based on the NodeB
CDT Tracing."

Figure 1.2 Drawing for RNC traffic measurement counters (limited capacity)

Figure 1.2 shows the traffic measurement data for four days. The green line indicates the MeanRTWP,
the yellow line indicates the MinRTWP, and the blue line the CellDCHUEs (number of users in a cell).
This figure shows that the RTWP rises by about 15 dB when the number of users is large and decreases
to the normal value when the number of users is small. In cell 54591 shown in Figure 1.2, the number of
users is about 50. In this case, the air interface capacity may be limited. The intermodulation symptom,
adjacent cell interference, and service bugs (or performance algorithm defect), however, comply with the
same principles. Therefore, the problem cause cannot be determined at this point. If such a cell is on the
list of top sites, check whether the passive intermodulation (PIM) exists, whether the configuration of
missing neighboring cells exists, and whether the capacity is limited. In addition, based on the analysis
of smaller granularity-based RTWP data, check whether the algorithm or implementation defect exists.
If only the problem explanation is required, assess the capacity further to determine whether the capacity
is limited.
Figure 1.3 Drawing for RNC traffic measurement counters (a problem in country T)

Figure 1.3 shows the traffic measurement data of four days covering three cells. Though the RTWP rise
is obviously affected by the number of users (the RTWP rises sharply if the number of users is large), the
air interface capacity of the cell may be limited based on the capacity calculation by using the capacity
assessment method described in section 4.5"Traffic Measurement Capacity or Service (Such as Product
Bugs) Factors", and the internal RAT algorithm may be improperly used. This figure shows the RNC
traffic measurement counters (country T problems). The first round of problem identification concludes
that the problems include link deletion of iPhone terminals and high UE open-loop TX power on the
RACH channel. After the optimization on the network side, the RTWP rise is greatly controlled.
Therefore, do not draw hasty conclusions in the case of the live network traffic measurement condition
shown in this Figure 1.3. You are advised to identify the problem based on the methods described in
sections 3.2.3"Method 2: Identifying a Problem Based on the Real-time Cell RTWP Tracing of the Main
and Diversity Receivers or the Tracing of Number of Users"and 3.2.4"Method 3: Identifying a Problem
by Analyzing Services and Interference Based on the NodeB CDT Tracing", and then check whether the
causes for an RTWP rise are identified based on the implementation of the related solutions.
RNC Traffic Measurement Counters Failing to Directly Specify Whether the

Problem Is Caused by External Interference or Internal Interference
Figure 1.1 shows that: when the number of users is large, the RTWP is high; when the number
of users is small, the RTWP is low. Though the RTWP change is not necessarily affected by
the number of users, the internal service may be abnormal. For the traffic measurement data
that cannot come to an exact conclusion even after the basic interference check, analyze the
data details by using the methods described in sections 3.2.3"Method 2: Identifying a Problem
Based on the Real-time Cell RTWP Tracing of the Main and Diversity Receivers or the
Tracing of Number of Users" and 3.2.4"Method 3: Identifying a Problem by Analyzing
Services and Interference Based on the NodeB CDT Tracing."
Figure 1.1 Drawing for RNC traffic measurement counters (unknown causes)
CellID : 54562
18
16
14
12
10
-2
0 24 48 72 96 120 144 168 192
VS.MeanRTWP VS.MinRTWP VS.CellDCHUEs

Analysis of the Making of Network-wide Interference Distribution Drawing

Based on Traffic Measurement
If the cells with abnormal RTWP rise reside in area-based sites, use the MapInfo tool to make
the network-wide interference distribution drawing. Analyze the distribution feature and rules
of cells where the RTWP is abnormal from the aspect of areas, thereby quickly filtering cells
with abnormal RTWP caused by external interference.
Based on the analysis results of abnormal traffic measurement-based RTWP in network-wide
cells (which are marked with abnormal RTWP), add the engineering parameter data such as
longitude or latitude, direction, and angle of a cell to draw the network-wide interference (a
cause for abnormal RTWP) distribution drawing on MapInfo as follows:
Figure 1.1 Schematic drawing of narrowband interfering signals
In general, external system interference most likely leads to the area-based distribution of
cells where the RTWP is abnormal.
In Figure 1.1, the sites or cells (marked red) where the RTWP is abnormal show that most of
the cells where the RTWP is high are located in the long-bar shape with obvious direction in
geographic distribution. Therefore, you can easily determine that the abnormal RTWP in cells
of the long-bar shape is caused by external RAT interference, while the abnormal RTWP in
scattered cells probably due to other causes which must be analyzed in the following
procedure.
Based on the case shown in Figure 1.1, the interference direction is determined after the
analysis. The further troubleshooting finds that a directional microwave device is available on
Baiyun Mountain, Guangzhou, China. This device interferes with the wireless devices in the
upper direction of microwave antennas.

3.2.3 Method 2: Identifying a Problem Based on the Real-time

Cell RTWP Tracing of the Main and Diversity Receivers or the
Tracing of Number of Users
When the cells where RTWP problems may occur are identified after the analysis of traffic
measurement data, identify the cell RTWP problems for a single site. Methods of collecting
the real-time RTWP data of the main and diversity receivers are as follows:
2. On the NodeB LMT, click Board RTWP. In the displayed pane, view the real-time
RTWP data of the frequencies corresponding to the doubted cells. This method is
applicable to identify the obvious RTWP problems in a few sites. (For details, see section
2.4.2"Real-Time RNC and NodeB Tracing (Granularity: 1s).")
3. On the NodeB LMT, enable the RTWP routine test tracing function. Run the MML
command STR RTWPRTTST: TYPE=AUTO;. The cell RTWP data of the main and
diversity receivers is recorded automatically. This method is applicable to identify the
RTWP problems in multiple sites or the intermittent RTWP problems. You are advised to
export the recorded data after 24 hours and then use a related tool to analyze the data.
(For details, see section 2.4.4"RTWP Routine Test (RTWP Tracing of the Main and
Diversity Receivers) and Analysis Tools.")
Table 1.1 RTWP problem categories

Category Type Sub-category Symptom
PN (minimum Real-time High RTWP The pedestal RTWP is high and stable.
RTWP in idle tracing stably
hours of the
traffic) High RTWP The pedestal RTWP is high and the
unstably pedestal RTWPs in different time
ranges are inconsistent.
RTWP in idle Real-time RTWP peak The second-based measured RTWP is
hours tracing too high. If the RTWP rises
abnormally at an interval shorter than
10 seconds, the problem is identified.
RTWP The RTWP rises slowly. If the RTWP
fluctuation rises abnormally at an interval longer
than 10 seconds, the problem is
identified.
RTWP in busy Real-time RTWP peak The second-based measured RTWP is
hours tracing too high. If the RTWP rises
abnormally at an interval shorter than
10 seconds, the problem is identified.
RTWP The RTWP rises slowly. If the RTWP
fluctuation rises abnormally at an interval longer
than 10 seconds, the problem is
identified.
The problem is categorized into the following types based on RTWP of the main diversity and
RTWP of the diversity receiver:

 Large difference between RTWP of the main receiver and RTWP of the diversity
receiver
Figure 3.2 Cell RTWP of the main receiver in busy hours > High cell RTWP of the diversity
receiver in busy hours
Figure 3.1 shows that the difference between RTWP of the main receiver and RTWP of the diversity
receiver in busy hours is not the same with that in idle hours. The difference between the RTWP of the
main receiver and the RTWP of the diversity receiver in busy hours is larger than that in idle hours. The
difference shows that PIM may occur on the main receiver.
A. RTWP of the main receiver is inconsistent with and irrelevant to RTWP of the diversity
receiver. In addition, the RTWP change is not regular.
1. Improper networking configuration (incorrect crossed pairs and feeder connection in
sectors): Determine whether the networking configuration is proper by checking the
correlation between the RTWP changes in adjacent cells. Check whether antennas of the
main and diversity receivers cover the same area.
2. If the RTWP of the main receiver or RTWP of the diversity receiver is high, the
intermodulation interference (on the main receiver) or external interference exists. In this
case, you are advised to check the intermodulation interference and the external
interference.
3. If the RTWP of the main receiver or RTWP of the diversity receiver is abnormally low
and sustains, a feeder may not be connected. Alternatively, an indoor site or the diversity
receiver channel is activated by misoperation.
B. The difference between RTWP of the main receiver and RTWP of the diversity receiver is
basically the same, and the RTWP fluctuation is consistent.
1. The RF channel parameters are configured incorrectly, resulting in inconsistent values
between RTWP of the main receiver and RTWP of the diversity receiver. In this case,
you are advised to check the RF networking and channel parameter configuration
(especially in the site with complex feeder networking).
2. A TMA is faulty, resulting in abnormal uplink gain in one channel.

 Abnormally high RTWP

A. If the RTWP is high for a long time, the possible causes are as follows:
1. An external interference source is always available.
2. Incorrect RF channel configuration: If a TMA is configured, but the channel attenuation
value is not set, or the channel attenuation value is set incorrectly, the RF channel
configuration is incorrect.
3. If the distributed cell configuration is used in the multi-RRU networking scenario, the
cell background noise rises.
B. If the RTWP rises to a peak and sustains for a short time, the possible causes are as
follows:
1. An external intermittent interference source causes the RTWP of the main receiver and
RTWP of the diversity receiver rise within a short time.
2. The feeder system is disconnected or intermodulation interference exists.
3. Service problem: The RTWP of the main receiver and the RTWP of the diversity receiver
sustain a short rise peak due to the terminal services. If multiple users are connected
within a short time, the link deletion of iPhone terminals occurs. For details about
identifying the problem, see the method described in section 3.2.3"Method 2: Identifying
a Problem Based on the Real-time Cell RTWP Tracing of the Main and Diversity
Receivers or the Tracing of Number of Users."
 Abnormally low RTWP
Figure 3.1 Abnormally low cell RTWP of the diversity receiver
Figure 3.1 shows that the RTWP of the main receiver fluctuates greatly, but the RTWP of the diversity
receiver basically remains at –109 dBm. This problem may be caused when the diversity receiver is not
connected to an antenna.
 The RRU or the RFU antenna port is not connected to antennas.

 Incorrect RF channel parameter configuration: The incorrect configuration includes that

of the RF channel interconnection mode for different RF modules and that of the RF
channel gain.
 A TMA is faulty, and fails to provide the RF channel uplink gain.
 The RTWP problem determined based on the RF module may be caused by software
bugs.
 Feeders are damaged and the uplink difference loss increases.
3.2.4 Method 3: Identifying a Problem by Analyzing Services and

Interference Based on the NodeB CDT Tracing
If an RTWP problem cannot be identified based on the analysis of the RTWP of the main
receiver and RTWP of the diversity receiver in a cell, use the NodeB CDT to check whether
the external interference or the internal service causes the problem. The NodeB CDT tracing
provides the reported 2-ms RTWP data which can be matched with the service condition at
the physical layer. For details about data collection, see the method in section 2.4.3"NodeB
CDT." In addition, match the data with the service condition and analyze the problem based
on the provided figure collection.
The onsite personnel can send the collected data on the NodeB CDT to the maintenance
contact person. The R&D personnel analyze the 2-ms RTWP data contained in the CDT data
and snap shot the figure depicting the RTWP problem. The task is related to the service access
mode and must be complete by R&D personnel.
3.3 Other Product or Algorithm Causes (that Must Be

Analyzed by R&D Engineers)
After the troubleshooting of problems based on the output results of Tool for Initially
Troubleshooting RTWP Problem Causes.xls, if the abnormal RTWP is not caused by any of
the preceding causes, send the related data to R&D engineers. With the provided data, the
R&D engineers perform troubleshooting to check whether the abnormal RTWP is caused by
products, algorithms, or UEs.
Table 1.1 Check items

Check Item Result
A single cell has problems.
A single site has problems.

The RF channel configuration parameters are checked.
The adjacent cell configuration is checked.
An intermodulation test is conducted.
A TMA device is deployed and works properly.
The interference source is located in a site.

Table 1.2 Information collection items

Information Collection Item
NodeB main control log

Cell CDT tracing log
Cell RTWP traffic measurement data
Cell RTWP data
RF board RTWP data
Scanned interference result
Scanned spectrum result
RNC configure file
Schematic drawing for the feeder system connection
Feeder device model
Information indicating an indoor coverage system
Data provided to the R&D engineers must include the following:

 Extracted data in the preceding troubleshooting process: including RNC traffic
measurement data, real-time tracing data on the RNC LMT and the NodeB LMT, NodeB
CDT tracing results, and data of an RTWP routine test
 Tool for Initially Troubleshooting RTWP Problem Causes.xls (including the input and
output data) and Template of RF Factor Troubleshooting List.xls
 NodeB configuration file
 Main control logs and configuration of script query delay and script collection channel
(Note that for the RAN12 SPC200 and later versions, the main control logs and RRU
board logs are sufficient and the script collection is not required.)
 An antenna topology diagram (for the cells where 0.5/0.5 RRUs are in one cell)
 Scripts that can be used to query the delay between RRUs in the distribution cells
covering scenarios with high speed
 Performance tracing data or PCHR data for checking whether abnormal RTWP is caused
by the compatibility of iPhone UEs
 Number of HSDPA users in a cell and RTWP data
During the troubleshooting process, the R&D engineers may require other types of data.

4 Troubleshooting Procedure
4.1 Checking the RF Channel Parameter Configuration

The configuration of RF-related parameters is inconsistent with the baseline. As a result, the
RTWP rises abnormally.
Symptom
The settings of RF-related parameters are improper. As a result, the PN and RTWP always rise
or decrease by X dB.
Cause
Based on the fault tree describing the RF-related parameter configuration problems, as shown
in Figure 1.1, troubleshoot the parameter configuration problems according to the difficulty
level. The possible causes are detailed in the following:
Figure 1.1 Abnormal configuration fault tree
Analysis
The settings of RTWP RF-related parameters are affected by the following values queried on
the NodeB LMT:
1. Initial RTWP calibration values
Related commands are as follows:

RAN12.0
DSP RTWPINITADJ
SET RTWPINITADJ
Figure 1.1 Query of initial RTWP calibration values
RAN13.0:
LST RXBRANCH
MOD RXBRANCH

Figure 1.2 Configuration information
Function description:
This function is enabled to query the initial RTWP calibration value. The value is used when a
RTWP problem occurs due to the abnormal RF receiving channel. For the available RF
modules, the receiving channels have been calibrated at delivery. Therefore, this function is
enabled to adjust the channels only when a great RTWP difference is caused due to the
abnormal RF receiving channels. The value ranges from –13 dB to 13 dB. If the initial RTWP
calibration value is set incorrectly, the cell RTWP may be abnormal.
Recommended value: 0
Usually, the initial RTWP calibration value is set to 0. You are advised not to set the initial
RTWP calibration value instead of the receiving channel attenuation value.
2. Receiving channel attenuation value
LST RXATTEN
SET RXATTEN

Figure 2.1 Query results of receiving channel attenuation values
RAN13.0:
LST RXBRANCH
MOD RXBRANCH
These commands are run when a TMA is available. This function is enabled to adjust the
attenuation value when the channel background noise rises due to the TMA gain. If the
parameters are set to values that are smaller than required configuration, the RTWP rises
abnormally. If the parameters are set to values that are larger than required configuration, the
RTWP decreases abnormally. If the receiving channel attenuation value is set, but no TMA is
installed, the RTWP is abnormally low.
The recommended value is as follows:
 If a TMA is available on the feeder and the device runs properly, set the RF channel
attenuation value as follows:

RF channel attenuation value = TMA gain – RF cable attenuation volume

 If no TMA is available on the feeder, set the RF channel attenuation value to 0.
3. RF desensitivity volume
RAN12.0:
DSP RFDESPARAM
SET RFDESPARAM
Figure 3.1 Query results of RF desensitivity
RAN13.0:
LST RRU
MOD RRU

This function is enabled to set the RF Desensitivity parameter of the RF channels. You can
set the RF Desensitivity parameter to adjust the uplink desensitivity volume and reduce the
receiver sensitivity. The setting of the parameter affects all cells in an RRU. If the parameter
is set incorrectly, the cell uplink coverage is affected in terms of the cell KPIs and cell RTWP.
If the parameter is set when the uplink sensitivity of the whole RF module must be reduced,
the allowed values are 0 dB and 10 dB.
4. Desensitization intensity
RAN12.0:
DSP DESENS
SET DESENS
Figure 4.1 Query results of cell desensitization intensity
RAN13.0:
DSP DESENS
SET DESENS
Figure 4.2 Query results of desensitization intensity
This function is enabled to query the RF channel desensitization parameter. After setting the
cell desensitization value, you can reduce the cell uplink sensitivity. If the parameter is set
incorrectly, the cell uplink coverage, the cell KPIs, and cell RTWP are affected.

If the command is run when the uplink sensitivity of a single cell must be reduced, the
parameter values are between 0 dB and 30 dB.
TMA Gain and Working Mode

RAN12.0:
 LST TMAGAIN: This command is run to query the TMA gain.
 SET TMAGAIN: This command is run to set the TMA gain.
 LST TMAMODE: This command is used to query the TMA working mode.
 SET TMAMODE: This command is used to set the TMA working mode.
RAN13.0:
 LST TMASUBUNIT: This command is run to query the TMA subunit configuration.
 DSP TMASUBUNIT: This command is run to query the TMA subunit dynamic
information.
 MOD TMASUBUNIT: This command is run to modify the TMA subunit.
Figure 1.2 Query results of TMA subunit dynamic information

These commands are run to query and set the TMA gain and working mode to ensure that a
TMA works properly. If the TMA gain is set incorrectly, the cell RTWP (background noise) is
abnormal (higher or lower than the normal value). If the TMA works in Bypass mode, the cell
has no uplink gain. As a result, the cell uplink coverage reduces, affecting the KPIs and cell
background noise.
The recommended values are as follows:
TMA gain: varies according to the actual TMA capacity.
Working mode: Normal
4.2 Alarm Troubleshooting

When an RF module or the feeder system is faulty, the related alarms are reported. If any of
the alarms listed in this section is reported, the RTWP may be abnormal, affecting the service
KPIs. Therefore, perform troubleshooting according to the reported alarms:
2. ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced
Cause analysis: The alarm is reported if the difference between RTWP of the main
receiver and RTWP of the diversity receiver is larger than 10 dB.
Handling suggestion:
Symptoms of the reported alarm are as follows:
− The RTWP of the main receiver (or the diversity receiver) is abnormally high, and the
RTWP of the diversity receiver (or the main receiver) is normal. — Clear the alarm
by referring to the method of handling a high RTWP.
− The RTWP of the main receiver and RTWP of the diversity receiver are abnormally
high, and the difference between them is larger than 10 dB. — Clear the alarm by
referring to the method of handling a high RTWP.
− The RTWP of the main receiver (or the diversity receiver) is abnormally low, but the
RTWP of the diversity receiver (or the main receiver) is normal. — Clear the alarm
by referring to the method of handling a low RTWP.
3. ALM-26521 RF Unit RX Channel RTWP/RSSI Too Low
Cause analysis: The alarm is reported when the RTWP received on the RF channel is
lower than –114 dBm.
Handling suggestion:
− The RTWP of the main receiver or RTWP of the diversity receiver is abnormally low.
— Clear the alarm by referring to the method of handling a low RTWP.
− The RTWP of the diversity receiver is abnormally low. In the indoor coverage
scenario, the diversity channel may not be connected to antennas. If two RF modules
are in the same cabinet, the RF interconnection mode may be disabled.
− The RTWP of the main receiver is abnormally low. In the indoor coverage scenario,
the RX and TX channels are separated. As a result, no uplink signal is available on
the main receiver.
4. ALM-26532 RF Unit Hardware Fault
Cause analysis: The RF channel may be faulty, or the RX channel may be faulty,
resulting in abnormal RTWP.

Handling suggestion: Perform a soft reset or a hard reset on the RF module to check
whether the alarm can be cleared. If no, you are advised to replace the RF module with a
required one.
5. ALM-26752 ALD Hardware Fault
Cause analysis: If the TMA gain is invalid in the worst case, services on the RX channel
where the TMA resides are disconnected.
Handling suggestion: Replace the TMA device.
6. ALM-26758 TMA Running Data and Configuration Mismatch
Cause analysis: If the TMA gain or the working mode is inconsistent with the
configuration, the uplink TMA gain is abnormal, resulting in RTWP problems.
Handling suggestion: Reset the TMA gain or the working mode.
7. ALM-26755 TMA Bypass
Cause analysis: The TMA gain is invalid. As a result, the uplink sensitivity decreases,
the sector coverage narrows, and the cell RTWP (background noise) decreases.
Handling suggestion: Check whether the TMA is faulty. If yes, replace the TMA with a
required one. If no, set the TMA working mode to be normal.
8. ALM-26757 RET Antenna Running Data and Configuration Mismatch
Cause analysis: The tilt angle of the antenna is inconsistent with the configured value,
resulting in faulty uplink and downlink coverage. In this case, the cell service and the
RTWP may be abnormal.
Handling suggestion: Reset the tilt angle of the antenna.
9. ALM-26541 ALD Maintenance Link Failure
Cause analysis: If the TMA maintenance links are disconnected, the cell uplink gain
may be abnormal, resulting in the decrease of the RTWP background noise.
Handling suggestion: Check the TMA for the maintenance links. If the links cannot be
restored, replace the TMA device.
10. ALM-26529 RF Unit VSWR Threshold Crossed
Cause analysis: When a standing wave-related alarm is reported, especially in the case
of high standing wave ratio, the feeder may be faulty. The problem may be caused by a
broken feeder.
Handling suggestion: Troubleshoot the standing wave-related problem and clear the
high standing wave ratio.
4.3 Interference Troubleshooting

4.3.1 Rules for Identifying Interference
The interference is categorized into the following types based on the actual conditions:
1. Internal interference and external interference (based on the interference source)
Internal interference: The interfering signals generated in the feeder system are the source of
internal interference, for example, intermodulation interference.
External interference: The interfering signals generated on an air interface are the source of
external interference. For example, the PHS signals, the GSM signals, and interference from
an abnormal interference source are all known as external interference.

If the onsite conditions allow, block the local cell and the adjacent cells and check
whether the problem is caused by internal interference or external interference.
2. Regular interference, continuous interference, and intermittent interference (based on
the interference features)
 Regular interference: Such interference is normally caused by the interfering signals
generated on external devices. Under the impacts of regular interference, the cell RTWP
rises to a peak consecutively and regularly.
 Continuous interference: Under the impacts of continuous interference, the cell RTWP
sustains a high value at a certain time segment.
 Intermittent interference: Under the impacts of intermittent interference, a cell is
interfered with irregularly, and the interference time cannot be determined.
Compared with intermittent interference, the regular interference and continuous interference
can be troubleshot easily because of the stable and obvious symptoms. The interference
source of intermittent interference cannot be effectively located.
3. Single-site interference and multi-site interference (based on the interference
distribution)
 Single-site interference: When a single site or a single cell is interfered with, the
interference source may be near the site or the feeder.
 Multi-site interference: When multi-site with consecutive coverage or multiple cells are
interfered with, a signal source with high power may be available within the coverage.
Single-site interference is normally caused when an interference source is near the feeder.
Therefore, the interference source can be quickly located by troubleshooting.
Multi-site interference must be troubleshot by the geographical auxiliary tool such as
MapInfo. The interference scope is determined based on the engineering parameter data and
cell RTWP data. Then the interference source can be determined after the interference center
is located.

4.3.2 Intermodulation Interference

Symptom
The RTWP changes according to the DL output power. When the output power is high, the
RTWP rises. When the output power is low, the RTWP decreases. When no power is output,
the RTWP recovers normally.
Causes
The PIM feature refers to the intermodulation effect caused by the built-in non-linear features
of the passive components such as the connector, antenna feeder, antenna, and filter in the
environment of multi-carrier with high-power signals. Usually, the passive components are
linear. In the environment of high power, the passive components have non-linear features to
some extent. The non-linear features are generated due to the following factors: contact of
different metal materials, unsmooth contact surface of the same material, loose connection
between connectors, and magnetic substances. The passive components of the antenna feeder
system, such as the connector, feeder, antenna, and filter are not securely connected and water
comes into them. For the same set of antenna feeders, the carrier power rises as the increase of
the number of carriers input into the antenna feeder. As a result, severe PIM is generated in
the antenna feeder system. For the same band, systems in low bands (such as 850 MHz and
900 MHz) are more vulnerable to the impact of PIM than systems in high bands (such as 2100
MHz). Take band 8 as an example. The gap between the uplink frequency and the downlink
frequency is 45 MHz. For band 1, the gap between uplink frequency and downlink frequency
is 190 MHz. Therefore, the gap of band 1 is wider than that of band 8.
Filtering, Check, and Analysis

 Data input: data traced on the NodeB LMT in real time
 Data output: results specifying whether intermodulation interference exists
 Isolation tools: NodeB LMT (common tool) or intermodulation tester (In RAN13.0, the
intermodulation check function is added to the NodeB LMT.)
 Owner: onsite engineers
 Related version: none
 Impacts on the network: If the downlink load simulation test is started, the network
performance is affected.
Two methods are available for judging whether the antenna feeder intermodulation causes the
problem.
 Increase the downlink output power. After that, check the relationship between the
RTWP and the downlink output power of the NodeB.
 Trace the RTWP in on-line mode and analyze the relationship between the traced RTWP
at NodeB and the downlink output power of the NodeB.
By increasing the downlink output power, check the relationship between RTWP and the
downlink output power of the NodeB as follows:
(1) In idle hours when almost no traffic exists (when power of the top port on the RF
module approaches the sum of the pilot power and power of other public channels),
trace the RTWP which must be low. The traced RTWP is about –105 dBm (value of the
PN). Record the RTWP value.

(2) To take full use of the carrier power, use either of the following methods. In addition,
trace the change trend of RTWP of the main receiver and RTWP of the diversity
receiver in a cell on the NodeB LMT.
Method 1: On the NodeB LMT, run STR DLSIM to start the downlink load simulation test.
Set Load Ratio (%) to 99. Record the RTWP. To start downlink load simulation test, do as
follows:
(a) Run DEA CELLHSDPA on the RNC LMT to deactivate an HSDPA cell.
Figure 1.1 Starting downlink load (step 1)
(b) Run ADD RESERVEOVSF on the RNC LMT to reserve DL code numbers 14 and 15.
(c) Run ACT CELLHSDPA on the RNC LMT to activate an HSDPA cell.

(d) On the NodeB LMT, start the downlink load simulation test for all cells on the RF
module. After the startup to a point, stop to observe the RTWP for five minutes.
Method 2: Use a UE near the NodeB to start the HSDPA service. Do as follows:
On the NodeB LMT, start the tracing of downlink power. Use a UE to enable the HSDPA
loading service. Check whether the HSDPA codes are used and whether HSDPA cells can
transmit the maximum power. If the RTWP almost remains unchanged after the downlink load
simulation test or the HSDPA service is started, the antenna feeder does not encounter
intermodulation. If the RTWP changes obviously, for example, the change margin is 5 dB, the
antenna feeder may run improperly. In this case, the antenna feeder intermodulation may
exist.
If the antenna feeder of the system is shared with other network systems such as GSM and
CDMA, the antenna feeder system may contain a foreign system or the UMTS uplink signals
are affected by the PIM generated by the foreign system and the UMTS system in the antenna
feeder system. In this case, block and unblock the foreign system when the RTWP rises to
judge whether the interference is relevant to the foreign system.
To ensure the reliability of the test results, you must repeat the preceding operation and check
the consistence of results.
After the test is complete, the STP DLSIM command must be run on the NodeB LMT to stop the
downlink load simulation test. In addition, the RMV RESERVEOVSF must be run on the RNC LMT
to remove the preceding reserved codes. In the RAN13.0 and later versions, the intermodulation check
function is added on the NodeB LMT.
Trace the RTWP and analyze the relationship between the traced RTWP at NodeB and
the downlink output power of the NodeB.
On the NodeB LMT, start real-time tracing of RTWP and output power from the RF module.
Check the change of RTWP of the main receiver and RTWP of the diversity receiver and the
output power of the RF module. If the output power of the module increases, the RTWP rises.
If the output power decreases, the RTWP declines. In this case, intermodulation may exist in
the antenna feeder system. If the change trend of RTWP is irrelevant to the output power of
the RF module, no intermodulation exists in the antenna feeder system.

Figure 1.5 Schematic drawing of the traced RTWP and the downlink load power in the cells
where intermodulation interference exists
As shown in the preceding figure, after the downlink power loading is started, the RTWP rises
greatly. When the downlink power loading stops, the RTWP recovers. In this case,
intermodulation interference must exist in the tested cell.
From the aspect of accuracy in identifying interference in a cell, the method of starting the
downlink load simulation test is more favorable.
From the aspect of impacts on the network, the method of checking the change trend of
RTWP with power has the least impacts on the network.
Solutions
Check whether the antenna feeder is connected securely. Solve the problems such as improper
connection, component corrosion, and water inflow.
Method of checking intermodulation interference in the onsite scenario
For details, see the following reference document:
The Method to Detect the PIM Antenna System.doc
Case Review
For details about the case, see the Summary on the Processing of Abnormal RTWP in a NodeB
of Smart (Philippine).
Examples for abnormal RTWP due to other internal interference
(1) Multi-frequency intermodulation caused by load
The system is a DAS. The 3G signals combine with the 2G signals of carrier S and the 2G
signals of carrier P at the same time. Carrier P uses the frequency 747 MHz while carrier S
uses the frequency 850 MHz and the frequency hopping (FH) 815 MHz. Figure 1.1 shows the
traced RTWP in the current site:

Figure 1.1 Traced RTWP
The interference in the cell is caused by the loose connection of load. Once the load is
touched, the RTWP changes greatly.
The RTWP change features are as follows: The RTWP of the main receiver is irrelevant to
RTWP of the diversity receiver. Interference is affected by traffic volume to a certain extent.
The RTWP fluctuates at large margin. The interference continues for a certain period. The
time-based change of RTWP is irregular.
(2) Multi-frequency intermodulation caused by improper connection of multiple RF
connectors (such as duplexer connector, feeder, and jumper)
The site is an indoor site where multiple carriers share one DAS. Therefore, the structure of
the antenna feeder is complex, wherein the Hybrid coupler connector, feeder, and jumper are
poorly connected. The traced RTWP is shown in Figure 1.2.
The RTWP change features are as follows: The RTWP fluctuates at large margin. Interference
continues for a certain period. The time-based change of RTWP is irregular.
(3) Intra-frequency intermodulation caused by poor connection between the feeder and
the jumper
The 2G signals in the site that are transmitted on the combined channel with 3G signals
occupy one frequency. The feeder cable and jumper connector are poorly connected. As a
result, intermodulation interference occurs in the site. Figure 1.3 shows the structure of the
antenna feeder and the traced RTWP:

Figure 1.3 Structure of the antenna feeder (left) and the traced RTWP (right)
RTWP of the diversity receiver. The RTWP fluctuates at large margin. Interference continues
for a certain period. The time-based change of RTWP is irregular.
(4) Multi-frequency intermodulation generated by 2G and 3G signals together
In an indoor site, the 2G signals combine with 3G signals. The site shares one DAS with other
carriers. Figure 1.4 shows the traced RTWP in the site.
The main receiver interference (red lines) shown in the preceding figure is caused by
intermodulation generated by DCS signals and 3G signals at a certain connector.
The blue lines in the preceding figure indicate the diversity receiver signals. The diversity receiver is not
connected to antennas. Therefore, the external interference near the cabinet attacks the diversity receiver,
resulting in the blue peaks.
RTWP of the diversity receiver. The RTWP fluctuates at large margin. Interference continues
for a certain period. The time-based change of RTWP is irregular.

4.3.3 Inter-RAT Interference

Symptom
The interference from an external source is in endless variety. The identification of the
interference source depends on specific instruments and skills of onsite RF engineers.
Solutions vary according to the types of specific interference source and are related to the
policies made by local carriers and the radio committee.
No specific symptom identifies the interference from an external source. Therefore, the
interference from an external source must be excluded first before locating RTWP
abnormalities.
The standard bandwidth of UMTS signals is 5 Mbit/s. The signals of interference from an
external source contain the narrowband interfering signals with the bandwidth less than 5
Mbit/s and wideband interfering signals with the bandwidth greater than 5 Mbit/s. The signals
with the bandwidth equal to 5 Mbit/s are rare and can be omitted.
1. An example of external interfering signals with the bandwidth smaller than 5 Mbit/s
from a narrowband system is as follows:
Figure 1.1 Schematic drawing of narrowband interfering signals
2. An example of external interfering signals with bandwidth greater than 5 Mbit/s from a
wideband system is as follows:

Figure 2.1 Schematic drawing of wideband interfering signals
Causes
1. Illegitimate occupation of frequencies: Other systems (such as a communication system
or a microwave system) illegitimately occupy the RX frequencies configured for carriers,
resulting in the in-band co-channel interference for the uplink band.
2. Insufficient out-band radiation of other systems: The 3GPP protocol defines the
bandwidth of the downlink (DL) signals of communication systems. If the out-band
radiation of other communication systems fails to meet the specified scope, the generated
out-band radiation falls in the RX band exactly, resulting in in-band co-channel
interference. In addition, for the indoor distributed antenna system (DAS) with multiple
systems combined, if the isolation between the inter-RAT input port of combiner units is
insufficient, the RAT is interfered with by scattered out-band interference between
systems.
3. Out-band congestion: The local frequency resources are allocated on the adjacent
channels of the RX band of the local RAT, allowing the DL signals of other systems. If
the isolation between the local RAT antenna and another system antenna is insufficient,
the out-band congestion interference occurs.

 Data input: data traced on the NodeB LMT
 Data output: spectrum drawing
 Isolation tool: NodeB LMT or PYC script
 Owner: The analysis must be complete by onsite engineers by using the built-in
interference check or spectrum check function (provided in RAN13.0) of the NodeB
LMT. The PYC script is used to collect data by onsite engineers. R&D engineers analyze
the collected data.


 Impacts on the UMTS network:
Identify the impacts by using the following methods:
1. The onsite engineers can use the built-in interference check function of the NodeB LMT
to identify the impacts.
2. The onsite engineers can use the built-in spectrum check function of the NodeB LMT to
identify the impacts. The RAN13.0 and later versions provide the built-in spectrum
check function.
3. The onsite engineers collect data by using the PYC script provided by R&D engineers
and then send the data to the R&D engineers for analysis.
The details of the preceding three methods are as follows:
(1) Using the built-in interference check function of NodeB LMT
The interference check function in online mode can be used directly, which does not affect
services, to check whether interfering signals of other types (for example, GSM and LTE
signals with RBW = 15 kHz) exist in the bandwidth of 3.84 MHz in cells where the RTWP
rise is abnormal. The following methods can be used.
(a) If the RRU3804 module of 850 MHz (namely, band 5) is used and one UMTS cell is
configured in the onsite scenario, the uplink frequency number is 4140 and the RTWP of
this configured cell is always high.
Figure 3.1 Schematic drawing of using the interference check function of the NodeB LMT (1)
(b) When the RTWP in a configured cell is high, enable the online interference check
function, the tested frequency number is 4140. If the signals similar to the abnormal
signals (non-interfering signals with the bandwidth of 5 Mbit/s in the narrowband
system) shown in Figure 3.2 are detected on the spectrum, it can be determined that the
in-band interference exists. That is, multiple signals with the bandwidth which is much
higher than the bandwidth of the PN are discovered in the band.

Figure 3.2 Schematic drawing of using the interference check function of the NodeB LMT
(interference check, RWB = 15 kHz)
In the current online interference check mode, the scanned bandwidth is only 3.84 MHz. The
UMTS signals occupy the bandwidth of 5 MHz. Therefore, the spectrum edge within the 5
MHz beyond the 3.84 MHz cannot be scanned.
For details about how to use the interference check function of the NodeB LMT, see the
Usage Guide to Interference Check of NodeB LMT.
(2) Using the spectrum check function of NodeB LMT
The NodeB RAN13.0 and later versions provide the spectrum check function featuring high-
precision online scanning of carrier spectrum, online wideband carrier scanning, and offline
wideband spectrum scanning.
For details about the function, see the Guide to Usage of Spectrum Check of NodeB RAN13.0.
Take the online wideband spectrum scanning as an example. The scanning results after the
monophonic signals are fed in the diversity receiver are shown in Figure 3.3.

Figure 3.3 Scanned spectrum of analog interfering signals after the monophonic signals are fed
into the diversity receiver
(3) Using the PYC script to collect data

The built-in interference check function of the NodeB LMT is convenient for onsite engineers
and the results can be obtained directly in multiple scenarios. In certain complex scenarios,
however, the function is useless. For example, the RTWP is high and the overall PN rises in a
cell where no in-band interfering signal is detected. Therefore, the PYC script provided by the
R&D engineers must be used to collect data for further analysis.
For details about how to use the PYC script, see the Usage Guide to PYC Script.
The PYC script may vary according to different RF modules and NodeB version. Therefore, the onsite
engineers must inform the maintenance department of the module code and NodeB version. The MML
commands LST BRDINFO and LST VER can be used to query the module code and NodeB version
information. The PYC script is baselined and is to be archived. The script can be obtained directly from
the TAC.
Analysis of PYC script (performed by R&D engineers currently):

Figure 3.4 Typical interfering signals (varying according to the board type and analyzed
spectrum)
Figure 3.5 Typical UMTS signals (with double carrier configuration, wherein the RTWP in high
frequency cells rises)
Rules for judging interference from an external source based on the scanned spectrum are as follows:
Generally, the interference from an external source presents on the spectrum in the following modes:
 Narrowband interference with the bandwidth smaller than the UMTS carrier bandwidth
The interference on the UMTS network due to the intermodulation of other narrowband systems, such as
the GSM, presents as a peak where the bandwidth is smaller than the UMTS single-carrier bandwidth of
5 Mbit/s on the UMTS uplink in-band RX spectrum, as shown in IStep 1Figure 1.1.

 Wideband interference with the bandwidth greater than the UMTS carrier bandwidth
In addition to narrowband interference, the interference from an external source may refer to the
wideband interference with the spectrum width greater than 5 Mbit/s. The wideband interference can be
identified only after the scope of uplink spectrum scanning is extended to the width greater than one
UMTS carrier.
Solutions
The RF engineers perform troubleshooting to exclude the local interference. After that,
relative solution can be determined based on the type of interference source. The operating
interface of Huawei supports is used to search for the interference source but cannot remove
the interference source.
 Methods of locating external interference in the onsite scenario are as follows:
Preparation:
The exact start time and end time of external interference are unknown in general. Therefore,
full preparation and detailed analysis must be complete before the onsite operation to improve
the efficiency.
Pay attention to the following points during the preparation:
(1) Data to be collected
 RTWP data around the clock of a week (at least three days) about the cell under
measurement and the peripheral cells
 MapInfo drawing showing the location of sites, relative locations of sites, and distance
between sites (Nastar is recommended.)
 Antenna azimuth angle and antenna height of all cells
 Pictures of all cells for survey
 Whether the cell under measurement is the source signal cell of the repeaters
 Distribution of 2G and 3G repeaters around the cell under measurement
 Distribution of PHS NodeBs around the cell under measurement
 Drawing that shows the antenna feeder structure of the cell under measurement
(2) Analysis to be performed and expected conclusion
Analysis 1: the long-term and short-term features of RTWP data about a cell under
measurement and traced in different periods
Expected conclusion 1: When to locate the interference in the cell after the time range when
interference is concentrated is worked out according to the time-based feature of RTWP?
Analysis 2:
 Long-term and short-term features of RTWP in the peripheral cells of the cell under
measurement in the same period
 Environment of the cell under measurement according to the provided materials such as
pictures of the cells for survey and the drawing that shows the location of cells
 Correlation between the main receiver and diversity receiver of a cell under
measurement according to the structure of antenna feeders
 Using the angle of arrival (AOA) method to combine the RTWP data of the cell under
measurement with that of the peripheral cells, and the antenna orientation and height to
predict the interference source location: Determine the direction of the interference
source to the local site according to the antennas of multiple NodeB cells. After that,

mark the direction on a map. The point of intersection of all antenna orientation indicates
the position of the interference source.
Figure 1.1 Using the AOA method to locate the interference source
Expected conclusion 2: Where to locate the interference source?

(3) Onsite location method and procedure
(a) Start the NodeB LMT to measure the RTWP of the cell under measurement in real time
and monitor the start time and features of external interference.
(b) On the platform where antennas are installed, check the actual condition of the
peripheral antenna environment for metal obstacles, distribution of antennas of other
network systems or other carriers on the platform, and especially the objects that are
worth doubting.
(c) Connect a YBT250, an AC filter, and an antenna to test the intensity, orientation, and
spectrum features of interference.
(d) Determine the location of the interference source under doubt based on the preceding
analysis.
(e) Check the relationship between the status change (such as on, off, enable, and disable) of
the determined interference source and the interference: For the devices controlled by
carriers, such as repeater, power on or power off the devices at proper time upon
agreement of the carriers to verify the relationship between the operations and
interference. For the devices that are not controlled, the method of observation at
suitable time is applicable.
For details about how to use YBT250, see the Guide to Testing W-Electromagnetic
Interference-20041101-B-2.0.

Case Review
For details about the case, see the Summary on Locating Interference of the WCDMA
Microwave Wideband in Guangzhou Unicom and Nanning Unicom.
Examples for RTWP under other external interference are as follows:
(1) The self excitation of a repeater interferes with the peripheral sites.
Figure 1.1 Location of sites
The preceding figure shows the location of the 501800 site and the peripheral ones. One 3G
repeater near the 501800 site encounters self excitation and generates a self-excitation signal
at an interval of about one hour. As a result, the uplink bands of multiple peripheral cells are
interfered with. The interference level varies greatly according to the distance between and
direction of cells and the 3G repeater. The abnormal RTWP of all cells, however, occurs
clearly at an interval of one hour.
Figure 1.2 RTWP traced in neighboring cells

The 501800 site is an indoor site with a single antenna for receiving signals.
The RTWP change features are as follows:

 The RTWP of the main receiver is relevant to the RTWP of the diversity receiver.
 The RTWP change affects multiple neighboring cells.
 The interference changes abruptly.
 The interference appears at regular intervals.
(2) The self excitation of a repeater causes the interference of uplink bands in the
source signal cell of the repeater.
In the 45680 site, a 3G repeater is deployed. The source signal cell of the repeater is the
54291 cell of the site. The occurrence of self excitation in the repeater is irregular. Figure 1.3
shows the measured RTWP.

The RTWP change features are as follows:

 The RTWP of the main receiver is relevant to the RTWP of the diversity receiver.
 The interference changes abruptly.
(3) The improper gain setting and self excitation of a repeater cause the interference of
uplink bands in the source signal cell of the repeater.
The gain for the repeater of the 45680 site is set to 90 dB. Figure 1.4 shows the traced RTWP.
Figure 1.4 Traced RTWP in the 45680 site
If the gain setting is adjusted to 70 dB, the RTWP recovers normally.

The RTWP change features are as follows: When the gain setting of a repeater is incorrect, the
RTWP changes specially. That is, the interference stays high and stable.
(4) The 3G antenna encounters close irradiation of a 2G repeater antenna, resulting in
the interference of the uplink bands.
The 3G antenna of the 45680 site encounters close irradiation of 2G repeater antenna of
another carrier and the 3G antenna has space diversity. The 3G antenna shown in Figure 1.5 is
a diversity antenna and the main antenna diversity is far from the 2G antenna. Figure 1.5
shows the antenna position and measured RTWP:

Figure 1.5 Antenna position (left) and measured RTWP (right)
The RTWP change features are as follows: The RTWP of the main receiver is relevant to
RTWP of the diversity receiver. The interference changes abruptly.
(5) When a train crosses the site, the RTWP changes.
The 45680 site is near a railway station where the train shift is dense. Figure 1.6 shows the
site location and traced RTWP.
Figure 1.6 Site location (left) and traced RTWP (right)
(6) When the status of an indoor air conditioner controller switches over, the uplink
bands of the site are interfered with.
Figure 1.7 shows the interference with uplink bands when the status of an indoor air
conditioner controller switches over.

Figure 1.7 Traced RTWP in real time — air conditioner 1
(7) When the site encounters the startup or stop of an outdoor air conditioner of
another carrier, the uplink bands are interfered with.
Figure 1.8 shows the traced RTWP.
Figure 1.8 Traced RTWP in real time — air conditioner 2
(8) When an indoor emergency light switches over from the on state to the off state, the
uplink bands are interfered with.
Figure 1.9 shows the traced RTWP changes (enclosed in red) when the indoor emergency
light switches from the on state to the off state.

Figure 1.9 Traced RTWP in real time — emergency light
(9) Uplink interference occurs at an interval of 200 seconds (The interference may be
caused by the compressor of an air conditioner. Due to the property-related causes, no
experiment can be conducted to prove the correctness of the doubt.)
Figure 1.10 shows the long-term features and short-term features of traced RTWP.
Figure 1.10 Long-term features (left) and short-term features (right) of traced RTWP
RTWP of the diversity receiver. The interference changes abruptly. The interference appears
at regular intervals.
(10) Interference is generated by the YBT250 itself at the frequency of 1924.3 MHz
(when the directional antenna connecting YBT250 is close to the device).

Figure 1.11 Spectrum when the directional antenna connecting YBT250 is close to the device
Note the feature of YBT250 in locating the interference source.

(11) Uplink interference is generated on a transmission line.
Figure 1.12 Interference generated on a transmission line
(12) Interference is generated similarly to the interference generated due to self

excitation of a repeater.
Figure 1.13 shows the long-term features and short-term features of traced RTWP.
Figure 1.13 Long-term features (left) and short-term features (right) of traced RTWP
Figure 1.14 shows the features of the observed spectrum.

Figure 1.14 Spectrum features
In addition to the features shown in the preceding static figure, the spectrum has the following
additional features:
(a) The spectrum is scanned between the frequency range of 1914 MHz to 1951 MHz.
(b) The spectrum change margin varies according to the frequencies.
(c) After a period of scanning, the frequency jumps.
RTWP of the diversity receiver. The interference changes abruptly.
4.4 Network Planning

4.4.1 Neighboring Cell Interference
If a neighboring cell is missing in the configuration, a few of UEs under the missing
neighboring cell cannot be switched over to the local cell even when the UEs are far away
from the neighboring cell and enters the coverage area of the local cell. With the increase of
path loss between the UEs and the missing neighboring cell, the RX power rises. The
coupling loss between the UEs and the cabinet top ports of the local cell decreases gradually.
In this case, the local cell is interfered with and the RTWP of the cell rises.
Symptom
The missing configuration of neighbor cells has few impacts on the RTWP rise and results in
small margin of RTWP rise (rise margin < 10 dB). The RTWP peak usually lasts about a few
seconds or dozens of seconds. The RTWP peaks occur irregularly and have no mapping with
the traffic volume of the local cell in idle hours or busy hours.
When UEs of the DAS sites are near the DAS port, the coupling loss of the cell with
interference is smaller than that of the outdoor cells. Therefore, the rise margin of indoor
distributed sites is greater than that of outdoor sites.
Causes
If a neighboring cell is missing in the configuration, a few of UEs under the missing
neighboring cell cannot be switched over to the local cell even when the UEs are far away

from the neighboring cell and enters the coverage area of the local cell. With the increase of
path loss between the UEs and the missing neighboring cell, the RX power rises. The
coupling loss between the UEs and the cabinet top ports of the local cell decreases gradually.
In this case, the local cell is interfered with and the RTWP of the cell rises. When the path loss
between the UEs and the local cell is greater than that between the UEs and the serving cell
by about 10 dB, call loss occurs. Therefore, the interference margin cannot be greater than 10
dB.

 Data input: PCHR data and MML files
 Data output: a table describing the missing neighbor cells
 Isolation tool: NPMaster
The NPMaster tool and usage guide of the tool are available at the following URL:
http://support.huawei.com/support/pages/editionctrl/catalog/ShowVersionDetail.do?
actionFlag=clickNode&p_line=&node=000001410343&colID=ROOTWEB|
CO0000000065&
For details about the operation procedure for troubleshooting of missing neighbor cells, see
section 7 "NeighborHood" in the Manual of NPMaster_UMTS_Several Methods.
 Impact of isolated analysis on the UMTS network: none
Solutions
Complete the configuration of missing neighboring cells.
Case Review
For details about the case, see the Guide to and Cases of Co-channel Neighborhood
Optimization.
4.4.2 Strong Coverage

The RX power of UEs ranges from –50 dBm to +21 dBm. When the power control is normal,
the UEs can adjust the TX power with the change of wireless channel. When the wireless
channel is in over-coverage state, the TX power is higher than the required TX power on the
NodeB even if the UEs transmit signals at the minimum TX power. As a result, the RTWP
rises.
Symptom
The maximum rise margin of the RTWP in this case is relatively small (for example, the
maximum rise margin ranges from 10 dB to 20 dB). The duration of an RTWP peak, however,
is long, ranging from one minute to dozens of minutes. In addition, if the RTWP is traced by
day, the RTWP peak occurs regularly. For the cells covering special scenarios such as stadium
and exhibition and convention center, the occurrence of RTWP peak may not be regular.
In addition, the traffic measurement shows that the frequency at the time range when RTWP
peaks occur has linear relationship with the user number. When the user number and user

throughput are far lower than the cell capacity threshold, the RTWP rises greatly at longer
interval compared with the RTWP rise due to limited capacity.
The proportion of high RSCP in a cell and the proportion of high RX power of a UE are both
high.
Causes
Due to strong coverage of a cell, the mean coupling loss between a NodeB and UEs is small.
When a few of UEs approach the antenna, the uplink power control has reached the minimum.
As a result, the RTWP rises greatly.

 Data input: conceptual diagram of indoor distribution; recording of power test at the
antenna port or MR data
 Data output: Certain points may be under good coverage. To confirm further, perform
dial test on the points to verify the coverage.
 Isolation tool: For details, see case review in the following section. (A prototype tool is
available for extracting coupling loss.)
 Impacts on the UMTS network: The analysis has no effect on the network if the antenna
feeder system is not processed.
(1) For indoor sites, analyze the conceptual diagram of the system to check whether
power at the antenna port is high. In addition, check whether the antenna is mounted
high, insufficiently, or near UEs according to the actual conditions. Generally, a
distance of two meters must be kept between the indoor antenna and UEs.
(2) Based on the MR data, gather statistics of the distribution of coupling loss in the
cell. Check whether the coupling loss is small. (Generally, the minimum coupling
loss must be greater than 70 dB.) If no, no power control failure occurs due to strong
coverage.
Solutions
For an indoor site, the indoor coverage vendors must rectify the antenna feeder system.
Case Review
For details about the case, see the Guide to UMTS Scenario Quantification — Extracting
Coupling Loss.
4.5 Traffic Measurement Capacity or Service (Such as

Product Bugs) Factors
Symptom
The RTWP problem caused by high traffic has the following symptoms (based on the real-
time RTWP data on the RNC LMT):

1. The rise in the number of users in a cell is consistent with the cell RTWP rise. Generally,
if the number of users in a cell rises, the service proportion for a carrier does not change
greatly. In addition, the number of users in a cell almost equals the traffic performance of
the related device in Huawei. (A related figure is required.)
2. The number of users in a cell increases sharply in a sudden manner, causing RTWP
peaks, as shown in Figure 2.1.
Figure 2.1 Relationship between the number of users in a cell and RTWP peaks
The service-related problems may be triggered in a high-traffic scenario. Therefore, if the

RTWP problem is caused due to traffic, troubleshoot the service-related problems first.
Cause
The abnormal RTWP rise is directly caused after the user uplink load increases. For example,
when the uplink load reaches the capacity threshold of a cell, the RTWP rises to the
maximum. If the admission control algorithm is disabled, the RTWP stays high continuously
in the high traffic cell due to severe capacity overloading.
The service volume fluctuates with time. Therefore, the RTWP peaks vary according to time
with moderate change margin. The change trend of RTWP is consistent with that of service
volume.
Analysis
1. Analyze the problem by referring to the UMTS Performance_Performance Baseline for
Uplink capability V1.0.rar
2. Analyze the problem by using tools such as a tool for analyzing the uplink capacity (The
tool prototype will be available by the end of November 2011.)
Solution
For details about the solution, see the Summary of RTWP Optimization Solutions for High-
Traffic Cells.ppt.

Case Review
For details about the case, see the Report on Analysis of RTWP Peak and Low RRC Access
Success Rate of Guangzhou Unicom.

5 Improvement Actions for RTWP Problems
5.1 Improvement Actions on the Feeder System

5.1.1 Improvement Actions for Intermodulation Problems
If the feeder system is under the impact of intermodulation interference, take the following
improvement actions:
1. Test the feeders with intermodulation interference to locate the components with
intermodulation problems. Replace such components with required ones.
2. Check whether metal obstructions are available in front of antennas. If yes, adjust the tilt
angle of antennas to prevent signals from being transmitted to the metal obstructions
directly.
3. In a multi-frequency feeder system, calculate the 3-order, 5-order, 7-order, and 9-order
intermodulation products between all frequencies to prevent the frequency signals from
falling onto the cell uplink bands. If the frequency signals fall onto the cell uplink bands,
ensure that the intermodulation counter of the feeder system meets the requirement to
avoid interference.
For details about intermodulation problems, see the Introduction to Intermodulation
Principle -For Customer V1.0.ppt.
5.1.2 Improvement Actions on External Interference

If the system is under the impact of external interference, take the following improvement
actions:
4. For the area-based interference caused by a large interference source, locate the
interference source and rectify the fault.
5. For the interference source in a single site or in a single cell (for example, the interfering
signals are generated in other feeder systems), adjust the horizontal and vertical distances
between the feeders and the interference points to increase the isolation.
6. For the wide uplink interference from foreign systems (such as the CDMA system),
install a filter in the system to reduce the interference.

5.2 Improvement Actions for RF-related Configuration

Problems
5.2.1 Improvement Action on RF Channel Parameters
7. In a complex feeder system, measure the feeder loss accurately and then adjust the
channel attenuation value. For example, check the combiner, divider, and splitter usage
in the feeder system.
8. In a repeater, adjust the repeater parameters to avoid the interference with the cell uplink
service.
9. If the cell coverage scope is abnormal, change the tilt angle of feeders to adjust the
coverage scope and reduce the impact of abnormal service on the RTWP.
10. Check the cell scenario. For example, if a cell is configured with 2-antenna, but the
actual scenario is a single-antenna cell, adjust the cell configuration to a single antenna.
11. For a scenario configured with distributed cells, adjust the background noise value of the
cell.
12. If two RF modules are in the same cabinet, and the RF interconnection mode-based
scenario is required, check whether the RF interconnection mode is enabled. In addition,
the RF interconnection links must be online. If the RF interconnection links are offline,
no signals are available in the diversity receiver.
5.3 Service-level Improvement Actions

5.3.1 Improvement Action to Optimize the Performance
Parameters
Table 1.1 The performance parameter optimization may affect the network. Therefore, you are advised to take the
improvement action under the R&D engineers' assistance. RTWP optimization measures
RTWP Optimization
Measure Supported Impact Available Measure to Implement Remarks
Version Scope Different Versions ation
RA RA RA RAN13
N10 N11. N12 .0
.0 0 .0
Optimizing CQI All RNC and     The These measures
feedback period cell measure are common
can be and preferred.
Optimizing the All Cell     used onsite
access-related directly.
parameter (in the
DAS)

RTWP Optimization
Optimizing the All RNC    Internal
fixed 10-ms PO parameters are
involved in
RAN13.0 and
earlier versions.
Rectifying the RAN12.0 RNC   The solution is
iPhone 4 link provided in
deletion problem RNC
R12SPC516.
Enabling the EFD RAN12.0 RNC   The The EFD
function measure function is
has enabled for
impacts on improving the
KPIs. network where
the iPhone
terminals have a
high penetration
rate.
Optimizing the 2- RAN10.0 RNC    R&D The internal
ms RTWP and the engineers parameters are
fixed PO must take involved.
part in
Performing SIB 7 RAN12.0 Cell   implementi
RTWP control ng
measures. The measure is
provided in
NodeB
R12SPC430.
Performing the RAN13.0 RNC  If the fixed PO
HSUPA PO optimization is
autosensing different,
adjustment change the
service to 10-
ms service by
using the
measure.
Enabling the RAN10.0 RNC    
HSUPA load-
based TTI switch
+ disabling the 2-
ms period
reattempt
Setting multi- All Cell    
antenna receiving

RTWP Optimization
Performing 0.5/0.5 All Cell    
reconstruction
Performing multi- RAN13.0 NodeB 
RRU
demodulation
Changing the All RNC     These measures
HSUPA target are not
retransmission common. The
times to 10% onsite personnel
are advised to
Changing the PS All RNC     select a site to
R99 target BLER implement the
to 10% measures.
Disabling the RAN10.0 RNC and    
HSUPA 2 ms NodeB
function
Restricting the All Cell    
maximum HSUPA
users in a cell
For details about the optimization measures listed in Table 1.1, see the Summary of RTWP
Optimization Solutions for High-Traffic Cells.ppt.
5.3.2 Improvement Action for Device Capacity

13. In a site where the baseband resource capacity is limited, the RTWP may be higher than
the expected value due to user access congestion. In this case, the size capacity must be
expanded to reduce the traffic in the NodeBs.
14. When the free capacity of a service processing board on the MBSC side is insufficient,
the cells created based on the board may be inaccessible. As a result, the user accesses
congest. In this case, adjust the service subrack capacity on the MBSC of the NodeB to
reduce the traffic on the service processing board.
15. In a multicarrier sector, a suitable cell load policy ensures the effective usage of NodeB
resources. If the policy is used incorrectly, users served in some cells encounter access
congestion, resulting in abnormally high RTWP. In this case, properly adjust the cell load
policy to ensure the user load balancing between cells.
16. If the transport is limited, the transport resources may not be allocated, resulting in
difficult user access. In this case, expand the capacity for transport.
17. If the RTWP is high when the capacity on the air interface is limited, but the free
baseband resource capacity is rich, use the 4-antenna rectification solution to improve
the UL capacity and reduce the cell RTWP.

6 References
6.1 M2000 Threshold Management

Step 2 Open the Threshold Setting window.
Figure 1.1 Threshold Setting window

Step 3 Set the threshold alarms.

Figure 1.1 shows that a customized alarm is named RTWP_Interference_Alarm. The
M2000 automatically allocates an alarm ID 40926.
Figure 1.1 Threshold alarm setting
----End
Alarm setting rules are as follows:

Prerequisites for generating alarms: alarm threshold setting is optional.
 Select a site with high RTWP as an abnormal site and set a single counter value as
follows: [VS.MeanRTWP]>{-95.0}
 Select a site that is interfered with. Set a combined counter value as follows:
[VS.MeanRTWP]>{-95.0})&&([VS.HSUPA.UE.Mean.Cell]<{0.5}

If the counter value is set as follows, an alarm is cleared: [VS.MeanRTWP]<{-100.0}

The specific alarm value for triggering the reporting of an abnormal RTWP is determined by
the onsite personnel based on the actual network coverage. If the actual UL service volume in
the network is large, set the RTWP threshold to a large value. If the actual UL service volume
is small, set the RTWP threshold to a small value.
Figure 1.2 Threshold settings
----End

6.2 References
References of this guide are as follows:
2. Guide to Methods of Collecting Data of an RTWP Routine Test and Usage of
RTWPAnalysis.doc
3. Initially Troubleshooting RTWP Problem Causes.xls
4. RF Factor Troubleshooting List.xls
5. Summary of RTWP Optimization Solutions for High-Traffic Cells.ppt
6. Introduction to Intermodulation Principle -For Customer V1.0.ppt
Attachment For
UMTS RTWP Troubleshooting.rar

UMTS RTWP Troubleshooting Guide - 20111201-A-V1.0

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

UMTS RTWP Troubleshooting Guide - 20111201-A-V1.0

Caricato da

Copyright:

Formati disponibili

Prepared by Liu Qiong, Zhang Junjie, Date

Huawei Technologies Co., Ltd.

2011-10-27 V1.0 Completed Zhangjunjie

2019-1-15 Huawei Confidential Page 2 of 87

3 RTWP Troubleshooting Flow...................................................................................................25

2019-1-15 Huawei Confidential Page 3 of 87

4.4.1 Neighboring Cell Interference................................................................................................................75

5 Improvement Actions for RTWP Problems...........................................................................79

2019-1-15 Huawei Confidential Page 4 of 87

Figure 1-1 Possible causes for RTWP rise..............................................................................................................9

Figure 2-1 Method of measuring RTWP...............................................................................................................10

Figure 2-4 ReC of the UL load factor and ROT...................................................................................................14

Figure 2-5 RTWP data collection nodes...............................................................................................................15

Figure 2-6 Real-time RTWP tracing on the RNC LMT........................................................................................16

Figure 2-11 Schematic drawing of tracing results on the NodeB LMT................................................................19

Figure 2-12 Cell RTWP tracing on the NodeB LMT............................................................................................20

Figure 2-13 Schematic drawings of settings for user tracing................................................................................21

Figure 2-14 Schematic drawing of settings for cell tracing..................................................................................22

Figure 3-1 Symptoms and possible causes for RTWP problems..........................................................................25

Figure 3-2 Procedure for identifying an RTWP problem......................................................................................27

2019-1-15 Huawei Confidential Page 5 of 87

Figure 3-12 Schematic drawing of narrowband interfering signals......................................................................38

Figure 3-14 Abnormally low cell RTWP of the diversity receiver.......................................................................41

Figure 4-1 Abnormal configuration fault tree.......................................................................................................44

Figure 4-2 Query of initial RTWP calibration values...........................................................................................45

Figure 4-3 Configuration information...................................................................................................................45

Figure 4-4 Query results of receiving channel attenuation values........................................................................46

Figure 4-5 Configuration information...................................................................................................................47

Figure 4-6 Query results of RF desensitivity........................................................................................................48

Figure 4-7 Configuration information...................................................................................................................48

Figure 4-8 Query results of cell desensitization intensity.....................................................................................49

Figure 4-9 Query results of desensitization intensity............................................................................................49

Figure 4-10 Configuration information.................................................................................................................50

Figure 4-11 Query results of TMA subunit dynamic information........................................................................50

Figure 4-12 Starting downlink load (step 1).........................................................................................................55

Figure 4-13 Starting downlink load (step 2).........................................................................................................55

Figure 4-14 Starting downlink load (step 3).........................................................................................................55

Figure 4-15 Starting downlink load (step 4).........................................................................................................56

Figure 4-17 Traced RTWP....................................................................................................................................58

Figure 4-18 Traced RTWP....................................................................................................................................58

Figure 4-20 Traced RTWP....................................................................................................................................59

Figure 4-21 Schematic drawing of narrowband interfering signals......................................................................60

Figure 4-22 Schematic drawing of wideband interfering signals.........................................................................61

2019-1-15 Huawei Confidential Page 6 of 87

Figure 4-29 Location of sites................................................................................................................................68

Figure 4-30 RTWP traced in neighboring cells.....................................................................................................68

Figure 4-31 Traced RTWP....................................................................................................................................70

Figure 4-32 Traced RTWP in the 45680 site.........................................................................................................70

Figure 4-33 Antenna position (left) and measured RTWP (right).........................................................................71

Figure 4-34 Site location (left) and traced RTWP (right).....................................................................................71

Figure 4-35 Traced RTWP in real time — air conditioner 1.................................................................................72

Figure 4-36 Traced RTWP in real time — air conditioner 2.................................................................................72

Figure 4-37 Traced RTWP in real time — emergency light.................................................................................73

Figure 4-40 Interference generated on a transmission line...................................................................................74

Figure 4-42 Spectrum features..............................................................................................................................75

Figure 6-1 Threshold Setting window...................................................................................................................83

Figure 6-2 Threshold alarm setting.......................................................................................................................84

Figure 6-3 Threshold settings................................................................................................................................85

2019-1-15 Huawei Confidential Page 7 of 87

Table 3-1 RF-related alarms..................................................................................................................................25

Table 3-2 Counter values.......................................................................................................................................26

Table 3-3 Typical RTWP-related RNC traffic measurement counters..................................................................28