T-Mobile Module 7 - Parameter Optmisation

3G RANOP
Module 7 Parameter Optimisation
2005 Nokia
V1-Filename.ppt / yyyy-mm-dd / Initials
3G RAN Optimisation
Cluster Preparation
Cluster health checks Parameter consistency check Neighbour list verification Uplink interference as a problem indicator
Network Statistics
Cell Resources RRC/RAB Performance Handovers Abnormal Release
RF Optimisation and Neighbour Planning
RF optimisation New Site Integration Neighbour plan optimisation
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
Signalling Flows
RRC Establishment RAB Establishment SHO ISHO
Drive Test Analysis

2 2005 Nokia
Drive Survey Analysis System Performance (RRC and RAB phases)
Parametric Optimisatio n
Use of Parameters to optimise network performance

Objectives After this module the delegate shall be able to: List some of the parameters that can be tuned for improved performance Match these parameters to Call Setup and Call Retention improvement areas
2005 Nokia
Parameter Optimisation Introduction

The foundation of good network performance comes from a well optimised:
RF Plan neighbour plan Scrambling plan
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 Basic Radio Platform (Site/Antenna Location,etc)
4 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
The UE types in the network needs to be taken into account during parameter optimisation There are always tradeoffs (e.g setup time versus success rate) Parameter values may be different from network to network due to NW plan and operator strategy and therefore these parameters should be tuned in every network
Nokia Parameters an Introduction

Managed Objects
RNC = Radio Network Controller WBTS = WCDMA Base Station WCEL = WCDMA Cell ADJ = Adjacency for WCDMA cell ADJS = intra-frequency adjacency ADJI = inter-frequency adjacency ADJG = inter-system adjacency HOP = Handover Path HOPS, HOPI, HOPG FMC = Frequency Measurement Control FMCS, FMCI, FMCG COCO = Radio Network Connection Configuration
RNC
COCO
WBTS
HOPG
HOPI HOPS ADJS
FMCS FMCI FMCG WCELL
ADJI ADJG
See RNC Parameter Dictionary DN00211177
2005 Nokia
Common Channel Power settings

Common Channel power settings are critically important as they define the cell edge. The latest recommended settings are based on Nokias global experience and have been seen to work well. Care should be taken when optimising these parameters. The link budget of the PCCPCH and SCCPCH can be compared with Data on the DPCH.
There tends to be plenty of margin in AICH and PICH.

In general neighbouring cells should not have CPICH power differences greater than 3dB otherwise this can lead to soft handover radio link failures. Exceptions may occur if one cell is an indoor solution and the other is a macrocell
2005 Nokia
DL Common Control Channel

DL Common control channels must be heard over the whole cell. The only common physical channel that can have power control is SCCPCH, when it carries the FACH transport channel.
All other downlink common physical channels don't use power control: PCCPCH, CPICH, P-SCH, S-SCH, PICH, AICH and SCCPCH
The power of the common physical channels are set relative to the CPICH:
Parameters PtxPrimaryCPICH PtxPrimarySCH PtxSecSCH PtxPrimaryCCPCH PtxSecCCPCH PtxPICH PtxAICH Default (Relative) Default (Absolute) 33 dBm 33 dBm -3 dB 30 dBm -3 dB 30 dBm -5 dB 28 dBm 0 dB 33 dBm -8 dB 25 dBm -8 dB 25 dBm
2005 Nokia

Different quality requirement for the common channels make power planning a non-trivial task In this example the mobile "sees" the cell but cannot access it as it cannot Pilot coverage decode the BCH
P-CCPCH coverage
Possible values in dBm CPICH = 33dBm P-CCPCH = 28 dBm S-CCPCH = 33 dBm SCH1= SCH2 = P-CCPCH = 28dBm
2005 Nokia

Not all the CCCH need to be treated in the same way: Only Power Setting (depending on coverage) CPICH P-CCPCH P/S-SCH AICH
Power Setting and channel availability for multiple access/depending on coverage and traffic) PICH depending on paging repetition used per radio frame (10ms) S-CCPCH depending on traffic load on FACH
Setting the DL Common Control Channel Power is a trade off between: cell coverage: all the channels must be decoded at the cell edge cell capacity: the common channel power steal resources from the traffic channels
2005 Nokia
Effects CPICH Power modification

Less Power Available for traffic
Increased soft handover overhead

Too much power Late cell reselection /handout too late /handover
Reduced system capacity
Non- ideal traffic distribution
CPICH Transmit Power

