You are on page 1of 74

B8-B9 MR1Ed4 QOS Variations

Professional Customer Services 31/01/06

All rights reserved 2005, Alcatel

Agenda
Page 2

Impact of B9 on QOS main indicators


Preliminary Impact on CS QOS indicators
Good Results

J J

Impact on PS QOS indicators


Improvements even if several QOS variations on main indicators

Annexes (give some explanations related to QOS variations linked to new B9 algorithms)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Preliminary
Page 3

B9MR1Ed4 not yet migrated on field Until now, feedbacks come from first off pilots migrated with B9MR1Ed1 or Ed2. Some issues detected on these pilots and on lab acceptance are corrected in B9MR1Ed4 => We need your feedbalck to validate the corrections This presentation distinguishes the QOS variations
Linked to B9 evolution Linked to a problem corrected in B9 MR1Ed4 Linke to a problem not corrected in B9 MR1Ed4

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 4

Impact of B9 on QOS main indicators


Impact on CS QOS indicators
RLE phase Call Establishment Call Drop HO Miscalleneous

Impact on PS QOS indicators Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GSM


Page 5

Radio Link Establishment phase :


SDCCH assign Congestion

Some congestion appears in some network, solved by parameter tuning (FR A25/178551) => in Jersey: default values have been applied on BS_AG_BLK_RES and AG_PREMPT_PCH =>root cause identified and correction planned in B9MR1Ed5

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GSM


Page 6

Call Establishment (1/2) RTCH assign phase: stable but

On multiband/concentric cells, an increase of RTCH/HO radio congestion can be observed. It is linked to RFD Multiband cell secured TCH assignment (RFD145637)

=> The impact is an increase of CS traffic in outer zone


parameter tuning can solve the issue (MAX_PDCH has to be decreased if too high)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GSM


Page 7

Call Establishment (2/2)


Call Setup Success Rate : stable

Slight increase in VIP due the parameter setting which done is favour of CS. If B8 is not MR6, CSSR could be >100%. In B9, it is no more true because

of a correction done in B8MR6 on MC140a counter


CSSR > 100% CSSR < 100% B8 B9

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GSM


Page 8

Handover
decrease of HO success rate (under investigation) No impact on call drop rate (increase of ROC)

no end user impact


Problem identified on BTS when parameter clock synchro mode has the value ignore

issue identified in the SUMA SW, Corrected in MR1 Ed04


It is important to check carefully the value of this parameter because it seems to change spontaneously to ignore

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GSM


Page 9

Miscellaneous: Speech Codec counters variation


Some issues have been seen on both pilots:

Counter MC701a increased by a huge factor: there are 20 times more requests from "FR only MS" in B9 than in B8 => FR20/177215; MC701A (RTCH_assign_FR_request) : Number of TCH normal assignments requests from FR only mobiles Counter issue : See explanation in annex4 No impact on end user (only counter issue)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 10

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New Features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 11

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New Features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GPRS


Recommendations Variation of QOS indicators in GPRS linked to:
Important
Page 12

new B9 algorithms => some explanation could be requested by the customer (feel free to ask NPI/TD/PCS if you need support for this part) real issues under investigation : it is very important to correlate the variations with

end users performances in order to identify the severity of the issue

B9MR1Ed4 has not been deployed on field yet. This means that the correction done in this release are still to be validated on field: We NEED your feedbacks. The customer must NOT be informed of the variations described in this presentation (except if known by the customer via Restriction List or pilot QOS results)
B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006
All rights reserved 2005, Alcatel

Agenda
Page 13

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New Features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

GPRS - Sleeping GPRS


Page 14

On Ed2, less sleeping GPRS cells in B9 than in B8 but still occurrences


Corrected in B9 MR1Ed4

On Ed2, some occurrences of Sleeping GPU (no more GPRS on all cells supported by this GPU)
Corrected in B9 MR1Ed4 => No more end user impact in B9MR1Ed4 =>To be checked carefully (Two alerters exist in case of new occurrence)
B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006
All rights reserved 2005, Alcatel

Agenda
Page 15

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New Features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GPRS


Page 16

DL TBF Establishment

Decrease of establishment success rate (FR 45/172169 and 45/176776) The increased failures causes are radio and BSS failures. Complete Analysis done in QOS task force. A counter issue has been identified (Corrected in B9 MR1Ed4) and an explanation is available toward customers for remaining issues (it can be provided if needed) Not seen as critical by first-offs (end user impact should be low)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GPRS


Page 17

UL TBF Establishment J
On Ed2, increase of failure due to BSS

It should be corrected in B9 MR1Ed4


No impact on the end user (very low variation) If CS is favored by parameter setting, there can be an increase of UL TBF establishment failure due to radio congestion in case of high CS load (due to the new radio resources allocation) Impact on the end user depends on the rate of radio cong

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 18

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GPRS


Page 19

DL TBF release

Normal release : decrease due to


Acceptable release increase : due to radio preemption (P146 counter) => Increase day after day (unless GPU reset is done) Drop increase (due to radio drop and blocking situations) (FR A45/176775)

Complete analysis done in QOS task force An explanation is available toward customers (it can be provided if needed) Impact on end user is considered as minor (the drop can occur when the TBF is inactive and if not, the impact could be a slight decrease of the throughput)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

DL acceptable releases causes


Page 20
DL TBF Acceptable Release causes
50000 45000 40000 35000 30000 25000 20000 15000 10000 5000 0
24 .1 0. 20 05 26 .1 0. 20 05 28 .1 0. 20 05 30 .1 0. 20 05 01 .1 1. 20 05 03 .1 1. 20 05 05 .1 1. 20 05 07 .1 1. 20 05 09 .1 1. 20 05 11 .1 1. 20 05 13 .1 1. 20 05 15 .1 1. 20 05 17 .1 1. 20 05 19 .1 1. 20 05 21 .1 1. 20 05 23 .1 1. 20 05

3,5 3 2,5 2 1,5 1 0,5 0

Transm Preempt NC0 Resel NC2 Resel Suspend Radio Preempt %Acceptable Rel

B8

B9

DL TBF Acceptable Release causes


70000 60000 50000 40000 30000 20000 10000 0 1,6 1,4 1,2 1 0,8 0,6 0,4 0,2 0

Transm Preempt NC0 Resel NC2 Resel Suspend Radio Preempt %Acceptable Rel

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

10 /3 1/ 20 05 11 /0 2/ 20 05 11 /0 4/ 20 05 11 /0 6/ 20 05 11 /0 8/ 20 05 11 /1 0/ 20 05 11 /1 2/ 20 05 11 /1 4/ 20 05 11 /1 6/ 20 05 11 /1 8/ 20 05 11 /2 0/ 20 05 11 /2 2/ 20 05 11 /2 4/ 20 05 11 /2 6/ 20 05 11 /2 8/ 20 05 11 /3 0/ 20 05 12 /0 2/ 20 05 12 /0 4/ 20 05

B8

B9

All rights reserved 2005, Alcatel

Impact of B9 on Main QoS Indicators : GPRS


Page 21

UL TBF release

Normal release : stable but B9 release causes different from B8 ones


High decrease of releases due to suspend (counter issue under investigation)

Increase of releases due to preemption (P147) (same issue as in DL)

No impact on end user (the variation is negligeable)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

UL acceptable release causes


Page 22
UL TBF Acceptable Release causes
50000 45000 40000 35000 30000 25000 20000 15000 10000 5000 0 1,4 1,2 1 0,8 0,6 0,4 0,2 0

Transm Preempt NC0 Resel NC2 Resel Suspend Radio Preempt %Acceptable Rel

24 .1 0. 20 05 26 .1 0. 20 05 28 .1 0. 20 05 30 .1 0. 20 05 01 .1 1. 20 05 03 .1 1. 20 05 05 .1 1. 20 05 07 .1 1. 20 05 09 .1 1. 20 05 11 .1 1. 20 05 13 .1 1. 20 05 15 .1 1. 20 05 17 .1 1. 20 05 19 .1 1. 20 05 21 .1 1. 20 05 23 .1 1. 20 05

B8

B9

UL TBF Acceptable Release causes


25000 20000 15000 10000 5000 0 0,3 0,25 0,2 0,15 0,1 0,05 0

Transm Preempt NC0 Resel NC2 Resel Suspend Radio Preempt %Acceptable Rel

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

10 /3 1/ 20 05 11 /0 2/ 20 05 11 /0 4/ 20 05 11 /0 6/ 20 05 11 /0 8/ 20 05 11 /1 0/ 20 05 11 /1 2/ 20 05 11 /1 4/ 20 05 11 /1 6/ 20 05 11 /1 8/ 20 05 11 /2 0/ 20 05 11 /2 2/ 20 05 11 /2 4/ 20 05 11 /2 6/ 20 05 11 /2 8/ 20 05 11 /3 0/ 20 05 12 /0 2/ 20 05 12 /0 4/ 20 05

B8

B9

All rights reserved 2005, Alcatel

Agenda
Page 23

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

UL/DL Reallocation Variations

J
Page 24

DL, variations linked to new B9 alogorithms (common to both pilots)

Decrease of DL T4 requests High Increase of DL T2 success rate High decrease of DL T4 success rate, due to failures during the preparation phase

UL, variations linked to new B9 algorithms (common to both pilots)


Increase of UL T1 requests Decrease of UL T2 & T4 requests High increase of UL T2 success rate High decrease of UL T4 success rate, due to failures during the preparation phase

