Escolar Documentos
Profissional Documentos
Cultura Documentos
11
Section 1
Radio Fine Tuning
Module 1
Typical Radio Problems
3JK11052AAAAWBZZA Issue 01
Document History
Page
Switch to notes view!
1 Theoretical Presentation 7
2 Coverage Problem 9
3 Interference Problem 18
4 Unbalanced Power Budget Problem 32
5 TCH Congestion Problem 38
6 Deducing the Right Team for Intervention 43
Symptoms:
Customers complain about dropped calls or/and no network
OMC QoS indicators
TCH failure rate
Call drop rate
Low proportion of better cell HO
High rate of DL quality HO
A interface indicators
High rate of Clear Request messages, cause radio interface failure
No information is available on non-covered parts of the network, as there are non-mobiles making calls over
there!
Nevertheless, cells in border of non-covered zones do have a particular behavior:
B
A
Cell A will mainly perform Better Cell handovers towards its neighbors, whereas cell B, bordering the non-
coverage area, will perform emergency handovers for MSs exiting the network.
For these MSs, mainly DL Quality HO will be triggered:
DL because MS antenna is less efficient than BTS one,
Quality rather than Level since Qual has a greater priority in Alcatel-Lucent HO causes.
RMS:
Provides statistics from any area in the network which are available at any time.
Cost-effective.
Easier and cheaper to perform than Drive test or Abis Trace.
The operator can tune 54 parameters (based on RxLev, BFI, C/I, Radio Link Counter S, Path Balance, etc.) to
define up to 16 templates (depending on cell type rural, urban, etc. for example).
Trigger from the OMC-R.
TRX index RxLev_UL RxLev_DL RxQual_UL RxQual_DL Path_loss_UL Path_loss_DL delta_Path_loss Delta_quality AV_MS_PWR Nb_of_samples
1 -89.29 -84.67 0.42 0.43 123.82 123.67 0.15 -0.01 34.53 3074
2 -89.77 -89.09 0.41 0.38 124.87 128.09 -3.21 0.03 35.11 10 253
3 -83.15 -79.15 0.17 0.33 116.05 121.22 -5.16 -0.16 32.9 5339
It could have been coverage problems if this trace was made for 3 mono-TRX cells. In this case, the 3 lines are
uncorrelated. Anyway, delta path loss of frequency 111 is greater than 5dB, showing a problem on this TRX.
If this is a 3-TRX cell, it cannot be a coverage problem as the three TRXs are not impacted. It will be either
interference or malfunction of one TRE.
If the trace is done on 3 mono-TRX cells, in that case, it could be a coverage problem. Be careful when
interpreting this result table: even if average levels in the UL and the DL are high and a lot of Quality problems
are seen, nobody can say that samples with bad quality have a good level! The level seen is just an average
One should have a look at the next slide
All samples are Bad Coverage samples (BC). None is interference, showing that this cell is not facing any
interference problem.
A coverage problem is observed when a significant amount of the traffic of a cell is suffering from both low level
and bad quality (RxQual).
To confirm, distribution of samples per RXLEV band should be also considered to know the proportion of calls
which are experiencing a low signal level.
If a lot of samples of low level and bad quality are observed for only a sub-part of the TRXs (can be one only)
then a BTS hardware problem or a problem on the antenna should be suspected.
If all the TRXs are experiencing a lot of samples of low level and bad quality then a coverage problem must be
suspected.
These RMS indicators are provided on the NPO tool per TRX, per Cell:
Matrix of Number of Measurement Results per DL RxQual value and per DL RxLev band
RMQLDSAM = RMS_DL_RxQuality_RxLevel_sample
Vector of Percentage of Samples per DL RxLev band
RMQLDLVDV = RMS_DL_RxLevel_distrib
Vector of Percentage of Samples per DL RxQual band
RMQLDQUDV = RMS_DL_RxQuality_distrib
RxQuality (Nb)
7
6
Interval of average
5 Timing Advance
4
[0, 2]
3 ]2, 4]
2 ]4, 6]
1 ]6, 8]
X Out of Range
0 RxLevel
[-110, [-104, [-98, [-92, [-86, [-80, [-74, [-68, [-62, [-56, (dB)
-104[ -98[ -92[ -86[ -80[ -74[ -68[ -62[ -56[ -47[
01/12/2001
01/01/2002
02/01/2002
03/01/2002
04/01/2002
05/01/2002
06/01/2002
07/01/2002
08/01/2002
09/01/2002
10/01/2002
11/01/2002
12/01/2002
13/01/2002
14/01/2002
considered
In order to know if the coverage problem is due to a big amount of traffic at the cell border or rather to indoor
calls, the average TA value per RXQUAL value and RXLEV band as well as the Percentage of TA values over TA
threshold should be observed:
Matrix of Average TA per UL RxQual value and per UL RxLev band
RMQLUTAM = RMS_UL_RxQuality_RxLevel_TimingAdvance
Rate of Measurements Results whose TA is greater than the TA threshold
RMTAGTR = RMS_TimingAdvance_greater_threshold_rate
Maximum TA value of all values reported in Measurement Results
RMTAMXN = RMS_TimingAdvance_max
5 2.5
4
Bad quality 3
1
for a specific TA band 0
[0,5[ [6,11[ [12,18 [19,24 [25,30[ [31,36[ [37,42[ [43,48[ [49,54[ [55,63[
[ [
-47 - 59
- 60
- 70
- 80
- 90
- 110
[0,5[ [6,11[ [12,18 [19,24 [25,30[ [31,36[ [37,42[ [43,48[ [49,54[ [55,63[
[ [
Coverage problem
In order to know if the coverage problem is due to a big amount of traffic at the cell border or rather to indoor
calls, the average TA value per RXQUAL value and RXLEV band as well as the Percentage of TA values over TA
threshold should be observed:
Matrix of Average TA per UL RxQual value and per UL RxLev band
RMQLUTAM = RMS_UL_RxQuality_RxLevel_TimingAdvance
Rate of Measurements Results whose TA is greater than the TA threshold
RMTAGTR = RMS_TimingAdvance_greater_threshold_rate
Maximum TA value of all values reported in Measurement Results
RMTAMXN = RMS_TimingAdvance_max
Definition: Interference
A network facing interference problems presents good RxLev and bad RxQual
at the same time on some areas.
Symptoms
Customers complain about bad speech quality (noisy calls) and/or call drops
OMC QoS indicators:
SDCCH/TCH Drop
Low proportion of better cell HO
High rate of DL/UL quality HO and interference HO
Low HO success rate
A interface indicators
High rate of Clear Request messages, cause radio interface failure
Mainly, interferences are in the DL, due to bad frequency planning introducing interferences in the network. And
this problem will not change till the frequency plan is not returned
Sometimes, interference can be in the UL in very dense area (for example, microcell area), since MSs are very
close.
Finally, sometimes interferences are not coming from BS or MS but from another radio equipment, either in the
UL or the DL.
The feature Radio Measurement Statistics (RMS) is designed to make far easier the work for planning and
optimization of the network by providing the operator with useful statistics on reported radio measurements.
In fact these statistics give directly the real cell characteristics by taking into account the MS distribution.
Thanks to this feature, the operator is able to:
detect interfered frequencies.
assess the quality of the cell coverage.
detect and quantify cell unexpected propagation.
assess the traffic distribution in the cell from statistics on reported neighboring cells.
evaluate the voice quality in the cell.
etc.
In regards to the RTCH Measurements Observation (measurement type 11), the Radio Measurement Statistics
feature (RMS) brings the following advantages:
smaller report files.
the report files always have the same maximum length no matter what the measurement duration is.
every measurement is taken into account (no sampling).
no more need for measurement post-processing tools for statistics. Directly available with NPO.
CFE (Nb)
[22,
[14, 25[
18[
Interval of number
[18,
[14, 22[
18[ of samples
[14, 18[
[14, [0, 14 793]
[10, 14[ ]14 793, 23 446]
[8, 10[ ]23 446, 29 586]
]29 586, 34 348]
[6, 8[
]34 348, 38 239]
[4, 6[ ]38 239, 41 529]
[2, 4[ ]41 529, 44 378]
[1, 2[ ]44 378, 46 892]
X Out of Range
[0, 1[ RxLevel
[-110, [-104, [-98, [-92, [-86, [-80, [-74, [-68, [-62, [-56, (dB)
-104[ -98[ -92[ -86[ -80[ -74[ -68[ -62[ -56[ -47[
These RMS indicators are provided on the NPO tool per TRX, per Cell:
Matrix of Number of Measurements Results per CFE band (or BFI band) and per UL RxLev band
RMFEM = RMS_UL_ConsecutiveFrameErasure_RxLevel_sample
Vector of Average number of Consecutive Frame Erasure per UL RxLev band
RMFEBFAV = RMS_UL_ConsecutiveFrameErasure_avg_per_RxLevel
Vector of Average UL RxQual per RxLev band
RMQLUQUAV = RMS_UL_RxQuality_avg_per_RxLevel
5 2.5
4
Bad quality 3
1
for a specific TA band 0
[0,5[ [6,11[ [12,18 [19,24 [25,30[ [31,36[ [37,42[ [43,48[ [49,54[ [55,63[
[ [
-47 - 59
- 60
- 70
- 80
- 90
- 110
[0,5[ [6,11[ [12,18 [19,24 [25,30[ [31,36[ [37,42[ [43,48[ [49,54[ [55,63[
[ [
interference problem
These RMS indicators are provided on the NPO tool per TRX, per Cell:
Matrix of Number of Measurements Results per CFE band (or BFI band) and per UL RxLev band
RMFEM = RMS_UL_ConsecutiveFrameErasure_RxLevel_sample
Vector of Average number of Consecutive Frame Erasure per UL RxLev band
RMFEBFAV = RMS_UL_ConsecutiveFrameErasure_avg_per_RxLevel
Vector of Average UL RxQual per RxLev band
RMQLUQUAV = RMS_UL_RxQuality_avg_per_RxLevel
GSM interference
co-channel
adjacent
Non-GSM interference
other Mobile Networks
other RF sources
F(BTS1) = F(BTS2)+1
Level F(BTS2)
F(BTS1)
6 dB
Frequency
Examination
Neighbor cells in Abis trace (only for BCCH)
Non-neighbor cells in RMS (MAFA frequencies)
Frequency planning C/(I adjacent) < -6dB
Correction
Downtilt increase of interferer, or even change of antenna orientation
Reduction of BS power if necessary, Change of frequency (best solution)
Concentric cell implementation (1 extra TRX needed if traffic cannot be supported
by Outer+Inner configuration)
GSM Interference
Co-Channel interference
-12dB are sufficient (-9dB according to GSM)
by Outer+Inner configuration
F(BTS1) = F(BTS2)
Level F(BTS2)
F(BTS1)
-12 dB
Frequency
Co-channel interference
Symptom
Usually downlink interference
High rate of quality HO, call drop and call failure
Examination
Neighbor cells in Abis trace (only for BCCH)
Non-neighbor cells in RMS (MAFA frequencies)
Frequency planning C/I < 12 dB
Correction
Downtilt increase of interferer, or even change of antenna orientation
Reduction of BS power, Change of frequency
Concentric cell implementation (1 extra TRX needed if traffic cannot be supported
by Outer+Inner configuration)
BTS1: ARFCN 5 MS 2
BTS 1 (outdoor) BTS 2
BTS2: ARFCN 6 (Micro)
1
MS 1
MS1 indoor (indoor)
RxLev_UL: - 90 dBm
MS2 outdoor, connected to BTS2
1: no level on BTS1 2
(BTS 1 under-roof)
2: - 80 dBm on BTS1:
interferer UL/DL
3: no level on BTS1
cell algo prevents BTS2->BTS1 HO
When interferences are created by frequency planning, its not so hard to detect them. But frequency planning
tools mainly consider DL C/I and coverage.
Some problems are more difficult to predict. For example, lets consider a microcell layer:
B
A
A and B are 2 microcells with the coverage described before in dense urban environment.
Even if both cells A & B are using adjacent frequencies (5 and 6), the overlapping area is far from cell A
antenna. Thus, in this area C/I is lower than 6 dB.
A red MS is connected to cell A. When the MS starts its call, it transmits full power and a PC algorithm quickly
reduces MS power as the received level is very good (microcell coverage). When MS A enters the building, it faces
a loss of signal of 20 dB. Then, the MS power increases to MS_TXPWR_MAX.
A second mobile B is connected to cell B and moves down in the coverage area of cell B. The MS power of B
decreases quickly down to MS_TXPWR_MIN as the MS is close to the antenna. But when MS B arrives outside the
building where A is sitting, A and B are close and transmitting on adjacent frequencies Then B has to increase
its power to avoid dropping its call. By the way, global level of freq B is increased in all cell B creating
interference in the UL. All Rights Reserved Alcatel-Lucent 2008
3JK11052AAAAWBZZA Issue 01
Section 1 Module 1 Page 29
3 Interference Problem
GSM Interference: Forced Directed Retry
:2
The MS is emitting at high level (far from
C ell 1
BTS1)
UL interference for BTS 3
BTS 1
BTS 1 is emitting at high level
DL interference at BTS 3
MS
BTS 2
el
C
l 2
: 45 BTS 3
Ce
ll 3 : 2 3
umbrella
capture FDR
microcell
The situation described on the slide corresponds to the usage of FDR in a single layer network. This is in that case
a heavy-to-tune algorithm presenting of lot of interference and bad quality call risks, since the mobile will be
connected to a cell when being not in its
Allservice area. Alcatel-Lucent 2008
Rights Reserved
3JK11052AAAAWBZZA Issue 01
Section 1 Module 1 Page 30
3 Interference Problem
Non-GSM Interference
Other RF interferers:
medical devices: GSM equipment disturb them more than the opposite!
anti-theft mechanisms.
Example:
Microcell
antenna
shop
Qual DL Qual
UL
Level Level
interference
The Microcell is showing a very high call drop rate. On one frequency, very small call duration.
No problem seen in the frequency plannig. No potential interferer.
Abis trace:
The Spectrum analyzer connected on the antenna feeder highlights a peak on GSM freq 6 in the UL
Anti-theft mechanism turned off: no more problem
All Rights Reserved Alcatel-Lucent 2008
3JK11052AAAAWBZZA Issue 01
Section 1 Module 1 Page 31
4 Unbalanced Power Budget Problem
UL Quality HO is triggered:
UL since the problem is in the UL.
Quality as Quality has greater priority than level.
RMS:
Path Balance vector per TRX
Number of calls with abnormal bad FER (good RxQual & bad FER)
Abis monitoring:
|delta path-loss| > 5dB
Check if problem is occurring for 1 TRX or all
Problem on 1 TRX: FU/CU or TRE problem or ANY problem or cables connected to this equipment.
All TRXs: problem on antenna, feeder, jumper or common equipment (e.g., ANX, ANC).
106 -94.52 -87.19 0.43 0.25 127.55 130.19 -2.64 0.18 33.03 2066
89 -84.29 -75.17 0.65 0.44 115.32 118.17 -2.85 0.21 31.03 2001
118 -90.75 -83.36 0.46 0.41 123.22 126.36 -3.14 0.04 32.46 3193
124 -88.89 -85.30 0.29 0.67 120.48 128.30 -7.82 -0.37 31.59 2931
106 84.75% 4.07% 3.68% 3.19% 1.36% 1.50% 0.92% 0.53% 2.95%
89 81.41% 1.70% 2.95% 3.65% 6.35% 2.55% 1.30% 0.10% 3.95%
118 83.62% 4.23% 4.23% 3.35% 1.57% 1.79% 0.97% 0.25% 3.01%
124 90.79% 1.06% 2.18% 2.35% 1.77% 1.30% 0.48% 0.07% 1.84%
Nb Samples
3000
2500 Nb
Samples
2000
1500
1000
500
PathBalance
0
[-110, [-20, [-10, [-6, [-3, [0, [3, [6, [10, [20, (dB)
-20[ -10[ -6[ -3[ 0[ 3[ 6[ 10[ 20[ 110[
A fair average Path Balance at Cell level can hide a bad value for one TRX
These RMS indicators are provided on the NPO tool per TRX, per Cell:
Vector of the Number of Measurement Results per Path Balance band
RMPBV = RMS_PathBalance_sample
Average Path Balance value
RMPBAN = RMS_PathBalance_avg
Every BTS has its proper architecture and the diagnosis must be adapted.
Cells on wheel operational by several operators around the world for special events coverage & capacity:
IRMA (SFR) connected to Caens BSC.
Orange coverage / Football WC 1998 for Paris Stade de France :
Specific cells covering Paris Stadium. During games, only small capacity (using joker frequencies). During
breaks, some TRX off-cells around are turned off, and frequencies are reused for stadium cells.
Use the B-Erlang law to estimate the number of TCHs required for a 2%
blocking rate, thus the target configuration
Add TRXs to reach the new target configuration and find joker frequencies
and / or implement concentric cells
Warning: offered traffic is not the capacity delivered by the system but the traffic asked by the users.
Software solution
Use specific densification features
Half Rate
Forced Directed Retry
Traffic handover
Fast Traffic handover
Candidate Cell Evaluation (FREEFACTOR / LOADFACTOR)
Half rate may not only mean SW solution. Need of G2 BSC/TC, Evolium TRE or G2 DRFU.
Correction
Check the tuning of default radio parameters
action
Planning team
Standard parameters ?
Maintenance team
Dimensionning team
Consult the config. db No Yes Choose an (other) classical algo
On
Yes Identify the tunable parameters
purpose
Cell corrected ?
No
Neighbor cell ?
Impact simulation of a
NOK Impact estimation parameter modification
N times
Check ? System
No No Simulation
With QOS ? problem ?
OK ?
Yes =N Yes
OK