P. 1
utrankpianalysisguide-20051010-b-1-0-121023022115-phpapp01

utrankpianalysisguide-20051010-b-1-0-121023022115-phpapp01

|Views: 0|Likes:

More info:

Published by: Maxime Netstat Tchapo Tanté on Oct 08, 2013
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

11/28/2013

pdf

text

original

Sections

  • 1.Overview
  • 1.1Intended Audience
  • 1.2Objectives
  • 2.Introduction to Nastar
  • 3.UTRAN KPI Analysis
  • 4.UTRAN KPI Analysis
  • 4.1Call Completion Rate
  • 4.1.1RRC Setup Analysis
  • 4.1.2RAB Setup Analysis
  • 4.2Soft Handover Analysis
  • 4.2.1Overview
  • 4.2.2Cell SHO Prepare Failure Analysis
  • Figure 1-15 Cell SHO Prepare Failure Analysis
  • 4.2.3Cell SHO Failure Analysis
  • 4.3CS Inter-RAT Handover Analysis
  • 4.3.1Overview
  • 4.3.2CS Inter-RAT Handover Prepare Failure Analysis
  • Figure 1-19 CS inter-RAT handover prepare failure analysis
  • 4.3.3CS Inter-RAT Handover Failure Analysis
  • Figure 1-20 CS inter-RAT handover failure analysis
  • 4.3.4Cell Inter-RAT Handover Analysis
  • 4.4PS Inter-RAT Handover Analysis
  • Cell Inter-RAT Handover Analysis
  • 4.4.1Overview
  • 4.4.2PS Inter-RAT Handover Failure Analysis
  • 4.4.3Cell Inter-RAT Handover Analysis
  • 4.5Cell Update Analysis
  • 4.5.1Overview
  • 4.5.2Cell Update Failure Analysis
  • 4.6Call Drop Analysis
  • CS Call Drop Analysis
  • PS Call Drop Analysis
  • Cell Call Drop Analysis
  • 4.6.1Overview
  • 4.6.2CS Call Drop Analysis
  • 4.6.3PS Call Drop Analysis
  • 4.6.4Cell Call Drop Analysis
  • 4.7Traffic Load Analysis
  • 4.7.1Overview
  • 4.7.2Cell Traffic Analysis
  • 5.Analyzing Complicated Problems
  • Narrowing down area range and time range
  • Analyzing abnormal logs
  • Analyzing repeated problems
  • 5.1Narrowing Down Area Range and Time Range
  • 5.2Analyzing Abnormal Logs
  • 5.3Analyzing Repeated Problems

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

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

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

