Вы находитесь на странице: 1из 12

Process for GPRS

Monitoring/Optimization

Better
throughput

Company Confidential
1 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Optimization tasks
• Network checks
• Network/interface configuration
• Sleeping cells
• Capacity optimization
• Air interface
• Abis interface
• PCU
• Gb interface
• PAPU
• Gi & Gn interface

Company Confidential
2 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Network and interface checks

Basic checks done on different interfaces


• Radio interface/BTS checks:
• GENA=Y, EGENA=Y, GTRX=Y
• EDGE TRX (TSDB type) to be equipped for GPRS and EDGE use
• # of Dedicated RTSLs =2/3.
Note : Exact number of dedicated time slots for a cell is calculated using the formulae:
No. of dedicated tsls = (CDED * No of tch tsls on trxs with GTRX=Y)/100.
Above formulae gives the exact value of dedicated tsls which at times is different from the value reflected in GPRS GOS for
“Capacity dedic PS” as this counter is influenced by cell/trx outages.

• Abis checks:
• EDGE TRX with GTRX = Y should only be connected to DAP
• DAP pool equipped is same at BSC and BTS ends i.e. MML and traffic manager should have same DAP tsls.
• PCU should not have any unused EDAPs (DAP without any TRXs)
• Gb interface checks:
• Minimum Gb link size to support 4 RTSL EDGE terminal is 4 TSLs (256 kbits). Thus the same to be
maintained.

Company Confidential
3 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Network checks – Sleeping cells

• Sleeping cell scripts daily in the network


• Scripts implemented in crontab and run daily after 0010 hrs for previous
day
• Case by case analysis of sleeping done – corrective actions based on
global guidance
• Additional checks
• BCSU working state
• Sleeping cell alarms monitored
• BTS WITH NO TRANSACTIONS (7738) – cause code 10
• TRAFFIC CHANNEL ACTIVATION ALARM (7725)

Company Confidential
4 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Locations in the network which are looked w.r.t
capacity optimization/monitoring
PCU/NSEI
PAPU
Air Interface (Radio) Abis Gn
Gb

BTS BSC SGSN GGSN


Um Abis Gb Gn

Gi

GPRS Core
Gi
Company Confidential
5 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
1. Capacity Optimization - Air Interface (Radio) :
Monitoring cells with high GPRS blocking :
•Daily analysis of cell wise GPRS GOS report done to reduce Hard blocking
and Soft blocking

• The above monitoring process to be followed everyday to identify the cells


with high utilization/ data blocking.
• Cells showing consistent blocking for 3 days to be acted upon as per
above process.

Company Confidential
6 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
2. Capacity Optimization - Abis (EDAP) :
ND report 280 is used for monitoring EDAP pool Utilization and based on this report
EDAP pool is been expanded.
• 280 report is extracted on EDAP id on hourly basis and analysis is done for 48 hrs.
This helps in knowing the pattern of EDAP pool utilization in a complete day.

•Expansion of EDAP pool needs to be checked with the capacity available on NSEI
0r else NSEI needs to be re-dimensioned accordingly.

Company Confidential
7 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
3. Capacity Optimization – PCU/NSEI :
• Limitations on PCU are:
• 64 cells
• 128 trxs with GTRX set to “Y”
• 256 tsls (This includes EDAP subtsls + default territory + tsls used for upgrades)
In case of mixed configuration, limitation w.r.t. tsls is a concern.
• In order to get number of free tsls on NSEI there are various commands that need to be used on MML and
service terminal which gives various outputs and then these outputs are used together to determine the
tsl utilization per NSEI.

Output of various commands used to determine the utilizations in terms of tsls used in each NSEI.
(MAX Conn-Tsl Count) in decimal + tsls for upgrade
In the above eg it indicates that NSEI 1407 is heavily utilized and needs PCU balancing
determine free tsls on that PCU

• Using the above method in all BSCs, NSEIs that are low/heavily utilized are determined and then PCU balancing
is done accordingly. New NSEIs are also equipped in case of PCU, space on E1 and space on PAPU for GB is available.
Company Confidential
8 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
4. Capacity Optimization – GB Utilization :
• Gb Utilization for a particular Bearer Id is reported using the formulae which is reported
in the daily GB Util report as “Max_bytes_rec”:
(8*(dlci_1_bytes_rec
+ dlci_2_bytes_rec
+ dlci_3_bytes_rec
Frl_8a = + dlci_4_bytes_rec
+ dlci_5_bytes_rec)/(period_duration*60))
---------------------------------------------------
c_nsvc.committed_info_rate*16

• This is been monitored daily and if any GB reports its utilization > 70 % for more than 3 consecutive
days, it is been planned for expansion. i.e. Access rate/CIR is increased.
(Capacity on PAPU needs to be checked before GB link is expanded)
• Best approach followed to reduce Gb utilization is to check the RLC payload for cells/sites in that Gb
In case of more there are more than 1 site that contribute to high RLC payload, these sites are
distributed to low utilized Gbs. However capacity on NSEI in terms of free tsls also needs to be checked
before site shifting.
• Further an approach of using hourly data for Gb – ND report 240 helps in further analyzing the behavior
of that Gb i.e. is the Gb utilization high for just 1 single hour (in case a user is trying to download a
movie) or the Gb is responsible for carrying high data traffic for quite a number of hours of a day.
Company Confidential
9 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
5. Capacity Optimization – SGSN :
• Daily check on Attach Success Rate & PDP context activation success rate is done and
if any degradation found, is alarmed to Core team

• Max number of Attach subscribers per PAPU is 20k for SG3 (will be upgraded to SG5) and
that of SG5 is 40 k. In case of 70 % utilization, BSCs are shifted to low Utilized PAPU.

• PAPU utilization in terms of tsls for Gb link termination:


• Each PAPU has a limitation of 192 tsls for Gb termination which is used upto 85% max.
•In case any PAPU is approaching the max limit of tsls, BSC shifting is done to other/new PAPU
to have free tsls on high utilized PAPU.
• Periodic check is done to know the tsls available for Gbs that needs to be equipped for new BSCs

Company Confidential
10 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
6. Capacity Optimization – Gn & Gi interface :
• Gn interface : Daily monitoring done by checking throughput on Gn interface.

• Gi interface : Daily monitoring done from Mantra online link (which gives monthly/
daily/hourly/5 mins trend. In case of 75% utilization reported the same is planned
for expansion.

Company Confidential
11 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Concerns and comments for expansion
• Adding trx(s) for reducing blocking on radio are sometimes restricted with capacity on E1 (Abis).
• Expanding EDAP pool to reduce EDAP congestion are sometimes restricted by tsl utilization on NSEI.
• Increasing NSEIs are sometime restricted by tsl availability on PAPU.
• Expanding Gbs are sometimes restricted by tsl availability on PAPU.
Augmentation of capacity at any node of data network needs to be checked with the capacity right up to
PAPU/SGSN.

Recommendation for capacity augmentation


• Minimum DAP size should be 4 TSL (16 subtsls) to cater for 4 RTSL EDGE MS. Recommended Dap size should be
6 TSLs for 4 RTSL EDGE MS.
• Recommended amount of EDAPs per PCU by product line are 2, 4, or 8 (Maximum16) for even distribution of
EDAPs per PCU. With the configurations used in present network it would be advisable to have 4 EDAPs per PCU.
However this would require very high no. of PCUs. The best worked out count for EDAPs per PCU is 5/6.
• Minimum Gb link size to support 4 RTSL EDGE terminal is 4 TSL (CIR=256kbps). In case of good EDGE throughput
required, 6 TSL (384kbps) Gb links are recommended.

Company Confidential
12 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials