RAN Performance Management Guide(RAN11.0_01)

RAN

11.0

Performance Management Guide

Issue 01

Date 2009-03-25

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Introduction to Performance Management...........................................................................1-11.1 Definition of Performance Management.........................................................................................................1-21.2 Functions of Performance Management.........................................................................................................1-2

2 Performance Management Principles....................................................................................2-12.1 Performance Data............................................................................................................................................2-2

2.1.1 Performance Data Levels.......................................................................................................................2-22.1.2 Performance Data Levels.......................................................................................................................2-4

2.2 Performance Data Collection and Storage......................................................................................................2-72.2.1 Level 1 Data Collection and Storage......................................................................................................2-72.2.2 Level 2 Data Collection and Storage......................................................................................................2-82.2.3 Level 3 Data Collection and Storage......................................................................................................2-9

2.3 Introduction to Performance Management Tools............................................................................................2-92.3.1 Nastar...................................................................................................................................................2-102.3.2 Probe.....................................................................................................................................................2-112.3.3 Assistant...............................................................................................................................................2-112.3.4 Trace Viewer........................................................................................................................................2-12

3 Quasi-Real-Time Performance Monitoring..........................................................................3-13.1 Definition of Quasi-Real-Time Performance Monitoring...............................................................................3-23.2 Items of Quasi-Real-Time Performance Monitoring......................................................................................3-23.3 Analysis and Handling Based on Quasi-Real-Time Performance Monitoring...............................................3-4

4 RAN Routine Performance Monitoring and Evaluation....................................................4-14.1 Introduction to RAN Routine Performance Evaluation..................................................................................4-24.2 Items and Evaluation of RAN Routine Performance Monitoring...................................................................4-2

4.2.1 Daily Report...........................................................................................................................................4-24.2.2 Weekly Report........................................................................................................................................4-84.2.3 Monthly Report......................................................................................................................................4-9

5 Introduction to RAN KPIs........................................................................................................5-1

6 RAN Call History Records Reference....................................................................................6-1

RANPerformance Management Guide Contents

Issue 01 (2009-03-25) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

Figures

Figure 2-1 Level structure of performance data...................................................................................................2-2Figure 2-2 Performance data levels......................................................................................................................2-3Figure 2-3 Performance data levels......................................................................................................................2-5Figure 5-1 Classification of KPIs by measurement set........................................................................................5-2Figure 6-1 Process of CHR collection..................................................................................................................6-1

RANPerformance Management Guide Figures


iii

Tables

Table 2-1 Sublevels of performance data.............................................................................................................2-4Table 2-2 CHRs and sample tracing data.............................................................................................................2-6Table 3-1 KPIs to be monitored in quasi-real time..............................................................................................3-2Table 3-2 Reference thresholds for quasi-real-time performance monitoring.....................................................3-4Table 4-1 Sheets in a daily report.........................................................................................................................4-3Table 4-2 Evaluation and analysis of accessibility KPIs......................................................................................4-5Table 4-3 Evaluation and analysis of CDR KPIs.................................................................................................4-6Table 4-4 Evaluation and analysis of mobility KPIs............................................................................................4-7Table 4-5 Sheets in a weekly report.....................................................................................................................4-8

RANPerformance Management Guide Tables


v

About This Document

PurposeThis document describes the RAN performance management principles, performance data,performance analysis methods, and performance problem solutions.

Product VersionsThe following table lists the product versions related to this document.

Product Name Product Version

RNC V100R011

V200R011

NodeB V100R011

V200R011

M2000 V200R008

Intended AudienceThis document is intended for:

l Network planning engineers

l Network administration engineers

l Network operators

Organization

1 Introduction to Performance Management

This defines performance management and describes its functions.

2 Performance Management Principles

This describes the structure,levels,collection,storage of performance data,and the tools used forperformance management.

3 Quasi-Real-Time Performance Monitoring

RANPerformance Management Guide About This Document


1

Quasi-real-time performance monitoring involves quasi-real-time display of some KPIs andperformance analysis and diagnosis.

4 RAN Routine Performance Monitoring and Evaluation

RAN routine performance monitoring is implemented by the following routine reports and theevaluation is implemented through analysis of those routine reports.

5 Introduction to RAN KPIs

RAN Key Performance Indicators (KPIs) reflect the performance of the network. Throughmonitoring the variations of KPIs, you can detect the network performance problems as soon aspossible.

6 RAN Call History Records Reference

Call History Records (CHRs) are provided by NEs to meet the requirements of pre-defined callsignaling messages.

ConventionsSymbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk, which if notavoided,will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided,could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.

Provides additional information to emphasize or supplementimportant points of the main text.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

About This DocumentRAN


2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-03-25)


Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder .

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

RANPerformance Management Guide About This Document


3

Format Description

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to a certain position.

About This DocumentRAN


4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-03-25)

1 Introduction to Performance Management

About This Chapter

This defines performance management and describes its functions.

1.1 Definition of Performance ManagementThe RAN performance management is performed during the phases of network operation,maintenance, and optimization. It collects performance data and checks whether the networkconfiguration is physically and logically correct. Thus, potential problems can be found andsolved as soon as possible.

1.2 Functions of Performance ManagementThe functions of performance management include quasi-real-time performance monitoring,routine performance monitoring and evaluation.

RANPerformance Management Guide 1 Introduction to Performance Management


1-1

1.1 Definition of Performance ManagementThe RAN performance management is performed during the phases of network operation,maintenance, and optimization. It collects performance data and checks whether the networkconfiguration is physically and logically correct. Thus, potential problems can be found andsolved as soon as possible.

Performance management is one of the functional areas defined by TelecommunicationManagement Network (TMN) involving monitoring, analyzing, and controlling the networkperformance. Performance management is defined as follows: collecting performance data ofthe network, equipment, functions, services, or other objects periodically or in event-triggeringmode; collecting performance-related flow data; analyzing and handling collected data; savingand managing collected data.

Through the monitoring and analysis of the collected data, performance management owns thefollowing advantages: providing the status of the network and equipment; evaluating the validityof the network itself, NEs, and other objects; supporting network planning and optimization;guaranteeing the QoS of the network.

1.2 Functions of Performance ManagementThe functions of performance management include quasi-real-time performance monitoring,routine performance monitoring and evaluation.

Quasi-Real-Time Performance MonitoringQuasi-real-time performance monitoring involves data collection at short intervals, KPImonitoring, and performance-related alarm monitoring.

Compared with other types of monitoring, however, this type of monitoring uses more resources.Generally, it applies to only a few Key Performance Indicators (KPIs), such as the callcompletion rate and call drop rate.