60%(997/1001) 99.13(16:00 ~ 17:00) 54. 10.UTRAN KPI Analysis Guide For Internal Use Only Figure 1-1 Nastar tasks Perf Daily Report and Perf Weekly Report can be generated in .31%(2016/2030) 99.67%(4/6) 1.92%(19/990) 10.75%(17090/17132) 99.85% 100. Perf Daily Report includes the following KPI.64%(2468/2502) 96. 2005 Confidential Information of Huawei No Spreading Without Permission Page 7 of 46 .09(12:00 ~ 13:00) 98. as shown in Table 1-2.34%(3/29) 3. By default.01%(30/997) Aug.5%) PS Service Drop Rate(< 30%) RN C: 1 17.00%(990/1000) 100.00%(16/16) 100.xls file by Nastar. Perf Daily Report is used to monitor network performance. 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. An object can be a self-defined clutter or RNC.5%) CDR Video Call Drop Rate(< 1.00%(29/29) 99.00%(4/4) 66.66%(3509/3521) 18.87%(36445/37624) 99.

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

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

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

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

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

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

9 0.3 0. To locate the problem.8 Bar Value 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. 10. The top ten cells that have the highest PS RAB setup failures. as shown in Figure 1-9.5 0.1 1 0.6 0.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. start Cell CS RAB Setup Fail Analysis to display the CS RAB setup fail rates.7 0. start Cell RAB Analysis to query the TOPN. 2005 Confidential Information of Huawei No Spreading Without Permission Page 14 of 46 . Aug. as shown in Figure 1-10. focus on the cells that have the lowest setup failures because the KPI is affected mostly by these cells. 1. If CS RAB setup fail rate is high in a cell. The queried results are outputted in four pages: (1) (2) (3) (4) The top ten cells that have the highest CS RAB setup failures.2 0.4 0. RAB Setup Fail Analysis In RAB Setup Analysis. The top ten cells that have the lowest PS RAB setup failures. 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.

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

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

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

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

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

Double click Soft Handover Analysis to display the RNC soft handover details (including soft handover success rate.2. softer handover success rate. 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.UTRAN KPI Analysis Guide For Internal Use Only 4. 10. as shown in Figure 1-14. as shown in Figure 1-13. and soft handover prepare success rate). Aug.

005 1 0.98 0.97 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.995 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.99 0.965 0.  SHO_FACTOR_UE SHO_FACTOR_UE is used to measure the proportion of soft handover subscribers. 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. which is similar to the proportion of soft handover area by making drive tests. 2005 Confidential Information of Huawei No Spreading Without Permission Page 21 of 46 . SHO_FACTOR_UE is used to measure the reasonable Aug.95 0.955 0.975 0.94 0. soft handover factor is used to measure the proportion and cost of soft handover.UTRAN KPI Analysis Guide For Internal Use Only 1. 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.96 0.985 0.945 0. 10.

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

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

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

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

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

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

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

To locate the problem. (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.56 % 0. start CS Inter-RAT Handover Failure Analysis to display the CS inter-RAT handover details (including CS inter-RAT handover success and failure rates). To locate the problem. track the signaling of core network and BSS for further analysis. This problem frequently occurs if a 2G network is adjusted. (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. This may be caused by incorrect data configuration or link connection of core network.3.04 % % 0% 0% 0.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. 98. 2005 Confidential Information of Huawei No Spreading Without Permission Page 29 of 46 . To locate the problem.43 0. check whether any data is incorrectly configured in the core network.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.3 CS Inter-RAT Handover Failure Analysis In the CS Inter-RAT Handover Analysis. as shown in Figure 1-20. 10. 4.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.

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

start Cell inter-RAT Handover Analysis to query the TOPN. 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.UTRAN KPI Analysis Guide For Internal Use Only 4. you can find the cell that has the greatest CS interRAT handover times. Thus. 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 . 10.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. Aug. the data configuration must be checked.4. you can find the cell that has the greatest CS inter-RAT handover failure times. as shown in Figure 1-21. 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.4 Cell Inter-RAT Handover Analysis In the CS inter-RAT Handover Analysis.3.1 Overview PS inter-RAT Handover Analysis is included in Nastar tasks. 4. the network coverage must be improved. In addition.

5 0. 0.3 0. 10.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.2 PS Inter-RAT Handover Failure Analysis In the PS inter-RAT Handover Analysis. 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.9 0.6 Bar Value 0.8 0. start PS inter-RAT Handover Failure Aug.4.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.2 0.7 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 32 of 46 .

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

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

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

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

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

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

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

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

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

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

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. Assume that the subscribers for different services are equivalent. In the Traffic Load Analysis. 10.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). traffic load proportions are displayed in Figure 1-33. Aug. The unit of traffic load is Erl. 2005 Confidential Information of Huawei No Spreading Without Permission Page 43 of 46 .

49 % 4.09 UNKNOWN_USER 0.UTRAN KPI Analysis Guide For Internal Use Only 0% 0% 14. In addition. the cell must be analyzed.3 % 85. If the cells have large RTWP_MAX_CELL_DBM values. 2005 Confidential Information of Huawei No Spreading Without Permission Page 44 of 46 . If the RTWP of a cell is greater than -100 dBm. start Cell RTWP Analysis. it is the most important cell in a network. Aug.808 PS_INTER_BKG_USER 0.388 CS_CONV_USER 0 CS_STR_USER 0 PS_CONV_USER 0 PS_STR_USER 25. In practice. 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.21 % Figure 1-33 Traffic Load 4. as shown in Figure 1-34. 10. this queried result can be used to find the cell that is seriously interfered. start Cell Traffic Analysis to query the TOPN.2 Cell Traffic Analysis If a cell has the highest traffic. The burst interference exerts little influence on the system but the continuous interference must be eliminated on a timely basis.7. the cell is easily congested and need to be expanded. Check whether it is the burst interference or continuous interference. In the Traffic Load Analysis.

or the indoor coverage for high traffic area must be improved. downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and the downlink is of interference. and re-configuration. If a cell has the greatest DL ADMSN DENY. 2005 Confidential Information of Huawei No Spreading Without Permission Page 45 of 46 . if the cell has the greatest downlink radio load. In this way. incoming handover. the handover area is unreasonable. the cell also has the greatest downlink admission rejects. In practice. 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. Combined with the utilization of OVSF codes.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. 10. the average CE and transmission can be estimated to further check whether the resources are sufficient. Aug. check whether the cross coverage is serious. In practice. start Cell Resource Analysis to display the admission reject proportions of call setup. For such cell. For the cell that has the greatest DL ADMSN DENY. you can further understand the influence exerted on the subscribers. 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.

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

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->