TROUBLE SHOOTING & CASE STUDY

---- GSM RNP & RNO 2008-02

HUAWEI TECHNOLOGIES CO., LTD.

CONTENT

Foundational Trouble Shooting Method & Skill

Enhanced Case Study of GSM RNO

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 1

Trouble Shooting Method Overview

Signaling Analysis Remote Trace and Analysis A, Abis, Um interface

OMC Traffic Statistics Remote monitor and Analysis Network, BSC, Cell level

Network Trouble

Drive Test Check on site Test a point or a line in detail

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 2

Trouble Shooting Procedure

Whats the trouble?

Why get the trouble?

How to resolve it?

User complaint specified (when, where, how) It happen in cell level or BSC level, in some place or all It happen in some hour or whole day It happen for some kind mobile phone, or some kind operator, or all

Traffic statistics analysis, the problem caused by radio part or BSS part. If caused by BSS part any alarm, check if any operation done at the time point which problem occur Signal tracing and analysis, find the detail reason Drive Test and Call Quality Test

Check and fix hardware alarm or connection problem Parameter check and optimization Find interference source and get rid of it Expand network capacity or upgrade for the software version

Summariz e the expe

All Rights Reserved 2008, Huawei Technologies CO., LTD.

rience
Page 3

CONTENT

Foundational Trouble Shooting Method & Skill

Enhanced Case Study of GSM RNO

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 4

Case 1: In VINH LINH site hard making call

Description:
Subscriber complain that it is difficult to make call at QTVLH (Vinh Linh).

Procedure test:
Drive test Check on the hardware alarm, and hardware condition. Check on antenna orientation, and antenna tilting. Check on the RF parameter, found some parameter does not suitable.

Solution:
Change of T3212 from 40 to 20. To standardize with MSC setting.

Follow up:
drive test and follow up with the mobile phone dealer. No more complaint received on the following days.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 5

Case 2: Coverage Issue in HA_TINH site

Case Description
Customer complained the signal was weak near the HA TINH site

Analysis
According to drive test result, in Hopping channels, we can see The signal of 87, 89 frequency is 15dB better than the other two In HA_TINH_A sector we cant handover to this cell We suspect HA_TINH site has swap feeder

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 6

Case 2: Coverage Issue in HA_TINH site

Traffic statistics
Use the UL\DL balance to check the swap feeder problem

Summary for swap feeder case

Swap between TCH TRX (TCH assignment failure) Swap between TCH and BCCH TRX (one sector area no main BCCH signal, also TCH assignment failure)
Swap between TCH TRX All Rights Reserved 2008, Huawei Technologies CO., LTD. Page 7 Swap between TCH and BCCH TRX HA_TINH A and B Swap feeder before and after (above is before)

Case 3: Weak signal in one street of THANH HOA

GA_THANH_HOA
TTA alarm cause the site coverage reduce

Afterthe thealarm alarmhad hadbeen beenfixed fixed After

Beforethe thealarm alarmhad hadbeen beenfixed fixed Before

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 8

Case 4: Coverage issue in HA_TINH market

Subscribers in HA_TINH market complained signal is weak inside the market.
Suggestion for this issue is adding new site or add indoor coverage system for market.

New Building

HA_TINH Market

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 9

Case 5: Bad Voice Quality issue in HA TINH BSC

Case Description
Voice quality turned bad since March 19th in the city area of HA_TINH

Analysis
Check the hardware equipment, no abnormal Later receive the same kind of complaint from other area of HA TINH BSC, so we suspect the E1 fault Co-operated with VMS1 MSC engineer, we tested the transmission between TC and MSC one by one and found 3 E1 fault

Solution
Locked the fault E1 and changed to other transmission, and then voice quality became ok.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 10

Case 6: Call Drop increased in THANH HOA city

Case Description
In THANH HOA city, some cell suddenly got the call drop times increased

Analysis
According to the traffic statistics analysis, UL interference is strong in THANGH_HOA_C cell, and a little strong in GA_THANH_HOA_B
Chart 2: GA_THANH_HOA_B turns bad at 7:00 am. Jan 5th
All Rights Reserved 2008, Huawei Technologies CO., LTD. Page 11

