01 Workshop-3G Optimisation - Sales Cluster

3G Optimisation Workshop
Jan 18, 2013

Atria Hotel and Conference, Tangerang
NOKIA SIEMENS NETWORK
Nokia Siemens Networks
Content
WCDMA Air Interface Basics
Capacity and Coverage Planning overview
Baseband Dimensioning (RU20 vs RU30)
3G Capacity Management
3G RAN KPI & Parameter
Content
WCDMA AIR INTERFACE
3G Network Planning Areas

3G Network Planning could be divided to
Radio Network Planning
Access Transmission Planning
CS core Network Planning
PS Core Network Planning
MGW
3GUEC
RNC
Iu-cs
BTS
Radio Planning
3G-SGSN
Iub,Iur
Iu-ps
Transmission Planning
Gn
Core Planning
Inter-PLMN
Backbone
Network
3G-GGSN
Gn
Data Network
(Internet)
PS Domain
IP
Firewall
UMTS Air Interface technologies

UMTS Air interface is built based on two technological solutions
WCDMA FDD
WCDMA TDD
WCDMA FDD is the more widely used solution
FDD: Separate UL and DL frequency band

WCDMA TDD technology is currently used in limited number of networks
TDD: UL and DL separated by time, utilizing same frequency

Both technologies have own dedicated frequency bands
This course concentrates on design principles of WCDMA FDD solution, basic planning
principles apply to both technologies
5
WCDMA FDD technology

Multiple access technology is wideband CDMA (WCDMA)
All cells at same carrier frequency

Spreading codes used to separate cells and users
Signal bandwidth 3.84 MHz
Multiple carriers can be used to increase capacity
Inter-Frequency functionality to support mobility between frequencies

Compatibility with GSM technology
Inter-System functionality to support mobility between GSM and UMTS
WCDMA Technology
Users share same time and frequency
Frequency
WCDMA Carrier
3 .8 4 M H z
f
5 M H z
5+5 MHz in FDD mode

5 MHz in TDD mode
WCDMA
5 MHz, 1 carrier
TDMA (GSM)
5 MHz, 25 carriers
Direct Sequence (DS) CDMA
Time
UMTS & GSM Network Planning
G S M 9 0 0 /1 8 0 0 :
3 G (W C D M A ):
Differences between WCDMA & GSM

High bit rates
WCDMA
Carrier spacing
Frequency reuse factor
Power control
frequency
Services with
Different quality
requirements
1
1500 Hz
200 kHz
118
2 Hz or lower
Quality control
Radio resource
management algorithms
Network planning
(frequency planning)
Frequency diversity
5 MHz bandwidth gives

multipath diversity with
Rake receiver
Frequency hopping
Packet data
Downlink transmit
diversity
Efficient packet
data
9
5 MHz
GSM
Load-based packet
scheduling
Supported for
improving downlink
capacity
Timeslot based
scheduling with GPRS
Not supported by the
standard, but can be
applied
Multiple WCDMA carriers Layered network

1 - 10 km
F3
F2
F2
F3
200 - 500 m
50 - 100 m
Micro BTS
F3
Pico BTSs
10
F1
Macro BTS
CDMA principle - Chips & Bits & Symbols

Bits (In this drawing, 1 bit = 8 Chips SF=8)
+1
Baseband Data
-1
Chip
Chip
+1
Spreading Code
-1
+1
Spread Signal
-1
Air Interface
g
n
i
d
a
e
r
p
Des
+1
-1
+1
Data
11
-1
Energy Box
Received Bit
Fr
eq
ue
nc
y
Ba
nd
Power/Hz
Originating Bit
Energy per bit = Eb = const
Duration
(t = 1/Rb)
Higher spreading factor Wider frequency band Lower power spectral density
BUT
Same Energy per Bit
12
Power density (Watts/Hz)
Spreading & Processing Gain

User bit
rate
Unspread narrowband signal
Spread wideband signal
Frequency
Bandwidth W (3.84 Mchip/sec)
W const 3.84 Mchip

Processing gain:
13
W
G p dB
R
sec
Processing Gain Examples

Voice user (R=12,2 kbit/s)
Power density
(W/Hz)
Gp=W/R=24.98
dB
Spreading sequences
have a different length
Processing gain depends
on the user data rate
Frequency (Hz)
Packet data user (R=384 kbit/s)
Power density
(W/Hz)
14
Gp=W/R=10 dB
Frequency (Hz)
Transmission Power
Power density
Frequency
High bit rate user
5MHz
Low bit rate user

Time
15
Characteristic to WCDMA
RAKE receiver takes advantage of multipath propagation
Fast power control keeps system stable by using minimum power necessary for links
Soft handover ensures smooth handovers, reduced probability of dropped calls
Multiservice Environment
Data speed
In R99 bit rate varies from 8 kbps up to 384 kbps
Variable bit rate also available
Bit rate gradually grows up to 21 Mbps (RU20)
Service delivery type

Real-time (RT) & non real-time (NRT)
Quality classes for user to choose

Different error rates and delays
Traffic asymmetric in uplink & downlink

Common channel data traffic
Inter-system handovers
16
Air Interface
Capacity and coverage coupled cell breathing
Neighbour cells coupled via
interference
Soft handover
Fast power control
Interference limited system (e.g.
GSM frequency limited)
RAKE Receiver
Cell-1
Rx
Finger
Rx
Finger
Rx
Finger
Rx
Finger
Cell-1
Cell-1
Delay 3
Code used
for the
connection
Delay 2
Delay 1
Cell-2
Combination or multipath components and in DL also signals from different cells

17
Output
Power Control in WCDMA

Fast power control is vital for WCDMA performance. It aims UE to control the transmitted
power on the same level with received power. This leads to minimised interference and
small power consumption
Power is controlled by parameters and needs to be defined during network optimisation
UE3
UE1
UE2
19
UE1
With Optimum
Power Control
UE2
UE3
UE4
Received power at BS
UE4
Received power at BS
Without
Power Control
UE1
UE2
UE3
UE4
Effect on Tx & Rx Power on Interference Levels
Downlink transmission power =

