B9 Status at MR1 Ed4 QD11

Release B9 B9 MR1 ed4 + QD#11 Status
27/06/06
All rights reserved 2005, Evolium
Agenda
Page 2
Context of B9 SYS-DR5 Delivery content QoS feedback Remaining Features & Configuration where feedback is welcomed Main Remaining Issues B9 Introduction Warning towards RSC Appendixes
IOT Status PS Alerters definition Features & configuration tested on field
B9 MR1 ed4+QD#11 status 27/06/06
Context of B9 SYS-DR5
Page 3
Main conditions to run General Availability Decision review are reached

Acceptance and pilot phases completed for the two FOs, Orange and Vimpelcom.
Green light for rollout granted for the two FOs with MR1 ed4 (QD8 and QD11)
Already widely deployed in FOs , but additionally also with numerous early adopters (more than 600 BSSs in B9)
Rollout finished in Vimpelcom (Nino).
Rollout ongoing in Orange France 315 BSSs on a total of 321 are in B9

Numerous early adopters have already started or finalized roll-out
All emergency issues coming from FOs and early adopters are followed and managed in daily UO meeting with NPI, ARO(PCS), C-TAC, and concerned Programs
Main issues are solved ; remaining are planned in next maintenance edition
Alcatel management decision taken to run General Availability Decision Review

Delivery Content BSSSAW01B Ed04_QD11

Page 4
Documentation
Page 5
BSS Software List - 3BK 13016 0991 TQZZA

Available
Restriction List - 3BK 13016 0993 TQZZA

Ed02 available
Operator Hints - 3BK 13016 0994 TQZZA

Ed01 available
Migration Software and Upgrade RL and OH - 3BK 13016 0995 TQZZA

Ed02 available
Counters and Indicators Status - 3BK 13091 0142 TQZZA

Ed01 available
Annex to the delivery note (technical dossier) - 3BK 13016 0992 TQZZA
Available
Page 6
QoS Feedback
Content
Page 7
B9 QOS CS
Main Results Main Improvements Remaining Issues
B9 QOS PS
Main Improvements Remaining Issues QOS expected variation due to new B9 algorithms Conclusion Annexes
B9 QOS
Page 8
CS
QOS Circuit B9MR1Ed4QD11 Radio Link Establishment - Results

Delta B8-B9 Figures must not be taken as reference (Not frozen networks on most of the pilots due to several B9 patches on a long period)
Page 9
SDCCH Congestion Rate

Customer
SDCCH Assignment Failure B8

2.87% (2.33 3.53)
B8
0.31% (0.02 - 0.87) Unreliable 2.03% 2.06% 0.10% 0.06% 0.05% 1.7% 0.48%
B9
0.73% (0.3 1.73) 0.94% (0.06 4.89)
B9
3.2% (2.78 3.88)
Orange France
(LeMans-Evolium)
Orange France
(LeMans-G2)
Tmobile (3BSCs)
SL,W,WDS
Stable 3.85%
1.92% 0.36% 0.08% 0.05% 0.79% 0.71%
8.73% 9.29% (5.78 8.80) (7.43 9.16) Under Investigation 4.52% (Burst on some 3.88% cells) 3.81% 5.18% 3.59% 5.13% 2.4% 5.44% 1.81% 2.43% 2.67% 5.67% 2.19% 3.4%
SFR (Evolium) SFR (G2) VIP (QD8)(PreP) VIP (QD8)(Nino)
QOS Circuit B9MR1Ed4QD11 Call Establishment - Results

Page 10
SDCCH Drop Rate

Customer
B8
0.40%
B9
0.43%
RTCH Assign Unsuccess rate B8 B9

<0 (FR counter B8MR5) <0 (FR counter B8MR5) 0.35% 0.21% 0.23% 0.68% 0.65% 0.52% 0.64% 0.48%
Call Setup Success Rate B8

(unreliable) (FR counter B8MR5) (unreliable) (FR counter B8MR5)
B9
99.09%
Orange France
(LeMans) (evolium)
Orange France
(LeMans) (G2)
1.05%
1.04%
0.83%
98.14%
Tmobile (3BSCs)
SL,W,WDS
0.33% 0.26% 0.47% 0.27% 0.39% 0.41% 0.7%
Stable 0.40%
0.3% 0.51% 0.32% 0.52% 0.4% 0.77%
0.11% 0.2% 0.27% 0.51% 0.46% 0.23% 0.51%
Stable / 99.31% Improved 99.54% 99.31%

99.05% 98.97% 99.01% 97.56%
99.5% 99.50% 99.22% 99.17% 99.02% 99.37% 98.72%
SFR (Evolium) SFR (G2) VIP (QD8)(PreP) VIP(QD8)(Nino)
QOS Circuit B9MR1Ed4QD11 Radio Congestion - Results

Page 11
RTCH Congestion Rate

Customer
B8
0.01%
B9
0.03%
Incoming Inter BSC Congestion Rate B8 B9

0.85% 0.99%
Incoming Intra BSC Congestion Rate B8 B9

1.12% 1.08%
Orange France
(LeMans) (evolium)
Orange France
(LeMans) (G2)
0.11%
0.22%
5.29%
3.25%
0.72%
1.42%
Tmobile (3BSCs)
SL,W,WDS
0.13% 0% 0.01% 0.05% 0.06% 0.17% 0.89%
Stability or Low increase 0.01% (unreliable) Related to new 0.48% 0% 1.61% 0.02% Radio Ressource 0% 1.06% Algorihm 0.28% Allocation
0.06% 0.1% 0.01% 0.63% 0.36% 0.36% 4.79% 14.67% 0.51% 0.44% 0.88% 11.63%
0.99% 0.24% 0.12% 1.89% 1.51% 5.54% 11.11%
1.31% 0.23% 0.41% 1.95% 2.46% 0.68% 8.83%
SFR (Evolium) SFR (G2) VIP (QD8)(PreP) VIP (QD8)(Nino)
QOS Circuit- B9MR1Ed4QD11 Call Drop rate Results

Page 12
Call Drop Rate

Customer B8 B9
Call Drop Rate - other networks

Customers B8 B9
Orange France (LeMans) (evolium)

Orange France (LeMans) (G2) Orange France West Tmobile (3BSCs) SL,W,WDS SFR (Evo, G2) VIP (QD8)(PreP) VIP (QD8)(Nino)
0.81%
0.95%
Voxtel
0.9%
0.96%
1.78%
2.25%
Orange Romania
0.41%
0.39%
1.01% 0.89% 0.70% 0.97% 0.77% 1.21% 0.63% 1.35%
1.03% unreliable 0.84% 1.04% 1.01% 1.40% 0.49% 1.3%
Jersey
0.7%
0.75%
Stable on some networks, slight degradation observed on others NO CUSTOMER COMPLAINT. => Indicator very sensible to traffic profile; On networks where this delta is observed, the observation time between B8 and last B9QD11 is 3 months later and the networks are no more in the equivalent configuration. => Recommendation: Specific monitoring to be done by RSC/RNE for next B8-B9 migrations
QOS Circuit- B9MR1Ed4QD11 Call Drop Rate

Page 13
B8-> B9QD11 Migration
Orange Romania (B8-B9QD11)
B8
B9
B8 Reference
B8
140000
Call drop
B9
1,4 1,2 1 0,8 0,6 0,4 0,2 0
Preemption Drop - BSS RTC Drop BSS Intern Drop - HO Drop - Radio % RTCH drop % Call Drop
Orange France Ouest (B8-B9QD11)
120000 100000 80000 60000 40000 20000 0

04 /2 4/ 20 06 04 /2 6/ 20 06 04 /2 8/ 20 06 04 /3 0/ 20 06 05 /0 2/ 20 06 05 /0 4/ 20 06 05 /0 6/ 20 06 05 /0 8/ 20 06 05 /1 0/ 20 06 05 /1 2/ 20 06 05 /1 4/ 20 06 05 /1 6/ 20 06 05 /1 8/ 20 06 05 /2 0/ 20 06 05 /2 2/ 20 06 05 /2 4/ 20 06 05 /2 6/ 20 06 05 /3 0/ 20 06
B9 QOS Main Improvements - GSM