Chart 1: THANH_HOA_C turns bad at 7:00 am. Jan 5th

Case 6: Call Drop increased in THANH HOA city

Where is the interference?

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 12

Case 6: Call Drop increased in THANH HOA city

THANH_HOA_C THANH_HOA_Cinterference interference disappeared at about disappeared at about7:30am 7:30amin in th Jan Jan12 12th

Objects THA_THA2_THANH-HOA-C THA_THA2_THANH-HOA-C THA_THA2_THANH-HOA-C THA_THA2_THANH-HOA-C THA_THA2_THANH-HOA-C THA_THA2_THANH-HOA-C THA_THA2_THANH-HOA-C THA_THA2_THANH-HOA-C THA_THA2_THANH-HOA-C

Date 20070112 20070112 20070112 20070112 20070112 20070112 20070112 20070112 20070112

Time 6:30:00 6:45:00 7:00:00 7:15:00 7:30:00 7:45:00 8:00:00 8:15:00 8:30:00

Frequency 84 ( main set/sub set) -89/-99 -89/-98 -89/-98 -89/-98 -103/-108 -106/-106 -103/-104 -106/-104 -102/-104

Frequency85 ( main set/sub set) -88/-102 -88/-102 -88/-101 -88/-101 -105/-109 -109/-109 -109/-108 -109/-109 -107/-108

Frequency86 ( main set/sub set) -89/-99 -89/-99 -89/-98 -89/-100 -104/-108 -108/-107 -109/-109 -107/-108 -105/-106

Frequency87 ( main set/sub set) -90/-95 -90/-95 -90/-95 -90/-96 -102/-108 -108/-108 -108/-108 -106/-107 -105/-108

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 13

Case 6: Call Drop increased in THANH HOA city

After the interference disappear, this area cells TCH call drop decreased
GATHANH_HOA_B interference disappeared at about 7:30am in Jan 12th

THANH_HOA_3C interference disappeared at about 7:30am in Jan 12th

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 14

Case 7: KY_LOI Call Drop Case

Case Description
KY_LOI site is high in call drop, and the call drop type is not RF call drop

Analysis
The mainly reason of Call Drops in KY_LOI site is internal clear. This reason means that, there is some problem with the BSC hardware equipment, or the transmission hardware equipment.
Sampling Time 2006-12-25 12:00 2006-12-25 13:00 2006-12-25 14:00 2006-12-25 15:00 2006-12-25 16:00 Objects M:2, No: 4, Name: KY_LOI-2 M:2, No: 4, Name: KY_LOI-2 M:2, No: 4, Name: KY_LOI-2 M:2, No: 4, Name: KY_LOI-2 M:2, No: 4, Name: KY_LOI-2 TCH call drop 2 11 9 14 7 TCH seizure failures (internal clear) 2 10 9 13 6

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 15

Case 7: KY_LOI Call Drop Case

There are many LAPD_OML alarms in KY_LOI site Suggestion is to check and fix the LAPD alarm of this site

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 16

Case 8: Immediate Assignment failure in THANH HOA

In THANH HOA province, some cells got many times Immediate Assignment Failure. Below is the normal signaling procedure for Immediate Assignment.

Abnormal signaling procedure is showed below, after Assignment cant receive SABM frame. It will send DEACTIVATE_SACCH when the Timer T3101 expired.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 17

Case 8: Immediate Assignment failure in THANH HOA

Solution
Modify the parameter MAX_TA from 62 to 40, in order to forbid too far access

Reason
Only in THANH HOA BSC has this issue, we suspect repeater make the ghost access.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 18

Case 9: No half rate for whole BSC

Case Description
After swapping 1 Alcatel BSC to Huawei BSC, BSC has no half rate traffic.

Analysis
Network topology: Before swap its Alcatel MSC-Alcatel BSC, After swap its Alcatel MSC-Huawei BSC. Signaling analysis: We traced the A interface signaling and found the Assignment Request from MSC only permit this BSC FR speech version 1. So we judged this problem was caused by wrong data configuration of BSC or MSC. Check BSC data configuration: Check cell data configuration in BSC, its correct. Check circuit pool number, it was set to 7, which means this BSC can support FR speech version 1,FR speech version 2,HR speech version 1. Check MSC data configuration: We check the Alcatel MSC data configuration, The half rate parameter was set to DR (dual rate) nor DRMSV (dual rate and multiple speech version), which means only permitted FR speech version 1.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 19

