Scribd
Upload
636 views18 pages

Nokia 2G CSSR Troubleshooting

The document discusses troubleshooting 2G CSSR issues like SD blocking, SD drop, and TCH blocking in Nokia networks. It describes potential causes like insufficient SD channels, hardware problems, interference, and provides solutions like optimizing channel parameters, drive testing for interference, checking alarms and TRX health. Useful reports are listed to analyze SD congestion, drops, and adjacent cells. Common alarm triggers and corrective actions are also outlined.

Uploaded by

krida agustiono
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
636 views18 pages

Nokia 2G CSSR Troubleshooting

The document discusses troubleshooting 2G CSSR issues like SD blocking, SD drop, and TCH blocking in Nokia networks. It describes potential causes like insufficient SD channels, hardware problems, interference, and provides solutions like optimizing channel parameters, drive testing for interference, checking alarms and TRX health. Useful reports are listed to analyze SD congestion, drops, and adjacent cells. Common alarm triggers and corrective actions are also outlined.

Uploaded by

krida agustiono
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 18

Nokia 2G_CSSR Troubleshooting

2G CSSR MAJOR CONTRIBUTORS

• SD BLOCKING

• SD DROP

• TCH BLOCKING
Reasons for SD Blocking:

• Insufficient SD defined.(min=No of trx-1)


• High no of SD attempts -LAC boundary.
• Nearby site outages.
• Extreme end-user behaviors: Sport event ending, festivals or celebrations.
• HW Problems.
Solutions for removal of SD Blocking:
• Check the No. of SDCCH channel Available, Change No of SD channel through TSL
optimization.
• Check LAC boundary, If location update is High then LAC Resizing is suggested.
• CRO and HYS parameters are useful to remove SD Blocking-Boundary LAC.
• Use of Dynamic SDCCH (It is a BSC parameter and will be applied on whole BTS).
• Hardware check / shift SD to new time slot(healthy Trx).

Following reports can be used for SD Block analysis


• RSBSS130 for SD congestion.
Reasons of SD Drop
• Hardware Fault.
• Interference.
• Bad Coverage.
• Outage.
• Overshooting.
• High Path Loss.
• Due to IOI-Interference
SDCCH Drop Rate Analysis Based on Several Reasons

• If SDCCH_Radio_fail counter value is high it means drops going may be due to Overshooting,
interference , Phantom RACH etc.

• If 7745 Channel Failure Rate Alarm persist on SDCCH then Shift the SDCCH from that TRX to
another TRX.

• If SD Drop is high we can also change some parameters RXP, PMAX,


• SD Drop can also be high due to high UL or DL issue in that cell. For UL we can put TMA and for DL
we can provide tilt or re orient that antenna.
Solutions for removal of SD Drop:
Interference:
• Check the BCCH Plan
• Co-BSIC & Co BCCH.
Arrange Drive Test:
• The best way to find the real issues for Interference makes DT.
• Check interference by Interference scanning.
Bad Coverage:
• If the drop call is due to low signal strength uplink & LOW SIGNAL STRENGHT
DOWNLINK,CHECK VSWR, feeder connection and etc.
Hardware Fault:
• Check Alarms.
• TRX condition.
• 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.
Useful Reports for SD Drop:
• Use report ZEOL COMMAND to find the alarms.
• RSBSS232 report for TA report.
• RSBSS76 REPORT FOR ADJACENT CELLS WITH SAME NCC_BCC_FREQ
Reasons of TCH BLOCKING

• High Utilization of TCH


• Time slot faulty.
• HW Problem.
Optimization TCH Blocking
• If hardware problem exist then need to escalate to the NOC TEAM
• Increase dual Rate for reduce the TCH Blocking[TCHF TO TCHD & TCHH TO TCHD]
• Remove Extra SDCCH Channel and convert in to TCHD in case of high TCH Traffic to
reduce the blocking
• In case of Overshooting check RXP setting
• In case of very high traffic in clusters then we can reduce the power Traffic Sharing
• Add Extra TRX
• Optimize the cell boundaries to share the traffic with surrounding cells Traffic
• BLT (BTS Load Threshold) can also be increased from 70 to 90 value.

/
ALARM TROUBLESHOOTING
Contents

• Alarm Definition
• Alarm Causes
• Troubleshooting
Alarm Definition :

• CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD – 7745:

Alarm Description :

• The rate of calls terminating in failure on a channel is above the threshold value set by the operator. The alarm is used
to supervise the functioning of traffic and signaling channels.
• Parameters, with their default values, affecting the alarm:
• ZEEN:TCHFR = TCH failure rate (20 %)
• SCHFR = SDCCH failure rate (80 %)
• PRDCFR = length of supervision period (60 min)
• CS = channel seizure threshold value (10)
Alarm Definition :

MEAN HOLDING TIME BELOW DEFINED THRESHOLD- 7743:

Alarms Description :

• Mean holding time on a channel is below the operator-defined minimum during the measurement period. The alarm is used to
supervise the functioning of traffic channels.
• Parameters, with their default values, affecting the alarm:
• ZEEN:MINHTT = minimum mean holding time for a TCH (10 s)
• PRDMHT = length of TCH supervision measurement (120 min)
• CS = channel seizure threshold value
Supplementary information fields :
Alarm Causes/Triggering Points:

• Hardware Issues:

• BTS unit hardware failures (TRX, BB2F,WCxA,DVxA)


• Antenna line fault (either loose cable / connector between TRX <--> Combiner / Duplexer unit, too much
bending in the cables, Crossed feeder cables, high VSWR etc). Identified the affected TRX/sector and correct
the fault in the antenna system. There might be something on the antenna system which caused the dropped calls.
• High Cable Loss on the antenna system
• Other common causes - loose connector assembly, uptight connection between antenna lines and over bent or
damaged cables, faulty connector assembly etc
• Bad SMA cable , bad feeder quality or their improper connectivity.
• RSSI values on the main and diversity paths are differing a lot.
RF Issues:

• BCCH Frequency used in MAL list


• Some segments in the network using same BCCH Frequency
• Value of TSC parameter is different as BCC value
• High Interference caused in the network
• Less TRX cell (low traffic) we may have alarm rather due to TCH, because the CDEF territory is pushing CS
calls mainly to TSL2 and TSL3, therefore these TSLs can trigger alarm easily
• Interference may cause this alarm may be co-channel or adjacent channel interference, or surrounded by other
transmitting equipment.
• BCCH-BSIC discrepancy.
• The sites which are adjacent to a highway such that there is fast moving traffic generating a high level of
handover between sectors/adjacent sites. Or the site is in an area of marginal coverage and calls are rapidly
passed between sites.
Corrective Actions:

If all HW issues are addressed at Cell site/BSC then below actions can further help in improving situation,

7743 :

• Parameter Optimization (FRU and FRL)


• BSS21483 Improved AMR packing and unpacking feature implementation

7745:
• It is recommend to keep TSC=BCC to improve overall TCH drop in network & reduce 7745 Alarms
• Proper RF planning to avoid any inconsistencies and adjacent channel interference.

You might also like