Chapter 4 WCDMA RAN Optimization - Integrity - v2

TURKCELL DAHİLİ
WCDMA RAN Optimization
Chapter 5: Service Integrity

TURKCELL DAHİLİ
Chapter 5 Objectives
After this module, the participants will be able to:
1. Explain why inner, outer, and open loop power control are needed
2. Explain the operation of inner loop power control and the impact of the
network
3. Explain the operation of outer loop power control and the impact of the
network
4. Control the channel switching by means of parameter settings
5. Explain which counters and formulas to use in order to retrieve the
worst cells
6. Explain how to optimize HSPA network
7. Explain how to optimize MBMS network
8. Explain techniques for troubleshooting Integrity KPIs, clustering and
drill through statistics analyze.
9. Analyze data from real networks and propose changes in order to
improve the networks integrity
© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

. A Figure2 5 - Service Integrity
TURKCELL DAHİLİ
Service Integrity Workflow
Recommendation
Performance Performance Verification of
&
Measurements Analysis changes
Implementation
BLER counters BLER, power, Test the settings Check statistics

and Down SIR parameters If not OK, roll back
Switching
counters Throughput
pmFaultyTransportBlocksBcUl
pmTransportBlocksBcUl
pmNoOfSwDownNgCong
PmNoOfSwDownNgAdm
PmDl Traffic volume counters

TURKCELL DAHİLİ
Worst Cells
Observability of Service Integrity is very limited.
Only UL BLER per RAB on RNC level can be monitored
The system is designed to fight against BLER deviations from
the set BLER targets
There are two counters on cell level before combining :
 pmFaultyTransportBlocksBcUl These counters

does also contain
 pmTransportBlocksBcUl BLER information
for all RAB’s
pmFaultyBlocksBcUL
100 
pmTranspor tBlocksBcUl

TURKCELL DAHİLİ
Worst Cells

TURKCELL DAHİLİ
Worst Cells – after combining
Formula Below shows Block Error rate after uplink combining at
RNC level. That means in RNC blocks coming from different legs
in SHO are compared:
pmFaultyTr ansportBlocksAcUl[UeRc]
100 
pmTranspor tBlocksAcUl[UeRc]
UeRc stands for different RAB’s

UeRc=2, Speech
UeRc=3, Video Call
UeRc=4, Packet Common Channel
UeRc=5, PS 64/64
UeRc=6, PS64/128
UeRc=7, PS 64/384
UeRc=10 multirab Speech+PS 0 or PS 64/64).

TURKCELL DAHİLİ
Optima - BLER

TURKCELL DAHİLİ
Optima - BLER
• BLER_CS_SP: Ses Servisi için combining sonrası elde edilen BLER %

• BLER_CS_64: Görüntülü konuşma (video call) için combining sonrası elde
edilen BLER %
• BLER_PS_R99: R99 Data servisleri için combining sonrası elde edilen BLER %
• BLER_AC_ALL: Tüm Servisler için combining sonrası elde edilen BLER %
• BLER_BC_ALL: Tüm Servisler için combining öncesi elde edilen BLER %

TURKCELL DAHİLİ
Optima - BLER

TURKCELL DAHİLİ
Optima - BLER
• R99, HS, EUL servisi After Combining sonrası BLER Dağılımı

• UL_BLER < 0.5 (%) : BLER % < %0.5’in altındaki örneklerin toplama oranı
• 0.5 <= UL_BLER < 1.5 (%) : 0.5% < BLER % < %1.5’in altındaki örneklerin toplama oranı
• 1.5 <= UL_BLER < 2.5 (%) : %1.5 < BLER % < %2.5’in altındaki örneklerin toplama oranı
• 2.5 <= UL_BLER < 5 (%) : %2.5 < BLER % < %5’in altındaki örneklerin toplama oranı
• 5 <= UL_BLER < 10 (%) : %5 < BLER % < %10’in altındaki örneklerin toplama oranı
• UL_BLER >= 20 (%) : BLER % > %20’in üstündeki örneklerin toplama oranı
• UL ile aynı aralıklarda DL BLER istatistikleri de verilmektedir.

. A Figure105 - Service Integrity
TURKCELL DAHİLİ
Optima - BLER
• R99, HS, EUL servisleri için RSCP Dağılımı
• RSCP < -115 dBm (%)
• -115 <= RSCP < -111 dBm (%)
• -111 <= RSCP < -103 dBm (%)
• -103 <= RSCP < -99 dBm (%)
• -99 <= RSCP < -91 dBm (%)
• -91 <= RSCP < -79 dBm (%)
• -79 <= RSCP < -71 dBm (%)
• -71 <= RSCP < -59 dBm (%)
• -59 dBm <= RSCP (%)
• R99, HS, EUL servisleri için Ec/No Dağılımı

• EC_NO < -18 dB (%)
• -18 <= EC_NO < -14 dB (%)
• -14 <= EC_NO < -10 dB (%)
• -10 <= EC_NO < -6 dB (%)
• -6 <= EC_NO dB (%)

WCMA Power Control TURKCELL DAHİLİ
Soft/Softer Handover benefits
The UE and the WCDMA RAN must achieve a connection

that has a sufficient Signal-to-Interference Ratio (SIR), even
when the UE is at the cell border.
The UE requires enough power to achieve sufficient downlink

SIR .
Using Soft or Softer Handover,

UE takes advantage of having
several simultaneous radio links
DL RBS's output power can be

lowered, reducing interference
and increasing capacity.
TURKCELL DAHİLİ
WCMA Power Control
The Outer Loop Power Control algorithm is used to maintain

the required Block Error Rate (BLER) for a service by
modifying the SIR target of Inner Loop Power Control.
TURKCELL DAHİLİ
Workflow
 Through performance statistics data (RNC counters) identify

RAB’s that are not performing in line with targets
(blerQualityTargetUl). That means - uplink BLER derived from
counters is higher than UL BLER Target value set by
parameter.
 Review radio parameter settings and verify settings against Ericsson
default/recommended values.
– Check RAB parameters on the RNC level (blerQualityTargetUl
and blerQualityTargetDl)
– Check the values of the RAB Power Mapping parameters,
– Check UL Outer Power loop parameters (SIRMax, ul SIR Step)
 Check if different blerQualityTarget settings should be investigated
(for example, what is happening changing target from 1 to 2% for
voice)

Cyclic Redundancy Check TURKCELL
(CRC) DAHİLİ
The Error detection and error protection of the data channels
are performed using Cyclic Redundancy Check (CRC)
coding, Forward Error Correction (FEC) and interleaving, all
after error correction
Transmitter
Original Data CRC Original Data Checksum 12 bits
244 bits Generator 1001011010.. 110010110011
RF
Transmission Path
Receiver
Received Data Received Checksum If Checksums do not match,
1001010010.. 110010110011
there is an error
CRC Re-Generated Checksum

Generator 110010110001

WCMA UL Inner Loop Power Control
TURKCELL DAHİLİ
The RBS maintains the QoS by sending Transmit Power Control (TPC)
commands in every slot (i.e., 1500 times per second in a 15 slots per 10 ms
format) requesting a power adjustment.
If estimated SIR >= target SIR, the RBS sends a down command.
If estimated SIR < target SIR, the RBS sends an up command
TURKCELL DAHİLİ
WCMA Outer Loop Power Control
There are two alternative

algorithms for uplink
Outer Loop Power
Control implemented :
 Constant Step
Regulator
 Jump Regulator
The parameter setting

the type of regulator is
ulOuterLoopRegulator

TURKCELL DAHİLİ
(cont)
The start point of SIR
target regulation is
determined by the Initial
Uplink SIR Target
(ulInitSirTargetLow or
ulInitSirTargetHigh)
depending on the
Spreading Factor of
DPDCH
The two configurable

parameters sirMax and
sirMin set the limits of the
uplink SIR target,
expressed in dB

TURKCELL DAHİLİ
SIR Target Behavior According to the
Constant Step Regulator algorithm
Constant Step Regulator algorithm When the
NBR_OF_CRC_OK of
concecutive transport
blocks is fulfilled SIR is
decreased by ulSirStep
Whenever the Cyclic

Redundancy Check
(CRC) indicates that the
reception of a transport
block is erroneous, the
uplink SIR target is
increased by configurable
increment ulSirStep,
expressed in dB

TURKCELL DAHİLİ
(cont)
Jump Regulator algorithm
 -X Y
SIRtarget_new  SIRtarget  ulSirStep  
 (Z * UP_DOWN_STEP_RATIO) Z 
Where:
ulSirStep is the configurable parameter that defines the size of SIR target
increment.
Z is the total number of received transport blocks.
X is the number of transport blocks that have a CRC=OK.
Y is the number of transport blocks that have a CRC=NG.

TURKCELL DAHİLİ
SIR Target Behavior According to
the Jump Regulator algorithm
Jump Regulator algorithm Whenever the CRC
indicates that the
reception of a transport
block is erroneous, the
uplink SIR target is
increased by ulSirStep.
Whenever a transport
block is correct, the UL
SIR target is decreased
by a fraction of ulSirStep.
This fraction,
UP_DOWN_STEP_RATI
O, depends on the BLER
target.
TURKCELL DAHİLİ
(cont) Default values for parameters blerQualityTarget UL/DL set on TrCH
RAB Type TrCH Default Value

BLER Targets SRB SRB -20 ( 1% BLER)
Speech 12.2 Speech -20 (1% BLER)

The purpose of configurable SRB -20 (1% BLER)
BLER targets is to enable the Conversational CS data 64 CS64

SRB
-25 (0.3% BLER)
-20 (1% BLER)
operator to trade quality of CS Streaming 57.6 CS57.6 -20 (1% BLER)

the connections versus SRB -20 (1% BLER)
resource usage. PS Interactive 64/64 PS64

SRB
-20 (1% BLER)
-20 (1% BLER)
PS Interactive 64/128 PS128 -20 (1% BLER)
 blerQualityTargetDl SRB -20 (1% BLER)
PS Interactive 64/384 PS384 -20 (1% BLER)

SRB -20 (1% BLER)
 blerQualityTargetUl Speech+ PS Interactive 64/64 Speech -20 (1% BLER)

PS64 -20 (1% BLER)
SRB -20 (1% BLER)
10*log (blerqualitytargetxl) PS Streaming 16/64 PS Streaming -13 (5% BLER)

PS8/8 -13 (5% BLER)
SRB -20 (1% BLER)

TURKCELL DAHİLİ
Throughput - Session throughput
and THold
Throughput = the perceived user data rate from the
application layer.
Throughput will never reach the peak rate, since the TCP and
IP overhead, and retransmissions, have to be taken into
account.
The throughput can be expressed per session, per bearer or

per cell.

TURKCELL DAHİLİ
Throughput - Session throughput
and THold

TURKCELL DAHİLİ
Worst Cells - Average Throughput
Observability of throughput measurements on cell level are
split into RB specific measures (HSDPA/EUL/R99).
Average Throughput : DCH/FACH Average Throughput kbit/s

P int DCH _ I _ TF ( RncFunctio n) 
 pmSentPacketData2( RncFunction)  
