04 Air Interface Optimization

3G RANOP RU30
Air interface optimization
Soc Classification level

1
Nokia Siemens Networks
RN31574EN30GLA0
Course Content
KPI overview
Performance monitoring
Air interface optimization
Traffic Monitoring
Capacity Enhancement

2
RN31574EN30GLA0
Module Objectives
At the end of the module you will be able to:
Describe techniques for interference and neighbour analysis
and interference reduction
Discuss techniques for coverage monitoring and enhancement
Understand techniques for slow fading analysis
Describe techniques to monitor and improve CQI
Describe how to improve neighbour plan with NSN Optimizer
Tool

3
RN31574EN30GLA0
Air Interface Optimization

Interference monitoring and reduction
Overview
Ec/Io
Little I
Pilot pollution - cell matrix
Propagation delay - positioning
SHO delay
Coverage monitoring and enhancement

Slow fading analysis
CQI monitoring and improvement (HSDPA)
NSN Optimizer Tool (appendix)

4
RN31574EN30GLA0
Interference monitoring Ec/Io

Ec/Io = RSCP / RSSI
Indicates total amount of interference in a cell
Decreases from cell centre towards cell edge
Power
(dBm)
RSSI
Ec/Io
Ec/Io
RSCP
distance

5
RN31574EN30GLA0
Interference monitoring little i

Little i = adjacent cell interference / own cell interference
Indicates overlap of cells due to their total DL power
Increases from cell centre towards cell edge
RSSI
i = 0.3
i = 1.0
cell centre
power of server
dominates
cell edge
power of neighbours
dominate
cell 1

6
cell 2
RN31574EN30GLA0
Interference monitoring pilot pollution

Pilot pollution = total adjacent cell RSCP / own cell RSCP
Indicates overlap of cells due to their CPICH power
Increases from cell centre towards cell edge
Dominance of neighboring CPICH usually consequence of SHO problem
RSCP
cell centre
serving CPICH
dominates
cell 1

7
cell edge
neighbouring CPICH
dominate
RN31574EN30GLA0
cell 2

Overview
Ec/Io
Little I
SHO delay


8
RN31574EN30GLA0
Ec/Io monitoring RRC messages

Ec/Io indicated by the following RRC messages
Connection request
serving cell only
whole cell area covered
Cell update
serving cell only
cell edge (cell update) only
Event 1A report
all measured cells
cell edge (SHO) only
Event 1B report
all active cells
Event 1C report
all active cells and better neighbor
Event 1E report
all active cells
cell edge (HHO) only
Event 1F report
all active cells
UE
BS
RNC
Connection request
Cell update
Event 1A1F report

9
RN31574EN30GLA0
Ec/Io monitoring connection request

New RU30 counters M1033C0M1033C9
Number of connection requests falling into specific Ec/Io interval
Updated in serving cell
Ec/Io -2 dB
-2 dB > Ec/Io -4 dB
-4 dB > Ec/Io -6 dB
-6 dB > Ec/Io -8 dB
-8 dB > Ec/Io -10 dB
-10 dB > Ec/Io -12 dB
-12 dB > Ec/Io -14 dB
-14 dB > Ec/Io -16 dB
-16 dB > Ec/Io -18 dB
-18 dB > Ec/Io

10
RN31574EN30GLA0

Practical example RNC cluster
HHO Ec/Io
threshold
Typical
target
Somewhat lower Ec/Io

for the 900 MHz band
Number of cells versus median Ec/Io

11
RedRN31574EN30GLA0
= 2 GHz Green = 900 MHz

Practical example single cell of average performance (2 GHz)
HHO Ec/Io
threshold
Typical
target
Whole cell area

Most calls setup under
acceptable conditions
Few calls setup under
bad conditions
Very seldom call setup
in HHO area
Number of connection requests versus Ec/Io

12
RN31574EN30GLA0
Ec/Io monitoring event 1A report

Counters M1007C38M1007C47
Number of Event 1A reports falling into specific Ec/Io interval
Updated in best active cell
Ec/Io -5 dB
-5 dB > Ec/Io -10 dB
-10 dB > Ec/Io -12 dB
-12 dB > Ec/Io -14 dB
-14 dB > Ec/Io -16 dB
-16 dB > Ec/Io -18 dB
-18 dB > Ec/Io -20 dB
-20 dB > Ec/Io -22 dB
-22 dB > Ec/Io -24 dB
-24 dB > Ec/Io

13
RN31574EN30GLA0

