Beruflich Dokumente
Kultur Dokumente
2005 Nokia
3G RAN Optimisation
Cluster
Preparati
on
RF
Optimisation
and Neighbour
Planning
Signalling
Flows
Drive Test
Analysis
RRC Establishment
RAB Establishment
SHO
ISHO
Network
Statistics
Inter-System
Working and
Optimisation
3G<>2G Cell
reselection
Neighbour Planning
Handover Process and
compressed mode
3G ISHO service
analysis (AMR and PS)
GSM ISHO Optimisation
Parametri
c
Optimisati
on
Cell Resources
RRC/RAB Performance
Handovers
Abnormal Release
Use of Parameters to
optimise network
performance
The maximum benefits from parameter optimisation can only be realised if the
above are in place.
Although parameter optimisation can provide short term gains they do not
correct underlying network problems. (E.g SHO <> Dominance)
Feature Strategy
Parameterisation
Neighbour Definition
Scrambling Code Planning
RNC
COCO
WBTS
FMCS
FMCI
FMCG
HOPG
HOPI
HOPS
ADJS
WCELL
ADJI
ADJG
P-CCPCH
coverage
Pilot
CPICH = 33dBm
P-CCPCH = 28 dBm
S-CCPCH= 33 dBm
SCH1= SCH2 = P-CCPCH = 28dBm
Reduced system
capacity
Non-ideal traffic
distribution
CPICH coverage
holes
Reduced system
coverage
Unreliable scrambling
code detection
Slow initial
synchronisation
synchonisation
CPICH Transmit
Power
Too little
power
Unreliable channel
estimation
Early cell reselection
/handout
/handover
too early
IncreasedEb/No
requirement
Non-ideal traffic
distribution
Reduced system
capacity
20 W
33 dBm
CPICH
20 W
33 dBm
CPICH
20 W
28 dBm
CPICH
20 W
28 dBm
CPICH
33 dBm
CPICH
20 W
30 dBm
CPICH
S-Criterion
fulfilled
Squal > 0
Qqualmin
(24...0)
Qrxlevmin
(115...25)
Pcompensation
(typ =>0db)
Qrxlevmeas (dBm)
CPICH RSCP
Srxlev > 0
100%
100%
90%
90%
80%
80%
70%
70%
60%
60%
[%]
[%]
50%
50%
40%
40%
30%
30%
20%
20%
10%
10%
0%
0%
> -60
-60 to 70
-70 to 80
-80 to - -90 to 90
100
RSCP (dBm)
< -115
> -4
<-21
100
PDF
CDF
90
80
100.0%
70
> 10000
>5.5s
3000 to 5000
5.3s-5.5s
0 to 3000
5.1s-5.3s
4.9s-5.1s
0.0%
4.7s-4.9s
10
4.5s-4.7s
20.0%
4.3s-4.5s
20
4.1s-4.3s
40.0%
30
3.9s - 4.1s
40
3.7s - 3.9s
60.0%
3.5s - 3.7s
50
<3.5s
80.0%
60
Parameter
Sintrasearch
Qhyst2
Treselection
Default
12dB
2dB
3s
Set1
14dB
0
1
Set2
12dB
2
0
Set3
14dB
2
0
RACH Process
Optimum RACH performance is needed to ensure;
High RRC Setup performance and RRC Connection Access Success.
In both cases the testing is concentrated on RRC Setup success rate, and the
number of RRC Connection Requests sent.
Node B
RNC
Start
Start
TX/RX
TX/RX
NBAP: RL Setup Response
ALCAP:ERQ
ALCAP:ECF
[FACH] RRC: RRC Connection Setup
Start
TX/RX
L1 Synchronisation
NBAP: Synchronisation Indication
RACH Process
L1 ACK / AICH
Uplink
PreamblePreamble
MS
1
Message part
PowerOffsetLastPreamblePRACHmessa
PRACH_preamble_retrans
# PRACH preambles transmitted during one PRACH cycle without receiving AICH response
RACH_tx_Max
# preamble power ramping cycles that can be done before RACH transmission failure is reported
100%
88%
80%
60%
40%
20%
0%
1
0% 2%
0% 5%
0%
6%
100%
90%
80%
70%
60%
50%
40%
30%
20%
10%
0%
1
100.0%
100%
99%
98%
97%
96.2%
96%
95%
94%
-25dB
-20dB
Call Setup Success Rate
120.0%
100.0%
80.0%
60.0%
40.0%
20.0%
>5.5s
5.3s-5.5s
5.1s-5.3s
4.9s-5.1s
4.7s-4.9s
4.5s-4.7s
4.3s-4.5s
4.1s-4.3s
3.9s - 4.1s
3.7s - 3.9s
3.5s - 3.7s
0.0%
<3.5s
N_INSYNC_IND
indicators on
L1
Timer T312
started
UE initiates physical
dedicated channel
establishment before
sending e.g. RRC
Connection Setup Complete
message on DPDCH
in sync
indicators on
L1
N312 L1 in
sync
indicators
L1 Synchronization
established
BTS sends NBAP:
SYNCHRONIZATION
IDICATION
-message
Timer
T312
stopped
L1
Synchronizati
on
established
UE
Node B
RNC
Start
Start TX/RX
TX/RX
Start
TX/RX
L1 Synchronisation
Call Setup time can be improved by changing ATO and/or changing the Signalling
Radio Bearer (SRB) bit rate
Both call setup delay and access performance should be considered and balanced.
ATO
In RAN1.5. 2 ED2 the total offset consists of ActivationTimeOffset parameter part
and fixed SignallingDelayOffset part
ActivationTimeOffset part represents the processing delay of RNC and BTS.
The SignalingDelayOffset is an RNC internal parameter that implies a
required offset based on the SRB bit rate, the actual procedure and the
length of a RRC message. The fixed values set in RNC are below (ms)
RB Procedures
Service
SRB 3,4
SRB 13,6
AMR
280
70
CS
280
70
PS
200
50
AMR_701
500
200
1600
1400
Time(ms)
1200
1000
800
1000ms
600
1
2
3
4
5
6
7
8
9
10
11
12
RRCConnectionRequest
RRCConnectionSetup
RRCConnectionSetupComplete
MM CM Service Request
MM Authentication Request
MM Authentication Response
SecurityModeCommand
SecurityModeComplete
CC SetUp
CC Call Proceeding
RadioBearerSetup
RadioBearerSetupComplete
<=>
<=>
<=>
<=>
<=>
<=>
<=>
<=>
<=>
<=>
<=>
<=>
RRCConnectionSetup
RRCConnectionSetupComplete
MM CM Service Request
MM Authentication Request
MM Authentication Response
SecurityModeCommand
SecurityModeComplete
CC SetUp
CC Call Proceeding
RadioBearerSetup
RadioBearerSetupComplete
CC Alerting
1300ms
400
200
0
1
10
11
12
The difference in call setup time to the previous page is almost the
difference between the RadioBearerSetup and
RadioBearerSetupcomplete messages (part 11).
100
99
98
97
96
95
94
SRB 3.4kbps
SRB 13.6kbps
Maximum DL power
If call setups are attempted and are failing in bad Ec/No or RSCP
conditions then one solution to improve the call setup success rate
might be to tune CPICHtoRefRABOffset
The max DL power is determined by Admission Control as
EbNoDCH is the (linear) value
of the planned downlink Eb/No
of the service transferred on the
DCH
Rref is the
maximum DCH bit
rate of the reference
service (parameter
DLreferenceBitRate).
Maximum DL power
Example Maximum and Minimum Power for different services
WCEL-CPICHtoRefRABOffset = 2dB and RNC-PCrangeDL = 15dB
Service Type
3.4 kbps
standalone
SRB
13.6 kbps
standalone
SRB
12.2 kbps
speech +
3.4 kbps
SRB
64 kbps
data +
3.4 kbps
SRB
128 kbps
data +
3.4 kbps
SRB
384 kbps
data +
3.4 kbps
SRB
Maximum
27.8 dBm
31.8 dBm
32.2 dBm
35.2 dBm
38.0 dBm
40 dBm
Minimum
15 dBm
16.8 dBm
17.2 dBm
20.2 dBm
23.0 dBm
25 dBm
SHO Optimisation
The main emphasis in SHO optimisation is related to SHO overhead, SHO
success rate, call drop rate and average Active Set size.
Neighbor planning is more important than SHO parameter optimisation, so
it should be done properly
Acceptable SHO overhead in this case is 50 % or less, one example below
600
500
400
300
200
100
0
50
100
Soft handover overhead [%]
150
200
SHO Failures
The SHO failures are mainly related to:
Initial Synchronization Failure of the new added RL
Active Synchronization Failure of the existing RL(s)
Different soft handover parameters can help with synchronization
problems between radio links.
When new radio link is added to the Active set the L1 synchronization
between the UE and the new BTS must be achieved. The UL/DL
synchronization procedures are needed to establish reliable new
connection between BTS and UE.
Some of the initial synchronization failures are due to the fact that
there can be difference in the UL noise rise levels of the adjacent cells
(check Noise rise from Module1)
If a lot of initial synchronization failures for SHO links are seen then one
possibility is to try to reduce those by delaying the additions.
SHO Failure
If there are many Active Synchronization Failures detected, one action
could be to advance the SHO activity (e.g. using cell individual offsets)
or in general use different FMCS (usually these conditions are improved
when addition is done earlier e.g. add 4dB and drop 6dB).
If UE does not have enough level to receive ActiveSet
Update message it is possible that call drop happen
because of H/O failure.
Call drop be avoided by setting earlier timing (timing for
sending out Measurement report )of H/O between
targeted cells.
Use FMC parameter
Use ADJSEcNooffset
Impact only
between 2 targeted
cells
SHO Parameters
The most important FMCS parameters to be used for SHO optimisation are
Parameters
Default
value
CPICH Ec/No Filter Coefficient 600 ms
Addition Window
2.5 dB
Addition Time
100ms
Drop Window
4 dB
Drop Time
640ms
384kbps
UE
BTS
Dylo restrictions
Radio link conditions under DRNC cannot trigger DyLO
The reconfiguration of Iub AAL2 transmission resources is not
performed due to DyLO
DyLO is not allowed during compressed mode measurement
Triggering of DyLO
Ptx, ave is averaged
radio link power,
measured and reported
to RNC by BTS
distance
Ptx, RL
DyLO is triggered if
time
Default
43
384kbps
384kbps
Set1
43
64kbps
384kbps
Set2
38 or 36
64kbps
384kbps
Set 2 gives
smallest time in
idle mode & more
time in 128
kbits/s: improved
NRT coverage
sf32
FACH
0
Idle
Time
16:44:44:114
16:44:39:717
16:44:32:206
16:44:28:111
16:44:25:637
16:44:23:935
16:44:19:619
300
16:44:15:594
16:44:44:274
16:44:41:209
16:44:34:199
16:44:28:191
16:44:25:667
16:44:23:935
16:44:19:109
16:44:13:620
16:44:05:037
16:43:59:009
16:43:54:864
16:43:53:491
16:43:49:866
16:43:45:459
16:43:39:451
16:43:34:344
16:43:28:805
16:43:22:396
16:43:16:879
16:43:07:605
16:42:58:402
16:42:53:485
16:42:50:761
16:42:40:816
16:42:33:295
16:42:25:084
300
16:44:06:039
16:44:00:220
16:43:56:325
16:43:54:502
16:43:51:289
16:43:48:454
16:43:43:416
16:43:37:549
16:43:32:901
16:43:27:894
16:43:21:895
16:43:16:387
16:43:07:875
16:42:59:204
16:42:54:256
16:42:51:702
16:42:43:821
400
Sf8
16:42:35:809
16:42:21:229
16:42:14:159
16:42:05:265
16:41:57:764
16:41:49:754
16:41:44:736
RB_Status
400
Sf8
16:42:28:799
16:42:21:789
16:42:19:786
16:42:11:234
16:42:02:351
16:41:56:252
16:41:39:209
sf32
FACH
0
Idle
16:41:49:252
16:41:44:245
16:41:39:209
RB_Status
-70
200
StatusID
-80
RSCP
-90
sf16
-100
100
-110
-120
-130
StatusID
-9
200
-14
sf16
100
RB Status Statistics(vs EcNo)
100%
50%
0%
0.00%
90%
10.67%
70%
30%
20%
> -4
> -4
-4 to -6
Time
-7 -8
-4 to -6
11.73%
60%
-6 to -8
384
-6 to -8
13.26%
25.81%
80%
40%
10%
17.03%
-8 to -10
-8 to -10
-10 to -12
Ec/No [dB]
-10 to -12
32.37%
38.30%
47.55%
50.94%
56.40%
76.04%
100.00%
57.16%
88.37%
56.09%
sf32
128
-14 -15
-12 to -14
sf16
51.03%
37.74%
sf8
40.72%
30.34%
11.54%
11.32%
18.75%
-12 to -14
-14 to -16
-14 to -16
5.21%
4.65%
-16 to -18
-16 to -18
< -18
6.98%
Ec/No [dB]
64
Ec/No
100.00%
80.00%
60.00%
sf8
sf16
sf32
-19
40.00%
20.00%
-24
0.00%
< -18