Scribd Logo
Upload

Welcome to Scribd!

  • 383 views

    NSN Alarm

    Uploaded by

    Rashed Sobuj
    The document discusses the alarm 7745_Mean holding time below threshold. It provides: 1) The definition of the alarm as a mean holding time on a channel being below the operator-defined minimum during the measurement period, which can indicate faulty channels. 2) Potential reasons for the alarm including hardware issues like BTS failures, RF issues like interference, and BSC/network issues like message distribution problems. 3) Steps for troubleshooting including checking for other degradation alarms, recommissioning the BTS, verifying RF parameters, and analyzing handover settings if there are many intracell handovers.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd

    NSN Alarm

    Uploaded by

    Rashed Sobuj
    383 views12 pages
    The document discusses the alarm 7745_Mean holding time below threshold. It provides: 1) The definition of the alarm as a mean holding time on a channel being below the operator-defined minimum during the measurement period, which can indicate faulty channels. 2) Potential reasons for the alarm including hardware issues like BTS failures, RF issues like interference, and BSC/network issues like message distribution problems. 3) Steps for troubleshooting including checking for other degradation alarms, recommissioning the BTS, verifying RF parameters, and analyzing handover settings if there are many intracell handovers.

    Original Description:

    NSN ALARM

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the alarm 7745_Mean holding time below threshold. It provides: 1) The definition of the alarm as a mean holding time on a channel being below the operator-defined minimum during the measurement period, which can indicate faulty channels. 2) Potential reasons for the alarm including hardware issues like BTS failures, RF issues like interference, and BSC/network issues like message distribution problems. 3) Steps for troubleshooting including checking for other degradation alarms, recommissioning the BTS, verifying RF parameters, and analyzing handover settings if there are many intracell handovers.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    383 views12 pages

    NSN Alarm

    Uploaded by

    Rashed Sobuj
    The document discusses the alarm 7745_Mean holding time below threshold. It provides: 1) The definition of the alarm as a mean holding time on a channel being below the operator-defined minimum during the measurement period, which can indicate faulty channels. 2) Potential reasons for the alarm including hardware issues like BTS failures, RF issues like interference, and BSC/network issues like message distribution problems. 3) Steps for troubleshooting including checking for other degradation alarms, recommissioning the BTS, verifying RF parameters, and analyzing handover settings if there are many intracell handovers.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    You are on page 1of 12

    Alarm 7743_ Mean holding time below threshold

    Contents
    Alarm Definition as per NED Reasons for Alarm Troubleshooting

    Alarm Definition as per NED :


    7745 MEAN HOLDING TIME BELOW DEFINED THRESHOLD Meaning :
    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 and to detect the possible faulty 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

    Reasons for Alarm


    Hardware Issues:
    BTS unit hardware failures (DTRX, TRX. DDU,BB2F,WCxA,DVxA) Crossed feeder cables. Bad SMA cables and RF cables used for connection between DTRX/DDU. RSSI values on the main and diversity paths are differing a lot. High VSWR

    RF Issues:
    BCCH Frequency used in MAL list Some segments in the network using same BCCH Frequency Value of TSC parameter is same as BCC value High Interference in the network. Large number of intracell handovers (AMR packing/unpacking, interference)

    BSC/Network Issues
    LAPD message distribution problem due to unused (floating) TRX signaling links on the BCSU concerned Telecom links overloading the BCSU Repeated Transmission Failures

    Troubleshooting
    1. Check the BTS alarms for presence of degradation alarms TRX FAULTY, 7745 Channel Failure rate above threshold, TRX Operation degraded etc. 2. Check the hardware showing that alarm and trouble shoot for the alarm as per NED. 3. Recommissioned particular BTS with RFCAD. 4. Make sure all the TRX test are passed during the commissioning. 5. Check for any High VSWR or RF feeder swapping in the sector. Once the troubleshooting for the BTS HW part is done and verified and all issues were addressed. Please start for the verification on RF part. 1. Check for alarm 7744: HIGH TCH INTERFERENCE showing high interference in the cell. 2. Verify for any adjacent cells having same BCCH frequency using ZEAT command. 3. Use ND reports and KPI data to for high UL interference and radio drops. 4. KPI analysis of the affected cells for large number of intracell handovers causing shorter duration TCH seizures.

    Troubleshooting
    Incase of large handover attempts in the segment follow following guidelines 1. Check the handover parameters in the cells for intracell handover thresholdsand margins. 2. Tune the TCH access parameters for 1800 band from 900 band i.e LAR,LER and NBL for segments. 3. Tune the FRL/FRU and LSEG parameters for TCH load distribution in both BTSs in Segment Note : Changes in the handover parameters should be done inconsultation with local RF team as per their recommendations

    Note
    MHT is the duration during which a MS is using the TCH in the cell. So if it is too short, it means either the calls are dropped as soon as the TCH is seize... or there is a HO taking place immediately. Check your drops and your outgoing HO : are they high ? If drops : HW problem, probably If HO : settings are done in such a way that HO are triggered quickly from this cell.

    The Mean Holding Time for TCH reflects the average duration of calls on traffic channel.
    formula: (Traffic * Time duration(s) ) / (Number of Calls + Incomming Handovers) This statistics is depending much more on users behaviors, it's not really reflect a specific problem in the cell. To be sure you need to correlate the MHT with drop call rate for example.

    Alarm7740_Means Beating BTS Alarm

    7740 Means Beating BTS alarm


    7740 means beating BTS alarm at Bsc end. At that time run a cmd at same Bsc ZEOL::NR=7740; <HIST> CALBSC01 BCF-0030 EQUIPM 2011-11-24 03:35:02.45 (45498) 7740 BEATING BTS ALERM 8081 00 00 B5 01 02 See it on the same bcf but remember one thing that I marked there bold and underline style. This is the CODE..8081 MEANS LOSS OF FRAME ALINGMENT. Now you have to do the activity on the basis of code what you find there. This alarm activated due to any alarm repeats more than 20 times in a minute. When you rectified the issue it's cancelled automatically after few hours later.

    Alarm_ 7745 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD

    CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD


    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, and to detect the possible faulty channels.

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy