cBSS Performance Management Guide

1 Performance Management Principle

Performance Management Principle

About This Chapter

To learn the performance management principle, you need to be familiar with the performance data system and performance management process. 1.1 Performance Data System By performance management activity, the performance data can be classified into three categories at different levels, namely, key performance indexes (KPI) of daily performance monitoring, performance data for initial analysis, and performance data for deeply locating problems. 1.2 Performance Management Process The performance management process consists of two phases, namely, the daily performance monitoring phase and the problem isolating and locating phase.

Issue 2.0 (2008-03-14)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1-1

1 Performance Management Principle

cBSS Performance Management Guide

1.1 Performance Data System

By performance management activity, the performance data can be classified into three categories at different levels, namely, key performance indexes (KPI) of daily performance monitoring, performance data for initial analysis, and performance data for deeply locating problems. 1.1.1 Level 1 Data (KPI for the Daily Performance Monitoring) The Level 1 data refers to the KPIs used in the daily monitoring. The KPIs are related to the service quality, traffic, and resource usage. 1.1.2 Level 2 Data (Performance Data for Initial Analysis) The Level 2 data refers to the KPIs used in initial isolation and location after problems are detected. Through the data, you can determine the causes of the performance problems and take appropriate measures. 1.1.3 Level 3 Data (Performance Data for Deeply Locating Problems) The Level 3 data is used for deeply locating problems.

1.1.1 Level 1 Data (KPI for the Daily Performance Monitoring)

The Level 1 data refers to the KPIs used in the daily monitoring. The KPIs are related to the service quality, traffic, and resource usage.

Description
The Level 1 data refers to the KPIs used for evaluating the network performance and condition, for example, the traffic, call drop rate, and call setup success rate. Through the KPIs, you can judge whether the network has problems.

Collection
Collecting the level 1 data is collecting the traffic measurement data. The equipment automatically collects the traffic measurement data. You do not need to operate. The traffic measurement data is reported every 30 minutes. All reported data are saved in the BAM of the BSC as a binary file and the BAM reports the counter that is used to measure the performance KPI to the M2000.

Saving the Data

By default, the traffic data is saved in the FTP directory of the BAM. You can use the data through the FTP mode. The data is saved in the binary format. The daily traffic measurement file is saved in different folders, and the folder name is the date, for example, 20060728. The traffic measurement file name is the name of the measured object plus the file creation time, for example, BSCOVERALL_200606040000.DAT. Because the local server does not exist, you need to obtain the original traffic measurement data from the BAM through the FTP mode.

Browse and Analysis

The following two methods are used for browsing and analyzing the data:
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 2.0 (2008-03-14)

cBSS Performance Management Guide

l l

1 Performance Management Principle

Browsing the traffic measurement data in real time through the M2000 client Browsing and analyzing the traffic measurement data by using the Nastar CDMA2000 analysis tool to import the traffic measurement data

1.1.2 Level 2 Data (Performance Data for Initial Analysis)

The Level 2 data refers to the KPIs used in initial isolation and location after problems are detected. Through the data, you can determine the causes of the performance problems and take appropriate measures.

Description
The Level 2 data is the outcome of an detailed analysis of the daily performance monitoring KPIs. Through the Level 2 data, you can determine the specific causes of problems. Generally, deep analysis is required only when problems occur. For example, in the CDMA2000 1X network, only when the call setup success rate is low, you need to collect and analyze the performance measurement items to judge what causes the problem.

Collection
Collecting the level 2 data is collecting the traffic measurement data. The equipment automatically collects the traffic measurement data. You do not need to operate. The traffic measurement data is reported every 30 minutes. All reported data are saved in the BAM of the BSC as a binary file and the BAM reports the counter that is used to measure the performance KPI to the M2000. The biggest difference between the performance data for initial analysis and the KPI for the daily performance monitoring is that you need to collect and analyze the performance data for initial analysis only when the problem is found out.

Saving the Data

By default, the traffic data is saved in the FTP directory of the BAM. You can use the data through the FTP mode. The data is saved in the binary format. The daily traffic measurement file is saved in different folders and the folder is named according to the date, for example, 20060728. The traffic measurement file name is the name of the measured object plus the file creation time, for example, BSCOVERALL_200606040000.DAT. Because the local server does not exist, you need to obtain the original traffic measurement data from the BAM through the FTP mode.

Browse and Analysis

The following two methods are used for browsing and analyzing the data:
l l

Browsing the traffic measurement data in real time through the M2000 client Browsing and analyzing the traffic measurement data by using the Nastar CDMA2000 analysis tool to import the traffic measurement data

1.1.3 Level 3 Data (Performance Data for Deeply Locating Problems)

The Level 3 data is used for deeply locating problems.
Issue 2.0 (2008-03-14) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-3

1 Performance Management Principle

cBSS Performance Management Guide

Description
The Level 3 data is performance data beyond the performance measurement items, for example, subscriber interface tracing data, RF measurement tool (RFMT) monitoring data, call history record (CHR), pilot strength measurement messages (PSMMs) for CDMA2000 1X services, RouteUpdate data for CDMA2000 1xEV-DO services, reverse signal strength indicator (RSSI) data of BTSs, BTS IMSI monitoring data, and Walsh code channel monitoring data. The level 3 data is the deepest and narrowest. It is used by the on-site engineers to precisely locate and solve problems.

Collection
You need to collect the Level 3 data only when deeply locating performance problems. Table 1-1 lists the Level 3 performance data. Table 1-1 Level 3 performance data Type Subscriber Interface Tracing Description Trace the signaling of the special user during a call and display the result in the maintenance window is real time. Collection Use the user IMSI as an identifier to trace the signaling message of several interfaces and to choose the interface to be traced. The following methods are used to collect the RFMT:
l

Storage Location The data is saved as date_time_user.d at in ..\Airbridge \OutputFile\trace \user.

Analysis Tools LMT service maintenance system

RFMT

Record the forward and reverse wireless environment information and call features during a call.

The data is saved in the BAM as a database.

Nastar

Tracing the call information of the sector carrier frequency Collecting the optimization of the neighboring cell Tracing the specified and random IMSI call
Issue 2.0 (2008-03-14)

1-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

cBSS Performance Management Guide

1 Performance Management Principle

Type CHR

Description Records the key event and information during a call.

Collection Export the record when a call ends. You can choose to export the record of all calls or the record of abnormal calls. The following two methods are used to collect the PSMM: Periodical report and pilot triggering report.

Storage Location The data is saved in the BAM.

Analysis Tools Nastar

PSMM (1X)

Pilot strength measurement message, such as the PSMM, PPSMM, and EPSMM messages or the air interface messages like CFSRPT. Pilot strength measurement message: RouteUpdate message Collect the BTS reverse main and diversity received signal strength.

The data is saved as PSMMTRACE** *******.dat in .. \cdma2000 \TRACE\PSMM.

Nastar

RouteUpdate (DO)

Reported in pilot-triggered mode

..\cdma2000 \TRACE \RUTRACE**** ****.dat The data is saved in ..\Airbridge \Services \BTSITFLOG. Each BTS has two files, namely, BTSXXX_ITF_L OG.LOG and BTSXXX_ITF_L OG.BAK.

Nastar

BTS reverse RSSI

Two triggering methods are used, namely, 30s periodic recording and 2s threshold triggering.

Nastar

Issue 2.0 (2008-03-14)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1-5

1 Performance Management Principle

cBSS Performance Management Guide

Type IMSI Tracing of the BTS

Description Record the forward and reverse wireless environment information and call features of the user with specified IMSI during a call made in a specified BTS.

Collection The collecting method is 2s periodic reporting, and the collected data includes the forward transmit power, reverse RSSI, leg handoff status, reverse BTS-level frame error rate, and reverse capturing information. Collecting the quantity of the assigned and remained Walsh Collecting the allocated and remained Walsh space

Storage Location The data is saved in ..\Airbridge \Services \BTSITFLOG. Each BTS has two files, namely, BTSXXX_ITF_L OG.LOG and BTSXXX_ITF_L OG.BAK.

Analysis Tools Nastar

Monitoring the Walsh channel

Monitoring the Walsh channel power to check the integrity of the Walsh tree and the assignment ability of the SCH.

The radio resource monitoring data is saved in:

l

LMT service maintenance system

..\Airbridge \OutputFile \Rmon \RADIO_RES OURCE for CDMA2000 1X carriers. ..\Airbridge \OutputFile \Rmon\EVDORADIO_R ESOURCE for CDMA2000 1xEV-DO carriers.

Saving the Data

See Table 1-1

Browse and Analysis

See Table 1-1

1-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Issue 2.0 (2008-03-14)

cBSS Performance Management Guide

1 Performance Management Principle

1.2 Performance Management Process

