Part 3 :

Optimization
Network Deployment Steps
 High level PM data analysis and assessment

System Program (PLMN)

Using Reporting Suite 3G RAN Reports or MS
Weekly KPI
Access KPI Queries
No No action
( PLMN)
needed
<X%
System Program (RNC)

Yes
Weekly KPI
No Mapinfo
(RNC) Mataching failure
<X%? distribution into
network topology Solution Proposal

Yes

System Program (WCEL) Others 3G RAN Reports

Identify Top50 Worst
Cells based on
Daily KPI
highest number of root
(WCEL)
causes failures
< X%

System Program (WCEL) Others 3G RAN Reports

Yes Identify Call failure Identify failures root-
phases of bad causes and failure
performing KPIs, for distribution of bad KPIs
example CSSR

Presentation / Author / Date

PM Data analysis process

Presentation / Author / Date

Traffic Monitoring
 Principles of traffic monitoring -
bottlenecks
WBTS RNC
UE
IuCS Interface

User
User Plane
Plane

SS7 (RANAP)
Air Interface WSP Iub Interface
Resource Throughput
CNBAP IuPS Interface
PRACH Connectivity
FACH-c&u DNBAP
PCH Unit Load User Plane
AAL2 or IP SIG
Code User Plane DSP Usage SS7 (RANAP)
DCH
Capacity

User Plane
Iur Interface
Both interfaces and internal resources of
WCDMA network should be monitored
D-RNC
 Principles of traffic monitoring - reactive /
Reactive monitoring proactive
• Consider setup failure (already discussed in chapter 2)
• Daily BH analysis needed

Proactive monitoring
• Consider amount of traffic
• Weekly analysis enough
 Traffic Monitoring
Principles
Transmitted carrier power
Node B reporting
Total DL power
R99 power
HSDPA power
Received total wideband power
Code tree allocation
Channel element allocation
Iub transmission
RNC processing load
Number of users
 Node B reporting
Node B informs RNC about air interface load by the following messages
Common NBAP radio resource indication
• Transmitted carrier power
• Total power R99 + HSDPA
• R99 power
• Received total wideband power
• Total power R99 + HSUPA
• HSUPA power (calculated by Node B, not directly measured)
Dedicated NBAP measurement report
• Power of each dedicated radio link

C - NBAP
IuB D - NBAP

Node B RNC
Total DL power - optimization flow
High total DL
power

High pilot High SHO

Otherwise
pollution overhead

Neighbor Check SHO parameter Add second

analysis settings carrier
Check adjacent cell
interference
R99 power -
 R99 power -
Number of radio resource indications falling into specific R99 power interval

The definition of the load target depends on the presence of HSDPA users
• No HSDPA user present → static load target PtxTarget
• At least one HSDPA user present → dynamic load target PtxTargetPS
 HSPA power
HSPA power includes
• HS-PDSCH
• All HS-SCCH
• All HSUPA DL signaling channels (E-AGCH, E-RGCH, E-HICH)
HSDPA power - dynamic share with R99
DL power shared dynamically between R99 and HSDPA
Realized by dynamic load target for NRT R99 traffic PtxTargetPS
For RT R99 traffic still static load target PtxTarget

PtxTargetPS is adjusted between

• Minimum load target PtxTargetPSMin (default 36 dBm)
• Maximum load target PtxTargetPSMax (default 40 dBm)

PtxTargetPSMin ≤ PtxTargetPS ≤
PtxTargetPSMax
RNC checks periodically, whether adjustment of PtxTargetPS needed
Period defined by PtxTargetPSAdjustPeriod (default 5 RRI periods)
HSDPA power - dynamic share with R99
PtxTargetPS adjusted under the following conditions

1) HSDPA congestion
• Too much total DL power present in cell
PtxTotal ≥
PtxHighHSDPAPwr
• PtxHighHSDPAPwr defines overload threshold for HSDPA cell (default 41 dBm)

2) DCH congestion
• Too much R99 power present in cell

PtxNonHSPA ≥
PtxTargetPS -
• The offset is fixed to 1 dB
Offset
HSDPA power - dynamic share with R99
HSDPA Congestion
HSDPA power congestion, if If actual load target PtxTargetPS > optimum load target
Ptxtotal ≥ PtxHighHSDPAPwr Decrease PtxTargetPS by PtxTargetPSStepDown (default 1 dB)

PtxMax 43 dBm

PtxHighHSDPAPwr
-10..50; 0.1; 41 dBm
PtxTotal
PtxTargetPSMax
-10..50; 0.1; 40 dBm

PtxTargetPS PtxTargetPSMin
-10..50; 0.1; 36 dBm

Optimum
load target PtxNonHSDPA PtxNRT

PtxNC
HSDPA power - dynamic share with R99
DCH Congestion
DCH power congestion, if If actual load target PtxTargetPS < optimum load target
PtxNonHSDPA ≥ PtxTargetPS - 1dB Increase PtxTargetPS by PtxTargetPSStepUp (default 1 dB)

PtxMax 43 dBm

PtxHighHSDPAPwr

PtxTotal
PtxTargetPSMax

PtxTargetPS
PtxTargetPSMin

Optimum
load target PtxNonHSDPA PtxNRT

PtxNC
 RTWP sources
High adjacent cell Low adjacent cell
interference interference
i-factor

Noise rise due to

real traffic
PrxOffset
e.g. 1 dB above PrxTarget -100 dBm
PrxTarget -101 dBm
e.g. 4 dB above PrxNoise

Own cell load factor

(throughput)
RTWP of empty cell
MUST be equal PrxNoise -105 dBm
Intermodulation out of band (e.g. 1 dB)
-106 dBm
Receiver noise figure (e.g. 2 dB)
-108 dBm
Thermal noise -108 dBm
Total UL power - role of BTS commissioning
RTWP measured by BTS at antenna connector
Then corrected due to
• Feeder loss
• MHA gain

RTWPcorrected = RTWPmeasured + feeder loss – MHA gain

Corrected RTWP reported to RNC

With wrong settings wrong RTWP values reported

Previous example for 2 GHz range

Probably feeder loss underestimated → corrected RTWP underestimated
Total UL power - optimization flow
Total UL power

Close to -112 Still below BTS Often > -100

dBm receiver noise dBm

Check HW Check feeder loss / MHA gain Check

commissioning setting - High traffic density
- HW
- Intermodulation
 R99 code allocation - principles
Code resource required depends on type of radio bearer
• Signaling SF 256 for 3.4 Kbit/s, SF 128 for 13.6 Kbit/s
• Voice HR SF 128 or SF 256
• Voice FR, 16K data SF 128
• 32K data SF 64
• 64K data SF 32
• 128K data SF 16
• 256K data, 384K data SF 8
Only 1 code per bearer allocated

SF=8

SF=16

SF=32

SF=64

SF=128
 R99 code allocation - blocking
Practical example – single cell
Blocking per SF per hour
Blocking rate
for SF8
Total blocking rate

Very high blocking especially for SF8

But still also for SF16 and sometimes
even for SF32
Blocking rate
for SF16
 R99 code allocation - re-arrangement
Code tree quickly fragmented, if not re-arranged from time to time
Then few users of high SF (low data rate) block huge amount of resources
for users of low SF (high data rate)
Re-arrangement performed
• Periodically according CodeTreeOptTimer (default 1h) OR
• If code tree occupation > CodeTreeUsage (default 40%) OR
• If more than MaxCodeReleases consecutive releases of codes (default 40)

Blocking before re-arrangement Blocking after re-arrangement

 HSDPA code allocation - principles