=>Normal behaviour linked to B9 algorithms enhancement => better Radio ressource management (see explanation in Annex1) On Ed2, Blocking reallocations issue (FR45/176874 ) some cells on which T1, T3 and T4 reallocations are blocked => Corrected in B9MR1Ed4 => no more end user impact In case of new occurrence an alerter is available
B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006
All rights reserved 2005, Alcatel

1200000 1000000

1400000

400000 200000

800000 600000

0
10/03/2005 10/05/2005 10/07/2005 10/09/2005 10/11/2005 10/13/2005 10/15/2005 10/17/2005 10/19/2005 10/21/2005 10/23/2005 10/25/2005 10/27/2005 10/29/2005 10/31/2005 11/02/2005 11/04/2005 11/06/2005 11/08/2005 11/10/2005 11/12/2005 11/14/2005 11/16/2005 11/18/2005 11/20/2005 11/22/2005 11/24/2005 11/26/2005 11/28/2005

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006


DL resource realloc T2 T2 DL Ressources Realloc

DL Ressources Realloc T1

20

40

60

80

100

120

BSS fail

Prep fail

Success

Radio fail

10/03/2005 10/05/2005 10/07/2005 10/09/2005 10/11/2005 10/13/2005 10/15/2005 10/17/2005 10/19/2005 10/21/2005 10/23/2005 10/25/2005 10/27/2005 10/29/2005 10/31/2005 11/02/2005 11/04/2005 11/06/2005 11/08/2005 11/10/2005 11/12/2005 11/14/2005 11/16/2005 11/18/2005 11/20/2005 11/22/2005 11/24/2005 11/26/2005 11/28/2005

% Success
50000 45000 40000 35000 30000 25000 20000 15000 10000 5000 0

External stop

DL Ressources Realloc T3

DL resource realloc T4 DL Ressources Realloc T4

DL Reallocation Variations : some RNO Reports

B8 B9

100 90 80 70 60 50 40 30 20 10 0

BSS fail

Prep fail

Success

Radio fail

Page 25

%Success

External stop

All rights reserved 2005, Alcatel

100

200

300

400

500

600

700

1000000

1200000

200000

400000

600000

800000

0
10/03/2005 10/05/2005 10/07/2005 10/09/2005 10/11/2005 10/13/2005 10/15/2005 10/17/2005 10/19/2005 10/21/2005 10/23/2005 10/25/2005 10/27/2005 10/29/2005 10/31/2005 11/02/2005 11/04/2005 11/06/2005 11/08/2005 11/10/2005 11/12/2005 11/14/2005 11/16/2005 11/18/2005 11/20/2005 11/22/2005 11/24/2005 11/26/2005 11/28/2005

UL resource realloc T1

UL resource realloc T2

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006


10 /0 10 3 /20 /0 0 10 5 /20 5 /0 0 10 7 /20 5 /09 05 10 /20 /11 05 10 /20 /1 0 10 3 /20 5 /1 0 10 5 /20 5 /17 05 10 /20 /1 0 10 9 /20 5 /2 0 10 1 /20 5 /23 05 10 /20 /25 05 10 /20 /2 0 10 7 /20 5 /2 0 10 9 /20 5 /31 05 11 /20 /02 05 11 /20 /0 0 11 4 /20 5 /0 0 11 6 /20 5 /08 05 11 /20 /10 05 11 /20 /1 0 11 2 /20 5 /1 0 11 4 /20 5 /16 05 11 /20 /18 05 11 /20 /2 0 11 0 /20 5 /2 0 11 2 /20 5 /24 05 11 /20 /26 05 11 /20 /28 05 /20 05

180 160 140 120 100 80 60 40 20 0

UL Ressources Realloc T2

UL Ressources Realloc T1

20

40

60

80

100

120

BSS fail

Prep fail

Success

Radio fail

% Success

BSS fail

Prep fail

External stop

Success BSS fail Prep fail Success Radio fail External stop

Radio fail

10/03/2005 10/05/2005 10/07/2005 10/09/2005 10/11/2005 10/13/2005 10/15/2005 10/17/2005 10/19/2005 10/21/2005 10/23/2005 10/25/2005 10/27/2005 10/29/2005 10/31/2005 11/02/2005 11/04/2005 11/06/2005 11/08/2005 11/10/2005 11/12/2005 11/14/2005 11/16/2005 11/18/2005 11/20/2005 11/22/2005 11/24/2005 11/26/2005 11/28/2005

UL Reallocation Variations : some RNO Reports

% Success
50000 45000 40000 35000 30000 25000 20000 15000 10000 5000 0 100 90 80 70 60 50 40 30 20 10 0

External stop

80000 70000 60000 50000 40000 30000 20000 10000 0


