Professional Documents
Culture Documents
T-Mobile Module 7 - Parameter Optmisation
T-Mobile Module 7 - Parameter Optmisation
2005 Nokia
3G RAN Optimisation
Cluster Preparati on
RF Optimisation and Neighbour Planning Cluster health checks Parameter consistency check Neighbour list verification Uplink interference as a problem indicator RF optimisation New Site Integration Neighbour plan optimisation
Network Statistics
Signalling Flows
3G<>2G Cell reselection Neighbour Planning Handover Process and compressed mode 3G ISHO service analysis (AMR and PS) GSM ISHO Optimisation Use of Parameters to optimise network performance
Parametri c Optimisati on
2005 Nokia
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)
The UE types in the network needs to be taken into account Feature Strategy during parameter optimisation There are always tradeoffs (e.g Parameterisation setup time versus success rate) Parameter values may be Neighbour Definition different from network to network due to NW plan and Scrambling Code Planning operator strategy and therefore these parameters should be Basic Radio Platform (Site/Antenna Location,etc) tuned in every network
4 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
RNC
COCO
WBTS
ADJI ADJG
2005 Nokia
2005 Nokia
P-CCPCH coverage
Pilot
Possible values in dBm CPICH = 33dBm P-CCPCH= 28 dBm S-CCPCH= 33 dBm SCH1= SCH2 = P-CCPCH = 28dBm
8 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
10
2005 Nokia
20 W
33 dBm CPICH
Neighbouring Node B with equal CPICH result in balanced radio links during soft handover Inner loop power control will be driven by both Node Bs Scenario results in unbalanced radio links during soft hand over. Inner loop power control will be driven by Node B with 28dBm CPICH and therefore the radio link to the second Node B may fail Slightly unbalanced radio links during soft handover Inner loop power control will be driven primarily by the 28dBm CPICH Node B
20 W
28 dBm CPICH
20 W
33 dBm CPICH
20 W
28 dBm CPICH
20 W
30 dBm CPICH
11
2005 Nokia
12
2005 Nokia
Minimum required quality level in the cell (WCEL- QqualMin = -18dB) Minimum required RX level in the cell (WCEL- QrxlevMin = -111dBm)
13 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Squal > 0
S-Criterion fulfilled
Squal >0 AND Srxlev > 0
The Qqualmin and Qrxlevmin parameters should be tuned carefully as non optimum settings can have significant impact on CSSR, Call setup time and time on 3G
14 2005 Nokia
Qqualmin (24...0)
Srxlev > 0
There is a tradeoff between maximising 3G utilisation and CSSR (end user experience)
These calls may be unable to setup the call after Qqualmin is changed to 18dB from current 20dB
Even though the CSSR is ~ 70% successful in poor RF conditions (Ec/No<-18 dB) It is recommended to leave the Qqualmin and Qrxlevmin as 18dB and 111 dBm respectively
15 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
PDF CDF
100.0% 80.0% 60.0% 40.0% 20.0% 3.5s - 3.7s 3.7s - 3.9s 3.9s - 4.1s 4.1s-4.3s 4.3s-4.5s 4.5s-4.7s 4.7s-4.9s 5.1s-5.3s 5.3s-5.5s 4.9s-5.1s 0.0%
Setup Time [ms]
16
2005 Nokia
>5.5s
<3.5s
Set3 3 dB 3 3 3
17
2005 Nokia
Start the measurements at Ec/No ~-8dB -> with Qqualmin = -20 dB -> Sintrasearch >= 12dB -> test at least 12dB and 14dB
18 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
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.
Minimise the impact of UE Tx power (preamble power) to the cell capacity. Minimise call setup delay Different UE performance is taken into account
19
2005 Nokia
RNC
This phase starts when UE sends the RRC CONNECTION REQUEST message using the PRACH channel It is completed when RNC, after reserving all the necessary resources for the RRC Connection (RNC, BTS, Radio and Transmission), replies with DL RRC CONNECTION SETUP message, carried over S-CCPCH (FACH sub-channel)
Start TX/RX
L1 Synchronisation NBAP: Synchronisation Indication
20
2005 Nokia
RACH Process
Downlink Not detected BS
UEtxPowerMaxPRACH PowerRampStepPRACHpreamble
L1 ACK / AICH
Uplink PreamblePreamble MS
1 2
Message part
PowerOffsetLastPreamblePRACHmessage 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
22
2005 Nokia
Clear improvement in number of needed RRC Connection Request messages per call. For 20dB 100% of established calls are setup with only 1 RRC Connection Request message
Clear improvement number of sent preambles per RRC Connection Request for 20dB case. For 20dB 50% of cases the needed number of preambles is <=4 where as for 25dB it is ~6.5 There should also be improvement of the call setup time
23
2005 Nokia
3 33 3. %
3. % 33
-33 dB
3 33 3. % 3 33 3. % 3. % 33 3. % 33 3. % 33 3. % 33 33 . % 3 .3 s - 3 .3 s 3 .3 s - 3 .3 s 3 .3 s - 3 .3 s 33 33 . s- . s 33 33 . s- . s 33 33 . s- . s 33 33 . s- . s 33 33 . s- . s 33 33 . s- . s 33 33 . s- . s >33 . s <33 . s
24
2005 Nokia
UE initiates physical dedicated channel establishment before sending e.g. RRC Connection Setup Complete message on DPDCH
RRC Connection Setup Complete message SENT after 7 TSLs from DL sync is achieved
25
2005 Nokia
RNC
Start TX/RX
L1 Synchronisation
26
2005 Nokia
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 Physical channel and measurement procedures Service SRB 3,6 SRB 16,6 All services 80 20 Transport channel procedures Service SRB 3,6 SRB 16,6 AMR 240 60 CS 240 60 PS 160 40
The recommended value for ActivationTimeOffset is 700ms for RAN1.5.2 (For RAN04 it will be 300ms) has been used.
28
2005 Nokia
Time(ms)
33 33 33 3 33 3 33 3 33 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
1000ms
3RRCConnectionRequest 3RRCConnectionSetup 3RRCConnectionSetupComplete 3MM CM Service Request 3MM Authentication Request 3MM Authentication Response 3SecurityModeCommand 3SecurityModeComplete 3CC SetUp 3 3 CC Call Proceeding 3 3RadioBearerSetup 3 3RadioBearerSetupComplete
<=> <=> <=> <=> <=> <=> <=> <=> <=> <=> <=> <=>
RRCConnectionSetup RRCConnectionSetupComplete MM CM Service Request MM Authentication Request MM Authentication Response SecurityModeCommand SecurityModeComplete CC SetUp CC Call Proceeding RadioBearerSetup RadioBearerSetupComplete CC Alerting
1300ms
The difference in call setup time to the previous page is almost the difference between the RadioBearerSetup and RadioBearerSetupcomplete messages (part 11).
29
2005 Nokia
30
RRC Connection Access phase Success Rate should be evaluated when changing the SRB bit rate
Example of RRC performance with SRB 3.5 kbits/s and 13.6 kbits/s
2005 Nokia
33 3 33 33 33 33 3 3 3 3
S B 3 3b s R . kp S B 3 3p R .3 s kb
3 3 /3 3 3 3 /3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 3 /3 /3 3 3 3 3 3 3 /3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 3 /3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 /3 3 /3 3 3 3 3 3 /3 3 3 /3 3 3 3 3 /3 3 /3 3 3 3 3 /3 3 3 3
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 RDCH is the maximum transport channel bit rate of downlink DCH. Ptx,DPCH,max is the value of WCEL-PtxDLabsMax - WCELPtxDPCHMax.
EbNoref is the (linear) value of the planned downlink Eb/No of the reference service which is defined with parameter Downlink BLER target of the reference service (DLreferenceTargetBLER).
31 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Rref is the maximum DCH bit rate of the reference service (parameter DLreferenceBitRate) .
Ptx,off defines the power of the primary CPICH in relation to the maximum code power of the ref. service (WCELCPICHtoRefRABoffset)
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 27.8 dBm 15 dBm 13.6 kbps standalone SRB 31.8 dBm 16.8 dBm 12.2 kbps 64 kbps 128 kbps 384 kbps speech + data + data + data + 3.4 kbps SRB 3.4 kbps SRB 3.4 kbps SRB 3.4 kbps SRB 32.2 dBm 17.2 dBm 35.2 dBm 20.2 dBm 38.0 dBm 23.0 dBm 40 dBm 25 dBm
Maximum Minimum
However, it should be noted that the minimum power used is increased if Offset is reduced as well (Minimum power=Max power DL PC Range) which might lead to the situation where too high powers are allocated even in the good coverage conditions -> too much power is wasted in BTS. CPICHtoRefRABOffset of 0 dB (default 2 dB) could be tested with RNC-PCrangeDL of 20 dB (default 15 dB)
32 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
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
150
200
33
2005 Nokia
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.
34 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
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
SHO Parameters
The most important FMCS parameters to be used for SHO optimisation are
Parameters Default value CPICH Ec/No Filter Coefficient 3 3 3 ms Addition Window 3 dB .3 Addition Time 33 3 ms Drop Window 3dB Drop Time 33 3 ms
Default values should work fine, but in some cases more conservative SHO settings (add 4 dB, drop 6 dB) could be used to avoid high ASU period (time between Active Set Update message)
36
2005 Nokia
37
2005 Nokia
Radio link is modified to use lower bit rate (with physical channel reconfiguration message) when Tx power is getting close to maximum, in order to ensure sufficient quality
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
38 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Triggering of DyLO
Ptx, ave is averaged radio link power, measured and reported to RNC by BTS
distance
Ptx, RL
DyLO is triggered if
Ptx, ave > Ptx, max Offset Dylo can be started only if the current bitrate is higher than Maximum Allowed DL User Bitrate in HHO
time
39 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Possible triggering of the DyLO is checked before the bit rate is upgraded, in order to avoid ping-pong effect
New Ptx, max is calculated by AC according to the new bit rate Initial Tx power Ptx, init is calculated by AC according to the new bit rate Fixed, 2 DyLO is possible if Ptx, init < (Ptx, max Offset) dB Upgrade is not possible, the next lower bit rate is tried (lower power)
40
2005 Nokia
Time spent on different bearers spreading factors Default Set3 Set3 sf3 3 :3 .3 3 333 2 2 :2 2 .2 2 2 3 :3 .3 3 333 sf33 3 :3 .3 3 333 3 :3 .3 3 333 3 :3 .3 3 333 sf33 3 :3 .3 3 333 3 :3 .3 3 333 3 :3 .3 3 333 FACH 3 :3 .3 3 333 3 :3 .3 3 333 3 :3 .3 3 333 Idle 3 :3 .3 3 333 3 :3 .3 3 333 3 :3 .3 3 333 384 kbits/s as initial & Minimum Bitrate gives poor results
41 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Set 2 gives smallest time in idle mode & more time in 128 kbits/s: improved NRT coverage
RB_Status 33 3 Sf8 33 3 33 3
RB_Status
sf16
sf16
Sf8 33 3
33 : 3 3 : 3 3 : 3 33 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3 3 : 3 3 : 3 3 : 33 3 3: 3: 333 3 33: 3 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3 3 3 33: 3: 33 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 333 3 33: 3 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3 3 3 33: 3: 33 3: 3: 333 3 33: 3 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 3 3 3 333 3: 3: 3: 33 3333 3: 3: 3: 33 3333 3: 3: 3: 33 3333
3:3:3:33 3333 3 3 :3 3 :3 3 :3 3 3 3 3 :3 3 :3 3 :3 33 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3 3 :3 3 :3 3 :3 3 3 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333 3:3:3:33 3333
33 3
33 3
33 3
3: 3: 3: 33 3333
42 2005 Nokia
Time
RSCP
StatusID
Ec/No
StatusID
-33
-33
-33
-33
-33
-3
-3
-333
-333
-333
-333
-33
3. 3 33 % 3. 3 33 % 3. 3 33 % 3. 3 33 % 33 % . 3 > -3
-33
3 33 % 3. 3
3 33 % 3. 3
33 3%
3% 3 3 % > -3
3% 3
3% 3
3% 3
3% 3 3 33 % 3. 3
3% 3
3% 3
3% 3
3% 3
33 % . 3
384
- 3to - 3
3. 3 33 %
2 2 .2 2 %
2 2 .2 2 %
-7 -8
-3to -3 -3to -3 -3to -33 Ec/No [dB] - 33 -33 to
- 3to -3 3. 3 33 % - 3to - 33
3. 3 33 % 3. 3 33 %
3. 3 33 %
3. 3 33 % 3. 3 33 %
128
Ec/No [dB]
3. 3 33 %
3. 3 33 %
3. 3 33 %
- 33 - 33 to
3. 3 33 %
2 2 .2 2 %
3. 3 33 %
- 33 - 33 to
-14 -15
3. 3 33 %
3. 3 33 %
3. 3 33 %
- 33 -33 to
64
3. 3 33 % 33 % . 3 33 % . 3 33 % . 3 < -33
3. 3 33 %
- 33 - 33 to
3. 3 33 %
sf3
sf33
sf33