Network Optimization User Guide
(GSM)
Issue 06
Date 2012-08-31
Copyright © Huawei Technologies Co., Ltd. 2012. 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 a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial BaseBantian, Longgang Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
About This Document
Purpose
This section describes how to perform GSM network optimization on the Nastar. Through this function, you can perform various theme analysis functions on the Nastar, such as MR analysis, frequency analysis, neighboring cell analysis, uplink interference analysis, GSM/UMTS neighboring cell analysis, VIP analysis, complaint analysis support, cell performance analysis, terminal inventory analysis, and network geographic analysis. This helps to quickly locate network problems.
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 06 (2012-08-31)
This is the sixth formal release.
Issue 05 (2012-06-25)
This is the fifth formal release.
Issue 04 (2012-05-08)
Issue 03 (2012-03-15)
This is the third formal release.
Issue 02 (2011-11-11)
This is the second formal release.
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 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 coverage analysis data to locate network problems.
4 Subscribing to GSM Data Sources
This section describes how to enable data source switches by using the data source subscription function before performing various Global System for Mobile Communications (GSM) 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.
This section describes the MML commands involved when the Nastar implements the GSM data source subscription function or delivers E2E tasks. For details about the MML commands, see the Nastar Data Source Subscription MML Command List Overview of GSM.
6 GSM MR Analysis
The GSM MR analysis function enables you to obtain GSM measurement report (MR) analysis data, create GSM MR analysis tasks, query GSM MR analysis results, and export GSM MR analysis reports from the Nastar. Through this function, the Nastar directly displays radio link information and provides analysis of and suggestions on wireless network problems for quickly locating problems.
7 GSM Neighboring Cell Analysis
The GSM neighboring cell analysis function enables you to obtain GSM neighboring cell analysis data, create GSM neighboring cell analysis tasks, query and export GSM neighboring cell analysis results, query and export possible GSM neighboring cell analysis results, query analysis results of GSM intra-frequency neighboring cells, and query analysis results of GSM co-BCCH and co-BSIC cells. The Nastar supports the analysis of defined and undefined GSM neighboring cells. By using this function, you can identify and handle the problems of redundant or missing neighboring cell configuration of a cell. Through this function, the Nastar directly displays the required information, helping you solve network quality problems that are caused by the redundant or missing neighboring cell configuration.
8 GSM/UMTS Neighboring Cell Analysis
The GSM/UMTS neighboring cell analysis function enables you to obtain GSM/UMTS neighboring cell analysis data, create GSM/UMTS neighboring cell analysis tasks, query GSM/ UMTS neighboring cell analysis results, and export GSM/UMTS neighboring cell analysis results from the Nastar. The Nastar supports the function of identifying redundant and missing inter-RAT neighboring cells. This helps to solve the network quality problems caused by redundant and missing neighboring cell configuration.
9 GSM Frequency Analysis
The GSM frequency analysis function enables you to obtain GSM frequency analysis data, create GSM frequency analysis tasks, query and export GSM frequency analysis results, and query and export GSM frequency optimization results. The Nastar provides the interference matrix analysis function and frequency interference matrix analysis function based on Measurement Reports (MRs) to assist you in adjusting the frequency setting. In addition, you can plan a frequency optimization scheme based on frequency interference matrix and judge the usability of the scheme based on frequency optimization results. You are advised to perform neighboring cell analysis before starting frequency analysis. This helps to improve the accuracy of neighboring cell identification and enable the Nastar to generate a correct interference model.
10 GSM Uplink Interference Analysis
The GSM uplink interference analysis function enables you to obtain GSM uplink interference analysis data, create GSM uplink interference analysis tasks, and query GSM uplink interference analysis reports. By analyzing uplink level of cells, the Nastar displays the signal strength of the measurement ARFCNs of some cells in the analysis results, helping you select appropriate ARFCNs according to the actual situation.
11 GSM Terminal Inventory Analysis
This section describes the GSM terminal inventory analysis tasks, including the management of terminal Information and terminal inventory analysis tasks and the query and export of terminal inventory 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 GSM 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.
12 GSM VIP Analysis
The GSM VIP analysis function enables you to obtain GSM VIP analysis data, create GSM VIP analysis tasks, and query GSM VIP analysis results 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.This function can be used to quickly locate and resolve problems. Normally there is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used during the
troubleshooting. However, this function provides an anonymous data processing method. You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected.
13 GSM Complaint Analysis Support
The GSM complaint analysis support function enables you to create complaint analysis support tasks, query complaint analysis support results, and export complaint analysis support reports from the Nastar. After receiving a subscriber complaint, the Nastar can quickly searches for all call records of the complaint subscriber in a problem cell based on the known problem cell and International Mobile Subscriber Identity (IMSI) of the complaint subscriber, and called number of the complaint subscriber. Through the analysis of causes of exceptions such as access failure, handover failure, and abnormal call drop, the Nastar helps you locate and solve complaint problems. Normally there is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used during the troubleshooting. However, this function provides an anonymous data processing method. You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected.
14 GSM Cell Performance Analysis
The GSM cell performance analysis function enables you to obtain GSM cell performance analysis data, create GSM cell performance analysis tasks, query GSM cell performance analysis results, and export GSM cell performance analysis reports from the Nastar. By providing call data of abnormal users in problem cells, the Nastar assists you in analyzing the root cause of abnormal calls. This helps to provide better services and improve user satisfaction. This function can be used to quickly locate and resolve problems. Normally there is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used during the troubleshooting. However, this function provides an anonymous data processing method. You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected.
15 GSM Network Geographic Analysis
GSM network geographic analysis involves obtaining GSM network geographic analysis data, creating a GSM network geographic analysis task, viewing the GSM network geographic analysis result. 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.
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.
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.
Convention Description
{ 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.
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.
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.
Action Description
Click Select and release the primary mouse button without moving
Action Description
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
Contents
About This Document...ii
1 Overview...1
1.1 Position of the Nastar on the Network...2
1.2 Analysis Data Sources (GSM)...3
1.3 Network Optimization Process...5
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...12
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...20
3.1 Introduction to GSM Basic Data...22
3.2 Collecting Configuration Data...24
3.3 Importing Configuration Data...25
3.4 Importing Engineering Parameters...27
3.5 Checking Engineering Parameters and Configuration Data...29
3.6 GIS Management...31
3.6.1 Viewing Analysis Results by Using the Google Earth...31
3.6.2 Querying Analysis Results Through the GIS Window...33
3.7 Managing the GIS Window...34
3.7.1 Importing a Map...34
3.7.2 Converting the Map File Format...35
3.7.3 Loading Site Information...36
3.7.4 Filtering Cells...37
3.7.5 Searching Cells...38
3.7.6 Moving/Zooming In On/Zooming Out On/Refreshing/Fully Displaying a Map...39
3.7.7 Measuring Distance on the Map...39
3.7.8 Saving the Map Display Effect...40
3.8.1 Interface Description: GIS...40
3.8.2 Parameters for Creating or Modifying a Data Collection Task...41
3.9 How Do I Deal With the GIS Ineffectiveness?...44
4 Subscribing to GSM Data Sources...45
4.1 Basic Knowledge of GSM Data Source Subscription...46
4.2 Setting Data Source Switches (As an Administrator User)...49
4.3 Querying the Data Source Switch Status on the Live Network (As a Common User)...51
4.4 GUI Description: Subscribing to GSM Data Source...52
5 Appendix: MML Command Reference...57
6 GSM MR Analysis...58
6.1 Basic Knowledge of GSM MR Analysis...60
6.1.1 GSM MR Analysis...60
6.1.2 TopN KPIs...61
6.1.3 GSM MR Theme Analysis...63
6.2 Process of GSM MR Analysis...65
6.3 Obtaining GSM MR Analysis Data...67
6.3.1 Creating a GSM Performance Data Collection Task...68
6.3.2 Creating a Data Import Task...70
6.3.3 Checking the Integrity of Analysis Data...74
6.4 Creating GSM MR Analysis Tasks...77
6.5 Querying GSM MR Overview Analysis Results...79
6.5.1 Querying GSM BSC Analysis Results...80
6.5.2 Querying GSM Cell Group Analysis Results...82
6.5.3 Querying GSM TopN TRX Analysis Results...85
6.5.4 Querying GSM MR Filter Condition Analysis Reports...86
6.6 Querying GSM MR Results...87
6.7 Comparing GSM MR Analysis Results...88
6.8 Exporting GSM MR Overview Reports...90
6.9 Technical Specifications for GSM MR Analysis...91
6.10 Reference for the GSM MR Analysis GUI...92
6.10.1 Interface Description: GSM MR Analysis...92
6.10.2 Parameters for Creating or Modifying a Data Collection Task...95
6.10.3 Parameters for Creating and Modifying GSM MR Analysis Tasks...98
6.10.4 Parameters for Querying GBSC Reports...102
6.10.5 Parameters for Querying the GSM Cell Group Reports...105
6.10.6 Parameters for Querying the GSM TopN TRX Reports...109
6.10.7 Parameters for Querying the GSM MR Filter Condition Analysis Reports...112
6.10.8 Parameters for Querying the MR Analysis Results of GSM Cells...114
6.10.9 Parameters for Comparing GSM MR Analysis Results...117
7 GSM Neighboring Cell Analysis...120
7.1.1 GSM Neighboring Cell Analysis Function...122
7.1.2 Algorithms for GSM Neighboring Cell Analysis...124
7.2 Process of GSM Neighboring Cell Analysis...125
7.3 Obtaining GSM Neighboring Cell Analysis Data...127
7.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks...127
7.3.2 Creating a GSM Measure Task File for Neighbor Cell Data Collection Task...130
7.3.3 Creating a GSM Performance Data Collection Task...131
7.3.4 Creating a Data Import Task...133
7.3.5 Checking the Integrity of Analysis Data...137
7.4 Creating GSM Neighboring Cell Analysis Task...140
7.5 Querying GSM Neighboring Cell Analysis Results...143
7.6 Querying GSM Possible Neighboring Cell Analysis Results...144
7.7 Querying GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis Results...146
7.8 Querying GSM Intra-Frequency Neighboring Cell Analysis Results...146
7.9 Exporting GSM Neighboring Cell Analysis Reports...147
7.10 Exporting GSM Possible Neighboring Cell Analysis Reports...150
7.11 Technical Specifications for GSM Neighboring Cell Analysis...151
7.12 Reference for the GSM Neighboring Cell Analysis GUI...151
7.12.1 Interface Description: GSM Neighboring Cell Analysis...152
7.12.2 Interface Description: GSM Possible Neighboring Cell Analysis...153
7.12.3 Parameters of GSM Neighboring Cell E2E Tasks...154
7.12.4 Parameters for Creating or Modifying a Data Collection Task...157
7.12.5 Parameters for Creating and Modifying GSM Neighboring Cell Analysis Tasks...159
7.12.6 Parameters for Querying GSM Neighboring Cell Analysis Results...161
7.12.7 Parameters for Querying GSM Possible Neighboring Cell Analysis Results...171
7.12.8 Parameters for Querying GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis Results...177
7.12.9 Parameters for Querying GSM Intra-frequency Neighboring Cell Analysis Results...179
8 GSM/UMTS Neighboring Cell Analysis...183
8.1 Basic Knowledge of GSM/UMTS Neighboring Cell Analysis...185
8.1.1 GSM/UMTS Neighboring Cell Analysis...185
8.1.2 Algorithms for GSM/UMTS Neighboring Cell Analysis...186
8.2 Process of GSM/UMTS Neighboring Cell Analysis...187
8.3 Obtaining GSM/UMTS Neighboring Cell Analysis Data...189
8.3.1 Creating GSM/UMTS Neighboring Cell Measurement Data E2E Tasks...189
8.3.2 Creating a GSM Performance Data Collection Task...191
8.3.3 Creating a Data Import Task...192
8.3.4 Checking the Integrity of Analysis Data...197
8.4 Creating GSM/UMTS Neighboring Cell Analysis Tasks...200
8.5 Querying GSM/UMTS Neighboring Cell Analysis Results...202
8.6 Querying GSM/UMTS Possible Neighboring Cell Analysis Results...204
8.7 Exporting GSM/UMTS Neighboring Cell Analysis Reports...205
8.9 Technical Specifications for GSM/UMTS Neighboring Cell Analysis...207
8.10 Reference to the GSM/UMTS Neighboring Cell Analysis Interface...208
8.10.1 Interface Description: GSM/UMTS Neighboring Cell Analysis...208
8.10.2 Interface Description: GSM/UMTS Possible Neighboring Cell Analysis...209
8.10.3 Parameters of GSM/UMTS Neighboring Cell Data E2E Tasks...210
8.10.4 Parameters for Creating or Modifying a Data Collection Task...211
8.10.5 Parameters for Creating and Modifying GSM/UMTS Neighboring Cell Analysis Tasks...213
8.10.6 Parameters for Querying the Analysis Reports of GSM/UMTS Neighboring Cells...215
8.10.7 Parameters for Querying the Analysis Reports of GSM/UMTS Possible Neighboring Cells...217
9 GSM Frequency Analysis...222
9.1 Basic Knowledge of GSM Frequency Analysis...224
9.1.1 GSM Frequency Analysis Function...224
9.1.2 Introduction to Process of GSM Frequency Analysis...225
9.1.3 Process of GSM Frequency Optimization...226
9.1.4 GSM ARFCN Spacing Rules...227
9.2 Process of GSM Frequency Analysis...231
9.3 Obtaining GSM Frequency Analysis Data...234
9.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks...234
9.3.2 Creating a GSM Measure Task File for Neighbor Cell Data Collection Task...236
9.3.3 Creating a GSM Performance Data Collection Task...238
9.3.4 Creating a Data Import Task...239
9.3.5 Checking the Integrity of Analysis Data...244
9.4 Creating GSM Frequency Analysis Tasks...247
9.5 Querying GSM Frequency Analysis Results...249
9.6 Querying GSM Frequency Optimization Results...250
9.7 Exporting GSM Frequency Analysis Reports...253
9.8 Exporting GSM Frequency Optimization Reports...255
9.9 Technical Specifications for GSM Frequency Analysis...256
9.10 Reference for the GSM Frequency Analysis GUI...257
9.10.1 Interface Description: GSM Frequency Analysis...257
9.10.2 Interface Description: GSM Frequency Optimization...260
9.10.3 Parameters of GSM Neighboring Cell E2E Tasks...262
9.10.4 Parameters for Creating or Modifying a Data Collection Task...264
9.10.5 Parameters for Creating and Modifying GSM Frequency Analysis Tasks...266
9.10.6 Parameters for Querying GSM Frequency Analysis Results...268
9.10.7 Parameters for Querying GSM Frequency Optimization Results...278
9.11 How Do I Handle the Failure to Execute a GSM Frequency Analysis Task Whose Progress Bar Stays at 13% or 75% But the Task Status is Displayed As Finished?...281
10 GSM Uplink Interference Analysis...283
10.1 Basic Knowledge of GSM Uplink Interference Analysis...285
10.2 Process of GSM Uplink Interference Analysis...285
10.3.1 Creating GSM Uplink Interference Analysis Data E2E Tasks...287
10.3.2 Creating a Data Import Task...289
10.3.3 Checking the Integrity of Analysis Data...293
10.4 Creating GSM Uplink Interference Analysis Tasks...296
10.5 Querying GSM Uplink Interference Analysis Results...298
10.6 Technical Specifications for GSM Uplink Interference Analysis...300
10.7 Reference for the GSM Uplink Interference Analysis GUI...300
10.7.1 Interface Description: GSM Uplink Interference Analysis...300
10.7.2 Parameters of GSM Uplink Interference Analysis E2E Tasks...301
10.7.3 Parameters for Creating and Modifying GSM Uplink Interference Analysis Tasks...303
10.7.4 Parameters for Querying GSM Uplink Interference Analysis Results...305
11 GSM Terminal Inventory Analysis...309
11.1 Basic Knowledge of GSM Terminal Inventory Analysis...311
11.2 GSM Terminal Inventory Analysis Process...311
11.3 Managing Terminal Information...313
11.4 Obtaining GSM Terminal Inventory Analysis Data...318
11.4.1 Creating GSM Terminal Inventory Data Analysis E2E Tasks...318
11.4.2 Creating a Data Import Task...320
11.4.3 Checking the Integrity of Analysis Data...324
11.5 Creating a GSM Terminal Inventory Analysis Task...327
11.6 Querying GSM Terminal Inventory Analysis Results...328
11.7 Exporting GSM Terminal Inventory Analysis Reports...330
11.8 Technical Specifications for GSM Terminal Inventory Analysis...330
11.9 Reference to the GSM Terminal Inventory Analysis Interface...331
11.9.1 Interface Description: GSM Terminal Inventory Analysis...331
11.9.2 Parameters for Creating and Modifying the Terminal Type...333
11.9.3 Parameters for GSM Terminal Inventory Analysis Data E2E Tasks...334
11.9.4 Parameters for Creating or Modifying GSM Terminal Inventory Analysis Tasks...335
11.9.5 Parameters for Querying GSM Terminal Inventory Analysis Results...336
12 GSM VIP Analysis...350
12.1 Basic Knowledge of GSM VIP Analysis...352
12.1.1 GSM VIP Analysis Function...352
12.1.2 Authority Policies for GSM VIP Analysis...353
12.2 Process of GSM VIP Analysis...358
12.3 Managing GSM VIP groups...360
12.4 Obtaining GSM VIP Analysis Data...364
12.4.1 Creating GSM VIP Analysis Data E2E Tasks...364
12.4.2 Creating a Data Import Task...366
12.4.3 Checking the Integrity of VIP Analysis Data...370
12.5 Setting a Mailbox for Sending Analysis Reports...371
12.6 Creating GSM VIP Analysis Tasks...372
12.8 Querying GSM VIP Trend Analysis Results...376
12.9 Technical Specifications for GSM VIP Analysis...379
12.10 Reference to the GSM VIP Analysis Interface...379
12.10.1 Interface Description: GSM VIP Analysis...380
12.10.2 Interface for GSM VIP Trend Analysis...381
12.10.3 Parameters for Creating and Modifying GSM VIP Subscribers/VIP Groups...383
12.10.4 Parameters of GSM VIP Analysis Data E2E Tasks...385
12.10.5 Parameters for Creating and Modifying GSM VIP Analysis Tasks...386
12.10.6 Parameters for Querying GSM VIP Analysis Results...389
12.10.7 Parameters for Setting the Mailbox of Analysis Results...397
13 GSM Complaint Analysis Support...398
13.1 Basic Knowledge of GSM Complaint Analysis Support...400
13.1.1 GSM Complaint Analysis Support Function...400
13.1.2 Authority Policies for GSM Complaint Analysis Support...401
13.2 Process of GSM Complaint Analysis Support...404
13.3 Creating GSM Complaint Analysis Support Tasks...405
13.4 Querying GSM Complaint Analysis Support Results...408
13.5 Exporting GSM Complaint Analysis Support Reports...411
13.6 Technical Specifications for GSM Complaint Analysis Support...412
13.7 Reference to the GSM Complaint Analysis Support Interface...412
13.7.1 Interface Description: GSM Complaint Analysis Support...413
13.7.2 Interface for Signaling Procedure Before Call Release and Measurement Information in the GSM Complaint Analysis Support Window...414
13.7.3 Parameters for Creating and Modifying GSM Complaint Analysis Support Tasks...418
13.7.4 Parameters for Querying GSM Complaint Analysis Support Results...419
14 GSM Cell Performance Analysis...430
14.1 Basic Knowledge of GSM Cell Performance Analysis...432
14.2 Process of GSM Cell Performance Analysis...432
14.3 Obtaining GSM Cell Performance Analysis Data...434
14.3.1 Creating GSM Cell Performance Data Analysis E2E Tasks...434
14.3.2 Creating a Data Import Task...436
14.3.3 Checking the Integrity of Analysis Data...440
14.4 Creating GSM Cell Performance Analysis Tasks...443
14.5 Querying GSM Cell Performance Analysis Results...445
14.6 Exporting GSM Cell Performance Analysis Reports...447
14.7 Technical Specifications for GSM Cell Performance Analysis...448
14.8 Reference to the GSM Cell Performance Analysis Interface...449
14.8.1 Interface Description: GSM Cell Performance Analysis...449
14.8.2 Parameters for GSM Cell Performance Analysis Data E2E Tasks...450
14.8.3 Parameters for Creating or Modifying GSM Cell Performance Analysis Tasks...451
14.8.4 Parameters for Querying GSM Cell Performance Analysis Results...452
15.1 Basic Knowledge of GSM Network Geographic Analysis...458
15.2 GSM network geographic Analysis Process...458
15.3 Obtaining GSM Network Geographic Analysis Data...460
15.3.1 Import Property Matrix...460
15.3.2 Creating GSM Network Geographic Analysis Data E2E Tasks...462
15.3.3 Creating a Data Import Task...463
15.3.4 Checking the Integrity of Analysis Data...468
15.4 Creating GSM Network Geographic Analysis Tasks...471
15.5 Querying GSM Network Geographic Analysis Results...473
15.6 Technical Specifications for GSM Network Geographic Observation...476
15.7 Reference to the GSM Network Geographic Analysis Interface...476
15.7.1 Interface Description: GSM Network Geographic Analysis...476
15.7.2 Parameters for Creating GSM Network Geographic Analysis Data E2E Tasks...477
15.7.3 Parameters for Creating and Modifying GSM Network Geographic Analysis Tasks...479
1
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 (GSM)
The Nastar mainly uses the following three types of data during the analysis of GSM networks: GSM configuration data, GSM engineering parameters, data related to Nastar analysis, and GSM property matrix.
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.
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 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.
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.
M2000 The M2000, an element management system, is a centralized
management platform developed by Huawei. The M2000 uniformly manages the NEs on a mobile network.
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 (GSM)
The Nastar mainly uses the following three types of data during the analysis of GSM networks: GSM configuration data, GSM engineering parameters, data related to Nastar analysis, and GSM property matrix.
Figure 1-2 Sources of the Nastar analysis data (GSM)
Table 1-2 describes the sources of the Nastar analysis data.
Table 1-2 Sources of the Nastar analysis data (GSM)
Analysis Data Source Function
GSM configuration data Basic information for network optimization, used for the Nastar to correctly retrieve data of each cell from data sources.
GSM 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
GSM performance data Obtained from the M2000 and used for GSM MR analysis, GSM frequency analysis, GSM
neighboring cell analysis, and GSM/UMTS neighboring cell analysis.
GSM/UMTS neighboring cell analysis data is retrieved from GSM performance data. GSM uplink interference
data
Obtained from the M2000 and used for GSM uplink interference analysis.
Analysis Data Source Function GSM neighboring cell
measurement data
Obtained from the M2000 and used for GSM frequency analysis and GSM neighboring cell analysis. GSM MR data GSM network geographic analysis data
Obtained from the SAU and used for GSM network geographic analysis.
Call History Record (CHR) data GSM VIP analysis data
Obtained from the SAU and used for GSM VIP analysis.
GSM cell performan ce analysis data
Obtained from the SAU and used for GSM cell performance analysis. GSM complaint analysis support data
Obtained from the SAU and used for GSM complaint analysis support.
GSM network geographic analysis data
Obtained from the SAU and used for GSM network geographic analysis.
GSM terminal inventory analysis data
Obtained from the SAU and used for GSM terminal inventory analysis.
GSM property matrix Obtained from the network planning tools (such
as the GENEX U-Net) and used for GSM network geographic 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.
Figure 1-3 Process of optimizing the Nastar
Table 1-3 describes each phase.
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.
Phase Step Description 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
2
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.
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.
l 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.
Prerequisites
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.
CAUTION
l If OSS Type, OSS User Name, OSS Password and OSS Server Port are not set correctly, E2E tasks will fail to start and the Nastar system will fail to collect data. l OSS User Name and OSS Password must be the same as the user name and password
set for the Nastar system on the M2000. For details, see How to Create a Nastar User on the M2000?.
l For the OSS Type parameter:
l If the OSS version is M2000V200R011C00CP2302 or a later patch version, set OSS Type to M2000V200R011C00CP2302.
l If the OSS version is M2000V200R011C01CP2302 or a later patch version, set OSS Type to M2000V200R011C01CP2302.
l If the OSS version is another version of M2000V200R011, set OSS Type to M2000V200R011.
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.
l You can click , , , and to select NEs. A single arrow
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.
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.
Related References
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.
Prerequisites
l You have logged in to the Nastar client. l You are authorized to manage NE groups.
Context
Custom NE group files in .csv, .xls, and .xlsx formats are supported.
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 2.4.3 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.
NOTE
The function of importing user-defined NE groups is unavailable for the LTE system.
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
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 2.4.3 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.
If you need to... Then...
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.
Related References
2.4.3 Parameters for Creating and Modifying Custom NE Groups
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
No. Name Description
(1) Navigation tree Indicates that the objects in the navigation tree are sorted by OSS.
(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: M2000V200R008, M2000V200R009, M2000V200R010, M2000V200R011,
M2000V200R011C00CP2302, M2000V200R011C01CP2302, M2000V200R012, OMC920V400R001, OMC920V400R005, OMC920V400R006 and OMC920V400R007
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.
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. This parameter cannot be null.
OSS Server Port Indicates the port number of the OSS server. This parameter cannot be null.
Parameter Description
Description It is the description of an OSS. Value range:
l A maximum of 128 characters
l The following characters are not allowed: ~ ! @ # $ % ^ & * + = < > ?
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.
This parameter cannot be null.
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.
This parameter cannot be null.
FTP User Name Indicates the user name used to log in to the FTP server. Value range:
l A maximum of 25 characters
l The following characters are not allowed: ~ ! @ # $ % ^ & * + = < > ?
l Case sensitive
This parameter cannot be null.
FTP Password Indicates the password used to log in to the FTP server. This parameter cannot be null.
FTP Transfer Mode Indicates the transfer mode set for the FTP server. The parameter value can be Passive Mode or Active Mode.
Parameter Description
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 A maximum of 25 characters
l The following characters are not allowed: ~ ! @ # $ % ^ & * + = < > ?
l Case sensitive
FTP password Indicates the password of the FTP service in the M2000 SLS system.
Related Tasks
2.2 Creating OSSs and the Managed NEs
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 A maximum of 128 characters
l Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `:"<>? l Unique and not null
l Case sensitive NE Group Type
(Only CDMA and LTE network need to set the parameter)
Indicates the type of the NE group.
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 A maximum of 250 characters
l Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `:"<>?
Related Tasks
3
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 coverage analysis data to locate network problems.
3.1 Introduction to GSM Basic Data
This section describes the GSM basic data used for analysis. The GSM basic data consists of engineering parameters, configuration data, and 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 performance analysis.
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.
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.
3.9 How Do I Deal With the GIS Ineffectiveness?
This section describes the cause of the problem that the GIS function is ineffective after you login in to the Nastar client.
3.1 Introduction to GSM Basic Data
This section describes the GSM basic data used for analysis. The GSM basic data consists of engineering parameters, configuration data, and 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.
GSM Engineering Parameters
GSM engineering parameters contain the basic information for GSM network optimization, including longitudes and altitudes of sites, and azimuths and downtilts of antennas. Table 3-1
shows GSM engineering parameters supported by the Nastar. Table 3-1 GSM engineering parameters
Parameter Description Value Range Optional/
Mandatory BSC Name Indicates the name of a
BSC.
String, a maximum of 50 characters
Mandatory BTS Name Indicates the name of a
BTS.
String, a maximum of 64 characters
Mandatory Cell Name Indicates the name of a
cell.
String, a maximum of 64 characters
MCC Indicates the mobile
country code.
l Integer l Value range:
[000,999]
Mandatory
MNC Indicates the mobile
network code.
l Integer l Value range:
[00,99]
Mandatory
LAC Indicates the location
area code of a cell. l Integerl Value range: [1,65533], 65535
Parameter Description Value Range Optional/ Mandatory
CI Indicates the cell
identification.
l Integer l Value range:
[0,65535]
Mandatory
BCCH Indicates the broadcast
control channel.
l Integer l Value range:
[0,1023]
Mandatory
BCC Indicates the color code
of a BTS.
l Integer
l Value range: [0,7]
Mandatory
NCC Indicates the network
color code.
l Integer
l Value range: [0,7]
Mandatory
Longitude Indicates the longitude where a cell is located, for example, 116.389722.
Value range:
[-180.00000,180.000 00]
Mandatory
Latitude Indicates the latitude where a cell is located, for example, 39.952778.
Value range:
[-90.00000,90.00000]
Mandatory
Azimuth Indicates the azimuth of an antenna.
Value range: [0.00,360.00]
Mandatory Outdoor Cell Indicates whether the cell
is an outdoor cell.
l 0: No, indoor cell l 1: Yes, outdoor
cell
Optional
Direct Cell Indicates whether the cell is a directional cell.
l 0: No l 1: Yes
Optional
TCH Indicates the traffic
channel. TCH ARFCNs must be separated by spaces. Optional
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.
l 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.
l To perform a network 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.
Prerequisites
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).
l You have logged in to the Nastar client.
Context
l A configuration data collection task is a user-defined scheduled task.
l 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.
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 double-click 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...
If... Then...
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. 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
Related References
3.8.2 Parameters for Creating or Modifying a Data Collection Task
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.