10/03/2005 10/05/2005 10/07/2005 10/09/2005 10/11/2005 10/13/2005 10/15/2005 10/17/2005 10/19/2005 10/21/2005 10/23/2005 10/25/2005 10/27/2005 10/29/2005 10/31/2005 11/02/2005 11/04/2005 11/06/2005 11/08/2005 11/10/2005 11/12/2005 11/14/2005 11/16/2005 11/18/2005 11/20/2005 11/22/2005 11/24/2005 11/26/2005 11/28/2005

UL resource realloc T3 T3 UL Ressources Realloc

UL Ressources Realloc T4

UL resource realloc T4

100 90 80 70 60 50 40 30 20 10 0

%Success

BSS fail

Prep fail

Success

Radio fail

Page 26

% Success

External stop

All rights reserved 2005, Alcatel

Agenda
Page 27

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

UL/DL Coding scheme usage - Edge


Page 28

DL EGPRS useful RLC traffic


MCS9 usef
50000000 45000000 40000000 35000000 30000000 25000000 20000000 15000000 10000000 5000000 0
10 /3 1 11 /200 /0 2 5 11 /200 /0 4 5 11 /200 /0 6 5 11 /200 /0 8 5 11 /200 /1 0 5 11 /200 /1 2 5 11 /200 /1 4 5 11 /200 /1 6 5 11 /200 /1 8 5 11 /200 /2 0 5 11 /200 /2 2 5 11 /200 /2 4 5 11 /200 /2 6 5 11 /200 /2 8 5 11 /200 /3 0 5 12 /200 /0 2 5 12 /200 /0 4 5 12 /200 /0 6 5 12 /200 /0 8 5 12 /200 /1 0 5 12 /200 /1 2 5 12 /200 /1 4 5 12 /200 /1 6/ 5 20 05

90 80 70 60 50 40 30 20 10 0

MCS8 usef MCS7 usef MCS6 usef MCS5 usef MCS4 usef MCS3 usef MCS2 usef MCS1 usef %ioMCSxusef %io8PSKusef

8PSK activated by default B8


18000000 16000000 14000000 12000000 10000000 8000000 6000000 4000000 2000000 0
10 /3 1 11 /200 /0 2 5 11 /200 /0 4 5 11 /200 /0 6 5 11 /200 /0 8 5 11 /200 /1 0 5 11 /200 /1 2 5 11 /200 /1 4 5 11 /200 /1 6 5 11 /200 /1 8 5 11 /200 /2 0 5 11 /200 /2 2 5 11 /200 /2 4 5 11 /200 /2 6 5 11 /200 /2 8 5 11 /200 /3 0 5 12 /200 /0 2 5 12 /200 /0 4 5 12 /200 /0 6 5 12 /200 /0 8 5 12 /200 /1 0 5 12 /200 /1 2 5 12 /200 /1 4 5 12 /200 /1 6/ 5 20 05

B9

UL EGPRS useful RLC traffic


MCS9 usef
40 35 30 25 20 15 10 5 0

MCS8 usef MCS7 usef MCS6 usef MCS5 usef MCS4 usef MCS3 usef MCS2 usef MCS1 usef %io MCSx usef %io MCS4 usef

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

UL/DL Coding scheme usage CS1


Page 29

Increase of CS1 usage in DL


B8
80000000 70000000 60000000 50000000 40000000 30000000 20000000 10000000 0
10 /3 1 11 /200 /0 5 2 11 /200 /0 5 4 11 /20 05 /0 6 11 /200 /0 5 8 11 /200 /1 5 0 11 /200 /1 5 2 11 /20 05 /1 4 11 /200 /1 5 6 11 /200 /1 5 8 11 /20 0 /2 5 0 11 /200 /2 5 2 11 /200 /2 5 4 11 /200 /2 5 6 11 /20 05 /2 8 11 /200 /3 5 0 12 /200 /0 5 2 12 /20 05 /0 4 12 /200 /0 5 6 12 /200 /0 5 8 12 /200 /1 5 0 12 /20 05 /1 2 12 /200 /1 5 4 12 /200 /1 6/ 5 20 05

B9

GPRS DL useful RLC traffic


100 90 80 70 60 50 40 30 20 10 0

CS4 usef CS3 usef CS2 usef CS1 usef %io CSx usef

See explanation in Annex2

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Retransmission
Page 30

Increase of retransmission rate in UL EGPRS


=>explained by the usage of 8PSK in UL : =>In B9, higher MCS are introduced in UL. As these MCS are more sensitive to radio conditions, their usage implies higher retransmission rate.

In DL, Different variations on both pilots


The increase of retransmission on one pilot could be linked to the fact that, in B8, there were High Ater Usage. no more in B9 with Dynamic Abis, so higher coding schemes used. As a consequence, an increase of retransmission can be oberved

Not an issue, normal behaviour

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 31

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

