Você está na página 1de 16

Nokia Siemens Networks

HSDPA Optimization Guideline for CELCOM


version 0.1
2/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

CHANGE HISTORY
Version Date Created by Comments
0.1 25.01.2008 Khoo Nee Sern, Endy First draft version
3/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

Table of Contents
1. Objective 4

2. Cluster Tuning 4
2.1 Cluster Preparation 4
2.2 Drive Test KPIs 5
2.2.1 HSDPA Throughput 5
2.2.2 RTT 5
2.2.3 HSDPA Accessibility and Drops 5
2.3 WBTS Alarm Check 5
2.4 Parameter Consistency Check 6
2.5 RF Optimization 6

3. Parameter Optimization 6
3.1 HSDPA Power 7
3.2 Iub Parameter 8
3.2.1 MaxBitRateNRTMACDFlow 8
3.2.2 SHA 8
3.2.3 SHFCA 8
3.3 HSDPA Selection and Mobility 8
3.4 HSDPA impact on R99 users 9

4. KPI Counter Monitoring 10


4.1 Capacity and Load 10
4.1.1 BTS Processing Capacity 10
4.1.2 DL spreading codes 11
4.1.3 WBTS Power 11
4.1.4 Iub Capacity 11
4.2 HSDPA Usage 13
4.2.1 Iub Data Volume and Throughput 13
4.2.2 HSDPA data volume (MAC-d) at Iub 13
4.2.3 Active HS-DSCH Mac-d throughput 13
4.2.4 HSDPA Users 13
4.3 HSDPA Performance 14
4.3.1 HSDPA Accessibility 14
4.3.2 HSDPA Retainability for NRT traffic 14
4.3.3 HSDPA Mac-hs efficiency 15
4.3.4 CQI 16
4/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

1. Objective
This document describes the optimization process for the HSDPA. The optimization process
is divided into the following categories that are separately explained:
• Cluster tuning where the purpose is to identify any poor HSDPA performance which
is caused by RF issues or neighbor planning problem. This mainly focuses on RF
optimization, especially on the hardware changes, i.e. antenna tilt and orientation,
or changes in the neighbor lists.
• Parameter optimization where the purpose is to optimize the HSDPA performance
via parameter tuning, e.g. HSDPA power, Iub parameter, etc.
• KPI counters monitoring can be further used in daily optimization to identify any
worst performance cells and troubleshoot what is the root cause of performance
degradation.

2. Cluster Tuning
Figure below shows the cluster tuning process flowchart. Cluster tuning is mainly to identify
any RF issues or missing neighbour problem. If the problem is not related to RF issues, then
it can be further optimised from parameter tuning or KPI counter troubleshooting.

Figure 1 Cluster tuning process

2.1 Cluster Preparation


Before starting any drive test campaign, the cluster area should be well prepared to ensure
minimal disruption to the data collection and subsequent troubleshooting activities. The drive
test route should cover a good percentage of main roads, motorways and different clutter
types. HSDPA is not selected during SRNC relocation when UE coming from CELL_FACH,
so we need to avoid RNC borders for HSDPA mobility.
5/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

2.2 Drive Test KPIs


Drive test KPIs are calculated after the measurement collection campaign. Among the KPIs to
be measured are:

2.2.1 HSDPA Throughput


HSDPA throughput varies due to many reasons:

• Capacity, e.g. BTS power, Iub capacity, CE


• Modulation scheme (QPSK, 16QAM)
• Scheduler type (Round Robin or Proportional Fair)
• HSDPA mobility, when mobility is disable there is a data gap during cell change
• Number of simultaneous HSDPA and R99 UE’s in the BTS/cell
• Radio condition (SINR, CQI)

The other possible reasons that HSDPA throughput may be bad because the BTS is not
scheduling sufficient data every TTI due to lack of incoming data from the RNC/core network.
This is not a radio problem, and it should be solved if more than 1 parallel FTP session is run
at the same time.

Figure 2 Scheduled TTI

2.2.2 RTT
Round Trip Time (RTT) depends upon:
• Uplink return channel bit rate and Transmission Time Interval (TTI)
• 64 kbps UL uses 20 ms TTI whereas 128 and 384 kbps UL use 10 ms TTI
• Size of the PING payload
• Core network connectivity
• the application server should be connected directly to the GGSN to minimize
the RTT
• Cell load and coverage conditions

Maximum performance can be achieved when 384kbps is allocated directly as initial bit rate
for uplink during RTT measurements.

2.2.3 HSDPA Accessibility and Drops


This refers to the number of successful HS-DSCH allocation and the number of drop calls
happen during the throughput measurement.

2.3 WBTS Alarm Check


6/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

Before drive test starts, we have to ensure that the sites in the cluster are free of any major
alarms. Alarm Check can be done with NetAct Reporting Suite Fault Management reports or
using standard NetAct GUI tools. The HSDPA related alarms are:
• 7772 PHYSICAL SHARED CHANNEL CONFIGURATION FAILED
• This alarm indicates that there has been an error when RNC has requested
configuration or reconfiguration of HSDPA channels to WBTS.
• 7776 HSDPA FAILURE IN WCEL
• Possible reason: HSDPA enabled in too many cells

2.4 Parameter Consistency Check

It is important to make sure the parameter is consistent, the following parameter consistency
checks should be done regularly:

• HSDPA power and PtxTarget thresholds


• 20W/40W/8W/ROC sites should have different power values
• Iub
• SHFA and SHA parameters according the size of VCC
• Dedicated FMCS and HOPS sets used for HSDPA
• Recommended parameters implemented
• HSDPA enabled in maximum three cells per BTS
• Alarm 7776 will be raised if more than three cell have HSDPA enabled in a
BTS

2.5 RF Optimization
HSDPA throughput depends directly on the radio channel conditions. These conditions are
changing rapidly all the time due to fast fading of the radio channel. BTS is able to change
the LA for each 2ms TTI based on the channel measurements. Average throughput in a
certain location can be estimated if the average SINR (signal to interference + noise ratio) is
known. SINR is dependent on the EcNo, RSCP and power allocation for HS-DSCH and total
WCDMA power, and orthogonality.

Benefits that can be gained with RF Optimisation to HSDPA performance:


• Improving average SINR for HS-DSCH, i.e. improving average HSDPA cell
throughput
• Well defined dominance areas reduces HS-DSCH to FACH transition for mobile
users if HSDPA mobility is disabled (RAS51)
• Well defined dominance areas improves probability to get HS-DSCH at the call setup

Therefore, it is extremely important to perform RF optimisation in areas having poor


dominance, e.g. physical change of antenna tilt, (azimuth, type and height) based on scanner
data. In general, if the optimization is done already for R99, then there is no need for separate
RF optimization for HSDPA.

3. Parameter Optimization
Many parameters for HSDPA can be optimized to improve the performance. The parameter
optimization can be categorized into few subjects:
7/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

• HSDPA throughput
➢ HSDPA power setting
➢ Iub configuration and parameter setting
• HSDPA selection and mobility
➢ HSDPA FMCS/HOPS
• HSDPA impact to R99 users
➢ HSDPA priority
➢ SHA/SHFCA parameter setting

3.1 HSDPA Power

Increasing HSDPA max power increases average HSDPA cell throughput. However, impact
on R99 users should always considered, when increasing HSDPA power. The following is the
effect of different settings of HSDPA power to the throughput.

Table 1 HSDPA Throughput vs Power

Dynamic Power Control is a feature in RAS51 that allows the user to set PtxMaxHsdpa equal
to the total power in the cell (e.g. 20W). Then the HSDPA power will be varied according to
the R99 usage in the cell and the HsdpaPriority parameter. However, increasing
PtxMaxHsdpa will possibly degrade EcNo of the R99 and affect the R99 performance.

HsdpaPriority =1

Figure 3 HSDPA has priority over NRT DCH


HsdpaPriority = 2
8/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

Figure 4 NRT DCH has priority over HSDPA

3.2 Iub Parameter


3.2.1 MaxBitRateNRTMACDFlow
This parameter defines the maximum bit rate of the MAC-d flow. For 16QAM, it should be set
as 3456kbps, and for QPSK it should be 1664kbps.