Page 14
The B9 main improvments can be summarized below

Call Setup Success Rate increased when CS is favoured
Orange Romania See Graph =>
Call success
B8-> B9 Migration
30000 25000 20000 99 15000 98,5 10000 5000 0
05 /0 7/ 20 05 06 /0 8/ 20 05 06 /0 9/ 20 05 06 /1 0/ 20 05 06 /1 1/ 20 05 06 /1 2/ 20 05 06 /1 3/ 20 05 06 /1 4/ 20 05 06 /1 5/ 20 05 06 /1 6/ 20 05 06 /1 7/ 20 05 06 /1 8/ 20 05 06 /1 9/ 20 05 06 /2 0/ 20 05 06 /2 1/ 20 05 06 /2 2/ 20 05 06 /2 3/ 20 05 06 /2 4/ 20 05 06 /2 5/ 20 05 06 /2 6/ 20 05 06 /2 7/ 20 05 06 /2 8/ 20 05 06 /2 9/ 20 05 06 /3 0/ 20 05 06 /3 1/ 20 06 06 /0 1/ 20 06 06 /0 2/ 20 06 06 /0 3/ 20 06 06 /0 4/ 20 06
Higher Values
100 99,5
Call drop Assign Unsucc SDCCH drop % Call success
98
% Call setup
97,5
Vimpelcom (QD8)
Multiband RFD improvment
B9 QOS Remaining Issues - GSM

Page 15
SDCCH Assignement Failure

Very low variation
Ressources Management
Radio congestion (no impact end users for Congestion on HO) Parameter tuning can reduce the radio congestion (tested in QD10 in ERA)
Under observation
Call drop rate
To be monitored in the next migrations with equivalent configurations before and after migrations
B9 QOS
Page 16
PS
B9 QOS
Page 17
PS Main Improvements
B9 QOS Main Improvements - PS

Page 18
PS Improvements brought by New features

Abis Dynamic and Statistical Multiplexing features have been successfully applied on global network
Orange France network offers MCS9 with ABIS dimensioning equivalent to B8 class 2 (MCS5) without any congestion
Extended UL TBF Mode (Main results from end user field tests) NACC/PSI (Main results from end user field tests) 8-PSK en UL
Abis Dynamic Orange France feature tests ExtraAbisTS reduction

B9 Abis Dimensioning Equivallent to B8 class 2 Allows MCS9 usage w/o limitation
Page 19
BSC1
In B8, BSC with about 80% of cells in class 2
Dynamic Abis Benefit1: Same transmission ressources as in B8 AND higher coding schemes usage
BSC2
In B8, BSC with about 80% of cells in class 4
Dynamic Abis Benefit2: lower transmission ressources than in B8 AND Same coding schemes usage On 80% of the cells of BSC2, the extraAbisTS have Been divided by 3
B8
B9 Iso B8
Extra Abis TS reduction MaxMCS=9 (Mainly on BSC2)
MAX_PDCH =12
Abis Dynamic Coding scheme Usage Orange France West Region Roll-out
Page 20
DL EGPRS useful RLC traffic

300000000 250000000 200000000 150000000 100000000 50000000 0
04 /24 /20 06 04 /26 /20 06 04 /28 /20 06 04 /30 /20 06 05 /02 /20 06 05 /04 /20 06 05 /06 /20 06 05 /08 /20 06 05 /10 /20 06 05 /12 /20 06 05 /14 /20 06 05 /16 /20 06 05 /18 /20 06 05 /20 /20 06 05 /22 /20 06 05 /24 /20 06 05 /26 /20 06 05 /30 /20 06
MCS9 usef MCS8 usef

80 70 60 50 40 30 20 10 0 400000000 350000000 300000000 250000000 200000000 150000000 100000000 50000000 0
GPRS DL useful RLC traffic

80 70 60 50 40 30 20 10 0
MCS7 usef MCS6 usef MCS5 usef MCS4 usef MCS3 usef MCS2 usef MCS1 usef %ioMCSxusef %io8PSKusef
CS4 usef CS3 usef CS2 usef CS1 usef %io CSx usef
Migration Period
8PSK Usage
90000000 80000000 70000000 60000000 50000000 40000000 30000000 20000000 10000000 0
UL EGPRS useful RLC traffic

40 35 30 25 20 15 10 5 0
MCS9 usef MCS8 usef MCS7 usef MCS6 usef MCS5 usef MCS4 usef MCS3 usef MCS2 usef MCS1 usef %io MCSx usef %io 8PSKusef
180000000 160000000 140000000 120000000 100000000 80000000 60000000 40000000 20000000 0
04 /24 /20 06 04 /26 /20 06 04 /28 /20 06 04 /30 /20 06 05 /02 /20 06 05 /04 /20 06 05 /06 /20 06 05 /08 /20 06 05 /10 /20 06 05 /12 /20 06 05 /14 /20 06 05 /16 /20 06 05 /18 /20 06 05 /20 /20 06 05 /22 /20 06 05 /24 /20 06 05 /26 /20 06 05 /30 /20 06
Migration Period
GPRS UL useful RLC traffic

71 70 69 68 67 66 65 64
04 /24 /20 06 04 /26 /20 06 04 /28 /20 06 04 /30 /20 06 05 /02 /20 06 05 /04 /20 06 05 /06 /20 06 05 /08 /20 06 05 /10 /20 06 05 /12 /20 06 05 /14 /20 06 05 /16 /20 06 05 /18 /20 06 05 /20 /20 06 05 /22 /20 06 05 /24 /20 06 05 /26 /20 06 05 /30 /20 06
Migration Period
04 /24 /20 06 04 /26 /20 06 04 /28 /20 06 04 /30 /20 06 05 /02 /20 06 05 /04 /20 06 05 /06 /20 06 05 /08 /20 06 05 /10 /20 06 05 /12 /20 06 05 /14 /20 06 05 /16 /20 06 05 /18 /20 06 05 /20 /20 06 05 /22 /20 06 05 /24 /20 06 05 /26 /20 06 05 /30 /20 06
Migration Period
B9 End-to-end performances
Vimpelcom pre-pilot : non-regression performance tests
Page 21
FTP throughputs (measured in real network conditions)

Radio conditions : around -75 dBm Normal load (no specific action taken) 140 MS class 10 (4+2) 139 120 Class 5 (MaxMCS=9) in B8 132
100
B8
65
Stability of DL throughput
80 60 40 20 0
B9
B9 B8
J High Increase of uplink

throughput 8PSK in uplink
27
FTP downlink FTP uplink
Throughputs in kbit/s
B9 End-to-end performances
Orange France : commitments on performances (static tests)
Page 22
GPRS CS3/CS4 Ping (ms) Commitments Measurement results Avg Min Max
Delay 0s 56o 1460o 650 2000 648 1787 621 1672 1042 2664
Delay 30s 56o 1460o 1110 3150 1043 2672 761 2444 1312 2905
J
In Orange France, commitments have been taken on absolute values only, not on non-regression compared to B8
GPRS CS3/CS4 FTP (kb/s by TS) Commitments Measurement results
DL UL 200KB 500KB 1000KB 200KB 500KB 1000KB 17,0 17,5 17,5 17,0 17,5 17,5 Avg 17,55 18,05 18,23 17,73 19,04 17,93 Min 12,08 16,38 17,08 14,72 17,48 17,24 Max 18,06 18,28 18,36 18,12 19,20 18,04 Delay 0s 56o 1460o 600 1680 610 1670 570 1633 661 1683 Delay 30s 56o 1460o 1080 2440 994 2157 711 1802 1092 2263
Conclusions:
All targets have been reached Very Good results with FTP UL EDGE > 50kbit/s (far above target)
EDGE MCS9 Ping (ms) Commitments Measurement results Avg Min Max
EDGE MCS9 FTP (kb/s by TS) Commitments Measurement results
DL UL 200KB 500KB 1000KB 200KB 500KB 1000KB 37,0 42,5 45,0 37,0 42,5 44,0 Avg 37,79 44,52 47,18 44,14 50,92 49,30 Min 26,08 26,2 32,48 27,64 36,96 38,08 Max 42,14 48,9 51,36 45,68 51,96 50,48
B9 New features tests

Extended UL TBF mode
Page 23
Orange France
Up to 62% gain on ping !
For EDGE ping 1460B, thanks to a gain on TBF establishment+high MCS maintained
Impact of Extended UL TBF on EDGE Ping measurements
EDGE ping 56B : 316ms HTTP gain : 33%

(reference page download time : down from 13,4sec to 8,9sec)
Statistical non-regression has been checked on pilot area J GO for network wide activation
1800 1600 1400 1200 1000 800 600 400 200 0
1670
610 316
disabled enabled disabled
643
enabled
Ping 56 bytes
Ping 1460 bytes
T-Mobile Germany
50% gain on short EDGE ping 31% gain on HTTP reference page

NACC and PSI Status
Page 24
Orange France
50% gain on TCP outage in DL
(from 3,3 sec to 1,6sec, with both features activated)
3,50 3,00 2,50 2,00 1,50 1,00 0,50 0,00
TCP outage per reselection, in FTP DL Transfer (avg in seconds, on 50% best samples)
3,29 2,51 1,93 1,62
Statistical non-regression has been checked on pilot area GO for network wide activation
Ref
NACC
PSI
NACC&PSI
T-Mobile Germany
Test performed successfully
Drive tests around one site with 3 P-GSM and 3 DCS cells, to assess feature gain on FTP transfers, in both UL and DL Mean FTP transfer not relevant : too many fluctuations Post-processing on Ethereal traces to get duration of TCP interruption

8PSK, IR and resegmentation in UL
Page 25
Orange France
Field tests performed in various radio conditions, to evaluate UL performances Parameter set1 (IR activated / Resegmentat deactivated) is the most efficient 8PSK + IR : +120% on RLC throughput compared to B8, in bad radio conditions
UL RLC/MAC throughput - Good conditions
UL RLC/MAC throughput - Medium / Bad conditions
100 90 80 70 60 50 40 30 20 10 0 28 47 62 55 43
B8
B9 def
SET1
SET2
SET3
UL RLC/MAC throughput - Mobility

100 90 80 70 60 50 76 77 76 76
B9default: IR and resegment. both deactivated SET1:IR SET2:Resegm. SET3:IR+Resegm.
100 90 80 70 60 50 40 30 20 10 0
89
88
87
89
33
40 30 20 10 0
29
B8
B9 def
SET1
SET2
SET3
B8
B9 def
SET1
SET2
SET3
B9 QOS
Page 26
PS Issues
B9 QOS Remaining Issues - GPRS

Page 27
Some GPRS KPIs remain below B8

DL TBF establishment success rate
Delta is usually not high and the end user impact should be low thanks to improvements brought by new B9 features
UL TBF establishment success rate

Delta is mainly linked to sleeping cells or highly degraded cells A end user impact can be foreseen; analysis on going mainly on SFR network
Some other GPRS QOS indicators variations can be observed and are linked to new B9 algorithms => See next slides
B9 QOS Remaining Issues - GPRS Sleeping GPRS cells

Page 28
Alerters (see annexes) have been defined to detect sleeping GPRS cells and Degraded UL TBF establishment cells Degraded DL TBF establishment cells Feedbacks from Networks in B9MR1Ed4QD11: Orange France IDF same number of sleeping Cells in B9 compare to B8MR5 (15 days analysed on 579 cells : 3 sleeping cells seen) To be completed with last migrated BSCs Orange Romania (2BSCs): no sleeping cells since the migration (2 weeks) Jersey (4BSCs) : few occurrences (3 weeks of QD11) Sleeping cells cause BSS : 2 cells (Workaround : reinit GPRS) Radio Failure cause : 2 cells (2 different Workarounds : reinit GPRS, lock/unlock BTS) Full sleeping (no UL Requests) : 1 cell (Workaround : reinit GPRS) SFR (4BSCs): B8 : average of 2 cells per week (reference seen on less than 2 weeks) B9 : average of 3 cells per week (reference on 3 weeks) (mainly G2 BTS)
Tmobile (3BSCs):
B9 : 1 or 2 cells per week in average (mainly G2 BTS)
B9 QOS
Page 29
PS - QOS Normal Variations
B9 QOS Normal Variations - GPRS

Page 30
Some GPRS QOS indicators variations can be observed and are linked to new B9 algorithms
Reallocation variations Increase of CS1 usage in DL Retransmission Decrease of average Allocated SPDCH Increased usage of soft preemption (P417 counter) See Annexes for more details
B9 QOS Normal Variations - GPRS UL/DL Reallocation Variations (1/3)

Page 31
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 explanations in Annex1)
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

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
B9 QOS Normal Variations GPRS (2/3) DL Realloc 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 32
%Success
External stop
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
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
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
B9 QOS Normal Variations GPRS (3/3) UL Realloc 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 resource realloc T4
100 90 80 70 60 50 40 30 20 10 0
%Success
BSS fail
Prep fail
Success
Radio fail
Page 33
% Success
External stop
B9 QOS Normal Variations GPRS Coding scheme usage CS1

Page 34
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

100 90 80 70 60 50 40 30 20 10 0
See explanation in Annex2

B9 QOS Normal Variations GPRS Retransmission

Page 35
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. It is considered by Alcatel as normal behaviour
In DL, when there is an increase of retransmission rate compared to B8

It is also be linked the increase of usage on high coding schemes There are 2 possible reasons for this increase
in B8, there were High Ater Usage or The migration in B9 is not iso B8 When Max_MCS > MCS allowed in B8 according to the class of the cell
In B9 with Dynamic Abis, higher coding schemes used. As a consequence, an increase of retransmission can be oberved
B9 QOS Normal Variations GPRS Decrease of average Allocated SPDCH

Page 36
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
B9 QOS Normal Variations GPRS(1/3) Increased usage of soft preemption : P417

Page 37
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).

Page 38
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

Page 39
PDCH Preemption
30000 25000 20000 15000 10000 5000
Soft preempted
84
0
106
02/28/2006
171
03/01/2006
114
03/02/2006
159
03/03/2006
4
03/04/2006
9
03/05/2006
109
03/06/2006
181
03/07/2006
195
03/08/2006
24496
03/09/2006
23754
03/10/2006
10116
03/11/2006
8192
03/12/2006
21493
03/13/2006
Example:
In B8 : values between 0 and 200 on the full BSC In B9 : values between 8000 and 25000 on the full BSC
02/27/2006
B9 QOS
Page 40
PS - Conclusion
QoS PS conclusion (1/2)

Page 41
High improvements brought by new features Several algorithms were impacted by the introduction of these new features
=> the QOS follow-up is impacted by these modifications with significant variations on several QOS indicators
Normal variations Unexpected variations
These improvements compensate the degradation of some PS QOS indicators (mainly TBF establishment success rate under investigation in TD) not directly perceived by end user. These improvements are obviously more significative on networks with Edge and CS3/CS4 activated (where the benefit of dynamic Abis is the most obvious)
QoS PS conclusion (2/2)

Page 42
The end user and new features tests are very important to show the non-regression and improvements of B9 => you can ask us some example of test sheets done on other networks => thank you to provide us the feedbacks on the tests you will do
Page 43
Remaining FEATURES & CONFIGURATIONS where feedback is welcomed
B9 features tested in Acceptance ONLY

Page 44
Telecom
NC2 improvement: Cell ranking with load criteria (without QoS) mobiles bad behaviour to activate the feature on field
O&M Improvements
Remote Inventory from the OMC-R for MFS Enhanced Remote Inventory export interface Customisation of radio parameter default values Counters on electromagnetic emission (EME) Better integration of IMT Inform NPI when these Export ASCII file interface for GB interface features will be used on V490 Introduction (for OMC) networks Activation follow-up, end of the activation
B9 features NOT specifically tested (1/2)

