UTRAN KPI Analysis Guide

For Internal Only

Use

Huawei Technologies Co., Ltd

Document name UTRAN KPI Analysis Guide RAN Maintenance Dept.

Confidentiality level For Internal Use Only Total 46 Pages

UTRAN KPI Analysis Guide

Prepared by Reviewed by Reviewed by Approved by

RAN Maintenance Dept.

Date Date Date Date

Aug. 10, 2005

Huawei Technologies Co., Ltd.
All Rights Reserved

UTRAN KPI Analysis Guide

For Internal Only

Use

Revision Edition
Date Aug. 10, 2005 Version Description The first version is complete. Author Wang Wei

UTRAN KPI Analysis Guide

For Internal Use Only

Table of Contents
1. OVERVIEW..........................................................................................................................................5 1.1 INTENDED AUDIENCE.......................................................................................................................5 1.2 OBJECTIVES......................................................................................................................................5 2. INTRODUCTION TO NASTAR..........................................................................................................6 3. UTRAN KPI ANALYSIS.....................................................................................................................6 3.1 NASTAR TASKS................................................................................................................................6 4. UTRAN KPI ANALYSIS.....................................................................................................................8 4.1 CALL COMPLETION RATE................................................................................................................8 4.1.1 RRC Setup Analysis.....................................................................................................................8 4.1.2 RAB Setup Analysis...................................................................................................................12 4.2 SOFT HANDOVER ANALYSIS..........................................................................................................19 4.2.1 Overview.....................................................................................................................................20 4.2.2 Cell SHO Prepare Failure Analysis............................................................................................22 4.2.3 Cell SHO Failure Analysis.........................................................................................................23 4.3 CS INTER-RAT HANDOVER ANALYSIS.........................................................................................25 4.3.1 Overview.....................................................................................................................................26 4.3.2 CS Inter-RAT Handover Prepare Failure Analysis....................................................................27 4.3.3 CS Inter-RAT Handover Failure Analysis..................................................................................29 4.3.4 Cell Inter-RAT Handover Analysis............................................................................................31 4.4 PS INTER-RAT HANDOVER ANALYSIS..........................................................................................31 4.4.1 Overview.....................................................................................................................................31 4.4.2 PS Inter-RAT Handover Failure Analysis..................................................................................32 4.4.3 Cell Inter-RAT Handover Analysis............................................................................................34 4.5 CELL UPDATE ANALYSIS...............................................................................................................34 4.5.1 Overview.....................................................................................................................................34 4.5.2 Cell Update Failure Analysis......................................................................................................36 4.6 CALL DROP ANALYSIS...................................................................................................................36 4.6.1 Overview.....................................................................................................................................36 4.6.2 CS Call Drop Analysis................................................................................................................37 4.6.3 PS Call Drop Analysis................................................................................................................39 4.6.4 Cell Call Drop Analysis..............................................................................................................40 4.7 TRAFFIC LOAD ANALYSIS..............................................................................................................42 4.7.1 Overview.....................................................................................................................................42 4.7.2 Cell Traffic Analysis...................................................................................................................44 5. ANALYZING COMPLICATED PROBLEMS..................................................................................46 5.1 NARROWING DOWN AREA RANGE AND TIME RANGE...................................................................46 5.2 ANALYZING ABNORMAL LOGS......................................................................................................46 5.3 ANALYZING REPEATED PROBLEMS................................................................................................46

Aug. 10, 2005

Confidential Information of Huawei No Spreading Without Permission

Page 3 of 46

UTRAN KPI Analysis Guide

For Internal Use Only

Aug. 10, 2005

Confidential Information of Huawei No Spreading Without Permission

Page 4 of 46

refer to GENEX Nastar V400R001C01 User Manual. 1. Huawei UTRAN traffic statistics provides sufficient KPI for network operation. call detail logs. For more information. algorithm management. and alarms. UTRAN KPI analysis is a major method used for monitoring and evaluating network operation. 2005 Confidential Information of Huawei No Spreading Without Permission Page 5 of 46 .1 Intended Audience This guide. These traffic statistics can be used to locate network problems and optimize network KPI. Comparing with drive tests. To better locate network problems and optimize network KPI. and resource distribution. the QoS and network operation are reflected through KPI. intended for network maintenance engineers and site audit engineers. tracked messages. analyze abnormal indices. Huawei provides a traffic statistics analysis tool Nastar for UTRAN KPI analysis. call detail logs. which supports the KPI analysis of RNC V100R002C03B092 and RNC V100R002C03B151. monitor the resource distribution. 10. KPI analysis can be used to monitor network operation directly and conveniently. Nastar can be used to obtain and analyze UTRAN KPI. UTRAN KPI analysis is also served to track the network traffic. introduces Nastar V400R001. and drive tests can be used together.UTRAN KPI Analysis Guide For Internal Use Only UTRAN KPI Analysis Guide 1. abnormal indices. This guide introduces how to use Nastar to analyze UTRAN KPI. 1.2 Objectives This guide aims to provide guidance for network maintenance personnel to monitor network KPI on a timely basis. and facilitate the network expansion and optimization. UTRAN KPI analysis is a major method for RAN maintenance engineers and network optimization engineers to evaluate network performance. and find out Aug. Overview In a commercial network.

UTRAN KPI Analysis The QoS of communication network is defined in ITU-T E. Introduction to Nastar Nastar provides such functions as index defining. and report generating. the following KPI must be considered for WCDMA RAN. 3. 2005 Confidential Information of Huawei No Spreading Without Permission Page 6 of 46 . 10. For more information. 2.1 Nastar Tasks Figure 1-1 shows a list of Nastar tasks. query defining. Network performance Call completion rate Call drop rate KPI RRC Setup Success Rate RAB Setup Success Rate Voice Call Drop Rate VP Call Drop Rate PS Call Drop Rate Mobility management Soft Handover Success Rate Inter-Frequency HO Success Rate Intra-Frequency HO Success Rate CS Inter-RAT HO Success Rate PS Inter-RAT HO Success Rate Cell Update Success Rate Traffic Equivalent User Cell Throughput Cell Resource Allocation Table 1-1 WCDMA RAN KPI 3.800. Considering the features of wireless communication network.UTRAN KPI Analysis Guide For Internal Use Only practical solutions. Aug. refer to GENEX Nastar V400R001C01 User Manual. as shown in Table 1-1.