Interference to the network
Uplink transmission power =

Interference to other cells
Uplink received power = Interference to

own cell users
Since every Tx and Rx power is causing interference to others, PC is

necessary to limit the interference
20
Handovers in WCDMA
Hard handover: UE handover between different frequencies or between WCDMA and GSM
Soft handover: UE handover between different base stations
Softer handover: UE handover within one base station but between different sectors
Soft handover keeps simultaneous connection to different base stations thus providing a way to improve call
quality during handover. (SHO gain)
Soft handover feature has a direct impact on network capacity and therefore is a trade-off between quality and
capacity. It has also an effect to coverage due cell breathing. (SHO overhead)
Received signal strength

Base station
BS1
Diversity (SHO gain)
BS1
Threshold
BS2
BS2
BS3
BS3
21
Distance from BS1
Soft/softer handover
UE is simultaneously connected to 2 to 3 cells during soft handover
Soft handover is performed based on UE cell pilot power measurements and handover
thresholds set by radio network planning parameters
Received signal strength
Radio link performance is improved during soft handover

Soft handover consumes base station and transmission resources
BS1
Soft handover
Threshold
BS2
BS2
BS3
Distance from BS1

22
BS1
BS3
Hard handover
Hard handovers are typically performed between WCDMA frequencies and
between WCDMA and GSM cells
GSM/GPRS
GSM/GPRS
GSM/GPRS
GSM/GPRS
Inter-System handovers (ISHO)
f1f
f1f
Inter-Frequency handovers (IFHO)
f2f
23
f2f
f2f
f2f
Other to own cell interference little i (1/2)

Low other to own cell interference can be achieved by planning clear dominance areas:
The cell coverage (and overlap) must be well
controlled
The cell should cover only what it is supposed to cover
Low(er) antenna hights and down tilt of the antennas
Use buildings and other environmental structures to isolate cells' coverage
Use indoor solutions to take advantage of in building isolation
Avoid sites "seeing" the buildings in especially horizon especially over the water or
area
> 3 km
24
< 300 m
otherwise open
Other to own cell interference-little i (2/2)

The DL load equation dictates the maximum capacity
DL
nk
n 1
Eb / No n
1 n i v n
W / Rn
Basically the other to own cell interference (i ) tells how much there is overlapping
between cells.
Some overlapping is needed in order to guarantee safe handovers BUT excessive
overlapping must be avoided
25
WCDMA Codes
In WCDMA two separate codes are used in the spreading operation
Channelisation code
Scrambling code
Channelisation code
DL: separates physical channels of different users and common

channels, defines physical channel bit rate
UL: separates physical channels of one user, defines physical channel bit
rate
Scrambling code
DL: separates cells in same carrier frequency

UL: separates users
26
DL Spreading and Multiplexing in WCDMA

Radio frame = 15 time slots
CHANNELISATION codes:
Pilot
CODE 1
Pilot
BCCH
P-CPICH
User 1
CODE 2
BCCH
User 2
P-CCPCH
User 3
SUM
CODE 3
User 1
DPCH1
CODE 4
User 2
DPCH2
Time
3.84 MHz
RF carrier
SCRAMBLING
CODE
CODE 5
User 3
DPCH3
3.84 MHz bandwidth
27
RF
DL & UL Channelisation Codes

Walsh-Hadamard codes: orthogonal variable spreading factor codes (OVSF codes)
SF for the DL transmission in FDD mode = {4, 8, 16, 32, 64, 128, 256, 512}
SF for the UL transmission in FDD mode = {4, 8, 16, 32, 64, 128, 256}
Good orthogonality properties: cross correlation value for each code pair in the code set
equals 0
In theoretical environment users of one cell do not interfere each other in DL
In practical multipath environment orthogonality is partly lost Interference between users of
same cell
Orthogonal codes are suited for channel separation, where synchronisation between
different channels can be guaranteed
Downlink channels under one cell
Uplink channels from a single user
Orthogonal codes have bad auto correlation properties and thus not suited in an
asynchronous environment
Scrambling code required to separate signals between cells in DL and users in UL
28
Channelisation Code Tree

SF=1
SF=2
SF=4
SF=8
C8(0)=[11111111]
C8(1)=[1111-1-1-1-1]
C2(0)=[11]
C8(2)=[11-1-111-1-1]
C4(1)=[11-1-1]
C8(3)=[11-1-1-1-111]
C8(0)=[1-11-11-11-1]
C4(2)=[1-11-1]
C2(1)=[1-1]
C16(0)=[..........
..]
C (1)=[..........
16
C4(0)=[1111]
C0(0)=[1
]
SF=16
C8(5)=[1-11-1-11-11]
..]
C16(2)=[..........
..]
C16(3)=[..........
..]
C16(4)=[..........
..]
C16(5)=[..........
..]
C16(6)=[..........
..]
C16(7)=[..........
..]
C16(8)=[..........
..]
C16(9)=[..........
..]
C16(10)=[..........
.]
C16(11)=[...........]
C16(12)=[........
C8(6)=[1-1-111-1-11] ...]
C16(13=[..........
C4(3)=[1-1-11]
.]
C16(14)=[........
C8(7)=[1-1-11-111-1] ...]
C16(15)=[........
...]
29
...
SF=256 SF=512
Physical Layer Bit Rates (DL)

Spreading
factor
512
256
128
64
32
16
8
4
4, with 3
parallel
codes
Channel
symbol
rate
(ksps)
7.5
15
30
60
120
240
480
960
2880
RSymbol
30
Channel bit
rate
(kbps)
15
30
60
120
240
480
960
1920
5760
SF
DPDCH
channel bit
rate range
(kbps)
36
1224
4251
90
210
432
912
1872
5616
Maximum user
data rate with rate coding
(approx.)
13 kbps
612 kbps
2024 kbps
45 kbps
105 kbps
215 kbps
456 kbps
936 kbps
2.3 Mbps
Rb _ phy 2 RSymbol
(QPSK modulation)
Half rate speech

Full rate speech
128 kbps
384 kbps
2 Mbps
Physical Layer Bit Rates (DL) - HSDPA

3GPP Release 5 standards introduced enhanced DL bit rates with High Speed Downlink
Packet Access (HSDPA) technology
Shared high bit rate channel between users High peak bit rates
Simultaneous usage of up to 15 DL channelisation codes (In HSDPA
SF=16)
Higher order
modulation scheme (16-QAM) Higher bit rate in same
HSDPA
band
Coding
55codes
10
15
Codingrate
rate Coding
Codingrate
rate
codes
10codes
codes
15codes
codes
16-QAM provides 4 bits per symbol
kbit/s
/ code physical
channel1.8
peak
rate
1/4 960600
kbps
1.2 Mbps
Mbps
QPSK
QPSK
16QAM
16QAM
31
1/4
600 kbps
1.2 Mbps
1.8 Mbps
2/4
2/4
1.2
1.2Mbps
Mbps
2.4
2.4Mbps
Mbps
3.6
3.6Mbps
Mbps
3/4
3/4
1.8
1.8Mbps
Mbps
3.6
3.6Mbps
Mbps
5.4
5.4Mbps
Mbps
2/4
2/4
2.4
2.4Mbps
Mbps
4.8
4.8Mbps
Mbps
7.2
7.2Mbps
Mbps
3/4
3/4
3.6
3.6Mbps
Mbps
7.2
7.2Mbps
Mbps
10.7
10.7Mbps
Mbps
4/4
4/4
4.8
4.8Mbps
Mbps
9.6
9.6Mbps
Mbps
14.4
14.4Mbps
Mbps
Physical Layer Bit Rates (UL) - HSUPA

3GPP Release 6 standards introduced enhanced UL bit rates with High Speed Downlink
Packet Access (HSUPA) technology
Fast allocation of available UL capacity for users High peak bit rates
Simultaneous usage of up to 2+2 UL channelisation codes (In HSUPA
SF=2 4)
32
Coding
Codingrate
rate
1/2
1/2
11xxSF4
SF4
480
480kbps
kbps
22xxSF4
SF4
960
960kbps
kbps
22xxSF2
SF2
1.92
1.92Mbps
Mbps
3/4
3/4
4/4
4/4
720
720kbps
kbps
960
960kbps
kbps
1.46
1.46Mbps
Mbps
1.92
1.92Mbps
Mbps
2.88
2.88Mbps
Mbps
3.84
3.84Mbps
Mbps
22xxSF2
SF2++
22xxSF4
SF4
2.88
2.88Mbps
Mbps
4.32
4.32Mbps
Mbps
5.76
5.76Mbps
Mbps
Content
COVERAGE & CAPACITY PLANNING
33
Coverage Planning Uplink Link budget

Uplink
Uplink- From UE to BTS
RX
RXRX
RX RX
RXRX
RX RX
RXRX
RX
EbNo values with diversity

MHA assumed to negate cable loss in UL.
Allowed propagation loss
34
153.7
151.9
When load increase for 50% to 80%

=>cell breathing effect
Coverage Planning Downlink Link budget
DL EbNo without diversity
35
WCDMA Uplink Load Equation

Complete version of the uplink load equation is:
UL
jN
1 a * i
W
j 1 1
Eb / No j . R j . j
Where,
N, is the number of simultaneously active users
W, is the chip rate i.e. 3.84 Mcps
Rj, is the L2 user bit rate e.g. 12.2 kbps
Eb/Noj is the Eb/No requirement for the jth user e.g. 4.4 dB for speech
j is the activity factor for the jth user e.g. 0.67 for speech (includes DPCCH overhead)
a, is the rise in uplink inter-cell interference ratio e.g. 0.7 dB
i, is the uplink inter-cell interference ratio e.g. 0.65 (for 3-sectorised Macro)
36
Capacity calculation example-Uplink

From UL load equation we can calculate load caused by one single 12.2
speech user.
UL
1
3840000
1
10
4.4
10
*12200 * 0.67
1 10
1.3
10
* 0.65 1.09%
UL EbNo= 4.4 dB with Rx diversity,

8.0 dB without Rx diversity
i=65 %,
tx power rise=1.3
Activity factor=0.67
Load caused by one
single speech user
If the cell has been planned with a maximum permissible uplink load of 80 % then its uplink
capacity is 73 simultaneous speech users
Without Uplink Rx diversity, Load caused by one single speech user is 2.49 % Assuming same
80% UL load then Uplink capacity without diversity is 32 simultaneous speech users
37
WCDMA Downlink Load Equation

The downlink load equation is:
jN
Eb / No j
j 1
W / Rj
DL (1 SHOOH ) j
Where,
1 i

, is the downlink orthogonality e.g. 0.5 (50%)
i, is the uplink inter-cell interference ratio e.g. 0.65 (65% for sectorised Macrocell)
SHOOH, is the soft handover overhead e.g. 0.2
38
Total Downlink Transmit Power (1/2)

The total traffic channel transmit power requirement can be expressed as:
jN
PBS
Eb / No j
N o L (1 SHOOH ) j
1/ Rj
j 1
Where,
1 DL

Capacity of the cell
No is the background noise spectral density
L is the average path loss between the UEs and Node Bs antenna connectors
L = IPL (Antenna Gains Cable Loss Body Loss + SHO Gain) IPL Correction Factor
39
Example Total Downlink Transmit Power (2/2)

The total downlink transmit power is now obtained by adding the power requirement of
the common channels.
The common channels include:
P-CPICH (100 % activity)
P-SCH (10 % activity)
S-CCPCH (up to 100 % activity)

PICH (96 % activity)
S-SCH (10 % activity)
AICH (up to 80 % activity)
P-CCPCH (90 % activity)
It can be assumed that the common channels consume 20 % of the total downlink
transmit power i.e. 20 W x 0.2 = 4 W/ 40Wx0.2=8W
40
Capacity Calculation Example - DL

In Downlink, the calculation is done for 12.2 speech user and 128 kbps data users
separately.
Result:
AMR, Number of supported AMR calls in DL is 56.
128 kbps data: Number of supported calls is 7, limiting
factor is DL load which is reached before BTS max. power
Users are added as long as either 80% load or BTS max

power (43 dbm/20W) is reached
From UL link budget with 80 % of load

With RU20 SW, 1 FSME card has 612 channel element. 56 AMR call
requires 56 CH => 1 FSME is required
41
Hardware Channel Requirements

Hardware channel requirement per traffic channel is a function of bit rate
Baseband resources per one Rel99 traffic
channel for SM Rel. 1
Baseband resources per one Rel99

traffic channel for SM Rel. 2
The higher of the DL and UL bit rates is used e.g. the 384/384 kbps
data service requires 12 (RU20) or 8 (RU30) hardware channels
Hardware channels are pooled across a WBTS creating a trunking gain
between cells
42
Less CE required in
DL and UL for PS 256
and PS 384
Number of simultaneous users per

cell
Relation between Loading and Capacity

SINGLE
FREQUENCY
CHANNEL
SINGLE CELL
70,0
60,0
50,0
40,0
UL loading 30%
UL loading 50%
UL loading 70%
30,0
20,0
10,0
0,0
Voice
CS 64
kbit/s
PS 64
kbit/s
PS 128
kbit/s
Higher loading means higher

capacity
50% loading: Capacity ~50Erl/800
kbit/s per cell
43
PS 384
kbit/s
64 kbit/s Coverage & Capacity in Macrocells

Max. path loss [dB]
180
175
170
WCDMA downlink 20W
165
160
WCDMA uplink
155
150
100
200
300
400
500
Limit is UL
coverage
44
600
700
800 900 1000 1100 1200
Limit is DL
capacity
Load [kbps]
Capacity in Macro vs. Micro Environments

Packet data throughput, calculated with CDMA capacity formulas
Assumptions
Micro cell:
higher orthogonality
Micro: higher
isolation between cells
Results
Multipath diversity gain

is smaller
within Micro environment
Downlink capacity is more sensitive to the environment because of orthogonal codes (other cell
interference affects more downlink)
Micro cells provide a higher capacity due to less multipath=> better Orthogonality
45
Coverage Improvement Alternatives

Mast head amplifier
basic solution for optimized uplink performance
compensates feeder cable loss
supported by NSN's base stations
can be used together with Smart Radio Concept
6 sectored site
utilizing narrowbeam antennas
~ 2 dB better antenna gain than in 3 sectored site
46
Capacity Improvement Alternatives

6 sectored site
~ 80% capacity gain compared to 3 sectors
(not 100% due to inter-sector interference)
More carriers (frequencies) per sector
doubling the amount of carriers with power
splitting gives roughly 60% more capacity
Increasing BTS power 20W 40W 60W
Dedicated Indoor & Microcells to traffic hot spots to free
capacity from macro layer
47
Content
RAN DIMENSIONING
49
BaseBand Dimensioning
Site
configuration
(# of carriers,
cell range)
Common
Control
Channels
Traffic Demand
Changed in RU30
using HSPA
Processing Set
R99
HSDPA
BaseBand requirements (#CE, CE licenses)
50
HSUPA
Active users
System Module Capacity in RU20

SM Rel. 1
SM Rel. 2
180
FSMB
3 sub modules, each
having 80 CE
Total 240 CE for traffic use
SM Rel. 2
180
FSMC
One sub module, which has
180 CE capacity for traffic use
SM Rel. 2
216
FSMD
Two sub module, which has
396 CE capacity for traffic use
180
216
FSME
Three sub module, which has 612 CE
capacity for traffic use
The available CE in RU20 was used both by R99 and HSPA

51
216
System Module Capacity in RU30

SM Rel. 1
FSMB
3 sub modules, each
having 80 CE
Total 240 CE for traffic
use
52
SM Rel. 2
FSMC
Has 5 sub unit
(240 CE)
SM Rel. 2
FSMD
Has 12 sub unit
(576 CE)
SM Rel. 2
FSME
Has 19 sub unit
(912 CE)
One available sub unit provides 48 CE for R99
General Baseband Dimensioning Rules in RU30
In RU30 System Module Rel2 capacity is INCREASED compared to RU10/RU20

In RU30, System Module Rel1 capacity and calculation is SAME as RU10/RU20
HSPA dimensioning approach changes in comparison to RU10/RU20

BTS processing steps are introduced (HSPA does NOT consume CE licenses any more NO scheduler pools any
longer)
HSDPA/HSUPA performance (throughputs, number of active users) improvement
53
Rel99 CE Requirement
Baseband resources per one Rel99 traffic channel for SM Rel. 2
Flexi Radio SM Rel. 2 : FSMC, FSMD, FSME

Baseband resources for SM Rel.1 (FSMB) and Ultrasite is still same as RU20
54
3G BTS Baseband Dimensioning Delta

- System
Module FSMD/E
System Module consists of certain number of baseband cards i.e. submodules
FSMD: 2 submodules
FSME: 3 submodules
Submodule
Each submodule consists of certain number of processing subunits

Each subunit can provide:
Rel99 processing resources (Rel99 CEs)
HSDPA processing resources (HSDPA users and throughput)
HSUPA processing resources (HSUPA users and throughput)
CCCH processing (e.g. extended cell case)
Interference cancellation processing (PIC)
55
Subunits
FSME

RU30 HSPA Processing Set
HSDPA processing set
MAX. number of
HSDPA
users per BTS
MAX. HSDPA throughput per

BTS
HSDPA BTS processing set 1

(PS 1)
up to 32
up to 7,2 Mbps

(PS 2)
up to 72
up to 21 Mbps

(PS 3)
up to 72
up to 84 Mbps
BB capacity
2 HSUPA resource steps (1/2 subunit)
56
Max number of HSUPA users
up to 24
Max HSUPA throughput
up to 5,8 Mbps

RU30 BTS Sub Unit Calculation
System Module Rel99 CE capacity = Min (#Rel99_CE_license; Rel99_CE_Subunit_capacity *
(Number_of_subunits roundup (Number of cells / 3) HSDPA_subunits HSUPA_subunits)
HSDPA _subunits = Max ( (Round up ((2 * MIMO_cells + non-MIMO_cells) / 6) + 1) ;
subunits_for_HSDPA_throughput ) + Number_of_LCGs * 0,25
Where
Number_of_subunits:
- FSMD = 13
-
FSME = 20
Rel99_CE_Subunit_capacity = 48
57

RU30 BTS Sub Unit Calculation for HSUPA
Baseband minimum decoding capacity
[Mbps]
Minimum
number of NRT
HSUPA UEs per
scheduler
0
1 - 24
25 - 48
49 - 72
73 - 96
97 - 120
121 - 144
145 - 168
169 - 192
193 - 216
217 - 240
241 - 264
265 - 288
289 - 312
313 - 336
337 - 360
361- 384
385 - 408
409 - 432
433- 456
457 - 480
58
2,8 5,8 11,6 17,4 23,2 29,0 34,8 40,6 46,4 52,2 58,0 63,8 69,6 75,4 81,2 87,0 92,8 98,6 104,4 110,2
116,0
0,5
0.5
1,5
2.5
3.5
4.5
5.5
6.5
7.5
8.5
9.5
10
1,5
2.5
3.5
4.5
5.5
6.5
7.5
8.5
9.5
10
1,5
1,5
1,5
1,5
2.5
3.5
4.5
5.5
6.5
7.5
8.5
9.5
10
2.5
3.5
4.5
5.5
6.5
7.5
8.5
9.5
10
2.5
2.5
2.5
2.5
2.5
2.5
3.5
4.5
5.5
6.5
7.5
8.5
9.5
10
3.5
4.5
5.5
6.5
7.5
8.5
9.5
10
3.5
3.5
3.5
3.5
3.5
3.5
3.5
3.5
4.5
5.5
6.5
7.5
8.5
9.5
10
4.5
5.5
6.5
7.5
8.5
9.5
10
4.5
4.5
4.5
4.5
4.5
4.5
4.5
4.5
4.5
4.5
5.5
6.5
7.5
8.5
9.5
10
5.5
6.5
7.5
8.5
9.5
10
5.5
5.5
5.5
5.5
5.5
5.5
5.5
5.5
5.5
5.5
5.5
5.5
6.5
7.5
8.5
9.5
10
6.5
7.5
8.5
9.5
10
6.5
6.5
6.5
6.5
6.5
6.5
6.5
6.5
6.5
6.5
6.5
6.5
6.5
6.5
7.5
8.5
9.5
10
7.5
8.5
9.5
10
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
7.5
8.5
9.5
10
8.5
9.5
10
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
8.5
9.5
10
9.5
10
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
9.5
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10

RU30 Baseband Capacity Improvement Case Study
Mapping from RU20 to RU30 with the same configuration
RU20
RU30
HSUPA RU20 RU30 Dimens ioning
RU20 calculation :
Required # CE for HSDPA : # of shared scheduler * 72 CE (72 CE reserved for @ shared scheduler).
Required # CE for HSUPA : please refer to the ppt attached. HSUPA resources are allocated in steps of CE.
RU30 calculation :
Required # subunit for CCCH : roundup (#of cells/3)
Required # subunit for HSDPA : Max ( (Round up ((2 * MIMO_cells + non-MIMO_cells) / 6) + 1) ;
subunits_for_HSDPA_throughput ) + Number_of_LCGs * 0,25
Required # subunit for HSUPA : please refer to the previous slide.
59
In RU30, 1 FSME
contains 912 Rel99 CEs
RU30 gains 30% more CE
capacity through HSPA
efficiency compare to
RU20
Upgradeable to 1548 CE
without additional system
module
Content
3G CAPACITY MANAGEMENT
60
1. DL Power Load
Solution for High DL Load (Marginal Load > 2%)
1.
2.
3.
4.
5.
6.
7.
61
Check traffic, there was possibility of HW

issue or installation problem if traffic is low
Check power related parameter related, nonHSPA power (e.g PtxTarget, PtxOffset)
Check SHO overhead > 150% (cells covers
to big area or to many overlapped area)
SHO optimization
Check PRACH delay to see whether there
was overshoot problem
Check compressed mode threshold for IRAT &
IFHO. To many CM will consume a lot of
power
Capacity optimization e.g reduce initial bit
rate, reduce minimum radio link power etc
Capacity upgrade
Proactive Monitoring DL Power

Proactive Monitoring of DL Power
62
Proactive Monitoring of DL Power while HSDPA is active
Reactive Monitoring DL Power

Reactive Monitoring of DL Power
63
2. RTWP
Solution for High RTWP

1.
2.
3.
4.
5.
64
If High RTWP, Low noise rise and low

traffic voice, UL PS and HSUPA
Check antenna/feeder installation
Check attenuation setting
If High RTWP, High noise rise and low
traffic voice, UL PS and HSUPA
Suspected : External interference
If High RTWP, High noise rise and low
traffic voice, high UL PS
Activate HSUPA
Decrease initial bit rate for UL
Disable PS 384
Optimization Tuning e.g Limiting UL rate
for SHO HSUPA (if HSUPA is active),
Power control tuning eg. Lowering initial
SIRTarget etc
Capacity upgrade If High RTWP, High
noise rise and High traffic
Split cell, Propose 2nd carrier
Proactive/Reactive Monitoring RTWP

Proactive Monitoring : RTWP
Reactive Monitoring : RTWP
UL Load
Optimis ation Recommendation
65
3. Common Channel Load

3.1 Paging Channel (PCH) Load
PCH throughput & load in case of 8 kbps PCH :
Solution for High PCH Load

1.
2.
3.
4.
Enabling 24 kbps PCH if high paging load occured at cell level (+ 2nd S-CCPCH)
DRX Cycle Length change from 1280ms to 640ms
Activation of CELL_PCH, more paging on cell level instead of LAC wide paging
LAC splitting is needed to reduce the Paging Load if high paging load was distributed evenly in all cells under the LAC. LAC
split methodology is based on the number of BH MTCs: the target is to balance BH MTC on hour level
24kbps Paging
66
3.2 S-CCPCH & FACH Load

S-CCPCH will carry PCH & FACH
There can be up to three SCCPCH channels configured in the cell.
S-CCPCH load (%) : RNC_979a S-CCPCH average load

FACH Load (%)
Solution for High S-CCPCH & FACH Load

1.
2.
3.
4.
5.
67
Increasing the number of available SCCPCHs if there was high FACH load
Evaluating whether there is excessive user plane data transfer within the CELL_FACH. If so, consider reducing the RLC buffer
thresholds that trigger the transition to CELL_DCH.
Evaluating whether there is a high level of signaling generated by cell, URA, location area, or routing area updates. If so,
consider adjusting the area boundaries or reducing the size of the location and routing areas.
Activation the 24 kbps Paging Channel feature if the PCH is loaded.
Upgrading the Node B configuration with an additional carrier
3.3 Random Access (RACH) Load
Random access channel load can be measured at RACH preamble

RACH-u capacity is defined by message size 360 bits and number of message per 10 ms (Parameter : RACH_parameter.
Default:2) = 360 bit/TB *1/10ms *2= 72 kbps
RACH-c capacity is defined by message size 168 bits and number of message per 10 ms (Parameter : RACH_parameter.
Default:2) = 168 bit/TB *1/10ms *2= 33.6 kbps
RACH Load
Solution for High RACH Load

1. Increasing RACH capacity parameter
Increasing the number of available PRACH preamble signatures
Increasing the number of available PRACH access slots
Increasing the number of available PRACH

2. Evaluate the counter PRACH delay to see whether overshoot coverage.
3. Evaluate whether or not there are large quantities of signalling generated by cell, URA, location area or routing area updates. If so,
consider adjusting the area boundaries.
4. Evaluate whether or not there is excessive user plane data transfer within CELL_FACH. If so, consider reducing the RLC buffer
thresholds that trigger the transition to CELL_DCH.
5. Upgrading the Node B configuration in terms of an additional carrier
68
Code Tree Monitoring

Code Tree Monitoring
RNC_520b KPI can be used as triggerig point to upgrade (second carrier).

The max code tree occupancy ranges from 35% up to 100%.
When max code occupancy is less than 80%, the code allocation failure rate still remains close to 0% and
roughly <90% max code occupancy means that code allocation failure rate is <1%.
Max code tree occupancy limit : 85 90%
Solution
Propose 2nd Carrier Activation.
69
Content
3G RAN KPI
70
3G RAN KPI
Accessibility
Call Setup Success Rate
HSDPA Accessibility
Retainability
Call Completion Rate
HSDPA Retainability
Mobility
SHO SR
IHSO SR
71
ACCESSIBILITY Call Setup Success Rate (CSSR)

FORMULA
CSSR KPI for CS voice
100 * ( sum( MOC _ CONV _ CALL _ ATTS MOC _ CONV _ CALL _ FAILS
MTC _ CONV _ CALL _ ATTS MTC _ CONV _ CALL _ FAILS
AMR _ CSSR
EMERGENCY _ CALL _ ATTS EMERGENCY _ CALL _ FAILS )

sum( MOC _ CONV _ CALL _ ATTS MTC _ CONV _ CALL _ ATTS
( sum( RAB _ ACC _ COMP _ CS _ VOICE )

sum( RAB _ STP _ ATT _ CS _ VOICE ))
EMERGENCY _ CALL _ ATTS RRC _ ATT _ REP _ MO _ CONV

RRC _ ATT _ REP _ MT _ CONV RRC _ ATT _ REP _ EMERGENCY )
RRC part
RAB part
CSSR KPI for PS NRT

100 * ( sum( MOC _ INTER _ CALL _ ATTS MOC _ INTER _ CALL _ FAILS
MOC _ BACKG _ CALL _ ATTS MOC _ BACKG _ CALL _ FAILS
MTC _ INTER _ CALL _ ATTS MTC _ INTER _ CALL _ FAILS
( sum( RAB _ ACC _ COMP _ PS _ INTER
MTC _ BACKG _ CALL _ ATTS MTC _ BACKG _ CALL _ FAILS )
RAB _ ACC _ COMP _ PS _ BACKG )
PS _ CSSR
*
sum( MOC _ INTER _ CALL _ ATTS MOC _ BACKG _ CALL _ ATTS
sum( RAB _ STP _ ATT _ PS _ INTER
MTC _ INTER _ CALL _ ATTS MTC _ BACKG _ CALL _ ATTS
RRC _ ATT _ REP _ INTER RRC _ ATT _ REP _ MO _ INTER
RRC _ ATT _ REP _ MO _ BACKG RRC _ ATT _ REP _ MT _ BACKG )
RAB _ STP _ ATT _ PS _ BACKG ))
RAB part
RRC part
72

Definition of Call Set-Up Success Rate (CSSR)
UE
RRC: Connection Request
RNC
BTS
CN
RRC Connection Setup phase

Resource Reservation in RNC, BTS, Transmission
RRC: RRC Connection Request Setup
RRC
RRC Connection Access phase

RNC waits reply from UE
RRC: RRC Connection Completed

RRC: Initial Direct Transfer cm service request
DIRECT TRANSFER (Call
Proceeding)
RANAP: Initial UE Message
RAB Connection Setup phase
RANAP: RAB Assignment

Request
Resource Reservation in RNC, BTS, Transmission
RRC: Radio Bearer Setup
RAB Connection Access phase
RAB
RNC waits reply from UE
RRC: Radio Bearer Setup

Complete
DIRECT TRANSFER (Alerting)
DIRECT TRANSFER (Connect)
DIRECT TRANSFER (Connect
Acknowledge)
73
RANAP: RAB Assignment

Response
Call Setup
Success
Rate
Call Setup Time

Failure analysis for low CSSR cells
RRC, RAB, HSPA Setup
Performance KPI/counters
Follow-Up
RRC, RAB Setup, PS
Setup Failure due AC
Yes
Air Interface
No
RRC, RAB Setup, PS
Setup Failure due
BTS
Yes
BTS
No
RRC, RAB Setup, PS
Setup Failure due Iub
Yes
Iub
No
RRC, RAB Setup, PS Setup
Failure due RNC, DMCU
Yes
RNC
No
RRC, RAB Setup failure due
to Frozen BTS
74
Yes
High Traffic Event

RRC Connection & Access Analysis
RRC_CONN_STP_FAIL_AC
Check UL Interference (R99 Noise Rise, RTWP), DL Power (HSDPA, R99 power) if
there is need to upgrade radio capacity
RRC_CONN_STP_FAIL_BTS
Check BTS configuration in terms of WAM and CE allocation Use Channel Element
(M5001) Counters in order to evaluate lack of Channel Elements
Evaluate NBAP counters (radio link reconfiguration failures) and KPIs for
troubleshooting BTS resources
Expand the Capacity or decrease the traffic offered to the site
RRC_CONN_STP_FAIL_TRANS
Evaluate Number of reconfiguration failure due the transmission
Expand the capacity or decrease the traffic offered to the site
Check COCO Configuration
RRC_CONN_STP_FAIL_RNC
Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)
DMPG problem in RNC
75

RRC Connection & Access Analysis
RRC_CONN_STP_FAIL_ICSU_OVERL
ICSU overload
RRC_CONN_STP_FAIL_RNTI ALLO FAIL
RNC decides to reject RRC connection request due to RNTI allocation failure caused by
RRMU overload
RRC_CONN_ACC_FAIL_RADIO
Perform drive test to detect if UL or DL coverage.
UL Coverage Tune Cell Dominance if the cause is UL interference
DL Coverage Tune SCCPCH Power if UE does not receive the RRC Setup Message
If UE does not synchronize tune CPICHToRefRABOffset
RRC_CONN_ACC_FAIL_MS
UL Coverage Tune Cell Dominance (or CPICH) in order to balance UL and DL (if UL
interference is not the cause)
76

Example: RRC Setup Failure Distribution
BTS failures dominant failure
cause here
77

RAB setup & Access Analysis
RAB_STP_FAIL_XXX_AC
Admission control could reject establishment of new Connection/bearer due to UL/DL
Power, etc
RAB_STP_FAIL_XXX_BTS
Check BTS configuration in terms of WAM and CE allocation Use Channel Element
(M5001) Counters in order to evaluate lack of Channel Elements
Evaluate NBAP counters (radio link reconfiguration failures) and KPIs for
troubleshooting BTS resources
Expand the Capacity or decrease the traffic offered to the site
RAB_STP_FAIL_XXX_TRANS
Evaluate Number of reconfiguration failure due the transmission
Check COCO Configuration & IP Route Parameter
78

RAB setup & Access Analysis
RAB_ACC_FAIL_XXX_MS
Evaluate cell resources TCP & RTWP
RAB_ACC_FAIL_XXX_RNC
Typically RNC Fault or incoming SRNC relocation failure
79

Example: RAB setup failure distribution - Voice
Failures due AC, RNC, TRANS and

BTS can be seen
80
ACCESSIBILITY HSDPA Accessibility

Formula
RNC _ 605a
M1002C385 ALLO_HS_DSCH_FLOW_INT M1002C389 ALLO_HS_DSCH_FLOW_BGR

M1002C385 ALLO_HS_DSCH_FLOW_INT M1002C389 ALLO_HS_DSCH_FLOW_BGR
M1002C475 DCH_SEL_MAX_HSDPA_US ERS_INT M1002C476 DCH_SEL_MAX_HSDPA_US ERS_BGR
M1002C401 REJ_HS_DSCH_RET_INT M1002C402 REJ_HS_DSC H_RET_BGR
M1002C413 SETUP_FAIL_RNC_HS_DSCH_INT M1002C415 SETUP_FAIL_UE_HS_DSCH_INT
M1002C416 SETUP_FAIL_BTS_HS_DSCH_INT M1002C417 SETUP_FAIL_IUB_HS_TOTAL_INT
M1002C421 SETUP_FAIL_RNC_HS_DSCH_BGR M1002C423 SETUP_FAIL_UE_HS_DSCH_BGR
M1002C424 SETUP_FAIL_BTS_HS_DSCH_BGR M 1002C425 SETUP_FAIL_IUB_HS_TOTAL_BGR
RNC_605a, HSDPA Accessibility for NRT traffic from user point of view
The accessibility of all started allocations for HS-DSCH for NRT Traffic from user
point of view
The number of times when HS-DSCH channel has been established divided by the
number of times when HS-DSCH channel has been selected by cell specific PS
Also the times that HS-DSCH channel selection fails due to UE and the times the
HS_DSCH would have been selected but the number of possible HS-DSCH users
were exceeded are included in the formula
81
100%

HSDPA Accessibility Analysis
Identify root cause of failure distribution and main failure contributor
1. HSDPA Access Failure _too many HSDPA users
Check simultaneous HSDPA users
DCH selected due to too many HSDPA users, RNC_660b
Upgrade HSDPA scheduler
Increase Max User per cell (16>48 > 64 > 72)

2. If high HSDPA Access Failures_UL DCH (RNC_661c/d)
Rejected HS-DSCH return channel due to lack of UL radio resources
Monitor UL load
UL Load optimisation (reduce RRM UL DCH activity factor
3. If high HSDPA Access Failure_UE
Check RB reconfiguration failure rate
ICSU log for UE types troubleshooting ?

82
HSDPA Scheduler
Upgrade
UL Load opti_UL
DCH
HSDPA Upgrade
Path

4. If high HSDPA Access Failure_BTS
Lack of UL channel resources (check CE resource utilisation using M5001 counters at BH)
Too high SHO overhead all branches must have enough CE capacity if UE is in SHO
when HS-DSCH allocation is started
83

5. HS-DSCH return channel setup fail due to Iub transport
Breakdown the failure distribution (64,128,384,MAC-d)
Evaluate number of reconfiguration failure due the transmission
Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533
6. HSDPA setup fail due RNC internal reason
Check RNC Unit load (DMPG)
Max number of users/RNC
DSP failures and faulty alarms
84
RETAINABILITY Call Completion Rate (CCSR)

Formula
CCSR KPI for CS voice
CCSR KPI for PS
85

Call Drop Analysis
Top (N) drops
Cell and its Neighbour

Cells availability
Alarms/Tickets
Neighbours Performance
(use SHO success per adjs
counters to identify badly
performing neighbours) & Map
Site OK ?
YES
Conf OK ?
3G Cell at
RNC border?
YES
SHO
Success
Rate <
90%?
SHO
ISHO
Failures
ISHO
No cell
found ratio
> 40 %
2G Cell Doctor
NO
YES
ISHO
Success
Rate <
90%
Iur
performance
Investigation Iur
New site ?
Analyse last detailed

radio measurements
NO
YES
Top
iss
ues
YES
YES
NO
86
Audit adjacent sites for

alarms, Availability,
configuration and
capacity
NO
Configuration &
Parameter audit
2G Investigation :
TCH blocking or TCH
seizure failure
(interference)
Traffic
3G cell at
inter-RNC
border ?
YES
3G cell
covers over a
coverage
hole?
RF and IFHO
neighbour
optimisation
RF and ISHO
neighbour
optimisation

Call Drop Analysis
87
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

Call Drop Analysis
5. Detecting DL or UL path loss problem if RAB drop due to radio (dominant call drop cause > 50%)
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 re-establishment timer -> T315 (rec.10s)
Ec/no distribution for bad coverage issue (M1007C38-M1007C47 CPICH_ECNO_CLASS_09)
6. Check core network parameter setting if RAB_ACT_FAIL_XXX_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)
88

Example: RAB active failures - Voice
Major cause Radio
89

Example: RAB active failures PS
90
RETAINABILITY HSDPA Retainability

Formula
Current RNC_609a HSDPA Retainability for NRT Traffic

RNC _ 609a
M1002C407 REL_ALLO_NORM_HS_DSCH_INT M1002C410 REL_ALLO_NORM_HS_DSCH_BGR

M1002C407 REL_ALLO_NORM_HS_DSCH_INT M1002C410 REL_ALLO_NORM_HS_DSCH_BGR
100%
M1002C408REL_ALLO_OTH_FAIL_HSD SCH_INT M1002C411R EL_ALLO_OTH_FAIL_HSD SCH_BGR

M1002C479REL_ALLO_RL_FAIL_HS_D SCH_INT M1002C482REL_ALLO_RL_FAIL_HS_ DSCH_BGR
The normal transition from HS-DSCH to FACH/DCH are considered as
a normal HS-DSCH release (including transitions due to mobility and pre-emption)
91

HSDPA Drop Analysis
92

HSDPA Drop Analysis
93
MOBILITY SHO Success Rate
94
MOBILITY SHO Success Rate
SHO improvement activities

ADJS Consistency check and rectification
1-way neighbour, missing neighbour rectification
Target cell HW issues clearance, congestion relief
Pilot pollution reduction
Parameter optimisaiton : ADJSEcNoOffset, Addition/Deletion timer
95
MOBILITY ISHO Success Rate
96
MOBILITY ISHO Success Rate
ISHO improvement activities

ADJG Consistency check and rectification (BSIC, LAC, CI, BCCH..)
Clean up no cell found neigbour
Target cell 2G Cell HW issues clearance, congestion relief
Tune ISHO threshold (AdjgRxLevMin)
Tune ISHO compressed Mode Setting (HHOEcNoThreshold, HHORSCPThreshold)
97
Thank you!
Nokia Siemens Networks:

Reinventing the connected world
98

01 Workshop-3G Optimisation - Sales Cluster

Uploaded by

Copyright:

Available Formats

01 Workshop-3G Optimisation - Sales Cluster

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01 Workshop-3G Optimisation - Sales Cluster

Uploaded by

Copyright:

Available Formats

3G Optimisation Workshop

Jan 18, 2013

NOKIA SIEMENS NETWORK

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA AIR INTERFACE

Nokia Siemens Networks

3G Network Planning Areas

Nokia Siemens Networks

UMTS Air Interface technologies

FDD: Separate UL and DL frequency band

TDD: UL and DL separated by time, utilizing same frequency

Nokia Siemens Networks

WCDMA FDD technology

All cells at same carrier frequency

Inter-Frequency functionality to support mobility between frequencies

Inter-System functionality to support mobility between GSM and UMTS

Nokia Siemens Networks

5+5 MHz in FDD mode

Nokia Siemens Networks

Direct Sequence (DS) CDMA

UMTS & GSM Network Planning

Nokia Siemens Networks

Differences between WCDMA & GSM

Nokia Siemens Networks

5 MHz bandwidth gives

Multiple WCDMA carriers Layered network

Nokia Siemens Networks

CDMA principle - Chips & Bits & Symbols

Nokia Siemens Networks

Energy per bit = Eb = const

Nokia Siemens Networks

Power density (Watts/Hz)

Spreading & Processing Gain

Unspread narrowband signal

Spread wideband signal

Bandwidth W (3.84 Mchip/sec)

W const 3.84 Mchip

Nokia Siemens Networks

Processing Gain Examples

Packet data user (R=384 kbit/s)

Nokia Siemens Networks

High bit rate user

Low bit rate user

Nokia Siemens Networks

Service delivery type

Quality classes for user to choose

Traffic asymmetric in uplink & downlink

Nokia Siemens Networks

Combination or multipath components and in DL also signals from different cells

Nokia Siemens Networks

Power Control in WCDMA

Nokia Siemens Networks

Effect on Tx & Rx Power on Interference Levels

Downlink transmission power =

Uplink transmission power =

Uplink received power = Interference to

Since every Tx and Rx power is causing interference to others, PC is

Nokia Siemens Networks