For details, refer to 3 Quasi-Real-Time Performance Monitoring.

Routine Performance Monitoring and EvaluationRoutine performance monitoring and evaluation are implemented through routine reports onnetwork KPIs.

Routine reports consist of daily reports, weekly reports, and monthly reports. The formats of theroutine reports can be set as required.

For details, refer to 4 RAN Routine Performance Monitoring and Evaluation.

1 Introduction to Performance ManagementRAN


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2009-03-25)

2 Performance Management Principles

About This Chapter

This describes the structure,levels,collection,storage of performance data,and the tools used forperformance management.

2.1 Performance DataThe implementation of performance management needs the support of performance data.Different types of performance management require different performance data, collectiongranularities, and completeness. Therefore, it is necessary to divide performance data intodifferent levels and types.

2.2 Performance Data Collection and StorageThe collection and storage of performance data vary with the data types.

2.3 Introduction to Performance Management ToolsThe performance management tools include Nastar, Probe, Assistant, and Trace Viewer.

RANPerformance Management Guide 2 Performance Management Principles


2-1

2.1 Performance DataThe implementation of performance management needs the support of performance data.Different types of performance management require different performance data, collectiongranularities, and completeness. Therefore, it is necessary to divide performance data intodifferent levels and types.

2.1.1 Performance Data LevelsThe implementation of performance management needs the support of performance data.Different types of performance management require different performance data, collectiongranularities, and completeness. Performance data is divided into three levels: performancestatistics, CHRs, and monitoring data. Each level is further divided into several sublevels.

2.1.2 Performance Data LevelsPerformance data is divided into three levels according to width and depth.

2.1.1 Performance Data LevelsThe implementation of performance management needs the support of performance data.Different types of performance management require different performance data, collectiongranularities, and completeness. Performance data is divided into three levels: performancestatistics, CHRs, and monitoring data. Each level is further divided into several sublevels.

Level Structure

Figure 2-1 shows the level structure of performance data.

Figure 2-1 Level structure of performance data

In the level structure, the higher the level is, the higher the generality of the corresponding databecome. The data of different layers should be unique as far as possible.

2 Performance Management PrinciplesRAN



Issue 01 (2009-03-25)

Three Levels of Performance Datal Level 1: performance statistics

Used for checking performance health and evaluating general performance; oriented tonetwork operators

l Level 2: history performance data

Used for locating and analyzing common performance problems; oriented to senior networkoperators and the Network Information Center (NIC)

l Level 3: system monitoring data

Used for locating deep-seated performance problems; oriented to experienced and seniorspecialists

Figure 2-2 shows the performance data levels.The width of performance data indicates the statusof system performance and the scope of the problems involved. The depth of performance datareflects the capability of the performance data to help solve performance problems. In addition,the width and depth reflect the requirements of performance management, such as therequirements for data, analysis tool, and network topology.

Figure 2-2 Performance data levels

Sublevels of Performance Data

Table 2-1 describes the sublevels of performance data.



2-3

Table 2-1 Sublevels of performance data

Item Sub-item Main use Collection mode

RAN Counters KPI KPI monitoring, KPIreporting, andnorthbound interface

Collecting dataperiodically;supporting small-granularitycollection

Commonperformanceindicator

Performance datareporting, northboundinterface, generalnetwork performance,traffic, and equipmentusage evaluation

Collecting dataperiodically;supportingcollections atintervals of 5, 15, 30,and 60 minutes

Historyperformance data

Call history record(CHR)

CDR analysis, QoSevaluation, commonproblem location, usercomplaint handling

Collecting data inevent-triggeringmode or collectingall data; supportingautomatic collectionfor abnormal calls;supportingcontrolled collectionfor normal calls

System HistoryRecord (SHR)

Recording of thenetwork or cell statusand analysis of CHRs

Collecting data inevent-triggeringmode or collectingall data

RAN Tracing andMonitoring Data

Real-Time UserMonitor (RUM)

Further analysis of theproblems that cannot belocated according toCHRs, by analyzingspecified IMSIs orrandom IMSIs that areadmitted on the carrierswith high call drop rates

Collecting data inevent-triggeringmode, which usuallyneeds to be startedand stopped

Real-Time SystemMonitor (RSM)

Real-time recording ofsystem status, such asload information andinterferenceinformation, to helplocate deep-seatedproblems

2.1.2 Performance Data LevelsPerformance data is divided into three levels according to width and depth.

The width of performance data indicates the status of system performance and the scope of theproblems involved. The depth of performance data reflects the capability of the performance




Issue 01 (2009-03-25)

data to help solve performance problems. In addition, the width and depth reflect therequirements of performance management, such as the requirements for data, analysis tool, andnetwork topology.

Figure 2-3 shows the performance data levels.

Figure 2-3 Performance data levels

2.1.2.1 Level 1 DataLevel 1 data is derived from performance statistics and alarm data.

2.1.2.2 Level 2 DataLevel 2 data is mainly derived from Call History Records (CHRs) and sample tracing data.

2.1.2.3 Level 3 DataLevel 3 data is mainly derived from drive test data and single UE tracing data.

Level 1 Data

Level 1 data is derived from performance statistics and alarm data.

Level 1 data features the maximum width, the minimum depth, and low processing cost.According to the output reports, network administrators can know the running state of thenetwork and quickly find out potential problems.

Because of the minimum depth, level 1 data cannot be independently used to locate networkproblems. The specific reasons are as follows:



2-5

l Statistics can give only performance statistics but cannot provide specific reasons.

l Some KPIs can indicate the degraded direction but they cannot provide specific reasonsindependently. For example, a KPI indicates an increase in the number of call drops. Ananalysis of the KPIs related to the call drop has revealed that the call drop is due to the SRBreset. The SRB reset, in turn, is due to poor coverage, UL interference, or untimelyhandover.

l Alarm data indicates the problems related to the running of the equipment. Alarm dataincludes : alarms related to the KPIs of the whole network, such as RNC board abnormalityalarm and Iu interface abnormality alarm, and alarms related to a cell or a NodeB, such asfeeder abnormality alarm and Iub transmission disruption alarm.

Level 2 Data

Level 2 data is mainly derived from Call History Records (CHRs) and sample tracing data.

Table 2-2 describes the CHRs and sample tracing data.

Table 2-2 CHRs and sample tracing data

Data Type CHRs Sample tracing data

Definition Important information that isexported by each NE during eachcalling procedure.

Data collected by UEs actively.The measurement is started whenthe preset conditions are met, andthe sample data can be set.

Scope Oriented to all the intra-RNC UEsthat meet the preset conditions.

