TCH Congestions

 Read the documents that ZTE provide about TCH in congestion.

 congestion gives the time when no resources are available (it is possible that nobody needs them so no blocks)
 Queried top cell in cluster few clusters (For busy hour) for TCH congestions.
 Checked steps as below.

TCH Congestion Resolution

1. Check if there is an alarm in this cell

2. If the traffic volume increases suddenly, check whether the surrounding base stations are broken

3. If there is no problem in the above two steps, it means user behavior and TCH congestion caused by increased traffic. There are many processing methods, increase TRX,
adjust HR rate threshold, adjust CRO (cell reselection parameter), adjust handover parameters.

4. If TCH congestion is serious, the preferred method is to increase TRX

For internal use only. No spreading without prior approval of ZTE. 1

Case 1
 In this case Site ID= 2135, Cell ID=1 (Cluster 41) for TCH congestions (Include handover)

 TCH in congestion due to traffic increase, traffic increment after curfew.

 There is 1800 cell in the direction so I tried balancing traffic with 1800 cell with below optimization steps.
 900---->1800 HoMarginPBGT=24 , 1800-->900 HoMarginPBGT=34
 In accordance with GSM specifications, a handover decision can be made after the required average values are acquired. The PBGT value of a neighbor cell is also a
reason that can trigger a handover. A decision to do a handover is made when the PBGT value of a neighbor cell is greater than or equal to the corresponding
threshold of the neighbor cell. The handover reason is that a more appropriate cell is detected.
 This parameter is the threshold that must be used for the decision of a handover caused by PBGT from a neighbor cell to the local cell.

For internal use only. No spreading without prior approval of ZTE. 2

For internal use only. No spreading without prior approval of ZTE. 3
  For further more improve I changed CRO settings of this cell

As a criterion of cell reselection caused by poor radio channel quality, C2 is created based on C1 and some offset parameters. The offset parameters can facilitate MSs'
preferentially selecting a specified cell or prevent MSs from selecting a specified cell. Usually, the offset parameters are set for load balancing in the network.

In addition, there are three factors affecting C2: cell reselection offset (ReselOffset), temporary offset (TemporaryOffset), and penalty time (PenaltyTime). TemporaryOffset
indicates a temporary correction value for C2.

After changing reselOffset 05, penaltyTime 031,

C2 = C1 - CRO

created 10 dBm level gap for traffic balancing when reselection.

For internal use only. No spreading without prior approval of ZTE. 4

  After Optimizations done TCH congestions decreased. From below KPI we can clearly understand it (From busy hour KPI).
 Also, no congestion in 1800 cell.

For internal use only. No spreading without prior approval of ZTE. 5

Case 2

 In this case Site ID= 2158, Cell ID=1 (Cluster 41) for TCH congestions (Include handover).

 In this case TCH congestion due to traffic pattern in the cell.

 I tried to optimize this cell using Traffic balancing (Using CRO).
 After changing reselOffset 03, penaltyTime 031,
For internal use only. No spreading without prior approval of ZTE. 6
C2 = C1 - CRO

created 6 dBm level gap for traffic balancing when reselection.

 Also I found that HR function optimization already have done for this cell.
 amrHrThs- When the number of busy timeslots (occupied TCHF, occupied TCHH/2, available PD channels, and congested PD channels) divided by the number of
total time slots (available TCHF, available TCHH/2, and available PD channels) is greater than or equal to AmrHRThs/100, and both the TRX and cell support AMR,
AMR is preferred to be used for the subsequent services.
 Already amrHrThs & HrtHs in 5

For internal use only. No spreading without prior approval of ZTE. 7

  After Optimizations done TCH congestions decreased. From below KPI we can clearly understand it (From busy hour KPI).

For internal use only. No spreading without prior approval of ZTE. 8

For internal use only. No spreading without prior approval of ZTE. 9
Case 3
 Found HTTL requested V3 site(Site ID=3213 cell id=1 BSC 315) for TCH congestions, HTTL suggestion was to add trx to solve this. But it is already configured to
maximum trx in v3 site= 2. So I tried to optimization done without adding trx using traffic balancing.
 With help of ZTE network optimization engineers below are the steps I taken.

1.) Checked which cell did most handovers with congestion cell.
2.) Checked that HO adjacent cell traffic,congestions, Trx for take decision to balancing traffic.
3.) Changed HomarginPBGT for handover traffic to both 900 & 1800 cells near site and CRO value  4, for balancing reselection traffic.

For internal use only. No spreading without prior approval of ZTE. 10

Case 4

 ZTE KPI optimization engineer zhang yayun assign some cells(BSC315) that belong to TCH blocking high(In below figure).

 Steps were we have to take, check alarms, packet loss in congestion and surrounding cell, if no alarms add new trx.
 There were no alarms in any of these sites effecting to KPI’s, So I added trx for optimizing TCH blocking.
 Only one cell trx adding failed because it is a V3 site(Maximum trx have already configured).

For internal use only. No spreading without prior approval of ZTE. 11

  After adding trx KPI improved.

For internal use only. No spreading without prior approval of ZTE. 12

For internal use only. No spreading without prior approval of ZTE. 13