PDCH Usage
Page 32

Decrease of average PDCH number allocated to MFS Optimal allocation Preemption

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

PDCH Usage
Page 33

Decrease of average PDCH number allocated to MFS Optimal allocation Preemption

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Allocated SPDCH
Page 34

In B8:
the BSC computes the limit of TS that could be allocated to the MFS (MAX_SPDCH_DYN) These TS are not necessarily allocated to the MFS

In B9:
The BSC computes the TS needed by itself for CS, by the MFS for PS, and allocates actually these TS to the MFS (MAX_SPDCH_LIMIT)

Conclusion in a real network


Most cells have low PS traffic (on average), which leads to lower MAX_SPDCH_LIMIT in B9 than MAX_PDCH_DYN in B8 (see case 0 and 1) In case PS traffic increases, the MAX_SPDCH_LIMIT would be equal or even higher to MAX_SPDCH_DYN (see case 2, 4 and 6) => More explanations are available in Annex3

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

PDCH Usage
Page 35

Decrease of average PDCH number allocated to MFS Optimal allocation Preemption

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

PDCH Usage : optimal allocation


Page 36

Different behaviour on both pilots


Increase of the optimal allocation time rate in Orange. => impact on the throughput per TBF which increases

J K

Decrease of the optimal allocation time rate in VIP. Probably due to the RAE-4 new mecanism more in favour of CS traffic on this network => impact on the throughput per TBF which decreases

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

PDCH Usage
Page 37

Decrease of average PDCH number allocated to MFS Optimal allocation Preemption

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Preemption : Increased usage of soft preemption:


P417 counter (1/2)
Page 38

In B8, the value of MaxSpdchDyn is reassessed for each TC allocation in the cell, but does not necessarily triggers a preemption:
a preemption will only be triggered if the CS zone of the cell enters in conflict with the RTSs currently used by the established TBFs.

In B9, the value of MaxSpdchLimit is also reassessed for each TCH allocation in the cell. If it is decreased, this will always trigger a preemption (at the next RR-Allocation-Indication message sending towards the MFS).
At any time, the targeted number of allocated PDCHs in the cell is equal to MaxSpdchLimit, so if MaxSpdchLimit is decreased, that will imply some PDCH preemptions (=> P417 is incremented, even if no TBF is present on the PDCH).

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Preemption : Increased usage of soft preemption:


P417 counter (2/2)
Page 39

Result
In case of successive CS call establishments / CS call releases, even if the average number of CS calls in the cell is constant, P417 will be much higher in B9 than in B8 (this is what was seen in Orange). In case of PS+CS congestion in the cell (i.e. in case the PS zone is in conflict with the CS zone), then the B8 and B9 counters should have nearer values. => no end user impact

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 40

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances/New features Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

B8-B9 Variations in end to end performances


Page 41

Summary
End2End Performances
Ping GPRS => In line with commitments (*) FTP GPRS => In line with commitments Ping Edge => In line with commitments (*) FTP Edge => In line with commitments (very good results in UL) => Issue with ping 32 bytes 5/15sec => under investigation

New Features
Extended UL TBF Mode 48% Gain on ping 0sec 56 bytes 61% Gain on ping 0sec 1460 bytes 33% Gain on HTTP reference page NACC/PSI Status =>Duration of TCP interruption per reselection , in FTP tranfer can be divided by 2 or more

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 42

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators
Recommendation Sleeping GPRS DL/UL TBF establishment DL/UL TBF release Reallocation variations Coding scheme usage/Retransmission PDCH Usage End to End Performances Miscellaneous

Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Miscalleneous
Page 43

Counter issues are described in Counter Status document


to be checked carefully because some main indicators are impacted by these issues Examples: P10 : number of DL LLC bytes discarded due to congestion has been multiplied by 7 or 8 => under investigation Wrong value of GPRS_xL_TBF_pilled_avg_indicator used to check the new RRM algorithm (it represents the average number of TBF per PDCH) = P451b/P38e always <1 while it should be > 1 => under investigation

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 44

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators Annexes

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 45

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators Annexes
Annex1 : Reallocation Variations Annex2 : increase of CS1 usage Annex3 : Allocated SPDCH Annex4 : Speech Codec Variation

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Realloc Variation: Alcatel answers


Page 46

Increase of T1 requests Decrease of T4 requests Decrease of T4 success rate Increase of DL T2 requests, decrease of UL T2 requests, increase of T2 success rate Decrease of T3 success rate (only one pilot)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Realloc Variation: Alcatel answers


Page 47

Increase of T1 requests Decrease of T4 requests Decrease of T4 success rate Increase of DL T2 requests, decrease of UL T2 requests, increase of T2 success rate Decrease of T3 success rate

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Realloc Variation: Increase of T1 requests