Oriented to one or more UEs in aspecified cell.

Content Calling procedure information,such as the signaling procedurestatus before call drop,measurement report informationreported before call drop, andsignal status during access to thenetwork.

Measurement results reported byUEs, such as DL pilot RSCP andEc/Io, and dedicated measurementinformation reported by the RNCand NodeBs.

Level 2 data is analyzed by Nastar.

Compared with level 1 data, level 2 data features smaller width but larger depth. It is orientedto network support engineers and used to locate common performance problems, which comprise80% of all problems.

Level 3 Data

Level 3 data is mainly derived from drive test data and single UE tracing data.

The main difference between drive test data and single UE tracing data is as follows:

l During a drive test, a UE is tested and its detailed information is recorded. The informationincludes the TX power of the UE, pilot signal status measured by the UE, DL pilot BLER,throughput, and signaling procedure. The Probe, along with the Scanner, can also collectcoverage information. The collection cost, however, is high.




Issue 01 (2009-03-25)

l During a single UE tracing, the information of the network side of a UE is traced. Theinformation includes the measurement results reported by the NodeB and the RNC as wellas standard interface (Iu/Iur/Iub/Uu) information. Single UE tracing is performed when aUE cannot support the Probe.

The relevant tools are as follows:l Probe: used to collect drive test data.

l Assistant: used to process drive test data and single UE tracing data.

l Trace Viewer: used to analyze single UE tracing data

Level 3 data has the maximum depth and minimum width. As a result, the processing cost ishigh. Level 3 data is mainly used by network engineers or administrators to solve differentproblems due to its low collection. Single UE tracing data and drive test data can be used tolocate almost all the problems.

2.2 Performance Data Collection and StorageThe collection and storage of performance data vary with the data types.

2.2.1 Level 1 Data Collection and StorageLevel 1 data includes performance statistics and alarm data. The traffic statistics in theperformance statistics are generated by the RNC and the NodeB and reported to the M2000. Thetraffic statistics of the RNC are stored as files in the RNC BAM before they are reported to theM2000, and the traffic statistics of the NodeB are reported to the M2000 through messages. Toview the traffic statistics of the NodeB, you need to export the related files from the M2000.

2.2.2 Level 2 Data Collection and StorageLevel 2 data includes Call History Records (CHRs), system log data, and sample tracing data.CHRs can be categorized into two types: default CHR and Performance CHR (PCHR). Thedefault CHRs record unexpected events upon occurrence during calls. PCHRs record theessential information of all calls, including both normal and abnormal calls.

2.2.3 Level 3 Data Collection and StorageLevel 3 data includes drive test data, single UE tracing data, interface tracing data, and linktracing data. The recording of specific types of data is user-defined. Because of its huge amount,level 3 data is usually stored in the terminal computer of the user.

2.2.1 Level 1 Data Collection and StorageLevel 1 data includes performance statistics and alarm data. The traffic statistics in theperformance statistics are generated by the RNC and the NodeB and reported to the M2000. Thetraffic statistics of the RNC are stored as files in the RNC BAM before they are reported to theM2000, and the traffic statistics of the NodeB are reported to the M2000 through messages. Toview the traffic statistics of the NodeB, you need to export the related files from the M2000.

NOTE

For alarm data collection and storage, you can refer to the related operation and maintenance manual, suchas the RAN Routine Maintenance Guide.

Data CollectionPerformance statistics are automatically collected by the RNC and NodeB.



2-7

The collection granularity can be set to 5, 15, 30, or 60 minutes on the M2000. The minimumreporting granularity is 5 minutes. The default is 30 minutes.

Data StorageAll the data reported by the RNC is stored in the RNC BAM. Meanwhile, the BAM reports partof the Key Performance Index (KPI) to the M2000. The performance statistics of the NodeB arereported to the M2000 directly.

The performance statistics in the BAM are stored in binary format. The default path for storingthe statistics is BAM active workspace\FTP\NastarResult. By default, the statistics are storedfor three days.

The file name includes the data recording time, start time, and end time, for example,A20060417.0400+0800-0500+0 800_EMS-NORMAL.mrf.bz2.

l RNC performance statistics are automatically reported through FTP and then stored in theM2000.

l NodeB performance statistics are reported to the M2000 in stream mode. NodeBperformance statistics files will be generated automatically.

Then, the M2000 provides performance statistics of the RNC and the NodeB for Nastar or thethird party through FTP interface.

Data ProvisionThe stored performance statistics can be exported directly to Nastar for analysis and queried onthe basis of granularity, cell, or RNC.

2.2.2 Level 2 Data Collection and StorageLevel 2 data includes Call History Records (CHRs), system log data, and sample tracing data.CHRs can be categorized into two types: default CHR and Performance CHR (PCHR). Thedefault CHRs record unexpected events upon occurrence during calls. PCHRs record theessential information of all calls, including both normal and abnormal calls.

Data Collectionl The RNC has individual switches for different information modules of the CHR. The

information modules include the intra-frequency neighboring cell optimization, inter-frequency neighboring cell optimization, and inter-RAT neighboring cell optimization.Currently, all the switches are off by default. If a switch being on proves to have little impacton products, the switch can be set to on by default. You can decide whether to report therelated information by setting the switches on the LMT or M2000.

l The system log data is recorded upon the occurrence of particular events.

l The sampling of tracing data is used to control the collection of tracing data by starting thetracing function on the RNC LMT. The data that can be controlled includes the collecteddata, sampling scope, and reporting period of measurement reports, among which thecollected data includes standard signaling, measurement reports, and internal messages.

Data Storagel The CHRs of the RNC are sent to the RNC BAM and then stored in the BAM after

compression. The CHRs of the NodeB are sent to and stored in the FTP server.




Issue 01 (2009-03-25)

l The system log data of the RNC is sent to and stored in the RNC BAM. The system logdata of the NodeB is sent to the specified FTP server through MML commands.

l The sample tracing data is recorded by the user and is usually stored in the terminalcomputer on which the tracing is started. You can set the file name and path for savingwhen starting the tracing.

Data ProvisionNastar has no special demands on the formats of CHRs and, therefore, can directly import andanalyze CHRs.

2.2.3 Level 3 Data Collection and StorageLevel 3 data includes drive test data, single UE tracing data, interface tracing data, and linktracing data. The recording of specific types of data is user-defined. Because of its huge amount,level 3 data is usually stored in the terminal computer of the user.

Data CollectionFor collection of drive test data, refer to related network planning documents.

To collect single UE tracing data and interface tracing data, start the tracing function on the RNCLMT. The data that can be controlled is as follows:l Messages on standard interfaces to be traced