For HSDPA fixed SF16
But several codes per bearer available
• Minimum guarantee of 5 codes
• Maximum number set usually to 15 codes
• Code resource has to be shared with R99

SF=1

SF=2

SF=4

SF=8

SF=16
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
………. ……….

R99 + HSPA signaling CH Guarantee for HSDPA

Dynamically shared between
R99 and HSDPA
 HSDPA code allocation - dynamic share with R99
Number of codes reserved for HSDPA can be adjusted dynamically
in dependence on R99 traffic
Possible levels configured with parameter HSPDSCHCodeSet
16 bit parameter to enable / disable each possible level individually

Examples
00000 00000 100000 = always 5 codes reserved (default)
11010 10100 100000 = number of reserved codes adjustable (5, 8, 10, 12, 14 or 15 codes,
recommended)

11-15 codes 0-4 codes always disabled

6-10 codes
HSDPA code allocation - dynamic share
with R99
Upgrade

RNC checks periodically, whether more codes can be reserved for HSDPA
Requirements for upgrade
• Free adjacent codes to go to next higher level defined by HSPDSCHCodeSet
• After upgrade still enough codes with SF128 available for R99 (at least HSPDSCHMarginSF128,

default = 8)
• Upgrade to 15 codes possible only with HSPDSCHMarginSF128 = 0
 HSDPA code allocation - dynamic share with R99
Downgrade due to NRT R99 traffic

If a NRT R99 request cannot be served due to code blocking, HSDPA is

downgraded only, if the actual number of codes exceeds
Maximum code set – DPCHOverHSPDSCHThreshold
• Default = 0 → HSDPA always has higher priority than incoming NRT R99 request
• Threshold = 5 → HSDPA downgraded due to incoming NRT R99 request, if actually
more than 15 - 5 = 10 codes reserved for HSDPA
Number of allocated SF16 codes

15 Maximum code set

14
13 DPCHOverHSPDSCHThreshold
12
11
10
9
8
7
6
5
 HSDPA code allocation - impact of HSUPA
New DL signaling channels occupying at least the following codes
• 1 x SF256 by E-AGCH
• 1 x SF128 by E-RGCH / E-HICH (these two channels share one code)
Loss of a second code with SF16 → maximum of 14 codes for HSDPA

SF=1

SF=2

SF=4

SF=8

SF=16

14 HS-PDSCH codes
SF=32
Codes for common
SF=64 channels in the cell Codes for associated DCHs
and non-HSDPA users
SF=128

SF=256 Up to three HS-

SCCH codes E-AGCH (256)

E-RGCH/E-HICH (128)
High code congestion - optimization flow
High code
congestion

Enable code tree

optimization

Still high
congestion

Many DCH of High SHO

low activity Many overhead
associated
DCH

Enable throughput Enable F-DPCH Check SHO parameter

based optimization (associated DCH) settings
(R99 DCH) Check adjacent cell
interference
 Traffic Monitoring
•Principles
•Transmitted carrier power
•Received total wideband power
•Code tree allocation
•Channel element allocation
•Monitoring
•BTS channel cards
•R99 dimensioning (optional)
•HSDPA dimensioning (optional)
•HSUPA dimensioning (optional)
•Iub transmission
•RNC processing load
•Number of users
 Monitoring - total utilization
For daily work often more convenient to know the percentage of occupied CE
instead the absolute number
Both for DL and UL six to indicate, how often total utilization falls into
certain interval
• 0-49 %
• 50-69 %
• 70-79 %
• 80-89 % 100%
• 90-99 % 90-99%
80-89%
• 100 %
70-79%
11
.0
3
11 .20
.0 10_
3. _
11 201 09
.0 0_ :00
3

10%
20%
30%
40%
50%
60%
70%
80%
90%

0%
:
100%

_
11 .201 11 00
.0 0 :0
3 __ 0:0
11 .201 13 0
.0 :0
3. 0__ 0:0
11 201 15 0
.0 0_ :00
3. _ : 00
11 201 17
.0 :0
3. 0__ 0:0
11 201 19 0
.0 :0
3. 0__ 0:0
12 201 21 0
.0 0_ :00
3. _ : 00
12 201 23
.0 :0
3. 0__ 0:0
12 201 01 0
.0 :0
3. 0__ 0:0
12 201 03 0
.0 0_ :00
3. _ :
Practical example – UL on single BTS

12 201 05 00
.0 :0
3 0__ 0:0
12 .20 07 0
.0 10 :
3. __ 00:0
12 201 09 0
.0 0_ :00
3. _ : 00
12 201 11
.0 :0
3. 0__ 0:0
20 1 0
10 3:0
__ 0:
15 00
:0
0:
00
70.00
75.00
80.00
85.00
90.00
95.00

RNC_731A
(0 - <50)% M5001C15
(50 - <70)% M5001C16
(70 - <80)% M5001C17
(80 - <90)% M5001C18
(90 - <100)% M5001C19
(100 or more)% M5001C20

utilization
Monitoring - total utilization

Avg Ratio of Used CE for UL in BTS

In most cases very high

Typically 80-89 % or 90-99 %

 Monitoring - utilization by HSPA
Both for DL and UL five additional to indicate, how often utilization by HSPA
falls into certain interval
• 0-19 %
• 20-39 %
• 40-59 %
• 60-79 %
• 80-100 %
 Monitoring - utilization by HSPA
Practical example – UL on single BTS
100% 40

90%
35
UL(90 - <100)% M5001C31
80%
30 UL (80 - <90)% M5001C30
70%
UL (70 - <80)% M5001C29
25
60% UL (50 - <70)% M5001C28

UL (0 - <50)% M5001C27
50% 20

Max HSUPA Users M1031C1

40%
15 Max HSDPA Users M1031C0

30%
Avg ratio of Used CE for UL for HSUPA in
10 BTS RNC_948A
20% Avg ratio of Used CE for DL for HSUPA in
BTS RNC_947A
5
10%
0

0
0

0
:0

:0

:0

:0

:0

:0

:0

:0

:0

:0

:0

:0
:0

:0

:0

:0
0% 0
0

0
0

0
:0

0
:0

:0

:0

:0

:0

:0

:0

:0
:

:
9

5
3

3
0

1
1

1
_

_
_

_
0

0
1

1
1

1
0

0
0

0
.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2
3

3
.0

.0

.0

.0

.0

.0

.0

.0
.0

.0

.0

.0

.0

.0

.0

.0
1

In most cases very high

1

utilization due to HSUPA

Typically 80-89 %
 R99 dimensioning
In general, each DCH occupies a certain number of CE in dependence
on the type of service
The CE occupation is the same for
• FSMC/D/E and WSPF cards
• R99 DCH and associated DCH

Service CE
SRB / voice / 16 K data 1
32 K data 2
64 K data 4
128 K data 4
256 K data 9
384 K data 12
 R99 dimensioning
Less CE needed for DCH of 256 K and 384 K
All other rules remain unchanged

Service CE
SRB / voice / 16 K data 1
32 K data 2
64 K data 4
128 K data 4
256 K data 6
384 K data 8
High CE occupation - optimization flow
High CE
occupation

Many
Many DCH of High SHO
associated
low activity overhead
DCH

Enable throughput Enable F-DPCH Check SHO parameter

based optimization (associated DCH) settings
(R99 DCH) Check adjacent cell
interference
 Traffic Monitoring
Principles
Transmitted carrier power
Received total wideband power
Code tree allocation
Channel element allocation
Iub transmission
Implementation principles
Monitoring options
Examples
RNC processing load
Number of users
Examples - physical ATM traffic
Two VC multiplexed by IMA
Cell rate reserved by CAC per VC