Page 48

Due to M-EGCH Statistical-Multiplexing in B9, addition of a new rule to trigger T1 reallocations (T1 reallocation triggered if the Max-MCS of a TBF can no longer be supported). The period of the BSC preemptions (triggered in B8 through LoadIndication message, triggered in B9 through message RR-AllocationIndication) passed from 15 seconds in B8 to 10 seconds in B9.
Reason: With the introduction of RAE-4, all the MaxSpdchLimit RTSs are allocated to the MFS (whereas in B8 only the RTSs supporting some TBFs were allocated to the MFS). So keeping a period of 15s for the PDCH preemptions in B9 could have increased CS blocking rate in the cells. Therefore, the periodicity of RR-Allocation-Indication sending was decreased from 15s to 10s (compared to the periodicity of Load-Ind sending in B8 which was the equivalent message) in order not to degrade the reactivity of RTS sharing between CS and PS traffic.

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Realloc Variation: Alcatel answers


Page 49

Increase of T1 requests Decrease of T4 requests Decrease of T4 success rate Increase of DL T2 requests, decrease of UL T2 requests, increase of T2 success rate Decrease of T3 success rate

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Realloc variations : Decrease of UL and DL T4 requests


Page 50

In B8, with the immediate UL feature, an incoming GPRS TBF is established on the already-established PDCHs of a TRX, even if those PDCHs support DL EGPRS TBFs the incoming GPRS TBF becomes candidate for T4 reallocation. In B9, thanks to M-EGCH Statistical Multiplexing, an incoming GPRS TBF is established on the other PDCHs of the TRX if it is possible the incoming GPRS TBF does not become candidate for T4 reallocation (except if all the PDCHs of the TRX support DL EGPRS TBFs).

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Realloc Variation: Alcatel answers


Page 51

Increase of T1 requests Decrease of T4 requests Decrease of T4 success rate Increase of DL T2 requests, decrease of UL T2 requests, increase of T2 success rate Decrease of T3 success rate

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Reallocations Variation : Decrease of UL and DL T4 success rate, due to failures during the preparation phase
Page 52

This is linked to the previous slide: A T4 request is only generated when the situation is already congested, i.e. when there are some DL EGPRS TBFs on all the PDCHs of the established TRXs a T4 reallocation is more likely to fail than in B8.

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Reallocations Variation: Alcatel answers


Page 53

Increase of T1 requests Decrease of T4 requests Decrease of T4 success rate Increase of DL T2 requests, decrease of UL T2 requests, increase of T2 success rate Decrease of T3 success rate

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Reallocations Variation : Increase of DL T2 requests, Decrease of UL T2 requests,

High increase of UL and DL T2 success rate


Page 54

Due to M-EGCH Statistical Multiplexing, P403b/P404b counter definition has changed between B8 and B9 (cf. MFS PM counter catalogue). The definition of a TBF candidate for T2 reallocation is different. So comparing B8 and B9 values is not relevant for T2 counters. Some reasons explaining the counter variations are (among others):
In B9, T2 reallocation can replace T3 reallocation during the whole TBF life (but in B8, only during the phase where the TBF is sub-optimal in number of RTSs). As a general rule, fewer constraints on Abis/Ater in B9 (due to dynamic Abis Allocation and M-EGCH Statistical-Multiplexing) more possibilities for T2 TBF reallocations to succeed. The number of T2 reallocations will be fully optimized in B9-MR3 through correction of AVP FT-R&D 9043 (3BKA20FBR172948 - Not optimized allocation for 3 MS 2+1 on 6 PDCH).

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Reallocations Variation: Alcatel answers


Page 55

Increase of T1 requests Decrease of T4 requests Decrease of T4 success rate Increase of DL T2 requests, decrease of UL T2 requests, increase of T2 success rate Decrease of T3 success rate

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex1: UL/DL Reallocations Variation : High decrease of UL and DL T3 success rate, due to failures during the preparation phase
Page 56

In B9, all the TBFs are always candidate for T3 reallocation, even if they have already an optimal allocation (i.e. even if they are alone on their RTSs). In B8, only the TBFs sub-optimal in number of RTSs are candidate for T3 reallocation Lower success rate in B9 than in B8, as the reallocation of the already-optimal TBFs is likely to fail (except if a radio defragmentation is possible).

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 57

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators Annexes
Annex1 : Reallocation Variations Annex2 : increase of CS1 usage Annex3 : Allocated SPDCH Annex4 : Speech Codec Variation

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex2: UL/DL Coding scheme usage : Increased CS1 usage rate in B9 (1/3)
Page 58

