GSM RNP&RNO Cases

................................................................2 Alarm Information .3 Title: Incorrect frequency led to a cell with abnormal traffic statistics........................................................1 Phenomenon Description:...................................... 4 2..................................3 Cause Analysis:.............................................................................................................................2 Alarm Information:.................................. 4 2..2 Alarm Information: ...................................................................................................................... 7 3............ 2 2............................4 Handling Process .................. 4 2...................................................3............. 9 Confidential Information of Huawei......................................1 Title: Co-BCCH and Co-BSIC caused wrong attempted incoming inter cell handover ........................ 6 3.........................1.......1...........................................................................2 Alarm Information ...............................2 Cause Analysis:........................ 7 3.................. 1 Chapter 2 Call Drop Problem ........ 2 2.......................................................................... 1 1...................................... 6 3........................................................4 Handling Process: ..................................... 2 2................................2...........................1......................................................... 2 2..................... 8 3...................3 Cause Analysis....4 Handling Process: ........................................ 2 2.........................1 Phenomenon Description:.......4 Title: External interference leads to drop call ............ 6 3...4.......................1 Phenomenon Description................................................................................................................................................................................................................................................................................4...............3 Cause Analysis:................3.........4 Suggestions and Summary: ..................... 1 1..............................................................1 Phenomenon Description:...................... 7 3...........................................................3 Cause Analysis:...............2 Alarm Information:................................................................ 5 2................................................................................................. 2 2.1.... 7 3.................................................... 2 2........................................ 9 4.............................................................................................3.1.............2..........................................................5 Suggestions and Summary ............................................2 Title: TCH seizure failure for the difference of BCC and TSC ..................2.............1 Phenomenon Description:............................4 Handling Process ........................................ 3 2.......................... 4 2....4 Handling Process: ....2 Alarm Information:.............2..........................................................................4...................1 Phenomenon Description.............................3.............................................................................................................3 Cause Analysis............3.................. 3 2............ 3 2........1 Phenomenon Description:.......................................................................................................3........ 6 3...........................................3 Cause Analysis:...................... 1 1........................ 7 3....................1....................................3 Title:Target Cell Blocking Cause Outgoing Handover Failure for a New Site On-air Commission Test ..............................................................................................................1.....................................3..... 7 3......................1.................3 Handling Process: .........................................1 Title: High TCH congestion rate caused by reverse connection between antenna and feeder cable .................................................. 5 Chapter 3 Congestion Problem......................................... No Spreading without Permission i .3 Cause Analysis............. 4 2.....1 Title: Can not make a call even there is high Rx level on mobile phone ....2........................... 3 2......................................................... 6 3........1 Title: Interference causes Call Drop ............................................................................ 7 3.......................... 7 3.. 4 2...................................................2 Alarm Information ........................ 2 2.......4 Handling Process ...................... 4 2.............GSM RNP&RNO Cases Table of Contents Table of Contents Chapter 1 Assignment Problem................................ 2 2. 8 Chapter 4 Handover ...................................................................................................1.................4..2..................4.......4 Handling Process ............................................5 Suggestions and Summary: ............2..2 Title: Call Drop Problem Due to A-interface Congestion .................................................3............................1.............1....................................... 4 2...........2................................................ 4 2................................................................................................... 6 3.........................................5 Suggestions and Summary: ...............................................1................................................................................ 1 1..................................1 Phenomenon Description.............................................................2.....................................................................1...... 1 1................................................................................