l UE identifiers to be traced

l Cells to be traced

To collect link tracing data, start the tracing function on the RNC LMT. The data that can becontrolled includes link performance data, such as UE transmit power and BLER.

Data StorageThe data is stored in the terminal computer on which the tracing is started. You can set the filename and path for saving when starting the tracing.

Drive test data is stored on the operated computer.

All tracing data is stored in files.

Data ProvisionAll tracing data is analyzed in files.

The tool for analyzing drive test data is determined by the terminal type. Single UE tracing dataand standard interface tracing data is analyzed by the Trace Viewer.

2.3 Introduction to Performance Management ToolsThe performance management tools include Nastar, Probe, Assistant, and Trace Viewer.

2.3.1 Nastar



2-9

Nastar is a network optimization tool, one of the Genex series wireless tools of Huawei. It is anintelligent network performance monitoring and optimizing platform, integrating a large numberof network optimization experiences of Huawei.

2.3.2 ProbeProbe is one of the Genex series wireless tools of Huawei for testing GSM/GPRS/EDGE,WCDMA, HSPA air interfaces. It is used to collect data of the wireless network air interfacesand to verify the planning and optimization of the wireless network. It also provides guidelinesfor troubleshooting, and further planning and optimizing network.

2.3.3 AssistantAssistant is one of the Genex series wireless tools of Huawei for postprocessing data. It is usedto analyze and process air interface data of GSM/GPRS/EDGE, WCDMS and HSPA (includingdrive test data and RNC data) and generate analysis reports.

2.3.4 Trace ViewerTrace Viewer is a tool released with the Huawei RNC. It can retrieve single UE tracing data andthe signaling messages of standard interface.

2.3.1 NastarNastar is a network optimization tool, one of the Genex series wireless tools of Huawei. It is anintelligent network performance monitoring and optimizing platform, integrating a large numberof network optimization experiences of Huawei.

Nastar can monitor the network performance, locate network problems, and forecast networkdevelopment trend efficiently through intelligent data management and analysis, whichconsequently meets the operator requirements of deeper service. Genex Nastar WCDMAprovides more network optimization and problem analysis through data and service integration.

The data source includes:

l Configuration data

l Engineering parameters

l Performance data

l CHR data

l RTWP data

l IOS trace data

l NodeB RTWP data

The main features of Nastar are as follows:

l Providing more than 30 performance queries that are classified into 5 subjects and Top Nquery, providing detailed information about the subjects on the basis of flexible secondaryquery to further analyze network problems and consider the user concerns.

l Outputting network routine operation, network health status and network monitoringreports automatically or non-automatically on the basis of intelligent graded reportingsystem to provide the most valued information for different users

l Analyzing the variation trend of KPIs and comparing KPIs of different periods to verifythe optimization effect

l Supporting user-defined specification and reporting pattern, providing custom-built serviceaccording to the operation strategies of the operators




Issue 01 (2009-03-25)

l Supporting neighboring cell optimization, analyzing pilot pollution, interference, call drop,access, and network coverage to erase incipient faults and solve the network problemsultimately

l Analyzing and checking configuration parameters, configuration parameters of historicalversions and neighboring cell configuration to help engineering personnel locate networkproblems quickly

l Displaying the analysis results in diagrams and maps to help locate fault areas

l Judging network and service variation tendency through long-term monitoring andanalyzing, providing expansion and relocation reference according to the operatorconceptions for more reasonable investment

2.3.2 ProbeProbe is one of the Genex series wireless tools of Huawei for testing GSM/GPRS/EDGE,WCDMA, HSPA air interfaces. It is used to collect data of the wireless network air interfacesand to verify the planning and optimization of the wireless network. It also provides guidelinesfor troubleshooting, and further planning and optimizing network.

Probe performs the following main functions:

l Performing WCDMA and GSM multimode test, collecting L1 data, decoding L1, L2, andL3 of WCDMA and GSM and air interface messages of L1, L2, and L3 of GPRS

l Performing continuous wave (CW) test and geographic average-calculation operation oftest data ,and exporting processed propagation model data as input of network planningsoftware

l Performing concurrent multiservice test, and supporting the set of test items and QoSparameters

l Saving, exporting, combining and retrieving test data, and providing original data fornetwork planning software and other daemons

l Automatically judging key events ,performing voice prompt, and providing other graphicalinterface prompts

2.3.3 AssistantAssistant is one of the Genex series wireless tools of Huawei for postprocessing data. It is usedto analyze and process air interface data of GSM/GPRS/EDGE, WCDMS and HSPA (includingdrive test data and RNC data) and generate analysis reports.

Assistant G/W helps network planning and optimization engineers learn the networkperformance more clearly so as to analyze network problems efficiently. Assistant provides thefollowing functions:

l Providing GSM, GPRS, and EDGE drive test data analysis, and providing comprehensivesolution for multi-network competition and interoperation between GSM and WCDMAsystems

l Providing WCDMA test data analysis, problem analysis , location reports and KPI statisticsreports

l Providing joint analysis of drive test data and RNC test data or single user tracing signalsto realize synchronization analysis of UL and DL data for further locating difficult problems

l Providing HSDPA drive test data analysis, realizing analysis of handover events amongHSDPA, R99, and 2G, and providing HSDPA-related performance analysis reports



2-11

l Providing HSDPA statistics analysis, and describing actual network condition,configuration, speed statistics, channel decoding statistics and service performance

l Providing HSUPA drive test data analysis, realizing analysis of handover events amongHSDPA, R99, and 2G, and providing HSUPA-related performance analysis reports,providing micro data analysis of HSUPA 2ms and 10ms and HSDPA crosstab reports

l Providing data-merged processing

l Providing multiple analysis methods through locking data or filtering data according todifferent conditions

2.3.4 Trace ViewerTrace Viewer is a tool released with the Huawei RNC. It can retrieve single UE tracing data andthe signaling messages of standard interface.

Trace Viewer is mainly used to retrieve tracing data. It is designed forl Network planners to solve difficult problems under the help of the drive test tool

l System engineers to analyze problems




Issue 01 (2009-03-25)

3 Quasi-Real-Time Performance Monitoring

About This Chapter

Quasi-real-time performance monitoring involves quasi-real-time display of some KPIs andperformance analysis and diagnosis.

3.1 Definition of Quasi-Real-Time Performance MonitoringThe RNC and NodeBs report the counters for calculating KPIs to the OM system at smallintervals. After calculation, the OM system monitors and displays these KPIs in real time. Thismode is called quasi-real-time monitoring.

3.2 Items of Quasi-Real-Time Performance MonitoringItems of quasi-real-time performance monitoring include the KPIs of VIP cells and the KPIs ofhot spot cells.

3.3 Analysis and Handling Based on Quasi-Real-Time Performance MonitoringKPIs monitored in quasi-real-time usually have corresponding reference thresholds. When a KPIvalue exceeds its reference threshold, corresponding measures shall be taken.

RANPerformance Management Guide 3 Quasi-Real-Time Performance Monitoring


3-1

3.1 Definition of Quasi-Real-Time Performance MonitoringThe RNC and NodeBs report the counters for calculating KPIs to the OM system at smallintervals. After calculation, the OM system monitors and displays these KPIs in real time. Thismode is called quasi-real-time monitoring.

Through the monitoring of KPIs in small granularity mode, quasi-real-time performancemonitoring helps rapidly know the variations of KPIs and improve KPIs that exceed thethresholds. In addition, it can help rapidly determine whether there are exceptions in a specialcase, such as before or after the upgrade, so that the exceptions can be removed in time.

Quasi-real-time monitoring of RAN system performance statistics is controlled by the M2000.The periods of performance monitoring and performance data collection are the same. Thecollection period and monitoring range are set on the M2000. The period granularity can be 5,15, 30, or 60 minutes. Performance monitoring results can be displayed on the M2000.

3.2 Items of Quasi-Real-Time Performance MonitoringItems of quasi-real-time performance monitoring include the KPIs of VIP cells and the KPIs ofhot spot cells.

Table 3-1 describes the KPIs to be monitored in quasi-real time.

Table 3-1 KPIs to be monitored in quasi-real time

Name Description RNCLevel

NodeBLevel

CellLevel

RRCConnectionSetup SuccessRate (service)

Number of RRC connectionsetup successes (service) /Number of RRC connectionsetup attempts (service)

√ – √

AMR RABAssignmentSuccess Rate

Number of AMR RABassignment successes / Numberof AMR RAB assignmentattempts

√ – √

VP RABAssignmentSuccess Rate

Number of VP RAB assignmentsuccesses / Number of VP RABassignment attempts

√ – √

PS RABAssignmentSuccess Rate

Number of PS RAB assignmentsuccesses / Number of PS RABassignment attempts

√ – √

CS AMR CallDrop Rate

Number of AMR call drops /Number of AMR RABassignment successes

√ – √

VP Call DropRate

Number of VP call drops /Number of VP RAB assignmentsuccesses

√ – √

3 Quasi-Real-Time Performance MonitoringRAN



Issue 01 (2009-03-25)


NodeBLevel

CellLevel

PS Service DropRate

Number of PS service drops /Number of PS RAB setupsuccesses

√ – √

Soft HandoverSuccess Rate

Number of soft handoversuccesses / Number of softhandover attempts

√ – √

CS Inter–RATHandoverSuccess Rate(from UTRANto GSM)

Number of successful CSservice handovers from UMTS /Number of attempted CSservice handovers from UMTS

√ – √

PS Inter-RATHandoverSuccess Rate(from UTRANto GSM)

Number of successful PSservice handovers from UMTS /Number of attempted PS servicehandovers from UMTS

√ – √

Inter-Freq HardHandoverSuccess Rate

Number of inter-frequency hardhandover successes / Number ofinter-frequency hard handoverattempts

√ – –

UL CE UsageRate

Occupied NodeB UL CEresources / Total NodeB UL CEresources

– √ –

DL CE UsageRate

Occupied NodeB DL CEresources / Total NodeB DL CEresources

– √ –

UL IubAllocatedBandwidthUsage Rate

Allocated bandwidth of UL Iub /Physical bandwidth of UL Iub

– √ –

DL IubAllocatedBandwidthUsage Rate

Allocated bandwidth of DL Iub /Physical bandwidth of DL Iub

– √ –

DL Code UsageRate

Occupied DL code resources /Total cell code resources

– – √

CS NetworkLoad

– √ – –

PS ULThroughput

– √ – –



3-3


NodeBLevel

CellLevel

PS DLThroughput

– √ – –

3.3 Analysis and Handling Based on Quasi-Real-TimePerformance Monitoring

KPIs monitored in quasi-real-time usually have corresponding reference thresholds. When a KPIvalue exceeds its reference threshold, corresponding measures shall be taken.

Table 3-2 lists the KPIs, reference thresholds, brief analysis, and handling suggestions.

CAUTIONThe reference thresholds provided in Table 3-2 are only for reference. In practice, the thresholdsshould meet the requirements of the network operators or the site.

Table 3-2 Reference thresholds for quasi-real-time performance monitoring

Name ReferenceThreshold

Brief Analysis HandlingSuggestion

RRC Connection SetupSuccess Rate (service)

98% If this KPI is lower thanthe referencethreshold, it leads to alow access success rateand low usersatisfaction.This KPI is mainlyaffected by lowcoverage, improperparameter setting, andequipment factors.

Analyze thecauses of thefailure and takecorrespondingmeasures.Forexample, increasethe power,enhance thecoverage quality,or handleequipmentalarms.

AMR RAB AssignmentSuccess Rate

98% If this KPI is lower thanthe referencethreshold, it leads to alow access success rateand low usersatisfaction.This KPI is mainlyaffected by lowcoverage, untimelyhandover, insufficientresource, andequipment factors.

Analyze thecauses of thefailure and takecorrespondingmeasures.Forexample, increasethe coveragequality, expandthe capacity, orreconfigureparameters.




Issue 01 (2009-03-25)



VP RAB AssignmentSuccess Rate



PS RAB AssignmentSuccess Rate



CS AMR Call Drop Rate 1.5% If this KPI is higherthan the referencethreshold, it leads to ahigh call drop rate andlow user satisfaction.This KPI is mainlyaffected by lowcoverage, untimelyhandover, missedneighboring cellconfiguration, pilotpollution, andequipment factors.

Analyze thecauses of thefailure and takecorrespondingmeasures.Forexample, increasethe coveragequality orreconfigureparameters.



3-5



VP Call Drop Rate 3% If this KPI is higherthan the referencethreshold, it leads to ahigh call drop rate andlow user satisfaction.This KPI is mainlyaffected by lowcoverage, untimelyhandover, missedneighboring cellconfiguration, pilotpollution, andequipment factors.


PS Service Drop Rate 5% If this KPI is higherthan the referencethreshold, it leads to ahigh service drop rateand low usersatisfaction.This KPI is mainlyaffected by lowcoverage, untimelyhandover, missedneighboring cellconfiguration, pilotpollution, andequipment factors.


Soft Handover SuccessRate

99% If this KPI is lower thanthe referencethreshold, it leads to ahigh call dropprobability and lowuser satisfaction.This KPI is mainlyaffected by untimelyhandover due toimproper handoverparameter setting, lowcoverage, insufficientsystem resources, andequipment factors.

Check equipmentalarms, systemresources, andhandoverparameter setting.




Issue 01 (2009-03-25)



CS Inter-RAT HandoverSuccess Rate (fromUTRAN to GSM)

96% If this KPI is lower thanthe referencethreshold, it leads to ahigh call dropprobability and lowuser satisfaction.This KPI is mainlyaffected by handoverparameter setting,other parametersetting, andneighboring cellconfiguration.

Check handoverparametersettings and otherparametersettings. Theimproper settingsmay causeuntimelyhandovers.

PS Inter-RAT HandoverSuccess Rate (fromUTRAN to GSM)

92% If this KPI is lower thanthe referencethreshold, it leads to ahigh service dropprobability and lowuser satisfaction.This KPI is mainlyaffected by handoverparameter setting,other parametersetting, andneighboring cellconfiguration.

Check handoverparametersettings and otherparametersettings. Theimproper settingsmay causeuntimelyhandovers.

Inter-Freq Hard HandoverSuccess Rate

95% If this KPI is lower thanthe referencethreshold, it leads to ahigh call dropprobability and lowuser satisfaction.This KPI is mainlyaffected by untimelyhandover due toimproper handoverparameter setting,improper compressedmode parametersetting, and networkcongestion.

Check handoverparametersettings,compressedmode parameters,and resourceusage.



3-7



UL CE Usage Rate – This KPI indicates theusage of NodeBhardware resources.

Find out potentialresourcebottlenecks andtake thecorrespondingexpansionmeasures.

DL CE Usage Rate – This KPI indicates theusage of NodeBhardware resources.


UL Iub AllocatedBandwidth Usage Rate

– This KPI indicates theusage of NodeB Iubresources.


DL Iub AllocatedBandwidth Usage Rate

– This KPI indicates theusage of NodeB Iubresources.


DL Code Usage Rate – This KPI indicates theusage of cell DL coderesources.


CS Network Load – This KPI indicates thecapacity of the CSdomain.

Find out potentialexpansionrequirements andtake thecorrespondingexpansionmeasures.




Issue 01 (2009-03-25)



PS UL Throughput – This KPI indicates thecapacity of the PSdomain.


PS DL Throughput – This KPI indicates thecapacity of the PSdomain.




3-9

4 RAN Routine Performance Monitoring andEvaluation

About This Chapter

RAN routine performance monitoring is implemented by the following routine reports and theevaluation is implemented through analysis of those routine reports.

4.1 Introduction to RAN Routine Performance EvaluationRAN routine performance evaluation involves periodically obtaining of network KPIs, analysisof network problems, and analysis of KPI variations.

4.2 Items and Evaluation of RAN Routine Performance MonitoringThe reports of routine performance monitoring consist of daily reports, weekly reports, andmonthly reports.

RANPerformance Management Guide 4 RAN Routine Performance Monitoring and Evaluation


4-1

4.1 Introduction to RAN Routine Performance EvaluationRAN routine performance evaluation involves periodically obtaining of network KPIs, analysisof network problems, and analysis of KPI variations.

RAN routine performance evaluation is implemented through routine reports.

Routing reports are provided for network administrators and network support engineers toperiodically obtain network KPIs and their variation so as to monitor the network quality.

NOTE

The NEL has Local Server that can collect CHR data automatically. The network operator needs to collectperformance statistics and network configuration data to generate daily reports.

4.2 Items and Evaluation of RAN Routine PerformanceMonitoring

The reports of routine performance monitoring consist of daily reports, weekly reports, andmonthly reports.

4.2.1 Daily ReportDaily reports are provided for network operators to monitor the network performance. Duringthe initial phase after the network is put into use, it is required to acquire the running status ofthe network at short periods. Daily reports can be used to find and identify some networkproblems.

4.2.2 Weekly ReportWeekly reports are provided for network operators to learn the variation tendency of the networkperformance as well as to analyze and optimize the KPIs with degradation trend. It focuses onthe variation tendency of each KPI.

4.2.3 Monthly ReportMonthly reports include the KPIs and the variation tendency of each KPI in a month.

4.2.1 Daily ReportDaily reports are provided for network operators to monitor the network performance. Duringthe initial phase after the network is put into use, it is required to acquire the running status ofthe network at short periods. Daily reports can be used to find and identify some networkproblems.

Generation ModesThe modes of generating daily reports are as follows:l Generating daily reports directly on the M2000

l Generating daily reports through the import of performance statistics into the Nastar

Main ContentsA daily report includes the following contents:

4 RAN Routine Performance Monitoring and EvaluationRAN



Issue 01 (2009-03-25)

l Main KPIs of the network

l KPI forecast

l Top N problem cells

l Problem causes and problem distribution areas

l KPIs of VIP cells (VICs)

A daily report includes the KPIs which are used to evaluate the network quality, displays intables the ten cells that have the worst KPIs, and provides reasons for bad KPIs.

Sheets in a Daily ReportTable 4-1 describes the sheets in a daily report.

Table 4-1 Sheets in a daily report

Sheet Name Description Function Remarks

KPI List of KPIs Providing the KPIs ofeach cell

KPI monitoring: Payparticular attention tothe red unsatisfactoryKPIs. In addition, notethe KPIs approachingthe thresholds.

CS Call DropCells

List of CS call drops Providing the numberof CS call drops in eachcell

Call drop monitoring:The CS Call DropCells and PS DropCells sheets focus onthe cells with severe calldrops. If the mostcauses for call drop areOther, analyze CHRsto find out the specificcauses.

PS Drop Cells List of PS servicedrops

Providing the numberof PS service drops ineach cell

RRC Fail List of the statisticsof RRC connectionfailures

Providing the numberof RRC connectionrejections in each cell

RRC connectionmonitoring: The RRCFail sheet lists the cellswith high RRCconnection rejectionrate and the rejectioncauses.

CS RAB FAIL List of the numberof CS RAB failures

Providing the numberof CS RAB failures ineach cell

RAB monitoring: TheCS RAB FAIL and PSRAB FAIL sheets listthe cells where the RABassignment fails.PS RAB FAIL List of the number

of PS RAB failuresProviding the numberof PS RAB failures ineach cell



4-3

Sheet Name Description Function Remarks

SHO FAIL List of the numberof soft handoverfailures

Providing the numberof soft handoverfailures in each cell

