Nastar Network Optimization User Guide (UMTS) - (V600R009 - 01) (PDF) - en

Nastar
V600R009
Network Optimization User Guide

(UMTS)
Issue
01
Date
2011-08-15
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2011-08-15)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Nastar
Network Optimization User Guide (UMTS)
About This Document
About This Document

Purpose
The Nastar provides network optimization function. The network optimization function helps
you perform various UMTS theme analyses on the Nastar, including coverage analysis, intrafrequency analysis, cell performance analysis, pilot pollution analysis, uplink interference
analysis, UMTS/GSM neighboring cell analysis, VIP analysis, complaint analysis support,
terminal analysis, and service geographic analysis. These analysis functions help to quickly
locate network problems. This section mainly describes how to perform various theme analysis
functions on the UMTS network.
Product Version
The products described in this guide are as follows:
Product Name
Product Version
Nastar
V600R009
Intended Audience
This document is intended for network optimization engineers.
Change History
Issue 01 (2011-08-15)
This is the first formal release.
Issue Draft C (2011-06-30)

This is the third release for the beta test.
Issue Draft B (2011-05-31)

This is the second release for the beta test.
Issue 01 (2011-08-15)

ii
Nastar
About This Document
Issue Draft A (2011-04-30)

This is the first release for the beta test.
Organization
1 Overview
The Nastar is deployed on the EMS side of an operator's network. The Nastar collects required
analysis data from NEs through the EMS data center, and provides theme analysis for network
optimization.
2 Configuring OSSs and NE Information
Before enabling the Nastar to collect data from an OSS, you must configure the OSS and NE
information. After you configure information including the IP address of the OSS and software
version, the Nastar obtains the NE list managed by the OSS and analyzes the NEs in the NE list
based on the configured OSS information.
3 Collecting Basic Data
The basic data that needs to be collected by the Nastar contains configuration data, engineering
parameters, and map data. The Nastar collects and imports basic data into the database so that
you can perform various theme analysis tasks based on other analysis data such as VIP analysis
data and uplink interference analysis data to locate network problems.
4 Subscribing to UMTS Data Sources
This section describes how to enable data source switches by using the data source subscription
function before performing various UMTS theme analysis functions. After required data source
switches are enabled, the Nastar can collect required data from network elements (NEs). This
function is the prerequisite for all Nastar theme analysis functions.
5 UMTS Coverage Analysis
The UMTS coverage analysis function enables you to obtain UMTS coverage analysis data,
create UMTS coverage analysis tasks, query UMTS coverage analysis results, and export UMTS
coverage analysis reports from the Nastar. The Nastar analyzes the measurement reports (MRs)
sent by UEs and displays the coverage status, signal quality, and subscriber distribution of a
measurement cell. This function helps to locate wireless network problems such as weak
coverage, cross coverage, and poor service quality.
6 UMTS Intra-Frequency Neighboring Cell Analysis
The UMTS intra-frequency neighboring cell analysis function enables you to obtain UMTS
intra-frequency neighboring cell analysis data, create UMTS intra-frequency neighboring cell
analysis tasks, query UMTS intra-frequency neighboring cell analysis results and possible
UMTS neighboring cell analysis results, and export UMTS intra-frequency neighboring cell
analysis reports from the Nastar. Based on configuration data and engineering parameters, the
Nastar aggregates and analyzes measurement reports (MRs) and events reported by UEs to check
missing and redundant neighboring cell configuration of measurement cells and neighboring
cells whose priorities need to be adjusted. By using this function, the Nastar directly displays
the required information, helping you solve network quality problems that are caused by
redundant or missing neighboring cell configuration or improper configuration of neighboring
cell priorities.
Issue 01 (2011-08-15)

iii
Nastar
About This Document
7 UMTS/GSM Neighboring Cell Analysis

The UMTS/GSM neighboring cell analysis function enables you to obtain UMTS/GSM
neighboring cell analysis data, create UMTS/GSM neighboring cell analysis tasks, query UMTS/
GSM neighboring cell analysis results, and export UMTS/GSM neighboring cell analysis results
from the Nastar. The Nastar allows you to check for redundant and missing inter-RAT
neighboring cells. This function helps to solve the network quality problems caused by redundant
and missing neighboring cell configuration.
8 UMTS Pilot Pollution Analysis
The UMTS pilot pollution analysis function enables you to obtain UMTS pilot pollution analysis
data, create UMTS pilot pollution analysis tasks, query UMTS pilot pollution analysis results,
and export UMTS pilot pollution analysis reports from the Nastar. By analyzing subscriber calls,
the Nastar identifies cells where pilot pollution exists, cells that cause interference, and severity
of cell pollution. The Nastar also displays the analysis results on a map so that you can learn the
detailed situation of pilot pollution. This function reduces the drive test (DT) time and improves
the accuracy of problem location.
9 UMTS Uplink Interference Analysis
The UMTS uplink interference analysis function enables you to obtain UMTS uplink
interference analysis data, create UMTS uplink interference analysis tasks, and query UMTS
uplink interference analysis reports. With the uplink interference analysis function, the Nastar
analyzes Received Total Wideband Power(RTWP) data reported by NodeBs and preliminarily
locates NodeBs that are affected by interference by ranking NodeBs based on their interference.
Then, you can view the charts showing the overall RTWP trends of the selected cells to determine
whether the average interference intensity of main and diversity antennas is proper and judge
the interference characteristics. You can also view the distribution chart of main and diversity
difference to determine whether the main and diversity antennas are connected correctly.
10 UMTS Terminal Analysis
This section describes the UMTS terminal analysis tasks, including the management of terminal
analysis tasks and the query and export of terminal analysis reports. The system analyzes the
KPIs in the call records of terminal users. This function helps operators identify the terminals
with poor performance in the UMTS network, therefore encouraging terminal manufacturers to
improve the terminals with poor performance and guide subscribers to purchase terminals with
good performance. In this case, subscribers can obtain stable services, and the subscriber
satisfaction can be improved.
11 UMTS VIP Analysis
The UMTS VIP analysis function enables you to obtain UMTS VIP analysis data, create UMTS
VIP analysis tasks, query UMTS VIP analysis results, and export UMTS VIP analysis reports
from the Nastar. By monitoring the KPIs related to the quality of service (QoS) of VIP
subscribers, the Nastar helps you identify and solve the network problems that may cause VIP
complaints so that the service quality of VIP subscribers is ensured and the satisfaction of VIP
subscribers is improved.
12 UMTS Complaint Analysis Support
The UMTS complaint analysis support function enables you to create UMTS complaint analysis
support tasks, query UMTS complaint analysis support results, and export UMTS complaint
analysis support reports from the Nastar. After receiving a complaint, the Nastar can quickly
locate call history records (CHRs) that are related to a problem cell involved in the complaint
based on the known problem cell and International Mobile Subscriber Identity (IMSI) of the
Issue 01 (2011-08-15)

iv
Nastar
About This Document
complaint subscriber. By analyzing causes of access failure, handover failure, and abnormal call
drop, the Nastar helps you locate and solve problems. This function improves the efficiency of
complaint handling and increases the subscriber satisfaction.
13 UMTS Cell Performance Analysis
The UMTS cell performance analysis function enables you to obtain UMTS cell performance
analysis data, create UMTS cell performance analysis tasks, query UMTS cell performance
analysis results, and export UMTS cell performance analysis reports from the Nastar. You can
learn the actual causes of abnormal calls in problem cells by querying abnormal call data. This
function helps to improve the service quality and subscriber satisfaction.
14 UMTS Service Geographic Analysis
UMTS service geographic analysis involves obtaining UMTS service geographic analysis data,
creating a UMTS service geographic analysis task, viewing the UMTS service geographic
analysis result, and exporting a UMTS service geographic analysis report. The Nastar displays
the relevant information on the map based on the data collected for the entire network to show
the distribution of network coverage, traffic, and abnormal events in an intuitive and
comprehensive manner.
15 GSM/UMTS Complaint Analysis Support
The GSM/UMTS complaint analysis support function helps operators handle subscriber
complaints from GSM and UMTS networks at the same time, which effectively reduces
operation costs. The GSM/UMTS complaint analysis support function enables users to manage
complaint analysis support tasks, and query and export complaint analysis support reports. After
receiving a subscriber complaint, the Nastar quickly identifies call records related to the
complaint subscriber in a problem cell. By analyzing call access and release information and
service quality information in call records, the Nastar helps locate and solve complaint problems.
This improves the efficiency of handling complaints and increases subscriber satisfaction.
Conventions
Symbol 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 not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
Issue 01 (2011-08-15)

Nastar
About This Document
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 in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
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 by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical 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.
Issue 01 (2011-08-15)
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.

vi
Nastar
About This Document
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.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 01 (2011-08-15)
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.

vii
Nastar
Contents
Contents
About This Document.....................................................................................................................ii
1 Overview.........................................................................................................................................1
1.1 Position of the Nastar on the Network................................................................................................................2
1.2 Analysis Data Sources (UMTS).........................................................................................................................3
1.3 Network Optimization Process...........................................................................................................................6
2 Configuring OSSs and NE Information....................................................................................8

2.1 Basic Knowledge of OSS Management.............................................................................................................9
2.2 Creating OSSs and the Managed NEs................................................................................................................9
2.3 Creating Custom NE Groups............................................................................................................................11
2.4 Reference for the OSS Management GUI........................................................................................................14
2.4.1 Interface Description: OSS Management................................................................................................14
2.4.2 Parameters for Setting the Object Attributes of OSS Management........................................................15
2.4.3 Parameters for Creating and Modifying Custom NE Groups..................................................................18
3 Collecting Basic Data..................................................................................................................19

3.1 Introduction to Basic UMTS Data....................................................................................................................21
3.2 Collecting Configuration Data..........................................................................................................................22
3.3 Importing Configuration Data..........................................................................................................................24
3.4 Importing Engineering Parameters...................................................................................................................25
3.5 Checking Engineering Parameters and Configuration Data.............................................................................28
3.6 GIS Management..............................................................................................................................................30
3.6.1 Viewing Analysis Results by Using the Google Earth............................................................................30
3.6.2 Querying Analysis Results Through the GIS Window...........................................................................32
3.7 Managing the GIS Window..............................................................................................................................33
3.7.1 Importing a Map......................................................................................................................................33
3.7.2 Converting the Map File Format.............................................................................................................34
3.7.3 Loading Site Information.........................................................................................................................35
3.7.4 Filtering Cells..........................................................................................................................................36
3.7.5 Searching Cells........................................................................................................................................37
3.7.6 Moving/Zooming In On/Zooming Out On/Refreshing/Fully Displaying a Map....................................38
3.7.7 Measuring Distance on the Map..............................................................................................................38
3.7.8 Saving the Map Display Effect................................................................................................................39
3.8 Reference to the Basic Data Collection Interface.............................................................................................39
Issue 01 (2011-08-15)

viii
Nastar
Contents
3.8.1 Interface Description: GIS.......................................................................................................................39

3.8.2 Parameters for Creating or Modifying a Data Collection Task...............................................................40
4 Subscribing to UMTS Data Sources........................................................................................44

4.1 Basic Knowledge of UMTS Data Source Subscription....................................................................................45
4.2 Setting Data Source Switches (As an Administrator User)..............................................................................48
4.3 Querying the Data Source Switch Status on the Live Network (As a Common User)....................................50
4.4 GUI Description: Subscribing to UMTS Data Source.....................................................................................51
5 UMTS Coverage Analysis..........................................................................................................56

5.1 Basic Knowledge of UMTS Coverage Analysis..............................................................................................58
5.2 UMTS Coverage Analysis Process...................................................................................................................58
5.3 Obtaining UMTS Coverage Analysis Data......................................................................................................60
5.3.1 Creating UMTS E2E Tasks.....................................................................................................................60
5.3.2 Creating a Data Import Task...................................................................................................................63
5.3.3 Checking the Integrity of Analysis Data.................................................................................................67
5.4 Creating UMTS Coverage Analysis Tasks.......................................................................................................70
5.5 Querying UMTS Coverage Analysis Results...................................................................................................73
5.6 Exporting UMTS Coverage Analysis Reports.................................................................................................74
5.7 Technical Specifications for UMTS Coverage Analysis..................................................................................76
5.8 Reference for the UMTS Coverage Analysis GUI...........................................................................................76
5.8.1 Interface for UMTS Coverage Analysis..................................................................................................76
5.8.2 Parameters for Creating UMTS E2E Tasks.............................................................................................79
5.8.3 Parameters for Creating and Modifying UMTS Coverage Analysis Tasks............................................81
5.8.4 Parameters for Querying UMTS Coverage Analysis Results.................................................................83
6 UMTS Intra-Frequency Neighboring Cell Analysis............................................................84

6.1 Basic Knowledge of UMTS Intra-Frequency Neighboring Cell Analysis.......................................................86
6.1.1 UMTS Intra-Frequency Neighboring Cell Analysis...............................................................................86
6.1.2 Algorithms for UMTS Intra-Frequency Neighboring Cell Analysis.......................................................87
6.2 UMTS Intra-Frequency Neighboring Cell Analysis Process...........................................................................88
6.3 Obtaining UMTS Intra-Frequency Neighboring Cell Analysis Data...............................................................91
6.3.1 Creating UMTS E2E Tasks.....................................................................................................................91
6.3.2 Creating a Data Import Task...................................................................................................................93
6.3.3 Checking the Integrity of Analysis Data.................................................................................................98
6.4 Creating UMTS Intra-Frequency Neighboring Cell Analysis Tasks.............................................................101
6.5 Querying UMTS Intra-Frequency Neighboring Cell Analysis Results..........................................................103
6.6 Querying Possible UMTS Neighboring Cell Analysis Results......................................................................104
6.7 Exporting UMTS Intra-Frequency Neighboring Cell Analysis Reports........................................................105
6.8 Exporting Possible Neighboring UMTS Cell Analysis Reports....................................................................107
6.9 Technical Specifications for UMTS Intra-frequency Neighboring Cell Analysis.........................................108
6.10 Reference for the UMTS Intra-Frequency Neighboring Cell Analysis GUI................................................108
6.10.1 Interface Description: UMTS Intra-Frequency Neighboring-Cell Analysis.......................................108
6.10.2 Parameters for Creating UMTS E2E Tasks.........................................................................................110
Issue 01 (2011-08-15)

ix
Nastar
Contents
6.10.3 Parameters for Creating and Modifying UMTS Intra-Frequency Neighboring Cell Analysis Tasks
........................................................................................................................................................................111
6.10.4 Parameters for Querying UMTS Intra-frequency Neighboring Cell Analysis Results.......................113
6.10.5 Parameters for Querying UMTS Possible Neighboring Cell Analysis Results...................................116
7 UMTS/GSM Neighboring Cell Analysis..............................................................................120

7.1 Basic Knowledge of UMTS/GSM Neighboring Cell Analysis......................................................................122
7.1.1 UMTS/GSM Neighboring Cell Analysis Function...............................................................................122
7.1.2 Algorithms for UMTS/GSM Neighboring Cell Analysis......................................................................123
7.2 UMTS/GSM Neighboring Cell Analysis Process..........................................................................................123
7.3 Obtaining UMTS/GSM Neighboring Cell Analysis Data..............................................................................125
7.3.1 Creating UMTS E2E Tasks...................................................................................................................126
7.3.2 Creating a Data Import Task.................................................................................................................128
7.3.3 Checking the Integrity of Analysis Data...............................................................................................132
7.4 Creating UMTS/GSM Neighboring Cell Analysis Tasks..............................................................................135
7.5 Querying UMTS/GSM Neighboring Cell Analysis Results...........................................................................138
7.6 Querying Possible UMTS/GSM Neighboring Cell Analysis Results............................................................139
7.7 Exporting UMTS/GSM Neighboring Cell Analysis Reports.........................................................................140
7.8 Exporting Possible Neighboring UMTS/GSM Cell Analysis Reports...........................................................142
7.9 Technical Specifications for UMTS/GSM Neighboring Cell Analysis.........................................................143
7.10 Reference to the Neighboring UMTS/GSM Cell Analysis Interface...........................................................143
7.10.1 Interface Description: UMTS/GSM Neighboring Cell Analysis........................................................143
7.10.2 Interface Description: Possible Neighboring UMTS/GSM Cell Analysis..........................................144
7.10.4 Parameters for Creating and Modifying Neighboring UMTS/GSM Cell Analysis Tasks..................147
7.10.5 Parameters for Querying UMTS/GSM Neighboring Cell Results......................................................149
7.10.6 Parameters for Querying UMTS/GSM Possible Neighboring Cell Results........................................154
8 UMTS Pilot Pollution Analysis..............................................................................................159

8.1 Basic Knowledge of UMTS Pilot Pollution Analysis....................................................................................161
8.2 UMTS Pilot Pollution Analysis Process.........................................................................................................161
8.3 Obtaining UMTS Pilot Pollution Analysis Data............................................................................................163
8.4 Creating UMTS Pilot Pollution Analysis Tasks.............................................................................................173
8.5 Querying UMTS Pilot Pollution Analysis Results.........................................................................................175
8.6 Exporting UMTS Pilot Pollution Analysis Reports.......................................................................................176
8.7 Technical Specifications for UMTS Pilot Pollution Analysis........................................................................176
8.8 Reference to the UMTS Pilot Pollution Analysis Interface...........................................................................177
8.8.1 Interface Description: UMTS Pilot Pollution Analysis.........................................................................177
8.8.2 Parameters for Creating UMTS E2E Tasks...........................................................................................179
8.8.3 Parameters for Creating and Modifying UMTS Pilot Pollution Analysis Tasks..................................180
8.8.4 Parameters for Querying UMTS Pilot Pollution Analysis Results........................................................182
Issue 01 (2011-08-15)

Nastar
Contents
9 UMTS Uplink Interference Analysis.....................................................................................186

9.1 Basic Knowledge of UMTS Uplink Interference Analysis............................................................................188
9.2 UMTS Uplink Interference Analysis Process................................................................................................188
9.3 Obtaining UMTS Uplink Interference Analysis Data....................................................................................190
9.4 Creating UMTS Uplink Interference Analysis Tasks.....................................................................................200
9.5 Querying UMTS Uplink Interference Analysis Results.................................................................................202
9.6 Technical Specifications for UMTS Uplink Interference Analysis................................................................203
9.7 Reference for the UMTS Uplink Interference Analysis GUI.........................................................................204
9.7.1 Interface for UMTS Uplink Interference Analysis................................................................................204
9.7.2 Parameters for Creating UMTS E2E Tasks...........................................................................................205
9.7.3 Parameters for Creating or Modifying a UMTS Uplink Interference Analysis Task............................207
9.7.4 Parameters for Querying UMTS Uplink Interference Analysis Results...............................................208
10 UMTS Terminal Analysis......................................................................................................210

10.1 Basic Knowledge of UMTS Terminal Analysis...........................................................................................212
10.2 UMTS Terminal Analysis Process...............................................................................................................212
10.3 Managing Terminal Information..................................................................................................................214
10.4 Obtaining UMTS Terminal Analysis Data...................................................................................................219
10.4.1 Creating UMTS E2E Tasks.................................................................................................................219
10.4.2 Creating a Data Import Task...............................................................................................................221
10.4.3 Checking the Integrity of Analysis Data.............................................................................................226
10.5 Creating a UMTS Terminal Analysis Task..................................................................................................229
10.6 Querying UMTS Terminal Analysis Results................................................................................................230
10.7 Exporting UMTS Terminal Analysis Reports..............................................................................................231
10.8 Technical Specifications for UMTS Terminal Analysis..............................................................................232
10.9 Reference to the UMTS Terminal Analysis Interface..................................................................................233
10.9.1 Interface Description: UMTS Terminal Analysis................................................................................233
10.9.2 Parameters for Creating and Modifying the Terminal Type...............................................................235
10.9.4 Parameters for Creating or Modifying UMTS Terminal Analysis Tasks............................................238
10.9.5 Parameters for Querying UMTS Terminal Analysis Results..............................................................239
11 UMTS VIP Analysis................................................................................................................247

11.1 Basic Knowledge of UMTS VIP Analysis...................................................................................................249
11.1.1 UMTS VIP Analysis Function............................................................................................................249
11.1.2 Authority Policies for UMTS VIP Analysis........................................................................................250
11.2 UMTS VIP Analysis Process.......................................................................................................................255
11.3 Managing UMTS VIP Groups......................................................................................................................257
11.4 Obtaining UMTS VIP Analysis Data...........................................................................................................260
Issue 01 (2011-08-15)

xi
Nastar
Contents
11.4.3 Checking the Integrity of VIP Analysis Data......................................................................................267

11.5 Setting a Mailbox for Sending Analysis Reports.........................................................................................268
11.6 Creating UMTS VIP Analysis Tasks............................................................................................................268
11.7 Querying UMTS VIP Analysis Results........................................................................................................271
11.8 Querying UMTS VIP Trend Analysis Results.............................................................................................273
11.9 Exporting UMTS VIP Analysis Reports......................................................................................................276
11.10 Technical Specifications for UMTS VIP Analysis.....................................................................................277
11.11 Reference to the UMTS VIP Analysis Interface........................................................................................277
11.11.1 Interface Description: UMTS VIP Analysis......................................................................................277
11.11.2 Interface for UMTS VIP Trend Analysis..........................................................................................279
11.11.3 Parameters for Creating and Modifying UMTS VIP Subscribers/VIP Groups.................................281
11.11.4 Parameters for Creating UMTS E2E Tasks.......................................................................................282
11.11.5 Parameters for Creating and Modifying UMTS VIP Analysis Tasks...............................................284
11.11.6 Parameters for Querying UMTS VIP Analysis Results....................................................................287
11.11.7 Parameters for Setting the Mailbox of Analysis Results...................................................................300
12 UMTS Complaint Analysis Support...................................................................................302

12.1 Basic Knowledge of UMTS Complaint Analysis Support...........................................................................304
12.1.1 UMTS Complaint Analysis Support Function....................................................................................304
12.1.2 Authority Policies for UMTS Complaint Analysis Support................................................................305
12.2 UMTS Complaint Analysis Support Process...............................................................................................308
12.3 Creating UMTS Complaint Analysis Support Tasks...................................................................................309
12.4 Querying UMTS Complaint Analysis Support Results................................................................................312
12.5 Exporting UMTS Complaint Analysis Support Reports..............................................................................314
12.6 Technical Specifications for UMTS Complaint Analysis Support..............................................................315
12.7 Reference to the UMTS Complaint Analysis Support Interface..................................................................315
12.7.1 Interface Description: UMTS Complaint Analysis Support................................................................315
12.7.2 Interface for Signaling Procedure Before Call Release and Measurement Information in the UMTS
Complaint Analysis Support Window............................................................................................................317
12.7.3 Parameters for Creating and Modifying UMTS Complaint Analysis Support Tasks.........................321
12.7.4 Parameters for Querying UMTS Complaint Analysis Support Results..............................................322
13 UMTS Cell Performance Analysis.......................................................................................343

13.1 Basic Knowledge of UMTS Cell Performance Analysis.............................................................................345
13.2 UMTS Cell Performance Analysis Process..................................................................................................349
13.3 Obtaining UMTS Cell Performance Analysis Data.....................................................................................351
13.4 Creating a UMTS Cell Performance Analysis Task.....................................................................................361
13.5 Querying UMTS Cell Performance Analysis Results..................................................................................363
13.6 Exporting UMTS Cell Performance Analysis Reports.................................................................................365
13.7 Technical Specifications for UMTS Cell Performance Analysis.................................................................365
13.8 Reference to the UMTS Cell Performance Analysis Interface.....................................................................366
Issue 01 (2011-08-15)

xii
Nastar
Contents
13.8.1 Interface Description: UMTS Cell Performance Analysis..................................................................366

13.8.3 Parameters for Creating or Modifying UMTS Cell Performance Analysis Tasks..............................370
13.8.4 Parameters for Querying UMTS Cell Performance Analysis Results.................................................371
14 UMTS Service Geographic Analysis...................................................................................376

14.1 Basic Knowledge of UMTS Service Geographic Analysis..........................................................................378
14.2 UMTS Service Geographic Analysis Process..............................................................................................378
14.3 Obtaining UMTS Service Geographic Analysis Data..................................................................................380
14.3.1 Import Property Matrix........................................................................................................................380
14.4 Creating UMTS Service Geographic Analysis Tasks..................................................................................391
14.5 Querying UMTS Service Geographic Analysis Results...............................................................................394
14.6 Technical Specifications for UMTS Service Geographic Observation........................................................396
14.7 Reference to the UMTS Service Geographic Analysis Interface.................................................................397
14.7.1 Interface Description: UMTS Service Geographic Analysis...............................................................397
14.7.3 Parameters for Creating and Modifying UMTS Service Geographic Analysis Tasks........................400
14.7.4 Parameters for Querying UMTS Service Geographic Analysis Results.............................................402
15 GSM/UMTS Complaint Analysis Support.........................................................................404

15.1 Basic Knowledge of GSM/UMTS Complaint Analysis Support.................................................................406
15.2 Process of GSM/UMTS Complaint Analysis Support.................................................................................407
15.3 Creating a GSM/UMTS Complaint Analysis Support Task........................................................................408
15.4 Querying GSM/UMTS Complaint Analysis Support Results......................................................................412
15.5 Exporting GSM/UMTS Complaint Analysis Support Reports....................................................................414
15.6 Technical Specifications for GSM/UMTS Complaint Analysis Support.....................................................416
15.7 Reference to the GSM/UMTS Complaint Analysis Support Interface........................................................417
15.7.1 Parameters for Creating and Modifying GSM/UMTS Complaint Analysis Support Tasks...............417
15.7.2 Parameters for Querying GSM/UMTS Complaint Analysis Support Results....................................418
Issue 01 (2011-08-15)

xiii
Nastar
1 Overview
Overview
About This Chapter

The Nastar is deployed on the EMS side of an operator's network. The Nastar collects required
analysis data from NEs through the EMS data center, and provides theme analysis for network
optimization.
1.1 Position of the Nastar on the Network
The Nastar is deployed on a distributed client/server (C/S) network and is connected to an
element management system (EMS).
1.2 Analysis Data Sources (UMTS)
The Nastar mainly uses the following three types of data during UMTS network analysis: UMTS
configuration data, UMTS engineering parameters, and data related to Nastar analysis.
1.3 Network Optimization Process
The optimization process of the Nastar consists of collection and check of basic data, network
evaluation, further optimization of each theme, and evaluation of optimization effect. All the
operations on the network must be recorded in details.
Issue 01 (2011-08-15)

Nastar
1 Overview
1.1 Position of the Nastar on the Network

The Nastar is deployed on a distributed client/server (C/S) network and is connected to an
element management system (EMS).
Figure 1-1 shows the position of the Nastar on the network.
Figure 1-1 Position of the Nastar on the network
The communication between different units on the network is based on the TCP/IP protocol.
The Nastar server and the EMS such as the M2000 must be in the same Local Area Network
(LAN), and the IP addresses of the Nastar server and the EMS must be on the same network
segment.
Table 1-1 describes the function of each unit.
Table 1-1 Description of the function units in the Nastar
Issue 01 (2011-08-15)
Functional Unit
Function Description
Nastar
The Nastar is one of the multi-user telecommunication platform

developed by Huawei. It helps you to perform performance analysis
for the radio network and perform network problem troubleshooting.

Nastar
1 Overview
Functional Unit
Function Description
SAU
SAU is short for Service Aware Unit (SAU).

The main functions of the SAU are as follows:
l Collecting raw data from BTSs
l Preprocessing raw data and saving the preprocessed data
l Uploading the preprocessed data
In a GSM, UMTS, or CDMA network, an SAU must be configured
for the base station controller to preprocess the performance data
required by the Nastar.
In an LTE network, the SAU is deployed on the OSS side as a server.
The M2000, an element management system, is a centralized
management platform developed by Huawei. The M2000 uniformly
manages the NEs on a mobile network.
M2000
The M2000 is connected to the Nastar, and provides the Nastar with
performance data, configuration data, call history record (CHR)
processed data, and measurement report (MR) preprocessed data
through FTP.
Radio network
Multiple radio networks are supported, including GSM, UMTS,

CDMA, and LTE networks.
MME
Mobility Management Entity (MME) provides data analysis function

for the SAU on the LTE network.
1.2 Analysis Data Sources (UMTS)

The Nastar mainly uses the following three types of data during UMTS network analysis: UMTS
configuration data, UMTS engineering parameters, and data related to Nastar analysis.
Figure 1-2 shows the sources of the Nastar analysis data on the network.
Issue 01 (2011-08-15)

Nastar
1 Overview
Figure 1-2 Sources of the Nastar analysis data (UMTS)
Table 1-2 describes the sources of the Nastar analysis data.

Table 1-2 Sources of the Nastar analysis data (UMTS)
Analysis Data Source
Description
UMTS configuration data
Basic information for network optimization, used

for the Nastar to correctly retrieve data of each
cell from data sources.
UMTS engineering parameters
Basic information for network optimization,

including longitudes and altitudes of sites, and
azimuths and down tilt angles of antennas.
Used for displaying the analysis data
geographically.
Data related
to Nastar
analysis
Issue 01 (2011-08-15)
Measurem
ent report
(MR) data
UMTS
neighborin
g cell data
Obtained from the SAU and used for UMTS intrafrequency neighboring cell analysis.
UMTS
pilot
pollution
analysis
data
Obtained from the SAU and used for UMTS pilot

pollution analysis.

Nastar
1 Overview
Analysis Data Source

UMTS
coverage
data
Obtained from the SAU and used for UMTS

coverage analysis data.
UMTS/
GSM
neighborin
g cell
measureme
nt data
Obtained from the SAU and used for UMTS/

GSM neighboring cell analysis.
UMTS
service
geographic
analysis
data

service geographic analysis.
Received
Total
Wideband
Power
(RTWP)
data
UMTS
uplink
interferenc
e analysis
data
Obtained from the M2000 and used for UMTS

uplink interference analysis.
Call
History
Record
(CHR) data
UMTS VIP
analysis
data
Obtained from the SAU and used for UMTS VIP

analysis.
UMTS cell
performan
ce analysis
data
Obtained from the SAU and used for UMTS cell

performance analysis.
UMTS
complaint
analysis
support
data

complaint analysis support.
UMTS
service
geographic
analysis
data

UMTS
terminal
analysis
data

terminal analysis.
UMTS property matrix
Issue 01 (2011-08-15)
Description
Obtained from the network planning tools (such

as the GENEX U-Net) and used for UMTS

Nastar
1 Overview
1.3 Network Optimization Process

The optimization process of the Nastar consists of collection and check of basic data, network
evaluation, further optimization of each theme, and evaluation of optimization effect. All the
operations on the network must be recorded in details.
Figure 1-3 shows the process of optimizing the Nastar.
Figure 1-3 Process of optimizing the Nastar
Table 1-3 describes each phase.
Issue 01 (2011-08-15)

Nastar
1 Overview
Table 1-3 Description of each phase

Phase
Step
Description
Preparati
on
Collection and
check of basic data
Basic data includes engineering parameters, configuration

data, VIP cells, VIP users, areas involving user complaints,
users with complaints, and maps of related areas.
In addition to basic data, you must check the consistency
between configuration data and engineering parameters in
the whole network and the integrity and accuracy of
engineering parameters.
Network
evaluation
The purpose of network evaluation is to learn the quality of

the live network and main problematic cells and collect data
for future in-depth analysis of network quality during the
comparison of network quality at the network level.
You can use other tools such as PRS to monitor and evaluate
network KPIs.
Issue 01 (2011-08-15)
Optimiz
ation
Further
optimization of
each theme
Use various performance analysis functions of the Nastar to

perform further optimization of each theme. The
performance analysis functions of the Nastar includes RF
performance optimization such as coverage analysis and
subscriber-based performance optimization such as
complaint analysis support and VIP analysis.
Effect
evaluati
on phase
Evaluation of
optimization effect
Evaluate the effect of network optimization.

Nastar
Configuring OSSs and NE Information
About This Chapter

Before enabling the Nastar to collect data from an OSS, you must configure the OSS and NE
information. After you configure information including the IP address of the OSS and software
version, the Nastar obtains the NE list managed by the OSS and analyzes the NEs in the NE list
based on the configured OSS information.
2.1 Basic Knowledge of OSS Management
This section describes the basic knowledge about the Operations Support System (OSS)
management functions. You should grasp the basic knowledge before performing management
operations.
2.2 Creating OSSs and the Managed NEs
This section describes how to create OSSs. You can create an OSS to initialize the protocol of
the interface between the Nastar and the EMS device so that the Nastar accesses the EMS device
through the interface to obtain the required data. In addition, you can set NEs managed by the
OSS so that the Nastar collects required data from the selected NEs.
2.3 Creating Custom NE Groups
This section describes how to create custom NE groups. The Nastar client provides the functions
of creating, modifying, deleting, importing, and exporting custom NE groups. You can add
certain NEs to an NE group so that the performance analysis can be performed for all the NEs
in an NE group.
2.4 Reference for the OSS Management GUI
This section describes the parameters about the interface of OSS management and the parameters
for setting the object attributes of OSS management. You can refer to the description when
performing the relevant operations on the interface.
Issue 01 (2011-08-15)

Nastar
2.1 Basic Knowledge of OSS Management

This section describes the basic knowledge about the Operations Support System (OSS)
management functions. You should grasp the basic knowledge before performing management
operations.
In the OSS management, objects represent the physical or logical entities on the network. A
physical or logical entity, namely, an object, can be an OSS or an NE.
l
Operations Support System

The operations support system (OSS) defines network management devices that can be
connected with the Nastar. The Nastar collects the required data from a specified FTP server
according to the relevant attributes set in the OSS and saves the data as files in a specified
path on the Nastar server.
NE
NEs are used to identify network devices, such as BTS and BSC.NEs can be classified into
physical NEs and virtual NEs.
Physical NEs are actual telecommunication devices of Huawei on the network.
Virtual NEs are the NEs that actually do not exist or are telecommunications devices
of other vendors on the network.
The OSS management subsystem provides the basic functions for managing objects. The
subsystems such as centralized task management add objects to the GUI through the OSS
management subsystem.
The OSS management of the Nastar enables you to create and delete OSSs, view and modify
OSS attributes, and manage the information about NEs managed by the OSS.
2.2 Creating OSSs and the Managed NEs

This section describes how to create OSSs. You can create an OSS to initialize the protocol of
the interface between the Nastar and the EMS device so that the Nastar accesses the EMS device
through the interface to obtain the required data. In addition, you can set NEs managed by the
OSS so that the Nastar collects required data from the selected NEs.
Prerequisite
You have logged in to the Nastar client.
Procedure
Step 1 Create an OSS.
1.
Choose Maintenance > OSS Management. The OSS Management window is displayed.
2.
Click New OSS.
3.
Set OSS property parameters.
Issue 01 (2011-08-15)

Nastar
CAUTION
The parameters such as OSS Type, OSS User Name, OSS Password, and OSS Server
Port must be set correctly. Otherwise, the Nastar will fail to deliver E2E tasks and fail to
collect data.
4.
Set FTP server parameters.
CAUTION
The parameters such as FTP Server Ip, FTP Server Port, FTP User Name, FTP
Password, FTP transfer mode, and FTP Protocol must be set correctly. Otherwise, the
Nastar fails to collect data.
l When double Ethernet adapters are installed in the M2000, you must fill in Internal
Server IP.
l When the network mode of the M2000 is Multi-server load sharing system (SLS)/
ATAE Cluster, you must fill in Standby FTP Server IP.
5.
Click OK.
6.
If OSS Type is set to M2000 V200R008 or a later version and the M2000 is deployed in
the Multi-server load sharing system (SLS)/ATAE Cluster mode, perform the following
operations to configure slave servers.
The network scale is large when the M2000 in M2000 V200R008 or a later version is
deployed in SLS mode. Therefore, data required by the Nastar is distributed over different
servers. In this case, you need to create a master server and then create slave servers during
the creation of an OSS.
a.
Select a created OSS (serving as a master server) from the navigation tree in the left
pane, and then click Slave Server. The Slave Server dialog box is displayed.
b.
Click Add. The Slave Server Information dialog box is displayed.
c.
Set parameters of a slave server. Then, click OK.
d.
Repeat the preceding operations to set parameters of all slave servers. Then, click
Close.
Step 2 Set NEs managed by an OSS.

1.
Select an OSS node from the navigation tree in the left of the OSS Management window,
and then click NE Manager. The Ne Selector dialog box is displayed.
2.
Set NEs managed by the selected OSS.

The pane on the left lists the NEs that can be selected, and the pane on the right lists the
NEs that are already selected. An NE can only be listed in either of the two panes.
,
,
, and
to select NEs. A single arrow
l You can click
indicates that you can select one or multiple NEs. Double arrows indicate that you can
select all NEs.
l You can select multiple NEs by pressing Ctrl.
Issue 01 (2011-08-15)

10
Nastar
l You can select the update automatically node under an NE type in the left pane and
then click
to move all the NEs under the NE type to the right pane.
l If you click
to select an NE under an NE type from the right pane to the left
pane, the system remove the update automatically node under an NE type from the
right pane automatically.
l If update automatically is displayed under the selected NE type in the right pane, the
system automatically updates all NEs under the NE type every four hours according to
the actual network situation.
CAUTION
l The Nastar does not support the NEs whose names contain any of the following
characters: &, , or '. Therefore, do not select NEs whose names contain any of those
characters. Otherwise, Nastar analysis will fail.
l If an NE is not added to the right pane, the data of this NE cannot be collected to the
Nastar server.
3.
Click OK.
----End
Follow-up Procedure
Delete an existing OSS.
1.
Select an OSS node to be deleted from the navigation tree in the left of the OSS
Management window. Then, click Delete.
If data collection tasks have existed in the selected OSS, the systems prompts The OSS
has been used in these Data Collection task, please delete them first:, You should delete
the data collect tasks first before you delete the OSS.
2.
Click OK in the displayed dialog box.
2.3 Creating Custom NE Groups

This section describes how to create custom NE groups. The Nastar client provides the functions
of creating, modifying, deleting, importing, and exporting custom NE groups. You can add
certain NEs to an NE group so that the performance analysis can be performed for all the NEs
in an NE group.
Prerequisite
l
You are authorized to manage NE groups.
Context
Custom NE group files in .csv, .xls, and .xlsx formats are supported.
Issue 01 (2011-08-15)

11
Nastar
Procedure
Step 1 Double-click System Function > NE Group Management from the navigation tree in the
Analysis Task Management window. The NE Group Management window is displayed.
TIP
You can also choose System Function > NE Group Management from the navigation tree in the Analysis
Task Management window and right-click Open. The NE Group Management window is displayed.
Step 2 Create a custom NE group.

If you need to...
Then...
Create a custom NE group by adding a new NE group
Perform Step 3.
Create a custom NE group by importing an NE group file
Perform Step 4.
Step 3 Create a custom NE group by adding a new NE group.

1.
Click the *** NE Group tab. Click Create to open the Edit NE Group dialog box.
In the name of the tab page, *** indicates the network system such as GSM, CDMA, UMTS,
or LTE.
2.
Set the relevant parameters.

l The Nastar supports the function of searching for objects in the object navigation tree.
After you click an object in the navigation tree, you can press Ctrl+F to search for and
locate an object.
l For details about the parameters, see Parameters for Creating and Modifying Custom
NE Groups.
3.
Click OK.
Step 4 Create a custom NE group by importing an NE group file.

1.
Click the *** NE Group tab, and then click Import.

In the name of the tab page, *** indicates the network system such as GSM, CDMA, or
UMTS.
2.
In the displayed Open dialog box, select an edited NE group file, and then click Open.
If an NE group file in .xls format or .xlsx format is selected and the file contains multiple
sheets, a message is displayed for you to select the sheet to be imported.
NOTE
If multiple lines of remarks regarding an NE group are inconsistent in the edited NE group file, the
system displays the last line of remarks on the Note title bar of the NE Group Management window.
It is recommended that the remarks in different lines regarding an NE group be consistent when you
define NE group information.
3.
Click Open.
The Message indicates the quantities of the successful and unsuccessful imported NE
group.
4.
Click OK.
----End
Issue 01 (2011-08-15)

12
Nastar
Follow-up Procedure
In the NE Group Management window, click the *** NE Group tab, and then select an NE
group to view, modify, delete or export this NE group.
In the name of the tab page, *** indicates the network system such as GSM, CDMA, UMTS or
LTE.
If you need to...
Then...
Query and modify the

properties of a custom NE
group
1. Click Modify.
2. View the information about members of the custom NE
group.
If the relevant parameters need to be modified, perform 3
through 4.
3. Modify the relevant parameters.
The objects and remarks of an NE groups can be modified
but the name of an NE group cannot be modified.
For details about the parameters, see Parameters for
Creating and Modifying Custom NE Groups.
4. Click OK.
NOTE
If the NE group is used by other tasks, the modification does not
affect the ongoing tasks. If the NE group is used by a periodic
task, the related information is updated in the next period after the
modification.
TIP
When you need to modify the information about NE groups in batches,
you can export the NE group information, make modifications, and
then import the NE group information again.
Delete a custom NE group.
1. Click Delete.
2. Click OK in the displayed dialog box.
NOTE
If the NE group is used by other tasks, the modification does not
affect the ongoing tasks. If the NE group is used by a periodic
task, the related information is updated in the next period after the
modification.
Export a custom NE group
1. Click Export.
2. Set the file name and specify the save path and file type in
the displayed Save dialog box, and then click Save.
All the NE group information displayed on this tab page
can be exported.
NOTE
The function of exporting user-defined NE group is unavailable for
the LTE system.
Issue 01 (2011-08-15)

13
Nastar
2.4 Reference for the OSS Management GUI

This section describes the parameters about the interface of OSS management and the parameters
for setting the object attributes of OSS management. You can refer to the description when
performing the relevant operations on the interface.
2.4.1 Interface Description: OSS Management

This section describes the interface of OSS management. Before perform the relevant operations,
you need to familiarize yourself with the functions of each area on the interface.
Figure 2-1 shows the interface of OSS management. Table 2-1 describes the items in Figure
2-1.
Figure 2-1 Interface of OSS management
Table 2-1 Interface description: OSS management
Issue 01 (2011-08-15)
No.
Name
Description
(1)
Navigation tree
Indicates that the objects in the navigation tree

are sorted by OSS.

14
Nastar
No.
Name
Description
(2)
Toolbar
Provides the buttons for creating and deleting

OSSs, setting slave servers, managing NEs,
modifying the attributes of the created OSSs,
and so on.
(3)
Area of OSS attributes
Displays the details of the OSS that you select

in the navigation tree.
(4)
Area of FTP server

information
Displays the details of the FTP server

corresponding to the OSS that you select in the
navigation tree.
2.4.2 Parameters for Setting the Object Attributes of OSS

Management
This section describes the parameters for creating or modifying the objects of OSS management.
You can refer to the description when creating or modifying the objects of OSS management.
Parameters Related to the OSS Attributes

Parameter
Description
OSS Name
Indicates the name of an OSS to be created or modified.

Value range:
l A maximum of 60 characters
l The following characters are not allowed: ~ ! @ # $ % ^ & * +
=<>?
l Unique and cannot be null
l Case sensitive
OSS Type
Indicates the type of the interface between the EMS and the
Nastar.
Value range: M2000V200R006, M2000V200R008,
M2000V200R009, M2000V200R010 and M2000V200R011
When the Nastar collects data from the OSS, this interface defines
the relevant principles such as the path of the configuration data
files and performance data files in the OSS and the naming rules
of the files. Thus, the Nastar can collect the required files from the
path specified by the OSS and saves the files in the specified path
on the Nastar client.
Issue 01 (2011-08-15)

15
Nastar
Parameter
Description
OSS Network Mode
Set the network mode of the M2000.

l Single/High Availability (HA)
l Remote High Availability (RHA)
l Multi-server load sharing system (SLS)/ATAE Cluster
Optional. The default value is Single/High Availability (HA).
NOTE
If the network mode is Multi-server load sharing system (SLS)/ATAE
Cluster, you need to set the slave servers.
OSS User Name
Indicates the user name used to log in to the OSS server.

This parameter cannot be null.
OSS Password
Indicates the password used to log in to the OSS server.

OSS Server Port
Indicates the port number of the OSS server.

Description
It is the description of an OSS.

Value range:
=<>?
l Case sensitive
Parameters Related to the FTP Server

Parameter
Description
FTP Server IP
Indicates the IP address of the FTP server where the file to be

collected is located.
Standby FTP Server IP
Indicates the IP address of the standby server when the network

mode of the M2000 is Multi-server load sharing system (SLS)/
ATAE Cluster.
Internal Server IP
Indicates the internal IP address for communicating with the NEs.

If the M2000 configures the dual Ethernet adapters, this parameter
cannot be null.
FTP Server Port
Indicates the port number of the FTP server where the file to be
collected is located.
This parameter can be set to any integer from 1 to 65535. The
default value is 21.
Issue 01 (2011-08-15)

16
Nastar
Parameter
Description
FTP User Name
Indicates the user name used to log in to the FTP server.

Value range:
=<>?
l Case sensitive
Indicates the password used to log in to the FTP server.
FTP Password

FTP Transfer Mode
Indicates the transfer mode set for the FTP server. The parameter
value can be Passive Mode or Active Mode.
FTP Protocol
l SFTP: Indicates the encrypted FTP transfer, which requires the

support from the FTP server.
l FTP: Indicates the non-encrypted FTP transfer, which is a
general FTP mode.
Parameter Related to the slave server Attributes

Parameter
Description
FTP server IP
Indicates the IP address of the slave server in the M2000 SLS

system.
The value of this parameter cannot be null.
FTP server port
Indicates the FTP service port.

Value range: an integer from 0 to 65535. The default value is 21.
If the parameter value is null, the system uses 0 as the port number.
FTP user
Indicates the valid user name of the FTP service in the M2000 SLS
system.
Value range:
=<>?
l Case sensitive
FTP password
Issue 01 (2011-08-15)
Indicates the password of the FTP service in the M2000 SLS

system.

17
Nastar
2.4.3 Parameters for Creating and Modifying Custom NE Groups

This section describes the parameters for creating and modifying custom NE groups. You can
refer to the parameter description when creating and modifying the custom NE groups.
Parameter Description
Parameter
Description
NE Group Name
Indicates the name of the NE group, for example, Cell_1.

Value range:
l Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `:"<>?
l Unique and not null
l Case sensitive
NE Group Type
Indicates the type of the NE group.
(Only CDMA and LTE

network need to set the
parameter)
l CDMA network supports three NE group types, as follows:

CARRIER
CARRIER-1x
CARRIER-EVDO
l LTE network supports two NE group types, as follows:
eNodeB Group
NE Group
Remarks
Provides the description of an NE group.

Value range:
l Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `:"<>?
Issue 01 (2011-08-15)

18
Nastar
Collecting Basic Data
About This Chapter

The basic data that needs to be collected by the Nastar contains configuration data, engineering
parameters, and map data. The Nastar collects and imports basic data into the database so that
you can perform various theme analysis tasks based on other analysis data such as VIP analysis
data and uplink interference analysis data to locate network problems.
3.1 Introduction to Basic UMTS Data
This section describes the basic data required for UMTS network analysis. The basic data
contains engineering parameters, configuration data, and data in map files.
3.2 Collecting Configuration Data
This section describes how to collect configuration data on the Nastar. The Nastar automatically
and periodically obtains configuration data from a specified directory on the M2000 server and
saves the data on the Nastar server.
3.3 Importing Configuration Data
This section describes how to import configuration data. The Nastar automatically obtains
configuration data from a specified directory on the Nastar server periodically and then import
the data into the database. After you create a configuration data import task on the Nastar client,
the Nastar automatically imports the configuration data periodically based on the created import
task.
3.4 Importing Engineering Parameters
This section describes how to import engineering parameters. You can import engineering
parameters into the Nastar database to provide a reference for certain algorithms related to
3.5 Checking Engineering Parameters and Configuration Data
This section describes how to check engineering parameters and configuration data. Through
this function, you can check whether the existing engineering parameter data is consistent with
the configuration data. If the check result is inconsistent, you can enable the Nastar to
synchronize the engineering parameter data with the configuration data to ensure data
consistency.
3.6 GIS Management
The Nastar can geographically display the performance analysis results through either the
Geographic Information System (GIS) window or Google Earth. You can view the Nastar
analysis result directly on the map, thus facilitating the service analysis.
Issue 01 (2011-08-15)

19
Nastar
3.7 Managing the GIS Window

You can import the map files in .wor, .tab or .sxwu format and view the site information in the
GIS window by using the engineering parameters. In addition, you can perform the following
operations in the GIS window through the GIS toolbar, such as move/center/zoom in on/zoom
out on a map and measure the distance between two points on the map.
3.8 Reference to the Basic Data Collection Interface
This section describes the interface for collecting basic data on the Nastar and the relevant
parameters. You can refer to this section when you import configuration data, engineering
parameters, or maps.
Issue 01 (2011-08-15)

20
Nastar
3.1 Introduction to Basic UMTS Data

This section describes the basic data required for UMTS network analysis. The basic data
contains engineering parameters, configuration data, and data in map files.
Map Files
Map files contain the geographical information of the area to be analyzed. Currently, the Nastar
supports map files in .wor, .tab, and .sxwu formats. If the PC is connected to the Internet, you
can view analysis results on the Google Earth.
NOTE
You can convert the map files in .wor or .tab formats to the map files in .sxwu format through the Convert
Map function of the Nastar.
Configuration Data
Configuration data contains the basic information for network optimization, which is used for
the Nastar to correctly retrieve data of each cell from data sources. The Nastar can obtain
configuration data from the specified path on the M2000.
UMTS Engineering Parameters

Engineering parameters are the basic information required for network optimization, including
longitudes and altitudes of sites and antenna azimuth. Table 3-1 shows UMTS engineering
parameters supported by the Nastar.
Table 3-1 UMTS engineering parameters
Issue 01 (2011-08-15)
Parameter
Description
Value Range
Optional/
Mandatory
RNCID
Indicates the ID of an
RNC.
Integer
Mandatory
NodeBID
Indicates the ID of a
NodeB.
Integer
Mandatory
NodeB Name
Indicates the name of a

NodeB.
String
Mandatory
CellID
Indicates the ID of a cell.
Integer
Mandatory
Cell Name
Indicates the name of a

cell.
String
Mandatory
LAC
Indicates the Location

Area Code (LAC) of a
cell.
Integer
Mandatory
RAC
Indicates the Routing

Area Code (RAC) of a
cell.
l Integer
Mandatory
l Value range: 1 to
255

21
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
SAC
Indicates the service area

code of a cell.
l Integer
Mandatory
Uarfcn-Down
Link
Indicates the downlink

UARFCNs of a cell.
Integer
Mandatory
Uarfcn-Up
Link
Indicates the uplink

UARFCNs of a cell.
Integer
Optional
P-SC
Indicates the primary

scrambling code of a cell.
Integer
Mandatory
LONGITUD
E
Indicates the longitude

where a cell is located, for
example, 116.389722.
[-180.0,180.0]
Mandatory
LATITUDE
Indicates the latitude

where a cell is located, for
example, 39.952778.
[-90.0,90.0]
Mandatory
AZIMUTH
Indicates the azimuth of

an antenna.
[0,360]
Mandatory
Is Outdoor
Indicates whether the cell

is an outdoor cell.
l 0: No
Optional
Indicates whether the cell

is a directional cell.
l 0: No
Is Direct
l Value range: 1 to
65535
l 1: Yes
Optional
l 1: Yes
Other Data
l
To perform a VIP analysis task, you need to obtain VIP subscriber information, including
the information about VIP subscribers and the corresponding IMSIs.
To perform a complaint analysis support task, you also need to obtain the complaint
subscriber information, including the information about complaint subscribers and the
corresponding IMSIs or the information about the called subscribers and the corresponding
IMSIs.
To perform a service geographic analysis task, you also need to obtain the property matrix
information. Property matrix can be generated using a network planning simulation tool,
such as GENEX U-Net.
3.2 Collecting Configuration Data

This section describes how to collect configuration data on the Nastar. The Nastar automatically
and periodically obtains configuration data from a specified directory on the M2000 server and
saves the data on the Nastar server.
Issue 01 (2011-08-15)

22
Nastar
Prerequisite
l
The configuration data is generated on the M2000. For details, refers to the Collecting and
Importing Basic Data > Collecting and Importing Configuration Data > Collecting
and Importing Configuration Data (xml.gz Format) chapter in the Nastar
Commissioning Guide (HP).
A configuration data collection task is a user-defined scheduled task.
The configuration data collection task can be executed periodically or once. The unit of the
task execution period can be minutes, hours, days, weeks, or months.
Context
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Click New. The New Task dialog box is displayed.
TIP
You can choose Task Type > Data Collection > Data Collection from the navigation tree and then doubleclick Data Collection to open the New Task. By default, Task Type is set to Data Collection.
Step 3 Set the basic task information.

1.
In Task Name, type the name of the data collection task.
2.
Select Data Collection > Data Collection from Task Type.
3.
In Run Type, select Once or Period.
Step 4 Click Next to set the execution time of the task.

1.
Click
. In the displayed Date/Time Selection dialog box, select the start time.
NOTE
l Begin time must be later than the current server time.

l If Run Type is set to Once, the Begin Time parameter becomes invalid after you select Execute
Immediately. In addition, the task is performed immediately after being created.
2.
Perform corresponding operations based on task types, once or periodical.

If...
Then...
Run Type is set to Once.
Perform Step 5.
Run Type is set to Period.
a. Set the task execution period in Period

Setting.
NOTE
Performance data can be collected at an interval of
half an hour or one hour.
Step 5 Click Next. Then, set parameters in the Basic Information and Task Parameter areas.
1.
In the OSS Name drop-down list box, select the name of the OSS that the NE to be analyzed
belongs to.
2.
In the Data Query drop-down list box, select Config Data.
Issue 01 (2011-08-15)

23
Nastar
3.
Set the parameters in the Task Parameter area.

l After Collect All NE is selected, all NE nodes in the NE object navigation tree are
automatically selected. That is, data of all NEs will be periodically collected and saved
as a file in a specified path on the Nastar.
l After Collect By NE Type is selected, Filter NE automatically becomes unavailable.
If you select an NE type node in the NE object navigation tree, all NE nodes under the
selected NE type node will be automatically selected. That is, data of all NEs under the
selected NE type will be periodically collected and saved as a file in a specified path on
the Nastar.
l If Collect All NE and Collect By NE Type are not selected, you can type a keyword
of NE name in Filter NE to search for the required NE object nodes in the NE object
navigation tree. Alternatively, select certain NE object nodes directly in the NE object
navigation tree. Data of all the selected NEs will be periodically collected and saved as
a file in a specified path on the Nastar.
l Select Specify the time range and set Start time and End time to collect related data
from the M2000 periodically or once within a specified time period and save the data
to a specified path on the Nastar.
Step 6 Click Finish.

The new data collection task is displayed in the task list.
----End
3.3 Importing Configuration Data

This section describes how to import configuration data. The Nastar automatically obtains
configuration data from a specified directory on the Nastar server periodically and then import
the data into the database. After you create a configuration data import task on the Nastar client,
the Nastar automatically imports the configuration data periodically based on the created import
task.
Prerequisite
Context
l
A data import task is a user-defined scheduled task. The Nastar allows you to create only
one configuration data import task for each network system.
The configuration data import task can only be executed periodically. The unit of the task
execution period can be Hour, Day, Week, or Month.
Procedure
1.
In Task Name, enter the name of the scheduled task.
2.
Select a *** configuration data import task from Task Type.
Issue 01 (2011-08-15)

24
Nastar
In the name of a task type, *** refers to the network system such as GSM, UMTS, CDMA,
or LTE.
Step 4 Click Next to set the execution period of the task.
1.
Click
You can also set the start time in the Begin time area.
NOTE
Begin time must be later than the current server time.
2.
Set Execution Interval and Execution times.

The new task is displayed in the task list.
----End
Follow-up Procedure
After the task is created, you can query the status of the task in the task list of the Task
Management window. If the task status is Complete, you can query the imported configuration
data by performing the following operations:
1.
Double-click System Function > Data Query in the Analysis Task Management
window. The Query Data dialog box is displayed.
TIP
You can also choose System Function > Data Query from the navigation tree in the Analysis Task
Management window and right-click Open. The Query Data window is displayed.
2.
In the Query Data dialog box, select *** Configuration Data.

In the name of a task type, *** refers to the network system such as GSM, UMTS, CDMA,
or LTE.
3.
Set the query conditions.

(1) Specify whether to limit the time range.
(2) Select the names of the NEs to be queried.
4.
Click Query.
The query results are displayed in the Query Data dialog box.
3.4 Importing Engineering Parameters

This section describes how to import engineering parameters. You can import engineering
parameters into the Nastar database to provide a reference for certain algorithms related to
Prerequisite
Context
Engineering parameters mainly include the engineering information, geographical information,
and key configuration information of cells.
Issue 01 (2011-08-15)

25
Nastar
The engineering parameter template files in .csv, .xls, and .xlsx formats can be imported. To
open .xlsx files, you must install Microsoft Office 2007. Nastar imports and exports CSV files
most efficiently. You are advised to save the engineering parameter data as CSV files.
NOTE
If an .xls engineering parameter file contains more than 27,000 records, this file cannot be imported. Therefore,
you are advised to convert an .xls file to the .csv format before importing it.
Procedure
Step 1 Double-click System Function > Engineering Parameter Management from the navigation
tree in the Analysis Task Management window.
TIP
You can also choose System Function > Engineering Parameter Management from the navigation tree
in the Analysis Task Management window and right-click Open. The Engineering Parameter
Management window is displayed.
Step 2 In the Engineering parameter management window, click the *** engineering
parameters tab and then click Import.
In the name of the tab, *** refers to the network system such as GSM, CDMA, UMTS, or LTE.
Step 3 In the displayed Open dialog box, select an engineering parameter file, and then click Open.
If an engineering parameter file in .xls or .xlsx format is selected and the file contains multiple
sheets, the system displays a message, prompting you to select the sheet to be imported.
NOTE
You are advised to import the engineering parameter data as CSV files.
Step 4 Configure the column headers.

l At the header of each column, right-click and choose the title of the current column.
When you move the pointer to the column header of a column, a pop-up message is displayed,
showing the information about this column, for example, Column No./Configured column
title/Column title in the engineering parameter file.
l The column headers marked with the * character must be configured. Otherwise, the import
operation is not allowed.
l If you need to modify an incorrectly configured column header, right-click the column
header, clear the check box next to the original header, and then reconfigure the header.
l The engineering parameters must meet the following restrictions in different network
systems. For details, see Table 3-2. Otherwise, the engineering parameter file cannot be
imported into the database.
Issue 01 (2011-08-15)

26
Nastar
Table 3-2 Restrictions on engineering parameters

Network System
Restriction
GSM
l The mandatory parameters must be configured, and the

values of the mandatory parameters must not be empty.
l The values of the parameters must be in the specified
range.
l The value of MCC+MNC+LAC+CI of a cell must be
unique.
NOTE
For details of the mandatory parameters and the range, see GSM
Engineering Parameters.
UMTS

range.
l The value of RNCID+CELLID of a cell must be unique.
NOTE
For details of the mandatory parameters and the range, see UMTS
CDMA

range.
l The value of MSCID+CELLID+SECTORID of a cell
must be unique.
NOTE
For details of the mandatory parameters and the range, see CDMA
LTE

range.
l The value of eNodeB ID+CELLID of a cell must be
unique.
NOTE
For details of the mandatory parameters and the range, see LTE
Step 5 Click OK.

Step 6 In the OK dialog box, check the number of added records, updated records, and failed records.
Then, click OK.
Step 7 Perform the operations as prompted.
Issue 01 (2011-08-15)

27
Nastar
If...
Then...
The imported engineering parameter data is

correct
Click Close.
The imported engineering parameter data is

abnormal.
The data that fails to be imported is

highlighted in red. In this case, perform either
of the following operations:
l Click Export Failed Records.
The system exports the error records to a
file. You can modify error data and then
complete the import operation.
l Click Close to complete the import
operation.
----End
Follow-up Procedure
l
Exporting engineering parameters

After engineering parameter data is imported, you can export all engineering parameter
data from the database and save the data as a .csv, .xls, or .xlsx file for easy query and
management. To export engineering parameter data, do as follows:
1.
In the Engineering parameter management window, click the *** engineering

parameters tab and then click Export.
In the name of the tab, *** refers to the network system such as GSM, CDMA, UMTS,
or LTE.
2.
Set a file name and specify the save path and file type in the displayed Save dialog
box, and then click Save.
NOTE
You are advised to export and save the engineering parameter data as CSV files.
Deleting engineering parameters

Select the engineering parameters to be deleted from the engineering parameter list, and
then click Delete.
3.5 Checking Engineering Parameters and Configuration

Data
This section describes how to check engineering parameters and configuration data. Through
this function, you can check whether the existing engineering parameter data is consistent with
the configuration data. If the check result is inconsistent, you can enable the Nastar to
synchronize the engineering parameter data with the configuration data to ensure data
consistency.
Prerequisite
l
Issue 01 (2011-08-15)

28
Nastar
You are authorized to manage engineering parameters.
Configuration data is imported. For details, see Importing Configuration Data.
Engineering parameter data is imported. For details, see Importing Engineering Parameters.
Procedure
Step 1 Double-click System Function > Engineering Parameter Management from the navigation
tree in the Analysis Task Management window.
Step 2 In the Engineering parameter management window, click the *** engineering
parameters tab.
In the name of the tab page, *** indicates the network system such as GSM, CDMA, UMTS,
or LTE.
Step 3 Check engineering parameters.
1.
Click Configuration Check. The Nastar displays the check results.

l Number of cells with configuration and engineering parameters: indicates the number
of cells that are configured with both engineering parameters and configuration data.
l Number of cells with configuration but without engineering parameters: indicates the
number of cells that are configured with configuration data but are not configured with
l Number of cells with engineering parameters but without configuration: indicates the
number of cells that are configured with engineering parameters but are not configured
with configuration data.
l Number of External Cells with configuration but without engineering parameter:
indicates the number of external neighboring cells that are configured with configuration
data but are not configured with engineering parameters. It is only for the GSM
2.
Click Export.
3.
Select the saving path, saving name, and saving format of the check results in the Save
dialog box.
The check results in .csv, .xls, or .xlsx format can be exported.
Check results are saved in a folder, the folder includes four files:
l Engineering Parameters and Configuration Shared: This sheet records the information
about cells that are configured with both engineering parameters and configuration data.
l Proprietary Engineering Parameter: This sheet records the information of cells that are
configured with only engineering parameters.
l Proprietary Configuration: This sheet records the information of cells that are
configured with only configuration data.
l External Neighboring Cell with No engineering parameter: This sheet records the
information of external neighboring cells that are configured with only configuration
data.
The file is used to check engineering parameters only on the GSM network.
Step 4 Optional: Click Configuration Synchronize to synchronize engineering parameter data with
configuration data.
After engineering parameter data is imported into the database, the Nastar updates some
engineering parameters based on the latest configuration data according to the LAC + CI.
Issue 01 (2011-08-15)

29
Nastar
The following engineering parameters are updated:

l GSM network: BCC, NCC, BCCH, Cell Name, Cell ID, and TCH.
l UMTS network: Cell Name, P-SC, and UARFCN-DOWNLINK.
l CDMA network: BSC ID, Cell ID, Sector ID, ARFCN, and BTS ID.
If the configuration data changes, you need to manually synchronize the engineering parameter
data with the configuration data to ensure data consistency. Alternatively, you can import the
modified engineering parameter file to achieve data consistency.
----End
3.6 GIS Management

The Nastar can geographically display the performance analysis results through either the
Geographic Information System (GIS) window or Google Earth. You can view the Nastar
analysis result directly on the map, thus facilitating the service analysis.
3.6.1 Viewing Analysis Results by Using the Google Earth

This section describes how to view analysis results by using the Google Earth. The Nastar can
quickly display BTS and performance analysis results (for example, VIP analysis results) on the
Google Earth. The three-dimensional map enables you to easily view the network performance
analysis results and reduces the workload of field survey.
Prerequisite
l
The PC is connected to the Internet.
The Google Earth is installed in the PC.
Context
The principles for displaying the Nastar data on the Google Earth are as follows:
l
After the engineering parameters are read, the geographic data is displayed on the scale of
2,600 meters at heights and with the last cell in the engineering parameter list being in the
center by default.
The Nastar data can be displayed on the Google Earth synchronously. The geographic data
is displayed on the scale of 2,600 meters at heights with the selected cell being in the center.
Currently, the Nastar can display the following analysis results on a map:
GSM neighboring cell analysis results, GSM VIP analysis results, and GSM service
geographic analysis results
UMTS intra-frequency neighboring cell analysis results, UMTS VIP analysis results,
UMTS pilot pollution analysis results, and UMTS service geographic analysis results
CDMA intra-frequency neighboring cell analysis results, CDMA VIP analysis results,
and CDMA pilot pollution analysis results
LTE VIP analysis
Issue 01 (2011-08-15)

30
Nastar
Click
on the toolbar in the GIS window (that is Service Geographic Observation
window) to view the legend information. It shows the display effect of each type of analysis
result.
NOTE
The description of operations related to the Google Earth is not provided in this document.
Procedure
Step 1 Double-click System Function > Satellite View from the navigation tree in the Analysis Task
Management window. The EarthViewWindow window is displayed.
The system loads the Google Earth components through the Internet. After the loading is
complete, the system automatically reads the engineering parameters in the Nastar system and
displays the engineering parameters as labels on the Google Earth.
If...
Then...
The EarthViewWindow window displays the

home page of the Google Earth
It indicates that the system fails to

automatically read the Nastar engineering
parameters.
This problem may be caused by the low
speed of loading the Google Earth
components. In this case, you need to
double-click System Function > Satellite
View again.
TIP
You can also choose System Function >
Satellite View from the navigation tree in the
Analysis Task Management window and
right-click Open. The Satellite View window
is displayed.
The EarthViewWindow window displays sites It indicates that the system succeeds in
automatically reading the Nastar
and cells, and the specified area is located.
Step 2 Enable the Google Earth to display the Nastar data synchronously.
After you click a cell in the analysis results, the Google Earth regards the selected cell as a center,
and then displays the geographic data on the scale of 2,600 meters at heights.
Step 3 View the cell information.
After you click a cell, the Google Earth displays the engineering parameter information about
the cell in a message box.
You can click the cell again to cancel the display of the message box.
----End
Issue 01 (2011-08-15)

31
Nastar
3.6.2 Querying Analysis Results Through the GIS Window

This section describes how to query analysis results through the Geographic Information System
(GIS) window. The Nastar can quickly display BTS and performance analysis results (for
example, VIP analysis results) in the GIS window.
Prerequisite
l
You are authorized to use the GIS.
Context
The principles for displaying Nastar data in the GIS window are as follows:
l
The Nastar data can be displayed in the GIS window synchronously. The geographic data
is displayed with the selected cell being in the center.
Currently, the Nastar can display the following analysis results on a map:
GSM neighboring cell analysis results, GSM VIP analysis results, and GSM service
geographic analysis results
UMTS intra-frequency neighboring cell analysis results, UMTS VIP analysis results,
UMTS pilot pollution analysis results, and UMTS service geographic analysis results
CDMA intra-frequency neighboring cell analysis results, CDMA VIP analysis results,
and CDMA pilot pollution analysis results
LTE VIP analysis
on the toolbar in the GIS window (that is Service Geographic Observation
Click
window) to view the legend information. It shows the display effect of each type of analysis
result.
Procedure
on the toolbar on the upper left corner of the Nastar client window. The GIS window
Step 1 Click
is displayed.
After the GIS window is displayed, click
to hide the GIS window.
Step 2 Load engineering parameters.

For details, see Loading Site Information. For details about the operations in the GIS window,
see Managing the GIS Window.
Step 3 Enable the GIS window to display the Nastar data synchronously.
After you click a cell in the engineering parameter list or an analysis result, the GIS window
regards the selected cell as a center to display the geographic data.
Step 4 Query cell information.
to select a cell. Then, the engineering parameters of the cell are displayed in the area
Click
in the right pane of the GIS window.
----End
Issue 01 (2011-08-15)

32
Nastar
3.7 Managing the GIS Window

You can import the map files in .wor, .tab or .sxwu format and view the site information in the
GIS window by using the engineering parameters. In addition, you can perform the following
operations in the GIS window through the GIS toolbar, such as move/center/zoom in on/zoom
out on a map and measure the distance between two points on the map.
Context
NOTE
The GIS window is the Service Geographic Observation window. You can click
corner of the Nastar client to open the window.
button in the upper left
3.7.1 Importing a Map

This section describes how to import a map. You can import the map files in .wor, .tab, or .sxwu
format to simulate the geographic environment, thus facilitating the analysis and location of
network problems.
Prerequisite
l
Context
The Nastar provides two modes for importing map files:
l
Mode 1: Importing a map file for the first time

If the map files in .wor or .tab format, the importing speed and the operation response are
slow. It is recommended to convert the map files in .wor or .tab format to the map files
in .sxwu format by referring to Converting the Map File Format. You can import the map
files in .sxwu format to improve the importing speed and the operation efficiency.
Mode 2: Loading a map file again (the map file was imported last time)
If you have already imported a map file, you are advised to load the map files to speed up
the importing process.
CAUTION
When you perform operations in the GIS window, you are advised not to import or load map
files repeatedly. This is to prevent any unknown impact.
Procedure
Step 1 Select a mode to import map files depending on the actual situation.
Issue 01 (2011-08-15)

33
Nastar
If You Want to ...
Then ...
Import a map file for the first time For details, see Step 2 to Step 4.
Load a map file again
Step 2 Click
Click
on the toolbar to load the map file that was
imported last time.
on the toolbar. The Choose... dialog box is displayed.
Step 3 Select a map file in .wor, .tab, or .sxwu format.

Step 4 Click Open.
The system starts importing the map file.
----End
Follow-up Procedure
Deleting the geography layer. Click Layer Management icon on the toolbar, select the
geography layer to be deleted, click Remove.
3.7.2 Converting the Map File Format

This section describes how to convert a map file in .wor or .tab format to .sxwu to improve the
efficiency of importing map files.
Prerequisite
Context
It takes a long time to import a map file in .wor or .tab format. If users on multiple clients attempt
to import the same map file, the work efficiency is low.
To solve this problem, the Nastar allows users to convert a map file in .wor or .tab format to .sxwu
and import the file because the Nastar can quickly identify and import map files in .sxwu format
and allows multiple users to share the map files in .sxwu format. This greatly improves the
efficiency of importing map files. It is recommended to convert the map files by one person,
and then share them to others.
Procedure
Step 1 Choose Maintenance > Map Convert on the menu bar.
Step 2 In the displayed Parameter Config dialog box, set the conversion parameter.
l Maps Path, select a map file in .wor or .tab format.
l Save Path, set the save path after format conversion.
l Save Name, set the file name after format conversion.
Step 3 Click OK.
Issue 01 (2011-08-15)

34
Nastar
The Nastar starts importing the map file. If the size of the map file is large, the format conversion
speed is low. It costs about 3 minutes to convert 1 MB map files.
The file after format conversion is saved in a folder, which contains multiple files. In the folder,
the File Name.sxwu file is used to import map data.
----End
3.7.3 Loading Site Information

This section describes how to load the site information. You can load the engineering parameters
to the GIS so that the site information of the network can be displayed in the GIS window.
Prerequisite
l
The required engineering parameters are imported to the Nastar.

For example, when you need to load the site information of the GSM network, you must
have imported the engineering parameters of the GSM network.
Context
When you open the client every time, you must load the site information again to view the site
information in the GIS window.
Procedure
Step 1 Click
on the toolbar. The Choose Geographic Sites dialog box is displayed.
Step 2 Choose the network system from the drop-down list box.
Step 3 Select the site whose information needs to be loaded from the group box at the bottom.
Step 4 Click OK.
After the site information is loaded, an icon is displayed in the GIS window.
----End
Follow-up Procedure
l
Displaying or hiding the site icon.

You can select or clear the check box before the Site layer navigation tree in the left pane
of the GIS window.
Setting the display effect.

Right-click Site Layer > The layer to be set on the navigation tree in the left pane of the
GIS window, and then choose Sector Display from the shortcut menu to set the display
effect of the sector, such as the size, dot, and color; choose Site Display from the shortcut
menu to set the display effect of the site, such as the size, dot, and color.
l
Issue 01 (2011-08-15)
Deleting the site layer.

35
Nastar
Click layer management icon

Remove.
l
on the toolbar, select the site layer to be deleted, click
Setting the opacity of the site layer.

Click layer management icon
Opacity.
on the toolbar, select the site layer to be deleted, set
3.7.4 Filtering Cells

This section describes how to filter cells. You can filter cells based on the network system,
specified engineering parameters, and specified areas to optimize only the specified cells. The
filtered cells are geographically displayed in highlighted colors to be differentiated from other
cells. In addition, the filtered cells can be saved as a cell group.
Prerequisite
l
The engineering parameters are imported to the Nastar.
Context
Before filtering cells, you must ensure that the engineering parameters are consistent with the
configuration data.
Procedure
Step 1 Draw polygons to define the areas to be filtered.
on the toolbar.
1.
Click
2.
Click the GIS work platform to add points to the polygon one by one.
CAUTION
The lines of a polygon must not intersect. Otherwise, certain selected areas may be missed
out.
If only one point of a line in the polygon is determined, the line is displayed as a broken
blue line. It indicates that you are drawing this line. If two points of a line in the polygon
are determined, the line is displayed as a solid blue line. It indicates that you have finished
drawing this line.
3.
After the last point is added, right-click the work platform to exit the drawing of polygon.
Then, open the Input dialog box.
4.
Set the name of the polygon.
5.
Click OK to complete the drawing of polygon.

The polygon and the polygon name are displayed on the GIS window.
Step 2 Set filtering conditions to filter the cells in the specified area, with the specified network system
and engineering parameter field.
Issue 01 (2011-08-15)

36
Nastar
1.
Click
on the toolbar. The Search dialog box is displayed.
2.
Select the area to be filtered in Region.
3.
Select the network system in Network Technology.
4.
Set the fields of engineering parameters in the lower left corner of the dialog box.
The Nastar supports the filtering through all engineering parameter fields. You can filter
cells either through a certain field or two fields. The relation between the two fields can be
set to And or Or.
Step 3 Click Search. The system starts to filter cells.

The filtering results are displayed in the Search Result area.
Step 4 Select or clear the check box in the Search Result area to determine whether to filter cells again.
Step 5 Geographically display the filtered cells.
Click Geographic(D). The cells selected in the Search Result area are highlighted in the GIS
window.
Step 6 Save the filtered cells as an NE group.
1.
Click Save As a NE Group(S) to open the Save as an NE group dialog box.
2.
Set NE Group Name and add the remarks.
3.
Click OK.
The cells selected in the Search Result area are saved as an NE group. You can view the
information about the NE group through the NE group management function.
----End
3.7.5 Searching Cells

This section describes how to search cells. You can using the search function to locate the cell
in the GIS window quickly.
Prerequisite
l
The required engineering parameters are imported to the Nastar.
Procedure
Step 1 In the GIS window, click
on the toolbar, or press Ctrl+F to open the Find window.
Step 2 Type the keyword in the Cell Name field.

Step 3 Choose the technology in the Select the network field.
Step 4 Click Find Next. Then, the system searches for the cells that the cell name contains the keyword.
l The keyword is case insensitive.
l The GIS window regards the searched cell in blue as a center.
----End
Issue 01 (2011-08-15)

37
Nastar
3.7.6 Moving/Zooming In On/Zooming Out On/Refreshing/Fully

Displaying a Map
This section describes how to adjust a map. You can zoom in or zoom out on a map to change
the map size, move a map, and display all the objects in the map window. In addition, you can
restore the map window to the default status through the refreshing function.
Prerequisite
Importing a map has been performed.
Procedure
l
Zoom in and zoom out on the map.

The Nastar enables you to zoom in and zoom out on the map by changing the position of
the mouse pointer.
1.
2.
Click the corresponding icon on the tool bar to zoom in or zoom out on the map.
Click
, and then click the map, the map is zoom in.
Click
, and then click the map, the map is zoom out.
Click the map.

TIP
You can scroll the mouse wheel forward or backward to zoom in or zoom out on the map.
Move the map.

When you move a map, the size of the map does not change.
on the toolbar.
1.
Click
2.
Move the mouse pointer on the map and drag the map to the required direction.
View the panoramic scene of a map.

After you click
, the system displays all the objects in the map window.
Refresh a map.
, the colors and connection lines of the site icons and sector icons that
After you click
are highlighted because of the service geographical application are cleared.
----End
3.7.7 Measuring Distance on the Map

This section describes how to measure distance on the map. You can measure distance between
two points on the map by using the distance measurement tool.
Prerequisite
Importing a map has been performed.
Issue 01 (2011-08-15)

38
Nastar
Procedure
Step 1 Click
on the toolbar.
Step 2 Click a point on the map and use it as the starting point for measuring the distance.
Then, the starting point is fixed. Press and hold the left mouse button, and then move the mouse.
When the mouse pointer moves away from the starting point, the system displays a solid black
connection line between the starting point and the mouse pointer.
In the status bar in the right pane of the window, the distance between two points is displayed
in the Distance(km) area in real time.
Step 3 Double-click or right-click the map to complete the distance measurement.
----End
3.7.8 Saving the Map Display Effect

This section describes how to save the map display effect. You can export the display effect of
overlapped layers in the map window as images in .png, .gif, or .jpg format.
Procedure
Step 1 Click
on the toolbar. The Open dialog box is displayed.
Step 2 Set the name, save path, and format of the file.
Step 3 Click Save.
----End
3.8 Reference to the Basic Data Collection Interface

This section describes the interface for collecting basic data on the Nastar and the relevant
parameters. You can refer to this section when you import configuration data, engineering
parameters, or maps.
3.8.1 Interface Description: GIS

This section describes the GIS interface, that is Service Geographic Observation window.
Before performing relevant operations, familiarize yourself with the functions of the areas on
the interface.
Figure 3-1 shows the GIS interface.
Issue 01 (2011-08-15)

39
Nastar
Figure 3-1 GIS interface
SN
Item
Description
(1)
Layer area
Allows users to perform operations on site layers or

geographic layers, such as selecting, clearing, or
deleting layers.
(2)
Toolbar
Shows common GIS operation buttons.
(3)
Main area
Shows cell relationships geographically.

At the bottom of the main area, it synchronously
displays the longitude and latitude of the location
where the pointer stays and the distance between two
points during distance measurement.
(4)
Parameter area
Displays engineering parameter information of

selected cells.
3.8.2 Parameters for Creating or Modifying a Data Collection Task

This section describes the parameters related to data collection tasks. You can refer to the
description when creating or modifying data collection tasks.
Issue 01 (2011-08-15)
Parameter
Value Range
Description
Task Name
Value range: [1.64]
Indicates the name of a task.

40
Nastar
Parameter
Value Range
Description
Task Type
Choose Task Type > Data Collection > Data

Collection.
Execution
Type
This parameter has two

options: One-time and
Periodic.
l One-time task: The system executes a task once

only at the specified time.
Start time
Indicates the start time for a task.
DST
You can select or clear

the check box next to
the option.
Indicates whether to use daylight saving time

(DST).
Run
immediatel
y
You can select or clear

the check box next to
the option.
If you select this option, Start time becomes

unavailable and the task will be executed
immediately after the setting.
Execution
Interval
Value range:
[1.527040]
Indicates the interval between periodic tasks. An

interval has two dimensions: duration and unit.
Execution
Times
Value range: [0,65535]
Indicates the number of times that a periodic task is

executed.
l Periodic task: The system executes a task

periodically at the preset time.
0 indicates that the execution times are not limited.
Issue 01 (2011-08-15)
End time
The value of this

parameter must be later
than Start time and
earlier than 12/31/2038
23:59:59.
Indicates the end time for a periodic task.
OSS Name
Select a parameter
value from the dropdown list box.
Indicates the name of an EMS.

41
Nastar
Parameter
Value Range
Description
Data Type
Select an option from

the drop-down list box.
The options vary with
the OSS version. For
details, see the
following description:
Indicates the type of the data that is collected from

the EMS to the Nastar.
l The data types

corresponding to the
OSS of the M2000
V200R006 are
Config data and
Any.
l The data types
corresponding to the
OSS of the M2000
V200R008, M2000
V200R009, M2000
V200R010 and
M2000 V200R011
are Config Data,
GSM Measure
Task File for
Neighbor Cell
Data, GSM Frqlog
Data, Performance
Data, Any Data,
and LTE CFG
Data.
Collect All
NE
You can select or not

select the option.
If you select this option, you can select all the NEs.
When the NEs change, the system automatically
updates the NEs every four hours.
Collect By
NE Type

select the option.
If you select this option, you can select the NEs by

the NE type. When the NEs under the selected NE
type change, the system automatically updates the
NEs under the selected NE type every four hours.
After you select this option, you can only select all
NEs under an NE type but cannot select some NEs
under an NE type.
Issue 01 (2011-08-15)
Filter NE
Allows you to type keywords to filter NEs.
Period
Select a parameter
value from the dropdown list box. The
options are 5 Minutes,
15 Minutes, 30
Minutes, 60 Minutes,
24 Hours.
Period for collecting data. For example, if you set

the value to 5 Minutes, the Nastar collects
performance data from the EMS at intervals of five
minutes.

42
Nastar
Parameter
Value Range
Description
Specify the
time range

select the option.
Indicates whether to collect data during the

specified time period.
Start Time
Indicates the start time of the data collection period.
End Time
Indicates the end time of the data collection period.
Source
directory
Indicates the path for storing files in the EMS.
Source file
Indicates the name of the file to be collected from

the EMS.
Destination
directory
Indicates the path for storing files on the Nastar.
The
following
files will be
collected
from ***
Indicates that the system collects the Source

directory/Source file from the selected OSS.
And save to
the server
path
Indicates that the collected file is stored in

$DATAROOT/oss_folder name containing the
start time of a period/Destination directory/
Source file on the Nastar server.
Get files
repeatedly

select the option.
Indicates that all the data in the M2000 is collected

to the Nastar each time when a periodic data
collection task is performed.
Get files all

over

select the option.
Indicates whether to traverse the files in

subdirectories of the configured source data path.
*** indicates the name of the OSS.
If this option is not selected, it indicates that the files

are not traversed.
Issue 01 (2011-08-15)

43
Nastar
Subscribing to UMTS Data Sources
About This Chapter

This section describes how to enable data source switches by using the data source subscription
function before performing various UMTS theme analysis functions. After required data source
switches are enabled, the Nastar can collect required data from network elements (NEs). This
function is the prerequisite for all Nastar theme analysis functions.
4.1 Basic Knowledge of UMTS Data Source Subscription
This section describes the functions and usage scenarios of UMTS data source subscription.
4.2 Setting Data Source Switches (As an Administrator User)
Before any Nastar theme analysis task is performed, the administrator user must enable data
source switches in batches for all theme analysis functions on network elements (NEs) through
the data source subscription function. This ensures that NEs can collect the required analysis
data for the Nastar.
4.3 Querying the Data Source Switch Status on the Live Network (As a Common User)
Before performing a theme analysis task on the Nastar, you must query the data source switch
status on the live network to verify that all required data source switches are enabled. If a required
data source switch is not enabled, request the administrator to enable it.
4.4 GUI Description: Subscribing to UMTS Data Source
The GUI related to subscribing to UMTS data sources is composed of four tabs: Set Data
Subscription, Query Network Data Subscription, VIP Signaling Tracing Setting, and VIP
Signaling Tracing Status. Before performing relevant operations, familiarize yourself with the
functions of the areas on the GUI.
Issue 01 (2011-08-15)

44
Nastar
4.1 Basic Knowledge of UMTS Data Source Subscription

This section describes the functions and usage scenarios of UMTS data source subscription.
Description
Data source subscription is used to enable various data source switches on network elements
(NEs) for Nastar analysis. After data source switches are enabled, the Nastar can collect required
data from the NEs.
For details about the functions and usage scenarios of data source subscription, see Table 4-1.
Table 4-1 Description of UMTS data source subscription
Theme
Required
Data
Source
Whether to
Enable Data
Source
Subscriptio
n
Function
UMTS
coverag
e
analysis
MR data
Yes
Used to enable the RNC-level MR measurement

function.
UMTS
uplink
interfere
nce
analysis
RTWP data
Yes
Used to enable the NodeB-level RTWP

measurement function.
UMTS
complai
nt
analysis
support
CHR data
Yes
Used to enable the RNC-level CHR measurement

function.
UMTS
intrafrequenc
y
neighbo
ring cell
analysis
UMTS
pilot
pollutio
n
analysis
Issue 01 (2011-08-15)

45
Nastar
Theme
Required
Data
Source
Whether to
Enable Data
Source
Subscriptio
n
Function
MR data,
CHR data
Yes
The following data will be subscribed to:
UMTS
VIP
analysis
UMTS
cell
perform
ance
analysis
UMTS
terminal
analysis
UMTS
service
geograp
hic
analysis
l UMTS MR service geographic data, used to

enable the RNC-level MR measurement
function.
l UMTS CHR service geographic data, used to
enable the RNC-level CHR measurement
function.
NOTE
MR data is required for the Nastar UMTS coverage analysis. Therefore, the Nastar delivers MML commands
through the data subscription function to enable the RNC-level MR data function and the cell-level MR data
function on RNCs to obtain analysis data. After these functions are enabled, the CPU usage on the Signaling
Processing Units (SPUs) of the RNCs is increased by about 8% relatively. For example, if the SPU CPU usage
is 45%, the increase 8% relatively is equal to the increase 3.6% absolutely, that is 3.6% / 45% = 8%. Other
modules of the RNCs are not affected.
Usage Scenario
Data source subscription is a function with a high security level. The following two types of
users have different permissions to perform this function:
l
Administrators: An administrator user is authorized to query the status of data source

switches and set data source switches.
Common users: A common user is only authorized to query the status of data source
switches.
NOTE
User rights can be set by choosing Security > Security Management.
Figure 4-1 describes the usage scenarios for the two types of users performing data source
subscription.
Issue 01 (2011-08-15)

46
Nastar
Figure 4-1 Usage scenario
Table 4-2 Description of usage scenarios
Issue 01 (2011-08-15)
User
Usage
Scenari
o
Description
Example
Admin
istrator
Initial
setting
An administrator user is
authorized to collect Nastar usage
information on the managed
networks when the Nastar is
initially used. In addition, the user
is authorized to enable data source
switches in batches for various
theme analysis functions.
Managed networks: network A

and network B

Involved theme analysis function:

VIP analysis
Select all cells on networks A and
B, and set the data source
subscription switch to ON for the
VIP analysis of all cells.
47
Nastar
User
Usage
Scenari
o
Description
Example
Routine
maintena
nce
Maintenance information can be

obtained in either of the following
methods:
l The administrator periodically

queries the status of data
source switches on the live
network and compares the
status with the historical status
set on the Nastar. If a data
source switch is set to ON on
the Nastar but it is set to OFF
on the live network, enable the
data source subscription
function again to set the data
source switch to ON.
l If a common user finds that the
status of a data source switch
on the live network does not
meet analysis requirements,
the administrator enables the
data source subscription
function again to enable the
data source switch.
Comm
on user
Routine
query
Common users can query whether

the data source status on the live
network meets analysis
requirements before performing
various theme analysis End to End
(E2E) tasks. If the data source
status does not meet analysis
requirements, common users can
request the administrator to enable
the required data source switches.
A common user queries the data

source status on network A. After
querying, the user finds that the
data source switch for VIP
analysis in cell a is set to OFF,
which does not meet analysis
requirements. Therefore, the user
requests the administrator to
enable this switch.
After receiving the application,
the administrator sets the data
source switch for VIP analysis in
cell a to ON.
4.2 Setting Data Source Switches (As an Administrator User)

Before any Nastar theme analysis task is performed, the administrator user must enable data
source switches in batches for all theme analysis functions on network elements (NEs) through
the data source subscription function. This ensures that NEs can collect the required analysis
data for the Nastar.
Issue 01 (2011-08-15)

48
Nastar
Prerequisite
l
You have logged in to the Nastar client as an administrator user.
You are authorized to set data source switches.
The Operating Support System (OSS) and NEs related to analysis tasks are created. For
details, see Creating OSSs and the Managed NEs.
The configuration data has been imported into the Nastar database. For details, see
Importing Configuration Data.
Context
Before setting data source switches, the administrator must learn about NE information and
Nastar usage information of the managed networks to enable data source switches in batches for
theme analysis functions.
Procedure
Step 1 In the navigation tree on the left of the Analysis Task Management window, double-click
System Function > Subscription Management.
Step 2 In the Subscription Management window, click a network system tab.
Step 3 In the NE navigation tree, select NEs to be set.
On the Set Data Subscription tab page, the status of the selected NEs in the Nastar database is
displayed synchronously. During initial setting, the status of all data source switches is OFF or
Nonsupport.
Step 4 On the Set Data Subscription tab page, click Set. The Set Performance Subscription dialog
box is displayed.
Step 5 Set all data source subscription switches for theme analysis functions to ON.
A data source subscription switch can be in one of the following states:
l ON: indicates that the data source switch for a theme analysis function on the selected NE
is enabled.
l OFF: indicates that the data source switch for a theme analysis function on the selected NE
is disabled. This value is not recommended.
l No Modification: The status of a data source switch on an NE is not modified on the Nastar.
This is the default value.
NOTE
The same type of data source can be shared by some theme analysis functions. For example, call history record
(CHR) data is required for the complaint analysis support function, very important person (VIP) analysis
function, and cell performance analysis function. Therefore, the status of data source switches for these theme
analysis functions must be the same. For details, see the description below the Set Performance
Subscription dialog box.
Step 6 Optional: Set the VIP signaling tracing switch.

NOTE
This step applies only to GSM subscription and UMTS subscription.
1.
On the VIP Signaling Tracing Setting tab, click ON. The VIP Switch Setting dialog box
is displayed.
2.
In the VIP group user navigation tree, select VIP users to set.
Issue 01 (2011-08-15)

49
Nastar
You can hold down shift to select VIP subscribers. Right-click and choose Select from the
shortcut menu to select the highlighted VIP subscribers.
You can also select Select None from the shortcut menu to clear the selected VIP
subscribers.
3.
In the NE object navigation tree, select NEs to set.
Step 7 Click Confirm.

The Nastar delivers MML commands to request NEs to enable the required data source switches.
The operation process information is displayed in the Operation Information area.
----End
Follow-up Procedure
After the required data sources are subscribed to, click Refresh. The data source subscription
status on NEs in the Nastar database is refreshed.
4.3 Querying the Data Source Switch Status on the Live

Network (As a Common User)
Before performing a theme analysis task on the Nastar, you must query the data source switch
status on the live network to verify that all required data source switches are enabled. If a required
data source switch is not enabled, request the administrator to enable it.
Prerequisite
l
You are authorized to query the data source switch status.
The Operating Support System (OSS) and network elements (NEs) related to analysis tasks
are created. For details, see Creating OSSs and the Managed NEs.
Procedure
System Function > Subscription Management.
Step 2 In the Subscription Management window, click a network system tab.
Step 3 In the NE navigation tree, select NEs to be queried.
Step 4 Click the Query Network Data Subscription tab on the right.
Step 5 Click Query.
After the query, the data source switch status of NEs on the live network is displayed in a table
in the lower right area.
Table 4-3 describes the status of data source switches.
Issue 01 (2011-08-15)

50
Nastar
Table 4-3 Description of data source switch status on the live network
Icon
Status
Description
ON
Indicates that a data source switch is enabled on an NE and the status

meets the Nastar analysis requirements.
OFF
Indicates that a data source switch is disabled on an NE and the status

does not meet the Nastar analysis requirements.
Unkno
wn
Indicates that the status of a data source switch on an NE is unknown.

That is, the Nastar cannot determine the status of the data source switch.
The possible causes are as follows:
l The Nastar does not communicate with the M2000/operation and
maintenance center (OMC) properly.
l The M2000/OMC does not communicate with the NE properly.
l The NE is not in the normal operating state, for example, the NE is
being upgraded or powered off.
Nonsu
pport
Indicates that the Nastar does not allow users to query the status of a data
source switch on an NE. For example: An NE is a base station controller.
A data source switch on the live network can only be enabled for cells.
In this case, the data source switches on this NE are in the Nonsupport
state.
All required data source switches must be set to ON for the normal execution of analysis tasks.
If a required data source switch is set to OFF, request the administrator to enable this switch.
NOTE
l It usually takes about 2 seconds to query the data source switch status on an NE. If you query the data source
switch status on multiple NEs, it may take some time.
l You can click Cancel to cancel the query.
----End
4.4 GUI Description: Subscribing to UMTS Data Source

The GUI related to subscribing to UMTS data sources is composed of four tabs: Set Data
Subscription, Query Network Data Subscription, VIP Signaling Tracing Setting, and VIP
Signaling Tracing Status. Before performing relevant operations, familiarize yourself with the
functions of the areas on the GUI.
Switch Settings
This tab sets the switch of the UMTS data source. For details, see Figure 4-2.
Issue 01 (2011-08-15)

51
Nastar
Figure 4-2 Switch setting interface
SN
Item
Description
(1)
NE navigation tree
You can select NEs to set in the NE navigation tree.
(2)
Button area
By clicking Set, you can set the subscription status of

the data source for each theme analysis.
By clicking Refresh, you can refresh the subscription
status of the data source for each theme analysis.
You can set three subscription states: ON, OFF, and
No Modification. For details, see Setting Data
Source Switches (As an Administrator User).
(3)
NE list area
The NE settings for each theme analysis are displayed

in a list.
TIP
You can select multiple records by holding down Ctrl.
(4)
Operation information
list area
In this area, you can view the setting of the data source
switch.
(5)
Area for displaying

data source status
icons
Icons show the switch status of the data source. For

details, see Table 1.
Switch Status on the Current Network

This tab displays the switch status of the UMTS data source on the current network. For details,
seeFigure 4-3.
Figure 4-3 Switch status on the current network
Issue 01 (2011-08-15)

52
Nastar
SN
Item
Description
(1)
NE navigation tree
You can select NEs to query in the NE navigation tree.

NOTE
If you have selected NEs in Set Data Subscription, you do
not need to select the NEs again in the NE navigation tree.
(2)
Button area
By clicking Query, you can query the data source

switch status of each NE on the live network.
(3)
NE list area
The data source switch status of each NE on the live

network is displayed in a list.
TIP
(4)
list
This area displays the result of querying the data

source switch.
(5)
Area for displaying

data source status
icons

Settings of VIP Signaling Tracing Switch

This tab sets the VIP signaling tracing switch. For details, seeFigure 4-4.
Figure 4-4 Settings of VIP signaling tracing switch
SN
Item
Description
(1)
NE navigation tree
You can select NEs to set VIP signaling tracing in the

NE navigation tree.
NOTE
Because you select NEs in area (2) and the system takes the
selection in area (2) in priority, you need not select NEs in
this area.
Issue 01 (2011-08-15)

53
Nastar
SN
Item
Description
(2)
Button area
By clicking ON, select VIP subscribers and NEs to

set VIP signaling tracing. After you click Confirm,
the system enables the VIP signaling tracing switch
for selected NEs.
After you click OFF, the system disables the VIP
signaling tracing switch for selected NEs.
(3)
VIP signaling tracing

NE list area
The basic information about NEs for which you have

set VIP signaling tracing is displayed in a list.
TIP
(4)
list area
This area displays the result of enabling or disabling

VIP signaling tracing for NEs.
(5)
Area for displaying

data source status icons

VIP Signaling Tracing Switch Status on the Current Network

This tab displays the VIP signaling tracing switch status of NEs on the current network. For
details, see Figure 4-5.
Figure 4-5 VIP signaling tracing switch status on the current network
SN
Item
Description
(1)
NE navigation tree
You can select NEs to query in the NE navigation

tree.
NOTE
If you have selected NEs in VIP Signaling Tracing
Setting, you do not need to select the NEs again in the NE
navigation tree.
(2)
Issue 01 (2011-08-15)
Button area
By clicking Query, you can query the VIP signaling

tracing switch status of each NE on the current
network.

54
Nastar
SN
Item
Description
(3)
VIP signaling tracing

NE list area
The data source switch status of NEs for which you

have set VIP signaling tracing on the live network is
displayed in a list.
TIP
(4)
list area
This area displays the result of querying the data

source switch.
(5)
Area for displaying

data source status icons

Table 4-4 Data source switch status

Icon
State
Description
ON
The data source switch of an NE on the current network is set to ON for

analysis by the Nastar.
OFF
The data source switch of an NE on the current network is set to OFF.

Therefore, the Nastar cannot perform analysis.
Unkno
wn
The data source switch of an NE on the current network is unknown. The

Nastar cannot detect the data source status of the NE. The possible causes
are as follows:
l The communication between the Nastar and the M2000/OMC is
abnormal.
l The communication between the M2000/OMC and NEs is abnormal.
l NEs are not in normal running status. For example, NEs are being
upgraded or have been shut down.
Nonsu
pporte
d
Issue 01 (2011-08-15)
The Nastar does not display the data source switch status of an NE on the
current network. For example, if an NE is of the base station controller
(BSC) level but the data source switch on the current network supports
only objects at the cell level, the data source switch status of the NE is
displayed as Nonsupport.

55
Nastar
UMTS Coverage Analysis
About This Chapter

The UMTS coverage analysis function enables you to obtain UMTS coverage analysis data,
create UMTS coverage analysis tasks, query UMTS coverage analysis results, and export UMTS
coverage analysis reports from the Nastar. The Nastar analyzes the measurement reports (MRs)
sent by UEs and displays the coverage status, signal quality, and subscriber distribution of a
measurement cell. This function helps to locate wireless network problems such as weak
coverage, cross coverage, and poor service quality.
5.1 Basic Knowledge of UMTS Coverage Analysis
This section describes the basic knowledge of UMTS coverage analysis. The Nastar performs
UMTS coverage analysis based on the measurement reports (MRs) reported by UEs and then
generates analysis results. These analysis results help users learn the coverage of measurement
cells and identify problems such as weak coverage, cross coverage, and poor service quality.
5.2 UMTS Coverage Analysis Process
This section describes the UMTS coverage analysis process.
5.3 Obtaining UMTS Coverage Analysis Data
This section describes how to enable the Nastar to obtain UMTS coverage analysis data. You
can create an E2E task to enable the Nastar to collect analysis data and create a data import task
to enable the Nastar to import the collected analysis data into the database.
5.4 Creating UMTS Coverage Analysis Tasks
This section describes how to create UMTS coverage analysis tasks. After you create a UMTS
coverage analysis task, the Nastar periodically analyze measurement reports (MRs) that are sent
by UEs and saved in the database. By querying the analysis results, you can learn the coverage
of the selected measurement cell and determine network problems such as weak coverage, cross
coverage, and poor service quality.
5.5 Querying UMTS Coverage Analysis Results
This section describes how to query UMTS coverage analysis reports. You can query the
measurement reports (MRs) sent by UEs within a specific period and then learn about the
coverage situation of the selected measurement cell according to the queried results. This
function helps you determine whether problems such as weak coverage, cross coverage, or poor
service quality exist.
5.6 Exporting UMTS Coverage Analysis Reports
Issue 01 (2011-08-15)

56
Nastar
This section describes how to export UMTS coverage analysis reports. You can export the
queried coverage analysis results as .csv or .xls files to determine the coverage of measurement
cells on the network based on the exported analysis results.
5.7 Technical Specifications for UMTS Coverage Analysis
This section describes the technical specifications for UMTS coverage analysis.
5.8 Reference for the UMTS Coverage Analysis GUI
This section describes the interface for UMTS coverage analysis and the relevant parameters.
Before performing relevant operations, familiarize yourself with the functions of UMTS
coverage analysis.
Issue 01 (2011-08-15)

57
Nastar
5.1 Basic Knowledge of UMTS Coverage Analysis

This section describes the basic knowledge of UMTS coverage analysis. The Nastar performs
UMTS coverage analysis based on the measurement reports (MRs) reported by UEs and then
generates analysis results. These analysis results help users learn the coverage of measurement
cells and identify problems such as weak coverage, cross coverage, and poor service quality.
An MR reported by a UE contains downlink RSCP, Ec/No, and transmit propagation delay (TP).
After the conditions for coverage analysis are set, the Nastar analyzes the coverage of the selected
cell and then displays analysis results in a two-dimensional (2-D) chart, a three-dimensional (3D) chart, and a table.
l
In the 2-D chart, information about the following services is displayed: AMR, VP, BE,
AMR+BE, and OTHER services. Information about each service contains three counters,
namely, RSCP_DL, Ec/No_DL, and TP.
In the 3-D chart, information about CS services and PS services is displayed. Information
about both CS services and PS services contains three counters, namely, RSCP_DL, Ec/
No_DL, and TP.
In the overview table, the counter statistics of all services involved in the 2-D chart are
displayed.
The results of coverage analysis can be exported as .csv files. Users can optimize cells with
coverage problems according to the exported analysis results.
5.2 UMTS Coverage Analysis Process

This section describes the UMTS coverage analysis process.
Figure 5-1 shows the process of UMTS coverage analysis.
Issue 01 (2011-08-15)

58
Nastar
Figure 5-1 Process of UMTS coverage analysis
Table 5-1 describes each procedure shown in Figure 5-1.

Table 5-1 Description of UMTS coverage analysis process
Issue 01 (2011-08-15)
No.
Procedure
Description
Create a UMTS
coverage data
E2E task
You need to choose Maintenance > E2E Task Management

on the Nastar client to open the E2E Task Management window
and then create a E2E task. After you create the task, the Nastar
issues rule files to the M2000, and then the M2000 sends the rule
files to the related SAU. Then, the SAU performs the
measurement task.

59
Nastar
No.
Procedure
Description
Create a UMTS
coverage
analysis data
import task
You need to choose Maintenance > Task Management on the

Nastar client to open the Task Management window, and then
create a UMTS coverage analysis data import task. After you
create the task, the Nastar periodically imports the coverage data
files saved on the Nastar server into the database.
Check the
integrity of
UMTS coverage
analysis data
You can double-click System Function > Data Query in the

Analysis Task Management window on the Nastar client to
open the Query Data dialog box and then verify that all the
required UMTS coverage analysis data is imported into the
database.
Create a UMTS
coverage
analysis task
In the Analysis Task Management window on the Nastar client,

you can create a UMTS coverage analysis task. After you create
the task, the Nastar periodically retrieves UMTS coverage
analysis data and UMTS configuration data from the database,
analyzes the retrieved data, and then generates analysis results.
Query UMTS
coverage
analysis results
You can view the analysis results of the UMTS coverage analysis
tasks that are executed successfully. The analysis result helps
you learn the coverage of the selected measurement cell and
determine cell problems such as weak coverage, cross coverage,
and poor service quality on the live network.
Export UMTS
coverage
analysis reports
You can enable the Nastar client to export UMTS coverage

analysis results as files.
5.3 Obtaining UMTS Coverage Analysis Data

This section describes how to enable the Nastar to obtain UMTS coverage analysis data. You
to enable the Nastar to import the collected analysis data into the database.
Context
NOTE
MR data is required for the Nastar UMTS coverage analysis. Therefore, the Nastar delivers MML commands
through the data subscription function to enable the RNC-level MR data function and the cell-level MR data
function on RNCs to obtain analysis data. After these functions are enabled, the CPU usage on the Signaling
Processing Units (SPUs) of the RNCs is increased by about 8% relatively. For example, if the SPU CPU usage
is 45%, the increase 8% relatively is equal to the increase 3.6% absolutely, that is 3.6% / 45% = 8%. Other
modules of the RNCs are not affected.
5.3.1 Creating UMTS E2E Tasks

This section describes how to create a E2E task. After you create an E2E task, the Nastar issues
rule files to the M2000 and then the M2000 sends rule files to the related SAU. The SAU performs
the raw data pre-processing tasks through the rule files, and then generate the pre-processed data.
The Nastar create the data collection task automatically to collect the pre-processed data from
the SAU to the Nastar.
Issue 01 (2011-08-15)

60
Nastar
Prerequisite
l
The OSS and NEs related to the analysis task are created. For details, see Creating OSSs
and the Managed NEs.
Configuration data is imported into the Nastar database. For details, see Importing
Configuration Data.
The data source is subscribed and the status is Open.
You are advised to observe the E2E task for five minutes to check whether the task is
executed normally after you create the E2E task by performing the following steps. If
Status of the E2E task is still Running after five minutes, it indicates that the E2E task is
executed normally. If Status of the E2E task is Complete or Failed after five minutes, it
indicates that the E2E task fails to be executed. Note that the Nastar monitors the tasks by
checking the task status on the M2000 at an interval of five minutes.
If the Nastar manages a network involved in different time zones, and if the local time in
the area where the Nastar server is deployed is earlier than the local time in the area where
the SAU is deployed, E2E tasks running on the Nastar will be complete in a four-hour delay.
This ensures that all required data is imported.
Context
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is
displayed.
Step 2 Click New Task. The New Task dialog box is displayed.
TIP
You can also double-click the E2E task in the navigation tree in the E2E Task Management window, or
right-click the E2E task and click New Task, the New Task dialog box is displayed.

1.
In the Task Name field, enter the name of the analysis data E2E task.
2.
In the E2E Task Management > E2E Task List, choose *** Analysis Data Task.
NOTE
If you select the UMTS Uplink Interference Analysis Data Task, you need to set OSS Name to select the
OSS to be analyzed.
Step 4 Click Next.

Step 5 Set Begin Time and End Time, and select one or multiple NEs from the NE list.
CAUTION
You must consider the time zone difference between the Nastar and the SAU when setting the
task execution range. For example: The Nastar delivers an E2E task to be executed from 04:00
to 05:00. The local time on the SAU is two hours later than the local time on the Nastar server.
In this case, the SAU preprocesses and reports the data related to the E2E task to the Nastar
server after 06:00 in the local time on the Nastar server. Therefore, the Nastar completes E2E
tasks in a four-hour delay to ensure that all required data is collected to the Nastar server.
You are advised to create an E2E task one day before creating a theme analysis task.
Issue 01 (2011-08-15)

61
Nastar
The Nastar supports the function of searching for objects in the object navigation tree. After you
click an object in the navigation tree, you can press Ctrl+F to search for and locate an object.
Step 6 Optional: Set the specified parameters of the E2E task. Only some tasks need to perform the
step.
If...
Then...
Creating a UMTS cell performance analysis Click Next, and then set the exception value
data E2E task
for each KPI in the exception value setting
list.
Creating a UMTS service geographic
observation analysis data E2E task
Click Next, set the bad threshold of the

downlink coverage quality.
Creating a UMTS VIP analysis data E2E

task
Click Next, select the VIP groups.
Creating a UMTS terminal analysis data

E2E task
Click Next, and then set the exception value

list.
Creating a UMTS/GSM neighboring cell

analysis data E2E task
Set the start/end BCC, NCC and ARFCN.
If you select Report Raw Data, it indicates

that the Nastar also displays the collected raw
call data when displaying the VIP KPI
aggregation information.
Step 7 Click Complete.

----End
Follow-up Procedure
In the task list on the right of the E2E Task Management window, select one analysis data E2E
task to view, delete, refresh, or cancel it.
If you need to...
Then...
View the selected task
Click Property.
Delete the selected task
Click Delete.
NOTE
The E2E tasks in the running or waiting state cannot be deleted.
Modify the selected task
1. Delete the selected task.

2. Create a new task.
Refresh the selected task
Issue 01 (2011-08-15)
Click Refresh.

62
Nastar
If you need to...
Then...
Cancel the selected task
Right-click a task from the task list in the right pane of the E2E
Task Management window, and then choose Cancel from the
shortcut menu.
NOTE
The E2E tasks in the running or waiting state can be cancelled.
5.3.2 Creating a Data Import Task

This section describes how to create a data import task. The Nastar periodically imports the
analysis data such as the performance data, VIP analysis data, and cell performance analysis
data on the Nastar server into the database to perform various theme analysis tasks.
Prerequisite
Context
l
A data import task is a user-defined scheduled task. You can create only one user-defined
scheduled task of the same type.
The data import task can only be executed periodically. The unit of the task execution period
can be Hour, Day, Week, or Month. The data import task of the same type can only be
created once on the Nastar. After the task is created, the Nastar automatically imports data
at the preset time.
A data import task can be performed only after the related data collection task is complete
(if the data collection task running type is period, only after the first period). Otherwise,
the integrity of the imported data may be affected.
You need to create data import tasks of different types based on the type of an analysis task.
Table 5-2 shows the mapping between analysis task types and types of data import tasks.
Table 5-2 Mapping Between Analysis Task Types and Types of Data Import Tasks
Issue 01 (2011-08-15)
Analysis Task
Type
Data Import Task Type
Manual Creation/Automatic
Creation
GSM MR Analysis
Import GSM Performance

Analysis Data
Manual creation
GSM Neighboring
Cell Analysis

Analysis Data and Import
GSM Measure Task File for
Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation

63
Nastar
Analysis Task
Type
Creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Interference Analysis Data
Manual creation
GSM VIP Analysis
Import GSM VIP Analysis

Data
Manual creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Performance Analysis Data
Manual creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Geographic Observation
Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
Issue 01 (2011-08-15)
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis
Import UMTS IntraFrequency Neighboring Cell

Analysis Data
Manual creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Neighboring Cell Analysis
Data
Manual creation
UMTS Coverage
Analysis
Import UMTS Coverage

Analysis Data
Manual creation
UMTS VIP
Analysis
Import UMTS VIP Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis
Import UMTS Pilot Pollution

Analysis Data
Manual creation

64
Nastar
Analysis Task
Type
Creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis
Import UMTS Terminal

Analysis Data
Manual creation
UMTS Service
Geographic
Analysis
l Import UMTS Sevice

Analysis CHR Data
Manual creation

Analysis MR Data
CDMA Uplink
Interference
Ranking Analysis
Import CDMA Uplink

Interference Analysis - TopN
Analysis Data
Manual creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Interference Analysis Spectrum Analysis Data
Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis
l Import CDMA IntraFrequency Neighboring

Cell Analysis Data (1X)
Manual creation
CDMA Complaint
Analysis Support
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

Pollution Analysis Data
(1X)
Manual creation

Cell Analysis Data
(EVDO)
l Import CDMA Pilot

(EVDO)
CDMA Coverage
Analysis
l Import CDMA Coverage

Analysis Data (1X)
Manual creation

Analysis Data (EVDO)
Issue 01 (2011-08-15)
CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis
Import CDMA VIP analysis

data import function
Manual creation

65
Nastar
Analysis Task
Type
Creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis
Import LTE VIP Analysis

Data
Manual creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis
Import LTE Cell Performance

Analysis Data
Manual creation
LTE Complaint
Analysis Support
LTE Cell Fault

Diagnosis
Analysis
Procedure
Step 3 Set the basic information about the task.
1.
In Task Name, type the name of the data import task.
2.
Select the type of the data import task from Task Type.
For details about how to set Task Type, see Table 5-2.
3.
Select the execution type of the data import task from Execution Type. You can only select
Periodic.

1.
Click . In the displayed Date/Time Selection dialog box, select the start time.
NOTE
Begin Time must be later than the current server time.
2.
Set the task execution period in Period Setting.

----End
Follow-up Procedure
You can select a data import task from the task list in the Task Management window and then
perform operations as required.
Issue 01 (2011-08-15)

66
Nastar
If you need to...
Then...
Delete a task
Click Delete.
NOTE
l You can delete only the tasks that you create. Administrators can delete
all tasks created by users.
l System tasks cannot be deleted.
l Running tasks cannot be deleted.
Suspend a task or
resume a task
Perform operations in either of the following modes:

l Manual mode
Right-click the task, and then choose Suspend or Resume from
the shortcut menu.
l Automatic mode
Right-click the task, and then choose Timely Suspend/Resume
from the shortcut menu. In the Timely Suspend/Resume dialog
box, set Suspend Time and Resume Time.
NOTE
Only the tasks in the Idle state can be suspended, and only the tasks in the
Suspend state can be resumed.
Cancel the execution

of a task
Right-click the task, and then choose Cancel from the shortcut menu.
After the operation is successful, the task status is changed from
Running to Idle.
NOTE
Only the tasks in the Running state can be cancelled.
5.3.3 Checking the Integrity of Analysis Data

This section describes how to check the integrity of analysis data. Before creating an analysis
task, you need to check that the Nastar has imported the required analysis data into the database.
Prerequisite
l
The data import task is performed.
Context
You need to query the data of different types according to the type of an analysis task. Table
5-3 shows the mapping between analysis task types and data types.
Table 5-3 Mapping Between Analysis Task Types and Data Types
Issue 01 (2011-08-15)
Analysis Task Type
Data Type
GSM MR Analysis Task
GSM configuration data and GSM MR analysis data
GSM Neighboring Cell

Analysis Task
GSM configuration data, GSM neighboring cell analysis data

and engineering parameters

67
Nastar
Issue 01 (2011-08-15)
Analysis Task Type
Data Type
GSM/UMTS Neighboring
Cell Analysis Task
GSM configuration data, GSM/UMTS neighboring cell

analysis data and engineering parameters
GSM Frequency Analysis

Task
GSM configuration data, GSM frequency analysis data and

engineering parameters
GSM Uplink Interference

Analysis Task
GSM configuration data and GSM uplink interference

analysis data
GSM VIP Analysis Task
GSM configuration data and GSM VIP analysis data and

GSM Complaint Analysis

Support Task
GSM configuration data
GSM Cell Performance

Analysis Task
GSM configuration data and GSM cell performance analysis

data
GSM Terminal Analysis

Task
GSM configuration data and GSM terminal analysis data
GSM Service Geographic

Analysis Task
GSM configuration data, property matrix, GSM service

geographic observation CHR analysis data, GSM service
geographic observation MR analysis data, and engineering
parameters
UMTS Uplink Interference

Analysis Task
UMTS configuration data and UMTS uplink interference

analysis data
UMTS Intra-Frequency
Task
UMTS configuration data, UMTS neighboring cell analysis

data and engineering parameters
UMTS/GSM Neighboring
Cell Analysis Task
UMTS configuration data, UMTS/GSM neighboring cell


Task
UMTS configuration data and UMTS coverage analysis data
UMTS VIP Analysis Task
UMTS configuration data and UMTS VIP analysis data and

UMTS Complaint Analysis

Support Task
UMTS Pilot Pollution

Analysis Task
UMTS configuration data and UMTS pilot pollution analysis

data
UMTS Cell Performance

Analysis Task
UMTS configuration data and UMTS cell performance

analysis data
UMTS Terminal Analysis

Task
UMTS configuration data and UMTS terminal analysis data

68
Nastar
Analysis Task Type
Data Type
UMTS Service Geographic

Analysis Task
UMTS configuration data, property matrix, UMTS service

geographic observation CHR analysis data, UMTS service
parameters
CDMA Uplink Interference

Analysis Task
CDMA configuration data, CDMA uplink interference

ranking analysis data, and CDMA uplink interference
spectrum analysis data
CDMA Intra-Frequency
Task
CDMA configuration data and CDMA neighboring cell

analysis data (1X services), CDMA neighboring cell analysis
data (EVDO services) and engineering parameters
CDMA Complaint Analysis

Support Task
CDMA configuration data
CDMA Pilot Pollution

Analysis Task
CDMA configuration data and CDMA pilot pollution

analysis data (1X services) or CDMA pilot pollution analysis
data (EVDO services)
CDMA Coverage Analysis

Task
CDMA configuration data and CDMA coverage analysis data

(1X services) or CDMA coverage analysis data (EVDO
services)
CDMA Cell Performance

Analysis Task
CDMA configuration data and CDMA cell performance

analysis data
CDMA VIP Analysis Task
CDMA configuration data and CDMA VIP analysis data and

LTE Coverage Analysis Task
LTE configuration data and LTE coverage analysis data
LTE VIP Analysis Task
LTE configuration data and LTE VIP analysis data and

LTE Terminal Analysis Task
LTE configuration data and LTE terminal analysis data
LTE Cell Performance

Analysis Task
LTE configuration data and LTE cell performance analysis

data
LTE Complaint Analysis

Support Task
LTE configuration data
LTE Cell Fault Diagnosis

Analysis Task
Procedure
Step 1 Double-click System Function > Data Query from the navigation tree in the Analysis Task
Management window. The Query Data window is displayed.
Issue 01 (2011-08-15)

69
Nastar
TIP
Step 2 Set Data Type on the left of the Query Data dialog box.
For details about how to set Data Type, see Table 5-3.
Step 3 Set Select Condition.
Select Condition is optional. You can set the time range only after selecting Is time limit
required.
Step 4 Select the NE object node to be queried in the NE object navigation tree.
Step 5 Click Query.
You can view the analysis data in the right pane of the window.
If no relevant analysis data is displayed, contact Huawei technical support engineers.
----End
5.4 Creating UMTS Coverage Analysis Tasks

This section describes how to create UMTS coverage analysis tasks. After you create a UMTS
coverage analysis task, the Nastar periodically analyze measurement reports (MRs) that are sent
by UEs and saved in the database. By querying the analysis results, you can learn the coverage
of the selected measurement cell and determine network problems such as weak coverage, cross
coverage, and poor service quality.
Prerequisite
l
Analysis data and configuration data are imported into the Nastar database. For details, see
Checking the Integrity of Analysis Data.
An analysis task can be performed only once.
A maximum of 50 tasks of this type can be created, and a maximum of data of seven days
can be involved in an analysis task.
Context
Procedure
Step 1 Click
in the Analysis Task Management window. The New Task dialog box is displayed.
TIP
l Alternatively, you can double-click a theme node from the navigation tree on the Analysis Task
Management window to open the New Task dialog box.
l You can also choose a theme node from the navigation tree on the Analysis Task Management window
and right-click New. The New Task dialog box is displayed.
Step 2 Set the basic task information such as Task Name, Task Type, and Note.
Step 3 Click Next.
Issue 01 (2011-08-15)

70
Nastar
Step 4 Select RNC or NE Group.

Select one or multiple cells on the navigation tree.
You can click any node in the navigation tree and then press Ctrl+F to search for and locate the
required object.
Step 5 Set filtering conditions on the Set parameters tab page.
By default, 12 filtering conditions are provided. Users can add filtering conditions or modify
the existing filtering conditions.
If you need to ...
Then ...
Add a filtering condition
Select a counter of a service, and then set a filtering

condition formula. Then, click Add.
The two-dimensional (2-D) chart supports the setting of
formulas with either one counter or two counters. The
three-dimensional (3-D) chart supports only the setting
of formulas with two counters.
Modify a filtering condition
1. Select a formula to be modified in the filtering

condition display area.
2. Modify the formula in the condition setting area.
3. Click Apply.
Delete a filtering condition
1. Select a formula to be deleted from the filtering

condition display area.
2. Click Delete.
NOTE
Filtering conditions of the tasks whose Status is Running or Stop cannot be modified or deleted.
Step 6 Click Next.

Step 7 Set the Task Type to One-time.
Step 8 Set the time range and the start time of the task.
The existing data is displayed in table on the *** Analysis Data tab page. In a data table, blue
cells indicate that theme data at the current time is normal, yellow cells indicate that configuration
data at the current time is normal, and green cells indicate that both theme data and configuration
data at the current time is normal. The method for specifying the time range varies according to
the selected analysis object.
Issue 01 (2011-08-15)

71
Nastar
If...
Then...
NE is selected
1. Set the time range in either of the following methods:

l Method 1: Set Time Range according to the
existing data status displayed on the *** Analysis
Data tab page.
l Method 2: Specify the analysis time range by
pressing and dragging the mouse in the table on the
*** Analysis Data tab page. The time in Time
Range will automatically refresh to the specified
time.
NOTE
l If no theme data is available in the specified time range,
and if no configuration data is available before the end
time for an analysis task, the task will fail.
l Press and hold the mouse to specify the continuous period
in a line of the table on the *** Analysis Data tab page.
l Press and hold Ctrl+Shift to select multiple lines of data
for analysis.
2. Set Execution Delay.

Set Time Range and Execution Delay.
NE Group is selected
----End
Follow-up Procedure
You can select an analysis task from the task list in the Analysis Task Management window
and then perform operations as required.
TIP
You can choose Theme Function > *** Analysis Task from the navigation tree on the left of the Analysis
Task Management window.
Here, *** indicates the name of a specific analysis task.
If you need to...

Modify a task
Then...
Select a task, and click
, or right-click View/Modify.
Only the tasks in the Waiting or Suspended state can be modified.

Delete a task
Select one or multiple tasks, and click
, or right-click Delete.
The tasks in the Running state cannot be deleted.

Suspended a task
Restore a suspended
task
Issue 01 (2011-08-15)
Select a task in the Waiting state, and click

Suspended.
Select a task in the Suspended state, and click
Resume.

, or right-click
, or right-click
72
Nastar
If you need to...
Then...
Save as the tasks
Right-click Save As to export the task information.
Refresh
Click
, or right-click Refresh to refresh the task status.
5.5 Querying UMTS Coverage Analysis Results

This section describes how to query UMTS coverage analysis reports. You can query the
measurement reports (MRs) sent by UEs within a specific period and then learn about the
coverage situation of the selected measurement cell according to the queried results. This
function helps you determine whether problems such as weak coverage, cross coverage, or poor
service quality exist.
Prerequisite
l
The progress bar of the UMTS coverage analysis task reaches 100%.
Procedure
Step 1 Choose UMTS Coverage Analysis Task from the navigation tree in the Analysis Task
Management window.
If you choose Theme Function, the task list on the right displays all the performance analysis
tasks.
Step 2 Select a task from the task list in the upper right pane.
All the analysis results of the selected task are displayed in the lower right pane.
Step 3 Select an analysis result from the result list on the lower right of the window.
Step 4 Double-click an analysis result, or right-click an analysis result and choose View Analysis
Result from the shortcut menu. The UMTS Coverage Analysis window is displayed.
NOTE
Only the analysis result whose Result Status is Successful can be queried.
Step 5 Query the UMTS coverage analysis results in the UMTS Coverage Analysis window.
1.
Select a cell from RNC Overview Report or NE Group Overview Report from the list
in the left pane.
You can export information about all cells under the selected node by using the export
function in the shortcut menu of the object navigation tree. If you click a cell node, only
information about the selected cell is exported.
You can right-click any object node in the navigation tree and then choose Save As... from
the shortcut menu. In the Save dialog box that is displayed, set the file name and file type,
specify a save path, and then click Save.
Issue 01 (2011-08-15)

73
Nastar
NOTE
l A file can be saved in .csv, .xls, or .xlsx format. The default file type is .csv.
l The fields contained in an exported file are different in the following situations:
l If no filter criterion is specified, an exported file contains the following three fields: Save
Node, Net Element (Group) Name, and Cell Name (Filter Condition:ALL).
l If filter criteria (not including a filter criterion with percentage) are specified, an exported
file contains the following three fields: Save Node, Net Element (Group) Name, and Cell
Name (Filter Condition:***).
l If filter criteria (including a filter criterion with percentage) are specified, an exported file
contains the following four fields: Save Node, Net Element (Group) Name, Cell Name
(Filter Condition:***), and Filter Percentage.
*** indicates the specific filter criterion, for example, AMR:[TP > 5] > 20%.
2.
View the two-dimensional (2-D) chart, three-dimensional (3-D) chart, and counter
overview information list of the selected cell in the right pane.
l On the 2-D chart tab page, AMR, VP, BE, AMR+BE, and other services are displayed
separately on different tab pages. Each tab page displays RSCP, ECNO, and TP of the
current service in bar charts and displays counter distribution in line charts.
The 2-D chart displays counter information with two Y axes. The X axis displays the
counter values. The left Y axis displays the percentage of the MRs of each counter value
to the total MRs. The right Y axis displays the values in the line chart. Each value in
the line chart is the sum of the MR percentages corresponding to all the counter values
equal to or smaller than the current counter value.
l On the 3-D chart tab page, each two of the three counters (RSCP, ECNO, and TP) are
grouped for the PS and CS services and the counter distribution is displayed on different
tab pages.
Different colors are used to differentiate the counter distribution density.
After you specify the value ranges of the two counters corresponding to the X axis and
Y axis in the formula setting area, the Nastar calculates the density sum of counter
distribution in the value range intersection.
l In the overview information table, the counter statistics of all services involved in the
2-D chart are displayed.
l You can right-click any area in a chart and then choose Zoom In, Zoom Out, or Auto
Range to resize the chart accordingly. You can also right-click any area in a chart and
then choose an option from the shortcut menu to perform the corresponding operation,
such as querying the attributes of the chart, saving the chart, or printing the chart.
l You can click any line in the query result list and then press Ctrl+F to search for required
information.
----End
Follow-up Procedure
The query results are exported. You can right-click the result list and then choose Save As from
the shortcut menu to save the current query results as a .csv, .xls, or .xlsx file.
5.6 Exporting UMTS Coverage Analysis Reports

This section describes how to export UMTS coverage analysis reports. You can export the
queried coverage analysis results as .csv or .xls files to determine the coverage of measurement
cells on the network based on the exported analysis results.
Issue 01 (2011-08-15)

74
Nastar
Prerequisite
l
UMTS coverage analysis results are queried. For details, see 5.5 Querying UMTS
Coverage Analysis Results.
Context
Exporting coverage analysis overview refers to exporting the overview table of all the
measurement cells involved in the selected coverage analysis task.
Procedure
l
Perform the following operations as required.

If you need to...
Export coverage analysis overview
information
Then...
1. Click
in the UMTS Coverage
Analysis window. The Save dialog box
is displayed.
2. Specify a save path. Then, click Save.
Export coverage analysis original data

information
1. Click
in the UMTS Coverage
Analysis window. The Save dialog box
is displayed.
2. Specify a save path. Then, click Save.
The progress of an export task is displayed in the Exported File List dialog box. You can
perform other operations during the execution of the export task.
Only one export task can be executed at a time on one client. If more than one export
tasks are created, other tasks are in the waiting state and can be executed only after the
running task is executed completely or canceled.
on the right of the progress bar to cancel an export task in the waiting
You can click
or running state so that the task is terminated and deleted from the task list. You can
click
on the right of the progress bar to delete an export task in the completed state
so that the task is deleted from the task list.
on the right of the progress bar to view detailed information about
You can click
an export task in the completed state.
You can close the Exported File List dialog box and view detailed execution
information about export tasks (including the number of completed tasks, the number
of running tasks, the number of waiting tasks, and the number of failed tasks) in
on the upper right of the Analysis Task Management window.
You can also click any icon to open the Exported File List dialog box to view detailed
task information.
----End
Issue 01 (2011-08-15)

75
Nastar
5.7 Technical Specifications for UMTS Coverage Analysis

This section describes the technical specifications for UMTS coverage analysis.
Item
Task Management Capacity
Number of NE objects supported

by one analysis task
<= 1,000 cells
Number of concurrent tasks
<= 5
Time range of analysis data
<= 7 days
Response time of task execution
Negligible
Number of E2E tasks by one OSS

(all the themes)
<= 200
Number of analysis tasks to be

created of one task type
<= 50
5.8 Reference for the UMTS Coverage Analysis GUI

This section describes the interface for UMTS coverage analysis and the relevant parameters.
Before performing relevant operations, familiarize yourself with the functions of UMTS
coverage analysis.
5.8.1 Interface for UMTS Coverage Analysis

This section describes the interface for UMTS coverage analysis. Before performing relevant
operations, familiarize yourself with the functions of the areas on the interface.
The analysis results of coverage analysis can be displayed in a two-dimensional chart, a threedimensional chart, and a summary table, as shown in Figure 5-2, Figure 5-3 and Figure 5-4.
Issue 01 (2011-08-15)

76
Nastar
Figure 5-2 Interface for the coverage analysis (1)
No. Name
Description
(1)
Button area
The buttons used for exporting the general information

about all the measurement cells.
(2)
Cell object navigation tree
You can precisely locate a cell object through the

navigation tree.
(3)
Search panel
You can precisely locate a cell object through the search

condition.
(4)
Filtering condition area
The system filters counters according to the filtering

formula that is set during the creation of analysis tasks and
then displays the result counters.
(5)
Two-dimensional chart area TAMR, VP, BE, AMR+BE, and other services are
displayed separately on different tab pages. Each tab page
displays RSCP, ECNO, and TP of the current service in
bar charts and displays counter distribution in line charts.
Issue 01 (2011-08-15)

77
Nastar
No. Name
Description
(6)
Three-dimensional chart area In the three-dimensional chart, each two of the three
counters (RSCP, ECNO, and TP) are grouped for the PS
and CS services. Therefore, you can find six tabs in the
chart.
(7)
Formula area
Issue 01 (2011-08-15)
After you type the values of the counters corresponding

to the horizontal and vertical axes in area (6), the system
automatically calculates the sum of the density of the
counter distribution in this overlapped area.

78
Nastar
No. Name
(8)
Description
Summary table area The summary table displays the statistics on the counters that
correspond to the services in the two-dimensional chart.
5.8.2 Parameters for Creating UMTS E2E Tasks

This section describes the parameters for creating UMTS E2E tasks. You can refer to the
description when creating a UMTS E2E task.
Common Information
Parameter
Description
Task Name
Indicates the name of an E2E task.
OSS Name
Indicates the name of the OSS related to the task.

Only when you choose the UMTS uplink interference analysis
data task, you must set the parameter
E2E Task List
Choose the E2E task type from the list.
Begin Time
Indicates the time when the task is executed.

The start time must precede the system time.
Issue 01 (2011-08-15)

79
Nastar
Parameter
Description
End Time
Indicates the time when the task stops running.
NE List
Indicates the NE object related to the task.
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Description
Service Type
Indicates service types involved during the exception

determination, such as Network level.
Exception Type
Indicates the exception types involved during the

exception determination, such as AMR Call setup
failure.
KPI
Indicates the KPIs involved during the exception

determination.
Determination
rule
Indicates the types of exception determination, such

as >=.
Exception Value
Indicates the exception threshold involved during the

exception determination, such as 30
The value is an integer from 0 to 65535.
UMTS VIP
Analysis Data
Task
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Selected
If you select this option, the VIP group can be selected.

If you select the Report Raw Data, this option is also
selected.
Group Name
Indicates the name of a VIP group.
Number of
Members
Indicates the number of members in the VIP group.
Report Raw Data
Indicates that the raw call data is also collected during

the collection of the KPI aggregation information of
all VIP objects of the selected VIP groups, thus
helping to analyze problems thoroughly.
Description
Indicates the description of the VIP group.
Start NCC
Indicates the range of the NCC.
End NCC
Start BCC
Indicates the range of the BCC.
End BCC
Issue 01 (2011-08-15)
ARFCN
Indication
Indicates the frequency band used by a inter-cell.
Start ARFCN
Indicates the range of the ARFCN.

80
Nastar
Parameter
Description
UMTS Service
Geographic
Analysis Data
Task
End ARFCN
The candidate neighboring cell list is determined by

the range of the NCC, BCC and ARFCN.
Downlink Ec/No
(dB)<=X
Indicates the threshold for determining poor coverage

quality on the downlink in the threshold for Traffic of
bad RxQual area.
The Nastar obtains only the data with the downlink
receive quality level smaller than or equal to X.
X indicates the downlink coverage quality. The default
value is -15.
UMTS
Terminal
Analysis Data
Task
Type
Indicates service types of the terminal analysis.
KPI name
Indicates the name of the KPIs.
Criterion
Indicates the relation of the KPI and the KPI threshold.
threshold
Indicates the threshold of a KPI.

In the analysis report of the corresponding task, if the
KPI value of a corresponding user does not reach the
threshold, it is considered that this is a problem KPI
or deteriorated KPI.
This parameter can be null. That is, no threshold is
provided.
5.8.3 Parameters for Creating and Modifying UMTS Coverage

Analysis Tasks
This section describes the parameters for creating and modifying UMTS coverage analysis tasks.
You can refer to the description when creating or modifying a UMTS coverage analysis task.
Task Common Information

Parameter
Description
Task Name
Indicates the name of an analysis task.

The value range is as follows:
l Characters not allowed: ` ~ ! @ # $ % ^ & * ( ) + = { } [ ] \ | ; ' : , . ? / < >
"
l Case sensitive
Task Type
Issue 01 (2011-08-15)
Choose the task type from the navigation tree.

81
Nastar
Parameter
Description
Remarks
Provides the description of the task.

Value range:
l The following characters are not allowed: ~ ! # $ % ^ * + = | \ / , ' `
Task Time Information

Parameter
Description
Task Type
One-time: The system executes the created tasks only once at the specified
time.
Time Range
Only the data generated between the start time and the end time will be
analyzed.
The start time should precede the end time, and the end time should precede
the locale system time.
Delayed
If you do not select it, the system will execute the task immediately.
If you select it, the system will execute the task at the time of the Execution
Delay.
Execution
Delay
Indicates the specified execution time of the task.

The parameter should not precede the end time of the Time Range.
NE Selection Information
Parameter
Description
NE
If you select this option, the navigation tree displays all the NEs of the entire
network.
NE Group
If you select this option, the navigation tree displays all the NE groups of
the entire network.
Parameter Setting Information

Parameter
Description
Filter conditions
Set the filter conditions of the analysis data.

The analysis results will only display the filtered analysis data.
Issue 01 (2011-08-15)

82
Nastar
5.8.4 Parameters for Querying UMTS Coverage Analysis Results

This section describes the parameters for querying UMTS coverage analysis results. You can
refer to the description when querying UMTS coverage analysis results.
Parameter
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Service
Type
AM
R,
VP,
BE,
AM
R
+BE
,
Othe
r
N/A
Indicates the service type for coverage analysis. The coverage

analysis involves the following types of services: AMR, VP, BE,
AMR+BE, and Other.
Total
Number
of TP
Measure
ment
Reports
[0,
+)
Nu
mbe
r
Indicates the total number of TP MRs of the selected cell by service

type.
Total
Number
of RSCP
Measure
ment
Reports
[0,
+)
Nu
mbe
r
Indicates the total number of RSCP MRs of the selected cell by

service type.
Total
Number
of ECNO
Measure
ment
Reports
[0,
+)
Nu
mbe
r
Indicates the total number of Ec/No MRs of the selected cell by

service type.
Average
TP
N/A
N/A
Indicates the average TP of the selected cell by service type in the

selected time segment.
Average
RSCP
(dBm)
[-11
5,-2
5]
dB
m
Indicates the average RSCP of the selected cell by service type in

the selected time segment.
Average
ECNO
(dB)
[-24,
0]
dB
Indicates the average Ec/No of the selected cell by service type in

the selected time segment.

83
Nastar
UMTS Intra-Frequency Neighboring Cell

Analysis
About This Chapter

The UMTS intra-frequency neighboring cell analysis function enables you to obtain UMTS
intra-frequency neighboring cell analysis data, create UMTS intra-frequency neighboring cell
analysis tasks, query UMTS intra-frequency neighboring cell analysis results and possible
UMTS neighboring cell analysis results, and export UMTS intra-frequency neighboring cell
analysis reports from the Nastar. Based on configuration data and engineering parameters, the
Nastar aggregates and analyzes measurement reports (MRs) and events reported by UEs to check
missing and redundant neighboring cell configuration of measurement cells and neighboring
cells whose priorities need to be adjusted. By using this function, the Nastar directly displays
the required information, helping you solve network quality problems that are caused by
redundant or missing neighboring cell configuration or improper configuration of neighboring
cell priorities.
6.1 Basic Knowledge of UMTS Intra-Frequency Neighboring Cell Analysis
This section describes the basic knowledge of UMTS intra-frequency neighboring cell analysis,
such as the UMTS neighboring cell analysis function, application scenarios, and algorithms for
neighboring cell analysis. The basic knowledge helps you perform the operations related to
UMTS intra-frequency neighboring cell analysis.
6.2 UMTS Intra-Frequency Neighboring Cell Analysis Process
This section describes the UMTS intra-frequency neighboring cell analysis process.
6.3 Obtaining UMTS Intra-Frequency Neighboring Cell Analysis Data
This section describes how to enable the Nastar to obtain UMTS intra-frequency neighboring
cell analysis data. You can create an E2E task to enable the Nastar to collect analysis data and
create a data import task to enable the Nastar to import the collected analysis data into the
database.
6.4 Creating UMTS Intra-Frequency Neighboring Cell Analysis Tasks
This section describes how to create UMTS intra-frequency neighboring cell analysis tasks.
After you create a UMTS intra-frequency neighboring cell analysis task, the Nastar periodically
analyzes UMTS neighboring cell analysis data, UMTS configuration data, and engineering
parameters in the database to identify redundant and missing neighboring cell configurations
and neighboring cells whose priorities need to be adjusted. By querying analysis results, you
Issue 01 (2011-08-15)

84
Nastar
can learn about the overall situation of the entire wireless network, quickly locating and solving
network quality problems caused by redundant neighboring cells, missing neighboring cells, or
improper configuration of neighboring cell priorities.
6.5 Querying UMTS Intra-Frequency Neighboring Cell Analysis Results
This section describes how to query UMTS intra-frequency neighboring cell analysis results.
You can query redundant neighboring cells and missing neighboring cells of the dominant cells
and query the neighboring cells whose priorities need to be adjusted to perform corresponding
operations accordingly.
6.6 Querying Possible UMTS Neighboring Cell Analysis Results
This section describes how to query possible UMTS neighboring cell analysis results. Based on
the possible UMTS neighboring cell analysis results, engineering parameters, and configuration
data, you can quickly learn about all the possible neighboring cells of UMTS cells and optimize
neighboring relations.
6.7 Exporting UMTS Intra-Frequency Neighboring Cell Analysis Reports
This section describes how to export UMTS intra-frequency neighboring cell analysis reports.
You can export the queried intra-frequency neighboring cell analysis results as .csv, .xls, or .xlsx
files. The exported analysis results help you configure and optimize neighboring relations on
the network.
6.8 Exporting Possible Neighboring UMTS Cell Analysis Reports
This section describes how to export possible neighboring UMTS cell analysis reports. You can
export the possible neighboring cell analysis results as .csv, .xls, or .xlsx files to help improve
the neighboring relations on the network.
6.9 Technical Specifications for UMTS Intra-frequency Neighboring Cell Analysis
This section describes the technical specifications for UMTS intra-frequency neighboring cell
analysis.
6.10 Reference for the UMTS Intra-Frequency Neighboring Cell Analysis GUI
This section describes the interface for UMTS intra-frequency neighboring cell analysis and the
relevant parameters. Before performing relevant operations, you can familiarize yourself with
the functions of the UMTS intra-frequency neighboring cell analysis.
Issue 01 (2011-08-15)

85
Nastar
6.1 Basic Knowledge of UMTS Intra-Frequency

This section describes the basic knowledge of UMTS intra-frequency neighboring cell analysis,
such as the UMTS neighboring cell analysis function, application scenarios, and algorithms for
UMTS intra-frequency neighboring cell analysis.
6.1.1 UMTS Intra-Frequency Neighboring Cell Analysis

This section describes the UMTS intra-frequency neighboring cell analysis function. With this
function, the Nastar collects and analyzes the measurement reports (MRs) and events reported
by UEs, helping to determine missing and redundant neighboring cells of a measurement cell
and identify the neighboring cells whose priorities need to be adjusted. The MRs can reflect the
actual propagation of radio signals. By displaying required information, the Nastar helps users
solve problems caused by missing or redundant neighboring cell configuration or improper
setting of neighboring cell priorities.

Proper neighboring relations ensure that a UE at the border of a cell initiates a handover in a
timely manner. In this case, handover gain is obtained, and interference inside the network is
reduced. Furthermore, the quality of network services is improved, and network performance is
stable.
Based on configuration data and engineering parameters, the Nastar performs intra-frequency
neighboring cell analysis for the selected measurement cell according to the MRs and events
reported by UEs. Based on obtained measurement data, the Nastar determines missing and
redundant neighboring cells, identifies neighboring cells whose priorities need to be adjusted,
and provides suggestions on adjusting neighboring cell priorities. According to the suggestions
provided by the Nastar, you can compare the suggested neighboring cell priorities and actual
neighboring cell priorities and then adjust the priorities of some neighboring cells accordingly.
Analysis results are displayed in a line chart or a bar chart. Different types of neighboring cells
and final ranking of neighboring cell priorities are displayed in different colors in the chart.
You can export the results of the neighboring cell analysis as a .csv, .xls, or .xlsx file, which
helps to optimize the neighboring relations on the network.
Some cells may share the same frequency and same primary scrambling code (PSC) with the
dominant cell. Therefore, the Nastar first identifies possible neighboring cells from undefined
neighboring cells in the measurement results by UARFCNs and PSCs and then predicts the signal
strength based on cell information including site location, antenna azimuth, and antenna gain.
After identifying possible neighboring cells, the Nastar generates analysis reports about possible
neighboring cells.
In addition, the Nastar can display UMTS neighboring cell analysis results and possible
neighboring cell analysis results on maps and highlight test cells, missing neighboring cells,
redundant neighboring cells, defined and undefined neighboring cells in different colors. This
function helps users query neighboring relationships.
Issue 01 (2011-08-15)

86
Nastar
Limitation and Impact

The following factors may affect the accuracy of neighboring cell analysis results:
l
Accuracy of engineering parameters
Stability of networks in some aspects including setting of air interface parameters and
network topology, during the collection of UMTS neighboring cell analysis data
Table 6-1 describes the network changes and their impacts.
Table 6-1 Network changes and their impacts

Network Change
Impact
Addition or deletion of
BTSs
Affects the network coverage and handovers between cells. In

this case, analysis results cannot accurately reflect the current
network status.
Change of antenna data,

such as azimuth, tilt
angle, or height
Results in changes of cell coverage and network interference.
Change of handover
relations and parameters
Affects the statistical results during the period of collecting the

data about neighboring relations and the period of optimizing
Change of RNC topology

or other NE topology
The RNC is responsible for collecting statistical results.

Therefore, a measurement task cannot be performed properly if
the network topology is changed. You are advised to keep the
network topology unchanged during data collection.
NOTE
The Nastar can measure and analyze UMTS intra-frequency neighboring cells only during soft handovers
or softer handovers.
6.1.2 Algorithms for UMTS Intra-Frequency Neighboring Cell

Analysis
This section describes the algorithms for UMTS intra-frequency neighboring cell analysis, such
as the algorithms used to check missing and redundant neighboring cells and the algorithm used
to provide suggested priorities of neighboring cells.
Neighboring cell analysis algorithms are used to check missing and redundant neighboring cells
and to provide suggested priorities of neighboring cells.
l
The algorithm for providing suggested priorities of neighboring cells is as follows:

1.
Calculate the overall score of each neighboring cell.

The Nastar calculates the overall score of a neighboring cell according to the algorithm
by considering the factors such as the number of times the neighboring cell occurs,
relative difference value between the Ec/Io of the neighboring cell and the Ec/Io of
the dominant cell, and absolute difference value between the Ec/Io of the neighboring
cell and the Ec/Io of the dominant cell.
Issue 01 (2011-08-15)

87
Nastar
2.
Neighboring cells are ranked in descending order based on their overall scores. The
priorities of the neighboring cells are directly proportional to their overall scores.
The highest suggested priority for a neighboring cell is 1.
The algorithm for checking missing neighboring cells is as follows:

If the suggested priority of an undefined neighboring cell is smaller than the number of
suggested neighboring cells, this undefined neighboring cell is considered as a missing
neighboring cell and needs to be configured according to the suggestion.
The algorithm for checking redundant neighboring cells is as follows:

If the suggested priority of a defined neighboring cell is equal to or greater than the number
of suggested neighboring cells, this defined neighboring cell is considered as a redundant
neighboring cell and needs to be deleted according to the suggestion.
6.2 UMTS Intra-Frequency Neighboring Cell Analysis

Process
This section describes the UMTS intra-frequency neighboring cell analysis process.
Figure 6-1 shows the process of UMTS intra-frequency neighboring cell analysis.
Issue 01 (2011-08-15)

88
Nastar
Figure 6-1 Process of UMTS Intra-Frequency Neighboring Cell Analysis
Figure 6-1 describes each procedure shown in Table 6-2.
Issue 01 (2011-08-15)

89
Nastar
Table 6-2 Description of UMTS Intra-Frequency Neighboring Cell Analysis Process

No.
Procedure
Description
Create a UMTS
neighboring cell
data E2E task

measurement task.
Create a UMTS
intra-frequency
neighboring cell
analysis data
import task

Nastar client to open the Task Management window and then
create a UMTS intra-frequency neighboring cell data import
task. After you create the task, the Nastar periodically imports
the UMTS intra-frequency neighboring cell data files saved on
the Nastar server into the database.
Check the
integrity of
UMTS intrafrequency
neighboring cell
analysis data

required UMTS intra-frequency neighboring cell analysis data
is imported into the database.
Create a UMTS
intra-frequency
neighboring cell
analysis task

you can create a UMTS intra-frequency neighboring cell
analysis task. After you create the task, the Nastar periodically
retrieves UMTS intra-frequency neighboring cell analysis data
and UMTS configuration data from the database, analyzes the
retrieved data, and then generates analysis results.
l Query
UMTS
intrafrequency
neighboring
cell analysis
results
You can view the analysis results of the UMTS intra-frequency

neighboring cell analysis tasks that are successfully performed
and add missing neighboring cells, delete redundant neighboring
cells, and adjust the priorities of neighboring cells accordingly.
l Query
possible
UMTS
neighboring
cell analysis
results
6
Issue 01 (2011-08-15)
Export UMTS
intra-frequency
neighboring cell
analysis reports
You can enable the Nastar client to export UMTS intrafrequency neighboring cell analysis results as files.

90
Nastar
6.3 Obtaining UMTS Intra-Frequency Neighboring Cell

Analysis Data
This section describes how to enable the Nastar to obtain UMTS intra-frequency neighboring
cell analysis data. You can create an E2E task to enable the Nastar to collect analysis data and
create a data import task to enable the Nastar to import the collected analysis data into the
database.
Context
NOTE
MR data is required for the Nastar UMTS intra-frequency neighboring cell analysis. Therefore, the Nastar
delivers MML commands through the data subscription function to enable the RNC-level MR data function and
the cell-level MR data function on RNCs to obtain analysis data. After these functions are enabled, the CPU
usage on the Signaling Processing Units (SPUs) of the RNCs is increased by about 8% relatively. For example,
if the SPU CPU usage is 45%, the increase 8% relatively is equal to the increase 3.6% absolutely, that is 3.6% /
45% = 8%. Other modules of the RNCs are not affected.

Prerequisite
l
Configuration Data.
Context
Issue 01 (2011-08-15)

91
Nastar
Procedure
displayed.
TIP

1.
2.
NOTE
OSS to be analyzed.
Step 4 Click Next.

CAUTION
step.
If...
Then...
data E2E task
list.
Issue 01 (2011-08-15)


92
Nastar
If...
Then...

task

E2E task

list.



----End
Follow-up Procedure
If you need to...
Then...
Click Property.
Click Delete.
NOTE

Click Refresh.
shortcut menu.
NOTE

Issue 01 (2011-08-15)

93
Nastar
Prerequisite
Context
l
at the preset time.
Issue 01 (2011-08-15)
Analysis Task
Type
Creation
GSM MR Analysis

Analysis Data
Manual creation
GSM Neighboring
Cell Analysis

Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Manual creation
GSM VIP Analysis

Data
Manual creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Manual creation

94
Nastar
Analysis Task
Type
Creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis

Analysis Data
Manual creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Data
Manual creation
UMTS Coverage
Analysis

Analysis Data
Manual creation
UMTS VIP
Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis

Analysis Data
Manual creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis

Analysis Data
Manual creation
UMTS Service
Geographic
Analysis

Analysis CHR Data
Manual creation

Analysis MR Data
CDMA Uplink
Interference
Ranking Analysis
Issue 01 (2011-08-15)
Import CDMA Uplink

Analysis Data

Manual creation
95
Nastar
Analysis Task
Type
Creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis

Manual creation
CDMA Complaint
Analysis Support
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

(1X)
Manual creation

Cell Analysis Data
(EVDO)
l Import CDMA Pilot

(EVDO)
CDMA Coverage
Analysis

Analysis Data (1X)
Manual creation

Issue 01 (2011-08-15)
CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis

Manual creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis

Data
Manual creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis

Analysis Data
Manual creation
LTE Complaint
Analysis Support

96
Nastar
Analysis Task
Type
Creation
LTE Cell Fault

Diagnosis
Analysis
Procedure
1.
2.
3.
Periodic.

1.
NOTE
2.

----End
Follow-up Procedure
If you need to...
Then...
Delete a task
Click Delete.
NOTE
Issue 01 (2011-08-15)

97
Nastar
If you need to...
Then...
Suspend a task or
resume a task

l Manual mode
the shortcut menu.
l Automatic mode
NOTE

of a task
Running to Idle.
NOTE

Prerequisite
l
Context
Issue 01 (2011-08-15)
Analysis Task Type
Data Type

Analysis Task

Cell Analysis Task


Task


Analysis Task

analysis data

98
Nastar
Issue 01 (2011-08-15)
Analysis Task Type
Data Type


Support Task

Analysis Task

data

Task

Analysis Task

parameters

Analysis Task

analysis data
Task

Cell Analysis Task


Task


Support Task

Analysis Task

data

Analysis Task

analysis data

Task

Analysis Task

parameters

Analysis Task


99
Nastar
Analysis Task Type
Data Type
Task


Support Task

Analysis Task


Task

services)

Analysis Task

analysis data



Analysis Task

data

Support Task

Analysis Task
Procedure
TIP
required.
Issue 01 (2011-08-15)

100
Nastar
Step 5 Click Query.
----End
6.4 Creating UMTS Intra-Frequency Neighboring Cell

Analysis Tasks
This section describes how to create UMTS intra-frequency neighboring cell analysis tasks.
After you create a UMTS intra-frequency neighboring cell analysis task, the Nastar periodically
analyzes UMTS neighboring cell analysis data, UMTS configuration data, and engineering
parameters in the database to identify redundant and missing neighboring cell configurations
and neighboring cells whose priorities need to be adjusted. By querying analysis results, you
can learn about the overall situation of the entire wireless network, quickly locating and solving
network quality problems caused by redundant neighboring cells, missing neighboring cells, or
improper configuration of neighboring cell priorities.
Prerequisite
l
Context
Procedure
Step 1 Click
TIP
Step 3 Click Next.
required object.
Issue 01 (2011-08-15)

101
Nastar
Step 5 On the Set parameters tab page, set Number of Configured Neighboring Cells.
Step 6 Click Next.
If...
Then...
NE is selected

Data tab page.
time.
NOTE
for analysis.


----End
Follow-up Procedure
TIP
Issue 01 (2011-08-15)

102
Nastar
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Save as the tasks
Refresh

Suspended.
Resume.
, or right-click
, or right-click

Click
6.5 Querying UMTS Intra-Frequency Neighboring Cell

Analysis Results
This section describes how to query UMTS intra-frequency neighboring cell analysis results.
You can query redundant neighboring cells and missing neighboring cells of the dominant cells
and query the neighboring cells whose priorities need to be adjusted to perform corresponding
operations accordingly.
Prerequisite
l
The progress bar of the UMTS intra-frequency neighboring cell analysis task reaches 100%.
Procedure
Step 1 Choose UMTS Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in
the Analysis Task Management window.
tasks.
Result from the shortcut menu. The UMTS Intra-Frequency Neighboring Cell Analysis
window is displayed.
Issue 01 (2011-08-15)

103
Nastar
NOTE
Step 5 Query the UMTS intra-frequency neighboring cell analysis results in the UMTS IntraFrequency Neighboring Cell Analysis window.
1.
Select the information about a dominant cell from the neighboring cell overview list in
Area (2).
For details about the area division, see 6.10.1 Interface Description: UMTS IntraFrequency Neighboring-Cell Analysis.
2.
Query information about the selected dominant cell in the right pane.
l Query all the neighboring cells of the selected dominant cell in the neighboring cell
information list in the right pane, that is, Area (3).
The Nastar determines the redundant neighboring cells, missing neighboring cells,
neighboring cells whose priorities need to be adjusted, and neighboring cells requiring
no operations according to the neighboring cell analysis algorithms. The Nastar also
provides related operation suggestions.
For details about the neighboring cell analysis algorithms, see 6.1.2 Algorithms for
UMTS Intra-Frequency Neighboring Cell Analysis.
If the name of a missing neighboring cell of the dominant cell is unknown, the
neighboring cell is marked cellid:p-sc.
Undefined neighboring cells are represented in gray.
l In the lower pane, that is, Area (4), the normal neighboring cells, redundant neighboring
cells, and missing neighboring cells of the selected dominant cell are represented in
different colors. You can select a parameter from the drop-down list box in the upper
right pane so that the parameter values corresponding to each neighboring cell are
displayed on a line chart.
In Area (5), the X axis displays the name of neighboring cells, the left Y axis displays
the overall scores of neighboring cells, and the right Y axis displays parameter values
in the line chart. In the chart, neighboring cells are displayed in descending order
according to their overall scores from left to right.
l You can right-click any area in a chart and then choose Zoom In, Zoom Out, or Auto
Range to resize the chart accordingly. You can also right-click any area in a chart and
then choose an option from the shortcut menu to perform the corresponding operation,
such as querying the attributes of the chart, saving the chart, or printing the chart.
information.
----End
Follow-up Procedure
6.6 Querying Possible UMTS Neighboring Cell Analysis

Results
This section describes how to query possible UMTS neighboring cell analysis results. Based on
the possible UMTS neighboring cell analysis results, engineering parameters, and configuration
Issue 01 (2011-08-15)

104
Nastar
data, you can quickly learn about all the possible neighboring cells of UMTS cells and optimize
Prerequisite
l
The progress bar of the UMTS intra-frequency neighboring cell analysis task reaches 100%.
Procedure
Step 1 Choose UMTS Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in
the Analysis Task Management window.
tasks.
Step 4 Right-click a result record, and then choose Possible neighboring cell analysis from the shortcut
menu. The UMTS Possible Neighboring Cell Analysis Task window is displayed.
NOTE
Step 5 Select a cell record from the possible neighboring cell overview table in the UMTS Possible
Neighboring Cell Analysis Task window.
l All the possible neighboring cells of the selected cell are displayed in the possible neighboring
cell confirmation table on the right.
l To add a possible neighboring cell for the current measurement cell, do as follows:
. The UMTS Possible Neighboring Cell Analysis dialog box is displayed.
1.
Click
2.
Select one or multiple cells from the Cell List navigation tree, and then click OK.
information.
----End
Follow-up Procedure
6.7 Exporting UMTS Intra-Frequency Neighboring Cell

Analysis Reports
This section describes how to export UMTS intra-frequency neighboring cell analysis reports.
You can export the queried intra-frequency neighboring cell analysis results as .csv, .xls, or .xlsx
files. The exported analysis results help you configure and optimize neighboring relations on
the network.
Issue 01 (2011-08-15)

105
Nastar
Prerequisite
l
UMTS intra-frequency neighboring cell analysis results are queried. For details, see 6.5
Querying UMTS Intra-Frequency Neighboring Cell Analysis Results.
Perform the following operations as required:
Procedure
If you need to ...

Export neighboring cell
overview information
Then ...
Click
in the UMTS Intra-Frequency Neighboring
Cell Analysis window.
The main information contained in the files is task name,
creator, start time of the result, end time of the result, and
related information about the measurement cells.
Export all the

neighboring cell analysis Click
Cell
Analysis
window.
results
You are only allowed to save all the neighboring cell analysis
results as .csv, .xls or .xlsx files on the basis of RNC.
The naming convention is Task name_NE
name_WholeNet_NCS.
Export possible
neighboring cell analysis Click
Cell
Analysis
window.
results
name_Possible_NCS.
You can click
click
You can click
Issue 01 (2011-08-15)

106
Nastar

task information.
NOTE
l Exporting neighboring cell overview information refers to exporting the information about all
the dominant cells involved in the selected analysis task.
l Exporting all neighboring cell analysis results refers to exporting the information about the intrafrequency neighboring cells of all dominant cells.
l Exporting possible neighboring cell analysis results refers to exporting the information about the
possible neighboring cells of a specific dominant cell.
----End
6.8 Exporting Possible Neighboring UMTS Cell Analysis

Reports
This section describes how to export possible neighboring UMTS cell analysis reports. You can
export the possible neighboring cell analysis results as .csv, .xls, or .xlsx files to help improve
the neighboring relations on the network.
Prerequisite
l
You have queried the possible neighboring UMTS cell analysis reports.
Context
Exporting the results of the possible neighboring cell analysis refers to the export of all the
information in the possible neighboring cell overview table of the possible neighboring cell
analysis report.
Procedure
Step 1 In the UMTS Possible Neighboring Cell Analysis Task window, click
neighboring cell overview table to open the Save dialog box.
above the possible
Step 2 Set a file name and specify the save path and file type. Then, click Save.
The progress of an export task is displayed in the Exported File List dialog box. You can perform
other operations during the execution of the export task.
l Only one export task can be executed at a time on one client. If more than one export tasks
are created, other tasks are in the waiting state and can be executed only after the running
task is executed completely or canceled.
l You can click
on the right of the progress bar to cancel an export task in the waiting or
running state so that the task is terminated and deleted from the task list. You can click
on the right of the progress bar to delete an export task in the completed state so that the task
is deleted from the task list.
Issue 01 (2011-08-15)

107
Nastar
l You can click

on the right of the progress bar to view detailed information about an
export task in the completed state.
l You can close the Exported File List dialog box and view detailed execution information
about export tasks (including the number of completed tasks, the number of running tasks,
the number of waiting tasks, and the number of failed tasks) in
on the
upper right of the Analysis Task Management window. You can also click any icon to open
the Exported File List dialog box to view detailed task information.
----End
6.9 Technical Specifications for UMTS Intra-frequency

This section describes the technical specifications for UMTS intra-frequency neighboring cell
analysis.
Item

<= 10,000 cells
<= 5
<= 7 days
Negligible

(all the themes)
<= 200

<= 50
6.10 Reference for the UMTS Intra-Frequency Neighboring

Cell Analysis GUI
This section describes the interface for UMTS intra-frequency neighboring cell analysis and the
relevant parameters. Before performing relevant operations, you can familiarize yourself with
the functions of the UMTS intra-frequency neighboring cell analysis.
6.10.1 Interface Description: UMTS Intra-Frequency NeighboringCell Analysis

This section describes the interface for UMTS intra-frequency neighboring-cell analysis. Before
performing relevant operations, you can familiarize yourself with the functions of the areas on
the interface.
The analysis results of intra-frequency neighboring cells can be displayed in tables or in column
charts, as shown in Figure 6-2.
Issue 01 (2011-08-15)

108
Nastar
Figure 6-2 UMTS intra-frequency neighboring-cell analysis interface
No. Name
Description
(1)
Button area
Consists of three buttons that are used for exporting

the overview information about neighboring cells, all
neighboring cell optimization results and all possible
neighboring cells of the test cells.
(2)
Current best cell information list Displays the information related to the current best
cell.
(3)
Neighboring cell list
Displays all the intra-frequency neighboring cells of

the cell selected in area (2).
(4)
Image area
Displays the information about all the neighboring

cells of the selected best cell in the combination of
column charts and line charts.
NOTE
If the name of a missing neighboring cell of the best cell is
unknown, the neighboring cell is marked cellid:p-sc.
Issue 01 (2011-08-15)

109
Nastar

Common Information
Parameter
Description
Task Name
OSS Name

E2E Task List
Begin Time

End Time
NE List
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Description
Service Type

Exception Type

failure.
KPI

determination.
Determination
rule

as >=.
Exception Value

UMTS VIP
Analysis Data
Task
Issue 01 (2011-08-15)
Selected

selected.
Group Name
Number of
Members

110
Nastar
Parameter
Description
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Report Raw Data

Description
Start NCC
End NCC
Start BCC
End BCC
ARFCN
Indication
Start ARFCN

End ARFCN
UMTS Service
Geographic
Analysis Data
Task
Downlink Ec/No
(dB)<=X

bad RxQual area.
value is -15.
UMTS
Terminal
Analysis Data
Task
Type
KPI name
Criterion
threshold

provided.
6.10.3 Parameters for Creating and Modifying UMTS IntraFrequency Neighboring Cell Analysis Tasks
This section describes the parameters for creating and modifying UMTS intra-frequency
neighboring cell analysis tasks. You can refer to the description when creating or modifying a
UMTS intra-frequency neighboring cell analysis task.
Issue 01 (2011-08-15)

111
Nastar

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:

Parameter
Description
Task Type
time.
Time Range
analyzed.
Delayed
Delay.
Execution
Delay

Issue 01 (2011-08-15)
Parameter
Description
NE
network.
NE Group
the entire network.

112
Nastar

Parameter
Description
Number of Configured
Neighboring Cells
Indicates the number of neighboring cells that you are

recommended to configure.
It can be any integer ranging from 0 to 31. The default value
is 30.
6.10.4 Parameters for Querying UMTS Intra-frequency

Neighboring Cell Analysis Results
This section describes the parameters for querying UMTS intra-frequency neighboring cell
analysis results. You can refer to the description when querying UMTS intra-frequency
neighboring cell analysis results.
General Information About a Test Cell
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
RNC ID
[0,+)
N/
A
Indicates the ID of an RNC.
Cell ID
[0,65535]
N/
A
Indicates the ID of a dominant cell.
Cell
Name
1 to 64
characters
N/
A
Indicates the name of a dominant cell, for example, Cell_1.
P-SC
[0,511]
N/
A
Indicates the primary scrambling code of a dominant cell.
Downlin
k
ARFCN
N/A
N/
A
Indicates the downlink absolute radio frequency channel

number (ARFCN) of the dominant cell.
Number
of
Measure
ment
Reports
[0,+)
Nu
mb
er
Indicates the number of MRs received by the dominant cell.
Average
ECNO
(dB)
[-24,0]
dB
Indicates the average ECNO of the dominant cell.
RSCP
(dBm)
[-115,-25]
dB
m
Indicates the average Received Signal Code Power (RSCP)

of the dominant cell.

113
Nastar
Paramet
er
Range
Un
it
Description
Number
of the
1A1C
Events
[0,+)
Nu
mb
er
Indicates the total number of 1A1C events triggered by

neighboring cells.
Number
of
Missing
Neighbor
ing Cells
[0,+)
Nu
mb
er
Indicates the number of missing intra-frequency

neighboring cells among the undefined neighboring cells
Number
of
Redunda
nt
Neighbor
ing Cells
[0,+)
Nu
mb
er
Indicates the number of redundant intra-frequency

neighboring cells among the defined neighboring cells of
the dominant cell.
Number
of
Configur
ed IntraFrequenc
y
Neighbor
ing Cells
[0,+)
Nu
mb
er
Indicates the number of defined intra-frequency

neighboring cells of the dominant cell.
Service
Type of
Cell
N/A
N/
A
Indicates the service type of the current dominant cell, such

as indoor site and outdoor site. Learning the service type
of the current dominant cell helps prevent important
neighboring cells from being mistakenly deleted.
Detailed Information About Neighboring Cells
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
Neighbor
ing RNC
ID
[0,+)
N/
A
Indicates the ID of the RNC that a neighboring cell belongs

to.
Neighbor
ing Cell
ID
0 to 65535
N/
A
Indicates the ID of a neighboring cell.
Neighbor
ing Cell
Name
1 to 64
characters
N/
A
Indicates the name of a neighboring cell, for example,

Cell_1.

114
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
P-SC
[0,511]
N/
A
Indicates the primary scrambling code of a neighboring cell.
Neighbor
ing Cell
Type
N/A
N/
A
Indicates the type of a neighboring cell. The options are

Defined Neighboring Cell (reserved), Defined Neighboring
Cell (redundant), Undefined Neighboring Cell (missing),
and Undefined Neighboring Cell (non-operation).
User
Modify
N/A
N/
A
Indicates whether the user operations are recommended.
Total
Score
N/A
N/
A
Indicates the total score of each neighboring cell. The total

score is calculated using the neighboring cell algorithm
based on each measurement result.
Recomm
ended
Priority
N/A
N/
A
Indicates the recommended priority of a neighboring cell

based on the total score of the neighboring cell. The higher
the total score, the higher is the recommended priority.
Average
RSCP of
Neighbor
ing Cells
(dBm)
[-115,-25]
dB
m
Indicates the average RSCP of a neighboring cell in all MRs

containing the information about this neighboring cell.
Average
ECNO of
Neighbor
ing Cells
(dB)
[-24,0]
dB
Indicates the average ECNO of a neighboring cell in all MRs

containing the information about this neighboring cell.
Average
ECNO of
Primary
Cells
(dB)
[-24,0]
dB
Indicates the average ECNO of the dominant cell in all MRs

containing the current neighboring cell.
Average
RSCP of
Primary
Cells
(dBm)
[-115,-25]
dB
m
Indicates the average RSCP of the best cell in all the

measurement reports that contains the current neighboring
cell.
If this option is selected, you are advised to perform

modification according to Neighboring Cell Type.
Otherwise, no user operation is recommended.

115
Nastar
Paramet
er
Range
Un
it
Description
MR
Number
of the
Neighbor
ing Cell
in the
Monitor
Set/
Detective
Set
[0,+)
Nu
mb
er
Indicates the number of MRs containing the current

neighboring cell in the monitor set or detected set.
MR
Number
of the
Neighbor
ing Cell
in the
Active
Set
[0,+)
Nu
mb
er
Indicates the number of MRs containing the current

neighboring cell in the active set.
Number
of the
1A1C
Events
[0,+)
Nu
mb
er
Indicates the number of 1A1C events triggered by the

current neighboring cell.
Number
of the 1D
Events
[0,+)
Nu
mb
er
Indicates the number of 1D events triggered by the current

neighboring cell.
Distance
(km)
[0,+)
km
Indicates the distance between the dominant cell and the

current neighboring cell.
Neighbor
ing Cell
Service
Type
N/A
N/
A
Indicates the type of a neighboring cell. The options are

indoor and outdoor. Learning the types of neighboring cells
helps prevent important neighboring cells from being
mistakenly deleted.
6.10.5 Parameters for Querying UMTS Possible Neighboring Cell

Analysis Results
This section describes the parameters for querying UMTS possible neighboring cell analysis
results. You can refer to the description when querying UMTS possible neighboring cell analysis
results.
Issue 01 (2011-08-15)

116
Nastar
Possible Neighboring Cell Overview Table
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
RNC ID
of
Dominan
t Cell
[0,
+)
N/A
Indicates the RNC ID of a dominant cell.
Dominan
t Cell ID
[0,6
553
5]
N/A
Dominan
t Cell
Name
1 to
64
char
acter
s
N/A
Indicates the name of a dominant cell, for example, Cell_1.
Dominan
t Cell
ARFCN_
DL
N/A
N/A
Indicates the downlink ARFCNs of a dominant cell.
Dominan
t Cell PSC
[0,5
11]
N/A
Neighbor
ing Cell
P-SC
[0,5
11]
N/A
Indicates the primary scrambling code of a neighboring UMTS

cell.
RNC ID
of the
Selected
Neighbor
ing Cell
[0,
+)
N/A
Indicates the ID of the RNC that the selected possible neighboring

cell belongs to.
Selected
Neighbor
ing Cell
CI
N/A
N/A
Indicates the cell identity of the selected possible neighboring cell.
Selected
Neighbor
ing Cell
Name
1 to
64
char
acter
s
N/A
Indicates the name of the RNC that the selected possible

neighboring cell belongs to.
Distance
(km)
(km)
[0,
+)
km
Indicates the distance between the dominant cell and the selected
possible neighboring cell.

117
Nastar
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Relative
Angle of
Neighbor
ing Cell
[0,3
60]
N/A
Indicates the relative angle between the selected possible

neighboring cell and the dominant cell.
Predicted
Signal
Strength
N/A
N/A
Indicates the signal strength of the selected possible neighboring

cell based on the dimensioning.
Obtain
From
Configur
ation
Data
0, 1
N/A
Indicates whether the selected possible neighboring cell is

obtained from the configuration data.
Number
of
Neighbor
ing Cell
Laps
[0,3]
N/A
Indicates the number of laps between the selected possible

neighboring cell and the dominant cell, that is, the number of cells
between the selected possible neighboring cell and the dominant
cell.
Number
of Cells
with
Same PSC
[0,
+)
Nu
mbe
r
Indicates the number of possible neighboring cells in the possible

neighboring cell pair.
Suggeste
d Priority
N/A
N/A
Indicates the recommended priority of a serving cell based on the

neighboring cell algorithm. The priority value is in inverse
proportion to the priority. There is a high probability that a possible
neighboring cell with a smaller priority value is configured as a
neighboring cell for the serving cell.
Number
of MRs
of
Neighbor
ing Cell
in
Monitor
Set/
Detected
Set
[0,
+)
Nu
mbe
r
Indicates the number of MRs for neighboring cells in the monitor

set and detected set.
Total
Number
of 1A1C
Events
[0,
+)
Nu
mbe
r
Indicates the number of 1A/1C events.

118
Nastar
Possible Neighboring Cell Confirmation Table
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Whether
to Use
N/A
N/A
Indicates whether to select the current possible neighboring cell

as the most possible neighboring cell of the test cell.
Cell
Name
1 to
64
char
acter
s
N/A
Indicates the name of a possible neighboring cell.
RNC ID
[0,
+)
N/A
Indicates the ID of the RNC that a possible neighboring cell

belongs to.
CI
CI
[0,6
553
5]
N/A
Indicates the cell identity of a possible neighboring cell.
Distance
(km)
[0,
+)
km
Indicates the distance between the dominant cell and the selected
possible neighboring cell.
Relative
Angle of
Neighbor
ing Cell
[0,3
60]
N/A
Indicates the relative angle between the selected possible

neighboring cell and the dominant cell.
Predicted
Signal
Strength
N/A
N/A
Indicates the signal strength of the selected possible neighboring

cell based on the dimensioning.
Obtain
From
Configur
ation
Data
N/A
N/A
Indicates whether the selected possible neighboring cell is

obtained from the configuration data.
Number
of
Neighbor
ing Cell
Laps
[0,3]
N/A
Indicates the number of laps between the selected possible

neighboring cell and the dominant cell, that is, the number of cells
between the selected possible neighboring cell and the dominant
cell.

119
Nastar
UMTS/GSM Neighboring Cell Analysis
About This Chapter

The UMTS/GSM neighboring cell analysis function enables you to obtain UMTS/GSM
neighboring cell analysis data, create UMTS/GSM neighboring cell analysis tasks, query UMTS/
GSM neighboring cell analysis results, and export UMTS/GSM neighboring cell analysis results
from the Nastar. The Nastar allows you to check for redundant and missing inter-RAT
neighboring cells. This function helps to solve the network quality problems caused by redundant
and missing neighboring cell configuration.
7.1 Basic Knowledge of UMTS/GSM Neighboring Cell Analysis
This section describes basic knowledge of UMTS/GSM neighboring cell analysis, such as the
UMTS/GSM neighboring cell analysis function, application scenarios, and algorithms for
UMTS/GSM neighboring cell analysis.
7.2 UMTS/GSM Neighboring Cell Analysis Process
This section describes the process of UMTS/GSM neighboring cell analysis.
7.3 Obtaining UMTS/GSM Neighboring Cell Analysis Data
This section describes how to enable the Nastar to obtain UMTS/GSM neighboring cell analysis
data. You can create an E2E task to enable the Nastar to collect analysis data and create a data
import task to enable the Nastar to import the collected analysis data into the database.
7.4 Creating UMTS/GSM Neighboring Cell Analysis Tasks
This section describes how to create UMTS/GSM neighboring cell analysis tasks. After you
create a UMTS/GSM neighboring cell analysis task, the Nastar periodically analyzes UMTS/
GSM neighboring cell analysis data, UMTS configuration data, and engineering parameters in
the Nastar database. By querying the analysis results, you can identify redundant inter-RAT
neighboring cells and missing inter-RAT neighboring cells to locate and solve problems
efficiently.
7.5 Querying UMTS/GSM Neighboring Cell Analysis Results
This section describes how to query UMTS/GSM neighboring cell analysis results. You can
query all the defined and undefined GSM neighboring cells of UMTS cells under some RNCs.
In addition, you can calculate the overall scores of neighboring cells according to the related
algorithm and sort the neighboring cells. The analysis results help you locate redundant and
missing inter-RAT neighboring cells.
Issue 01 (2011-08-15)

120
Nastar
7.6 Querying Possible UMTS/GSM Neighboring Cell Analysis Results

This section describes how to query possible UMTS/GSM neighboring cell analysis results. By
using this function, you can quickly learn about all possible GSM neighboring cells of UMTS
cells based on engineering parameters and configuration data and then optimize neighboring
relations.
7.7 Exporting UMTS/GSM Neighboring Cell Analysis Reports
This section describes how to export UMTS/GSM neighboring cell analysis reports. You can
export the UMTS/GSM neighboring cell analysis reports as .csv, .xls, or .xlsx files to help
optimize the neighboring relations on the network.
7.8 Exporting Possible Neighboring UMTS/GSM Cell Analysis Reports
This section describes how to export possible neighboring UMTS/GSM cell analysis reports.
You can export the possible neighboring cell analysis results as .csv, .xls, or .xlsx files to help
improve the neighboring relations on the network.
7.9 Technical Specifications for UMTS/GSM Neighboring Cell Analysis
This section describes the technical specifications for UMTS/GSM neighboring cell analysis.
7.10 Reference to the Neighboring UMTS/GSM Cell Analysis Interface
This section describes the interface for neighboring UMTS/GSM cell analysis and the relevant
parameters. Before performing relevant operations, familiarize yourself with the functions of
neighboring UMTS/GSM cell analysis.
Issue 01 (2011-08-15)

121
Nastar
7.1 Basic Knowledge of UMTS/GSM Neighboring Cell

Analysis
This section describes basic knowledge of UMTS/GSM neighboring cell analysis, such as the
UMTS/GSM neighboring cell analysis function, application scenarios, and algorithms for
UMTS/GSM neighboring cell analysis.
7.1.1 UMTS/GSM Neighboring Cell Analysis Function

This section describes the UMTS/GSM neighboring cell analysis function. This function is used
to analyze defined and undefined GSM neighboring cells of UMTS cells. Based on the analysis
results, you can check and handle problems caused by redundant or missing neighboring cell
configuration. This function enables the Nastar directly displays the required information,
helping you solve network quality problems that are caused by the redundant or missing
neighboring cell configuration.
Inter-RAT Neighboring Cell Analysis

After you set the conditions for checking the redundant or missing neighboring cell
configurations, the Nastar performs inter-RAT neighboring cell analysis for the selected cell.
The analysis results are displayed in a bar chart. In the bar chart, the defined GSM neighboring
cells, undefined GSM neighboring cells, redundant GSM neighboring cells, and missing GSM
neighboring cells are illustrated in different colors.
The Nastar can export analysis results of inter-RAT neighboring cells to a file. In the inter-RAT
neighboring cell analysis result window, you can export the result file of inter-RAT neighboring
cell analysis after adding the missing neighboring cells and deleting the redundant neighboring
cells. The result file provides the related optimization suggestions.
You can export the results of the inter-RAT neighboring cell analysis as a .csv, .xls, or .xlsx file,
which helps to optimize the neighboring relations on the network.
Requirements for the Network

The network must be stable during the period when neighboring cell data is collected. Otherwise,
the analysis results may be inaccurate. Table 7-1 describes the network changes and their
impacts.
Table 7-1 Network changes and their impacts
Issue 01 (2011-08-15)
Network Change
Impact
Addition or deletion of
BTSs
Affects the network coverage and handovers between cells. In

this case, analysis results cannot accurately reflect the current
network status.
Change of antenna data,

such as azimuth, tilt
angle, or height
Results in changes of cell coverage and network interference.

122
Nastar
Network Change
Impact
Change of handover
relations and parameters
Affects the statistical results during the period of collecting the

data about neighboring relations and the period of optimizing
Change of RNC topology

or other NE topology
The RNC is responsible for collecting statistical results.

Therefore, a measurement task cannot be performed properly if
the network topology is changed. You are advised to keep the
network topology unchanged during data collection.
7.1.2 Algorithms for UMTS/GSM Neighboring Cell Analysis

This section describes the algorithms for UMTS/GSM neighboring cell analysis, such as the
algorithms used to check missing and redundant neighboring cells.
Based on the information reported by UEs such as the signal level of a cell, the Nastar calculates
the overall scores and then sorts defined and undefined GSM neighboring cells. According to
the sequence of GSM neighboring cells and result analysis chart, users can analyze the
neighboring cells depending on the actual network situation, and then provide suggestions on
the missing GSM neighboring cell configuration and redundant GSM neighboring cells to be
deleted.
The algorithm for the UMTS/GSM neighboring cell analysis is as follows:
1.
Calculate the overall scores of all the GSM neighboring cells of the measurement cell.
The sequence of GSM neighboring cells is arranged on the basis of the strength of receive
level. That is, the stronger the signal level is, the smaller the sequence number of the GSM
neighboring cell and the higher the score is. The score is set during the creation of a UMTS/
GSM neighboring cell analysis task.
2.
Determine missing neighboring cells.

When the sequence number of an undefined GSM neighboring cell is smaller than or equal
to Neighboring Cell Count Setting that is set when a UMTS/GSM neighboring cell
analysis task is created, the GSM neighboring cell is regarded as a missing neighboring
cell.
3.
Determine redundant neighboring cells.

When the sequence number of a defined GSM neighboring cell is larger than Neighboring
Cell Count Setting that is set when creating a UMTS/GSM neighboring cell analysis task,
the GSM neighboring cell is regarded as a redundant neighboring cell.
7.2 UMTS/GSM Neighboring Cell Analysis Process

This section describes the process of UMTS/GSM neighboring cell analysis.
Figure 7-1 shows the process of UMTS/GSM neighboring cell analysis.
Issue 01 (2011-08-15)

123
Nastar
Figure 7-1 Process of UMTS/GSM neighboring cell analysis

Table 7-2 Description of UMTS/GSM neighboring cell analysis process
Issue 01 (2011-08-15)
No.
Procedure
Description
Create a
UMTS/GSM
neighboring cell
measurement
data E2E task

measurement task.

124
Nastar
No.
Procedure
Description
Create a UMTS/
GSM
neighboring cell
data import task

create a task for importing UMTS/GSM neighboring cell
measurement task files. After you create the task, the Nastar
periodically imports the UMTS/GSM neighboring cell
measurement task files saved on the Nastar server into the
database.
Check the
integrity
UMTS/GSM
neighboring cell
analysis data

required UMTS/GSM neighboring cell analysis data is imported
into the database.
Create a
UMTS/GSM
neighboring cell
analysis task

you can create a UMTS/GSM neighboring cell analysis task.
After you create the task, the Nastar periodically retrieves
UMTS/GSM neighboring cell measurement data and UMTS
configuration data from the database, analyzes the retrieved data,
and then generates analysis results.
l Query
UMTS/
GSM
neighboring
cell analysis
results
You can view the analysis results of the UMTS/GSM

neighboring cell analysis tasks that are successfully performed
and add missing neighboring cells and delete redundant
neighboring cells accordingly.
l Query
possible
UMTS/
GSM
neighboring
cell analysis
results
6
Export UMTS/
GSM
neighboring cell
analysis reports
You can enable the Nastar client to export UMTS/GSM

neighboring cell analysis results as files.
7.3 Obtaining UMTS/GSM Neighboring Cell Analysis Data

This section describes how to enable the Nastar to obtain UMTS/GSM neighboring cell analysis
Issue 01 (2011-08-15)

125
Nastar
Context
NOTE
MR data is required for the Nastar UMTS/GSM neighboring cell analysis. Therefore, the Nastar delivers MML
commands through the data subscription function to enable the RNC-level MR data function and the cell-level
MR data function on RNCs to obtain analysis data. After these functions are enabled, the CPU usage on the
Signaling Processing Units (SPUs) of the RNCs is increased by about 8% relatively. For example, if the SPU
CPU usage is 45%, the increase 8% relatively is equal to the increase 3.6% absolutely, that is 3.6% / 45% = 8%.
Other modules of the RNCs are not affected.

Prerequisite
l
Configuration Data.
Context
Procedure
displayed.
TIP

1.
2.
Issue 01 (2011-08-15)

126
Nastar
NOTE
OSS to be analyzed.
Step 4 Click Next.

CAUTION
step.
If...
Then...
data E2E task
list.


task

E2E task

list.



----End
Issue 01 (2011-08-15)

127
Nastar
Follow-up Procedure
If you need to...
Then...
Click Property.
Click Delete.
NOTE

Click Refresh.
shortcut menu.
NOTE

Prerequisite
Context
l
at the preset time.
Issue 01 (2011-08-15)

128
Nastar
Analysis Task
Type
Creation
GSM MR Analysis

Analysis Data
Manual creation
GSM Neighboring
Cell Analysis

Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Manual creation
GSM VIP Analysis

Data
Manual creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Manual creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
Issue 01 (2011-08-15)
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis

Analysis Data
Manual creation

129
Nastar
Analysis Task
Type
Creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Data
Manual creation
UMTS Coverage
Analysis

Analysis Data
Manual creation
UMTS VIP
Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis

Analysis Data
Manual creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis

Analysis Data
Manual creation
UMTS Service
Geographic
Analysis

Analysis CHR Data
Manual creation

Analysis MR Data
Issue 01 (2011-08-15)
CDMA Uplink
Interference
Ranking Analysis
Import CDMA Uplink

Analysis Data
Manual creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis

Manual creation
CDMA Complaint
Analysis Support

Cell Analysis Data
(EVDO)

130
Nastar
Analysis Task
Type
Creation
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

(1X)
Manual creation
l Import CDMA Pilot

(EVDO)
CDMA Coverage
Analysis

Analysis Data (1X)
Manual creation

CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis

Manual creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis

Data
Manual creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis

Analysis Data
Manual creation
LTE Complaint
Analysis Support
LTE Cell Fault

Diagnosis
Analysis
Procedure
1.
2.
Issue 01 (2011-08-15)

131
Nastar
3.
Periodic.

1.
NOTE
2.

----End
Follow-up Procedure
If you need to...
Then...
Delete a task
Click Delete.
NOTE
Suspend a task or
resume a task

l Manual mode
the shortcut menu.
l Automatic mode
NOTE

of a task
Running to Idle.
NOTE

Issue 01 (2011-08-15)

132
Nastar
Prerequisite
l
Context
Issue 01 (2011-08-15)
Analysis Task Type
Data Type

Analysis Task

Cell Analysis Task


Task


Analysis Task

analysis data


Support Task

Analysis Task

data

Task

Analysis Task

parameters

Analysis Task

analysis data
Task

Cell Analysis Task


Task

133
Nastar
Issue 01 (2011-08-15)
Analysis Task Type
Data Type


Support Task

Analysis Task

data

Analysis Task

analysis data

Task

Analysis Task

parameters

Analysis Task

Task


Support Task

Analysis Task


Task

services)

Analysis Task

analysis data



Analysis Task

data

134
Nastar
Analysis Task Type
Data Type

Support Task

Analysis Task
Procedure
TIP
required.
Step 5 Click Query.
----End
7.4 Creating UMTS/GSM Neighboring Cell Analysis Tasks

This section describes how to create UMTS/GSM neighboring cell analysis tasks. After you
create a UMTS/GSM neighboring cell analysis task, the Nastar periodically analyzes UMTS/
GSM neighboring cell analysis data, UMTS configuration data, and engineering parameters in
the Nastar database. By querying the analysis results, you can identify redundant inter-RAT
neighboring cells and missing inter-RAT neighboring cells to locate and solve problems
efficiently.
Prerequisite
l
Context
Issue 01 (2011-08-15)

135
Nastar
Procedure
Step 1 Click
TIP
Step 3 Click Next.
required object.
Step 5 On the Parameters Setting tab page, set Analysis Parameter, Possible neighboring cells,
Scores Settings, and Parameters displayed in the result.
Step 6 Click Next.
Issue 01 (2011-08-15)

136
Nastar
If...
Then...
NE is selected

Data tab page.
time.
NOTE
for analysis.

----End
Follow-up Procedure
TIP
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Issue 01 (2011-08-15)

Suspended.
Resume.

, or right-click
, or right-click
137
Nastar
If you need to...
Then...
Save as the tasks
Refresh
Click
7.5 Querying UMTS/GSM Neighboring Cell Analysis

Results
This section describes how to query UMTS/GSM neighboring cell analysis results. You can
query all the defined and undefined GSM neighboring cells of UMTS cells under some RNCs.
In addition, you can calculate the overall scores of neighboring cells according to the related
algorithm and sort the neighboring cells. The analysis results help you locate redundant and
missing inter-RAT neighboring cells.
Prerequisite
l
The progress bar of the UMTS/GSM neighboring cell analysis task reaches 100%.
Procedure
Step 1 Choose UMTS/GSM Neighboring Cell Analysis Task from the navigation tree in the Analysis
tasks.
Result from the shortcut menu. The UMTS/GSM Neighboring Cell Analysis window is
displayed.
NOTE
Step 5 Query the results of UMTS/GSM neighboring cell analysis in the UMTS/GSM Neighboring
Cell Analysis window.
1.
Select a measurement cell from the cell list on the left of the displayed window.
2.
In the GSM neighboring cell list in the right pane, query all the defined and undefined GSM
neighboring cells of the selected measurement cell.
l The Nastar determines the redundant neighboring cells, missing neighboring cells, and
neighboring cells requiring no operations according to the neighboring cell analysis
algorithms. The Nastar also provides related operation suggestions.
l For details about the neighboring cell analysis algorithms, see 7.1.2 Algorithms for
UMTS/GSM Neighboring Cell Analysis.
Issue 01 (2011-08-15)

138
Nastar
l If User Modify is selected in a row in the GSM neighboring cell list, the Nastar saves
the modified list automatically so that you can view the modified information the next
time you open the analysis report. The file with the modification automatically saved
is stored in the installation path of the client. This file is deleted automatically by the
Nastar when the corresponding task is deleted.
l If the possible neighboring cell table of the neighboring cell analysis result is modified
(see the description in 7.6 Querying Possible UMTS/GSM Neighboring Cell Analysis
Results), the information about the undefined neighboring cells in the GSM neighboring
cell list is replaced with the information about the most possible neighboring cell
selected in the possible neighboring cell analysis the next time the neighboring cell
analysis report is opened. The following fields in the report are updated: GSM
Neighboring Cell Name, LAC, CI, and Distance (km).
l You can double-click any area of the GSM neighboring cell list to zoom in on the list,
and then double-click the list again to restore it to the normal size.
3.
The undefined neighboring cells, defined neighboring cells, redundant neighboring cells,
and missing neighboring cells are represented in different colors in the chart area in the
lower pane. You can select a parameter from the drop-down list box in the upper right pane
so that the parameter values corresponding to each neighboring cell are displayed in a line
chart.
The chart displays only the top 32 neighboring cells with the highest integrated priorities.
----End
Follow-up Procedure
7.6 Querying Possible UMTS/GSM Neighboring Cell

Analysis Results
This section describes how to query possible UMTS/GSM neighboring cell analysis results. By
using this function, you can quickly learn about all possible GSM neighboring cells of UMTS
cells based on engineering parameters and configuration data and then optimize neighboring
relations.
Prerequisite
l
The progress bar of the UMTS/GSM neighboring cell analysis task reaches 100%.
Procedure
Step 1 Choose UMTS/GSM Neighboring Cell Analysis Task from the navigation tree in the Analysis
tasks.
Issue 01 (2011-08-15)

139
Nastar
Step 3 Right-click a result record, and then choose UMTS/GSM Possible Neighboring Cell
Analysis from the shortcut menu. The UMTS/GSM Possible Neighboring Cell Analysis
NOTE
Step 4 In the UMTS/GSM Possible Neighboring Cell Analysis window, query the analysis results of
possible UMTS/GSM neighboring cells.
1.
Select the information about a measurement cell from the possible neighboring cell
overview table.
2.
Query all the possible GSM neighboring cells of the selected measurement cell in the
possible neighboring cell confirmation table on the right.
information.
above the possible neighboring cell confirmation table to add possible
l Click
neighboring cells for the measurement cell.
----End
Follow-up Procedure
7.7 Exporting UMTS/GSM Neighboring Cell Analysis

Reports
This section describes how to export UMTS/GSM neighboring cell analysis reports. You can
export the UMTS/GSM neighboring cell analysis reports as .csv, .xls, or .xlsx files to help
optimize the neighboring relations on the network.
Prerequisite
l
UMTS/GSM neighboring cell analysis results are queried. For details, see 7.5 Querying
UMTS/GSM Neighboring Cell Analysis Results.
Perform the following operations as required:
Procedure
Issue 01 (2011-08-15)

140
Nastar
If you need to ...
Then ...
Export neighboring cell overview

information
In the UMTS/GSM Neighboring Cell

Analysis Task window, click
The main information contained in the files

is task name, creator, start time of the result,
end time of the result, and related information
about the measurement cells.
Export neighboring cell optimization
results of a measurement cell
In the UMTS/GSM Neighboring Cell

The main information contained in the files

is task name, creator, start time of the result,
end time of the result, RNC serving the
measurement cell, number and name of the
measurement cell, and information about
defined and undefined GSM neighboring
cells.
Export all the neighboring cell analysis In the UMTS/GSM Neighboring Cell
results
.
You are only allowed to save all the
neighboring cell analysis results as .csv files
on the basis of RNC. The neighboring cell
analysis results of each RNC correspond to
one .csv file.
name_WholeNet_NCS.
You can click
click
You can click
Issue 01 (2011-08-15)

141
Nastar

task information.
NOTE
l Exporting neighboring cell overview information refers to exporting the information about all
the measurement cells involved in the selected analysis task.
l Exporting neighboring cell optimization results of a measurement cell refers to exporting the
information about the defined and undefined neighboring cells of a specific measurement cell.
l Exporting all the neighboring cell analysis results refers to exporting the information about the
defined and undefined neighboring cells of all measurement cells.
----End
7.8 Exporting Possible Neighboring UMTS/GSM Cell

Analysis Reports
This section describes how to export possible neighboring UMTS/GSM cell analysis reports.
You can export the possible neighboring cell analysis results as .csv, .xls, or .xlsx files to help
improve the neighboring relations on the network.
Prerequisite
l
You have queried the possible neighboring UMTS/GSM cell analysis reports.
Context
Exporting the results of the possible neighboring cell analysis refers to the export of all the
information in the possible neighboring cell overview table of the possible neighboring cell
analysis report.
Procedure
Step 1 In the UMTS/GSM Possible Neighboring Cell Analysis Task window, click
possible neighboring cell overview table to open the Save dialog box.
above the
Step 2 Set a file name and specify the save path and file type. Then, click Save.
l You can click
Issue 01 (2011-08-15)

142
Nastar
l You can click

on the
----End
7.9 Technical Specifications for UMTS/GSM Neighboring

Cell Analysis
This section describes the technical specifications for UMTS/GSM neighboring cell analysis.
Item

<= 10,000 cells
<= 5
<= 14 days
Negligible

(all the themes)
<= 200

<= 50
7.10 Reference to the Neighboring UMTS/GSM Cell

Analysis Interface
This section describes the interface for neighboring UMTS/GSM cell analysis and the relevant
neighboring UMTS/GSM cell analysis.
7.10.1 Interface Description: UMTS/GSM Neighboring Cell

Analysis
This section describes the interface for UMTS/GSM neighboring cell analysis. Before
performing relevant operations, familiarize yourself with the rules for dividing areas on the
interface.
The UMTS/GSM neighboring cell analysis results can be displayed in table or in histogram
mode, as shown in Figure 7-2.
Issue 01 (2011-08-15)

143
Nastar
Figure 7-2 Interface for the UMTS/GSM neighboring cell analysis
No.
Name
Description
(1)
List of current
measurement cell
information
Displays the information about the current

measurement cell.
(2)
Neighboring cell list
Displays all the neighboring GSM cells of the cell

selected in Area (1).
(3)
Image area
Displays the information about all the neighboring

GSM cells of the selected measurement cell in the
combination of column charts and line charts.
(4)
Button area
Three buttons are provided to export all information

about the neighboring cell, the neighboring cell
optimization results of the measurement cell, and all
neighboring cell optimization results.
7.10.2 Interface Description: Possible Neighboring UMTS/GSM

Cell Analysis
This section describes the interface for possible neighboring UMTS/GSM cell analysis. Before
performing relevant operations, familiarize yourself with the functions of the areas on the
interface.
The possible neighboring cell analysis result is displayed in tables, which consist of a possible
neighboring cell overview table and a possible neighboring cell confirmation table, as shown in
Figure 7-3.
Issue 01 (2011-08-15)

144
Nastar
Figure 7-3 Interface of analyzing possible neighboring UMTS/GSM cells
No.
Name
Description
(1)
Possible neighboring
cell overview table
Displays the aggregation information of possible

neighboring GSM cells of all the cells involved in the task
in a table.
(2)
Possible neighboring
cell confirmation table
Displays all the possible neighboring GSM cells of the cell

selected in Area (1).

Common Information
Parameter
Description
Task Name
OSS Name

E2E Task List
Begin Time

Issue 01 (2011-08-15)

145
Nastar
Parameter
Description
End Time
NE List
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Description
Service Type

Exception Type

failure.
KPI

determination.
Determination
rule

as >=.
Exception Value

UMTS VIP
Analysis Data
Task
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Selected

selected.
Group Name
Number of
Members
Report Raw Data

Description
Start NCC
End NCC
Start BCC
End BCC
Issue 01 (2011-08-15)
ARFCN
Indication
Start ARFCN

146
Nastar
Parameter
Description
UMTS Service
Geographic
Analysis Data
Task
End ARFCN

Downlink Ec/No
(dB)<=X

bad RxQual area.
value is -15.
UMTS
Terminal
Analysis Data
Task
Type
KPI name
Criterion
threshold

provided.
7.10.4 Parameters for Creating and Modifying Neighboring UMTS/

GSM Cell Analysis Tasks
This section describes the parameters for creating and modifying neighboring UMTS/GSM cell
analysis tasks. You can refer to the description when creating and modifying a neighboring
UMTS/GSM cell analysis task.

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Issue 01 (2011-08-15)

147
Nastar
Parameter
Description
Remarks
Value range:

Parameter
Description
Task Type
time.
Time Range
analyzed.
Delayed
Delay.
Execution
Delay

Issue 01 (2011-08-15)
Parameter
Description
NE
network.
NE Group
the entire network.

148
Nastar

Parameter
Description
Neighboring Cell Count
Indicates the threshold of the neighboring cell sequence

number. All the undefined neighboring cells whose sequence
numbers are smaller than or equal to the value of this
parameter are regarded as missing neighboring cells. All the
defined neighboring cells whose sequence numbers are larger
than the value of this parameter are regarded as redundant
neighboring cells.
Indicates the omnidirectional gain of an antenna.
Omni gain

Unit: dBi
Directional gain
Indicates the directional gain of an antenna.

Unit: dBi
RankingNScore
Indicates the scores of the neighboring cell ranking No.1 to 8.

This parameter can be set to any integer from 0 to 100. In
addition, the neighboring cell with a small sequence number
must obtain a higher score than that of the neighboring cell
with a large sequence number.
Number of undefined
neighboring cells to be
displayed
Indicates that only the TopN undefined neighboring cells are

displayed.
N can be any integer from 20 to 50. The default value is 30.
7.10.5 Parameters for Querying UMTS/GSM Neighboring Cell

Results
This section describes the parameters for querying UMTS/GSM neighboring cell results. You
can refer to the description when querying UMTS/GSM neighboring cell results.
Parameters About a Test Cell
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
RNC ID
[0,+)
N/
A
Indicates the ID of the RNC that the dominant cell

belongs to.

149
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
Cell ID
[0,65535]
N/
A
Cell
Name
1 to 64
characters
N/
A
Indicates the name of a dominant cell, for example,

Cell_1.
P-SC
[0,511]
N/
A
ARFCN_
DL
N/A
N/
A
Indicates the downlink ARFCNs of a dominant cell.
Number
of MRs
[0,+)
N/
A
Indicates the total number of MRs received by each

dominant cell.
Number
of
Redunda
nt
Neighbor
ing Cells
[0,+)
N/
A
Indicates the number of redundant neighboring GSM

cells of the current dominant cell.
Number
of
Missing
Neighbor
ing Cells
[0,+)
N/
A
Indicates the number of missing neighboring GSM cells

of the current dominant cell.
Number
of
Configur
ed
Neighbor
ing GSM
Cells
[0,+)
N/
A
Indicates the number of defined neighboring GSM cells

Service
Type of
Serving
Cell
N/A
N/
A
Indicates the service type of the current dominant cell,

such as indoor site and outdoor site. Learning the service
type of the dominant cell helps prevent important
neighboring cells from being mistakenly deleted.

150
Nastar
Parameters About the Neighboring GSM Cells

Paramet
er
Range
U
ni
t
Description
BSC
Where
Test Cell
Is
Located
N/A
N/
A
Indicates the name of the BSC that a neighboring

GSM cell belongs to.
LAC
LAC [1,65533],
[65535]
N/
A
Indicates the location area code of a neighboring

GSM cell.
CI
CI [0,65535]
N/
A
Indicates the cell identity of a neighboring GSM

cell.
Cell
Name
1 to 64 characters
N/
A
Indicates the name of a defined or undefined

neighboring GSM cell of the current dominant cell.
BCCH
[0,1023]
N/
A
Indicates the broadcast control channel of a

neighboring GSM cell.
1 to 124: belong to PGSM; 128 to 251:

belong to GSM850;
0, 975 to 1023:
belong to E-GSM;
955 to 974: belong to
R-GSM; 811 to 885:
belong to DCS1800;
512 to 810: belong to
DCS1800 when the
high band supports
DCS1800; 512 to
810: belong to
PCS1900 when the
high band supports
PCS1900.
Issue 01 (2011-08-15)
BSIC
N/A
N/
A
Indicates the base station identity code of a

Defined
Neighbor
ing Cell
1 to 64 characters
N/
A
Indicates whether the selected cell is the defined

neighboring cell of the current dominant cell.
Suggeste
d
Operatio
n
N/A
N/
A
Indicates the operation suggestions provided by the

Nastar on a neighboring cell.
Values for this option are Missing Neighboring
Cell, Redundant Neighboring Cell, and No
operation.

151
Nastar
Paramet
er
Range
U
ni
t
Description
User
Modify
N/A
N/
A
Indicates whether the user operations are

recommended.
If this option is selected, you are advised to perform
modification according to Suggested Operation.
Otherwise, no user operation is recommended.
Issue 01 (2011-08-15)
Total
Score
N/A
N/
A
Indicates the total score of each neighboring cell

based on the measurement result according to the
neighboring cell algorithm.
Final
Priority
N/A
N/
A
Indicates the final sequence of priorities adjusted

on the basis of suggested priorities.
Suggeste
d Priority
N/A
N/
A
Indicates the suggested priorities provided on the

basis of total score of neighboring cells. The higher
the total score is, the higher the suggested priority
is.
Average
Receive
Level of
A
Neighbor
ing Cell
Ranking
No.1 in
MRs
(dBm)
N/A
N/
A
Indicates the average receive signal strength of a

neighboring GSM cell ranking No.1 in MRs.
Number
of
Measure
ment
Reports
[0,+)
N/
A
Indicates the number of MRs related to the current

Distance
(km)
[0,+)
N/
A
Indicates the distance between the current dominant

cell and a neighboring GSM cell.
Service
Type of
Neighbor
ing Cell
N/A
N/
A
Indicates the service type of a neighboring GSM

cell, such as indoor site and outdoor site. Learning
the service type of the neighboring GSM cell helps
prevent important neighboring cells from being
mistakenly deleted.

152
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
U
ni
t
Description
Number
of Times
A
Neighbor
ing Cell
Ranking
No.1 in
MRs
[0,+)
N/
A
Indicates the number of times a cell ranking No.1

in the neighboring cell list.
Number
of Times
A
Neighbor
ing Cell
Ranking
No.2 in
MRs
[0,+)
N/
A

Number
of Times
A
Neighbor
ing Cell
Ranking
No.3 in
MRs
[0,+)
N/
A

Number
of Times
A
Neighbor
ing Cell
Ranking
No.4 in
MRs
[0,+)
N/
A

Number
of Times
A
Neighbor
ing Cell
Ranking
No.5 in
MRs
[0,+)
N/
A


153
Nastar
Paramet
er
Range
U
ni
t
Description
Number
of Times
A
Neighbor
ing Cell
Ranking
No.6 in
MRs
[0,+)
N/
A

Number
of Times
A
Neighbor
ing Cell
Ranking
No.7 in
MRs
[0,+)
N/
A

Number
of Times
A
Neighbor
ing Cell
Ranking
No.8 in
MRs
[0,+)
N/
A

7.10.6 Parameters for Querying UMTS/GSM Possible Neighboring

Cell Results
This section describes the parameters for querying UMTS/GSM possible neighboring cell
results. You can refer to the description when querying UMTS/GSM possible neighboring cell
results.
Possible Neighboring Cell Overview Table
Issue 01 (2011-08-15)
Paramet
er
Range
U
ni
t
Description
RNC ID
[0,+)
N/
A
Indicates the ID of the RNC that the dominant

cell belongs to.
Cell ID
[0,65535]
N/
A

154
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
U
ni
t
Description
Cell
Name
1 to 64 characters
N/
A
Indicates the name of a dominant cell, for

example, Cell_1.
ARFCN_
DL
N/A
N/
A
Indicates the downlink ARFCNs of a dominant

cell.
P-SC
[0,511]
N/
A
Indicates the primary scrambling code of a

dominant cell.
Neighbor
ing Cell
BCCH
[0,1023]
N/
A
Indicates the broadcast control channel of a

Neighbor
ing Cell
BSIC
Consists of NCC[0,7]
and BCC[0,7].
N/
A
Indicates the base station identity code of a

BSC ID
of the
Selected
Possible
Neighbor
ing Cell
N/A
N/
A
Indicates the name of the BSC that the selected

possible neighboring GSM cell belongs to.
Possible
Neighbor
ing Cell
Name
1 to 64 characters
N/
A
Indicates the name of the selected possible

Neighbor
ing Cell
CGI
Consists of MCC
[000,999], MNC
[000,999], LAC
[1,65533],[65535], and
CI [0,65535].
N/
A
Indicates the global ID of the selected possible

LAC
LAC [1,65533],[65535]
N/
A
Indicates the location area code of the selected

possible neighboring GSM cell.
CI
CI [0,65535]
N/
A
Indicates the cell identity of the selected

possible neighboring GSM cell.
1 to 124: belong to PGSM; 128 to 251: belong

to GSM850; 0, 975 to
1023: belong to E-GSM;
955 to 974: belong to RGSM; 811 to 885: belong
to DCS1800; 512 to 810:
belong to DCS1800
when the high band
supports DCS1800; 512
to 810: belong to
PCS1900 when the high
band supports PCS1900.
BSIC=NCC*10+BCC

155
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
U
ni
t
Description
Distance
[0,+)
k
m
Indicates the distance from the dominant cell to

the selected possible neighboring GSM cell.
Relative
Angle of
Neighbor
ing Cell
[0,360]
N/
A
Indicates the relative angle between the selected

possible neighboring GSM cell and the
dominant cell.
Predicted
Signal
Strength
N/A
N/
A
Indicates the signal strength of the selected

possible neighboring GSM cell based on the
dimensioning.
Obtain
From
Configur
ation
Data
N/A
N/
A
Indicates whether the selected possible

neighboring GSM cell is obtained from the
configuration data.
Number
of
Neighbor
ing Cell
Laps
[0,3]
N/
A
Indicates the number of laps between the

selected possible neighboring GSM cell and the
dominant cell, that is, the number of cells
between the selected possible neighboring
GSM cell and the dominant cell.
Number
of
Possible
Neighbor
ing Cells
in the
Possible
Neighbor
ing Cell
Pairs
[0,+)
N/
A
Indicates the number of possible neighboring

cells in the possible neighboring GSM cell pair.
Number
of
Measure
ment
Reports
[0,+)
N/
A
Indicates the number of MRs of the current

Total
Score
N/A
N/
A
Indicates the total score of each neighboring cell

based on the measurement result according to
the neighboring cell algorithm.

156
Nastar
Possible Neighboring Cell Confirmation Table

Paramet
er
Range
U
ni
t
Description
Whether
to Use
N/A
N/
A
Indicates whether to select the current possible

neighboring UMTS cell as the most possible
neighboring cell of the test cell.
If the parameter is selected, the current possible
neighboring UMTS cell serves as the most
possible neighboring UMTS cell of the test cell.
In addition, you must replace the information
about the selected possible neighboring cell in the
possible neighboring cell confirmation table with
the corresponding information in the possible
neighboring cell overview table.
If this parameter is not selected, the most possible
neighboring cell is not determined. In addition,
the system clears all the information in the fields
in the possible neighboring cell overview table.
Issue 01 (2011-08-15)
Cell
Name
1 to 64 characters
N/
A
Indicates the name of a possible neighboring

GSM cell.
BSC
N/A
N/
A
Indicates the name of the BSC that a possible

neighboring GSM cell belongs to.
CGI
Consists of MCC
N/
[000,999], MNC
A
[000,999], LAC
[1,65533],[65535], and
CI [0,65535].
Indicates the global ID that a possible

neighboring GSM cell belongs to.
Neighbor
ing Cell
LAC
LAC [1,65533],
[65535]
N/
A
Indicates the location area code of a possible

Neighbor
ing Cell
CI
CI [0,65535]
N/
A
Indicates the cell identity of a possible

Distance
[0,+)
k
m
Indicates the distance between the dominant cell

and a possible neighboring GSM cell.
Relative
Angle of
Neighbor
ing Cell
[0,360]
N/
A
Indicates the relative angle between the dominant

cell and a possible neighboring GSM cell.
Predicted
Signal
Strength
N/A
N/
A
Indicates the signal strength of a possible

neighboring GSM cell based on the
dimensioning.

157
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
U
ni
t
Description
Obtain
From
Configur
ation
Data
N/A
N/
A
Indicates whether the possible neighboring GSM

cell is obtained from the configuration data.
Number
of
Neighbor
ing Cell
Laps
[0,3]
N/
A
Indicates the number of laps between the

dominant cell and a possible neighboring GSM
cell, that is, the number of cells between the
dominant cell and a possible neighboring GSM
cell.

158
Nastar
UMTS Pilot Pollution Analysis
About This Chapter

The UMTS pilot pollution analysis function enables you to obtain UMTS pilot pollution analysis
data, create UMTS pilot pollution analysis tasks, query UMTS pilot pollution analysis results,
and export UMTS pilot pollution analysis reports from the Nastar. By analyzing subscriber calls,
the Nastar identifies cells where pilot pollution exists, cells that cause interference, and severity
of cell pollution. The Nastar also displays the analysis results on a map so that you can learn the
detailed situation of pilot pollution. This function reduces the drive test (DT) time and improves
the accuracy of problem location.
8.1 Basic Knowledge of UMTS Pilot Pollution Analysis
The UMTS pilot pollution analysis function enables you to analyze routine calls. By analyzing
query reports, the Nastar identifies cells where pilot pollution exists, cells that cause interference,
and severity of cell pollution and displays the analysis results on a map. In this manner, you can
directly learn the details about pilot pollution.
8.2 UMTS Pilot Pollution Analysis Process
This section describes the UMTS pilot pollution analysis process.
8.3 Obtaining UMTS Pilot Pollution Analysis Data
This section describes how to enable the Nastar to obtain UMTS pilot pollution analysis data.
You can create an E2E task to enable the Nastar to collect analysis data and create a data import
task to enable the Nastar to import the collected analysis data into the database.
8.4 Creating UMTS Pilot Pollution Analysis Tasks
This section describes how to create UMTS pilot pollution analysis tasks. After you create a
UMTS pilot pollution analysis task, the Nastar identifies cells where pilot pollution exists, cells
that cause interference, and severity of cell pollution by obtaining subscriber call records. This
function helps to solve the pilot pollution caused by factors such as cross coverage, reducing the
drive test (DT) time and improving the accuracy of problem location.
8.5 Querying UMTS Pilot Pollution Analysis Results
This section describes how to query UMTS pilot pollution analysis results. The Nastar identifies
cells where pilot pollution exists, cells that cause interference, and severity of cell pollution by
obtaining the subscriber call records. This function helps you solve the pilot pollution caused
by factors such as cross coverage.
8.6 Exporting UMTS Pilot Pollution Analysis Reports
Issue 01 (2011-08-15)

159
Nastar
This section describes how to export UMTS pilot pollution analysis reports. You can export the
queried pilot pollution analysis results as .csv, .xls, or .xlsx files. The exported analysis results
help you determine cells where pilot pollution exists, cells that cause interference, and severity
of cell pollution.
8.7 Technical Specifications for UMTS Pilot Pollution Analysis
This section describes the technical specifications for UMTS pilot pollution analysis.
8.8 Reference to the UMTS Pilot Pollution Analysis Interface
This section describes the interface for UMTS pilot pollution analysis and the relevant
UMTS pilot pollution analysis.
Issue 01 (2011-08-15)

160
Nastar
8.1 Basic Knowledge of UMTS Pilot Pollution Analysis

The UMTS pilot pollution analysis function enables you to analyze routine calls. By analyzing
query reports, the Nastar identifies cells where pilot pollution exists, cells that cause interference,
and severity of cell pollution and displays the analysis results on a map. In this manner, you can
directly learn the details about pilot pollution.
Pilot pollution refers to the situation that there are excessive signals with close strength in an
area in a network using code division multiple access (CDMA) technology. Generally, excessive
radio signals form a cross coverage to the neighboring cells due to improper site layout or impacts
of geographical locations. In this case, pilot pollution is produced.
The pilot pollution affects network performance in the following aspects:
l
Reduced call connection ratio

When there is pilot pollution, the UE constantly performs cell reselection because it cannot
stably camp on a cell. During a call, the UE constantly changes serving cells, leading to
call failure easily.
Increased call drop rate

When there is pilot pollution, ping-pong hangovers occur frequently during a call because
the pilot is not strong enough to be the dominant pilot. As a result, the call drop rate
increases.
Reduced system capacity

Pilot pollution causes strong interference. Hence, the receive sensitivity of the system is
improved, and thus signals far away from the NodeB cannot be received. As a result, the
system capacity is reduced.
High Block Error Rate (BLER)

When there is pilot pollution, there is strong interference. Hence, the BLER is increased,
leading to the deterioration of the voice quality and the decrease in the data transmission
rate.
Severe pilot pollution may cause problems such as call drops, deteriorated voice quality, reduced
system capacity, and network interference. Based on routine calls, the Nastar analyzes the pilot
pollution, thus helping in locating polluted cells and polluter cells. Used with the GIS, this
function enables the Nastar to display polluted cells and polluter cells in geographic mode, thus
improving the efficiency of problem analysis and location.
8.2 UMTS Pilot Pollution Analysis Process

This section describes the UMTS pilot pollution analysis process.
Figure 8-1 shows the process of UMTS pilot pollution analysis.
Issue 01 (2011-08-15)

161
Nastar
Figure 8-1 Process of UMTS pilot pollution analysis

Table 8-1 Description of UMTS pilot pollution analysis process
Issue 01 (2011-08-15)
No.
Procedure
Description
Create a UMTS
pilot pollution
analysis data
E2E task

measurement task.

162
Nastar
No.
Procedure
Description
Create a UMTS
pilot pollution
analysis data
import task

create a UMTS pilot pollution analysis data import task. After
you create the task, the Nastar periodically imports the pilot
pollution analysis data files saved on the Nastar server into the
database.
Check the
integrity of
UMTS pilot
pollution
analysis data

required UMTS pilot pollution analysis data is imported into the
database.
Create a UMTS
pilot pollution
analysis task

you can create a pilot pollution analysis task. After you create
the task, the Nastar retrieves UMTS pilot pollution analysis data
and UMTS configuration data from the database, analyzes the
data, and then generates analysis results.
Query UMTS
pilot pollution
analysis results
You can view the analysis results of the UMTS pilot pollution
analysis tasks that are executed successfully and also perform
comprehensive analysis by map.
In addition, you can export the result files through the one-click
method in the analysis result query interface.
Export UMTS
pilot pollution
analysis reports
You can enable the Nastar client to export UMTS pilot pollution
8.3 Obtaining UMTS Pilot Pollution Analysis Data

This section describes how to enable the Nastar to obtain UMTS pilot pollution analysis data.
Context
NOTE
MR data is required for the Nastar UMTS pilot pollution analysis. Therefore, the Nastar delivers MML
commands through the data subscription function to enable the RNC-level MR data function and the cell-level
MR data function on RNCs to obtain analysis data. After these functions are enabled, the CPU usage on the
Signaling Processing Units (SPUs) of the RNCs is increased by about 8% relatively. For example, if the SPU
CPU usage is 45%, the increase 8% relatively is equal to the increase 3.6% absolutely, that is 3.6% / 45% = 8%.
Other modules of the RNCs are not affected.

Issue 01 (2011-08-15)

163
Nastar
Prerequisite
l
Configuration Data.
Context
Procedure
displayed.
TIP

1.
2.
NOTE
OSS to be analyzed.
Step 4 Click Next.

Issue 01 (2011-08-15)

164
Nastar
CAUTION
step.
If...
Then...
data E2E task
list.


task

E2E task

list.



----End
Follow-up Procedure
Issue 01 (2011-08-15)

165
Nastar
If you need to...
Then...
Click Property.
Click Delete.
NOTE

Click Refresh.
shortcut menu.
NOTE

Prerequisite
Context
l
at the preset time.
Issue 01 (2011-08-15)
Analysis Task
Type
Creation
GSM MR Analysis

Analysis Data
Manual creation

166
Nastar
Analysis Task
Type
Creation
GSM Neighboring
Cell Analysis

Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Manual creation
GSM VIP Analysis

Data
Manual creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Manual creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
Issue 01 (2011-08-15)
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis

Analysis Data
Manual creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Data
Manual creation
UMTS Coverage
Analysis

Analysis Data
Manual creation

167
Nastar
Analysis Task
Type
Creation
UMTS VIP
Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis

Analysis Data
Manual creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis

Analysis Data
Manual creation
UMTS Service
Geographic
Analysis

Analysis CHR Data
Manual creation

Analysis MR Data
CDMA Uplink
Interference
Ranking Analysis
Import CDMA Uplink

Analysis Data
Manual creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis

Manual creation
CDMA Complaint
Analysis Support
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

(1X)
Manual creation

Cell Analysis Data
(EVDO)
l Import CDMA Pilot

(EVDO)
Issue 01 (2011-08-15)

168
Nastar
Analysis Task
Type
Creation
CDMA Coverage
Analysis

Analysis Data (1X)
Manual creation

CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis

Manual creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis

Data
Manual creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis

Analysis Data
Manual creation
LTE Complaint
Analysis Support
LTE Cell Fault

Diagnosis
Analysis
Procedure
1.
2.
3.
Periodic.

1.
Click
Issue 01 (2011-08-15)

169
Nastar
NOTE
2.

----End
Follow-up Procedure
If you need to...
Then...
Delete a task
Click Delete.
NOTE
Suspend a task or
resume a task

l Manual mode
the shortcut menu.
l Automatic mode
NOTE

of a task
Running to Idle.
NOTE

Prerequisite
l
Issue 01 (2011-08-15)

170
Nastar
Context
Issue 01 (2011-08-15)
Analysis Task Type
Data Type

Analysis Task

Cell Analysis Task


Task


Analysis Task

analysis data


Support Task

Analysis Task

data

Task

Analysis Task

parameters

Analysis Task

analysis data
Task

Cell Analysis Task


Task


Support Task

171
Nastar
Issue 01 (2011-08-15)
Analysis Task Type
Data Type

Analysis Task

data

Analysis Task

analysis data

Task

Analysis Task

parameters

Analysis Task

Task


Support Task

Analysis Task


Task

services)

Analysis Task

analysis data



Analysis Task

data

Support Task

Analysis Task

172
Nastar
Procedure
TIP
required.
Step 5 Click Query.
----End
8.4 Creating UMTS Pilot Pollution Analysis Tasks

This section describes how to create UMTS pilot pollution analysis tasks. After you create a
UMTS pilot pollution analysis task, the Nastar identifies cells where pilot pollution exists, cells
that cause interference, and severity of cell pollution by obtaining subscriber call records. This
function helps to solve the pilot pollution caused by factors such as cross coverage, reducing the
drive test (DT) time and improving the accuracy of problem location.
Prerequisite
l
Context
Procedure
Step 1 Click
TIP
Issue 01 (2011-08-15)

173
Nastar
Step 3 Click Next.
required object.
Step 5 Click Next.
If...
Then...
NE is selected

Data tab page.
time.
NOTE
for analysis.


----End
Follow-up Procedure
Issue 01 (2011-08-15)

174
Nastar
TIP
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Save as the tasks
Refresh

Suspended.
Resume.
, or right-click
, or right-click

Click
8.5 Querying UMTS Pilot Pollution Analysis Results

This section describes how to query UMTS pilot pollution analysis results. The Nastar identifies
cells where pilot pollution exists, cells that cause interference, and severity of cell pollution by
obtaining the subscriber call records. This function helps you solve the pilot pollution caused
by factors such as cross coverage.
Prerequisite
l
The progress bar of the UMTS pilot pollution analysis task reaches 100%.
Procedure
Step 1 Choose UMTS Pilot Pollution Analysis Task from the navigation tree in the Analysis Task
Management window.
tasks.
Result. The UMTS Pilot Pollution Analysis window is displayed.
Issue 01 (2011-08-15)

175
Nastar
NOTE
Step 5 In the UMTS Pilot Pollution Analysis window, view the overview information and details of
the polluted cells and polluter cells.
l Initially, the polluted cell overview table is displayed on the left and the polluter cell details
table is displayed on the right of the UMTS Pilot Pollution Analysis window. You can click
in the upper left corner to switch the display mode, that is, polluter cell overview table
on the left and polluted cell details table on the right.
l You can select a polluted cell from the polluted cell overview table on the left to view all the
polluter cells of the selected cell in the polluter cell details table on the right. In the polluter
cell details table, select a polluter cell, and then click in the upper left corner of the window
to view the cells that are polluted by the selected polluter cell.
l For the description of the related parameters, see 8.8.4 Parameters for Querying UMTS
Pilot Pollution Analysis Results.
information.
----End
Follow-up Procedure
The Nastar supports the export of the query results. For details, see 8.6 Exporting UMTS Pilot
Pollution Analysis Reports.
8.6 Exporting UMTS Pilot Pollution Analysis Reports

This section describes how to export UMTS pilot pollution analysis reports. You can export the
queried pilot pollution analysis results as .csv, .xls, or .xlsx files. The exported analysis results
help you determine cells where pilot pollution exists, cells that cause interference, and severity
of cell pollution.
Prerequisite
l
UMTS pilot pollution analysis results are queried. For details, see 8.5 Querying UMTS
Pilot Pollution Analysis Results.
Procedure
Step 1 Right-click the query result list in the UMTS Pilot Pollution Analysis window, and then choose
Save As... from the shortcut menu. The Save dialog box is displayed.
Step 2 Set the file name and specify the file type and path to save the file. Then, click Save.
----End
8.7 Technical Specifications for UMTS Pilot Pollution

Analysis
This section describes the technical specifications for UMTS pilot pollution analysis.
Issue 01 (2011-08-15)

176
Nastar
Item

<= 10,000 cells
<= 5
<= 7 days
Negligible

(all the themes)
<= 200

<= 50
8.8 Reference to the UMTS Pilot Pollution Analysis

Interface
This section describes the interface for UMTS pilot pollution analysis and the relevant
UMTS pilot pollution analysis.
8.8.1 Interface Description: UMTS Pilot Pollution Analysis

This section describes the interface for UMTS pilot pollution analysis. Before performing
relevant operations, familiarize yourself with the functions of the areas on the interface.
The pilot pollution analysis results are displayed in tables, which consist of a polluted cell
overview table, a polluted cell details table, a polluter cell overview table, and a polluter cell
details table, as shown in Figure 8-2.
Issue 01 (2011-08-15)

177
Nastar
Figure 8-2 Pilot pollution analysis interface
No. Name
Description
(1)
Provides the function of switching the

information in Area (2) and (3).
Button area
Initially, Area (2) displays the polluted cell

overview table and Area (3) displays the
polluter cell details table. After you click the
switching button, Area (2) displays the
polluter cell overview table and Area (3)
displays the polluted cell details table.
(2)
Polluted cell overview table/polluter cell Displays the overview of all the polluted cells
overview table
or polluter cells involved in the task.
(3)
Polluter cell details table/polluted cell

details table
You can select a polluted cell from the

polluted cell overview table on the left to view
all the polluter cells of the selected cell in the
polluter cell details table on the right. In the
polluter cell details table, select a polluter cell,
and then click
in the upper left corner of
the window to view the cells that are polluted
by the selected polluter cell.
Issue 01 (2011-08-15)

178
Nastar

Common Information
Parameter
Description
Task Name
OSS Name

E2E Task List
Begin Time

End Time
NE List
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Description
Service Type

Exception Type

failure.
KPI

determination.
Determination
rule

as >=.
Exception Value

UMTS VIP
Analysis Data
Task
Issue 01 (2011-08-15)
Selected

selected.
Group Name
Number of
Members

179
Nastar
Parameter
Description
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Report Raw Data

Description
Start NCC
End NCC
Start BCC
End BCC
ARFCN
Indication
Start ARFCN

End ARFCN
UMTS Service
Geographic
Analysis Data
Task
Downlink Ec/No
(dB)<=X

bad RxQual area.
value is -15.
UMTS
Terminal
Analysis Data
Task
Type
KPI name
Criterion
threshold

provided.
8.8.3 Parameters for Creating and Modifying UMTS Pilot Pollution

Analysis Tasks
This section describes the parameters for creating and modifying UMTS pilot pollution analysis
tasks. You can refer to this description when creating and modifying a UMTS pilot pollution
analysis task.
Issue 01 (2011-08-15)

180
Nastar

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:

Parameter
Description
Task Type
time.
Time Range
analyzed.
Delayed
Delay.
Execution
Delay

Issue 01 (2011-08-15)
Parameter
Description
NE
network.
NE Group
the entire network.

181
Nastar
8.8.4 Parameters for Querying UMTS Pilot Pollution Analysis

Results
This section describes the parameters for querying UMTS pilot pollution analysis results. You
can refer to the description when querying UMTS pilot pollution analysis results.
Polluted Cell Overview Table

Paramet
er
Ran
ge
Uni
t
Description
RNC ID
[0,
+)
N/A
Indicates the ID of the RNC that a polluted cell belongs to.
Cell ID
[0,6
553
5]
N/A
Indicates the ID of a polluted cell.
Cell
Name
1 to
64
char
acter
s
N/A
Indicates the name of a polluted cell.
P-SC
[0,5
11]
N/A
Indicates the primary scrambling code of a polluted cell.
UARFC
N_DL
N/A
N/A
Indicates the UTRAN Absolute Radio Frequency Channel

Number (UARFCN) on the downlink.
UTRAN is an abbreviation for Universal Terrestrial Radio Access
Network.
Issue 01 (2011-08-15)
Average
ECNO
(dB)
[-24,
0]
dB
Indicates the average receive signal quality of pilot signals of a

polluted cell.
Average
RSCP
(dBm)
[-11
5,-2
5]
dB
m
Indicates the average receive signal strength of pilot signals of a

polluted cell.
Total
Number
of
Polluted
Events
[0,
+)
Nu
mbe
r
Indicates the total number of pollution events for a polluted cell.
Total
Number
of
Pollution
Neighbor
ing Cells
[0,
+)
Nu
mbe
r
Indicates the total number of cells that bring pollution to the

current cell.

182
Nastar
Polluter Cell Details Table

Paramet
er
Ran
ge
Uni
t
Description
RNC ID
[0,
+)
N/A
Indicates the ID of the RNC that a polluter cell belongs to.
Cell ID
[0,6
553
5]
N/A
Indicates the ID of a polluter cell.
Cell
Name
1 to
64
char
acter
s
N/A
Indicates the name of a polluter cell.

If the current polluter cell is a defined neighboring cell of the
current polluted cell, the name of a defined neighboring cell is
displayed in this field.
If the current polluter cell is an undefined neighboring cell of the
current polluted cell, the name of a possible neighboring cell is
If the system cannot find the detailed information about the cell
corresponding to the P-SC of the polluted cell, Unknown is
Average
ECNO
(dB)
[-24,
0]
dB

polluter cell.
Average
RSCP
(dBm)
[-11
5,-2
5]
dB
m

polluter cell.
Number
of
Polluted
Events
[0,
+)
Nu
mbe
r
Indicates the total number of pollution events that the current cell
is polluted by polluter cells.
Distance
(km)
[0,
+)
km
Indicates the distance between a polluted cell and a polluter cell.
Polluter Cell Overview Table
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
RNC ID
[0,
+)
N/A
Indicates the ID of the RNC that a polluter cell belongs to.
Cell ID
[0,6
553
5]
N/A
Indicates the ID of a polluter cell.

183
Nastar
Paramet
er
Ran
ge
Uni
t
Description
Cell
Name
1 to
64
char
acter
s
N/A
Indicates the name of a polluter cell.
P-SC
[0,5
11]
N/A
Indicates the primary scrambling code of a polluter cell.
UARFC
N_DL
N/A
N/A
Indicates the UARFCN.
Average
ECNO
(dB)
[-24,
0]
dB

polluter cell.
Average
RSCP
(dBm)
[-11
5,-2
5]
dB
m

polluter cell.
Number
of
Pollution
Events
[0,
+)
Nu
mbe
r
Indicates the total number of pollution events that the polluter cell
brings pollution to other cells.
Total
Number
of
Polluted
Neighbor
ing Cells
[0,
+)
Nu
mbe
r
Indicates the total number of cells that is polluted by the current

cell.
Polluted Cell Details Table
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
RNC ID
[0,
+)
N/A
Indicates the ID of the RNC that a polluted cell belongs to.
Cell ID
[0,6
553
5]
N/A
Indicates the ID of a polluted cell.
Cell
Name
1 to
64
char
acter
s
N/A
Indicates the name of a polluted cell.

184
Nastar
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Average
ECNO
(dB)
[-24,
0]
dB

polluted cell.
Average
RSCP
(dBm)
[-11
5,-2
5]
dB
m

polluted cell.
Number
of
Polluted
Events
[0,
+)
Nu
mbe
r
Indicates the total number of pollution events that the polluted cell
is polluted by the current polluter cell.
Distance
(km)
[0,
+)
km
Indicates the distance between a polluted cell and a polluter cell.

185
Nastar
UMTS Uplink Interference Analysis
About This Chapter

The UMTS uplink interference analysis function enables you to obtain UMTS uplink
interference analysis data, create UMTS uplink interference analysis tasks, and query UMTS
uplink interference analysis reports. With the uplink interference analysis function, the Nastar
analyzes Received Total Wideband Power(RTWP) data reported by NodeBs and preliminarily
locates NodeBs that are affected by interference by ranking NodeBs based on their interference.
Then, you can view the charts showing the overall RTWP trends of the selected cells to determine
whether the average interference intensity of main and diversity antennas is proper and judge
the interference characteristics. You can also view the distribution chart of main and diversity
difference to determine whether the main and diversity antennas are connected correctly.
9.1 Basic Knowledge of UMTS Uplink Interference Analysis
This section describes the basic knowledge of UMTS uplink interference analysis. With this
function, the Nastar analyzes Received Total Wideband Power (RTWP) data reported by the
NodeBs and generates analysis results for identifying interference on the network. In addition,
the Nastar analyzes the signal strength of the main and diversity antennas on the uplink, helping
users locate antenna problems.
9.2 UMTS Uplink Interference Analysis Process
This section describes the UMTS uplink interference analysis process.
9.3 Obtaining UMTS Uplink Interference Analysis Data
This section describes how to enable the Nastar to obtain UMTS uplink interference analysis
9.4 Creating UMTS Uplink Interference Analysis Tasks
This section describes how to create UMTS uplink interference analysis tasks. After you create
a UMTS uplink interference analysis task, the Nastar periodically analyzes Received Total
Wideband Power(RTWP) data of each NodeB in the database. By querying analysis results, you
can learn about the signal strength of the main and diversity antennas and the change trend of
signal strength of the selected measurement cell within a certain period. The information
provides references for identifying network interference.
9.5 Querying UMTS Uplink Interference Analysis Results
This section describes how to query UMTS uplink interference analysis results. You can query
Received Total Wideband Power (RTWP) data reported by NodeBs within a certain period and
Issue 01 (2011-08-15)

186
Nastar
then preliminarily locate NodeBs that are affected by interference based on query results. Then,
you can view the charts showing the overall RTWP trends of the selected cells to determine
whether the average interference intensity of main and diversity antennas is proper and check
the interference characteristics. You can also view the distribution chart of antenna strength
differences between the main and diversity antennas to determine whether the main and diversity
antennas are connected correctly.
9.6 Technical Specifications for UMTS Uplink Interference Analysis
This section describes the technical specifications for UMTS uplink interference analysis.
9.7 Reference for the UMTS Uplink Interference Analysis GUI
This section describes the interface for UMTS uplink-interference analysis and the relevant
UMTS uplink-interference analysis.
Issue 01 (2011-08-15)

187
Nastar
9.1 Basic Knowledge of UMTS Uplink Interference

Analysis
This section describes the basic knowledge of UMTS uplink interference analysis. With this
function, the Nastar analyzes Received Total Wideband Power (RTWP) data reported by the
NodeBs and generates analysis results for identifying interference on the network. In addition,
the Nastar analyzes the signal strength of the main and diversity antennas on the uplink, helping
users locate antenna problems.
Uplink interference has an impact on network quality. If uplink interference exists, the call
quality, network coverage, and network capacity may be greatly affected, and call drops,
handover problems, and congestion may occur frequently. If interference and load are not clearly
identified, load control cannot be performed properly.
With the uplink interference analysis function, the Nastar analyzes RTWP data reported by
NodeBs and preliminarily locates NodeBs that are affected by interference by ranking NodeBs
based on their interference. Then, you can view the charts showing the overall RTWP trends of
the selected cells to determine whether the average interference intensity of main and diversity
antennas is proper and judge the interference characteristics. You can also view the distribution
chart of main and diversity difference to determine whether the main and diversity antennas are
connected correctly.
After the conditions for uplink interference analysis are set, the Nastar performs uplink
interference analysis on the selected cells. The analysis results are displayed in a line chart. The
signal strength of the main and diversity antennas at each time point and the overall change
trends are displayed in different colors in the chart.
9.2 UMTS Uplink Interference Analysis Process

This section describes the UMTS uplink interference analysis process.
Figure 9-1 shows the process of UMTS uplink interference analysis.
Issue 01 (2011-08-15)

188
Nastar
Figure 9-1 Process of UMTS uplink interference analysis

Table 9-1 Description of UMTS uplink interference analysis process
Issue 01 (2011-08-15)
No.
Procedure
Description
Create a UMTS
uplink
interference
analysis data
E2E task

measurement task.

189
Nastar
No.
Procedure
Description
Create a UMTS
uplink
interference
analysis data
import task

create a UMTS uplink interference analysis data import task.
After you create the task, the Nastar periodically imports the
uplink interference analysis data files saved on the Nastar server
into the database.
Check the
integrity of
UMTS uplink
interference
analysis data

required UMTS uplink interference analysis data is imported
into the database.
Create a UMTS
uplink
interference
analysis task

you can create a UMTS uplink interference analysis task. After
you create the task, the Nastar periodically retrieves UMTS
uplink interference analysis data and UMTS configuration data
from the database, analyzes the retrieved data, and then generates
analysis results.
Query UMTS
uplink
interference
analysis results
You can view the analysis results of the UMTS uplink

interference analysis tasks that are executed successfully to
preliminarily locate NodeBs that are affected by interference.
Then, you can view the charts showing the overall RTWP trends
of the selected cells to determine whether the average
interference intensity of main and diversity antennas is proper
and judge the interference characteristics. You can also view the
distribution chart of main and diversity difference to determine
whether the main and diversity antennas are connected correctly.
9.3 Obtaining UMTS Uplink Interference Analysis Data

This section describes how to enable the Nastar to obtain UMTS uplink interference analysis

Prerequisite
l
Issue 01 (2011-08-15)

190
Nastar
Configuration Data.
Context
Procedure
displayed.
TIP

1.
2.
NOTE
OSS to be analyzed.
Step 4 Click Next.

CAUTION
Issue 01 (2011-08-15)

191
Nastar
step.
If...
Then...
data E2E task
list.


task

E2E task

list.



----End
Follow-up Procedure
If you need to...
Then...
Click Property.
Click Delete.
NOTE

Issue 01 (2011-08-15)
Click Refresh.

192
Nastar
If you need to...
Then...
shortcut menu.
NOTE

Prerequisite
Context
l
at the preset time.
Issue 01 (2011-08-15)
Analysis Task
Type
Creation
GSM MR Analysis

Analysis Data
Manual creation
GSM Neighboring
Cell Analysis

Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation

193
Nastar
Analysis Task
Type
Creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Manual creation
GSM VIP Analysis

Data
Manual creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Manual creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
Issue 01 (2011-08-15)
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis

Analysis Data
Manual creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Data
Manual creation
UMTS Coverage
Analysis

Analysis Data
Manual creation
UMTS VIP
Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis

Analysis Data
Manual creation

194
Nastar
Analysis Task
Type
Creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis

Analysis Data
Manual creation
UMTS Service
Geographic
Analysis

Analysis CHR Data
Manual creation

Analysis MR Data
CDMA Uplink
Interference
Ranking Analysis
Import CDMA Uplink

Analysis Data
Manual creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis

Manual creation
CDMA Complaint
Analysis Support
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

(1X)
Manual creation

Cell Analysis Data
(EVDO)
l Import CDMA Pilot

(EVDO)
CDMA Coverage
Analysis

Analysis Data (1X)
Manual creation

Issue 01 (2011-08-15)
CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis

Manual creation

195
Nastar
Analysis Task
Type
Creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis

Data
Manual creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis

Analysis Data
Manual creation
LTE Complaint
Analysis Support
LTE Cell Fault

Diagnosis
Analysis
Procedure
1.
2.
3.
Periodic.

1.
NOTE
2.

----End
Follow-up Procedure
Issue 01 (2011-08-15)

196
Nastar
If you need to...
Then...
Delete a task
Click Delete.
NOTE
Suspend a task or
resume a task

l Manual mode
the shortcut menu.
l Automatic mode
NOTE

of a task
Running to Idle.
NOTE

Prerequisite
l
Context
Issue 01 (2011-08-15)
Analysis Task Type
Data Type

Analysis Task


197
Nastar
Issue 01 (2011-08-15)
Analysis Task Type
Data Type
Cell Analysis Task


Task


Analysis Task

analysis data


Support Task

Analysis Task

data

Task

Analysis Task

parameters

Analysis Task

analysis data
Task

Cell Analysis Task


Task


Support Task

Analysis Task

data

Analysis Task

analysis data

Task

198
Nastar
Analysis Task Type
Data Type

Analysis Task

parameters

Analysis Task

Task


Support Task

Analysis Task


Task

services)

Analysis Task

analysis data



Analysis Task

data

Support Task

Analysis Task
Procedure
Issue 01 (2011-08-15)

199
Nastar
TIP
required.
Step 5 Click Query.
----End
9.4 Creating UMTS Uplink Interference Analysis Tasks

This section describes how to create UMTS uplink interference analysis tasks. After you create
a UMTS uplink interference analysis task, the Nastar periodically analyzes Received Total
Wideband Power(RTWP) data of each NodeB in the database. By querying analysis results, you
can learn about the signal strength of the main and diversity antennas and the change trend of
signal strength of the selected measurement cell within a certain period. The information
provides references for identifying network interference.
Prerequisite
l
Context
Procedure
Step 1 Click
TIP
Step 3 Click Next.
Issue 01 (2011-08-15)

200
Nastar

required object.
Step 5 Click Next.
If...
Then...
NE is selected

Data tab page.
time.
NOTE
for analysis.


----End
Follow-up Procedure
TIP
Issue 01 (2011-08-15)

201
Nastar
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Save as the tasks
Refresh

Suspended.
Resume.
, or right-click
, or right-click

Click
9.5 Querying UMTS Uplink Interference Analysis Results

This section describes how to query UMTS uplink interference analysis results. You can query
Received Total Wideband Power (RTWP) data reported by NodeBs within a certain period and
then preliminarily locate NodeBs that are affected by interference based on query results. Then,
you can view the charts showing the overall RTWP trends of the selected cells to determine
whether the average interference intensity of main and diversity antennas is proper and check
the interference characteristics. You can also view the distribution chart of antenna strength
differences between the main and diversity antennas to determine whether the main and diversity
antennas are connected correctly.
Prerequisite
l
The progress bar of the UMTS uplink interference analysis task reaches 100%.
Procedure
Step 1 Choose UMTS Uplink Interference Analysis Task from the navigation tree in the Analysis
tasks.
Result from the shortcut menu. The UMTS Uplink Interference Analysis window is displayed.
Issue 01 (2011-08-15)

202
Nastar
NOTE
Step 5 Select the information about a measurement cell from the list on the left of the UMTS Uplink
Interference Analysis window, and then browse the overall RTWP trends and the distribution
of antenna strength differences between the main and diversity antennas of the selected
measurement cell in the right pane.
l On the right pane:
The upper chart displays the change trends of interference signal strength of the main and
diversity antennas of the selected cell within a certain period.
The lower chart displays the distribution of antenna strength differences between the main
and diversity antennas of the selected cell. The Nastar calculates the differences between
the main and diversity antennas at each time point and then calculates the percentage of
each difference to the total number of differences.
You can drag a chart by moving the pointer or right-click any area in a chart and then
choose Zoom In, Zoom Out, or Auto Range to resize the chart accordingly. You can
also right-click any area in the chart and then choose an option from the shortcut menu
to perform the corresponding operation, such as querying the attributes of the chart, saving
the chart, or printing the chart.
l The overall RTWP change trend chart displays RTWP data that is aggregated every minute.
----End
Follow-up Procedure
9.6 Technical Specifications for UMTS Uplink Interference

Analysis
This section describes the technical specifications for UMTS uplink interference analysis.
Issue 01 (2011-08-15)
Item

<= 100 sites
<= 5
<= 7 days
Negligible

(all the themes)
<= 200

<= 50

203
Nastar
9.7 Reference for the UMTS Uplink Interference Analysis

GUI
This section describes the interface for UMTS uplink-interference analysis and the relevant
UMTS uplink-interference analysis.
9.7.1 Interface for UMTS Uplink Interference Analysis

This section describes the interface for UMTS uplink-interference analysis. Before performing
The uplink-interference analysis result interface displays the trends of the RTWP data in a line
chart, as shown in Figure 9-2.
Figure 9-2 Interface for the uplink-interference analysis of a cell
No. Name
Description
(1)
Cell information list
Displays the basic information about all the

cells involved in an analysis task in a table.
(2)
Overall RTWP trend chart of a cell
Displays the trends of the RTWPs of the

main and diversity antennas of a selected
cell in a time segment in a line chart.
Issue 01 (2011-08-15)

204
Nastar
No. Name
Description
(3)
Displays the distribution of the difference

between the RTWPs of the main and
diversity antennas of the selected cell in
column charts.
Distribution chart of the differences

between the RTWPs of the main and
diversity antennas

Common Information
Parameter
Description
Task Name
OSS Name

E2E Task List
Begin Time

End Time
NE List
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Issue 01 (2011-08-15)
Description
Service Type

Exception Type

failure.
KPI

determination.
Determination
rule

as >=.

205
Nastar
Parameter
Description
Exception Value

UMTS VIP
Analysis Data
Task
Selected

selected.
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Group Name
Number of
Members
Report Raw Data

Description
Start NCC
End NCC
Start BCC
End BCC
ARFCN
Indication
Start ARFCN

End ARFCN
UMTS Service
Geographic
Analysis Data
Task
Downlink Ec/No
(dB)<=X

bad RxQual area.
value is -15.
UMTS
Terminal
Analysis Data
Task
Issue 01 (2011-08-15)
Type
KPI name
Criterion

206
Nastar
Parameter
Description
threshold

provided.
9.7.3 Parameters for Creating or Modifying a UMTS Uplink

Interference Analysis Task
This section describes the parameters for creating and modifying UMTS uplink-interference
analysis tasks. You can refer to the description when creating or modifying a UMTS uplinkinterference analysis task.

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:
Issue 01 (2011-08-15)
Parameter
Description
Task Type
time.

207
Nastar
Parameter
Description
Time Range
analyzed.
Delayed
Delay.
Execution
Delay

Parameter
Description
NE
network.
NE Group
the entire network.
9.7.4 Parameters for Querying UMTS Uplink Interference Analysis

Results
This section describes the parameters for querying UMTS uplink interference analysis results.
You can refer to the description when querying UMTS uplink interference analysis results.
Parameter
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
RNC ID
N/A
N/
A
Indicates the ID of an RNC.
Cell ID
[0,655
35]
N/
A
Indicates the ID of a cell.
Cell
Name
1 to 64
charact
ers
N/
A
Indicates the name of a cell, for example, Cell_1.
P-SC
[0,511]
N/
A
Indicates the primary scrambling code of a cell.

208
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
Main
Average
Strength
(dBm)
N/A
N/
A
Indicates the average value of the interference strength of main

antennas.
Diversity
Average
Strength
(dBm)
N/A
N/
A
Indicates the average value of the interference strength of

diversity antennas.
Average
Differenc
e (MainDiversity
) (dB)
N/A
N/
A
Indicates the value calculated by dividing the sum of the signal

differences between the main and diversity antennas at each
time point in the selected time range by the total number of time
points.
Standard
Deviatio
n (MainDiversity
)
N/A
N/
A
Indicates the square root of the value calculated through the

following steps: Firstly, calculate the average of the signal
differences between the main and diversity antennas at every
time point in a selected time range. Secondly, subtract the
average from the signal differences between the main and
diversity antennas separately. Thirdly, divide the sum of the
squares of the values obtained in the second step by the total
number of time points.

209
Nastar
10
About This Chapter

This section describes the UMTS terminal analysis tasks, including the management of terminal
analysis tasks and the query and export of terminal analysis reports. The system analyzes the
KPIs in the call records of terminal users. This function helps operators identify the terminals
with poor performance in the UMTS network, therefore encouraging terminal manufacturers to
improve the terminals with poor performance and guide subscribers to purchase terminals with
good performance. In this case, subscribers can obtain stable services, and the subscriber
satisfaction can be improved.
10.1 Basic Knowledge of UMTS Terminal Analysis
This section describes the basic knowledge of UMTS terminal analysis. The UMTS terminal
analysis function enables the Nastar to analyze the performance of various types of terminals
and subscriber behavior from the perspective of terminals based on CHR data on the live
network.
10.2 UMTS Terminal Analysis Process
This section describes the UMTS terminal analysis process.
10.3 Managing Terminal Information
This section describes how to manage terminal information. The terminal management function
enables you to add terminal types and set up the management record for the added terminal types
as required for terminal performance analysis. In addition, you can modify the properties of an
existing terminal type, delete, or export a terminal type.
10.4 Obtaining UMTS Terminal Analysis Data
This section describes how to enable the Nastar to obtain UMTS terminal analysis data. You
so that the Nastar imports the collected analysis data into the database.
10.5 Creating a UMTS Terminal Analysis Task
This section describes how to create a UMTS terminal analysis task. After you create a UMTS
terminal analysis task, the Nastar obtains and analyzes the call records of all subscribers for the
selected NEs. You can query the analysis results to know about terminal inventory information
and terminal performance information on the live network.
10.6 Querying UMTS Terminal Analysis Results
Issue 01 (2011-08-15)

210
Nastar
This section describes how to query UMTS terminal analysis results. The analysis results help
you collect statistics on terminal inventory information and analyze related KPIs to learn about
the performance of various types of terminals on a UMTS network.
10.7 Exporting UMTS Terminal Analysis Reports
This section describes how to export UMTS terminal analysis reports. You can export the queried
terminal inventory analysis results and terminal performance analysis results as .xls or .xlsx files.
10.8 Technical Specifications for UMTS Terminal Analysis
This section describes the technical specifications for UMTS Terminal Analysis.
10.9 Reference to the UMTS Terminal Analysis Interface
This section describes the interface for UMTS terminal analysis and the relevant parameters.
Before performing relevant operations, familiarize yourself with the functions of UMTS terminal
analysis.
Issue 01 (2011-08-15)

211
Nastar
10.1 Basic Knowledge of UMTS Terminal Analysis

This section describes the basic knowledge of UMTS terminal analysis. The UMTS terminal
analysis function enables the Nastar to analyze the performance of various types of terminals
and subscriber behavior from the perspective of terminals based on CHR data on the live
network.
Function and Usage Scenario

Call records of subscribers can reflect the access performance, service retainability, and intraRAT handover performance of terminals. KPIs related to delay, service quality, and traffic can
reflect the terminal capability.
Nastar terminal analysis provides the following functions:
l
Terminal inventory analysis: The Nastar displays the distribution of terminals on the live
network by different dimensions such as vendor or terminal model.
Terminal analysis: The Nastar aggregates cell-level and service-level KPIs. Based on
aggregation results of cell-level KPIs, you can analyze the actual status of each cell and
queried results to determine whether the poor terminal performance is caused by a terminal
defect or is affected by special cells (for example, UMTS cells near a GSM network). Based
on aggregation results of service-level KPIs, you can analyze each service and queried
results to identify the service that is not properly supported by terminals on the live network.
The preceding functions help you identify problems caused by terminals, learn about the
performance of various types of terminals, analyze inventory information of various types of
terminals on the live network, and identify and analyze UMTS traffic problems related to dualmode terminals.
Basic Concept: IMEI

International Mobile Equipment Identity (IMEI) uniquely identifies an MS.
An IMEI consists of 15 digits ranging from 0 to 9 and is composed of the following four parts:
l
Type approval code (TAC): consists of six digits and is used to identify an MS type.
Final assembly code (FAC): consists of two digits and is used to identify a vendor.
Serial Number (SNR): consists of six digits and is used to uniquely identify an MS when
the TAC and FAC of two MSs are the same.
SP: a spare bit, which consists of only one digit and is reserved for use.
In an IMEI, the first eight digits that are composed of TAC and FAC uniquely identify an MS
type, and the later digits from 9 to 15 uniquely identify an MS of a certain type.
The Nastar analyzes only MSs of a certain type identified by the first eight digits that are
composed of TAC and FAC. In the Nastar window, IMEI-TAC refers to these eight digits.
10.2 UMTS Terminal Analysis Process

This section describes the UMTS terminal analysis process.
Figure 10-1 shows the process of UMTS terminal analysis.
Issue 01 (2011-08-15)

212
Nastar
Figure 10-1 Process of terminal analysis
Table 10-1 describes the items in the flowchart.
Issue 01 (2011-08-15)

213
Nastar
Table 10-1 Description of the terminal analysis process

No.
Procedure
Description
Manage terminal In the Analysis Task Management window on the Nastar client,
types
you can switch to the terminal type management window to set
the information about the terminal types on the network. The
terminal information includes the IMEI-TAC, vendor, model,
type, and supported network systems. After the information is
set, the Nastar can display the terminal information accordingly
based on the detected IMEI-TAC when creating a terminal
analysis task. This helps users analyze the terminal efficiently.
Query NE data
information

you can switch to the data query window to query whether the
raw data required for the terminal analysis is imported to the
database.
Create a
terminal
analysis E2E
task
On the Nastar client, choose Maintenance > E2E Task

Management to open the E2E Task Management window,
measurement task.
Create a terminal
analysis data
import task

Nastar client to open the Task Management window, and then
create a UMTS terminal analysis data import task. After the tasks
are created, the Nastar periodically imports the terminal data
files saved on the Nastar server into the database.
Create a
terminal
analysis task

you can create terminal analysis tasks. After obtaining the related
analysis data from the database, the Nastar analyzes data and
then generates the analysis result.
Query terminal
analysis results
You can view the analysis results of the tasks that are
successfully performed.
Export
terminal
analysis reports
You can export the result files through the one-key method in
the analysis result query interface.
10.3 Managing Terminal Information

This section describes how to manage terminal information. The terminal management function
enables you to add terminal types and set up the management record for the added terminal types
as required for terminal performance analysis. In addition, you can modify the properties of an
existing terminal type, delete, or export a terminal type.
Prerequisite
l
Issue 01 (2011-08-15)

214
Nastar
You are authorized to manage terminal types.
A terminal property file to be imported can be in .csv, .xls, or .xlsx format, as shown in
Table 10-2.
Context
Table 10-2 Example of a terminal property file
Property Name
Optional Parameter
Terminal Type
MS
Terminal Type
Netbook
Terminal Technology
GSM
Terminal Technology
GSM/WCDMA
A terminal type file in .csv, .xls, or .xlsx format to be imported must contain the following
fields: IMEI-TAC, Vendor, Terminal model, Chip Model, Terminal Type, Terminal
Technology, and Data Transfer, as shown in Table 10-3. The match sequence of columns
is specified and automatic matching of columns is not supported.
Table 10-3 Example of a terminal type file
IMEITAC
Vendor
Termina
l model
Chip
Model
Termina
l Type
Termina
l
Technol
ogy
Data
Transfer
86000400
Lenovo
TD800
Huawei8
MS
TDSCDMA
GPRS/
EDGE/
HSDPA
86004300
SAMSU
NG
GTI6320C
Huawei9
MS
TDSCDMA
GPRS/
EDGE
Procedure
System Function > Terminal Type Management.
TIP
You can also select and right-click System Function > Terminal Type Management, and choose
Open from the shortcut menu. The Terminal Type Management window is displayed.
Step 2 Optional: Customize terminal properties.

If the default terminal properties do not meet your requirements, you can customize them.
The default terminal properties and their values are as follows: Terminal Type (values: MS,
netbook, family gateway, and wireless landline), Terminal Technology (values: GSM,
WCDMA, GSM/WCDMA, GSM/TD-SCDMA, and LTE), and Data Transfer (values: GPRS/
Issue 01 (2011-08-15)

215
Nastar
EDGE, GPRS/EDGE/HSDPA, and GPRS/EDGE/HSPA). The default properties and their

values cannot be deleted, but you can add values for the default properties.
If you need to...
Then...
Customize a terminal
property by adding it
1. In the Terminal Type Management window, right-click

the table heading and choose Customize Column from the
shortcut menu. The Customize Column dialog box is
displayed.
2. In the Property area, click Add to add a property, and click
OK.
3. In the Property area, select the newly added property. In the
Value area, click Add to add a value for this property. Click
OK.
Customize a terminal
property by importing a
terminal property file
1. In the Terminal Type Management window, right-click

the table heading and choose Customize Column from the
shortcut menu. The Customize Column dialog box is
displayed.
2. Click Import. The Open dialog box is displayed.
3. Select an edited terminal property file, and click Open.
4. Perform operations as prompted, and click OK.
Step 3 Set the terminal type.

If you need to...
Then...
Set the terminal type by

adding it
1. Click Create in the lower-right corner of the window. The

Terminal Type Management-Create dialog box is
displayed.
2. Set related parameters.
Among the parameters, IMEI-TAC, Vendor, and
Terminal model are mandatory. For details about the
parameters, see Parameters for Creating and Modifying the
Terminal Type.
3. Click OK.
Issue 01 (2011-08-15)

216
Nastar
If you need to...
Then...
Set the terminal type by

importing a terminal type
file
1. Click Import in the lower-right corner of the window. The

Open dialog box is displayed.
2. Select an edited terminal type file, and click Open.
If a terminal type file in .xls or .xlsx format is selected and
if this file contains multiple worksheets, a message is
displayed for you to select the worksheet to be imported.
3. Perform operations as prompted.
l If the imported information is correct and no record is
identical with the existing records in the system, click
OK.
l If the imported information is correct but certain records
are identical with the existing records in the system, the
Confirm dialog box is displayed. In this case, click
Yes to overwrite the existing records and import new
records.
You can also click No in the displayed Confirm dialog
box to ignore the duplicate records and import the
additional records.
l If certain abnormal records exist in the information to be
imported, the current file cannot be imported. In this case,
the system displays the number of abnormal records.
Click Export Checked Result to export the check
result so that you can modify error information. Then,
terminate the current import task.
You can click Cancel to terminate the current import
task.
4. Click OK.
----End
Follow-up Procedure
In the Terminal Type Management window, perform various operations as required.
If you need to...
Then...
Modify a terminal
property and its
value
1. In the Terminal Type Management window, right-click the table

heading and choose Customize Column from the shortcut menu.
The Customize Column dialog box is displayed.
2. In the Property area, select a property, and click Edit to change the
name of the property.
3. In the Property area, select a property. In the Value, select a value,
and click Edit to modify the value of this property.
Issue 01 (2011-08-15)

217
Nastar
If you need to...
Then...
Delete a terminal
property and its
value
You are allowed to delete only user-defined properties.

2. In the Property area, select a property. In the Value, select a value,
and click Delete to delete the value of this property.
3. In the Property area, select one or multiple user-defined properties,
and click Delete to delete them.
The values of the deleted properties are also deleted.
Export a terminal
property and its
value

heading and choose Display Customize Column from the shortcut
menu. The Display Customize Column dialog box is displayed.
2. Set the display effect of columns.
3. Click OK.
Set the display

effect of terminal
information

2. Click Export.
3. In the Save dialog box, set a file name and specify a save path and
file type. Then, click Save.
Modify
information about
a terminal type
1. In the Terminal Type Management window, select a piece of

terminal type information, and click Modify. The Terminal Type
Management-Modify dialog box is displayed.
2. Modify the related parameters.
The vendor and terminal model cannot be empty and the IMEI-TAC
cannot be changed.
For details about the parameters, see Parameters for Creating and
Modifying the Terminal Type.
3. Click OK.
If a terminal type is used by certain tasks, the modification does not
affect the ongoing tasks. If a terminal type is used by a periodic task,
the related information is updated in the next period after the
modification.
Delete a terminal
type
1. In the Terminal Type Management window, select one piece or

multiple pieces of terminal type information, and click Delete.
2. In the displayed Suggestion dialog box, click Yes.
If a terminal type is used by certain tasks, the modification does not
affect the ongoing tasks. If a terminal type is used by a periodic task,
the related information is updated in the next period after the
modification.
Issue 01 (2011-08-15)

218
Nastar
If you need to...
Then...
Export terminal
type information
and save the
information in
a .csv, .xls, or .xlsx
file
1. In the Terminal Type Management window, select one piece or

multiple pieces of terminal type information, and click Export.
2. In the Save dialog box, set a file name and specify a save path and
file type. Then, click Save.
NOTE
You can also right-click any area in the Terminal Type Management window
and choose Save as from the shortcut menu to export all terminal type
information.
10.4 Obtaining UMTS Terminal Analysis Data

This section describes how to enable the Nastar to obtain UMTS terminal analysis data. You
so that the Nastar imports the collected analysis data into the database.

Prerequisite
l
Configuration Data.
Context
Issue 01 (2011-08-15)

219
Nastar
Procedure
displayed.
TIP

1.
2.
NOTE
OSS to be analyzed.
Step 4 Click Next.

CAUTION
step.
If...
Then...
data E2E task
list.
Issue 01 (2011-08-15)


220
Nastar
If...
Then...

task

E2E task

list.



----End
Follow-up Procedure
If you need to...
Then...
Click Property.
Click Delete.
NOTE

Click Refresh.
shortcut menu.
NOTE

Issue 01 (2011-08-15)

221
Nastar
Prerequisite
Context
l
at the preset time.
Issue 01 (2011-08-15)
Analysis Task
Type
Creation
GSM MR Analysis

Analysis Data
Manual creation
GSM Neighboring
Cell Analysis

Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Manual creation
GSM VIP Analysis

Data
Manual creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Manual creation

222
Nastar
Analysis Task
Type
Creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis

Analysis Data
Manual creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Data
Manual creation
UMTS Coverage
Analysis

Analysis Data
Manual creation
UMTS VIP
Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis

Analysis Data
Manual creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis

Analysis Data
Manual creation
UMTS Service
Geographic
Analysis

Analysis CHR Data
Manual creation

Analysis MR Data
CDMA Uplink
Interference
Ranking Analysis
Issue 01 (2011-08-15)
Import CDMA Uplink

Analysis Data

Manual creation
223
Nastar
Analysis Task
Type
Creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis

Manual creation
CDMA Complaint
Analysis Support
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

(1X)
Manual creation

Cell Analysis Data
(EVDO)
l Import CDMA Pilot

(EVDO)
CDMA Coverage
Analysis

Analysis Data (1X)
Manual creation

Issue 01 (2011-08-15)
CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis

Manual creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis

Data
Manual creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis

Analysis Data
Manual creation
LTE Complaint
Analysis Support

224
Nastar
Analysis Task
Type
Creation
LTE Cell Fault

Diagnosis
Analysis
Procedure
1.
2.
3.
Periodic.

1.
NOTE
2.

----End
Follow-up Procedure
If you need to...
Then...
Delete a task
Click Delete.
NOTE
Issue 01 (2011-08-15)

225
Nastar
If you need to...
Then...
Suspend a task or
resume a task

l Manual mode
the shortcut menu.
l Automatic mode
NOTE

of a task
Running to Idle.
NOTE

Prerequisite
l
Context
Issue 01 (2011-08-15)
Analysis Task Type
Data Type

Analysis Task

Cell Analysis Task


Task


Analysis Task

analysis data

226
Nastar
Issue 01 (2011-08-15)
Analysis Task Type
Data Type


Support Task

Analysis Task

data

Task

Analysis Task

parameters

Analysis Task

analysis data
Task

Cell Analysis Task


Task


Support Task

Analysis Task

data

Analysis Task

analysis data

Task

Analysis Task

parameters

Analysis Task


227
Nastar
Analysis Task Type
Data Type
Task


Support Task

Analysis Task


Task

services)

Analysis Task

analysis data



Analysis Task

data

Support Task

Analysis Task
Procedure
TIP
required.
Issue 01 (2011-08-15)

228
Nastar
Step 5 Click Query.
----End
10.5 Creating a UMTS Terminal Analysis Task

This section describes how to create a UMTS terminal analysis task. After you create a UMTS
terminal analysis task, the Nastar obtains and analyzes the call records of all subscribers for the
selected NEs. You can query the analysis results to know about terminal inventory information
and terminal performance information on the live network.
Prerequisite
l
Context
Procedure
Step 1 Click
TIP
Step 3 Click Next.
required object.
Step 5 Click Next.
Step 6 Set the Task Type to One-time, set the time range and the start time of the task.
----End
Issue 01 (2011-08-15)

229
Nastar
Follow-up Procedure
TIP
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Save as the tasks
Refresh

Suspended.
, or right-click

Resume.
, or right-click

Click
10.6 Querying UMTS Terminal Analysis Results

This section describes how to query UMTS terminal analysis results. The analysis results help
you collect statistics on terminal inventory information and analyze related KPIs to learn about
the performance of various types of terminals on a UMTS network.
Prerequisite
l
You are authorized to perform the terminal analysis function.
A terminal analysis task is executed successfully.
Procedure
Step 1 In the navigation tree on the left of the Analysis Task Management window, click UMTS
Terminal Analysis Task.
tasks.
Issue 01 (2011-08-15)

230
Nastar
Step 4 Double-click an analysis result or right-click an analysis result and choose View Analysis
Results from the shortcut menu. The UMTS Terminal Analysis Task window is displayed.
NOTE
Step 5 Click the Terminal Inventory Analysis tab to query terminal inventory information.
1.
In the Analysis Dimension area, the proportions of terminals on the live network are
displayed for the selected analysis item in a pie chart.
If you want to query the distribution proportions of terminals of different vendors on the
live network, select Manufacturer in Analysis Dimension.
2.
In TopN, set the number of records to be displayed. Press Enter.

If you want to query the distribution proportions of terminals of top 10 vendors with the
most occupancy, set TopN to 10. After the setting, the pie chart is divided into 11 parts,
including the distribution proportions of terminals of top 10 vendors and the distribution
proportion of terminals of all other vendors.
3.
Query statistical results in the pie chart.

Legends are displayed on the right of the pie chart. If a property is not defined for a certain
type of terminals in the Terminal Type Management window and if this property is
selected as an analysis item, this property is identified by Unknown+Number+(IMEITAC).
4.
Query statistical results in the table.

Information in the table is consistent with that in the pie chart. You can query the number
of terminals of a certain type and the proportion of these terminals on the live network by
an analysis item.
You can right-click statistical results and choose Save As from the shortcut menu to export
statistical results as a .csv, .xls, or .xlsx file.
Step 6 Click the Terminal Performance Analysis tab to analyze terminal performance.
1.
Select terminal performance KPIs to be analyzed from the navigation tree on the left. The
KPIs are classified by terminal properties, terminal capability, and others.
If the default terminal performance KPIs do not meet your requirements, click Custom
Indicator on the toolbar to group multiple terminal performance KPIs into one KPI set.
You can modify or delete user-defined KPI sets.
2.
Query the values of terminal performance KPIs for each type of terminals in the upperright table.
3.
Select a terminal type in the upper-right table, and query the values of KPIs for this type
of terminals in each cell in the lower-right table.
----End
10.7 Exporting UMTS Terminal Analysis Reports

This section describes how to export UMTS terminal analysis reports. You can export the queried
terminal inventory analysis results and terminal performance analysis results as .xls or .xlsx files.
Issue 01 (2011-08-15)

231
Nastar
Prerequisite
l
You have queried UMTS terminal analysis results. For details, see 10.6 Querying UMTS
Terminal Analysis Results.
Export terminal inventory analysis reports.
Procedure
1.
In the UMTS Terminal Analysis window, click Export Inventory Analysis

Report. The Save dialog box is displayed.
2.
Set a file directory name and specify a save path and file type. Then, click Save.
The system exports terminal inventory analysis reports of all analysis dimensions.
Export a terminal performance analysis report for a specified type of terminals.

1.
On the Terminal Performance Analysis tab page of the UMTS Terminal

Analysis window, select a certain type of terminals.
2.
Click Export Performance Analysis Report for the Selected Terminal. The Save
dialog box is displayed.
3.
Export terminal performance analysis reports for all types of terminals.

1.
In the UMTS Terminal Analysis window, click Export Performance Analysis

Report for All Terminals. The Save dialog box is displayed.
2.
Export all terminal analysis reports.

1.
In the UMTS Terminal Analysis window, click Export Terminal Analysis

Report. The Save dialog box is displayed.
2.
The exported reports include terminal inventory analysis reports and performance
analysis reports for all types of terminals.
----End
10.8 Technical Specifications for UMTS Terminal Analysis

This section describes the technical specifications for UMTS Terminal Analysis.
Issue 01 (2011-08-15)
Item

<= 10,000 cells
<= 5
<= 7 days
Negligible

(all the themes)
<= 200

232
Nastar
Item

<= 50
10.9 Reference to the UMTS Terminal Analysis Interface

This section describes the interface for UMTS terminal analysis and the relevant parameters.
Before performing relevant operations, familiarize yourself with the functions of UMTS terminal
analysis.
10.9.1 Interface Description: UMTS Terminal Analysis

This section describes the Terminal Inventory Analysis and Terminal Performance
Analysis tab pages of UMTS terminal analysis. Before performing relevant operations,
familiarize yourself with the functions of the areas on these tab pages.
Description of the Terminal Inventory Analysis Tab Page

This tab page displays the terminal inventory on the live network in tables and charts, as shown
in Figure 10-2.
Figure 10-2 Terminal Inventory Analysis tab page
Issue 01 (2011-08-15)

233
Nastar
SN
Item
Description
(1)
Toolbar
Provides four buttons for exporting inventory analysis reports,

terminal analysis reports, performance analysis reports of specific
terminals, and performance analysis reports of all terminals.
(2)
Statistical bar
chart
Displays the distribution proportion of each type of terminals on

the live network by a certain dimension in a pie chart. The pie chart
is displayed on the left, and the legends for the pie chart are
displayed on the right.
(3)
Statistical table Displays the number and distribution proportion of each type of
terminals on the live network by a certain dimension in a table.
Description of the Terminal Performance Analysis Tab Page

Figure 10-3 shows the Terminal Performance Analysis tab page.
Figure 10-3 Terminal Performance Analysis tab page
Issue 01 (2011-08-15)

234
Nastar
SN
Item
Description
(1)
KPI navigation
tree
Displays KPIs by category in the navigation tree. All KPIs are

selected by default.
(2)
Performance
Displays the performance counter value for a type of terminal in
counter value for cells and during various services.
a terminal type in
cells and during
various services
(3)
KPI value for

terminal type
Displays the values of KPIs related to each type of terminals.
10.9.2 Parameters for Creating and Modifying the Terminal Type

This section describes the parameters for creating and modifying the terminal type. You can
refer to this section when you create and modify the terminal type.
Description of Parameters Related to Terminals
Issue 01 (2011-08-15)
Parameter
Description
IMEI-TAC
Indicates the first eight digits of the International

Mobile Equipment Identity (IMEI) that identifies
the type of a terminal. The parameter is
mandatory.
Vendor
Indicates the vendor of a terminal. The parameter

is mandatory.
Terminal Model
Indicates the model of a terminal. The parameter

is mandatory.
Chip Model
Indicates the chip model of a terminal.
Terminal Technology
Indicates the system supported by a terminal. In

the system are GSM, WCDMA, TD-SCDMA,
GSM/WCDMA, GSM/TD-SCDMA, and
LTE.
Data Transfer
Indicates the transmission mode of data services

supported by a terminal. In the system are GPRS/
EDGE, GPRS/EDGE/HSDPA, and GPRS/
EDGE/HSPA.
Terminal Type
Indicates the type of a terminal. In the system are

Cellphone, Netbook, Home network
management device, and Fixed wireless
phone.

235
Nastar
NOTE
The system does not automatically display the manufacturers and models of terminals. Only the
manufacturers and models that are registered in the terminal type management are displayed.

Common Information
Parameter
Description
Task Name
OSS Name

E2E Task List
Begin Time

End Time
NE List
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Description
Service Type

Exception Type

failure.
KPI

determination.
Determination
rule

as >=.
Exception Value

UMTS VIP
Analysis Data
Task
Issue 01 (2011-08-15)
Selected

selected.

236
Nastar
Parameter
Description
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Group Name
Number of
Members
Report Raw Data

Description
Start NCC
End NCC
Start BCC
End BCC
ARFCN
Indication
Start ARFCN

End ARFCN
UMTS Service
Geographic
Analysis Data
Task
Downlink Ec/No
(dB)<=X

bad RxQual area.
value is -15.
UMTS
Terminal
Analysis Data
Task
Type
KPI name
Criterion
threshold

provided.
Issue 01 (2011-08-15)

237
Nastar
10.9.4 Parameters for Creating or Modifying UMTS Terminal

Analysis Tasks
This section describes the parameters for creating or modifying UMTS terminal analysis tasks.
You can refer to the description when creating or modifying a UMTS terminal analysis task.

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:

Parameter
Description
Task Type
time.
Time Range
analyzed.
Delayed
Delay.
Execution
Delay
Issue 01 (2011-08-15)


238
Nastar
Parameter
Description
NE
network.
NE Group
the entire network.
10.9.5 Parameters for Querying UMTS Terminal Analysis Results

This section describes the parameters for querying UMTS terminal analysis results. You can
refer to the description when querying UMTS terminal analysis results.
Overview
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
IMEITAC
Eigh
t
digit
s
N/A
Indicates the combination of the type approval code (TAC) and

the final assembly code (FAC) in an International Mobile
Equipment Identity (IMEI). An IMEI consists of 15 digits and
uniquely identifies a terminal in the world. In an IMEI, the TAC
refers to the first six digits, and the FAC refers to the seventh and
eighth digits. The combination of TAC and FAC uniquely
identifies a terminal.
Number
of
Terminal
s
[0,
+)
Nu
mbe
r
Indicates the number of terminals with the same IMEI-TAC and

different IMEIs.
Number
of RRC
Setup
Requests
(No
Service)
[0,
+)
Nu
mbe
r
Indicates the number of measurement reports (MRs) on the RRC

Connection Request message that carries the setup reason (cell
reselection, cell change command, registration, or separation).
Number
of
Abnorma
l RRC
Setups
(No
Service)
[0,
+)
Nu
mbe
r
Indicates the number of MRs on abnormal RRC connection setups

by sending an RRC Connection Request message that carries the
setup reason (cell reselection, cell change command, registration,
or separation).

239
Nastar
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Proportio
n of
Abnorma
l RRC
Setup
(No
Service)
[0,1
00]
Indicates the proportion of abnormal RRC connection setups (no

service).
Number
of RRC
Setup
Requests
(Service)
[0,
+)
Nu
mbe
r
Indicates the number of MRs on the RRC Connection Request

message that carries the setup reason (the setup reason is not cell
reselection, cell change command, registration, or separation).
Number
of
Abnorma
l RRC
Setups
(Service)
[0,
+)
Nu
mbe
r
Indicates the number of MRs on abnormal RRC connection setups

by sending an RRC Connection Request message that carries the
setup reason (the setup reason is not cell reselection, cell change
command, registration, or separation).
Proportio
n of
Abnorma
l RRC
Setup
(Service)
[0,1
00]
Indicates the proportion of abnormal RRC connection setups

(service).
Number
of RAB
Setup
Requests
[0,
+)
Nu
mbe
r
Indicates the number of MRs on the event that the core network
(CN) sends an RAB ASSIGNMENT REQUEST message after the
terminal signaling connection is set up successfully.
Number
of
Abnorma
l RAB
Setups
[0,
+)
Nu
mbe
r
Indicates the number of MRs on the event that the CN sends an

RAB ASSIGNMENT REQUEST message after the terminal
signaling connection is set up successfully but the CN does not
receive an RAB ASSIGNMENT RESPONSE message or the CN
receives an RAB ASSIGNMENT RESPONSE message that
contains Failure.
Proportio
n of
Abnorma
l RAB
Setup
[0,1
00]
Indicates the proportion of abnormal RAB setups after the terminal

signaling connection is set up successfully and the CN sends an
RAB ASSIGNMENT REQUEST message.

240
Nastar
Paramet
er
Ran
ge
Uni
t
Description
Number
of
Abnorma
l
Releases
[0,
+)
Nu
mbe
r
Indicates the total number of abnormal RAB releases. The RAB

is abnormally released in any of the following situations:
(1) The call is released by the RNC. If the RNC detects that a UE
fails to send data for a long time or if the RNC experiences an
exception (for example, SRB reset or exception on an AAL2 link
over the Iu interface), the RNC sends an RAB RELEASE
REQUEST message to request the CN to release the RAB or sends
an IU RELEASE REQUEST message to request the CN to release
the IU connection. Call releases initiated by the RNC with any of
the following cause values are considered as a normal release: User
Inactivity, Normal Release, Successful Relocation, Network
Optimization, UE Generated Signaling Connection Release. Call
releases initiated by the RNC with other cause values are
considered as abnormal release.
(2) The call is released by the CN. The CN sends an RAB
ASSIGNMENT REQUEST message to request the RNC to
release the RAB or sends an IU RELEASE COMMAND message
to request the RNC to release the IU connection. All call releases
initiated by the CN are considered as normal release.
(3) The call is released by a UE using a SIGNALING
CONNECTION RELEASE INDICATION message. Based on
domain information carried in the message, the RNC sends an IU
RELEASE REQUEST message to a related SGSN or MSC of the
CN to initiate IU connection release in the domain.After the IU
connection in the domain is released, the RNC initiates RRC
release for the UE if no IU connection in another domain is
available.Call release in this situation are considered as normal
release.
Issue 01 (2011-08-15)
Proportio
n of
Abnorma
l Release
[0,1
00]
Indicates the proportion of abnormal RAB releases.
Number
of SHO
Requests
[0,
+)
Nu
mbe
r
Indicates the number of soft handovers initiated by the terminal

during the service process. If multiple soft handovers are initiated
during the process of one call, the Nastar collects statistics on and
analyzes only the first and last handovers.
Number
of
Abnorma
l SHOs
[0,
+)
Nu
mbe
r
Indicates the number of abnormal soft handovers during the

service process. If multiple soft handovers are initiated during the
process of one call, the Nastar collects statistics on and analyzes
only the first and last handovers.
Proportio
n of
Abnorma
l SHOs
[0,1
00]
Indicates the proportion of abnormal soft handovers during the

service process. If multiple soft handovers are initiated during the
only the first and last handovers.

241
Nastar
Paramet
er
Ran
ge
Uni
t
Description
Number
of HHO
Requests
[0,
+)
Nu
mbe
r
Indicates the number of hard handovers initiated by the terminal

during the service process. If multiple hard handovers are initiated
during the process of one call, the Nastar collects statistics on and
analyzes only the last handover.
Number
of
Abnorma
l HHOs
[0,
+)
Nu
mbe
r
Indicates the number of abnormal hard handovers during the

service process. If multiple hard handovers are initiated during the
only the last handover.
Proportio
n of
Abnorma
l HHOs
[0,1
00]
Indicates the proportion of abnormal hard handovers during the

service process. If multiple hard handovers are initiated during the
only the last handover.
Number
of
Reports
for RRC
Setup
Delay
[0,
+)
Nu
mbe
r
Indicates the number of MRs with the valid interval between the
time when the terminal sends an RRC Connection Request
message and the time when the terminal receives an RRC
Connection Setup Complete message.
Average
RRC
Setup
Delay
[0,
+)
Indicates the average interval between the time when the terminal
sends an RRC Connection Request message and the time when the
terminal receives an RRC Connection Setup Complete message.
Proportio
n of Long
RRC
Setup
Delay
[0,1
00]
Indicates the proportion of MRs in which the interval between the

time when the terminal sends an RRC Connection Request
message and the time when the terminal receives an RRC
Connection Setup Complete message is greater than the specified
threshold to all MRs on the RRC connection setup delay.
Proportion of long RRC setup delay = Number of MRs in which
the interval between the time when the terminal sends an RRC
Connection Request message and the time when the terminal
receives an RRC Connection Setup Complete message is greater
than the specified threshold/Number of MRs with RRC connection
setup delay
Issue 01 (2011-08-15)
Number
of
Reports
for RAB
Setup
Delay
[0,
+)
Nu
mbe
r
Indicates the number of MRs with the valid interval between the
time when the terminal sends an RAB ASSIGNMENT REQUEST
message and the time when the terminal receives an RAB
ASSIGNMENT RESPONSE message.
Average
RAB
Setup
Delay
[0,
+)
Indicates the average interval between the time when the terminal
sends an RAB ASSIGNMENT REQUEST message and the time
when the terminal receives an RAB ASSIGNMENT RESPONSE
message.

242
Nastar
Paramet
er
Ran
ge
Uni
t
Description
Proportio
n of Long
RAB
Setup
Delay
[0,1
00]
Indicates the proportion of MRs in which the interval between the

time when the terminal sends an RAB ASSIGNMENT REQUEST
message and the time when the terminal receives an RAB
ASSIGNMENT RESPONSE message is greater than the specified
threshold to all MRs with RAB setup delay.
Proportion of long RAB setup delay = Number of MRs in which
the interval between the time when the terminal sends an RAB
ASSIGNMENT REQUEST message and the time when the
terminal receives an RAB ASSIGNMENT RESPONSE message
is greater than the specified threshold/Number of MRs with RAB
setup delay
Issue 01 (2011-08-15)
Number
of SQI
Reports
[0,
+)
Nu
mbe
r
Indicates the number of MRs with valid uplink SQI of the voice
service.
Proportio
n of Good
SQI
Reports
[0,1
00]
Indicates the proportion of MRs with uplink SQI (Good) that are
generated on the basis of the SQI statistical period during the
process of one call. This parameter reflects the voice quality during
the call process. You can use the SET USQICOUNT command to
set the threshold for good SQI. If the call duration is shorter than
the SQI statistical period, the Nastar does not collect statistics on
the SQI.
Proportio
n of
Accept
SQI
Reports
[0,1
00]
Indicates the proportion of MRs with uplink SQI (Accept) that are
set the threshold for acceptable SQI. If the call duration is shorter
than the SQI statistical period, the Nastar does not collect statistics
on the SQI.
Proportio
n of Bad
SQI
Reports
[0,1
00]
Indicates the proportion of MRs with uplink SQI (Bad) that are
set the threshold for bad SQI. If the call duration is shorter than
the SQI statistical period, the Nastar does not collect statistics on
the SQI.
As the Mean Opinion Score (MOS), SQI reflects the voice quality
during the call process. The SQI value ranges from 0 to 500. The
greater the SQI value, the better the voice quality.

243
Nastar
Paramet
er
Ran
ge
Uni
t
Description
Number
of
Reports
for AMR
Service
Duration
[0,
+)
Nu
mbe
r
Indicates the number of MRs with valid RAB occupation duration

during the voice service process.
1. Statistical start time:
Time when an RAB assignment is successful
Time when an incoming migration is successful
Time when an incoming inter-RAT handover is successful
2. Statistical end time:
Time when a terminal releases a call
Time when a terminal receives an IU REL CMD message (normal
release)
Time when a terminal receives an RB REL SUCC message
Issue 01 (2011-08-15)
Average
AMR
Service
Duration
[0,
+)
Indicates the average RAB occupation duration during the voice

service process.
Number
of
Reports
for VP
Service
Duration
[0,
+)
Nu
mbe
r

during the video-phone service process.
Average
VP
Service
Duration
[0,
+)
Indicates the average RAB occupation duration during the videophone service process.
Number
of
Reports
for Other
CS
Service
Duration
[0,
+)
Nu
mbe
r

during the process of a CS service (for example, streaming service)
other than the voice service and video-phone service.
Average
Duration
for Other
CS
Services
[0,
+)
Indicates the average RAB occupation duration during the process

of a CS service (for example, streaming service) other than the
voice service and video-phone service.
Number
of
Reports
for PS
Service
Duration
[0,
+)
Nu
mbe
r

during the R4 data service process.
For details about the RAB setup time and RAB release time, see
the description for the Number of Reports for AMR Service
Duration parameter.
Duration parameter.
Duration parameter.

244
Nastar
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Average
PS
Service
Duration
[0,
+)
Indicates the average RAB occupation duration during the R4 data

service process.
Number
of
Reports
for
HSDPA
Service
Duration
[0,
+)
Nu
mbe
r
Indicates the number of MRs with valid data transmission duration

during the HSDPA service process.
Average
HSDPA
Service
Duration
[0,
+)
Indicates the average data transmission duration during the

HSDPA service process.
Average
HSDPA
Rate
[0,
+)
kbit
/s
Indicates the ratio of the total volume of data that is transmitted

on the downlink to the valid data transmission duration during the
HSDPA service process.
Number
of
Reports
for
HSUPA
Service
Duration
[0,
+)
Nu
mbe
r

during the HSUPA service process.
Average
HSUPA
Service
Duration
[0,
+)
Indicates the average RAB occupation duration during the HSUPA

service process.
Number
of
Reports
for Other
PS
Service
Duration
[0,
+)
Nu
mbe
r

during the process of a PS service other than the R4 PS service,
HSDPA service, and HSUPA service.
Average
Duration
for Other
PS
Services
[0,
+)
The valid data transmission duration refers to the duration when

data is transmitted through the network during the service process.
Duration parameter.
Duration parameter.
s
Indicates the average RAB occupation duration during the process

of a PS service other than the R4 PS service, HSDPA service, and
HSUPA service.

245
Nastar
Cell Information
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
RNC ID
1 to
32
char
acter
s
N/A
Indicates the ID of the RNC where the terminal is located.
Cell ID
[0,2
047]
N/A
Indicates the ID of the cell where the terminal is located.
Cell
Name
1 to
64
char
acter
s
N/A
Indicates the name of the cell where the terminal is located.

246
Nastar
11
UMTS VIP Analysis
About This Chapter

The UMTS VIP analysis function enables you to obtain UMTS VIP analysis data, create UMTS
VIP analysis tasks, query UMTS VIP analysis results, and export UMTS VIP analysis reports
from the Nastar. By monitoring the KPIs related to the quality of service (QoS) of VIP
subscribers, the Nastar helps you identify and solve the network problems that may cause VIP
complaints so that the service quality of VIP subscribers is ensured and the satisfaction of VIP
subscribers is improved.
11.1 Basic Knowledge of UMTS VIP Analysis
This section describes the basic knowledge of UMTS VIP analysis, including UMTS VIP
analysis function and authority policies for UMTS VIP analysis.
11.2 UMTS VIP Analysis Process
This section describes the UMTS VIP analysis process.
11.3 Managing UMTS VIP Groups
This section describes how to manage UMTS VIP groups. The function of managing UMTS
VIP groups enables you to create VIP groups, modify the properties of existing VIP groups,
delete existing VIP groups, and export information about existing VIP groups. You can monitor
the service quality of VIP subscribers in a VIP group by creating VIP groups.
11.4 Obtaining UMTS VIP Analysis Data
This section describes how to enable the Nastar to obtain UMTS VIP analysis data. You can
create an E2E task to enable the Nastar to collect analysis data and create a data import task to
enable the Nastar to import the collected analysis data into the database.
11.5 Setting a Mailbox for Sending Analysis Reports
After a mailbox for sending analysis reports is set, the Nastar can send the generated analysis
reports to the specified mailboxes through the mailbox.
11.6 Creating UMTS VIP Analysis Tasks
This section describes how to create UMTS VIP analysis tasks. After you create a UMTS VIP
analysis task, the Nastar obtains the International Mobile Subscriber Identity (IMSI) reported
by a UE, and then aggregates and analyzes the number of service call reports of VIP subscribers
or VIP groups, traffic volume, and KPIs. This function helps to solve subscriber-level network
optimization problems so that service quality of VIP subscribers is ensured and VIP subscriber
satisfaction is improved.
Issue 01 (2011-08-15)

247
Nastar
11.7 Querying UMTS VIP Analysis Results

This section describes how to query UMTS VIP analysis reports. By monitoring the number of
service call records, traffic, and KPIs of the selected VIP subscriber, you can learn about the
quality of service (QoS) provided for the VIP subscriber and identify and solve the network
problems that may cause VIP complaints.
11.8 Querying UMTS VIP Trend Analysis Results
The Nastar provides functions for querying the analysis results of UMTS VIP trends, such as
setting trend analysis parameters, querying trend analysis results, and drilling down through
trend analysis results. By analyzing the trends based on periodic analysis results, the Nastar helps
network optimization engineers identify the KPI change trends during the monitoring and
optimization VIP KPIs. This implements further problem analysis and location.
11.9 Exporting UMTS VIP Analysis Reports
This section describes how to export UMTS VIP analysis reports. You can export the queried
VIP analysis results as .csv, .xls, or .xlsx files. The exported analysis results help you identify
network problems in advance and solve network problems that may cause complaints raised by
VIP subscribers.
11.10 Technical Specifications for UMTS VIP Analysis
This section describes the technical specifications for UMTS VIP Analysis.
11.11 Reference to the UMTS VIP Analysis Interface
This section describes the interface for UMTS VIP analysis and the relevant parameters. Before
performing relevant operations, familiarize yourself with the functions of UMTS VIP analysis.
Issue 01 (2011-08-15)

248
Nastar
11.1 Basic Knowledge of UMTS VIP Analysis

This section describes the basic knowledge of UMTS VIP analysis, including UMTS VIP
analysis function and authority policies for UMTS VIP analysis.
11.1.1 UMTS VIP Analysis Function

The UMTS VIP analysis function enables you to routinely monitor the calls of the selected VIP
subscribers on a UMTS network. The reports based on the routine monitoring help you know
the service quality experienced by VIP subscribers. This helps network optimization engineers
identify and solve potential network problems in advance, improving VIP subscriber
satisfaction.
VIP Analysis
The Nastar obtains the information about IMSIs reported by UEs during calls and finally helps
to solve the problems related to the subscriber-level network optimization through the
aggregation and analysis of KPIs (including network-level KPIs, service-level KPIs in CS and
PS domains, and KPIs of active cells) based on the VIP group level and VIP subscriber level.
l
Aggregation and analysis of KPIs by VIP group enable you to monitor the subscribers in
important groups in a centralized, convenient, and timely manner, hence improving
operation efficiency and reducing operation expenditure. In addition, this enables you to
identify problem VIP groups and problem VIP subscribers so that you can analyze and
solve the problems in advance to avoid losing the VIP subscribers.
The aggregation and analysis of KPIs based on the VIP subscriber level provide a detailed
analysis of KPI trends related to subscriber experience and behavior. For example, analysis
of variation trends based on voice service setup delay, analysis of variation trends based
on SQI distribution of voice service quality, analysis of variation trends based on data
service average rate, analysis of variation trends based on uplink BLER distribution of data
services, and analysis of variation trends based on service duration. In this manner, you can
quickly identify the VIPs with the worst and best service quality during a certain period
and learn about the time when network problems occur.
The Nastar also provides an in-depth analysis for the VIP subscribers whose raw data is collected
in advance. If the KPIs of some VIP subscribers in a group deteriorate but the problem cannot
be located on site, the Nastar helps network optimization engineers retrieve the detailed call
reports of these VIP subscribers within a specified period. By analyzing these reports, the
network engineers quickly locate the key call report that results in the deterioration of KPI values,
and then analyzes the information such as the network quality and signaling procedure before
link release and exception causes to locate problems.
Aggregation and analysis of KPIs of active cells by VIP group and VIP subscriber help network
optimization engineers learn about the main active areas of VIP subscribers on the network. If
there are any network problems in these active areas, the network optimization engineers can
quickly identify the key cells that need to be preferentially handled to solve these network
problems and solve the problem of the service quality deterioration caused by these network
problems in time.
Limitations
l
Issue 01 (2011-08-15)
The UMTS VIP analysis function allows NEs to report raw call data of important VIP
subscribers to the Nastar. The amount of raw data is huge. Therefore, limitations are
249
Nastar
required to prevent the system from becoming overloaded in the case of concurrent
operations by a large number of users. In the case of analysis by VIP group, the Nastar can
analyze data of 30,000 VIP subscribers (that is, the number of VIP subscribers in all VIP
groups that are selected for the analysis cannot exceed 30,000). In the case of analysis by
VIP subscriber, the Nastar can analyze data of 2,000 VIP subscribers (that is, the number
of VIP subscribers in all the VIP groups that are allowed to report raw data cannot exceed
2,000).
l
If further analysis for VIP subscribers fails, the number of call records under an RNC may
be too excessive. Therefore, you are advised to set the period for executing a task to hour
(s) and the number of subscribers whose call records are reported to 100 or below during
VIP analysis.
The Nastar can combine the call records upon inter-RNC handovers. That is, if inter-RNC
handovers occur during a call, the Nastar combines the call records for the same call.
However, if two inter-RNC handovers occur within 30s and the Nastar fails to obtain the
data of one RNC, the Nastar will combine the CHR records of the two calls into one.
11.1.2 Authority Policies for UMTS VIP Analysis

The Nastar provides secure authority management policies to ensure the security of private
information for subscribers. The authority management policies enable different types of users
to have different operation rights for the security of their private information.
Introduction to Authority Types

l
View rights allow users to view a security object on the Nastar client. If a user can view a
security object on the Nastar client, the user has the view rights to this security object. Here,
security objects refer to VIP groups for VIP analysis tasks.
View rights are associated with the management domain. If a security object is added to
the management domain of a user or a user group, the user or users in the group have the
view rights to this security object.
For details about how to enable view rights for users, see the description in "Management
domain of user" in Creating an Nastar User Account.
Operation rights allow users to perform an operation. If a user has operation rights, the user
can perform a specific operation. Here, operation rights include query rights to VIP analysis
tasks, operation rights to VIP analysis tasks, management rights to VIP groups, and rights
to create, modify, and delete subnets.
Operation rights are associated with the management domain. A user can perform the
operation corresponding to the operation rights for only the objects in the management
domain of the user.
Query rights to VIP analysis tasks: If a Nastar user has the rights, the user can query
the authorized VIP analysis tasks.
Operation rights to VIP analysis tasks: If a Nastar user has the rights, the user can create,
modify, query, or delete the authorized VIP analysis tasks.
Management rights to VIP groups: If a Nastar user has the rights, the user can create,
modify, query, or delete the authorized VIP groups.
If a Nastar user not in the administrator group has the rights create, modify, and delete
subnets, the Nastar adds the VIP groups created by this user to the management domain.
These VIP groups are visible to other users not in the administrator group.
For details about how to enable operation rights for users, see the description in "Operation
rights of user" in Creating an Nastar User Account.
Issue 01 (2011-08-15)

250
Nastar
Introduction to Authority Policies

The authority policies for each type of user to manage VIP groups are as follows:
l
Users in the administrator group: This type of user has view rights and operation rights
initially. That is, the user is authorized to create VIP groups, and modify, query, or delete
information about VIP groups created by any user.
Users not in the administrator group:

To create VIP groups, the user in the administrator group or security administrator group
must have operation rights to VIP groups and rights to create, modify, and delete
subnets.
For details, see Scenario 1 in Table 1.
To modify, query, or delete information about VIP groups created by the user in the
administrator group or security administrator group, the user does not need other rights.
To modify or delete information about VIP groups created by other users the user in the
administrator group or security administrator group must have operation rights and view
rights to VIP groups.
To query information VIP groups created by other users, the user in the administrator
group or security administrator group must have view rights to VIP groups.
The authority policies for each type of user to manage VIP analysis tasks are as follows:
l
Users in the administrator group: This type of user has view rights and operation rights to
all VIP analysis tasks initially. That is, the user is authorized to create VIP analysis tasks,
and modify, query, or delete VIP analysis tasks created by any user.

To create a VIP analysis task involving only the VIP groups created by the user in the
administrator group or security administrator group, the user must have operation rights
to VIP analysis tasks. (The authority policies for this type of user to modify and delete
VIP analysis tasks in this situation are the same as those to create VIP analysis tasks.)
To create a VIP analysis task involving VIP groups created by other users, the user in
the administrator group or security administrator group must have view rights to VIP
groups created by other users and have operation rights to VIP analysis tasks. (The
authority policies for this type of user to modify and delete VIP analysis tasks in this
situation are the same as those to create VIP analysis tasks.)
To query information about VIP analysis tasks created by the user in the administrator
group or security administrator group, the user does not need other rights.
To query VIP analysis tasks created by other users, the user in the administrator group
or security administrator group must have view rights to VIP groups created by other
users and have query rights to VIP analysis tasks.
Issue 01 (2011-08-15)
To ensure the security of private information for subscribers, asterisks (****) are used to
shield the last four digits of IMSI and MS Number in VIP analysis results.
251
Nastar
Example of Authority Policies

Authority policies vary according to the specific scenario. Table 11-1 describes the authority
policies in different scenarios.
NOTE
"User" in Table 11-1 refers to a user in the administrator group or security administrator group.
Table 11-1 Example of authority policies

Scenario
Operation Procedure
Scenario 1
1. Log in to the Nastar client as a user, for

example, user admin.
User A needs to create three VIP groups,

namely, VIP_a, VIP_b, and VIP_c.
2. Assign user A rights to manage VIP groups

and rights to create, modify, and delete
subnets.
In the Select Operation Rights dialog box,
add Create Subnet, Delete Subnet, and
Modify Subnet under Operation > Topo
Management, and VIP Group
Management under Operation > Nastar
PA to Selected Rights, and click OK. For
details, see Creating an Nastar User Account.
3. Log in to the client as user A.
4. Create three VIP groups, namely, VIP_a,
VIP_b, and VIP_c.
For details about how to create VIP groups,
see 11.3 Managing UMTS VIP Groups.
Scenario 2
User A needs to create a VIP analysis task
named X. Only the three VIP groups
(VIP_a, VIP_b, and VIP_c) created by
user A are involved in this analysis task.

2. Assign user A operation rights to VIP
analysis tasks.
add Operation > Nastar PA > UMTS VIP
Analysis to Selected Rights, and click OK.
For details, see Creating an Nastar User
Account.
4. Create a VIP analysis task named X.
For details about how to create VIP analysis
tasks, see 11.6 Creating UMTS VIP
Analysis Tasks.
Issue 01 (2011-08-15)

252
Nastar
Scenario
Operation Procedure
Scenario 3

User A needs to create a VIP analysis task

named Y. Two VIP groups (VIP_d and
VIP_e) created by user B are involved in
this analysis task.
2. Assign user A view rights to VIP_d and

VIP_e.
In the Select Domain dialog box, add
VIP_d and VIP_e under All Objects >
Network Device > Object Set > Subnet
Device Set to Selected devices and object
sets, and click OK. For details, see Creating
an Nastar User Account.
3. Assign user A operation rights to VIP
analysis tasks.
Analysis to Selected Rights, and click OK.
For details, see Creating an Nastar User
Account.
5. Create a VIP analysis task named Y.
For details about how to create VIP analysis
tasks, see 11.6 Creating UMTS VIP
Analysis Tasks.
Scenario 4
Log in to the client as user A.
User A needs to query analysis task X

created by user A.
Issue 01 (2011-08-15)

253
Nastar
Scenario
Operation Procedure
Scenario 5

User B needs to query analysis task X

created by user A. Three VIP groups
(VIP_a, VIP_b, and VIP_c) created by
user A are involved in this analysis task.
2. Assign user B view rights to VIP_a, VIP_b,

and VIP_c.
VIP_a, VIP_b, and VIP_c under All
Objects > Network Device > Object Set >
Subnet Device Set to Selected devices and
object sets, and click OK. For details, see
Creating an Nastar User Account.
3. Assign user B view rights to VIP analysis
tasks.
Analysis Task View to Selected Rights, and
click OK. For details, see Creating an Nastar
User Account.
4. Log in to the client as user B.
5. Query analysis results and trend analysis
results of VIP analysis task X.
For details about how to query VIP analysis
results and VIP trend analysis results, see
11.7 Querying UMTS VIP Analysis
Results and 11.8 Querying UMTS VIP
Trend Analysis Results.
Scenario 6
User B needs to modify detailed
information about VIP groups VIP_a,
VIP_b, and VIP_c created by user A.

and VIP_c.
3. Assign user B management rights to VIP
groups.
add Operation > Nastar PA > VIP Group
Management to Selected Rights, and click
OK. For details, see Creating an Nastar User
Account.
5. In the VIP Group Management window,
modify detailed information about these VIP
groups.
Issue 01 (2011-08-15)

254
Nastar
Scenario
Operation Procedure
Scenario 7

User B needs to query detailed information

about VIP groups VIP_a, VIP_b, and
VIP_c created by user A.

and VIP_c.
4. In the VIP Group Management window,
double-click each VIP group to query
detailed information.
11.2 UMTS VIP Analysis Process

This section describes the UMTS VIP analysis process.
Figure 11-1 shows the process of UMTS VIP analysis.
NOTE
Required rights must be assigned to users to properly perform VIP analysis tasks. For details about authority
policies, see 11.1.2 Authority Policies for UMTS VIP Analysis.
Issue 01 (2011-08-15)

255
Nastar
Figure 11-1 Process of UMTS VIP analysis

Table 11-2 Description of UMTS VIP analysis process
Issue 01 (2011-08-15)
No.
Procedure
Description
Manage UMTS
VIP groups
In the Analysis Task Management window on the Nastar

client, you can enter the VIP group management window to
create VIP groups and subscribers required for VIP analysis.
After creating VIP groups and subscribers, the Nastar
performs VIP analysis by VIP subscriber or VIP group.

256
Nastar
No.
Procedure
Description
Create a UMTS
VIP analysis data
E2E task
You can choose Maintenance > E2E Task Management

on the Nastar client to open the E2E Task Management
window and then create a E2E task. After you create the task,
the Nastar issues rule files to the M2000, and then the M2000
sends the rule files to the related SAU. Then, the SAU
performs the measurement task.
Create a UMTS VIP

analysis data import
task
You can choose Maintenance > Task Management on the

Nastar client to open the Task Management window and
then create a UMTS VIP analysis data import task. After the
task is created, the Nastar periodically imports the UMTS
VIP data files saved on the Nastar server into the database.
Check the integrity

of UMTS VIP
analysis data

required UMTS VIP analysis data is imported into the
database.
Create a UMTS
VIP analysis task

client, you can create a UMTS VIP analysis task. After the
task is created, the Nastar periodically retrieves UMTS VIP
analysis data and UMTS configuration data from the
database, analyzes the retrieved data, and then generates
analysis results.
Query UMTS VIP

analysis results
You can view the analysis results of the UMTS VIP analysis
tasks that are executed successfully and also perform
comprehensive analysis on maps.
Export UMTS VIP

analysis reports
You can enable the Nastar client to export UMTS VIP

11.3 Managing UMTS VIP Groups

This section describes how to manage UMTS VIP groups. The function of managing UMTS
VIP groups enables you to create VIP groups, modify the properties of existing VIP groups,
delete existing VIP groups, and export information about existing VIP groups. You can monitor
the service quality of VIP subscribers in a VIP group by creating VIP groups.
Context
IMSI refers to the international mobile subscriber identity. The IMSI is a 15-digit string formed
by digits 0 to 9. The structure of the IMSI from the left to the right is MCC+MNC+MSIN. The
MNC and the MSIN forms the NMSI.
Where:
l
MCC refers to the mobile country code of a mobile subscriber.
MNC refers to the mobile network code, namely, the PLMN code of a mobile subscriber.
Issue 01 (2011-08-15)

257
Nastar
PLMN refers to the public land mobile network.

l
MSIN refers to the mobile subscriber identification number.
NMSI refers to the national mobile subscriber identification. This identification can
uniquely identify an MS in a country.
The VIP group file to be imported must include the following fields: Group Name, Priority,
and Description, as shown in Table 11-3. The match sequence of columns is restricted and
automatic matching of columns is not supported.
Table 11-3 Example of a VIP group file
VIP
Group
Number
of
Members
Level
Creator
Creation
Time
Description
Group1
50
High
admin
2010-05-10
08:30:10
Second level
director of **
Group
Group2
100
Low
admin
2010-05-11
09:40:50
Project
manager of **
Group
The import and export of VIP group files in .csv, .xls, and .xlsx formats are supported.
Procedure
Step 1 Double-click Function List > System Function > VIP Group Management from the
navigation tree in the Analysis Task Management window. The VIP Group Management
TIP
You can also choose Function List > System Function > VIP Group Management from the navigation
tree in the Analysis Task Management window and right-click Open. The VIP Group Management
Step 2 On the UMTS VIP Group tab page, create a VIP group.
l Create a VIP group by adding a new VIP group.
1.
Click New. The VIP Group Management - Create VIP Group dialog box is
displayed.
2.
Set Group Name, Class, and Description.

If the asterisk (*) is present on the right of a parameter, it indicates that the setting of
this parameter is mandatory.
3.
Select one or multiple VIP subscribers from the Members list.

You can add, import, export modify, and delete a VIP group.
Issue 01 (2011-08-15)

258
Nastar
If you need to ...
Then ...
Create a VIP subscriber
a. Click Create. The VIP User Management

b. Set User Name, Phone, IMSI, and
Description.
If the asterisk (*) is present on the right of a
parameter, it indicates that the setting of this
parameter is mandatory.
For details about parameters, see 11.11.3
Parameters for Creating and Modifying
UMTS VIP Subscribers/VIP Groups.
c. Click OK.
Import VIP subscriber

information
Click Import.
If an .xls or .xlsx file is imported and the file
contains multiple sheets, a message is displayed
for you to select the sheet to be imported.
If file import fails, a message is displayed for you
to show the failure cause. You can modify the file
as required and import it again.
Export VIP subscriber

information
Click Export.
Modify VIP subscriber

information
Click Modify to set parameters related to the VIP

subscriber again. You can modify the user name,
MS number, and description information, but
cannot modify the IMSI.
The VIP subscriber information is exported as

a .csv, .xls, or .xlsx file.
For details about parameters, see 11.11.3

Parameters for Creating and Modifying UMTS
VIP Subscribers/VIP Groups.
Delete a VIP subscriber
4.
Click Delete.
Click OK.
l Create a VIP group by importing a VIP group file.

1.
Click Import. The Open dialog box is displayed.
2.
Select a VIP group file, and then click Open.

If an .xls or .xlsx file is imported and the file contains multiple sheets, a message is
displayed for you to select the sheet to be imported.
NOTE
l If multiple lines of information about Priority and Description for a VIP group are
inconsistent in the imported VIP group file, the system imports the last line of information
and displays the information in Priority and Description on the UMTS VIP Group tab
page. It is recommended that the description and priority information in different lines
regarding a VIP group be the same when you define the VIP group information.
l If the Priority column is empty, Medium is displayed by default.
Issue 01 (2011-08-15)

259
Nastar
3.
Click Modify. The UMTS VIP Group Management-Modify VIP Group dialog box
is displayed.
4.
You can add, import, export modify, and delete a VIP group, for details, see Table.
5.
Click OK.
----End
Follow-up Procedure
On the UMTS VIP Group tab page, select the information about a VIP group, and then perform
operations as required.
If you need to ...
Then ...
Modify a VIP group
Click Modify to set parameters related to the VIP group

again.
For details about parameters, see 11.11.3 Parameters
for Creating and Modifying UMTS VIP
Subscribers/VIP Groups.
NOTE
If the VIP group is used by other tasks, the modification does
not affect the ongoing tasks. If the VIP group is used by a
periodic task, the related information is updated in the next
period after the modification.
Export information about existing

VIP groups
Click Export.
Delete a VIP group
Click Delete.
NOTE
If the VIP group is used by other tasks, the modification does
not affect the ongoing tasks. If the VIP group is used by a
periodic task, the related information is updated in the next
period after the modification.
View the information about

members of a VIP group
Double-click a VIP group to view members of the VIP

group.
11.4 Obtaining UMTS VIP Analysis Data

This section describes how to enable the Nastar to obtain UMTS VIP analysis data. You can
create an E2E task to enable the Nastar to collect analysis data and create a data import task to
enable the Nastar to import the collected analysis data into the database.

Issue 01 (2011-08-15)

260
Nastar
Prerequisite
l
Configuration Data.
Context
Procedure
displayed.
TIP

1.
2.
NOTE
OSS to be analyzed.
Step 4 Click Next.

CAUTION
Issue 01 (2011-08-15)

261
Nastar
step.
If...
Then...
data E2E task
list.


task

E2E task

list.



----End
Follow-up Procedure
If you need to...
Then...
Click Property.
Click Delete.
NOTE

Issue 01 (2011-08-15)
Click Refresh.

262
Nastar
If you need to...
Then...
shortcut menu.
NOTE

Prerequisite
Context
l
at the preset time.
Issue 01 (2011-08-15)
Analysis Task
Type
Creation
GSM MR Analysis

Analysis Data
Manual creation
GSM Neighboring
Cell Analysis

Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation

263
Nastar
Analysis Task
Type
Creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Manual creation
GSM VIP Analysis

Data
Manual creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Manual creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
Issue 01 (2011-08-15)
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis

Analysis Data
Manual creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Data
Manual creation
UMTS Coverage
Analysis

Analysis Data
Manual creation
UMTS VIP
Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis

Analysis Data
Manual creation

264
Nastar
Analysis Task
Type
Creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis

Analysis Data
Manual creation
UMTS Service
Geographic
Analysis

Analysis CHR Data
Manual creation

Analysis MR Data
CDMA Uplink
Interference
Ranking Analysis
Import CDMA Uplink

Analysis Data
Manual creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis

Manual creation
CDMA Complaint
Analysis Support
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

(1X)
Manual creation

Cell Analysis Data
(EVDO)
l Import CDMA Pilot

(EVDO)
CDMA Coverage
Analysis

Analysis Data (1X)
Manual creation

Issue 01 (2011-08-15)
CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis

Manual creation

265
Nastar
Analysis Task
Type
Creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis

Data
Manual creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis

Analysis Data
Manual creation
LTE Complaint
Analysis Support
LTE Cell Fault

Diagnosis
Analysis
Procedure
1.
2.
3.
Periodic.

1.
NOTE
2.

----End
Follow-up Procedure
Issue 01 (2011-08-15)

266
Nastar
If you need to...
Then...
Delete a task
Click Delete.
NOTE
Suspend a task or
resume a task

l Manual mode
the shortcut menu.
l Automatic mode
NOTE

of a task
Running to Idle.
NOTE
11.4.3 Checking the Integrity of VIP Analysis Data

Prerequisite
l
Context
The data for VIP analysis includes configuration data and VIP analysis data.
Procedure
TIP
Step 2 Set Data Type to *** VIP analysis data on the left of the Query Data dialog box.
Issue 01 (2011-08-15)

267
Nastar

required.
Step 5 Select the VIP group to be queried in the VIP group navigation tree.
Step 6 Click Query.
l The Overview tab page displays NEs with data and the data time range (start time and end
time) of the NEs. The start time and end time are the actual time when the data is generated,
but not the time when the data is imported into the Nastar database.
l Each NE Name tab page displays detailed hourly data of an NE with data. On the tab page,
green cells indicate that VIP analysis data is available in the hour; white cells indicate that
no VIP analysis data is available in the hour.
If the data has been subscribed, the E2E task, the data collection task, and the data import task
is normal, but no relevant analysis data is displayed, contact Huawei technical support personnel.
----End
11.5 Setting a Mailbox for Sending Analysis Reports

After a mailbox for sending analysis reports is set, the Nastar can send the generated analysis
reports to the specified mailboxes through the mailbox.
Prerequisite
Procedure
Step 1 Choose Maintenance > E-mail Sending Setting. The Email Sending Setting window is
displayed.
Step 2 Set the parameters for the mailbox.
For details about parameters, see Parameters for Setting the Mailbox of Analysis Results.
Step 3 Click OK.
----End
Follow-up Procedure
When creating a VIP analysis task, you can select the mailbox that is already set or select an
FTP server to send VIP analysis reports.
11.6 Creating UMTS VIP Analysis Tasks

This section describes how to create UMTS VIP analysis tasks. After you create a UMTS VIP
analysis task, the Nastar obtains the International Mobile Subscriber Identity (IMSI) reported
by a UE, and then aggregates and analyzes the number of service call reports of VIP subscribers
Issue 01 (2011-08-15)

268
Nastar
or VIP groups, traffic volume, and KPIs. This function helps to solve subscriber-level network
optimization problems so that service quality of VIP subscribers is ensured and VIP subscriber
satisfaction is improved.
Prerequisite
l
An analysis task can be performed once or periodically. A periodic task is performed by

hours, days, or weeks.
Context
Procedure
Step 1 Click
TIP
Step 3 Click Next.
Step 4 Select one or multiple VIP groups.
Step 5 On the VIP KPI Threshold Setting tab page, set the threshold of each KPI.
l If the KPI value of a subscriber does not reach the threshold, this KPI is considered as a
problem KPI or a deteriorating KPI.
l Double-click a cell corresponding to a KPI in the Threshold column and keep the pointer
in the cell for several seconds. The threshold range of the KPI is displayed.
l To apply the modified threshold to subsequent VIP analysis tasks, click Apply. To restore
the modified threshold to the initial value, click Default.
Step 6 Click Next.
Step 7 Set the execution time for the task.
If...
Then...
Task Type is set to One-time
Set the time range and the start time of the

task.
Task Type is set to Period
Set the start time, the period, and the number

of execution times.
Step 8 Click Next.

Issue 01 (2011-08-15)

269
Nastar
Step 9 Optional: On the Export Analysis Report tab page, set the parameters for automatically
exporting an analysis report so that VIP analysis results can be automatically exported from the
Nastar client and saved on the Nastar server.
Report Name and Saving Path retain the default values and cannot be modified. File
Format can only be set to Excel. If you need to save an analysis report as a compressed file,
select Compress.
Step 10 Optional: Set relevant parameters on the Email User Setting tab page to enable the Nastar to
automatically send VIP analysis results to multiple mailboxes through e-mail.
l Select Auto-sending of analysis reports by Email.
l Click Add to select the mailboxes for sending the VIP analysis result.
In the Analysis Task Management window, double-click System Function > Management
of Automatical Delivering to User to set the mailbox for sending VIP analysis results.
Alternatively, you can click Create to create a new mailbox or click Import to import the
information about the existing mailboxes in batches.
l Select the report type of different level from the Sending Content drop-down list.
l Email Subject and Email Content retain the default values and cannot be modified.
----End
Follow-up Procedure
TIP
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Save as the tasks
Refresh
Issue 01 (2011-08-15)

Suspended.
Resume.
, or right-click
, or right-click

Click

270
Nastar
11.7 Querying UMTS VIP Analysis Results

This section describes how to query UMTS VIP analysis reports. By monitoring the number of
service call records, traffic, and KPIs of the selected VIP subscriber, you can learn about the
quality of service (QoS) provided for the VIP subscriber and identify and solve the network
problems that may cause VIP complaints.
Prerequisite
l
The progress bar of the UMTS VIP analysis task reaches 100%.
Procedure
Step 1 Choose UMTS VIP Analysis Task from the navigation tree in the Analysis Task
Management window.
tasks.
If a theme analysis task is executed more than 30 days, only result records of the latest 30 days
are displayed in the analysis result list. For example, the start time of a created VIP analysis task
is September 1, 2010. If the task is executed more than 30 days (if the task execution period is
12 hours, the task is executed more than 60 times), the result record on September 1, 2010 will
be deleted and the result records of 30 days from September 2, 2010 to October 1, 2010 are
reserved when the task is executed on October 1, 2010.
Result from the shortcut menu. The UMTS VIP Analysis Task window is displayed.
NOTE
Step 5 Query UMTS VIP analysis results in the UMTS VIP Analysis Task window.
1.
Select an object type to be queried on the right of the toolbar, including the ALL, Group, or
User.
2.
Select a VIP subscriber record or a VIP group record from the VIP group information list
in the left pane.
3.
On the Network Level KPI, CS Service KPI, PS Service KPI, and Active Cell tab pages
in the right pane, view detailed information about each service KPI and its change trend.
For the description of the related parameters, see 11.11.6 Parameters for Querying UMTS
VIP Analysis Results.
l The change trends of the KPIs are displayed in the KPI list area on the right only after
a VIP group is selected as the analysis object.
You can double-click a chart to zoom in and then double-click the chart again to restore
it to the normal size.
l The display options provided for different change trend charts are as follows:
Issue 01 (2011-08-15)

271
Nastar
In the change trend chart of a network-level KPI, the options to display Service and
Non-service are provided.
In the change trend chart of a CS KPI, the options to display AMR, VP, and
Other are provided.
In the change trend chart of a PS KPI, the options to display PS, HSDPA,
HSUPA, and Other are provided.
l Multiple KPI fields and services are involved in the AMR of SQI Distribution, UL
BLER Distribution, and RAB Negotiated Final Rate Distribution change trend
charts. That is, 3 (1 x 3 = 3) curves are included in the AMR of SQI Distribution chart;
12 (2 x 6 = 12) curves are included in the UL BLER Distribution chart; 2 (2 x 1 = 2)
curves are included in the RAB Negotiated Final Rate Distribution chart.
l On the Active Cell tab page, query active cell analysis results of the selected VIP group
or VIP subscriber.
in the upper part of the VIP group overview table, and click
in the upper
Click
left of the Nastar client window to open the Service Geographic Observation window.
The node corresponding to the selected theme is added to the navigation tree on the
left of the GIS window. The naming convention of the theme node is Network
system_Task name. The added node contains subnode Active Cell and various KPI
nodes. For details about the KPIs, see Description of parameters related to active
cell KPIs in 11.11.6 Parameters for Querying UMTS VIP Analysis Results.
If multiple VIP analysis result windows related to one network system are opened
at the same time, the GIS window can synchronously display information of one
analysis result window. Only one theme node is displayed in the navigation tree
on the left of the GIS window and corresponds to the VIP analysis results related
to one network system.
If the VIP analysis result window that is synchronously displayed with the GIS
window is closed, the theme node corresponding to the VIP analysis task is
automatically deleted from the navigation tree on the left of the GIS window,
and the rendering layer corresponding to the VIP analysis results is also
automatically deleted from the map area on the right.
When you open the GIS window initially, active cell nodes and KPI nodes under a
theme node are not selected by default. The geographic information can be displayed
only after a node under the theme node is selected.
After you select the Active Cell node under a theme node in the navigation tree on
the left of the GIS window, all active cells related to the VIP groups or VIP
subscribers involved in the currently selected analysis task are rendered in the map
area on the right.
If cells whose engineering parameters are not imported exist, a message is
displayed on the right of the window.
In the active cell list on the right of the VIP analysis result window, select a cell
record. The selected cell is centered and rendered in the map area of the GIS
window. Only one active cell can be selected at a time.
If multiple VIP analysis result windows related to different network systems are
opened and the GIS synchronous display function is enabled, multiple render
layers are automatically loaded in the map on the right after you select active cell
nodes or KPI nodes under multiple theme nodes in the navigation tree on the left
of the GIS window. After you clear the check boxes before the nodes, the render
layers are automatically deleted from the map.
Issue 01 (2011-08-15)

272
Nastar
After you select a KPI node under a theme node in the navigation tree on the left of
the GIS window, all active cells corresponding to the KPI for the VIP groups or VIP
subscribers involved in the currently selected analysis task are rendered in segment
in the map area on the right.
to open the Layer
The selected KPI corresponds to a layer. You can click
Management dialog box and query the layer information.
The names of these layers start with businessLayer.
The system collects KPI results corresponding to each cell and dynamically
separates these results into N parts (a maximum of five parts) on average to render
them in different colors. Each KPI result segment is rendered by one color.
Step 6 Start subscriber-level further analysis.
If certain KPIs of a VIP subscriber are abnormal according to the query results and further
analysis is required, select the basic information about the VIP subscriber and choose Deep
Analysis from the shortcut menu to start the complaint analysis support function for further
analysis.
For details about parameters, see 12.7.4 Parameters for Querying UMTS Complaint Analysis
Support Results.
----End
Follow-up Procedure
You can export analysis results. For details, see 11.9 Exporting UMTS VIP Analysis
Reports.
11.8 Querying UMTS VIP Trend Analysis Results

The Nastar provides functions for querying the analysis results of UMTS VIP trends, such as
setting trend analysis parameters, querying trend analysis results, and drilling down through
trend analysis results. By analyzing the trends based on periodic analysis results, the Nastar helps
network optimization engineers identify the KPI change trends during the monitoring and
optimization VIP KPIs. This implements further problem analysis and location.
Prerequisite
l
A periodic UMTS VIP analysis task is created.
Procedure
Step 1 Choose UMTS VIP Analysis from the navigation tree on the left of the Analysis Task
Management window.
If you choose Theme Function, the task list in the right pane displays all the performance
analysis tasks.
Step 2 Select a record of the period task from the task list in the upper right pane.
Issue 01 (2011-08-15)

273
Nastar
Step 3 Right-click the selected analysis result from the analysis result list in the lower right pane, and
choose Trend Analysis from the shortcut menu. The Trend Analysis Setting window is
displayed.
If a theme analysis task is executed for more than 30 days, the result records of only the last 30
days for the task are displayed in the analysis result list. For example, the start time of a created
VIP analysis task is September 1, 2010. If the task is executed for more than 30 days (if the task
period is 12 hours, the task is executed for more than 60 times), the result record on September
1, 2010 will be deleted and the result records of 30 days from September 2, 2010 to October 1,
2010 are saved when the task is executed on the 31st day.
Step 4 In the Trend Analysis Setting window, set trend analysis attributes, as shown in Table 11-5.
Table 11-5 Setting trend analysis attributes
Tab Page
Setting Description
User Object
Selects VIP groups for trend analysis.

Only the VIP groups selected during the creation of a VIP analysis task
are displayed. By default, all VIP groups selected during the creation of
a VIP analysis task are selected.
Counter
Selects KPIs to be analyzed.

You can select multiple KPIs at a time and set KPI search criteria.
Time
Specifies the time range for trend analysis.

l Time dimension cannot be changed and must be consistent with the
setting for a periodic task. If the execution period is Day for a created
periodic task, Time dimension is set to Day.
l Continuous period indicates that the KPI trends during a continuous
period are analyzed. If Time dimension is set to Day or Week, set the
start date and end date. If Time dimension is set to Hour, set the start
date and end date and specify exact hours for the dates.
l Specified period indicates that the KPI trends during multiple
continuous periods are analyzed.
NOTE
The number of the analysis results in the selected time range can not be more than
30.
Issue 01 (2011-08-15)

274
Nastar
Tab Page
Setting Description
Set Filter
Criteria
Obtains required subscribers for analysis.

For example, if you want to obtain subscribers whose total number of
initial access requests is greater than 10 and number of abnormal call
releases is greater than 2 during three consecutive periods, do as follows:
1. Click Add. The Add Filter Criteria dialog box is displayed.
2. Set Criterion Name.
3. On the Counter tab page, click Object.
4. In the Select Counter dialog box, select required KPIs, and click
OK.
For example, select Total number of initial access requests and
Number of abnormal call releases.
5. On the Counter tab page, select a KPI and specify its value range.
For example, specify the value of Total number of initial access
requests greater than 10 and the value of Number of abnormal call
releases greater than 2.
6. In the lower part of the Counter tab page, set the And and Or
relationships between the selected KPIs.
For example, set the And relationship for Total number of initial
access requests > 10 and Number of abnormal call releases > 2.
7. On the Time tab page, specify the time range meeting filter criteria.
For example, select N continuous periods and set N to 3.
8. Click OK.
Step 5 Click OK. The UMTS VIP Trend Analysis window is displayed.
Step 6 Query trend analysis results.
1.
Select an object to be queried in the left pane.

By default, all users and KPIs are selected.
2.
On the Chart tab page in the right pane, query the trend analysis chart.
The x-axis of the chart indicates the task execution period and displays time information
about all periodic tasks. Detailed time information and value are displayed after you click
a point in a chart. For details about the trend analysis chart, see 11.11.2 Interface for UMTS
VIP Trend Analysis.
3.
On the Table tab page in the right pane, query the trend analysis table.
The trend analysis table contains all parameter values of the selected objects during the
specified periods.
Step 7 Optional: Drill down through trend analysis results.

If you find that the value of a KPI at the certain time is abnormal during the trend analysis within
the specified period, you can drill down through the detailed analysis results for this KPI during
a certain period using the time drilldown function.
Click Time Drilldown and choose the analysis period to switch to the VIP analysis result
window.
----End
Issue 01 (2011-08-15)

275
Nastar
Follow-up Procedure
l
Click Export raw trend analysis data on the toolbar to export trend analysis reports
in .csv, .xls or .xlsx format of the following dimensions: All, VIP group, and VIP subscriber.
Click Trend Analysis Attributes on the toolbar to query the trend analysis attributes.
11.9 Exporting UMTS VIP Analysis Reports

This section describes how to export UMTS VIP analysis reports. You can export the queried
VIP analysis results as .csv, .xls, or .xlsx files. The exported analysis results help you identify
network problems in advance and solve network problems that may cause complaints raised by
VIP subscribers.
Prerequisite
l
UMTS VIP analysis results are queried. For details, see 11.7 Querying UMTS VIP
Analysis Results.
Context
NOTE
To ensure the security of private information for subscribers, asterisks (****) are used to shield the last
four digits of IMSI and MS Number in VIP analysis results. In the exported VIP analysis results, the last
four digits of IMSIs and MSISDNs are also shielded by asterisks (****).
Procedure
Step 1 Click
in the UMTS VIP Analysis Task window. The Save dialog box is displayed.
Step 2 Set the file name and specify the save path and file type. Then, click Save.
l You can click
l You can click
on the
----End
Issue 01 (2011-08-15)

276
Nastar
11.10 Technical Specifications for UMTS VIP Analysis

This section describes the technical specifications for UMTS VIP Analysis.
Item
Number of subscribers supported

l <= 30,000 (for summarization analysis)
<= 5
Number of VIP groups
<= 100
Number of VIP subscribers
<= 30,000
Number of VIP subscribers that

report data sources
<= 2,000
<= 7 days
<= 60 minutes

(all the themes)
<= 200

<= 50
l <= 2,000 (for thoroughly analysis)
11.11 Reference to the UMTS VIP Analysis Interface

This section describes the interface for UMTS VIP analysis and the relevant parameters. Before
performing relevant operations, familiarize yourself with the functions of UMTS VIP analysis.
11.11.1 Interface Description: UMTS VIP Analysis

This section describes the interface for UMTS VIP analysis. Before performing relevant
The VIP analysis results are displayed in charts and tables, as shown in Figure 11-2.
Issue 01 (2011-08-15)

277
Nastar
Figure 11-2 VIP analysis interface
No. Name
Description
(1)
Button area
Provides the function of exporting the

aggregation information about VIP groups.
(2)
VIP group overview table
Displays the aggregation information about

abnormal KPIs of all the VIP subscribers or
VIP groups involved in the task in a table.
(3)
Area for selecting object types
Provides options for displaying the

aggregation information about abnormal
KPIs in Area (2) based on VIP subscribers or
VIP groups.
l Aggregation based on VIP subscribers
When you select this mode, the
KPIs of all the VIP subscribers in a certain
VIP group is displayed in Area (2).
l Aggregation based on VIP groups
When you select this mode, the
KPIs of all the VIP subscribers in all VIP
groups is displayed in Area (2).
Issue 01 (2011-08-15)

278
Nastar
No. Name
Description
(4)
Network-level KPI information table
Displays the network-level KPI values or

aggregation values corresponding to the VIP
subscribers or VIP groups selected in Area
(2).
(5)
KPI change chart
Displays the variation trend of a certain KPI

of a VIP subscriber selected in Area (2) when
you select the aggregation of abnormal KPIs
based on VIP subscribers in Area (3).
(6)
Service KPIs in CS domain/PS domain/

active cell information table
Displays the service KPIs in CS domain, PS

domain, and active cells of the VIP
subscribers or VIP groups selected in Area (2)
on three tab pages respectively.
11.11.2 Interface for UMTS VIP Trend Analysis

This section describes the interface for UMTS VIP trend analysis. Before performing relevant
VIP trend analysis results are displayed in charts and tables, as shown in Figure 11-3.
Figure 11-3 VIP trend analysis interface
Issue 01 (2011-08-15)

279
Nastar
SN
Item
Description
(1)
Button area
Provides three buttons, which are used to query trend analysis

attributes, export raw trend analysis data, and drill down
through trend analysis results, respectively.
(2)
User selection
area
Enables you to select users whose trend analysis results need

to be displayed. The analysis results are displayed in the
following navigation tree mode: All > User Group > User.
l User Group displays the level information about this user
group.
l User displays MSISDNs and IMSIs of users.
(3)
KPI selection
area
Enables you to select KPIs whose trend analysis results need

to be displayed.
(4)
Trend analysis
chart
Displays KPI change trends during each period for the selected
users.
l User and time dimension information is displayed at the top
of the tab page.
l A KPI name is displayed at the top of each chart.
l The x-axis of a chart indicates the task execution period and
displays time information about all periodic tasks.
l The y-axis of a chart indicates the actual KPI value range.
l Legends for KPI types are displayed at the bottom of a chart.
l Detailed time information and value are displayed after you
click a point in a chart.
l You can right-click a chart to zoom in on, zoom out on, or
save as a chart, and drill down through detailed information
by time.
(5)
Trend analysis
table
Displays detailed KPI information during each period for the

selected users by the different tab pages of the KPI type. The
KPI information in this table is displayed synchronously with
the change trend chart.
l User and time dimension information is displayed at the top
of the tab page.
l Parameters in the table are period, KPI 1, KPI 2, ..., and KPI
N.
If the KPI type is CS service, it displays the KPIs of AMR,
VP, and CS Other. If the KPI type is PS service, it displays
the KPIs of PS, HSDPA, HPUPA, and PS Other.
Issue 01 (2011-08-15)

280
Nastar
11.11.3 Parameters for Creating and Modifying UMTS VIP

Subscribers/VIP Groups
This section describes the parameters for creating and modifying UMTS VIP subscribers and
VIP groups. You can refer to the description when creating and modifying a UMTS VIP
subscriber and VIP group.
Description of Parameters Related to VIP Subscribers

Parameter
Description
User Name
Indicates the name of a VIP subscriber.

Value range:
l Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `
l Not null
l Duplicated allowed (a VIP subscriber is allowed to use
multiple SIM card)
l Case sensitive
MS Number
Indicates the number of a UE used by a VIP subscriber.

Value range:
l A combination of 0-digit to 20-digit numerals from 0 to 9
l Duplicated allowed
IMSI
Indicates the International Mobile Subscriber Identity (IMSI) of

a VIP subscriber.
Value range: A combination of 15-digit numerals from 0 to 9
Description
Indicates the description of the VIP subscriber.

Value range:
Description of Parameters Related to VIP Groups

Parameter
Description
Group Name

Value range:
l Case sensitive
Issue 01 (2011-08-15)

281
Nastar
Parameter
Description
Class
Indicates the level of a VIP group, such as Very Important,

Important, Medium, Low, and Very Low.
Value range: You can select a value from the drop-down list box.
Description

Value range:
Members
Indicates the information about members in the VIP group.

Common Information
Parameter
Description
Task Name
OSS Name

E2E Task List
Begin Time

End Time
NE List
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Issue 01 (2011-08-15)
Description
Service Type

Exception Type

failure.

282
Nastar
Parameter
Description
KPI

determination.
Determination
rule

as >=.
Exception Value

UMTS VIP
Analysis Data
Task
Selected

selected.
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Group Name
Number of
Members
Report Raw Data

Description
Start NCC
End NCC
Start BCC
End BCC
ARFCN
Indication
Start ARFCN

End ARFCN
UMTS Service
Geographic
Analysis Data
Task
Downlink Ec/No
(dB)<=X

bad RxQual area.
value is -15.
UMTS
Terminal
Analysis Data
Task
Issue 01 (2011-08-15)
Type
KPI name
Criterion

283
Nastar
Parameter
Description
threshold

provided.
11.11.5 Parameters for Creating and Modifying UMTS VIP Analysis

Tasks
This section describes the parameters for creating and modifying UMTS VIP analysis tasks. You
can refer to the description when creating and modifying a UMTS VIP analysis task.

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:

Parameter
Description
Task Type
l One-time: The system executes the created tasks only once at

the specified time.
l Period: The system executes the created tasks periodically at
the preset time.
Issue 01 (2011-08-15)

284
Nastar
Parameter
One-time
task
Description
Time
Range
Only the data generated between the start time and the end time
will be analyzed.
The start time should precede the end time, and the end time
should precede the locale system time.
Delayed
If you do not select it, the system will execute the task
immediately.
If you select it, the system will execute the task at the time of the
Execution Delay.
Periodic
task
Executio
n Delay
Start
Time
Indicates date for starting a task. The start time should be later
than the current server time.
The parameter should not precede the end time of the Time
Range.
After the date is set, the Nastar will execute the task at 00:00 of
the next day by default. This parameter is valid for only periodic
tasks.
Executio
n Delay
Indicates the time delayed for running a task.

Value range: 0 to 24. Unit: hour.
The parameter must be used with Start Time. After this parameter
is set, the Nastar will execute the task certain hours later than
00:00 of the specified day in Start Time. If Start Time is set to
12/16/2009 and Execution Delay is set to 3 hours, the Nastar will
execute the task at 03:00 on December 17, 2009.
Period
Indicates the interval between periodic tasks.
Number
of
executio
n times
Indicates the times that a periodic task is executed. If this

parameter is set to 0, you can infer that the task is executed all the
time.
Value range: 0 to 9999. This parameter is valid for only periodic
tasks.
VIP Information
Issue 01 (2011-08-15)
Parameter
Description
Group Name
Number of
Members
Report Raw
Data
Indicates that the raw call data is also collected during the collection of the
KPI aggregation information of all VIP objects of the selected VIP groups,
thus helping to analyze problems thoroughly.

285
Nastar
Parameter
Description
Last update
time
l When the IMSI information of the VIP E2E tasks in the running state is
changed, it displayed the time when the IMSI information is changed.
l When the VIP E2E task is new, it displayed NA.
Description
Type
The VIP analysis tasks involve the service type.

This field is read-only.
KPI name
Indicates the name of a KPI.

Criterion
Indicates the relation of the KPI and the threshold.
Threshold

In the analysis report of the corresponding task, if the KPI value of a
corresponding user does not reach the threshold, it is considered that this is
a problem KPI or deteriorated KPI.
This parameter can be null. That is, no threshold is provided.
Email Sending Information

Parameter
Description
Type
The VIP analysis tasks involve the service type such as

CS service KPIs.
KPI Name
Indicates the name of a KPI.

Threshold

threshold, it is considered that this is a problem KPI or
deteriorated KPI.
provided.
Issue 01 (2011-08-15)

286
Nastar
Parameter
Description
Report Name
Indicates the name of the exported VIP analysis result

file. The default name is as follows:
l For a one-time task, the file name is Name of the
VIP analysis task_Once_Result No._Start
time_End time.xls.
l For a periodic task, the file name is Name of the VIP
analysis task_Cycle_Result No._Start time_End
time.xls.
The value of this parameter cannot be changed.
Indicates the directory for saving the exported VIP
analysis result file on the Nastar server. The default
directory is /export/home/omc/report/LTEVIP.
Saving Path
The value of this parameter cannot be changed.

File Format
Indicates the format of the exported VIP analysis result

file. The file can only be saved in .xls format.
Compress
After you select this option, the exported VIP analysis

result file is saved in .zip format.
Auto-sending of analysis reports

by Email
After you select this option, the system delivers the

exported VIP analysis result file to the mailboxes of the
specified users.
Sending Content
Indicates the report type.

l Statistical Report, only including the VIP analysis
results.
l All Report, including the VIP analysis results and
the VIP further analysis results.
l User's Deep Analysis Report, only including the VIP
further analysis results.
Address
Indicates the mailbox to which the file is to be sent. You

can click Add in the displayed Select Sending Object
to set and manage user mailboxes.
Subject
Indicates the title of an email.

Users are not allowed to change the value of this
parameter.
Content
Indicates the contents of an email.

Users are not allowed to change the value of this
parameter.
11.11.6 Parameters for Querying UMTS VIP Analysis Results

This section describes the parameters for querying UMTS VIP analysis results. You can refer
to the description when querying UMTS VIP analysis results.
Issue 01 (2011-08-15)

287
Nastar
Network KPI
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
Number
of reports
[0,+)
Nu
mb
er
Indicates the total number of MRs involved in the networklevel KPIs.
Service
RRC
setup
success
rate (%)
[0.00,100.
00]
Indicates the success rate from network access to service

RRC setup.
Service
Number
of RRC
setup
failures
[0,+)
Nu
mb
er
Indicates the number of failures from network access to

service RRC setup.
Service
Average
RRC
access
delay (s)
N/A
Sec
ond
Indicates the average delay for service RRC setup during a

successful call initiation.
Nonservice
RRC
setup
success
rate (%)
[0.00,100.
00]
Indicates the success rate from network access to non-service

RRC setup.
Nonservice
Number
of RRC
setup
failures
[0,+)
Nu
mb
er
Indicates the number of failures from network access to nonservice RRC setup.
Nonservice
Average
RRC
access
delay (s)
N/A
Sec
ond
Indicates the average delay for non-service RRC setup during

a successful call initiation.
RRC
Setup
Success
Rate in
CS
Domain
[0.00,100.
00]
RRC is an abbreviation for Radio Resource Control.

Statistical point: The service RRC setup is requested and the
RRC setup is successful.
Statistical point: duration from the time receiving RRC

CONN REQ and the time receiving RRC CONN SETUP
CMP.
Statistical point: duration from the time receiving RRC

CONN REQ and the time receiving RRC CONN SETUP
CMP.
%
Indicates the success rate from network access to CS service

RRC setup.

288
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
Number
of RRC
Setup
Failures
in CS
Domain
[0,+)
Nu
mb
er
Indicates the number of failures from network access to CS

service RRC setup.
RRC
Setup
Success
Rate in
PS
Domain
[0.00,100.
00]
Indicates the success rate from network access to PS service

RRC setup.
Number
of RRC
Setup
Failures
in PS
Domain
[0,+)
Nu
mb
er
Indicates the number of failures from network access to PS

service RRC setup.
Average
Originate
d-Call
RRC
Setup
Delay
N/A
Sec
ond
Indicates the average delay for originated-call RRC setup

during a successful call initiation.
Number
of
Originate
d-Call
RRC
Setup
Delay
[0,+)
Nu
mb
er
Indicates the number from network access to PS service RRC

setup.
SHO
success
rate (%)
[0.00,100.
00]
Indicates the success rate of soft handovers (including softer

handovers) during the successful service process.
Number
of SHO
failures
[0,+)
Nu
mb
er
Indicates the number of soft handover failures during the

successful service process.
HHO
success
rate (%)
[0.00,100.
00]
Indicates the success rate of hard handovers during the

Number
of HHO
failures
[0,+)
Nu
mb
er
Indicates the number of failed hard handovers during the


289
Nastar
Paramet
er
Range
Un
it
Description
Number
of InterRAT
Outgoing
HO
Requests
[0,+)
Nu
mb
er
Indicates the number of outgoing handover requests (from

UMTS network to another network system) initiated by UEs.
Number
of
Successf
ul InterRAT
Outgoing
HOs
[0,+)
Nu
mb
er
Indicates the number of successful outgoing handovers (from

UMTS network to another network system) initiated by UEs.
Number
of InterRAT
Incoming
HO
Requests
[0,+)
Nu
mb
er
Indicates the number of inter-RAT handover requests (from

another network system to UMTS network) initiated by UEs.
Number
of
Successf
ul InterRAT
Incoming
HOs
[0,+)
Nu
mb
er
Indicates the number of successful inter-RAT handovers

(from another network system to UMTS network) initiated
by UEs.
Paramet
er
Range
Un
it
Description
Number
of reports
[0,+)
Nu
mb
er
Indicates the total number of MRs involved in the KPIs in CS

domain.
Call drop
rate (%)
[0.00,10
0.00]
Indicates the call drop rate from the network access to the call
initiation.
CS Service KPI
Call drop rate (%) = Number of call drops/Number of

successful call accesses x 100%
Number
of call
drops
Issue 01 (2011-08-15)
[0,+)
Nu
mb
er
Indicates the number of abnormal dropped calls from the

network access to the call initiation.

290
Nastar
Paramet
er
Range
Un
it
Description
Call
setup
success
rate (%)
[0.00,10
0.00]
Indicates the success rate from the initiation of RAB request

to the call setup.
Call
completi
on
success
rate (%)
[0.00,10
0.00]
RAB
setup
success
rate (%)
[0.00,10
0.00]
Call setup success rate (%) = RRC setup success rate x RAB
setup success rate
%
Indicates the success rate from the initiation of RAB request

to the call completion.
Call completion success rate (%) = RRC setup success rate x
RAB setup success rate x (1 - Service call drop rate)
Indicates the success rate of RAB setups after the network

access.
RAB is an abbreviation for Radio Access Bearer.
RAB setup success rate (%) = Number of successful RAB
setups/Number of RAB setups x 100%
The successful RAB setup is measured when an RAB
assignment response message is sent to the CN after the RAB
is set up successfully.
Number
of RAB
setup
failures
[0,+)
Nu
mb
er
Indicates the number of RAB setup failures after the network

access.
Average
RAB
access
delay (s)
N/A
Sec
ond
Indicates the average delay for RAB setup during a successful

call initiation.
Average RAB setup delay (s) = Service RAB setup delay/
Number of service RAB setup delays
Service RAB setup delay = RAB request completion time RAB request time
The RAB request completion time is measured when the RAB
assignment procedure is successful. That is, after receiving an
RAB setup completion message, the SRNC sends a Radio
Access Bearer Assignment Response message to the CN.
The RAB request time is measured when the UTRAN receives
a Radio Access Bearer Assignment Request message from the
CN.
Issue 01 (2011-08-15)

291
Nastar
Paramet
er
Range
Un
it
Description
Average
call
connecti
on delay
(s)
N/A
Sec
ond
Indicates the average delay for call connection during a

Average call connection delay (s) = Service call connection
delay/Number of service call connection delays
Service call connection delay = RAB request completion time
- Signaling access time
The signaling access time is measured when a RRC SETUP
REQ or RELOC REQ message is received or equals to the
incoming inter-RAT handover request time.
Average
duration
(s)
N/A
Sec
ond
Indicates the average duration of a successful call initiation.

Average duration (s) = Service duration/Number of service
durations
Service duration = RAB release time - RAB request
completion time
The RAB release time is measured when a UE receives an IU
REL CMD message (normal release) or an RB REL SUCC
message during RAB release.
Issue 01 (2011-08-15)
Average
Originate
d-Call
RAB
Setup
Delay
N/A
Sec
ond
Indicates the average delay for originated-call RAB setup

Total
Number
of
Originate
d-Call
RAB
Setup
Delays
[0,+)
Nu
mb
er
Indicates the number from network access to originated-call

RAB setup.
Average
Originate
d-Call
Connecti
on Delay
N/A
Sec
ond
Indicates the average delay for originated-call connection


292
Nastar
Paramet
er
Range
Un
it
Description
Total
Number
of
Originate
d-Call
Connecti
on
Delays
[0,+)
Nu
mb
er
Indicates the number from network access to originated-call

connection.
Average
ratio of
Good
SQI (%)
[0.00,10
0.00]
Indicates the ratio of Good SQI of signal quality during a voice

call.
Average
ratio of
Accept
SQI (%)
[0.00,10
0.00]
Average
ratio of
Bad SQI
(%)
[0.00,10
0.00]
Ratio of
level 1
UL
BLER
(%)
[0.00,10
0.00]
This KPI is valid for only the AMR service.

SQI indicates a level of a voice service, which can be Good,
Accept, Bad. The threshold for each level is determined by the
RNC configuration. Default configuration: Bad for a voice
service with a score lower than 200, Good for a voice service
with a score higher than 313.
%
Indicates the ratio of Accept SQI of signal quality during a

voice call.
Indicates the ratio of Bad SQI of signal quality during a voice

call.
Indicates the proportion of the uplink BLER with level 1

during the successful call initiation.
BLER is an abbreviation for Block Error Rate.
Standard for level 1: 0-0.78%
Ratio of
level 2
UL
BLER
(%)
Issue 01 (2011-08-15)
[0.00,10
0.00]

Standard for level 2: 0.78%-1.56%

293
Nastar
Paramet
er
Range
Un
it
Description
Ratio of
level 3
UL
BLER
(%)
[0.00,10
0.00]

Ratio of
level 4
UL
BLER
(%)
[0.00,10
0.00]
Ratio of
level 5
UL
BLER
(%)
[0.00,10
0.00]
Ratio of
level 6
UL
BLER
(%)
[0.00,10
0.00]
Paramet
er
Range
Un
it
Description
Number
of reports
[0,+)
Nu
mb
er
Indicates the total number of MRs involved in the KPIs in

PS domain.
Call drop
rate (%)
[0.00,100.00
]
Indicates the call drop rate from the network access to the
call initiation.

%



Standard for level 6: >12.48%
PS Service KPI
Call drop rate (%) = Number of call drops/Number of

successful call accesses x 100%
Issue 01 (2011-08-15)
Number
of call
drops
[0,+)
Nu
mb
er
Indicates the number of abnormal dropped calls from the

network access to the call initiation.
Call
setup
success
rate (%)
[0.00,100.00
]
Indicates the success rate from the initiation of RAB

request to the call setup.
Call setup success rate (%) = RRC setup success rate x
RAB setup success rate

294
Nastar
Paramet
er
Range
Un
it
Description
Call
completi
on
success
rate (%)
[0.00,100.00
]
Indicates the success rate from the initiation of RAB

request to the call completion.
RAB
setup
success
rate (%)
[0.00,100.00
]
Call completion success rate (%) = RRC setup success rate

x RAB setup success rate x (1 - Service call drop rate)
%
Indicates the success rate of RAB setups after the network

access.
RAB setup success rate (%) = Number of successful RAB
setups/Number of RAB setups x 100%
The successful RAB setup is measured when an RAB
assignment response message is sent to the CN after the
RAB is set up successfully.
Issue 01 (2011-08-15)
Number
of RAB
setup
failures
[0,+)
Nu
mb
er
Indicates the number of RAB setup failures after the

network access.
DCCC
rate
increase
success
rate (%)
[0.00,100.00
]
Indicates the Dynamic Channel Configuration Control

(DCCC) rate increase success rate during the successful
call process.
Number
of DCCC
rate
increase
failures
[0,+)
Nu
mb
er
Indicates the number of DCCC rate increase failures during

the successful call process.
DCCC
rate
decrease
success
rate (%)
[0.00,100.00
]
Indicates the DCCC rate decrease success rate during the

successful call process.
Number
of DCCC
rate
decrease
failures
[0,+)
Nu
mb
er
Indicates the number of DCCC rate decrease failures

during the successful call process.
DCCC rate increase success rate (%) = Number of

successful DCCC rate increases/Number of DCCC rate
increase initiations x 100%

295
Nastar
Paramet
er
Range
Un
it
Description
Average
RAB
access
delay (s)
N/A
Sec
ond
Indicates the average delay for RAB setup during a

Average RAB setup delay (s) = Service RAB setup delay/
Number of service RAB setup delays
Service RAB setup delay = RAB request completion time
- RAB request time
The RAB request completion time is measured when the
RAB assignment procedure is successful. That is, after
receiving an RAB setup completion message, the SRNC
sends a Radio Access Bearer Assignment Response
message to the CN.
The RAB request time is measured when the UTRAN
receives a Radio Access Bearer Assignment Request
message from the CN.
Average
call
connecti
on delay
(s)
N/A
Sec
ond
Indicates the average delay from an RAB request to the

signaling access during a successful call initiation.
Service call connection delay = RAB request completion
time - Signaling access time
message to the CN.
The signaling access time is measured when a RRC SETUP
REQ or RELOC REQ message is received or equals to the
incoming inter-RAT handover request time.
Average
duration
(s)
N/A
Sec
ond
Indicates the average duration of a successful call

initiation.
Average duration (s) = Service duration/Number of service
durations
Service duration = RAB release time - RAB request
completion time
The RAB release time is measured when a UE receives an
IU REL CMD message (normal release) or an RB REL
SUCC message during RAB release.
message to the CN.
Issue 01 (2011-08-15)

296
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
Average
Originate
d-Call
RAB
Setup
Delay
N/A
Sec
ond
Indicates the average delay for originated-call RAB setup

Total
Number
of
Originate
d-Call
RAB
Setup
Delays
[0,+)
Nu
mb
er
Indicates the number from network access to originatedcall RAB setup.
Average
Originate
d-Call
Connecti
on Delay
N/A
Sec
ond
Indicates the average delay for originated-call connection

Total
Number
of
Originate
d-Call
Connecti
on
Delays
[0,+)
Nu
mb
er
Indicates the number from network access to originatedcall connection.
Ratio of
level 1
UL
BLER
(%)
[0.00,100.00
]

Ratio of
level 2
UL
BLER
(%)
[0.00,100.00
]
Ratio of
level 3
UL
BLER
(%)
[0.00,100.00
]
This KPI is valid for only PS services.

Standard for level 1: 0=< X =<0.39%
%

Standard for level 2: 0.39%< X =<0.78%


297
Nastar
Paramet
er
Range
Un
it
Description
Ratio of
level 4
UL
BLER
(%)
[0.00,100.00
]

Ratio of
level 5
UL
BLER
(%)
[0.00,100.00
]
Ratio of
level 6
UL
BLER
(%)
[0.00,100.00
]
UL RAB
average
negotiate
d final
rate
(kbps)
[0.00,+)
DL RAB
average
negotiate
d final
rate
(kbps)
[0.00,+)
HSDPA
Average
rate
(kbps)
[0.00,+)

%


Standard for level 6: 12.48%< X
kbi
t/s
Indicates the final negotiated rate of uplink RAB when a

common PS service is initiated.
Average final negotiated rate of uplink RAB (kbit/s) =
Final negotiated rate of service uplink RAB/Number of
times for collecting the final negotiated rate of service
uplink RAB
kbi
t/s
Indicates the final negotiated rate of downlink RAB when

a common PS service is initiated.
Average final negotiated rate of downlink RAB (kbit/s) =
Final negotiated rate of service downlink RAB/Number of
times for collecting the final negotiated rate of service
downlink RAB
kbi
t/s
Indicates the average HSDPA rate during the successful

call process.
For versions earlier than RAN13.0:
Average HSDPA rate = Total HSDPA data amount
transmitted on the downlink/[HSDPA service duration x (1
- Percentage of BO 0)]
Average HSDPA rate (kbit/s) = Sum of all calculated
average HSDPA rates/Number of the collected average
HSDPA rated
For RAN13.0:
Average HSDPA rate = Bytes of HSDPA MAC-d flow/
Duration for sending HSDPA MAC-d flow
Average HSDPA rate (kbit/s) = Sum of all calculated
average HSDPA rates/Number of the collected average
HSDPA rates
Issue 01 (2011-08-15)

298
Nastar
Active Cell
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
RNC ID
[0,4
095]
N/A
Indicates the ID of the RNC that an active cell belongs to.
Cell ID
[0,6
553
5]
N/A
Indicates the ID of an active cell.
Cell
Name
N/A
N/A
Indicates the name of an active cell.
Number
of RRC
accesses
[0,
+)
Nu
mbe
r
Indicates the number of signaling accesses for a VIP group or VIP

subscriber in an active cell.
Number
of
abnormal
RRC
accesses
[0,
+)
Nu
mbe
r
Indicates the number of abnormal signaling accesses for a VIP

group or VIP subscriber in an active cell.
Number
of RRC
releases
[0,
+)
Nu
mbe
r
Indicates the number of signaling releases for a VIP group or VIP

subscriber in an active cell.
Number
of
abnormal
RRC
releases
[0,
+)
Nu
mbe
r
Indicates the number of abnormal signaling releases for a VIP

Number
of CS
RAB
accesses
[0,
+)
Nu
mbe
r
Indicates the number of CS service accesses for a VIP group or

VIP subscriber in an active cell.
Number
of CS
RAB
abnormal
accesses
[0,
+)
Nu
mbe
r
Indicates the number of abnormal CS service accesses for a VIP

Number
of CS
RAB best
cell
releases
[0,
+)
Nu
mbe
r
Indicates the number of times that an active cell serves as the best
cell before the CS service performed by a VIP group or VIP
subscriber is released.

299
Nastar
Paramet
er
Ran
ge
Uni
t
Description
Number
of CS
RAB
abnormal
best cell
releases
[0,
+)
Nu
mbe
r
cell before the CS service performed by a VIP group or VIP
subscriber is abnormally released.
Number
of PS
RAB
accesses
[0,
+)
Nu
mbe
r
Indicates the number of PS service accesses for a VIP group or

VIP subscriber in an active cell.
Number
of PS
RAB
abnormal
accesses
[0,
+)
Nu
mbe
r
Indicates the number of abnormal PS service accesses for a VIP

Number
of PS
RAB best
cell
releases
[0,
+)
Nu
mbe
r
cell before the PS service performed by a VIP group or VIP
subscriber is released.
Number
of PS
RAB
abnormal
best cell
releases
[0,
+)
Nu
mbe
r
cell before the PS service performed by a VIP group or VIP
subscriber is abnormally released.
11.11.7 Parameters for Setting the Mailbox of Analysis Results

This section describes the parameters for setting the mailbox of analysis results. You can refer
to this part when you set mailboxes.
Issue 01 (2011-08-15)
Parameter
Description
SMTP Host Name or

Address
Refers to the address of the sending email server.
Send Email Address
Refers to the email of the sender.
The address can be either an IP address or a domain name. For

example, 10.0.0.1 or mail.yourdomain.com.

300
Nastar
Parameter
Description
Is it required to authenticate
Indicates that the authentication is required when you log in to

the email server.
If you select this option, you need to set User Name and
Password. If you do not select this option, the User Name and
Password are unavailable.
Issue 01 (2011-08-15)
User Name
Refers to the user name used to log in to the email sending

server.
Password
Refers to the password used to log in to the email sending

server.

301
Nastar
12
UMTS Complaint Analysis Support
About This Chapter

The UMTS complaint analysis support function enables you to create UMTS complaint analysis
support tasks, query UMTS complaint analysis support results, and export UMTS complaint
analysis support reports from the Nastar. After receiving a complaint, the Nastar can quickly
locate call history records (CHRs) that are related to a problem cell involved in the complaint
based on the known problem cell and International Mobile Subscriber Identity (IMSI) of the
complaint subscriber. By analyzing causes of access failure, handover failure, and abnormal call
drop, the Nastar helps you locate and solve problems. This function improves the efficiency of
complaint handling and increases the subscriber satisfaction.
12.1 Basic Knowledge of UMTS Complaint Analysis Support
This section describes the basic knowledge of UMTS complaint analysis support, including
UMTS complaint analysis support function and authority policies for UMTS complaint analysis
support.
12.2 UMTS Complaint Analysis Support Process
This section describes the UMTS complaint analysis support process.
12.3 Creating UMTS Complaint Analysis Support Tasks
This section describes how to create UMTS complaint analysis support tasks. After receiving a
UMTS subscriber complaint, you can create a UMTS complaint analysis support task on the
Nastar to search for the subscriber call records related to the complaints based on the problem
cell and international mobile subscriber identity (IMSI) of the complaint subscriber. This
function helps you analyze and locate problems.
12.4 Querying UMTS Complaint Analysis Support Results
This section describes how to query UMTS complaint analysis support results. You can view
subscriber call records and detailed information about each record by using this function. The
Nastar provides UE capability, access and release information, and service quality in each call
record to help you determine the network location where problems occur and possible causes.
12.5 Exporting UMTS Complaint Analysis Support Reports
This section describes how to export UMTS complaint analysis support reports. You can export
the queried complaint analysis support results as .xls, or .xlsx files as required. The exported
analysis results help you determine the network location where the problem occurs and the
possible causes.
Issue 01 (2011-08-15)

302
Nastar
12.6 Technical Specifications for UMTS Complaint Analysis Support

This section describes the technical specifications for UMTS complaint analysis support.
12.7 Reference to the UMTS Complaint Analysis Support Interface
This section describes the interface for UMTS complaint analysis support and the relevant
UMTS complaint analysis support.
Issue 01 (2011-08-15)

303
Nastar
12.1 Basic Knowledge of UMTS Complaint Analysis

Support
This section describes the basic knowledge of UMTS complaint analysis support, including
UMTS complaint analysis support function and authority policies for UMTS complaint analysis
support.
12.1.1 UMTS Complaint Analysis Support Function

This section describes the basic knowledge of UMTS complaint analysis support. The Nastar
can perform UMTS complaint analysis support based on the call records before and after some
complaints in the UMTS network. This function helps you locate and solve complaint problems,
improves the efficiency of solving problems, and improves subscriber satisfaction.
Complaint Analysis Support

The Nastar obtains the call event records of complaint subscribers, and then filters, aggregates,
and analyzes data based on a specified history period and detailed call records of subscribers in
a specified area, assisting in locating and solving problems. The complaint analysis support
consists of the aggregation and analysis of cause types in call reports of complaint subscribers,
aggregation and analysis of information about call reports of complaint subscribers, analysis of
detailed information about call reports of complaint subscribers, analysis of procedure before
signaling release in call reports of complaint subscribers, and analysis of active cells in call
reports of complaint subscribers.
l
The aggregation and analysis of cause types in call reports of complaint subscribers help
network engineers filter and aggregate call reports based on exception causes.
Causes are classified into three types: non-exception, setup failure, and abnormal call
release. For details about cause types, see Table 12-1.
Table 12-1 Cause type and related description
Issue 01 (2011-08-15)
Cause Type
Description
Non-exception
Indicates that the call is normally released.
Setup failure
Indicates the call reports in which the RRC

access, CS service access, or PS service access
fails.
Abnormal release
Indicates the call reports in which the CS call

drops, PS call drops, or abnormal RRC release
are recorded.
The aggregation and analysis of call information of complaint subscribers provide the
overview of information about all the filtered call reports. The information includes the
access time, access cell, release time, release cell, IMSI, IMEI, service duration, link setup
type, and call status. This function helps network engineers quickly identify abnormal call
reports (for example, too-short-time call reports) and preliminarily learn about the situation
of complaint subscribers.
304
Nastar
The analysis of detailed call reports of complaint subscribers provides the detailed
information about all the filtered call reports. The information includes the subscriber
information, access/release information, CS service information, PS service information,
handover information and statistical information. This function helps network engineers
learn the key events that occur during calls, service usage, and MRs before the signaling
release, accurately and quickly assisting in problem location.
The analysis of procedure before signaling release in call reports of complaint subscribers
provides the detailed procedure before signaling release of all the filtered subscribers. This
function helps network engineers locate problems based on the information before signaling
release.
The UMTS complaint analysis support function requires raw call data from complaint
subscribers. The amount of raw data is huge. Therefore, a limitation must be imposed to
prevent system overload in the case of concurrent operations by a large number of users.
If IMSI is used to identify complaint subscribers, the maximum number of concurrent
complaint subscribers allowed by the Nastar cannot exceed 2,000, and the selected
complaint subscribers can be under different OSSs.
Some subscribers' call records are missing during complaint analysis. The possible cause
is that the number of call records under an RNC has exceeded 100,000. To ensure data
processing performance, the Nastar is designed to process 100,000 call records at most.
Therefore, it is recommended that a complaint analysis task should contain less than 100
subscribers' call records within three days.
The Nastar can combine the call records upon inter-RNC handovers. That is, if inter-RNC
handovers occur during a call, the Nastar combines the call records for the same call.
However, if two inter-RNC handovers occur within 30s and the Nastar fails to obtain the
data of one RNC, the Nastar will combine the CHR records of the two calls into one.
Limitations
12.1.2 Authority Policies for UMTS Complaint Analysis Support

The Nastar provides secure authority management policies to ensure the security of private
information for subscribers. The authority management policies enable different types of users
to have different operation rights for the security of their private information.
Introduction to Authority Types

l
View rights allow users to view a security object on the Nastar client. If a user can view a
security object on the Nastar client, the user has the view rights to this security object.
View rights are associated with the management domain. If a security object is added to
the management domain of a user or a user group, the user or users in the group have the
view rights to this security object.
For details about how to enable view rights for users, see the description in "Management
domain of user" in Creating an Nastar User Account.
Operation rights allow users to perform an operation. If a user has operation rights, the user
can perform a specific operation. Here, operation rights include query rights to complaint
analysis support tasks and operation rights to complaint analysis support tasks.
Operation rights are associated with the management domain. A user can perform the
operation corresponding to the operation rights for only the objects in the management
domain of the user.
Issue 01 (2011-08-15)

305
Nastar
Query rights to complaint analysis support tasks: If a Nastar user has the rights, the user
can query the authorized complaint analysis support tasks.
Operation rights to complaint analysis support tasks: If a Nastar user has the rights, the
user can create, query, or delete the authorized complaint analysis support tasks.
For details about how to enable operation rights for users, see the description in "Operation
rights of user" in Creating an Nastar User Account.
Introduction to Authority Policies

The authority policies for managing complaint analysis support tasks are as follows:
l
Users in the administrator group: This type of user has view rights and operation rights to
all complaint analysis support tasks initially. That is, the user is authorized to create
complaint analysis support tasks, and query or delete complaint analysis support tasks
created by any user.

To create complaint analysis support tasks, the user in the administrator group or
security administrator group must have operation rights to complaint analysis support
tasks.
To query or delete information about complaint analysis support tasks created by the
user in the administrator group or security administrator group, the user does not need
other rights.
To delete complaint analysis support tasks created by others, the user in the
administrator group or security administrator group must have operation rights to
complaint analysis support tasks.
To query information about complaint analysis support tasks created by the user in the
administrator group or security administrator group, the user must have query rights to
complaint analysis support tasks.
NOTE
After a user is assigned permission to query complaint analysis support tasks, the user can query
all complaint analysis support tasks created by any user.
Example of Authority Policies

Authority policies vary according to the specific scenario. Table 12-2 describes the authority
policies in different scenarios.
NOTE
"User" in Table 12-2 refers to a user in the administrator group or security administrator group.
Issue 01 (2011-08-15)

306
Nastar
Table 12-2 Example of authority policies

Scenario
Operation Procedure
Scenario 1

User A needs to create a complaint analysis

support task named X.
2. Assign user A operation rights to complaint

analysis support tasks.
add Operation > Nastar PA > UMTS
Complaint Assistant Analysis to Selected
Rights, and click OK. For details, see
4. Create a complaint analysis support task
named X.
For details about how to create complaint
analysis support tasks, see 12.3 Creating
Tasks.
Log in to the client as user A.
Scenario 2
User A needs to query or delete analysis
task X created by user A.
Scenario 3
User B needs to delete analysis task X
created by user A.

2. Assign user B operation rights to complaint
Complaint Assistant Analysis to Selected
Rights, and click OK. For details, see
4. Delete analysis task X.
For details about how to delete complaint
analysis support tasks, see Follow-up
Procedure in 12.3 Creating UMTS
Complaint Analysis Support Tasks.
Issue 01 (2011-08-15)

307
Nastar
Scenario
Operation Procedure
Scenario 4

User B needs to query analysis task X

created by user A.
2. Assign user B query rights to complaint

Complaint Analysis Support Task View to
Selected Rights, and click OK. For details,
see Creating an Nastar User Account.
4. Query analysis results of complaint analysis
support task X.
For details about how to query complaint
analysis support results, see 12.4 Querying
Results.
12.2 UMTS Complaint Analysis Support Process

This section describes the UMTS complaint analysis support process.
Figure 12-1 shows the process of UMTS complaint analysis support.
NOTE
Required rights must be assigned to users to properly perform complaint analysis support tasks. For details
about authority policies, see 12.1.2 Authority Policies for UMTS Complaint Analysis Support.
Figure 12-1 Process of UMTS complaint analysis support
Issue 01 (2011-08-15)

308
Nastar

Table 12-3 Description of UMTS complaint analysis support process
No.
Procedure
Description
Create a UMTS
complaint
analysis
support task

you can create a UMTS complaint analysis support task. After
the task is created, the Nastar retrieves analysis data related to
the complaint analysis support from the database, analyzes the
Query UMTS
complaint
analysis
support results
You can view the analysis results of the complaint analysis

support tasks that are executed successfully and also perform
Export UMTS
complaint
analysis
support reports
You can enable the Nastar client to export UMTS complaint

analysis support results as files.
12.3 Creating UMTS Complaint Analysis Support Tasks

This section describes how to create UMTS complaint analysis support tasks. After receiving a
UMTS subscriber complaint, you can create a UMTS complaint analysis support task on the
Nastar to search for the subscriber call records related to the complaints based on the problem
cell and international mobile subscriber identity (IMSI) of the complaint subscriber. This
function helps you analyze and locate problems.
Prerequisite
l
The information about the complaint subscriber is collected.
The configuration data must be imported before creating the task. If not, the NE selection
tree is none.
A maximum of 200 tasks of this type can be created, and a maximum of data of history
seven days can be involved in an analysis task.
The IMSI file of the complaint subscriber to be imported contains only the IMSI column,
as shown in Table 12-4.
Context
Table 12-4 Example of a GSM complaint subscriber IMSI file

IMSI
460079053010239
Issue 01 (2011-08-15)

309
Nastar
IMSI
460005396052916
460022068262211
Procedure
Step 1 Click
TIP
Step 3 Click Next.
Step 4 In the Filter NEs area, perform the following operations:
1.
Click Select to choose one or multi objects in Select NE Object.
2.
Click OK.
3.
The chosen cells are shown in table.
4.
Optional: Click Delete to delete the cells you have chosen.
Step 5 In the Filter Users area, perform the following operations:

l Adding a subscriber
1.
Click Add. In the displayed Add User dialog box, enter the IMSI of the subscriber.
2.
Click OK.
NOTE
l A maximum of 2000 IMSI numbers can be entered.

l You can only enter the 15-digit numerals.
l Importing subscriber information
Issue 01 (2011-08-15)
1.
2.
Select the edited IMSI file of a complaint subscriber, and then click Open.
3.
Perform the operations as prompted.

If...
Then...
The imported information is correct

and no identical records exist
In the displayed dialog box, click OK.

and identical records exist
In the displayed OK dialog box, click Yes to

import the new records that will overwrite
identical records.

310
Nastar
If...
Then...
Abnormal records exist in the

imported information
Current files cannot be imported and the

Nastar displays a message, indicating the
number of abnormal records.
l Click Export Check Result to export
check results from the Nastar so that you
can make modifications based on the
error information to complete the current
import task.
l Click Cancel to terminate the import task.
Step 6 Click Next.

Step 7 Set the Task Type to One-time, set the time range.
----End
Follow-up Procedure
TIP
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Save as the tasks
Refresh
Issue 01 (2011-08-15)

Suspended.
Resume.
, or right-click
, or right-click

Click

311
Nastar
12.4 Querying UMTS Complaint Analysis Support Results

This section describes how to query UMTS complaint analysis support results. You can view
subscriber call records and detailed information about each record by using this function. The
Nastar provides UE capability, access and release information, and service quality in each call
record to help you determine the network location where problems occur and possible causes.
Prerequisite
l
The progress bar of the UMTS complaint analysis support task reaches 100%.
Procedure
Step 1 Choose UMTS Complaint Analysis Support Task from the navigation tree in the Analysis
tasks.
Result from the shortcut menu. The UMTS Complaint Analysis Support Task window is
displayed.
NOTE
Step 5 In the navigation tree on the left of the UMTS Complaint Analysis Support Task window,
select a call record to be queried.
The navigation tree can be expanded in two modes: Cause type-IMSI and IMSI-Cause type.
l In Cause type-IMSI mode, all filtered call records are classified by cause type and the call
records of each cause type is classified by IMSI.
l In IMSI-Cause type mode, all filtered call records are classified by IMSI and the call records
of each IMSI is classified by cause type.
You can type an IMSI or a cause type in the Search area above the navigation tree to quickly
search for and locate the required call record.
For detailed description of cause types, see 12.1.1 UMTS Complaint Analysis Support
Function.
Step 6 On the Overview tab page, query the overview information about the filtered call records and
select a call record.
The overview information includes the access time, access cell, release time, release cell, IMSI,
IMEI, and service duration. For details about parameters, see 12.7.4 Parameters for Querying
UMTS Complaint Analysis Support Results.
l
Issue 01 (2011-08-15)
indicates that the call record in this line is abnormal.

312
Nastar
indicates that the CHR in this line is a combined CHR.

The Nastar supports the combination of inter-RNC CHRs. If an inter-RNC handover occurs
during a call, the Nastar combines the records related to one call and displays a combined
CHR in the overview table. You can double-click a combined CHR to open the CHR list tab
page corresponding to the combined CHR and query detailed information. The tab page is
named IMSI***_Serial number, where *** refers to the IMSI number.
You can click any line in the list and press Ctrl+F to search for and locate a call record.
Step 7 In the detailed call report table of a complaint subscriber on the right of the window, query the
details of all the filtered call records. The details include information about the subscriber, call
access or call release, CS service, PS service, statistical and handover.
Step 8 On the Signaling Procedure Before Call Release tab page, query the detailed signaling
procedure before call release for the selected call record.
l Signaling information table: contains all signaling transmitted between NEs during a call.
Information in this table is displayed synchronously with the signaling procedure chart.
l Signaling procedure chart: shows the signaling interaction between NEs during a call. This
chart is displayed synchronously with the information in the signaling information table.
l If you double-click a record in the signaling procedure table or a signaling record in the
signaling procedure chart, the Information dialog box is displayed. Detailed signaling
information is displayed in a navigation tree, which contains the meanings of fields
represented by specific bytes. In addition, the Nastar automatically parses the enumerated
values or variant values represented by fields in a message according to protocols.
For details about the signaling procedure chart, see Description of the Signaling Procedure
Before Call Release Tab Page.
Step 9 On the Measurement Information tab page, query the detailed measurement information
before call release for the selected call record and the change trend chart.
l Detailed measurement information table: contains detailed information about measurement
reports (MRs) before call release.
l KPI change trend chart: shows the change trends of Ec/No, RSCP, and RSSI Power.
For details about parameters and the change trend chart, see Description of the Measurement
Information Tab Page.
Step 10 Optional: Query the complaint analysis support results on the GIS window.
in the upper left of
Click
the Nastar client window to open the Display the Nastar Service based on longitude and
latitude window.
l The node corresponding to the selected theme is added to the navigation tree on the left of
the GIS window. The naming convention of the theme node is Network system_Task
name. The second-level node is the task name, and the three-level node is the KPI name,
such as the access and release cell.
If multiple complaint analysis support result windows related to one network system are
opened at the same time, the GIS window can synchronously display information of one
analysis result window. Only one theme node is displayed in the navigation tree on the
left of the GIS window and corresponds to the complaint analysis support results related
Issue 01 (2011-08-15)

313
Nastar
If a combined complaint analysis support result windows is displayed as one network

system, the GIS window can display information of the combined analysis result window
under the node of the network system.
If the complaint analysis support result window that is synchronously displayed with the
GIS window is closed, the theme node corresponding to the complaint analysis support
task is automatically deleted from the navigation tree on the left of the GIS window, and
the rendering layer corresponding to the complaint analysis support results is also
l When you open the GIS window initially, the access and release cells of all the call records
are displayed under the root node in the complaint analysis support result window by default.
Switch to one node on the left tree of the complaint analysis support result window, the
GIS window can synchronously display the access and release cell information of the
related node.
If cells whose engineering parameters are not imported exist, a message is displayed on
the right of the window.
----End
Follow-up Procedure
Export query results. You can right-click in the result list and then choose Save As from the
shortcut menu to save the current query results as a .xml, .txt, .xls, or .xlsx file.
12.5 Exporting UMTS Complaint Analysis Support Reports

This section describes how to export UMTS complaint analysis support reports. You can export
the queried complaint analysis support results as .xls, or .xlsx files as required. The exported
analysis results help you determine the network location where the problem occurs and the
possible causes.
Prerequisite
l
UMTS complaint analysis support results are queried. For details, see 12.4 Querying
Export a complaint analysis support overview report.
Procedure
Issue 01 (2011-08-15)
1.
in the UMTS Complaint Analysis Support window. The Save dialog box
Click
is displayed.
2.
Set the folder and specify the save path and file type. Then, click Save.
Export a complaint analysis support data report.

. The Save dialog box
1.
In the UMTS Complaint Analysis Support window, click

is displayed.
2.
Set the folder and specify the save path and file type. Then, click Save.

314
Nastar
An exported data report contains overview table information, subscriber information,

call access information, call release information, CS service, PS service, statistical
information and handover information. Measurement information can not be exported.
You can also right-click the complaint analysis support overview table and then choose
Export complaint analysis support data report from the shortcut menu to export a
complaint analysis support data report.
----End
12.6 Technical Specifications for UMTS Complaint

Analysis Support
This section describes the technical specifications for UMTS complaint analysis support.
Item
Number of subscribers supported

<= 2,000
<= 5
<= Past 7 days
<= 15 minutes

(all the themes)
<= 200

<= 200
12.7 Reference to the UMTS Complaint Analysis Support

Interface
This section describes the interface for UMTS complaint analysis support and the relevant
UMTS complaint analysis support.
12.7.1 Interface Description: UMTS Complaint Analysis Support

This section describes the interface for UMTS complaint analysis support. Before performing
The complaint analysis support results are displayed in charts and tables, as shown in Figure
12-2 and Figure 12-3.
Issue 01 (2011-08-15)

315
Nastar
Figure 12-2 Complaint analysis support interface (1)
No. Name
Description
(1)
Button area
Two buttons are provided to export

complaint analysis support overview report
and complaint analysis support data report.
(2)
Search panel
You can precisely locate a call report

through the search condition.
(3)
Navigation tree of the call report cause type The navigation tree of the call report cause
overview of complaint subscribers
type overview of complaint subscribers
provides two display modes, namely, Cause
type-IMSI and IMSI-Cause type.
(4)
Call report overview table
Issue 01 (2011-08-15)
Provides options for displaying the

information of all the filtered call reports in
Area (3). The information includes access
time, access cell, release time, release cell,
IMSI, IMEI, service duration, link
establishment type, and call status.

316
Nastar
No. Name
Description
(5)
Table of the signaling flow before the call

release associated with the complaint
subscriber call report and table of the
measurement information
Displays the detailed information of the

signaling flow and measurement
information before the call release
associated with the complaint subscriber
call report.
(6)
Table related to subscribers, signaling

access/release, CS services, PS services,
Statistical and handover
Provides options for displaying the detailed

information of all the filtered call reports in
Area (3).
Figure 12-3 Complaint analysis support interface (2)
No. Name
Description
(7)
Provides raw reports for combined call records.
Combined call record list
12.7.2 Interface for Signaling Procedure Before Call Release and

Measurement Information in the UMTS Complaint Analysis
Support Window
This section describes the function of each area on the Signaling Procedure Before Call
Release and Measurement Information tab pages in the UMTS complaint analysis support
window.
Issue 01 (2011-08-15)

317
Nastar
Description of the Signaling Procedure Before Call Release Tab Page

The signaling procedure before call release is displayed in charts and tables, as shown in Figure
12-4.
Figure 12-4 Signaling Procedure Before Call Release
SN
Item
Description
(1)
Signaling
information
table
Contains signaling information transmitted between NEs during a

call, including the signaling time, signaling direction, signaling type,
and contents. Information in this table is displayed synchronously
with the signaling procedure chart.
Issue 01 (2011-08-15)

318
Nastar
SN
Item
Description
(2)
Signaling
procedure
chart
Shows the signaling interaction between NEs during a call. This chart
is displayed synchronously with the information in the signaling
information table.
l The signaling time is displayed on the left of the chart. The time
format is HH:MM:SS.Tick, where Tick is the unit of the time. 1
Tick equals to 10 ms.
l NEs are displayed at the top of the chart. Uu interface is a
communication interface between the UE and the NodeB. Iub
interface is a communication interface between the NodeB and
the RNC. Iur interface is a communication interface between the
RNC and the other RNC. Iu interface is a communication
interface between the RNC and the CN.
l Characters on the chart refer to the signaling number and name.
Solid lines refer to the standard signaling, dashed lines refer to
the non-standard signaling, and arrows indicate the signaling
direction.
You can refer to the standard signaling specifications to know the
detailed signaling information.
Description of the Measurement Information Tab Page

This tab page contains a detailed measurement report table and a KPI change trend chart, as
shown in Figure 12-5.
Issue 01 (2011-08-15)

319
Nastar
Figure 12-5 Measurement Information tab page
SN
Item
Description
(1)
Detailed
measurement
report table
Contains detailed information about measurement reports (MRs)

before call release, including the measurement time, measurement
object, measurement object type, BCCH, BSIC, and KPIs.
(2)
KPI change
trend chart
Shows the change trends of Ec/No, RSCP, and RSSI.

Each trend chart consists of the following four parts from left to right:
l Title
l Y-axis, displaying only the maximum value and minimum value
l KPI change trend chart, displaying the change trends of KPIs in
a maximum of 20 MRs
l Legend
Table 12-5 describes the change trend of each KPI.
Issue 01 (2011-08-15)

320
Nastar
Table 12-5 Description of KPI change trend

KPI
Usage
Description
Ec/No
Indicates the change trend of the

signal intensity according to the
received cells of the UE.
Displayed as a broken line chart. The

value ranges from -25 to 0.
RSCP

signal level according to the received
cells of the UE.
Displayed as a broken line chart. The

value ranges from -115 to -25.
RSSI

RSSI according to the received intercells of the UE.
Displayed as a broken line chart.
12.7.3 Parameters for Creating and Modifying UMTS Complaint

Analysis Support Tasks
This section describes the parameters for creating and modifying UMTS complaint analysis
support tasks. You can refer to this description when creating and modifying a UMTS complaint
analysis task.

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:
Issue 01 (2011-08-15)

321
Nastar

Parameter
Description
Task Type
time.
Time Range
analyzed.

Parameter
Description
Filter NEs
Choose the NEs to be analyzed.
Filter User
The filtering condition can be IMSI.
12.7.4 Parameters for Querying UMTS Complaint Analysis Support

Results
This section describes the parameters for querying UMTS complaint analysis support results.
You can refer to the description when querying UMTS complaint analysis support results.
Summary
Paramet
er
Range
Un
it
Description
Serial
Number
(0, 2 to the
power 31 - 1)
N/
A
Indicates the serial number of a CHR in the call report

overview table. Serial number is a keyword of a CHR
and uniquely identifies a CHR. This is an internal Nastar
identification.
Combined CHRs share one serial number. A CHR that
is not combined corresponds to one serial number.
Combine
d
Combined
Empty
N/
A
Indicates whether a CHR is combined.

The Nastar supports the combination of inter-RNC
CHRs.
If a yellow icon is displayed in the column, the CHR is
combined.
Abnorma
l
Issue 01 (2011-08-15)
Abnormal
Indicates whether a CHR is abnormal.
Empty
If a red exclamation mark is displayed in the column,

the CHR is abnormal.

322
Nastar
Paramet
er
Range
Un
it
Description
Abnorma
l Cause
RRC access
failure
N/
A
Indicates the cause of an exception according to the

abnormal release cause and MRs before call release.
Abnormal RRC
release
CS service
access failure
CS service call
drop
PS service
access failure
PS service call
drop
Network
UMTS
N/
A
Indicates the network that a call accesses.
Access
Type
Intra-RAT
static incoming
migration
N/
A
Link setup is classified into the following types:

Intra-RAT static incoming migration, that is, the radio
link to the DRNC is already set up before the migration.
Intra-RAT hard
handover
associated
incoming
migration
Intra-RAT hard handover associated incoming

migration, that is, the first radio link that is triggered by
the migration request on the IU interface is set up.
Intra-RAT
CCH migration
Inter-RAT incoming handover
Intra-RAT
incoming
handover
RRC normal setup (with DRD)
Normal RRC
setup (without
DRD)
Intra-RAT CCH migration

RRC normal setup (without DRD)
The results of the preceding four types are displayed as
Migrated from another RNC, and the results of the later
two types are displayed as Access from home RNC.
Normal RRC
setup (with
DRD)
Issue 01 (2011-08-15)

323
Nastar
Paramet
er
Range
Un
it
Description
Requeste
d Service
Type
CHR_RAB_TR
AF_CS_AMR
N/
A
Indicates the service type of the RAB.
N/
A
Indicates the signaling access time for a call.
CHR_RAB_TR
AF_CS_VP,
CHR_RAB_TR
AF_CS_OTHE
R,
CHR_RAB_TR
AF_BUTT,
CHR_RAB_TR
AF_NULL,
CHR_RAB_TR
AF_PS_GENE
RAL,
CHR_RAB_TR
AF_PS_CMB,
CHR_RAB_TR
AF_PS_HSDP
A,
CHR_RAB_TR
AF_PS_HSUP
A,
CHR_RAB_TR
AF_PS_HSDP
A_HSUPA,
CHR_RAB_TR
AF_BUTT,
CHR_RAB_TR
AF_NULL
Issue 01 (2011-08-15)
Access
Time
N/A
Access
Cell
N/A
N/
A
Indicates the name of the cell where the signaling

accesses.
Release
Time
N/A
N/
A
Indicates the signaling release time for a call.
Release
Cell
N/A
N/
A
Indicates the name of the cell where the signaling is

released.
The signaling access time is measured when an RRC

CONN SETUP REQ or RELOC REQ message is
received or equals to the time of inter-RAT incoming
handover request.
The signaling release time is measured when the RRC

release procedure starts, that is, an RRC
CONNECTION RELEASE message is received.

324
Nastar
Paramet
er
Range
Un
it
Description
IMSI
000000000000
000-999999999
999999
N/
A
Indicates the International Mobile Subscriber Identity

(IMSI) of a subscriber.
IMEI
000000000000
000-999999999
999999
N/
A
Indicates the International Mobile Equipment Identity

(IMEI) of a UE.
Peer
MSISDN
N/A
N/
A
Indicates the peer MSISDN of the peer UE. This

parameter is valid for only voice services.
Duration
N/A
Se
co
nd
Indicates the duration of a call.
Se
co
nd
Indicates the duration of a service call.
Service
Duration
[0,+)
Duration = Release time - Access time
Service call duration = RAB request completion time RAB release time
message to the CN.
The RAB release time is measured when an IU REL
CMD message (normal release) or an RB REL SUCC
message is received during RAB release.
Access
failure
cause
N/A
N/
A
Indicates the cause in the RRC setup request message,

that is, the cause value carried in an RRC
CONNECTION REJECT message transmitted over the
Uu interface.
For details, see the description in 25.331-10.2.36 in
3GPP specifications.
IU
release
cause
N/A
N/
A
Indicates the cause of the signaling release for a call, that

is, the cause value carried in an IU RELEASE
REQUEST message transmitted over the Iu interface.
For details, see the description in 25.413 - 9.1.6 in 3GPP
specifications.
RRC
abnormal
release
caus
N/A
N/
A
Indicates the cause of an abnormal call release, that is,

the cause value carried in an IU RELEASE REQUEST
message transmitted over the Iu interface.
The causes include the general exception cause,
subcause of exceptions, and detailed exception cause.
specifications.
Issue 01 (2011-08-15)

325
Nastar
Paramet
er
Range
Un
it
Description
Cause for
CS RAB
Setup or
Release
Failure
N/A
N/
A
Indicates the cause of a CS RAB setup failure or release

failure, that is, the cause value carried in an RAB
ASSIGNMENT RESPONSE message transmitted over
the Iu interface.
specifications.
Cause for
PS RAB
Setup or
Release
Failure
N/A
N/
A
Indicates the cause of a PS RAB setup failure or release

failure, that is, the cause value carried in an RAB
ASSIGNMENT RESPONSE message transmitted over
the Iu interface.
specifications.
User Information
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
TMSI/
PTMSI
0000000FFFFFFFF
N/
A
Indicates the temporary subscriber identifier allocated by

the network in CS domain or PS domain.
IMSI
00000000000
0000-9999999
99999999
N/
A

IMEI
00000000000
0000-9999999
99999999
N/
A

(IMEI) of a UE.
Peer
MSISDN
N/A
N/
A
Indicates the MSISDN of the peer UE. This parameter is

valid for only voice services.
UE HSDSCH
capabilit
y
[1,64]
N/
A
Indicates the high-speed shared control channel

capability of a UE.
UE
EDCH
capabilit
y
[1,16]
The value ranges from 1 to 64. The value is in direct

proportion to the capability.
N/
A
Indicates the enhanced dedicated channel capability of a

UE.
The value ranges from 1 to 16. The value is in direct
proportion to the capability.

326
Nastar
Access/Release Information
Paramet
er
Range
Un
it
Description
Access
Time
N/A
N/
A
Indicates the time when the signaling accesses during a call.
RL link
setup
time
N/A
N/
A
Indicates the RL setup time during radio link access for a call.
Access
Cell
N/A
N/
A
Indicates the name of the cell where the signaling accesses.
RRC
status
during
access
HR_RRC
_SRB_H
SUPA
Indicates the RRC status during the signaling access.

CHR_RRC_SRB_HSUPA: indicates that the signaling is set
up on the HSUPA on the uplink and on the R99DCH on the
downlink.
CHR_RR
C_SRB_
HSDPA
CHR_RRC_SRB_HSDPA: indicates that the signaling is set

up on the R99DCH on the uplink and on the HSDPA on the
downlink.
CHR_RR
C_SRB_
HSUPA_
HSDPA
CHR_RRC_SRB_HSUPA_HSDPA: indicates that the

signaling is set up on the HSUPA on the uplink and on the
HSDPA on the downlink.
CHR_RR
C_SRB_
EFACH
CHR_RRC_SRB_EFACH: indicates that the signaling is set

up on the RACH on the uplink and on the EFACH on the
downlink.
CHR_RR
C_SRB_
DCH
CHR_RRC_SRB_DCH: indicates that the signaling is set up

on the R99DCH on the uplink and on the R99DCH on the
downlink.
CHR_RR
C_SRB_
FACH
CHR_RRC_SRB_FACH: indicates that the signaling is set

up on the R99 RACH on the uplink and on the R99 FACH on
the downlink.
CHR_RR
C_BUTT
CHR_RRC_BUTT: indicates other combination.
Access
cause
N/A
N/
A
Indicates the cause in the RRC setup request message.
Access
delay
(ms)
N/A
Sec
ond
Indicates the signaling access delay during a call.
Access
TP
[0,3069 ]
Indicates the propagation delay of the signaling access during

a call.
Time Propagation (TP) is used by Huawei.
Target
DRD cell
during
access
Issue 01 (2011-08-15)
N/A
N/
A
Indicates the target cell for a handover.

327
Nastar
Paramet
er
Range
Un
it
Description
Access
failure
cause
N/A
N/
A
Indicates the possible causes of the access failure.
Measure
ment
informati
on during
access
N/A
N/
A
Indicates the information about the network environment

measurement during the signaling access.
Release
Time
N/A
N/
A
Indicates the signaling release time for a call.
Cell for
Release
N/A
N/
A
Indicates the ID of the cell where the signaling is released.
IU
release
cause
N/A
N/
A
Indicates the cause of signaling release for a call.
RRC
abnormal
release
caus
N/A
N/
A
Indicates the cause of an abnormal signaling release for a call.
Measure
ment
informati
on during
call
release
N/A
N/
A

measurement during the signaling release. The information
about a maximum of 10 MRs can be collected. The
information includes Ec/No and RSCP of release cells and
RSSI of inter-RAT cells.
Contains Ec/No and RSCP of serving cells and neighboring

cells (a maximum of three neighboring cells).
The causes include the general exception cause, subcause of

exceptions, and detailed exception cause.
CS Service Information
Paramet
er
Range
U
ni
t
Description
RAB
setup
time
N/A
N/
A
Indicates the setup duration of RAB service during

a call.
RAB is an abbreviation for Radio Access Bearer.
The RAB request completion time is measured
when the RAB assignment procedure is successful.
That is, after receiving an RAB setup completion
message, the SRNC sends a Radio Access Bearer
Assignment Response message to the CN.
Issue 01 (2011-08-15)

328
Nastar
Paramet
er
Range
U
ni
t
Description
RAB
request
service
type
CHR_RAB_TRAF_
CS_AMR
N/
A

The service types in CS domain are as follows:
CHR_RAB_TRAF_
CS_VP,
CHR_RAB_TRAF_CS_AMR
CHR_RAB_TRAF_
CS_OTHER,
CHR_RAB_TRAF_CS_OTHER
CHR_RAB_TRAF_CS_VP
CHR_RAB_TRAF_
BUTT,
CHR_RAB_TRAF_
NULL
UL/DL
RB rate
during
RAB
setup
(kbps)
[0.00,+)
UL/DL
channel
type for
RB
transmiss
ion
during
RAB
setup
CHR_NO_TRCH
kb
it/s
Indicates the uplink/downlink radio bearer rate

during the RAB setup.
RB is an abbreviation for Radio Bearer.
CHR_DCH
N/
A
Indicates the type of uplink/downlink radio bearer

transmission channel during the RAB setup.
CHR_FACH
The types are as follows:
CHR_RACH
CHR_NO_TRCH
CHR_HSDSCH
CHR_DCH
CHR_EDCH
CHR_FACH
CHR_RACH
CHR_HSDSCH
CHR_EDCH
Issue 01 (2011-08-15)
RAB call
drop
indicatio
n
Call drop
Indicates the service indication of RAB call drops.
Normal
N/
A
Ratio of
Good
SQI (%)
[0,100]
Indicates the ratio of Good SQI of voice services

during a call.
SQI indicates a level of a voice service, which can
be Good, Accept, Bad. The threshold for each level
is determined by the RNC configuration. Default
configuration: Bad for a voice service with a score
lower than 200, Good for a voice service with a
score higher than 313.

329
Nastar
Paramet
er
Range
U
ni
t
Description
Ratio of
Accept
SQI (%)
[0,100]
Indicates the ratio of Accept SQI of voice services

during a call.
Ratio of
Bad SQI
(%)
[0,100]
Average
SQI
[0,500]

%
Indicates the ratio of Bad SQI of voice services

during a call.
N/
A
Indicates the average SQI of voice services during

a call.
SQI is an abbreviation for Signal Quality Indicator.
Issue 01 (2011-08-15)
Number
of times
UL
service
BLER
falls into
levels 1
to 6
[0,+)
Total
number
of UL
blocks
received
within
the five
periods
before
link
release
[0,+)
Nu
m
be
r
Indicates the total number of BLERs within level

1 to level 6 on the uplink service.
BLER is an abbreviation for Block Error Rate.
Standards for BLER level 1 to 6 of the AMR
service:
0-0.78%, 0.78%-1.56%, 1.56%-3.12%,
3.12%-6.24%, 6.24%-12.48%, and >12.48%
Nu
m
be
r
Indicates the total number of blocks received on the

uplink during the periods from 1 to 5 before link
release.
The time before link release is the time when a
service is release, for example, an IU RELEASE
message is received.

330
Nastar
Paramet
er
Range
U
ni
t
Description
Number
of UL
error
blocks
received
within
the five
periods
before
link
release
[0,+)
Nu
m
be
r
Indicates the total number of error blocks received

on the uplink during the periods from 1 to 5 before
link release.
RAB
release
time
N/A
N/
A
Indicates the RAB release time during a call.
Best cell
before
the RAB
release
N/A
N/
A
Indicates the name of the cell with the best signal

quality before the RAB release.
UL/DL
rate
during
RAB
release
(kbps)
[0.00,+)
UL/DL
channel
type
during
RAB
release
CHR_NO_TRCH
CHR_DCH
The time before link release is the time when a

service is release, for example, an IU RELEASE
message is received.
RAB release time is measured when a UE receives

an IU REL CMD message (normal release) or an
RB REL SUCC message during RAB release.
Indicates the uplink/downlink rate during the RAB

release.
N/
A
Indicates the type of uplink/downlink transmission

channel during the RAB release.
N/
A
Indicates the cause of an RAB setup failure or

release failure.
CHR_FACH
CHR_RACH
CHR_HSDSCH
CHR_EDCH
RAB
setup or
release
failure
cause
Issue 01 (2011-08-15)
N/A

331
Nastar
PS Service Information
Paramet
er
Range
U
nit
Description
RAB
setup
time
N/A
N/
A
Indicates the setup duration of PS services during a

call, that is, the RAB request completion time.
RAB
request
service
type
CHR_RAB_TRA
F_PS_GENERAL
,
The RAB request completion time is measured when

the RAB assignment procedure is successful. That is,
after receiving an RAB setup completion message, the
SRNC sends a Radio Access Bearer Assignment
Response message to the CN.
N/
A

In PS domain, the service types are as follows:
CHR_RAB_TRAF_PS_GENERAL
CHR_RAB_TRA
F_PS_CMB,
CHR_RAB_TRAF_PS_CMB
CHR_RAB_TRA
F_PS_HSDPA,
CHR_RAB_TRAF_PS_HSDPA
CHR_RAB_TRA
F_PS_HSUPA,
CHR_RAB_TRAF_PS_HSDPA_HSUPA
CHR_RAB_TRAF_PS_HSUPA
CHR_RAB_TRA
F_PS_HSDPA_H
SUPA,
CHR_RAB_TRA
F_BUTT,
CHR_RAB_TRA
F_NULL
Issue 01 (2011-08-15)
UL/DL
RB rate
during
RAB
setup
(kbps)
[0.00,+)
UL/DL
channel
type for
RB
transmiss
ion
during
RAB
setup
CHR_NO_TRCH
RAB call
drop
indicatio
n
Call drop
CHR_DCH
Indicates the uplink/downlink radio bearer rate during

the RAB setup.
N/
A
Indicates the type of uplink/downlink radio bearer

transmission channel during the RAB setup.
N/
A
Indicates the service indication of RAB call drops.
CHR_FACH
CHR_RACH
CHR_HSDSCH
CHR_EDCH
Normal

332
Nastar
Paramet
er
Range
U
nit
Description
UL/DL
RAB
negotiate
d final
rate
(kbps)
[0.00,+)
kbi
t/s
Indicates the uplink/downlink final transmission rate

during the data sending of RAB service.
Number
of UL
TRB
RLC
resets
[0,+)
Nu
mb
er
Indicates the number of uplink radio bearer resets

after multiple RLC retransmissions fail in
acknowledged mode.
Number
of DL
TRB
RLC
resets
[0,+)
Nu
mb
er
Indicates the number of downlink radio bearer resets

after multiple RLC retransmissions fail in
acknowledged mode.
HSDPA
Ratio of 0
BO (%)
[0,100]
Indicates the proportion that the amount of

transmission data is zero.
HSDPA is an abbreviation for High Speed Downlink
Packet Access.
This KPI is valid for only versions earlier than BSC
V900R013.
Issue 01 (2011-08-15)
HSDPA
PDCP
UL data
amount
[0,+)
byt
e
Indicates the amount of uplink data at the packet data

convergence layer of the HSDPA service.
HSDPA
PDCP
DL data
amount
[0,+)
byt
e
Indicates the amount of downlink data at the packet

data convergence layer of the HSDPA service.
Bytes of
HSDPA
MAC-d
flow
(sufficien
t UE
resources
)
[0,+)
byt
e
Indicates the bytes of HSDPA MAC-d flow when UE

data sources are sufficient, that is, the total amount of
data transmitted at the PDCP layer for an HSDPA
subscriber on the downlink over the Iu interface.
This parameter is valid for only BSC V900R013 and
later versions.

333
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
U
nit
Description
Duration
for
sending
HSDPA
MAC-d
flow
(sufficien
t UE
resources
)
[0,+)
Se
co
nd
Indicates the duration for sending the HSDPA MACd flow when UE data sources are sufficient, that is,
the total duration for sending the data transmitted at
the PDCP layer for an HSDPA subscriber on the
downlink over the Iu interface.
Bytes of
HSDPA
MAC-d
flow
(insuffici
ent UE
resources
)
[0,+)
Duration
for
sending
HSDPA
MAC-d
flow
(insuffici
ent UE
resources
)
[0,+)
Number
of times
UL
service
BLER
falls into
levels 1
to 6
[0,+)
Total
number
of UL
blocks
received
within
the five
periods
before
link
release
[0,+)

later versions.
byt
e
Indicates the bytes of HSDPA MAC-d flow when UE

data sources are insufficient, that is, the total amount
of data transmitted at the PDCP layer for an HSDPA
subscriber on the downlink over the Iu interface.
later versions.
Se
co
nd
Indicates the duration for sending the HSDPA MACd flow when UE data sources are insufficient, that is,
the total duration for sending the data transmitted at
the PDCP layer for an HSDPA subscriber on the
downlink over the Iu interface.
later versions.
Nu
mb
er
Indicates the total number of BLERs within level 1 to

level 6 on the uplink service.
Standards for BLER level 1 to 6 of PS services:
0=< X =<0.39%, 0.39%< X =<0.78%, 0.78%< X
=<3.12%, 3.12%< X =<6.24%, 6.24%< X =<12.48%,
12.48%< X
Nu
mb
er
Indicates the total number of blocks received on the

uplink during the periods from 1 to 5 before link
release.
The time before link release is the time when a service
is release, for example, an IU RELEASE message is
received.

334
Nastar
Paramet
er
Range
U
nit
Description
Number
of UL
error
blocks
received
within
the five
periods
before
link
release
[0,+)
Nu
mb
er
Indicates the total number of error blocks received on

the uplink during the periods from 1 to 5 before link
release.
RAB
release
time
N/A
N/
A
Indicates the RAB release time during a call.
Best cell
before
the RAB
release
N/A
N/
A
Indicates the name of the best cell before the RAB

release.
UL/DL
rate
during
RAB
release
(kbps)
[0.00,+)
kbi
t/s
Indicates the uplink/downlink rate during the RAB

release.
UL/DL
channel
type
during
RAB
release
CHR_NO_TRCH
N/
A
Indicates the type of uplink/downlink transmission

channel during the RAB release.
N/
A
Indicates the cause of an RAB setup failure or release

failure.
The time before link release is the time when a service

is release, for example, an IU RELEASE message is
received.
CHR_DCH
CHR_FACH
CHR_RACH
CHR_HSDSCH
CHR_EDCH
RAB
setup or
release
failure
cause
Issue 01 (2011-08-15)
N/A


335
Nastar
Statistical Information
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Number
of DCCC
increase
initiation
s
[0,
+)
Nu
mbe
r
Indicates the number of DCCC rate increase initiations during a

call.
Number
of
successfu
l DCCC
increases
[0,
+)
Nu
mbe
r
Indicates the number of successful DCCC rate increases during a

call.
Number
of DCCC
decrease
initiation
s
[0,
+)
Nu
mbe
r
Indicates the number of DCCC rate decrease initiations during a

call.
Number
of
successfu
l DCCC
decreases
[0,
+)
Nu
mbe
r
Indicates the number of successful DCCC rate decreases during a

call.
Number
of RAB
Setup
Times/
Number
of
Successf
ul RAB
Setup
Times/
Number
of
Normal
RAB
Releases
(AMR)
[0,
+)
Nu
mbe
r
Indicates the number of RAB setup times, successful RAB setup

times, and normal RAB releases in the AMR service during a call.

336
Nastar
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Number
of RAB
Setup
Times/
Number
of
Successf
ul RAB
Setup
Times/
Number
of
Normal
RAB
Releases
(VP)
[0,
+)
Nu
mbe
r

times, and normal RAB releases in the VP service during a call.
Number
of RAB
Setup
Times/
Number
of
Successf
ul RAB
Setup
Times/
Number
of
Normal
RAB
Releases
(PS)
[0,
+)
Nu
mbe
r

times, and normal RAB releases in the PS service during a call.

337
Nastar
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Number
of RAB
Setup
Times/
Number
of
Successf
ul RAB
Setup
Times/
Number
of
Normal
RAB
Releases
(HSDPA
)
[0,
+)
Nu
mbe
r

times, and normal RAB releases in the HSDPA service during a
call.
Number
of Soft
Handove
r
Attempts
[0,
+)
Nu
mbe
r
Indicates the number of soft handover attempts during a call.
Number
of
Successf
ul Soft
Handove
rs
[0,
+)
Nu
mbe
r
Indicates the number of successful soft handovers during a call.
Number
of Softer
Handove
r
Attempts
[0,
+)
Nu
mbe
r
Indicates the number of softer handover attempts during a call.
Number
of
Successf
ul Softer
Handove
rs
[0,
+)
Nu
mbe
r
Indicates the number of successful softer handovers during a call.

338
Nastar
Paramet
er
Ran
ge
Uni
t
Description
Number
of Times
IntraFrequenc
y Hard
Handove
rs Are
Initiated
[0,
+)
Nu
mbe
r
Indicates the number of times intra-frequency hard handovers are

initiated during a call.
Number
of Times
IntraFrequenc
y Hard
Handove
rs Are
Initiated
Successf
ully
[0,
+)
Nu
mbe
r
Indicates the number of times intra-frequency hard handovers are

initiated successfully during a call.
Number
of Times
InterFrequenc
y Hard
Handove
rs Are
Initiated
[0,
+)
Nu
mbe
r
Indicates the number of times inter-frequency hard handovers are

initiated during a call.
Number
of Times
InterFrequenc
y Hard
Handove
rs Are
Initiated
Successf
ully
[0,
+)
Nu
mbe
r
Indicates the number of times inter-frequency hard handovers are

initiated successfully during a call.
Paramet
er
Ran
ge
Uni
t
Description
SHO
initiating
time
N/A
N/A
Indicates the time when a soft handover request is initiated.
Handover Information
Issue 01 (2011-08-15)

339
Nastar
Paramet
er
Ran
ge
Uni
t
Description
Measure
ment
informati
on during
SHO
N/A
N/A

measurement during a soft handover, including:
IDs of cells in active set
Ec/NO of cells in active set (dB)
RSCP of cells in active set (dBm)
IDs of cells in monitoring set
Ec/NO of cells in monitoring set (dB)
RSCP of cells in monitoring set (dBm)
SHO
target cell
N/A
N/A
Indicates the information about target cells (a maximum of three

target cells) for soft handovers, including:
ID of SHO target cell
Link setup time
Link removal time
Operation type
SHO type
CRNC communication context
SHO
failure
cause
N/A
N/A
Indicates the cause of a failed soft handover.
HHO
initiating
time
N/A
N/A
Indicates the time when a hard handover request is initiated.
HHO
initiating
cause
N/A
N/A
Indicates the cause of a hard handover request is initiated.
HHO
failure
cause
N/A
N/A
Indicates the cause of a failed hard handover.
HHO
target cell
N/A
N/A
Indicates the information about the target cell for a hard handover.
Measure
ment
informati
on during
HHO
N/A
N/A

measurement during a hard handover, including:
The causes include the general exception cause, subcause of

exceptions, and detailed exception cause.
IDs of cells in active set

CRNC communication context
HHO target cell
Ec/NO of the target cell (dB)
RSCP of the target cell (dBm)
Issue 01 (2011-08-15)

340
Nastar
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
InterRAT HO
initiating
time
N/A
N/A
Indicates the time when an inter-RAT handover request is

initiated.
InterRAT HO
initiating
cause
N/A
N/A
Indicates the cause of an inter-RAT handover request.
MCC of
InterRAT HO
target cell
[000
,
999]
N/A
Indicates the Mobile Network Code (MCC) of the target cell for
an inter-RAT handover.
MNC of
InterRAT HO
target cell
A
twodigit
or
thre
edigit
num
ber
from
0 to
9
N/A
Indicates the MNC of the target cell of the inter-RAT handover.
LAC of
InterRAT HO
target cell
[1,6
553
3]
N/A
Indicates the location area code of the target cell for an inter-RAT
handover.
CI of
InterRAT HO
target cell
[0,6
553
5]
N/A
Indicates the cell identity of the target cell for an inter-RAT

handover.
A
thre
edigit
num
ber
from
0 to
9

341
Nastar
Paramet
er
Ran
ge
Uni
t
Description
InterRAT HO
target
System
CH
R_G
SM_
SYS
,
N/A
Indicates the target system for an inter-RAT handover, including:

CHR_GSM_SYS,
CHR_GPRS_SYS,
CHR_CDMA_SYS,
CHR_WCDMA_SYS,
CH
R_G
PRS
_SY
S,
CHR_TDSCDMA_SYS
CH
R_C
DM
A_S
YS,
CH
R_
WC
DM
A_S
YS,
CH
R_T
DSC
DM
A_S
YS
InterRAT HO
failure
cause
Issue 01 (2011-08-15)
N/A
N/A
Indicates the failure cause of an inter-RAT handover.

342
Nastar
13
UMTS Cell Performance Analysis
About This Chapter

The UMTS cell performance analysis function enables you to obtain UMTS cell performance
analysis data, create UMTS cell performance analysis tasks, query UMTS cell performance
analysis results, and export UMTS cell performance analysis reports from the Nastar. You can
learn the actual causes of abnormal calls in problem cells by querying abnormal call data. This
function helps to improve the service quality and subscriber satisfaction.
13.1 Basic Knowledge of UMTS Cell Performance Analysis
This section describes the basic knowledge of UMTS cell performance analysis, which helps to
quickly identify problem cells and enables the Nastar to obtain the data of abnormal calls of
problem cells. By analyzing and displaying the data of abnormal calls, the Nastar assists in
identifying the causes of problem cells and facilitating in-depth problem analysis.
13.2 UMTS Cell Performance Analysis Process
This section describes the UMTS cell performance analysis process.
13.3 Obtaining UMTS Cell Performance Analysis Data
This section describes how to enable the Nastar to obtain UMTS cell performance analysis data.
13.4 Creating a UMTS Cell Performance Analysis Task
This section describes how to create UMTS cell performance analysis tasks. After you create a
UMTS cell performance analysis task, the Nastar analyzes abnormal call records of problem
cells. By querying analysis results, you can learn about the causes of abnormal calls in a cell.
13.5 Querying UMTS Cell Performance Analysis Results
This section describes how to query UMTS cell performance analysis results. After analyzing
the abnormal call records of problem cells, the Nastar displays analysis results including
exception causes and bottom subscribers in an analysis report, helping you locate and solve
problems related to cell performance.
13.6 Exporting UMTS Cell Performance Analysis Reports
This section describes how to export UMTS cell performance analysis reports. You can export
the queried cell performance analysis results as .xls or .xlsx files to locate problem cells on the
network based on the analysis results.
Issue 01 (2011-08-15)

343
Nastar
13.7 Technical Specifications for UMTS Cell Performance Analysis

This section describes the technical specifications for UMTS cell performance analysis.
13.8 Reference to the UMTS Cell Performance Analysis Interface
This section describes the interface for UMTS cell performance analysis and the relevant
UMTS cell performance analysis.
Issue 01 (2011-08-15)

344
Nastar
13.1 Basic Knowledge of UMTS Cell Performance Analysis

This section describes the basic knowledge of UMTS cell performance analysis, which helps to
quickly identify problem cells and enables the Nastar to obtain the data of abnormal calls of
problem cells. By analyzing and displaying the data of abnormal calls, the Nastar assists in
identifying the causes of problem cells and facilitating in-depth problem analysis.
Cell Performance Analysis

Generally, the whole-to-partial analysis method is used during network optimization or
performance analysis. That is, the Nastar locates and analyzes network problems by monitoring
performance KPIs, and then analyzes the KPIs of the entire network or a specific BSC. Then,
the Nastar analyzes cells of a faulty BSC to identify the bottom problem cells. After that, the
Nastar performs in-depth analysis on the bottom problem cells.
At present, the Nastar can perform cell-level analysis for performance data. The Nastar can
provide detailed and in-depth analysis on problem cells.
The functions provided by the Nastar are as follows:
l
The Nastar analyzes exceptional call records based on the RNC or NE groups and provides
bottom causes of exceptional cells. This helps network engineers to identify the detailed
causes of the exception, thus improving work efficiency.
After the main exceptions of problem cells are identified, the Nastar provides users with
an in-depth understanding of bottom users with poor KPIs by providing the function of
analyzing bottom problem users in cells. This function helps network engineers to locate
bottom users of an exception type in problem cells. In this manner, network engineers can
solve the problems of bottom users, hence improving cell performance.
If problem cells are not identified, the Nastar performs exception analysis of a large number
of cells under the BSC, which helps to quickly identify the bottom problem cells.
The results of cell performance analysis can be exported as .csv, .xls or .xlsx files. In this manner,
users can optimize problem cells on the network according to the exported analysis results.
Exception Types
The cell performance exceptions are analyzed from two aspects, namely, objective network
exception and subjective subscriber experience exception. For details, see Table 13-1.
Table 13-1 Exception types and functions
Issue 01 (2011-08-15)
Service
Type
Exception Type
Network
level
Objective
network
exception
Function
Non-service RRC
setup failure
Indicates exceptional conditions

during the RRC setup process.
Service RRC setup

failure

during the RRC setup process.
Outgoing SHO
failures

during outgoing soft handovers.

345
Nastar
Service
Type
Exception Type
Subjective
experience
exception
CS AMR
service
Objective
network
exception
Subjective
experience
exception
CS VP
service
CS other
service
Issue 01 (2011-08-15)
Objective
network
exception
Function
Incoming SHO
failures

during incoming soft handovers.
Outgoing HHO
failures

during outgoing hard handovers.
Incoming HHO
failures

during incoming hard handovers.
Non-service RRC
long access delay

when delay is very long during
the access of the RRC.
Service RRC long

access delay

when delay is very long during
the access of the RRC.
AMR Call setup

failure

during the call setup process.
AMR Call
completion failure

during the call completion
process.
AMR Call drop

if service call drops occur.
AMR RAB setup

failure

if the RAB fails to be set up.
AMR Long call

connection delay

if call connection delay occurs.
AMR Long RAB

setup delay

during the RAB setup process.
AMR Short service

duration

if extra-short call duration occurs.
AMR High ratio of

bad SQI

if service quality is poor.
CS Other Call setup

failure

CS Other Call
completion failure

process.
CS Other Call drop

CS Other RAB setup

failure


346
Nastar
Service
Type
Exception Type
Subjective
experience
exception
PS PS
service
Objective
network
exception
Subjective
experience
exception
PS HSDPA
service
Issue 01 (2011-08-15)
Objective
network
exception
Function
CS Other Long call
connection delay

CS Other Long RAB

setup delay

CS Other Short
service duration

PS call setup failure

PS call completion
failure

process.
PS call drop

PS RAB setup failure

PS long call
connection delay

PS long RAB
connection delay

PS short service
duration

PS DCCC rate
increase failure

during the increase of the rate of
the DCCC.
PS DCCC rate
decrease failure

during the decrease of the rate of
the DCCC.
Low PS UL RAB
negotiated final rate

if the transmission rate of uplink
services is low.
Low PS DL RAB
negotiated final rate

if the transmission rate of
downlink services is low.
HSDPA call setup

failure

HSDPA call
completion failure

process.

347
Nastar
Service
Type
Exception Type
Subjective
experience
exception
PS HSUPA
service
Objective
network
exception
Subjective
experience
exception
Issue 01 (2011-08-15)
Function
HSDPA call drop

HSDPA RAB setup

failure

HSDPA long call

connection delay

HSDPA long RAB

setup delay

HSDPA short service

duration

HSDPA DCCC rate

increase failure

the DCCC.
HSDPA DCCC rate

decrease failure

the DCCC.
HSDPA Low
HSDPA DL average
rate

HSUPA call setup

failure

HSUPA call
completion failure

process.
HSUPA call drop

HSUPA RAB setup

failure

HSUPA long call

connection delay

HSUPA long RAB

setup delay

HSUPA short service

duration

HSUPA DCCC rate

increase failure

the DCCC.

348
Nastar
Service
Type
PS other
service
Exception Type
Objective
network
exception
Subjective
experience
exception
Function
HSUPA DCCC rate
decrease failure

the DCCC.
HSUPA poor UL
BLER level

PS Other call setup

failure

PS Other call
completion failure

process.
PS Other call drop

PS Other RAB setup

failure

PS Other long call

connection delay

PS Other long RAB

setup delay

PS Other short service

duration

PS Other DCCC rate

increase failure

the DCCC.
PS Other DCCC rate

decrease failure

the DCCC.
Limitations
If further analysis for cell performance fails, the number of call records under an RNC may be
too excessive. Therefore, it is recommended that a cell performance analysis task should contain
the network elements (NEs) under the same RNC within three days.
13.2 UMTS Cell Performance Analysis Process

This section describes the UMTS cell performance analysis process.
Figure 13-1 shows the process of UMTS cell performance analysis.
Issue 01 (2011-08-15)

349
Nastar
Figure 13-1 Process of UMTS cell performance analysis

Table 13-2 Description of UMTS cell performance analysis process
Issue 01 (2011-08-15)
No.
Procedure
Description
Create a UMTS
cell performance
analysis data E2E
task
You need to choose Maintenance > E2E Task

Management on the Nastar client to open the E2E Task
Management window and then create a E2E task. After you
create the task, the Nastar issues rule files to the M2000, and
then the M2000 sends the rule files to the related SAU. Then,
the SAU performs the measurement task.

350
Nastar
No.
Procedure
Description
Create a UMTS cell

performance
task
You need to choose Maintenance > Task Management on

the Nastar client to open the Task Management window and
then create a UMTS cell performance analysis data import
task. After you create the task, the Nastar periodically
imports the UMTS performance data files saved on the
Nastar server into the database.
Check the integrity

of UMTS cell
performance
analysis data

required UMTS cell performance analysis data is imported
into the database.
Create a UMTS
cell performance
analysis task

client, you can create a UMTS cell performance analysis task.
After you create the task, the Nastar periodically retrieves
UMTS cell performance analysis data and UMTS
configuration data from the database, analyzes the retrieved
Query UMTS cell

performance
analysis results
You can view the analysis results of the UMTS cell

performance analysis tasks that are executed successfully.
Export UMTS cell

performance
analysis reports
You can enable the Nastar client to export UMTS cell

performance analysis reports as files.
13.3 Obtaining UMTS Cell Performance Analysis Data

This section describes how to enable the Nastar to obtain UMTS cell performance analysis data.

Prerequisite
l
Configuration Data.
Issue 01 (2011-08-15)

351
Nastar
Context
Procedure
displayed.
TIP

1.
2.
NOTE
OSS to be analyzed.
Step 4 Click Next.

CAUTION
step.
Issue 01 (2011-08-15)

352
Nastar
If...
Then...
data E2E task
list.


task

E2E task

list.



----End
Follow-up Procedure
If you need to...
Then...
Click Property.
Click Delete.
NOTE

Click Refresh.
shortcut menu.
NOTE
Issue 01 (2011-08-15)

353
Nastar

Prerequisite
Context
l
at the preset time.
Issue 01 (2011-08-15)
Analysis Task
Type
Creation
GSM MR Analysis

Analysis Data
Manual creation
GSM Neighboring
Cell Analysis

Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Manual creation
GSM VIP Analysis

Data
Manual creation

354
Nastar
Analysis Task
Type
Creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Manual creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
Issue 01 (2011-08-15)
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis

Analysis Data
Manual creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Data
Manual creation
UMTS Coverage
Analysis

Analysis Data
Manual creation
UMTS VIP
Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis

Analysis Data
Manual creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis

Analysis Data
Manual creation

355
Nastar
Analysis Task
Type
Creation
UMTS Service
Geographic
Analysis

Analysis CHR Data
Manual creation

Analysis MR Data
CDMA Uplink
Interference
Ranking Analysis
Import CDMA Uplink

Analysis Data
Manual creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis

Manual creation
CDMA Complaint
Analysis Support
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

(1X)
Manual creation

Cell Analysis Data
(EVDO)
l Import CDMA Pilot

(EVDO)
CDMA Coverage
Analysis

Analysis Data (1X)
Manual creation

Issue 01 (2011-08-15)
CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis

Manual creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis

Data
Manual creation

356
Nastar
Analysis Task
Type
Creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis

Analysis Data
Manual creation
LTE Complaint
Analysis Support
LTE Cell Fault

Diagnosis
Analysis
Procedure
1.
2.
3.
Periodic.

1.
NOTE
2.

----End
Follow-up Procedure
Issue 01 (2011-08-15)

357
Nastar
If you need to...
Then...
Delete a task
Click Delete.
NOTE
Suspend a task or
resume a task

l Manual mode
the shortcut menu.
l Automatic mode
NOTE

of a task
Running to Idle.
NOTE

Prerequisite
l
Context
Issue 01 (2011-08-15)
Analysis Task Type
Data Type

Analysis Task


358
Nastar
Issue 01 (2011-08-15)
Analysis Task Type
Data Type
Cell Analysis Task


Task


Analysis Task

analysis data


Support Task

Analysis Task

data

Task

Analysis Task

parameters

Analysis Task

analysis data
Task

Cell Analysis Task


Task


Support Task

Analysis Task

data

Analysis Task

analysis data

Task

359
Nastar
Analysis Task Type
Data Type

Analysis Task

parameters

Analysis Task

Task


Support Task

Analysis Task


Task

services)

Analysis Task

analysis data



Analysis Task

data

Support Task

Analysis Task
Procedure
Issue 01 (2011-08-15)

360
Nastar
TIP
required.
Step 5 Click Query.
----End
13.4 Creating a UMTS Cell Performance Analysis Task

This section describes how to create UMTS cell performance analysis tasks. After you create a
UMTS cell performance analysis task, the Nastar analyzes abnormal call records of problem
cells. By querying analysis results, you can learn about the causes of abnormal calls in a cell.
Prerequisite
l
Context
Procedure
Step 1 Click
TIP
Step 3 Click Next.
Issue 01 (2011-08-15)

361
Nastar
required object.
Step 5 Click Next.
If...
Then...
NE is selected

Data tab page.
time.
NOTE
for analysis.


----End
Follow-up Procedure
TIP
Issue 01 (2011-08-15)

362
Nastar
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Save as the tasks
Refresh

Suspended.
Resume.
, or right-click
, or right-click

Click
13.5 Querying UMTS Cell Performance Analysis Results

This section describes how to query UMTS cell performance analysis results. After analyzing
the abnormal call records of problem cells, the Nastar displays analysis results including
exception causes and bottom subscribers in an analysis report, helping you locate and solve
problems related to cell performance.
Prerequisite
l
The progress bar of the UMTS cell performance analysis task reaches 100%.
Procedure
Step 1 Choose UMTS Cell Performance Analysis Task from the navigation tree in the Analysis Task
Management window.
tasks.
Result from the shortcut menu. The UMTS Cell Performance Analysis Task window is
displayed.
NOTE
Step 5 Query the UMTS cell performance analysis results in the UMTS Cell Performance Analysis
Task window. Select a cell node from the object navigation tree in the left pane. Then, you can
Issue 01 (2011-08-15)

363
Nastar
view the counter overview information of the selected cell in the middle area and the ranking of
counters on the right of the window.
1.
Select a cell node in the navigation tree in the left pane.

You can type the key field of a cell in the Search area, and then click
locate the cell.
2.
to search for and
The areas on the right and in the middle of the window show counter overview information
about the selected cell and ranking of counters.
l A table in the middle area of the window displays the number of records of each
exception type in a cell and the percentage of each exception type to all exception types.
A pie chart in the lower area of the window displays the percentage of each exception
type.
The abnormal cell performance is analyzed from objective network exception and
subjective experience exception. For details, see 13.1 Basic Knowledge of UMTS Cell
Performance Analysis.
l In the area on the right, the bottom subscribers identified by IMSIs, bottom cells, and
bottom exception causes are illustrated in tables. The tables show the number of
exception records and the percentage of each exception type.
You can set Quantity to determine the number of bottom subscribers, bottom cells, and
bottom exception causes. By default, bottom 10 subscribers, cells, and exception causes
are displayed. The default number cannot be modified.
NOTE
Bottom Exceptional Cell in the Show drop-down list is valid only when the overview node or NE
group node in the object navigation tree is selected.
l In the pie chart area, you can right-click the chart and then choose an option from the
shortcut menu to perform the corresponding operation, such as modifying the attributes
of the chart, and resizing, saving, and printing the chart.
Step 6 Start further analysis for one exception type.
l Select a cell or a RNC node in the navigation tree in the left pane, and right-click Start
Further Analysis. Then, the system will display all the exception records of the selected cell
or the selected BSC.
. Then, the system will
l In the middle area, choose an exception type and click
display all the exception records of the selected exception type of the subscriber or the cell.
l In the area on the right, choose a subscriber or a cell and click
. Then, the system
will display all the exception records of the selected subscriber or the selected cell of the
exception type.
----End
Follow-up Procedure
You can export analysis results. For details, see 13.6 Exporting UMTS Cell Performance
Analysis Reports.
Issue 01 (2011-08-15)

364
Nastar
13.6 Exporting UMTS Cell Performance Analysis Reports

This section describes how to export UMTS cell performance analysis reports. You can export
the queried cell performance analysis results as .xls or .xlsx files to locate problem cells on the
network based on the analysis results.
Prerequisite
l
UMTS cell performance analysis results are queried. For details, see 13.5 Querying UMTS
Cell Performance Analysis Results.
Procedure
in the UMTS Cell Performance Analysis Task window. The Save dialog box is
Step 1 Click
displayed.
Step 2 Set the file name and specify the file type and path to save the file. Then, click Save.
l The progress of an export task is displayed in the Exported File List dialog box. You can
You can click
or running state so that the task is terminated and deleted from the task list. You can click
on the right of the progress bar to delete an export task in the completed state so that
the task is deleted from the task list.
You can click
You can close the Exported File List dialog box and view detailed execution information
on
the upper right of the Analysis Task Management window. You can also click any icon
to open the Exported File List dialog box to view detailed task information.
l The exported analysis results are classified into analysis results of bottomN exception
subscribers obtained from cell performance analysis and exception overview results obtained
from cell performance analysis. These types of analysis results are contained in two files
separately.
----End
13.7 Technical Specifications for UMTS Cell Performance

Analysis
This section describes the technical specifications for UMTS cell performance analysis.
Issue 01 (2011-08-15)

365
Nastar
Item

<= 5,100 cells
<= 5
<= 7 days
Negligible

(all the themes)
<= 200

<= 50
13.8 Reference to the UMTS Cell Performance Analysis

Interface
This section describes the interface for UMTS cell performance analysis and the relevant
UMTS cell performance analysis.
13.8.1 Interface Description: UMTS Cell Performance Analysis

This section describes the UMTS performance analysis. Before performing relevant operations,
familiarize yourself with the functions of the areas on the interface.
The analysis results of the cell performance analysis can be displayed in tables or in pie charts,
as shown in Figure 13-2.
Issue 01 (2011-08-15)

366
Nastar
Figure 13-2 Interface of cell performance analysis
No.
Name
Description
(1)
Button area
Aggregation information about cell exception

analysis results can be exported.
(2)
Cell object navigation tree
Cell objects whose analysis results are to be displayed

can be searched through the navigation tree.
The navigation tree node is named in the format of
NE object name [Number of exception records]. In
this case, the exceptional records of each NE are
displayed intuitively.
(3)
List of exception types of

cells
(4)
Pie chart of exception types Causes and proportions of each type of exceptions are
of cells
displayed in pie charts.
Issue 01 (2011-08-15)
Exception types, number of exception records, and

proportion of each exception type are displayed in
tables.

367
Nastar
No.
Name
Description
(5)
List of bottom cells
Bottom cells, bottom users, and bottom exception

types of selected cell objects as well as number of
exception records are displayed in tables.
(6)
Pie chart for ranking bottom Proportions of each cell, user, and exception type are
cells
displayed in pie charts for each ranking mode.

Common Information
Parameter
Description
Task Name
OSS Name

E2E Task List
Begin Time

End Time
NE List
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Issue 01 (2011-08-15)
Description
Service Type

Exception Type

failure.
KPI

determination.
Determination
rule

as >=.

368
Nastar
Parameter
Description
Exception Value

UMTS VIP
Analysis Data
Task
Selected

selected.
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Group Name
Number of
Members
Report Raw Data

Description
Start NCC
End NCC
Start BCC
End BCC
ARFCN
Indication
Start ARFCN

End ARFCN
UMTS Service
Geographic
Analysis Data
Task
Downlink Ec/No
(dB)<=X

bad RxQual area.
value is -15.
UMTS
Terminal
Analysis Data
Task
Issue 01 (2011-08-15)
Type
KPI name
Criterion

369
Nastar
Parameter
Description
threshold

provided.
13.8.3 Parameters for Creating or Modifying UMTS Cell

Performance Analysis Tasks
This section describes the parameters for creating or modifying UMTS cell performance analysis
tasks. You can refer to the description when creating or modifying a UMTS cell performance
analysis task.

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:
Issue 01 (2011-08-15)
Parameter
Description
Task Type
time.

370
Nastar
Parameter
Description
Time Range
analyzed.
Delayed
Delay.
Execution
Delay

Parameter
Description
NE
network.
NE Group
the entire network.
13.8.4 Parameters for Querying UMTS Cell Performance Analysis

Results
This section describes the parameters for querying UMTS cell performance analysis results. You
can refer to the description when querying UMTS cell performance analysis results.
Exception Type Overview Table

Paramet
er
Range
U
n
it
Description
Service
Type
Network-level services:
N
/
A
Indicates the service type

corresponding to a cell exception.
CS AMR
CS VP
CS Other
PS PS
PS HSDPA
PS HSUPA
PS Other
Issue 01 (2011-08-15)

371
Nastar
Paramet
er
Range
U
n
it
Description
Exceptio
n Type
Network-level exceptions:
N
/
A
Abnormal cell performance can be

analyzed on the basis of objective
network exceptions and subjective
exceptions.
Non-service RRC setup failure

Service RRC setup failure
Outgoing soft handover failure
Incoming soft handover failure
Outgoing hard handover failure
Incoming hard handover failure
Non-service long RRC access
delay
Service long RRC access delay
CS AMR-related exceptions:
Call setup failure
Call completion failure
Call drop
RAB setup failure
Long call connection delay
Long RAB setup delay
Short service duration
High ratio of bad SQI
Exceptions related to CS VIP and
other services:
Call setup failure
Call drop
RAB setup failure
Exceptions related to PS common
PS services:
Call setup failure
Call drop
RAB setup failure
DCCC rate increase failure
Issue 01 (2011-08-15)

372
Nastar
Paramet
er
Range
U
n
it
Description
DCCC rate decrease failure

Poor uplink BLER level
Low downlink RAB negotiated
final rate
Exceptions related to PS HSDPA:
Call setup failure
Call drop
RAB setup failure
Low average downlink rate
Exceptions related to PS HSUPA:
Call setup failure
Call drop
RAB setup failure
Poor uplink BLER level
Exceptions related to PS other
services:
Call setup failure
Call drop
RAB setup failure
Issue 01 (2011-08-15)

373
Nastar
Paramet
er
Range
U
n
it
Description
Number
of
Reports
[0,+)
N
u
m
b
e
r
Indicates the number of abnormal call

records related to an exception type.
Ratio(%)
[0.00,100.00]
% Indicates the proportion of abnormal

call records related to an exception type
to the total number of abnormal call
records.
Exception Type Ranking Table

Paramet
er
Ran
ge
Uni
t
Description
Show
N/A
N/A
Specifies a rank mode, which consist of the following types:

Top abnormal causes
Top abnormal subscribers
Top abnormal cells
Quantity
[0,5
0]
Nu
mbe
r
Sets the number of displayed objects.
Exception Type Ranking Table-Top Exceptional Causes
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Exceptio
n Type
N/A
N/A
Indicates the cause of an exception.
Number
of
Reports
[0,
+)
Nu
mbe
r
Indicates the number of abnormal call records due to a certain

cause.
Ratio(%)
[0.0
0,10
0.00
]
Indicates the proportion of abnormal call records due to a certain

cause to the total number of abnormal call records.

374
Nastar
Exception Type Ranking Table-Top Exceptional Subscribes

Paramet
er
Ran
ge
Uni
t
Description
IMSI
N/A
N/A
Indicates the International Mobile Subscriber Identity (IMSI) of a

top abnormal subscriber.
Number
of
Reports
[0,
+)
Nu
mbe
r
Indicates the number of abnormal call records related to a

subscriber.
Ratio(%)
[0.0
0,10
0.00
]
Indicates the proportion of abnormal call records related to a

subscriber to the total number of abnormal call records.
Exception Type Ranking Table-Top Exceptional Cells
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Cell
Name
N/A
N/A
Indicates the name of a top abnormal cell.
Number
of
Reports
[0,
+)
Nu
mbe
r
Indicates the number of abnormal call records related to an

abnormal cell.
Ratio(%)
[0.0
0,10
0.00
]
Indicates the proportion of abnormal call records related to an

abnormal cell to the total number of abnormal call records.

375
Nastar
14
UMTS Service Geographic Analysis
About This Chapter

UMTS service geographic analysis involves obtaining UMTS service geographic analysis data,
creating a UMTS service geographic analysis task, viewing the UMTS service geographic
analysis result, and exporting a UMTS service geographic analysis report. The Nastar displays
the relevant information on the map based on the data collected for the entire network to show
the distribution of network coverage, traffic, and abnormal events in an intuitive and
comprehensive manner.
14.1 Basic Knowledge of UMTS Service Geographic Analysis
The UMTS service geographic analysis function enables the Nastar to locate and display required
information on a map based on measurement report (MR) data, call history record (CHR) data,
and property matrices related to mobile subscribers. This function helps operators identify
problem areas on the network, reducing drive test costs.
14.2 UMTS Service Geographic Analysis Process
This section describes the UMTS service geographic analysis process.
14.3 Obtaining UMTS Service Geographic Analysis Data
This section describes how to enable the Nastar to obtain UMTS service geographic analysis
data. With this function, users can import the property matrix used for service geographic
localization into the Nastar database, create E2E tasks to collect and analyze data, and create
data import tasks to import the collected analysis data into the database.
14.4 Creating UMTS Service Geographic Analysis Tasks
This section describes how to create UMTS service geographic analysis tasks. After you create
and then execute a UMTS service geographic analysis task, the Nastar displays required
information such as the distribution of network coverage, traffic, and abnormal events on the
map, based on the collected measurement report (MR) and call history record (CHR) data of the
selected NE in an intuitive and a comprehensive manner.
14.5 Querying UMTS Service Geographic Analysis Results
This section describes how to query UMTS service geographic analysis results. After you
execute a UMTS service geographic analysis task, the Nastar displays required information on
the map based on the collected measurement report (MR) and call history record (CHR) data of
the selected NE and the property matrix imported into the Nastar database to show the
distribution of network coverage, traffic, and abnormal events in an intuitive and comprehensive
manner.
Issue 01 (2011-08-15)

376
Nastar
14.6 Technical Specifications for UMTS Service Geographic Observation

This section describes the technical specifications for UMTS Service Geographic Observation.
14.7 Reference to the UMTS Service Geographic Analysis Interface
This section describes the interface for UMTS service geographic analysis and the relevant
UMTS service geographic analysis.
Issue 01 (2011-08-15)

377
Nastar
14.1 Basic Knowledge of UMTS Service Geographic

Analysis
The UMTS service geographic analysis function enables the Nastar to locate and display required
information on a map based on measurement report (MR) data, call history record (CHR) data,
and property matrices related to mobile subscribers. This function helps operators identify
problem areas on the network, reducing drive test costs.
Description
Compared with the traditional planning software, the Nastar can display and locate data collected
from the live network on a map using the UMTS service geographic analysis function. This
function enables the Nastar to display the distribution of coverage, traffic, and abnormal events
on the live network comprehensively.
The UMTS service geographic analysis function provides the following functions:
l
Network coverage geographic analysis supports the geographic rendering for the following
indicators: Ec/No, RSCP, SHO Rate, LAC, and Primary Serving Cell.
Compared with the traditional simulation, the network coverage geographic analysis
enables the Nastar to display the actual coverage of serving cells, helping operators identify
areas with coverage problems, such as weak coverage.
Network traffic geographic analysis supports the geographic rendering for the following
indicators: Traffic Distribution of Voice Service, Traffic of bad RxQual area, HSDPA
Throughput, and Rate Of Throughput.
The network traffic geographic analysis enables the Nastar to display the traffic distribution
of each area on a map, helping operators identify heavy-traffic areas.
Network event geographic analysis supports the geographic rendering for the following
indicators: Number of Service Call Drops, Number of Failed SHOs, and Number of Failed
HHOs.
The abnormal event geographic analysis enables the Nastar to display the location where
a call setup fails and a call drops in each area and the number of call setups and call drops
on a map, helping operators identify the areas where abnormal events occur frequently.
The UMTS service geographic analysis function provides the following functions:
l
Identifies areas with heavy traffic to help site deployment.
Evaluates network quality to help quickly identify network problems.
Limitation
The UMTS service geographic analysis function enables the Nastar to analyze and collect
statistics on MRs and abnormal calls of all subscribers on a network. A limitation is set for the
amount of data to be analyzed. This prevents system overload in the case of heavy traffic or if
the analysis is performed for a long time. For the DL580 server, the Nastar can collect statistics
on and analyze data of not more than 6,000 cells. For the DL980 server, the Nastar can collect
statistics on analyze data of not more than 10,000 cells.
14.2 UMTS Service Geographic Analysis Process

This section describes the UMTS service geographic analysis process.
Issue 01 (2011-08-15)

378
Nastar
Figure 14-1 shows the process of the UMTS service geographic analysis.
Figure 14-1 Process of UMTS service geographic analysis

Table 14-1 Description of UMTS service geographic analysis process
Issue 01 (2011-08-15)
No.
Procedure
Description
Import property
matrix
You can choose Maintenance > Property Matrix

Management on the Nastar client to open the Property
Matrix Management window and then import property
matrix to the Nastar database for service geographic analysis.

379
Nastar
No.
Procedure
Description
Create a UMTS
service geographic
analysis data E2E
task
You can choose Maintenance > E2E Task Management

on the Nastar client to open the E2E Task Management
window and then create a E2E task. After you create the task,
the Nastar issues rule files to the M2000, and then the M2000
sends the rule files to the related SAU. Then, the SAU
performs the measurement task.
Create a UMTS
service geographic
task
You can choose Maintenance > Task Management on the

Nastar client to open the Task Management window and
then create a UMTS service geographic observation analysis
CHR data import task and a UMTS service geographic
observation analysis MR data import task. After the task is
created, the Nastar periodically imports the UMTS service
geographic observation analysis CHR data and the UMTS
service geographic observation analysis MR data files saved
on the Nastar server into the database.
Check the integrity

of UMTS service
geographic analysis
data
You can double-click Function List > System Function >

Data Query in the Analysis Task Management window on
the Nastar client to open the Query Data dialog box and then
verify that all the required UMTS service geographic
observation analysis CHR data and UMTS service
geographic observation analysis MR data are imported into
the database.
Create a UMTS
service geographic
analysis task
You can create a UMTS service geographic analysis task in

the Analysis Task Management window. After the task is
created, the Nastar periodically retrieves UMTS service
geographic analysis data and UMTS configuration data from
the database, analyzes the retrieved data, and then generates
analysis results.
Query UMTS
service geographic
analysis results
After a UMTS service geographic analysis task is executed

successfully, you can query the analysis results in grids in the
Service Geographic Observation window, and view the
geographic layers of counters.
14.3 Obtaining UMTS Service Geographic Analysis Data

This section describes how to enable the Nastar to obtain UMTS service geographic analysis
data. With this function, users can import the property matrix used for service geographic
localization into the Nastar database, create E2E tasks to collect and analyze data, and create
data import tasks to import the collected analysis data into the database.
14.3.1 Import Property Matrix

Property matrix contains the longitude and latitude of each grid center point, cell information,
and receive signal level in a grid on the map. You can import the property matrix to match the
actual receive signal level in measurement reports (MRs) to determine the position of each
subscriber on the map.
Issue 01 (2011-08-15)

380
Nastar
Prerequisite
l
A property matrix file is obtained.
Procedure
Step 1 Choose Maintenance > Property Matrix Management. The Property Matrix
Management window is displayed.
Step 2 Click the *** Property Matrix tab, and then query the property matrix that is already imported
or not imported.
l *** indicates GSM or UMTS.
l The NEs in a configuration file are displayed in the NE Name column.
l You can check whether the property matrix of an NE is imported in the Property Matrix
column. The cells in red of this column indicate that the property matrix of the NE is not
imported.
If the service geographic analysis is required for some NEs but the property matrix of these
NEs is not imported into the Nastar database, import the property matrix and then perform
the service geographic analysis.
l Data in the property matrix table can be displayed after being filtered.
Click on the right of a column heading and select a filter item from the drop-down list to
filter data in the property matrix table.
Step 3 Click Import on the right of the window. The Import dialog box is displayed.
Step 4 Click Add. In the Open dialog box, select a property matrix file.
Property matrix files are in .txt format.
Step 5 Click Open.
Step 6 Repeat Step 4 to Step 5. All the property matrix files to be imported are added to List of ToBe-Imported Files.
Step 7 Click OK.
You can view the feature matrix import check result in the displayed dialog box.
l The Error dialog box is displayed, indicating that the subscriber feature matrix import check
fails.
You can click the link path to view the tracing record.
l The Information dialog box is displayed, indicating that the subscriber matrix import check
passes successfully and the check result is uploaded to the server.
After the files are imported, the import information about the property matrix of NEs is refreshed
in the Property Matrix column.
----End
Follow-up Procedure
You can export the property matrix as a .txt file for future use. To export the property matrix,
do as follows:
Issue 01 (2011-08-15)

381
Nastar
1.
In the Property Matrix Management window, click the *** Property Matrix tab.
*** indicates GSM or UMTS.
2.
Click Export on the right of the window. The Export dialog box is displayed.
3.
Select NEs whose property matrix needs to be exported and specify a save path.
4.
Select Combine files into one file after export as required.
5.
Click OK.

Prerequisite
l
Configuration Data.
Context
Procedure
displayed.
TIP

1.
2.
Issue 01 (2011-08-15)

382
Nastar
NOTE
OSS to be analyzed.
Step 4 Click Next.

CAUTION
step.
If...
Then...
data E2E task
list.


task

E2E task

list.



----End
Issue 01 (2011-08-15)

383
Nastar
Follow-up Procedure
If you need to...
Then...
Click Property.
Click Delete.
NOTE

Click Refresh.
shortcut menu.
NOTE

Prerequisite
Context
l
at the preset time.
Issue 01 (2011-08-15)

384
Nastar
Analysis Task
Type
Creation
GSM MR Analysis

Analysis Data
Manual creation
GSM Neighboring
Cell Analysis

Neighboring Cell
Manual creation
GSM/UMTS
Neighboring Cell
Analysis

Analysis Data
Manual creation
GSM Frequency
Analysis

Neighboring Cell
Manual creation
GSM Uplink
Interference
Analysis
Import GSM Uplink

Manual creation
GSM VIP Analysis

Data
Manual creation
GSM Complaint
Analysis Support
GSM Cell
Performance
Analysis
Import GSM Cell

Manual creation
GSM Terminal
Analysis
Import GSM Terminal

Analysis Data
Manual creation
GSM Service
Geographic
Analysis
l Import GSM Sevice

Analysis CHR Data
Manual creation
l Import GSM Sevice

Analysis MR Data
Issue 01 (2011-08-15)
UMTS Uplink
Interference
Analysis
Import UMTS Uplink

Manual creation
UMTS IntraFrequency
Neighboring Cell
Analysis

Analysis Data
Manual creation

385
Nastar
Analysis Task
Type
Creation
UMTS/GSM
Neighboring Cell
Analysis
Import UMTS/GSM
Data
Manual creation
UMTS Coverage
Analysis

Analysis Data
Manual creation
UMTS VIP
Analysis

Data
Manual creation
UMTS Complaint
Analysis Support
UMTS Pilot
Pollution Analysis

Analysis Data
Manual creation
UMTS Cell
Performance
Analysis
Import UMTS Cell

Manual creation
UMTS Terminal
Analysis

Analysis Data
Manual creation
UMTS Service
Geographic
Analysis

Analysis CHR Data
Manual creation

Analysis MR Data
Issue 01 (2011-08-15)
CDMA Uplink
Interference
Ranking Analysis
Import CDMA Uplink

Analysis Data
Manual creation
CDMA Uplink
Interference
Spectrum Analysis
Import CDMA Uplink

Manual creation
CDMA IntraFrequency
Neighboring Cell
Analysis

Manual creation
CDMA Complaint
Analysis Support

Cell Analysis Data
(EVDO)

386
Nastar
Analysis Task
Type
Creation
CDMA Pilot
Pollution Analysis
l Import CDMA Pilot

(1X)
Manual creation
l Import CDMA Pilot

(EVDO)
CDMA Coverage
Analysis

Analysis Data (1X)
Manual creation

CDMA Cell
Performance
Analysis
Import CDMA Cell

Manual creation
CDMA VIP
Analysis

Manual creation
LTE Coverage
Analysis
Import LTE Coverage

Analysis Data
Manual creation
LTE VIP Analysis

Data
Manual creation
LTE Terminal
Analysis Tasks
Import LTE Terminal

Analysis Data
Manual creation
LTE Cell
Performance
Analysis

Analysis Data
Manual creation
LTE Complaint
Analysis Support
LTE Cell Fault

Diagnosis
Analysis
Procedure
1.
2.
Issue 01 (2011-08-15)

387
Nastar
3.
Periodic.

1.
NOTE
2.

----End
Follow-up Procedure
If you need to...
Then...
Delete a task
Click Delete.
NOTE
Suspend a task or
resume a task

l Manual mode
the shortcut menu.
l Automatic mode
NOTE

of a task
Running to Idle.
NOTE

Issue 01 (2011-08-15)

388
Nastar
Prerequisite
l
Context
Issue 01 (2011-08-15)
Analysis Task Type
Data Type

Analysis Task

Cell Analysis Task


Task


Analysis Task

analysis data


Support Task

Analysis Task

data

Task

Analysis Task

parameters

Analysis Task

analysis data
Task

Cell Analysis Task


Task

389
Nastar
Issue 01 (2011-08-15)
Analysis Task Type
Data Type


Support Task

Analysis Task

data

Analysis Task

analysis data

Task

Analysis Task

parameters

Analysis Task

Task


Support Task

Analysis Task


Task

services)

Analysis Task

analysis data



Analysis Task

data

390
Nastar
Analysis Task Type
Data Type

Support Task

Analysis Task
Procedure
TIP
required.
Step 5 Click Query.
----End
14.4 Creating UMTS Service Geographic Analysis Tasks

This section describes how to create UMTS service geographic analysis tasks. After you create
and then execute a UMTS service geographic analysis task, the Nastar displays required
information such as the distribution of network coverage, traffic, and abnormal events on the
map, based on the collected measurement report (MR) and call history record (CHR) data of the
selected NE in an intuitive and a comprehensive manner.
Prerequisite
l
UMTS service geographic observation CHR analysis data, UMTS service geographic
observation MR analysis data, UMTS configuration data, engineering parameters, and
property matrix are imported into the Nastar database. For details, see Checking the
Integrity of Analysis Data.
Issue 01 (2011-08-15)

391
Nastar
Context
l
An analysis task can be performed once or periodically. A periodic task is performed by

days.
Procedure
Step 1 Click
TIP
Step 3 Click Next.
required object.
Step 5 On the Set Counter Threshold tab page, set the threshold for Traffic of bad RxQual area.
Step 6 Click Next.
Step 7 Set the execution time for the task.
If...
Then...
Task Type is set to One-time
Go to the next step to set the time range and

the start time of the task.
Task Type is set to Period
Set Set Periodic Task, Set Busy Hour for

Periodic Task.
Issue 01 (2011-08-15)

392
Nastar
If...
Then...
NE is selected

Data tab page.
time.
NOTE
for analysis.

----End
Follow-up Procedure
TIP
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Issue 01 (2011-08-15)

Suspended.
Resume.

, or right-click
, or right-click
393
Nastar
If you need to...
Then...
Save as the tasks
Refresh
Click
14.5 Querying UMTS Service Geographic Analysis Results

This section describes how to query UMTS service geographic analysis results. After you
execute a UMTS service geographic analysis task, the Nastar displays required information on
the map based on the collected measurement report (MR) and call history record (CHR) data of
the selected NE and the property matrix imported into the Nastar database to show the
distribution of network coverage, traffic, and abnormal events in an intuitive and comprehensive
manner.
Prerequisite
l
You are authorized to use the Geographic Information System (GIS).
The required engineering parameters are imported into the Nastar.
The progress of the UMTS service geographic analysis task has reached 100%.
The required map file is obtained.
Procedure
Step 1 Choose Theme Function > UMTS Service Geographic Observation from the navigation tree
on the left of the Analysis Task Management window.
If you choose Theme Function, the right task list displays all performance analysis tasks.
Step 2 Select a UMTS service geographic analysis task from the task list in the upper right of the
Analysis Task Management window.
The analysis results of the selected task are displayed in the lower right pane.
Step 3 Select an analysis result from the result list in the lower right of the Analysis Task
Management window.
Step 4 Right-click the analysis result and choose Service Geographic Observation from the shortcut
menu. The Service Geographic Observation window is displayed.
You can also double-click the selected analysis result to open the Service Geographic
Observation window.
NOTE
Step 5 Query the UMTS service geographic analysis result in the Service Geographic Observation
window.
1.
to import the map file.

Optional: Click
For details, see Importing a Map.
2.
Click
Issue 01 (2011-08-15)
to load site information.

394
Nastar
For details, see Loading Site Information.

3.
In the left navigation tree, choose the service geographic analysis node.
l The geographic data of the selected theme analysis is displayed synchronously on the
map located on the right of the window.
l Select a geographic analysis theme node, and right-click Display to open the Display
- *** dialog box. In the displayed dialog box, set information about legends and NEs.
*** indicates the name of the theme node.
On the NE tab page, you can click any node in the navigation tree and then press Ctrl
+F to search for and locate the required object.
4.
Optional: In the button area in the upper left of the window, click
Management dialog box and set map layers.
to open the Layer
NOTE
Layers can be classified into service layers and map layers. You can set attributes on service layers, such
as setting legends or deleting layers. You can only move map layers upwards or downwards.
l If multiple layers are available, select a map layer and click Up (U) or Down (D) on the
right of the layer list to adjust the map layer overlap sequence. You can also determine
whether a map layer is displayed or not and set the transparency of the map layer to be
displayed in the Properties area at the bottom of the map layer list.
l On the right of the map layer list, click Add to add a map layer file.
Map files must be in the .tab format.
l After selecting a map layer, click Properties on the lower right of the map layer list to
set the legends and NEs to be displayed on the map layer.
5.
In the geographic display area in the middle of the window, view abnormal events and the
relevant theme information on the map in grid view mode.
l Select a grid to view detailed information such as site name, longitude, and latitude, in
the detailed information display area on the right of the window.
l In the button area on the upper left of the window, perform the following operations, as
shown in Table 14-4.
Table 14-4 Functions of buttons
Button
Description
Enables you to open the legend to view the counter value range
corresponding to a color.
You can also set the legend in the Layer Management dialog
box.
or
Enables you to switch between Select Tool and Hand Tool.

Enables the Nastar to measure the distance.
For details, see Measuring Distance on the Map.
or
Issue 01 (2011-08-15)
Enables you to zoom in or zoom out on the map.

For details, see Moving/Zooming In On/Zooming Out On/
Refreshing/Fully Displaying a Map.

395
Nastar
Button
Description
Enables the Nastar to display the map in full screen.
Enables the Nastar to refresh the map.
Enables the Nastar to save a map.
For details, see Saving the Map Display Effect.
and
Enables the Nastar to filter cells.

For details, see Filtering Cells.
Enables the Nastar to load the preceding map.
Enables the Nastar to search for cells.
For details, see Searching Cells.
----End
14.6 Technical Specifications for UMTS Service Geographic

Observation
This section describes the technical specifications for UMTS Service Geographic Observation.
Issue 01 (2011-08-15)
Item

l <= 6,000 carriers (HP580)
<= 5
<= 7 days
<= 60 minutes

(all the themes)
<= 200

<= 10
l <= 12,000 carriers (HP785)

396
Nastar
14.7 Reference to the UMTS Service Geographic Analysis

Interface
This section describes the interface for UMTS service geographic analysis and the relevant
UMTS service geographic analysis.
14.7.1 Interface Description: UMTS Service Geographic Analysis

This section describes the window for UMTS service geographic analysis. Before performing
operations, you need to understand the functions of the areas in the window.
The results of service geographic analysis are displayed in grids, as shown in Figure 14-2.
Figure 14-2 Window for service geographic analysis
SN
Name
Navigation tree for

In the navigation tree, you can select a theme
geographic analysis themes node for geographic analysis. The
corresponding geographic data about this
theme is displayed in area 3.
Button area
Issue 01 (2011-08-15)
Description
You can search and locate cell objects by key

word.

397
Nastar
SN
Name
Description
Area for displaying

You can view the results of related themes in
geographic analysis results grids.
After selecting a grid, you can view detailed
information about this grid such as the site
name, longitude, and latitude in area 4.
Area for displaying

detailed information
You can view detailed information about the

selected grid.

Common Information
Parameter
Description
Task Name
OSS Name

E2E Task List
Begin Time

End Time
NE List
Special Parameter
Parameter
UMTS Cell
Performance
Analysis Data
Task
Issue 01 (2011-08-15)
Description
Service Type

Exception Type

failure.
KPI

determination.

398
Nastar
Parameter
Description
Determination
rule

as >=.
Exception Value

UMTS VIP
Analysis Data
Task
Selected

selected.
UMTS/GSM
Neighboring
Cell Analysis
Data Task
Group Name
Number of
Members
Report Raw Data

Description
Start NCC
End NCC
Start BCC
End BCC
ARFCN
Indication
Start ARFCN

End ARFCN
UMTS Service
Geographic
Analysis Data
Task
Downlink Ec/No
(dB)<=X

bad RxQual area.
value is -15.
UMTS
Terminal
Analysis Data
Task
Issue 01 (2011-08-15)
Type
KPI name
Criterion

399
Nastar
Parameter
Description
threshold

provided.
14.7.3 Parameters for Creating and Modifying UMTS Service

Geographic Analysis Tasks
This section describes the parameters for creating and modifying UMTS service geographic
analysis tasks. You can refer to the description when creating or modifying a UMTS service
geographic analysis task.

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:

Parameter
Description
Task Type
l One-time: The system executes the created tasks only once at

the specified time.
l Period: The system executes the created tasks periodically at
the preset time.
Issue 01 (2011-08-15)

400
Nastar
Parameter
Description
One-time
task
Time
Range
Only the data generated between the start time and the end time
will be analyzed.
The start time should precede the end time, and the end time
should precede the locale system time.
Delayed
If you do not select it, the system will execute the task
immediately.
If you select it, the system will execute the task at the time of the
Execution Delay.
Periodic
task
Executio
n Delay
Start
Time
Indicates date for starting a task. The start time should be later
than the current server time.
The parameter should not precede the end time of the Time
Range.
After the date is set, the Nastar will execute the task at 00:00 of
the next day by default. This parameter is valid for only periodic
tasks.
Executio
n Delay
Indicates the time delayed for running a task.

Value range: 0 to 24. Unit: hour.
The parameter must be used with Start Time. After this parameter
is set, the Nastar will execute the task certain hours later than
00:00 of the specified day in Start Time. If Start Time is set to
12/16/2009 and Execution Delay is set to 3 hours, the Nastar will
execute the task at 03:00 on December 17, 2009.
Period
Indicates the interval between periodic tasks.
Number
of
executio
n times
Indicates the times that a periodic task is executed. If this

parameter is set to 0, you can infer that the task is executed all the
time.
Value range: 0 to 9999. This parameter is valid for only periodic
tasks.
Issue 01 (2011-08-15)
Parameter
Description
NE
network.
NE Group
the entire network.

401
Nastar

Parameter
Description
The persent for low quality

>= X (%) of traffic
Indicates the traffic volume that is measured when the

percentage of the MRs with poor coverage quality to all MRs
in the grid is greater than or equal to X%.
X is the threshold for high traffic volume. Value range: an
integer from 0 to 100. Default value: 10.
14.7.4 Parameters for Querying UMTS Service Geographic Analysis

Results
This section describes the parameters for querying UMTS service geographic analysis results.
You can refer to the description when querying UMTS service geographic analysis results.
Network Coverage Geographic Observation

Paramet
er
Ran
ge
Uni
t
Description
Primary
Serving
Cell
N/A
N/A
The traffic map is rendered according to the cells that serve as

primary serving cells most frequently in MRs in the raster view.
If some cells serve as primary serving cells for the same number
of times, the traffic map is rendered according to the primary
serving cell in the MR last reported.
RSCP
N/A
dB
m
The traffic map is geographically rendered according to the

average RSCP value in MRs in the raster view.
Ec/No
N/A
dB
The traffic map is rendered according to the average receive signal

quality in MRs in the raster view.
LAC
N/A
The traffic map is rendered according to the percentage of the MRs

containing serving cells corresponding to the LAC occurring most
frequently to the total number of MRs in the raster view.
SHO
Rate
N/A
The traffic map is rendered according to the percentage of MRs in

the soft handover state to the total number of MRs in the raster
view.
If the active set of an MR contains two or more cells, the MR is in
the soft handover state.
Issue 01 (2011-08-15)

402
Nastar
Network Traffic Geographic Observation

Paramet
er
Ran
ge
Uni
t
Description
Traffic
Distributi
on of
Voice
Services
N/A
Erla
ng
The traffic map is rendered according to the traffic volume (unit:

Erlang) of voice services (default service, AMR) in the raster view.
Traffic of
Bad
RxQual
Area
N/A
Erla
ng
If the percentage of the MRs containing the Ec/No value of voice

services (default service, AMR) lower than a specified threshold
(default value, -15dB) to the total number of MRs in the raster
view is higher than a specified threshold (default value, 10%), the
traffic map is rendered according to the traffic volume (unit:
Erlang) of voice services with poor coverage quality in the raster
view.
HSDPA
Through
put
N/A
KB
The traffic map is rendered according to the traffic at the HSDPA

PDCP layer. This parameter is used only in RAN13.0.
Rate of
Through
put
N/A
KB/
s
The traffic map is rendered according to the rate of throughput in

the raster view.
Network Event Geographic Observation
Issue 01 (2011-08-15)
Paramet
er
Ran
ge
Uni
t
Description
Number
of
Service
Call
Drops
N/A
Nu
mbe
r
The traffic map is rendered according to the number of call drops

in the raster view.
Number
of Failed
SHOs
N/A
Nu
mbe
r
The traffic map is rendered according to the number of failed soft

handovers in the raster view.
Number
of Failed
HHOs
N/A
Nu
mbe
r
The traffic map is rendered according to the number of failed hard

handovers in the raster view.

403
Nastar
15
GSM/UMTS Complaint Analysis

Support
About This Chapter

The GSM/UMTS complaint analysis support function helps operators handle subscriber
complaints from GSM and UMTS networks at the same time, which effectively reduces
operation costs. The GSM/UMTS complaint analysis support function enables users to manage
complaint analysis support tasks, and query and export complaint analysis support reports. After
receiving a subscriber complaint, the Nastar quickly identifies call records related to the
complaint subscriber in a problem cell. By analyzing call access and release information and
service quality information in call records, the Nastar helps locate and solve complaint problems.
This improves the efficiency of handling complaints and increases subscriber satisfaction.
15.1 Basic Knowledge of GSM/UMTS Complaint Analysis Support
This section describes how to use the Nastar to perform GSM/UMTS complaint analysis support
based on call records of GSM subscribers and UMTS subscribers before and after complaints.
This helps to locate and solve complaint problems.
15.2 Process of GSM/UMTS Complaint Analysis Support
This section describes the process of GSM/UMTS complaint analysis support.
15.3 Creating a GSM/UMTS Complaint Analysis Support Task
This section describes how to create a GSM/UMTS complaint analysis support task when
creating a UMTS complaint analysis support task. After receiving a GSM or UMTS subscriber
complaint, you can create a GSM/UMTS complaint analysis support task on the Nastar to quickly
search for the subscriber call records related to the complaints based on the problem cell and
international mobile subscriber identity (IMSI) of the complaint subscriber. This function helps
you analyze and locate problems. You can create a GSM/UMTS complaint analysis support task
when creating a GSM complaint analysis support task or a UMTS complaint analysis support
task.
15.4 Querying GSM/UMTS Complaint Analysis Support Results
This section describes how to query GSM/UMTS complaint analysis support results. Through
this function, you can view subscriber call records and detailed information about each record.
The Nastar provides information about the terminal capability, access and release, and service
quality regarding each call record to assist you in determining the network location where
problems occur and the possible causes.
Issue 01 (2011-08-15)

404
Nastar
15.5 Exporting GSM/UMTS Complaint Analysis Support Reports

This section describes how to export GSM/UMTS complaint analysis support reports. You can
export the queried complaint analysis support results as .xls or .xlsx files as required. The
exported analysis results help you determine the network location where the problem occurs and
the possible causes.
15.6 Technical Specifications for GSM/UMTS Complaint Analysis Support
This section describes the technical specifications for GSM/UMTS complaint analysis support.
The technical specifications of GSM/UMTS complaint analysis support is included in GSM
complaint analysis support or UMTS complaint analysis support.
15.7 Reference to the GSM/UMTS Complaint Analysis Support Interface
This section describes the interface for GSM/UMTS complaint analysis support and the relevant
GSM/UMTS complaint analysis support.
Issue 01 (2011-08-15)

405
Nastar
15.1 Basic Knowledge of GSM/UMTS Complaint Analysis

Support
This section describes how to use the Nastar to perform GSM/UMTS complaint analysis support
based on call records of GSM subscribers and UMTS subscribers before and after complaints.
This helps to locate and solve complaint problems.
Complaint Analysis Support

The Nastar obtains the call event records of complaint subscribers, and then filters, aggregates,
and analyzes data based on a specified history period and detailed call records of subscribers in
a specified area, assisting in locating and solving problems. The complaint analysis support
consists of the aggregation and analysis of cause types in call reports of complaint subscribers,
aggregation and analysis of information about call reports of complaint subscribers, analysis of
detailed information about call reports of complaint subscribers, analysis of procedure before
signaling release in call reports of complaint subscribers, and analysis of active cells in call
reports of complaint subscribers.
l
The aggregation and analysis of cause types in call reports of complaint subscribers help
network engineers filter and aggregate call reports based on exception causes.
Causes are classified into five types: non-abnormal, access failed, abnormal release, service
quality problem, and others. For details about cause types, see Table 15-1.
Table 15-1 Cause type and related description
Cause Type
Description
Non-exception
Indicates that the call is normally released.
Call setup failure
Indicates that the call fails to be set up.
Abnormal call release
Indicates that the call is abnormally released

because of abnormal release of the TCH.
QoS problem
Indicates that the call is normally released and

one-way audio, crosstalk occurs or HQI smaller
than 50 during the call process.
Other
Indicates that the call is released because of

other exceptions.
The aggregation and analysis of information about call reports of complaint subscribers
provide an overview of information about all the filtered call reports. The information
includes the access time, access cell, release time, release cell, IMSI, IMEI, and service
duration. This function helps network engineers quickly identify abnormal call reports (for
example, too-short-time call reports) and preliminarily learn about the situation of
complaint subscribers.
The analysis of detailed information about call reports of complaint subscribers provides
the detailed information about all the filtered call reports. This function helps network
engineers learn the key events that occur during calls, service usage, and measurement
reports (MRs) before signaling release, accurately and quickly assisting in problem
location.
Issue 01 (2011-08-15)

406
Nastar
The information of GSM network includes the subscriber information, call access
information, call release information, and handover information.
The information of UMTS network includes the subscriber information, access/release
information, CS service information, PS service information, and handover information.
l
The analysis of procedure before signaling release in call reports of complaint subscribers
provides the detailed procedure before signaling release of all the filtered subscribers. This
function helps network engineers locate problems based on the information before signaling
release.
GSM complaint analysis support
Limitations
The GSM complaint analysis support function requires raw call records of complaint
Therefore, if IMSI is used to identify complaint subscribers, the maximum number of
complaint subscribers selected in a complaint analysis support task cannot exceed 2,000;
if peer MSISDN is used to identify complaint subscribers, the maximum number of
complaint subscribers selected in a complaint analysis support task cannot exceed 200.
NOTE
The maximum number of complaint subscribers allowed in a complaint analysis support task is
different when IMSI or peer MSISDN is used to identify complaint subscribers. The causes are as
follows:
A subscriber call report contains the IMSI of the calling party and the peer MSISDN. The format of
IMSI is fixed and unique; whereas the peer MSISDN can be a mobile phone number, fixed-line phone
number, or hotline and the MSISDN combination is different in each country. To ensure that all call
records of complaint subscribers can be obtained when the peer MSISDN is used to identify complaint
subscribers, the Nastar allows users to perform fuzzy search. That is, after users type keywords, all
call records whose peer MSISDN field contains keywords can be obtained. In this manner, the
integrity of analysis data is ensured, but the obtained call reports are several times of those queried
by IMSI.
Therefore, the maximum number of complaint subscribers allowed in a complaint analysis support
task when the peer MSISDN is used to identify complaint subscribers is smaller than that in the case
when IMSI is used to identify complaint subscribers.
UMTS complaint analysis support

The UMTS complaint analysis support function requires raw call data from complaint
If IMSI is used to identify complaint subscribers, the maximum number of concurrent
complaint subscribers allowed by the Nastar cannot exceed 2,000, and the selected
complaint subscribers can be under different OSSs.
15.2 Process of GSM/UMTS Complaint Analysis Support

This section describes the process of GSM/UMTS complaint analysis support.
Figure 15-1 shows the process of GSM/UMTS complaint analysis support.
Issue 01 (2011-08-15)

407
Nastar
Figure 15-1 Process of GSM/UMTS complaint analysis support

Table 15-2 Description of GSM/UMTS complaint analysis support process
No.
Procedure
Description
Create a GSM/
UMTS
complaint
analysis
support task

you can create a GSM/UMTS complaint analysis support task.
After the task is created, the Nastar retrieves analysis data related
to the complaint analysis support from the database, analyzes the
Query GSM/
UMTS
complaint
analysis
support results
You can view the analysis results of the complaint analysis

support tasks that are executed successfully and also perform
Export GSM/
UMTS
complaint
analysis
support reports
You can enable the Nastar client to export GSM/UMTS

complaint analysis support results as report files.
15.3 Creating a GSM/UMTS Complaint Analysis Support

Task
This section describes how to create a GSM/UMTS complaint analysis support task when
creating a UMTS complaint analysis support task. After receiving a GSM or UMTS subscriber
Issue 01 (2011-08-15)

408
Nastar
complaint, you can create a GSM/UMTS complaint analysis support task on the Nastar to quickly
search for the subscriber call records related to the complaints based on the problem cell and
international mobile subscriber identity (IMSI) of the complaint subscriber. This function helps
you analyze and locate problems. You can create a GSM/UMTS complaint analysis support task
when creating a GSM complaint analysis support task or a UMTS complaint analysis support
task.
Prerequisite
l
Information about complaint subscribers is collected.
Configuration data is imported before you create a complaint analysis support task. If
configuration data is not imported, no object node is displayed in the object navigation tree.
Licenses for GSM complaint analysis support, UMTS complaint analysis support, GSM/
UMTS complaint analysis support in GSM complaint analysis support, and GSM/UMTS
complaint analysis support in UMTS complaint analysis support are available.
A maximum of 200 tasks of this type can be created, and a maximum of data of history
seven days can be involved in an analysis task.
The IMSI file of the complaint subscriber to be imported contains only the IMSI column,
as shown in Table 15-3.
Context
Table 15-3 Example of a GSM complaint subscriber IMSI file

IMSI
460079053010239
460005396052916
460022068262211
l
The peer number file of the complaint subscriber to be imported contains only the Peer
No. column, as shown in Table 15-4.
Table 15-4 Example of a GSM complaint subscriber peer number file
Peer No.
015839017891
051385852201
02136039950
Procedure
Step 1 Click
Issue 01 (2011-08-15)
409
Nastar
TIP
Step 3 Click Next.
Step 4 In the Analysis Type area, select GSM/UMTS Complaint Analysis Support.
NOTE
If you select UMTS Complaint Analysis Support, you can perform UMTS complaint analysis support.
For details about how to create a UMTS complaint analysis support task, see 12.3 Creating UMTS
Complaint Analysis Support Tasks.
Step 5 In the Filter NEs area, perform the following operations:

1.
Click Select to choose one or multi objects in Select NE Object.
2.
Click OK.
3.
The chosen cells are shown in table.
4.
Optional: Click Delete to delete the cells you have chosen.
Step 6 In the Filter Users area, perform the following operations:

l Adding a subscriber
1.
Click Add. In the displayed Add User dialog box, enter the IMSI of the subscriber.
2.
Click OK.
NOTE
l A maximum of 2000 IMSI numbers can be entered.

l You can only enter the 15-digit numerals.
l Importing subscriber information
Issue 01 (2011-08-15)
1.
2.
Select the edited IMSI file of a complaint subscriber, and then click Open.
3.
Perform the operations as prompted.

If...
Then...

and no identical records exist
In the displayed dialog box, click OK.

and identical records exist
In the displayed OK dialog box, click Yes to

import the new records that will overwrite
identical records.

410
Nastar
If...
Then...
Abnormal records exist in the

imported information
Current files cannot be imported and the

Nastar displays a message, indicating the
number of abnormal records.
l Click Export Check Result to export
check results from the Nastar so that you
can make modifications based on the
error information to complete the current
import task.
l Click Cancel to terminate the import task.
Step 7 Click Next.

Step 8 Set the Task Type to One-time, set the time range.
----End
Follow-up Procedure
TIP
If you need to...

Modify a task
Then...

Delete a task

Suspended a task
Restore a suspended
task
Save as the tasks
Refresh
Issue 01 (2011-08-15)

Suspended.
Resume.
, or right-click
, or right-click

Click

411
Nastar
15.4 Querying GSM/UMTS Complaint Analysis Support

Results
This section describes how to query GSM/UMTS complaint analysis support results. Through
this function, you can view subscriber call records and detailed information about each record.
The Nastar provides information about the terminal capability, access and release, and service
quality regarding each call record to assist you in determining the network location where
problems occur and the possible causes.
Prerequisite
l
The progress bar of the GSM complaint analysis support task or the UMTS complaint
analysis support task reaches 100%.
Procedure
Step 1 Click the GSM Complaint Analysis Support Task node or the UMTS Complaint Analysis
Support Task node in the navigation tree in the Analysis Task Management window.
If you click the Theme Function node, the task list in the right pane displays all the performance
analysis tasks.
Step 2 Select a GSM complaint analysis support task from the task list on the upper right of the Analysis
Step 3 Select an analysis result from the result list on the lower right of the Analysis Task
Management window.
Step 4 Right-click the result and choose View Analysis Result from the shortcut menu. The GSM
Complaint Analysis Support window or the UMTS Complaint Analysis Support window is
displayed.
You can also double-click the result to open the analysis result window.
NOTE
Step 5 In the navigation tree on the left of the GSM Complaint Analysis Support window or the
UMTS Complaint Analysis Support window, select a call record to be queried.
The navigation tree can be expanded in two modes: Cause type-IMSI and IMSI-Cause type.
l In Cause type-IMSI mode, all filtered call records are classified by cause type and the call
records of each cause type is classified by IMSI.
l In IMSI-Cause type mode, all filtered call records are classified by IMSI and the call records
of each IMSI is classified by cause type.
You can type an IMSI or a cause type in the Search area above the navigation tree to quickly
search for and locate the required call record.
For detailed description of cause types, see 15.1 Basic Knowledge of GSM/UMTS Complaint
Analysis Support.
Issue 01 (2011-08-15)

412
Nastar
Step 6 On the Overview tab page, query the overview information about the filtered call records and
select a call record.
The overview information includes the access time, access cell, release time, release cell, IMSI,
IMEI, and service duration. For details about parameters, see 15.7.2 Parameters for Querying
GSM/UMTS Complaint Analysis Support Results.
l
l
l
indicates that the call record in this line is abnormal.

indicates the cause type of this call in the navigation tree is Other and the exception
status is unknown.
indicates that the CHR in this line is a combined CHR.
The Nastar supports the combination of inter-BSC CHRs. If an inter-BSC handover occurs
during a call, the Nastar combines the records related to one call and displays a combined
CHR in the overview table. You can double-click a combined CHR to open the CHR list tab
page corresponding to the combined CHR and query detailed information. The tab page is
named IMSI***_Serial number, where *** refers to the IMSI number.
You can click any line in the list and press Ctrl+F to search for and locate a call record.
Step 7 In the detailed call report table of a complaint subscriber on the right of the window, query the
details of all the filtered call records. The details include information about the subscriber, call
access or call release, and handover.
Step 8 On the Signaling Procedure Before Call Release tab page, query the detailed signaling
procedure before call release for the selected call record.
l Signaling information table: contains all signaling transmitted between NEs during a call.
Information in this table is displayed synchronously with the signaling procedure chart.
l Signaling procedure chart: shows the signaling interaction between NEs during a call. This
chart is displayed synchronously with the information in the signaling information table.
l If you double-click a record in the signaling procedure table or a signaling record in the
signaling procedure chart, the Information dialog box is displayed. Detailed signaling
information is displayed in a navigation tree, which contains the meanings of fields
represented by specific bytes. In addition, the Nastar automatically parses the enumerated
values or variant values represented by fields in a message according to protocols.
For details about the signaling procedure chart of the GSM network, see Description of the
Signaling Procedure Before Call Release Tab Page. For details about the signaling procedure
chart of the UMTS network, see Description of the Signaling Procedure Before Call Release
Tab Page.
Step 9 On the Measurement Information tab page, query the detailed measurement information
before call release for the selected call record and the change trend chart.
l Detailed measurement information table: contains detailed information about measurement
reports (MRs) before call release.
l KPI change trend chart: shows the change trends of TA, DLRxLevel, DLRxQuality/Level,
ULRxQuality/Level, and MS/BTS Power.
For details about parameters and the change trend chart of the GSM network, see Description
of the Measurement Information Tab Page. For details about parameters and the change trend
chart of the UMTS network, see Description of the Measurement Information Tab Page.
Step 10 Optional: Query the complaint analysis support results on the GIS window.
Issue 01 (2011-08-15)

413
Nastar
Click
in the upper left of
the Nastar client window to open the Display the Nastar Service based on longitude and
latitude window.
l The node corresponding to the selected theme is added to the navigation tree on the left of
the GIS window. The naming convention of the theme node is Network system_Task
name. The second-level node is the task name, and the three-level node is the KPI name,
such as the access and release cell.
If multiple complaint analysis support result windows related to one network system are
opened at the same time, the GIS window can synchronously display information of one
analysis result window. Only one theme node is displayed in the navigation tree on the
left of the GIS window and corresponds to the complaint analysis support results related
If a combined complaint analysis support result windows is displayed as one network
system, the GIS window can display information of the combined analysis result window
under the node of the network system.
If the complaint analysis support result window that is synchronously displayed with the
GIS window is closed, the theme node corresponding to the complaint analysis support
task is automatically deleted from the navigation tree on the left of the GIS window, and
the rendering layer corresponding to the complaint analysis support results is also
l When you open the GIS window initially, the access and release cells of all the call records
are displayed under the root node in the complaint analysis support result window by default.
Switch to one node on the left tree of the complaint analysis support result window, the
GIS window can synchronously display the access and release cell information of the
related node.
If cells whose engineering parameters are not imported exist, a message is displayed on
the right of the window.
----End
Follow-up Procedure
Export query results. You can right-click in the result list and then choose Save As from the
shortcut menu to save the current query results as a .xml, .txt, .xls, or .xlsx file.
15.5 Exporting GSM/UMTS Complaint Analysis Support

Reports
This section describes how to export GSM/UMTS complaint analysis support reports. You can
export the queried complaint analysis support results as .xls or .xlsx files as required. The
exported analysis results help you determine the network location where the problem occurs and
the possible causes.
Prerequisite
l
You have queried GSM/UMTS complaint analysis support results. For details, see 15.4
Querying GSM/UMTS Complaint Analysis Support Results.
Issue 01 (2011-08-15)

414
Nastar
Procedure
l
Export a complaint analysis support overview report.

NOTE
An exported complaint analysis support overview report contains the following three result files in
the default .xlsx format:
l Aggregation result file for complaint analysis support summary in the overview table. The file
naming convention is Overview table_Summary.xlsx.
l Statistical result file obtained by the aggregation mode "IMSI-Cause type" in the overview
navigation tree. The file naming convention is Overview tree_IMSI-Cause type.xlsx.
l Statistical result file obtained by the aggregation mode "Cause type-IMSI" in the overview
navigation tree. The file naming convention is Overview navigation tree_Cause typeIMSI.xlsx.
1.
In the GSM Complaint Analysis Support or UMTS Complaint Analysis

Support window, click
2.
. The Save dialog box is displayed.
Set the file name and specify the save path and file type. Then, click Save.
The progress of an export task is displayed in the Exported File List dialog box. You
can perform other operations during the execution of the export task.
Only one export task can be executed at a time on one client. If more than one
export tasks are created, other tasks are in the waiting state and can be executed
only after the running task is executed completely or canceled.
on the right of the progress bar to cancel an export task in the
You can click
waiting or running state so that the task is terminated and deleted from the task
on the right of the progress bar to delete an export task in
list. You can click
the completed state so that the task is deleted from the task list.
You can click
on the right of the progress bar to view detailed information
about an export task in the completed state.
information about export tasks (including the number of completed tasks, the
number of running tasks, the number of waiting tasks, and the number of failed
on the upper right of the Analysis Task
tasks) in
Management window. You can also click any icon to open the Exported File
List dialog box to view detailed task information.
Export a complaint analysis support data report.

NOTE
An exported complaint analysis support data report contains the following three result files in the
default .xlsx format:
l Aggregation result file for complaint analysis support summary in the overview table. The file
naming convention is Overview table_Summary.xlsx.
l File containing detailed information about GSM complaint call records. The file naming
convention is Information table_Details_GSM.xlsx.
l File containing detailed information about UMTS complaint call records. The file naming
convention is Information table_Details_UMTS.xlsx.
1.
In the GSM Complaint Analysis Support or UMTS Complaint Analysis

Support window, click
2.
Issue 01 (2011-08-15)
. The Save dialog box is displayed.
Set the file name and specify the save path and file type. Then, click Save.
415
Nastar
The progress of an export task is displayed in the Exported File List dialog box.
You can perform other operations during the execution of the export task.
Only one export task can be executed at a time on one client. If more than one
export tasks are created, other tasks are in the waiting state and can be executed
only after the running task is executed completely or canceled.
on the right of the progress bar to cancel an export task in
You can click
the waiting or running state so that the task is terminated and deleted from the
task list. You can click
on the right of the progress bar to delete an export
task in the completed state so that the task is deleted from the task list.
on the right of the progress bar to view detailed information
You can click
about an export task in the completed state.
information about export tasks (including the number of completed tasks, the
number of running tasks, the number of waiting tasks, and the number of failed
on the upper right of the Analysis Task
tasks) in
Management window. You can also click any icon to open the Exported File
List dialog box to view detailed task information.
The exported data contains the following:
Subscriber information, call access information, call release information, and
handover information in GSM networks
Subscriber information, access/release information, CS service information, PS
service information, and handover information in UMTS networks
You can also right-click a call record in the complaint analysis support overview table and
choose Export Complaint Analysis Support Data Report from the shortcut menu to
export a complaint analysis support data report for the call record.
----End
15.6 Technical Specifications for GSM/UMTS Complaint

Analysis Support
This section describes the technical specifications for GSM/UMTS complaint analysis support.
The technical specifications of GSM/UMTS complaint analysis support is included in GSM
complaint analysis support or UMTS complaint analysis support.
Issue 01 (2011-08-15)
Item

<= 2,000 subscribers
<= 5
<= Past 7 days
<= 15 minutes

(all the themes)
<= 200

416
Nastar
Item

<= 200
15.7 Reference to the GSM/UMTS Complaint Analysis

Support Interface
This section describes the interface for GSM/UMTS complaint analysis support and the relevant
GSM/UMTS complaint analysis support.
15.7.1 Parameters for Creating and Modifying GSM/UMTS

Complaint Analysis Support Tasks
This section describes the parameters for creating and modifying GSM/UMTS complaint
analysis support tasks. You can refer to this description when creating and modifying a GSM/
UMTS complaint analysis support task.

Parameter
Description
Task Name

"
l Case sensitive
Task Type
Remarks

Value range:
Issue 01 (2011-08-15)
Parameter
Description
Task Type
time.
417
Nastar
Parameter
Description
Time Range
analyzed.

Parameter
Description
Analysis Type
Choose the GSM/UMTS complaint analysis support.
Filter NEs
Choose the NEs to be analyzed.
Filter User
The filtering condition can be IMSI or Peer No..
15.7.2 Parameters for Querying GSM/UMTS Complaint Analysis

Support Results
This section describes the parameters for querying GSM/UMTS complaint analysis support
results. You can refer to the description when querying GSM/UMTS complaint analysis support
results.
Summary
NOTE
This section only describes the parameters of the summary table. If you want to query other parameters, refer
to Parameters for Querying GSM Complaint Analysis Support Results and 12.7.4 Parameters for Querying
Paramet
er
Range
Un
it
Description
Serial
Number
(0, 2 to the
power 31 - 1)
N/
A
Indicates the serial number of a CHR.This uniquely

identifies a CHR.
Combined CHRs share one serial number. A CHR that is
not combined corresponds to one serial number.
Combine
d
Combined
Empty
N/
A
Indicates whether a CHR is combined.

The Nastar supports the combination of inter-RAT CHRs.
If a yellow icon is displayed in the column, the CHR is
combined.
Abnorma
l
Issue 01 (2011-08-15)
Abnormal
Empty
N/
A
Indicates whether a CHR is abnormal.

If a red exclamation mark is displayed in the column, the
CHR is abnormal.

418
Nastar
Paramet
er
Range
Un
it
Description
Abnorma
l Cause
RRC access
failure
N/
A
Indicates the cause of an exception according to the

abnormal release cause and MRs before call release.
N/
A
Indicates the network that a call accesses.
Abnormal
RRC release
CS service
access failure
CS service
call drop
PS service
access failure
PS service
call drop
Network
GSM
UMTS
Issue 01 (2011-08-15)

419
Nastar
Paramet
er
Range
Un
it
Description
GSM:
N/
A
Indicates the signaling access type.
Non-short
message of
originated
call
Short
message of
originated
call
Terminated
call
Call
reestablishm
ent
Emergency
call
Location
update
IMSI detach
Incoming
BSC
handover
Non-short
message of
terminated
call
Short
message of
terminated
call
Normal
location
update
Periodical
location
update
IMSI attach
UMTS:
Intra-RAT
static
incoming
migration
Intra-RAT
hard
handover
Issue 01 (2011-08-15)

420
Nastar
Paramet
er
Range
Un
it
Description
N/
A
Indicates the requested service type.
associated
incoming
migration
Intra-RAT
CCH
migration
Inter-RAT
incoming
handover
Normal RRC
setup
(without
DRD)
Normal RRC
setup (with
DRD)
Requeste
d Service
Type
GSM: not
involved
UMTS:
CS AMR
CS VP
CS other
PS general
PS CMB
PS HSDPA
PS HSUAP
PS
HSDPA_HS
UPA
Issue 01 (2011-08-15)
Access
Time
N/A
N/
A
Indicates the access time of a call, that is, signaling access

time.
Access
Cell
N/A
N/
A
Indicates the cell where a call is initiated. The cell

information carried in the ** signaling.
Release
Time
N/A
N/
A
Indicates the release time of a call, that is, signaling release

time.
Release
Cell
N/A
N/
A
Indicates the cell where a call is released. The cell

information carried in the ** signaling.
IMSI
N/A
N/
A


421
Nastar
Paramet
er
Range
Un
it
Description
IMEI
N/A
N/
A

(IMEI) of a UE.
Peer
MSISDN
N/A
N/
A
Indicates the MSISDN of the peer UE. This parameter is

valid for only voice services.
Duration
N/A
Sec
ond

GSM:
Duration = RF CHANNEL RELEASE - CHANNEL
REQUIRED
UMTS:
Duration = RRC CONN SETUP REQ (or RELOC REQ)
- RRC CONNECTION RELEASE
Service
Duration
N/A
Sec
ond

GSM:
Service duration = DisConnect - Connect Acknowledge
UMTS:
Service duration = Radio Access Bearer Assignment
Response - IU REL CMD (or RB REL SUCC)
Issue 01 (2011-08-15)
Call
Setup
Result
N/A
N/
A
Indicates the call setup result generated in a GSM network

during the GSM/UMTS complaint analysis support.
Call
Resease
Result
N/A
N/
A
Indicates the call completion result generated in a GSM

network during GSM/UMTS complaint analysis support.
Access
failure
cause
N/A
N/
A
Indicates the cause of a call access failure.
IU
release
cause
N/A
N/
A
Indicates the cause of a call release from the Iu interface.
RRC
abnormal
release
cause
N/A
N/
A
Indicates the cause of an abnormal RRC release.
Cause for
CS RAB
Setup or
Release
Failure
N/A
N/
A
Indicates the cause of a CS RAB setup failure or release

failure.

422
Nastar
Issue 01 (2011-08-15)
Paramet
er
Range
Un
it
Description
Cause for
PS RAB
Setup or
Release
Failure
N/A
N/
A
Indicates the cause of a PS RAB setup failure or release

failure.

423

Nastar Network Optimization User Guide (UMTS) - (V600R009 - 01) (PDF) - en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nastar Network Optimization User Guide (UMTS) - (V600R009 - 01) (PDF) - en

Uploaded by

Copyright:

Available Formats

Nastar

Network Optimization User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Issue Draft C (2011-06-30)

Issue Draft B (2011-05-31)

Huawei Proprietary and Confidential

About This Document

Issue Draft A (2011-04-30)

Huawei Proprietary and Confidential

About This Document

7 UMTS/GSM Neighboring Cell Analysis

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Huawei Proprietary and Confidential

About This Document

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

2 Configuring OSSs and NE Information....................................................................................8

3 Collecting Basic Data..................................................................................................................19

Huawei Proprietary and Confidential

3.8.1 Interface Description: GIS.......................................................................................................................39

4 Subscribing to UMTS Data Sources........................................................................................44

5 UMTS Coverage Analysis..........................................................................................................56

6 UMTS Intra-Frequency Neighboring Cell Analysis............................................................84

Huawei Proprietary and Confidential

7 UMTS/GSM Neighboring Cell Analysis..............................................................................120

8 UMTS Pilot Pollution Analysis..............................................................................................159

Huawei Proprietary and Confidential

9 UMTS Uplink Interference Analysis.....................................................................................186

10 UMTS Terminal Analysis......................................................................................................210

11 UMTS VIP Analysis................................................................................................................247

Huawei Proprietary and Confidential

11.4.3 Checking the Integrity of VIP Analysis Data......................................................................................267

12 UMTS Complaint Analysis Support...................................................................................302

13 UMTS Cell Performance Analysis.......................................................................................343

Huawei Proprietary and Confidential

13.8.1 Interface Description: UMTS Cell Performance Analysis..................................................................366