Silent Call Analysis Guideline
January 2017
HUAWEI TECHNOLOGIES CO., LTD.
Contents
Cell/Node B issue Check
Performance data Analysis PCHR Analysis
Transmission Issue
RTWP Issue
coverage Issue
CDT/IOS Collect CDT/IOS Analysis
Device Issue
Performance/PCHR Analysis
Yes Yes
From PCHR
Analysis at whole network or RNC level Silent call rate > 0.5% Whether TOP cell cause Cell/Node B check
high Silent call rate
No No
1. Transmission
Good Check RNC parameter 2. RTWP
Check CN issue Need CN engineer 3. Poor coverage
analysis and check 4. Bad EC/NO
Silent Call counter explain
Silent call rate = ([Link] + [Link])/([Link] +
[Link])
The silent call recorded at RNC, when the lost frame rate or bad frame rate reached 20%, the 3G network will record silence count.
TOP Cell principle
Check 3 days KPI of silent call, if silent call rate > 1% and silent call number >30 as TOP cell which need deep analysis.
CDT/IOS data Analysis
1. UE Trace Principle silent call: ULTotalDataFrame continuously appear 3
Collect Trace Data 2. IOS Trace packages less than 10. Reason Check
Check call silent time
Silent call
1. Transmission
2. RTWP
Cell/Node B issue check 3. Poor coverage
4. Bad EC/NO
5. Device issue
CDT Trace collect method IOS Trace collect method
Trace - the message setting - message type - Select all Trace - the message setting - message type - Select all
UE Trace - UE - select Debug Mode IOS Trace - UE - Basic - select Debug Mode
UE Trace - Other - select Layer2 data transfer, L2 data report IOS Trace - UE - Basic - RAB - AMR
IOS Trace - UE - Other - select Layer2 data transfer, L2 data report
Cell/Node B issue Check
•IPPath drop rate > 2% Transmission Issue Fix transmission problem
Check the FFT and handle
•RTWP > -90 dBm High RTPW the interference issue
•RSCP < -100 dBm Poor coverage
RF tuning and propose
new site
•RSCP > -95 dBm and
Bad ECNO
EC/NO < -14 dB
Adjust parameter to avoid PERFENH_DLBLINDDETECT_WHEN_SRBAMRONDCH-0
Device issue Device issue CFG_DL_BLIND_DETECTION_SWITCH-0