Académique Documents
Professionnel Documents
Culture Documents
CS Succ RRC
ConnectReq pmTotNoRrc
Ps ConnectReq pmTotNoRrc
nn aringRrcCo pmNoLoadSh - Ps ConnectReq pmTotNoRrc
PsSucc ConnectReq pmTotNoRrc
_ _
PS Succ RRC
The basic idea is to calculate the load sharing reject for PS and CS by a
wheight factor given by the fraction of the RRC_CS (or PS) respect to the total
number of RRCs. In case of RRC Succ general the formula is muche more
simple instead....
nn aringRrcCo pmNoLoadSh - ConnectReq pmTotNoRrc
Succ ConnectReq pmTotNoRrc
_ _ general Succ RRC
112
RRC Connection Establishment Success Rate CS and PS in case of Load Sharing
0
1000
2000
3000
4000
5000
6000
7000
8000
9000
10000
Days
0%
20%
40%
60%
80%
100%
120%
LoadSharingReject
RRC_SUC_CS_LS
RRC_SUC_PS_LS
Load Sharing Impact on Accessibility (CSSR) KPI - Results
The RRC Succ estimation CS and PS are
disturbed by the Load Sharing rejects.
We registered strong fluctuations of
values expecially in case of high IFLS
activity....
113
RRC Connection Establishment Success Rate General in case of Load Sharing
0
1000
2000
3000
4000
5000
6000
7000
8000
9000
10000
Days
0.0%
20.0%
40.0%
60.0%
80.0%
100.0%
120.0%
LoadSharingEvents
RRC_SUC_LS
Load Sharing Impact on Accessibility (CSSR) KPI - Results
In case of RRC Succ Rate calculated for all
kinds of RRC, the estimation is much more
stable instead and not affected by IFLS!
114
RRC Connection Estab. Succ. Rate comparison (General, CS, PS) including Load Sharing
80.0%
85.0%
90.0%
95.0%
100.0%
105.0%
110.0%
Days
RRC_SUC_LS
RRC_SUC_CS_LS
RRC_SUC_PS_LS
Load Sharing Impact on Accessibility (CSSR) KPI - Results
Here it is quite evident the noise introduced by
the load sharing in CS and PS RRC Succ
estimations.
>100% values
Strong KPI
deterioration
Please consider that the values are calculated on daily base. So they
should be quite stable
115
Conclusions (1/2)
When Load sharing is introduce the accessibility formulae should be updated to
take into consideration the RRC Connection Attempts rejected to be redirected
towards the other frequency ().
While no problem should exist for the tot accessibility formula:
2 new formulae are proposed for the CS and PS specific KPIs:
However the estimation given by this KPI is not extremely stable/reliable and
accurate (the average error seems to be acceptable compared to the error that
affects the other formulae but the fluctuation are high).
ConnectReq pmTotNoRrc
Cs ConnectReq pmTotNoRrc
nn aringRrcCo pmNoLoadSh - Cs ConnectReq pmTotNoRrc
CsSucc ConnectReq pmTotNoRrc
_ _
CS Succ RRC
ConnectReq pmTotNoRrc
Ps ConnectReq pmTotNoRrc
nn aringRrcCo pmNoLoadSh - Ps ConnectReq pmTotNoRrc
PsSucc ConnectReq pmTotNoRrc
_ _
PS Succ RRC
nn aringRrcCo pmNoLoadSh - ConnectReq pmTotNoRrc
Succ ConnectReq pmTotNoRrc
_ _ general Succ RRC
116
Conclusions
An alternative suggestion could be to use the following formula for CSSR
CSSR_CS = RRC_Succ_Global x RAB_CS_Succ
CSSR_PS = RRC_Succ_Global x RAB_PS_Succ
The estimation given by this KPI is much more stable/reliable and the average
error seems to be acceptable compared to the error that affects the other
formulae.
The main drawback of this solution is that the Global RRC Succ is often a little bit
worse compared with the real CS and PS values.
(This is probably related to different radio environment: i.e. the major part
of RRC Connections are established for registration purpose, when the
UE is entering back to 3G coverage; those radio procedures often occur
at cell coverage borders and so are affected by a worse performance.)
117
Agenda
3. Channel Structure
2. Architecture
1. Overview
5. InterFrequency Mobility Principles
6. KPIs
4. Accessibility & Mobility Principles
6. Capacity Management
RBS KPI
118
RBS Counters KPIs
This appendix reports the main KPIs that could be used for HS testing
divided by:
Throughput
Scheduling Ratio and Transmission efficiency
CQI/ACK/NACK
Power
RBS RSSI
Note that performing tests with a single HS user in a unloaded network is
useful to:
Have specific user information for a user
Verify counters/KPI meanings and compare them with UE based KPI
119
Throughput Counters
Counters:
pmSumAckedBits: the number of Media Access Control high-speed (MAC-hs) bits received and
acknowledged by the UE.
pmSumTransmittedBits: the number of transmitted bits at MAC-hs, level including retransmissions
pmSumNonEmptyUserBuffers: The number of user buffers containing high-speed data.
pmNoActiveSubFrames: the number of subframes containing high-speed data transmitted by the
RBS.
pmNoInactiveRequiredSubFrames: the number of empty subframes transmitted even though data is
scheduled for priority queue.
Still not used:
pmAverageUserRate (PDF): The distribution of the average user rate among all users allocated to
high-speed-DSCH in the cell.
120
Throughput KPIs
DSCH UE Thr. NET = Av. Throughput (PS-HS) without retransmission:
Sum(pmSumAckedBits)/(Sum(pmSumNonEmptyUserBuffers)*0.002s)
DSCH UE Thr. GROSS = Av. Throughput (PS-HS) with retransmission:
Sum(pmSumTransmittedBits)/(Sum(pmSumNonEmptyUserBuffers)*0.002)
DSCH Cell Thr. NET = The MAC-hs throughput on cell level
pmSumAckedBits / (0.002s * pmNoActiveSubFrame)
DSCH Cell Thr. GROSS = The MAC-hs data rate on cell level
pmSumTransmittedBits / (0.002 s* pmNoActiveSubFrame)
Cell Thr. NET = The MAC-hs throughput on cell level
pmSumAckedBits / (ROP period)
Cell Thr. GROSS = The MAC-hs data rate on cell level
pmSumTransmittedBits / (ROP period)
121
Throughput KPIs Values Live Network
RBS Name
RBS
Sector
RBS
Sector
Carrier
Average
Number
Of UE In
a Queue
DSCH UE
Throughput
NET
DSCH UE
Throughput
GROSS
DSCH Cell
Throughput
NET
DSCH Cell
Throughput
GROSS
RBS32601-01 3 1 1 92.32 148.32 194.89 313.11
RBS05314-01 2 2 1 164.11 221.32 265.44 357.98
RBS37058-01 1 2 1 183.97 202.45 292.65 322.04
RBS00003-01 3 2 1 218.77 259.69 218.77 259.69
RBS34645-01 2 1 1 242.96 350.73 242.96 350.73
RBS01281-01 3 1 1 248.4 405.3 248.4 405.3
RBS37058-01 2 2 1 324.44 405.58 324.79 406.02
RBS01780-01 1 1 1 352.6 566.15 491.79 789.63
RBS00357-01 2 1 1 389 518.5 389 518.5
RBS00429-01 1 2 1 399.94 542.16 399.94 542.16
RBS37242-01 3 1 1 424.5 500.75 424.5 500.75
RBS34375-01 2 1 1.01 449.73 749.43 461.94 769.76
RBS01263-01 1 1 1 456.78 565.98 456.78 565.98
RBS23074-01 3 2 1 509.66 552.27 509.66 552.27
RBS23066-01 2 1 1 518.67 518.67 518.67 518.67
RBS04995-01 1 2 1 556.41 648.95 557.03 649.67
RBS00370-01 1 1 1 632.88 838.31 632.88 838.31
RBS01546-01 2 1 1 652.58 878.57 751.29 1,011.47
RBS01281-01 1 1 1 662.62 1,142.64 662.62 1,142.64
RBS34375-01 3 1 1 710.73 1,071.00 710.73 1,071.00
RBS23025-01 3 1 1.01 734.94 901.09 828.62 1,015.96
RBS37058-01 3 2 1 764.56 995.06 817.15 1,063.51
RBS00353-01 1 1 1 770.18 1,170.15 775.24 1,177.84
RBS34645-01 1 1 1 828.63 1,319.63 933.18 1,486.14
RBS23025-01 2 1 1 881.87 1,205.44 913.16 1,248.20
RBS05314-01 1 2 1 1,183.36 1,390.58 1,193.88 1,402.94
RBS00429-01 2 2 1 1,200.85 1,605.63 1,200.85 1,605.63
RBS01164-01 3 2 1 1,285.29 1,503.11 1,285.65 1,503.53
RBS01164-01 2 2 1 1,318.85 1,537.49 1,354.04 1,578.52
122
Transmission efficiency KPIs
MAC Tx efficiency (or Efficiency factor ) =
Sum(pmNoActiveSubFrame )/ (Sum(pmNoActiveSubFrame)+Sum(pmNoInactiveRequiredSubFrame))
Scheduling Ratio = This KPI simply highlights the percentage of time the HS-DSCH is used
Sum(pmNoActiveSubFrame)*0.002/ (ROP period)
Transmission ratio = This highlight the percentage of time there is something to transmit. This is a good index
on how efficiently the application level can exploit DSCH capabilities
(Sum(pmNoActiveSubFrame)+Sum(pmNoInactiveRequiredSubFrame))*0.002 /
(ROP period)
Av.# UEs in queue
Sum(pmSumNonEmptyUserBuffers) / ( Sum(pmNoActiveSubFrame)+ Sum(pmNoInactiveRequiredSubFrames) )
123
( + )
Transmission Efficiency (1/2)
The first index to look at when talking about transmission efficiency is the ratio
between the used TTI (the one where something is transmitted) and the total
#TTI in the test period
Mac Tx Efficiency = 99.05%
Scheduling Ratio = 81.3%
Nothing transmitted
PDU is transmitted
Buffer not empty but PDU not transmitted
Transmission Ratio = 82.8%
( + )
( + )
( + + )
124
Transmission Efficient KPIs Values Live Network
RBS Name Sector Carrier
%
Scheduling
Ratio
%
Tranmission
Ratio
RBS32601-01 3 1 0.00% 0.00%
RBS05314-01 2 2 1.54% 2.49%
RBS37058-01 1 2 0.01% 0.02%
RBS00003-01 3 2 0.00% 0.00%
RBS34645-01 2 1 0.00% 0.00%
RBS01281-01 3 1 0.00% 0.00%
RBS37058-01 2 2 0.11% 0.11%
RBS01780-01 1 1 0.00% 0.00%
RBS00357-01 2 1 0.00% 0.00%
RBS00429-01 1 2 0.03% 0.03%
RBS37242-01 3 1 0.00% 0.00%
RBS34375-01 2 1 0.00% 0.00%
RBS01263-01 1 1 0.00% 0.00%
RBS23074-01 3 2 0.00% 0.00%
RBS23066-01 2 1 0.00% 0.00%
RBS04995-01 1 2 0.12% 0.12%
RBS00370-01 1 1 0.02% 0.02%
RBS01546-01 2 1 0.06% 0.07%
RBS01281-01 1 1 0.00% 0.00%
RBS34375-01 3 1 0.15% 0.15%
RBS23025-01 3 1 0.11% 0.12%
RBS37058-01 3 2 0.01% 0.01%
RBS00353-01 1 1 0.03% 0.03%
RBS34645-01 1 1 0.34% 0.38%
RBS23025-01 2 1 0.09% 0.09%
RBS05314-01 1 2 0.06% 0.06%
RBS00429-01 2 2 0.07% 0.07%
RBS01164-01 3 2 0.03% 0.03%
RBS01164-01 2 2 0.14% 0.15%
125
CQI/ACK/NACK counters
pmReportedCqi: the Channel Quality Indicators (CQI) reported by the UE in
the cell and received by the RBS.
pmUsedCqi: the CQI, used by the RBS for scheduling the priority queue for
the HS-DSCH.
Within the reportedCQI tables, there is a column called InvalidCQI. This
counter will be used as well
pmAckReceived: The number of Acknowledgements (ACK) that the RBS
receives from the User Equipment (UE) over the High-Speed Downlink
Shared Channel (HS-DSCH).
pmNackReceived: The number of Negative-Acknowledgements (NACK) that
the RBS receives from the User Equipment (UE) over the High-Speed
Downlink Shared Channel (HS-DSCH).
126
CQI/ACK/NACK KPIs
HS-BLER: pmNackReceived /(pmNackReceived + pmAckReceived)
RtxOverhead = Percentage of the Retransmitted bits over the total
100*(pmSumTransmittedBits - pmSumAckedBits) /(pmSumTransmittedBits)
CQI specific
Av. Reported
Av. USed CQI
Delta CQI = Difference between the 2 averaged values above. This is an index of how much CQI adjustment acts.
CQIequalTo0 = Count(CQIreported=0)/Count(CQIreported). This is the main reason of MAC inefficiency
InvalidCQI = invalideCQI/Count(CQIreported). Not clear what invlid means
Proposal: (ACK+NACK)/ActiveTTI: still not clear WHAT WE CAN SEE FROM IT
(pmNackReceived+pmAckReceived)/ActiveFrame
127
HS scheduling
The CQI=0 percentage drop to 0.01%, almost nothing.
The BLER and the Retransmission rate are almost identical, that means the CQI adjustment
has been able to reach the target
Baseline Test 2
Reported BLER [%]
12,6 12,5
RtxOverhead [%]
14,8 15,0
Av Reported CQI
10,1 17,0
Av Used CQI
9,8 16,5
Delta CQI
0,32 0,48
(ACK+NACK)/Active [%]
98,68 97,29
CQI = 0 [%]
0,79 0,01
The BLER is the ratio between NACK
and (ACK + NACK)
The Rtx overhead is the ratio between
the transmitted and the acked bits
Delta CQI could be seen as index of the
CQI adjustment impact
When 0 is received no transmission will
be allowed to the mobile for the following
TTI
128
Integrity KPIs Values Live Network
RBS
Name
RBS
Sector
RBS
Sector
Carrier
% HS-
BLER
% Rtx
Overhead
MAC
Transmission
Efficiency
RBS23066-01 2 1 0.00% 0.00% 100.00%
RBS37058-01 1 2 4.14% 9.13% 62.87%
RBS37242-01 3 1 8.85% 15.23% 100.00%
RBS23074-01 3 2 9.43% 7.72% 100.00%
RBS05314-01 2 2 10.01% 25.85% 61.83%
RBS04995-01 1 2 11.74% 14.26% 99.89%
RBS01164-01 2 2 12.03% 14.22% 97.41%
RBS05314-01 1 2 12.99% 14.90% 99.12%
RBS01164-01 3 2 13.28% 14.49% 99.97%
RBS01263-01 1 1 13.64% 19.29% 100.00%
RBS23025-01 3 1 14.18% 18.44% 89.32%
RBS37058-01 2 2 14.34% 20.01% 99.89%
RBS00003-01 3 2 15.38% 15.76% 100.00%
RBS37058-01 3 2 18.06% 23.16% 93.56%
RBS34375-01 2 1 18.24% 39.99% 98.14%
RBS01546-01 2 1 18.33% 25.72% 87.02%
RBS00370-01 1 1 18.44% 24.51% 100.00%
RBS00429-01 1 2 19.62% 26.23% 100.00%
RBS32601-01 3 1 21.05% 37.76% 47.37%
RBS23025-01 2 1 22.70% 26.84% 96.60%
RBS34375-01 3 1 23.36% 33.64% 100.00%
RBS01780-01 1 1 23.64% 37.72% 71.70%
RBS00429-01 2 2 24.27% 25.21% 100.00%
RBS00357-01 2 1 25.00% 24.98% 100.00%
RBS34645-01 1 1 27.50% 37.21% 88.80%
RBS00353-01 1 1 28.36% 34.18% 99.35%
RBS34645-01 2 1 30.77% 30.73% 100.00%
RBS01281-01 3 1 33.68% 38.71% 100.00%
RBS01281-01 1 1 38.09% 42.01% 100.00%
129
RBS power
pmTransmittedCarrierPowerNonHs: The transmitted carrier power for all
non high-speed codes in the cell.
pmTransmittedCarrierPower: the transmitted carrier power measured at
the TX reference point every 4 seconds.
Notes:
Every 100 ms the transmitted carrier power for all non high-speed codes in the
cell are sampled. The problem is that there are not necessary data enough to
transmit in every slot: hence some kind of normalization should be investigated.
130
0
0.1
0.2
0.3
0.4
0.5
0.6
1
.
0
1
.
3
1
.
6
2
.
0
2
.
5
3
.
2
4
.
0
5
.
0
6
.
3
7
.
9
1
0
.
0
1
2
.
6
1
5
.
8
2
0
.
0
TxCarrierPower
R99Power
Tx Power examples
(almost 100% of Scheduling Ratio)
CCH power = 1.7 The Max power = 8.7
The power is calculated at the antenna reference point
131
Transmitted Power (2/2)
The Average Tx power is:
Total Carrier = 4.85 W
R99 power = 1.63 W
TotalHS_power = 3.22 W
Note that the HS power is an estimation of the power transmitted for the HS on average
during the test period but it is NOT an estimate of the power that HS required in the cell!
The activity of the HS (when we transmit something) is still low (80%).
Maybe a more interesting KPI could be:
TotalHS_power/SchedulingRatio*100
= 100*3.22/81.3 = 3.96 W
It is interesting to notice anyway that even with a single user the MaxTxPower is
reached.
132
RBS list of counters
pmTransmittedCarrierPowerNonHs: The transmitted carrier power for all non high-speed codes in the cell.
pmTransmittedCarrierPower: the transmitted carrier power measured at the TX reference point every 4 seconds
pmNoActiveSubFrames: the number of subframes containing high-speed data transmitted by the RBS.
pmNoInactiveRequiredSubFrames: the number of empty subframes transmitted even though data is scheduled for priority queue.
pmSumNonEmptyUserBuffers: The number of user buffers containing high-speed data.
pmSumAckedBits:the number of Media Access Control high-speed (MAC-hs) bits received and acknowledged by the UE.
pmSumTransmittedBits: Description The number of transmitted bits at MAC-hs, level including retransmissions
pmReportedCqi: the Channel Quality Indicators (CQI) reported by the UE in the cell and received by the RBS.
pmUsedCqi: the CQI, used by the RBS for scheduling the priority queue for the HS-DSCH. pmAckReceived: The number of
Acknowledgements (ACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HS-
DSCH).
pmNackReceived: The number of Negative-Acknowledgements (NACK) that the RBS receives from the User Equipment (UE) over the
High-Speed Downlink Shared Channel (HS-DSCH). pmAverageRssi: The average Received Signal Strength Indication (RSSI).
133
Agenda
3. Channel Structure
2. Architecture
1. Overview
5. InterFrequency Mobility Principles
6. KPIs
4. Accessibility & Mobility Principles
6. Capacity Management
RNC KPI
134
The length of time in seconds that a cell is available for Packet Interactive HS service is defined as cell HS availability. in the example, the cell HS
availability during 24 hour period is reported.
1) HS cell Availability (24 Hours period)
Cell Availability (
1
)
100 *
3600 * 24
meMan) pmHsDownti meAuto pmHsDownti ( 3600 * 24
ch) Av_HS(Hsds
100 *
Attempt ngHsHardHo pmNoIncomi
dChTarget) HoReturnOl pmNoHsHard oSuccess ingHsHardH (pmNoIncom - Attempt ngHsHardHo pmNoIncomi
dIn_Lost PS_M_HSHar
139
pmInactivityHsIdle
Retainability
The new and existing cell counters used for Retainability are given in the
following list:
Counter name
pmNoSystemRabReleasePacket
pmNoNormalRabReleasePacket
pmChSwitchFachIdle
pmNoTpSwitchSp64Speech
pmNoSystemRbReleaseHs
pmNoNormalRbReleaseHs
New/existing
Existing
Existing
Existing
Existing
New
New
New
The number of signalling connection releases
triggered for PS Interactive RAB mapped on HS-
DSCH due to inactivity (Channel Switching
Evaluation algorithms request the execution of a
switch to idle).
The counter is stepped at the reception of RANAP Iu Release
Command from CN, for HS channel cell or RANAP RAB
assignment Request (when the RAB is released) and the RANAP
cause is User Inactivity.
Number of system releases of packet RABs mapped
on HS-DSCH in the Serving HS-DSCH cell.
Number of successful normal releases of packet RABs
mapped on HS-DSCH in the Serving HS-DSCH cell.
140
Retainability
HS Radio Bearer retainability, drop rate =
100 *
pmNoSystemRbReleaseHs
pmNoSystemRbReleaseHs + pmNoNormalRbReleaseHs
Total PS Interactive retainability, drop rate =
100 *
( pmNoSystemRabReleasePacket )
pmNoSystemRabReleasePacket + pmNoNormalRabReleasePacket
141
System Utilization
It is possible to measure HS A-DCH utilisation in terms of code usage and average
number of users per cell.
Two new set of counters shall be implemented. The first set is used to observe the HS A-
DCH code utilisation per cell. The KPI indicates the the total number of A-DCH radio
bearers established in a cell.
( pmSumPsHsAdchRabEstablish /pmSamplePsHsAdchRabEstablish )
The second set is used to observe the average number of users per cell (hence the
number of HS users), which is done by looking only at the best cell:
(pmSumBestPsHsAdchRabEstablish /pmSampleBestPsHsAdchRabEstablish )
142
Throughput
143
Throughput
1) Average Throughput for PS interactive HS (RNC Level)
8 *
nHs4 ketDuratio pmTotalPac nHs3 ketDuratio pmTotalPac nHs2 ketDuratio pmTotalPac nHs1 ketDuratio pmTotalPac
etDataHs4 pmSentPack etDataHs3 pmSentPack etDataHs2 pmSentPack etDataHs1 pmSentPack
P PintHS_I_T
144
Retrans rate live RNC
Object Name
Retrans Rate
PS Int HS
RNCCN1 99.63%
RNCKS1 99.49%
RNCKS2 100.00%
RNCNY1 98.03%
145
Mobility
For mobility only the HS serving cell
change procedure is considered .
Counter name
pmNoHsCcSuccess
pmNoHsCcAttemptt
New/existing
New
New
The corresponding KPI is
1) Success rate for HS Cell
Change in target cell
Note that no AC is
requested in the cell
change procedure
100 *
mpt pmHsCcAtte
ess pmHsCcSucc
S PS_M_HSCC_
146
Admission & Congestion Control
Number of of radio links that are on SF=4 in UL
pmSumSf4Ul /pmSamplesSf4Ul
RNC counter monitoring no. of admission rejects (RAB setup) of HSDPA
users
pmNoOfNonHoReqDeniedHs
RNC counters monitoring no. of HSDPA users (connections) released due to
congestion
pmNoOfTermHsCong & pmNoOfIurTermHsCong