Page 45
Features where no need for feedback requested to pronounce GADR
Telecom
Load based 3G handover filtering ANC eVOlution for size reduction and TMA supply Support of Extended UL TBF mode, NACC and Packet (P) SI Status on G2 BTS
O&M Improvements
MFS alarm flow reduction Activation follow-up, end of the activation Keeping adjacencies on inter-OMC move BTS
Inform NPI when these features will be used on networks
RNO/NPA
Direct connection of RNO to the OMC-R Move BSS data between two NPA servers RNO optimisation of tree building filling for non RNO objects
B9 features NOT specifically tested (2/2)

Page 46
Features for which feedback from first user to be obtained

GSM
Inform NPI when this feature will be used on networks
Unbalanced TRX Output Power
B8 features non regression status

Page 47
Features tested by customers

Dynamic SDCCH allocation TBF establishment time improvement CS-3 / CS-4 Inform NPI when these EDGE features will be used on Warnings on QoS indicators variation networks Display of indicator reliability (from PM reporting) Multi-Objects evolution charts QoS at Busy Hour Support of Centralised backup for X-Large OMC-R - legato Citrix support / RNO WAN GCH Congestion Control: GPRS & EDGE (implicit) GPRS redirection - lab only Full intra-RA LLC PDU re-routing - lab only GCH resource anticipation - fast access - lab only Network Controlled cell reselection (NC2) in Packet Transfer Mode - lab only
Features to be tested
GPRS/EDGE with Abis/Ater over satellite links 3G search deactivation in PTM Tool Chain 10500 Cells (availability date to be confirmed) planned by VIP
B7 features non regression status

Page 48
Features tested by customers

Adaptative Multirate Codec (AMR) in HR mode Adaptative Multirate Codec (AMR) in FR mode GSM to UMTS cell re-selection Inform NPI when these Multiple GPU per BSC features will be used on Interoperability with UMTS networks GSM to UMTS cell re-selection GPRS to UMTS cell re-selection triggered by MS Radio Measurement Statistics (RMS) Extensive Logical Configuration update (MLU) Tandem free operation (TFO) lab only Coordination of CS and GPRS services via Gs interface lab only
HW configuration NOT tested during FOs & early adopters

Page 49
HW for which feedback from first user will be interesting
BTS
Edge+ HP TRA (including 2nd Abis) Mix M4M/M5M with EDGE
Inform NPI when these configurations will be used on networks
MFS
DS10 RC23 30 GPU DS10 RC40 30 GPU
OMC
X Large
New New HW (V490) 6000 cells
Page 50
MAIN REMAINING ISSUES on MR1 ED4 QD11
Main remaining FRs(U0) not yet corrected (1/6)

Page 51
3BKA45FBR184547 - SDCCH assignment failure degradation after Migration to B9

Reported by CLARO and seen on other networks too Operational Impact : decreased CS accessibility Work-around: under study (one track is to change T3111value approval from CLARO on-going to perform the modification on 2 cells) Correction : under investigation
3BKA45FBR183007 - Sleeping GPRS G2 DRFU Cells

Reported by T-MOBILE and SFR Operational Impact : no PS on that cell Preventive work-around: none Corrective work-around: Re-Init GPRS at cell level Correction : 1 case corrected in GPU (QD#13) ; 1 other case under investigation

Page 52
3BKA45FBR187032- Since B9 introduction, UL TBF establishment success rate decrease on whole BSS
Reported by SFR Operational Impact : decreased PS accessibility Work-around: none Correction : under investigation ; 1 correction already identified ; other corrections under study, via trace collection campaigns in SFR and TLO ; target = QD#13
3BKA45FBR188213 DL TBF establishment success rate degradation in B9 MR1 ed5

Reported by VIP Operational Impact : decreased PS accessibility Work-around: none Correction : under investigation

Page 53
3BKA45FBR184632 - Problems with FTP and Ping application for SIEMENS S75 MS
Reported by T-MOBILE Operational Impact : in certain conditions, in EDGE, ping duration are increased and ftp throughputs decreased Work-around: none Correction : corrected in GPU for QD#13
3BKA45FBR186206 CS2/CS4:First 1000 Byte Ping needs more than 5 sec in case that Extended UL TBF Mode and LLC PDU Re-routing features are enabled
Reported by T-MOBILE Operational Impact : long ping durations in GPRS when the 2 optional features are enabled (Extended UL TBF Mode and LLC PDU Re-routing) Work-around: none Correction : corrected in GPU for QD#13

Page 54
3BKA45FBR188097 Unix Patch installation failure during B8/B9 MFS A9135 Migration
Reported by Orange France
Operational Impact : if, during migration method application, the check of Unix shell type is NOK on stand-by machine, then Unix patch installation should not be performed Security level of the MFS is equivalent to the B8 one Work-around: change the global shell of root from csh to ksh on both stations Correction : under investigation
3BKA45FBR186666 GPRS blocked on 2 cells = 100% failure cause Radio congestion, followed by GPU auto-reset upon Cell Re-Init
Reported by KSA Operational Impact : DLS inconsistency due to the EGSM_RR_ALLOC_STRATEGY change from 0 to 1. During this change, the data model should also change but it does not It impacts networks having a mix of PGSM+G1 frequency bands Work-around: Cell Deletion/Re-Creation (all TRXs of the cell are re-created with the new Data Model) Correction : corrected by OMC add-on for QD#13

Page 55
3BKA20FBR182557 In case of firewall allowing only the floating IP address, the SNMP exchange protocol cannot be established between the MFS and the OMCR
Reported by SFR Operational Impact : The OMC-R never receives responses from the MFS on SNMP because the request from the OMC-R for the activation of SNMP on MFS active station is done through the floating IP address ( the only one known by the OMC-R ), but the response from the MFS is done with the fixed IP address Work-around: None (or deactivate the firewall) Correction : Under study for B10
3BKA20FBR180896 & 182449 The dataPatch file needs to be systematically applied manually at the end of B8 to B9 MFS migration
Reported by SFR & ORO
Operational Impact : GPRS degradation on associated BSSs in B9 Work-around: Manual download of dataPatch file after Validate the New MFS Software step is completed Correction: MR4

Page 56
3BKA45FBR189463 - In case of Abis ring and BBH in at least one cell, if the Abis1 fails, there is no more call possible on TRX that are in BBH mode
Reported by True Move Operational Impact : in case of Abis ring and BBH in at least one cell, if the Abis1 fails, there is no more call possible on TRX that are in BBH mode because they become in dummy configuration Work-around: Reset all TREs that are concerned Correction : corrected in BTS in MR4 and in MR1 to be decided
Already corrected in QD#12 (1/3)

Page 57
3BKA20FBR187631 - No GPRS call after B8-B9 Migration for certain E-GSM cell configurations
Reported by KSA Operational Impact : after B8->B9 Migration or after Cell Creation in B9, no PS is possible on E-GSM cells configured with Hopping TRX and EGSM_RR_ALLOC_STRATEGY = 0 Preventive work-around: configure the cell with NH, or set EGSM_RR_ALLOC_STRATEGY = 1 but with the side effect that Phase 1 MS will fail to connect G1 TRX Corrective work-around: same as preventive one
3BKA20FBR185991- GPRS is not allowed by the OMC-R on hopping P-GSM TRX within E-GSM Cells in case EGSM_RR_ALLOC_STRATEGY = 0
Reported by KSA Operational Impact : not possible to modify such cell configurations nor to create them It concerns networks having a mix of PGSM+G1 frequency bands Palliative work-around: migrate to B9 with EGSM_RR_ALLOC_STRATEGY=1 but Phase 1 MS will hardly work

Page 58
3BKA20FBR185729 OMC-R/NMC re-synchronisation functionality does not work

Reported by SFR Operational Impact : OMC-R/NMC re-synchronisation functionality does not work Preventive work-around: none Corrective work-around: none
3BKA20FBR187787 - After alarm acknowledgment from NMC, several field of the alarm are disappearing in AS 3BKA20FBR187788 - Answer to the NMC action Retrieve Current Alarms Data does not contain the alarm acknowledgment information 3BKA20FBR187789 - After resynchronisation from AS, several fields of the alarm are disappearing in AS
Reported by SFR Operational Impact : functionality Alarm Acknowledgment Propagation Between OMC-R and NMC cannot be used Preventive work-around: none Corrective work-around: none

Page 59
3BKA20FBR186647 - B9 GPRS Cells Misaligned even after Resynchronisation and Re-initialize GPRS
Reported by KSA Operational Impact : loss of O&M supervision, no possibility to recover GPRS activity on misaligned cells Preventive action: none Corrective action: none
Maintenance releases
Page 60
MR1 ed4
QD12: delivered under validation in KSA (new BSC SW, GOM patch, OMC patches to correct Temip issues) QD13: in preparation only to solve blocking remaining issues for customers having started with MR1ed4 ( MFS patch to correct TMO issues and OMC add-on to correct E-GSM issue of KSA) QDn: not planned today
MR1ed6
Target: end of June 06 Normal MR1 maintenance release, integrating all corrections of MR1 ed4 QD13 + OMC evolution to support MX MFS.
MR4
Target: end September 06
Mainly new equipments (Mx, Twin) + 2G-2G HO, PS on extended cell and QoS features
Page 61
Networks STATUS
B9 Introduction Status w625

Page 62
Area AMEI AMEI APAC E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM
Country KSA Pakistan Thailand Brazil France France Germany Jersey Moldavia Poland Romania Russia
Customer Ettihad Etisalat Mobily Paktel TAO / True Move CLARO Orange SFR/ CEGETEL T_Mobile Jersey Telecom Voxtel ERA Orange Vimplecom (Nizhny Novgorod)
Current relea se B9 B9 B9 B9 B9 B9 B9 B9 B9 B9 B9 MR1 MR1 MR1 MR1 MR1 MR1 MR1 MR1 MR1 MR1 MR1 ed4 ed4 ed4 ed4 ed4 ed4 ed4 ed4 ed4 ed4 ed4 QD# 12 QD# 10+ QD# 10+ QD# 11 QD# 12 QD# 11 QD# 11 QD# 11 QD# 10+ QD# 11
N b BSC in Tota l nb B9 of BSC 2 8 156 124 315 4 4 4 9 17 102 21 766 15 8 156 124 321 239 211 4 9 17 119 21 1244
B9 MR1 ed4 QD# 08 TOTAL
Networks already in B9 766 BSSs on overall 3733 base installed= 20%

B9 Introduction
Customer interested in B9
Area AMEI AMEI AMEI AMEI AMEI AMEI AMEI AMEI AMEI AMEI AMEI AMEI AMEI CHINA APAC APAC APAC APAC APAC E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM E&LAM Country Cameroon Egypt Ivory Coast Kenya Madagascar Mali Pakistan Qatar South Africa Sudan Tanzania Tunisia Vietnam China Brunei Indonesia Malaysia Philippines Vietnam Armenia Austria Bulgaria El Salvador Italy Caraibes Netherlands Paraguay Portugal Ukrainia Customer SCM / Mobilis / Orange Mobinil Orange Ivoiris Kencell / celltel SMM / Antaris Orange Orange Mobilink Qtel Vodacom Areeba Celtel Tanzania Orascom VMS & Vinaphone DST N ext relea se B9 B9 B9 B9 B9 B9 B9 B9 B9 B9 B9 B9 B9 B9 B9 MR1 MR1 M1 ed4 QD# 11 MR1 ed4 QD11 MR1 MR1 MR1 ed4 QD11 MR1 ed6? When July 06 Q2 06 July 06 June 06 Q2 06 July 06 Q4 06 June 06 Q3 06 Comments Edge deployment
Page 63
Edge deployment done in August 06 Edge deployment Edge deployment
MR1 MR4 MR1 MR4
July 06 Q1 07 Q4 06 Q2/ Q2 07 2007 2006 Q3 06 Q3 06 August 06 October 06 Q3/ Q4 06 July 06 July 06 Q3 06 September 06 Q3/ Q4 06 Q3 06 Q3 06 Q3 06
Edge deployment + MFS Evol Potential FO for Twin in B8, commitment to deliver twin in Q3'07 then B9 MR4 for twin BSC Evolution (and MBO evol) Viettel on ly 2007 Mx contractual commitment B7 upgrade is not clear due to equipment relocation
B9 MR1 corresponds to the last available edition
Indosat B9 CELCOM 013 (formerly TCSB) B9 Digitel B9 VMS B9 MR1 ed6 Vivacell Telering MOBILTEL Personal WIND Orange Orange Hola / Vox TMN UMC B9 MR1 B9 MR1 B9 MR1 B9 B9 B9 B9 B9 B9 B9 MR1 MR1 MR1 MR1 MR1 MR1 MR1
MFS Evolution
not clear
Page 64
Specific Warnings towards RSC
Specific Warnings towards RSC (1/4)

Page 65
Remaining problems are all included in the Restriction List

http://webqaf.cit.alcatel.fr/delivery/frames/release_b9.html RSC can extract the critical ones compared to their customers networks Main remaining issues with B9 MR1 ed4 are listed in the presentation
Methods including Restriction are specific for each MR

use the one delivered with the B9 MR1 ed4 software on delivery server do not use the last version available under DIAMS which refer only to the last SW release Be careful, sometimes restrictions cant be included in the method: read the table at the end of the SW migration & RL documents that precise the methods impacted by the restriction
Some B9 and non-regression features have not been tested on field

see technical presentation for the complete list need RSC feedback as soon as one of these features is activated on field

Page 66
Sanity Checks mandatory before MFS migration

Sanity checks to be launched twice on each B8 MFS : one week minimum BEFORE the migration to let time to correct potential issues and just before the migration to ensure the migration
MFS Patch installation

Be careful, the dataPatch file needs to be systematically applied manually at the end of B8 to B9 MFS migration
Unix patch installation

Be careful, if the patch installation fails, dont try a new attempt.
EGSM feature
Networks having EGSM_RR_ALLOC_STRATEGY=0 in B9 & hopping will encounter problems in a mix of PGSM+G1 frequency bands or in G1 band only Issues linked to FR 3BKA20FBR187631 (BSC) & 3BKA20FBR185991 (OMC) QD#12 is mandatory to avoid these problems

Page 67
Incorrect behaviour of script remove_db.pl used to remove a BSSIM database and described in the OMC-R TSG
FR from Orange France 3BKA45FBR189073 Side effect of the script is that other bssim db are removed A discover is then mandatory on non-suitable removed BSS A correction is brought as an OMC add-on in QD13
In case of sleeping cells, install alerters if customer is aware of them and agrees
A re-init GPRS can be launched automatically thanks to O&M automatic scripts
Go for B9 MR1 ed4 QD#11 + GOM patch of QD#12

The GOM patch has to be also installed to avoid MFS crash Note that this patch has not been tested by Orange Skill Center Up to each Orange network to decide if this patch can be installed anyway

Page 68
Some GPRS QOS indicators variations can be observed and are linked to new B9 algorithms
Reallocation variations Increase of CS1 usage in DL Retransmission Decrease of average Allocated SPDCH Increased usage of soft pre-emption (P417 counter)
The end user and new features tests are very important to show the non-regression and improvements of B9
=> you can ask PCS some example of test sheets done on other networks => thank you to provide to PCS the feedbacks on the tests you will do
RNE Resources need to be reinforced in order to be able to perform the field tests, to analyse the results, to analyse the QOS variations, prepare and present them to the customer
ANNEXES
June 2006
IOT status with Alcatel BSS B9 (1/4)

Page 70
Gb interface Alcatel BSS B9 Ericsson SGSN R5.5

Customer : Orange No issue
Gb interface Alcatel BSS B9 Ericsson SGSN R6

Gb interface BSS B9 Nortel SGSN GPRS06

Customer : Claro Orange with B9MR0 T-Mobile with B9 MR2 No issue
Gb interface BSS B9 Nortel SGSN SG5 (GPRS07)

Customer : Claro No issue
Gb interface BSS B9 Nokia SGSN SG5

Customer : Orange NL No issue

Page 71
A interface BSS B9 Ericsson MSC R11

Customer : Orange/Claro No issue on tests performed. All tests not performed due to E1 issues, a RA has been written
A interface BSS B9 MR2 MSC Siemens CS3.0

Customer : T-Mobile No issue

Page 72
3G2G UTRAN Nokia RAN04 BSS B9

Customer : Orange Joint statement, if agreed by Nokia
3G2G UTRAN Nortel UA4.1 BSS B9


Page 73
Other tests made on site at customers A ZTE MSC BSS B9

Customer : Paktel OK (waiting for confirmation from the RSC)
Gb ZTE SGSN BSS B9

Customer : Paktel OK (waiting for confirmation from the RSC)
Alerters definition Sleeping GPRS cells

Page 74
Sleeping GPRS cells alerter raised when

(the number of UL TBF estab success = 0) AND (the number of UL TBF requests > X) AND (the number of DL TBF estab requests =0)
QoS alerter Scope: ENDTIME>@DAY, "9:00" && ENDTIME<=@DAY, "23:00" Critical Predicate: (P30a + P30b + P30c==0) && (P62a+P62b+P62c-P438c > X) && (P91a+P91b+P91c+P91d+P91e+P91f==0 ) Major Predicate: Warning Predicate: Clearance Predicate: (P30a + P30b + P30c>0) || (P91a+P91b+P91c+P91d+P91e+P91f >0 ) Table: GPRS: CELL Stability (mins): 60 X : this value can be adapted. The recommended value is 20 When the alerter is raised, it is recommended to check the QOS status of the cell with RNO
Alerters definition UL Degraded GPRS cells

Page 75
Unefficiency UL TBF establishment alerter raised when

[ (The number of UL TBF requests >50) AND (The UL TBF success rate < 20%) ]
Definition Warning Predicate: ((P62A+P62B+P62C) > 50) && ((P30A+P30B+P30C) / (P62A+P62B+P62C)) < 0.2)) Clearance Predicate: ((P30A+P30B+P30C) / (P62A+P62B+P62C)) > 0.5)) Table: GPRS: CELL Stability (mins): 120 (restriction in B9 , the value 60 will be considered)
Alerters definition DL Degraded GPRS cells

Page 76
Unefficiency DL TBF establishment alerter raised when

[(The number of DL TBF requests >50) AND (The DL TBF success rate < 20%)]
Definition Warning Predicate: ((P91A+P91B+P91C+P91D+P91E+P91F)>50) && ((P90A+P90B+P90C+P90D+P90E+P90F) / (P91A+P91B+P91C+P91d+P91E+P91F)) < 0.2) Clearance Predicate: ((P90A+P90A+P90C+P90D+P90E+P90F) / (P91A+P91B+P91C+P91D+P91E+P91F) > 0.5) Table: GPRS: CELL Stability (mins): 120 (restriction in B9, the value 60 will be considered)
B9 features tested in Acceptance AND on Field (1/2)

Page 77
Telecom features
Support of Incremental Redundancy in uplink Network Assisted Cell Change (NACC) Packet (P)SI Status A-bis dynamic allocation Statistical GCH multiplexing Extended Uplink TBF Mode Autonomous packet resource allocation (implicit) Improvements to Ater resource management Enhanced E-GSM band handling RMS Improvement Counter improvement for Release B9: New GPRS counters Counters to improve TBF drops computation BSC Alarm flow reduction (implicit) Improved 2G to 3G cell reselection SI2quater scheduling

Page 78
O&M Improvements
Synchronization of PRC with SC modifications Wait Traffic Clear period at PRC activation Detailed logs of PRC activation (implicit) Call origin in "Usage State On Demand (implicit) OMC-R view manager (implicit) Refinement of X.25 alarms (discrimination between network and applicative alarms) & X25 alarm reduction Alarm acknowledgement propagation between OMC and NMC (implicit) FR A20/187787- FR A20/187788 - FR A20/187789 corrected QD#12 V490 Introduction(for NPA) T2 granted from Orange Functional Access Domain editor Command Mode enhancements (more commands) Supervision of process, memory, disk (MFS) Visibility of GPRS problems USOD : more telecom info on GSM + GPRS TS TRE/TCU mapping improvement (implicit) TRX/RSL mapping improvement (implicit) Automatic O&M procedures Security improvements for IP Network Elements (MFS) FR A45/180222 & 180224 & 180225 & 180309 to be corrected in B10

Page 79
O&M Improvements (cont)

OMC security: Missing /usr and /var part Security improvements for O&M systems (LDAP, ) Desktop introduction in BSSUSM Customer Documentation about HMI changes X-Large capacity to 6000 cells with new hardware MFS alarm flow reduction Alerters Improvements (TMO) Cell Post-it Spreadsheet facilities Column and row sorting in spreadsheet Spreadsheet snapshot Abort Quick diag operation (implicit) Use relative dates in Cell zone (implicit) RNO support of MNC and MCC as filters Laser topology reports Remote inventory database in Laser Back up time extended up to 120 days Access via HTML
RNO/NPA Improvement
LASER
HW configuration tested during FOs & early adopters

Page 80
BSC
G2 Type 2 to 6
OMC
Small new HW (v880) Large old HW (E450) Large old HW (E4500) X large new HW (v880)
BTS
TRE G3 (including 2nd Abis) TRA G4 (including 2nd Abis) M4M G2 BTS
RNO
Large and X-large
TC
TC G2 TC G2.5 (Compact, with MT120)
NPA
Large and X-large
MFS
AS800
Laser
DS10 RC23 & RC40
B9 QOS
Page 81
PS - Annexes
Annexes
Page 82
Annex1 : Reallocation Variations Annex2 : increase of CS1 usage Annex3 : Allocated SPDCH Annex4 : Speech Codec Variation Annex5 : How to decrease CS congestion in B9 network Annex6 : Alerters Annex7 : FR content Annex8 : B9MR1Ed4QD10 BSS Correction and restriction list Annex9 :Decrease of TBF release due to NC0 reselection
Annex1: Reallocation Variations

Page 83
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)
Annex1: Increase of T1 requests

Page 84
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. Presented to Orange France
Annex1: Decrease of UL and DL T4 requests

Page 85
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).
Presented to Orange France
Annex1: Decrease of UL and DL T4 success rate, due to failures during the prep phase
Page 86
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.
Annex1:Increase of DL T2 requests, Decrease of UL T2 requests, High increase of UL and DL T2 success rate (1/4)
Page 87
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 (CR A20/160643V2).
Annex1: Increase of DL T2 requests, Decrease of UL T2 requests, High increase of UL and DL T2 success rate (2/4)
Page 88
Example illustrating some differences between B8 and B9 for T2 reallocation:

In B8, if the existing TBF is optimal in number of RTSs in the direction of the bias then, if it is possible, the concurrent TBF will be established in front of it. There is no T2 reallocation of the existing TBF in this case because the T3-reallocation criteria saying that the number of RTSs in the direction of the bias shall be increased cannot be fulfilled.
In B9, in the same situation, it will be checked if a significant throughput gain can be offered to the MS in the direction of the bias. The gain targeted is the same as for a T3 reallocation: MIN_THROUGHPUT_GAIN. If so, a T2 TBF reallocation will be triggered (contrary to B8).
If not, if it is possible, the concurrent TBF will be established in front of the existing one (as in B8). Presented to Orange France
Another example is provided in the next slides

Annex1: Enhanced transmission resource management in RRM (3/4) Example 1 B8 behaviour

