B9 EA Followup w613

7/28/2019 B9 EA Followup w613

1/31

All rights reserved 2005, Evolium

Release B9 MR1Early Adopters follow-up

NPI/28.03.2006


2/31

B9 MR1 status from NPI 28.03.2006 All rights reserved 2005, Evolium

Page 2

Agenda

B9 MR1 SW B9 QoS Feedback

B9 MR1 Introduction - First-off

B9 MR1 Introduction Early adopters

Appendix


3/31


Page 3

Software Migration RL 3BK 13016 0988 TQZZA Edition 01 available for QD#9 New update taking into account issues encountered during upgrade & migration in MR1 ed4

by FO and early adopters

BSS Restriction List 3BK 13016 0961 TQZZA Edition 03 available

Operator Hints 3BK 13016 0962 TQZZA Edition 02 available

Counters & Indicators Status 3BK 13091 0138 TQZZA Edition 01 available

Delivery B9 MR1 ed4 + QD#9done Wednesday 15th March

Includes only a new BSC SW to solve

3BKA20FBR180232 - High RTCH congestion rate in concentric cell

3BKA20FBR180387 - Routine test executed at wrong time

3BKA20FBR181691 - Handover to target cell with AMR_HR and MS originating calls in AMR_HR

generates mute calls

Installed on Claro pilot Friday 17th of March: One issue on cell shared cell concentric cellsexplanation available: problem understood correction planned in B9 MR1 ed5

Networks having concentric cells on their network are impacted by this delivery:

ERA (very few) , SFR , Jersey , Orange France , TMO (very few) , Saudi Arabia(concentric cells will be set in near future)

B9 MR1 ed4 SW


4/31


Page 4

Delivery B9 MR1 ed4 + QD#10available

Includes a new GPU SW to solve mainly problems on G2 BTS with DRFU: 3BKA20FBR171550 - Bad DL establishment rate with DATA ERR BE DRFU failed allocation to TRX 3BKA20FBR182146 - requests not purged in case of trans establishment failure (SFR - DRFU) 3BKA20FBR182147 - Pdchs remains in state deestablishing even after complete deestablishment (SFR) 3BKA20FBR180509 - Ahe abnormal rate of GCH_REL_IND on G2 BTS 3BKA20FBR181831 - sleeping cell on DRFU BTS with GCH blocked

Includes also the following Orange France issues:

3BKA20FBR177547 - Increase of TBF DL and UL release cause preemption radio (P146) - AVP

9FR0046

3BKA20FBR178522 - a GPU2-AC is not able to switch from one synchro bus to another 3BKA20FBR178520 - a GPU2-AC as master always sends signal on its bus

Includes also an OMC-R add-on:

3BKA20FBR182106 - no FADs available after login (case Corba crash)

Authorization not yet given to install this patch on top of QD#8 or QD#9

Already installed on SFR pilot since 20th of March but not sufficient to solve G2 BTS issues

Networks having G2 BTS on their network are impacted by this delivery:

SFR , Jersey , Orange France , TMO

As it includes P146 counter correction, all networks migrating from now have to takethis QD#10

B9 MR1 ed4 SW


5/31


Page 5

Concentration Issues (FR A20/175960, A32/178363 , A32/178392, A32/178384)

Impact: several workarounds to be applied during the concentration operation

Annoying for TMO network if concentration performed

First concentration operation in B9 will be done with the support of TD

Request of all CCL filled in during upgrade/migration from FO and early adopters.

Received from Claro, SFR, T-Mobile

Missing Jersey, ERA

Networks that will migrate soon and will have to send CCL: True Move, Voxtel,

Mobily

B9 MR1 ed4 SW


6/31


Page 6

Agenda




Appendix


7/31


Page 7

Introduction

Aim of these slides is to show that there are

Difficulties in B9 to ensure KPIs stability

But Investigations on going and some corrections significantly improve the QOS

results

And

Possible need to prepare customer to the need of parameter tuning due tonew B9 algorithms


8/31


Page 8

GSM QOS summary

Positive feedacks No major degradations compare to B8

B9 is stable and similar to B8

Remaining Main Issue

In most networks, risk of increase of CS congestion due to new B9 algorithm,less reactive than in B8

=> Compromise has to be found by parameter tuning

Other possible issue warning flag

SDCCH assign failure rate increase and SDCCH drop radio rate increase are

under investigation

Solved issue

