05 6275 Hspa E01 KH Mo

Contents
Key Performance Indicators for UMTS and HSPA

 UMTS Network
 Call / Connection Analysis
 Mobility Analysis
 Quality Aspects
 HSPA
 Appendix
00-1 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

Content
HSPA
 General Aspects
 HSDPA
 HSUPA
 Practical Protocol Trace Examples

Content
HSPA
 General Aspects
 HSDPA
 HSUPA

Multiplexing Options
With the support of HSPA (HSDPA plus HSUPA – or E-DCH) there is a great variaty of TrCH combinations.
Up to 7 different TrCH combinations in CELL_DCH state are possible in Rel. 6 of 3GPP but UTRAN will not
configure all possible combinations. However, HSUPA capable UE’s must support all of them.
The RB’s can be multiplexed with transport channel type

- "DCH“ for the UL or DL, when the corresponding DCH transport channel are configured.
- "E-DCH" for the UL, when the corresponding E-DCH MAC-d flow(s) is configured.
- "HS-DSCH" for the DL, when the corresponding MAC-d flow(s) is configured.
DCH is needed for CS traffic, which is usually symmetric. PS traffic can be configured to all options, where
limited support (usually as option) for RT PS traffic on HS-DSCH/E-DCH is given. RT PS traffic needs so
the DCH/DCH option. The decision is done in the RNC with knowledge about the type of traffic and the type
of UEs. Switching between the different TrCH options is handled by Channel Type Switching (CTS)
depending on load, capability, mobility….. . Changing the rate for the Rel 99 traffic channel is provided by
BRA (Bit Rate Adaptation).
In Rel 99: only DCH/DCH possible

In Rel 5: only DCH/DCH, HS-DSCH + DCH/DCH possible
All other combinations should be supported starting with Rel 6 UEs!!!

TrCH Combinations and RRC States
RRC idle 3GPP 25.331 (8.5.21)
CELL_PCH URA_PCH CELL_FACH

Paging / SRB 0 Paging / SRB 0 FACH / RACH
RRC connected
HS-DSCH + DCH / DCH HS-DSCH / DCH

DCH / DCH
DCH / E-DCH* CELL_DCH HS-DSCH / E-DCH
HS-DSCH + DCH / E-DCH + DCH HS-DSCH + DCH / E-DCH*
TCH combinations for UL / DL, * not likely to be implemented

Content
HSPA
 General Aspects
 HSDPA
 HSUPA

HSDPA Implementation
HSDPA Capable UEs
HSDPA Capable cell
HSDPA (high-speed downlink packet access) is a wideband code division multiple access (WCDMA) key feature, which
provides high data rate transmission in a CDMA downlink to support multimedia services. HSDPA brings high-speed
data delivery to 3G terminals, ensuring that users requiring effective multimedia capabilities benefit from data rates
previously unavailable because of limitations in the radio access network (RAN).
Node B Rel. 99 Node B with HSDPA