Somewhat lower Ec/Io

HHO Ec/Io Typical

threshold target
Lower Ec/Io in SHO (cell

edge) than during RRC
setup (whole area)
Number of cells versus median Ec/Io

14
RedRN31574EN30GLA0

HHO Ec/Io
threshold
Typical
target
#reports
Cell edge
Many calls in bad
conditions
A considerable fraction of
calls even in HHO area
Number of event 1A reports versus Ec/Io

15
RN31574EN30GLA0
Ec/Io monitoring causes for low quality

Low
Ec/Io
Low
RSCP
High
Transmitted
Carrier
Power
High
Little i
Io mainly
due to UE
receiver
noise
Io mainly
due to own
cell
interference
Io mainly
due to other
cell
interference

16
RN31574EN30GLA0

Overview
Ec/Io
Little I
SHO delay


17
RN31574EN30GLA0
Little I monitoring - requirements

Estimate of little I requires knowledge both of
Ec/Io (total interference)
TCP (own cell interference)
Little I monitoring not supported by NSN counters

Requires analysis of protocol trace

18
RN31574EN30GLA0
Little I monitoring role for capacity

Little I indicates grade of total cell power overlap
The higher the overlap, the lower the capacity
1.5
0.75
0.5
0.25
0
Example
16 W overload threshold
Little I = 1.0 throughput = 700 kbps
Little I = 0.5 throughput = 1100 kbps (about 60% more)

19
RN31574EN30GLA0
Little I monitoring RRC setup

Typical target
Typical target
Micro cell
Macro cell
Somewhat higher little I

Number of cells versus median little i

20
RedRN31574EN30GLA0
Little I monitoring RRC setup

Typical target
Whole cell area
Micro cell
Most calls little effected by

adjacent cell interference
Typical target
Macro cell
Few calls strongly effected

by adjacent cell interference
Number of connection requests versus little i

21
RN31574EN30GLA0
Little I monitoring impact on Ec/Io

Clear relationship
Low Ec/Io mainly due to
Not due to high DL load
Median Ec/Io versus median little I

22
EachRN31574EN30GLA0
point = one cell
Little I monitoring impact on Ec/Io

Practical example single cell of average performance
Clear relationship
Ec/Io versus little I

23
EachRN31574EN30GLA0
point = one call

Overview
Ec/Io
Little I
SHO delay


24
RN31574EN30GLA0
Pilot pollution monitoring requirements

Pilot pollution monitoring requires complete knowledge of the surroundings
of the UE
Event 1A report the only suitable message
RNC informs UE about ADJS cells to be measured by measurement control
message after
RRC setup
Active set update
UE
BS
RNC
Measurement control =
List of ADJS cells
Event 1A report =
ADJS cells measured by UE

25
RN31574EN30GLA0
Pilot pollution monitoring combined neighbour list

Each cell has its own ADJS list
In SHO the ADJS lists of the individual active cells are combined together
according the following rules
1.
Active set cells are included
2.
Neighbour cells which are common to three active set cells are included
3.
Neighbours which are common to the controlling cell and a second active set cell are
included. (cell, other than the controlling cell, which has the highest CPICH Ec/Io)
4.
Neighbour cells which are common to two active set cells are included
5.
Neighbour cells which are defined for only one active set cell are included
6.
Neighbours which are defined only for the second ranked cell are included
7.
Neighbours which are defined only for the third ranked cell are included
If the combined list exceeds the maximum number of 32 cells during any
step then the handover control stops with the algorithm

26
RN31574EN30GLA0
Pilot pollution monitoring combined neighbour list

Because of neighbour list combining it is possible
to measure handover activity between cells without
ADJS relationship
In the example ADJS relationship exists between
cells 2-6 and 6-7, but not between 2-7
In cell 2 cell 6 can be added to active set
Than cell 7 can be added to active cell as well, even
if cell 2 still is best active cell
1
2
Neighboured
4
5
6
Not neighboured
9
7
8
UE path
27
RN31574EN30GLA0
Pilot pollution monitoring detected set reporting

According standard operation UE measures ADJS cells only
Nearby cells forgotten in ADJS list will escape detection
Will never become active and therefore can strongly interfere with active set
Detected set reporting

Force UE to measure and report all visible cells
Reported cell not defined as ADJS is detected cell ADJD
ADJS
cells
Serving
BTS
SHO to ADJD cell allowed, if no ADJS cell available
Problems
High signaling load for RNC due to longer
measurement reports
Unstable SHO decisions due to degraded UE
measurement accuracy (more neighbors measured
Other nearby
cells
during same time)

