Professional Documents
Culture Documents
4 GSM Call Drops (Influence Factors + Troubleshooting Methods and Tools + Deliverables) 20110730 (合作方版)
4 GSM Call Drops (Influence Factors + Troubleshooting Methods and Tools + Deliverables) 20110730 (合作方版)
4 GSM Call Drops (Influence Factors + Troubleshooting Methods and Tools + Deliverables) 20110730 (合作方版)
Security Level:
GSM Call Drop: Influence Factors + Troubleshooting Methods and Tools + Deliverables
Prepared by: Wang Zhicheng Approved by: Qi Haofeng
www.huawei.com
Huawei Confidential
Abstract
This slide provides the main factors that affect the GSM call drop rate, 14 standard actions required for troubleshooting call drops, and the methods for identifying the main factors that affect the GSM call drop rate, such as analyzing top N problem cells and call history records (CHRs). This slide also lists the required deliverables for reporting call drops, including the analysis results of top N problem cells and CHRs. In addition, this slide provides some representative cases, which indicate that it is significant for onsite engineers to analyze call drops according to the standard actions and call drops are mainly caused by common problems including inappropriate parameter settings, cross coverage, missing neighboring cells, interference, and indoor signal leakage.
Huawei Confidential
Change History
Date
2010-11-30
Version
Version issued in December 2010
Description
1. Added principles for selecting top N cells. 2. Added CHR analysis, including the instructions for analyzing CHRs by using the Nastar and Insightsharp. 3. Added common measures for optimizing call drops. 4. Added the checklist for troubleshooting call drops.
Reviewer
Yan Yafeng (employee ID: 37189), Zha Shuangliu (employee ID: 57469), Zhao Jinjin (employee ID: 105415), Ni Hongxiang (employee ID: 50324), Zhu Kan (employee ID: 137966), Chen Ruiqun (employee ID: 140495), Chen Kai (employee ID: 143018), Li Wenhui (employee ID: 146717), Jiang Ying (employee ID: 162124), Peng Xiang (employee ID: 119711), Chen Wei (employee ID: 119773) Qi Haofeng (employee ID: 118729), Si Fazhong (employee ID: 119461), Chen Wei (employee ID: 119773), Wang Fei (employee ID: 162184), Zhang Liang (employee ID: 51995), Zha Shuangliu (employee ID: 57469), Zhao Jinjin (employee ID: 105415), Shi Yuan (employee ID: 146349), Guo Hongliang (employee ID: 42533), Ni Hongxiang (employee ID: 50342), Zhu Kan (employee ID: 137966), Chen Ruiqun (employee ID: 140495), Chen Kai (employee ID: 143018), Li Wenhui (employee ID: 146717), Li Peng (employee ID: 52434), Liu Fang (employee ID: 58813), Jiang Xueyi (employee ID: 59075), Xun Lijun (employee ID: 54865), Wan Lu (employee ID: 51624), Wang Song (employee ID: 55188)
Author
Wang Zhicheng (employee ID: 151324)
2011-07-30
1. Added call drop analysis based on various data and required actions to focus on the procedure for analyzing call drops and the required data and tools. 2. Added the methods for identifying and troubleshooting call drops caused by other factors. 3. Added the required actions for troubleshooting call drops. 4. Added the impacts of parameter settings from other vendors on call drops and related cases. 5. Added the impacts of traffic sharing on a dual-band network or a network configured with the co-BCCH on call drops and related cases. 6. Added the impact of seasonal changes in KPIs on call drops and related cases.
7. Added the cases of optimizing the top N cells where call drops occur.
Huawei Confidential
Telephone Number See the telephone book. See the telephone book.
Huawei Confidential
Page 4
Huawei Confidential
Page 5
A call drops when it is terminated abnormally. For example, a call is terminated because the BSC or the MS releases the TCH due to an exception. Call drop measurement: When receiving a Connection Failure or an Error Indication message from the BTS, the BSC sends the Clear Request message to the MSC and measures one call drop in a corresponding performance counter based on the cause value.
MS
BTS
BSC
MSC
Clear request
Calculate call drop counter
Call drop measurement during drive tests (DTs): The BSC measures one normal call release when the Disconnect or Channel Release message is received during a DT call. Only when the BSC receives neither of the preceding messages and the MS enters idle mode from the dedicated mode, the BSC measures one call drop.
Page 6
Huawei Confidential
The BSC measures call drops by cause, which facilitates call drop type identification and cause analysis. In normal cases, most call drops are caused by Um interface problems, and therefore you need to focus on these call drops. Call drops caused by Um interface problems are measured as CM33C and classified into call drops in the stable state and call drops due to handovers. Call drops due to other causes seldom occur and are easy to locate. You need to focus on only CM334 and CM333. You need not pay attention to call drops caused by loop back because loopback is seldom used on the network. CM33:CELL_TRAF_CH_CALL_DROPS
Huawei Confidential
Page 7
Call drops caused by Um interface problems are classified into call drops in the stable state and call drops due to handovers. Call drops in the stable state: You need to focus on CM3300 and CM3301. In normal cases, most call drops in the stable state are measured as CM3301. Call drops due to handovers: In normal cases, the percentage of inter-cell handovers is high. Therefore, most call drops due to handovers are measured as H3127Ca and H3128Ca. By analyzing the percentages of various call drops, you can determine whether the call drop problem is caused by a certain reason. If the call drops of a specific type whose percentage is generally low increase, you need to focus on these call drops.
Huawei Confidential
Page 8
Huawei Confidential
Page 9
Call Drop Problem Overview Cause Analysis and Data Processing Actions and Deliverables Required for Troubleshooting Call Drops
Huawei Confidential
Page 10
Step 1: Determine the scope of the call drop problem by analyzing performance dataor CHRs. The scope of the call drop problem can be top N cells, entire network, top N cells+entire network, top N MS types, or top N subscribers.
NOTE 1: The methods for determining the scope of the call drop problem vary according to scenario. If the call drop rate increases after network swapping or upgrade, you need to compare the performance dataor CHRs before and after the network swapping or upgrade. If the call drop rate on a network is always high and cannot meet the requirement, you need only to analyze the current performance dataor CHRs. NOTE 2: performance dataare generally used to determine whether the scope of the call drop problem is top N cells, entire network, or top N cells+entire network. If call drops occur because certain types of MSs are used or only calls of certain subscribers drop, you need to analyze CHRs.
Step 2: Analyze call drop causes based on various data. Step 3: Take required actions according to the checklist to analyze root causes of call drops and determine how to troubleshoot call drops.
NOTE: The required actions for analyzing call drops are described in the next section.
Step 4: Troubleshoot call drops and evaluate the result. If the call drop problem is not resolved, repeat step 1 through step 4.
Huawei Confidential
Page 11
Principle for Analyzing Call Drops: Analyze Data, Provide a Conclusion, and Determine the Next Action
You can take most required actions by using tools, which facilitate the analysis of data such as traffic statistics, CHRs, neighboring cell data, parameters, alarms, and radio frequency (RF) channel data. Based on the analysis result, you can determine how to troubleshoot the call drop problem. When troubleshooting the call drop problem, focus on the main cause so that the problem can be resolved as soon as possible.
1. Determine the scope of the call drop problem
3-1. Take the required actions for analyzing the call drop problem and provide a conclusion or a temporary conclusion on root causes
3-2. Provide solutions and determine how to troubleshoot the call drop problem
4-1. Troubleshoot the call drop problem by troubleshooting the main causes first and then other causes
No
Yes
4-3. Provide a summary report and cases
Huawei Confidential
Page 12
Determining the Scope of the Call Drop Problem Methods for determining top N cells, top N
MS types, or top N subscribers
The methods for determining top N cells, top N MS types, and top N subscribers vary according to the scenario where call drops occur. Scenario 1: The call drop rate increases abruptly because of unknown reasons after network swapping or upgrade. Method for determining top N cells: Calculate the difference in the call drop rates and the difference in the numbers of call drops during a specified time range when the call drop KPIs deteriorate for each cell. Rank cells according to the differences in the call drop rates in descending order to obtain the top N cells with increased call drop rates and rank cells according to the differences in the numbers of call drops in descending order to obtain the top N cells with increased numbers of call drops. The methods for determining top N MS types and top N subscribers are similar to that for determining top N cells. Scenario 2: The call drop rate in the current network does not meet the requirement all the time. Method for determining top N cells: Rank cells according to the call drop rates in descending order to obtain the top N cells with high call drop rates and rank cells by the numbers of call drops in descending order to obtain the top N cells with large numbers of call drops. The methods for determining top N MS types and top N subscribers are similar to that for determining top N cells.
Huawei Confidential
Page 13
Top N cells: After 20% of top N cells with high call drop rates and top N cells with large numbers of call drops are ignored, the call drop rate of the entire network improves significantly and becomes similar to the call drop rate before the call drop KPIs deteriorate, or the call drop rate of the entire network meets the requirement. Entire network: After 20% of top N cells with high call drop rates and top N cells with large numbers of call drops are ignored, the call drop rate of the entire network does not improve. Top N cells+entire network: After 20% of top N cells with high call drop rates and top N cells with large numbers of call drops are ignored, the call drop rate of the entire network improves but is still higher than the call drop rate before the call drop KPIs deteriorate and does not meet the requirement. Top N MS types or subscribers: After 20% of top N types of MSs or 20% of top N subscribers with high call drop rates are ignored, the call drop rate of the entire network improves significantly and becomes similar to the call drop rate before the call drop KPIs deteriorate, or the call drop rate of the entire network meets the requirement. NOTE: The MS compatibility problem usually occurs during network swapping. However, CHRs or data similar to CHRs on the original network may be unavailable. In this case, you need to pay attention to subscriber complaints and check whether subscribers complain about call drops.
Huawei Confidential
Page 14
Traffic statistics
CHRs
Signaling DT data
Huawei Confidential
Page 15
By analyzing traffic statistics, you can identify call drops caused by Um interface problems (call drops in the stable state and call drops caused by handovers) and call drops caused by device faults (call drops caused by transmission faults and device faults). You can also further identify call drops caused by the Um interface problems such as low levels and poor transmission quality. However, you cannot identify call drops caused by core network (CN) problems by analyzing traffic statistics. Provide the R&D personal with the performance statistical report obtained by analyzing performance datausing tools.
Huawei Confidential
Page 16
Call Drop(RF Cause) TCH(TA) 0.00% TCH(Uplink Received Level) 81.82% TCH(Downlink Received Level) 0.00% TCH(Uplink and Downlink Received Level) 0.00% TCH(Uplink and Downlink FER) 0.00% TCH(Uplink Quality) 0.00% TCH(Downlink Quality) 9.09% TCH(Uplink and Downlink Quality) 0.00% TCH(Other) 9.09%
Huawei Confidential
Page 17
Analyzing CHRs
CHR is a call history record, which logs the detailed information about each call. By analyzing CHRs using the Nastar, you can identify call drops caused by CN problems (do not affect call drop KPIs), Um interface problems, and transmission and device faults and further identify call drops caused by the Um interface problems.
Call Drop Caused by the Um Interface Problems Call Drops on TCH(TA) Call Drops on TCH(Uplink Received Level) Call Drops on TCH(Uplink Interference) Call Drops on TCH(Uplink Received Level Suddenly Decrease) Call Drops on TCH(Uplink Quality) Call Drops on TCH(Downlink Received Level) Call Drops on TCH(Downlink Interference) Call Drops on TCH(Downlink Quality) Call Drops on TCH(Downlink Received Level Suddenly Decrease) Call Drops on TCH(Uplink and Downlink Received Level) Call Drops on TCH(Uplink and Downlink Interference) Call Drops on TCH(Uplink and Downlink Quality) Percentage Times 2.17% 5 41.30% 95 3.04% 7 0.00% 39.13% 2.17% 1.30% 10.87% 0.00% 0.00% 0.00% 0.00% 0 90 5 3 25 0 0 0 0
Huawei Confidential
Page 18
Huawei Confidential
Page 19
By analyzing signaling and single-subscriber CHRs, you can identify the call drop causes based on the signaling procedures and measurement reports (MRs). Abis signaling can be traced by cell. That is, you can trace the Abis signaling all calls in a cell. Single-subscriber signaling contains all information about the calls of a single subscriber. CHRs log the information about all historical calls but contain limited MRs. By analyzing the signaling traced over the Abis interface, you can identify the cause of a call drop based on the messages related to call drops and the level and quality information in MRs. By analyzing the single-subscriber signaling and CHRs, you can identify the call drop causes of a single subscriber.
Huawei Confidential
Page 20
Use the Traffic Recording Review tool on the local maintenance terminal (LMT) to display the signaling of a single subscriber and analyze the signaling procedure and the level and quality information in the MRs. Use the Insightsharp to display the CHRs of a single subscriber, the detailed call signaling, and ten MRs generated before call drops and analyze these data. Use the PFMStudio to analyze the signaling traced over the Abis interface. Select the path where the Abis signaling file to be analyzed is saved and click RUN. The PFMStudio automatically export files with the signaling related to one call drop saved in one file. All the files are saved to the out directory in the path for saving the Abis signaling file. Click Icon Display and perform signaling analysis.
Huawei Confidential
Page 21
Analyzing DT Data
DT data contains only the downlink information about a single subscriber. Therefore, you can analyze the DT data together with the single-subscriber signaling to identify the call drop causes. You can perform DTs in top N cells or top N areas to identify call drop causes.
DT call drops
Handover parameters
Interference problems
Cross coverage
Terminal problems
Due to missing configuration of neighboring cell relationships, handovers cannot be triggered in time. Due to redundant neighboring cell relationship, inappropriate handovers occur. This, then, causes call drops.
Due to inappropriate configuration of handover parameters, handovers cannot be triggered in time or inappropriate handovers occur. This, then, causes call drops.
Due to cofrequency/adjacent -frequency interference, internetwork interference, or intermodulation interference of equipment, call drops due to bad quality occur.
Due to the geographical location and terrain of the site, cross coverage is caused and then call drops occur.
Because some terminals do not analyze the levels and BSICs of neighboring cells in time, handovers cannot be triggered in time. This, then, causes call drops.
Huawei Confidential
Page 22
Tools: TEMS and Probe. The TEMS or Probe can play back DT data such as level, quality, and signal noise ratio and presents the DT data explicitly on the GUI.
By analyzing the DT data, you can identify the call drop causes.
DT data can provide more downlink information such as the BA2 list than signaling and traffic statistics.
Huawei Confidential
Page 23
Huawei Confidential
Page 24
Principle for Analyzing Call Drops: Analyze Data, Provide a Conclusion, and Determine the Next Action
You can take most required actions by using tools, which facilitate the analysis of data such as traffic statistics, CHRs, neighboring cell data, parameters, alarms, and radio frequency (RF) channel data. Based on the analysis result, you can determine how to troubleshoot the call drop problem. When troubleshooting the call drop problem, focus on the main cause so that the problem can be resolved as soon as possible.
1. Determine the scope of the call drop problem 2. Analyze the call drop causes
3-1. Take the required actions for analyzing the call drop problem and provide a conclusion or a temporary conclusion on root causes
3-2. Provide solutions and determine how to troubleshoot the call drop problem
4-1. Troubleshoot the call drop problem by troubleshooting the main causes first and then other causes
No
Yes
4-3. Provide a summary report and cases
Huawei Confidential
Page 25
The causes of call drops are complicated. Currently, a checklist containing 14 check items is available for identifying call drop scopes and causes, including top N problem cells, top N causes, and combination of some causes. You are advised to perform analysis according to the checklist.
Huawei Confidential
Page 26
1. Check results.
2. Solutions and measures for rectifying the 2. Provide a summary report and RF tunnel faults. cases. 1. Check results. 1. Rectify the device faults and clear the alarms.
Check for device faults and alarms by referring to the GSM Parameters Check theme and output the check results. Check the reasonableness and consistency of parameter settings by referring to the GSM Parameters Check theme and output the check results. Check for BTS or BSC version differences and parameter differences by referring to the GSM Parameters Check theme and output the check results and impacts of the differences. Check the parameter settings and versions of the devices that are from other vendors and in the boundaries of the areas served by the devices from other vendors by referring to the GSM Parameters Check theme and output the check results.
2. Solutions and measures for rectifying the 2. Provide a summary report and device faults and clearing the alarms. cases. 1. Check results. 2. Solutions and measures for optimizing parameter settings. 1. Check results and impacts of the differences. 2. Solutions and measures for optimizing parameter settings and BTS or BSC versions. 1. Inappropriate parameter settings of the devices from other vendors. 2. Solutions and measures for optimizing the parameter settings. 1. Optimize parameter settings. 2. Provide a summary report and cases. 1. Optimize parameter settings. 2. Optimize BTS or BSC versions 3. Provide a summary report and cases.
Check for BTS or BSC version differences and parameter differences Check the parameters of the devices from other vendors in the boundaries of the areas served by the devices from other vendors
Huawei Confidential
Page 27
Deliverable
1. Coverage evaluation results of problem areas and solution for optimizing RF coverage. 2. Check result of power matching accuracy and solution for optimizing the power matching. 3. Analysis results of the information about new sites, removed sites, and changed sites and changes in RF parameter settings, impacts of these changes, and solution for optimizing RF coverage.
Subsequent Action
2. Check power matching after network swapping by referring to the GSM Parameters Check theme and the guide to checking power matching and output the check results. Pay attention to common problems such as combiner and tower-mounted amplifier (TMA) faults.
3. After network swapping or network expansion, obtain and analyze the information about new sites, modified sites, and changed sites and the changes in RF parameter settings and output the impacts of these changes.
1. Optimize power matching. 2. Optimize RF coverage 3. Provide a summary report and cases.
Analyze neighboring relationships (for newly deployed sites and areas where Huawei devices are interconnected to devices from other vendors)
1. Analyzing neighboring relationships by referring to the GSM Neighboring Cell Optimization theme and output the analysis results. 2. After network swapping or network expansion, check whether neighboring relationships need to be adjusted by analyzing site changes and output the analysis results.
1. Analysis results of neighboring relationships, such as missing neighboring cells and redundant neighboring cells. 1. Optimize neighboring relationships. 2. Conclusion in inheriting or adjusting neighboring relationships 3. Solutions for optimizing neighboring relationships. 1. For call drops caused by reasonable changes in traffic and KPIs, provide an analysis report to explain the problem objectively to the customer and provide suggestions on how to resolve the problem. For call drops caused by unreasonable changes in traffic and KPIs, troubleshoot the traffic and KPI problems. 2. Optimize traffic distribution in special scenarios such as a dual-band network and a network configured with the co-BCCH. 3. Provide a summary report and cases. 2. Provide a summary report and cases.
Analyze changes in traffic and KPIs in special scenarios (networks supporting GSM900 and DCS1800 and configured with coBCCH)
1. Analyze the changes in traffic and KPIs and output the analysis results and the impacts of these changes. 2. In a network supporting GSM900 and DCS1800 and configured with the co-BCCH, check the difference in call drops and traffic distribution between GSM900 and DCS1800 and between the overlaid subcell and underlaid subcell.
1. Changes in traffic and KPIs and impacts of these changes. 2. Changes in traffic and KPIs in special networking scenarios such as a dual-band network and a network configured with co-BCCH and the impacts of these changes.
Huawei Confidential
Page 28
3. Provide a summary report and cases. 1. Analysis results of the frequencies used on 1. Analyze the frequencies used on the current network the current network, evaluation result of the and evaluate the frequency replanning gain by referring frequency replanning gain, and solutions and to the GSM Frequency Replanning theme and output the measures for replanning frequencies or analysis and evaluation results. 1. Replan or optimize frequencies. optimizing frequencies. 2. Analyze whether there is internal and external interference and output the analysis results. 3. After network swapping or expansion, analyze whether frequencies are inherited or replanned and output the conclusion. 2. Eliminate interference. 2. Interference analysis results and measures for eliminating interference. 3. Provide a summary report and cases. 3. Conclusion in inheriting or adjusting frequencies and solutions and measures for optimizing frequencies. 1. For a reasonable increase in call drops caused by emergence events, prepare an analysis report to explain the problem objective to the customer and provide suggestions. 2. For an unreasonable increase in call drops caused by emergence events, troubleshoot the problem.
Check for abrupt events such as charging policy Analyze the impacts of abrupt events on call drops and changes, weather output the analysis results. changes, and mass gatherings 1. Analyze CHRs and output top N subscribers whose calls drop, top N cells where call drops occur, top N call drop causes, and characteristics of call drop causes (especially the percentage of call drops caused by disordered serial numbers). 2. Analyze the causes of the call drops that subscribers complain by analyzing CHRs and output analysis results.
Huawei Confidential
Page 29
1. Top N types of call drops and causes. In special scenarios such as network swapping, analyze 2. Subsequent actions to be taken. CHRs to determine whether calls initiated by certain types of MSs or certain subscribers always drop. Check the reasonableness and consistency of parameter 1. Check results. settings by referring to the GSM Parameters Check 2. Solutions and measures for optimizing theme and output the check results. parameter settings.
Take required actions according to the top N types of call drops and causes.
1. Check results and impacts of the Check for BTS or BSC version differences and parameter differences. differences by referring to the GSM Parameters Check 2. Solutions and measures for optimizing theme and output the check results and impacts of the parameter settings and BTS or BSC differences. versions.
1. Optimize parameter settings. 2. Optimize BTS or BSC versions 3. Provide a summary report and cases.
Analyze changes in traffic and KPIs in special scenarios (networks supporting GSM900 and DCS1800 and configured with coBCCH)
1. For call drops caused by reasonable changes in traffic and KPIs, provide an analysis report to explain the 1. Changes in traffic and KPIs and impacts 1. Analyze the changes in traffic and KPIs and output the problem objectively to the customer and provide of these changes. analysis results and the impacts of these changes. suggestions on how to resolve the problem. For call drops 2. Changes in traffic and KPIs in special caused by unreasonable changes in traffic and KPIs, 2. In a network supporting GSM900 and DCS1800 and configured with the co-BCCH, check the difference in call networking scenarios such as a dual-band troubleshoot the traffic and KPI problems. network and a network configured with codrops and traffic distribution between GSM900 and 2. Optimize traffic distribution in special scenarios such as DCS1800 and between the overlaid subcell and underlaid BCCH and the impacts of these changes. a dual-band network and a network configured with the subcell. 3. Solutions and measures. co-BCCH.
3. Provide a summary report and cases. Analyze the correlation between the traffic changes in CS and PS services and the number of call drops and output 1. Traffic changes in CS and PS services the traffic changes and the impacts of the changes, including the changes in the proportions of data and CS and the impacts of the changes. services, change causes, and the correlation between the 2. Solutions and measures. traffic changes in data and CS services and the number of call drops. 1. For call drops caused by reasonable traffic changes in CS and PS services, provide an analysis report to explain the problem objectively to the customer and provide suggestions on how to resolve the problem. 2. For call drops caused by unreasonable traffic changes in CS and PS services, troubleshoot the traffic problems. 3. Provide a summary report and cases.
Huawei Confidential
Page 30
3. After network swapping or expansion, analyze whether frequencies are inherited or replanned and output the conclusion. Check for abrupt events such as charging policy changes, weather changes, and mass gatherings
Analyze the impacts of abrupt events on call drops and output the analysis results.
Analyze the longterm traffic trends due to seasonal changes and subscriber number increase
Obtain the long-term trends of traffic and KPIs, analyze whether the trends are consistent with the trend of the call drop rate, and output the analysis results.
1. Correlation between the long-term trends of traffic and KPIs and the trend of the call drop rate. 2. Solutions and measures.
Take required actions according to the top N types of call drops and causes.
Huawei Confidential
Page 31
Call Drops in Top N Cells and on the Entire Network Required Action Checklist
See the required action checklists for call drops in the top N cells and on the entire network.
Huawei Confidential
Page 32
1. Analyze the call drop scope and causes based on various data such as traffic statistics, signaling, DT data, alarms, parameter settings, and CHRs. 2. Take required actions to further analyze the call drop causes.
By using the following types of data analysis templates, you can quickly identify call drop causes and further identify the causes by taking the required actions:
1. Templates for identifying call drop causes 2. Templates for providing supplementary information for call drop analysis
The following attached excel describes the common templates for analyzing the call drop problem:
Huawei Confidential
Page 33
There are four types of templates for identifying call drop causes: Performance statistical analysis: 1. Templates for identifying the call drop scope (top N cells, entire network, or top N cells+entire network) 2. Template for identifying the causes of call drops that occur in the top N cells and on the entire network CHR analysis: 3. Templates for identifying the call drop scope (top N MS types or top N subscribers) 4. Template for identifying the causes of call drops that occur on top N types of MSs and top N subscribers.
Huawei Confidential
Page 34
Templates for Providing Supplementary Information for the Call Drop Analysis Channel and Frequency Analysis
Common performance counters in RF tunnel and frequency analysis are:
Rate of Outgoing Handovers and Incoming Handovers (100% x (Outgoing Handovers/Incoming Handovers)) Rate of Good RxLev and Bad HQI on Downlink(Downlink Receive Level Rank 5~7, and Downlink Receive Quality Rank 6~7) Rate of Uplink-and-Downlink Imbalance(Downlink)(Uplink-and-Downlink Balance Level 1~2) Rate of Uplink-and-Downlink Imbalance(Uplink)(Uplink-and-Downlink Balance Level 10~11) Rate of Uplink Interference(Rate of Uplink Interference Band 4~5) Rx Level Difference between Main and Diversity Antenna(Average Main Level in the Customized MR-Average Diversity Level in the Customized MR)
If the scope of the call drop problem is top N cells, analyze the preceding performance counters of the top N cells. If the scope of the call drop problem is entire network or top N cells+entire network, rank cells in the entire network by each of the preceding performance counters to identify problem cells and analyze the problem cells on the entire network.
Huawei Confidential
Page 35
Templates for Providing Supplementary Information for the Call Drop Analysis Device Fault Analysis
Common performance counters in device fault analysis are:
TRX Usability(Abnormal Condition:<100%) TCH Availability(Abnormal Condition:<100%) Cell Out-of-Service DuRaten(BCCH Fault)(Abnormal Condition:>0) Rate of CHAN_ACTIV Failure(Abnormal Condition:>0%) Traffic Volume(Abnormal Condition:=0) Outgoing or Incoming Handover Requests(Abnormal Condition:=0) Channel Requests(Abnormal Condition:=0) If the scope of the call drop problem is top N cells, analyze the preceding performance counters of the top N cells. If the scope of the call drop problem is entire network or top N cells+entire network, rank cells in the entire network by each of the preceding performance counters to identify problem cells and analyze the problem cells on the entire network.
Huawei Confidential
Page 36
Templates for Providing Supplementary Information for the Call Drop Analysis Coverage Analysis
Common performance counters in coverage analysis are: Rate of Weak Received-Power on Downlink(Downlink Receive Level Rank 0~2) Rate of Weak Received-Power on Uplink(Uplink Receive Level Rank 0~2) Rate of Bad HQI on Downlink(Downlink Receive Quality Rank 6~7) Rate of Bad HQI on Uplink(Uplink Receive Quality Rank 6~7) Rate of MRs (Weak Coverage) Rate of MRs (Excessive Coverage) If the scope of the call drop problem is top N cells, analyze the preceding performance counters of the top N cells. If the scope of the call drop problem is entire network or top N cells+entire network, rank cells in the entire network by each of the preceding performance counters to identify problem cells and analyze the problem cells on the entire network.
Huawei Confidential
Page 37
Templates for Providing Supplementary Information for the Call Drop Analysis Neighboring Cell Analysis
Common performance counters in neighboring cell analysis are: Proportion of Call Drop Rate Due to Handover Success Rate of Outgoing Internal Inter-Cell Handovers Success Rate of Incoming Internal Inter-Cell Handovers Success Rate of Outgoing External Inter-Cell Handovers Success Rate of Incoming External Inter-Cell Handovers Success Rate of Internal Intra-Cell Handover, Handover Density ((Outgoing Handovers + Incoming Handovers)/Traffic Volume) Rate of Outgoing Handovers and Incoming Handovers (100% x (Outgoing Handovers/Incoming Handovers)) If the scope of the call drop problem is top N cells, analyze the preceding performance counters of the top N cells. If the scope of the call drop problem is entire network or top N cells+entire network, rank cells in the entire network by each of the preceding performance counters to identify problem cells and analyze the problem cells on the entire network.
Huawei Confidential
Page 38
Templates for Providing Supplementary Information for the Call Drop Analysis Traffic and Abrupt Event Analysis
To analyze call drops caused by traffic changes and abrupt environment changes, analyze the trend of the call drop rate and the following performance counters: call drop rate, traffic volume, call setup performance counters, handover performance counters, coverage performance counters, device status performance counters, channel and frequency performance counters, and neighboring cell performance counters. If the scope of the call drop problem is top N cells, analyze the preceding performance counters of the top N cells. If the scope of the call drop problem is entire network or top N cells+entire network, analyze both the preceding performance counters and the trend of the call drop rate.
Huawei Confidential
Page 39
Templates for Providing Supplementary Information for the Call Drop Analysis Dual-Band Network/Overlaid and Underlaid Subcell Analysis
For a dual-band or an enhanced dual-band network configured with overlaid and
underlaid subcells, analyze and compare the call drop and traffic counters of the bands and overlaid and underlaid subcells to determine whether the call drop problem can be resolved by optimizing networking or parameter settings.
Huawei Confidential
Page 40
Principle+Tools+Cases+Deliverables 20110730.PPT.
Huawei Confidential
Page 41
[Data Analysis] 1. Template for analyzing RF tunnels and frequencies 2. Template for ranking cells by Rate of Good RxLev and Bad HQI on Uplink 3. Template for ranking cells by Rate of Good RxLev and Bad HQI on Downlink 4. Template for ranking cells by Rate of Uplink-and-Downlink Imbalance(Downlink) 5. Template for ranking cells by Uplink-and-Downlink Imbalance(Uplink) 6. Template for ranking cells by Uplink Interference 7. Template for ranking cells by Rx Level Difference between Main and Diversity Antenna 8. Template for ranking cells by the mean signal strength difference between the serving cell and the neighboring cell
[Data Analysis] 1. Cross connections between cells: Perform DTs to check whether the connections between the main of a cell and the antenna of another cell are cross connection and check the order of wires. 2. Antenna misconnections between cells: Perform DTs along the direction of the major lobe in the cells under possible problem [Data Analysis] sites to check whether the BCCH of the major lobe in each cell is the same as the Alarm list planned BCCH. [Characteristics] 3. Interference caused by antenna intermodulation: Conduct the start idle The voltage standing timeslot test and stop idle timeslot test on wave radio (VSWR) the LMT during off-peak hours and compare alarm is reported. the interference band information carried in Abis signaling before and after idle timeslots are sent. If the interference increases after idle timeslots are sent (the interference band levels increase to 3 to 5), there is interference from the antenna system of the BTS. [Tools] DT software and IntferBandAnalyse
Analysis templates [Characteristics] and 1. The difference between the receive level of the main and the receive level of characteristi the diversity is great. cs 2. The uplink and the downlink are imbalanced. (Proportion of uplink and downlink imbalance level 1 + Proportion of uplink and downlink imbalance level 2) > 15% (poor downlink or good uplink) or Proportion of uplink and downlink imbalance level 11 > 30% (good downlink or poor uplink) 3. The proportion of interference band levels 3 to 5 is high in a specific time period or a day. 4. The proportion of call drops caused by poor HQIs is high. 5. The mean signal strength difference between the serving cell and the neighboring cell is less than 0. [Tools] PRS, OMStar, and DownlinkAnalyse
Huawei Confidential
Page 42
Huawei Confidential
Page 43
Triggering conditions: 1. Check all parameters on the entire network if call drops occur after the network structure or traffic changes because of the following causes: CN parameter adjustment, 2G or 3G service adjustment, parameter adjustment on the entire network during network swapping, and network deployment, network upgrades, and timer or soft parameter adjustment 2. Check all parameters for some sites in an area or at the boundaries of areas served by the devices from other vendors if call drops occur after the network structure or traffic changes because of the following causes: network expansion, network reparenting, part parameter adjustment, coverage adjustment, and adjustment of the boundaries of areas served by the devices from other vendors. 3. If the network structure or traffic does not change, check and optimize core parameters during routine call drop optimization. If the call drop problem persists after the core parameters are optimized, check all parameters.
Huawei Confidential Page 44
[Data Analysis]
1. Template for analyzing call drop scopes
[Data Analysis]
1. Check and optimize parameter settings.
Perform DTs in the coverage of the following areas to check 2. Template for analyzing the distribution of call whether call drops are caused drop causes 2. Check and optimize parameter by inappropriate parameter relationships. settings: top N cells, boundaries 3. Template for analyzing the correlation of areas served by the devices between the trend of CS or PS service traffic 3. Check whether parameter settings from other vendors, areas and the trend of the call drop rate are consistent and perform other where 2G/3G interoperability is parameter checks. allowed. [Characteristics] The scope of the call drop problem is top N cells, entire network, or top N cells+entire network. [Tools] PFMStudio, DAMS, CME, and OMStar [Tools] DT software and signaling analysis software
Huawei Confidential
Page 45
Huawei Confidential
Page 46
For details about how to optimize neighboring relationships, see the 6 GSM Neighboring Cell Optimization Principles, Tools, and Deliverables 20110730.PPT.
Huawei Confidential
Page 47
Parameter
Other Data
Huawei Confidential
Page 48
Required Actions Check the Parameters of the Other Vendors Devices in the Boundaries of HW and Other Vendors Devices
Triggering conditions: 1. If network swapping or network deployment involves the boundaries of the areas served by the devices from other vendors, check the parameters of the devices from other vendors before network swapping or network deployment. 2. If the call drop rates in the boundaries of the areas served by the devices from other vendors are abnormal, check the parameters of the devices from other vendors. Data and Characteristics
Data Performance Data
[Data Analysis] 1. Template for analyzing weak coverage (top N cells, top N cells+entire network) 2. Template for ranking cells by Rate of Weak Received-Power on Downlink (entire network, top N cells+entire network) 3. Template for analyzing inappropriate neighboring cells (top N cells, top N cells+entire network) 4. Template for ranking cells by the proportions of call drops caused by handovers (entire network, top N cells+entire network) 5. Template for ranking cells by the handover densities (entire network, top N cells+entire network) 6. Template for ranking cells by the handover success rates (entire network, top N cells+entire network) 7. Template for ranking cells by Outgoing Handover/Incoming Handover (entire network, top N cells+entire network) 8. GSM Cell to GSM Cell Outgoing Handover Measurement [Characteristics] 1. The call drop rates deteriorate in the boundaries of the areas served by the devices from other vendors. 2. The differences between the numbers of outgoing handovers and the numbers of incoming handovers are great in the boundaries of the areas served by the devices from other vendors. 3. The outgoing handover success rates are low and the incoming handover success rates are normal in the boundaries of the areas served by the devices from other vendors. 4. The outgoing handover success rates and the incoming handover success rates are low in the boundaries of the areas served by the devices from other vendors.
Parameter
[Data Analysis] [Data Analysis] Perform DTs in the boundaries of the areas served by the devices from other vendors to check whether call drops are caused by inappropriate parameter settings. [Tools] DT software and signaling analysis software Analyze Huawei parameters and the parameters of the devices from other vendors in terms of handovers, camp-on, neighboring cells, configurations, timers to check whether the call drop rates are affected by inappropriate parameter settings.
For details about how to check all parameters, see the 2 GSM Parameters Check: Check Rules+Tools+Cases+Deliverables 20110730.PPT.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 49
network expansion.
2. If the call drop problem persists after the RF tunnel faults are rectified, inappropriate parameter settings are modified, and neighboring cells are optimized, check the network coverage thoroughly and troubleshoot the
coverage problems.
3. During routine network maintenance, check network coverage periodically.
Huawei Confidential
Page 50
Parameter
Other Data
[Data Analysis] 1. Analyze CHRs to identify the cell with the highest call drop rate and the subscriber with the highest call drop rate in the problem cell and perform DTs in the areas where the call drop problem is serve based on the feedback from the subscriber. 2. Analyze MRs containing information such as levels, TA values, and quality information to identify coverage problems. If the TA value is small but the level is high, power is wasted. If the TA value is small and the level is low, weak coverage in buildings or RF tunnel faults occur. If the TA value is large but the level is low, weak coverage occurs. If the TA value is large and the level is high, cross coverage occurs.
[Data Analysis]
[Characteristics]
1. Call drops caused by abnormal handovers and low levels occurs because the following problems occur: weak coverage, coverage hole, cross coverage, downlink interference, missing neighboring cells, or inappropriate settings of handover parameters. 2. The antennas or combiners may be faulty or power mismatch occurs if the coverage of a cell or a site shrinks after network swapping.
2. The call drop rate increases and traffic volume NOTE decreases after network adjustment operations such as It is difficult to identify the coverage shrink caused by power network swapping, network deployment, network matching problems and combiner faults by checking RF expansion, and RF optimization. tunnels. Therefore, you need to focus on power and 3. The proportions of weak coverage or cross coverage combiners if the RF tunnel check does not show any MRs are high for some cells. problems but the coverage shrinks.
Huawei Confidential
Page 51
Huawei Confidential
Page 52
1. Template for analyzing the correlation between the trend of CS or PS service traffic and the trend of the call drop rate [Characteristics] The call drop rate increases during a period and the increasing trend of the call drop rate is correlated with the increasing trends of CS and PS services.
Huawei Confidential
Page 53
Huawei Confidential
Page 54
Other Data
Huawei Confidential
Page 55
Huawei Confidential
Page 56
If the call drop rate increases slowly with seasonal traffic changes, analyze the long-term traffic or KPI trends to determine whether the increase in the call drop rate is acceptable.
Data and Characteristics
Data
1. Template for analyzing the correlation between the trend of CS or PS service traffic and the trend of the call drop rate [Characteristics] The call drop rate increases slowly with seasonal changes in traffic and increase in the subscriber number.
Huawei Confidential
Page 57
Required Actions Check for Complaints and Call Drops Caused by Other Causes by Analyzing CHRs
Triggering conditions: 1. When tracing and analyzing the signaling of VIP subscribers to ensure the service quality, check for complaints and call drops caused by other causes. 2. Subscribers complain about call drops. 3. When analyzing call drop records thoroughly, check for complaints and call drops caused by other causes. Currently, no tool is available for analyzing call drop records thoroughly and therefore engineers must be highly qualified. 4. Call drops due to other causes refer to abnormal call releases due to causes other than Um interface problems and are classified into call drops due to disordered serial numbers, call drops due to sudden downlink failures, and call drops due to BSC-initiated releases. The call drops due to other causes can be identified by analyzing CHRs traffic statistics, and signaling.
Huawei Confidential
Page 58
Required Actions
The attached excel provides the triggering
conditions, templates, data, and characteristics related to the required actions.
Huawei Confidential
Page 59
Focus on the call drops measured as CM333 and CM334 and ignore the call drops caused by failures to start loopback and failures to return to normal calls from loopback because BSC or BTS local switching is disabled in most cases. Determine whether the Abis interface links are faulty by analyzing the proportion and number of the call drops measured by CM333. If call drops occur because the RSL is disconnected, they are measured as CM333. Determine whether some devices are faulty by analyzing the proportion and number of the call drops measured by CM334. The call drops caused by the following operations are measured as CM334: Enable TRX mutual aid; dynamically modify cell attributes, TRX frequencies, or TRX FH data; dynamically delete cells or TRXs; blocking cells, TRXs, or channels The call drops caused by software errors are also measured as CM334. If the number of call drops measured as CM333 and CM334 increases, check for and clear related alarms. Check for and rectify transmission and hardware faults onsite if necessary.
Alarm ID 1000 11270 11278 11280 20081 20082 2204 4414 3606
Alarm Name LAPD_OML Fault Alarm Transmission LAPD Link Interrupt Alarm E1/T1 Local Alarm E1/T1 Remote Alarm Loss of E1/T1 Signals Alarm(LOS) Loss of E1/T1 Frames Alarm(LOF) TRX Commnunication Alarm TRX VSWR Alarm DRU Hardware Alarm
Huawei Confidential
Page 60
Call drops due to other causes refer to abnormal call releases due to causes other than Um interface problems and are classified into call drops due to disordered serial numbers, call drops due to sudden downlink failures, and call drops due to BSC-initiated releases. Such call drops can be identified by analyzing CHRs, traffic statistics, and signaling. BSC-initiated releases are generally caused by transmission faults, hardware faults, resource faults, or resource insufficiency. The call drops due to BSC-initiated releases can be identified by CM333 or CM334, or BSC Release in CHRs and seldom occur on the network. If such call drops count for more than 5% of the total call drops, troubleshoot them by rectifying transmission and hardware faults, resolving resource problems, and clearing related alarms. numbers, call drops due to Call drops due to disordered uplink serial sudden downlink failures, and call drops due to sudden level decreases can be identified by analyzing the traffic statistics, CHRs, and signaling. The possible root causes for such call drops include signaling interference, intermodulation interference between MSs, and subscriber behaviors such as MS power-off. The inter-frequency intermodulation interference is the root cause for the call drops due to disordered serial numbers and call drops due to sudden downlink failures. You can reduce the probability of intermodulation interference by taking the following measures: 1. Enable dummy bit randomization 2. Enable Flex Tsc in limited areas 3. Enable encryption 4. Adjust ARFCNs
Signaling for call drops due to sudden downlink failures and sudden level decreases
Huawei Confidential
Page 61
Huawei Confidential
Page 62
Huawei Confidential
Page 63
Problem Analysis
Step 1: Determine the scope of the call drop problem. According to the analysis of
traffic statistics, the call drop problem occurs on the entire network and in top N
cells, most of which are in the boundaries of the areas served by the devices from other vendors
Step 2: Analyze the call drop causes. According to the analysis of traffic statistics,
most call drops are caused low levels over the Um interface.
Huawei Confidential
Page 64
Conclusion
Check the parameters of the devices from other vendors in the boundaries of the areas served by the devices from other vendors
The handover parameter settings of the devices from other vendors are inappropriate. As a result, MSs are likely to be handed over from the cells served by the devices from other vendors to Huawei cells due to high TA values or low levels. In this case, there is a high probability of call drops.
Analyze neighboring relationships (for newly deployed sites and areas where Huawei devices are Acceptable interconnected to devices from other vendors) Check network coverage (power matching and newly deployed sites) Analyze changes in traffic and KPIs in special scenarios (networks supporting GSM900 and DCS1800 and configured with co-BCCH) Check CS and PS services (their proportions and changes) Analyze frequencies after network expansion, deployment, or reconstruction Check for abrupt events such as charging policy changes, weather changes, and mass gatherings Analyze the long-term traffic trends due to seasonal changes and subscriber number increase Check for complaints and call drops due to other causes by analyzing CHRs
Traffic statistics: The proportion of cells with low uplink levels is high. DT data: Weak coverage occurs.
N/A
Serious weak coverage occurs because the antenna tilts are large at some sites.
This required action is not taken. This required action is not taken. This required action is not taken. This required action is not taken. This required action is not taken.
Huawei Confidential
Page 65
Conclusion
The levels of the main and diversity are different for some cells.
Solution
Rectify the RF tunnel fault.
Effect Evaluation
The call drop rate decreases.
Check for device faults and alarms Some cells report device fault alarms.
Check the parameters of the devices from other vendors in the boundaries of the areas served by the devices from other vendors Check network coverage (power matching and newly deployed sites) The handover parameter settings of the devices from other vendors are inappropriate. As a result, many calls drop because of low levels after MSs are handed over from the cells served by the devices from other vendors to Huawei cells. Serious weak coverage occurs because the antenna tilts are large at some sites.
The call drop rate in the top N cells in Adjust the handover parameter the boundaries of the areas served by settings of the devices from other the devices from other vendors vendors. becomes normal. The number of call drops due to low levels decreases and the call drop rate becomes normal.
The following figure shows the troubleshooting measures and the trend of the call drop rate. After the coverage and the handover parameter settings of the devices from other vendors are adjusted, the call drop rate decreases significantly.
Huawei Confidential
Page 66
Problem Analysis
Step 1: Determine the scope of the call drop problem. According to the analysis of traffic statistics, the call drop problem occurs on the entire network and in top N cells, most of which work on GSM900. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics, most call drops are caused by Um interface problems due to high levels and poor quality.
Huawei Confidential
Page 67
Check network coverage (power matching and newly deployed sites) Analyze changes in traffic and KPIs in special scenarios (networks supporting GSM900 and DCS1800 and configured with co-BCCH)
Huawei Confidential
Page 68
Transfer some traffic from GSM900 to DCS1800 by adjusting the settings of parameters such as Interlayer HO Hysteresis.
The call drop rate decreases significantly after the parameter settings are adjusted. See the following figure.
Huawei Confidential
Page 69
Problem Analysis
Step 1: Determine the scope of the call drop problem. According to the analysis of traffic statistics, the call drop problem occurs in top N cells and most top N cells are the overlaid subcells. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics, most call drops are caused low levels over the Um interface.
Huawei Confidential
Page 70
Solution
1. Adjust the settings of the parameters related to assignment and handovers between the overlaid subcell and the underlaid subcell to balance the traffic between the overlaid subcell and the underlaid subcell. 2. Adjust the PDCH configuration on the current network.
Effect Evaluation
Analyze changes in traffic and KPIs in special scenarios (networks supporting GSM900 and DCS1800 and configured with co-BCCH)
Huawei Confidential
Page 71
Problem Analysis
Step 1: Determine the scope of the call drop problem. According to the analysis of traffic statistics, the call drop problem occurs in top N cells and on the entire network. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics, most call drops are caused by Um interface problems.
Huawei Confidential
Page 72
Problem Analysis
Step 1: Determine the scope of the call drop problem. The call drop problem occurs in the area around the Longfeng expressway bridge. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics, most call drops are caused low levels over the Um interface.
Huawei Confidential
Page 74
Case 5 Call Drop Troubleshooting in a Typical Area Step 4: Troubleshoot call drops
Step 3: Take required actions.
Acceptable Acceptable
Required Action Check RF tunnels for main and diversity faults, cross connections, and interference Check for device faults and alarms Check network coverage (power matching and newly deployed sites)
Traffic statistics: Most call drops The Longfeng expressway bridge runs are caused low levels over the Um through a wetland preservation area, where interface. no primary network coverage is available Check all parameters and therefore the network coverage is DT data: No primary network Analyze neighboring relationships (for newly chaotic. As a result, calls are handed over coverage is available and deployed sites and areas where Huawei randomly between cells, interference is therefore the network coverage is devices are interconnected to devices from strong, and the network quality is poor. The chaotic. As a result, calls are other vendors) DT before optimization operations shows handed over randomly between that the network quality is poor and Analyze frequencies after network cells, interference is strong, and handovers are performed frequently. expansion, deployment, or reconstruction the network quality is poor.
Determine the cells providing primary network coverage, optimize neighboring relationships, optimize frequencies, and adjust parameter settings.
The call drop rate in the problem area decreases significantly. The following figures show the receive quality before and after optimization.
Huawei Confidential
Page 75
Problem Analysis
Step 1: Determine the scope of the call drop problem. The call drop problem occurs in top N cells. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics,
most call drops are caused low levels over the Um interface.
Huawei Confidential
Page 76
On the current network, if the level of a neighboring DT data: A call initiated in cell A is handed over to cell B where the level is low. As a result, cell under another BSC is the call drops after the handover. According to the moving direction of the DT car, the call greater than 82 dBm, this should be handed over to cell C where the level is higher than that in cell B. neighboring cell has a Parameters: Cell A and cell C are served by the same BSC and cell B is served by another higher priority than the BSC. For cells served by the same BSC, Inter-layer HO Threshold is set to 63 and bit 14 neighboring cells served by the same BSC as the of the 16-bit priority is set to 1. For the neighboring cells served by another BSC, Interlayer HO Threshold is set to 25. In this case, if the level is greater than the sum of Inter- serving cell. As a result, calls in the serving cell are layer HO Threshold and HO Hysteresis, bit 14 of the 16-bit priority is set to 0. On the first handed over to the current network, if the level of a neighboring cell served by another BSC is greater than 82 dBm, the neighboring cell has a higher priority than the neighboring cells served by the neighboring cell served by same BSC as the serving cell. As a result, calls in the serving cell are first handed over to another BSC. This handover mechanism is inappropriate. the neighboring cell served by another BSC.
Adjust the setting of Inter-layer HO Threshold for the neighboring cells served by another BSC.
Huawei Confidential
Page 77
Problem Analysis
Step 1: Determine the scope of the call drop problem. The call drop problem occurs in top N cells. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics, most call drops are caused low levels over the Um interface.
Huawei Confidential
Page 78
Analyze neighboring relationships (for newly Traffic statistics: Most call drops are caused low deployed sites and areas where Huawei devices are levels over the Um interface. interconnected to devices from other vendors) DT data: A call in cell A is not handed over to cell B when the MS is moving to a street corner. After Check network coverage (power matching and the MS passes through the street corner, the call newly deployed sites) drops because the level decreases and the network quality becomes poor.
The call is not handed over to cell B in time because cross coverage occurs in cell A.
Adjust the antenna tile and azimuth of cell A to control the coverage.
Huawei Confidential
Page 79
Huawei Confidential
Page 80
Analyze neighboring relationships (for newly Traffic statistics: Most call drops are caused low levels over the Um deployed sites and areas where Huawei interface. devices are interconnected to devices from DT data: After the test MS in cell A passes through the corner of the other vendors) street, the network quality becomes poor. The call initiated by the test MS fails to be handed over to cell B because cell B is not configured Check network coverage (power matching as a neighboring cell of cell A and therefore drops. After the call drops, and newly deployed sites) the test MS initiates another call and accesses cell B.
Huawei Confidential
Page 81
Problem Analysis
Step 1: Determine the scope of the call drop problem. The call drop problem occurs in top N cells. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics, most call drops are caused by Um interface problems due to the high uplink level but poor uplink quality in the problem cell and low downlink levels in the neighboring cells.
Step 3: Take required actions. Most call drops are caused by Um interface problems due to the high uplink level but poor uplink quality in the problem cell and low downlink levels in the neighboring cells. In addition, uplink interference is strong in the cell and reverse handovers occur frequently on carrier A in the cell. Because of the uplink interference on carrier A in the cell, calls in the cell are likely to drop or be handed over to neighboring cells and then drop due to low levels in the neighboring cells. Step 4: Troubleshoot call drops and evaluate the result. The call drop rate becomes normal after the ARFCN of carrier A is changed to an ARFCN without interference.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 82
Problem Analysis
Step 1: Determine the scope of the call drop problem. According to the analysis of traffic statistics, the call drop problem occurs on most BSCs in the entire network. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics, most call drops are caused by Um interface problems due to high levels and poor quality. Step 3: Take required actions. The call drop rates increase after the BTS upgrade. Therefore, check whether the call drop rate problem is caused by the differences in BTS versions. The default values of Second-Level Filter are different between the two BTS versions. BTS3012 V100R008C12SP26: 260 kbit/s BTS3012 V100R008C11B325: 200 kbit/sIn tight frequency reuse pattern, uplink interference increases if the bandwidth increases from 200 kbit/s to 260 kbit/s, which increases the call drop rates. Step 4: Troubleshoot call drops and evaluate the result. The call drop rates become normal after the default value of Second-Level Filter in BTS3012 V100R008C12SP26 is changed to 200 kbit/s.
Huawei Confidential
Page 83
Problem Analysis
Step 1: Determine the scope of the call drop problem. The call drop problem occurs in top N cells. Step 2: Analyze the call drop causes. According to the analysis of traffic statistics, most call drops are caused low levels over the Um interface.
Huawei Confidential
Page 84
Analyze neighboring relationships (for newly deployed sites and areas where Acceptable Huawei devices are interconnected to devices from other vendors) Check RF tunnels for main and diversity faults, cross connections, and interference Check network coverage (power matching and newly deployed sites) Some combiners are added to BTSs, but the power of the BTSs is not increased. Traffic statistics: Most call drops are caused low levels over the Um interface. DT data: The network coverage becomes weak after the network swapping. After the network Increase the swapping, some power of the combiners are added to BTSs to BTSs but the power of which the BTSs is not increased. combiners As a result, the network are added. coverage becomes weak.
Huawei Confidential
Page 85
According to the analysis of CDMA CHRs, the call is released by the MSC on the CDMA network.
Cause Value of a Call Release Meaning of the Cause Value Telephone Number of the Calling/Called Party Access Time (Precise to Second) Access Time (Precise to Millisecond) Call Duration Call Flag
272
1528101****
2010-11-12 10:38
960
163770
According to the analysis of GSM CHRs, the call is released with the
cause value "Sequence error". As a result, the call is released by the MSC on the CDMA network.
Page 86
Huawei Confidential
Introduction to Three Network Optimization Tools Evaluation of Working Efficiency of the Tools Used to Take Required Actions for Call Drop Analysis
Huawei Confidential
Page 87
Nastar
PRS
DAMS
Huawei Confidential
Page 88
DAMS
Network Monitoring
RF Optimization
Customer Experience Parameters Management
VIP Guarantee + Complain Handling Query & Sharing of Data + All Network Parameter Check + Modification & Management
Huawei Confidential
Page 89
RF Optimization - Nastar
UMTS
Analysis of GSM-UMTS neighboring cells
Coverage analysis
GSM
Frequency analysis
Cell performance analysis
VIP KPI analysis Note: For information about how to use these three network optimization tools, see their help files which you can obtain after you install the tools.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 90
Check the results of the cell performance analysis Export the report of the cell performance analysis
End
Huawei Confidential
Page 91
Chart
Top N
The same indicator is displayed in different charts. Different parameters are displayed in different charts in the
same report.
ye
Collect parameter check and optimization experience of experts (Rule development platform) Check all parameters on the entire network (Parameter check of the DAMS)
parameters on the entire network are checked twice a week. If any parameter settings are inappropriate, engineers can modify them directly. Personnel are specially assigned for checking all parameters on the entire network.
Twice a week
Modify parameters
Parameter Modification
Problem resolved
Parameter adjustment Parameter Parameter adjustment requirement n adjustment requirement 2 requirement 1 Top N cell/carrier identification, onsite test, and complaint handling
Check configuration or engineering parameters. (One engineer) Modify/Check parameters Deliver modified parameters.
Parameter modification involves engineering parameters and configuration parameters. Onsite engineers modify the engineering parameters and system engineers modify the configuration parameters. Configuration parameters are classified into different levels. Low-level configuration parameters can be modified by any engineers and high-level configuration parameters can be modified only by system engineers. Parameter modification must be checked by the DAMS and approved by the personnel specially assigned for checking parameters. The DAMS manages the parameter modification history.
Problem resolved
Introduction to Three Network Optimization Tools Evaluation of Working Efficiency of the Tools Used to Take Required Actions for Call Drop Analysis
Huawei Confidential
Page 94
Appendix Evaluation of Working Efficiency of the Tools Used to Take Required Actions for Call Drop Analysis
Required Action
Identify call drop causes by analyzing performance dataand CHRs
Tool
Traffic statistics: PRS and excel templates CHRs: Nastar and Insightsharp OMStar, MainDivAnalyse, Check RF tunnels for main and diversity faults, cross DownlinkAnalyse, and 5 minutes/BSC connections, and interference IntferBandAnalyse Check for device faults and alarms OMStar and alarm console 5 minutes/BSC Check all parameters Parameter check tool and OMStar 1~5 minutes/BSC Check for BTS or BSC version differences and Not available parameter differences Check the parameters of the devices from other vendors in the boundaries of the areas served by the Not available devices from other vendors Analyze neighboring relationships (for newly deployed sites and areas where Huawei devices are Nastar 30 minutes interconnected to devices from other vendors) Check network coverage (power matching and newly Not available deployed sites) Analyze changes in traffic and KPIs in special scenarios (networks supporting GSM900 and Not available DCS1800 and configured with co-BCCH) Check CS and PS services (their proportions and Not available changes) Analyze frequencies after network expansion, Nastar and MapInfo 60 minutes/BSC deployment, or reconstruction Check for abrupt events such as charging policy Not available changes, weather changes, and mass gatherings Analyze the long-term traffic trends due to seasonal Not available changes and subscriber number increase Check for complaints and call drops due to other Nastar and Insightsharp 10~30 minutes/BSC causes by analyzing CHRs
Processing Duration Required by Tools Traffic statistics: 10 minutes/BSC CHRs: 20~30 minutes/BSC
30~60 minutes/BSC
A long time for obtaining data and 10 minutes for analyzing data A long time for obtaining data and 10 minutes for analyzing data Statistical analysis: 30~60 minutes/BSC Single-call CHRs: 3~10 minutes/Call
Huawei Confidential
Page 95
Thank you
www.huawei.com