Rel. 5 or later
Dedicated pipe for every UE Fast pipe is shared among UEs
HSDPA Implementation
In the Release 5 implementation the radio bearer can only be configured to
-"DCH“ for the UL and DL, when the corresponding DCH transport channel are configured.
-HSDPA in DL, DCH in UL plus DL (DCH in DL is needed in all cases for the SRB).
-FACH
The Channel Type Switching between these states can be used to handle mobility for example. (Very basic
implementation, switch to FACH, let the UE do ist cell update.
Today normally the soft handover for the A-DCH is supported, anyway there are situations, which require
special support, for example, the support of compressed mode for the A-DCH may not be given, or HSDPA
over Iur may not be implemented.
Ather configuration possibilities require support of Rel. 6 Ues and latter:
- HSDPA DL/HSUPA UL SRB on DCH (in Dl and UL);

- HSDPA DL/HSUPA UL SRB on HSDPA/EDCH with F-DCH
- HS-Cell FACH
- HS-Cell RACH

HSDPA UE Categories 1/2
HS- DSCH max. No. of min. * Inter-TTI Dual-Stream MIMO Peak
Modulation
category HS-DSCH Codes interval supported Rate
1 5 3 (6 ms) QPSK/16QAM No 1.2 Mbps
2 5 3 QPSK/16QAM No 1.2 Mbps
7 10 1 QPSK/16QAM No 7 Mbps
11 5 2 QPSK only No 1 Mbps
12 5 1 QPSK only No 1.8 Mbps
13 15 1 QPSK/16QAM/ 64QAM No 17.4 Mbps
14 15 1 QPSK/16QAM/ 64QAM No 21.1 Mbps
15 15 1 QPSK/16QAM Yes 23.4 Mbps
16 15 1 QPSK/16QAM Yes 28 Mbps
17 15 1 QPSK/16QAM with MIMO or 64QAM only 17.4 or 23.4 Mbps
18 15 1 QPSK/16QAM with MIMO or 64QAM only 21.1 or 28 Mbps

19 15 1 QPSK/16QAM/ 64QAM Yes 35.3 Mbps
20 15 1 QPSK/16QAM/ 64QAM Yes 42.2 Mbps

HSDPA UE Categories 2/2
Total Number of
Total Number Supported
max. No. min. serving/ Supported modulations
HS- of serving/ modulations without
of Inter- secondary serving with MIMO operation Peak
DSCH secondary MIMO operation with
HS-DSCH TTI HS-DSCH cells in and aggregated cell Rate
cat. serving HS- aggregated cell
Codes interval which MIMO can operation
DSCH cells operation
be configured
21 15 1 2 0 QPSK/16QAM - 23.4 Mbps
22 15 1 2 0 QPSK/16QAM - 28 Mbps
23 15 1 2 0 QPSK/16QAM/64QAM - 35.3 Mbps
24 15 1 2 0 QPSK/16QAM/64QAM - 42.2 Mbps
25 15 1 2 2 - QPSK/16QAM 46.7 Mbps
26 15 1 2 2 - QPSK/16QAM 55.9 Mbps
27 15 1 2 2 - QPSK/16QAM/64QAM 70.6 Mbps
28 15 1 2 2 - QPSK/16QAM/64QAM 84.4 Mbps
29 15 1 3 0 QPSK/16QAM/64QAM - 63.3 Mbps
30 15 1 3 3 QPSK/16QAM/64QAM QPSK/16QAM/64QAM 126.6 Mbps
31 15 1 4 0 QPSK/16QAM/64QAM - 84.4 Mbps
33 15 1 6 0 QPSK/16QAM/64QAM - 126.6 Mbps
35 15 1 8 0 QPSK/16QAM/64QAM - 168.8 Mbps
• Terminal categories 21-24 require the DC-HSDPA with 42Mbps network support feature to obtain peak rates
• Terminal categories 25-28 require the DC-HSDPA with MIMO 84Mbps network support feature to obtain peak rates
• Terminal categories 29-36 require future releases features to obtain peak rates

RRC States with HSDPA – pure HSDPA
RRC idle 3GPP 25.331 (8.5.21)
CELL_PCH URA_PCH CELL_FACH

Paging / SRB 0 Paging / SRB 0 FACH / RACH
RRC connected
DCH / DCH HS-DSCH + DCH / DCH

CELL_DCH
Possible transitions

HSDPA Channels
Rel99
DCH
Needed for DL data
(e.g. CS traffic)
1-4 x HS-SCCH
HS-DPCCH and the SRB
Associated
1-15 x HS-
(SRB can use HS-PDSCH

PDSCH
DPCH
from Rel. 6 on)
Needed for UL data

and the SRB
(SRB can use E-DCH
from Rel. 6 on)

Link Adaptation of HSDPA Users
• 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 and ACK/NAK for the
MAC-hs PDUs
• CQI based link adaptation defines directly the HS-DSCH capacity.
• If CQI information is not received for several consecutive times (possible UL problems) the
scheduling of the priority queues for that mobile are stopped until CQI from the UE is received again
• Based on reported CQI by the UEs different kinds of statistical distributions can be calculated and
presented to show the Radio Quality of the HSDPA users.
HSDPA MAC-hs Retransmissions

• When one MAC-hs PDU is not correctly delivered a NAK is reported by the UE on the HS-DPCCH
and a retransmission will be triggered.
• The maximum number of retransmissions for one MAC-hs PDU is defined with a respective
parameter (normally the default value used by vendors is 3)
The Quality/HSDPA Efficiency of the Link Adaptation Mechanism can be seen in the average
retransmission Rate for the MAC-hs PDUs or in the HSDPA Successful transmission ratio see next slide

HSDPA Efficiency – Nokia
KPI Formula (with short names)

100*sum([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]) /sum([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_6_CODE_QPSK] +[ORIG_TRANS_7_CODE_QPSK] +[ORIG_TRANS_8_CODE_QPSK]
+[ORIG_TRANS_9_CODE_QPSK] +[ORIG_TRANS_10_CODE_QPSK] +[ORIG_TRANS_11_CODE_QPSK]
+[ORIG_TRANS_12_CODE_QPSK] +[ORIG_TRANS_13_CODE_QPSK] +[ORIG_TRANS_14_CODE_QPSK]
+[ORIG_TRANS_15_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] +
[ORIG_TRANS_6_CODE_16QAM] +[ORIG_TRANS_7_CODE_16QAM] + [ORIG_TRANS_8_CODE_16QAM]
HSDPA MAC-hs
+[ORIG_TRANS_9_CODE_16QAM] +[ORIG_TRANS_10_CODE_16QAM] +[ORIG_TRANS_11_CODE_16QAM]
efficiency
+[ORIG_TRANS_12_CODE_16QAM] +[ORIG_TRANS_13_CODE_16QAM] +[ORIG_TRANS_14_CODE_16QAM]
+[ORIG_TRANS_15_CODE_16QAM] +[ORIG_TRANS_MAC_EHS_64QAM] +[RETRANS_1_CODE_QPSK] +
[RETRANS_2_CODE_QPSK] + [RETRANS_3_CODE_QPSK] + [RETRANS_4_CODE_QPSK] +
[RETRANS_5_CODE_QPSK] + [RETRANS_6_CODE_QPSK] +[RETRANS_7_CODE_QPSK]
+[RETRANS_8_CODE_QPSK] +[RETRANS_9_CODE_QPSK] +[RETRANS_10_CODE_QPSK]
+[RETRANS_11_CODE_QPSK] +[RETRANS_12_CODE_QPSK] +[RETRANS_13_CODE_QPSK]
+[RETRANS_14_CODE_QPSK] +[RETRANS_15_CODE_QPSK] +[RETRANS_1_CODE_16QAM] +
[RETRANS_2_CODE_16QAM] + [RETRANS_3_CODE_16QAM] + [RETRANS_4_CODE_16QAM] +
[RETRANS_5_CODE_16QAM] +[RETRANS_6_CODE_16QAM] +[RETRANS_7_CODE_16QAM]
+[RETRANS_8_CODE_16QAM] +[RETRANS_9_CODE_16QAM] +[RETRANS_10_CODE_16QAM]
HSDPA Successful transmission ratio i.e. efficiency of HSDPA data transmission between BTS and HSDPA Capable
UEs done by MAC-hs. KPI is based on successfully sent MAC-hs PDUs divided by totally sent MAC-hs
Comment
PDUs. (Total number of all successful sent MAC-hs PDUs divided by total number of all transmitted MAC-hs PDUs
(including retransmissions)).

HSDPA Efficiency! – Huawei
• Huawei offers counters for the number of ACKs and NAKs of the HSDPA transmission in the cell
Under: HSDPA Measurement (HSDPA.LOCELL)
Counter ID Counter Name Counter Description

50331654 VS.AckTotal Total number of ACKs received
50331655 VS.NackTotal Total number of NACKs received
50331656 VS.DtxTotal Total number of TTIs when the NodeB can not translate the acknowledgement information from the UE
50331657 VS.AckFirst Number of ACKs received after 1st transmission
50331658 VS.AckRetrans.1 Number of ACKs received after 1st retransmission
50331659 VS.AckRetrans.2 Number of ACKs received after 2nd retransmission
50331660 VS.AckRetrans.3 Number of ACKs received after 3rd retransmission
50331661 VS.AckRetrans.4 Number of ACKs received after 4th retransmission
50331668 VS.AckRemain Number of times the NodeB does not receive the ACK from the UE after the last retransmission
A similar KPI can be created alike to Nokia when one ACK is seen as one successfully transmitted PDU and one NAK as one not
successfully transmitted PDU

HSDPA Efficiency!! – Huawei
• Huawei defines as the HSDPA Efficiency (not similar with Nokia) the following KPI:
KPI Formula
(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)/
HSDPA Efficiency
(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean +
At NodeB in %
VS.HSDPA.ScheInactiveDataTtiRatio.Mean)
HSDPA Efficiency = Duration when there is HSDPA data transmission/ Duration when there
is HSDPA data in the buffer
Comment
This KPI provides the proportion of the duration when there is HSDPA data transmission to
the duration when there is HSDPA data in the buffer.

HSDPA Efficiency – Ericsson
KPI Formula
PINTHS_I_Bler =
HSDPA BLER on radio node Level 100 * (HsDschResources.pmNackReceived / (HsDschResources.pmNackReceived +
For DU Radio Nodes, Baseband Radio Nodes, HsDschResources.pmAckReceived))
RBS 6402
Also the following counters can be used to roughly estimate the data retransmission rate:
Sum of all sample values recorded during a ROP for HS-DSCH user RLC throughput
measurements.
pmSumHsDlRlcUserPacketThp
The user RLC throughput includes user data but excludes retransmissions.
Unit: 1 kbps
Sum of all sample values recorded during a ROP for HS-DSCH RLC throughput.
pmSumHsDlRlcTotPacketThp Total RLC throughput includes both user data and retransmissions.
Unit: 1 kbps

HSDPA Radio Link Setup
NODE B
UE in CELL_DCH
NBAP: RADIO LINK RECONFIGURATION PREPARE In case no RL has
DCH / DCH HS-DSCH Information, selected HS-DSCH RNTI and the HS-PDSCH RL ID already been
NBAP: RADIO LINK RECONFIGURATION READY established (UE on
cell FACH), the
HS-DSCH Information Response
Radio Link Setup
NBAP:RADIO LINK RECONFIGURATION COMMIT procedure is used
instead of the Radio
AAL2 Setup Link Reconfiguration
procedure.
RRC:RADIO BEARER RECONFIGURATION
RRC:RADIO BEARER RECONFIGURATION COMPLETE
HS-DSCH Frame Protocol: HS-DSCH CAPACITY REQUEST
Common Transport Channel Priority Indicator and User Buffer Size
HS-DSCH Frame Protocol: HS-DSCH CAPACITY ALLOCATION

HS-SCCH Common Transport Channel Priority Indicator, HS-DSCH Credits, HS-DSCH Interval,
HS-DSCH Repetition period, Maximum MAC-d PDU length
UE in CELL_DCH
UE listens to HS-DCCH (High Speed Downlink Control Channel)
HS-DSCH + DCH / DCH

HSPA Bearer Analysis - Nokia
Number of attempts to setup a RAB of specific maximum bit rate
Counter Counter Name Bitrate Class (kbps)

M1001C659 RAB_STP_ATT_BR_CLASS_1_DL 0 < Bitrate < 384
M1001C665 RAB_STP_ATT_BR_CLASS_7_DL Bitrate > 14400
Counter Counter Name Bitrate Class (kbps)

M1001C666 RAB_STP_ATT_BR_CLASS_1_UL 0 < Bitrate < 128
M1001C670 RAB_STP_ATT_BR_CLASS_4_UL Bitrate > 2000

Number of attempts and successes to setup a RAB with HSPA
M1022C3 PS_ATT_HSDSCH_EDCH_INT HSDPA + HSUPA attempted

M1022C4 PS_ATT_HSDSCH_EDCH_BGR HSDPA + HSUPA attempted
M1022C21 HS_E_REQ_HS_E_ALLO_INT Full success, both allocated
M1022C22 HS_E_REQ_HS_E_ALLO_BGR Full success, both allocated
M1022C23 HS_E_REQ_HS_D_ALLO_INT Partial success, HSDPA + DCH allocated
M1022C24 HS_E_REQ_HS_D_ALLO_BGR Partial success, HSDPA + DCH allocated
M1022C27 HS_E_REQ_D_D_ALLO_INT No success, DCH + DCH allocated only
M1022C28 HS_E_REQ_D_D_ALLO_BGR No success, DCH + DCH allocated only
M1022C5 PS_ATT_HSDSCH_DCH_INT HSDPA + DCH attempted

M1022C6 PS_ATT_HSDSCH_DCH_BGR HSDPA + DCH attempted
M1022C25 HS_D_REQ_HS_D_ALLO_INT Full success, HSDPA + DCH allocated
M1022C26 HS_D_REQ_HS_D_ALLO_BGR Full success, HSDPA + DCH allocated
M1022C29 HS_D_REQ_D_D_ALLO_INT No success, DCH + DCH allocated only
M1022C30 HS_D_REQ_D_D_ALLO_BGR No success, DCH + DCH allocated only

Number of HSDPA setup failures per cause
M1002C401 REJ_HS_DSCH_RET_INT lack of radio resources for A-DCH

M1002C402 REJ_HS_DSCH_RET_BGR
M1002C476 DCH_SEL_MAX_HSDPA_USERS_BGR maximum number of users
M1002C477 DCH_SEL_MAX_HSDPA_USERS_INT
M1002C416 SETUP_FAIL_BTS_HS_DSCH_INT Node B failure
M1002C424 SETUP_FAIL_BTS_HS_DSCH_BGR
M1002C414 SETUP_FAIL_IUB_MAC_D_INT lack of Iub resources for A-DCH
M1002C422 SETUP_FAIL_IUB_MAC_D_BGR
M1002C417 SETUP_FAIL_IUB_HS_TOTAL_INT lack of AAL2 resources within RNC
M1002C425 SETUP_FAIL_IUB_HS_TOTAL_BGR.
M1002C415 SETUP_FAIL_UE_HS_DSCH_INT radio bearer reconfiguration failure within UE
M1002C423 SETUP_FAIL_UE_HS_DSCH_BGR
M1002C413 SETUP_FAIL_RNC_HS_DSCH_INT internal RNC failure
M1002C421 SETUP_FAIL_RNC_HS_DSCH_BGR

Number of HSUPA setup failures per cause
M1002C523 SETUP_FAIL_EDCH_UE_INT radio bearer reconfiguration failure within UE

M1002C524 SETUP_FAIL_EDCH_UE_BGR
M1002C525 SETUP_FAIL_EDCH_BTS_INT Node B failure
M1002C526 SETUP_FAIL_EDCH_BTS_BGR
M1002C527 SETUP_FAIL_EDCH_TRANS_INT Transport failure
M1002C528 SETUP_FAIL_EDCH_TRANS_BGR
M1002C529 SETUP_FAIL_EDCH_OTHER_INT Any other failure
M1002C530 SETUP_FAIL_EDCH_OTHER_BGR
Less cause counters defined than for HSDPA setup

HSPA Accessability - Nokia
KPI Formula
100* sum([HS_E_REQ_HS_E_ALLO_STRE] + [HS_E_REQ_HS_E_ALLO_INT] +

[HS_E_REQ_HS_E_ALLO_BGR] + [HS_E_REQ_HS_D_ALLO_STRE] +
[HS_E_REQ_HS_D_ALLO_INT] + [HS_E_REQ_HS_D_ALLO_BGR] +
[HS_D_REQ_HS_D_ALLO_STRE] + [HS_D_REQ_HS_D_ALLO_INT] +
[HS_D_REQ_HS_D_ALLO_BGR])
/
sum([PS_ATT_HSDSCH_EDCH_STRE] + [PS_ATT_HSDSCH_EDCH_INT] +
[PS_ATT_HSDSCH_EDCH_BGR] + [PS_ATT_HSDSCH_DCH_STRE] +
HSDPA Setup Success Ratio for NRT traffic
[PS_ATT_HSDSCH_DCH_INT] + [PS_ATT_HSDSCH_DCH_BGR] -
RNC_914c
[HS_D_REQ_D_D_ALLO_STR_CELL] - [HS_D_REQ_D_D_ALLO_BGR_CELL] -
[HS_D_REQ_D_D_ALLO_INT_CELL] - [HS_E_REQ_D_D_ALLO_STR_CELL] -
[HS_E_REQ_D_D_ALLO_BGR_CELL] - [HS_E_REQ_D_D_ALLO_INT_CELL])
=
100* sum([M1022C190] + [M1022C21] + [M1022C22] + [M1022C191] + [M1022C23] +
[M1022C24] + [M1022C192] + [M1022C25] + [M1022C26])
/
sum([M1022C181] + [M1022C3] + [M1022C4] + [M1022C182] + [M1022C5] + [M1022C6] –
[M1022C222] - [M1022C221] - [M1022C220] - [M1022C219] - [M1022C218] - [M1022C217])

HSPA Bearer Setup (over All) Analysis – Huawei
Counter ID Counter Name Counter Description
67190705 VS.HSDPA.RAB.SuccEstab Number of Successful HSDPA RAB Establishments for Cell
67190704 VS.HSDPA.RAB.AttEstab Number of HSDPA RAB Establishment Attempts for Cell
KPI Formula
HSDPA RAB Setup
Success Ratio (VS.HSDPA.RAB.SuccEstab/VS.HSDPA.RAB.AttEstab) x 100%
In % on Cell
This KPI is used to check the RAB Setup Success Ratio of PS services that are carried by HSDPA in a cluster. The
HSDPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST
Comment message from the CN for setting up the HSDPA service. The HSDPA RAB Setup Success Procedure starts when
the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when
the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN.
Also the number of Failed HSDPA Service Establishments Due to Insufficiency of Different Resources:
73393830 VS.HSDPA.RAB.FailEstab.DLPower.Cong Number of Failed HSDPA Service Establishments Due to DL Power Insufficiency
for Cell
73393831 VS.HSDPA.RAB.FailEstab.DLIUBBand.Cong Number of Failed HSDPA Service Establishments Due to DL Iub Bandwidth
Insufficiency for Cell
67192916 VS.RAC.NewCallReq.Fail.HSDPANum.Cong Number of Failed Admissions Due to HSDPA User Number Exceeding Threshold
During RAB Establishment for Cell
67192917 VS.RAC.NewCallReq.Fail.HSUPANum.Cong Number of Failed Admissions Due to HSUPA User Number Exceeding Threshold
During RAB Establishment for Cell

HSPA Bearer Setup Analysis – Ericsson
KPI Formula
100 * (UtranCell.pmTotNoRrcConnectReqPsSucc /
Pint_HS_A =
(UtranCell.pmTotNoRrcConnectReqPs - UtranCell.pmNoLoadSharingRrcConnPs)) *
• Packet-Switched (PS) Data Interactive HS
(UtranCell.pmNoNormalNasSignReleasePs /
Accessibility
(UtranCell.pmNoNormalNasSignReleasePs +
• Accessibility success rate per UtranCell for
UtranCell.pmNoSystemNasSignReleasePs)) *
PS interactive HS.
(UtranCell.pmNoRabEstablishSuccessPacketInteractiveHs /
in %, on RNC level
UtranCell.pmNoRabEstablishAttemptPacketInteractiveHs)
With the counters:
Total number of successful Interactive and Background (Originating & Terminating) RRC
pmTotNoRrcConnectReqPsSucc
Connection attempts
Total number of Interactive and Background (Originating & Terminating) RRC
pmTotNoRrcConnectReqPs
Connection attempts
pmNoLoadSharingRrcConnPs Number of Packet (originating & terminating) Load Sharing RRC Connection attempts.
Number of successful normal releases of the NAS signalling sequence at call setup
pmNoNormalNasSignReleasePs towards a PS CN from the originating states Idle, URA_PCH, CELL_FACH, CELL_DCH
and URA_PCH/CELL_FACH. Incremented in the best cell in the active set.
Number of system-initiated releases of the NAS signalling sequence at call setup
pmNoSystemNasSignReleasePs towards a PS CN from the originating states Idle, URA_PCH, CELL_FACH, CELL_DCH
and URA_PCH/CELL_FACH.
Number of successful RAB establishments for the PS Interactive RAB mapped on a RB
containing HS-DSCH. Incremented in the serving HS-DSCH cell.
pmNoRabEstablishSuccessPacketInteractiveHs
For Multi Carrier connections, this counter is incremented only if this cell is a serving
HS-DSCH cell.
Number of RAB establishment attempts for the PS Interactive RAB mapped on a RB
pmNoRabEstablishAttemptPacketInteractiveHs
containing HS-DSCH.

Number of Active Users
Max peak number of simultaneous HSDPA users (per day, hour)
Number of simultaneous HSDPA users on average (per day, hour)
16 HSDPA users (16 is typically the maximum of HSDPA users per cell, can be more)
….
3
2
1 HSDPA users
No HSDPA users
PS - CS traffic distribution
Hour ,day, month,
amount of HSDPA devices,
HSDPA licenses, amount no user (here 90 %)
2 User (here 9 %)
Of codes per cell, second
3 user here 1 %
Carrier needed?

Number of HSDPA Users – Nokia
Time there is a specific number of HSDPA users present in the cell
M1000C167 DUR_HSDPA_NO_USERS
M1000C168 DUR_HSDPA_USERS_1_OR_2
…
M1000C240 DUR_HSDPA_USERS_17_TO_20
…
…
…

Number of HSUPA Users – Nokia
Time there is a specific number of HSUPA users present in the cell
M1000C271 DUR_HSUPA_NO_USERS
M1000C272 DUR_HSUPA_USERS_1_OR_2

Number of HSDPA Users – Huawei
KPI Formula
Number of HSDPA Users

• This KPI provides the mean and maximum VS.HSDPA.UE.Mean.Cell,
number of HSDPA UEs in an HSDPA VS.HSDPA.UE.Max.Cell
serving cell.
With the counters:
67202932 VS.HSDPA.UE.Mean.Cell Average Number of HSDPA UEs in a Cell
73403763 VS.HSDPA.UE.Max.Cell Maximum Number of HSDPA UEs in a Cell
Also other specific counters fro the average number of HSDPA users are given by Huawei:
73410491 VS.HSDPA.64QAM.UE.Mean.Cell Average Number of 64QAM UEs in a Cell

73410493 VS.HSDPA.MIMO64QAM.UE.Mean.Cell Average Number of MIMO+64QAM UEs in a Cell
73410508 VS.HSDPA.DC.PRIM.UE.Mean.Cell Average number of DC-HSDPA UEs in anchor carrier in a Cell
73410509 VS.HSDPA.DC.SEC.UE.Mean.Cell Average number of DC-HSDPA UEs in supplementary carrier in a Cell
73441142 VS.HSDPA.UE.Mean.Cell.Free Average Number of Free HSDPA Users in a Cell
73423469 VS.HSDPA.UE.Max.Cell.Free Maximum Number of Free HSDPA Users in a Cell
73425884 VS.HSDPA.4C.PRIM.UE.Mean.Cell Average Number of 4C-HSDPA UEs Using This Cell as the Primary Carrier Cell
73425887 VS.HSDPA.3C.PRIM.UE.Mean.Cell Average Number of 3C-HSDPA UEs Using This Cell as the Primary Carrier Cell
73425890 VS.HSDPA.MC.SEC.UE.Mean.Cell Average Number of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs Using This Cell as the Secondary Carrier Cell
73425893 VS.HSDPA.DB.PRIM.UE.Mean.Cell Average Number of DB-HSDPA UEs Using This Cell as the Primary Carrier Cell
73426170 VS.HSDPA.SRBoH.UE.Mean.Cell Average number of users capable of the SRB over HSDPA feature in a cell

Number of HSDPA Users – Ericsson
KPI Formula
PintHs_U_User = (UtranCell.pmSumBestPsHsAdchRabEstablish /
• PS Interactive HS Users UtranCell.pmSamplesBestPsHsAdchRabEstablish) +
• The average number of PS Interactive HS (UtranCell.pmSumBestPsEulRabEstablish /
users per UtranCell. UtranCell.pmSamplesBestPsEulRabEstablish)
With the counters:
Sum of all sample values recorded during a ROP for the number of A-DCH radio bearers
pmSumBestPsHsAdchRabEstablish
established in the cell carrying HS-DSCH in the active set.
pmSamplesBestPsHsAdchRabEstablish Number of samples recorded within the ROP for pmSumBestPsHsAdchRabEstablish.
Sum of all sample values recorded during a ROP for the number of E-DCH radio bearers
established in the best cell.
pmSumBestPsEulRabEstablish
For Multi Carrier connections, this counter is incremented only if this cell is a serving HS-DSCH
cell.
pmSamplesBestPsEulRabEstablish Number of samples recorded within the ROP for pmSumBestPsEulRabEstablish.
KPI Formula
PintHs_U_Conn =
• PS Interactive HS Connections
UtranCell.pmSumHsConnServ / UtranCell.pmSamplesHsConnServ
• The average number of PS Interactive HS
connections per UtranCell.
With the counters:
Sum of all sample values recorded during a ROP for number of HSDPA connections (UE connections with at
least one PS RAB mapped on a DCH/HS or EUL/HS Radio Bearer).
pmSumHsConnServ
The level counter maintains the current number of HSDPA users (UE connections with at least one PS RAB
mapped on a DCH/HS or EUL/HS Radio Bearer). Sampling rate: 5 s
pmSamplesHsConnServ Number of samples recorded within the ROP for pmSumHsConnServ.

HSDPA Code Allocation
The HSDPA resources of a UTRAN cell consume Channelization Codes. The channelization codes’
spreading factors (SFs) for HS-PDSCHs and HS-SCCHs are 16 and 128, respectively. All HS-PDSCH and
HS-SCCH channelization codes which one single UE can receive are under the primary scrambling code
(the associated DCHs can be under secondary SCs) . The maximum configuration, allows 15 HS-PDSCHs
and 4 HS-SCCHs per cell (the minimum is one HS-PDSCH and one HS-SCCH). In standard
implementation the code resources are permanently configured by O&M. In some vendors case a dynamic
allocation between Rel. 99 and HS-PDSCH codes is available (Flexible code tree management).
In standard implementation there is one code tree available. When 15 codes are configured, There are
almost no codes left for Rel. 99 users (voice needs Rel 99 DCHs, all HSDPA users need an associated
DCH in Rel 5 implementation).
HS-PDSCH and Rel. 99 Code Shortage

-Alternative 1: Introduce 2nd Frequency f2 beside f1. f1 is for Idle mode & Rel. 99 traffic, f2 is the HSDPA
preferred layer
-Alternative 2: Allow Secondary Scrambling Code on f1. HS-PDSCH and HS-SCCH on Secondary
Scrambling Code, Impact on Admission and Congestion Control, Transmitted Carrier Power Utilization
-Alternative 3: Flexible code tree management

HSDPA Code Allocation
For HS-DSCH
SF16 15 x SF16
SF32 32
SF64 64 FACH 64 PCH
SF128 128 128 128 128 128 128 128

PICH HS-SCCH HS-SCCH HS-SCCH
256 256 256 256 256 256 256 256 256 256 256 256
CPICH BCH (PCH)

If two S-CCPCH are used (stand alone PCH + stand alone FACH)
a maximum of 3 HS-SCCHs is available

HSDPA Code Usage
Maximum
HSDPA Code usage rate
Minimum
utilization of the HS-PDSCH codes Average
The HS-PDSCH code usage ratio considers the accumulated number of HS-PDSCH codes of one TTI related
to the total number of TTI per sampling period and the Max. no of HS-PDSCH codes per cell. TTIs where HS-
PDSCH codes have been transmitted and where no codes i.e. no TTI’s have been transmitted shall be
considered. There is no difference if the codes are used as QPSK or 16QAM codes. The usage ratio of HS-
PDSCH code is measured. At the end of GP, the mean, minimum and maximum values are provided.

Node B Measurements
Uu Node B Iub
HARQ DSP FP prority

TRX transmission
process queue
buffer
Original
Radio transmission Number of/
connection MAC-D flow
by QSPK/ Dropped/
16QAM Discarded discarded
CQI
distribution MAC-hs MAC-d
Retrans. by PDUs PDUs
QPSK/
16QAM
Retrans.
distribution
Link adaptation / Power Control

HS-SCCH power
Packet Scheduler Flow Control

HSDPA Throughput Calculation
Higher layer data
Higher layer data packets (e.g. IP packets)
320 bits 320 bits

RLC PDU header* data (RLC SDU) header* data (RLC SDU) ………
1600 kbps
RNC
16 bits 16 bits
RLC
336 bits 336 bits

MAC-d PDU header* data (MAC-d SDU) header* data (MAC-d SDU) ………
1680 kbps
Iub
LA defines fixed number of MAC-d 10x336=3360 bits MAC-d
PDUs for one MAC-hs PDU (10) padding
MAC-hs PDU header* data (MAC-hs SDU) data (MAC-hs SDU) 8 other ………
21 bits 57 bits
MAC-hs
1720 3440 bits

kbps
Transport block (TB) MAC-hs PDU ………
Layer1
*Headers of the different PDUs are defined in TS25.321 and TS25.322

HSDPA Throughput Calculation – Example
Number of
HS-DSCH Modulation Transport Block MAC-d PDU per
Size RLC Throughput
Codes MAC-HS PDU LA in Node B defines (based
1 QPSK 365 1 160 kbps on the received Channel Quality
2 QPSK 699 2 320 kbps
Indication-CQI) about the amount
of data to be sent to the UE.
3 QPSK 1036 3 480 kbps Example is for max 5 codes.
4 QPSK 1380 4 640 kbps
5 QPSK 1711 5 800 kbps Besides the 336 bit MAC-d PDU
there Is for Category 10
5 QPSK 2046 6 960 kbps UE a high transport block size
5 QPSK 2404 7 1.12 Mbps PDU containing 656 bits
5 QPSK 2726 8 1.28 Mbps (640 data plus 16 header)
Example is for 336 PDU size
5 QPSK 3090 9 1.44 Mbps
5 QPSK 3440 10 1.60 Mbps
5 QPSK / 16QAM 3440 / 4420 10 / 13 1.60 / 2.08 Mbps
5 QPSK / 16QAM 3440 / 4748 10 / 14 1.60 / 2.24 Mbps
5 QPSK / 16QAM 3440 / 5480 10 / 16 1.60 / 2.56 Mbps
336 bits
MAC-d
5 QPSK / 16QAM 3440 / 6101 10 / 18 1.60 / 2.88 Mbps data (MAC-d SDU)
header
5 QPSK / 16QAM 3440 / 6793 10 / 20 1.60 / 3.20 Mbps
5 QPSK / 16QAM 3440 / 7168 10 / 21 1.60 / 3.36 Mbps
MAC-d
656 bits
high transport block sizes for category 10 UEs: header data (MAC-d SDU)

HSDPA Throughput Measurements
Transmitted Data
Throughput calculations could
BTS measures the number of incoming PDU in DL direction consider the traffic class
Background
Number of MAC-D PDUs received Interactive
Streaming
(Conversational)
Transferred data volume at Iub can be calculated as:
 MAC_D_PDU( 336)_TOT  336  MAC_D_PDU (656)_TOT  656 Mbit 

1000000
When one MAC-hs PDU is correctly delivered without retransmission or X number of retransmissions and
the ack has been received the respective counter below is incremented by one
Number of HS PDUs transmitted
Once
Twice
3 times
…..
HSDPA “Retransmission ratio” done by MAC-hs can be calculated based on successfully sent MAC-hs
PDUs divided by totally sent MAC-hs PDUs Actually, this is the successfully sent MAC-hs PDUs
divided by all transmitted MAC-hs PDUs including retransmissions

HSDPA Throughput Measurements
Discarded PDUs
When one MAC-hs PDU is assembled and transmitted based on Link Adaptation selection, then it may
happen that it is correctly delivered without any retransmission, or some retransmissions are needed (with
same TFRC [Transport Format and Resource Combinations] as the original tx).
-In case the timer expires for certain MAC-d flow then all the non acknowledged MAC-hs PDUs are cleared.
Number of MAC–HS PDUs deleted
-In case the max number of retransmissions (Parameter, normally set to 4) is exceeded for certain HARQ
flow the corresponding MAC-hs is cleared.
Number of MAC-HS deleted due to Max number of retransmissions
-MAC-D PDUs can be dropped from BTS buffer due to overflow of the buffer
Number Mac-D dropped due to overflow

HSDPA Throughput on Iub
-RLC: PDU size 320 bits payload + 16 bits header = 336 bits, overhead is 16/320 = 5 %.
TCP
-MAC-d: No header.
IP
-FP: HS-DSCH data frames FP-header and tail produces 9 bytes overhead and each MAC-d
PDCP
PDU produces 1 padding byte overhead. There may be 1 to 34 PDUs in the HS-DSCH frame.
RLC Thus, the FP overhead is varying between 3 to19 %.
MAC-d For example, for 10 PDUs in a frame the FP overhead is 9 + 10 = 19 bytes = 152 bits, and 152 /
3360 = 4.5 %. FP data rate = 500*3512 = 1.756 Mbps. (1 HSDPA frame per 2 ms, 3512 bit = 3360 bit
HS-DSCH-FP for MAC-d PDUs + 152 bit for FP overhead)
-The AAL2 overhead is 5 / 48 = 10.4 %.

TNL
-The ATM overhead is 5 / 53
-MAC-hs: 21 bit header + padding. For 10 * PDU the header + padding = 80 bits, with payload
(10*336) = 3440 bits. Data rate = 500 * 3440 = 1.72 Mbps.
Example with 5 codes and QPSK:
RLC MAC L1 FP rate (Iub)
Payload + RLC headers + MAC-hs headers and Payload + RLC

padding headers + FP
1.6 Mbps 1.68 Mbps 1.72 Mbps 1.756 Mbps

HSDPA Throughput KPIs – Nokia
KPI Formula
([RECEIVED_HS_MACD_BITS]+([MC_HSDPA_ORIG_DATA_PRI]+[MC_HSDPA_ORIG_
Transferred data volume at Iub
DATA_SEC])*8) / 1000 [Mbit]
RNC_608c
= ([M5000C126]+([M5002C128]+[M5002C129])*8)/1000
HSDPA MAC-d Data Volume at BTS ([RECEIVED_HS_MACD_BITS] –

RNC_739d [DISCARDED_HS_MACD_BITS]+([MC_HSDPA_ORIG_DATA_PRI]+
• successfully delivered MAC-d PDU data to [MC_HSDPA_ORIG_DATA_SEC])*8) / 1000 [Mbit]
HSDPA Capable UEs, assuming that MAC-hs = ([M5000C126]-[M5000C127] + ([M5002C128]+[M5002C129])*8) / 1000
is capable of delivering the PDUs
Active HS-DSCH cell throughput (([RECEIVED_HS_MACD_BITS] - [DISCARDED_HS_MACD_BITS]

RNC_722d +([MC_HSDPA_ORIG_DATA_PRI]+[MC_HSDPA_ORIG_D ATA_SEC])*8) * 500) /
• the average active HS-DSCH MAC-d cell ([HS_SCCH_PWR_DIST_CLASS_0] + [HS_SCCH_PWR_DIST_CLASS_1] +
throughput from network perspective [HS_SCCH_PWR_DIST_CLASS_2] + [HS_SCCH_PWR_DIST_CLASS_3] +
calculated as the HSDPA MAC-d throughput [HS_SCCH_PWR_DIST_CLASS_4] + [HS_SCCH_PWR_DIST_CLASS_5]) [kbit/s]
at BTS divided by the active HS-DSCH time = (([M5000C126]-[M5000C127] +([M5002C128]+[M5002C129])*8) * 500) / ([M5000C69]
from the network perspective + [M5000C70] + [M5000C71] + [M5000C72] + [M5000C73] + [M5000C74])

HSDPA Throughput Measurements – Nokia
M5002C5 - M5002C20 TOTAL ACKNOWLEDGED DATA IN MAC-HS PDUS FOR SPI (0...15)
M5002C130 ORIGINAL HSDPA DATA
M5002C58-M5002C73 ACTIVE HSDPA USERS IN SPI (0...15)
M5002C74 ALL ACTIVE HSDPA USERS
M5002C75-M5002C90 SAMPLES FOR ACTIVE HSDPA USERS IN SPI (0...15)
M5002C91 SAMPLES FOR ALL ACTIVE HSDPA USERS
M5002C92-M5002C107 ALLOCATED HSDPA USERS IN SPI (0...15)
M5002C108 ALL ALLOCATED HSDPA USERS
M5002C109-M5002C124 SAMPLES FOR ALLOCATED HSDPA USERS IN SPI (0...15)
M5002C125 SAMPLES FOR ALL ALLOCATED HSDPA USERS

HSDPA Cell Throughput – Huawei
KPI Formula
Mean
Throughput for
One HSDPA
Cell VS.DataOutput.Mean/(VS.DataTtiRatio.Mean -VS.HSDPA.InactiveDataTtiRatio.Mean)
Object: Nodeb
Unit: kbps
provides the MAC-hs throughput when at least one HSDPA user is transferring data at the physical layer
Comment
during the entire measurement period.
With the (NodeB) counters:

50341668 VS.DataOutput.Mean Average throughput of MAC-d PDUs in a cell
Ratio of the time when at least one HSDPA user has data to transmit in the queue
50341659 VS.DataTtiRatio.Mean buffer (During a measurement period, if at least one HSDPA user in a cell has data to transmit in the
queue buffer in a TTI, the NodeB counts the number of all such TTIs. Assume that the number is A, and
the total number of TTIs within the measurement period is B. Then, VS.DataTtiRatio.Mean = A/B)
Number of TTIs in which at least one HSDPA user in a cell has TRB data to transmit
in the queue buffer but there is no conventional TRB data transmission at the
VS.HSDPA.InactiveDat physical layer
50341693 (During a measurement period, if at least one HSDPA user in a cell has data to transmit in the queue
aTtiRatio.Mean
buffer but there is no conventional HSDPA data transmission at the physical layer within a TTI, the NodeB
counts the number of such TTIs in the measurement period. Assume that the number is A, and the total
number of TTIs in the measurement period is B. Then, VS.HSDPA.InactiveDataTtiRatio.Mean = A/B.)

HSDPA User Throughput – Huawei
There are not such counters as by Nokia for the different data rates of HSDPA bearers. As already shown:
KPI Formula
Mean Throughput for

One HSDPA User VS.HSDPA.MeanChThroughput
On Cell, in kbps
This counter indicates the mean downlink throughput for ONE HSDPA UE in a cell. When the data is transferred to an HSDPA
serving cell, the RNC measures the data transfer time of all the UEs and the total bytes sent in the cell. At the end of the
Comment
measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean downlink throughput of
MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.
For 3900 series NodeBs, it is recommended that you use the NodeB counters in the following formula to calculate the single user
throughput. These NodeB counters measure the valid throughput when data exists in the user buffer every transmission time interval
(TTI). In this case, the value of this KPI is more accurate for UEs. The throughput of a single user at the NodeB MAChs layer is calculated
using the following formula:
KPI Formula
Mean Throughput for
One HSDPA User
VS.HSDPA.DataOutput.Traffic/(VS.HSDPA.DataTtiNum.User x 2)
On Cell, in kbps with
NodeB counters
With the counters:
measures the total traffic volume of the MAC-hs/ MAC-ehs PDUs with ACKs from all users in a TTI within a
VS.HSDPA.DataOutput.Traffic
measurement period. (Unit : bit).
measures the total number of user-level TTIs (TTI = 2ms) within which there is data to transmit in HSDPA user
VS.HSDPA.DataTtiNum.User queue buffers within a measurement period. (VS.HSDPA.DataTtiNum.User x 2) and converts the number of TTIs
to the data transmission time.

Other HSDPA Throughput counters – Huawei
VS.HSDPA.FullBuffer.Throughput.SumNum.0 Samples with average HSDPA session speed 256 Kbit/s


HSDPA Cell Throughput – Ericsson
KPI Formula
(HsDschResources.pmSumAckedBitsSpi00 + HsDschResources.pmSumAckedBitsSpi01 +
PINTHS_I_DLTP_L1 = HsDschResources.pmSumAckedBitsSpi02 + HsDschResources.pmSumAckedBitsSpi03 +
HSDPA Cell Throughput HsDschResources.pmSumAckedBitsSpi04 + HsDschResources.pmSumAckedBitsSpi05 +
• Equation for a single HsDschResources.pmSumAckedBitsSpi06 + HsDschResources.pmSumAckedBitsSpi07 +
Utran Cell given HsDschResources.pmSumAckedBitsSpi08 + HsDschResources.pmSumAckedBitsSpi09 +
• In kbps HsDschResources.pmSumAckedBitsSpi10 + HsDschResources.pmSumAckedBitsSpi11 +
• DU Radio Nodes, HsDschResources.pmSumAckedBitsSpi12 + HsDschResources.pmSumAckedBitsSpi13 +
Baseband Radio HsDschResources.pmSumAckedBitsSpi14 + HsDschResources.pmSumAckedBitsSpi15) /
Nodes, RBS 6402 (0.002 * (HsDschResources.pmNoActiveSubFrames +
HsDschResources.pmNoInactiveRequiredSubFrames))

HSDPA User Throughput – Ericsson
KPI Formula
(HsDschResources.pmSumAckedBitsSpi00 + HsDschResources.pmSumAckedBitsSpi01 +
HsDschResources.pmSumAckedBitsSpi02 + HsDschResources.pmSumAckedBitsSpi03 +
PINTHS_I_DlTP_User_ HsDschResources.pmSumAckedBitsSpi14) / (0.002 * (
L1 = HsDschResources.pmSumNonEmptyUserBuffersSpi00 +
HsDschResources.pmSumNonEmptyUserBuffersSpi01 +
HSDPA User HsDschResources.pmSumNonEmptyUserBuffersSpi02 +
Throughput HsDschResources.pmSumNonEmptyUserBuffersSpi03 +
• in kbps HsDschResources.pmSumNonEmptyUserBuffersSpi04 +
• for DU Radio Nodes, HsDschResources.pmSumNonEmptyUserBuffersSpi05 +
Baseband Radio HsDschResources.pmSumNonEmptyUserBuffersSpi06 +
Nodes, RBS 6402 HsDschResources.pmSumNonEmptyUserBuffersSpi07 +
HsDschResources.pmSumNonEmptyUserBuffersSpi14))

Other HSDPA Throughput counters – Ericsson
pmAckQpsk[0] Number of HSDPA MAC packets with QPSK and TBS = 500 bit with ACK
… Proceed in steps of 1000 bit
pmAckQpsk[29] Number of HSDPA MAC packets with QPSK and TBS = 29500 bit with ACK
pmAck16Qam[0] Number of HSDPA MAC packets with 16QAM and TBS = 500 bit with ACK
pmUsedTbsQpsk[0] Number of HSDPA MAC packets with QPSK and TBS = 500 bit with ACK or NACK
pmUsedTbsQpsk[29] Number of HSDPA MAC packets with QPSK and TBS = 29500 bit with ACK or NACK
pmUsedTbs16Qam[0] Number of HSDPA MAC packets with 16QAM and TBS = 500 bit with ACK or NACK

UL A-DCH Throughput
UL Bi trate of the A-DCH (rel 99)
HS_DPCCH Channel requires an UL DPCH (return channel) to be allocated.

The return channel is also used for transmission of the TCP acknowledgements, RLC acknowledgements and other
user data. KPI have been defined to monitor the uplink bit rates assigned to HSDPA connections. Supported bit rate can
be usually 64, 128 or 384 kbps
These bit rates will depend upon the USIM QoS profile as well as RNC Parameter settings and load. Bit rate can be also
downgraded due the congestions depending of activated features. Increased uplink bit rates allow greater throughput
performance but have a greater requirement for resources – RF coverage, Node B resources, Iub transport…
HS_DSCH return channel allocations 64kbps
HS_DSCH return channel allocations 128kbps
HS_DSCH return channel allocations, 384kbps
HS_DSCH return channel allocations, xxxx kbps

A-DCH Throughput – Nokia
Total allocation time for all A-DCH of a specific service and data rate within a cell
M1002C503 ALLO_DUR_DSCH_RET_16_INT
M1002C504 ALLO_DUR_DSCH_RET_16_BGR
Number of A-DCH releases due to incoming R99 RT requests
M1002C478 REL_ALLO_HS_DSCH_PRE_EMP_INT
M1002C481 REL_ALLO_HS_DSCH_PRE_EMP_BGR

A-DCH Measurements – Huawei
There are not such counters as by Nokia.

A-DCH Measurements – Ericsson
Only the following 2 counters:
Sum of all sample values recorded during a ROP for the number of A-DCH
pmSumBestPsHsAdchRabEstablish
radio bearers established in the cell carrying HS-DSCH in the active set.
Sum of all sample values recorded during a ROP for number of established
pmSumPsHsAdchRabEstablish
A-DCH radio bearers.

CQI Distribution
UE categories 1...6
CQI TBS Codes Mod The UE reports the CQI
<5 365 1 QPSK measured assuming a transmit
5 699 2 QPSK power PCPICH +  + .
6 699 2 QPSK Measurement power offset 
7 699 2 QPSK signaled to Node B and UE by
8 1036 3 QPSK NBAP and RRC (example =
9 1380 4 QPSK PtxMaxHSDPA – PCPICH
10 1711 5 QPSK depends on vendor)
Reference power adjustment  is
HS-DPCCH
11 2046 5 QPSK
12 2404 5 QPSK used to signal how much quality
13 2726 5 QPSK is better than maximum TBS
14 3090 5 QPSK supported by UE (given in UE
15 3090 5 QPSK category specific tables).
16 3762 5 QPSK Table to left (from 25.214) defines
17 4420 5 16QAM CQI for UE categories 1 to 6.
18 4748 5 16QAM
Based on 10% BLER.
19 5480 5 16QAM
The Algorithm to calculate CQI
value is not specified by 3GPP so
20 6101 5 16QAM
CQI depends on UE.
21 6793 5 16QAM
22 7168 5 16QAM
23 7168 5 16QAM
24 7168 5 16QAM
≥ 25 7168 5 16QAM

CQI Distribution
CQI distribution (very poor environment)
700000 100%
90%
Number of samples
600000
80%
500000 70%
400000 60%
50%
300000 40%
200000 30%
20%
100000
10%
0 0%
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
CQI value
 

CQI Distribution
Channel Quality Indicator
one counter for each CQI value

plus one for the failed decoding
CQI distribution gives an idea about the average CIR in that cell, can be so the basis of
dimensioning the Iub interface, optimization of power and other RF characteristics. Furthermore a
broad distribution gives indication about a big variance in the user distribution, it may be good to
deploy in such cases indoor solutions to separate users in buildings from those outdoor.

CQI Distribution – Nokia
Number of reports indicating a specific CQI
M5000C8 CQI_DIST_CL_0
…

CQI Distribution KPI – Nokia
KPI Formula
sum([CQI_DIST_CL_1]+2*[CQI_DIST_CL_2]+3*[CQI_DIST_CL_3]+4*[CQI_DIST_CL_4]+5*[CQI_DIST_CL_5]
+6*[CQI_DIST_CL_6]+7*[CQI_DIST_CL_7]+8*[CQI_DIST_CL_8]+9*[CQI_DIST_CL_9]+10*[CQI_DIST_CL_10]
+11*[CQI_DIST_CL_11]+12*[CQI_DIST_CL_12]+13*[CQI_DIST_CL_13]+14*[CQI_DIST_CL_14]+15*[CQI_DIST_
CL_15]+16*[CQI_DIST_CL_16]+17*[CQI_DIST_CL_17]+18*[CQI_DIST_CL_18]+19*[CQI_DIST_CL_19]+20*[CQI
_DIST_CL_20]+21*[CQI_DIST_CL_21]+22*[CQI_DIST_CL_22]+23*[CQI_DIST_CL_23]+24*[CQI_DIST_CL_24]+
25*[CQI_DIST_CL_25]+26*[CQI_DIST_CL_26]+27*[CQI_DIST_CL_27]+28*[CQI_DIST_CL_28]+29*[CQI_DIST_
CL_29]+30*[CQI_DIST_CL_30]) / 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_DIS
Average reported CQI
T_CL_22]+[CQI_DIST_CL_23]+[CQI_DIST_CL_24]+[CQI_DIST_CL_25]+[CQI_DIST_CL_26]+[CQI_DIST_CL_27
RNC_706b
]+[CQI_DIST_CL_28]+[CQI_DIST_CL_29]+[CQI_DIST_CL_30])
=
sum([M5000C9]+2*[M5000C10]+3*[M5000C11]+4*[M5000C12]+5*[M5000C13]+6*[M5000C14]
+7*[M5000C15]+8*[M5000C16]+9*[M5000C17]+10*[M5000C18]+11*[M5000C19]+12*[M5000C20]
+13*[M5000C21]+14*[M5000C22]+15*[M5000C23]+16*[M5000C24]+17*[M5000C25]+18*[M5000C26]+19*[M5000
C27]+20*[M5000C28]+21*[M5000C29]+22*[M5000C30]+23*[M5000C31]+24*[M5000C32]+25*[M5000C33]+26*[M
5000C34]+27*[M5000C35]+28*[M5000C36]+29*[M5000C37]+30*[M5000C38])
/ sum([M5000C8]+[M5000C9]+[M5000C10]+[M5000C11]+[M5000C12]+[M5000C13]+[M5000C14]
+[M5000C15]+[M5000C16]+[M5000C17]+[M5000C18]+[M5000C19]+[M5000C20]+[M5000C21]+[M5000C22]+[M5
000C23]+[M5000C24]+[M5000C25]+[M5000C26]+[M5000C27]+[M5000C28]+[M5000C29]+[M5000C30]+[M5000C
31]+[M5000C32]+[M5000C33]+[M5000C34]+[M5000C35]+[M5000C36]+[M5000C37] +[M5000C38])

CQI Distribution – Huawei
50331670 … 5033199 VS.CQI.1 … VS.CQI.30 Number of reports with CQI1 … CQI30
50331754 … 50331784 VS.UsedCQI0 … VS.UsedCQI30 Number of times the NodeB transmits data with CQI=0 … CQI30
A similar KPI as by Nokia can be created with the existing counters.

CQI Distribution – Ericsson
pmReportedCqi[0] Number of reports with CQI 0

CQI Distribution – Ericsson
Ericsson has also counters for the different HSDPA throughput on RLC excluding retransmissions (that can show somehow how
good are the HSDPA transmission conditions in the cells):
Number of times that the HS-DSCH DL user RLC throughput has been within a defined range during the ROP. The
user RLC throughput includes user data but excludes retransmissions.
The individual counter elements are stepped based on the following ranges:
[0]: 0 <= x < 25 kbps , [1]: 25 <= x < 50 kbps, [2]: 50 <= x < 100 kbps, [3]: 100 <= x < 200 kbps ...
[13]: 1100 <= x < 1200 kbps, [14]: 1200 <= x < 1400 kbps ...
[17]: 1800 <= x < 2000 kbps, [18]: 2000 <= x < 2500 kbps, [19]: 2500 <= x < 3000 kbps ...
[23]: 4500 <= x < 5000 kbps, [24]: 5000 <= x < 6000 kbps, [25]: 6000 <= x < 7000 kbps, [26]: 7000 <= x < 8000 kbps
[27]: 8000 <= x < 10000 kbps, [28]: 10000 <= x < 12000 kbps, [29]: 12000 <= x < 14000 kbps, [30]: 14000 <= x <
17000 kbps
pmHsDlRlcUserPack [31]: 17000 <= x < 20000 kbps, [32]: 20000 <= x < 24000 kbps, [33]: 24000 <= x < 28000 kbps, [34]: 28000 <= x <
etThp 34000 kbps
[35]: 34000 <= x < 40000 kbps, [36]: 40000 <= x < 50000 kbps, [37]: 50000 <= x < 60000 kbps, [38]: 60000 <= x <
80000 kbps
[39]: 80000 <= x < 100000 kbps, [40]: 100000 <= x < 130000 kbps, [41]: 130000 <= x kbps
Condition: Values are read periodically from an internal level counter that maintains the current throughput.
An individual counter element is incremented by one when a throughput sample is within its range.
For Multi Carrier connections, this counter is incremented only if this cell is the serving HS-DSCH cell, but then
includes packets transmitted in both the serving HS-DSCH cell and its secondary serving HS-DSCH cells.
Counter type: PDF
Sampling rate: 0.1 s