Case 9: No half rate for whole BSC

Message Assignment Request Traced in HA TINH and THANH HOA BSC Message Assignment Request Traced in NGHE AN BSC

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 20

Case 9: No half rate for whole BSC

Solution
Change MSC half rate parameter from DR (dual rate) to DRMSV (dual rate and multiple speech version), problem was solved.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 21

Case 10: Handover Frequently in Cao-Lanh

Issue Description:
During Drive Test in Cao-Lanh site in Dec 12th, two places show handover frequently.
B: Triangle handover: UL of cell A -> OL of cell A -> UL of Neighbor cell B -> UL of cell A ->

A: Weak coverage area, frequently ping-pong between Tran-Quoc-Toan2_DTP and Cao-Lanh1_DTP

Drive Test by VNP

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 22

Case 10: Cao-Lanh Drive Test after Optimization

Result
After doing optimization, Frequently Handover issue had been resolved, as showed below:
Action1: Change CaoLanh1_DTP azimuth from 340>320 to improve Place A coverage, its the main road direction. Action2: Increase PBGT handover threshold between 3 sectors of Cao-Lanh site: from 4->8, and increase PBGT watch time and valid time: from (4, 3) -> (5, 4) in order to reduce PBGT handover times between different sectors of Cao-Lanh.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 23

Case 10: What is Triangle Handover?

1) UL of cell A -> OL of cell A
U to O HO Received Level Threshold: 35, if current signal > -75dBm, it will trigger U->O HO, make OL get more traffic.

2) OL of cell A -> UL of Neighbor cell B

PBGT HO Threshold: 68=4dB, if Path loss A Path loss B > 4dB, and during PBGT watch time: 4s, last PBGT valid time: 3s. O to U HO Received Level Threshold: 20, it means if signal reduce to -90dBm will HO from O -> U. So it trigger PBGT HO to neighbor cell, for 1800 coverage is always weaker than 900 band.

3) UL of Neighbor cell B -> UL of cell A

But actually, this area Neighbor Cell Bs 900, is not as strong as Cell As 900. So it will HO back to UL of Cell A.
OL

Cell B

2
If the MS stand at this area, it may triangle handover again and again
OL

UL

3
UL

Cell A
All Rights Reserved 2008, Huawei Technologies CO., LTD.

1
Page 24

Case 10: Drive Test Log File Analysis 1

Now MS is using OL(1800 band) of Cao-Lanh3_DTP. Preparing HO to UL(900 band) of Cao-Lanh2_DTP by PBGT HO.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 25

Case 10: Drive Test Log File Analysis 2

After HO to UL(900 band) of Cao-Lanh2_DTP, it find Cao-Lanh3_DTP is stronger than Cao-Lanh2_DTP, preparing HO back to UL of CaoLanh3_DTP.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 26

Case 10: Drive Test Log File Analysis 3

HO back to UL(900 band) of Cao-Lanh3_DTP

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 27

Case 10: Drive Test Log File Analysis 4

HO back to OL(1800 band) of Cao-Lanh3_DTP

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 28

Case 10: How to Anti Triangle Handover

In order to reduce Triangle Handover, we must reduce step 2.
OL
2

Cell B

UL

OL

UL
1

Why?

Cell A

Step 1 is UL to OL, for Co-BCCH cells, UL is 900 for coverage, OL is 1800 for traffic load, so we prefer MS to use OL sub cell channel if the 1800 quality is not so bad. We cant modify parameter to avoid or delay the HO form UL to OL, otherwise OL channel will be wasted and UL will be easy to congested. Step 2 is PBGT from 1800 to neighbors 900, PBGT is triggered only between the same layer cells. For dual band co-site, we often set 1800 cell layer higher than 900, but for Co-BCCH cell, 900 and 1800 combined into only one cell, so OL of Cell A is the same layer with UL of Cell B, even they are using different frequency band and 900 is much better than 1800(about 10 ~ 20dB stronger). In this case we must try to delay the PBGT handover from 1800 to neighbors 900, so we increase PBGT handover threshold between 3 sectors of Cao-Lanh site: from 4->8, and increase PBGT watch time and valid time: from (4, 3) -> (5, 4) to reduce PBGT handover times between different sectors of Cao-Lanh.
All Rights Reserved 2008, Huawei Technologies CO., LTD. Page 29

Case 10: PBGT Handover of Cao-Lanh After Modify

PBGT Handover times reduced after parameter optimization, this means triangle handover times also reduced accordingly.
After

Before

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 30

Case 11: DTP Single Way Call

Problem Description: User complained single way call in Sa-Dec_DTP site.
45

Sa-Dec_DTP Mean Holding Time Trend

V: TCH_MEAN_HOLDING_TIME (s)
V: TCH_MEAN_HOLDING_TIME (s)

Analysis: From CQT we found the percentage of

40

single way call was nearly 90%, so we suspect it caused by equipment and transmission part. From OMC Traffic Statistics, we can see this problem began from 12-14 10pm. Because in single way bad cells, subscriber will hung up more quickly, so that MHT will be shorter, like the charts shows here.
V: TCH_MEAN_HOLDING_TIME (s)
45 40 35 30
V: TCH_MEAN_HOLDING_TIME (s)

35 30 25 20 15 8 12-12 8 12-13 8 12-14 16 12-11 18 12-11 20 12-11 10 12-12 12 12-12 14 12-12 16 12-12 18 12-12 20 12-12 10 12-13 12 12-13 14 12-13 16 12-13 18 12-13 20 12-13 10 12-14 12 12-14 14 12-14 16 12-14 18 12-14 20 12-14 8 12-15 10 12-15 12 12-15 14 12-15
14 12-15

V: TCH_MEAN_HOLDING_TIME (s)
50 45 40 35 30

V: TCH_MEAN_HOLDING_TIME (s)

25 20 15 16 12-11 18 12-11 20 12-11 10 12-12 12 12-12 14 12-12 16 12-12 18 12-12 20 12-12 10 12-13 12 12-13 14 12-13 16 12-13 18 12-13 20 12-13 10 12-14 12 12-14 14 12-14 16 12-14 18 12-14 20 12-14 10 12-15 12 12-15 14 12-15 8 12-12 8 12-13 8 12-14 8 12-15

25 20 15 8 12-12 8 12-13 8 12-14 16 12-11 18 12-11 20 12-11 10 12-12 12 12-12 14 12-12 16 12-12 18 12-12 20 12-12 10 12-13 12 12-13 14 12-13 16 12-13 18 12-13 20 12-13 10 12-14 12 12-14 14 12-14 16 12-14 18 12-14 20 12-14 8 12-15 10 12-15 12 12-15

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 31

Case 11: DTP Single Way Call

Result: After Switch the GTNU board in 13:00 12-16, Mobile A and B can hear each other. And then did CQT, one way call did not happen anymore. Double checked by OMC Traffic Statistics, this problem didnt exist.

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 32

Case 11: DTP Single Way Call

Some days later, single way call happen again. The percentage of single way call was about 30% Check traffic statistics, found some abnormal in A-interface from 01-21 10:00AM. Confirmed with customer, the subscriber complaint also start from that time point. At last, we asked OMC engineer, they expanded some A-interface at that time, and the A-interface quality was not good. After locked these A-interface, the single way call disappeared.
AL0050:Mean Number of Uninstalled Circuits on the A Interface 78 78 78.217 90.089 102 102.283 AL0089:Mean Number of Circuits with Uninstalled Peer Circuits on the A Interface 0 0 0 58.744 109 109.303

Date 21/01/2008 21/01/2008 21/01/2008 21/01/2008 21/01/2008 21/01/2008

Time 7:00:00 8:00:00 9:00:00 10:00:00 11:00:00 12:00:00

BSC Name BSC_242H_DTP BSC_242H_DTP BSC_242H_DTP BSC_242H_DTP BSC_242H_DTP BSC_242H_DTP

All Rights Reserved 2008, Huawei Technologies CO., LTD.

Page 33

Thank You
All Rights Reserved 2008, Huawei Technologies CO., LTD. Page 34