............ 13 5.. 11 4...........................1.................... 9 4..................................................1................................3 Cause Analysis...1...................................................... 13 5..................................... 13 5............................................................ 12 5.......... 9 4..................................... 13 5..............................................................1 Phenomenon Description.. 12 5................2.................2.... 13 5................................. 9 4........................... 14 5....................2...........1 Phenomenon Description.........................................................5 Suggestions and Summary ......................................3..................................................................................................... 13 5...................................2....................................................................2 Alarm Information ........................ 13 5....................... 14 ii Confidential Information of Huawei....2 Alarm Information ...........1.......................... 12 5.........................1 Title: zero outgoing interBSC handover success rate ...................................................................1.......3 Cause Analysis....................3........ 12 5...................1 Phenomenon Description...............................................................................3.................................................3............................................................................................................3 Cause Analysis...................................... 13 5.. 10 4....................... 9 4......................................2 Title: A interface identifier deferent cause BSC handover successful ratio was low....................... 11 Chapter 5 Data Configuration Problem ................2..................................................4 Handling Process .......1......3..3...........................................................GSM RNP&RNO Cases Table of Contents 4......................................... 12 5.........................................................2.............................. 12 5...................................................................2 Alarm Information ...... 14 5..................................................................................................................2..........3 Title: Non-configuration of BA2 table causes no handover ....................4 Handling Process ................... 10 4..................... 11 4...........................5 Suggestions and Summary .................... No Spreading without Permission ...4 Handling Process ...............................................................................................................................4 Handling Process ................ 10 4...2 Alarm Information .3 Cause Analysis.............. 10 4..............................................2 Title: Wrong CGI causes low outgoing inter BSC successs rate...2 Alarm Information ..1 Phenomenon Description......................3.................................................... 12 5...............................................1 Phenomenon Description.............................2...................................................3 Cause Analysis................2..........1.............................................. 10 4........................................................................................................................................... 10 4...........................2............................................3.......2 Alarm Information ....................4 Handling Process . 10 4..... 11 4..3 Cause Analysis..3 Title: Wrong parameter settings of IDLE SD Thrash leads to fake congestion ........................1................................1.................................................................1 Phenomenon Description....................................4 Handling Process ...............5 Suggestions and Summary ...........5 Suggestions and Summary ............................................. 10 4............................................................3...........................

1.1. We have found the cell with highest Rx level covering very far (TA is more than 63). or implement extended cell technology. The Rx level of the second strength cell is about -80dBm. 1. make software simulation before new BTS installation. the cell which TA<63. In those situations when coverage is very far (Rx>-80. and its TA is 16. Considered that Rx_access_min in the 900 netwok equals 5.1. Confidential Information of Huawei. for 1st cell. 1st cell C2>2nd cell C2. couldn't be chosen even the Rx level is high (-80dBm). C1 = 105-80 = 25 = C2. Rx level ranges from -76dBm to -92dBm. even though other cells covering closer (due to higher propogation loss their signal is lower). 1. TA>63). and estimate coverage of the BTS. we found that there are several cells covering the problem spot. we need adjust antanna's downtilt during installation. C1 = 105-76 = 29 = C2.4 Suggestions and Summary: If possible.1 Title: Can not make a call even there is high Rx level on mobile phone 1. and call cannot be established from it.2 Cause Analysis: During the investigation by using Sagem testing MS.1 Phenomenon Description: There is high Rx level on mobile phone (idle state) but can not make a call.1. No Spreading without Permission 1 . All cells covered the place are 900 cells (all cells CRO = 0). for 2nd cell.3 Handling Process: To solve the problem. need adjust downtilt or output power of the far coverage cell. therefore. 1.GSM RNP&RNO Cases Chapter 1 HAssignment ProblemH Chapter 1 Assignment Problem 1.

2 Title: Call Drop Problem Due to A-interface Congestion 2. 2 Confidential Information of Huawei.1.GSM RNP&RNO Cases Chapter 2 HCall Drop ProblemH Chapter 2 Call Drop Problem 2. 2.1. Thus it was obviouse that the problem was due to interference .1 Title: Interference causes Call Drop 2.2 Alarm Information: No alarm information 2.1. And some problem can be better viewed in idle mode . 24 (58%) calls were blocked. congestion . After changing the frequency a second drive test confirms that the problem was solved. 2. After analysing the logfiles of the DT we found that we found there is unjustified handover due to quality to a cell not suppose to serve in that area and it cause the call drop.1 Phenomenon Description: call drop in highway always occurs in only one direction of the road . 2.4 Handling Process: We did a drive test in the area using tems software connected to two phones one in idle mode and the other in dedicated mode we tested the road in both way .1. This cell didn't apear in the dedicated mode phon logfile.5 Suggestions and Summary: Performing Drive test for some problems is Mandatory . path balance and coverage as a source for the problem .1 Phenomenon Description: Total 41 calls were attempted form the Ashulia bazaar Site. And the Drop occured as suspected .2.1. 2.3 Cause Analysis: After checking eliminating hardware. No Spreading without Permission . After checking the logfile of the mobile in the idle mode there was cell overshooting to the area of call Drop and causing Co-channel thus causing the call drop.

2.GSM RNP&RNO Cases Chapter 2 HCall Drop ProblemH DT was performed in the coverage area of DCS Ashulia Bazar on 14th December.06 divided by 100). there was available free TCH when the calls were blocked.this message from MS MM layer. 2006]. But even after the alarms were recovered the call blocking problems were not solved. 100 channels are available. The Description of this statistic item is . this number should be brought down to zero by adding more circuits. Though the good signal level and good call quality there is a notable amount of blocked call in the site.4 Handling Process: From the traffic statistics it seems there is a notable amount of CM SERVICE REJECTIONS DUE TO CONGESTION in the CM Service rejection causes. Another important statistics item is the Percentage of A-interface circuit (Busy) reached more than 90% in the site which is resulting in the failure of a call. Currently we have notable rejections during busy hour because of A interface congestion. As uplink (from Terminal) and downlink (from DT) data was simultaneously examined. 2. it was clear that.98 ERL in HR. This shows there is serious congestion on the A interface thereby making it difficult to make calls especially during busy hour. No Spreading without Permission 3 . High temperature alarm. Confidential Information of Huawei.5 Suggestions and Summary: The most critical thing required is to expand the A interface. 2. 2. Because of the faulty E1 there occured E1 remote alarms.08ERL in FR and 8. NSS will respond MS a CM SERVICE REJECT message in which the rejection cause is congestion.06Erl in the peak hour. This value is much bigger than the recommended 0.2. if NSS cannot normally respond to a CM SERVICE REQUEST message due to the congestion after receiving. Second extended I/O alarm.2 Alarm Information: E1 remote alarm.7Erl/channel. Second extended I/O alarm.2. "No circuit/Channel available". 2.This alarm happened many times. So the traffic per A inferface channel is 0.96 (96.2. 87. The traffic volume (excluding very early assignment) is 96.7 channel. The alarms means Low voltage and Rectifier fault alarm.Also. Mains supply failure. During the DT there were following message from the L3 information when we encountered such block calls. 2006 (between 6PM & 7PM). In terms of statistics excluding synchronization channel and NO.3 Cause Analysis: Huawei Team made a series of Drive test and signal tracing in the problem zone after getting complaint from the customer. [Excerpt from customer complaint sent on 14th December.

4 Title: External interference leads to drop call 2.1 Phenomenon Description: The customer RNP engineers reported that one cell was abnormal from the traffic statistics. adding that the call drop rate became high and handover rate became low.3.3.4. At the same area. 2.2 Alarm Information: High call drop rate and low handover rate 2. there was need for changing the frequency for this cell in question 2.GSM RNP&RNO Cases Chapter 2 HCall Drop ProblemH 2.5% error. weak signal. MS can't make call any more 2. 3.1 Phenomenon Description: During the driver test.4. Changed the frequency of the TRX and the error was corrected and the traffic statistics became normal.4 Handling Process: 1.2 Alarm Information: No any alarm on OMC 2.Checked all the frequency of the site and neighbour sites with the result of finding out that this frequency was incorrect. Checked and analyzed the traffic statistics of this site. No Spreading without Permission . 2. 4. 4 Confidential Information of Huawei. MS faces drop call when the receiving signal is below -75dBm. with the result of 5.3.3 Title: Incorrect frequency led to a cell with abnormal traffic statistics 2. Went to the site and carried out dial test with the result of high call drop rate and low handover rate. which led to interference among the cells. 5. 2. As a result.3.3 Cause Analysis: The frequency of the cell with abnormal traffic statistics was incorrect.4. Made local loop of radio frequency of that cell with abnormal traffic statistics.3 Cause Analysis: 1.

TRX or CDU faulty. the problem still exists. because sector 1 and 2 are normal. 4. transmission problem. of idle TCHs in Interf. 5. of idle TCHs in Interf. it means there exists uplink interference. the frequency resource came from airforce. 7. 9. A jam was found in one rooftop and produced the interference in one direction. The conclusion is proved by MS measurement reports which have high bit error rate in Abis interface. 5. 8. this situation just exist one area which covered by sector 3 of site A. 2. so transmission of Abis interface is ok. 4. changed and swapped the TRX and CDU. sector 1 and 2 are normal. 2. No Spreading without Permission 5 .5 Suggestions and Summary External interference is normal case in some country. and the problem was solved. checked all the alarms of hardware on OMC and found no alarms on the hardware. when we face problems. unbalance between uplink and downlink. so this is considered as external interference and brought spectrum tool to test the external interference. checked the traffic statistics and found that the cause is balance between uplink and downlink. we shall analyze the problem step by step Confidential Information of Huawei.4. 6. interference in Um interface(uplink and downlink). switched off this equipment. 3. band 5" and "Average num.GSM RNP&RNO Cases Chapter 2 HCall Drop ProblemH 2.4 Handling Process 1. 3. 2. swapped antenna between sector 1 and 3 and found the problem still exists in that area. checked the traffic statictics and found that the "Average num. 6. analyzed the drive test data and didn't find any downlink interference. radio parameters are unsuitable.4. band 4" have big numbers.

4. and no connection fault of hardware is found. 5. Tracing the Abis interface signaling.2 Alarm Information None 3.1. but the obvious difference of receiving level after expansion is not found from that of before expansion.1. 3. When call tests are done near the BTS. and the jumper of Cell 2 is connected with the antenna of Cell 1. the TCH occupied failures are very often.1. that the receiving level of downlink signal is much low. The problem should locate in the stand-alone transmitting channel because all the expanded TRX are connected with the antenna by a stand-alone transmitting feeder cable. there are many TCH occupied failures when TA=2. 6 Confidential Information of Huawei. No Spreading without Permission . the TCH congestion occurs in the old TRXs. and two transmitting antennas must be employed along with BTSs's configurations increasing. The transmitting channels are interchanged.1. It is found out from the analyzing of traffic statistics result after expansion. the transmitting antennas are connected reversely with the jumpers. 2. but no improvement. HPA to Combiner.1 Phenomenon Description High TCH congestion rate with some BTSs after expansion 3.3 Cause Analysis The network needs expansion due to the capacity requirement. The main reason is that the antenna labels below the tower are not installed. 3. So the problem must locate in the feeder cable connected the antenna and the expanded TRXs.GSM RNP&RNO Cases Chapter 3 HCongestion ProblemH Chapter 3 Congestion Problem 3. Checking the jumpers on the tower.1 Title: High TCH congestion rate caused by reverse connection between antenna and feeder cable 3. Meanwhile the coverage directions of BCCH and TCH TRXs is different. Both TRX and HPA are replaced.4 Handling Process Check the transmitting channel from TRX. so that feeder cables are not in order on the platform of antennas. The jumper of Cell 1 is connected with the antenna of Cell 2.

No Spreading without Permission 7 . if it is not same.For traffic. so the reason is not for configestion. "Cell-A" visualize "outgoing handover successful rate" is very low when we do commission test after cutover. but other site is ok after network optimization. find that immediately assignment failure rate and handover assignment failure rate are high. the mobile still doesn't handover to the other better signal strength G900 adjacent "cell-B".1 Phenomenon Description In one place.2 Alarm Information No 3.2.2. no congestion. change these two parameter to be same.2 Alarm Information None Confidential Information of Huawei. frequency and so on.Check the frequency planning.Check the tables which have been modified. check the TSC parameter. 4. the 1800 system is Huawei equipment. When we do drive test find that even the serving cell Rx-lev is as poor as -100dBm. we use the forcing handover function several times but only few times handover successful 3. this site is not busy. 3. HSN.2 Title: TCH seizure failure for the difference of BCC and TSC 3.GSM RNP&RNO Cases Chapter 3 HCongestion ProblemH 3. TCH seizure failure rate must be high 3. so the reason is not for interference.1 Phenomenon Description In dual-band network.2. no problem.Check the statistics.3 Title:Target Cell Blocking Cause Outgoing Handover Failure for a New Site On-air Commission Test 3. 6.Finally. no abnormal interference.Test the signal in the site. RNP engineer find that one site''s TCH seizure failure rate is high.3.4 Handling Process 1. find that: the TSC is different from BCC. no same frequency or adjacent frequency interference. 5.2. another vender is S company. and the other KPI is ok 3.3 Cause Analysis BCC and TSC should be same. 2. the problem is solved 3.3.

it visualize that huawei BSC send "handover required" to MSC.4 Handling Process Change the penalty time for handover failure from "10s" to "20s". The mobile can't attempt to handover into "cell-B" again within short time after handover failure. No Spreading without Permission . check the same connect serial number.Trace the signaling. 3.3.3 Cause Analysis 1. Check the statistics. the target G900 "cell-B" block rate is very high 3. the mobile handover to another adjacent cell successful and the problem solved 8 Confidential Information of Huawei. 2. so we can make sure that there is no trouble about data for handover.GSM RNP&RNO Cases Chapter 3 HCongestion ProblemH 3.3. but there is no signaling of "handover command" for this "handover required" from MSC.Because force handover can be successful.

1 Phenomenon Description One day we found one cell (cell A) which was not on air but still had attempted incoming inter cell handovers and TCH seizures. no successful incoming inter cell handovers and no attempted outgoing inter cell handovers.2 Alarm Information No Alarm 4. From above exact phenomenon.1. so it showed that all the TCH seizures failure were caused by handover. after finished this. we checked the performance of A. All the incoming inter cell handovers were failed. So those cells would consider the signal was come from A. Some other cells which had neighbor relation with A can receive B’s signal because B had overshooting problem. but no incoming inter cell handovers. Of course. The number of incoming inter cell handovers was always same as TCH seizures.1. No Spreading without Permission 9 . 4.1.1 Title: Co-BCCH and Co-BSIC caused wrong attempted incoming inter cell handover 4. A and B didn’t have neighbor relation. Confidential Information of Huawei. the handover would fail because cell A was not on air. and there were no attempted incoming handovers and TCH seizures.4 Handling Process According to above analysis. the most probability was that some closed cells(for example cell B) had Co-BCCH and Co-BSIC with cell A.GSM RNP&RNO Cases Chapter 4 Handover Chapter 4 Handover 4. but all of them were failed 4.3 Cause Analysis We checked there were many attempted incoming inter cell handovers. we checked the problem as following steps: 1)Checked the BCCH and BSIC and found there was a cell B (2 Km away) Co-BCCH and Co-BSIC with cell A.1. when other cell(cell C) intended to hand over to cell B and it wrongly handed over to cell A. 2)Changed the BSIC of A and down tilt the antenna of B. So it would handover to A wrongly. A was defined neighbor relation with other closed cells.

2. Checked BSC handover parameters.3. But ERRICSON sites handover successful was normal. We checked the traffic statistic.2. No Spreading without Permission . 4. during drive test in the area. 10 Confidential Information of Huawei. everything is ok.3 Title: Non-configuration of BA2 table causes no handover 4.2. checked that cause value"protocol error between MSC-BSC ---1100000". so I think our handover data is correct. At last we doubted that link have some problems. it was noticed that in dedicated mode.5 Suggestions and Summary We need to attention some practical problems. Customer have one MSC and two BSC. I found MSC identifier is GSM_phase_2+ and HUAWEI BSC identifier is GSM_phase_2.4 Handling Process Checked traffic statistic and found HUAWEI sites handover successful ratio was low. One MSC and one BSC belong to HUAWEI. so two side data was consistent. we can found our aim cell CGI. Traced A interface link. 4. We can found ERRICSON sites can send require to HUAWEI sites. we found that HUAWEI BSC handover successful ration was low.3 Cause Analysis Because our INTRA-BSC handover was normal. that problem solved 4. But in fact we couldn't do that.2 Title: A interface identifier deferent cause BSC handover successful ratio was low 4.GSM RNP&RNO Cases Chapter 4 Handover 4. there was cell reselection and no handover from one cell/site to another. So MSC data also was normal.2 Alarm Information No Alarm 4. I changed HUAWEI BSC identifier to GSM_phase_2+. But ERRICSON BSC handover successful ratio was normal 4.1 Phenomenon Description In Iran ESFAHAN MTCE.1 Phenomenon Description In a recent GSM Project which involves 1 (2-module) BSC + 4 BTS312 (S222/222) + 5 BTS312 (S222/444) + 3 BTS312 (S22/22).2.2. so I checked BSC and MSC A interface identifier.ERRICSON BSC identifier is GSM_phase_2+. although in theory GSM_phase_2+ and GSM_phase_2 are compatible.

3.3.Implemented DT to ascertain the anomaly has being corrected. As result of this.Reported the problem to BSS Engineer at the BSC site who did the configuration to check the adjacent relationship if it is ok.3 Cause Analysis From the "Serving + Neighbor window".2 Alarm Information No Alarm 4. 3. the serving cell was displayed with no neighbors being displayed. 4. all BCCH frequencies in the network can be put into the BA2 table so as to use the performance measuring function of the undefined adjacent cells in the traffic statistics console to find out the adjacent missing cells. BA list is sent through system information 5. and 5ter. 2.The BA2 table was then configured dynamically in the BSC Auto Data Configuration system by the BSS Engineer. Non-configuration of BA2 table suspected 4. In order to know the cells adjacent to the current serving cell. all site installation/configuration must be carefully checked by BSS Engineers and ensure to be in order before any other optimization measure is taken to solve problems discovered on site. No Spreading without Permission 11 . This information lists the BCCHs of all the neighbor cells. 4.GSM RNP&RNO Cases Chapter 4 Handover 4. 5bis. neighbor cell description information will be broadcast periodically in the system information of each cell. and it was observed that there was no problem with the adjacent relationship. is used to inform the MS in the active mode to search the BCCH frequencies of adjacent cells.Also checked was the BA2 table if configured or not in BSC and it was observed that the BA2 was not configured. MS must keep on measuring the BCCH signal levels of the serving cell as well as the neighbor cells. MS must extract this information from the system information and use it as the basis of neighbor cell signal measurement.5 Suggestions and Summary This problem was as a result of an oversight from the BSS Engineer on site.3. BA2 list.4 Handling Process 1. Confidential Information of Huawei.3. During network optimization.