The performance management process consists of two phases, namely, the daily performance monitoring phase and the problem isolating and locating phase. Figure 1-1 shows the performance management process and related performance data. Figure 1-1 Performance management process and related performance data

1.2.1 Daily Performance Monitoring The daily performance monitoring monitors the KPI to check whether the network has performance problems. The problems include: The network quality cannot meet the expectation, and the resource is insufficient. The daily performance monitoring is a process to find out the problem. It is the first phase of the performance management. 1.2.2 Problem Isolation and Location Problem isolation and location is how to locate and solve the problem when the problem occurs.

Issue 2.0 (2008-03-14)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1-7

1 Performance Management Principle

cBSS Performance Management Guide

1.2.1 Daily Performance Monitoring

The daily performance monitoring monitors the KPI to check whether the network has performance problems. The problems include: The network quality cannot meet the expectation, and the resource is insufficient. The daily performance monitoring is a process to find out the problem. It is the first phase of the performance management. 1.2.1.1 Network Quality Monitoring Network quality monitoring is implemented to evaluate whether the network service quality meets the requirements and to find out the problems if the service quality is not good. 1.2.1.2 Bottleneck Analysis for Network Resources The bottleneck analysis for network resources is aimed at using the statistics of the traffic and resources to judge whether the network resources are likely to encounter a bottleneck.

Network Quality Monitoring

Network quality monitoring is implemented to evaluate whether the network service quality meets the requirements and to find out the problems if the service quality is not good. The service quality of a radio network is reflected by the KPIs. The KPIs include the traffic, call setup success rate (for CDMA2000 1X services), call drop rate, and congestion rate. The KPIs directly reflect the service quality. The KPI for the network quality monitoring is collected and measured through the traffic measurement. Then, compare the KPI with the threshold and analyze the KPI to find out the existing problems and the KPI to be optimized. Monitoring normally focuses to the whole network or some key areas. The methods to monitor the network quality include:

Quasi real time monitoring

The purpose of the quasi real time monitoring is to quickly know the change of the network KPI in certain scenarios by monitoring the KPI and take measures to improve the KPI if the KPI is getting worse. The operation and management (OM) system can count the KPI and display and monitor the KPI in real time. When the network quality decreases, the OM system generates an alarm. The quasi real time monitoring is performed in the M2000. The monitoring period is the same as the collection period of the traffic measurement data. You can configure the period in the M2000. The period can be 30 or 60 minutes. You can set the KPI alarm threshold in the M2000. If the KPI reaches the alarm threshold, the M2000 automatically generates the performance alarm.

Routine report
The routine report is used by the network planning engineers, network optimization engineers, or on-site engineers to know the network KPI and change of the network quality and to monitor the network quality. Compared to the quasi real time monitoring, the routine report requires to analyze and organize the data. Based on the report time, the routine report is classified into: Daily report, weekly report, and monthly report. Table 1-2 lists the contents of the three types of the routine report.
1-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 2.0 (2008-03-14)

cBSS Performance Management Guide

1 Performance Management Principle

Table 1-2 Recommendation for the routine report Report Type Daily report Focus Often used in the initial running period of the network when the network running conditions need to be known in a short period. You need the report to find out and locate some network problems. As a result, except the KPI used to evaluate the network quality, the daily report also includes 10 cells whose KPI is the worst and gives the causes that lead to the poor KPI. Often used by the OM personnel to know the change trend of the network quality. For the index that are getting worse, the OM personnel consider to do the optimization analysis in advance. The content of the weekly report focuses on the change trend of the KPI. Similar to the application scenario of the weekly report, the monthly report focuses on the change trend in a long time.

Weekly report

Monthly report

NOTE

l l l

The content and format of the routine report are not fixed. The Nastar supports the automatic export of all kind of routine reports. The routine report of the Nastar can use the traffic measurement data to analyze the specific causes of the KPI that are getting worse. It can simply locate the network problem. The Nastar can also export the report of the network health check. The report includes: network mark, VIP user group mark, VIP cell group mark, network interference cell check, and neighboring cell configuration check.

Handling method
When finding out problems during the network quality monitoring, start the problem isolation and location. You need to collect the Level 2 and Level 3 data. For details, see 1.2.2 Problem Isolation and Location. This document provides solutions to the problems that occur to each common KPI. For details, see 3 KPIs in CDMA2000 1X Daily Performance Monitoring and 4 KPIs in CDMA2000 1xEV-DO Daily Performance Monitoring.

Bottleneck Analysis for Network Resources

The bottleneck analysis for network resources is aimed at using the statistics of the traffic and resources to judge whether the network resources are likely to encounter a bottleneck. The network resource bottle analysis is to associate the KPIs such as the network congestion rate and resource usage and then analyze the KPIs. Together with the traffic change, the analysis is used to check whether the network has a resource bottleneck. In addition, the development
Issue 2.0 (2008-03-14) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-9

1 Performance Management Principle

cBSS Performance Management Guide

trend and capacity expansion time are predicted based on the long-term running data of the network. Then based on the predicted data, find out the bottleneck that affects the network service development in advance and take measures to optimize the network.

Purpose of the Bottleneck Analysis

The bottleneck of the network resource must lead to the decrease of the network quality. As a result, you need to know the running conditions of the network and the possibly existing bottleneck in advance. Take optimization measures before the network quality getting worse. The following are the causes of the resource bottleneck of a network:
l l

Unbalanced resource usage of different services Unbalanced traffic distribution in different areas

The usages of the network resources have great differences. If the resources are not used in balance, some system resource becomes the network bottleneck.

Method to analyze the bottleneck

Based on the statistic such as the traffic change, resource assignment congestion, and resource usage, monitor, record, and measure the key points in the networking running. Summarize and measure the following performance index in a fixed interval: Success and failure of related serviceDelayThroughput See all performance indexes and the KPI measurement results, consider the software and hardware configuration of the network, and use the methods such as measurement, count, and comparison to know the network running condition and predict the possibly existing network bottleneck. Periodically monitor the traffic change. The monitor period can be:
l l l l

A week Half a month A month Two months

At the same time, pay attention to the traffic congestion of each service. Avoid that the traffic in some area is too heavy and the network is partly overloaded. The traffic congestion rate is a key index to judge whether the resource bottleneck appears. Through the comparison and analysis of the traffic measurement data, you can know the cell which has the most serious congestion. Table 1-3 lists the key resources for traffic analysis. Table 1-3 Resources for traffic analysis Contents SPUO load Public channel load Focus Measures the system load. Measures the public channel signaling of the carrier frequency and traffic load.
Issue 2.0 (2008-03-14)

1-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

cBSS Performance Management Guide

1 Performance Management Principle

Contents Carrier frequency load Forward transmit power of CDMA2000 1X carriers Usage of the CE, Walsh, and License Power consumption per traffic unit in CDMA2000 1X services

Focus Measures the forward and reverse load of the carrier frequency. Measures the usage of the carrier frequency power. Measures the traffic load of the carrier frequency. Measures the relation between the traffic and the power.

For details, see KPIs in CDMA2000 1X Daily Performance Monitoring and KPIs in CDMA2000 1xEV-DO Daily Performance Monitoring.

Handling the resource bottleneck

For the resource bottleneck of part of the system, you can add the system hardware or carrier frequency to share the traffic. You can also modify the configuration, adjust the parameter, and replace the equipment. For the hot areas, if increasing resource and adjusting the parameter cannot meet the requirement of the traffic, you need to expand the system capacity. Otherwise, the service quality and user satisfaction are directly affected.
NOTE

The Nastar provides a system solution to analyze the resource bottleneck.

1.2.2 Problem Isolation and Location

Problem isolation and location is how to locate and solve the problem when the problem occurs. 1.2.2.1 Common Procedure for Performance Analysis Based on the collected performance data, performance analysis is aimed at determining the causes of the problems and solving the problem. Based on the difficulty and depth of the problem, the performance analysis is classified into initial analysis and deep locating. 1.2.2.2 Initial Analysis Phase The initial analysis is to associate the alarm, configuration data, and index measurement data to check the causes of the problem. In addition, through the relation between index measurement data, you can refine the problem to an area, a time segment, or a network element. It also provides the general causes of the problem and the adjustment measures. 1.2.2.3 Deep Locating Phase The deep locating is to deep locate some difficult problems. It needs more specific data. In addition, it analyzes the data that collected both at the system and the road test. The logs, CHR, RFMT signaling tracing, and road test provide materials for the deep analysis of the part network performance. 1.2.2.4 Collection of the Drive Test Data The drive test is that a mobile phone does a simulated call test in the specific line. It collects the related information through the drive test software.
Issue 2.0 (2008-03-14) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-11

1 Performance Management Principle

cBSS Performance Management Guide

Common Procedure for Performance Analysis