28
RN31574EN30GLA0
RNC
Pilot pollution monitoring NSN counters

With the optional counters M1013, for each ADJS or ADJD cell one can evaluate
the following properties
M1013C2 / M1013C3 = average Ec/Io difference active non active cell (for all active cells)
M1013C4 / M1013C5 = average Ec/Io (for all reported cells)
M1013C6 / M1013C7 = average RSCP (for all reported cells)
From these counters follows the overall pilot pollution
Pilot _ pollution
RSCP
neighbor_ cell _ i
RSCPbest _ active _ cell
Ec / Io
neighbor_ cell _ i
Ec / Iobest _ active _ cell
With the optional counters M1028, for each ADJD cell one can evaluate the
following properties
M1028C0 / M1028C1 = average Ec/Io (for all reported ADJD cells)
M1028C2 / M1028C3 = average RSCP (for all reported ADJD cells)

29
RN31574EN30GLA0
Pilot pollution monitoring overall results

Typical target
in SHO
Pilot pollution higher in

the 900 MHz band
In general rather high
values, as SHO (cell
edge) considered only
Number of cells versus median pilot pollution

30
RedRN31574EN30GLA0
Pilot pollution monitoring overall results

Typical target
in SHO
#reports
Cell edge
Many calls strongly effected
by adjacent cell interference
Number of event 1A reports versus pilot pollution

31
RN31574EN30GLA0
Pilot pollution monitoring impact on Ec/Io

Clear relationship
pilot pollution
For one cells low Ec/Io

due to low RSCP
Median Ec/Io versus median pilot pollution

32
EachRN31574EN30GLA0
point = one cell
Pilot pollution monitoring impact on Ec/Io

Clear relationship
Low Ec/Io mainly due to pilot pollution
Some reports taken under very low RSCP
Ec/Io versus pilot pollution

33
EachRN31574EN30GLA0
point = one event 1A report
Pilot pollution monitoring cell matrix

In case of high pilot pollution the interfering neighbors must be found
Treat each event 1A report by the following way
Best active cell = server
Each other cell = neighbor
Evaluate for each neighbor the following properties

N = total number of reports collected for the server
n = number of reports collected for specific neighbor
Average Ec/Io = Ec/Ioserver - Ec/Ioneighbor
n Ec / Io [ dB] /10
Pilot _ pollution _ neighbor 10
N
Example values for pilot pollution
Ec/Io = 4dB (addition window) pollution = 10-0.4 = 0.4
Ec/Io = 6dB (drop window) pollution = 10-0.6 = 0.25

34
RN31574EN30GLA0

Practical example single cell of high overall pilot pollution
Ec/Io per
neighbor
Pilot pollution per
neighbor
N reports
for server
n reports for
neighbor
e.g. 79 / 87 * 100.78 / 10
= 1.088
Goal to detect neighbors responsible for high pilot pollution
Consider for each neighbor

How often reported ?
With which strength relative to the server ?
35
RN31574EN30GLA0

In general very strong neighbors

(problem over whole server area)
Occasionally too strong

neighbors (local problem)
Very frequently reported
Rarely reported
Then as strong as server or even

stronger
But then stronger than

server
Cause for high pilot pollution

Two very strong neighbors (probably their coverage area too large)
SC 123 in the average stronger than server (pilot pollution = 1.1)
SC 172 in the average almost as strong as server (pilot pollution = 0.7)
36
RN31574EN30GLA0

In general strong
neighbors
In general very
weak neighbor
Frequently reported
Very seldom
reported
Then as strong as
server or even stronger
Far below server
Cause for pilot pollution

Several strong neighbors (probably coverage area of server too large)
SC 506 / SC 504 / SC 174 / SC 197
All with pilot pollution = 0.20.4

37
RN31574EN30GLA0

Cause of pilot pollution
One very strong neighbor (SC 92) with pilot pollution 0.7
Two strong neighbors (SC 89..91) with pollution = 0.2...0.4
On the other side many unnecessary neighbors with pilot pollution = 0
38
RN31574EN30GLA0
Pilot pollution monitoring optimization flow

High overall
pilot pollution
Many not very

strong
neighbours
Few very
strong
neighbours
Intra-BTS
Check angle
between sectors
Check horizontal
antenna beam

39
Inter-BTS
Check whether coverage

area of neighbor is too large
RN31574EN30GLA0
Check whether coverage

area of server is too large

Overview
Ec/Io
Little I
SHO delay


40
RN31574EN30GLA0
Propagation delay monitoring limitations

To recognize whether a cell is too large, at least the distances of the served
users must be known
UL frame protocol encapsulating RRC connection request the only message
indicating propagation delay
The propagation delay is given with a resolution of 3 chips = 234 m
UE
BS
RNC
RRC connection request

UL frame protocol
RRC connection request encapsulated
Propagation delay

41
RN31574EN30GLA0
Propagation delay monitoring NSN counter

Counters M1006C128M1006C148
Number of connection requests falling into specific propagation delay interval
The intervals are hardcoded, but depend on the setting of the parameter
PRACHDelayRange (see next slide)
The parameter offers the following options
Set 1 up to 5 km
Set 2 up to 10 km
Set 3 up to 20 km
Set 4 up to 60 km
Set 5 up to 180 km

42
RN31574EN30GLA0
Propagation delay monitoring NSN counter

43
RN31574EN30GLA0
Propagation delay monitoring too large cell

Practical example single cell with high pilot pollution
Cell matrix indicates
No extremely strong neighbor
But several significant neighbors
Server itself might be too large
Distant access outside

intended cell area
Number of connection requests versus propagation delay

44
RN31574EN30GLA0
Propagation delay monitoring positioning

Estimate of the position of an UE requires knowledge about the distance to
three BTS
Two possible options exist
Combination of propagation delay information and propagation model
Three visible BTS needed only
But result depends on propagation model
Combination of Rx-Tx time difference and round trip time

Active set with three BTS needed
But result model independent
Positioning not supported by NSN


45
RN31574EN30GLA0

Practical example single cell with high pilot pollution
Server
Too distant
access
Positioning confirms too distant

access indicated by propagation
delay statistics
Probably water reflection

46
Number
of connection requests per pixel
RN31574EN30GLA0

Practical example cell appearing as strong interferer
Too distant
access
Server
Positioning indicates too distant

access along broad street
Cell is interferer due to street
canyoning effect
Number of connection requests per pixel

47
RN31574EN30GLA0

Overview
Ec/Io
Little I
SHO delay


48
RN31574EN30GLA0
SHO delay monitoring idea

Pilot pollution can be introduced not only by too huge overlap between cells,
but also by problems with SHO
UE informs RNC too late about the need for SHO
RNC setups new radio link too late
RNC cannot perform SHO because no resource available in target cell
Ec/Io
New RL setup e.g.

1dB difference
CPICH 1
CPICH 2
Addition window
4dB difference
1st event 1A report e.g.
2dB difference
time

49
RN31574EN30GLA0
SHO delay monitoring idea

Consider difference Ec/Io between serving cell and best non active cell
under the following conditions
First event 1A report sent after RRC setup (measurement)
Last event 1A report sent before first RL setup due to SHO (execution)
Difference should be as close as possible to addition window

Too small according measurement UE acts too late
Too small according execution RNC acts too late
SHO delay monitoring not supported by NSN counters


50
RN31574EN30GLA0
SHO delay monitoring overall results

Practical example RNC cluster (measurement)
Addition
window
RT 1A window usually 3dB

NRT 1A window often 1-2dB only
If NRT service running, UE needs more
time to inform RNC about SHO
Speed up SHO process by somewhat
larger addition window (4.5 to 5 dB)
But than also larger drop window (6.5
to 7 dB) needed to avoid ping-pong
Number of cells versus median 1A window
Red = RT Green = NRT

51
RN31574EN30GLA0
Sometimes 1A reporting
although addition
window not fulfilled yet
SHO delay monitoring overall results

Practical example RNC cluster (execution)
RT almost same statistic as for measurement mode

no further delay due to RNC processing
NRT statistic clearly shifted to even smaller 1A window
further delay due to RNC processing
Number of cells versus median 1A window

52
RN31574EN30GLA0
Addition
window
SHO delay monitoring impact on pilot pollution

RRC release
margin
Neighbor
equals server
Addition
window
1A reporting although addition

High pilot pollution

in case of too late
SHO process
Pilot pollution versus 1A window
Each point = one event 1A report

53
RN31574EN30GLA0
SHO delay monitoring impact on Ec/Io

RRC release
margin
Neighbor
equals server
Addition
window
1A reporting although addition

Very low quality in

case of too late SHO
process
Some reports taken under very

low RSCP
Ec/Io versus 1A window

