You are on page 1of 7

TCH Assignment

Its a process of by which TCH is assigned to the MS. After the SD request MS gets TCH successfully and the call transfers to TCH it means TCH assignment is successful. For the best KPI TCH assignment should tend to 100%. It degrades due to HW problems. Reasons for TCH Assignment failure: Hardware Fault(TRXs,Combiner,Duplexer,Cables) VSWR High Path Loss. Faulty TMA. High TCH Blocking. Loose connections. DR being used extensively Solutions for removal of TCH Assignment: Clear VSWR IF TRXs are faulty lock them and try to replace them soon to avoid blocking. Path Imbalance clear. Connection from BTS to Antenna Connector connection Check TMA. Check Duplexer,Combiner,TRXs connections, Multicoupler etc. Reports for TCH Assignment: ZEOL to check alarms 208 for path imbalance 196 for UL-DL interference ZAHP for Flick report

TCH Drop
Drop during conversation is known as TCH drop. It takes place after connect ACK msg on TCH.TCH drop occurring. For TCH drop first cross check the BCCH of that cell, hardware issue may be, change RXP* and RLT** value. Find out there is any interference, neighbor defined. Reasons for TCH Drop: Wrong Parameter Planning. BAD HOSR. Hardware Fault. High TR Fail. Overshoot. Outage. Due to Low Coverage. Due to ICM Band(CDMA) Solutions for removal of TCH Drop: Check Parameter: Check the BCCH Plan (C/I or C/A). Co-BSIC & Co BCCH. Check the Timer T 100(should be 20 ms)

Check Overshooting: If a cell is picking call from long distance, Check the sample log according to TA. Site Orientation. Effective tilt should be check. Mount position should be check Improve HOSR: Check the Hopping plan. Check the Neighbor Plan High TR Fail: Check and clear TR fail from oss end. Bad Coverage: If the drop call is due to low signal strength uplink, check the receive path of this particular TRX. Check receiver sensitivity, VSWR, feeder connection and etc. Drops due to Low Signal Strength. If the drop call reason is due to low signal strength downlink, then, check the transmit path. Check cards, feeder and etc. Use MapInfo or Google Earth to find location of sites. Effective tilt should be check. Mount position should be check. Check HW: Check Alarms on site. Check TRXs. Check Slips. Check the Hopping plan. Check BB2F card. Check VSWR, Path imbalance. Connector Connection. Check TMA Reports for TCH Drop: 163 for TCH Drop ZEOL for alarms. ZAHP for Flicks. 232 for TA report. 208 Path Imbalance report. 204 for BTS report. 216 for all parameter. 196 for UL-DL Qul. 62 for Adj cell having same or adj freq. NOTE: * Rxlev access min (RXP): With this parameter we define the minimum power level an MS has to receive before it is allowed to access the cell. Range: -110..-47 (dBm) Default: -105 **Radio link timeout (RLT): With this parameter we define the maximum value of the radio link counter expressed in SACCH blocks. Range: 4..64, with step size of 4 Default: 20

SDCCH Drop
When we assigned SD for call origination and at that time due to some problem or any mismatch comes by which SD loss occurs, it is called as SD Drop. It occurs between allocation of SD and before TCH allocation. Sometimes SD drop occurs because queuing is not activated in the system. If SD drop is high plz look on parameters likeovershooting, shift the SD timeslot , may be hardware issue, interference, change the values of RXP, PMAX, may be issue of uplink or downlink issue in that cells for UL put a TMA in that cell and for DL provide tilt ,re orient that antenna. If SD Drop is high: If SD drop is high plz look on parameters likeOvershooting Shift the SD time slot Hardware issue Interference Change the values of RXP PMAX It may be uplink or downlink issue in which cells for UL put a TMA in that cell and for DL provide tilt Re orient that antenna. Reasons of SD Drop: Hardware Fault. Interference. MAIO mismatch. Bad Coverage. High TR Fail. Outage. Overshooting. Abis Drop. High Path Loss. Wrong Parameter Planning. Due to ICM Band(CDMA) High LAPD Utilization Heavy blocking and DR feature being used extensively Solutions for removal of SD Drop: Interference: Check the BCCH Plan (C/I or C/A). Co-BSIC & Co BCCH. Use latest ND 111 and MapInfo to find out proper frequency to reduce interference. Arrange Drive Test: The best way to find the real issues for Interference makes DT. Check interference by Interference scanning. Check clean BCCH by frequency scanning. Overshooting: LAC Planning. If a cell is picking call from long distance,Check the sample log according to TA. Cell orientation need to be defined according to clutter.

Mount position Effective Tilt High TR Fail: Check and clear TR fail from OSS end. Bad Coverage: If the drop call is due to low signal strength uplink, check the receive path of this particular TRX. Check receiver sensitivity, VSWR, feeder connection and etc. Drops due to Low Signal Strength. If the drop call reason is due to low signal strength downlink, then, check the transmit path. Check cards, feeder and etc. Use MapInfo or Google Earth to find location of sites. High LAPD Utilization: Check LAPD util report from OSS, and define 32 kbps signaling instead of 16kbps. Hardware Fault: Check Alarms. TRX condition. Check Path Imbalance. VSWR of the Cell. Connector Connection. Some times you will find issues on BCCH TRX.In this case BCCH shift from one to other TRX will reduce SD drop. Check for parameter: Check the Timer T 3101 Check the Timer T 200(20ms) T11 Expired(10 s) MAIO check. Useful Reports for SD Drop: Use report ZEOL to find the alarms. Use 208 for Path loss analysis. Use 196 for UL-DL Interference. Use 163 report for SD drop. Use report 216 for detail SD Drop. 232 report for TA report. 62 for Adj cell having same or adj freq. ND 111 for freq plan. 204 for BTS and cell report.

Blocking and Congestion


Difference Between Blocking and Congestion: It is very important to know difference between blocking and congestion. Some people think that both are same, but they differ from each other. If all the SD resources are full and not available for SD assign then its come into congestion. If at a particular time call is attempted and it fails then itknown as Blocking.

SDCCH Blocking
SD blocking means that you are not getting SD resource for the call origination. When MS connects with NW then RACH and AGCH are provided. After AGCH,SDCCH is provided but if SDCCH is not provided at this time due some problems or due to unavailable of SD by BSC ,its called as SD Blocking. There are no of reasons for that.If such a case arises the customer will not be able to originate any call. Reasons for SD Blocking: Some of them areLAC boundary. HW Prob. Solutions for removal of SD Blocking: Here are some steps by which we can reduce SD Blocking1. Check the No. of SDCCH channel Available, if less then increase SD channel taking care that there is no TCH Blocking. 2. Check LAC boundary, If location update is more then change theLAC of that site and set C2 and HYS. 3. Use of Dynamic SDCCH (It is a BSC parameter and will be applied on whole BTS). 4. Hardware check / shift SD to new time slot. 5. Some times BMA and HYS parameters are useful to remove SDBlocking. Usefull Reports For SD Blocking: Use 182 to analyses SD Blocking reasons. 130 for SD congestion.

Handover Success Rate (HOSR)


If HOSR will be good TCH drop will also be good. If Handover success rate degrades call drop rate will take place. Reasons for Poor HOSR: Improper Neighbor planning. CO-BCCH-BSIC issues in Neigh. Parameter Check. HSN clash. SL value. LAC boundary. DAC value mismatch. Syn mismatch. Overshoot. HW Issues. Low Coverage Solutions for removal of HOSR: Arrange Drive Test: The best way to find the real issues for HO fail make DT and check layer 3 msg for HO fail. By DT it is very easy to find the fail between cells.

Neighbor Tuning: Try to retune neighbors Avoid CO-BCCH-BSIC neighbors. Avoid extra neighs. Delete long distance neighs. Check neighs are defined form both ends. If there are high fail delete and recreate neighs. Parameter Check: 1. Retune SL.It can change bw -90,-95,-105. 2. Check HSN. 3. Check SYN. 4. Retune LDR, LUR, IDR, IUR. 5. Retune LMRG, QMRG, PMRG. DAC value Check: Check DAC value. If DAC value is high or low tune it at the TH value. It should be 2050. Overshoot: When neighs are far away then chances of HO fail increases. In this case ping-pong HO takes place by which fail takes place. So if the inter distance is high its better to delete that kind of neighbour. LAC BoundaryCheck LAC boundry. High fail takes place there will be Inter BSC cells. High fail takes place there will be Inter MSC cells. Define proper LAC in neigh cells. HW Issues: Clear HW issues. Check TRXs. Check outages. Check BOIA Card. Because if it is faulty incoming and outgoing HO will be fail. Clear Reports: Clear ZEAT. Clear 60. Clear 67. Clear 61. Reports for HOSR : 153 reports for HO fail bw two cells. 154 HO analyses. 60 for discrepancy. 67 for Sync report. 61 for one way neigh. ZEAT for CO-BCCH-BSIC neighs 74 for HO definition report. ZELO for inter MSC HO report. 150 for high HO fail. 157 for high HO attempt and call ratio. 158 for intra BSS HO observation. 62 for Adj cell having same or adj freq.