8  1000   
 pmSentPacketData3( RncFunction )  pmSentPacketData 4( RncFunction ) 
 pmTotalPac ketDuration 2( RncFunction)  
 
 pmTotalPac ketDuration3( RncFunction)  pmTotalPac ketDuration 4( RncFunction 
Average Throughput : HS Average Throughput kbit/s

P int HS _ I _ TP ( RncFunctio n) 
8  1000  ( pmSentPacketDataHs3( RncFunction)  pmSentPacketDataHs 4( RncFunction))

( pmTotalPac ketDurationHs3( RncFunction)  pmTotalPac ketDurationHs 4( RncFunction))
TURKCELL DAHİLİ
Worst Cells - Average Throughput
######################################################################################################################
MO Class Pm Counter Type Flags
######################################################################################################################
RncFunction pmSentPacketData1 long PEG,ropReset
RncFunction pmSentPacketDataHs1 long PEG,ropReset
RncFunction pmSentPacketDataInclRetrans1 long PEG,ropReset
RncFunction pmSentPacketDataInclRetransHs1 long PEG,ropReset

TURKCELL DAHİLİ
HS Data Retransmission Rate

TURKCELL DAHİLİ
Optima – Throughput

TURKCELL DAHİLİ
• PS_INT_R99_AVG_THR : R99 RLC Throughput Değeri

• PS_INT_HS_AVG_THR : HSDPA RLC Throughput Değeri
• PS_INT_R99_DL_LATENCYY (ms) : R99 Latency Değeri
• PS_INT_HS_DL_LATENCYY (ms): HSDPA Latency Değeri

TURKCELL DAHİLİ
Worst Cells – Average User
Throughput DCH/FACH
DCH/FACH User Throughput, Downlink (kbit/s )
pmSumDchDlRlcUserPacketThp (UtranCell )
P int DCH _ I _ D(Tp _ User (UtranCell ) 
pmSamplesDchDlRlcUserPacketThp (UtranCell )
DCH/FACH User Throughput, Uplink (kbit/s )
pmSumDchUlRlcUserPacketThp (UtranCell )
P int DCH _ I _ UlTp _ User (UtranCell ) 
pmSamplesDchUlRlcUserPacketThp (UtranCell )

TURKCELL DAHİLİ
Worst Cells – Average User
Throughput HS/EUL
HS User Throughput, Downlink (kbit/s )
pmSumHsDlRlcUserPacketThp (UtranCell )
P int HS _ I _ DlTp _ User (UtranCell ) 
pmSamplesHsDlRlcUserPacketThp (UtranCell )
EUL User Throughput, Uplink (kbit/s )
pmSumEulRlcUserPacketThp (UtranCell )
P int EUL _ I _ UITp _ User (UtranCell ) 
pmSamplesEulRlcUserP acketThp (UtranCell )

TURKCELL DAHİLİ
HS User vs Total Throughput

TURKCELL DAHİLİ
EUL User vs Total Throughput

TURKCELL DAHİLİ
HS/EUL Data RLC Net T’put

TURKCELL DAHİLİ

TURKCELL DAHİLİ
• PS_INT_R99_DL_USER_THR
• PS_INT_R99_UL_USER_THR
• PS_INT_HS_DL_USER_THR
• PS_INT_EUL_UL_USER_THR
• PS_INT_R99_DL_DATA_MBYTE
• PS_INT_R99_UL_DATA_MBYTE
• PS_INT_HS_DL_DATA_MBYTE
• PS_INT_EUL_UL_DATA_MBYTE_WO_MD
• PS_INT_EUL_UL_DATA_MBYTE_W_MD
• CH_DWNSWITCH_SUC_PC
• CH_UPSWITCH_SUC_PC
TURKCELL DAHİLİ
Optima – Throughput Ölçüm Farkları
RNC
•pmSentPacketDatax: Accumulated amount of user data transmitted on the downlink. The counter
accumulates the amount of RLC user data transmitted, excluding retransmissions and RLC header.
Incremented when PS interactive user data is transmitted
•pmTotalPacketDurationx: Accumulated time that data has been transmitted
Cell
•pmSamplesDchDlRlcUserPacketThp: Incremented by one when the corresponding sum counter is

incremented. This counter is incremented separately for each active Packet Interactive (RAB) connection,
but is not stepped when the corresponding sum counter is not stepped because the throughput is 0 kbps.
•pmSumDchDlRlcUserPacketThp : Sum of all sample values recorded during a ROP for downlink user
RLC throughput for PS Interactive on R99 DCH. Incremented in the best cell in the active set.
The user RLC throughput includes user data but excludes retransmissions, padding bits, data PDU
headers and RLC control PDUs.
Condition: Values are read periodically from an internal level counter and added to this counter.
The level counter maintains the current downlink RLC throughput for PS Interactive on R99 DCH, including
user data only.
This counter is incremented separately for each active Packet Interactive (RAB) connection, but is not
incremented when the throughput is 0 kbps. For a multi-RAB combination containing more than one PS
Interactive RB, this counter is incremented for only one of the R99 PS Interactive RBs in the combination.

TURKCELL DAHİLİ
Channel type switching
Prio 1 Prio 2 Prio 3
384 / HS
EUL / HSDPA DCH / HSDPA DCH/ DCH

EUL / HS DCH / DCH
64 / HS
Down
FACH Throughput
Up Inactivity
Buffersize Coverage
Activity URA Mobility
Idle

TURKCELL DAHİLİ
Channel type switching

TURKCELL DAHİLİ
Channel Type Switching
The URA_PCH state is not an idle state.
By introducing this state the RRC request in the system will

decrease so in order to check the accessability rate for PS data
this formula can be used:
pmChSwitchSuccessUraFach
100 
pmChSwitchAttemptUraFach

TURKCELL DAHİLİ
The buffer load is defined as the minimum of the Radio Link Control (RLC)
transmission window and the sum of bytes in the SDU buffers and
retransmission buffers of some of the RLC instances.
UL RLC buffer load > ulRlcBufUpswitch, a measurement report is sent

from the UE.
DL RLC buffer load (in the RNC) > dlRlcBufUpswitch.
The success rate for

upswitch the HSDPA
pmDlUpswitchSuccess  Rate  The success rate for

100  upswitching from one DCH
pmDlUpswitchAttempt  Rate  channel to another

TURKCELL DAHİLİ
All counters:
###################################################################################################################################
MO Class Pm Counter Type Flags
###################################################################################################################################
UtranCell pmChSwitchAttemptDchUra long PEG,ropReset
UtranCell pmChSwitchAttemptEulUra long PEG,ropReset
UtranCell pmChSwitchAttemptFachUra long PEG,ropReset
UtranCell pmChSwitchAttemptHsUra long PEG,ropReset
UtranCell pmChSwitchAttemptUraDch long PEG,ropReset
UtranCell pmChSwitchAttemptUraEul long PEG,ropReset
UtranCell pmChSwitchAttemptUraFach long PEG,ropReset
UtranCell pmChSwitchAttemptUraHs long PEG,ropReset
UtranCell pmChSwitchFachIdle long PEG,ropReset
UtranCell pmChSwitchSuccDchUra long PEG,ropReset
UtranCell pmChSwitchSuccEulUra long PEG,ropReset
UtranCell pmChSwitchSuccFachUra long PEG,ropReset
UtranCell pmChSwitchSuccHsUra long PEG,ropReset
UtranCell pmChSwitchSuccUraDch long PEG,ropReset
UtranCell pmChSwitchSuccUraEul long PEG,ropReset
UtranCell pmChSwitchSuccUraFach long PEG,ropReset
UtranCell pmChSwitchSuccUraHs long PEG,ropReset
UtranCell pmDlUpswitchAttemptHigh long PEG,ropReset
UtranCell pmDlUpswitchAttemptHs long PEG,ropReset
UtranCell pmDlUpswitchAttemptLow long PEG,ropReset
UtranCell pmDlUpswitchAttemptMedium long PEG,ropReset
UtranCell pmDlUpswitchSuccessHigh long PEG,ropReset
UtranCell pmDlUpswitchSuccessHs long PEG,ropReset
UtranCell pmDlUpswitchSuccessLow long PEG,ropReset
UtranCell pmDlUpswitchSuccessMedium long PEG,ropReset
UtranCell pmDownSwitchAttempt long PEG,ropReset
UtranCell pmDownSwitchSuccess long PEG,ropReset
UtranCell pmUlUpswitchAttemptEul long PEG,ropReset
UtranCell pmUlUpswitchAttemptHigh long PEG,ropReset
UtranCell pmUlUpswitchAttemptLow long PEG,ropReset
UtranCell pmUlUpswitchAttemptMedium long PEG,ropReset
UtranCell pmUlUpswitchSuccessEul long PEG,ropReset
UtranCell pmUlUpswitchSuccessHigh long PEG,ropReset
UtranCell pmUlUpswitchSuccessLow long PEG,ropReset
UtranCell pmUlUpswitchSuccessMedium long PEG,ropReset
UtranCell pmUpswitchFachHsAttempt long PEG,ropReset
UtranCell pmUpswitchFachHsSuccess long PEG,ropReset

DOWNSWITCH TURKCELL DAHİLİ
Downswitch optimize the usage of the RAN resources for the packet interactive RABs. The
RAN system will monitor the throughput and if the user/application reduces the data rate, a
down switch to radio bearer with a lower rate will occur if the lower rate is sufficient to satisfy the
needs of the user
Downswitch due to:

64/384 128/384 384/384
Coverage
Capacity
Inactivity 64/128 128/128 384/128
Throughput
64/64 128/64 384/64
Benefit:
Optimise resource to the momentary needs
More efficient use of network capacity
TURKCELL DAHİLİ
DL Code Power Coverage Related Channel Switching
The DL Code Power Coverage Triggered Downswitch evaluation algorithm monitors the code power use
in the DL.
If the code power increases so that a switch to a lower rate transport channel on the DL is required
because of insufficient coverage, a downswitch request is sent to the Channel Switching execution
function. The goal is to minimize dropping because of bad link quality.
When DL transmitted code power increases too close to its maximum possible value on the current
transport channel, there is a risk that the link quality cannot be maintained. In this situation, a user
must be switched down to a lower rate to decrease the needed DL transmitted code power. The
function controls that no user is using a rate in an area where there is risk for no coverage of that
particular rate. Therefore, it is important that the mapping for maximum DL power is tuned so that
the desired coverage is achieved.
The algorithm monitors the DL-transmitted code power of all radio links in the active set and the
code power is then filtered by each RBS in the active set.
A downswitch request is issued when all handover radio links use a power above the power alarm
threshold
The power alarm threshold is defined by the downswitchPwrMargin parameter. If the transmitted
DL code power falls below the power alarm threshold while the timer (coverageTimer parameter)
runs, the request is canceled and no downswitch is executed. Once triggered, the downswitch request
is repeated at an interval specified by the repeatTimer parameter as long as the downswitch
condition is still satisfied.
TURKCELL DAHİLİ
DL Code Power Coverage Related Channel Switching

TURKCELL DAHİLİ
Capacity Related Channel Switching
The idea:
Congestion control is used to resolve overload in both the uplink and the downlink.
It uses Power and RSSI (Received Signal Strength Indicator) measurements.
In case of overload, congestion control
1. reduces bit rates of delay tolerant (non-guaranteed) existing connections down

to common channels
2. as a second option, removes existing connections.
• Admission Control switches a UE from one dedicated transport channel to another

one at the next lower rate (for example, from 64/384 to 64/128 and from 64/128 to
64/64), when the resources are needed for a new UE with high priority.
• Congestion Control can switch a UE from a dedicated to a common transport channel
to resolve a congestion situation.

TURKCELL DAHİLİ
Throughput - Channel Switching
Coverage, bad
quality or RAB
not supported
by EUL can
Cell_DCH EUL/HS trigger
Upswitch downswitch to
HS, DCH or
based on Cell_DCH 384/HS FACH
throughput
Downswitch
Cell_DCH 64/HS based on
throughput or
Coverage inactivity
triggered downswitch Cell_DCH 64/384
DL
Cell_DCH 64/128 SHO can
initiate a
Soft switch if it
Cell_DCH 64/64 fails to add a
Congestion
RL
Common Dedicated
to Cell_FACH
to common
Dedicated based on
No
based on Activit UL/DL user
URA_PCH activity
buffer size y inactivity or
or activity No cong.
activity
TURKCELL DAHİLİ
Inactivity - Channel Switching
The Algorithm:
When the throughput on both the uplink and downlink is below

the threshold value (downswitchThreshold), the timer
downswitchTimer starts (when on DCH/DCH) or the timer
hsdschInactivityTimer starts (when on DCH/HS or EUL/HS).
If the throughput increases above a second threshold

(downswitchTimerThreshold) before the timer expires, the
timer is stopped and no switch is issued.

TURKCELL DAHİLİ
Optimization of the
downswitch from DCH to
common channels is a
trade-off between resource
utilization and user
throughput.
The downswitchThreshold parameter determine how the radio access

network should behave in the end of a TCP transmission.

TURKCELL DAHİLİ
************************************************************************************************************************************
ChannelSwitching downswitchTimer long
------------------------------------------------------------------------------------------------------------------------------------
Time after which a connection with low throughput is switched down from a dedicated channel to FACH/RACH.
Once the throughput on both the uplink and downlink has fallen below the value of downswitchThreshold, the RNC normally requests a downswitch to FACH/RACH after this length of time. If
CELL_FACH state is not available, the connection is switched down to IDLE state. However, the downswitch is not requested if the throughput has subsequently increased above the value
of downswitchTimerThreshold.
It is recommended after setting this value to ensure that dlThroughputDownswitchTimer > downswitchTimer, ulThroughputDownswitchTimer > downswitchTimer and
ulThroughputDownswitchTimer > hsdschInactivityTimer. This ensures that, when the throughput is very low on both the uplink and the downlink, the user will be switched down to FACH
rather than to DCH with a lower rate.
0 disables traffic-volume-initiated channel-switching from dedicated channel to FACH/RACH.
If RncFeature=InactivityTimerCellConfig is activated, the value of UtranCell::downswitchTimer may override this value in some cells.
Resolution: 5
Change takes effect: New connections
Unit: 0.1 s
Range: 0 to 1000, Default=10
************************************************************************************************************************************
ChannelSwitching downswitchTimerSp long
------------------------------------------------------------------------------------------------------------------------------------
Time after which a connection is switched down to Multi-RAB SP0 ("Speech 12.2 kbps + Packet 0/0 kbps") if no PS data has been transmitted, either from a "Speech 12.2 kbps + Packet
64/64 kbps" multi-RAB, or if the feature InactivityTimerCellConfig is activated, from a multi-RAB consisting of Speech with a single PS Interactive on HSDPA.
If the feature InactivityTimerCellConfig is deactivated, the value of ChannelSwitching::hsdschInactivityTimer is used instead to specify the time after which a multi-RAB consisting of Speech
with a single PS Interactive on HSDPA is switched down to Multi-RAB SP0, if no PS data has been transmitted.
If Multi-RAB SP0 (feature RabCombination009) is deactivated, the packet part of the connection is released instead.
The default value setting for this attribute is based on packet performance criteria. However, the actual value setting may need to deviate from the default value in order to limit the number
of simultaneous multi-RAB connections in the RBS, typically to deal with limitations in the transport network.
Special values:
0 turns off the use of this timer, meaning that the packet part of the connection will not be downswitched or released due to PS inactivity.
Value mapping:
1 : 0.5 s
...
60 : 30 s
...
180 : 90 s
Unit: 0.5 s
************************************************************************************************************************************
ChannelSwitching downswitchTimerThreshold long
------------------------------------------------------------------------------------------------------------------------------------
Throughput threshold used to achieve hysteresis for downswitching from dedicated channel to FACH/RACH.
Once the throughput on both the uplink and downlink has fallen below the value of downswitchThreshold, a downswitch to FACH/RACH is normally requested after the length of time set in
downswitchTimer. However, the downswitch is not requested if the throughput has subsequently increased above this threshold value.
Dependencies: downswitchTimerThreshold >= downswitchThreshold
Unit: kbps

TURKCELL DAHİLİ
Channel rate switching
The channel switching 384 / HS
feature use the total EUL / HSDPA DCH / HSDPA
throughput, i.e. throughput EUL / HS
64 / HS
including the
retransmissions, when
determine if a rate switching
should occur.
64/384 128/384 384/384

pmDownSwitchSuccess
100 
pmDownSwitchAttempt
64/128 128/128 384/128
64/64 128/64 384/64

TURKCELL DAHİLİ
Optima - Channel rate switching

TURKCELL DAHİLİ
• FACH->idle : FACH : Idle geçişi olan bağlantı sayısı

• Downswitch SR : Downswitch Başarı Oranı
• Upswitch Fail FACH->HS: FACH HS geçişindeki başarı oranı
• Upswitch Fail FACH->DCH : FACH DCH geçişindeki başarı oranı
• DL Upswitch Fail DCH->DCH : Downlink yönünde DCHDCH geçişindeki başarı oranı
• UL Upswitch Fail DCH->DCH : Uplink yönünde DCHDCH geçişindeki başarı oranı
• Upswitch Fail DCH->HS,DL Trig : DCH  HS geçişindeki başarı oranı
• Upswitch Fail DCH->EUL,UL Trig : DCH  HSUPA geçişindeki başarı oranı

TURKCELL DAHİLİ
• Upswitch Fail DCH->HS,DL Trig : DCH  HS geçişi
• Kaynak yetersizliği nedeniyle HS destekli terminale R99 verilmişse

• Terminal Compressed Mode’da HSDPA desteklemiyorsa
• Upswitch Fail DCH->EUL,UL Trig : DCH  HSUPA geçişi
• Kaynak yetersizliği nedeniyle HS destekli terminale R99 verilmişse

• Terminal Compressed Mode’da HSDPA desteklemiyorsa

TURKCELL DAHİLİ

TURKCELL DAHİLİ
Throughput based Downswitch
DL
throughput
Next lower rate
dlDownswitchBandwidth
Margin e.g. 80%
dlThroughputDownswit
chTimer
Downswith
request executed

TURKCELL DAHİLİ
Throughput based Downswitch
The CELL_DCH to CELL_DCH Downswitch evaluation algorithm determines whether a switch to
a lower rate channel is made.
The same algorithm applies both to Single RABs and Multi-RABs.
The algorithm monitors UL and DL throughput separately.
A channel switch request to the next lower UL-rate radio bearer (UL triggered) or to the next
lower DL-rate radio bearer (DL triggered) is issued in the following situation:
DL throughput decreases below the threshold specified by the

dlDownswitchBandwidthMargin parameter or UL throughput decreases below the
threshold specified by the ulDownswitchBandwidthMargin parameter.
If the above condition holds for the duration of a downswitch timer, a downswitch request is
executed by the Channel Switching function. The downswitch timer is specified by the
dlThroughputDownswitchTimer parameter for a DL trigger and
ulThroughputDownswitchTimer parameter for a UL trigger.
If the dlDownswitchBandwidthMargin parameter is set to 0 or the

ulDownswitchBandwidthMargin parameter is set to 0, CELL_DCH to CELL_DCH Downswitch
evaluation is turned off for DL or UL respectively.

TURKCELL DAHİLİ
T’put Based Channel Upswitch
Monitored Measurements for Upswitch
The algorithm monitors the UL and the DL throughput separately.
A channel switch request to a higher UL-rate radio bearer (UL triggered) or to a higher DL-rate radio
bearer (DL triggered) is issued if all of the following conditions are fulfilled:
•DL throughput increases above the threshold specified by the bandwidthMargin parameter or UL
throughput increases above the threshold specified by the bandwidthMarginUl parameter.
•For a trigger on the DL, the transmitted code power consumption on the current rate is below the
power upswitch threshold for all radio links in the active set. This condition applies only if current rate
is equal to or higher than the threshold specified by the dlPrefRate parameter.
•The Maximum Bit Rate (MBR) capability for QoS profiling does not indicate that the current rate is
the MBR for the connection.
•After a throughput-based downswitch, DL throughput has fallen below the threshold specified by the
dlThroughputAllowUpswitchThreshold parameter or UL throughput has fallen below the threshold
specified by the ulThroughputAllowUpswitchThreshold parameter.

TURKCELL DAHİLİ
Timers for Upswitch Evaluation
Upswitch requests are issued when the upswitch conditions hold for the duration of upswitch
timers, as specified by the upswitchTimer parameter in the DL and the upswitchTimerUl
parameter in the UL.
An upswitch request is executed by the Channel Switching function after querying Admission
Control, which must grant admission for each radio link in the active set.
If the upswitch request is denied, the value of the corresponding upswitch timer is doubled and
the algorithm is restarted. A new upswitch request is made if the upswitch conditions still hold
when the new upswitch timer expires. To avoid excessive delay, the maximum value of the
upswitch timers is limited to 10 seconds (hard coded).
Note: If the original timer is set to a value larger than 10 seconds, the value is not modified
between successive requests.

TURKCELL DAHİLİ
Throughput and Code Power Threshold Parameters for Upswitch Evaluation
Upswitch requests are issued when the upswitch conditions hold for the duration of upswitch
timers, as specified by the upswitchTimer parameter in the DL and the upswitchTimerUl
parameter in the UL.
An upswitch request is executed by the Channel Switching function after querying Admission
Control, which must grant admission for each radio link in the active set.
If the upswitch request is denied, the value of the corresponding upswitch timer is doubled and
the algorithm is restarted. A new upswitch request is made if the upswitch conditions still hold
when the new upswitch timer expires. To avoid excessive delay, the maximum value of the
upswitch timers is limited to 10 seconds (hard coded).
Note: If the original timer is set to a value larger than 10 seconds, the value is not modified
between successive requests.

TURKCELL DAHİLİ
The algorithm applies both for Single RAB and for Multi RAB. The
algorithm monitors the UL and the DL throughput separately :
•DL throughput >bandwidthMargin or

•UL throughput > bandwidthMarginUl.
•DL throughput < dlThroughputAllowUpswitchThreshold or

•UL throughput < ulThroughputAllowUpswitchThreshold
•(Max allowed code power) – (Current transmitted code power + estimated increase in
power) > upswitchPwrMargin + downswitchPwrMargin.
•The maximum bitrate capability for QoS profiling < maximum bitrate for
the user.

TURKCELL DAHİLİ
###################################################################################################################
#################
MO Class Attribute Type Flags
###################################################################################################################
#################
ChannelSwitching bandwidthMargin long
------------------------------------------------------------------------------------------------------------------------------------
Throughput threshold for triggering an upswitch of a downlink radio bearer on DCH to a higher DCH rate. Expressed relative to the maximum
allowed rate for the currently allocated radio bearer.
When the downlink throughput has been above this threshold for the length of time defined by upswitchTimer, an upswitch from DCH to a higher
DCH rate is normally requested. However, the upswitch is not requested after a throughput-based downswitch unless the downlink throughput
has fallen below the value of dlThroughputAllowUpswitchThreshold at least once since the downswitch. The upswitch is also not requested if it
would cause the transmitted power to become too high, as defined using upswitchPwrMargin.
Special values:
0 is used to turn off the use of this threshold, meaning that an upswitch will never take place, regardless of user throughput.
Dependencies: If dlThroughputAllowUpswitchThreshold = 0, no extra restriction applies to upswitches in the downlink after a throughput-based
downswitch.
Unit: %
************************************************************************************************************************************
ChannelSwitching bandwidthMarginUl long
------------------------------------------------------------------------------------------------------------------------------------
Throughput threshold for triggering an upswitch of an uplink radio bearer on DCH to a higher DCH rate. Expressed relative to the maximum
allowed rate for the currently allocated radio bearer.
When the uplink throughput has been above this threshold for the length of time defined by upswitchTimerUl, an upswitch from DCH to a higher
DCH rate is normally requested. However, the upswitch is not requested after a throughput-based downswitch unless the uplink throughput has
fallen below the value of ulThroughputAllowUpswitchThreshold at least once since the downswitch. The upswitch is also not requested if it
would cause the transmitted power to become too high, as defined using upswitchPwrMargin.
Special values:
0 is used to turn off the use of this threshold, meaning that an upswitch will never take place, regardless of user throughput.
Dependencies: If ulThroughputAllowUpswitchThreshold = 0, no extra restriction applies to upswitches in the uplink after a throughput-based
downswitch.
Unit: %

TURKCELL DAHİLİ
######################################################################################################
##############################
MO Class Attribute Type Flags
######################################################################################################
##############################
ChannelSwitching dlThroughputAllowUpswitchThreshold long
------------------------------------------------------------------------------------------------------------------------------------
Throughput threshold for allowing an upswitch in the downlink after a throughput-based downswitch. Expressed relative to the
maximum allowed rate for the currently allocated radio bearer (the rate to which the UE has been downswitched).
After a throughput-based downswitch, upswitches are prohibited until the downlink throughput has fallen below this threshold at
least once.
Special values:
0 is used to turn off the use of this threshold, meaning that no extra restriction applies to upswitches in the downlink after a
throughput-based downswitch.
Unit: %
************************************************************************************************************************************
ChannelSwitching ulThroughputAllowUpswitchThreshold long
------------------------------------------------------------------------------------------------------------------------------------
Throughput threshold for allowing an upswitch in the uplink after a throughput-based downswitch. Expressed relative to the
maximum allowed rate for the currently allocated radio bearer (the rate to which the UE has been downswitched).
After a throughput-based downswitch, upswitches are prohibited until the uplink throughput has fallen below this threshold at
least once.
Special values:
0 is used to turn off the use of this threshold, meaning that no extra restriction applies to upswitches in the uplink after a
throughput-based downswitch.
Unit: %
************************************************************************************************************************************

TURKCELL DAHİLİ
Before issuing an upswitch request for the DL, the Channel Switching feature evaluates if the code power is sufficient to
support the transport channel with the higher rate.
The required code power for the upswitch is estimated by scaling up code power measured on the current transport
channel according to the relative rate difference between the current rate and the higher one, as shown in Figure.
The coverage test is passed if the resulting power is at least (downswitchPwrMargin+ upswitchPwrMargin) dB below the
maximum code power for the higher rate.
For example, an upswitch from 64 to 128 kbps in the default setting requires roughly a power margin of 3 dB (from power
scaling) + 1 dB (downswitchPowerMargin) + 3 dB (upswitchPowerMargin), that is, a total of 7 dB.

TURKCELL DAHİLİ
HSDPA SCHEDULER
AND TFRC SELECTION
TURKCELL DAHİLİ
HSDPA
 Shared channel transmission (dynamically in time and code)
 Higher order modulation (QSPK and 16QAM).
 Short transmission time interval (TTI = 2ms)
 Fast Link adaption (adjusting to multi path fading, path loss).
 Fast scheduling
 Fast hybrid automatic-repeat-request (ARQ)

(retransmissions in the RBS)

TURKCELL DAHİLİ
HSDPA CHANNEL STRUCTURE

› HS-DSCH - High-Speed Downlink Shared Channel
› HS-PDSCH - High-Speed Physical Downlink Shared Channel
› HS-SCCH - High-Speed Shared Control Channel(s)
› HS-DPCCH - High-Speed Dedicated Physical Control Channel
› A-DCH (DPDCH+DPCCH) - Associated Dedicated Channel

TURKCELL DAHİLİ
TECHNIQUES FOR HSDPA

TURKCELL DAHİLİ
DYNAMIC POWER ALLOCATION

TURKCELL DAHİLİ
FAST LINK ADAPTATION

Link adaptation: power control
Fast rate switching
› Adjust transmission parameters to match instantaneous Bad channel Good channel

channel conditions conditions conditions
 
more power less power
› Path loss and shadowing
› Interference variations
› Fast multi-path fading
rate adaptation
› Bit Energy = Power  1/(data rate)
› HS-DSCH: Rate control (constant power)

Bad channel Good channel
› Adaptive coding (R = 1/3 – 1) conditions conditions
› Adaptive modulation (QPSK, 16QAM, or 64QAM)  
low data rate high data rate
› Adapt on 2 ms TTI basis  fast
› Release 99: Power control (constant rate)

TURKCELL DAHİLİ
SHARED CHANNEL TRANSMISSION

TURKCELL DAHİLİ
DYNAMIC CODE ALLOCATION

TURKCELL DAHİLİ
HS CODE RESOURCE

TURKCELL DAHİLİ
CODE MULTIPLEXING
› Code multiplexing increases the number of HS users and the
cell throughput
› In one HS-DSCH TTI 1,2,3 or 4 UEs may be code

multiplexed
› If the amount of R99 users high enough in the same carrier,

then no code multiplexing can be done
2ms TTI
› 1st scheduled UE capability >= maxNumHsPdschCodes ->
no code multiplexing can be done User #1 User #2
› Enabled for operator to configure number of HS-SCCH

codes for a cell (if Code Multiplexing is activated)
› numHsScchCodes:
› value range 1….4

TURKCELL DAHİLİ
RLC PDU SIZE

TURKCELL DAHİLİ
PROTOCOL STACKS FOR THE HS-DSCH
USER PLANE
› Protocols and functions involved in HSDPA user plane
are as follows:

TURKCELL DAHİLİ
HS-DSCH MAX. ACHIEVABLE BIT

RATE
 Maximum achievable HS-DSCH bit rate depends on:
– Available HS-PDSCH power
– Radio conditions (radio channel type, interference, UE speed,
etc.)
– UE HS-DSCH category
– Available number of HS-PDSCH codes
– 16QAM availability
– 64QAM availability
– Enhanced Layer 2 availability

TURKCELL DAHİLİ
HS-DSCH MAX. ACHIEVABLE BIT
RATE
 The RLC PDU size for HS-DSCH transmission is either flexible or fixed to
336 bits or 656 bits.
 Transmission Time Interval (TTI) of the HS-DSCH is 2 ms.
 The minimum number of HS-PDSCH codes used for transmission is

controlled by the parameter numHsPdschCodes.
 The maximum number of HS-PDSCH codes is 15.
 Together with 16QAM modulation and a fixed RLC PDU size of 656 bits,
the number of payload bits that are possible to transmit in a single TTI is
26880, corresponding to a bit rate of 13.4 Mbps at the RLC payload level.
 Together with 64QAM modulation and flexible RLC PDU size, the
corresponding bit rate is 20.8 Mbps at the RLC payload level.

TURKCELL DAHİLİ
MAC-d PDU SIZE

 MAC-d PDU Size = RLC payload size + RLC header + MAC header
 MAC-d PDU Size = 320+16+0 = 336, OR

 MAC-d PDU Size = 640+16+0 = 656 bits.
 With a 336-bit MAC-d PDU size, user bit rates above 6Mbps cannot be
supported.
 Category 7-10 and 13-20 UEs support 656-bit PDU sizes.
 If codeThresholdPdu656 < numHsPdschCodes => 656-bit RLC PDU sizes

will be used for Category 7-10 and 13-20 UEs.
 With Enhanced Layer 2:

– The PDU size is flexible
– More than one PQ can be multiplexed for one UE.

TURKCELL DAHİLİ
HSDPA SCHEDULER
 Scheduling = which UE to transmit to at a given time instant and
at what rate
– Formally part of MAC-hs (layer 2)
 Basic idea: transmit at fading peaks

– May lead to large variations in data rate between users
– Tradeoff: fairness vs cell throughput

TURKCELL DAHİLİ
RESOURCE ESTIMATION
 Resource estimation procedure estimates available HS-PDSCH codes and HS-
PDSCH power in the upcoming TTI.
 Total power available for all the HSDPA channels and the Enhanced Uplink
downlink channels, P_HS, is estimated as:
– P_HS = P_max – P_nonHS – hsPowerMargin [dB]
– P_max : maximumTransmissionPower
– P_nonHS : Total transmitted carrier power of all codes not used for HS-PDSCH,
HS-
SCCH, E-HICH, E-RGCH and E-AGCH transmission, i.e. the total power of all
dedicated and common channels.
 Based on the P_HS estimate, the total power available for the HS-PDSCH,
P_HSPDSCH, is estimated as:
– P_HSPDSCH = P_HS – P_HsscchPower – P_EUL [dB]
– P_HsscchPower : Code power used for the HS-SCCH
– P_EUL : Code power used for the E-HICH, E-RGCH and E-AGCH.

TURKCELL DAHİLİ
FLEXIBLE SCHEDULER
 The feature Flexible Scheduler provides the abilities to:
– Choose among the 5 possible queueSelectionAlgorithms:
 EQUAL_RATE
 MAXIMUM_CQI
 PROPORTIONAL_FAIR_HIGH
 PROPORTIONAL_FAIR_LOW
 PROPORTIONAL_FAIR_MEDIUM
 ROUND_ROBIN
– Code Multiplexing
– HS-SCCH Power Control

TURKCELL DAHİLİ
QUEUE SELECTION FACTORS

TURKCELL DAHİLİ
REMAINING RESOURCE CHECK
 Remaining resource check algorithm checks if we have one of

the following resources left to be assigned to another user at
the same TTI:
– HS-SSCH codes
– HS-PDSCH codes
– Remaining HS power (P_HS)

TURKCELL DAHİLİ
TFRC SELECTION
 HSDPA Scheduler defines:
– Which UE should transmit in that TTI
– Available HS-PDSCH transmission power
– Available number of HS-PDSCH codes
 With HSDPA Scheduler algorithm’s outputs, the MAC-hs / MAC-ehs

TFRC selection algorithm defines:
– Transport Block Size
– Modulation Type
– Number of HS-PDSCH Codes
– HS-PDSCH Transmission Power
 CQI is used for scheduling to select the PQ of highest CQI reported.

However, it is also used by TFRC selection algorithm to define the bit
rate.

TURKCELL DAHİLİ
Optimizing HSDPA
 SW and HW preparations such as new sites, new
carriers, new transmissions solutions and new SW
versions in all NE.
 Review radio parameter settings. There will be a major

impact on the power parameter settings
 System Interference
 Handover performance, the network must have well

confined HO areas.
 System Load - The DL Load is here measured as the

percentage of used DL Power compared to the
available one. pmTransmittedCarrierPower
Optimizing HSDPA – Power
TURKCELL DAHİLİ
performance
HSDPA will take whatever power that is left in RBS after
common channels and dedicated channels has taken their
part. The average power utilization in the network will increase
with HSDPA.
Power
Max cell power Power of the Common Channels, e.g.
CPICH and SCH should be increased and
HSDPA power verified. This because with 100% cell load
Admission control threshold the common channels should remain their
quality.
DCH power Max power of the DCH (other RABs)

should be increased and verified. The
DCH channel should remain their quality in
CCH power the cell border, where they are using their
max power.
time

Optimizing Power performance - Hints
TURKCELL DAHİLİ
In areas with poor coverage it is possible to increase the

success of the random access procedure by maximizing the
number of transmitted preambles.
Set parameter powerOffsetP0 to 1 dB,

preambleRetransMax to 32, and maxPreambleCycle to 32.
They ensure that the UE transmits the maximum number of

preambles before aborting the attempt, thus ensuring
maximum detection probability in the RBS.
Tests have shown that the coverage improvement with this

setting is in the order of 1 - 3 dB.

HSDPA Throughput Concepts
TURKCELL DAHİLİ
The throughput for HSDPA can be divided in different categories:
Application throughput is defined as TCP/IP to end-to-end throughput. It is

the net payload throughput and is considered to be error free. It is
measured every second.
Physical Served Throughput is defined as the Layer 1 throughput that

includes all received transport blocks, including error blocks.
MAC-HS Throughput is defined as the Layer 2 throughput that includes all

received acknowledge transport blocks, excluding error blocks. It is
measured every 200 millisecond.
Radio Link Control (RLC) Throughput is defined as the Layer 2

throughput that includes all PDU and SDU. It is measured every 3rd
second.

TURKCELL DAHİLİ
HSDPA Throughput Concepts

TURKCELL DAHİLİ
HSDPA Throughput Counters
pmSumAckedBits is the number of MAC-hs bits received and
acknowledged by the UE
pmSumTransmittedBits is the number of transmitted bits at MAC-

hs level including retransmissions
pmNoActiveSubFrames is the number of subframes containing

high speed data transmitted by the RBS
pmNoInactiveRequiredSubFrames is the number of empty

subframes transmitted even though data is scheduled for priority
queue
pmSumNonEmptyUserBuffers is the number of user buffers

containing high speed data

TURKCELL DAHİLİ
HSDPA Throughput
The throughput for HSDPA is calculated differently from the other RAB due
to the MAC-HS.
Average HS cell throughput can be obtained on DSCH level:

pmSumAckedBits
ROPperiod
The Average Scheduled Cell throughput on MAC-hs level (when data is being
transmitted):
pmSumAckedBits
TTI pmNoActiveSubFrame
The Average Scheduled Cell throughput on MAC-hs level (when there is data to
transmit in the buffer):
pmSumAckedBits
0.002*(pmNoActiveSubFrames  pmNoInactiveRequired SubFrame)

TURKCELL DAHİLİ
HSDPA Throughput
The throughput for HSDPA is calculated differently from the other RAB due
to the MAC-HS.
Average net user throughput with no retransmissions can be obtained on

DSCH level:
pmSumAckedBits
TTI  pmSumNonEmptyUserBuffers
Average gross user throughput with no retransmissions can be

obtained on DSCH level:
pmSumTrans mittedBits
0.002*pmSumNonEmptyUserBuffers

TURKCELL DAHİLİ
HSDPA Throughput considerations
The scheduled throughput. This is mainly related to coverage and available
power for HSDPA.
The percentage of TTIs that the channel is available but there is data in the
buffer. This could be problems with decoding CQI or ACK or that the A-DCH
is not synchronized.
The percentage of TTIs that the UE has something n the buffer. This is
mainly due to TCP effects.

TURKCELL DAHİLİ
HSDPA Throughput efficiency
considerations

TURKCELL DAHİLİ
The scheduling ratio

% of time the HS-DSCH is in use:
TTI x pmNoActiveSubFrame
100 x
ROPperiod
The transmission ratio

% of time there is something to transmit:
TTI x pmNoActiveSubFrame  pmNoInactiveRequiredSubFrame

100 x
ROPperiod

TURKCELL DAHİLİ
The MAC transmission efficiency - HS-DSCH is in use
pmNoActiveSubFrame
100 x
pmNoActiveSubFrame  pmNoInavtive RequiredSubFrame
Average number of UE in the queue when HS is transmitting
pmSumNonEmptyUserBuffers
100 x
pmNoActiveSubFrame  pmNoInavtive RequiredSubFrame

TURKCELL DAHİLİ
HSDPA MAC-Hs BLER

TURKCELL DAHİLİ
HSDPA Retransmission Overhead

TURKCELL DAHİLİ
HSDPA Throughput increase
By changing the TCP
window settings in the
laptop the scheduled
throughput is almost the
same as the cell
throughput
By changing the UTRAN

parameters such as
pwrAdm the application
throughput has increased

. A Figure100
5- Service Integrity
TURKCELL DAHİLİ
Optima – HS Throughput Efficiency

. A Figure101
TURKCELL DAHİLİ
Optima – HS Throughput Efficiency

. A Figure102
TURKCELL DAHİLİ
Optima – HSDPA CQI

. A Figure103
TURKCELL DAHİLİ
Optima – CQI
USED_CQI(0-5) %
USED_CQI(6-10) %
USED_CQI(11-15) %
USED_CQI(16-20) %
USED_CQI(21-25) %
USED_CQI(26-30) %
NACK %
Retransmission %
REPORTED_CQI(0-5)%
REPORTED_CQI(6-10)%
REPORTED_CQI(11-15)%
REPORTED_CQI_64QAM(0-5)%
. A Figure104
TURKCELL DAHİLİ
HSDPA Reported CQI

. A Figure105
TURKCELL DAHİLİ
HSDPA Used CQI

. A Figure106
TURKCELL DAHİLİ
Optima – HS Code Usage

. A Figure107
TURKCELL DAHİLİ
Optima – HSDPA User Number

. A Figure108
TURKCELL DAHİLİ
HSDPA Iub Performance

. A Figure109
TURKCELL DAHİLİ
EUL SCHEDULER AND

E-TFCI SELECTION
TURKCELL DAHİLİ
EUL GENERAL PRINCIPLES

 Enhanced Uplink (EUL) is a natural complement to the High-Speed
Downlink Packet Access (HSDPA) for high-performance packet data
applications.
 EUL can also be referred as High-Speed Uplink Packet Access

(HSUPA).
 HSDPA : allocates a significant amount of transmission carrier power to

a single user.
 EUL : allows a single user to operate at very high uplink signal-to-

interference ratios.
 The uplink transport channel E-DCH allows for improved uplink

performance compared to the DCH in terms of the following:
– Reduced delays
– Increased data rates
– Increased capacity
© Ericsson AB 2010 | Ericsson Confidential | EUL Scheduler and E-TFCI Selection | 05 May 2010
© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev . A Figure111
TURKCELL DAHİLİ
TECHNIQUES FOR EUL

 Fast hybrid ARQ: The RBS can rapidly request retransmissions
of erroneously received data, which implies increased robustness
and reduced retransmission delays.
 Soft combining: Retransmissions are softly combined with

previously received copies of the retransmitted data to increase
the probability of a successful reception.
 Fast scheduling: This allows rapid resource reallocations

between UEs, exploiting the burstiness in packet data
transmissions. It also allows the system to admit a larger number
of high-data rate users and rapidly adapts to interference
variations, thereby leading to an increase in capacity as well as
an increase in the likelihood that a user will experience high data
rates.
TURKCELL DAHİLİ
DIFFERENCES BETWEEN HSDPA & EUL
TURKCELL DAHİLİ
EUL LIMITING FACTORS

 Interferance headroom
 RBS hardware
 Iub bandwidth
 UE available transmit power
 There is no limitation due to code tree shortage – each Ue has
its own code tree; hence, no need for another modulation
scheme
TURKCELL DAHİLİ
E-DCH Protocol Architecture
TURKCELL DAHİLİ
EUL DATA FLOW IN UPLINK
TURKCELL DAHİLİ
E-DCH MAX ACHIEVABLE BIT
RATE  The maximum achievable bit rate on the E-DCH depends on the following factors:
– Available power
– Radio conditions (radio channel type, interference, UE speed, etc.)
– Number of E-DCH codes
– TTI length (2 ms or 10 ms)
– Choice of transport format table
 RLC PDU size is fixed to 336 bits (320 bit payload).
 Transmission Time Interval (TTI) of the E-DCH is 2 ms or 10 ms.
 The maximum number of E-DCH codes to use is four codes: (2 x SF2 + 2 x SF4)
 2 x SF4 => 43 RLC PDUs in one 10 ms TTI => 1.376 Mbps.
 2 x SF2 + 2 x SF4 => 34 RLC PDUs in one 2 ms TTI => 5.44 Mbps.
 The maximum rate that the scheduler can grant is given by eulUeMaxRate and is
defined by:
– eulUeMaxRate = min (eulMaxAllowedSchRate, Maximum rate due UE
Capability, MBR, eulMaxShoRate if the user is in soft HO)
TURKCELL DAHİLİ
UE E-DCH CATEGORIES
TURKCELL DAHİLİ
MAC-e HARQ Protocol
TURKCELL DAHİLİ
MAC-e HARQ Protocol
TURKCELL DAHİLİ
MAC-e HARQ Protocol

 The MAC-e HARQ protocol allows up to a maximum number of HARQ transmission attempts, which can
be configured on the cell level per Mac-d flow with the parameter harqTransmUlMax.
 If the serving E-DCH cell cannot decode a MAC-e PDU after harqTransmUlMax transmission attempts, it
will send a HARQ failure indication to the SRNC, using the E-DCH frame protocol.
 # of HARQ processes = 4 , 10 ms TTI

 # of HARQ processes = 8 , 2ms TTI
 MAC-e RTT = 40 ms , 10 ms TTI
 MAC-e RTT = 16 ms , 2 ms TTI
TURKCELL DAHİLİ
EUL PHYSICAL CHANNELS
TURKCELL DAHİLİ
EUL PHYSICAL CHANNELS
TURKCELL DAHİLİ
EUL PHYSICAL CHANNELS - DL
TURKCELL DAHİLİ
EUL PHYSICAL CHANNELS - UL
TURKCELL DAHİLİ
CODE ALLOCATION OF COMMON

CHAN.S
TURKCELL DAHİLİ
EUL PARAMETERS
 eulTargetRate: The target scheduled grant for a user.
 eulLowRate: Defines an EUL scheduling grant below eulTargetRate. A user's grant
will at most be reduced to this level in a single step during overload situations.
 eulMaxAllowedSchRate: The maximum allowed scheduled data rate per user.
 eulMaxShoRate: Defines the maximum rate that may be allocated in the serving cell
for scheduled data to an E-DCH user during a soft handover.
 eulNonServHwRate: The amount of hardware resources (in terms of a bit rate) that
dynamically may be allocated to a non-serving E-DCH radio link for processing
scheduled data.
 The maximum rate that the scheduler can grant is given by eulUeMaxRate and is
defined by:
– eulUeMaxRate = min (eulMaxAllowedSchRate, Maximum rate due UE Capability, MBR,
eulMaxShoRate if the user is in soft HO)
TURKCELL DAHİLİ
EUL RATE CALCULATIONS

 At the first scheduling action, when the
scheduled grant is zero kbps, the only valid
step is to increase the scheduled grant so it
corresponds to the minimum hardware
already allocated.
 After the initial increase the scheduled rate
is increased at least to eulTargetRate.
 The increase in the scheduled rate with the
maximum step size at each consecutive
scheduling action continues until:
– There are no more resources to

schedule, or
– UE signals that it is “happy”, or
– The grant reaches the maximum
value that it is allowed for the
user, for example as determined
from the E-DCH Maximum
Bitrate (MBR) for the connection
received over NBAP.
 If the scheduled grant is below
eulTargetRate, the EUL scheduler always
tries to increase the scheduled grant to
become at least equal to eulTargetRate.
 If an overload is detected, the grant can be
reduced at most to eulLowRate.
 When the UE is inactive, the scheduled
grant is reduced first to the minimum HW
allocation and then to zero kbps.
TURKCELL DAHİLİ
EUL ACTIVITY HANDLING

 The reduction of scheduled rate due to inactivity is typically handled in two steps:
– Inactive user with a high scheduled rate is reduced quickly to a scheduled
rate corresponding to the minimum hardware allocation level.
– Inactive user with a scheduled rate already corresponding to the minimum
hardware allocation is after another short period given a scheduled rate of
zero kbps.
› If the UE is not using its scheduled grant => Grant is reduced towards the UE measured
rate (not below eulLowRate).
TURKCELL DAHİLİ
Stepping of Rate (10 ms TTI) eulInactivityHighRateTime
(200ms)
Scheduled grant
Received user rate
eulMinStepSize
(64Kbps)
Unused
resources
eulMaxStepSiz
e
(384Kbps) eulInactivityLowRateTime
(1000ms)
eulTargetRate
(128Kbps)
eulMinHwSchRate
(32Kbps)
Zero kbps
Time
“UE rate increase request” Absolute grant order to UE

TURKCELL DAHİLİ
Rescheduling
Calculated Rate Scheduled Grant
Rescheduling is possible since

UE1 could have at least eulTargetRate
Not possible since and the calculated rate for UE1<UE2
calculated rate for UE1>
calculated for rate UE2 2
eulTargetRate
1 1
eulReservedHwBandwidthSchedDataServCell – 32Kbps
TURKCELL DAHİLİ
UL Uu LOAD ESTIMATOR
TURKCELL DAHİLİ
HW LOAD ESTIMATOR
 The Enhanced Resource
Handler (ERH) is
responsible for allocating
HW for the E-DCH user.
 The scheduler checks

the uplink HW load by
comparing the total
allocated HW load with
the maximum allowed
HW load for each HW
resource pool.
TURKCELL DAHİLİ
HW LOAD ESTIMATOR
TURKCELL DAHİLİ
HW LOAD ESTIMATOR
TURKCELL DAHİLİ
EUL MAC-e Scheduled User Throughput Net
TURKCELL DAHİLİ
EUL MAC-e Scheduled User Throughput Gross
TURKCELL DAHİLİ
EUL MAC-e Scheduled Cell Throughput Net
TURKCELL DAHİLİ
Average EUL Scheduled users
TURKCELL DAHİLİ
EUL Rise Over Thermal
EUL IntraCell Noise Rise
TURKCELL DAHİLİ
EUL Waiting Time
TURKCELL DAHİLİ
EUL Iub Limiting Ratio
TURKCELL DAHİLİ
EUL Resource Monitoring
EUL Interference Limit:
EUL UL Uu Load Limit:
TURKCELL DAHİLİ
EUL Resource Monitoring
EUL UL Hardware Limit:
EUL Users Capacity Allocation Failure Rate::
TURKCELL DAHİLİ
EUL Grant Reduction Reason
TURKCELL DAHİLİ

. A Figure146

Chapter 4 WCDMA RAN Optimization - Integrity - v2

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

Chapter 4 WCDMA RAN Optimization - Integrity - v2

Uploaded by

Copyright:

Available Formats

TURKCELL DAHİLİ

WCDMA RAN Optimization

Chapter 5: Service Integrity

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

BLER counters BLER, power, Test the settings Check statistics

PmDl Traffic volume counters

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

 pmFaultyTransportBlocksBcUl These counters

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

UeRc stands for different RAB’s

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

• BLER_CS_SP: Ses Servisi için combining sonrası elde edilen BLER %

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

• R99, HS, EUL servisi After Combining sonrası BLER Dağılımı

• UL ile aynı aralıklarda DL BLER istatistikleri de verilmektedir.

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

• R99, HS, EUL servisleri için Ec/No Dağılımı

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

Soft/Softer Handover benefits

The UE and the WCDMA RAN must achieve a connection

The UE requires enough power to achieve sufficient downlink

Using Soft or Softer Handover,

DL RBS's output power can be

The Outer Loop Power Control algorithm is used to maintain

 Through performance statistics data (RNC counters) identify

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

CRC Re-Generated Checksum

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

There are two alternative

The parameter setting

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

The two configurable

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

Whenever the Cyclic

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

RAB Type TrCH Default Value

Speech 12.2 Speech -20 (1% BLER)

BLER targets is to enable the Conversational CS data 64 CS64

operator to trade quality of CS Streaming 57.6 CS57.6 -20 (1% BLER)

resource usage. PS Interactive 64/64 PS64

PS Interactive 64/128 PS128 -20 (1% BLER)

 blerQualityTargetDl SRB -20 (1% BLER)

PS Interactive 64/384 PS384 -20 (1% BLER)

 blerQualityTargetUl Speech+ PS Interactive 64/64 Speech -20 (1% BLER)

10*log (blerqualitytargetxl) PS Streaming 16/64 PS Streaming -13 (5% BLER)

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

The throughput can be expressed per session, per bearer or

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

Average Throughput : DCH/FACH Average Throughput kbit/s

Average Throughput : HS Average Throughput kbit/s

8  1000  ( pmSentPacketDataHs3( RncFunction)  pmSentPacketDataHs 4( RncFunction))

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

• PS_INT_R99_AVG_THR : R99 RLC Throughput Değeri

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev

DCH/FACH User Throughput, Uplink (kbit/s )

© Ericsson AB 2008 05_03813 LZU 108 6924 Uen Rev