Congestion in concentric cells => solved in QD9


9/31


Page 9

GPRS TBF Establishment

GPRS TBF establishment Success Rate

DL : 0pts < decrease < depends on the network

Main Causes

Radio failures (main cause: could be linked to MS problems)

BSS failures (not all BSCs) (an improvement has been seen in QD8)

High improvement compare to B9 first migrations but still degradation compare to B8.

UL : Degradation mainly due to sleeping cells:

Main Causes

Radio failures (usually due to sleeping cells) (most degradation in case fast initialGPRS access feature is activated) (Solution found)

BSS failures (usually due to sleeping cells) (Solved in QD8) Temporarly radio congestion can be observed. It can be due to

CS favoured by parameter tuning and the network is CS loaded.

sleeping cells : this is under observation


10/31


Page 10

GPRS TBF release (1/4)

GPRS Acceptable release causes

DL :

Decrease of release due to NC0 reselection (all BSCs)

Increase day after day of drop due to radio preemption until GPU reset (allBSCs) => solved in QD10 (to be confirmed with more observation data)

UL :

High Decrease of release due to suspend procedure (all BSCs)

Increase day after day of drop due to radio preemption until GPU reset (all

BSCs) => solved in QD10 (to be confirmed with more observation data)


11/31


Page 11

GPRS - TBF Release (2/4)Acceptable TBF release causes evolution

DL TBF Acceptable Release causes

0

2000

4000

6000

8000

10000

12000

02/27/200

6

02/28/200

6

03/01/200

6

03/02/200

6

03/03/200

6

03/0

4/200

6

03/05/200

6

03/06/200

6

03/07/200

6

03/08/200

6

03/09/200

6

03/10/200

6

03/1

1/200

6

03/12/200

6

03/13/200

6

03/1

4/200

6

03/15/200

6

03/16/200

6

03/17/200

6

03/18/200

6

03/19/200

6

03/20/200

6

03/21/200

6

03/22/200

6

03/23/200

6

00,20,40,60,811,21,41,61,82

NC0 Resel

NC2 Resel

Suspend

Radio Preempt

%Acceptable Rel

UL TBF Acceptable Release causes

0

1000

2000

3000

40005000

6000

7000

8000

02/27/20

06

02/28/20

06

03/01/20

06

03/02/20

06

03/03/20

06

03/0

4/20

06

03/05/20

06

03/06/20

06

03/07/20

06

03/08/20

06

03/09/20

06

03/10/20

06

03/1

1/20

06

03/12/20

06

03/13/20

06

03/1

4/20

06

03/15/20

06

03/16/20

06

03/17/20

06

03/18/20

06

03/19/20

06

03/20/20

06

03/21/20

06

03/22/20

06

03/23/20

06

0

0,1

0,2

0,30,4

0,5

0,6

NC0 Resel

NC2 Resel

Suspend

Radio Preempt

%Acceptable Rel

Solved in QD10 !!

Still not explained


12/31


Page 12

GPRS - TBF Release (3/4)Drop rate

GPRS Drop rate

DL : 0.5 < degradation < depends on the network

Main Causes

Blocking drop (quite all BSCs)

Reallocation drop (Not all BSCs, not all networks)

BSS Drop (not all BSCs can be minor or high)

=> a decrease has been observed since QD8 on some BSCs

=> a decrease has also been observed on some BSCs in QD10 and has tobe confirmed with more observation data

Radio Drop rate seems stable

UL : No clear trend


13/31


Page 13

-Drop TBF causes evolution 2 differentcases

DL TBF Drop Causes

0

2000

4000

6000

8000

10000

12000

02/27/20

06

02/28/20

06

03/01/20

06

03/02/20

06

03/03/20

06

03/04/20

06

03/05/20

06

03/06/20

06

03/07/2006

03/08/20

06

03/09/20

06

03/10/20

06

03/1

1/20

06

03/12/20

06

03/13/20

06

03/1

4/20

06

03/15/20

06

03/16/20

06

03/17/20

06

03/18/20

06

03/19/20

06

03/20/20

06

03/2

1/20

06

03/22/20

06

03/23/20

06

0

1

2

3

4

5

6BSS pb

NC2 resel drop

Gb drop

Realloc Drop

Blocking drop

Stagnat drop

Radio Drop

%Real rad drop

% Drop

DL TBF Drop Causes

010000

20000

30000

40000

50000

60000