Handover monitoring:Pay more attention tothe cells with more softhandover failures.l The SHO FAIL

sheet lists the cellswhere soft handoverfails.

l The InterFreqHHO Fail sheet liststhe cells where inter-frequency hardhandover fails.

l The CS InterRATHHO FAIL sheetlists the cells wherethe inter-RAT hardhandover in the CSdomain fails.

l The PS InterRATHHO FAIL sheetlists the cells wherethe inter-RAT hardhandover in the PSdomain fails.

InterFreq HHOFail

List of the numberof inter-frequencyhard handoverfailures

Providing the numberof inter-frequency hardhandover failures ineach cell

CS InterRATHHO FAIL

List of the numberof CS domain inter-RAT hard handoverfailures

Providing the numberof CS domain inter-RAT hard handoverfailures in each cell

PS InterRATHHO FAIL

List of the numberof PS domain inter-RAT hard handoverfailures

Providing the numberof PS domain inter-RAT hard handoverfailures in each cell

Traffic List of trafficinformation

Providing trafficinformation of eachcell

–

VIP Cell List of trafficinformation of eachVIP cell

Providing trafficinformation of eachVIP cell

VIP cell analysis: TheVIP Cell sheet lists thecall drop informationand related KPIs of eachVIP cell.

Hot Traffic Cell List of trafficinformation of eachhot spot cell

Providing trafficinformation of each hotspot cell

–

Evaluation and AnalysisThe daily report generated by Nastar covers aspects such as the traffic, access, and handover.

The KPIs are analyzed in respect of the accessibility, Call Drop Rate (CDR), and mobility.

Table 4-2 provides the evaluation and analysis of the accessibility KPIs.




Issue 01 (2009-03-25)

Table 4-2 Evaluation and analysis of accessibility KPIs

KPI Function ReferenceValue

Evaluation and Analysis

RRCConnectionSetupSuccess Rate(service)

Indicating thesuccess rate ofRRC connectionsetup

98% If this KPI is obviously lower than thereference value, the access success rate islow and ,therefore, optimization isrequired.The main reasons include too many poor-coverage points, improper power settings,and network congestion.It is required to optimize RF, adjust powersettings, and expand network capacity.

AMR RABAssignmentSuccess Rate

Indicating thesuccess rate ofAMR RABassignment

98% If this KPI is obviously lower than thereference value, the access success rate islow and ,therefore ,optimization isrequired.The main causes include poor coverage,handover problems, insufficientresources, and equipment factors.It is required to enhance the coverage,expand the network capacity, and adjustparameters.

Video CallRABAssignmentSuccess Rate

Indicating thesuccess rate ofVP RABassignment

98% If this KPI is obviously lower than thereference value, the access success rate islow and ,therefore, optimization isrequired.The main causes include poor coverage,handover problems, insufficientresources, and equipment factors.It is required to enhance the coverage,expand the network capacity, and adjustparameters.

PS RABAssignmentSuccess Rate

Indicating thesuccess rate ofPS RABassignment

97% If this KPI is obviously lower than thereference value, the access success rate islow and ,therefore ,optimization isrequired.The main causes include poor coverage,handover problems, insufficientresources, and equipment factors.It is required to enhance the coverage,expand the network capacity, and adjustparameters.

Table 4-3 provides the evaluation and analysis of the CDR KPIs.



4-5

Table 4-3 Evaluation and analysis of CDR KPIs



CS AMRCall DropRate

Indicating thelink retainabilityof AMR services

1.5% If this KPI is obviously higher than thereference value, the service retainability ispoor and, therefore, optimization isrequired.The main causes include poor coverage,handover problems, insufficientresources, and equipment factors.It is required to adjust the network basedon specific causes.

VP CallDrop Rate

Indicating thelink retainabilityof VP services

3% If this KPI is obviously higher than thereference value, the service retainability ispoor and ,therefore, optimization isrequired.The main causes include poor coverage,handover problems, insufficientresources, and equipment factors.It is required to adjust the network basedon specific causes.

PS ServiceDrop Rate

Indicating thelink retainabilityof PS services

5% If this KPI is obviously higher than thereference value, the service retainability ispoor and ,therefore ,optimization isrequired.The main causes include poor coverage,handover problems, insufficientresources, and equipment factors.It is required to adjust the network basedon specific causes.

Table 4-4 provides the evaluation and analysis of mobility KPIs.




Issue 01 (2009-03-25)

Table 4-4 Evaluation and analysis of mobility KPIs



SoftHandoverSuccess Rate

Indicating theperformance ofsoft handover inthe network

99% If this KPI is obviously lower than thereference value, the performance of softhandover is low ,andtherefore ,optimization is required.The main causes are untimely handoverdue to improper handover parametersettings, poor coverage, insufficientresources, and equipment factors.It is required to optimize handoverparameters or handle equipment alarms.

Inter-FreqHardHandoverSuccess Rate

Indicating theperformance ofinter-frequencyhard handover inthe network

95% If this KPI is obviously lower than thereference value, the performance of inter-frequency hard handover degrades, whichaffects the user experience.The main causes are untimely handoverdue to improper handover parametersettings, improper compressed modeparameter settings, and networkcongestion.It is required to optimize handoverparameters and adjust the network.

CS Inter-RATHandoverSuccess Rate(fromUTRAN toGSM)

Indicating theperformance ofCS domain inter-RAT handover(from UTRANto GSM) in thenetwork

96% If this KPI is obviously lower than thereference value, the performance of theinter-RAT handover in the CS domaindegrades, which affects the userexperience.The main causes are improper setting ofthe handover parameters, the otherparameters, and neighboring cells.It is required to check the networkconfiguration and alarms.

PS Inter-RATHandoverSuccess Rate(fromUTRAN toGSM)

Indicating theperformance ofPS domain inter-RAT handover(from UTRANto GSM) in thenetwork

92% If this KPI is obviously lower than thereference value, the performance of theinter-RAT handover in the PS domaindegrades, which affects the userexperience.The main causes are improper setting ofthe handover parameters, he otherparameters, and neighboring cells.It is required to check the networkconfiguration and alarms.



4-7

4.2.2 Weekly ReportWeekly reports are provided for network operators to learn the variation tendency of the networkperformance as well as to analyze and optimize the KPIs with degradation trend. It focuses onthe variation tendency of each KPI.

Generation ModesThe modes of generating weekly reports are as follows:

l Generating weekly reports directly on the M2000

l Generating weekly reports through the import of performance statistics into the Nastar

Main ContentsA weekly report includes the following contents:

l Variation tendency of the main KPIs of the network in a week