4 Handling Process After adding the missing neighbor the cell having the problem at hand and changing the BCCH of the neibor added the inter BSC handover returned to normal 5.GSM RNP&RNO Cases Chapter 5 HData Configuration ProblemH Chapter 5 Data Configuration Problem 5.1. Check for CO-BCCH CO-BISC problem 12 Confidential Information of Huawei.This neigbor was not online as we discovered from the BTS maintenance. So the problem was due to CO BCCH between undefined neighbor and offline external neighbor 5.1 Title: zero outgoing interBSC handover success rate 5. There was only on external BSC neighbor 5.1.1. After checking the sites around .1.3 Cause Analysis The main reasons causing the failure of handover between cells follow: 1) Unreasonable handover data configuration 2) Problem with equipment (individual TRX damaged) 3) Congestion 4) Interference 5) Clock problem 6) Coverage 7) uplink/downlink unbalance There was no interference or congestion or hardawre problem. No Spreading without Permission . We suspect there is a a data configuration problem. and serving in the same area and it was not defined as a neighbor. We checked the neighbor and found one external neighbor.1.2 Alarm Information No Alarm 5.5 Suggestions and Summary When you have a handover problem check the neigbor defintion and possible cells that can be defined as a neighbor .1 Phenomenon Description From the traffic statisticas we a found a cell with high attempted outgoing inter BSC handover but with zero success. we found a cell with the same BCCH as the external neighbor in the same BSC of the cell having the problem.

