Escolar Documentos
Profissional Documentos
Cultura Documentos
www.huawei.com
2.
3.
Abnormality of Equipment Clock/ DSP/CPU, Insufficient RAN Board Resources, Transmission Alarm.
5.
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.
4.
Configuration Inconsistency.
RRC.FailConnEstab.NoReply
VS.RAB.FailEstCS.RIPFail
2.
Equipment and Interface Problem.
VS.RAB.FailEstabCS.RNL, VS.RAB.FailEstabCS.TNL.
3.
Network Element and Interface Resource.
VS.RAB.FailEstCs.Power.Cong, VS.RAB.FailEstab.CS.DLIUBBand.Cong,
VS.RAB.FailEstab.CS.ULIUBBand.Cong, VS.RAB.FailEstCs.ULCE.Cong, VS.RAB.FailEstCs.DLCE.Cong,
VS.RAB.FailEstCs.Code.Cong
4.
5.
6.
Relocation Problem.
VS.RAB.FailEstCS.Relo
Capability Problem.
VS.RAB.FailEstCS.Unsp .
Setup redirection problem.
C. Methodology
The methodology to analyze Call Drop problem containing several step below:
1.
Data Preparation
2.
Traffic Analysis.
3.
Equipment Analysis.
4.
Coverage and Interference Analysis.
5.
Signalling Analysis
Hourly/Daily Statistic (CS RAB assignment failure per cell, RRC connection reject per cell, Cell TX and RX Power, etc).
The latest Site Map, Neighbor relation, and cell configuration/parameter data.
Single subscriber tracing recorded by RNC.
CHR recorded by RNC.
Active and History Alarm.
Data files collected by DT.
The Traffic analysis is related to CE utilization, IUB,IU Utilization, and Code Utilization. This Information we can get from the Daily/Hourly
Statistic.
The RRC Rejection Cause related to traffic utilization can we get in Raw counter below:
VS.RRC.Rej.UL.CE.Cong = UL CE utilization
VS.RRC.Rej.DL.CE.Cong = DL CE utilization
VS.RAB.FailEstCs.ULCE.Cong = UL CE Utilization
VS.RAB.FailEstCs.DLCE.Cong = DL CE Utilization
The Alarm information of RNC, Node b, MSS, MGW, and Interface(Transmission) can we gather as early diagnosis to reduce time if we
found Call Drop problem.
The History and Active Alarm can help to give quick reference for analyzing the network problem.
Alarms that affect access failure mainly include transmission alarms of the carrier signaling (E1/T1, SAAL,NCP/CCP, MTP3B, internal IPC
and AAL2PATH) and equipment alarms (clock, CPU, DSP, etc.). If such alarms occured, find out the causes and eliminate these alarms
thoroughly.
Radio network signaling includes signaling of four standard interfaces of UU, IU IUB and IUR. When an abnormality occurs in the signaling flow,
we can check which part of signaling flow is missing.
The missing of signaling flow should be correlated to UU,IUB,IU, and IUR interface problem.
According to single subscriber tracing messages, the call drop is defined as:
1)
RRC CONNECTION REQUEST FAILURE
- RNC Fails on receiving UL message of RRC CONNECTION SETUP COMPLETE.
2)
Check the call drop time and the signaling message before call drop for further analysis.
The Imsi trace tool with all interface message and monitoring kpi(CPICH RSCP, CPICH ECNO, UL SIR, UL TX PWR, and DL TX CODE POWER)
helping us distinguishing Call Fail Reason. The Call Fail related to Air Interface or not related to Air Interface problem.
10
It is Shows details of all calls based on output from Trace Management->Interface Trace Task->UE.
Provide convenient, PC-based analysis
1. Call Message Event
2. The downlink CPICH RSCP and ECNO Distribution.
3. UL SIR Distribution.
4. UE Tx Power distribution.
5. DL Tx Code Pwr
11
12
COMPLETE.
High UL TX PWR
Distribution
Bad UL SIR
Distribution
High DL TX CODE
POWER Distribution
Thank you