3.2.2 SHA
SharedHsdpaAllocation is ATM protocol level parameter (includes the AAL2 overhead and
ATM overhead). It defines the amount of Iub bandwidth on a VCC allocated for HSDPA traffic
only. The application throughput can be multiplied by ~1.30 to get the ATM level SHA value.

Table below shows an example of the effect of different SHA setting on 1E1 site. As the SHA
setting is higher, the achievable HSDPA throughput is higher as the AAL2 resources are
reserved in the Iub for HSDPA. Below shows some test results from Kepong test bed:

Average HSDPA Throughput (kbps)


SHA (kbps)
1 HSDPA 1 HSDPA + 1 R99 1 HSDPA + 2 R99
0 1000 690 450
0.3 1000 596 470
0.5 1000 621 550
Table 2 SHA setting

Another impact of SHA setting, especially to Iub capacity-limited sites with HSDPA enabled, is
the increase in AAL2 CAC Rejection rate, which affects to the RRC and RAB establishment
success rate, soft handover success rate, and call drop rate. Care must be taken to tune the
SHA parameter to match the available E1 configuration of the site.

3.2.3 SHFCA
SharedHsdpaFlowControlAllocation defines the maximum amount of HSDPA traffic RNC is
allowed to send to a VCC on Iub. The impact is to the Mac-d flow, therefore the conversion
rate is approximately SHFCA*0.7 = Mac-d flow on Iub.

3.3 HSDPA Selection and Mobility


9/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

Release Margin Average Ec/No , Release Margin Peak Ec/No in HSDPA HOPS can be
changed to increase HSDPA selection probability in SHO areas. Tuning AdditionTime in
HSDPA FMCS and Enable RRC Connection Release, Release Margin Average Ec/No ,
Release Margin Peak Ec/No = 3.5dB in HSDPA HOPS can reduce the amount of HS-DSCH
to FACH transitions. This would lead better average mobile HSDPA throughput.

Figure 5 HSDPA HOPS parameter

CPICH Ec/No or RSCP HHO threshold in HSDPA FMCS should not be too high, to avoid
triggering of IFHO/ISHO measurements too early for HSDPA connections.

3.4 HSDPA impact on R99 users

Maximum HSDPA power setting should be compromise between optimized HSDPA


performance and interfering effect on R99.

Figure below shows an example of the degradation of EcNo if PtxMaxHsdpa is set to 8W. In
low RF area, degraded EcNo will lead to degraded R99 throughput performance.

Figure 6 HSDPA impact on EcNo


10/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

4. KPI Counter Monitoring


In the optimization process, the performance must be continuously monitored in order to
troubleshoot for optimization steps to be carried out. The following are the main items in
HSDPA performance:
• Capacity and load
• Data Volume and Throughput
• CQI
• Mobility

4.1 Capacity and Load


It is important to ensure that there is sufficient capacity in the Node B hardware (CE), air
interface (codes, power), and the transmission (Iub) after HSDPA activation.

4.1.1 BTS Processing Capacity


Enabling HSDPA, with or without, active HSDPA users will reserve 32 CE if HSDPA is
enabled in BTS. If HSDPA is Enabled in 3 Cells it will reserve 3*32=96 CE’s (RAS5.1).

In RAS5.1, there is dedicated measurement in BTS for the channel element usage.
• M5001C0, MAX_AVAIL_CE
• M5001C2, AVE_AVAIL_CE
• M5001C3, MAX_USED_CE_DL
• M5001C4, MAX_USED_CE_UL
• M5001C7, AVG_AVAIL_CE_DL
• M5001C8, AVG_AVAIL_CE_UL

We can verify the average utilised CE against the available CE to identify any possibility of
CE blocking.

M5001C7 AVG_USED_CE_DL
RNC_730A  Average Ratio of utilised CE for DL in BTS  x100%
M5001C2 AVE_AVAIL_CE

M5001C8 AVG_USED_CE_UL
RNC_731A  Average Ratio of utilised CE for UL in BTS  x100%
M5001C2 AVE_AVAIL_CE

Below shows one of the sample of CE utilization of a site with 3WSPCs :


DL CE Utilisation

MAX_AVAIL_CE MAX_USED_CE_DL CE_Uti_DL

250 45.00%
40.00%
CE Utilisation, %

200 35.00%
30.00%
150
25.00%
20.00%
100
15.00%
50 10.00%
5.00%
0 0.00%
1/1/2008

1/2/2008

1/3/2008

1/4/2008

1/5/2008

1/6/2008

1/7/2008

1/8/2008

1/9/2008

1/10/2008

1/11/2008

1/12/2008

1/13/2008

1/14/2008

1/15/2008

1/16/2008

1/17/2008

1/18/2008

1/19/2008

1/20/2008

1/21/2008

1/22/2008

1/23/2008

1/24/2008

1/25/2008

1/26/2008

1/27/2008

Figure 7 DL CE Utilization

If there is problem due to CE capacity, it is worth to cross check RRC connection setup failure
or RAB setup failure due to BTS.
11/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

4.1.2 DL spreading codes


Enabled HSDPA will reserved together with Common Channels 45 codes (SF 128), so when
HSDPA is enabled in the cell, there are free codes left for 4 x 384 users:

Code tree occupancy:

RNC_113a 
 CODE_CAPACITY 100%
 DENOM_CODE_CAPACITY
Code blocking can be calculated from counters which are triggered when there is no code for SFx (x=4,8…256) are
available:

256

 NO _ CODES _ AVAILABLE _ SFx


x4
 100%
NBR _ SUCC _ CODE _ TREE _ ALLO 
256

 NO _ CODES _ AVAILABLE _ SFx


x4

Code tree occupancy is heavily increased due to HSDPA activation, roughly this means 36%
(together with codes for CCCH) code tree occupancy without any load. So introduction of
HSDPA increase possibility of code blcoking.

Figure 8 Code tree

4.1.3 WBTS Power


In case of WBTS Power, there are no reserved resources for HSDPA
• Power is reserved for HSDPA only when there is active HSDPA users in the cells and
HSDPA power is shared between HSDPA users. If HSDPA dynamic power allocation in
use, increased Rel99 traffic can decrease HSDPA throughput & power
• KPIs used to understand the existing total downlink transmit power
• Average total DL transmit power
• Maximum total DL transmit power
• Average non-HSDPA transmit power
• PtxTotal and PrxTotal in class (0-4) are useful to identify any cell overloading problem.

4.1.4 Iub Capacity


Iub reserved load and bandwidth can be monitored to verify the reservation of the Iub by R99
and specifically by HSDPA traffic.
12/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

Iub reservation success rate can be monitored to check for any rejection on the AAL2 CAC
Reservation algorithm. HSDPA reservation success rate is calculated by below formula. If the
reservation fails then one of M800C7, M800C8 or M800C9 is incremented. M800C7 indicates
a lack of external resources whereas M800C8 indicates a lack of internal resources. M800C9
is incremented if the failure is for any other reason.

sum(AAL2_SUCCEEDED_HSPDA)
x100%
sum(AAL2_SUCCEEDED_HSPDA  TRANSPORT_REJECTED_EXT_HSDPA
 TRANSPORT_REJECTED_INT_HSDPA  OTHER_REJECTED_HSDPA)

The number of HSDPA AAL2 reservation rejected because of too many users can be verified
from counter REJECTED_HSDPA_TOO_MANY_USERS. This counter is incremented in
failure cases where Shared HSDPA Allocation has failed and the number of MAC-d flows
(HSDPA users) is limited to the number given by parameter “NbrOfOverbookedHSDPAUsers”

AAL2 CAC rejection also useful to see what is the impact to R99 users for different SHA
setting. It can be further verified from Service Level counters whether it affect to the RRC or
RAB performance.

sum(AAL2_CAC_REJECTED)
x100%
sum(AAL2_RM_SUCCEEDED  AAL2_CAC_REJECTED)

Below figure shows the improvement of AAL2 CAC rejection after fine tuning the SHA
parameter.
AAL2 CAC Reservation vs Rejection
Ave_Reserved_Bandm idth Peak_CAC_Reservation Iub_CAC_Reservation_R99 CAC_Rejection

100.00%
90.00%
80.00%
70.00%
60.00%
50.00%
40.00%
30.00%
20.00%
10.00%
0.00%
11/15/2007-00
11/15/2007-06
11/15/2007-12
11/15/2007-18

11/16/2007-00
11/16/2007-06
11/16/2007-12

11/16/2007-18
11/17/2007-00

11/17/2007-06
11/17/2007-12
11/17/2007-18
11/18/2007-00

11/18/2007-06
11/18/2007-12

11/18/2007-18
11/19/2007-00
11/19/2007-06
11/19/2007-12

11/19/2007-19

11/20/2007-01
11/20/2007-08
11/21/2007-04
11/21/2007-10
11/21/2007-16

11/21/2007-22
11/22/2007-05
11/22/2007-11
11/22/2007-18
11/23/2007-00
11/23/2007-06

11/23/2007-12
11/23/2007-18
11/24/2007-00
11/24/2007-06
11/24/2007-12

11/24/2007-18
11/25/2007-00
11/25/2007-06
11/25/2007-12
11/25/2007-18
11/26/2007-00

11/26/2007-06
11/26/2007-12
11/26/2007-18
11/27/2007-00
11/27/2007-06

11/27/2007-12

11/27/2007-18

Figure 9 AAL2 CAC rejection


13/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

4.2 HSDPA Usage


4.2.1 Iub Data Volume and Throughput
These measurements cover the data volume transferred and the Mac-hs throughput

4.2.2 HSDPA data volume (MAC-d) at Iub


HSDPA received data (Mbit) in RAN access points (=WCELLs). It is based on received MAC-
d PDUs in HS-DSCH data frames at BTS.

RNC _ 608a 
sum( MAC _ D _ PDU _ TOT ) * 336
Mbit 
1000000

4.2.3 Active HS-DSCH Mac-d throughput


The average active HS-DSCH MAC-d throughput from network perspective calculated as the
HSDPA MAC-d throughput at BTS, divided by the active HS-DSCH time (time when there is
scheduled TTIs) from the network perspective. This formula does not include retransmissions
from the WBTS to the UE.

sum( MAC _ D _ PDU _ TOT  MAC _ D _ PDU _ DROP _ BTS _ OWFL) * 336 / 1000
RNC _ 722a 
sum( HS _ SCCH _ PWR _ DIST _ CLASS _ 0  HS _ SCCH _ PWR _ DIST _ CLASS _ 1
 HS _ SCCH _ PWR _ DIST _ CLASS _ 2  HS _ SCCH _ PWR _ DIST _ CLASS _ 3
 HS _ SCCH _ PWR _ DIST _ CLASS _ 4  HS _ SCCH _ PWR _ DIST _ CLASS _ 5) / 500

4.2.4 HSDPA Users


When HSDPA is active, counter M1000C168-M1000C175 are incremented depending the
number of simultaneous HSDPA users in a cell. This can be used as a reference of how
many simultaneous users are serving by the HSDPA BTS.
HSDPA Users

DUR_HSDPA_NO_USERS DUR_HSDPA_USERS_1_OR_2 DUR_HSDPA_USERS_3_OR_4


DUR_HSDPA_USERS_5_OR_6 DUR_HSDPA_USERS_7_OR_8 DUR_HSDPA_USERS_9_OR_10
DUR_HSDPA_USERS_11_OR_12 DUR_HSDPA_USERS_13_OR_14 DUR_HSDPA_USERS_15_OR_16

100.00%

80.00%

60.00%

40.00%

20.00%

0.00%
10/1/2006

10/3/2006

10/5/2006

10/7/2006

10/9/2006

10/11/2006

10/13/2006

10/15/2006

10/17/2006

10/19/2006

10/21/2006

10/23/2006

10/25/2006

10/27/2006

10/29/2006

10/31/2006

11/2/2006

11/4/2006

11/6/2006

11/8/2006

11/10/2006

11/12/2006

Figure 10 HSDPA users distribution

Average number of HSDPA simultaneous users can be monitored from the AAL2 counters:

M550C11SUM_AAL2_CONNECTIONS_HSDPA
M550C7 NBR_SAMPLES

And the maximum HSDPA simultaneous users, MAX_AAL2_CONNECTIONS_HSDPA can


be used as a reference to consider BTS to upgrade to 15 codes multiplexing in RAS06.
14/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

4.3 HSDPA Performance


Following figure shows the counters in HSDPA traffic measurements.

Figure 11 HSDPA traffic measurement counters

4.3.1 HSDPA Accessibility


The accessibility of all started allocations for HS-DSCH for NRT Traffic from user point of view
calculates the number of times when HS-DSCH channel has been established divided by the
number of times when HS-DSCH channel has been selected by cell specific PS.

sum( ALLO _ HS _ DSCH _ FLOR _ INT  ALLO _ HS _ DSCH _ FLOW _ BGR)


RNC _ 605a   100%
sum( ALLO _ HS _ DSCH _ FLOR _ INT  ALLO _ HS _ DSCH _ FLOW _ BGR
 DCH _ SEL _ MAX _ HSDPA _ USER _ INT  DCH _ SEL _ MAX _ HSDPA _ USERS _ BGR
 REJ _ HS _ DSCH _ RET _ INT  REJ _ HS _ DSCH _ RET _ BGR
 SETUP _ FAIL _ RNC _ HS  DSCH _ INT  SETUP _ FAIL _ UE _ HS _ DSCH _ INT
 SETUP _ FAIL _ BTS _ HS  DSCH _ INT  SETUP _ FAIL _ IUB _ HS _ DSCH _ INT
 SETUP _ FAIL _ RNC _ HS  DSCH _ BGR  SETUP _ FAIL _ UE _ HS _ DSCH _ BGR
 SETUP _ FAIL _ BTS _ HS  DSCH _ BGR  SETUP _ FAIL _ IUB _ HS _ DSCH _ BGR)

HSDPA MAC-d flow setup failures typically indicates lack of the resources (Radio, BTS, Iub)
for HSDPA or for UL return channel. HSDPA Setup can also fail if maximum amount of
HSDPA users in the cell exceeds. Failure counters itself are not enough to indicate
congestion but together with other counters e.g. BTS CE usage it is possible to identify cells
having capacity problems.

4.3.2 HSDPA Retainability for NRT traffic


This KPI is based on Traffic Measurement. The normal transition from HS-DSCH to
FACH/DCH is considered as a normal HS-DSCH release (including transitions due to mobility
and pre-emption). And the failure releases are mainly RL Failures releases or release other
than RL failure. RL failure release refer to the release of HS-DSCH allocation due the radio
15/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

link failure indication from BTS, RLC protocol reset internally in the RNC or UL RCL
unrecoverable error (Cell Update sent by UE).

sum(( REL _ ALLO _ NORM _ HS _ DSCH _ INT  REL _ ALLO _ NORM _ HS _ DSCH _ BGR)
RNC _ 609a   100%
sum( REL _ ALLO _ NORM _ HS _ DSCH _ INT  REL _ ALLO _ NORM _ HS _ DSCH _ BGR
REL _ ALLO _ OTH _ FAIL _ HS _ DSCH _ INT  REL _ ALLO _ OTHER _ FAIL _ HS _ DSCH _ BGR
REL _ ALLO _ RL _ FAIL _ HS _ DSCH _ INT  REL _ ALLO _ RL _ FAIL _ HS _ DSCH _ BGR))

4.3.3 HSDPA Mac-hs efficiency


MAC-hs efficiency quantifies HSDPA retransmission ratio between BTS and HSDPA capable
UE done by MAC-hs. This is number of all successful sent MAC-hs PDUs divided by total
number of all transmitted MAC-hs PDUs including retransmissions