13(16:00 ~ 17:00) 54. 2005 Confidential Information of Huawei No Spreading Without Permission Page 7 of 46 . RNC Name Traffic CS User Based on Equivalent User PS User Based on Equivalent User RRC Connection Setup Success Rate(service)(> 95%) RRC Connection Setup Success Rate(other)(> 95%) Access AMR RAB Assignment Success Rate(> 95%) Video Call RAB Assignment Success Rate(> 95%) PS RAB Assignment Success Rate(> 95%) RB Setup Success Rate(> 95%) Soft Handover Success Rate(> 98%) Softer Handover Success Rate(> 98%) HO Soft Handover Factor based on Radio Link Number(< 40%) Inter-Freq Hard Handover Success Rate(> 85%) CS Inter-RAT Handover Success Rate( from UTRAN to GSM)(> 85%) PS Inter-RAT Handover Success Rate( from UTRAN to GSM)(> 85%) CS AMR Call Drop Rate(< 1. By default.xls file by Nastar.5%) PS Service Drop Rate(< 30%) RN C: 1 17.85% 100.64%(2468/2502) 96.UTRAN KPI Analysis Guide For Internal Use Only Figure 1-1 Nastar tasks Perf Daily Report and Perf Weekly Report can be generated in . Perf Daily Report includes the following KPI.00%(990/1000) 100.00%(29/29) 99. An object can be a self-defined clutter or RNC.00%(4/4) 66.60%(997/1001) 99. Perf Daily Report is used to monitor network performance. as shown in Table 1-2.31%(2016/2030) 99.92%(19/990) 10.87%(36445/37624) 99.01%(30/997) Aug.00%(16/16) 100.34%(3/29) 3.67%(4/6) 1.09(12:00 ~ 13:00) 98.66%(3509/3521) 18.75%(17090/17132) 99.5%) CDR Video Call Drop Rate(< 1. 10.

3%. 78. refer to Section 4 UTRAN KPI Analysis.3 % 2. as shown in Figure 1-3.1 Call Completion Rate This section consists of the following parts:   RRC Setup Analysis RAB Setup Analysis 4.01 % Figure 1-3 RRC Setup Aug. as shown in Figure 1-1. 4. UTRAN KPI Analysis 4.69 % 0.UTRAN KPI Analysis Guide For Internal Use Only Table 1-2 Perf Daily Report If network performance cannot meet the previous KPI or the KPI is changed. Overview RRC Setup Analysis is included in Nastar.1 RRC Setup Analysis 1. Double click RRC Setup Analysis to display the RRC setup details.961 RRC_SETUP_SUCC 7 RRC_REJ 2.1. RRC setup success rate is 97.186 RRC_SETUP_FAIL_NO_RSP 97. 10. Most RRC setup failures result from RRC Setup Fail No Response while few RRC setup failures (seven times) result from RRC Setup Reject. 2005 Confidential Information of Huawei No Spreading Without Permission Page 8 of 46 .

as shown in Figure 1-5. 10. The networks.451 5.387 9.385 16. In particular.639 51.  A certain area has too many subscribers or any equipment in this area is faulty.97 % 7.  RRC REQ REG If network coverage is poor. RRC Setup Scenario Analysis One of the reasons for RRC Setup Fail No Response is poor coverage. are covered poorly.55 % 20.UTRAN KPI Analysis Guide For Internal Use Only There are two reasons for RRC Setup Fail No Response:  Downlink FACH and RACH are covered unevenly. so RRC setup reasons and RRC setup success rate can be used for further analysis. Aug. 2. built during the early period.27 % Figure 1-4 RRC setup scenario (pie chart) Use Scenario Analysis to analyze RRC setup scenarios. inter-system reselection may occur. Most RRC setup requests are caused by:  RRC REQ CELL RESEL If network coverage is poor. inter-system reselection areas are covered poorly.21 % RRC_REQ_ORG RRC_REQ_TERM RRC_REQ_CELL_RESEL RRC_REQ_REG 63. 2005 Confidential Information of Huawei No Spreading Without Permission Page 9 of 46 . subscribers attempt to register for many times. 6. Start Scenario Analysis to display a pie or bar chart for presenting RNC indices.

On Huawei networks. Low RRC SETUP SUCC RATE REG indicates that many registrations are attempted within the area (Ec/Io falls between -14 dB and -18 dB).UTRAN KPI Analysis Guide For Internal Use Only 0. resident threshold Ec/Io is greater than -18 dB while inter-system reselection start threshold Ec/Io is less than -14 dB. only the areas of RRC setup reject must be analyzed.96 0. The queried results are outputted in three pages: (1) The top ten cells that have the highest RRC setup reject times.95 0. RRC SETUP SUCC RATE ORG is very high while RRC SETUP SUCC RATE REG is very low. RRC setup reject occurs in a small-scale network. 3. In RRC Setup Analysis.965 g b c d e f g g g RNC:41(ID:41)-RRC_SETUP_SUCC_RATE_ORG RNC:41(ID:41)-RRC_SETUP_SUCC_RATE_TERM RNC:41(ID:41)-RRC_SETUP_SUCC_RATE_INTERRAT_CELL_RESEL RNC:41(ID:41)-RRC_SETUP_SUCC_RATE_REG Figure 1-5 RRC setup scenario (bar chart) Figure 1-5 shows RRC setup success rates.98 Bar Value 0.99 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 10 of 46 . RRC Setup Reject Analysis RRC setup reject are caused by:   Admission reject due to crowded subscribers Access failure due to equipment faults RRC setup reject may occur no matter how poor network coverage is. however. Aug. Therefore.975 0. start Cell RRC Analysis to query the TOPN.97 0.985 0. High RRC SETUP SUCC RATE ORG (99%) indicates that the network is covered by PCH and RRC SETUP SUCC RATE can be high in a well-covered network. 10.955 0. which has poor coverage.945 0 Time 0.

To locate the problem. check whether the threshold is reasonable. start Cell RRC Reject Analysis for further analysis. power congestion may occur. (2) CE Congestion Aug. and check whether the network capacity is insufficient. two RRC setup rejects are caused by Power Congestion.UTRAN KPI Analysis Guide For Internal Use Only (2) The top ten cells that have the highest RRC setup success rates. If network load is heavy. If power congestion is confirmed. For the top ten cells that have the maximum RRC setup fail rates. (3) The top ten cells that have the highest RRC setup failure rates. 10. check whether there is any interference. 2005 Confidential Information of Huawei No Spreading Without Permission Page 11 of 46 . RRC setup reject may be caused by the following reasons: (1) Power Congestion RRM performs the admission algorithm decision but uplink or downlink admission decision is rejected. 2 0 0 0 0 0 0 100 % 0% 0% RRC_REJ_POWER_CONG_CELL RRC_REJ_CE_CONG_CELL RRC_REJ_RL_FAIL_CELL RRC_REJ_AAL2_FAIL_CELL RRC_REJ_FP_FAIL_CELL RRC_REJ_CODE_CONG_CELL RRC_REJ_OTHER_CELL Figure 1-6 RRC setup reject analysis Figure 1-6 shows the results of Cell RRC Reject Analysis. For the top ten cells that have the maximum RRC setup rejects. In this figure. so RRC setup reject occurs. start Cell Traffic Load Analysis to check whether uplink or downlink is congested by focusing on the maximum RTWP and the maximum TCP. start Cell Scenario Analysis for further analysis.

analyze call detail logs. start Cell Traffic Load Analysis to check the DCH user number and the bandwidth of AAL2 path.2 RAB Setup Analysis 1. (7) Other If there is any problem in RNC. To locate the problem. To locate the problem. Overview Aug. Analyze the data and logs of the boards or CEs in NodeB to check whether NodeB fails or NodeB resource is insufficient. (3) RL Fail During the RRC setup process. code resource may be insufficient. RRC setup reject may occur.UTRAN KPI Analysis Guide For Internal Use Only If there are many subscribers. To locate the problem. (6) Code Congestion If there is high traffic in the indoor micro cell.1. start Cell OVSF Code Allocation Analysis to analyze the code allocation and confirm major services. 4. To locate the problem. (4) AAL2 Fail If transmission resource is insufficient or any transmission equipment is faulty. Check whether transmission resource is insufficient or any transmission equipment is faulty. NodeB recognizes RRC setup fail because NodeB fails or NodeB resource is insufficient. 2005 Confidential Information of Huawei No Spreading Without Permission Page 12 of 46 . 10. check whether there is any BTS alarm. CE resources may become insufficient in RNC. start Cell Traffic Load Analysis to check the DCH user number and forecast the required CE quantity in accordance with the traffic model. (5) FP Fail If the transmission fails or an equipment is faulty. To locate the problem. To locate the problem start Cell Traffic Load Analysis to check the DCH user number. FP synchronization may fail. the AAL2 path setup of lub interface may fail.

15 % Figure 1-8 RAB setup analysis Check such RAB setup rates as CS_RAB_REQ_SETUP_CONV_0_32 (AMR). RAB Setup Analysis is included in Nastar.UTRAN KPI Analysis Guide For Internal Use Only Figure 1-7 Nastar tasks Figure 1-7 shows a list of Nastar tasks. 10. and 384 K Aug. 64 K (PS). as shown in Figure 1-8.19 % 3.13 % 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 13 of 46 .370 CS_RAB_REQ_SETUP_CONV_0_32 101 CS_RAB_REQ_SETUP_CONV_32_64 5 PS_RAB_REQ_SETUP_64K 5 PS_RAB_REQ_SETUP_128K 749 PS_RAB_REQ_SETUP_384K 23. CS_RAB_REQ_SETUP_CONV_32_64 (VP). 128 K (PS). 73. Double click RAB Setup Analysis to display RAB setup details.15 % 0.37 % 2.

3 0.9 0. as shown in Figure 1-9. If CS RAB setup fail rate is high in a cell.1 0 0 Time g g g RNC:1(ID:1)-RB_SETUP_SUCC_RATE g g RNC:1(ID:1)-PS_RAB_SETUP_SUCC_RATE_128K g RNC:1(ID:1)-CS_RAB_ SETUP_SUCC_RATE_VP RNC:1(ID:1)-CS_RAB_ SETUP_SUCC_RATE_AMR RNC:1(ID:1)-PS_RAB_SETUP_SUCC_RATE_64K RNC:1(ID:1)-PS_RAB_SETUP_SUCC_RATE_384K Figure 1-9 RB and RAB setup success rates 2.1 1 0. 10. The top ten cells that have the lowest CS RAB setup failures. 1. Aug. RAB Setup Fail Analysis In RAB Setup Analysis. Click Produce a Bar Chart to display the RB and RAB setup success rates. 2005 Confidential Information of Huawei No Spreading Without Permission Page 14 of 46 . The top ten cells that have the highest PS RAB setup failures. start Cell CS RAB Setup Fail Analysis to display the CS RAB setup fail rates. The queried results are outputted in four pages: (1) (2) (3) (4) The top ten cells that have the highest CS RAB setup failures.7 0.8 Bar Value 0. The top ten cells that have the lowest PS RAB setup failures.5 0. start Cell RAB Analysis to query the TOPN. To locate the problem.2 0.UTRAN KPI Analysis Guide For Internal Use Only (PS) to confirm major services in the network. Low RAB setup success rate may occur in the cells that have lowest setup times. focus on the cells that have the lowest setup failures because the KPI is affected mostly by these cells. as shown in Figure 1-10.4 0.6 0.

(3) TNL_CELL RAB setup fails because IU transmission setup fails.05 % 0 % % 0. so this reason seldom occurs.UTRAN KPI Analysis Guide For Internal Use Only 99. (5) POWER_CONG_CELL Aug. 2005 Confidential Information of Huawei No Spreading Without Permission Page 15 of 46 . To locate the problem. To locate the problem. 10. track the signaling and check the RAB setup messages in specific cells. (2) RELOC_CELL When initializing the migration process.571 CS_RAB_SETUP_SUCC_CONV_CELL 0 CS_RAB_SETUP_SUCC_STR_CELL 0 CS_RAB_SETUP_FAIL_PARAM_CELL 0 CS_RAB_SETUP_FAIL_RELOC_CELL 10 CS_RAB_SETUP_FAIL_TNL_CELL 0 CS_RAB_SETUP_FAIL_CONG_CELL 0 CS_RAB_SETUP_FAIL_POWER_CONG_CELL 0 CS_RAB_SETUP_FAIL_CE_CONG_CELL 0 CS_RAB_SETUP_FAIL_CODE_CONG_CELL 5 CS_RAB_SETUP_FAIL_OTHER_CELL Figure 1-10 Cell CS RAB setup fail analysis Cell CS RAB setup failures may be caused by the following reasons: (1) PARAM_CELL RNC regards the parameters transmitted by core network as invalid parameters.32 0 % % 0% 1. In a core network. (4) CONG_CELL This may be caused by RNC resource allocation failure. This reason is mainly caused by the process integration related to subscriber action sequence. this situation is always avoided. This reason seldom occurs.63 0 % 0 % 0. analyze the RNC logs and obtain the detailed resource failure information. RNC receives the RAB setup request messages but RNC does not process the request. check the transmission capacity and operation stability. To locate the problem.

(6) CE_CONG_CELL CE resource admission fails in RNC. new RAN cannot be set up because cell load is too heavy. analyze the code resource of cell traffic to check whether code resource is restricted due to cell overload. code resource allocation fails because too many subscribers are crowded on the network or code resource allocation fails.09 % 0% 0% % 6. 2005 Confidential Information of Huawei No Spreading Without Permission Page 16 of 46 . If PS RAB setup fail rate is high. To locate the problem. To locate the problem. 84. check whether the parameters of admission algorithm are reasonable.82 0% 0% 0 0 37 0 0 0 0 3 0 0 4 PS_RAB_SETUP_SUCC_CONV_CELL PS_RAB_SETUP_SUCC_STR_CELL PS_RAB_SETUP_SUCC_INTER_CELL PS_RAB_SETUP_SUCC_BKG_CELL PS_RAB_SETUP_FAIL_PARAM_CELL PS_RAB_SETUP_FAIL_RELOC_CELL PS_RAB_SETUP_FAIL_CONG_CELL PS_RAB_SETUP_FAIL_POWER_CONG_CELL PS_RAB_SETUP_FAIL_CE_CONG_CELL PS_RAB_SETUP_FAIL_CODE_CONG_CELL PS_RAB_SETUP_FAIL_OTHER_CELL Figure 1-11 Cell PS RAB setup fail analysis Cell CS RAB setup failure may be caused by the following reasons: (1) PARAM_CELL RNC regards the parameters transmitted by core network as invalid Aug. If yes. as shown in Figure 1-11.UTRAN KPI Analysis Guide For Internal Use Only According to RRM admission decision. To locate the problem. consider to optimize the coverage and expand the capacity. (8) OTHER_CELL This may caused by RB setup failure or other reasons.09 % 0% 0% 9. 10. start Cell PS RAB Setup Fail Analysis to display the PS RAB setup fail rates. analyze RB setup success rates. CE must be expanded. (7) CODE_CONG_CELL During the RAB setup process.

RNC receives the RAB setup request messages but RNC does not process the request. If yes. analyze the RNC logs and obtain the detailed resource failure information. the QoS is not supported by RNC or RRM Aug. In a core network. (2) RELOC_CELL When initializing the migration process. this situation is always avoided. To locate the problem. analyze the code resource of cell traffic to check whether code resource is restricted due to cell overload. This reason seldom occurs. (6) CE_CONG_CELL CE resource admission fails in RNC. (8) UNSUP_CELL During the RAB setup process. (3) TNL_CELL RAB setup fails because IU transmission setup fails. 10. To locate the problem. track the signaling and check the RAB setup messages in specific cells. To locate the problem. 2005 Confidential Information of Huawei No Spreading Without Permission Page 17 of 46 . To locate the problem. check whether the parameters of admission algorithm are reasonable.UTRAN KPI Analysis Guide For Internal Use Only parameters. (5) POWER_CONG_CELL According to RRM admission decision. This reason is mainly caused by the process integration related to subscriber action sequence. To locate the problem. check the transmission capacity and operation stability. new RAN cannot be set up because cell load is too heavy. (7) CODE_CONG_CELL During the RAB setup process. code resource allocation fails because too many subscribers are crowded on the network or code resource allocation fails. (4) CONG_CELL This may be caused by RNC resource allocation failure. consider to optimize the coverage and expand the capacity. CE must be expanded. so this reason seldom occurs.

10. To analyze the RB setup failure. (3) SIMU_RECFG_INCOMP UE regards that the RB setup process and other processes simultaneously occur and they are incompatible. This reason seldom occurs in the network.645 0 0 0 0 3 1 0 RB_SETUP_SUCC_CELL RB_SETUP_FAIL_CFG_UNSUPP_CELL RB_SETUP_FAIL_PHYCH_FAIL_CELL RB_SETUP_FAIL_SIMU_RECFG_INCOMP_CELL RB_SETUP_FAIL_CELL_UPDT_CELL RB_SETUP_FAIL_CFG_INVALID_CELL RB_SETUP_FAIL_NO_RSP_CELL RB_SETUP_FAIL_OTHER_CELL Figure 1-12 Cell RB setup fail analysis Cell RB setup failure may be caused by the following reasons: (1) CFG_UNSUPP UE acknowledges the RB setup failure because of configuration unsupported. as shown in Figure 1-12. It is mainly caused by compatibility problem of UE in some unknown scenarios.18 % 0 0. analyze RB setup success rates.76 % 0. 99. In a commercial network. (9) OTHER_CELL This may caused by RB setup failure or other reasons. To locate the problem.UTRAN KPI Analysis Guide For Internal Use Only admission fails in RAB. 2005 Confidential Information of Huawei No Spreading Without Permission Page 18 of 46 . Aug. RAB setup is mainly caused by admission failure and RB setup failure. (2) PHYCH_FAIL The RB setup failure may occur if FACH is migrated to DCH but downlink physical layers are not synchronized during the RB setup process. It is mainly caused by UE defects. This reason seldom occurs. The rooted reason is poor coverage.06 % % 0% 1. start Cell RB Setup Fail Analysis to display the RB setup fail rates. RNC processing ensures RRC processes nesting.

analyze call detail logs. 10. It is mainly caused by poor coverage. To locate the problem. This reason frequently occurs. This reason seldom occurs.2 Soft Handover Analysis This section consists of the following parts:    Overview Cell SHO Prepare Failure Analysis Cell SHO Failure Analysis Aug. (7) OTHER Cell RB setup failure is caused by other reasons.UTRAN KPI Analysis Guide For Internal Use Only (4) CELL_UPDT During the RB setup process. 2005 Confidential Information of Huawei No Spreading Without Permission Page 19 of 46 . the Cell Update process occurs. 4. The RB setup failure is caused by process nesting. (6) NO_RESPONSE UE does not acknowledge the RB setup request. It is mainly caused by inconsistent understanding of network and UE. so UE cannot receive the RB setup request message. (5) CFG_INVALID UE regards the configured parameters are invalid ones.

and soft handover prepare success rate).2. as shown in Figure 1-14. as shown in Figure 1-13. Double click Soft Handover Analysis to display the RNC soft handover details (including soft handover success rate.UTRAN KPI Analysis Guide For Internal Use Only 4. softer handover success rate.1 Overview Figure 1-13 Nastar Tasks Soft Handover Analysis is included in Nastar tasks. Aug. 10. 2005 Confidential Information of Huawei No Spreading Without Permission Page 20 of 46 .

985 0. SHO_FACTOR-RL can be calculated as follows: (Subscriber number of link 1 of active set*1 + Subscriber number of link 2 of active set*2 + Subscriber number of link 3 of active set*3)/Total subscriber number – 1 SHO_FACTOR_RL is used to indicate the influence of soft handover exerted on NodeB CE and to evaluate the subscriber resource utililization.97 0.995 0.  SHO_FACTOR_UE SHO_FACTOR_UE is used to measure the proportion of soft handover subscribers.99 0. SHO_FACTOR_RL and SHO_FACTOR_UE are defined as follows:  SHO_FACTOR_RL SHO_FACTOR_RL is used to measure average link number.94 0.95 0. soft handover factor is used to measure the proportion and cost of soft handover. which is similar to the proportion of soft handover area by making drive tests.98 0.955 0. 10.UTRAN KPI Analysis Guide For Internal Use Only 1.945 0.005 1 0. SHO_FACTOR_UE is used to measure the reasonable Aug.96 0.975 0.935 0 Time Bar Value g b c d e f g RNC:1(ID:1)-SHO_SUCC_RATE RNC:1(ID:1)-SHO_PREP_SUCC_RATE g RNC:1(ID:1)-SOFTERHO_SUCC_RATE Figure 1-14 Soft Handover Analysis In the previous figure.965 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 21 of 46 . SHO_FACTOR_UE can be calculated as follows: (Subscriber number of link 2 of active set + Subscriber number of link 3 of active set)/Total subscriber number SHO_FACTOR_UE is used to indicate the subscribers in the soft handover area.

The queried results are outputted in four pages: (1) The top ten cells that have the highest soft handover failure times (2) The top ten cells that have the lowest soft handover success rates (3) The top ten cells that have the highest soft handover prepare failure times (4) The top ten cells that have the lowest soft handover prepare success rates During the early period. the greater the subscriber number of link 3 of active set is. 10.46 % 0% 0 7 0 67 SHO_PREP_RL_SETUP_FAIL SHO_PREP_AAL2_SETUP_FAIL SHO_PREP_FP_SYNC_FAIL SHO_PREP_FAIL_OTHER_CELL 90. 0% 9. If the subscriber number of link 3 of active set is very great. as shown in Figure 1-15. The greater the difference between them is.54 % Figure 1-15 Cell SHO Prepare Failure Analysis Aug. To query the cells that have the highest soft handover prepare failure times. 4. low soft handover success rates may exist in the cells that have less soft handover times.2. start Cell SHO Prepare Failure Analysis to display the soft handover prepare failure details. Attention must be paid to the cells that have the highest soft handover failure times and the highest soft handover prepare failure times because they affect the KPI of soft handover greatly.UTRAN KPI Analysis Guide For Internal Use Only relationship between soft handover area and soft handover distribution. start Cell SHO Analysis to query the TOPN. SHO_FACTOR_UE is greater than SHO_FACTOR_UE. 2005 Confidential Information of Huawei No Spreading Without Permission Page 22 of 46 .2 Cell SHO Prepare Failure Analysis In the Soft Handover Analysis. SHO_FACTOR_RL is greater than 1 while SHO_FACTOR_UE is less than 1.

and RNC link state reject. and data configuration of NodeB boards can be used to locate the problems. To locate the problem. radio resource admission reject. To locate the problem. 2005 Confidential Information of Huawei No Spreading Without Permission Page 23 of 46 . If NodeB CE resource is insufficient. (2) SHO_PREP_AAL2_SETUP_FAIL When the links are added during the soft handover. 10. 4. Internal NodeB logs.UTRAN KPI Analysis Guide For Internal Use Only Cell SHO prepare failure may be caused by the following reasons: (1) SHO_PREP_RL_SETUP_FAIL The links cannot be added during the soft handover because NodeB CE resource is insufficient or NodeB is faulty. The queried results are outputted in four pages: (1) (2) (3) The top ten cells that have the highest soft handover failure times The top ten cells that have the lowest soft handover success rates The top ten cells that have the highest soft handover prepare failure times Aug. Cell Traffic Load Analysis. such as insufficient RNC resource. check whether the intermittent transmission interruption occurs or the IMA group transmission is incorrectly configured. one or more boards must be added for expansion. (4) SHO_PREP_ FAIL_OTHER_CELL Soft handover prepare failure is caused by other reasons. RNC logs must be used for further analysis. transmission equipments must be expanded. (3) SHO_PREP_FP_SYNC_FAIL When the links are added during the soft handover.2. start Cell SHO Analysis to query the TOPN. the synchronization of AAL2 and FP of lub interface fails. the AAL2 setup of lub interface fails because the transmission bandwidth is insufficient.3 Cell SHO Failure Analysis In the Soft Handover Analysis. If the transmission bandwidth is insufficient.

RNC performs the serial connection. 0 0.14 % 0 0% % 0% 0% 2. (2) SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP UE feeds back that the soft handover process is incompatible with other concurrent processes when radio links are added in RNC. start Cell SHO Failure Analysis to display the soft handover failure details. Attention must be paid to the cells that have the highest soft handover failure times and the highest soft handover prepare failure times because they affect the KPI of soft handover greatly. as shown in Figure 1-16.11 % % 99. 10. (4) SHO_RL_ADD_FAIL_NO_RSP Aug. The problem is mainly caused by some handsets.75 % 0. This reason seldom occurs in a commercial network. In the Cell SHO Analysis. 2005 Confidential Information of Huawei No Spreading Without Permission Page 24 of 46 . low soft handover success rates may exist in the cells that have less soft handover times. This reason seldom exists in a commercial network. (3) SHO_RL_ADD_FAIL_CFG_INVALID UE regards active set update of adding radio links in RNC as invalid configuration.797 0 0 0 4 0 0 0 3 0 SHO_SUCC_CELL SHO_RL_ADD_FAIL_CFG_UNSUPP SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP SHO_RL_ADD_FAIL_CFG_INVALID SHO_RL_ADD_FAIL_NO_RSP SHO_RL_DEL_FAIL_CFG_UNSUPP SHO_RL_DEL_FAIL_SIMU_RECFG_INCOMP SHO_RL_DEL_FAIL_CFG_INVALID SHO_RL_DEL_FAIL_NO_RSP SHO_FAIL_OTHER_CELL Figure 1-16 Cell SHO Failure Analysis Soft handover failure may be caused by the following reasons: (1) SHO_RL_ADD_FAIL_CFG_UNSUPP UE does not support to add radio links in RNC during the active set update.UTRAN KPI Analysis Guide For Internal Use Only (4) The top ten cells that have the lowest soft handover prepare success rates During the early period. When handling the processes.

When handling the processes.3 CS Inter-RAT Handover Analysis This section consists of the following parts:    Overview CS Inter-RAT Handover Prepare Failure Analysis CS Inter-RAT Handover Failure Analysis Aug. analyze the logs to locate the problems. 2005 Confidential Information of Huawei No Spreading Without Permission Page 25 of 46 . (5) SHO_RL_DEL_FAIL_CFG_UNSUPP UE does not support to delete radio links in RNC during the active set update. soft handover failure is seldom caused by other reasons. (9) SHO_FAIL_OTHER_CELL Soft handover failure is caused by other reasons. however. 4. the RF optimization is required. If network coverage is poor or soft handover area is small. If network coverage is poor or soft handover area is small. Soft handover failure is mainly caused by this reason. Thus. (8) SHO_RL_ADD_FAIL_NO_RSP RNC does not receive the acknowledgement of active set update of deleting radio links. The problem is mainly caused by some handsets. This reason seldom occurs in a commercial network. (6) SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP UE feeds back that the soft handover is incompatible with other concurrent processes when radio links are deleted in RNC.UTRAN KPI Analysis Guide For Internal Use Only RNC does not receive the acknowledgement of active set update of adding radio links. This reason seldom occurs in a commercial network. Soft handover failure is mainly caused by this reason. soft handover failure easily occurs. the RF optimization is required. soft handover failure easily occurs. (7) SHO_RL_ADD_FAIL_CFG_INVALID UE regards the active set update of deleting radio links in RNC as invalid configuration. RNC performs the serial connection. Thus. 10. If soft handover failure is caused by other reasons.

CS inter-RAT handover between a 2G network and a 3G network seldom occurs. CS inter-RAT handover prepare failure rate. as shown in Figure 1-17. Double click CS Inter-RAT Handover Analysis to display the CS inter-RAT handover details between a 2G network and a 3G network (including CS interRAT handover success rate.UTRAN KPI Analysis Guide For Internal Use Only  Cell Inter-RAT Handover Analysis 4. 10. Aug.1 Overview Figure 1-17 Nastar tasks CS Inter-RAT Handover Analysis is included in Nastar tasks. In a commercial network. as shown in Figure 1-18.3. 2005 Confidential Information of Huawei No Spreading Without Permission Page 26 of 46 . and CS inter-RAT handover failure rate).

1 % 0 0% % 0. 10. start CS Inter-RAT Handover Prepare Failure Analysis to display the CS inter-RAT handover details.57 % 0.95 % 0% 2.2 CS Inter-RAT Handover Prepare Failure Analysis In the CS Inter-RAT Handover Analysis.92 % Figure 1-18 CS Inter-RAT Handover Analysis 4.735 CS_INTRAT_HO_OUT_SUCC 40 CS_INTRAT_HO_OUT_FAIL 17. 82. 2005 Confidential Information of Huawei No Spreading Without Permission Page 27 of 46 .38 % 0% 0% Figure 1-19 CS inter-RAT handover prepare failure analysis CS inter-RAT handover prepare failure may be caused by the following reasons: (1) CS_INTERRAT_HO_PREP_FAIL_TARGET_FAIL CS inter-RAT handover prepare failure is caused by Relocation Failure Target CN/RNC or Target System (cause value) because the data Aug.9 % 1. as shown in Figure 1-19.UTRAN KPI Analysis Guide For Internal Use Only 605 CS_INTRAT_HO_OUT_PREP_FAIL 2.3.18 % 80.775 CS_INTRAT_HO_OUT_PREP_SUCC 0 CS_INTRAT_HO_OUT_PREP_FAIL_TARGET_FAIL 0 CS_INTRAT_HO_OUT_PREP_FAIL_TALLOC_EXPIR 0 CS_INTRAT_HO_OUT_PREP_FAIL_TARGET_UNSUPP 13 CS_INTRAT_HO_OUT_PREP_FAIL_RELOC_ABORT 560 CS_INTRAT_HO_OUT_PREP_FAIL_NO_RSRC_AVAIL 0 CS_INTRAT_HO_OUT_PREP_FAIL_UNKNOWTARGET 32 CS_INTRAT_HO_OUT_PREP_FAIL_REQINFNOTAVAI 0 CS_INTRAT_HO_OUT_PREP_FAIL_NO_RSP 0 CS_INTRAT_HO_PREP_FAIL_OTHER 16.

(4) CS_INTERRAT_HO_PREP_FAIL_RELOC_ABORT After sending the handover prepare request. (5) CS_INTERRAT_HO_PREP_FAIL_NO_RSRC_AVAIL CS inter-RAT handover prepare failure is caused by No Resource Available (cause value) because the data configuration of MSC is incorrect or there is no available resource in BSC. Although the previous inter-RAT handover processes are incomplete. track the signaling of core network and BSS for further analysis. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes. such as location update. (6) CS_INTERRAT_HO_PREP_FAIL_UNKNOWTARGET Aug. To locate the problem. To locate the problem. 2005 Confidential Information of Huawei No Spreading Without Permission Page 28 of 46 . To locate the problem. To locate the problem. track the signaling of core network and BSS for further analysis. (2) When inter-RAT handover prepare process is performed. they are normal nested processes. track the signaling of core network and BSS for further analysis. an MS hangs up the call. Thus. track the signaling of core network and BSS for further analysis. (3) CS_INTERRAT_HO_PREP_FAIL_TARGET_UNSUPP CS inter-RAT handover prepare failure is caused by Relocation Not Supported in Target RNC or Target System (cause value) because BSC does not support some parameters of handover requests. Location update process is complete before inter-RAT handover process is complete.UTRAN KPI Analysis Guide For Internal Use Only configuration of core network is incorrect or BSS does not support the handover. core network initializes the release. Thus. core network initializes the release. (2) CS_INTERRAT_HO_PREP_FAIL_TALLOC_EXPIR CS inter-RAT handover prepare failure is caused by TRELOCalloc Expiry (cause value) because the data configuration or link connection of core network is incorrect. RNC receives the release message from core network. 10.

This may be caused by incorrect data configuration or link connection of core network.43 0. (7) CS_INTERRAT_HO_PREP_FAIL_ REQINFNOTAVAI CS inter-RAT handover prepare failure is caused by Requested Information Not Available because the data configuration is incorrect or target BSC does not support the handover. 10. as shown in Figure 1-20.3. 2005 Confidential Information of Huawei No Spreading Without Permission Page 29 of 46 .UTRAN KPI Analysis Guide For Internal Use Only CS inter-RAT handover prepare failure is caused by Unknown Target RNC (cause value) because the data configuration of MSC is incorrect or the LAC of target cell is not configured.56 % 0. 98. start CS Inter-RAT Handover Failure Analysis to display the CS inter-RAT handover details (including CS inter-RAT handover success and failure rates).3 CS Inter-RAT Handover Failure Analysis In the CS Inter-RAT Handover Analysis. track the signaling of core network and BSS for further analysis. (8) CS_INTERRAT_HO_PREP_FAIL_NO_RSP CS inter-RAT handover prepare failure occurs because core network does not respond to the handover prepare request.735 CS_INTRAT_HO_OUT_SUCC 0 CS_INTRAT_HO_OUT_FAIL_CFG_UNSUPP 27 CS_INTRAT_HO_OUT_FAIL_PHYCH_FAIL Figure 1-20 CS inter-RAT handover failure analysis Aug. This problem frequently occurs if a 2G network is adjusted.97 0 % % 0 CS_INTRAT_HO_OUT_FAIL_UNSPEC 0 CS_INTRAT_HO_OUT_FAIL_NO_RSP 12 CS_INTRAT_HO_OUT_FAIL_RELOC_ABORT 1 CS_INTRAT_HO_FAIL_OTHER 2.04 % % 0% 0% 0. To locate the problem. To locate the problem. 4. To locate the problem. track the signaling of core network and BSS for further analysis. check whether any data is incorrectly configured in the core network.

 Some parameters (such as ciphering mode) transmitted to UE are inconsistent with that of BSC.UTRAN KPI Analysis Guide For Internal Use Only CS inter-RAT handover failure may be caused by the following reasons: (1) CS_INTERRAT_HO_ FAIL_UNSPEC CS inter-RAT handover failure is caused by Unspecified (cause value). UE does not acknowledge the request because network coverage is poor. However. This reason is caused by the nesting of handover process and release process. To locate the problem. compare the parameters of UE with that of BSC. This reason seldom occurs in a network. 2005 Confidential Information of Huawei No Spreading Without Permission Page 30 of 46 . CS inter-RAT handover failure is mainly caused by:  The signals of 2G network are weak or UE fails to access the network due to serious interference. 10. (4) CS_INTERRAT_HO_ FAIL_ RELOC_ABORT After sending the handover request message to UE. Aug. the cause is not Normal Release because the link is released abnormally due to other reasons. analyze the RNC logs. To locate the problem. This reason may be mainly caused by abnormal UE. (5) CS_INTERRAT_HO_ FAIL_NO_RSP After RNC sends the handover request message to UE. (6) CS_INTERRAT_HO_ FAIL_OTHER CS inter-RAT handover failure is caused by other reasons. RNC receives the release message from core network. (2) CS_INTERRAT_HO_ FAIL_PHYCN_FAIL CS inter-RAT handover failure is caused by Physical Channel Failure (cause value). (3) CS_INTERRAT_HO_ FAIL_ CFG_UNSUPP CS inter-RAT handover failure is caused by Configuration Unsupported (cause value) because UE does not support the handover request.

The queried results are outputted to list: (1) (2) (3) (4) The cell that have the lowest CS inter-RAT handover success rate The cell that have the greatest CS inter-RAT handover prepare failure times The cell that have the greatest CS inter-RAT handover failure times The cell that have the greatest CS inter-RAT handover times Through the previous results. Thus. as shown in Figure 1-21. 10. you can find the cell that has the greatest CS inter-RAT handover failure times.UTRAN KPI Analysis Guide For Internal Use Only 4. the network coverage must be improved. In addition. Aug.4 PS Inter-RAT Handover Analysis This section consists of the following parts:    Overview PS Inter-RAT Handover Failure Analysis Cell Inter-RAT Handover Analysis 4.3. 2005 Confidential Information of Huawei No Spreading Without Permission Page 31 of 46 . the data configuration must be checked. 4.4.1 Overview PS inter-RAT Handover Analysis is included in Nastar tasks. Double click PS Inter-RAT Handover Analysis to display the PS inter-RAT handover details between a 2G network and a 3G network. you can find the cell that has the greatest CS interRAT handover times. Thus. PS inter-RAT handover from a 2G network to a 3G network need not be analyzed because PS inter-RAT handover from a 2G network to a 3G network cannot be identified in access network. start Cell inter-RAT Handover Analysis to query the TOPN.4 Cell Inter-RAT Handover Analysis In the CS inter-RAT Handover Analysis.

start PS inter-RAT Handover Failure Aug.5 0.9 0. 10. 2005 Confidential Information of Huawei No Spreading Without Permission Page 32 of 46 .2 0.6 Bar Value 0.3 0. PS_INTRAT_HO_OUT_UTRAN_REQ indicates that the PS inter-RAT handover is initialized by the UE in a dedicated channel.1 0 0 Time g b c d e f g RNC:41(ID:41)-PS_INTRAT_HO_OUT_UTRAN_SUCC_RATE RNC:41(ID:41)-PS_INTRAT_HO_OUT_UE_SUCC_RATE Figure 1-22 PS inter-RAT handover success rate 4.2 PS Inter-RAT Handover Failure Analysis In the PS inter-RAT Handover Analysis.UTRAN KPI Analysis Guide For Internal Use Only 10 PS_INTRAT_HO_OUT_UTRAN_REQ 0 PS_INTRAT_HO_OUT_UE_REQ 100 % 0% Figure 1-21 PS inter-RAT handover analysis Figure 1-22 shows PS_INTRAT_HO_OUT_UTRAN_REQ and PS_INTRAT_HO_OUT_UTRAN_UE. 0.4.7 0.4 0. PS_INTRAT_HO_OUT_UTRAN_UE indicates that the PS inter-RAT handover is initialized by combined services or the PS inter-RAT reselection is initialized by the UE that is not in a dedicated channel.8 0.

UTRAN KPI Analysis Guide For Internal Use Only Analysis to display the PS inter-RAT handover success and failure rates. 10. (3) PS_INTERRAT_HO_ FAIL_ CFG_UNSUPP PS inter-RAT handover failure is caused by Configuration Unsupported (cause value) because UE does not support the handover request. Aug. (4) PS_INTERRAT_HO_ FAIL_NO_RSP After RNC sends the handover request message to UE. (2) PS_INTERRAT_HO_ FAIL_PHYCN_FAIL PS inter-RAT handover failure is caused by Physical Channel Failure (cause value) because the signals of 2G network are weak or UE fails to access the network due to serious interference. This reason seldom occurs in a network. as shown in Figure 1-23. This reason may be mainly caused by abnormal UE. 80 % 8 PS_INTRAT_HO_OUT_UTRAN_SUCC 0 PS_HO_OUT_FAIL_CFG_UNSUPP 0 PS_HO_OUT_FAIL_PHYCH_FAIL 0 PS_HO_OUT_FAIL_UNSPEC 0 PS_HO_OUT_FAIL_NO_RSP 2 PS_HO_OUT_FAIL_OTHER 20 % 0% 0% Figure 1-23 PS inter-RAT handover failure analysis PS inter-RAT handover failure may be caused by the following reasons: (1) PS_INTERRAT_HO_ FAIL_UNSPEC PS inter-RAT handover failure is caused by Unspecified (cause value). 2005 Confidential Information of Huawei No Spreading Without Permission Page 33 of 46 . UE does not acknowledge the request because network coverage is poor or UE does not support the handover.

Thus. 2005 Confidential Information of Huawei No Spreading Without Permission Page 34 of 46 .5. you can find the cell that has the greatest PS interRAT handover times. This cell update process is different from that of cell reselection. Cell update process is mainly caused by poor network coverage. start Cell Inter-RAT Handover Analysis to query the TOPN.UTRAN KPI Analysis Guide For Internal Use Only (5) PS_INTERRAT_HO_ FAIL_OTHER PS inter-RAT handover failure is caused by other reasons. To locate the problem. Double click Cell Update Analysis to display the cell update details (including cell update times and cell update success rate). so you must be familiar with diverse cell update processes. the cell update is caused by abnormal links or RLC reset if UE is not Aug. as shown in Figure 1-24.1 Overview Cell Update Analysis is included in Nastar tasks. If the state transition is disabled in a network. The queried results are outputted to list: (1) (2) (3) (4) The cell that have the lowest PS inter-RAT handover success rate The cell that have the greatest PS inter-RAT handover prepare failure times The cell that have the greatest PS inter-RAT handover failure times The cell that have the greatest PS inter-RAT handover times Through the previous results. Cell update process is initialized because the links of UE are abnormal or RLC is reset.5 Cell Update Analysis This section consists of the following parts:   Overview Cell Update Failure Analysis 4. In the Cell Update Analysis.3 Cell Inter-RAT Handover Analysis In the PS Inter-RAT Handover Analysis. 4. 4.4. analyze the RNC logs. the network coverage must be improved. 10. start Cell Update Scenario Analysis to display different cell update scenarios.

93. click Create a Bar Chart to display the cell update success rates.UTRAN KPI Analysis Guide For Internal Use Only in CELL_FACH or CELL_PCH state. the cell updates are caused by abnormal links (RL) or RLC reset (RLC_ERR). If cell update is caused by other reasons.05 0.07 0.01 0 0 Time g g g g g g g g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_RESEL RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_REENTER RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_PAGE RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_UL_DATA_TRANS RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_RLC_ERR RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_RL RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_PRD RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_OTHER Figure 1-25 Cell update success rates Aug.03 0. 0.64 % 0 0 0 211 15 0 0 0 CELL_UPDT_REENTER CELL_UPDT_PAGE CELL_UPDT_UL_DATA_TRANS CELL_UPDT_RLC_ERR CELL_UPDT_RL_FAIL CELL_UPDT_PRD CELL_UPDT_RESEL CELL_UPDT_OTHER Figure 1-24 Cell update scenarios In the Cell Update Scenario Analysis. thus low cell update success rate may be caused by poor network coverage.02 0.06 Bar Value 0. cell update success rate must be greater than 85%.36 % 0% 0% 6. 2005 Confidential Information of Huawei No Spreading Without Permission Page 35 of 46 . In general.04 0. as shown in Figure 1-25. 10.

VP. Double click Call Drop Analysis to display the RNC call drop details.UTRAN KPI Analysis Guide For Internal Use Only 4. start Cell Update Analysis to query the TOPN.5. 4.6. start Cell Update Scenario Analysis for Cell to analyze the cell update failure and summarize the cell update failure scenarios. cell update times are less. Aug. CS.2 Cell Update Failure Analysis In the Cell Update Analysis. The queried results are outputted to list: (1) (2) The cell that has the lowest cell update success rate The cell that has the greatest cell update failure times If a cell has the lowest cell update success rate. Attention must be paid to the cell that has the greatest cell update failure times.1 Overview Call Drop Analysis is included in Nastar tasks. and PS).6 Call Drop Analysis This section consists of the following parts:     Overview CS Call Drop Analysis PS Call Drop Analysis Cell Call Drop Analysis 4. click Create a Pie Chart to display the call drop details for different services (including voice. In the queried results of Cell Update Analysis. as shown in Figure 1-27. 10. Then. 2005 Confidential Information of Huawei No Spreading Without Permission Page 36 of 46 .

25 0.65 0. as shown in Figure 1-27.35 0.54 % RNC_CS_RAB_REL_AMR_TRIG_BY_RNC RNC_CS_RAB_REL_CONV_64K_TRIG_BY_RNC RNC_CS_RAB_REL_STR_TRIG_BY_RNC RNC_PS_RAB_REL_REQ 86. click Create a Bar Chart to display the call drop rates for different services (including voice. the call drop rate of CS service is less than that of VP service or PS service because of their different service coverage capabilities and service process complexities.6. In general.2 0.5 0.55 0. VP. click Create a Pie Chart to display the CS call drop reasons.05 0 0 Time Bar Value g g RNC:41(ID:41)-CS_RAB_AMR_DROP_RATE g RNC:41(ID:41)-CS_RAB_STR_DROP_RATE g RNC:41(ID:41)-CS_RAB_VP_DROP_RATE RNC:41(ID:41)-PS_RAB_DROP_RATE Figure 1-27 Call drop rates 4. 2005 Confidential Information of Huawei No Spreading Without Permission Page 37 of 46 .UTRAN KPI Analysis Guide For Internal Use Only 0% 1. 0.45 0.34 % 75 8 0 515 12.15 0. especially in the poor-covered areas. Aug.1 0.12 % Figure 1-26 Call drop analysis In the Cell Drop Analysis. and PS).3 0. as shown in Figure 1-28.4 0. CS.2 CS Call Drop Analysis In the CS Call Drop Analysis. 10.6 0.

34 % 75 8 0 515 12.UTRAN KPI Analysis Guide For Internal Use Only 0% 1. If this reason occurs. this reason seldom occurs. To solve the problem. the problem may be caused by any faulty or defective equipment. In the early network. In practice. call drops are mainly caused by this reason. normal release is recorded as abnormal release during the RB setup process. (3) RNC_CS_RAB_REL_TRIG_BY_RNC_AAL2_LOSS If IU CS interface (AAL2 path) is abnormal. This reason is mainly caused by poor network coverage (including adjacent cell missing and small handover area). UE closes the transmitter abnormally or uplink demodulation is asynchronous. 10. RNC initializes the release. As a result. To solve the problem. Aug.54 % RNC_CS_RAB_REL_AMR_TRIG_BY_RNC RNC_CS_RAB_REL_CONV_64K_TRIG_BY_RNC RNC_CS_RAB_REL_STR_TRIG_BY_RNC RNC_PS_RAB_REL_REQ 86. (2) RNC_CS_RAB_REL_TRIG_BY_RNC_SRB_RESET CS call drops may be caused by link releasing due to downlink SRB reset. 2005 Confidential Information of Huawei No Spreading Without Permission Page 38 of 46 . small handover area. the network coverage must be improved. In some versions of RNC. call drops are mainly caused by this reason. network coverage must be improved. In the early network.12 % Figure 1-28 CS call drop reasons CS call drops may be caused by the following reasons: (1) RAB_CS_REL_RF_LOSS CS call drop may be caused by abnormal release caused by the lost synchronization of links because of poor network coverage (including adjacent cell missing.

As a result. network coverage must be improved. To solve the problem. 10. as shown in Figure 1-29. UE closes the transmitter abnormally or uplink demodulation is asynchronous.91 % RAB_PS_REL_RF_LOSS RNC_PS_RAB_REL_TRIG_BY_RNC_TRB_RESET RNC_PS_RAB_REL_TRIG_BY_RNC_SRB_RESET RNC_PS_RAB_REL_TRIG_BY_RNC_GTPU_LOSS PS_RAB_DROP_OTHER 51. There are few call drop statistics in RNC (Version 12). 2005 Confidential Information of Huawei No Spreading Without Permission Page 39 of 46 . (2) RNC_PS_RAB_REL_TRIG_BY_RNC_SRB_RESET Aug. 4.UTRAN KPI Analysis Guide For Internal Use Only (4) CS_RAB_DROP_OTHER CS call drops may be caused by other reasons.05 % 0% 2. This reason is mainly caused by poor network coverage (including adjacent cell missing and small handover area). start PS Call Drop Analysis. click Create a Pie Chart to display the PS call drops. call drops are mainly caused by this reason. 40. In practice.65 % Figure 1-29 PS call drop reasons PS call drop may be caused by the following reasons: (1) RAB_PS_REL_RF_LOSS PS call drops may be caused by abnormal release because the links are asynchronous.3 PS Call Drop Analysis In the Call Drop Analysis. Therefore. Such reasons as process interaction timeout and cell update failure are recorded in CS_RAB_DROP_OTHER. Then. these call drops are recorded in CS_RAB_DROP_OTHER. many call drops are caused by process interaction timeout and cell update failure.6. In the early network.39 % 15 26 208 0 266 5.

If this reason occurs. call drops are mainly caused by this reason. To solve the problem. call drops are mainly caused by this reason. In the early network. In practice. Such reasons as process interaction timeout and cell update failure are recorded in PS_RAB_DROP_OTHER. as shown in Figure 1-30. many call drops are caused by process interaction timeout and cell update failure. the problem may be caused by any faulty or defective equipment. In practice. (5) PS_RAB_DROP_OTHER PS call drops may be caused by other reasons. Therefore. This reason is mainly caused by poor network coverage (including adjacent cell missing and small handover area). 10. (3) RNC_PS_RAB_REL_TRIG_BY_RNC_TRB_RESET PS call drops may be caused by link releasing due to downlink TRB reset. This reason is mainly caused by poor network coverage (including adjacent cell missing and small handover area). In the early network. start Cell Call Drop Analysis. this reason seldom occurs. the network coverage must be improved. 4.4 Cell Call Drop Analysis In the Cell Drop Call Analysis. and then click Create a Pie Chart to display the cell drop reasons. There are few call drop statistics in RNC (Version 12).6. query the TOPN to find the cell that has the greatest CS call drop rate. To solve the problem. 2005 Confidential Information of Huawei No Spreading Without Permission Page 40 of 46 . RNC initializes the release. Aug.UTRAN KPI Analysis Guide For Internal Use Only PS call drops may be caused by link releasing due to downlink SRB reset. (4) RNC_PS_RAB_REL_TRIG_BY_RNC_GTPU_LOSS If IU CS interface (AAL2 path) is abnormal. these call drops are recorded in PS_RAB_DROP_OTHER. the network coverage must be improved.

(4) RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_AAL2_LOSS If IU CS interface (AAL2 path) is abnormal. the network coverage must be improved. In practice. (3) RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_UTRAN Cell call drops may be caused by abnormal link releasing due to UTRAN. (2) RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_SRB_RESET Cell call drops may be caused by link releasing due to downlink SRB reset.UTRAN KPI Analysis Guide For Internal Use Only 0% 33. Actually. 10. If this reason occurs.33 % 0 RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_OM 0 RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_UTRAN 0 RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_RAB_PREM 2 RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_SRBRESET 0 RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_AAL2LOSS 4 CS_RAB_DROP_CELL_OTHER 0% 0% 66. To solve the problem.67 % Figure 1-30 CS cell drop reasons CS Cell call drops may be caused by the following reasons: (1) RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_OM Cell call drops may be caused by CS link releasing due to operation and maintenance (for example. the problem may be caused by any faulty or defective equipment. RNC initializes the release. call drops are mainly caused by this reason. (5) RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_RAB_PREM Cell call drops may be caused by CS link releasing due to high priority Aug. use CDL for further analysis. 2005 Confidential Information of Huawei No Spreading Without Permission Page 41 of 46 . cell block). This reason is mainly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem. In the early network. this reason seldom occurs. cell call drops caused by this reason are normal.

You can choose Time Range or Query Object to query the RNC traffic load. Check whether the expansion is required according to cell call drop times. cell call drop may occur. (6) CS_RAB_DROP_CELL_OTHER Cell call drops may be caused by other reasons. 4. these call drops are recorded in CS_RAB_DROP_CELL_OTHER. as shown in Figure 1-32. If load or resource is insufficient. Such reasons as process interaction timeout and cell update failure are recorded in CS_RAB_DROP_CELL_OTHER.1 Overview Traffic Load Analysis is included in Nastar tasks. In practice. 2005 Confidential Information of Huawei No Spreading Without Permission Page 42 of 46 . Therefore.UTRAN KPI Analysis Guide For Internal Use Only preemption. Aug.7. Double click Traffic Load Analysis to display the RNC traffic load details. There are few call drop statistics in RNC (Version 12).7 Traffic Load Analysis This section consists of the following parts:   Overview Cell Traffic Analysis 4. many call drops are caused by process interaction timeout and cell update failure. 10.

The unit of traffic load is Erl. 10. click Create a Pie Chart to display the traffic load details. Aug. traffic load proportions are displayed in Figure 1-33.UTRAN KPI Analysis Guide For Internal Use Only Figure 1-32 Query traffic load Choose Busy Time (Busy Time can be Automatic Querying or Designated Time). 2005 Confidential Information of Huawei No Spreading Without Permission Page 43 of 46 . In the Traffic Load Analysis. UNKNOWN_USER indicates that the subscribers are from other RNC and service type is unknown. Assume that the subscribers for different services are equivalent.

If the RTWP of a cell is greater than -100 dBm. The burst interference exerts little influence on the system but the continuous interference must be eliminated on a timely basis.808 PS_INTER_BKG_USER 0.2 Cell Traffic Analysis If a cell has the highest traffic.3 % 85.7.UTRAN KPI Analysis Guide For Internal Use Only 0% 0% 14. as shown in Figure 1-34. it is the most important cell in a network. In the Traffic Load Analysis. Aug. the cell is easily congested and need to be expanded. Check whether it is the burst interference or continuous interference.09 UNKNOWN_USER 0.388 CS_CONV_USER 0 CS_STR_USER 0 PS_CONV_USER 0 PS_STR_USER 25. 2005 Confidential Information of Huawei No Spreading Without Permission Page 44 of 46 . start Cell RTWP Analysis.21 % Figure 1-33 Traffic Load 4. In practice.49 % 4. If the cells have large RTWP_MAX_CELL_DBM values. In addition. start Cell Traffic Analysis to query the TOPN. The queried results are outputted as follows: (1) (2) (3) (4) The cell that has the greatest RTWP The cell that has the greatest TCP The cell that has the greatest DCH UE The cell that has the greatest downlink admission rejects The cell that has the greatest RTWP represents the cell that has the greatest uplink radio load. the cell must be analyzed. 10. this queried result can be used to find the cell that is seriously interfered.

The cell that has the greatest DCH UE is used to measure the subscriber number of a cell. The cell that has the greatest DL ADMSN DENY is used to measure the cell that has the greatest downlink radio load. downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and the downlink is of interference. and re-configuration. In practice. the cell also has the greatest downlink admission rejects. 10. or the indoor coverage for high traffic area must be improved. Aug. if the cell has the greatest downlink radio load. check whether the cross coverage is serious and check whether the indoor coverage of high traffic area must be improved to decrease large power consumption. For the cell that has the greatest DL ADMSN DENY. In practice. In this way. you can further understand the influence exerted on the subscribers. the average CE and transmission can be estimated to further check whether the resources are sufficient. start Cell Resource Analysis to display the admission reject proportions of call setup. Combined with the utilization of OVSF codes. 2005 Confidential Information of Huawei No Spreading Without Permission Page 45 of 46 .UTRAN KPI Analysis Guide For Internal Use Only -65 -70 -75 -80 Items -85 -90 -95 -100 -105 2005-04-21 00:00:00 2005-04-21 04:30:00 2005-04-21 09:30:00 2005-04-21 14:30:00 DateTime 2005-04-21 19:30:00 b c d e f g RTWP_MAX_CELL_DBM Figure 1-34 Cell RTWP analysis The cell that has the greatest TCP represents the cell that has the greatest downlink radio load. For such cell. incoming handover. If a cell has the greatest DL ADMSN DENY. check whether the cross coverage is serious. the handover area is unreasonable.

Aug. 5. but the results.3 Analyzing Repeated Problems If time range or area range falls within a fixed scope after the KPI analysis is performed for several days.2 Analyzing Abnormal Logs Execute the command LST CELL in MML on the RNC maintenance console to find the service subrack. Therefore.UTRAN KPI Analysis Guide For Internal Use Only 5. Analyzing Complicated Problems Further analysis is necessary because the KPI of traffic statistics does not represent the processes. 5. use Sample Trace on the RNC maintenance console in a given time to obtain the detailed call procedure for further analyzing problem causes and involved subscribers. use the following methods:    Narrowing down area range and time range Analyzing abnormal logs Analyzing repeated problems 5. reasons. Then. 10. and involved subscribers. Some reasons may not be found through the KPI analysis.1 Narrowing Down Area Range and Time Range The area range of abnormal traffic statistics can be determined by querying the TOPN. To analyze complicated problems. it is necessary for us to use further analysis to locate complicated problems. send the CDL of service subrack from BAM to a service engineer for further analyzing abnormal processes. After determining the area range. query the time range of problem (The time range falls within 30 minutes). 2005 Confidential Information of Huawei No Spreading Without Permission Page 46 of 46 .

Sign up to vote on this title
UsefulNot useful