Beruflich Dokumente
Kultur Dokumente
Only
Revision Edition
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
1. Overview
In a commercial network, the QoS and network operation are reflected through
KPI. UTRAN KPI analysis is a major method used for monitoring and evaluating
network operation. UTRAN KPI analysis is also served to track the network traffic,
monitor the resource distribution, and facilitate the network expansion and
optimization. Huawei UTRAN traffic statistics provides sufficient KPI for network
operation, algorithm management, and resource distribution. These traffic
statistics can be used to locate network problems and optimize network KPI.
UTRAN KPI analysis is a major method for RAN maintenance engineers and
network optimization engineers to evaluate network performance. Comparing with
drive tests, call detail logs, and alarms, KPI analysis can be used to monitor
network operation directly and conveniently. To better locate network problems
and optimize network KPI, abnormal indices, call detail logs, tracked messages,
and drive tests can be used together.
Huawei provides a traffic statistics analysis tool Nastar for UTRAN KPI analysis.
Nastar can be used to obtain and analyze UTRAN KPI. This guide introduces
how to use Nastar to analyze UTRAN KPI. For more information, refer to GENEX
Nastar V400R001C01 User Manual.
This guide, intended for network maintenance engineers and site audit engineers,
introduces Nastar V400R001, which supports the KPI analysis of RNC
V100R002C03B092 and RNC V100R002C03B151.
1.2 Objectives
practical solutions.
2. Introduction to Nastar
Nastar provides such functions as index defining, query defining, and report
generating. For more information, refer to GENEX Nastar V400R001C01 User
Manual.
Perf Daily Report and Perf Weekly Report can be generated in .xls file by Nastar.
An object can be a self-defined clutter or RNC. Perf Daily Report is used to
monitor network performance. By default, Perf Daily Report includes the following
KPI, as shown in Table 1-2.
If network performance cannot meet the previous KPI or the KPI is changed, refer
to Section 4 UTRAN KPI Analysis.
1. Overview
RRC Setup Analysis is included in Nastar, as shown in Figure 1-1. Double click
RRC Setup Analysis to display the RRC setup details, as shown in Figure 1-3.
RRC setup success rate is 97.3%. Most RRC setup failures result from RRC
Setup Fail No Response while few RRC setup failures (seven times) result from
RRC Setup Reject.
78,961 RRC_SETUP_SUCC
7 RRC_REJ
2,186 RRC_SETUP_FAIL_NO_RSP
97.3 %
2.69 %
0.01 %
The networks, built during the early period, are covered poorly. In particular,
inter-system reselection areas are covered poorly.
A certain area has too many subscribers or any equipment in this area is
faulty.
One of the reasons for RRC Setup Fail No Response is poor coverage, so RRC
setup reasons and RRC setup success rate can be used for further analysis. Start
Scenario Analysis to display a pie or bar chart for presenting RNC indices.
7,451 RRC_REQ_ORG
6.97 % 5,639 RRC_REQ_TERM
51,385 RRC_REQ_CELL_RESEL
16,387 RRC_REQ_REG
9.21 %
63.55 %
20.27 %
Use Scenario Analysis to analyze RRC setup scenarios, as shown in Figure 1-5.
0.99
0.985
0.98
0.975
Bar Value
0.97
0.965
0.96
0.955
0.95
0.945
0
Time
g
b
c
d
e
f RNC:41(ID:41)-RRC_SETUP_SUCC_RATE_ORG
g RNC:41(ID:41)-RRC_SETUP_SUCC_RATE_TERM
g RNC:41(ID:41)-RRC_SETUP_SUCC_RATE_INTERRAT_CELL_RESEL
g RNC:41(ID:41)-RRC_SETUP_SUCC_RATE_REG
Figure 1-5 shows RRC setup success rates. RRC SETUP SUCC RATE ORG is
very high while RRC SETUP SUCC RATE REG is very low. On Huawei networks,
resident threshold Ec/Io is greater than -18 dB while inter-system reselection start
threshold Ec/Io is less than -14 dB. Low RRC SETUP SUCC RATE REG
indicates that many registrations are attempted within the area (Ec/Io falls
between -14 dB and -18 dB), which has poor coverage. 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.
RRC setup reject may occur no matter how poor network coverage is; however,
RRC setup reject occurs in a small-scale network. Therefore, only the areas of
RRC setup reject must be analyzed.
In RRC Setup Analysis, start Cell RRC Analysis to query the TOPN. The queried
results are outputted in three pages:
(1) The top ten cells that have the highest RRC setup reject times.
(2) The top ten cells that have the highest RRC setup success rates.
(3) The top ten cells that have the highest RRC setup failure rates.
For the top ten cells that have the maximum RRC setup fail rates, start Cell
Scenario Analysis for further analysis. For the top ten cells that have the
maximum RRC setup rejects, start Cell RRC Reject Analysis for further
analysis.
2 RRC_REJ_POWER_CONG_CELL
0 RRC_REJ_CE_CONG_CELL
0 RRC_REJ_RL_FAIL_CELL
0 RRC_REJ_AAL2_FAIL_CELL
0 RRC_REJ_FP_FAIL_CELL
0 RRC_REJ_CODE_CONG_CELL
0 RRC_REJ_OTHER_CELL
100 % 0%
0%
Figure 1-6 shows the results of Cell RRC Reject Analysis. In this figure, two RRC
setup rejects are caused by Power Congestion. RRC setup reject may be caused
by the following reasons:
(2) CE Congestion
(3) RL Fail
During the RRC setup process, NodeB recognizes RRC setup fail because
NodeB fails or NodeB resource is insufficient. 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.
(5) FP Fail
If there is high traffic in the indoor micro cell, code resource may be
insufficient. To locate the problem, start Cell OVSF Code Allocation
Analysis to analyze the code allocation and confirm major services.
(7) Other
If there is any problem in RNC, RRC setup reject may occur. To locate the
problem, analyze call detail logs.
1. Overview
Figure 1-7 shows a list of Nastar tasks. RAB Setup Analysis is included in Nastar.
Double click RAB Setup Analysis to display RAB setup details, as shown in
Figure 1-8.
2,370 CS_RAB_REQ_SETUP_CONV_0_32
73.37 % 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.19 %
3.13 % 0.15 %
0.15 %
Click Produce a Bar Chart to display the RB and RAB setup success rates, as
shown in Figure 1-9.
1.1
1
0.9
0.8
0.7
Bar Value
0.6
0.5
0.4
0.3
0.2
0.1
0
0
Time
In RAB Setup Analysis, start Cell RAB Analysis to query the TOPN. The queried
results are outputted in four pages:
(1) The top ten cells that have the highest CS RAB setup failures.
(2) The top ten cells that have the lowest CS RAB setup failures.
(3) The top ten cells that have the highest PS RAB setup failures.
(4) The top ten cells that have the lowest PS RAB setup failures.
Low RAB setup success rate may occur in the cells that have lowest setup times.
To locate the problem, focus on the cells that have the lowest setup failures
because the KPI is affected mostly by these cells.
If CS RAB setup fail rate is high in a cell, start Cell CS RAB Setup Fail Analysis
to display the CS RAB setup fail rates, as shown in Figure 1-10.
1,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
99.05 % 0 CS_RAB_SETUP_FAIL_CE_CONG_CELL
0
0 % %
0.63
% 0 CS_RAB_SETUP_FAIL_CODE_CONG_CELL
0 %
0.32
0 % % 5 CS_RAB_SETUP_FAIL_OTHER_CELL
0%
(1) PARAM_CELL
(2) RELOC_CELL
When initializing the migration process, 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, so this reason seldom occurs. In a core network, this situation is
always avoided.
(3) TNL_CELL
RAB setup fails because IU transmission setup fails. To locate the problem,
check the transmission capacity and operation stability.
(4) CONG_CELL
(5) POWER_CONG_CELL
(6) CE_CONG_CELL
(7) CODE_CONG_CELL
During the RAB setup process, code resource allocation fails because too
many subscribers are crowded on the network or code resource allocation
fails. To locate the problem, analyze the code resource of cell traffic to
check whether code resource is restricted due to cell overload.
(8) OTHER_CELL
If PS RAB setup fail rate is high, start Cell PS RAB Setup Fail Analysis to
display the PS RAB setup fail rates, as shown in Figure 1-11.
0 PS_RAB_SETUP_SUCC_CONV_CELL
0 PS_RAB_SETUP_SUCC_STR_CELL
37 PS_RAB_SETUP_SUCC_INTER_CELL
84.09 % 0 PS_RAB_SETUP_SUCC_BKG_CELL
0 PS_RAB_SETUP_FAIL_PARAM_CELL
0 PS_RAB_SETUP_FAIL_RELOC_CELL
0 PS_RAB_SETUP_FAIL_CONG_CELL
3 PS_RAB_SETUP_FAIL_POWER_CONG_CELL
0% 0 PS_RAB_SETUP_FAIL_CE_CONG_CELL
0% 0 PS_RAB_SETUP_FAIL_CODE_CONG_CELL
4 PS_RAB_SETUP_FAIL_OTHER_CELL
9.09 %
0%
6.820 %
%
0%
0%
(1) PARAM_CELL
parameters. This reason seldom occurs. To locate the problem, track the
signaling and check the RAB setup messages in specific cells.
(2) RELOC_CELL
When initializing the migration process, 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, so this reason seldom occurs. In a core network, this situation is
always avoided.
(3) TNL_CELL
RAB setup fails because IU transmission setup fails. To locate the problem,
check the transmission capacity and operation stability.
(4) CONG_CELL
(5) POWER_CONG_CELL
(6) CE_CONG_CELL
(7) CODE_CONG_CELL
During the RAB setup process, code resource allocation fails because too
many subscribers are crowded on the network or code resource allocation
fails. To locate the problem, analyze the code resource of cell traffic to
check whether code resource is restricted due to cell overload.
(8) UNSUP_CELL
During the RAB setup process, the QoS is not supported by RNC or RRM
(9) OTHER_CELL
1,645 RB_SETUP_SUCC_CELL
0 RB_SETUP_FAIL_CFG_UNSUPP_CELL
0 RB_SETUP_FAIL_PHYCH_FAIL_CELL
0 RB_SETUP_FAIL_SIMU_RECFG_INCOMP_CELL
0 RB_SETUP_FAIL_CELL_UPDT_CELL
3 RB_SETUP_FAIL_CFG_INVALID_CELL
1 RB_SETUP_FAIL_NO_RSP_CELL
99.76 % 0.18 % 0 RB_SETUP_FAIL_OTHER_CELL
0
0.06
% %
0%
(1) CFG_UNSUPP
(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.
(3) SIMU_RECFG_INCOMP
(4) CELL_UPDT
During the RB setup process, the Cell Update process occurs. The RB
setup failure is caused by process nesting.
(5) CFG_INVALID
(6) NO_RESPONSE
(7) OTHER
Overview
4.2.1 Overview
1.005
1
0.995
0.99
0.985
0.98
Bar Value
0.975
0.97
0.965
0.96
0.955
0.95
0.945
0.94
0.935
0
Time
In the previous figure, soft handover factor is used to measure the proportion and
cost of soft handover. SHO_FACTOR_RL and SHO_FACTOR_UE are defined as
follows:
SHO_FACTOR_RL
SHO_FACTOR_UE
In the Soft Handover Analysis, start Cell SHO Analysis to query the TOPN. 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, low soft handover success rates may exist in the cells
that have less soft handover times. Attention must be paid to the cells that have
the highest soft handover failure times and the highest soft handover prepare
failure times because they affect the KPI of soft handover greatly.
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, as shown in Figure 1-15.
0 SHO_PREP_RL_SETUP_FAIL
7 SHO_PREP_AAL2_SETUP_FAIL
0 SHO_PREP_FP_SYNC_FAIL
0%
67 SHO_PREP_FAIL_OTHER_CELL
9.46 %
0%
90.54 %
(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. Internal NodeB logs, Cell Traffic
Load Analysis, and data configuration of NodeB boards can be used to
locate the problems. If NodeB CE resource is insufficient, one or more
boards must be added for expansion.
(2) SHO_PREP_AAL2_SETUP_FAIL
When the links are added during the soft handover, the AAL2 setup of lub
interface fails because the transmission bandwidth is insufficient. If the
transmission bandwidth is insufficient, transmission equipments must be
expanded.
(3) SHO_PREP_FP_SYNC_FAIL
When the links are added during the soft handover, the synchronization of
AAL2 and FP of lub interface fails. To locate the problem, check whether
the intermittent transmission interruption occurs or the IMA group
transmission is incorrectly configured.
In the Soft Handover Analysis, start Cell SHO Analysis to query the TOPN. 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, low soft handover success rates may exist in the cells
that have less soft handover times. Attention must be paid to the cells that have
the highest soft handover failure times and the highest soft handover prepare
failure times because they affect the KPI of soft handover greatly.
In the Cell SHO Analysis, start Cell SHO Failure Analysis to display the soft
handover failure details, as shown in Figure 1-16.
2,797 SHO_SUCC_CELL
0 SHO_RL_ADD_FAIL_CFG_UNSUPP
0 SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP
0 SHO_RL_ADD_FAIL_CFG_INVALID
4 SHO_RL_ADD_FAIL_NO_RSP
0
0.11
% % 0 SHO_RL_DEL_FAIL_CFG_UNSUPP
0 SHO_RL_DEL_FAIL_SIMU_RECFG_INCOMP
99.75 % 0.14 %
0 0 SHO_RL_DEL_FAIL_CFG_INVALID
0%%
0% 3 SHO_RL_DEL_FAIL_NO_RSP
0 SHO_FAIL_OTHER_CELL
0%
(1) SHO_RL_ADD_FAIL_CFG_UNSUPP
UE does not support to add radio links in RNC during the active set update.
This reason seldom exists in a commercial network.
(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. When handling
the processes, RNC performs the serial connection. The problem is mainly
caused by some handsets.
(3) SHO_RL_ADD_FAIL_CFG_INVALID
(4) SHO_RL_ADD_FAIL_NO_RSP
RNC does not receive the acknowledgement of active set update of adding
radio links. Soft handover failure is mainly caused by this reason. If network
coverage is poor or soft handover area is small, soft handover failure easily
occurs. Thus, the RF optimization is required.
(5) SHO_RL_DEL_FAIL_CFG_UNSUPP
UE does not support to delete radio links in RNC during the active set
update. This reason seldom occurs in a commercial network.
(6) SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP
UE feeds back that the soft handover is incompatible with other concurrent
processes when radio links are deleted in RNC. When handling the
processes, RNC performs the serial connection. The problem is mainly
caused by some handsets.
(7) SHO_RL_ADD_FAIL_CFG_INVALID
UE regards the active set update of deleting radio links in RNC as invalid
configuration. This reason seldom occurs in a commercial network.
(8) SHO_RL_ADD_FAIL_NO_RSP
(9) SHO_FAIL_OTHER_CELL
Overview
4.3.1 Overview
605 CS_INTRAT_HO_OUT_PREP_FAIL
2,735 CS_INTRAT_HO_OUT_SUCC
40 CS_INTRAT_HO_OUT_FAIL
17.9 %
1.18 %
80.92 %
2,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
82.1 % 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
0
0%% 32 CS_INTRAT_HO_OUT_PREP_FAIL_REQINFNOTAVAI
0.95 % 0 CS_INTRAT_HO_OUT_PREP_FAIL_NO_RSP
0% 0 CS_INTRAT_HO_PREP_FAIL_OTHER
16.57 %
0.38 %
0%
0%
(1) CS_INTERRAT_HO_PREP_FAIL_TARGET_FAIL
(2) CS_INTERRAT_HO_PREP_FAIL_TALLOC_EXPIR
(3) CS_INTERRAT_HO_PREP_FAIL_TARGET_UNSUPP
(4) CS_INTERRAT_HO_PREP_FAIL_RELOC_ABORT
After sending the handover prepare request, RNC receives the release
message from core network. This may be caused by two reasons:
(5) CS_INTERRAT_HO_PREP_FAIL_NO_RSRC_AVAIL
(6) CS_INTERRAT_HO_PREP_FAIL_UNKNOWTARGET
(8) CS_INTERRAT_HO_PREP_FAIL_NO_RSP
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,735 CS_INTRAT_HO_OUT_SUCC
0 CS_INTRAT_HO_OUT_FAIL_CFG_UNSUPP
27 CS_INTRAT_HO_OUT_FAIL_PHYCH_FAIL
0.43
0.04 %
%
98.56 % 0%
0%
0.97
0 % %
After sending the handover request message to UE, RNC receives the
release message from core network. However, the cause is not Normal
Release because the link is released abnormally due to other reasons. This
reason is caused by the nesting of handover process and release process.
After RNC sends the handover request message to UE, UE does not
acknowledge the request because network coverage is poor.
(1) The cell that have the lowest CS inter-RAT handover success rate
(2) The cell that have the greatest CS inter-RAT handover prepare failure times
(3) The cell that have the greatest CS inter-RAT handover failure times
(4) 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 times. Thus, the network coverage must be improved. In addition,
you can find the cell that has the greatest CS inter-RAT handover failure times.
Thus, the data configuration must be checked.
Overview
4.4.1 Overview
10 PS_INTRAT_HO_OUT_UTRAN_REQ
0 PS_INTRAT_HO_OUT_UE_REQ
100 % 0%
0.9
0.8
0.7
0.6
Bar Value
0.5
0.4
0.3
0.2
0.1
0
0
Time
fedcbg RNC:41(ID:41)-PS_INTRAT_HO_OUT_UTRAN_SUCC_RATE
g RNC:41(ID:41)-PS_INTRAT_HO_OUT_UE_SUCC_RATE
8 PS_INTRAT_HO_OUT_UTRAN_SUCC
0 PS_HO_OUT_FAIL_CFG_UNSUPP
0 PS_HO_OUT_FAIL_PHYCH_FAIL
80 % 0 PS_HO_OUT_FAIL_UNSPEC
0 PS_HO_OUT_FAIL_NO_RSP
2 PS_HO_OUT_FAIL_OTHER
20 %
0%
0%
After RNC sends the handover request message to UE, UE does not
acknowledge the request because network coverage is poor or UE does
not support the handover.
(1) The cell that have the lowest PS inter-RAT handover success rate
(2) The cell that have the greatest PS inter-RAT handover prepare failure times
(3) The cell that have the greatest PS inter-RAT handover failure times
(4) The cell that have the greatest PS inter-RAT handover times
Through the previous results, you can find the cell that has the greatest PS inter-
RAT handover times. Thus, the network coverage must be improved.
Overview
4.5.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). 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. This cell update process is different from that of cell
reselection, so you must be familiar with diverse cell update processes. In the
Cell Update Analysis, start Cell Update Scenario Analysis to display different
cell update scenarios, as shown in Figure 1-24. If the state transition is disabled
in a network, the cell update is caused by abnormal links or RLC reset if UE is not
0 CELL_UPDT_REENTER
0 CELL_UPDT_PAGE
0 CELL_UPDT_UL_DATA_TRANS
211 CELL_UPDT_RLC_ERR
15 CELL_UPDT_RL_FAIL
0 CELL_UPDT_PRD
0 CELL_UPDT_RESEL
93.36 % 0 CELL_UPDT_OTHER
0%
0%
6.64 %
In the Cell Update Scenario Analysis, click Create a Bar Chart to display the cell
update success rates, as shown in Figure 1-25. In general, the cell updates are
caused by abnormal links (RL) or RLC reset (RLC_ERR), thus low cell update
success rate may be caused by poor network coverage. If cell update is caused
by other reasons, cell update success rate must be greater than 85%.
0.07
0.06
0.05
Bar Value
0.04
0.03
0.02
0.01
0
0
Time
g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_RESEL
g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_REENTER
g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_PAGE
g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_UL_DATA_TRANS
g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_RLC_ERR
g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_RL
g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_PRD
g RNC:41(ID:41)-CELL_UPDT_SUCC_RATE_OTHER
In the Cell Update Analysis, start Cell Update Analysis to query the TOPN. The
queried results are outputted to list:
(1) The cell that has the lowest cell update success rate
(2) The cell that has the greatest cell update failure times
If a cell has the lowest cell update success rate, cell update times are less.
Attention must be paid to the cell that has the greatest cell update failure times.
In the queried results of Cell Update Analysis, start Cell Update Scenario
Analysis for Cell to analyze the cell update failure and summarize the cell
update failure scenarios.
Overview
4.6.1 Overview
Call Drop Analysis is included in Nastar tasks. Double click Call Drop Analysis
to display the RNC call drop details. Then, click Create a Pie Chart to display the
call drop details for different services (including voice, VP, CS, and PS), as shown
in Figure 1-27.
0% 75 RNC_CS_RAB_REL_AMR_TRIG_BY_RNC
1.34 % 8 RNC_CS_RAB_REL_CONV_64K_TRIG_BY_RNC
0 RNC_CS_RAB_REL_STR_TRIG_BY_RNC
515 RNC_PS_RAB_REL_REQ
12.54 %
86.12 %
In the Cell Drop Analysis, click Create a Bar Chart to display the call drop rates
for different services (including voice, VP, CS, and PS), as shown in Figure 1-27.
In general, 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, especially in the poor-covered areas.
0.65
0.6
0.55
0.5
0.45
Bar Value
0.4
0.35
0.3
0.25
0.2
0.15
0.1
0.05
0
0
Time
g RNC:41(ID:41)-CS_RAB_AMR_DROP_RATE g RNC:41(ID:41)-CS_RAB_VP_DROP_RATE
g RNC:41(ID:41)-CS_RAB_STR_DROP_RATE g RNC:41(ID:41)-PS_RAB_DROP_RATE
In the CS Call Drop Analysis, click Create a Pie Chart to display the CS call drop
reasons, as shown in Figure 1-28.
0% 75 RNC_CS_RAB_REL_AMR_TRIG_BY_RNC
1.34 % 8 RNC_CS_RAB_REL_CONV_64K_TRIG_BY_RNC
0 RNC_CS_RAB_REL_STR_TRIG_BY_RNC
515 RNC_PS_RAB_REL_REQ
12.54 %
86.12 %
(1) RAB_CS_REL_RF_LOSS
(2) RNC_CS_RAB_REL_TRIG_BY_RNC_SRB_RESET
CS call drops may be caused by link releasing due to downlink SRB reset.
This reason is mainly caused by poor network coverage (including adjacent
cell missing and small handover area). To solve the problem, the network
coverage must be improved. In the early network, call drops are mainly
caused by this reason.
(3) RNC_CS_RAB_REL_TRIG_BY_RNC_AAL2_LOSS
(4) CS_RAB_DROP_OTHER
CS call drops may be caused by other reasons. 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. In
practice, many call drops are caused by process interaction timeout and
cell update failure. Therefore, these call drops are recorded in
CS_RAB_DROP_OTHER.
In the Call Drop Analysis, start PS Call Drop Analysis. Then, click Create a Pie
Chart to display the PS call drops, as shown in Figure 1-29.
40.39 %
15 RAB_PS_REL_RF_LOSS
26 RNC_PS_RAB_REL_TRIG_BY_RNC_TRB_RESET
208 RNC_PS_RAB_REL_TRIG_BY_RNC_SRB_RESET
0 RNC_PS_RAB_REL_TRIG_BY_RNC_GTPU_LOSS
266 PS_RAB_DROP_OTHER
5.05 %
0% 2.91 %
51.65 %
(1) RAB_PS_REL_RF_LOSS
PS call drops may be caused by abnormal release because the links are
asynchronous. This reason is mainly caused by poor network coverage
(including adjacent cell missing and small handover area). As a result, UE
closes the transmitter abnormally or uplink demodulation is asynchronous.
To solve the problem, network coverage must be improved. In the early
network, call drops are mainly caused by this reason.
(2) RNC_PS_RAB_REL_TRIG_BY_RNC_SRB_RESET
PS call drops may be caused by link releasing due to downlink SRB reset.
This reason is mainly caused by poor network coverage (including adjacent
cell missing and small handover area). To solve the problem, the network
coverage must be improved. In the early network, call drops are mainly
caused by this reason.
(3) RNC_PS_RAB_REL_TRIG_BY_RNC_TRB_RESET
PS call drops may be caused by link releasing due to downlink TRB reset.
This reason is mainly caused by poor network coverage (including adjacent
cell missing and small handover area). To solve the problem, the network
coverage must be improved. In the early network, call drops are mainly
caused by this reason.
(4) RNC_PS_RAB_REL_TRIG_BY_RNC_GTPU_LOSS
(5) PS_RAB_DROP_OTHER
PS call drops may be caused by other reasons. There are few call drop
statistics in RNC (Version 12). Such reasons as process interaction timeout
and cell update failure are recorded in PS_RAB_DROP_OTHER. In
practice, many call drops are caused by process interaction timeout and
cell update failure. Therefore, these call drops are recorded in
PS_RAB_DROP_OTHER.
In the Cell Drop Call Analysis, query the TOPN to find the cell that has the
greatest CS call drop rate, start Cell Call Drop Analysis, and then click Create a
Pie Chart to display the cell drop reasons, as shown in Figure 1-30.
0% 33.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.67 %
(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, cell block). Actually, cell call drops caused by
this reason are normal.
(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.
This reason is mainly caused by poor network coverage (including adjacent
cell missing and small handover area). To solve the problem, the network
coverage must be improved. In the early network, call drops are mainly
caused by this reason.
(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, use CDL for further analysis.
(4) RNC_CS_RAB_REL_CELL_TRIG_BY_RNC_AAL2_LOSS
(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
(6) CS_RAB_DROP_CELL_OTHER
Cell call drops may be caused by other reasons. 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_CELL_OTHER. In
practice, many call drops are caused by process interaction timeout and
cell update failure. Therefore, these call drops are recorded in
CS_RAB_DROP_CELL_OTHER.
Overview
4.7.1 Overview
Traffic Load Analysis is included in Nastar tasks. Double click Traffic Load
Analysis to display the RNC traffic load details. You can choose Time Range or
Query Object to query the RNC traffic load, as shown in Figure 1-32.
Choose Busy Time (Busy Time can be Automatic Querying or Designated Time).
In the Traffic Load Analysis, click Create a Pie Chart to display the traffic load
details. Assume that the subscribers for different services are equivalent, traffic
load proportions are displayed in Figure 1-33. UNKNOWN_USER indicates that
the subscribers are from other RNC and service type is unknown. The unit of
traffic load is Erl.
4.388 CS_CONV_USER
0% 0 CS_STR_USER
0% 0 PS_CONV_USER
0 PS_STR_USER
25.808 PS_INTER_BKG_USER
14.49 % 0.09 UNKNOWN_USER
0.3 %
85.21 %
If a cell has the highest traffic, it is the most important cell in a network. In
addition, the cell is easily congested and need to be expanded. In the Traffic Load
Analysis, start Cell Traffic Analysis to query the TOPN. The queried results are
outputted as follows:
(4) 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. In practice, this queried result can be used to find the cell that is
seriously interfered. If the RTWP of a cell is greater than -100 dBm, the cell must
be analyzed. Check whether it is the burst interference or continuous
interference. The burst interference exerts little influence on the system but the
continuous interference must be eliminated on a timely basis. If the cells have
large RTWP_MAX_CELL_DBM values, start Cell RTWP Analysis, as shown in
Figure 1-34.
-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 2005-04-21 19:30:00
DateTime
gfedcb RTWP_MAX_CELL_DBM
The cell that has the greatest TCP represents the cell that has the greatest
downlink radio load. In practice, if the cell has the greatest downlink radio load,
the cell also has the greatest downlink admission rejects. For such cell, 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.
The cell that has the greatest DCH UE is used to measure the subscriber number
of a cell. Combined with the utilization of OVSF codes, the average CE and
transmission can be estimated to further check whether the resources are
sufficient.
The cell that has the greatest DL ADMSN DENY is used to measure the cell that
has the greatest downlink radio load. In practice, downlink radio load is a
bottleneck because the uplink is asymmetric to the downlink and the downlink is
of interference. If a cell has the greatest DL ADMSN DENY, check whether the
cross coverage is serious, the handover area is unreasonable, or the indoor
coverage for high traffic area must be improved.
For the cell that has the greatest DL ADMSN DENY, start Cell Resource
Analysis to display the admission reject proportions of call setup, incoming
handover, and re-configuration. In this way, you can further understand the
influence exerted on the subscribers.
Further analysis is necessary because the KPI of traffic statistics does not
represent the processes, but the results. Some reasons may not be found
through the KPI analysis. Therefore, it is necessary for us to use further analysis
to locate complicated problems. To analyze complicated problems, use the
following methods:
The area range of abnormal traffic statistics can be determined by querying the
TOPN. After determining the area range, query the time range of problem (The
time range falls within 30 minutes).
Execute the command LST CELL in MML on the RNC maintenance console to
find the service subrack. Then, send the CDL of service subrack from BAM to a
service engineer for further analyzing abnormal processes, reasons, and involved
subscribers.
If time range or area range falls within a fixed scope after the KPI analysis is
performed for several days, 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.