Configured bandwidth

M550 – CAC AAL2

Even Path Measurements
maximum reserved bandwidth
2 Free
VCs with 8250 (ATM) cells
bandwidth per second
far below per VC
configured on 1 IMA group
bandwidth
No risk of physical congestion

Maximum reserved bandwidth

Minimum reserved bandwidth

Examples - logical ATM traffic
Two VC multiplexed by IMA
Number of AAL connections established by CAC per VC

Even in busy hour number of AAL connections

clearly below maximum of 248
No risk of logical congestion
 Traffic Monitoring
Principles
Transmitted carrier power
Received total wideband power
Code tree allocation
Channel element allocation
Iub transmission
RNC processing load
RNC block diagram
Monitoring options
Number of users
 Case — High Call Drop Rate due to RNC Traffic
Measurement Defect (Continued)

Solution

After the patch is installed for the RNC, almost all the call drops with the cause being “Other” have disappeared
and the PS call drop rate is obviously lower, as shown in the following table. The problem is thus solved.

Note: You can get the table on the right via custom report or “Performance Query” of Nastar.
 Traffic Monitoring
•Principles
•Transmitted carrier power
•Received total wideband power
•Code tree allocation
•Channel element allocation
•Iub transmission
•RNC processing load
•Number of users
 Number of users - licenses
R99
• No license for specific number of users per cell required
• New user allocated, as long all types of RAN resources available

HSPA
• License for specific number of users per cell required
• The following levels are available
• 16 users
• 48 users
• 64 users
• 72 users
• If maximum number of users present, new user rejected, even if all
types of RAN resources still available
 Call setup - phases
RRC and RAB RRC connection setup
RAN resources reserved for
signaling connection between UE
and RNC
Phase: Setup Access Active RRC access
Connection between UE and RRC
RRC active
UE has RRC connection
Active If dropped, also active RAB

Success
Setup Access Complete dropped
Complete Complete RAB setup

Access
Active Attempts to start call
Release RAB setup access
Connection between UE and core
Attempts

Active RRC RAB active phase

UE has RAB connection
Failures Drop

CSSR affected if any of the following

Access failures events takes place
• RRC Connection Setup Fail
• RRC Connection Access Fail
Setup failures • RAB Setup Fail
(blocking)
• RAB Setup Access Fail
Call setup – successful RRC establishment
Signalling and trigger
UE Node B RNC
Three phase for RRC
[RACH] RRC Connection Request
AC to check to accept
or reject RRC
Connection Request
RRC Connection Setup NBAP RL Setup Request
Allocation of UTRAN
phase Start
Start TX/RX
TX/RX
resources
NBAP RL Setup Response
ALCAP ERQ
ALCAP ECF
[FACH] RRC: RRC Connection Setup

Start TX/RX
RRC Connection
L1 Synchronisation
Access phase
NBAP Synchronization Indication Waiting for UE reply

[DCH] RRC Connection Setup Complete

=
RRC Connection Active phase
RRC Connection – SETUP and ACCESS PHASE
Signalling and trigger
UE Node B RNC
Three phase for RRC

[RACH] RRC Connection Request

AC to check to accept or
reject RRC Connection
Request
RRC Connection Setup NBAP RL Setup Request
Allocation of UTRAN
phase Start TX/RX resources
NBAP RL Setup Response
ALCAP ERQ
ALCAP ECF
[FACH] RRC: RRC Connection Setup

Start TX/RX
RRC Connection Access
phase L1 Synchronisation
NBAP Synchronization Indication Waiting for UE reply

[DCH] RRC Connection Setup Complete

=
1. RRC setup attempts.
2. RRC setup attempts per setup cause.
(SEE NEXT SLIDE)
3. RRC setup failures due to
• handover control , • admission control
• transport (Transmission)• RNC internal
• frozen BTS • BTS • ICSU overload
4. RRC setup failure per cause.
5. RRC setup complete.
6. RRC access failures due to
• radio interface • UE• RNC internal
7. RRC access complete.
8. Special reason: RRC active release
due to
• SRNC Relocation • Pre-emption
• User inactivity • RNC HW resources
• ISHO to GAN • Inter-system handover to GSM • IF
inter-RNC hard handover • Inter-frequency inter-
RNC hard handover
9. RRC active failures due to
• Iu interface (transport) • radio interface
(synchronisation) • BTS • Iur interface (DRNC) •
RNC internal • UE • Transmission
10. RRC active complete
1. RAB setup attempts. Separate counter
per each RAB type.
2. RAB setup failures due to
• admission control • transport (transmission) • RNC
internal • frozen BTS • BTS (RT only) • anchoring (NRT
only) • capacity license (for CS voice RAB only)
3. RAB setup complete. Separate counter
per each RAB type.
4. RAB access failures due to
• UE • RNC internal
5. RAB access complete. Separate counters
per each RAB type.
6. Special reason: RAB active release due to
• SRNC relocation • pre-emption • capacity license pre-
emption (only for CS voice RAB)
7. RAB active failures due to
• Iu interface (transport) • radio interface (synchronisation) •
BTS • Iur interface (DRNC) • RNC internal • UE •
Transmission
8. RAB reconfiguration attempts.
9. RAB reconfiguration failures.
10. RAB active complete. Separate
counters per each RAB type.
Drop Call Analysis

Presentation / Author / Date

Case 1: Drop due to missing neighbor

Problem: Detected Nighbor (DN)

UE sends a Measurement Report that contains an event1a means
adding a new RL (cell) to Active Set
If the reported cell is not in the current neighbor cell list and the
reported Ec/No is better than the best serving cell Ec/No in AS
by some dBs (set by a RNC parameter)
If for any reason the new cell can not be added to AS, call will be
released
Case 1: Drop due to missing neighbor

DL BLER gets worse

“DN” cell better than the serving cell

Case 2: Drop due to Poor Coverage (low RSCP)

Problem: Poor DL coverage

When UE gets to an area with low RSCP ( < -105 dBm)
regardless Ec/No values there is high risk for drop.
UE will likely ramp up the transmitted power and reach its
max power. The DL BLER will probably increase and SIR
target cannot maintain anymore, finally the call drops.
Case 2: Drop due to DL Poor Coverage

UE max Tx power
and
high DL BLER
Very bad RSCP
Case 3:
PS: Session Error due to Poor DL Coverage

UE enters a very low coverage area (RSCP < – 105 dBm).

The packet connection is carried on a 64/64 DCH Channel
as consequence of the low coverage conditions.
The UE will likely ramp up its power to the maximum, goes
to Idle Mode and the Application and RLC throughputs go
to zero.
At this point the RAS application will start the Session
Timeout timer, if the throughput is not resumed the Session
Error event is triggered with cause “session timeout”.
PS: Session Error due to Poor DL Coverage

App throughput ~64kbps

Very low RSCP

 FINAL WORDS
For network tuning, we need to rely on field measurements which require extensive
drive tests
Finding the best possible configuration for antenna heights, tilts, azimuths and
parameter setting for all the present cells/sectors in the network and also for
any new sites that might be needed to improve coverage
Power adjustment can also be used for network tuning but can become
complicated and result in poor network performance
Use of Remote Electrical Tilt (RET) Antenna is preferred over mechanical tilt
antenna
Neighbour definition is of prime importance in UMTS network (Soft handover gain
and interference reduction). Keep neighbour list upto 20.
Automated tools are needed that could suggest the best possible neighbour
relations, antenna heights and tilts by using both the field measurements and
the propagation models & simulations
Skilled people, right methods and advanced tools are needed to perform 3G tuning
and optimisation
 Max HSPA users in cell/RNC,RNC