2. after invetigating the External neighbors of this cell we found there neighbors having wrong CGI.2.4 Handling Process No alarms are found.1 Phenomenon Description Recently in TMIB network of Bangladesh we found that after comissioning new BSC at CTG(CB37) Version (G3BSC32V300R002C12). 2. Uplink/downlink Unbalance Caused by Antenna & Feeder System 5.GSM RNP&RNO Cases Chapter 5 HData Configuration ProblemH 5. Transmission Failure. Coverage. 3.3 Title: Wrong parameter settings of IDLE SD Thrash leads to fake congestion 5. 4. 5 Unreasonable Parameter Settings. Unreasonable Parameter Settings. and the cell is on the bordaer of the BSC.2 Alarm Information No Alarm 5. Interference.No problem in interfernce was found.2.3 Cause Analysis call drop maybe caused by: 1.2.2 Title: Wrong CGI causes low outgoing inter BSC successs rate 5.5 Suggestions and Summary correct the CGI the neighboring cell in the external neighbors relation table of the BSC 5. TCH congestion is around 5% to 10% in all cell at evening time.2. No Spreading without Permission 13 . 5.3.1 Phenomenon Description we found a problem of low outgoing inter BSC successs rate 5. 6. after further analysing we found that specfic cell in the BSC cause this problem. After checking the traffic statistics it is found that at the evening time TCH is congested where as from Erl B table it Confidential Information of Huawei.

2 Alarm Information No Alarm 5. 5.3 Cause Analysis At first we check the data configuration specially cell data that is set by customer when comission those sites and found that in Channel Management Console the parameter IDlE SD Thrashold is put 24.3. so TCH channel would become less and leads to overflow. 4 Apr 2006 09:35:00 UTC OVS Local SE 85725jonysaha So the reason may be wrong setting of IDLE SD thrash leads to more.As this parameter set to 24.\. No Spreading without Permission .4 Handling Process Tue. Later change all site this parameter.So the reason may be wrong setting of IDLE SD thrash leads to more TCH is Convered to SDCCH and leads fake congestion.IDLE SD Thrash: When the number of idle SDCCH channels is less than or equal to the \Idle SD Thrsh. The default value of this parameter is 2.GSM RNP&RNO Cases 0 should not be congested. Also Min Recovery time is long (600S). TCH is Convered to SDCCH and leads fake congestion. 14 Confidential Information of Huawei. the system will try to find available TCHs and convert them to SDCCH channels. and System will convert more TCH to SDCCH. Then from BTS Maintanance console check the BT view channel state and found that at evening time more TCH is converted to SDCCH where as dedicated SDCCH in IDLE.3.As for trail we change one site this parameter and check the KPI next day and found that for that site all cells congestion vanishes. After checking the SDCCH congestion. that meansall the time there would be idle SD channel less than 24.3. The default value of this parameter is 2. It should carry more traffic then congestion. found that no SDCCH congestion seen 5.

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.