Static HSDPA Power
Node-B Tx power
Max power
Active MAC-D flow (s)
Transmitted Non HSPA power

carrier power
Static HSPA power
Power for Real time traffic
1-15 x HS-PDSCH (no PC, slow power adjustment due to HS-

SCCH)
HS-DPCCH (CQI based fast power control)

Power Measurements for Static HSDPA
Maximum
Non HSPA power Minimum
Average
Need to consider the non HSPA power only. Non HSPA power + static HSDPA power gives
transmitted carrier power

Dynamic HSDPA Power
Power
Transmitted carrier power
Maximum power
Transmission with
maximum HSDPA power
R99 RT load
target
1 2 R99 NRT overload
threshold
R99 NRT load
target
Non HSDPA power

time
HSDPA power not fixed, but slowly adjusted in dependence on the traffic in the cell
1) HSDPA users dominate

Downgrade R99 power threshold so that more power becomes available for HSDPA
2) R99 users dominate

Upgrade R99 power thresholds to that more power becomes available for R99

Power Measurements for Dynamic HSDPA
Maximum
Non HSPA power Minimum
Average
Maximum
Transmitted carrier power Minimum
Average
Need both the non HSPA and transmitted carrier power is considered. Transmitted carrier
power – non HSPA power gives the HSDPA power
Maximum
HSDPA power Minimum
Average

HSDPA Power Measurements Counters – Nokia
M1000C138 AVERAGE RATIO BETWEEN NON HSDPA POWER AND THE MAXIMUM POWER
M1000C139 ON HSDPA POWER DENOMINATOR
M1000C140 AVERAGE RATIO FOR ACTIVE NON HSDPA POWER AND THE MAXIMUM POWER
M1000C141 ACTIVE NON HSDPA POWER DENOMINATOR
M1000C236 MIN HSPA DL POWER (in dBm)
M1000C237 MAX HSPA DL POWER 8in dBm)
M1000C238 AVE HSPA DL POWER
M1000C239 HSPA DL POWER SAMPLES
M1000C144 DL DCH SELECTED DUE TO HSDPA POWER

Power Measurements Counters – Huawei
The following counters provide the transmitted carrier power (TCP) measurement values of a cell for assessing the downlink load state in
the cell.
67199618 VS.MeanTCP Mean Transmitted Power of Carrier for Cell
67199682 VS.MaxTCP Maximum Transmitted Power of Carrier for Cell
67199683 VS.MinTCP Minimum Transmitted Power of Carrier for Cell
The following counters provide the downlink non-HSPA TCP measurement values of a cell for assessing downlink non-HSPA power load
state in the cell.
Non-HSPA power is the power used to transmit data on the common channels, DPDCH, and DPCCH, including power consumed by loads
on the DPCCH and DPDCH when HSDPA users use SRB over DCH.
67202902 VS.MeanTCP.NonHS Mean Non-HSDPA Transmitted Carrier Power for Cell
67202900 VS.MaxTCP.NonHS Maximum Non-HSDPA Transmitted Carrier Power for Cell
67202901 VS.MinTCP.NonHS Minimum Non-HSDPA Transmitted Carrier Power for Cell
Cell loads are classified into non-HSPA power loads and HSPA power loads. HSPA power is the power used to transmit data on the HS-
PDSCH, HS-SCCH, E-AGCH, E-RGCH, and E-HICH.
The following counters provide the measurement values of power required to meet the guaranteed bit rate (GBR) for SC-HSDPA users in
an HSDPA cell. These measurement values are used to assess downlink load state in the cell.
67202984 VS.HSDPA.MeanRequiredPwr Mean Power Required by HS-DSCH for Cell
67202982 VS.HSDPA.MaxRequiredPwr Maximum Power Required by HS-DSCH for Cell
67202983 VS.HSDPA.MinRequiredPwr Minimum Power Required by HS-DSCH for Cell