Call Drop analysis licensed capacity:Max AMR/Iups
throughput
Top (N) drops
Neighbours’ Performance
Traffic
(use SHO success per adjs
Cell and its Neighbour counters to identify badly
Cells availability Site performing neighbours) & Map Audit adjacent sites
OK ? for alarms,
Alarms/Tickets
Availability,
YES configuration and
capacity
Configuration & NO
Conf OK
Parameter audit ?
3G Cell at Iur Investigation
YES
SHO based on RNC border? performance Iur
YES
DSR, CPICH
EcNo SHO
Success YES
difference, SHO Relocation success in
SHO branch Rate <
setup fail 90%? target RNC
BTS/Iub
NO
New site ?

ISHO Analyse last RF and IFHO

NO
ISHO detailed radio neighbour
HHO RSSI & Failures
measurements optimisation
BSIC time,
ISHO
cancellation YES 3G cell
3G cell at covers over
inter-RNC
a coverage
Top border ?
hole ?
iss No cell
ues RF and ISHO
found YES
neighbour
ratio >40
optimisation
%
2G Cell Doctor
NO No cell
2G found
Investigation : ISHO ratio > 90 Wrong reference
TCH blocking YES Success % and clock (10MHz tuning)
or TCH Rate < enough
seizure failure 90% ADJG
(interference)

Presentation / Author / Date HSDPA IFHO failures, reject CM for IFHO

Call Drop analysis
1. Check high call drop cells and its neighbouring cells of any faulty alarms
2. Identify call drop root cause failure distribution and main failure contributor (radio, Iu, BTS,
Iur, MS, RNC)

3. Check SHO KPI if performance < 90% ( leads to radio failure)

• Check if cells are at RNC border (check Iur capacity and SRNC relocation problem)
• Detect badly performing neighbours using HO success rate per adjacency counters (M1013)
• High incoming HO failure rate in all adjs – check sync alarms
• Assessing neighbor list plan and visualization check with map
• Evaluate HO control parameters and trigger threshold
4. Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)
 Check missing neighbour (M1015), GSM frequency plan neighbour RNC and MSC database
consistency audit, check alarm of reference clock in 3G or in 2G, check 2G TCH congestion
 Check RRC Drop ISHO RT / NRT
Presentation / Author / Date
Call Drop analysis
5. Detecting DL or UL path loss problem if RAB drop due to radio (dominant call
drop cause > 50%)
 Check UL Lost Active KPI from Iub counters (active L1 synchronization failure) to check UL/DL
path loss problem
 Check ASU failure rate (UNSUC_ASU) which link to NO RESPONSE FROM RLC
 Mapping radio failures with Tx power and CPICH related parameters ->
CPICHToRefRABOffset, PTXDPCH MAX
 Check Call reestablishment timer -> T315
 Ecno distribution for bad coverage issue (M1007C38-M1007C47)
6. Check core network parameter setting if RAB_ACT_FAIL_XXX_IU
 Check SCCP SGSN/RNC IuPS Tias/Tiar if RAB_ACT_FAIL_BACKG_IU
7. If high RAB_ACT_FAIL_XXX_BTS
 Check if any BTS faulty alarm (7653 cell faulty alarm)
 If no alarms, COCO detach/attach
8. If high RAB_ACT_FAIL_XXX_MS
• Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimisation)

Presentation / Author / Date

HSDPA Low Throughput

Presentation / Author / Date

HSDPA Throughput Analysis

Presentation / Author / Date

Good CQI but poor HSDPA throughput

Presentation / Author / Date

COMMON CALL PERFORMANCE ISSUES

Presentation / Author / Date

Common Call Performance Issues

Presentation / Author / Date

Common Call Performance Issues

Presentation / Author / Date

Common Call Performance Issues

Presentation / Author / Date

Common Call Performance Issues

Presentation / Author / Date

Common Call Performance Issues

Presentation / Author / Date

Common Call Performance Issues

Presentation / Author / Date

Video Call Performance Issues

Presentation / Author / Date

Video Call Performance Issues

Presentation / Author / Date

ISHO Performance Issues

Presentation / Author / Date

Soft Handover Neighbour Tuning

Presentation / Author / Date

Active Set Usage
M1013
(These counters are referred to cell addition and cell replacement – no target for deletion)

Absolute Value must be considered not Failure Rate!

Active Set Usage
Major

Mino
r
High # out- Yes
going fails for a Failure
defined ADJS? ADJS
High # out-
going
attempts?
Unbalanced ADJS

Yes
Yes
Zero High # fails for
attempts?
a source?
Failure
WCEL
High #
Yes In – out attempts for
Low used Adjs pairs? a source?

Yes
No Adjs Yes
Min
or
Ping-Pong Unbalanced WCEL

Filtering over attempts must be taken into count Filtering over failure in
that:
- statistical data must stabilized over time.
absolute terms it is possible
- traffic distribution is not considered and a to find the major critical
double-check to localize the event and DT
feedback is required to understand if fenomena events
is traffic driven or cell dependent
Active Set Usage
Filtering criteria:

Major
- High number of failures for a defined out-going adjs ( failure
ADJS)
- high number of fail for a defined source ( failure WCEL )

Minor
- high number of attempts in-comig and out-going for a defined pair
with occasional failure ( ping-pong )
Filtering action are required to find bi-lateral corrispondence
- very low number of attempt with failure ( low used adjs )
- zero number of attempt for declared adjs – stabilized value ( no adjs )
- high number of attempts with occsional failure for an out-going adjs
( unbalanced ADJS )
Either in-coming or out-going condition is sufficient
- high number of attempts with occsional failure for a defined source
( unbalanced WCEL )
Failure ADJS
Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 23 1 442 34 4 0
Source_cell_B 1 0 11 0 53 25 345 0
…
Source_cell_Z 322 54 15 0 2 0 12 0

Failure ADJS

Once anlyzed the

Analyze RSCP from DT
RSCP, the coverage
Very low value of plot taking care to
& NWP coverage plot
considering inter-site
RSCP that not the evaluation of
distance allow the adjs to intersite-distance, it
be used is easy to
understand if
target can be used.
Yes Yes
Target act Down tilt If not only down
as polluter? possibile? tilt is possible or
DERR (ADJS object
Paremeter) cell to
avoid the failure
DERR cell Down tilt during SHO.
Analyze Ec/No from DT
Down tilt must be
carefully anlyzed.
If from Ec/No the
cell can be recovered
Ec/No offset
an individual offset
or filtering (ADJS
object Parameter)
can be introduced
Failure ADJS – Individual Ncell Offset

Ec/Io

Reporting
P CPICH 1 Range

AdjsEcNoOffset
to modify
measurement
P CPICH 2 reporting
behaviour.
Effectively
'moves' cell
border (shrinks or
enlarges cell)

Enlarging Cell 3 by x dB

P CPICH 3
time
Reporting Reporting
Event 1B Event 1A
Failure ADJS – Forbidding Neighbour Cell

E c/ I o

P CPICH 1
PCPICH3 is
Report forbidden to affect
ing the reporting range as
Range its quality is quite
unstable.
AdjsDERR
P CPICH 2 to forbid a cell from
reporting range
calculation in some
instances
P CPICH 3

Time
Failure WCEL
Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 23 15 442 34 124 23
Failure WCEL Source_cell_B 1 0 11 0 53 0 345 0
…
Source_cell_Z 322 1 15 0 2 0 12 0

Analyze Ec/No &BLER Most of the Target failure during the 1A or 1C

