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

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

10. 3.UTRAN KPI Analysis Guide For Internal Use Only practical solutions. Aug. 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. as shown in Table 1-1. Considering the features of wireless communication network. 2.800. refer to GENEX Nastar V400R001C01 User Manual. Introduction to Nastar Nastar provides such functions as index defining. and report generating. the following KPI must be considered for WCDMA RAN.1 Nastar Tasks Figure 1-1 shows a list of Nastar tasks. 2005 Confidential Information of Huawei No Spreading Without Permission Page 6 of 46 . For more information. query defining. UTRAN KPI Analysis The QoS of communication network is defined in ITU-T E.

87%(36445/37624) 99.60%(997/1001) 99. An object can be a self-defined clutter or RNC.67%(4/6) 1. 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. Perf Daily Report is used to monitor network performance.00%(29/29) 99.5%) CDR Video Call Drop Rate(< 1. By default.01%(30/997) Aug.00%(16/16) 100.5%) PS Service Drop Rate(< 30%) RN C: 1 17.00%(990/1000) 100. 10.92%(19/990) 10.09(12:00 ~ 13:00) 98.75%(17090/17132) 99.xls file by Nastar.31%(2016/2030) 99.64%(2468/2502) 96.13(16:00 ~ 17:00) 54.66%(3509/3521) 18.34%(3/29) 3. as shown in Table 1-2. 2005 Confidential Information of Huawei No Spreading Without Permission Page 7 of 46 .00%(4/4) 66. Perf Daily Report includes the following KPI.85% 100.UTRAN KPI Analysis Guide For Internal Use Only Figure 1-1 Nastar tasks Perf Daily Report and Perf Weekly Report can be generated in .

10. RRC setup success rate is 97.961 RRC_SETUP_SUCC 7 RRC_REJ 2.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.01 % Figure 1-3 RRC Setup Aug.69 % 0.186 RRC_SETUP_FAIL_NO_RSP 97. Double click RRC Setup Analysis to display the RRC setup details. as shown in Figure 1-1. Overview RRC Setup Analysis is included in Nastar. UTRAN KPI Analysis 4.1 Call Completion Rate This section consists of the following parts:   RRC Setup Analysis RAB Setup Analysis 4.3 % 2. 78. 4.1 RRC Setup Analysis 1.1. 2005 Confidential Information of Huawei No Spreading Without Permission Page 8 of 46 .3%. Most RRC setup failures result from RRC Setup Fail No Response while few RRC setup failures (seven times) result from RRC Setup Reject. refer to Section 4 UTRAN KPI Analysis. as shown in Figure 1-3.

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

UTRAN KPI Analysis Guide For Internal Use Only 0. 3. RRC SETUP SUCC RATE ORG is very high while RRC SETUP SUCC RATE REG is very low.98 Bar Value 0. In RRC Setup Analysis. 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.96 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 10 of 46 . which has poor coverage.97 0.975 0. start Cell RRC Analysis to query the TOPN. only the areas of RRC setup reject must be analyzed.955 0. On Huawei networks.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. Aug. resident threshold Ec/Io is greater than -18 dB while inter-system reselection start threshold Ec/Io is less than -14 dB.95 0. Therefore.945 0 Time 0. The queried results are outputted in three pages: (1) The top ten cells that have the highest RRC setup reject times. however. Low RRC SETUP SUCC RATE REG indicates that many registrations are attempted within the area (Ec/Io falls between -14 dB and -18 dB). RRC setup reject occurs in a small-scale network. 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.985 0.99 0.

If network load is heavy. 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. so RRC setup reject occurs. (2) CE Congestion Aug.UTRAN KPI Analysis Guide For Internal Use Only (2) The top ten cells that have the highest RRC setup success rates. check whether the threshold is reasonable. 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 RRC Reject Analysis for further analysis. check whether there is any interference. To locate the problem. and check whether the network capacity is insufficient. power congestion may occur. two RRC setup rejects are caused by Power Congestion. (3) The top ten cells that have the highest RRC setup failure rates. In this figure. For the top ten cells that have the maximum RRC setup rejects. 2005 Confidential Information of Huawei No Spreading Without Permission Page 11 of 46 . If power congestion is confirmed. 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. 10. For the top ten cells that have the maximum RRC setup fail rates. start Cell Scenario Analysis for further analysis.

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

UTRAN KPI Analysis Guide For Internal Use Only Figure 1-7 Nastar tasks Figure 1-7 shows a list of Nastar tasks. 64 K (PS).37 % 2.15 % 0. as shown in Figure 1-8. Double click RAB Setup Analysis to display RAB setup details. 10. 73.19 % 3.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.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. and 384 K Aug.13 % 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 13 of 46 . CS_RAB_REQ_SETUP_CONV_32_64 (VP). 128 K (PS).

2 0. as shown in Figure 1-9. The top ten cells that have the lowest PS RAB setup failures. RAB Setup Fail Analysis In RAB Setup Analysis. Low RAB setup success rate may occur in the cells that have lowest setup times. Aug.4 0. To locate the problem. as shown in Figure 1-10. 2005 Confidential Information of Huawei No Spreading Without Permission Page 14 of 46 .1 1 0. If CS RAB setup fail rate is high in a cell.9 0. 1.3 0. 10. The queried results are outputted in four pages: (1) (2) (3) (4) The top ten cells that have the highest CS RAB setup failures. start Cell RAB Analysis to query the TOPN. focus on the cells that have the lowest setup failures because the KPI is affected mostly by these cells.6 0. start Cell CS RAB Setup Fail Analysis to display the CS RAB setup fail rates.8 Bar Value 0. The top ten cells that have the lowest CS RAB setup failures. Click Produce a Bar Chart to display the RB and RAB setup success rates. The top ten cells that have the highest PS RAB setup failures.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.5 0.7 0.UTRAN KPI Analysis Guide For Internal Use Only (PS) to confirm major services in the network.

so this reason seldom occurs. analyze the RNC logs and obtain the detailed resource failure information.63 0 % 0 % 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 15 of 46 . (2) RELOC_CELL When initializing the migration process. To locate the problem.UTRAN KPI Analysis Guide For Internal Use Only 99. (5) POWER_CONG_CELL Aug.05 % 0 % % 0. This reason is mainly caused by the process integration related to subscriber action sequence. 10. In a core network. this situation is always avoided. (4) CONG_CELL This may be caused by RNC resource allocation failure. To locate the problem. (3) TNL_CELL RAB setup fails because IU transmission setup fails. RNC receives the RAB setup request messages but RNC does not process the request.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. To locate the problem. track the signaling and check the RAB setup messages in specific cells. This reason seldom occurs. check the transmission capacity and operation stability.32 0 % % 0% 1.

as shown in Figure 1-11.UTRAN KPI Analysis Guide For Internal Use Only According to RRM admission decision.09 % 0% 0% 9. check whether the parameters of admission algorithm are reasonable. (7) CODE_CONG_CELL During the RAB setup process. (8) OTHER_CELL This may caused by RB setup failure or other reasons. analyze RB setup success rates. 84.09 % 0% 0% % 6. analyze the code resource of cell traffic to check whether code resource is restricted due to cell overload. (6) CE_CONG_CELL CE resource admission fails in RNC. 2005 Confidential Information of Huawei No Spreading Without Permission Page 16 of 46 . 10. If yes. code resource allocation fails because too many subscribers are crowded on the network or code resource allocation fails. CE must be expanded. To locate the problem. To locate the problem. new RAN cannot be set up because cell load is too heavy. consider to optimize the coverage and expand the capacity. If PS RAB setup fail rate is high.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. To locate the problem. start Cell PS RAB Setup Fail Analysis to display the PS RAB setup fail rates.

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