CPICH coverage holes
Unreliable scrambling code detection Unreliable channel estimation Early cell reselection /handout too early /handover
Too little power
Reduced system coverage

Slow initial synchronisation synchonisation IncreasedEb/No requirement Non- ideal traffic distribution Reduced system capacity
10
2005 Nokia
Common Channel Power Configuration

Soft handover is driven by the CPICH Ec/Io which means that CPICH power allocations are important If neighbouring cells have different CPICH allocations then radio links will be unbalanced during soft handover and radio links may fail Requirement to align CPICH allocations as much as possible
20 W
33 dBm CPICH
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
Call Setup Key Areas for investigation

Cell Selection and Reselection Initial cell selection to a good cell and subsequent cell reselections to better cells is essential to increase the Call Setup Success Rate (CSSR) and speed up the call setup time. RACH Process Improve the RRC Setup Performance Activation Time Offset Improve PS Call Setup success rate by allowing more time for Radio Bearer setup and Reconfiguration procedures SRB changes Decrease call setup time by increasing the speed of the signalling bearer
12
2005 Nokia
Cell Reselection Parameter Examples

Cell reselection triggering time (WCEL-Treselection = 2s)
Reselection takes place immediately when the UE notices that there is difference between the cells Ec/No values (in worst case scenario there can be up to 3dB + Qhyst difference based on the measurement accuracy requirement)
Cell reselection hysteresis 2 (WCEL-Qhyst2 = 4dB)

This will add 4dB hysteresis to the neighboring cell evaluation (target for the cell reselection)
Cell Re-selection Quality Offset 2 (HOPS-AdjsQoffset2 = 0dB)

This parameter is used in the cell re-selection and ranking between WCDMA cells. The value of this parameter is subtracted from the measured CPICH Ec/No of the neighbor cell before the UE compares the quality measure with the cell re-selection/ ranking criteria
Sintrasearch (WCEL-Sintrasearch = 12dB)

This parameter is used by the UE to calculate the threshold (CPICH Ec/No) to start intra frequency (SHO) measurements (Sintrasearch above QqualMin value)
Minimum required quality level in the cell (WCEL- QqualMin = -18dB) Minimum required RX level in the cell (WCEL- QrxlevMin = -111dBm)
Cell Selection - S Criterion

If the cell does not fulfill the suitable cell criteria (i.e. S-criteria) the UE cannot access the cell and therefore the UE is out of the coverage
Qqualmeas (dB) (CPICH Ec/N0)
Squal > 0
S-Criterion fulfilled
Squal >0 AND Srxlev > 0
Qqualmin (24...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
Qrxlevmin (115...25) Pcompensation (typ =>0db)
Qrxlevmeas (dBm) CPICH RSCP
Srxlev > 0
Cell Selection example

BLER for Each for each RSCP range Call Setup status statistics RSCP 100% 90% 80% 70% 60% [%] 50% 40% 30% 20% [%] 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% BLER for Each Ec/No Call Setup status statistics for each Ec/No range
10%
0%
> -60
-60 to 70
-70 to 80
-80 to - -90 to - -100 to - -112 to 90 100 112 115 RSCP (dBm)
< -115
> -4
-4 to - -6 to - -8 to - -10 to -12 to -14 to -16 to -18 to 6 8 10 -12 -14 -16 -18 -21 Ec/No [dB]
<-21
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
Cell Reselection and Call Setup Time

Poor cell reselection can lead to poor call setup time distribution (due to UE having to send several RRC Connection Requests
Poor Cell Reselection Performance

Call Setup Delay (PDF & CDF)
100 90 80 70
Corrected Reselection Performance

Call Setup Delay CDF
PDF CDF
100.0% 80.0% 60.0% 40.0% 20.0%
60
50
40
30 20 10 0 0 0 to 3000 3000 to 5000 5000 to 8000 8000 to 10000 > 10000
3.5s - 3.7s
3.7s - 3.9s
3.9s - 4.1s
4.9s-5.1s
0.0% <3.5s
Setup Time [ms]
4.1s-4.3s
4.3s-4.5s
4.5s-4.7s
4.7s-4.9s
5.1s-5.3s
5.3s-5.5s
Setup Time (seconds)
16
2005 Nokia
>5.5s
Cell Reselection Test Case Example

Default Normal conditions
Qqualmin = -20dB Search when CPICH<-8dB, neighbours must be 2dB better, delay reselection by 3s
Set1 Aggressive Reselection

Start Searching Earlier (-6dB), no hysteresis to neighbour, change after 1s delay
Set2 Faster Change

Change immediately but capped by hysteresis
Set3 Search earlier with faster Change

Searching starts at -6dB, hysteresis to neighbours but change immediately
Parameter Sintrasearch Qhyst2 Treselection
Default 12dB 2dB 3s
Set1 14dB 0 1
Set2 12dB 2 0
Set3 14dB 2 0
17
2005 Nokia
Cell Reselection Test Case Results

Scanner data chart: If the measurements for cell reselection happens at about Ec/No 8dB, there is 95% possibility that second best server is >2dB lower than the best server
This means that the cell reselection has 80% probability it does not to lead to ping pong
If the reselection happens at about 16dB there is only 30% possibility that the second best server is >2dB lower than best server This does not leave enough room for deviation between best and second best server Note: With common channel setting in this network: base Ec/No (own cell) is around -4 dB (thats why not more than 1 cell at Ec/No > -4 dB)
Start the measurements at Ec/No ~-8dB -> with Qqualmin = -20 dB -> Sintrasearch >= 12dB -> test at least 12dB and 14dB
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
RRC Setup Phase

UE Node B
[RACH] RRC:RRC Connection Request NBAP: RL Setup Request
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
NBAP: RL Setup Response ALCAP:ERQ ALCAP:ECF [FACH] RRC: RRC Connection Setup
Start TX/RX
L1 Synchronisation NBAP: Synchronisation Indication
[DCH] RRC: RRC Connection Setup Complete
20
2005 Nokia
RACH Process
L1 ACK / AICH
Downlink BS
Not detected
UEtxPowerMaxPRACH
PowerRampStepPRACHpreamble
Uplink MS
Preamble Preamble 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
Initial preample power: Ptx = CPICHtransmissionPower-RSCP(CPICH) +RSSI(BS) + PRACHRequiredReceivedCI
21
2005 Nokia
RACH Process parameters

Main parameters to improve the RRC Connection Setup performance are listed below WCEL-PRACH_preamble_retrans & RACH_tx_Max (def 8 & 8) WCEL-PowerOffsetLastPreamblePRACHmessage (def 2dB) WCEL-PowerRampStepPRACHpreamble (def = 2dB) The RRC Connection Access success is highly dependent on the UE so all used UEs should be tested carefully before making any changes. Note, Some of the UEs (especially the ones with, early, Qualcomm chipset) could have fixed values for some parameters (an example from Sanyo): PRACH_preamble_retrans & RACH_tx_Max = 8 & 8 PowerRampStepPRACHpreamble = 3dB
22
2005 Nokia
RACH Process test

Two values for PRACHRequiredReceivedCI tested (drive testing)
-20dB & -25dB : UL interference conditions are at the same level (reported in SIB 7 for both cases)
PRACH req. C/I = -25dB PRACH req. C/I = -20dB
PRACH req. C/I = -20dB 100% 80%

%
PRACH req. C/I = -25dB
100% 88%
60% 40% 20% 0% 1 2 3 4 # RRC Connection Request Messages per call setup 0% 2% 0% 5% 0% 6%
100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% 1 2 3 4 5 6 7 8
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
RACH Process test

Two values for PRACHRequiredReceivedCI tested (drive testing) -20dB -25dB UL interference conditions are at the same level (reported in SIB 7 for both cases) Clear improvement in call setup delay for 20dB case. ~65% of the established calls are through with only 3.5 3.7s delay and the >5.5s delay tail disappears (in this case).
100% 99% 98% 97% 96% 95% 94% -25dB Call Setup Success Rate -20dB 96.2% 100.0%
PRACH req. C/I = -25
PRACH req. C/I = -20
120.0% 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
4.9s-5.1s
5.1s-5.3s
5.3s-5.5s
0.0%
<3.5s
Call Setup Delay (seconds) RRC Conn. Req. to Alerting
24
2005 Nokia
>5.5s
RRC Setup & Access Phase

When a physical dedicated channel establishment is initiated by the UE, the UE starts a timer WCEL-T312 (def=10s) and waits for layer 1 to indicate WCEL-N312 (def=4) "in sync" indications On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset On the BTS side after receiving synchronisation indicators the BTS sends NBAP: SYNCHRONIZATION INDICATION message to RNC after which the closed loop and outer loop PC start to control the powers
N_INSYNC_IND indicators on L1 Timer T312 started L1 Synchronization established BTS sends NBAP: SYNCHRONIZATION IDICATION -message RNC receives RRC Connection Setup Complete message ->
1
UE initiates physical dedicated channel establishment before sending e.g. RRC Connection Setup Complete message on DPDCH in sync indicators on L1 Timer T312 stopped L1 Synchronization established RRC Connection Setup Complete message SENT after 7 TSLs from DL sync is achieved
N312 L1 in sync indicators
25
2005 Nokia
RRC Setup & Access Phase

In case UE is not able to establish synchronisation within timer T312 it stops TX on the DCH In case BTS is not able to establish synchronisation it does not send NBAP:Synchronization Indication message to RNC
The BTS tries to establish synchronization until RNC sends NBAP:Radio Link Deletion message
UE Node B
[RACH] RRC:RRC Connection Request NBAP: RL Setup Request
RNC
Start TX/RX
NBAP: RL Setup Response
ALCAP:ERQ
ALCAP:ECF [FACH] RRC: RRC Connection Setup
Start TX/RX
L1 Synchronisation
26
2005 Nokia
Radio Bearer Process

Call Setup Success Rate (CSSR) depends on how well UE responds to the Radio Bearer (RB) Reconfiguration or RB Setup processes If UE does not have enough time to setup the lower layers for the new RB configuration then call setup will fail.
This could be improved by increasing the Activation Time Offset (ATO) parameter:
Connection Frame Number (CFN) is used in NBAP and RRC messages, when a radio link is reconfigured. It is used to indicate the activation time of the reconfiguration, and it is set by the Packet Scheduler
The CFN, which is set to the "activation time" field in L3 messages, is:
(the CFN provided by FP + (ActivationTimeOffset + SignalingDelayOffset)/10) mod 256
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.
27
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
ATO change case

AMR_701
1600 1400 1200 1500 500 200
Time(ms )
1000 800 600 400 200 0 1 2 3 4 5 6 7 8 9 10 11 12
1000ms
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
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
SRB change case
30
Example of RRC performance with SRB 3.5 kbits/s and 13.6 kbits/s
RRC Connection Access phase Success Rate should be evaluated when changing the SRB bit rate
2005 Nokia
15
100 94 95 96 97 98 99

RRC Setup SuccessRate
S RB 3.4kbps S RB 13.6kbps
RRC Access SuccessRate RRC Setup & Access SuccessRate
/0 7 16 /2 /0 00 7 4 17 /2 /0 00 7 4 18 /2 /0 00 7 4 19 /2 /0 00 7 4 20 /2 /0 00 7 4 21 /2 /0 00 7 4 22 /2 /0 00 7 4 23 /2 /0 00 7 4 24 /2 /0 00 7 4 25 /2 /0 00 7 4 26 /2 /0 00 7 4 27 /2 /0 00 7 4 28 /2 /0 00 7 4 29 /2 /0 00 7 4 30 /2 /0 00 7 4 31 /2 /0 00 7 4 01 /2 /0 00 8 4 02 /2 /0 00 8 4 03 /2 /0 00 8 4 04 /2 /0 00 8 4 05 /2 /0 00 8 4 06 /2 /0 00 8 4 07 /2 /0 00 8 4 08 /2 /0 00 8 4 09 /2 /0 00 8 4 10 /2 /0 00 8 4 11 /2 /0 00 8 4 12 /2 /0 00 8 4 13 /2 /0 00 8 4 14 /2 /0 00 8 4 15 /2 /0 00 8 4 16 /2 /0 00 8 4 17 /2 /0 00 8/ 4 20 04
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).
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)
31
2005 Nokia
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 speech + 3.4 kbps SRB