l Problem causes and problem distribution areas

Sheets in a Weekly Report

Table 4-5 describes the sheets in a weekly report.

Table 4-5 Sheets in a weekly report

SheetName

Description Function Remarks

KPI List of KPIs Provides the KPIs of eachcell

KPI monitoring: Payparticular attention to the redunsatisfactory KPIs. Inaddition, note the CDR KPIsapproaching the thresholds.

PAGEReport

List and chartof paginginformation

Provides a list and a chartthat indicate the number ofpaging attempts and pagingsetups performed atdifferent time points whenthe UE is in idle mode

–

RRC Report List and chartof RRCinformation

Provides a list and a chartthat indicate the RRCconnection setup and failureinformation at different time

RRC monitoring: The RRCReport sheet provides thevariation tendency of theRRC connection setupsuccess rate in a week.

RABReport

List and chartof RABinformation

Provides a list and a chartthat indicate the RABassignment and failureinformation at different time

RAB monitoring: The RABReport sheet provides thevariation tendency of theRAB assignment successrate in a week.




Issue 01 (2009-03-25)

SheetName

Description Function Remarks

CDR List and chartof CS and PScall dropinformation

Provides a list and a chartthat indicate the CS and PScall drop information atdifferent time points

Call drop monitoring: TheCDR sheet provides thevariation tendency of the calldrop rate in a week.

Inter-RATHO Report

List and chartof inter-RAThandoverinformation

Provides a list and a chartthat indicate the inter-RAThandover information atdifferent time

Handover monitoring: TheInter-RAT HO Reportsheet provides the variationtendency of the handoversuccess rate in a week.

Traffic List and chartof trafficinformation

Provides a list and a chartthat indicate the CS traffic,PS interactive traffic, and PSbackground traffic atdifferent time

Traffic monitoring: TheTraffic sheet provides thevariation tendency of theaverage traffic and busy-hour traffic in a week.

Evaluation and AnalysisThe evaluation of the KPIs in the KPI sheet is the same as that in the daily report. For details,refer to 4.2.1 Daily Report.

The other sheets provide the variation tendency of each KPI in a week. If the KPIs are degraded,refer to 4.2.1 Daily Report for handling suggestions to optimize the network.

4.2.3 Monthly ReportMonthly reports include the KPIs and the variation tendency of each KPI in a month.

The functions and contents of the monthly report are the same as those of the weekly report. Fordetails, refer to 4.2.2 Weekly Report.



4-9

5 Introduction to RAN KPIs

RAN Key Performance Indicators (KPIs) reflect the performance of the network. Throughmonitoring the variations of KPIs, you can detect the network performance problems as soon aspossible.

Attributes of CountersEach counter has the following three attributes:

l Measurement object:indicating the signaling procedure or algorithm, such as the RadioResource Control (RRC) connection setup and Radio Access Bearer (RAB) release.

l Measurement set:indicating the measurement range, such as the RNC or a cell.

l Measured service:indicating the measured service type, such as the CS, PS, and AdaptiveMulti-Rate (AMR) services.

Classification of KPIs by Measurement SetFigure 5-1 shows the measurement sets. RNC counters and cell counters are of ultimateimportance. Most KPIs are calculated on the basis of these counters.

l RNC overall performance measurement: used to measure the overall performance of theRNC through measuring the basic signaling procedures

l Cell measurement: used to measure the performance of each cell

RANPerformance Management Guide 5 Introduction to RAN KPIs


5-1

Figure 5-1 Classification of KPIs by measurement set

Classification of KPIs by Measurement Mode

According to the measurement mode, KPIs can be classified into four types: Original, Inner-Calculate, Calculate, and Custom.

Original and Inner-Calculate KPIs are reported by the RNC.

l Original KPIs: original KPIs obtained in the RNC

l Inner-Calculate KPIs: KPIs calculated according to original RNC KPIs

Calculate and Custom KPIs are calculated by Nastar on the basis of Original and Inner-CalculateKPIs reported by the RNC. Calculate and Custom KPIs extend the application of KPIs.

l The formulas of Calculate KPIs cannot be modified.

l The formulas of Custom KPIs can be modified.

Classification of KPIs by Indicated Performance

KPIs that are commonly used in routine monitoring can be classified by indicated networkperformance. KPIs are classified into the following types:

l Accessibility KPIs

l Availability KPIs

l Coverage KPIs

l Mobility KPIs

l Retainability KPIs

5 Introduction to RAN KPIsRAN



Issue 01 (2009-03-25)

l Service integrity KPIs

l Traffic KPIs

Collection of KPIsKPIs can be viewed and analyzed on the M2000. In addition, KPIs can be exported from theM2000 in different file types.l Exported KPIs can be saved as .txt, .html, .csv, or .xls files when displayed in a table.

l Exported KPIs are saved as .jpg files when displayed in a line chart or a bar chart.

For detailed information on KPIs, refer to RAN Key Performance Indicators Reference.

RANPerformance Management Guide 5 Introduction to RAN KPIs


5-3

6 RAN Call History Records Reference

Call History Records (CHRs) are provided by NEs to meet the requirements of pre-defined callsignaling messages.

Process of CHR CollectionThe NEs can provide CHRs of failed calls or all CHRs. Figure 6-1 shows the process of CHRcollection.

Figure 6-1 Process of CHR collection

The NEs in the 3G CN and RAN can export CHRs of failed calls or all CHRs to the externaldata collection, storage, and management system in real time, so as to meet analysisrequirements. The RNC can generate CHRs but no bills. Currently, the RNC can provide onlyCHRs of failed calls rather than all CHRs.

RANPerformance Management Guide 6 RAN Call History Records Reference


6-1

CHR ApplicationsCHRs help to locate failed calls by recording the default information and help to improve themaintainability and serviceability by recording the internal processing information in detail.

CHRs can be used for:

l Fault location and handling

l User complaint and handling

l Service analysis

l Network quality analysis

l UE KPI analysis

CHR TypesAccording to contents and recording triggering modes, CHRs are classified into the followingtypes:l Default CHR

The default CHRs record unexpected events upon occurrence during calls.l Performance CHR (PCHR)

PCHRs record the associated performance data of all calls, including both normal andabnormal calls, during the time from RRC connection setup to RRC connection release.

Unless otherwise stated, the CHR in performance application refers to the PCHR.

6 RAN Call History Records ReferenceRAN



Issue 01 (2009-03-25)

Date post:	30-Nov-2015
Category:	Documents
Upload:	jarropedro
View:	72 times
Download:	0 times

RAN Performance Management Guide(RAN11.0_01)

Documents