Power Measurements Counters – Ericsson
pmTransmittedCarrierPower[0] TCP = -0.5 dBm
pmTransmittedCarrierPower[1] TCP = 0.5 dBm
… Proceed in steps of 1 dB
pmTransmittedCarrierPowerHs[0] HSDPA power = -0.5 dBm
pmTransmittedCarrierPowerHs[1] HSDPA power = 0.5 dBm
… Proceed in steps of 1 dB

HSDPA Serving Cell Change
Drift Serving
Source
Target
1. Radio Link Addition RNSAP
2. Radio Link Setup Request Request
NBAP
3. Radio Link Setup Response

NBAP
4. Radio Link Addition
RNSAP Response
5. ALCAP Iub Data Transport Bearer Setup (DCH) 6. ALCAP Iub Data Transport
Bearer Setup (DCH)
7. Radio Link RNSAP

8. Radio Link Reconfiguration Prepare Reconfiguration Prepare
NBAP 9. Radio Link Reconfiguration Ready NBAP
10. Radio Link Reconfiguration Prepare

NBAP
11. Radio Link Reconfiguration Ready
NBAP
12. Radio Link
RNSAP Reconfiguration Ready
13. ALCAP Iub Data Transport Bearer Setup (HS-DSCH)

14. ALCAP Iub Data Transport
Bearer Setup (HS-DSCH)

HSDPA Serving Cell Change
Drift Serving
Source
Target
15. Radio Link

RNSAP
Reconfiguration Commit
16. Radio Link Reconfiguration Commit
NBAP
17. Radio Link Reconfiguration Commit
NBAP
18. Physical Channel Reconfiguration
RRC
19. Physical Channel Reconfiguration Complete
RRC
Bearer Release (HS-DSCH) 21. ALCAP Iub Data Transport
Bearer Release (HS-DSCH)
22. Radio Link Deletion

23. Radio Link Deletion RNSAP
Request
Request NBAP
24. Radio Link Deletion
NBAP Response 25. Radio Link Deletion
RNSAP Response
Bearer Release (DCH) 27. ALCAP Iub Data Transport
Bearer Release (DCH)

HSDPA Serving Cell Change Measurements
Number of initiated HS-DSCH Serving Cell Changes (SCC)
One counter per cause

-causes depend on the implementation (vendor)
-1d or 1b events may be used as trigger, Active set updates as well.
Number of failed HS-DSCH Serving Cell Changes
one counter per cause

Possible causes,
-Node B resources (radio, baseband, UE,..)
-Transport resources
-
Number of successful HS-DSCH Serving Cell Changes

Serving Cell Change Analysis – Nokia
Number of serving cell changes per cause
M1008C213 HS-DSCH Serving Cell Changes started due to CPICH Ec/N0

M1008C214 HS-DSCH Serving Cell Changes started due to UL SIR error
M1008C215 HS-DSCH Serving Cell Changes started due to Active Set Update
M1008C216 HS-DSCH Serving Cell Changes started due to other reason
Number of successful serving cell changes
M1008C222 HS-DSCH Serving Cell Changes Intra BTS Serving Cell Changes Successful
M1008C223 HS-DSCH Serving Cell Changes Inter BTS Serving Cell Changes Successful

Serving Cell Change Analysis – Nokia
Number of failed serving cell changes
M1008C217 HS-DSCH Serving Cell Changes failed due to UE

M1008C218 HS-DSCH Serving Cell Changes failed due to BTS
M1008C219 HS-DSCH Serving Cell Changes failed due to Transport
M1008C220 HS-DSCH Serving Cell Changes failed due to AC
M1008C221 HS-DSCH Serving Cell Changes failed due to other reason
M1008C224 HS-DSCH Serving Cell Changes prevented due to Timer

Serving Cell Change Analysis – Huawei
KPI Formula
Service Cell Change Success Service Cell Change Success Ratio with SHO (H2H) = (HS-DSCH service cell change Success with SHO/HS-DSCH service cell
Ratio with SHO (H2H) change Attempt with SHO) x 100%
• Object: Cell =
• in % (VS.HSDPA.SHO.ServCellChg.SuccOut/VS.HSDPA.SHO.ServCellChg.AttOut) x 100%
With the counters:
67190699 VS.HSDPA.SHO.ServCellChg.SuccOut provides the number of successful HSDPA serving cell changes in a cell.
67190698 VS.HSDPA.SHO.ServCellChg.AttOut Number of Intra-RNC HSDPA Serving Cell Change Attempts for Cell
KPI Formula
H2H Intra-Frequency Hard H2H Intra-Frequency Hard Handover Success Ratio =(H2H Intra – frequency Hard Handover Success/H2H Intra - frequency
Handover Success Ratio Hard Handover Attempt) x 100%
• Object: Cell =
• in % (VS.HSDPA.HHO.H2H.SuccOutIntraFreq/VS.HSDPA.HHO.H2H.AttOutIntraFreq) x 100%
With the counters:
provides the number of successful intrafrequency HSDPA hard handover attempts without
67190703 VS.HSDPA.HHO.H2H.SuccOutIntraFreq
channel change in a cell.
provides the number of intra-frequency HSDPA hard handover attempts without channel
67190700 VS.HSDPA.HHO.H2H.AttOutIntraFreq
change in a cell.
Huawei names the HS inter frequency HO also ar SCC and has respective counters (not shown here).

Serving Cell Change Analysis – Ericsson
Incoming SCC attempts with HSDSCH/DCH - Number of attempted Serving HS-DSCH Cell Changes
pmNoHsCcAttempt
for which this cell was the target cell.
Successful incoming SCC with HSDSCH/DCH - Number of successful Serving HS-DSCH Cell
pmNoHsCcSuccess
Changes for which this cell was the target cell.
Incoming SCC attempts with HSDSCH/E-DCH - Number of attempted Serving E-DCH/HS-DSCH Cell
pmNoEulCcAttempt
Changes for which this cell was the target cell.
Successful incoming SCC with HSDSCH/E-DCH - Number of successful Serving E-DCH/HS-DSCH

pmNoEulCcSuccess
Cell Changes for which this cell was the target cell.

SHO Measurements for A-DCH
There is only one and one HSDPA serving cell at any time, anyway the associated DCH (A-DCH) can be in soft-
handover state, depending on the implementation, this can be basis for optimization. In some vendors case there
is an independent set of parameters for HSDPA active UEs. 3GPP defines UE should support up to 6 cells in the
active set, in the usually implementations it is restricted to 3.
Number of cells in the active set for HSDPA active UE
Replacements 1c
Additions 1a
Deletions 1b
Duration (per HSDPA Serving cell)
1 cell in the active set
2 cells in the active set
3 cells in the active set

Soft Handover Analysis for A-DCH - Nokia
Number of SHO attempts per event
M1007C53 CELL ADDITION REQUEST ON SHO FOR HSDPA MOBILITY

M1007C54 CELL DELETION REQUEST ON SHO FOR HSDPA MOBILITY
M1007C55 CELL REPLACEMENT REQUEST ON SHO FOR HSDPA MOBILITY
Number of SHO failures per event
M1007C56 CELL ADDITION FAILURE ON SHO FOR HSDPA MOBILITY

M1007C57 CELL DELETION FAILURE ON SHO FOR HSDPA MOBILITY
M1007C58 CELL REPLACEMENT FAILURE ON SHO FOR HSDPA MOBILITY
Treatment analogue to R99 DCH

Counters are updated in all source cells analogue to R99 DCH

Soft Handover Analysis for A-DCH - Nokia
TIME a cell belongs to an active set with size 1, 2 or 3
M1007C48 ONE CELL IN THE ACTIVE SET FOR HSDPA MOBILITY

M1007C49 TWO CELLS IN THE ACTIVE SET FOR HSDPA MOBILITY
M1007C50 THREE CELLS IN THE ACTIVE SET FOR HSDPA MOBILITY
SHO overhead analogue to R99 DCH

Soft Handover Analysis for A-DCH – Huawei/Ericsson
Huawei & Ericsson do not offer such counters (counters for SHO includes also the SHO measurements of A-DCH.

DC – HSDPA
f1 5 MHz
f2 5 MHz
f1 f1
f2 f2
Both carriers good f1 good only
f1
f2
f2 good only

DC-HSDPA – Channels
+ Common CHs + E-AGCH, E-RGCH, E-HICH
Primary serving cell
HS-DPCCH HS-SCCH
E-DPDCH/E-DPCCH HS-PDSCH
DPDCH/DPCCH
F-DFCH
UL DPCCH
HS-SCCH
HS-PDSCH
Secondary serving cell
• DC HSDPA UEs are assigned HS-DSCHs in the primary serving and secondary cell
• UL for DC HSDPA UEs transmitted via primary serving cell (no UL in secondary serving HS cell)
• the primary serving cell is carrying
• Full set of dedicated and common control channels
• UL transport channels E-DCH and control channels
• Secondary serving cell is having less signaling (maximum HS-DSCH capacity)
• Among common channels only CPICH is used
• E-AGCH, E-RGCH and E-HICH might by existent for dual cell HSUPA

DC – HSDPA Measurements – Nokia
M5000C328 SUM OF ACTIVE DC HSDPA USERS WITH TWO CARRIERS
M5000C329 SUM OF ACTIVE DC HSDPA USERS WITH ONE CARRIER
M5000C330 SUM OF CAPABLE DC HSDPA USERS
M5000C331 TTI SCHEDULED DC HSDPA USER FOR PRIMARY CARRIER WITH ONE CARRIER
M5000C332 TTI SCHEDULED DC HSDPA USER FOR SECONDARY CARRIER WITH ONE CARRIER
M5000C333 TTI SCHEDULED DC HSDPA USER FOR PRIMARY CARRIER WITH TWO CARRIER
M5000C334 TTI SCHEDULED DC HSDPA USER FOR SECONDARY CARRIER WITH TWO CARRIER
M5000C435 MC HSDPA DATA RECEIVED IN MAC-D PDUS
M5000C436 MC HSDPA DATA DISCARDED IN MAC-D PDUS
M5002C126 ACKNOWLEDGED MC HSDPA DATA FOR PRIMARY CELL
M5002C127 ACKNOWLEDGED MC HSDPA DATA FOR SECONDARY CELL
M5002C128 ORIGINAL MC HSDPA DATA FOR PRIMARY CELL
M5002C129 ORIGINAL MC HSDPA DATA FOR SECONDARY CELL
M5002C130 ORIGINAL HSDPA DATA
M1005C252 MAC-D SETUP ATTEMPT FOR DC-HSDPA
M1005C253 SUCCESSFUL MAC-D SETUP FOR DC-HSDPA
M1005C254 FAILED MAC-D SETUP FOR DC-HSDPA
M1006C209 RB SETUP ATTEMPT FOR DC-HSDPA
M1006C210 SUCCESSFUL RB SETUP FOR DC-HSDPA
M1006C211 RB SETUP FAIL FOR DC-HSDPA DUE TO NO REPLY
M1006C212 RB SETUP FAIL FOR DC-HSDPA DUE TO UE NACK
KPI Formula
sum([ACTIVE_DC_HSDPA_USERS_1C_SUM] +
Average number of active DC HSDPA users [ACTIVE_DC_HSDPA_USERS_2C_SUM])/sum([DENOM_CPC_USERS])
• RNC_5149c (KPI index in WCDMA16) =
sum([M5000C329] + [M5000C328])/sum([M5000C327])
The average number of active DC HSDPA users using either 1 or 2 Carriers.
Comment The counter in the KPI denominator is telling about CPC users but actually this is a general
denominator for number of HSPA users (including all multi carrier scenarios).

DC – HSDPA Measurements – Huawei
KPI Formula
Average Number
of DC-HSDPA VS.HSDPA.DC.PRIM.UE.Mean.Cell
Users VS.HSDPA.DC.SEC.UE.Mean.Cell
• on Cell
Comment This KPI measures the average number of DC-HSDPA users that use this cell as the primary or secondary carrier cell.
KPI Formula
HSDPA DC RAB
Setup Success (HSDPA DC RAB Setup Successes/HSDPA DC RAB Setup Attempts) x 100%
Ratio =
• on Cell, (VS.HSDPA.RAB.DC.SuccEstab/VS.HSDPA.RAB.DC.AttEstab) x100%
• in %
This KPI is used to check the RAB Setup Success Ratio of the HSDPA DC RAB service in an RNC or a cluster.
Comment
The RNC level KPI is calculated by aggregating all the cell counters.
Number of times that all the users configured in DC mode in a cell are scheduled by
50331719 VS.HSDPA.DCCfg. AnchorCarrierActedNum
AnchorCarrier during the measurement period
Total number of times DC-HSDPAenabled users are scheduled by the supplementary
50331720 VS.HSDPA.DCCfg.SupCarrierActed-Num
carrier
Total number of times DC-HSDPAenabled users are scheduled by the anchor and
50331721 VS.HSDPA.DCCfg.DualCarrierActed-Num
supplementary carriers at the same time
50332170 VS.DataOutput. DCHSDPA.Traffic MAC-ehs traffic volume of DC-HSDPA/ DC-HSDPA +MIMO users

DC – HSDPA Measurements – Ericsson
Ericsson offers one KPI for the HSDPA MC User Throughput - Priority Queue
KPI Formula
(HsDschResources.pmSumAckedBitsMcPqSpi00 + HsDschResources.pmSumAckedBitsMcPqSpi01 +
HsDschResources.pmSumAckedBitsMcPqSpi02 + HsDschResources.pmSumAckedBitsMcPqSpi03 +
HsDschResources.pmSumAckedBitsMcPqSpi14) / (0.002 * (
HsDschResources.pmSumNonEmptyUserBuffersMcPqSpi00 +
PINTHSMC_I_DLTP_UserPQ_L1 = HsDschResources.pmSumNonEmptyUserBuffersMcPqSpi01 +
HSDPA MC User Throughput - HsDschResources.pmSumNonEmptyUserBuffersMcPqSpi02 +
Priority Queue HsDschResources.pmSumNonEmptyUserBuffersMcPqSpi03 +
• In kbps, HsDschResources.pmSumNonEmptyUserBuffersMcPqSpi04 +
• On DU Radio Nodes HsDschResources.pmSumNonEmptyUserBuffersMcPqSpi05 +
HsDschResources.pmSumNonEmptyUserBuffersMcPqSpi14))

HS-FACH
HS CellFACH on DL, but not on UL
• There is a low UL performance because RACH used
• No ACK/NACK and CQI sending
• Blind repetition for HARQ
• Default CQIvalue for link adaptation
• Mobility based on cell reselection as usual in Cell_FACH
Example:
4 retransmissions
Original transmissions
HS-DPSCH

HS-FACH Measurements – Nokia
RNC counters:
M1001C705 UE SUPPORT FOR HS CELL_FACH
M1006C213 SUM OF UE OPERATING TIME IN ENHANCED CELL_FACH
M1006C214 NUM OF UE MEASURED IN ENHANCED CELL_FACH
M1006C215 CELL_DCH TO ENHANCED CELL_FACH ATTEMPTS
M1006C216 CELL_ DCH TO ENHANCED CELL_FACH SUCCESSFUL
M1006C217 ENHANCED CELL_FACH TO CELL_DCH ATTEMPTS
M1006C218 ENHANCED CELL_FACH TO CELL_DCH SUCCESSFUL
M1006C219 CELL_PCH TO ENHANCED CELL_FACH ATTEMPTS
M1006C220 CELL_PCH TO ENHANCED CELL_FACH SUCCESSFUL
M1006C221 ENHANCED CELL_FACH TO CELL_PCH ATTEMPTS
M1006C222 ENHANCED CELL_FACH TO CELL_PCH SUCCESSFUL
BTS counters:
M1006C249 RADIO BEARER CONFIGURED FOR HS-FACH DL
M5000C421 SUM OF USERS IN EFACH
M5000C422 MAX NUMBER OF USERS IN EFACH
M5000C437 NUMBER OF USER DATA FRAMES PROCESSED DL EFACH
M5000C438 NUMBER OF CONTROL DATA FRAMES PROCESSED DL EFACH
M5002C50 USER DATA VOLUME DL EFACH
M5002C51 CONTROL DATA VOLUME DL EFACH
M5002C52 USER DATA TRANSMITTED TIME DL EFACH
M5002C53 CONTROL DATA TRANSMITTED TIME DL EFACH

HS-FACH Measurements – Nokia
M1006C318 MAX NUMBER OF HS-FACH/R99-RACH USERS PER CELL

M1006C320 MAX NUMBER OF PCH USERS WITH H-RNTI ALLOCATED PER CELL
M1006C321 MAX NUMBER OF HSPA AND HS-FACH USERS PER CELL
KPI Formula
sum([U_DATA_VOL_DL_EFACH])*8 / 1000
HS-FACH data volume downlink
=
(in Mbit)
sum([M5002C50])*8 / 1000
KPI calculates the high speed CELL_FACH User Plane data volume sent by the MAC-ehs scheduler to the
Comment
UE.
KPI Formula
sum([U_DATA_VOL_UL_EFACH]) * 8 / 1000
HS-FACH data volume uplink
=
(in Mbit)
sum([M5002C54]) * 8 / 1000
KPI calculates the high speed CELL_FACH User Plane data volume received by the MAC-I scheduler from
Comment
the UE.

HS-FACH Measurements – Huawei
KPI Formula
E-FACH Traffic
Volume VS.CRNCIubBytesEFACH.Tx
• In byte
This KPI provides the number of downlink MAC PDU bytes sent by the CRNC on the E-FACH over the Iub interface in a
Comment
cell. The measurement is triggered when the CRNC sends downlink data on the E-FACH over the Iub interface.
KPI Formula
Mean Number of
VS.EFACHUEs
E-FACH Users
This KPI provides the average number of UEs that are carried on the E-FACH in the cell
Comment The system periodically samples the UEs that are carried on the EFACH. At the end of the measurement period, the
average number of UEs that are carried on the E-FACH in the measurement period is obtained by dividing the
accumulated value of sample data in the period by the number of samples.
73441122 VS.EDRXUEs Number of UEs Carried on the EFACH and Using E-DRX
73410512 VS.EFACHUEs Number of UEs carried on EFACH for Cell
73426171 VS.EFACHUEs.Max Maximum Number of UEs on E_FACH for Cell

HS-FACH Measurements – Ericsson
KPI Description Formula Unit Level
Packet-Switched (PS) Interactive HS-FACH User Hsdsch.pmSumHsFachRlcUserPacketThp /

PintHSFach_I_Tp_User kbps RNC
Throughput. Hsdsch.pmSamplesHsFachRlcUserPacketThp
Sum of all sample values recorded during a ROP for the number of established PS RABs in state CELL_FACH for UEs
pmSumHsFachPsIntRabEst
currently using HS-FACH.
Number of samples recorded within the ROP for pmSumHsFachPsIntRabEst.
Condition: Incremented by one when the value of the internal level counter is sampled, even when the sampled value is 0.
pmSamplesHsFachPsIntRabEst
Counter type: SCAN
On RNC
Sum of all sample values recorded during a ROP for total RLC throughput for DTCH (no signalling) on HS-FACH.
pmSumHsFachRlcTotPacketThp
The total RLC throughput includes both initial transmissions and retransmissions.
pmSamplesHsFachRlcTotPacketThp Number of samples recorded within the ROP for pmSumHsFachRlcTotPacketThp

Content
HSPA
 General Aspects
 HSDPA
 HSUPA

HSUPA Channels
or
Plus Plus
HSDPA DCH
One in the serving E-DCH cell

(Option)
One for all the cells that belong

to the E-DCH radio link set.
1-4 x HS-SCCH
HS-DPCCH
1-15 x HS-
E-AGCH
F-DPCH
PDSCH
E-DPCCH
E-RGCH
E-DPDCH
E-HICH
(1…3 )
(1...3)
(1...2 )
share one code
UL DPDCH: max. 64 kbit/s

(when E-DPCCH configured)

HSUPA Channels
The UE can have:

-1-2 E-DPDCH [4 possible in future (2xSF 2 +2xSF4), but with UL DPDCH max is 2]
-1-3 E-RGCH [max active set size can be 4, 3 implementation]
-1-3 E-HICH [max active set size can be 4, 3 implementation]
-E-AGCH
Serving E-DCH Cell and HS-DSCH serving cell are always identical [3GPP 25.309 (6.3.2)]
The E-DCH Dedicated Physical Data Channel (E-DPDCH) and E-DCH Dedicated Physical Control Channel
(E-DPCCH) are called E-DCH Dedicated Physical Channel (E-DPCH).

HSUPA UE Capability Classes
HSUPA UE capability classes (seen as in TS 25.306; Rel. 9):
max. 2 & 10 ms max. #. of max. # of Reference

E- DCH min.
E-DCH TTI E-DCH E-DCH Bits* / E-DCH Bits* / Modulation combination
Category SF
Codes support 10 ms TTI 2 ms TTI Class
1 1 4 10 ms only 7110 - QPSK 0.73 Mbps
2 2 4 10 & 2 ms 14484 2798 QPSK 1.46 Mbps
3 2 4 10 ms only 14484 - QPSK 1.46 Mbps
4 2 2 10 & 2 ms 20000 5772 QPSK 2.92 Mbps
5 2 2 10 ms only 20000 - QPSK 2.0 Mbps
6 4 2 10 & 2 ms 20000 11484 QPSK 5.76 Mbps
7 4 2 10 & 2 ms 20000 22996 QPSK & 16QAM 11.5 Mbps
8 4 2 2 ms only - 11484 QPSK 11.5 Mbps
9 4 2 2 ms only - 22996 QPSK & 16QAM 23 Mbps
• Category 7 is defined in 3GPP Rel. 7 and supports QPSK and 16 QAM in Uplink
• Categories 8 and 9 are defined in Rel. 9 and support DC-HSUPA

E-DCH Traffic Measurements
Number of E-DCH radio link establishments
From RRC FACH sub-state
From RRC DCH sub-state
Number of successful E-DCH radio link establishments
Per traffic category
Number of failed HSUPA setups
Causes (resources – RNC, BTS or

transport, UE)
Number of simultaneous E-DCH users per cell
Causes (resources – RNC, BTS or

transport, UE)

E-DCH Radio Link Set
Serving E-DCH cell Serving E-DCH Radio Link Set

Has to be the HSDPA Serving Cell Served by one Node B
Cell A
Cell A Cell B

DCH Radio Link Set
(Support of 4 cells in active set usually not given)
Cell B
Cell A
Cell B
Cell A
Cell C Cell D
Cell C
Cell A
Cell C
Cell B Cell D

Serving E-DCH cell

Cell from which the UE receives Absolute Grants from the Node B scheduler. A UE has one Serving E-DCH cell.
Serving E-DCH Radio Link Set

Set of cells which contains at least the Serving E-DCH cell and from which the UE can receive and combine one Relative Grant.
The UE has only one Serving E-DCH RLS. So the serving RLS is determined by the UTRAN if the cells in the
same Node B being in the E-DCH active set should also transmit the same RG like the E-DCH serving cell.
Non-Serving E-DCH Radio Link(‘s)

Cell’s which belong to the E-DCH active set but do not belong to the Serving EDCH RLS and from which the UE can receive one
Relative Grant. The UE can have zero, one or several non-serving E-DCH RL(‘s). The UTRAN wants to indicate to the UE, that
these non-serving E-DCH cells transmit independent RG’s.
DCH Radio Links

Cells which serve the DCH. Not every cell in the DCH active set is necessarily part of the E-DCH active set.

E-DCH Mobility
There is only one and one E-DCH serving cell at any time for one UE using HSUPA. The E-DCH can be in soft-
handover state and the Serving Cell can change. 3GPP defines UE should support up to 6 cells in the active set,
in the usually implementations it is restricted to 3.
Number of started E-DCH serving cell changes (in serving cell)
Causes
Number of successful E-DCH serving cell changes (in source cell)
Intra Node B
Inter Node B

Soft Handover Analysis for E-DCH - Nokia
Number of cell additions with E-DCH
M1007C67 CELL ADDITION ATTEMPT REQ BY UE TO E-DCH AS

M1007C68 CELL ADDITION SUCCESS TO EDCH ACTIVE SET
M1007C69 CELL NOT ADDED TO E-DCH ACTIVE SET BUT ADDED TO DCH AS
Cell addition here covers both event 1A and 1C

No counters for event 1B

Soft Handover Analysis for E-DCH - Nokia
TIME a cell belongs to an active set with size 1, 2 or 3
M1007C63 ONE CELL IN E-DCH ACTIVE SET DURATION

M1007C64 TWO CELLS IN E-DCH ACTIVE SET DURATION
M1007C65 THREE CELLS IN E-DCH ACTIVE SET DURATION
SHO overhead analogue to R99 DCH
Number of serving cell changes with E-DCH
M1008C239 E-DCH Serving Cell Changes started

M1008C240 E-DCH Intra BTS Serving Cell Change successful
M1008C241 E-DCH Inter BTS Serving Cell Change successful
M1008C242 E-DCH Downgraded to DCH in Serving Cell Change HS-DSCH Serving Cell

Handover Analysis for E-DCH – Huawei
KPI Formula
E-DCH Soft
(Successful Attempts to Add or Delete EDCH Links/Attempts to Add or Delete EDCH Links due to Soft Handover) x
Handover
100%
Success Ratio
=
• On Cell,
(VS.HSUPA.SHO.SuccOut/VS.HSUPA.SHO.AttOut) x 100%
• In %
Comment This KPI is used to check EDCH RL additions and deletions due to soft handover in a cell.
KPI Formula
E-DCH Cell
(Successful Attempts to Change EDCH Serving Cells/Attempts to Change EDCH Serving Cells due to Soft Handover
Change Success
or Multiple Links) x 100%
Ratio with SHO
=
• On Cell
(VS.HSUPA.SHO.ServCellChg.SuccOut/VS.HSUPA.SHO.ServCellChg.AttOut) x 100%
• In %
Comment This KPI is used to check the success ratio of HSUPA serving cell changes in soft handover status for cell.
KPI Formula
E-DCH Cell
Change Success (Successful Attempts to Change Serving Cell/Attempts to Change EDCH Serving Cells due to EDCH-to-EDCH Inter-
Ratio with Inter- Frequency Hard Handover Triggered by RNC) x 100%
HHO =
• On Cell (VS.HSUPA.HHO.E2E.SuccOutInterFreq/VS.HSUPA.HHO.E2E.AttOutInterFreq) x 100%
• In %
This KPI is used to check the E-DCH service cell change success ratio with the Inter-HHO procedure in an RNC or a
Comment
cluster.

Channel Switch Analysis for E-DCH – Huawei
KPI Formula
E2D Channel
(Successful Attempts to Switch Channel Type from EDCH to DCH/Attempts to Switch Change Type from EDCH to
Switch Success
DCH) x 100%
Ratio
=
• On Cell
(VS.HSUPA.E2D.Succ/VS.HSUPA.E2D.Att) x 100%
• In %
This KPI is used to check the channel switch success ratio when there is UE handover (switch) from E-DCH to DCH
Comment
in the same cell.
KPI Formula
D2E Channel
(Successful Attempts to Switch Channel Type from DCH to EDCH/Attempts to Switch Change Type from DCH to
Switch Success
EDCH) x 100%
Ratio
=
• On Cell
(VS.HSUPA.D2E.Succ/VS.HSUPA.D2E.Att) x 100%
• In %
This KPI is used to check the channel switch success ratio when there is UE handover (switch) from E-DCH to DCH
Comment
in the same cell.
KPI Formula
E2D Handover
(Successful Attempts to Switch Channel Type from EDCH to DCH/Attempts to Switch Change Type from EDCH to
Success Ratio
DCH) x 100%
with Inter HHO
=
• On Cell
(VS.HSUPA.HHO.E2D.SuccOutInterFreq/VS.HSUPA.HHO.E2D.AttOutInterFreq) x 100%
• In %
Comment This KPI is used to check the success ratio of HSUPA Inter-Frequency Hard Handover from EDCH to DCH in a cell.

Handover Analysis for E-DCH – Ericsson
E-DCH setup counters:
pmCapacityAllocAttServEDchUsers E-DCH setup attempts

pmCapacityAllocRejServEDchUsers E-DCH setup failures
pmNoServingCellReqDeniedEul E-DCH setup failure due to maximum number of users
EUL Cell Change KPI:

KPI Formula
PS_M_EULCC_S =
• PS Interactive EUL Cell Change success rate

100 * (UtranCell.pmNoEulCcSuccess / UtranCell.pmNoEulCcAttempt)
• This metric measures the success rate for EUL Cell
Change in target cell.
• WIth RNC meas.
• In %
EUL Reconfiguration KPI:
KPI Formula
PS_M_EULtoDCHRC_S =
• PS Interactive reconfiguration EUL to DCH success rate

• This metric measures the success rate for EUL to DCH 100 * (UtranCell.pmEulToDchSuccess / UtranCell.pmEulToDchAttempt)
reconfiguration
• With RNC meas
• In %

DL Codes for HSUPA
SF = 1
SF = 2
SF = 4
SF = 8
SF = 16
SF = 32 Codes for 15
HS-PDSCH's
SF = 64 (
SF = 128
SF = 256 1 code left
Code Image Example: FACH/PCH separated, with max. 1 HS-SCCH, 1E-HICH/E-RGCH/E-

AGCH and 15 HS-PDSCH (other allocations possible!)

DL Codes for HSUPA
HSUPA can only be set up together with HSDPA. For HSUPA, code allocation for E-AGCH, E-RGCH, and
E-HICH is additional necessary. The channelization codes spreading factors (SFs) are:
• 16 for HS-PDSCHs
• 128 for HS-SCCHs
• 128 for E-RGCH / E-HICH
• 256 for E-AGCH
The maximum number of HS-SCCH is three for the separate type of common channel. Combined type of
common channel is possible. The following maximum configurations are currently available:
• PCH and FACH are mapped on the same S-CCPCH:

– 14 HS-PDSCHs
– 4 HS-SCCHs
– 1 E-HICH/E-RGCH and 1 E-AGCH
All HS-PDSCH, HS-SCCH, E-AGCH and E-RGCH/E-HICH channelization codes an individual UE can
receive must be subordinated to the same scrambling code tree, that is the primary scrambling code.

DL Power with HSUPA
Node-B Tx power
Max power
Active MAC-D flow (s)
or MAC-es flow (s)
Transmitted
carrier power
PHSPA = ΣPHS-PDSCH+ΣPHS-SCCH+ΣPE-AGCH +ΣPE-RGCH +ΣPE-HICH
Pnon-HSPA = Ptotal – PHSPA

non HSPA power
NBAP: COMMON MEASUREMENT REPORT

DL Power with HSUPA
The non-HSPA transmitted carrier power (TCP) refers to the amount of TCP of all codes which are not used
for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH, or E-HICH. The non-HSPA TCP is the difference between
the total TCP on one downlink carrier from one UTRAN access point and the TCP of all codes which are not
used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH, or E-HICH, i.e. the HSPA TCP (PHSPA). In other words,
PHSxPA is calculated as follows:
PHSPA = ΣPHS-PDSCH+ΣPHS-SCCH+ΣPE-AGCH +ΣPE-RGCH +ΣPE-HICH
The resulting Pnon-HSPA is used to calculate the non-HSPA power ratio which will be included in a NBAP:
COMMON MEASUREMENT REPORT message.
Pnon-HSPA = Ptotal – PHSPA

Dynamic UL Noise Rise with HSUPA
UL noise rise
Maximum noise rise
Received total wideband power
R99 RT load
target
1 2 R99 NRT overload
threshold
R99 NRT load
target
Non HSUPA wideband power

time
Allowed UL noise rise for R99 not fixed, but slowly adjusted in dependence on the traffic in the cell
1) HSUPA users dominate

Downgrade R99 wideband power threshold so that more noise rise is allowed due to HSUPA
2) R99 users dominate