32.2 dBm 17.2 dBm
64 kbps data + 3.4 kbps SRB

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 RNCPCrangeDL of 20 dB (default 15 dB)
32
2005 Nokia
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
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.
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 all of FMC targeted areas

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
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
Packet Scheduler Parameters

The focus for PS data tests is to minimize the PS call drop and keep the throughput high The performance depends on the usage of certain bit rate and different RRC states of the connection. Dynamic Link Optimisation (DyLo) feature could impact the achieved throughput Maximum allowed bitrate in certain cells (e.g. Rural, Highway) could be set to a lower value if there is risk of capacity shortage (Radio, Iub)
Further performance/throughput could be optimized with different bearer activity/inactivity timers and traffic volume parameters.
The optimum set of parameters depend on the used application (FTP, MSS, email) and amount of data.
37
2005 Nokia
DyLO Improves NRT traffic coverage

128kbps 384kbps UE
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
Triggering of DyLO
Ptx, ave is averaged radio link power, measured and reported to RNC by BTS Ptx, max is determined by Admission Control
Ptx, RL distance
The value of the Offset is fixed at 2 dB Ptx, max DyLO is triggered if Offset Ptx, ave > Ptx, max Offset
Triggering of DyLO Ptx, ave
Dylo can be started only if the current bitrate is higher than Maximum Allowed DL User Bitrate in HHO
time
Dylo Bit Rate Upgrade