Page 89
Max_SPDCH_Dyn = 8, but only 1 PDCH (PDCH 0) is allocated to the MFS. UL TBF establishment for MSa, EGPRS, (4+1)
0 1 2 3 4 5 6 7
If DL LLC PDU arrives before new PDCHs are established: DL establishment on PDCH 0, MSa becomes candidate to T3 reallocation.
0
U MSa L D L
U MSa L D MSa L
If new PDCHs are established before arrival of DL LLC PDU (PDCH anticipation): PDCHs 1-3 are established, T2 reallocation, UL establishment on PDCH 2 and DL establishment on PDCH 0-3.
0 1 2 3 4 5 6 7
When the new PDCHs are established, MSa is allocated on PDCH 0-3 after T3 reallocation.
0 1 2 MSa 3 4 5 6 7
U L
U L
MSa
D MSa MSa MSa MSa L
D MSa MSa MSa MSa L

Annex1: Enhanced transmission resource management in RRM (4/4) Example 1 B9 behaviour

Page 90
Max_SPDCH_Limit = 8, With Autonomous Packet Resource allocation feature, PDCH0-7 are allocated to the MFS, but the TRX is not established (no M-EGCH link). UL establishment for MSa, EGPRS, (4+1): 1 GCH is established (N_GCH_For_Estab), UL TBF for MSa is established on PDCH 2, 4 GCHs are established (to reach Target_Nb_GCH=5). 0 1 2 3 4 5 6 7
U L D L
MSa
When DL LLC PDU arrives: PDCH 0-3 is a possible candidate, DL TBF for MSa is established on PDCH 0-3, Target_Nb_GCH = 18, If it is possible, 13 new GCHs are established to reach Target_Nb_GCH.
0 1 2 MSa 3 4 5 6 7
U L
D MSa MSa MSa MSa L
Contrary to B8, there is no T2 reallocation in this case in B9

Annex1: High decrease of UL and DL T3 success rate due to failures during the preparation phase, Variations of the number of T3 requests (1/2)
Page 91
In B9, all the TBFs can be candidate for T3 reallocation, even if they have already an optimal number of 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. Variations of the number of T3 requests (1):
In B8, in a given cell, up to 5 T3 TBF requests are systematically played in each direction every second (N_MAX_PERIODIC_REALLOC = 5). In B9, in a given cell, up to 20 T3 TBF requests are played in each direction every second (N_MAX_PERIODIC_REALLOC_T3 = 20), but the process is stopped as soon as the first T3 TBF request succeeds.
This can explain variations of the number of T3 requests between B8 and B9.
Annex1: High decrease of UL and DL T3 success rate due to failures during the preparation phase, Variations of the number of T3 requests (2/2)
Page 92
Variations of the number of T3 requests (2):

Examples: - 5 (successful or unsuccessful) T3 TBF requests per second in B8 versus 1 successful T3 TBF request per second in B9. - 5 (successful or unsuccessful) T3 TBF requests per second in B8 versus 20 unsuccessful T3 TBF requests per second in B9. Whether there will be fewer or more T3 requests in B9 than in B8 depends on many factors (PS traffic load in the cell, PS traffic burstiness, number of RTSs available for PS traffic in the cell, ...). In B9, TBFs are more likely to have an optimal allocation than in B8 (because fewer constraints on Abis/Ater in B9 due to dynamic Abis Allocation and M-EGCH Statistical-Multiplexing). Both in B8 and B9, the number of T3 TBF requests is only incremented in case of sub-optimal TBF allocation (B8: sub-optimal in number of RTSs, B9: sub-optimal according to throughput ratio). Presented to Orange France But in B9, this number of sub-optimal TBFs is lower.
This can explain a decrease of the number of T3 requests.

Annexes
Page 93
Annex2 : Increased CS1 usage rate in B9 (1/4)

Page 94
Increase of CS1 usage in DL

6000000 5000000 4000000 3000000 2000000 1000000 0
02/21/2006 02/22/2006 02/23/2006 02/24/2006 02/25/2006 02/26/2006 02/27/2006 02/28/2006 03/01/2006 03/02/2006 03/03/2006 03/04/2006 03/05/2006 03/06/2006 03/07/2006 03/08/2006 03/09/2006 03/10/2006 03/11/2006 03/12/2006 03/13/2006
B8
B9
CS4 usef
CS3 usef
CS2 usef
CS1 usef
Explained by two reasons:

DL TBF drops delayed in bad radio conditions, due to RLC/MAC parameter modifications.
The defence mechanism linked to TBF_CS_DL is more often triggered and it can explain why the CS1 usage rate is increased in B9 release.
Use of Max_CS=CS1 in DL, when Established_Nb_GCH=1


Page 95
A) DL TBF drops delayed in bad radio conditions, due to RLC/MAC parameter modifications:
RLC/MAC parameter modifications:
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
These parameters have been modified due to :

Introduction of statistical multiplexing and dynamic Abis features
Radio link failure detection at RLC layer must take into account possible lack of transmission resource, thus reducing the radio throughput
Introduction of the GPRS QoS feature (MAC scheduling modifications)


Page 96
B) Number of established GCH in the M-EGCH link equal to 1

The maximum allowed (M)CS of a best-effort TBF (TBF_Max_allowed_(M)CS) is computed according to: - the GPRS capability of the TRX (HW capability and EN_EGPRS value) - the direction of the TBF (DL or UL) - the Max_GPRS_(M)CS parameter value. - the number of established GCHs in the M-EGCH link
Number of established GCHs in the M-EGCH link
GPRS
Max allowed (M)CS of the TBF according to the number of GCHs of the M-EGCH link UL TBF CS2 CS4 MCS2 MCS5 MCS6 MCS7 MCS9 DL TBF CS1* CS4 MCS1* MCS5 MCS6 MCS7 MCS9
1 >= 2 1 2 3 4 >= 5
(*) The maximum allowed (M)CS of an (E)GPRS DL TBF established on a TRX having an M-EGCH link containing 1 GCH is set to (M)CS1 (and not (M)CS2). Indeed, it shall be guaranteed that the MFS-BTS signalling messages will always be possible to be sent in the M-EGCH link in DL
EGPRS

Page 97
B) Number of established GCH in the M-EGCH link equal to 1 This situation can happen in the following cases:
Heavy GCH congestion, due to under-dimensioning on terrestrial interfaces (Abis and/or Ater) Short transitory phase, during the M-EGCH link establishment phase Target_Nb_GCH computed to 1, in case only one PDCH is active on the TRX, and Max_(E)GPRS=(M)CS2.
This happens mainly for GMM/SM traffic (for which only one RTS is used). In that specific case, the DL blocks are sent in CS1 instead of CS2, which is deemed acceptable as throughput optimisation is not required. It can even be considered as an advantage, as CS1 is more robust than CS2.
Annexes
Page 98
Annex3: Allocated SPDCH (1/10) Autonomous Packet Resource Allocation (RAE4) algorithm
Page 99
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
Annex3: Allocated SPDCH (2/10) Autonomous Packet Resource Allocation (RAE4) algorithm
Page 100
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
Annex3: Allocated SPDCH (3/10) Impact of RAE4 on allocated SPDCH counters

Page 101
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.
Annex3: Allocated SPDCH (4/10) Impact of RAE4 on GPRS_MAX_PDCH_Dyn_avg (KPI)

Page 102
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)
Annex3: Allocated SPDCH (5/10) 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 103
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
Annex3: Allocated SPDCH (6/10) Examples of MAX_SPDCH_LIMIT Calculation (1/4)

Page 104
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
Example : Parameters 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)

Page 105
Case 1: Medium CS & No PS traffic

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

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

Page 106
Case 3: Medium CS & PS traffic

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

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

Page 107
Case 5: High CS & Medium PS traffic

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

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
Annex3: Allocated SPDCH (10/10) Conclusion

Page 108
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)
Annexes
Page 109
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 110
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.
Annexes
Page 111
Annex 5 : How to decrease CS congestion in B9 network

Page 112
In case of congested networks, an increase of CS congestion can be observed in B9

Linked to new radio resource allocation in B9 Some parameter tuning can decrease the CS congestion HIGH_TRAFFIC_LOAD_GPRS is the main parameter to be decreased: Load threshold used to determine a certain margin of radio timeslots reserved for CS traffic between two sending of the BSCGP RR Allocation Indication messages. The threshold is expressed in percentage of the radio timeslots available in the cell 1st step: apply the BTP recommended default value:
70 for a cell with 1, 2 or 3 TRX 80 for a cell with more than 3 TRX
=> Check the GPRS QOS which can be degraded by the modification 2nd step: In case of still CS degradation compare to B8:
Decrease again the parameter HIGH_TRAFFIC_LOAD_GPRS Check that MAX_PDCH_HIGH_LOAD is different from 0 (To minimize the impact in GPRS traffic.)
3rd step: Check activation of traffic management features (HR, Directed Retry, traffic HO, fast traffic HO, dyn SDCCH)
Annexes
Page 113
Annex1 : Reallocation Variations Annex2 : increase of CS1 usage Annex3 : Allocated SPDCH Annex4 : Speech Codec Variation Annex5 : How to decrease CS congestion in B9 network Annex6 : Alerters Annex7 : FR content Annex8 :Decrease of TBF release due to NC0 reselection
Annex6: (1/3) Alerters definition Sleeping GPRS cells

Page 114
Sleeping GPRS cells alerter raised when

(the number of UL TBF estab success = 0) AND (the number of UL TBF requests > X) AND (the number of DL TBF estab requests =0)
QoS alerter Scope: ENDTIME>@DAY, "9:00" && ENDTIME<=@DAY, "23:00" Critical Predicate: (P30a + P30b + P30c==0) && (P62a+P62b+P62c-P438c > X) && (P91a+P91b+P91c+P91d+P91e+P91f==0 ) Major Predicate: Warning Predicate: Clearance Predicate: (P30a + P30b + P30c>0) || (P91a+P91b+P91c+P91d+P91e+P91f >0 ) Table: GPRS: CELL Stability (mins): 60 X : this value can be adapted. The recommended value is 20 When the alerter is raised, it is recommended to check the QOS status of the cell with RNO
Annex6: (2/3) Alerters definition UL Degraded GPRS cells

Page 115
Unefficiency UL TBF establishment alerter raised when

[ (The number of UL TBF requests >50) AND (The UL TBF success rate < 20%) ]
Definition Warning Predicate: ((P62A+P62B+P62C) > 50) && ((P30A+P30B+P30C) / (P62A+P62B+P62C)) < 0.2)) Clearance Predicate: ((P30A+P30B+P30C) / (P62A+P62B+P62C)) > 0.5)) Table: GPRS: CELL Stability (mins): 120 (restriction in B9 , the value 60 will be considered)
Annex6: (3/3) Alerters definition DL Degraded GPRS cells

Page 116
Unefficiency DL TBF establishment alerter raised when

[(The number of DL TBF requests >50) AND (The DL TBF success rate < 20%)]
Definition Warning Predicate: ((P91A+P91B+P91C+P91D+P91E+P91F)>50) && ((P90A+P90B+P90C+P90D+P90E+P90F) / (P91A+P91B+P91C+P91d+P91E+P91F)) < 0.2) Clearance Predicate: ((P90A+P90A+P90C+P90D+P90E+P90F) / (P91A+P91B+P91C+P91D+P91E+P91F) > 0.5) Table: GPRS: CELL Stability (mins): 120 (restriction in B9, the value 60 will be considered)
Annexes
Page 117
Annex7: QOS Variation After Migration=>FR

Page 118
The following information is needed in a QOS FR

Seen by the customer ? Value of the degradation compare to B8. Is it common to all cells (check alc_multi_xxx RNO report) ? If not, What is the rate of cells impacted with the level of degradation. - - For the impacted cells give some feature/configuration information (if you can find it) (CS3/4 activated ? edge activated ? BTS type... all other information which could help the investigation...) Is it common to all BSC with the same level of degradation ? If not what could be some differences between each BSC (parameter tuning, feature activated) (this point is to help TD by some track if you can find any) have you seen a workaround ? (for example do you notice that a GPU reset has an impact on the QOS degradation...) All these information can then be correlated with other networks and could help the analysis
Annexes
Page 119
Annex 8 : Decreased of number of reselections in PTM : Impact of B9 on P396b and P434c

Page 120
P396b : Number of UL TBF releases requested by RRM to RLC upon receipt of the Flush message. P434c : Number of UL TBF releases due to NC0 cell reselections In B9, the algorithm in RLC to detect abnormal UL TBF release is less strict than in B8, i.e. more time is given to conclude that the MS is actually lost. Therefore, in case of cell reselection, it is more likely that the FLUSH message will be received before the TBF is released
P396b higher than in B8, P434c lower than in B8
No impact on end-user :
No influence on the TBF establishment in the new cell In B9 as in B8, trigger to reroute remaining LLC-PDUs (DL case) is the Flush message
Page 121
aww-evolium.cit.alcatel.fr

B9 Status at MR1 Ed4 QD11

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

B9 Status at MR1 Ed4 QD11

Hochgeladen von

Copyright:

Verfügbare Formate

Release B9 B9 MR1 ed4 + QD#11 Status

All rights reserved 2005, Evolium

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

Main conditions to run General Availability Decision review are reached

Rollout ongoing in Orange France 315 BSSs on a total of 321 are in B9

Alcatel management decision taken to run General Availability Decision Review

Delivery Content BSSSAW01B Ed04_QD11

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

BSS Software List - 3BK 13016 0991 TQZZA

Restriction List - 3BK 13016 0993 TQZZA

Operator Hints - 3BK 13016 0994 TQZZA

Migration Software and Upgrade RL and OH - 3BK 13016 0995 TQZZA

Counters and Indicators Status - 3BK 13091 0142 TQZZA

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

QOS Circuit B9MR1Ed4QD11 Radio Link Establishment - Results

SDCCH Congestion Rate

SDCCH Assignment Failure B8

SFR (Evolium) SFR (G2) VIP (QD8)(PreP) VIP (QD8)(Nino)

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

QOS Circuit B9MR1Ed4QD11 Call Establishment - Results

SDCCH Drop Rate

RTCH Assign Unsuccess rate B8 B9

Call Setup Success Rate B8

0.33% 0.26% 0.47% 0.27% 0.39% 0.41% 0.7%

0.11% 0.2% 0.27% 0.51% 0.46% 0.23% 0.51%

Stable / 99.31% Improved 99.54% 99.31%

99.5% 99.50% 99.22% 99.17% 99.02% 99.37% 98.72%

SFR (Evolium) SFR (G2) VIP (QD8)(PreP) VIP(QD8)(Nino)

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

QOS Circuit B9MR1Ed4QD11 Radio Congestion - Results

RTCH Congestion Rate

Incoming Inter BSC Congestion Rate B8 B9

Incoming Intra BSC Congestion Rate B8 B9

0.13% 0% 0.01% 0.05% 0.06% 0.17% 0.89%

0.99% 0.24% 0.12% 1.89% 1.51% 5.54% 11.11%

1.31% 0.23% 0.41% 1.95% 2.46% 0.68% 8.83%

SFR (Evolium) SFR (G2) VIP (QD8)(PreP) VIP (QD8)(Nino)

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium

QOS Circuit- B9MR1Ed4QD11 Call Drop rate Results

Call Drop Rate

Call Drop Rate - other networks

Orange France (LeMans) (evolium)

1.01% 0.89% 0.70% 0.97% 0.77% 1.21% 0.63% 1.35%

1.03% unreliable 0.84% 1.04% 1.01% 1.40% 0.49% 1.3%

B9 MR1 ed4+QD#11 status 27/06/06

QOS Circuit- B9MR1Ed4QD11 Call Drop Rate

B8-> B9QD11 Migration

Orange Romania (B8-B9QD11)

Orange France Ouest (B8-B9QD11)

120000 100000 80000 60000 40000 20000 0

B9 MR1 ed4+QD#11 status 27/06/06

All rights reserved 2005, Evolium