54
RN31574EN30GLA0
SHO delay monitoring event 1B

Not only event 1A, but also event 1B related SHO procedure might be done
too late
Unwanted consumption of capacity, as bad active cell kept too much time in
active set
UE informs RNC too late about the need to drop bad active cell
RNC deletes radio link too late
Ec/Io
RL deletion e.g.
9dB difference
Drop window
6dB difference
CPICH 1
CPICH 2
1st event 1B report e.g.

8dB difference
time

55
RN31574EN30GLA0
SHO delay monitoring event 1B

Consider difference Ec/Io between best and worst active cell under the
following conditions
First event 1B report sent after RRC setup (measurement)
Last event 1B report sent before first RL deletion due to drop (execution)
Difference should be as close as possible to drop window

Too large according measurement UE acts too late
Too large according execution RNC acts too late
SHO delay monitoring again not supported by NSN counters


56
RN31574EN30GLA0
SHO delay monitoring overall results event 1B

Practical example RNC cluster (measurement)
RT 1B window usually 8 to 9 dB
Drop
window
NRT 1B window usually 7 to 9 dB

UE in general needs too much time to inform
RNC about SHO
Sometimes 1B reporting
although drop window
not fulfilled yet
In principle SHO process could be speed up by

somewhat lower drop window (5 to 5.5 dB)
But contradicts requirements for event 1A !!
Number of cells versus median 1B window

57
RN31574EN30GLA0
SHO delay monitoring overall results event 1B

Practical example RNC cluster (execution)
Drop
window
Statistic slightly shifted to
bigger 1B window
Sometimes 1B execution
although drop window
not fulfilled yet
Small further delay due to

RNC processing
Number of cells versus median 1B window

58
RN31574EN30GLA0



59
RN31574EN30GLA0
RSCP monitoring RRC messages

RSCP indicated by the following RRC messages
Connection request
serving cell only
whole cell area covered
Cell update
serving cell only
cell edge (cell update) only
Event 1A report
all measured cells
Event 1B report
all active cells
Event 1C report
all active cells and better neighbor
Event 1E report
all active cells
Event 1F report
all active cells
RSCP reporting by connection request optional feature only

UE
BS
RNC
Connection request
Cell update
Event 1A1F report

60
RN31574EN30GLA0
RSCP monitoring connection request

New RU30 counters M1033C10M1033C26
Number of connection requests falling into specific RSCP interval
RSCP < -113 dBm
-113 dBm RSCP < -110 dBm
RSCP < -50 dBm
61
RN31574EN30GLA0
RSCP monitoring event 1A report

RSCP monitoring in SHO not supported by NSN counters

62
RN31574EN30GLA0

HHO RSCP Typical
Typical
threshold
target RT target NRT
Clearly better coverage in

900 MHz band
Too low coverage in 2 GHz
band especially for NRT
40W cells with 4W CPICH
required
Number of cells versus median RSCP

63
RedRN31574EN30GLA0

#reports
HHO RSCP Typical

Typical
threshold
target RT target NRT
Number of event 1A reports versus RSCP

64
RN31574EN30GLA0
RSCP monitoring impact on Ec/Io

Ec/Io goes slowly down with

decreasing coverage
Dependence much weaker than
on little I or pilot pollution
Median Ec/Io versus median RSCP 2 GHz band

Each point = one cell
65
RN31574EN30GLA0

Lower Ec/Io at same coverage in

comparison to 2 GHz band
In 900 MHz band higher adjacent
cell interference
Median Ec/Io versus median RSCP 900 MHz band

Each point = one cell
66
RN31574EN30GLA0

Ec/Io rather stable down

to coverage of -100 dBm
Than rapid drop with
decreasing coverage
Ec/Io versus RSCP

67
RN31574EN30GLA0



68
RN31574EN30GLA0
Slow fading analysis - motivation

Both Ec/Io and RSCP undergo certain scatter due to shadowing
Must be taken into account when specifying thresholds for opposite procedures e.g.
Event 1A (add cell) / 1B (drop cell)
Event 1F (enter compressed mode) / 1E (leave compressed mode)
Cell re-selection or ISHO to 2G / to 3G
If thresholds for such procedures are to close together, ping-pong mobility and thus
unwanted signaling occurs
NSN counter do not give scatter of Ec/Io and RSCP directly
Must be determined manually from Ec/Io and RSCP distributions of each cell

69
RN31574EN30GLA0
Slow fading analysis scatter of Ec/Io

Default difference
Default difference
Drop window
addition window
HHO Ec/Io threshold