After downgrade of DCH bit rate due to DyLO, upgrade of the bit rate can only be performed from the initial bit rate
Cell level parameter Initial and minimum allowed bit rate in downlink is configurable by operator Bit rate upgrade from any other bit rate is not possible Bit rate upgrade is based on downlink traffic volume measurement reports (capacity requests) A change in radio link power conditions does not trigger upgrade
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 dB DyLO is possible if Ptx, init < (Ptx, max Offset) Upgrade is not possible, the next lower bit rate is tried (lower power)
40
2005 Nokia
DyLO Test example parameter settings

PtxDLabsMax InitialAndMinimumAllowedBitrateDL MaxBitRateDLPSNRT
Default 43 384kbps 384kbps
Set1 43 64kbps 384kbps
Set2 38 or 36 64kbps 384kbps
BTS types of Supreme,Optima38dBm, Metrosite 36dBm
Time spent on different bearers spreading factors

Default Set1 Set2 sf8 36:45.873 24:27.095 16:37.340 sf16 00:00.000 12:30.764 24:27.813 sf32 02:07.373 08:43.990 08:46.952 FACH 14:37.097 09:26.672 10:19.881 Idle 00:37.344 00:21.919 00:10.115
Set 2 gives smallest time in idle mode & more time in 128 kbits/s: improved NRT coverage
384 kbits/s as initial & Minimum Bitrate gives poor results

RB_Status
400 Sf8 200 300
RB_Status
sf16
1 6:4 1:44 :24 5 1 6:4 1:49 :25 2 1 6:4 1:56 :25 2 1 6:4 2:02 :35 1 1 6:4 2:11 :23 4 1 6:4 2:19 :78 6 1 6:4 2:21 :78 9 1 6:4 2:28 :79 9 1 6:4 2:35 :80 9 1 6:4 2:43 :82 1 1 6:4 2:51 :70 2 1 6:4 2:54 :25 6 1 6:4 2:59 :20 4 1 6:4 3:07 :87 5 1 6:4 3:16 :38 7 1 6:4 3:21 :89 5 1 6:4 3:27 :89 4 1 6:4 3:32 :90 1 1 6:4 3:37 :54 9 1 6:4 3:43 :41 6 1 6:4 3:48 :45 4 1 6:4 3:51 :28 9 1 6:4 3:54 :50 2 1 6:4 3:56 :32 5 1 6:4 4:00 :22 0 1 6:4 4:06 :03 9 1 6:4 4:15 :59 4 1 6:4 4:19 :61 9 1 6:4 4:23 :93 5 1 6:4 4:25 :63 7 1 6:4 4:28 :11 1 1 6:4 4:32 :20 6 1 6:4 4:39 :71 7 1 6:4 4:44 :11 4
16:41:39:209 16:41:44:736 16:41:49:754 16:41:57:764 16:42:05:265 16:42:14:159 16:42:21:229 16:42:25:084 16:42:33:295 16:42:40:816 16:42:50:761 16:42:53:485 16:42:58:402 16:43:07:605 16:43:16:879 16:43:22:396 16:43:28:805 16:43:34:344 16:43:39:451 16:43:45:459 16:43:49:866 16:43:53:491 16:43:54:864 16:43:59:009 16:44:05:037 16:44:13:620 16:44:19:109 16:44:23:935 16:44:25:667 16:44:28:191 16:44:34:199 16:44:41:209 16:44:44:274
sf32 FACH 0 Idle
Dylo Test example- compare throughput with the coverage
2005 Nokia
1 6:4 1:39 :20 9
sf32 FACH 0 Idle Sf8 400 sf16