Explained by the fact that the DL TBF drops due to bad radio conditions are delayed in B9 through the following parameter modification
Default value of N3105_LIMIT changed from 16 to 20 Default value of EGPRS_N3105_LIMIT changed from 16 to 20 Default value of N_stagnating_Window_DL_LIMIT changed 10 from to 32 Creation of a new parameter : MIN_RLF_TIME_DL
Definition : Minimum time before detecting a radio link failure of a DL TBF, triggered by N3105 or NstagnatingWindowDL Default value : 4 seconds

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex2: UL/DL Coding scheme usage : Increased CS1 usage rate in B9 (2/3)
Page 59

These parameters have been modified due to :


Introduction of statistical multiplexing and dynamic Abis features
Mechanism in RLC for detection of radio link failure must take into account possible lack of transmission resource, thus reducing the radio throughput

Introduction of the GPRS QoS feature (PFC support)


Modification of the scheduling mechanism

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex2: UL/DL Coding scheme usage : Increased CS1 usage rate in B9 (3/3)
Page 60

When DL TBF drops are delayed in case of bad radio conditions


the mechanism linked to TBF_CS_DL is more often triggered and it can explain why the CS1 usage rate is increased in B9 release.
TBF_CS_DL : threshold defining the number of consecutive Packet Downlink Ack/Nack not received above which the coding scheme of a downlink acknowledged or unacknowledged TBF is changed to CS1

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 61

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators Annexes
Annex1 : Reallocation Variations Annex2 : increase of CS1 usage Annex3 : Allocated SPDCH Annex4 : Speech Codec Variation

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (1/10)


Autonomous Packet Resource Allocation (RAE4) algorithm
Page 62

Reminder in B8:
The BSC evaluates the number of timeslots that the MFS could use to carry PS traffic (Max_SPDCH_Dyn), The MFS does not know which timeslots are usable for PS traffic, To serve a new TBF, the MFS needs to request new timeslots to the BSC. Event-triggered mechanism
Max_SPDCH_Dyn = 8
TS allocated to BSC

TS allocated to MFS

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (2/10)


Autonomous Packet Resource Allocation (RAE4) algorithm
Page 63

In B9, new needs appear linked to AbisDynamic and StatMux, QoS management (with RealTime PFC), and faster TBF establishment New algorithm : Autonomous Packet Resource Allocation
The BSC evaluates a number of timeslots that the MFS can use to carry PS traffic (Max_SPDCH_Limit), Periodical exchange of messages between the BSC and the MFS:
BSC to MFS: list of RTS that the MFS can use, MFS to BSC: acknowledgement of allocated / de-allocated RTS.

The MFS knows which timeslots can be used to serve a new TBF. Max_SPDCH_Limit = 8 Periodical mechanism
TS allocated to BSC TS allocated to MFS

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (3/10)


Impact of RAE4 on allocated SPDCH counters
Page 64

Counter number

Name

Definition

P414

CUMULATED_MAX_PDCH_DYN_S ECONDS

This counter integrates over time the value of MAX_SPDCH_DYN during the whole granularity period.

Counter number P414bis

Name CUMULATED_TIME_ALLOCATED_ SPDCH

Definition This counter integrates over time the values of the allocated SPDCH during the whole granularity period.

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (3/5)


Impact of RAE4 on GPRS_MAX_PDCH_Dyn_avg (KPI)
Page 65

In B8 :
GPRS_MAX_PDCH_Dyn_avg = [ P414 / observation period ] Average value of MAX_SPDCH_Dyn (available SPDCH to MFS)

In B9 :
GPRS_MAX_PDCH_Dyn_avg = [ P414bis / observation period ] Average value of MAX_SPDCH_Limit (allocated SPDCH to MFS)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (4/5)


Allocated SPDCH in B8 and B9 (hourly evolution)
Compared hourly evolution (B8/B9) of PDCH allocation counters
(Average on 224 cells with typical 2TRX configuration : NB_TS=14, MIN_PDCH=2, MAX_PDCH=9)
10

Page 66

P414
5

P414bis
3

2
0:00 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00 9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00 19:00 20:00 21:00 22:00 23:00

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (6/10)


Examples of MAX_SPDCH_LIMIT Calculation (1/4)
Page 67

Pa ra meters MIN_PDCH MAX_PDCH MAX_PDCH_HIGH_LOAD HIGH_TRAFFIC_LOAD_GPRS THR_MARGIN_PRIO_CS NB_TS 2 9 2 85 15 14

Typical Parameters in Orange France for a cell with 2 TRX

Case 0: No CS & No PS traffic


AV_USED_CS_TS AV_USED_PS_TS MAX_SPDCH_DYN (B8) MAX_SPDCH_LIMIT (B9)
B T S T T T T T T T T T T T T T

0 0 9 8

Free TS (12) are split equally between CS and PS (6 and 6) 6 TS are kept for circuit, so 8 are allocated to packet traffic (6+2 due to MIN_PDCH)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (7/10)