from DT & NWP coverage The following gives the number of attempts per event
event.
plot considering inter-site
distance RT Services
KPI ( 1 ) = M1007C10 CELL ADD _ REQUEST ON SHO FOR
RT TRAFFIC
Yes KPI ( 2 ) = M1007C12 CELL REPL _ REQUEST ON SHO
WCEL
Pollution/Interference FOR RT TRAFFIC NRT Services
polluted/interfered?
KPI ( 1 ) = M1007C27 CELL ADD _ REQUEST ON SHO
FOR NRT TRAFFIC
KPI ( 2 ) = M1007C29 CELL REPL _ REQUEST ON SHO
FOR NRT TRAFFIC
Analyze Ec/No from DT
Once anlyzed the Ec/No, BLER, the coverage plot
taking care to the evaluation of intersite-
Yes
distance, it is easy to understand if the WCEL is
KPI(1) ? interferered/Polluted
Tune 1A
If not, two KPIs allow to separate the dominant
contribute
The failure among
rate for the 1A procedure
all the and 1C. can be estimated as well
ADD ( REPL
Relaxing )_ FAIL _ ONSHO
the parameters _ FOR _ x /
an improvement should be
Yes ADD (
achievedREPL )_ REQ _ ON _ SHO _ FOR _ x + ADD ( REPL )_
KPI(2) ? FAIL _ ONSHO _ FOR _ x
Tune 1C
M1007C14 / M1007C12 + M1007C14
M1007C36 / M1007C11 + M1007C36
M1007C30 / M1007C27 + M1007C30
M1007C37 / M1007C28 + M1007C37
M1007C31 / M1007C29 + M1007C31
Failure WCEL - 1A
ActiveSetWeightingCoefficient
Ec/Io is used to weight either
the measurement result Strongest CPICH in AS: P CPICH 1
of the best active set cell
(0) or the sum of
measurement results of all
P CPICH 2 AdditionWindow
active set cells (<>0)
determines the
1A relative
threshold used
by the UE to
calculate the
reporting
range of event
1A. The threshold
is either relative
to the CPICH
Ec/No
P CPICH 3 measurement
result of the
best active set
cell (0), or to
AdditionTime AdditionReportingInterval time
the sum of
defines the defines the period of active set
'time-to-trigger' time that the UE wait, measurement
interval Measurement if the RNC is unable results (<>0)
no to add Ncell to AS,
between the Report
cell entering before sending
the reporting Add to further reports
range and the the AS? periodically, with
interval
UE sending the
measurement
RNC AdditionReportingInterval,
report to the until the Ncell moves
RNC with the 1A out of reporting
event range, or RNC adds
Ncell to AS.
Failure WCEL - 1C
ReplacementWindow
determines the margin by which the
CPICH Ec/No measurement result of
the monitored cell (MNew) must exceed
the CPICH Ec/No measurement result
Ec/Io AS has 3 cells
of the an active set cell (MInAS)
before the UE can send the event 1C
triggered Measurement Report to theP CPICH 1
RNC: MNew >= MInAs +
ReplacementWindow / 2 P CPICH 2

P CPICH 4
1C

weakest CPICH in AS P CPICH 3

ReplacementTime
Defines the period of time the
monitored cell must continuously
stay within the reporting range
before the UE can send a
ReplacementReportingInterval
Measurement Report to the RNC
time
in order
If the RNC istonot replace an active
able to
set the
replace cell active
with the cellmonitored
with the cell
(event cell,
monitored 1C). the UE continues
reporting after the initial
report by reverting to
periodical measurement no
reporting. The parameter
Replacement Reporting Interval Measurement AS
determines the interval of Report update?
periodical measurement reports
when such reporting is
triggered by the event 1C.
RNC
NO ADJS
Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 0 - 442 34 124 23
Source_cell_B 0 - 11 0 53 0 345 0
…
Source_cell_Z 322 1 15 0 2 0 12 0

No Adjs

Zero
attempts?

Repeat Analysis Comparing the ADJS plan provisioned

Yes into the network with the M1013
matrix, it is easy to find if one
declared ADJS is not used (not
Statistic
Stable? present in the list)
Statistic data must be stabilized
Yes before decide to remove it and DT
analysis can help n estimating the
amount of residual noise if down tilt
DT analysis for the Adjs
is not possible

Remove ADJS
Low used ADJS
Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 25 4 442 34 124 23
Low used Adjs Source_cell_B 245 23 11 0 53 0 345 0
…
Source_cell_Z 322 1 3 1 2 1 123 20

Analyze DT
result and
NWP data
It is not difficult in live network to
find some pair working with very low
For low used ADJS has to be
Yes intended and ADJS that has few
Monitored Qual
from DT number of attemps in one day (e.g
acceptable?
<3)
with occasional failure.
Alter. ADJS The ADJS removal has to be
ADJ Offset present?
considered as the last option, after
the quality has been monitored by
Yes
drive test result, considering the
overall capability of the target to be
Interference
evaluation
recovered (e.g. inter-site distance,
power budget) and other options are
available for that area.
Statistic data must be stabilized
Remove ADJS before decide to remove it and DT
analysis can help in estimating the
amount of residual noise if down tilt
is not possible
Unbalanced ADJS

Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z

Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 54 3 345 10 23 1 124 5
Unbalance ADJS Source_cell_B 25 1 11 0 137 3
…
Source_cell_Z 32 2 45 2

Analyze RSCP from DT & NWP

coverage plot considering inter-
site distance e traffic An high number of attempt
distribution could be an indication of a
problem and even in case of
the failure is not associated
an evaluation is required.
Attempt over
the same UE?
No action The key point is the
required
inviduation of the attempt
distribution, that in case are
Yes
not justified but partcualar
Yes
Yes
populated area, coluld
Target act Down tilt
possibile?
generate lot of signalling.
as polluter?
The attempts could be
genarated by 1B event ever
the same UE not counted in
DERR cell Down tilt the M1013.
Analyze Ec/No from DT
& evaluate unbalance
The possibility to recover the
ADJS is the favourite option
and the down tilt carefully
Ec/No offset analyzed considering the
failure associated.
Unbalanced WCEL
Unbalanced WCEL

Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z

Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 543 13 345 10 876 7 124 5
Analyze RSCP from DT & NWP Source_cell_B 25 1 11 0 137 3
coverage plot considering …
inter-site distance and traffic Source_cell_Z 32 2 45 2
distribution

An high number of attempt

Attempt over could be an indication of a
No action
the same UE?
required
problem and even in case of the
failure is not associated an
Yes
evaluation is required.
Yes The key point is the inviduation
WCEL interfered Interference /
pollution of the attempt distribution,
polluted?
that in case are not justified
but partcular populated area,
coluld generate lot of signalling.
Analyze Ec/No from DT The attempts could be
genarated by 1B event ever the
same UE not counted in the
Yes
M1013.
KPI(1) ? Tune 1A The possibility to have an
interference/pollution increase
respect to the unbalanced ADJS.
The optimization should be
Yes performed at WCEL level
KPI(2) ? Tune 1C
The KPI reported are the same
of Failure WCEL
Ping Pong
Down tilt
Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 54 3 345 10 23 1 124 5
DERR cell Yes
Source_cell_B 987 13 11 0 137 3
…
Source_cell_Z 32 2 45 2

Down tilt
possibile?
Ping-pong

No action
Yes required
In this particular case the
high number of attempt is
Analyze RSCP from DT & Attempt from
NWP coverage plot concentrated in a pair
the same UE?
considering inter-site
distance From A >> B and from B >>A
as in the picture
As in the previous case
could be an indication of a
pollution One of them act
as polluter? problem and even in case
of the failure is not
associated an evaluation is
Analyze Ec/No from DT required to avoid to use a
lot signalling.

Not stable, Comparable

Fading? value? The optimization should be
performed at ADJS level
Yes Yes considering that the
filtering option could get
Filtering
to smoother measured
Histeresys
using value
Ec/NoOffset
on the pair
Ping Pong - Filtering

EcNoFilterCoefficient EcNoAveragingWindow

Applied for averaging of

periodical meas. reports

I am in the System Information [ ] UTRAN

CELL_DCH sub-state
Measurement Control [ ]
UE Node B RNC
Measurement Type: Intra-frequency measurements
Reporting events:
1A: Event 1A triggered when CPCIH Ec/Io of the measured cell enters
UE Ec/NoFilterCoeff
reporting range for a defined period of time controls the higher layer
1B: Event 1B triggered when CPICH EC/I0 of the measured cell drops out filtering of physical layer
of the UE reporting range for a defined period of time measurements before the
1C: Event 1C triggered when CPICH EC/IO of the measured cell enter in event evaluation and
AS by a defined margin for a defined period of time measurement reporting is
performed by the UE.
Pollution
Polluter Detection
The best way to individuate a Polluter is the Drive Test
A feedback can come from coverage plot, RNP feedback and Counters
A polluter can be of different type:

1. PSC Pollution
Too high reuse factor for the PSC. New PSC plan is required
2. DL Noise raise
ADJS signal strength out of usage window (will be never utilized
by the UE)
A down tilt or power reduction is the solution evaluating all the
side effects
3. Dominant site
A dominant site over-shooting the ADJ becoming congested
A down tilt or power reduction is the solution evaluating all the
side effects
PSC Pollution
A confirm for the polluter of the first type can come from the counter
M1007C38-47 CELL SPECIFIC CPICH EC / NO - CLASS x
Pollution Criteria:
The M1007C38-47 gives an indication of Ec / No distribution value
measured during event 1A . Having the distribution highly unbalanced
( normally centered on class 2, 3, 4 ) we have an indication of a probable
problem. For example unbalancing towards the scarce value of Ec /No but
continuing to add cells to AS could give an indication of pollution

High number
of class0-3?

Yes
High number of Isolated/unavailable
class>6? WCEL

Yes
Not Polluted WCEL

Polluted WCEL
DL Noise Raise

Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z

Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 25 4 0 - 124 23
Source_cell_B 245 23 11 0 53 0 345 0
…
Source_cell_Z 322 1 3 1 0 - 123 20

The NO ADJS and low used ADJS criteria before presented can
give a confirm for a pollution of this type.
After the statistical data are stabilized, making across-check with
the provisioned ADJS Plan the probable polluters are individuated.
This is obviously a cautelative estimation to be integrated and
confirmed by drive test results
Dominant site

Target_cell_A Target_cell_B Target_cell_C … Target_cell_Z

Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 25 4 26 3 124 23
Source_cell_B 245 23 11 0 53 0
… … …
Source_cell_Z 245 45

Filtering the M1013 pairs for the recurrent target cell with
associated occasional failure we have an estimation of the probable
polluters
For the polluters, originating failures a down tilt is required
Polluted Cell Criteria:
SHO over head can give a soft help in individuating cell where
polluter / overshooting site can be present or where unbalanced cell
criteria could apply

Soft Handover Overhead = RNC_79B =

 M1007C0 ONE_CELL_IN_ACT_SET_RT + M1007C19 ONE_CELL_IN_ACT_SET_NRT 
 
 ( M1007C1 TWO_CELL_IN_ACT_SET_RT + M1007C20 TWO_CELL_IN_ACT_SET_NRT ) ⋅ 2 + 
 ( M1007C2 THREE_CELL_IN_ACT_SET_RT + M1007C21 THREE_CELL_IN_ACT_SET_NRT ) ⋅ 3 
 − 1 ⋅100%
 M1007C0 ONE_CELL_IN_ACT_SET_RT + M1007C19 ONE_CELL_IN_ACT_SET_NRT 
 
 M1007C1 TWO_CELL_IN_ACT_SET_RT + M1007C20 TWO_CELL_IN_ACT_SET_NRT + 
 M1007C2 THREE_CELL_IN_ACT_SET_RT + M1007C21 THREE_CELL_IN_ACT_SET_NRT 
 
Cell Reselection
Cell Reselection 2G -> 3G
Cell Reselection
List

BCCH: FDD_Qm
in, FDD_Qoffset

Start GSM MS starts WCDMA measurements if :

RLA_C< F(Qsearch_I) for 0<Qsearch_I<=7
measurement or
RLA_C> F(Qsearch_I) for 7<Qsearch_I<=15

If, for suitable UMTS cell

& for a period of 5 s:
CPICH RSCP > RLA_C + FDD_Qoffset
WCDMA cell
reselection
and

CPICH Ec/No ≥ FDD_Qmin

2G -> 3G Measurement

Depending on operator´s 2G – 3G interworking strategy parameter Q_search_I should planned accordingly.

In the best case, 3G In the best case, 3G cell

cell measurements are measurements are
possible when RLA_C restricted to the condition:
level < –74 dBm RLA_C level > –78 dBm

GSM

GSM 3G 3G 3G
GSM

Configuration 1 Configuration 2 Configuration 3

RLA_C< RLA_C> F(Qsearch_I) RLA_C< ∞ (always).
F(Qsearch_I) ( 7<Qsearch_I<=15 ) (Qsearch_I=7)
( 0<Qsearch_I<=6 )
2G -> 3G Cell Re-selection Parameters
Qsearch_I and Qsearch_P define the threshold for non-GPRS/GPRS (respectively) capable UEs to measure 3G
neighbour cells when a running average of the received downlink signal level (RLA_C) of the serving cell
below (0-7) or above (8-15) the threshold

Value 0 1 … 6 7 8 9 10 … 14 15
dBm -98 -94 … -74 Always -78 -74 -70 … -54 Never

UE always measures 3G If RLA_C > -70 UE starts

If RLA_C < -94 UE starts 3G measurements
3G measurements cells

FDD_Qoffset and FDD_GPRS_Offset the non-GPRS/GPRS (respectively) capable UEs add this offset to the
RLA_C of the GSM cells. After that the UE compares the measured RSCP values of 3G cells with signal levels
of the GSM cells

Value 0 1 2 3 … 8 … 14 15

dBm Always -28 -24 -20 … 0 … 24 28

Always select irrespective

Reselect in case RSCP >
of RSCP value
GSM RXLev (RLA_C) +28dB
FDD_Qmin, defines minimum Ec/No threshold that a 3G cell must exceed, in order the UE makes a cell
reselection from 2G to 3G.
Cell Re-selection Example-Weaker WCDMA
Non GPRS case
RSCP/
RLA_C Ec/No

Cell re-selection to WCDMA

Serving GSM Cell RLA_C

Qsearch_I=0
(-98 dBm)

FDD_Qoffset =6 (-8 dB)

Measurements starts (serving cell)

FDD_Qmin=0
RSCP (-20 dB)
Neighbour WCDMA Cell

Ec/N0
Minimum Quality Requirement for WCDMA
t
5 sec.
Cell Re-selection Example-Weaker WCDMA
GPRS case
RSCP/
RLA_C Ec/No
RLA_P
Cell re-selection to WCDMA

FDD_GPRS_Qoffset =10 (8 dB)

Serving GSM Cell (Best) Qsearch_P=0
(-98 dBm)

RSCP

Measurements starts (serving cell)

FDD_Qmin
=-20 dB

Neighbour WCDMA Cell Ec/N0

Minimum Quality Requirement for WCDMA

t
5 sec.
Cell Reselection 3G -> 2G
Whilst camping in a 3G cell the UE performs intra-frequency, inter-frequency, and inter-system
measurements based on the measured CPICH EcNo.
Serving cell parameters Sintrasearch, Sintersearch and SsearchRAT are compared with Squal (CPICH
Ec/No – Qqualmin) in S-criteria for cell re-selection

1 - None (Squal > Sintrasearch )

2 - WCDMA intra-frequency (Sintersearch < Squal ≤ Sintrasearch)
3 - WCDMA intra- and inter- frequency, no inter-RAT cells (SsearchRAT < Squal ≤ Sintersearch)
4 - WCDMA intra- and inter-frequency and inter-RAT cells (Squal ≤ SsearchRAT )

Sintrasearch Sintersearch SsearchRAT

4 3 2 1

WCDMA
CELL
Cell Reselection 3G -> 2G

UE starts GSM measurements if

CPICH EcNo CPICH Ec/No =< qQualMin + sSearchRAT

Serving WCDMA cell

SintraSearch First ranking of all the cells based on calculation, with
CPICH RSCP (WCDMA) and RSSI (GSM) hysteresis parameter

SinterSearch Rs = CPICH RSCP + Qhyst1

Rn= Rxlev(n) - Qoffset1
Neighbour WCDMA or GSM
SsearchRAT
cell calculation with offset
qQualMin parameter

No Yes
Rn (GSM) > Rs (WCDMA)
And
Rxlev (GSM) >QrxlevMin

Second ranking only for WCDMA Cell re-selection

cells based on CPICH Ec/No to GSM
Rs = CPICH Ec/No + Qhyst2
Rn=CPICH_Ec/No(n)-Qoffset2 Cell re-selection to
WCDMA cell of highest
R value
Cell Reselection 3G -> 2G
UE ranks the serving cell and the measured neighboring cells to find out if reselection should be made
• All the measured suitable cells (S-criteria) are included in the ranking.
• Criteria for a suitable cell (S-criteria) is defined as
– WCDMA intra-frequency neighbour cell:
CPICH Ec/No > AdjsQqualmin and CPICH RSCP > AdjsQrexlevmin
– WCDMA inter-frequency cell:
CPICH Ec/No > AdjiQqualmin and CPICH RSCP > AdjiQrexlevmin
– GSM cell:
Rxlev > Qrxlevmin

Ranking is done using Criteria R, and the UE reselects to the cell with highest R-criteria. R-criteria is
defined
as:
• For serving cell: Rs = Qmeas,s + Qhysts
• For neighboring cell Rn = Qmeas,n – Qoffsetts,n
Qmeas is CPICH Ec/No for WCDMA cell and RxLev for GSM cell
How to avoid ping pong ?
When phone is camped on 3G, GSM measurements can start when CPICH Ec/Io of serving cell is below
Ssearch_RAT + QqualMin.
When phone is camped on GSM, cell reselection to 3G is possible if CPICH Ec/Io of the candidate is above
FDD_Qmin.
Therefore, to avoid ping pongs between 3G and GSM the following condition should be met:

FDD_Qmin >= QqualMin + Ssearch_RAT

CPICH Ec/Io

FDD_Qmin >= -12 dB

QqualMin +Ssearch_RAT

Ssearch_RAT=4 dB

QqualMin=-18 dB
Camping on 3G Measure GSM Camping on 3G
t
How to avoid ping pong ?

Parameters for cell reselections

• Qqualmin = -18dB Ssearch_RAT =2dB -> the 3G->2G cell reselection starts when Ec/No hits -16dB
• FDDQmin(GPRSFDDQmin) = -14dB (6) and QsearchP/QsearchI = always

The cell reselection paramters 3G -> 2G and 2G -> 3G provide only 2dB hysteresis which is not enough and should be
noticed from the RNC statistics as high amount of INTR_RAT_CELL_RE_SEL_ATTS from all the RRC Connection
Setup Attempts

• Recommendation is to adjust the FDDQmin from -14dB to -10dB (or even up to -8dB) to provide 6 to 8 dB
hysteresis between 3G to 2G cell reselection and 2G to 3G cell reselection
• Another parameter to tune is Qrxlevmin

On top of Treselection the above parameters will slow down further the 2G to 3G and 3G to 2G cell reselections
Treselection
How long the reselection conditions must be fulfilled before reselection is triggered?
Treselection

Impacts all cell reselections : Inter RAT, intra frequency and inter frequency
The UE reselects the new cell, if the cell reselection criteria (R-criteria, see next slide) are fulfilled during a time
interval
Treselection
As this parameter impacts on all the cell reselections too long Treselection timer might cause problems in high mobility
areas but too short timer causes too fast cell reselections and eventually causes also cell reselection ping pong
Recommended value 1s should work in every conditions i.e. enough averaging to make sure that correct cell is
selected
However careful testing is needed to check the performance of different areas
• (Dense) Urban area, slow moving UEs with occasional need for fast and accurate (to correct cell) reselections e.g.
outdoor to indoor scenarios or city highways – in some cases cell by cell parameter tuning is performed to find
most optimal value between 0s and 2s but typically 1s is optimal value when workload is considered as well
• Highways, fast moving UEs must reselect correct cell – typically 1s works the best (however occasionally also 0s
might be needed in fast speed outdoor to indoor cell reselections e.g. tunnels)
• Rural areas, slow or fast moving UEs need very often reselect between different RATs and make proper cell
reselections even when the coverage is poor – typically 1s works the best
• Location Area Borders, usually the coverage is fairly poor – typically 1s works the best but sometimes to reduce
location area reselection ping pong 1s is used when going from LA1 to LA2 and 2s from LA2 to LA1
IRATHO
IRATHO

As M1013 described in PartI, M1015 return statistic for intesystem HO. The filtering criteria
can be replicated with the exception of ping-pong

Filtering criteria:
Major
- High number of failures for a defined out-going adjg (failure ADJG)
- high number of fail for a defined source (failure WCEL)

Minor
- very low number of attempt with failure (low used adjg)
- zero number of attempt for declared adjs– stabilized value (no adjg)
- high number of attempts for an out-going adjs (unbalanced ADJG)
out-going condition is sufficient
- high number of attempts for a defined source (unbalanced WCEL)

Same procedures can be applied to the case considering that the event related are 1E and 1F
1E/1F Events for CPICH Ec/No and RSCP
HHoEcNo(RSCP)Thres
HHoEcNo(RSCP)Cancel hold
Defines the threshold of Ec/No(RSCP) determines the absolute CPICH
e.g. P-CPICH Ec/No

that must be exceeded by a measurement Ec/No threshold which is used by the

of an active set cell to be canceled the UE to trigger the reporting event 1F.
Cell 1 event 1F related When the measured CPICH Ec/No of
all active set cells has become worse
Cell 2 than or equal to the threshold in
question, the RNC starts inter-
frequency or inter-RAT (GSM)
measurements in compressed mode
for the purpose of hard handover.

Cell 3

1F
1E

HHoEcNo(RSCP)CancelTime
determines the time period during which the CPICH
RSCP of the active set cell must stay better than the
threshold HHoRscpCancel before the UE can trigger the
reporting event 1E.
time
HHoEcNo(RSCP)TimeHysteresis
determines the time period during which the CPICH Ec/No of the active
set cell must stay worse than the threshold HHoEcNoThreshold before
the UE can trigger the reporting event 1F.
IRATHO – Triggering reason