Upgrade R99 wideband power thresholds to that more noise rise is allowed due to R99

Noise Rise Measurements for Dynamic HSUPA
Maximum
Received total wideband power Minimum
Average
Only the received total wideband power (i.e. the noise rise due to the total traffic) can
be measured directly !!
Maximum
Wideband power due to HSUPA Minimum
Average
Maximum
Wideband power due to R99 Minimum
Average
The wideband power due to a certain type of service must be calculated from the RTWP
and the service specific load factor !!

Noise Rise Measurements for HSUPA – Nokia 1/2
Only the received total wideband power (i.e. the noise rise due to the total traffic) can be measured directly !!
Nokia has the following measurements:
Counter Name Incremented when
M1000C0 AVE_PRXTOT_CLASS_0 (Lrt<=UnloadedRT) AND (Lnrt<=UnloadedNRT)
• Class 0 is detected when own cell is considered unloaded (or very low load):
• LRT  UnloadedRT (2%) and LNRT  UnloadedNRT (1%)
• UnloadedRT and UnloadedNRT are RNC internal parameters
M1000C2 AVE_PRXTOT_CLASS_1 HSUPA disabled:
(PrxTotal<=PrxTarget–PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))
HSUPA enabled:
(PrxNonEDPCH<=PrxTarget–PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))
(PrxTotal>PrxTarget–PrxOffset) AND (PrxTotal<PrxTarget) AND ((Lrt>UnloadedRT) OR
(Lnrt>UnloadedNRT))
HSUPA enabled:
(PrxNonEDPCH>PrxTarget–PrxOffset) AND (PrxNonEDPCH<PrxTarget) AND ((Lrt>UnloadedRT)
OR (Lnrt>UnloadedNRT))
(PrxTotal>=PrxTarget) AND (PrxTotal<PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR
(Lnrt>UnloadedNRT))
HSUPA enabled:
(PrxNonEDPCH>=PrxTarget) AND (PrxNonEDPCH<PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT)
OR (Lnrt>UnloadedNRT))
(PrxTotal>=PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))
HSUPA enabled:
(PrxNonEDPCH>=PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))

Noise Rise Measurements for HSUPA – Huawei
50331850 VS.HSUPA.LoadOutput.0 UL load factor = 0.25 dB (0.056)


50331870 VS.HSUPA.LoadOutput.20 UL load factor = 17 dB (0.980)
50331876 VS.HSUPA.Over-LoadNum Number of times the uplink is overloaded in a cell
The preceding counters indicate the distribution of cell load (that is, the ratio of the actual RTWP in a cell to the reference RTWP) on the air
interface during a measurement period.
The uplink Uu interface load is sampled every 2 ms within a measurement period. The corresponding counter is incremented by 1 each
time the uplink Uu interface load is within the correponding load range.

67199617 VS.MeanRTWP Mean Power of Totally Received Bandwidth for Cell
67199680 VS.MaxRTWP Maximum Power of Totally Received Bandwidth for Cell
67199681 VS.MinRTWP Minimum Power of Totally Received Bandwidth for Cell
These counters provide the received total wideband power (RTWP) measurement values of a cell for assessing the uplink interference
level and uplink loads in the cell.
73415859 VS.HSUPA.MeanRSEPS Average Received Scheduled E-DCH Power Share for Cell
73403758 VS.HSUPA.MaxRSEPS Maximum Received Scheduled E-DCH Power Share for Cell
73403760 VS.HSUPA.MinRSEPS Minimum Received Scheduled E-DCH Power Share for Cell
Received scheduled E-DCH power share (RSEPS) is the ratio of E-DCH channel interference to the total interference of the cell, which is
measured on the NodeB. For details. Values of these counters are used to calculate uplink uncontrollable loads and they serve as data
input for the uplink admission algorithm and load reshuffling (LDR) algorithm.

Noise Rise Measurements for HSUPA – Ericsson
Ericsson offers the following counters for the load factors:
pmLDch[0] UL load factor = 0.01 (R99 users)

… Proceed in steps of 0.02
pmLEDchTot[0] UL load factor = 0.01 (HSUPA users)
… Proceed in steps of 0.02
pmLdch - The measured uplink Uu load of a cell for users configured with only Release 99 DCH on the uplink. Load contributions from
DPDCH, DPCCH, and HS-DPCCH are included. The sampled value represents a load factor with range 0..1, where 0 means no load
and 1 is maximum possible load.
pmLedchTot - The measured uplink Uu load of a cell that is caused by users configured with an E-DCH. Load contributions from E-
DPDCH (both scheduled and not scheduled), E-DPCCH, DPCCH, and DPDCH (if one is configured) are included, but not that from the
HS-DPCCH. The sampled value is a load factor and is unitless with range 0..1, where 0 means no load and 1 is maximum possible
load.

HSUPA Users per Cell
• The maximum number of HSPA users is given by

features and defined with parameters:
• The measurements of the number of HSUPA
users is done to monitor the resource utilization
on cell and BTS level
128 users!
HSDPA Capable cell
HSDPA Capable UEs

HSUPA Users per Cell – Nokia 1/2
Counter Name
M1002C271 DUR_HSUPA_NO_USERS
M1000C365 DURATION OF ACTIVE HSUPA USERS - 21 TO 24 SIMULTANEOUS USERS
M1000C368 DURATION OF ACTIVE HSUPA USERS -33 TO 36 SIMULTANEOUS USERS
HSUPA Users per Cell – Nokia 2/2
M1000C387 DURATION OF ACTIVE HSUPA USERS - 113 OR MORE USERS
M1000C388 MAX NUMBER OF HSUPA USERS PER SERVING CELL
M1000C389 SUM OF HSUPA USERS IN SERVING CELL
M1000C390 DURATION OF ACTIVE HSDPA USERS - 73 TO 80 SIMULTANEOUS USERS
M1000C393 DURATION OF ACTIVE HSDPA USERS - 113 OR MORE SIMULTANEOUS USERS
M1000C283 MAX NUMBER OF HSUPA USERS PER CELL
M1000C286 SUM OF HSUPA USERS PER CELL
M1000C287 HSUPA USERS PER CELL DENOMINATOR

HSUPA Users per Cell – Huawei
67203850 VS.HSUPA.UE.Mean.Cell Average Number of HSUPA UEs in a Cell
73403761 VS.HSUPA.UE.Max.Cell Maximum Number of HSUPA UEs in a Cell
73410507 VS.HSUPA.16QAM.UE.Mean.Cell Average Number of HSUPA 16QAM UEs in a Cell
Average Number of HSUPA 16QAM UEs in a Cell

73394088 VS.HSUPA.16QAM.UE.Mean.Cell.DENO
(Denominator)
Average Number of HSUPA 16QAM UEs in a Cell

73394087 VS.HSUPA.16QAM.UE.Mean.Cell.NUM
(Numerator)

HSUPA Users per Cell – Ericsson
pmNoSchEdchEul [0] Duration of cell with 0 HSUPA users

… Proceed in steps of 1 HSUPA user
… Proceed in steps of 5 users
pmNoSchEdchEul [14] Duration of cell with 34.5 HSUPA users
… Proceed in steps of 10 users
pmNoSchEdchEul [19] Duration of cell with 84.5 HSUPA users

KPI Formula
PintEul_U_User =
• PS Interactive EUL Users

• The average number of PS UtranCell.pmSumBestPsEulRabEstablish / UtranCell.pmSamplesBestPsEulRabEstablish
Interactive EUL users per
UtranCell.
• On RNC level
KPI Formula
PintEul2ms_U_User =
• PS Interactive EUL 2ms TTI

Users UtranCell.pmSumBestPsIntEulTti2RabEst/UtranCell.pmSamplesBestPsIntEulTti2RabEst
• The average number of PS
Interactive EUL 2ms TTI users
per UtranCell.

DU and Baseband Radio Node
Number of rejected attempts to allocate resources for new Serving E-DCH user (related to
pmCapacityAllocRejServEDchUsers
pmCapacityLimitServEDchUsers).
pmSamplesCapacityServEdchUsers Number of samples in pmSumCapacityServEDchUsers.
Aggregate of all sample values (measurement_value) recorded within the ROP for number of
pmSumCapacityServEDchUsers
Serving E-DCH users.
pmCapacityAllocAttServEDchUsers Number of attempts to allocate serving E-DCH user.
Baseband Radio Node
pmCapacityLimitServEDchUsers Licensed limit for number of Serving E-DCH users in the cell.
The distribution of the number of Serving E-DCH users, as percentages of the corresponding
pmCapacityOfServEDchUsers
license limit.
DU Radio Node
The distribution of the number of Serving E-DCH users, as percentages of the corresponding
pmCapacityServEDchUsers
license limit.

HSUPA Throughput – Nokia
M5000C320 HSUPA MACE PDUS WITH 2MS TTI
M5000C321 HSUPA MACE PDUS WITH 10MS TTI
M5000C322 HSUPA MACE PDU DATA WITH 2MS TTI
M5000C323 HSUPA MACE PDU DATA WITH 10MS TTI
M5000C324 SUM OF HSUPA USERS WITH 2MS TTI
M5000C325 SUM OF HSUPA USERS WITH 10MS TTI
M5000C326 HSUPA USERS DENOMINATOR
M5002C38 UE HSUPA THROUGHPUT CLASS 00 (TP <= 32 kbps)
M5002C39 UE HSUPA THROUGHPUT CLASS 01 (32 kbps < TP <= 64 kbps)
M5002C49 UE HSUPA THROUGHPUT CLASS 11 (TP > 4096 kbps)

HSUPA 2ms TTI Utilization and User Throughput – Nokia
KPI Formula
100 *MAC-e data received with 2 ms TTI by BTS /MAC-e data received with 2 ms and 10
E-DCH 2ms TTI utilization ms TTI by BTS
• In % =
100*sum([M5000C322])/sum([M5000C322] + [M5000C323])
Comment the ratio of MAC-e data received with 2 ms TTIs and total MAC-e data received by BTS.
KPI Formula
Sum([MACE_PDU_DATA_2MS_TTI]+[MACE_PDU_DATA_10MS_TTI])*8/
Average HSUPA user throughput Sum(([MACE_PDUS_2MS_TTI]/500)+([MACE_PDUS_10MS_TTI]/100))
• In kbps =
Sum([M5000C322]+ [M5000C323])*8/Sum(([M5000C320]/500)+ ([M5000C321]/100))
Average HSUPA end user throughput calculated as sum of MAC-e / MAC-i data volume
updated only for serving cell divided by sum of activity time coming from all active HSUPA
Comment users .
Weights 500 and 100 in denominator are used to calculated active transmission time in
seconds out of TTIs.

MAC-e BLER– Nokia
KPI Formula
100-100* sum([MACE_PDU_RETR_00_COUNTER]) sum([MACE_PDU_RETR_00_COUNTER] +

[MACE_PDU_RETR_01_COUNTER] + [MACE_PDU_RETR_02_COUNTER] +
MAC- e scheduler efficiency [MACE_PDU_RETR_09_COUNTER] + [MACE_PDU_RETR_10_COUNTER] +
• In % [MACE_PDU_RETR_11_COUNTER] + [MACE_PDU_RETR_12_COUNTER] +
[MACE_PDU_HARQ_FAIL_COUNTER])
=
100-100* sum([M5000C128]) / sum([M5000C128] + [M5000C129] + [M5000C130] + [M5000C131]
+ [M5000C132] + [M5000C133] + [M5000C134] + [M5000C135] + [M5000C136] + [M5000C137] +
[M5000C138] + [M5000C139] + [M5000C140] + [M5000C142])
measured Block Error Rate for HSUPA Radio Bearers in Uplink Block Error Rate calculated based
Comment on HARQ first and successful transmissions compared to all successful transmissions and failed
transmissions

HSUPA Throughput – Huawei
KPI Formula
Mean Throughput VS.HSUPA.MeanChThroughput
for One HSUPA
User With NodeB counters=
• On Cell (VS.HSUPA.2msTTI.Traffic + VS.HSUPA.10msTTI.Traffic)/ (VS.HSUPA.2msPDU.TTI.Num x 0.002 +
• In kbps VS.HSUPA.10msPDU.TTI.Num x 0.01)
This counter indicates the mean uplink throughput for ONE HSUPA UE in a cell. When the data is received in HSUPA active
cells, the RNC measures the data transfer time of all the UEs and the total bytes received in the cell. At the end of the
measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean uplink throughput of
Comment MAC-d flow in the cell. The RLC header and the retransfer data are excluded.
It is recommended that you use the NodeB counters in the following formula to calculate the single user throughput. These
NodeB counters measure the actual transmission rate sampled every transmission time interval (TTI) over
the air interface. In this case, the value of this KPI is more accurate for UEs.
KPI Formula
Mean Throughput
for One HSUPA
Cell VS.HSUPA.Thruput.ROTAll/ (VS.HSUPA.DataTtiNum x 0.002)
• On NodeB
• In kbps
This counter provides the Mean HSUPA Cell Throughput when at least one HSUPA UE is transmitting data during the entire
measurement period. When the data (including SRB and TRB data) of HSUPA UEs is received in HSUPA active cells, the
NodeB measures the total data that UEs successfully receive at the MAC-e/i layer in the serving cell. At the same time, the
NodeB measures the number of TTIs when at least one HSUPA UE is transmitting data to obtain the total transmission
Comment
duration. (If there are multiple Ues transmitting data in a TTI, this number is increased by one.) At the end of the measurement
period, the NodeB divides the total successfully received data by the total transmission duration to obtain the average
throughput at the MAC-e/i layer in one HSUPA cell. When a UE performs a softer handover, the data of this UE is calculated in
both the original and target cells.

HSUPA Throughput Counters – Huawei
50332551 VS.HSUPA.Thruput Total traffic volume of HSUPA users in a cell
VS.HSUPA.Thruput.ROTAll
50341883 Cell throughput of HSUPA users under all uplink Uu loads
50342552 VS.HSUPA.MeanBitRate Average throughput of HSUPA users in a cell
50342553 VS.HSUPA.MeanBitRate.WithData Average throughput of HSUPA users in a cell when data is transmitted
50332386 VS.HSUPA. 2msTTI.Traffic Traffic of Mac-e/ Mac-i PDUs received from 2 ms TTI HSUPA users in a cell
50332387 VS.HSUPA. 10msTTI.Traffic Traffic of Mac-e/ Mac-i PDUs received from 10 ms TTI HSUPA users in a cell

MAC-e Counters – Huawei
50331888 VS.HSUPA.PDUNum Number of successfully received MAC-e/MAC-I PDUs from the UE in a cell
50331889 VS.HSUPA.RetransPDUNum Number of MAC-e/ MAC-i PDUs to be retransmitted by the UE in a cell
50331885 VS.HSUPA.ACKTotal Number of transmitted ACKs
50331886 VS.HSUPA.NACK Total Number of transmitted NACKs
50332379 VS.HSUPA.2msPDU.TTI.Num Number of TTIs in which HSUPA 2 ms Mac-e/Mac-i TRBs are received in a cell
50332380 VS.HSUPA.10msPDU.TTI.Num Number of TTIs in which HSUPA 10 ms Mac-e/Mac-i TRBs are received in a cell
50332386 VS.HSUPA.2msTTI.Traffic Traffic of Mac-e/ Mac-i PDUs received from 2 ms TTI HSUPA users in a cell
50332387 VS.HSUPA.10msTTI.Traffic Traffic of Mac-e/ Mac-i PDUs received from 10 ms TTI HSUPA users in a cell

HSUPA Throughput KPIs – Ericsson
Packet-Switched (PS) Interactive EUL User
Eul.pmSumEulRlcUserPacketThp /
PintEUL_I_UlTp_User Throughput, Uplink kbps RNC
Eul.pmSamplesEulRlcUserPacketThp
• in a measurement period of 15 minutes.
DU Radio
Nodes,
EUL 10 ms TTI User Throughput EDchResources.pmSumAckedBitsCellEulTti10 / (0.01 *
PINTEUL10ms_I_ULTP_User_L1 kbps Baseband
EDchResources.pmNoActive10msFramesEul)
Radio Nodes,
RBS 6402
DU Radio
Nodes,
EUL 2 ms TTI User Throughput EDchResources.pmSumAckedBitsCellEulTti2 / (0.002 *
PINTEUL2ms_I_ULTP_User_L1 kbps Baseband
EDchResources.pmNoActive2msFramesEul)
Radio Nodes,
RBS 6402
DU Radio
(EDchResources.pmSumAckedBitsCellEulTti10 + Nodes,
EUL Cell Throughput
PINTEUL_I_ULTP_L1 EDchResources.pmSumAckedBitsCellEulTti2) / (0.002 * kbps Baseband
EDchResources.pmNoActive2msIntervalsEul) Radio Nodes,
RBS 6402
DU Radio
Nodes,
EUL 10 ms TTI Cell Throughput EDchResources.pmSumAckedBitsCellEulTti10 / (0.01 *
PINTEUL10ms_I_ULTP_L1 kbps Baseband
EDchResources.pmNoActive10msIntervalsEulTti10)
Radio Nodes,
RBS 6402
DU Radio
Nodes,
EUL 2 ms TTI Cell Throughput EDchResources.pmSumAckedBitsCellEulTti2 / (0.002 *
PINTEUL2ms_I_ULTP_L1 kbps Baseband
EDchResources.pmNoActive2msIntervalsEulTti2)
Radio Nodes,
RBS 6402
EDchResources.pmSumAckedBitsCellEulTti2Td / (0.002 * DU Radio

PINTEUL2msTd_I_ULTP_Cell_L1 EUL 2 ms TTI TD Cell Throughput kbps
EDchResources.pmNoActive2msFramesEulTd) Nodes

EUL BLER – Ericsson
PINTEUL10ms_I_Bler EUL BLER on RNC level for EUL10ms users. 100 * % RNC
Values of all pmEulHarqTransmTti10PSRabs (UtranCell.pmEulHarqTransmTti10Failure /
ranges are added. (UtranCell.pmEulHarqTransmTti10PsRabs
+
UtranCell.pmEulHarqTransmTti10Failure))
PINTEUL2ms_I_Bler EUL BLER on RNC level for EUL2ms users. 100 * % RNC
Values of all pmEulHarqTransmTti2PSRabs (UtranCell.pmEulHarqTransmTti2Failure /
ranges are added. (UtranCell.pmEulHarqTransmTti2PsRabs +
UtranCell.pmEulHarqTransmTti2Failure))

HS-Cell RACH
With this feature in the uplink direction the E-DCH can be used in the Cell_FACH state
• 3GPP Rel8 UEs required

• Only UE categories that supports continuous HS-DSCH data reception are able to support HS
Cell_FACH feature
• UEs 1-4 and 11 Categories are not HS Cell_FACH capable

• UEs 5-10,12 and higher Categories are HS Cell_FACH capable
UE Rel8
UE Rel7
In DL - HS-DSCH In DL - HS-DSCH
In UL - RACH IN UL - E-DCH

HS-Cell RACH Measurements – Nokia
Counter ID Counter name
M1006C327 HS-FACH ABNORMAL RELEASE
M5000C481 SUM OF USERS IN HS CELL FACH WITH HS UL
M5000C482 MAX NUMBER OF USERS IN HS CELL FACH WITH HS UL
M5000C483 SUM OF USERS IN HS CELL FACH
M5000C484 MAX NUMBER OF USERS IN HS CELL FACH
M5000C485 DENOMINATOR FOR HS CELL FACH USERS
M5000C486 MINIMUM HIGH SPEED CELL FACH USERS LOAD
M5000C487 AVERAGE HIGH SPEED CELL FACH USERS LOAD
M5000C488 MAXIMUM HIGH SPEED CELL FACH USERS LOAD
M5000C489 AVERAGE COMMON EDCH RESOURCE USAGE
M5000C490 MAXIMUM COMMON EDCH RESOURCE USAGE
M5000C491 AVAILABLE COMMON E-DCH RESOURCES
M5000C492 DENOMINATOR FOR HS CELL FACH USERS WITH HS UL
M5006C71 AVERAGE NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WITH HS RACH
M5006C72 MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS WITH HS RACH
M5006C73 AVERAGE NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS
M5006C74 MAXIMUM NUMBER OF ACTIVE HIGH SPEED CELL_FACH USERS
M5006C75 AVAILABLE NUMBER OF HIGH SPEED CELL_FACH USERS WITH HS RACH

HS-Cell RACH Measurements – Nokia
M1006C319 MAX NUMBER OF HS-FACH/HS-RACH USERS PER CELL
M1006C320 MAX NUMBER OF PCH USERS WITH H-RNTI ALLOCATED PER CELL
M5000C460 CONFIGURED HS-RACH SIGNATURES
M5000C461 NUMBER OF SUCCESSFULLY ACKNOWLEDGED HS-RACH PREAMBLES

HS-Cell RACH Measurements – Huawei
KPI Formula
E-RACH Traffic
Volume
VS.CRNCIubBytesERACH.Rx
• In byte
• On Cell
This KPI provides the bytes of UL MAC PDUs (including the signaling data and the service data, not including the FP header)
Comment
received by the CRNC over the ERACH FP on the Iub interface.
73423349 VS.ERACH.Estab.MaxTime Maximum Service Setup Duration on an ERACH for Cell

73441136 VS.ERACH.Estab.MeanTime Average Service Setup Duration on an ERACH for Cell
73423352 VS.ERACH.Estab.MinTime Minimum Service Setup Duration on an ERACH for Cell
73441137 VS.EFACH.Estab.MeanTime Average Service Setup Duration on an EFACH for Cell
73441118 VS.ERACHUEs Number of UEs Carried on ERACH for Cell
73426172 VS.ERACHUEs.Max Maximum Number of Ues on E_RACH for Cell
73441170 VS.CRNCIubBytesERACH. Rx Number of Bytes over Iub ERACH for Cell
50332250 VS.ERACH.OccupiedNum.Mean Mean used Common E-DCH number in one cell (NodeB counter)
50332251 VS.ERACH.OccupiedNum.Max Max used Common E-DCH number in one cell (NodeB counter)
50332410 VS.ERACH.Thruput Throughput of ERACH users at the Mac-i layer in a cell (NodeB counter)

HS-Cell RACH Measurements – Ericsson
KPI Description
Values are read periodically from an internal level counter and added to this counter.
pmSumEulFachPsIntRabEst The level counter maintains the current number of established PS RABs in state
CELL_FACH for UEs currently using EUL-FACH.
pmSamplesEulFachPsIntRabEst Number of samples recorded within the ROP for pmSumEulFachPsIntRabEst.
Payload in the uplink for the PS RAB on EUL-FACH. SRB is excluded. Payload traffic
pmUlTrafficVolumePsIntEulFach volume includes user data, Medium Access Control (MAC) and Radio Link Control (RLC)
header information and retransmissions, but not control frames.
Number of abnormal disconnections from common channels (i.e.CELL_FACH state) for
pmNoCellFachDiscAbnormEulFach
EUL-FACH users.
Number of MAC-is PDUs, corresponding to the SRB with TTI = 10 ms, which the MAC-is
re-ordering function could not deliver within the ROP. This applies only to Ues in
pmEulFachMacisPduTti10UndelivSrb CELL_FACH using EUL-FACH. A MAC-is PDU cannot be delivered if it has a TSN less
than that of a PDU received earlier and is received outside the reception window defined
for the MAC-is re-ordering function.
Number of MAC-is PDUs, corresponding to the PS RBs with TTI = 10 ms, which the
MAC-is re-ordering function could not deliver within the ROP. This applies only to Ues in
pmEulFachMacisPduTti10UndelPsRab CELL_FACH using EUL-FACH. A MAC-is PDU cannot be delivered if it has a TSN less
than that of a PDU received earlier and is received outside the reception window defined
for the MAC-is re-ordering function.
Number of MAC-is PDUs, corresponding to the SRB with TTI = 10 ms, which have been
pmEulFachMacisPduTti10DelivSrb delivered to MAC-d within the ROP by the MAC-is re-ordering function for UEs in
CELL_FACH using EUL-FACH.
Number of MAC-is PDUs, corresponding to the PS RBs with TTI = 10 ms, which have
pmEulFachMacisPduTti10DelPsRabs been delivered to MAC-d within the ROP by the MAC-is re-ordering function for UEs in
CELL_FACH using EUL-FACH.

HS-Cell RACH Measurements – Ericsson
PS Interactive EUL-FACH Users

UtranCell.pmSumEulFachPsIntRabEst /
PintEulFach_U_User The average number of PS Interactive EUL- RNC
UtranCell.pmSamplesEulFachPsIntRabEst
FACH users per UtranCell.

Content
HSPA
 General Aspects
 HSDPA
 HSUPA

HSDPA Call – RRC Connection Setup
UE HSDPA capability class
RRC connection setup in principle like for any other service

UE indicates HSDPA capability class

HSDPA Call – RL and RB Setup
RNTI on HS-DSCH
RL and RB setup in principle like for any other service

UE gets RNTI for HS-DSCH

HSDPA Call – Capacity Allocation
Instantaneous rate
40 packets / 10 ms = 4000 packets / s
Throughput
206 packets / 0.476 s = 433 packets / s
(first allocation 20:46:16.150
last allocation 20:46:16.626)
Capacity allocation = instantaneous number of MAC-d PDUs which can be sent by the RNC to
Node B within a short time
Throughput = total number of MAC-d PDUs sent by the RNC to Node B over bigger time scale

05 6275 Hspa E01 KH Mo

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

05 6275 Hspa E01 KH Mo

Загружено:

Авторское право:

Доступные форматы

Contents

Key Performance Indicators for UMTS and HSPA

00-1 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

00-2 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

00-3 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

The RB’s can be multiplexed with transport channel type

In Rel 99: only DCH/DCH possible

00-4 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

RRC idle 3GPP 25.331 (8.5.21)

CELL_PCH URA_PCH CELL_FACH

HS-DSCH + DCH / DCH HS-DSCH / DCH

DCH / E-DCH* CELL_DCH HS-DSCH / E-DCH

HS-DSCH + DCH / E-DCH + DCH HS-DSCH + DCH / E-DCH*

TCH combinations for UL / DL, * not likely to be implemented

00-5 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

00-6 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

HSDPA Capable UEs

HSDPA Capable cell

Node B Rel. 99 Node B with HSDPA

In the Release 5 implementation the radio bearer can only be configured to

Ather configuration possibilities require support of Rel. 6 Ues and latter:

- HSDPA DL/HSUPA UL SRB on DCH (in Dl and UL);

00-8 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

18 15 1 QPSK/16QAM with MIMO or 64QAM only 21.1 or 28 Mbps

00-9 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

00-10 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

RRC idle 3GPP 25.331 (8.5.21)

CELL_PCH URA_PCH CELL_FACH

DCH / DCH HS-DSCH + DCH / DCH

00-11 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

HS-DPCCH and the SRB

(SRB can use HS-PDSCH

Needed for UL data

00-12 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

HSDPA MAC-hs Retransmissions

00-13 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

KPI Formula (with short names)

00-14 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

Counter ID Counter Name Counter Description

00-15 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

00-16 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

00-17 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

HS-DSCH Frame Protocol: HS-DSCH CAPACITY ALLOCATION

00-18 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

Number of attempts to setup a RAB of specific maximum bit rate

Counter Counter Name Bitrate Class (kbps)

Counter Counter Name Bitrate Class (kbps)

00-19 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

Number of attempts and successes to setup a RAB with HSPA

M1022C3 PS_ATT_HSDSCH_EDCH_INT HSDPA + HSUPA attempted

M1022C5 PS_ATT_HSDSCH_DCH_INT HSDPA + DCH attempted

00-20 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

Number of HSDPA setup failures per cause

M1002C401 REJ_HS_DSCH_RET_INT lack of radio resources for A-DCH

00-21 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

Number of HSUPA setup failures per cause

M1002C523 SETUP_FAIL_EDCH_UE_INT radio bearer reconfiguration failure within UE

Less cause counters defined than for HSDPA setup

00-22 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

100* sum([HS_E_REQ_HS_E_ALLO_STRE] + [HS_E_REQ_HS_E_ALLO_INT] +

00-23 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

00-24 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved

00-25 TA-TC 6271 NAK www.techcom.de Copyright © All rights reserved