Based on the collected performance data, performance analysis is aimed at determining the causes of the problems and solving the problem. Based on the difficulty and depth of the problem, the performance analysis is classified into initial analysis and deep locating. Figure 1-2 shows the procedure for performance analysis.

1-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Issue 2.0 (2008-03-14)

cBSS Performance Management Guide

1 Performance Management Principle

Figure 1-2 Procedure for performance analysis

Issue 2.0 (2008-03-14)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1-13

1 Performance Management Principle

cBSS Performance Management Guide

Initial analysis
The initial analysis is to associate the alarm, configuration data, and index measurement data to check the causes of the problem. In addition, through the relation between index measurement data, you can refine the problem to an area, a time segment, or a network element. It also provides the general causes of the problem and the adjustment measures. For details about the initial analysis phase, see 1.2.2.2 Initial Analysis Phase.

Deep locating
The deep locating is to deep locate some difficult problems. It needs more specific data. In addition, it analyzes the data that collected both at the system and the road test. The logs, CHR, RFMT signaling tracing, and road test provide materials for the deep analysis of the part network performance. For details about the deep analysis phase, see 1.2.2.3 Deep Locating Phase.

Initial Analysis Phase

The initial analysis is to associate the alarm, configuration data, and index measurement data to check the causes of the problem. In addition, through the relation between index measurement data, you can refine the problem to an area, a time segment, or a network element. It also provides the general causes of the problem and the adjustment measures. The input of the initial analysis phase is the abnormal KPIs found in the daily performance monitoring. For the definitions of common KPIs, see KPIs in CDMA2000 1X Daily Performance Monitoring and KPIs in CDMA2000 1xEV-DO Daily Performance Monitoring. For each type of KPI, the cBSS provides specific performance measurement items, which facilitate initial isolation and analysis of problems. For the specific measurement items of each type of KPI, see Performance Data for Initial Analysis of CDMA2000 1X Problems and Performance Data for Initial Measurement point of CDMA2000 1xEV-DO Problems. After a problem is detected, you first need to learn the recent alarms and check whether the parameter and resource configuration is changed. Then, you need to isolate and analyze the problem according to the performance data.

Equipment Alarm Analysis

The equipment alarm reflects the operation status of the equipment in the whole network. When an index in the traffic measurement is abnormal, it is possibly that the equipment generates an alarm. You can save time by distinguishing the different alarms and associating them with the traffic measurement indexes. You can query the equipment alarm in the M2000 centralized fault management system and the cBSS alarm management system. If the alarms exist in the system, clear the alarms in time, estimate the impact to the KPI, and determine whether the fault causes the problem.

System Parameter Configuration Check

Unreasonable configuration of parameters affects the network quality. The system upgrade or resource adjustment cause the change of the parameter configuration. If you analyze only the phenomenon of the problem, the cost of analysis is high. As a result, during the initial analysis,
1-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 2.0 (2008-03-14)

cBSS Performance Management Guide

1 Performance Management Principle

check the basic network parameters and correct the wrongly configured parameters, including the PN planning, power control parameter, paging parameter (CDMA2000 1X services), and register parameter.

Isolation Analysis
After excluding the equipment fault and system parameter configuration fault, according to the performance data, do the isolation analysis. To obtain the overall network performance, you need to obtain the traffic measurement data of busy hour for more than a week. The common ways are as follows:
l

Collating the carrier frequency By collating the carrier frequency of abnormal indexes, you can obtain the analysis of the TOPN cell whose index is abnormal. With the geography display of tools, you can obtain information such as the location, start time, and type of the problem.

Worst time segment Obtain the worst time segment when the indexes are abnormal. Causes division Through the detailed traffic measurement indexes, further analyze the causes of the problem. The traffic measurement can analyze the following problems: A interface problem, resource assignment failure, and wireless interface fault. The reflect of these problems to the KPI is the abnormality of the indexes such as the call drop rate and call setup success rate (CDMA2000 1X services). More specific traffic measurement indexes are needed to isolate the KPI problems. For example, in the CDMA2000 1X network, the call failure is divided into A1 interface failure, call resource assignment failure, capture of the reverse service channel preamble failure, and level 2 handshake failure. Through the division of causes, you can effectively isolate the problem.

Index association Many indexes are associated. For example, the interference and coverage simultaneously affect several indexes. Thus, analyze the key KPI together with other indexes.