100
42
100
200
300
Time
CPICH RSCP and RB Status (Set2)
CPICH Ec/No and RB Status (Set2)
Time V1-Filename.ppt / yyyy-mm-dd / Initials
RSCP
StatusID
Ec/No
-9 -4
StatusID
-90
-80
-70
-60
-130
-120
-110
-100
-24
20.00% 40.00% 60.00% 80.00% 0.00% > -4
-19
-14
100.00%
120.00%
100%
10% 0% > -4
20%
30%
40%
50% 100.00%
60%
70%
80%
90%
0.00%
384
-4 to -6
-7-8
-4 to -6 -6 to -8 -8 to -10 -10 to -12 Ec/No [dB]
51.03%
38.30%
10.67%
-6 to -8 -8 to -10 30.34%
40.72% 56.40%
47.55%
11.73% 13.26%
128
RB Status Statistics(vs EcNo)
Ec/No [dB]
-10 to -12
17.03%
57.16%
25.81%
RB Status Statistics(vs EcNo)
-12 to -14
RB Status for each Ec/No
-14-15
-12 to -14 -14 to -16 -16 to -18 < -18 sf8 sf32 sf16
11.54% -14 to -16 11.32% 37.74%
56.09% 50.94%
32.37%
64
5.21% < -18 6.98% 4.65%
-16 to -18
18.75% 88.37% sf8 sf16 sf32
76.04%

Summary Parameter optimisation is not a substitute for RF Optimisation In optimisation we have to consider the balances between power (resources) and success/speed Call Setup can be improved by improving Cell Selection and Reselection, SRB Rate and ATO Call retention can be improved by adjusting SHO parameters at the expense of resource usage
DyLO can affect the measured throughput from surveys
43
2005 Nokia

T-Mobile Module 7 - Parameter Optmisation

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

T-Mobile Module 7 - Parameter Optmisation

Diunggah oleh

Hak Cipta:

Format Tersedia

3G RANOP

Module 7 Parameter Optimisation

V1-Filename.ppt / yyyy-mm-dd / Initials

Cell Resources RRC/RAB Performance Handovers Abnormal Release

RF Optimisation and Neighbour Planning

RF optimisation New Site Integration Neighbour plan optimisation

Inter-System Working and Optimisation

RRC Establishment RAB Establishment SHO ISHO

Drive Test Analysis

Drive Survey Analysis System Performance (RRC and RAB phases)

Use of Parameters to optimise network performance

V1-Filename.ppt / yyyy-mm-dd / Initials

Module 7 Parameter Optimisation

V1-Filename.ppt / yyyy-mm-dd / Initials

Parameter Optimisation Introduction

Nokia Parameters an Introduction

FMCS FMCI FMCG WCELL

See RNC Parameter Dictionary DN00211177

V1-Filename.ppt / yyyy-mm-dd / Initials

Common Channel Power settings

There tends to be plenty of margin in AICH and PICH.

V1-Filename.ppt / yyyy-mm-dd / Initials

DL Common Control Channel

V1-Filename.ppt / yyyy-mm-dd / Initials

DL Common Control Channel

V1-Filename.ppt / yyyy-mm-dd / Initials

DL Common Control Channel

V1-Filename.ppt / yyyy-mm-dd / Initials

Effects CPICH Power modification

Increased soft handover overhead

Reduced system capacity

Non- ideal traffic distribution

CPICH Transmit Power

Too little power

Reduced system coverage

V1-Filename.ppt / yyyy-mm-dd / Initials

Common Channel Power Configuration

V1-Filename.ppt / yyyy-mm-dd / Initials

Call Setup Key Areas for investigation

V1-Filename.ppt / yyyy-mm-dd / Initials

Cell Reselection Parameter Examples

Cell reselection hysteresis 2 (WCEL-Qhyst2 = 4dB)

Cell Re-selection Quality Offset 2 (HOPS-AdjsQoffset2 = 0dB)

Sintrasearch (WCEL-Sintrasearch = 12dB)

Cell Selection - S Criterion

Qrxlevmin (115...25) Pcompensation (typ =>0db)

Qrxlevmeas (dBm) CPICH RSCP

Cell Selection example

-80 to - -90 to - -100 to - -112 to 90 100 112 115 RSCP (dBm)

Cell Reselection and Call Setup Time

Poor Cell Reselection Performance

Corrected Reselection Performance

100.0% 80.0% 60.0% 40.0% 20.0%

Setup Time (seconds)

V1-Filename.ppt / yyyy-mm-dd / Initials

Cell Reselection Test Case Example

Set1 Aggressive Reselection

Set2 Faster Change

Set3 Search earlier with faster Change

Parameter Sintrasearch Qhyst2 Treselection

Default 12dB 2dB 3s

V1-Filename.ppt / yyyy-mm-dd / Initials

Cell Reselection Test Case Results

High RRC Setup performance and RRC Connection Access Success.