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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.005 1 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 21 of 46 . SHO_FACTOR_UE can be calculated as follows: (Subscriber number of link 2 of active set + Subscriber number of link 3 of active set)/Total subscriber number SHO_FACTOR_UE is used to indicate the subscribers in the soft handover area.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. soft handover factor is used to measure the proportion and cost of soft handover.995 0.945 0.955 0.965 0.98 0. 10.  SHO_FACTOR_UE SHO_FACTOR_UE is used to measure the proportion of soft handover subscribers.975 0.96 0.95 0. which is similar to the proportion of soft handover area by making drive tests.UTRAN KPI Analysis Guide For Internal Use Only 1.985 0. SHO_FACTOR_UE is used to measure the reasonable Aug.94 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.99 0.97 0.

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

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

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

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

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

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

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

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

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

Thus.3. Thus. 10. start Cell inter-RAT Handover Analysis to query the TOPN. you can find the cell that has the greatest CS interRAT handover times. 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. Aug.4. 4.UTRAN KPI Analysis Guide For Internal Use Only 4.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. In addition. Double click PS Inter-RAT Handover Analysis to display the PS inter-RAT handover details between a 2G network and a 3G network. the data configuration must be checked. the network coverage must be improved. as shown in Figure 1-21.4 Cell Inter-RAT Handover Analysis In the CS inter-RAT Handover Analysis. 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. you can find the cell that has the greatest CS inter-RAT handover failure times. 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.

9 0. 10.4.2 PS Inter-RAT Handover Failure Analysis In the PS inter-RAT Handover Analysis. 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.3 0.5 0.6 Bar Value 0.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.4 0.2 0.7 0.8 0. PS_INTRAT_HO_OUT_UTRAN_REQ indicates that the PS inter-RAT handover is initialized by the UE in a dedicated channel. 0. 2005 Confidential Information of Huawei No Spreading Without Permission Page 32 of 46 .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. start PS inter-RAT Handover Failure Aug.

UTRAN KPI Analysis Guide For Internal Use Only Analysis to display the PS inter-RAT handover success and failure rates. This reason may be mainly caused by abnormal UE. 80 % 8 PS_INTRAT_HO_OUT_UTRAN_SUCC 0 PS_HO_OUT_FAIL_CFG_UNSUPP 0 PS_HO_OUT_FAIL_PHYCH_FAIL 0 PS_HO_OUT_FAIL_UNSPEC 0 PS_HO_OUT_FAIL_NO_RSP 2 PS_HO_OUT_FAIL_OTHER 20 % 0% 0% Figure 1-23 PS inter-RAT handover failure analysis PS inter-RAT handover failure may be caused by the following reasons: (1) PS_INTERRAT_HO_ FAIL_UNSPEC PS inter-RAT handover failure is caused by Unspecified (cause value). Aug. (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. (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. 10. (4) PS_INTERRAT_HO_ FAIL_NO_RSP After RNC sends the handover request message to UE. This reason seldom occurs in a network. 2005 Confidential Information of Huawei No Spreading Without Permission Page 33 of 46 . UE does not acknowledge the request because network coverage is poor or UE does not support the handover. as shown in Figure 1-23.

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

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

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

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

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

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

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

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

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

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

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

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

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

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)//-->