Take related measures to the network problem that is located by the traffic measurement, such as adjusting the antenna system, excluding the interference, and optimizing the parameters. Continue to focus on the change of the KPI.

Deep Locating Phase

The deep locating is to deep locate some difficult problems. It needs more specific data. In addition, it analyzes the data that collected both at the system and the road test. The logs, CHR, RFMT signaling tracing, and road test provide materials for the deep analysis of the part network performance. Due to the complexity and uncertainty of the wireless network, analyze only the traffic measurement data cannot deep locate problems. The system provides the following data to help the analysis: CHR, RFMT, PSMM (CDMA2000 1X services), and RouteUpdate (CDMA2000 1xEV-DO services). These data provide materials for deep locating. For details, see Performance Data for Deep Problem Location. For the problems located by analyzing the CHR, RFMT, and PSMM (CDMA2000 1X services), take the corresponding optimization measures and continuously trace the optimization results. If deep locate the problem, you need also analyze the data collected by the drive test.
Issue 2.0 (2008-03-14) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-15

1 Performance Management Principle

cBSS Performance Management Guide

For example, in the CDMA2000 1X network, with the CHR, RFMT, and PSMM, you can evaluate the network performance from several aspects. The aspect includes:

Analysis of Call Setup Failures (CDMA2000 1X services) and Call Drops

Through the analysis of the CHR, you can distinguish the cause type of the call setup failure (CDMA2000 1X services) and call drop and determine the specific cause that lead to the call setup failure (CDMA2000 1X services) and call drop. The type of the causes includes equipment abnormality and wireless link failure. If the failure is caused by the abnormal equipment, locate the abnormal equipment. If the wireless link fails, locate whether the failure is the forward link failure, reverse link failure, or handoff failure.

Analysis of the paging duration

Through the analysis of the call access duration, you can precisely evaluate the connection and paging of the network, locate the carrier frequency and mobile phone that have problems, and distinguish whether the problem is caused by the equipment or the air interface access probe.

Analysis of the Voice Quality (CDMA2000 1X)

Analyze from the aspect of the system, the voice quality is affected by source coding, channel coding, and transmission bit error. Through the analysis of the forward and reverse air interface bit error, distribution of the uplink and downlink rate frames of the DPUSb/DPUDb, and distribution of the uplink and downlink rate frames of the DPUTb. You can evaluate and analyze the voice quality and locate the carrier frequency and mobile phone that have problems.

Optimization of the Neighboring Cell Search Window

Using the analysis of the PSMM (CDMA2000 1X services) and the existed search window configuration in the BAM, check the rationality of the search window size of the active set and neighbor set. Then you can locate the carrier frequency whose search window is configured unreasonable. The analysis also provides configuration suggestions.

Optimization of the PSMM Neighboring Cell (CDMA2000 1X Services)

The analysis of the PSMM provides the optimization solution for the network structure, finds out the problem existed in the neighboring cells, and guides you to improve the network structure.

Analysis of the Data Service

Through the analysis of the CHR, you can obtain the average throughput at the user level, RLP average retransmission rate, release times of the SCH application (CDMA2000 1X services), average FER, forward and reverse load. Thus, you can effectively evaluate the performance of the VIP data users and locate the data service transmission performance.

Analysis of the MS Abnormal Power Control (CDMA2000 1X Services)

Through the abnormal power control events recorded in the CHR, analyze all the subscriber call to check whether many abnormalities exist and collate them. Thus, you can locate the mobile phone whose power control is abnormal and the affected sector carrier frequency.
1-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 2.0 (2008-03-14)

cBSS Performance Management Guide

1 Performance Management Principle

Collection of the Drive Test Data

The drive test is that a mobile phone does a simulated call test in the specific line. It collects the related information through the drive test software. The drive test is irreplaceable in obtaining the information of the coverage structure of the wireless network. It checks whether the following problems exist:
l l l l

Cross coverage Coverage dead zone Unbalanced uplink and downlink Reversely installed antenna

Normally, the following methods are used to analyze the network performance:
l l l l l l l

Comparison analysis of the data collected by the receiver and test MS Network coverage analysis Pilot pollution analysis Handoff analysis Access analysis Call drop analysis Analysis of the data service throughput and assignment strategy

During the drive test, test calls and load loading are used to simulate a real network. For details, see 8 Common Test Calls and Load Loading Functions and 9 CDMA2000 1xEV-DO Common Test Calls and Load Loading Functions.

Issue 2.0 (2008-03-14)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1-17