This action might not be possible to undo. Are you sure you want to continue?
A. Call Fail Reason
The Call Fail Reason can be classified into several reason : 1. Coverage and Interference Problem.
• Coverage Hole and UL Interference. Missing neighbor, wrong setting of neighbor cell, improper setting of Qqualmin and Qrxlevmin. Low setting of preamble Power Ramp Step, Low setting for Common Channel. Low Setting of Initial SIR Target. Abnormality of Equipment Clock/ DSP/CPU, Insufficient RAN Board Resources, Transmission Alarm. High Cell Load, High CE Utilization, High IUB,IU CS/PS Utilization. Inconsistent Number of AAL2PATHs across IU/IUB Interface. PATH ID and NSAP Address Configuration Error of AAL2PATH.
Improper radio and neighbor parameter setting.
• • •
Equipment and Interface Problem.
Network Element and Interface Resource.
• • •
RRC.Power. 3.FailEstCs.Cong.Code.RAB.TNL. VS.RAB.Rej.RRC. • RRC.Rej. VS.FailEstCs.RAB.FailEstab.Cong.DLIUBBandCong.Cong.Fail(Iub problem).ULCE.Fail.RAB.RAB. VS.ULIUBBandCong.DLIUBBand. VS.RRC. VS. • VS.A. VS. • VS.RRC.RRC. Call Fail Reason Statistic Based The Call Fail Reason can be classified into several reason : 1.DLCE.RAB. Network Element and Interface Resource. Coverage and Interference Problem.FailEstabCS.RRC.CS.Code.RAB. VS.FailEstCs. Equipment and Interface Problem.Power.FailEstabCS.ULIUBBand.Rej.RL.Rej.RIPFail 2.RAB. VS. • VS.Rej.RRC.CS.Cong.FailConnEstab. • VS.Cong. VS.Cong.FailEstCs.Cong.FailEstCS.Rej.Rej.RAB.RNL.Cong. VS.Cong .UL.FailEstab.DL.Rej.NoReply • VS. VS.TNL. VS.CE.Cong.CE.RRC.
Inter. • VS. Relocation Problem.Unsp .FailEstCS.FailEstCS. 5.Reject.RRC.Rej.Intrat VS.RAB. • VS. Setup redirection problem.Att VS.Reject.Service.4. • VS.RRC. 6.RAB.Redir.RRC. .Relo Capability Problem.Redir.Redir.
. B. Call Fail Analysis Flow .
RRC connection reject per cell. 6 . Coverage and Interference Analysis. 5. Methodology The methodology to analyze Call Drop problem containing several step below: 1. Traffic Analysis. Equipment Analysis. and cell configuration/parameter data. Signalling Analysis C.1 Data Preparation • • • • • • Hourly/Daily Statistic (CS RAB assignment failure per cell. Cell TX and RX Power. The latest Site Map. Neighbor relation. CHR recorded by RNC. Single subscriber tracing recorded by RNC. Data files collected by DT.C. 3. 4. etc). Active and History Alarm. Data Preparation 2.
CE.DL.Rej.Cong = Cell Load – VS.DL/ULIUBBand.Cong = DL CE utilization – VS.RRC.RRC.Code.CS.DLCE.RAB.UL.RRC.Rej.Rej.RAB.FailEstab.C.RAB.RAB.RRC.ULCE.Cong = Code Utilization.2 Traffic Analysis • The Traffic analysis is related to CE utilization.RAB.FailEstCs.Cong = Code Utilization.FailEstCs.CE.FailEstCs. and Code Utilization.Rej.Cong = DL CE Utilization – VS. This Information we can get from the Daily/Hourly Statistic.Cong = UL CE utilization – VS.Cong = Iub utilization • • 7 . The RRC Rejection Cause related to traffic utilization can we get in Raw counter below: – VS.RRC.Rej. – VS.FailEstCs.Code.Power. The RAB Fail Cause related to traffic utilization can we get in Raw counter below: – VS.Cong = UL CE Utilization – VS.IU Utilization.Power.Cong = Cell Load – VS.DL/ULIUBBandCong = Iub utilization – VS. IUB.
inconsistency neighbor parameter. internal IPC and AAL2PATH) and equipment alarms (clock. and Interface(Transmission) can we gather as early diagnosis to reduce time if we found Call Drop problem. MSS. MTP3B.4 Coverage and Interference Analysis • • • • • The Threshold of CPICH RSCP <=-95 dBm consider as Poor Coverage.). If the downlink transmit power reaches the maximum before call fail and the downlink BLER is weak. SAAL.3 Equipment Analysis • • The Alarm information of RNC. and node b power amplifier failure. If the uplink transmit power reaches the maximum before call fail.NCP/CCP. Poor Coverage could be due to cross feeder. The History and Active Alarm can help to give quick reference for analyzing the network problem. etc. DSP.C. the call fail is probably due to poor downlink coverage. missing neighbor. If such alarms occured. CPU. UL Interference problem if RTWP is greater than 10 dB from normal value of normal RTWP value -103 to -107 dBm. find out the causes and eliminate these alarms thoroughly. Node b. neighboring sites down. the call fail is probably due to poor uplink coverage. MGW. Alarms that affect access failure mainly include transmission alarms of the carrier signaling (E1/T1. 8 . • C.
UL TX PWR.IU. IU IUB and IUR. and DL TX CODE POWER) helping us distinguishing Call Fail Reason.5 Signalling Analysis • Radio network signaling includes signaling of four standard interfaces of UU.C. • • 2) RAB ASSIGNMENT REQUEST FAILURE . 9 . CPICH ECNO. UL SIR.IUB.RNC Fails on receiving UL message of RRC CONNECTION SETUP COMPLETE. and IUR interface problem. The Call Fail related to Air Interface or not related to Air Interface problem.CN Fails on receiving UL message of RAB ASSIGNMENT RESPONSE • Check the call drop time and the signaling message before call drop for further analysis. the call drop is defined as: 1) RRC CONNECTION REQUEST FAILURE . The Imsi trace tool with all interface message and monitoring kpi(CPICH RSCP. The missing of signaling flow should be correlated to UU. According to single subscriber tracing messages. we can check which part of signaling flow is missing. When an abnormality occurs in the signaling flow.
Call Fail Analysis Guide Using Signalling IMSI Trace 10 .
5. PC-based analysis 1. UL SIR Distribution. 4. The downlink CPICH RSCP and ECNO Distribution. Provide convenient. 3. Call Message Event 2. DL Tx Code Pwr • 11 . UE Tx Power distribution.IMSI Trace on LMT • It is Shows details of all calls based on output from Trace Management->Interface Trace Task->UE.
UE Tx Power distribution. UL SIR Distribution. 4. 3. Call Message Event The downlink CPICH RSCP and ECNO Distribution. DL TX Code Pwr.Trace Viewer for Post Processing IMSI Trace Log 1. 1 2 3 4 5 12 . 5. 2.
RncId-Lac-Cell Id Identification • • Filter The Message by RANAP_LOCATION_REPORT/RANAP_INITIAL_UE_MESSAGE message.Call Message Event. Convert The HEX value into DEC value. .
Call Fail Message defined as: 1.CN Fails on receiving UL message of RAB ASSIGNMENT RESPONSE. 2. RRC CONNECTION REQUEST FAILURE . . .RNC Fails on receiving UL message of RRC CONNECTION SETUP COMPLETE. RAB ASSIGNMENT REQUEST FAILURE.Call Message Event.Call Fail Identification • • Synchronize the Time of Call Fail.
Call Message Event. The Serving ECNO is -14 to -13.5 dB.NoReply (RNC does not receive RRC CONNECT SETUP COMPLETE ) • • • Filter The Message by RRC_RRC_CONNECT_REQUEST. and RRC_RRC_CONNECT_SETUP_CMP. If No RRC_RRC_CONNECT_SETUP_CMP after RRC_RRC_CONN_SETUP.RRC.FailConnEstab. RRC_RRC_CONN_SETUP. .
Check All Trace Viewer KPI(RSCP.RAB SETUP FAIL(Failure in Radio Interface prcedure(14)) • • Filter The Message by RANAP_RAB_ASSIGNMENT_RESPONSE-raB-FailedList>cause>Disconnect->radioNetwork(14)Failure in Radio Interface Procedure. etc) and Alarm Issues.UL SIR. .ECNO.Call Message Event.
Bad RSCP and ECNO Distribution . If ECNO <=-12 dB and RSCP >=-80 dBm consider as DL Interference/Pilot Pollution.Coverage and Interference Analysis CPICH RSCP and ECNO • • • • The Breakdown from RF Problem. Drive Test for verification is needed. Check for missing neighbor and nearby Site problem. Checking CPICH and RSCP Distribution. If RSCP <=-95 dBm Consider as Poor Coverage.
Checking UL TX PWR Distribution. High UE TX PWR can be due to Excessive UL Coverage or High UL Interference. If UE TX PWR more than 5 dBm consider as high UE TX PWR. Max UE TX PWR is to 24 dBm. Check if any missing neighbor or nearby Site Problem. High UL TX PWR Distribution .Coverage and Interference Analysis UE TX POWER • • • • • The Breakdown from RF Problem.
5 dB.5 dB can be due to Excessive UL Coverage or High UL Interference. The SIR Target for this Services is -1.Coverage and Interference Analysis UL SIR • • • • The Breakdown from RF Problem. If The SIR Measured Less than -1. Checking UL SIR Distribution. Check any missing neighbor or neighbor Site Problem Bad UL SIR Distribution .
2 is equal to CPICH POWER (example 33dBm) . The TX CODE POWER MIN Value for this AMR 12. Check any missing neighbor or neighbor Site Problem.2 is equal to 18 dBm If The TX Code Power Reaching near to CPICH POWER can be due to Poor Coverage/Fringe Cell/DL Interference.Coverage and Interference Analysis DL TX CODE POWER • • • • • The Breakdown from RF Problem. High DL TX CODE POWER Distribution . The TX CODE POWER MAX Value for this AMR 12. Checking DL TX Code Power Distribution.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.