HHO Ec/Io cancel
Scatter of Ec/Io often larger

than 2 dB
Risk of ping-pong 1A/1B
Scatter of Ec/Io rarely larger
than 3 dB
Little risk of ping-pong 1F/1E
Number of cells versus scatter of Ec/Io (RRC connection request)

Red = 2 GHz Green = 900 MHz
70
RN31574EN30GLA0
Slow fading analysis scatter of Ec/Io

Default difference Default difference
Drop window
addition window
HHO Ec/Io threshold

HHO Ec/Io cancel
Under SHO conditions more scatter

of Ec/Io than during RRC setup
More shadowing at cell edge
Number of cells versus scatter of Ec/Io (Event 1A report)

71
RN31574EN30GLA0
Slow fading analysis scatter of RSCP

Default difference
HHO Ec/Io threshold
HHO Ec/Io cancel
Scatter of RSCP usually much
larger than 3 dB
High risk of ping-pong 1F/1E
Number of cells versus scatter of RSCP (Event 1A report)

72
RN31574EN30GLA0



73
RN31574EN30GLA0
CQI monitoring - motivation

For HSDPA there is no fast power control, but link adaptation
The actual HSDPA data rate depends on the channel quality index CQI
The CQI is estimated by the UE with a vendor specific algorithm on the
basis of
CPICH Ec/Io (measured by UE)
Initial HSDPA power (signaled by RNC at HSDPA setup and serving cell change)
CQI

74
RN31574EN30GLA0

According NSN CQI reported every 4ms by UE
Reported CQI compensated by Node B on the basis of
Actual HS-PDSCH power
Number of ACK and NACK
Node B decides about transport block size for next sub-frame

Modulation (QPSK, 16QAM, 64QAM)
Coding rate (1:6 1:1)
Number of codes (1 15)
CQI (corrected)

75
RN31574EN30GLA0

The mapping between CQI and transport format is hardcoded by 3GPP in
dependence of the UE category
CQI requirements
13 for data rate > 1 Mbit/s
16 for 16QAM
26 for 64QAM
1
136
QPSK
16
3576
16-QAM
176
QPSK
17
4200
16-QAM
232
QPSK
18
4672
16-QAM
320
QPSK
19
5296
16-QAM
376
QPSK
20
5896
16-QAM
464
QPSK
21
6568
16-QAM
648
QPSK
22
7184
16-QAM
792
QPSK
23
9736
16-QAM
928
QPSK
24
11432
16-QAM
10
1264
QPSK
25
14424
10
16-QAM
11
1488
QPSK
26
15776
10
64-QAM
12
1744
QPSK
27
21768
12
64-QAM
13
2288
QPSK
28
26504
13
64-QAM
14
2592
QPSK
29
32264
14
64-QAM
15
3328
QPSK
30
32264
14
64-QAM
-2

76
Mapping CQI transport format

for UE category 13
RN31574EN30GLA0
CQI monitoring reported CQI

WBTS counters M5000C8M5000C38
Number of reports indicating specific CQI
M5000C8 number of reports indicating CQI = 0

Counters consider CQI as reported by UE, not CQI corrected by Node B

77
RN31574EN30GLA0
CQI monitoring reported CQI

Practical example CQI distribution for two cells
QPSK

78
RN31574EN30GLA0
16QAM
64QAM
CQI monitoring compensated CQI

CQI compensation makes it difficult to map reported CQI from UE to
expected HSDPA transport block size
1
136
QPSK
176
QPSK
232
QPSK
320
QPSK
376
QPSK
464
QPSK
648
QPSK
792
QPSK
928
QPSK
10
1264
QPSK
11
1488
QPSK
12
1744
QPSK
13
2288
QPSK
14
2592
QPSK
15
3328
QPSK

79
RN31574EN30GLA0
X = 3 dB
CQIMEASURED = 3
232 bits per TB (116 K)
e.g. HSDPA power
signaled to UE = 37 dBm
e.g. actual HSDPA power

= 40 dBm
X = (40 37) dB = 3 dB
CQICOMPENSATED = 3 + 3 = 6
464 bits per TB (232 K)
CQI monitoring transport format

No counters for compensated CQI available yet
Just WBTS counters for transport format selected by Node B
M5000C49M5000C53 number of packets with 15 codes and QPSK
M5000C54M5000C58 number of packets with 15 codes and 16QAM
M5000C86M5000C95 number of packets with 615 codes and QPSK
M5000C96M5000C105 number of packets with 615 codes and 16QAM