Examples of MAX_SPDCH_LIMIT Calculation (2/4)
Page 68

Case 1: Medium CS & No PS traffic


AV_USED_CS_TS AV_USED_PS_TS MAX_SPDCH_DYN (B8) MAX_SPDCH_LIMIT (B9)
B T S T T T T T T T T T T T T T

4 0 8 6

Free TS (8) are split equally between CS and PS (4 and 4) 4 more TS are kept for circuit, so 6 are allocated to PS traffic

Case 2: No CS & Medium PS traffic


AV_USED_CS_TS AV_USED_PS_TS MAX_SPDCH_DYN (B8) MAX_SPDCH_LIMIT (B9)
B T S T T T T T T T T T T T T T

0 4 9 9

Free TS (10) are split equally between CS and PS (5 and 5) 5 TS are kept for circuit, so 9 are allocated to PS traffic

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (8/10)


Examples of MAX_SPDCH_LIMIT Calculation (3/4)
Page 69

Case 3: Medium CS & PS traffic


AV_USED_CS_TS AV_USED_PS_TS MAX_SPDCH_DYN (B8) MAX_SPDCH_LIMIT (B9)
B T S T T T T T T T T T T T T T

4 4 8 7

Free TS (6) are split equally between CS and PS (3 and 3) 3 TS more are kept for circuit, so 7 are allocated to packet traffic

Case 4: Medium CS & High PS traffic


AV_USED_CS_TS AV_USED_PS_TS MAX_SPDCH_DYN (B8) MAX_SPDCH_LIMIT (B9)
B T S T T T T T T T T T T T T T

4 7 8 8

Free TS (3) are split equally between CS and PS (1.5 and 1.5) But we must keep a margin of 2 TS for CS due to HIGH_TRAFFIC_LOAD_GPRS, so 8 remain allocated for PS

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (9/10)


Examples of MAX_SPDCH_LIMIT Calculation (4/4)
Page 70

Case 5: High CS & Medium PS traffic


AV_USED_CS_TS AV_USED_PS_TS MAX_SPDCH_DYN (B8) MAX_SPDCH_LIMIT (B9)
B T S T T T T T T T T T T T T T

7 4 5 5

Free TS (3) are split equally between CS and PS (1.5 and 1.5) We must keep a margin of 2 TS for CS due to HIGH_TRAFFIC_LOAD_GPRS, so 5 TS remain allocated for PS

Case 6: High CS & High PS traffic


AV_USED_CS_TS AV_USED_PS_TS MAX_SPDCH_DYN (B8) MAX_SPDCH_LIMIT (B9)
B T S T T T T T T T T T T T T T

7 7 4 5

We must keep a margin of 2 TS for CS due to HIGH_TRAFFIC_LOAD_GPRS, so 5 TS remain allocated for PS

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex3: Allocated SPDCH (10/10) Conclusion


Page 71

In B8:
the BSC computes the limit of TS that could be allocated to the MFS (MAX_SPDCH_DYN) These TS are not necessarily allocated to the MFS

In B9:
The BSC computes the TS needed by itself for CS, by the MFS for PS, and allocates actually these TS to the MFS (MAX_SPDCH_LIMIT)

Conclusion in a real network


Most cells have low PS traffic (on average), which leads to lower MAX_SPDCH_LIMIT in B9 than MAX_PDCH_DYN in B8 (see case 0 and 1) In case PS traffic increases, the MAX_SPDCH_LIMIT would be equal or even higher to MAX_SPDCH_DYN (see case 2, 4 and 6)

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Agenda
Page 72

Impact on QOS main indicators


Impact on CS QOS indicators Impact on PS QOS indicators Annexes
Annex1 : Reallocation Variations Annex2 : increase of CS1 usage Annex3 : Allocated SPDCH Annex4 : Speech Codec Variation

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

All rights reserved 2005, Alcatel

Annex4: Speech codec variation


Speech Coder Counters variation Explanation The analysis has
show the following change in the implementation of the counter:
In B8, we counted as:
Data call: MC701E; Speech:
Support FR AMR or HR AMR: MC701D Only support FR&HR&EFR: MC701C Only support FR&HR: MC701B Only support FR: MC701A Other: Not counted;
Page 73

In B9
Data call: MC701E; Speech:
Support FR AMR or HR AMR: M701D Only support FR&HR&EFR: M701C Only support FR&HR: M701B Only support FR: MC701A Other: MC701A;=> accepted in B9, the description in BCC will be updated accordingly

The "other" including:


Only support HR; Only support EFR&HR; Only support FR&EFR; Only support EFR.
All rights reserved 2005, Alcatel

B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006

Page 74

www.alcatel.com
B8-B9 MR1Ed4 - QOS Variations / 31 Jan 2006
All rights reserved 2005, Alcatel