99. To analyze the RB setup failure. This reason seldom occurs. as shown in Figure 1-12. 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. 10. It is mainly caused by UE defects.06 % % 0% 1. RNC processing ensures RRC processes nesting. (9) OTHER_CELL This may caused by RB setup failure or other reasons.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.18 % 0 0. analyze RB setup success rates. (3) SIMU_RECFG_INCOMP UE regards that the RB setup process and other processes simultaneously occur and they are incompatible. Aug. In a commercial network. The rooted reason is poor coverage.76 % 0.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 . This reason seldom occurs in the network. It is mainly caused by compatibility problem of UE in some unknown scenarios. start Cell RB Setup Fail Analysis to display the RB setup fail rates. To locate the problem.

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

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

97 0. soft handover factor is used to measure the proportion and cost of soft handover.005 1 0.995 0.99 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 21 of 46 . 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.98 0. 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. SHO_FACTOR_RL and SHO_FACTOR_UE are defined as follows:  SHO_FACTOR_RL SHO_FACTOR_RL is used to measure average link number.96 0.955 0.UTRAN KPI Analysis Guide For Internal Use Only 1.975 0. 10.95 0.965 0.945 0.985 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.94 0. SHO_FACTOR_UE is used to measure the reasonable Aug. which is similar to the proportion of soft handover area by making drive tests.  SHO_FACTOR_UE SHO_FACTOR_UE is used to measure the proportion of soft handover subscribers.

low soft handover success rates may exist in the cells that have less soft handover times. 2005 Confidential Information of Huawei No Spreading Without Permission Page 22 of 46 .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. To query the cells that have the highest soft handover prepare failure times. SHO_FACTOR_RL is greater than 1 while SHO_FACTOR_UE is less than 1. If the subscriber number of link 3 of active set is very great. 4. start Cell SHO Analysis to query the TOPN. 10. start Cell SHO Prepare Failure Analysis to display the soft handover prepare failure details. the greater the subscriber number of link 3 of active set is. 0% 9. The greater the difference between them is. 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. 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. SHO_FACTOR_UE is greater than SHO_FACTOR_UE.2.2 Cell SHO Prepare Failure Analysis In the Soft Handover Analysis. as shown in Figure 1-15.54 % Figure 1-15 Cell SHO Prepare Failure Analysis Aug.UTRAN KPI Analysis Guide For Internal Use Only relationship between soft handover area and soft handover distribution.

To locate the problem. RNC logs must be used for further analysis. 4. (3) SHO_PREP_FP_SYNC_FAIL When the links are added during the soft handover. one or more boards must be added for expansion. Internal NodeB logs. (2) SHO_PREP_AAL2_SETUP_FAIL When the links are added during the soft handover. If the transmission bandwidth is insufficient. and RNC link state reject. and data configuration of NodeB boards can be used to locate the problems. If NodeB CE resource is insufficient. radio resource admission reject. the synchronization of AAL2 and FP of lub interface fails. 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. 10. transmission equipments must be expanded.2. check whether the intermittent transmission interruption occurs or the IMA group transmission is incorrectly configured. 2005 Confidential Information of Huawei No Spreading Without Permission Page 23 of 46 . To locate the problem. such as insufficient RNC resource. start Cell SHO Analysis to query the TOPN. Cell Traffic Load Analysis.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. (4) SHO_PREP_ FAIL_OTHER_CELL Soft handover prepare failure is caused by other reasons.3 Cell SHO Failure Analysis In the Soft Handover Analysis. the AAL2 setup of lub interface fails because the transmission bandwidth is insufficient.

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. This reason seldom occurs in a commercial network. When handling the processes.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. (4) SHO_RL_ADD_FAIL_NO_RSP Aug. The problem is mainly caused by some handsets. (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.75 % 0. low soft handover success rates may exist in the cells that have less soft handover times. 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. RNC performs the serial connection. 2005 Confidential Information of Huawei No Spreading Without Permission Page 24 of 46 . 0 0. as shown in Figure 1-16. In the Cell SHO Analysis. 10.14 % 0 0% % 0% 0% 2. 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.11 % % 99.

Soft handover failure is mainly caused by this reason. (9) SHO_FAIL_OTHER_CELL Soft handover failure is caused by other reasons. 2005 Confidential Information of Huawei No Spreading Without Permission Page 25 of 46 . When handling the processes. soft handover failure easily occurs. the RF optimization is required. the RF optimization is required. 10. soft handover failure easily occurs. If soft handover failure is caused by other reasons. RNC performs the serial connection. (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. If network coverage is poor or soft handover area is small. 4. soft handover failure is seldom caused by other reasons. Soft handover failure is mainly caused by this reason.UTRAN KPI Analysis Guide For Internal Use Only RNC does not receive the acknowledgement of active set update of adding radio links. If network coverage is poor or soft handover area is small. (8) SHO_RL_ADD_FAIL_NO_RSP RNC does not receive the acknowledgement of active set update of deleting radio links.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. This reason seldom occurs in a commercial network. This reason seldom occurs in a commercial network. (5) SHO_RL_DEL_FAIL_CFG_UNSUPP UE does not support to delete radio links in RNC during the active set update. analyze the logs to locate the problems. The problem is mainly caused by some handsets. Thus. however. (7) SHO_RL_ADD_FAIL_CFG_INVALID UE regards the active set update of deleting radio links in RNC as invalid configuration. Thus.

Aug. 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. as shown in Figure 1-17. and CS inter-RAT handover failure rate). CS inter-RAT handover prepare failure rate. 2005 Confidential Information of Huawei No Spreading Without Permission Page 26 of 46 .UTRAN KPI Analysis Guide For Internal Use Only  Cell Inter-RAT Handover Analysis 4. CS inter-RAT handover between a 2G network and a 3G network seldom occurs. as shown in Figure 1-18. In a commercial network.1 Overview Figure 1-17 Nastar tasks CS Inter-RAT Handover Analysis is included in Nastar tasks. 10.3.

9 % 1. as shown in Figure 1-19.18 % 80. 82.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.2 CS Inter-RAT Handover Prepare Failure Analysis In the CS Inter-RAT Handover Analysis.3.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. start CS Inter-RAT Handover Prepare Failure Analysis to display the CS inter-RAT handover details. 2005 Confidential Information of Huawei No Spreading Without Permission Page 27 of 46 .95 % 0% 2.735 CS_INTRAT_HO_OUT_SUCC 40 CS_INTRAT_HO_OUT_FAIL 17.1 % 0 0% % 0.57 % 0.92 % Figure 1-18 CS Inter-RAT Handover Analysis 4.UTRAN KPI Analysis Guide For Internal Use Only 605 CS_INTRAT_HO_OUT_PREP_FAIL 2. 10.

(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. track the signaling of core network and BSS for further analysis. 10. Location update process is complete before inter-RAT handover process is complete. Although the previous inter-RAT handover processes are incomplete. (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. (4) CS_INTERRAT_HO_PREP_FAIL_RELOC_ABORT After sending the handover prepare request. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes. (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. To locate the problem. (6) CS_INTERRAT_HO_PREP_FAIL_UNKNOWTARGET Aug. To locate the problem. they are normal nested processes. 2005 Confidential Information of Huawei No Spreading Without Permission Page 28 of 46 . To locate the problem. Thus. core network initializes the release.UTRAN KPI Analysis Guide For Internal Use Only configuration of core network is incorrect or BSS does not support the handover. such as location update. To locate the problem. (2) When inter-RAT handover prepare process is performed. 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. RNC receives the release message from core network. core network initializes the release. track the signaling of core network and BSS for further analysis.

as shown in Figure 1-20.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. 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.43 0. 4. 98. To locate the problem. (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.3 CS Inter-RAT Handover Failure Analysis In the CS Inter-RAT Handover Analysis. To locate the problem.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. (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. track the signaling of core network and BSS for further analysis.04 % % 0% 0% 0. This may be caused by incorrect data configuration or link connection of core network. 10. check whether any data is incorrectly configured in the core network. track the signaling of core network and BSS for further analysis. 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. To locate the problem. 2005 Confidential Information of Huawei No Spreading Without Permission Page 29 of 46 .

(2) CS_INTERRAT_HO_ FAIL_PHYCN_FAIL CS inter-RAT handover failure is caused by Physical Channel Failure (cause value). To locate the problem. 10. This reason may be mainly caused by abnormal UE. (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. 2005 Confidential Information of Huawei No Spreading Without Permission Page 30 of 46 . To locate the problem. UE does not acknowledge the request because network coverage is poor.  Some parameters (such as ciphering mode) transmitted to UE are inconsistent with that of BSC. analyze the RNC logs.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). RNC receives the release message from core network. (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. the cause is not Normal Release because the link is released abnormally due to other reasons. However. (4) CS_INTERRAT_HO_ FAIL_ RELOC_ABORT After sending the handover request message to UE. This reason seldom occurs in a network. compare the parameters of UE with that of BSC. Aug. 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. This reason is caused by the nesting of handover process and release process.

4. In addition. you can find the cell that has the greatest CS inter-RAT handover failure times. as shown in Figure 1-21. Aug. 10.4 Cell Inter-RAT Handover Analysis In the CS inter-RAT Handover Analysis. 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.UTRAN KPI Analysis Guide For Internal Use Only 4. Double click PS Inter-RAT Handover Analysis to display the PS inter-RAT handover details between a 2G network and a 3G network. 2005 Confidential Information of Huawei No Spreading Without Permission Page 31 of 46 .1 Overview PS inter-RAT Handover Analysis is included in Nastar tasks. Thus. the network coverage must be improved. you can find the cell that has the greatest CS interRAT handover times. 4.3. the data configuration must be checked.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. Thus. 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.

2 PS Inter-RAT Handover Failure Analysis In the PS inter-RAT Handover Analysis. 10.6 Bar Value 0.4 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 32 of 46 .8 0.9 0.3 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. start PS inter-RAT Handover Failure Aug. 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.5 0.4.7 0.2 0. 0.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.

This reason may be mainly caused by abnormal UE. as shown in Figure 1-23. Aug. (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. (4) PS_INTERRAT_HO_ FAIL_NO_RSP After RNC sends the handover request message to UE.UTRAN KPI Analysis Guide For Internal Use Only Analysis to display the PS inter-RAT handover success and failure rates. (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. 10. UE does not acknowledge the request because network coverage is poor or UE does not support the handover. 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 .

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

10. 0.05 0.06 Bar Value 0. the cell updates are caused by abnormal links (RL) or RLC reset (RLC_ERR). cell update success rate must be greater than 85%.36 % 0% 0% 6. as shown in Figure 1-25.07 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 35 of 46 .UTRAN KPI Analysis Guide For Internal Use Only in CELL_FACH or CELL_PCH state. If cell update is caused by other reasons. 93.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. thus low cell update success rate may be caused by poor network coverage. click Create a Bar Chart to display the cell update success rates. In general.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.03 0.02 0.04 0.

Attention must be paid to the cell that has the greatest cell update failure times.2 Cell Update Failure Analysis In the Cell Update Analysis.1 Overview Call Drop Analysis is included in Nastar tasks. 10.UTRAN KPI Analysis Guide For Internal Use Only 4. Aug. as shown in Figure 1-27.6. In the queried results of Cell Update Analysis. Then. and PS). click Create a Pie Chart to display the call drop details for different services (including voice. 2005 Confidential Information of Huawei No Spreading Without Permission Page 36 of 46 . CS. start Cell Update Analysis to query the TOPN. start Cell Update Scenario Analysis for Cell to analyze the cell update failure and summarize the cell update failure scenarios.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. Double click Call Drop Analysis to display the RNC call drop details.5. cell update times are less. 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. 4. VP.

as shown in Figure 1-27. 10. Aug.4 0.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. especially in the poor-covered areas.3 0. and PS).65 0.35 0.2 0. 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. click Create a Pie Chart to display the CS call drop reasons.15 0.55 0.12 % Figure 1-26 Call drop analysis In the Cell Drop Analysis. CS. 2005 Confidential Information of Huawei No Spreading Without Permission Page 37 of 46 . In general.6 0. click Create a Bar Chart to display the call drop rates for different services (including voice.UTRAN KPI Analysis Guide For Internal Use Only 0% 1. VP.45 0.5 0.25 0.6.34 % 75 8 0 515 12. 0. as shown in Figure 1-28.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 CS Call Drop Analysis In the CS Call Drop Analysis.1 0.

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

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

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

To solve the problem. 2005 Confidential Information of Huawei No Spreading Without Permission Page 41 of 46 . This reason is mainly caused by poor network coverage (including adjacent cell missing and small handover area). use CDL for further analysis. the network coverage must be improved. (3) RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_UTRAN Cell call drops may be caused by abnormal link releasing due to UTRAN.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. RNC initializes the release. cell call drops caused by this reason are normal. In the early network. (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. the problem may be caused by any faulty or defective equipment. 10. To solve the problem. this reason seldom occurs. In practice. (4) RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_AAL2_LOSS If IU CS interface (AAL2 path) is abnormal. (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.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.UTRAN KPI Analysis Guide For Internal Use Only 0% 33. cell block). If this reason occurs. Actually. call drops are mainly caused by this reason.

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

10. traffic load proportions are displayed in Figure 1-33. Aug. The unit of traffic load is Erl. Assume that the subscribers for different services are equivalent.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). In the Traffic Load Analysis. 2005 Confidential Information of Huawei No Spreading Without Permission Page 43 of 46 . UNKNOWN_USER indicates that the subscribers are from other RNC and service type is unknown. click Create a Pie Chart to display the traffic load details.

If the RTWP of a cell is greater than -100 dBm. In the Traffic Load Analysis. Aug.2 Cell Traffic Analysis If a cell has the highest traffic. this queried result can be used to find the cell that is seriously interfered.808 PS_INTER_BKG_USER 0.49 % 4. If the cells have large RTWP_MAX_CELL_DBM values. the cell is easily congested and need to be expanded.3 % 85. 2005 Confidential Information of Huawei No Spreading Without Permission Page 44 of 46 . start Cell RTWP Analysis. as shown in Figure 1-34.21 % Figure 1-33 Traffic Load 4. the cell must be analyzed. 10. In addition.7. it is the most important cell in a network.388 CS_CONV_USER 0 CS_STR_USER 0 PS_CONV_USER 0 PS_STR_USER 25.UTRAN KPI Analysis Guide For Internal Use Only 0% 0% 14.09 UNKNOWN_USER 0. Check whether it is the burst interference or continuous interference. The burst interference exerts little influence on the system but the continuous interference must be eliminated on a timely basis. In practice. 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 that has the greatest DL ADMSN DENY is used to measure the cell that has the greatest downlink radio load. start Cell Resource Analysis to display the admission reject proportions of call setup. 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. If a cell has the greatest DL ADMSN DENY. downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and the downlink is of interference. For such cell. Combined with the utilization of OVSF codes. and re-configuration. or the indoor coverage for high traffic area must be improved. the average CE and transmission can be estimated to further check whether the resources are sufficient. check whether the cross coverage is serious. the handover area is unreasonable. you can further understand the influence exerted on the subscribers.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. In practice. if the cell has the greatest downlink radio load. The cell that has the greatest DCH UE is used to measure the subscriber number of a cell. 2005 Confidential Information of Huawei No Spreading Without Permission Page 45 of 46 . the cell also has the greatest downlink admission rejects. 10. In this way. In practice. Aug. incoming handover. For the cell that has the greatest DL ADMSN DENY.

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

Sign up to vote on this title
UsefulNot useful