M5000C283 total number of packets with 64QAM (no subdivision in
dependence on number of codes)

80
RN31574EN30GLA0
CQI monitoring transport format

Practical example transport format distribution for two cells
Cell with low CQI

QPSK
Typically 5 codes allocated

Cell with high CQI
Typically 10 codes allocated
16QAM

81
RN31574EN30GLA0
CQI monitoring optimization flow

Low CQI
Low HSDPA
power
Low Ec/Io
Low
RSCP ?

82
High adjacent
cell
interference ?
RN31574EN30GLA0
High R99
traffic ?
Wrong power
settings ?
(next chapter)



83
RN31574EN30GLA0
NetAct tool (Optimiser 2.0)

Adjacency Based Measurements Counters
M1013 Autodef SHO
M1013C0 Number of Intra Frequency SHO attempts
Counter is Updated when SRNC starts a Branch Addition or Branch Replacement procedure.
M1013C1 Number of completed Intra Frequency SHO
Counter is updated when SRNC successfully ends the Branch Addition or Branch Replacement
procedure.
M1014 Autodef IFHO

M1014C0 Number of Inter Frequency HHO attempts
Counter is updated when SRNC starts inter-frequency HHO
M1014C1 Number of completed Inter Frequency HHO
Counter is updated when SRNC successfully ends inter-frequency HHO
M1015 Autodef ISHO
M1015C0 Number of Inter System HHO attempts
Counter is updated when SRNC starts inter-system HHO
M1015C1 Number of completed Inter System HHO
Counter is update when SRNC receives RANAP:IU RELEASE COMMAND from core network after
successful Inter System HHO
84
RN31574EN30GLA0

Adjacency Based Measurements Counters
For each measurements (SHO, IFHO

and ISHO) Statistic show:
# of HO attempts
# of HO completed (successful)
to source and target cell objects
Measurement is carried out in SRNC
HO completion is considered
successful if the SRNC during the
handover decision does not detect
any errors (errors in the source RNC
side or failure messages from
RRC/Iu/Iur/Iub interfaces)
Object identifiers for M1013 and M1014
Source-RNC/Source-CID
Target-RNC/Target-CID
MCC/MNC
Object identifiers for M1015 (ISHO)
Source-RNC/Source-CID
GSM-LAC/GSM-CID
85
RN31574EN30GLA0
MCC/MNC

Automated Adjacency Optimisation for 3G in Optimizer 2.0
Accurate and efficient process for optimizing

operational WCDMA cell adjacencies.
Measurement based optimization
Current adjacency status analysis
Deletion of unused adjacencies
based on KPIs
HO attempts, HO success
Adjacency candidate identification,
activation and measurement
Interfering intra-frequency cells
Cell pair Ec/No difference from WCDMA
Neighbour cell signal strength from GSM
Final adjacency list optimization
Scrambling code re-allocation
Full visibility and control to the user
86
RN31574EN30GLA0

Automated Adjacency Optimisation for 3G in Optimizer 2.0

87
RN31574EN30GLA0

Creating new adjacencies
A fast way to identify missing intra-frequency
adjacencies
Interference measurements colleted from
RNC
New adjacencies can be created based on
that statistics
Rotation method used to achieve the optimal
lists
for other adjacency types
Optimizer creates adjacency candidates
Candidates are downloaded to network and
measured
Statistics collected directly from RNC
Cell pair Ec/No difference
Successful BSIC verifications & BSIC verification
time
Final adjacency list is generated

88
RN31574EN30GLA0

Creating ADJx based on PM data (AutoDef)
Optimizer will show adjacency based SHO amounts for

undefined neighbours. Purpose is to search all ADJS and
ADJG new neighbours which are within certain max distance
Example 1-5 km in urban area and 4-10 km outside urban

area.
After that only those will be selected which have enough
SHO/ISHO attempts.The selected neighbours could be
provisioned straight away to the network

89
RN31574EN30GLA0

How to create Missing ADJx based on PM data-1
1. Select area from the map
and start the ADJ Optimization tool
2. Select ADJG, ADJS and ADJW types

90
RN31574EN30GLA0

3. Select right actions from rules,
common Deletion and
Creation tabs

91
RN31574EN30GLA0

6. Save plan from here with
any name
5. Start from here
4. Purpose is to search all ADJS and ADJG new

neighbours which are within certain max distance like
1-5 km in urban area and 4-10 km outside urban area.
After that only those will be selected which have
enough SHO/ISHO attempts.
92
RN31574EN30GLA0

7. List all new neighbors

93
RN31574EN30GLA0

8. Select the whole week

or one day for PM data analysis
9. Select the right profile to

browser (ADJG, ADJS)
10. Update the list of

Neighbours from here
11. Sort according to
the PM attempts

94
RN31574EN30GLA0

12. See the ADJ on top of the map
13. Provision the selected neighbors to the network
Note ! These neighbors are defined only for one way direction.
See next slides how to make those bi-directionally (Refresh
actual operation with RAC)
95
RN31574EN30GLA0

14. Open the CM data exchange
under the main window
15. Select refresh actual and wait
Until the data is updated
16. Open the adjacency optimization without selecting any

tabs from Deletion or Creation, just to find just created one way ADJx

96
RN31574EN30GLA0

17. Save the plan and list the planned elements
18. You can see now the ADJx neigbours which
can now provisioned to the network

97
RN31574EN30GLA0

Creating ADJx based on DSR measurements (ICSU)
Detected set measurements are not coming from

undefined neighbours (based on ICSU logs)
Aim is to find source of interference
cell having many DSR results but no SHO
attempts (with neighbour list combination list)
Solutions
Add found cell to the neighbour
Down tilt to decrease the interference
DSR measurements are suitable also for ADJG
neighbours

98
RN31574EN30GLA0

Creating ADJx based on DSR measurements (ICSU)
DSR activation
When DSR is not activated, UE monitors only cells in its NCL (either read from
BCCH or sent from RNC in SHO case).
When DSR IS activated, UE scans ALL scrambling codes in same frequency
band and if cells are found that fulfil certain criteria, UE reports this/these
cell(s) as detected cells.
criteria for detection is that UE has to be able to detect if Ec/N0 is greater than
-18 (or -20???) dB
for a DSR to be triggered, detected cell/s must fulfill "normal" HO criteria, i.e.
for example, are within the reported range relative to P-CPICH of strongest AS
cell.
Details of activation :MML command that is sent to RNC that sets some flag
active and RNC orders UE to measure and report. It can be done by HIT
macro, but Optimizer is not (supposed to) using them but same commands
that are in HIT macros are sent directly to RNC.

99
RN31574EN30GLA0
SHO success at RNC border

SHO Success Ratio RNC2 border with RNC3 Data before parameter change

100
RN31574EN30GLA0
SHO success at RNC border

SHO Success Ratio RNC2 border with RNC3 Data after parameter change

101
RN31574EN30GLA0

04 Air Interface Optimization

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

04 Air Interface Optimization

Încărcat de

Drepturi de autor:

Formate disponibile

3G RANOP RU30

Air interface optimization

Soc Classification level

Soc Classification level

Soc Classification level

Air Interface Optimization

Coverage monitoring and enhancement

Soc Classification level

Interference monitoring Ec/Io

Soc Classification level

Interference monitoring little i

Soc Classification level

Interference monitoring pilot pollution

Soc Classification level

Air Interface Optimization

Coverage monitoring and enhancement

Soc Classification level

Ec/Io monitoring RRC messages

serving cell only

whole cell area covered

serving cell only

cell edge (cell update) only

all measured cells

cell edge (SHO) only

all active cells

cell edge (SHO) only

all active cells and better neighbor

cell edge (SHO) only

all active cells

cell edge (HHO) only

all active cells

cell edge (HHO) only

Soc Classification level

Ec/Io monitoring connection request

Soc Classification level

Ec/Io monitoring connection request

Somewhat lower Ec/Io

Number of cells versus median Ec/Io

Ec/Io monitoring connection request

Whole cell area

Number of connection requests versus Ec/Io

Ec/Io monitoring event 1A report

Soc Classification level

Ec/Io monitoring event 1A report

Somewhat lower Ec/Io

HHO Ec/Io Typical

Lower Ec/Io in SHO (cell

Number of cells versus median Ec/Io

Ec/Io monitoring event 1A report

Number of event 1A reports versus Ec/Io

Ec/Io monitoring causes for low quality

Soc Classification level

Air Interface Optimization

Coverage monitoring and enhancement

Soc Classification level

Little I monitoring - requirements

Little I monitoring not supported by NSN counters

Soc Classification level

Little I monitoring role for capacity

Little I = 0.5 throughput = 1100 kbps (about 60% more)

Little I monitoring RRC setup

Somewhat higher little I

Number of cells versus median little i