MAC _ HS _ PDU _ RETR _ DIST _ CL _ O  MAC _ HS _ PDU _ RETR _ DIST _ CL _ 1  MAC _ HS _ PDU _ RETR _ DIST _ CL _ 2
MAC _ HS _ PDU _ RETR _ DIST _ CL _ 3  MAC _ HS _ PDU _ RETR _ DIST _ CL _ 4  MAC _ HS _ PDU _ RETR _ DIST _ CL _ 5
RNC _ 607b   100%
 ORIG _ TRANS _ 1 _ CODE _ QPSK  ORIG _ TRANS _ 2 _ CODE _ QPSK  ORIG _ TRANS _ 3 _ CODE _ QPSK
 ORIG _ TRANS _ 4 _ CODE _ QPSK  ORIG _ TRANS _ 5 _ CODE _ QPSK  ORIG _ TRANS _ 1 _ CODE _ 16QAM
 ORIG _ TRANS _ 2 _ CODE _ 16QAM  ORIG _ TRANS _ 3 _ CODE _ 16QAM  ORIG _ TRANS _ 4 _ CODE _ 16QAM
 ORIG _ TRANS _ 5 _ CODE _ 16QAM  RETRANS _ 1 _ CODE _ QPSK  RETRANS _ 2 _ CODE _ QPSK
 RETRANS _ 3 _ CODE _ QPSK  RETRANS _ 4 _ CODE _ QPSK  RETRANS _ 5 _ CODE _ QPSK
 RETRANS _ 1 _ CODE _ 16QAM  RETRANS _ 2 _ CODE _ 16QAM  RETRANS _ 3 _ CODE _ 16QAM
 RETRANS _ 4 _ CODE _ 16QAM  RETRANS _ 5 _ CODE _ 16QAM

Distribution of MAC-hs retransmissions indicates the number of retransmissions needed to


correctly deliver the MAC-hs PDU. MAC_HS_PDU_RETR_DIST_CL_0 below indicates no re-
transmission percentage is quite high, more than 80%.

MAC-hs Re-Transmission Distribution


MAC_HS_PDU_RETR_DIST_CL_0 MAC_HS_PDU_RETR_DIST_CL_1 MAC_HS_PDU_RETR_DIST_CL_2 MAC_HS_PDU_RETR_DIST_CL_3
MAC_HS_PDU_RETR_DIST_CL_4 MAC_HS_PDU_RETR_DIST_CL_5
100.00%

80.00%

60.00%

40.00%

20.00%

0.00%
1/1/2008

1/2/2008

1/3/2008

1/4/2008

1/5/2008

1/6/2008

1/7/2008

1/8/2008

1/9/2008

1/10/2008

1/11/2008

1/12/2008

1/13/2008

1/14/2008

1/15/2008

1/16/2008

1/17/2008

1/18/2008

1/19/2008

1/20/2008

1/21/2008

1/22/2008

1/23/2008

1/24/2008

1/25/2008

1/26/2008

1/27/2008

Figure 12 MAC-hs retransmission

Below shows the transmission and retransmission mainly using 5 codes, QPSK or 16QAM.

Figure 13 HSDPA modulation types


16/16 HSDPA Optimization Guideline for CELCOM 25/01/2008

4.3.4 CQI
HS-DSCH Link Adaptation and HSSCCH power control are based on the instantaneous
signal quality information received from the UE, i.e. Channel Quality Indicator, CQI.
Theoretically CQI can be used as a reference of potential throughput. Example of distribution
can be seen in figure below.

Figure 14 CQI distribution

CQI reporting is UE dependent, so different UEs can report different CQI values in the similar
conditions.

Average reported CQI:

sum(CQI_DIST_CL_0 )  CQI_DIST_CL_1  CQI_DIST_CL_2  CQI_DIST_CL_3  CQI_DIST_CL_4  CQI_DIST_CL_5


 CQI_DIST_CL_6  CQI_DIST_CL_7  CQI_DIST_CL_8  CQI_DIST_CL_9  CQI_DIST_CL_10  CQI_DIST_CL_11
 CQI_DIST_CL_12  CQI_DIST_CL_13  CQI_DIST_CL_14  CQI_DIST_CL_15  CQI_DIST_CL_16  CQI_DIST_CL_17
 CQI_DIST_CL_18  CQI_DIST_CL_19  CQI_DIST_CL_20  CQI_DIST_CL_21  CQI_DIST_CL_22  CQI_DIST_CL_23
 CQI_DIST_CL_24  CQI_DIST_CL_25  CQI_DIST_CL_26  CQI_DIST_CL_27  CQI_DIST_CL_28  CQI_DIST_CL_29
 CQI_DIST_CL_30

RNC _ 706a 
31