1. Low measured absolute

CPICH Ec/No, event 1E/1F 2 . Low measured absolute
CPICH RSCP, events 1E/1F
FMCG: GSMcauseCPICHEcNo
FMCG: GSMcauseCPICHrscp

Triggering reason gives

3. UE Tx power approaches an indication
its maximum allowed 4. DL DPCH approaches its
power, event 6A/6D maximum allowed power

FMCG: GSMcauseTxPwrUL FMCG: GSMcauseTxPwrDL

6 . Others
5. Quality deterioration report - Load and Service based HO
from UL outer loop PC - IMSI based HO
- Emergency ISHO
FMCG: GSMcauseUplinkQuality

GSMcauseX
These parameters indicates whether a handover to GSM caused by low measured absolute CPICH Ec/No of the serving cell is
enabled (1)
IRATHO – Triggering reason

It’s important to know which is the most frequent triggering reason:

It’s possible to diffentiate between quality and coverage reasons and understand the
network limiting factors:

1. CPICH coverage
2. Pilot pollution
3. UL/DL Service coverage

In actual case is possible to dsciminate between low CPICH coverage triggered by high# RSCP
attempts or probable pilot pollution triggered by high # Ec/No attempts

A KPI that gives reason for that is

IS _ HHO _ W _ CMOD _ xxx _( N ) RT

xxx _ Cause _ perc =
∑ IS _ HHO _ W _ CMOD _ xxx _( N ) RT
Allcauses
IRATHO – Triggering reason
Enabling all the causes a screaning on the network is returned individuating the limiting factor
and the required action.

Start

Yes
High # Ec/No? DL interference/ Pollution
DL Qual limiting
should be evaluated

DL
Yes
High # RSCP? CPICH power analisys/ new
DL level limiting
site required
This condition
should be the
dominannt one
Yes without
High # UE New site required or new
UL level limiting associated
Tx pwr? Parametrization for IRATHO
failure

UL
Yes
Load analisys and UL
High # UL Qual? UL qual limiting interference evaluation

End

Yes
High # DL New planning for service is
Service limiting
DPCH? required
IRATHO - Failure
CN
UE Node B RNC

RRC: Measurement Control

ISHO triggering
Failure can happen
RRC: Measurement Report (5 reasons are
possible)
at different point:
NBAP: Radio Link Reconfiguration Prepare
NBAP: Radio Link Reconfiguration Ready
Initial Before decision
NBAP: Radio Link Reconfiguration Commit Compressed

RRC: Physical Channel Reconfiguration

Mode
Configuration
- Before CM
RRC: Physical Channel Reconfiguration Complete - During CM
NBAP: Compressed Mode Command
- Measuring GSM
RRC: Measurement Control
GSM RSSI cell
Measurement
RRC: Measurement Report

RRC: Cell Change Order from UTRAN

After decision
RANAP: SRNS Context Request - Drop

RANAP: SRNS Context Response

Utran and ue have to
RANAP: SRNS Data Forward Command treated as particular
RANAP: IU Release Command case
RANAP: IU Release Complete
CM not possible
UE
UE BTS
BTS RNC
RNC

AC is responsible for checkiing if CM is possiblle RRC: Measurement Control

RRC: Measurement Report (3,4,5)

If CM fails one of the following mus be checked:

Admission
Admission Control
Control
check
check for
for CM
CM

Not enough resources – AC reject CM. NBAP: Radio Link Reconfiguration Prepare

Evaluate interference NBAP: Radio Link Reconfiguration Ready

Expand capacity NBAP: Radio Link Reconfiguration Commit

RRC: Physical Channel Reconfiguration

(see PartI) RRC: Physical Channel Reconfiguration Complete

NBAP: Compressed Mode Command

The following KPI gives an indication of the number of CM

RX Level measurement phase for
all ISHO neighbours RRC: Measurement Control

procedure not started RRC: Measurement Report

NBAP: Compressed Mode Command

BSIC verification phase for target cell
RRC: Measurement Control

IS_COM_MOD_STA_NOT_POS RRC: Measurement Report

IS_COM_MOD_STA_NOT_POS + ∑ IS_HHO_W_CMOD j
j

Considering that M1010C2 (INTER SYST COM MOD STA NOT POS FOR RT) is updated if it is
not possible to start inter-system compressed mode measurement due to radio resource
congestion, BTS- or UE-related reasons to have a better insight on radio congestion it could
be better to use, e.g. for UL the M1002C361 REQ FOR COM MODE UL REJECT TO INT SYST
HHO IN SRNC and the M1002C357 REQ FOR COM MODE UL TO INT SYST HHO IN SRNC and
use the following :

M1002C361/M1002C357
NO Cell Found … measurement
fail
No Cell Found
Counters
NO Cell Found means:
there is no suitable gsm target cell in terms of RX Level
Compressed
OR Mode start
the target gsm is suitable but its BSIC verification fails
AND HHO Attempt
Counters
the maximum number of measurement reported are received
AND … measurement not
maximum measurement interval is not expired fail

The following KPI gives an indication of the number of GSM cell not found

∑ IS _ HHO _ NO _ CELL _ xxx _( N ) RT

ISHO _ Meas _ Fail _ Rate = Allcauses

∑ IS _ HHO _ W _ CMOD _ xxx _( N ) RT

Allcauses

Missing ADJG could be the reason or a dedicated parameter tuning for the 1F event.
The KPI can be madified taling care of the WO_CMOD events
NO Cell Found
Start

High #
NO Cell? End

Yes

Yes
New site
GSMCause=Ec/ Pollution evaluation required
Nol?

Reduce “Cancel”
Verify Good GSM coverage
in the far field? Increase “Time hysteresis”
ADJG

ADJG Good GSM coverage

Coverage anlisys
Addition? in the near field?

Yes Yes

Reduce
End
“thershold”
DROP & UNSUCCESS IRATHO
Optimization for unsuccess is not possible
because the reason are:
UTRAN Failure
- physical channel failure (the UE is not able to
Counter
establish the phy.
- Protocol error
- Inter-Rat protocol error
UE Failure
Counter - Unspecified
Drop are related to drop call occurred
during the procedure

ISHO Unsuccess
HHO Attempt
Counters Counters ∑ CON _ DRPS _ IS _ HHO _ xxx _( N ) RT
ISHO _ Drop _ Rate = Allcauses

∑ IS _ HHO _ ATT _ xxx _( N ) RT

Allcauses

ISHO Success
Counters In this case the optimization is required and
pass through the evaluate of GSM and 3G plot
coverage. Optimize If necessary number of
ADJG or NWP parameters otherwise tune
RRC Drop RNW parameters.
Counters Thresholds can be relaxed to favourite an
early exit from 3G layer
3G –> 2G Unbalancing

This topic present the inherent problem due to the fact that the 2G layer is not involved in
the analisys.
Few consideration can be performed under some assumption:
The following KPIs used over a cluster for CS voice service gives the percentage of the CM
started over all the RAB, giving an idea of the attempted mobility procedure requested for a
cluster where the 3G coverage should be assured

∑ IS _ HHO _ ATT _ xxx _ RT

Perc _ Voice _ Call _ ISHO = Allcauses

RAB _ ACC _ COMP _ CS _ VOICE

Better to use completes: failures, normal & SRNC reloc on denominator and use the KPI inside the
3G cluster or difining a polygon where 3G service is required

Once Correlated with voice drop due to radio link failure and rrc drop during ISHO, the KPI can
help operator in understand the ISHO strategy. Similar KPI is possible for PS

Threshold to shrink the HO area or inhibit the procedure has to be setted