1 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials

Company Confidential

(E)GPRS Capacity Optimization

2 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials

Company Confidential

(1) If AMR and/or HR is used add Dual rate TSL(2) If Dual rate not possible add TRX (need to check the PCU, A-bis and Gb capacity)(3) CS traffic management (change HO parameters, resource management parameters)(4) Increase nbr of dedicated PS timeslots

Yes

Check PS traffic

behavior TBF/TSL >1.2 , (max(tbf_37c, tbf_38c))And

UL / DL multislot allocation blocking – hard (max(tbf_15, tbf_16))

AndDL multislot blocking – soft (blck_33)

Radio problem analysisCS Busy Hour

Configuration check

CMAX=CDEF => Increase CMAX0.75*CMAX < peak_gprs_territory => Increase CMAX (or add/enable TRXs)Peak_gprs_territory > (1-margin) * nbr of tsl in GTRXs (DR or FR) => enable more TRXs for GPRSCDEF-ava_44>0 => Reduce CS traffic if PS is high (check Not used RTSLs!)“GPRS inactivity” alarm (ref TN808)If ho_61 is “big” => check territory upgrade reasons (PS triggers => Increase CDEF. CS triggers => Decrease CDEF if PS traffic is small, otherwise actions 1-4

Do nothing

No

YesNo

Do nothingCheck Statistical

validity

y % of congestion in previous BHs

3 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials

Company Confidential

(1) If AMR and/or HR is used add Dual rate TSL(2) If Dual rate not possible add TRX (need to check the PCU, A-bis and Gb capacity)(3) CS traffic management (change HO parameters, resource management parameters)(4) Increase nbr of dedicated PS timeslots

Yes

Check PS traffic

behaviorTBF/TSL >1.2 , (max(tbf_37c, tbf_38c))

AndUL / DL multislot allocation blocking – hard (max(tbf_15, tbf_16))

AndDL multislot blocking – soft (blck_33)

Radio problem analysisPS Busy Hour

Configuration check

CMAX=CDEF => Increase CMAX0.75*CMAX < peak_gprs_territory => Increase CMAX (or add/enable TRXs)Peak_gprs_territory>=(1-margin) * nbr of tsl in GTRXs (DR or FR) => enable more TRXs for GPRS“GPRS inactivity” alarm (ref TN808)CDEF<ava_44 => Increase CDEF (check EDAP, PCU capacity first)If ho_61 is “big” => check territory upgrade reasons (PS triggers => Increase CDEF. CS triggers => Decrease CDEF if PS traffic is small, otherwise actions 1-4Do nothing

No

No

Check Statistical

validity

y % of congestion in previous BHs

Do nothing

Yes

4 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials

Company Confidential

Abis-EDAP Performance Analysis

Is there severe

congestion in EDAP pool?

Do we worry about

this link?

Yes

NoDo nothing

Increase pool size

Yes

Yes

Dap_13

(x)75% of congested EDAPsOrPayload x MBytes

NoDo nothingCheck

Statisticalvalidity

y% of congestion in previous BHs

Dap_13 : Down Link EDAP Congestion due to small Pool sizeP_nbsc_dynamic_abis

5 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials

Company Confidential

PCU/DSP Performance Analysis

Is there severe congestion in PCU/DSP

allocation?

Do we worry about

this link?

Yes

NoDo nothing

PCU Replanning is needed

Yes

Yes

Dap_15(DL), Dap_14(UL)Blck_32

(x)75% of congested PCU/DSPOrPayload x MBytes

NoDo nothingCheck

Statisticalvalidity

y % of congestion in previous BHs

Dap_15 : Down link EDAP congesting due to PCU limitation, %Blck_32 : Territory Upgrade rejection due to PCU capacity , %

6 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials

Company Confidential

Gb Performance Analysis - FR

Is there severe

congestion in Gb link?

Yes

Increase Gb capacity

Yes

Frl_8a ,Against Values from the table

NoDo nothingCheck

Statisticalvalidity

Y % of congestion in previous BHs

Tool can read the Gb Link size : C_NSVC (Configuration data)

Following table can be hard code in the toolOr allowed the user to change if needed

Frl_8a : Maximum received load % ( DL)

Gb bandwidth [kbps]

Restricting Gb link utilisation [%]

128 25

256 61

384 68

512 68

640 70

768 75

896 85

1024 90