70000

02/2

1/20

06

02/23/20

06

02/25/20

06

02/27/20

06

03/0

1/20

06

03/03/20

06

03/05/20

06

03/07/20

06

03/09/20

06

03/1

1/20

06

03/13/20

06

03/15/20

06

03/17/20

06

03/19/20

06

03/2

1/20

06

03/23/20

06

0

5

10

15

20

25

30BSS pb

NC2 resel drop

Gb drop

Realloc Drop

Blocking drop

Stagnat drop

Radio Drop

%Real rad drop

% Drop

Probably due to G2

BTS on the BSCs

Improvement of DropCause BSS fail

since QD8 still

to be confirmed

B8

B8 B9

B9 B9-QD8


14/31


Page 14

Conclusion QOS Variation => FR

The following information is needed in a QOS FR Value of the degradation compare to B8.

Is it common to all cells ?

If not, What is the rate of cells impacted with the level of degradation. - - For theimpacted cells give some feature information (if you can find it) (CS3/4 activated ?edge activated ? ... all other information it is interesting according to you...)

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 animpact on the QOS degradation...)

All these information can then be correlated with other networks and could help the

analysis=> Several networks are now in B9 and we need these details informationsto solve or explain the QOS variations. We can NOT perform these detailedanalysis on all the B9 networks.


15/31


Page 15

Agenda



Vimpelcom

Orange France


Appendix

B9 MR1 I t d ti Fi t OFF


16/31


Page 16

B9 MR1 Introduction First OFFcustomers

Vimpelcom Lab in B9 MR1 ed4 + QD#8

Pilot in B9 MR1 ed4 + QD#8

Rollout in NiNo finished (21 BSC) in B9 MR1 ed4 + QD#8

Current issues:

FR A20/172954: RNO-NPA Daemon stops autonomously after 2 days of correct running Impact: For NPA embedded configuration, after 2 days of correct running, no request

from RNO is accepted-A process stop/start has to be performed from OMC

A new daemon re-compiled with the option REUSE LOCAL ADDRESS will be

delivered to VIP this week

FR A20/180641: 4 Individual cells GPRS sleeping (B9 MR1 Ed04) Solved by re-init

GPRS at cell level New traces needed

5 sleeping cells per day observed on one BSC Same problem seen in T-Mobile Pb

followed in the context of TMO

Green light for roll-out given Friday 10th of March

Next Step: Upgrade lab in B9 MR1 ed5

lab pre-pilot full-pilot rollout31 January 4 February 13 March 13 March

B9 MR1 I t d ti Fi t OFF


17/31


Page 17

B9 MR1 Introduction First OFFcustomers

Orange France

Lab platforms of Cevennes in B9 MR1 ed4 + QD#8 & QD#9

Pilot in Villejuif in B9 MR1 Ed4 + QD#8 & QD#9 since Friday 17th of March

Pilot in Donges to be upgraded in QD#9 or QD#10 soon

Network in B8 MR5 ed2 + MFS ed3

Go for rollout (T6): New delay due to QD#10 announcement : 21st of April QoS results : after QD#9 installation is observed:

AVP FR0130: UL TBF Establishment failure due to Radio on 3 cells (1 cell per BSC)

AVP FR0128: UL TBF Establishment failure due to BSS (WA is reinit GPRS for both issues)

Main issues: FR A45/175530: Increase of delay response on NPA and RNO (OFR - FR0024 )

Under investigation by METRICA team Metrica delivery end of March for TD

FR A45/177876: Metrica database corrupted when "init 6" command is done: modification needed in init 6 AVP9FR0118

methods where NPA stop is requested are updated including the way to stop all Metrica processes beforelaunching init 6

script corrected in MR1 ed5

FR A20/183578: ORANGE NPA V490 PILOT - Problem during CD1 installation

For V490 NPA Large & Xlarge, partition /db was not created

WA: create manually the partition at the end of CD1 installation

lab pilot Donges pilot Villejuif rollout31 january 13 February 27 February end March


18/31


Page 18

Agenda



B9 MR1 Introduction Early adopters T-Mobile

Jersey telecom ERA Claro SFR Mobily Paktel Voxtel

True Move (ex. TAO)Appendix


19/31


Page 19

B9 MR1 Introduction - Early adopters (1/7)

T-Mobile Lab in B9 MR1 ed4+QD#8

Network in B8 MR5 ed4

Interfaces: T. Sennhenn (technical) / A. Ploetz (commercial)

Pilot in Stuttgart area fully in MR1 ed4 + QD#8 (3 BSC)

QoS feedback:

no degradation for GSM

FR A45/182645: Degradation of the indicator UL_TBF_Success_Rate for GPRS

Main issues:

FR A20/182241: GPRS sleeping cells in T-Mobile OMC pilot

Same as VIP sleeping cells

Under analysis new traces requested but no re-occurrence this week end

FR A45/177492: no FADs available after login - correction available in QD#10

Due to G2 BTS & QoS issues, Go for rollout has been postponed probably to Q3 2006

lab Bonn lab Nuremberg pilot rollout30 january 30 january 27 February Unknown


20/31


Page 20


Jersey Telecom

Pilot in B9 MR1 Ed2 + QD#6

Acceptance of E-GSM feature done:

EGSM functional tests (GATP tests + 3G/2G inter-working on air between one mini indoor NodeB and one live

EGSM sector+ SMSCB on G1 band frequency + Jersey target multi-band EGSM-DCS configuration)

BSS O&M Non-Regression (basic operational tests)

CS3/CS4 tests

Generalization of the E-GSM feature 2 weeks after acceptance: EGSM is now configured in Guernsey on a couple of cells

Interfaces: Y. Lacheteau (technical) / P. Lawrance (commercial)

Upgrade in B9 MR1 ed4 + QD#10 planned w619/W620

Current Issues under investigation:

FR A20/179371 & FR A20/180509 : cases of GPRS sleeping cells, reinit GPRS with or w/oconsecutive GPU reset.

High rate of GCH release, mainly on all G2 BTSs and in 2 cells with Evolium BTSs

Corrected QD#10

2 alerters installed

FR A20/178555: GSM/GPRS outage on some cell configurations after migration to B9 withBS_AG_BLK-RES to 1

Jersey issue on 12 cells with non default parameters values Palliative by setting default values successfully applied

Corrected B9 MR1 ed5

FR A20/181693 : Sporadic high RTCH congestion on some cells

investigation in TD on-going.

pilot rollout (4 BSC) upgrade MR1 ed4

11 January ended 8th May


21/31


Page 21


ERA - Poland

Network in B9 MR1 ed2 + QD#7

Upgrade of the network in B9 MR1 Ed4 + QD#9 (or QD#10?) started:

OMC upgrade finished

MFS upgrade 28th of March

1 BSC upgrade 29th

of March Remaining MFS & BSC from 4th of April until 13th of April

Interfaces: W. Mizera (technical) / J. Danecki (commercial)

Network performance degradation observed:

Permanent congestion on RTCH on non-concentric cells Similar to Jersey issue

Tuning of parameters : HIGH_TRAFFIC_LOAD_GPRS decreased from 80 to 70

Improvement observed.

pilot rollout (17 BSC) upgrade QD#96 February 20 February 27 March


22/31


Page 22


Claro - Brazil Lab in B9 MR1 ed4

Network in B8 MR6 ed3

Interfaces: A. Stoenescu (technical) / H. Chevenement (commercial)

ATL region (6 BSC) upgraded in B9 MR1 ed4 + QD#9

QoS feedback:

FR A45/183011: Increase of BSS failures during the TBF Establishment / TBF Drop due to BSS

problems for BSCES05

Current issue:

FR A94/183089: GPU does not recognize BSC cells on BSCES02

No more GPRS on one BSC because no cell was created in the GPU.

Pb due to cell shared. 6 BTS are impacted. The WA is to delete and re-create the BTS withits configuration

OMC issue A20/176418 Cell shared creation failed for the MFS: No GPRS traffic ispossible on the shared cell, when GPRS is declared on the secondary sector Corrected B9MR1 ed5

WA: Remove Cell Shared then Launch a Reshuffling and Create again Cell Shared

lab pilot ATL rollout (136 BSC)30 january 13 February Unknown


23/31


24/31

B9 MR1 status from NPI 28.03.2006All rights reserved 2005, Evolium

Page 24


Paktel - Pakistan Swap of ZTE Only G1 band

IOT started with B9 MR1 Ed4 : 1rst call passed successfully A interface finished successfully

Gb interface interface delayed due to GPRS configuration issues

Current Issues: FR A91/182814: Backup fail on OMC-R V490

FR A91/182817: Error installing Verity K2 License. Network description:

13 BSCs from ZTE have to be replaced total of 298 BTS to swap

8 Alcatel BSCs are available and will replaced ZTE ones as follows:

1 BSC the 27th of March and 1 week of observation using AnaQoS tool

7 BSC from the 3rd April for 3 weeks

5 Alcatel BSCs will replaced ZTE ones as soon as site will be available

10 BSC more will be introduced later for extension purpose Network will be fully swap the 19th of May

Interfaces: M. KHEDR (technical) / A. VANWELSENAERS (commercial)

Training under consolidation (O&M profile via AU, RNE via PCS, telecom/GPRS profilevia TD immersion)


25/31


Page 25


Voxtel - Moldavia NPA migrated in B9 MR1 ed4 + QD#9

RNO installed in B9 MR1 ed4 + QD#9

OMC migration on-going

MFS sanity check script run: some errors were found

10 BSC to migrate w14?

Authorisation given by Orange Skill Center but alignment to T6 version is mandatoryafterwards

True Move Thailand Pilot on-going in Bangkok with B9 MR1 ed4 + QD#10:

NPA migration on-going

OMC X-Large migration planned w14

The first MFS will be migrated on Friday 7th of April

The first BSC will be migrated on Monday 10th of April, then 1 week of observation

Go for rollout will be given Monday 17th of April

Migration of the 2nd X-large OMC, the 2nd MFS and the 60 remaining BSC

lab pilot rollout (10 BSC)

none none 20th March

lab pilot rollout (61 BSC)

none 27th March 17th April

New


26/31


Page 26

Agenda


B9 MR1 Introduction First Off


Appendixes:

Early adopters management process


27/31


Page 27

Early Adopters Management Process

Go/Nogo to be organised per early adopter before the start of the lab / pilot

Contractual commitments (features, deadlines, training, support, KPI, equipments)

Lab & pilot descriptions (tool chain, OMC, MFS, BSC, BTS, External OMC equipment asNMC, Citrix)

Compliancy with all pre-requisites defined in NPI checklist

Equipments compliant with Engineering rules

Licences available

Test plan availability (features to be tested on which equipment)

IOT checked (core, SGSN, 3G)

Level of RSC training

External support requirement (TAC, PCS, other)

Tools availability at the good level (Protocol analyser, Radio traces SW, Drive tests tools)

Documentation availability (Restriction list, SW migration RL, Operator Hints, rollback

procedure for BSC and MFS, migration procedures which integrate additional checksbefore migration)

Green light from NPI/PLM/TD Project Leader/QAD mandatory before rollout until GADR

pronounced


28/31


Page 28

Early adopters managed by NPI and CTAC

Weekly meetings lead by NPI & CTAC to: Give a feedback on first-off activities, current potential issues

Obtain a feedback on activities from early adopters

To share information between early adopters

In case of technical issues, CTAC is the first interface:

Daily report from early adopters to NPI (Guidot / Maleyrie) and CTAC (Alves / Semedo),

copy TD (Bomy / Acbard), PCS (Garcia / Colin / Fonseca / Sundralingam) & Product LineDeputy Director (Lamouroux) with following information:

a clear title (name of the customer and status green/yellow/red flag)

Short status of the activity

Main issues encountered

Next step

Write a fault report in ARTS database:

1 problem per FR All details included & traces given

U0 Fault reports are followed in a daily meeting by TD at 9h CET

CTAC participates to it

Program can participate in case he is interested in one FR or if some information arerequested by TD



29/31


Page 29

Quick deliveries (QD) process used up to now during acceptance and pilot for first-off customers

Could be used by early adopters to unblock last blocking problems ifmandatory or as a preventive action

Can not be done for a dedicated early adopter because too costly (NREG

tests performed by TD each time) except for a G0

Generic SW release

Specific package per customer is not possible

Consequently Convergence on generic maintenance release mandatory for

roll-out for all customers.



30/31


Page 30

CS congestion in B9 on non-concentric cells

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 tuned:

Load threshold used to determine a certain margin of radio timeslots reserved for CStraffic between two sending of the BSCGP RR Allocation Indication messages. Thethreshold 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.)The second step is under testing in ERA Improvement not clear

Not all relevant features are activated on ERA, which explains there is no realimprovement


31/31


Page 31

aww-evolium.cit.alcatel.fr

B9 EA Followup w613

Documents

Transcript of B9 EA Followup w613