iManager Nastar Network Optimization User Guide (GSM)(V600R009_06)(PDF)-En

iManager NastarV600R009

Network Optimization User Guide(GSM)

Issue 06

Date 2012-08-31

HUAWEI TECHNOLOGIES CO., LTD.

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 writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 06 (2012-08-31) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis section describes how to perform GSM network optimization on the Nastar. Through thisfunction, you can perform various theme analysis functions on the Nastar, such as MR analysis,frequency analysis, neighboring cell analysis, uplink interference analysis, GSM/UMTSneighboring cell analysis, VIP analysis, complaint analysis support, cell performance analysis,terminal inventory analysis, and network geographic analysis. This helps to quickly locatenetwork problems.

Product VersionThe products described in this guide are as follows:

Product Name Product Version

Nastar V600R009

Intended AudienceThis 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)This is the fourth formal release.

iManager NastarNetwork Optimization User Guide (GSM) About This Document


ii

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.

Organization1 Overview

The Nastar is deployed on the EMS side of an operator's network. The Nastar collects requiredanalysis data from NEs through the EMS data center, and provides theme analysis for networkoptimization.

2 Configuring OSSs and NE Information

Before enabling the Nastar to collect data from an OSS, you must configure the OSS and NEinformation. After you configure information including the IP address of the OSS and softwareversion, the Nastar obtains the NE list managed by the OSS and analyzes the NEs in the NE listbased on the configured OSS information.

3 Collecting Basic Data

The basic data that needs to be collected by the Nastar contains configuration data, engineeringparameters, and map data. The Nastar collects and imports basic data into the database so thatyou can perform various theme analysis tasks based on other analysis data such as VIP analysisdata 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 subscriptionfunction before performing various Global System for Mobile Communications (GSM) themeanalysis functions. After required data source switches are enabled, the Nastar can collectrequired data from network elements (NEs). This function is the prerequisite for all Nastar themeanalysis functions.

5 Appendix: MML Command Reference



iii

This section describes the MML commands involved when the Nastar implements the GSM datasource subscription function or delivers E2E tasks. For details about the MML commands, seethe 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) analysisdata, create GSM MR analysis tasks, query GSM MR analysis results, and export GSM MRanalysis reports from the Nastar. Through this function, the Nastar directly displays radio linkinformation and provides analysis of and suggestions on wireless network problems for quicklylocating problems.

7 GSM Neighboring Cell Analysis

The GSM neighboring cell analysis function enables you to obtain GSM neighboring cellanalysis data, create GSM neighboring cell analysis tasks, query and export GSM neighboringcell analysis results, query and export possible GSM neighboring cell analysis results, queryanalysis results of GSM intra-frequency neighboring cells, and query analysis results of GSMco-BCCH and co-BSIC cells. The Nastar supports the analysis of defined and undefined GSMneighboring cells. By using this function, you can identify and handle the problems of redundantor missing neighboring cell configuration of a cell. Through this function, the Nastar directlydisplays the required information, helping you solve network quality problems that are causedby 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/UMTSneighboring cell analysis data, create GSM/UMTS neighboring cell analysis tasks, query GSM/UMTS neighboring cell analysis results, and export GSM/UMTS neighboring cell analysisresults from the Nastar. The Nastar supports the function of identifying redundant and missinginter-RAT neighboring cells. This helps to solve the network quality problems caused byredundant and missing neighboring cell configuration.

9 GSM Frequency Analysis

The GSM frequency analysis function enables you to obtain GSM frequency analysis data, createGSM frequency analysis tasks, query and export GSM frequency analysis results, and query andexport GSM frequency optimization results. The Nastar provides the interference matrix analysisfunction 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 frequencyoptimization scheme based on frequency interference matrix and judge the usability of thescheme based on frequency optimization results. You are advised to perform neighboring cellanalysis before starting frequency analysis. This helps to improve the accuracy of neighboringcell 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 interferenceanalysis data, create GSM uplink interference analysis tasks, and query GSM uplink interferenceanalysis reports. By analyzing uplink level of cells, the Nastar displays the signal strength of themeasurement ARFCNs of some cells in the analysis results, helping you select appropriateARFCNs according to the actual situation.

11 GSM Terminal Inventory Analysis

This section describes the GSM terminal inventory analysis tasks, including the management ofterminal Information and terminal inventory analysis tasks and the query and export of terminalinventory analysis reports. The system analyzes the KPIs in the call records of terminal users.



iv

This function helps operators identify the terminals with poor performance in the GSM network,therefore encouraging terminal manufacturers to improve the terminals with poor performanceand guide subscribers to purchase terminals with good performance. In this case, subscriberscan 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 VIPanalysis tasks, and query GSM VIP analysis results from the Nastar. By monitoring the KPIsrelated to the quality of service (QoS) of VIP subscribers, the Nastar helps you identify and solvethe network problems that may cause VIP complaints so that the service quality of VIPsubscribers is ensured and the satisfaction of VIP subscribers is improved.This function can beused to quickly locate and resolve problems. Normally there is no way to avoid that some userdata such as International Mobile Subscriber Identity (IMSI) will be used during thetroubleshooting. However, this function provides an anonymous data processing method. Youare obligated to take considerable measures, in compliance with the laws of the countriesconcerned and the user privacy policies of your company, to ensure that the personal data ofusers is fully protected.

13 GSM Complaint Analysis Support

The GSM complaint analysis support function enables you to create complaint analysis supporttasks, query complaint analysis support results, and export complaint analysis support reportsfrom the Nastar. After receiving a subscriber complaint, the Nastar can quickly searches for allcall records of the complaint subscriber in a problem cell based on the known problem cell andInternational Mobile Subscriber Identity (IMSI) of the complaint subscriber, and called numberof 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 complaintproblems. Normally there is no way to avoid that some user data such as International MobileSubscriber Identity (IMSI) will be used during the troubleshooting. However, this functionprovides an anonymous data processing method. You are obligated to take considerablemeasures, in compliance with the laws of the countries concerned and the user privacy policiesof 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 performanceanalysis data, create GSM cell performance analysis tasks, query GSM cell performance analysisresults, and export GSM cell performance analysis reports from the Nastar. By providing calldata of abnormal users in problem cells, the Nastar assists you in analyzing the root cause ofabnormal calls. This helps to provide better services and improve user satisfaction. This functioncan be used to quickly locate and resolve problems. Normally there is no way to avoid that someuser data such as International Mobile Subscriber Identity (IMSI) will be used during thetroubleshooting. However, this function provides an anonymous data processing method. Youare obligated to take considerable measures, in compliance with the laws of the countriesconcerned and the user privacy policies of your company, to ensure that the personal data ofusers 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 geographicanalysis result. The Nastar displays the relevant information on the map based on the datacollected for the entire network to show the distribution of network coverage, traffic, andabnormal events in an intuitive and comprehensive manner.



v

ConventionsSymbol Conventions

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

Symbol Description

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

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

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

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

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

General Conventions

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

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

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

Command Conventions

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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



vi


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

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

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

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

GUI Conventions

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


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

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

Keyboard Operations

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

Format Description

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

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

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

Mouse Operations

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

Action Description

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



vii

Action Description

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

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



viii

Contents

About This Document.....................................................................................................................ii

1 Overview.........................................................................................................................................11.1 Position of the Nastar on the Network................................................................................................................21.2 Analysis Data Sources (GSM)............................................................................................................................31.3 Network Optimization Process...........................................................................................................................5

2 Configuring OSSs and NE Information....................................................................................82.1 Basic Knowledge of OSS Management.............................................................................................................92.2 Creating OSSs and the Managed NEs................................................................................................................92.3 Creating Custom NE Groups............................................................................................................................122.4 Reference for the OSS Management GUI........................................................................................................14

2.4.1 Interface Description: OSS Management................................................................................................142.4.2 Parameters for Setting the Object Attributes of OSS Management........................................................152.4.3 Parameters for Creating and Modifying Custom NE Groups..................................................................18

3 Collecting Basic Data..................................................................................................................203.1 Introduction to GSM Basic Data......................................................................................................................223.2 Collecting Configuration Data..........................................................................................................................243.3 Importing Configuration Data..........................................................................................................................253.4 Importing Engineering Parameters...................................................................................................................273.5 Checking Engineering Parameters and Configuration Data.............................................................................293.6 GIS Management..............................................................................................................................................31

3.6.1 Viewing Analysis Results by Using the Google Earth............................................................................313.6.2 Querying Analysis Results Through the GIS Window...........................................................................33

3.7 Managing the GIS Window..............................................................................................................................343.7.1 Importing a Map......................................................................................................................................343.7.2 Converting the Map File Format.............................................................................................................353.7.3 Loading Site Information.........................................................................................................................363.7.4 Filtering Cells..........................................................................................................................................373.7.5 Searching Cells........................................................................................................................................383.7.6 Moving/Zooming In On/Zooming Out On/Refreshing/Fully Displaying a Map....................................393.7.7 Measuring Distance on the Map..............................................................................................................393.7.8 Saving the Map Display Effect................................................................................................................40

3.8 Reference to the Basic Data Collection Interface.............................................................................................40

iManager NastarNetwork Optimization User Guide (GSM) Contents


ix

3.8.1 Interface Description: GIS.......................................................................................................................403.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...........................................................................................454.1 Basic Knowledge of GSM Data Source Subscription......................................................................................464.2 Setting Data Source Switches (As an Administrator User)..............................................................................494.3 Querying the Data Source Switch Status on the Live Network (As a Common User)....................................514.4 GUI Description: Subscribing to GSM Data Source........................................................................................52

5 Appendix: MML Command Reference...................................................................................57

6 GSM MR Analysis......................................................................................................................586.1 Basic Knowledge of GSM MR Analysis..........................................................................................................60

6.1.1 GSM MR Analysis..................................................................................................................................606.1.2 TopN KPIs...............................................................................................................................................616.1.3 GSM MR Theme Analysis......................................................................................................................63

6.2 Process of GSM MR Analysis..........................................................................................................................656.3 Obtaining GSM MR Analysis Data..................................................................................................................67

6.3.1 Creating a GSM Performance Data Collection Task...............................................................................686.3.2 Creating a Data Import Task...................................................................................................................706.3.3 Checking the Integrity of Analysis Data.................................................................................................74

6.4 Creating GSM MR Analysis Tasks..................................................................................................................776.5 Querying GSM MR Overview Analysis Results..............................................................................................79

6.5.1 Querying GSM BSC Analysis Results....................................................................................................806.5.2 Querying GSM Cell Group Analysis Results..........................................................................................826.5.3 Querying GSM TopN TRX Analysis Results.........................................................................................856.5.4 Querying GSM MR Filter Condition Analysis Reports..........................................................................86

6.6 Querying GSM MR Results.............................................................................................................................876.7 Comparing GSM MR Analysis Results............................................................................................................886.8 Exporting GSM MR Overview Reports...........................................................................................................906.9 Technical Specifications for GSM MR Analysis.............................................................................................916.10 Reference for the GSM MR Analysis GUI....................................................................................................92

6.10.1 Interface Description: GSM MR Analysis............................................................................................926.10.2 Parameters for Creating or Modifying a Data Collection Task.............................................................956.10.3 Parameters for Creating and Modifying GSM MR Analysis Tasks......................................................986.10.4 Parameters for Querying GBSC Reports.............................................................................................1026.10.5 Parameters for Querying the GSM Cell Group Reports......................................................................1056.10.6 Parameters for Querying the GSM TopN TRX Reports.....................................................................1096.10.7 Parameters for Querying the GSM MR Filter Condition Analysis Reports........................................1126.10.8 Parameters for Querying the MR Analysis Results of GSM Cells......................................................1146.10.9 Parameters for Comparing GSM MR Analysis Results......................................................................117

7 GSM Neighboring Cell Analysis...........................................................................................1207.1 Basic Knowledge of GSM Neighboring Cell Analysis..................................................................................122



x

7.1.1 GSM Neighboring Cell Analysis Function...........................................................................................1227.1.2 Algorithms for GSM Neighboring Cell Analysis..................................................................................124

7.2 Process of GSM Neighboring Cell Analysis..................................................................................................1257.3 Obtaining GSM Neighboring Cell Analysis Data..........................................................................................127

7.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks.........................................................1277.3.2 Creating a GSM Measure Task File for Neighbor Cell Data Collection Task......................................1307.3.3 Creating a GSM Performance Data Collection Task.............................................................................1317.3.4 Creating a Data Import Task.................................................................................................................1337.3.5 Checking the Integrity of Analysis Data...............................................................................................137

7.4 Creating GSM Neighboring Cell Analysis Task............................................................................................1407.5 Querying GSM Neighboring Cell Analysis Results.......................................................................................1437.6 Querying GSM Possible Neighboring Cell Analysis Results........................................................................1447.7 Querying GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis Results..............................................1467.8 Querying GSM Intra-Frequency Neighboring Cell Analysis Results............................................................1467.9 Exporting GSM Neighboring Cell Analysis Reports.....................................................................................1477.10 Exporting GSM Possible Neighboring Cell Analysis Reports.....................................................................1507.11 Technical Specifications for GSM Neighboring Cell Analysis....................................................................1517.12 Reference for the GSM Neighboring Cell Analysis GUI.............................................................................151

7.12.1 Interface Description: GSM Neighboring Cell Analysis.....................................................................1527.12.2 Interface Description: GSM Possible Neighboring Cell Analysis......................................................1537.12.3 Parameters of GSM Neighboring Cell E2E Tasks..............................................................................1547.12.4 Parameters for Creating or Modifying a Data Collection Task...........................................................1577.12.5 Parameters for Creating and Modifying GSM Neighboring Cell Analysis Tasks..............................1597.12.6 Parameters for Querying GSM Neighboring Cell Analysis Results...................................................1617.12.7 Parameters for Querying GSM Possible Neighboring Cell Analysis Results.....................................1717.12.8 Parameters for Querying GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis Results...........1777.12.9 Parameters for Querying GSM Intra-frequency Neighboring Cell Analysis Results..........................179

8 GSM/UMTS Neighboring Cell Analysis..............................................................................1838.1 Basic Knowledge of GSM/UMTS Neighboring Cell Analysis......................................................................185

8.1.1 GSM/UMTS Neighboring Cell Analysis..............................................................................................1858.1.2 Algorithms for GSM/UMTS Neighboring Cell Analysis......................................................................186

8.2 Process of GSM/UMTS Neighboring Cell Analysis......................................................................................1878.3 Obtaining GSM/UMTS Neighboring Cell Analysis Data..............................................................................189

8.3.1 Creating GSM/UMTS Neighboring Cell Measurement Data E2E Tasks.............................................1898.3.2 Creating a GSM Performance Data Collection Task.............................................................................1918.3.3 Creating a Data Import Task.................................................................................................................1928.3.4 Checking the Integrity of Analysis Data...............................................................................................197

8.4 Creating GSM/UMTS Neighboring Cell Analysis Tasks..............................................................................2008.5 Querying GSM/UMTS Neighboring Cell Analysis Results...........................................................................2028.6 Querying GSM/UMTS Possible Neighboring Cell Analysis Results............................................................2048.7 Exporting GSM/UMTS Neighboring Cell Analysis Reports.........................................................................2058.8 Exporting GSM/UMTS Possible Neighboring Cell Analysis Reports...........................................................207



xi

8.9 Technical Specifications for GSM/UMTS Neighboring Cell Analysis.........................................................2078.10 Reference to the GSM/UMTS Neighboring Cell Analysis Interface...........................................................208

8.10.1 Interface Description: GSM/UMTS Neighboring Cell Analysis........................................................2088.10.2 Interface Description: GSM/UMTS Possible Neighboring Cell Analysis..........................................2098.10.3 Parameters of GSM/UMTS Neighboring Cell Data E2E Tasks..........................................................2108.10.4 Parameters for Creating or Modifying a Data Collection Task...........................................................2118.10.5 Parameters for Creating and Modifying GSM/UMTS Neighboring Cell Analysis Tasks..................2138.10.6 Parameters for Querying the Analysis Reports of GSM/UMTS Neighboring Cells...........................2158.10.7 Parameters for Querying the Analysis Reports of GSM/UMTS Possible Neighboring Cells............217

9 GSM Frequency Analysis........................................................................................................2229.1 Basic Knowledge of GSM Frequency Analysis.............................................................................................224

9.1.1 GSM Frequency Analysis Function......................................................................................................2249.1.2 Introduction to Process of GSM Frequency Analysis...........................................................................2259.1.3 Process of GSM Frequency Optimization.............................................................................................2269.1.4 GSM ARFCN Spacing Rules................................................................................................................227

9.2 Process of GSM Frequency Analysis.............................................................................................................2319.3 Obtaining GSM Frequency Analysis Data.....................................................................................................234

9.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks.........................................................2349.3.2 Creating a GSM Measure Task File for Neighbor Cell Data Collection Task......................................2369.3.3 Creating a GSM Performance Data Collection Task.............................................................................2389.3.4 Creating a Data Import Task.................................................................................................................2399.3.5 Checking the Integrity of Analysis Data...............................................................................................244

9.4 Creating GSM Frequency Analysis Tasks......................................................................................................2479.5 Querying GSM Frequency Analysis Results..................................................................................................2499.6 Querying GSM Frequency Optimization Results...........................................................................................2509.7 Exporting GSM Frequency Analysis Reports................................................................................................2539.8 Exporting GSM Frequency Optimization Reports.........................................................................................2559.9 Technical Specifications for GSM Frequency Analysis.................................................................................2569.10 Reference for the GSM Frequency Analysis GUI........................................................................................257

9.10.1 Interface Description: GSM Frequency Analysis................................................................................2579.10.2 Interface Description: GSM Frequency Optimization.........................................................................2609.10.3 Parameters of GSM Neighboring Cell E2E Tasks..............................................................................2629.10.4 Parameters for Creating or Modifying a Data Collection Task...........................................................2649.10.5 Parameters for Creating and Modifying GSM Frequency Analysis Tasks.........................................2669.10.6 Parameters for Querying GSM Frequency Analysis Results..............................................................2689.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.....................................................................................28310.1 Basic Knowledge of GSM Uplink Interference Analysis.............................................................................28510.2 Process of GSM Uplink Interference Analysis.............................................................................................28510.3 Obtaining GSM Uplink Interference Analysis Data.....................................................................................287



xii

10.3.1 Creating GSM Uplink Interference Analysis Data E2E Tasks............................................................28710.3.2 Creating a Data Import Task...............................................................................................................28910.3.3 Checking the Integrity of Analysis Data.............................................................................................293

10.4 Creating GSM Uplink Interference Analysis Tasks.....................................................................................29610.5 Querying GSM Uplink Interference Analysis Results.................................................................................29810.6 Technical Specifications for GSM Uplink Interference Analysis................................................................30010.7 Reference for the GSM Uplink Interference Analysis GUI.........................................................................300

10.7.1 Interface Description: GSM Uplink Interference Analysis.................................................................30010.7.2 Parameters of GSM Uplink Interference Analysis E2E Tasks............................................................30110.7.3 Parameters for Creating and Modifying GSM Uplink Interference Analysis Tasks...........................30310.7.4 Parameters for Querying GSM Uplink Interference Analysis Results................................................305

11 GSM Terminal Inventory Analysis.....................................................................................30911.1 Basic Knowledge of GSM Terminal Inventory Analysis.............................................................................31111.2 GSM Terminal Inventory Analysis Process.................................................................................................31111.3 Managing Terminal Information..................................................................................................................31311.4 Obtaining GSM Terminal Inventory Analysis Data.....................................................................................318

11.4.1 Creating GSM Terminal Inventory Data Analysis E2E Tasks............................................................31811.4.2 Creating a Data Import Task...............................................................................................................32011.4.3 Checking the Integrity of Analysis Data.............................................................................................324

11.5 Creating a GSM Terminal Inventory Analysis Task....................................................................................32711.6 Querying GSM Terminal Inventory Analysis Results.................................................................................32811.7 Exporting GSM Terminal Inventory Analysis Reports................................................................................33011.8 Technical Specifications for GSM Terminal Inventory Analysis................................................................33011.9 Reference to the GSM Terminal Inventory Analysis Interface....................................................................331

11.9.1 Interface Description: GSM Terminal Inventory Analysis.................................................................33111.9.2 Parameters for Creating and Modifying the Terminal Type...............................................................33311.9.3 Parameters for GSM Terminal Inventory Analysis Data E2E Tasks..................................................33411.9.4 Parameters for Creating or Modifying GSM Terminal Inventory Analysis Tasks.............................33511.9.5 Parameters for Querying GSM Terminal Inventory Analysis Results................................................336

12 GSM VIP Analysis..................................................................................................................35012.1 Basic Knowledge of GSM VIP Analysis.....................................................................................................352

12.1.1 GSM VIP Analysis Function...............................................................................................................35212.1.2 Authority Policies for GSM VIP Analysis..........................................................................................353

12.2 Process of GSM VIP Analysis......................................................................................................................35812.3 Managing GSM VIP groups.........................................................................................................................36012.4 Obtaining GSM VIP Analysis Data..............................................................................................................364

12.4.1 Creating GSM VIP Analysis Data E2E Tasks.....................................................................................36412.4.2 Creating a Data Import Task...............................................................................................................36612.4.3 Checking the Integrity of VIP Analysis Data......................................................................................370

12.5 Setting a Mailbox for Sending Analysis Reports.........................................................................................37112.6 Creating GSM VIP Analysis Tasks..............................................................................................................37212.7 Querying GSM VIP Analysis Results..........................................................................................................374



xiii

12.8 Querying GSM VIP Trend Analysis Results................................................................................................37612.9 Technical Specifications for GSM VIP Analysis.........................................................................................37912.10 Reference to the GSM VIP Analysis Interface...........................................................................................379

12.10.1 Interface Description: GSM VIP Analysis........................................................................................38012.10.2 Interface for GSM VIP Trend Analysis.............................................................................................38112.10.3 Parameters for Creating and Modifying GSM VIP Subscribers/VIP Groups...................................38312.10.4 Parameters of GSM VIP Analysis Data E2E Tasks..........................................................................38512.10.5 Parameters for Creating and Modifying GSM VIP Analysis Tasks..................................................38612.10.6 Parameters for Querying GSM VIP Analysis Results.......................................................................38912.10.7 Parameters for Setting the Mailbox of Analysis Results...................................................................397

13 GSM Complaint Analysis Support......................................................................................39813.1 Basic Knowledge of GSM Complaint Analysis Support.............................................................................400

13.1.1 GSM Complaint Analysis Support Function.......................................................................................40013.1.2 Authority Policies for GSM Complaint Analysis Support..................................................................401

13.2 Process of GSM Complaint Analysis Support.............................................................................................40413.3 Creating GSM Complaint Analysis Support Tasks......................................................................................40513.4 Querying GSM Complaint Analysis Support Results..................................................................................40813.5 Exporting GSM Complaint Analysis Support Reports.................................................................................41113.6 Technical Specifications for GSM Complaint Analysis Support.................................................................41213.7 Reference to the GSM Complaint Analysis Support Interface.....................................................................412

13.7.1 Interface Description: GSM Complaint Analysis Support..................................................................41313.7.2 Interface for Signaling Procedure Before Call Release and Measurement Information in the GSMComplaint Analysis Support Window............................................................................................................41413.7.3 Parameters for Creating and Modifying GSM Complaint Analysis Support Tasks............................41813.7.4 Parameters for Querying GSM Complaint Analysis Support Results.................................................419

14 GSM Cell Performance Analysis..........................................................................................43014.1 Basic Knowledge of GSM Cell Performance Analysis................................................................................43214.2 Process of GSM Cell Performance Analysis................................................................................................43214.3 Obtaining GSM Cell Performance Analysis Data........................................................................................434

14.3.1 Creating GSM Cell Performance Data Analysis E2E Tasks...............................................................43414.3.2 Creating a Data Import Task...............................................................................................................43614.3.3 Checking the Integrity of Analysis Data.............................................................................................440

14.4 Creating GSM Cell Performance Analysis Tasks........................................................................................44314.5 Querying GSM Cell Performance Analysis Results.....................................................................................44514.6 Exporting GSM Cell Performance Analysis Reports...................................................................................44714.7 Technical Specifications for GSM Cell Performance Analysis...................................................................44814.8 Reference to the GSM Cell Performance Analysis Interface.......................................................................449

14.8.1 Interface Description: GSM Cell Performance Analysis.....................................................................44914.8.2 Parameters for GSM Cell Performance Analysis Data E2E Tasks.....................................................45014.8.3 Parameters for Creating or Modifying GSM Cell Performance Analysis Tasks.................................45114.8.4 Parameters for Querying GSM Cell Performance Analysis Results...................................................452

15 GSM Network Geographic Analysis...................................................................................456



xiv

15.1 Basic Knowledge of GSM Network Geographic Analysis..........................................................................45815.2 GSM network geographic Analysis Process................................................................................................45815.3 Obtaining GSM Network Geographic Analysis Data..................................................................................460

15.3.1 Import Property Matrix........................................................................................................................46015.3.2 Creating GSM Network Geographic Analysis Data E2E Tasks.........................................................46215.3.3 Creating a Data Import Task...............................................................................................................46315.3.4 Checking the Integrity of Analysis Data.............................................................................................468

15.4 Creating GSM Network Geographic Analysis Tasks...................................................................................47115.5 Querying GSM Network Geographic Analysis Results...............................................................................47315.6 Technical Specifications for GSM Network Geographic Observation........................................................47615.7 Reference to the GSM Network Geographic Analysis Interface..................................................................476

15.7.1 Interface Description: GSM Network Geographic Analysis...............................................................47615.7.2 Parameters for Creating GSM Network Geographic Analysis Data E2E Tasks.................................47715.7.3 Parameters for Creating and Modifying GSM Network Geographic Analysis Tasks.........................47915.7.4 Parameters for Querying GSM Network Geographic Analysis Results..............................................481



xv

1 Overview

About This Chapter

The Nastar is deployed on the EMS side of an operator's network. The Nastar collects requiredanalysis data from NEs through the EMS data center, and provides theme analysis for networkoptimization.

1.1 Position of the Nastar on the NetworkThe Nastar is deployed on a distributed client/server (C/S) network and is connected to anelement 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 GSMproperty matrix.

1.3 Network Optimization ProcessThe optimization process of the Nastar consists of collection and check of basic data, networkevaluation, further optimization of each theme, and evaluation of optimization effect. All theoperations on the network must be recorded in details.

iManager NastarNetwork Optimization User Guide (GSM) 1 Overview


1

1.1 Position of the Nastar on the NetworkThe Nastar is deployed on a distributed client/server (C/S) network and is connected to anelement 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 networksegment.

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 platformdeveloped by Huawei. It helps you to perform performance analysisfor the radio network and perform network problem troubleshooting.



2

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 BTSsl Preprocessing raw data and saving the preprocessed datal Uploading the preprocessed dataIn a GSM, UMTS, or CDMA network, an SAU must be configuredfor the base station controller to preprocess the performance datarequired 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 centralizedmanagement platform developed by Huawei. The M2000 uniformlymanages the NEs on a mobile network.The M2000 is connected to the Nastar, and provides the Nastar withperformance data, configuration data, call history record (CHR)processed data, and measurement report (MR) preprocessed datathrough FTP.

Radio network Multiple radio networks are supported, including GSM, UMTS,CDMA, and LTE networks.

MME Mobility Management Entity (MME) provides data analysis functionfor 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 GSMproperty matrix.

Figure 1-2 shows the sources of the Nastar analysis data on the network.



3

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, usedfor the Nastar to correctly retrieve data of eachcell from data sources.

GSM engineering parameters Basic information for network optimization,including longitudes and altitudes of sites, andazimuths and down tilt angles of antennas.Used for displaying the analysis datageographically.

Data relatedto Nastaranalysis

GSM performance data Obtained from the M2000 and used for GSM MRanalysis, GSM frequency analysis, GSMneighboring cell analysis, and GSM/UMTSneighboring cell analysis.GSM/UMTS neighboring cell analysis data isretrieved from GSM performance data.

GSM uplink interferencedata

Obtained from the M2000 and used for GSMuplink interference analysis.



4

Analysis Data Source Function

GSM neighboring cellmeasurement data

Obtained from the M2000 and used for GSMfrequency analysis and GSM neighboring cellanalysis.

GSM MRdata

GSMnetworkgeographicanalysisdata

Obtained from the SAU and used for GSMnetwork geographic analysis.

CallHistoryRecord(CHR) data

GSM VIPanalysisdata

Obtained from the SAU and used for GSM VIPanalysis.

GSM cellperformance analysisdata

Obtained from the SAU and used for GSM cellperformance analysis.

GSMcomplaintanalysissupportdata

Obtained from the SAU and used for GSMcomplaint analysis support.

GSMnetworkgeographicanalysisdata

Obtained from the SAU and used for GSMnetwork geographic analysis.

GSMterminalinventoryanalysisdata

Obtained from the SAU and used for GSMterminal inventory analysis.

GSM property matrix Obtained from the network planning tools (suchas the GENEX U-Net) and used for GSM networkgeographic analysis.

1.3 Network Optimization ProcessThe optimization process of the Nastar consists of collection and check of basic data, networkevaluation, further optimization of each theme, and evaluation of optimization effect. All theoperations on the network must be recorded in details.

Figure 1-3 shows the process of optimizing the Nastar.



5

Figure 1-3 Process of optimizing the Nastar

Table 1-3 describes each phase.

Table 1-3 Description of each phase

Phase Step Description

Preparation

Collection andcheck of basic data

Basic data includes engineering parameters, configurationdata, 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 consistencybetween configuration data and engineering parameters inthe whole network and the integrity and accuracy ofengineering parameters.

Networkevaluation

The purpose of network evaluation is to learn the quality ofthe live network and main problematic cells and collect datafor future in-depth analysis of network quality during thecomparison of network quality at the network level.You can use other tools such as PRS to monitor and evaluatenetwork KPIs.



6

Phase Step Description

Optimization

Furtheroptimization ofeach theme

Use various performance analysis functions of the Nastar toperform further optimization of each theme. Theperformance analysis functions of the Nastar includes RFperformance optimization such as coverage analysis andsubscriber-based performance optimization such ascomplaint analysis support and VIP analysis.

Effectevaluation phase

Evaluation ofoptimization effect

Evaluate the effect of network optimization.



7

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 NEinformation. After you configure information including the IP address of the OSS and softwareversion, the Nastar obtains the NE list managed by the OSS and analyzes the NEs in the NE listbased on the configured OSS information.

2.1 Basic Knowledge of OSS ManagementThis section describes the basic knowledge about the Operations Support System (OSS)management functions. You should grasp the basic knowledge before performing managementoperations.

2.2 Creating OSSs and the Managed NEsThis section describes how to create OSSs. You can create an OSS to initialize the protocol ofthe interface between the Nastar and the EMS device so that the Nastar accesses the EMS devicethrough the interface to obtain the required data. In addition, you can set NEs managed by theOSS so that the Nastar collects required data from the selected NEs.

2.3 Creating Custom NE GroupsThis section describes how to create custom NE groups. The Nastar client provides the functionsof creating, modifying, deleting, importing, and exporting custom NE groups. You can addcertain NEs to an NE group so that the performance analysis can be performed for all the NEsin an NE group.

2.4 Reference for the OSS Management GUIThis section describes the parameters about the interface of OSS management and the parametersfor setting the object attributes of OSS management. You can refer to the description whenperforming the relevant operations on the interface.

iManager NastarNetwork Optimization User Guide (GSM) 2 Configuring OSSs and NE Information


8

2.1 Basic Knowledge of OSS ManagementThis section describes the basic knowledge about the Operations Support System (OSS)management functions. You should grasp the basic knowledge before performing managementoperations.

In the OSS management, objects represent the physical or logical entities on the network. Aphysical 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 beconnected with the Nastar. The Nastar collects the required data from a specified FTP serveraccording to the relevant attributes set in the OSS and saves the data as files in a specifiedpath on the Nastar server.

l NENEs are used to identify network devices, such as BTS and BSC.NEs can be classified intophysical 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. Thesubsystems such as centralized task management add objects to the GUI through the OSSmanagement subsystem.

The OSS management of the Nastar enables you to create and delete OSSs, view and modifyOSS attributes, and manage the information about NEs managed by the OSS.

2.2 Creating OSSs and the Managed NEsThis section describes how to create OSSs. You can create an OSS to initialize the protocol ofthe interface between the Nastar and the EMS device so that the Nastar accesses the EMS devicethrough the interface to obtain the required data. In addition, you can set NEs managed by theOSS so that the Nastar collects required data from the selected NEs.

PrerequisitesYou 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.



9

CAUTIONl 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 Useron 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.

CAUTIONThe parameters such as FTP Server Ip, FTP Server Port, FTP User Name, FTPPassword, FTP transfer mode, and FTP Protocol must be set correctly. Otherwise, theNastar 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 followingoperations to configure slave servers.The network scale is large when the M2000 in M2000 V200R008 or a later version isdeployed in SLS mode. Therefore, data required by the Nastar is distributed over differentservers. In this case, you need to create a master server and then create slave servers duringthe creation of an OSS.

a. Select a created OSS (serving as a master server) from the navigation tree in the leftpane, 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.



10

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 theNEs 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 arrowindicates that you can select one or multiple NEs. Double arrows indicate that you canselect 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 leftpane, the system remove the update automatically node under an NE type from theright pane automatically.

l If update automatically is displayed under the selected NE type in the right pane, thesystem automatically updates all NEs under the NE type every four hours according tothe actual network situation.

CAUTIONl 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 thosecharacters. 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 theNastar 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 OSSManagement window. Then, click Delete.

If data collection tasks have existed in the selected OSS, the systems prompts The OSShas been used in these Data Collection task, please delete them first:, You should deletethe data collect tasks first before you delete the OSS.

2. Click OK in the displayed dialog box.

Related References2.4.2 Parameters for Setting the Object Attributes of OSS Management



11

2.3 Creating Custom NE GroupsThis section describes how to create custom NE groups. The Nastar client provides the functionsof creating, modifying, deleting, importing, and exporting custom NE groups. You can addcertain NEs to an NE group so that the performance analysis can be performed for all the NEsin an NE group.

Prerequisitesl You have logged in to the Nastar client.l You are authorized to manage NE groups.

ContextCustom 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 theAnalysis 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 AnalysisTask 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 andlocate an object.

l For details about the parameters, see 2.4.3 Parameters for Creating and ModifyingCustom 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, orUMTS.



12

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 multiplesheets, 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, thesystem 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 youdefine NE group information.

3. Click Open.The Message indicates the quantities of the successful and unsuccessful imported NEgroup.

4. Click OK.

----End

Follow-up ProcedureIn the NE Group Management window, click the *** NE Group tab, and then select an NEgroup 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 orLTE.


Query and modify theproperties of a custom NEgroup

1. Click Modify.2. View the information about members of the custom NE

group.If the relevant parameters need to be modified, perform 3through 4.

3. Modify the relevant parameters.The objects and remarks of an NE groups can be modifiedbut the name of an NE group cannot be modified.For details about the parameters, see 2.4.3 Parameters forCreating and Modifying Custom NE Groups.

4. Click OK.NOTE

If the NE group is used by other tasks, the modification does notaffect the ongoing tasks. If the NE group is used by a periodictask, the related information is updated in the next period after themodification.

TIPWhen you need to modify the information about NE groups in batches,you can export the NE group information, make modifications, andthen import the NE group information again.



13


Delete a custom NE group. 1. Click Delete.2. Click OK in the displayed dialog box.

NOTEIf the NE group is used by other tasks, the modification does notaffect the ongoing tasks. If the NE group is used by a periodictask, the related information is updated in the next period after themodification.

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 pagecan be exported.

NOTEThe function of exporting user-defined NE group is unavailable forthe LTE system.

Related References2.4.3 Parameters for Creating and Modifying Custom NE Groups

2.4 Reference for the OSS Management GUIThis section describes the parameters about the interface of OSS management and the parametersfor setting the object attributes of OSS management. You can refer to the description whenperforming the relevant operations on the interface.

2.4.1 Interface Description: OSS ManagementThis 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 Figure2-1.



14

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 treeare sorted by OSS.

(2) Toolbar Provides the buttons for creating and deletingOSSs, 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 selectin the navigation tree.

(4) Area of FTP serverinformation

Displays the details of the FTP servercorresponding to the OSS that you select in thenavigation tree.

2.4.2 Parameters for Setting the Object Attributes of OSSManagement

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.



15

Parameters Related to the OSS AttributesParameter Description

OSS Name Indicates the name of an OSS to be created or modified.Value range:l A maximum of 60 charactersl The following characters are not allowed: ~ ! @ # $ % ^ & * +

= < > ?l Unique and cannot be nulll Case sensitive

OSS Type Indicates the type of the interface between the EMS and theNastar.Value range: M2000V200R008, M2000V200R009,M2000V200R010, M2000V200R011,M2000V200R011C00CP2302, M2000V200R011C01CP2302,M2000V200R012, OMC920V400R001, OMC920V400R005,OMC920V400R006 and OMC920V400R007When the Nastar collects data from the OSS, this interface definesthe relevant principles such as the path of the configuration datafiles and performance data files in the OSS and the naming rulesof the files. Thus, the Nastar can collect the required files from thepath specified by the OSS and saves the files in the specified pathon 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 ClusterOptional. The default value is Single/High Availability (HA).NOTE

If the network mode is Multi-server load sharing system (SLS)/ATAECluster, 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.



16

Parameter Description

Description It is the description of an OSS.Value range:l A maximum of 128 charactersl The following characters are not allowed: ~ ! @ # $ % ^ & * +

= < > ?l Case sensitive

Parameters Related to the FTP ServerParameter Description

FTP Server IP Indicates the IP address of the FTP server where the file to becollected is located.This parameter cannot be null.

Standby FTP Server IP Indicates the IP address of the standby server when the networkmode 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 parametercannot be null.

FTP Server Port Indicates the port number of the FTP server where the file to becollected is located.This parameter can be set to any integer from 1 to 65535. Thedefault 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 charactersl The following characters are not allowed: ~ ! @ # $ % ^ & * +

= < > ?l Case sensitiveThis 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 parametervalue can be Passive Mode or Active Mode.



17


FTP Protocol l SFTP: Indicates the encrypted FTP transfer, which requires thesupport from the FTP server.

l FTP: Indicates the non-encrypted FTP transfer, which is ageneral FTP mode.

Parameter Related to the slave server AttributesParameter Description

FTP server IP Indicates the IP address of the slave server in the M2000 SLSsystem.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 SLSsystem.Value range:l A maximum of 25 charactersl The following characters are not allowed: ~ ! @ # $ % ^ & * +

= < > ?l Case sensitive

FTP password Indicates the password of the FTP service in the M2000 SLSsystem.

Related Tasks2.2 Creating OSSs and the Managed NEs

2.4.3 Parameters for Creating and Modifying Custom NE GroupsThis section describes the parameters for creating and modifying custom NE groups. You canrefer to the parameter description when creating and modifying the custom NE groups.



18

Parameter DescriptionParameter Description

NE Group Name Indicates the name of the NE group, for example, Cell_1.Value range:l A maximum of 128 charactersl Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `:"<>?l Unique and not nulll Case sensitive

NE Group Type(Only CDMA and LTEnetwork need to set theparameter)

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 charactersl Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `:"<>?

Related Tasks2.3 Creating Custom NE Groups



19

3 Collecting Basic Data

About This Chapter

The basic data that needs to be collected by the Nastar contains configuration data, engineeringparameters, and map data. The Nastar collects and imports basic data into the database so thatyou can perform various theme analysis tasks based on other analysis data such as VIP analysisdata and coverage analysis data to locate network problems.

3.1 Introduction to GSM Basic DataThis section describes the GSM basic data used for analysis. The GSM basic data consists ofengineering parameters, configuration data, and map files.

3.2 Collecting Configuration DataThis section describes how to collect configuration data on the Nastar. The Nastar automaticallyand periodically obtains configuration data from a specified directory on the M2000 server andsaves the data on the Nastar server.

3.3 Importing Configuration DataThis section describes how to import configuration data. The Nastar automatically obtainsconfiguration data from a specified directory on the Nastar server periodically and then importthe 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 importtask.

3.4 Importing Engineering ParametersThis section describes how to import engineering parameters. You can import engineeringparameters into the Nastar database to provide a reference for certain algorithms related toperformance analysis.

3.5 Checking Engineering Parameters and Configuration DataThis section describes how to check engineering parameters and configuration data. Throughthis function, you can check whether the existing engineering parameter data is consistent withthe configuration data. If the check result is inconsistent, you can enable the Nastar tosynchronize the engineering parameter data with the configuration data to ensure dataconsistency.

3.6 GIS ManagementThe Nastar can geographically display the performance analysis results through either theGeographic Information System (GIS) window or Google Earth. You can view the Nastaranalysis result directly on the map, thus facilitating the service analysis.

iManager NastarNetwork Optimization User Guide (GSM) 3 Collecting Basic Data


20

3.7 Managing the GIS WindowYou can import the map files in .wor, .tab or .sxwu format and view the site information in theGIS window by using the engineering parameters. In addition, you can perform the followingoperations in the GIS window through the GIS toolbar, such as move/center/zoom in on/zoomout on a map and measure the distance between two points on the map.

3.8 Reference to the Basic Data Collection InterfaceThis section describes the interface for collecting basic data on the Nastar and the relevantparameters. You can refer to this section when you import configuration data, engineeringparameters, 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 youlogin in to the Nastar client.



21

3.1 Introduction to GSM Basic DataThis section describes the GSM basic data used for analysis. The GSM basic data consists ofengineering parameters, configuration data, and map files.

Map FilesMap files contain the geographical information of the area to be analyzed. Currently, the Nastarsupports map files in .wor, .tab, and .sxwu formats. If the PC is connected to the Internet, youcan view analysis results on the Google Earth.

NOTEYou can convert the map files in .wor or .tab formats to the map files in .sxwu format through the ConvertMap function of the Nastar.

Configuration DataConfiguration data contains the basic information for network optimization, which is used forthe Nastar to correctly retrieve data of each cell from data sources. The Nastar can obtainconfiguration data from the specified path on the M2000.

GSM Engineering ParametersGSM engineering parameters contain the basic information for GSM network optimization,including longitudes and altitudes of sites, and azimuths and downtilts of antennas. Table 3-1shows 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 aBSC.

String, a maximum of50 characters

Mandatory

BTS Name Indicates the name of aBTS.


Mandatory

Cell Name Indicates the name of acell.


MCC Indicates the mobilecountry code.

l Integerl Value range:

[000,999]

Mandatory

MNC Indicates the mobilenetwork code.


[00,99]

Mandatory

LAC Indicates the locationarea code of a cell.


[1,65533], 65535

Mandatory



22

Parameter Description Value Range Optional/Mandatory

CI Indicates the cellidentification.


[0,65535]

Mandatory

BCCH Indicates the broadcastcontrol channel.


[0,1023]

Mandatory

BCC Indicates the color codeof a BTS.

l Integerl Value range: [0,7]

Mandatory

NCC Indicates the networkcolor code.

l Integerl Value range: [0,7]

Mandatory

Longitude Indicates the longitudewhere a cell is located, forexample, 116.389722.

Value range:[-180.00000,180.00000]

Mandatory

Latitude Indicates the latitudewhere a cell is located, forexample, 39.952778.

Value range:[-90.00000,90.00000]

Mandatory

Azimuth Indicates the azimuth ofan antenna.

Value range:[0.00,360.00]

Mandatory

Outdoor Cell Indicates whether the cellis an outdoor cell.

l 0: No, indoor celll 1: Yes, outdoor

cell

Optional

Direct Cell Indicates whether the cellis a directional cell.

l 0: Nol 1: Yes

Optional

TCH Indicates the trafficchannel.

TCH ARFCNs mustbe separated byspaces.

Optional

Other Datal 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 thecorresponding IMSIs or the information about the called subscribers and the correspondingIMSIs.

l To perform a network geographic analysis task, you also need to obtain the property matrixinformation. Property matrix can be generated using a network planning simulation tool,such as GENEX U-Net.



23

3.2 Collecting Configuration DataThis section describes how to collect configuration data on the Nastar. The Nastar automaticallyand periodically obtains configuration data from a specified directory on the M2000 server andsaves the data on the Nastar server.

Prerequisitesl The configuration data is generated on the M2000. For details, refers to the Collecting and

Importing Basic Data > Collecting and Importing Configuration Data > Collectingand Importing Configuration Data (xml.gz Format) chapter in the NastarCommissioning Guide (HP).

l You have logged in to the Nastar client.

Contextl 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 thetask 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 ExecuteImmediately. 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.



24

If... Then...

Run Type is set to Period. a. Set the task execution period in PeriodSetting.NOTE

Performance data can be collected at an interval ofhalf 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 areautomatically selected. That is, data of all NEs will be periodically collected and savedas 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 theselected NE type node will be automatically selected. That is, data of all NEs under theselected NE type will be periodically collected and saved as a file in a specified path onthe Nastar.

l If Collect All NE and Collect By NE Type are not selected, you can type a keywordof NE name in Filter NE to search for the required NE object nodes in the NE objectnavigation tree. Alternatively, select certain NE object nodes directly in the NE objectnavigation tree. Data of all the selected NEs will be periodically collected and saved asa file in a specified path on the Nastar.

l Select Specify the time range and set Start time and End time to collect related datafrom the M2000 periodically or once within a specified time period and save the datato a specified path on the Nastar.

Step 6 Click Finish.The new data collection task is displayed in the task list.

----End

Related References3.8.2 Parameters for Creating or Modifying a Data Collection Task

3.3 Importing Configuration DataThis section describes how to import configuration data. The Nastar automatically obtainsconfiguration data from a specified directory on the Nastar server periodically and then importthe 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 importtask.




25

Contextl 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.l 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


Step 2 Click New. The New Task dialog box is displayed.

Step 3 Set the basic task information.1. In Task Name, enter the name of the scheduled task.2. Select a *** configuration data import task from Task Type.

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 . In the displayed Date/Time Selection dialog box, select the start time.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.

Step 5 Click Finish.The new task is displayed in the task list.

----End

Follow-up ProcedureAfter the task is created, you can query the status of the task in the task list of the TaskManagement window. If the task status is Complete, you can query the imported configurationdata by performing the following operations:

1. Double-click System Function > Data Query in the Analysis Task Managementwindow. The Query Data dialog box is displayed.

TIP

You can also choose System Function > Data Query from the navigation tree in the Analysis TaskManagement 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.

a. Specify whether to limit the time range.b. Select the names of the NEs to be queried.

4. Click Query.The query results are displayed in the Query Data dialog box.



26

3.4 Importing Engineering ParametersThis section describes how to import engineering parameters. You can import engineeringparameters into the Nastar database to provide a reference for certain algorithms related toperformance analysis.


Context

Engineering parameters mainly include the engineering information, geographical information,and key configuration information of cells.

The engineering parameter template files in .csv, .xls, and .xlsx formats can be imported. Toopen .xlsx files, you must install Microsoft Office 2007. Nastar imports and exports CSV filesmost efficiently. You are advised to save the engineering parameter data as CSV files.

NOTEIf 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 navigationtree in the Analysis Task Management window.

TIP

You can also choose System Function > Engineering Parameter Management from the navigation treein the Analysis Task Management window and right-click Open. The Engineering ParameterManagement window is displayed.

Step 2 In the Engineering parameter management window, click the *** engineeringparameters 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 multiplesheets, 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 columntitle/Column title in the engineering parameter file.

l The column headers marked with the * character must be configured. Otherwise, the importoperation is not allowed.



27

l If you need to modify an incorrectly configured column header, right-click the columnheader, 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 networksystems. For details, see Table 3-2. Otherwise, the engineering parameter file cannot beimported into the database.

Table 3-2 Restrictions on engineering parameters

Network System Restriction

GSM l The mandatory parameters must be configured, and thevalues of the mandatory parameters must not be empty.

l The values of the parameters must be in the specifiedrange.

l The value of MCC+MNC+LAC+CI of a cell must beunique.

NOTEFor details of the mandatory parameters and the range, see GSMEngineering Parameters.

UMTS l The mandatory parameters must be configured, and thevalues of the mandatory parameters must not be empty.


l The value of RNC ID+CELL ID of a cell must be unique.NOTE

For details of the mandatory parameters and the range, see UMTSEngineering Parameters.

CDMA l The mandatory parameters must be configured, and thevalues of the mandatory parameters must not be empty.


l The value of MSC ID+CELL ID+SECTOR ID of a cellmust be unique.

NOTEFor details of the mandatory parameters and the range, see CDMAEngineering Parameters.

LTE l The mandatory parameters must be configured, and thevalues of the mandatory parameters must not be empty.


l The value of eNodeB ID+CELL ID of a cell must beunique.

NOTEFor details of the mandatory parameters and the range, see LTEEngineering Parameters.

Step 5 Click OK.



28

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.

If... Then...

The imported engineering parameter data iscorrect

Click Close.

The imported engineering parameter data isabnormal.

The data that fails to be imported ishighlighted in red. In this case, perform eitherof the following operations:l Click Export Failed Records.

The system exports the error records to afile. You can modify error data and thencomplete the import operation.

l Click Close to complete the importoperation.

----End

Follow-up Procedurel Exporting engineering parameters

After engineering parameter data is imported, you can export all engineering parameterdata from the database and save the data as a .csv, .xls, or .xlsx file for easy query andmanagement. To export engineering parameter data, do as follows:

1. In the Engineering parameter management window, click the *** engineeringparameters tab and select the engineering parameters to be exported from theengineering parameter list. 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 dialogbox, and then click Save.

NOTE

You are advised to export and save the engineering parameter data as CSV files.

l Deleting engineering parametersSelect the engineering parameters to be deleted from the engineering parameter list, andthen click Delete.

3.5 Checking Engineering Parameters and ConfigurationData

This section describes how to check engineering parameters and configuration data. Throughthis function, you can check whether the existing engineering parameter data is consistent withthe configuration data. If the check result is inconsistent, you can enable the Nastar tosynchronize the engineering parameter data with the configuration data to ensure dataconsistency.



29

Prerequisitesl You have logged in to the Nastar client.l You are authorized to manage engineering parameters.l Configuration data is imported. For details, see 3.3 Importing Configuration Data.l Engineering parameter data is imported. For details, see 3.4 Importing Engineering

Parameters.

Procedure

Step 1 Double-click System Function > Engineering Parameter Management from the navigationtree in the Analysis Task Management window.

Step 2 In the Engineering parameter management window, click the *** engineeringparameters 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 numberof cells that are configured with both engineering parameters and configuration data.

l Number of cells with configuration but without engineering parameters: indicates thenumber of cells that are configured with configuration data but are not configured withengineering parameters.

l Number of cells with engineering parameters but without configuration: indicates thenumber of cells that are configured with engineering parameters but are not configuredwith configuration data.

l Number of External Cells with configuration but without engineering parameter:indicates the number of external neighboring cells that are configured with configurationdata but are not configured with engineering parameters. It is only for the GSMengineering parameters.

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 configurationdata.The file is used to check engineering parameters only on the GSM network.



30

Step 4 Optional: Click Configuration Synchronize to synchronize engineering parameter data withconfiguration data.After engineering parameter data is imported into the database, the Nastar updates someengineering parameters based on the latest configuration data according to the specificparameters.

The following engineering parameters are updated:l GSM network: Synchronize the configuration for BCC, NCC, BCCH, Cell Name, and TCH

parameters based on the LAC+CI.l UMTS network: Synchronize the configuration for Cell Name, P-SC, and UARFCN

Downlink parameters based on the RNC ID+Cell ID.l CDMA network: Synchronize the configuration for BSC ID, Cell ID, Sector ID, ARFCN

parameters based on the BTS ID.

NOTEThe Nastar system currently does not support the configuration synchronization of the engineeringparameters on the LTE network.

If the configuration data changes, you need to manually synchronize the engineering parameterdata with the configuration data to ensure data consistency. Alternatively, you can import themodified engineering parameter file to achieve data consistency.

----End

3.6 GIS ManagementThe Nastar can geographically display the performance analysis results through either theGeographic Information System (GIS) window or Google Earth. You can view the Nastaranalysis result directly on the map, thus facilitating the service analysis.

3.6.1 Viewing Analysis Results by Using the Google EarthThis section describes how to view analysis results by using the Google Earth. The Nastar canquickly display BTS and performance analysis results (for example, VIP analysis results) on theGoogle Earth. The three-dimensional map enables you to easily view the network performanceanalysis results and reduces the workload of field survey.

Prerequisitesl You have logged in to the Nastar client.l The PC is connected to the Internet.l The Google Earth is installed in the PC.

ContextThe 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 thecenter by default.

l The Nastar data can be displayed on the Google Earth synchronously. The geographic datais displayed on the scale of 2,600 meters at heights with the selected cell being in the center.



31

l Currently, the Nastar can display the following analysis results on a map:

– GSM neighboring cell analysis results, GSM VIP analysis results, GSM networkgeographic analysis results, and GSM/UMTS neighboring cell analysis results

– UMTS intra-frequency neighboring cell analysis results, UMTS VIP analysis results,UMTS pilot pollution analysis results, UMTS network geographic analysis results, andUMTS/GSM neighboring cell analysis results

– CDMA intra-frequency neighboring cell analysis results, CDMA VIP analysis results,and CDMA pilot pollution analysis results

– LTE VIP analysis

Click on the toolbar in the GIS window (that is Network Geographic Observationwindow) to view the legend information. It shows the display effect of each type of analysisresult.

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 TaskManagement window. The EarthViewWindow window is displayed.

The system loads the Google Earth components through the Internet. After the loading iscomplete, the system automatically reads the engineering parameters in the Nastar system anddisplays the engineering parameters as labels on the Google Earth.

If... Then...

The EarthViewWindow window displays thehome page of the Google Earth

It indicates that the system fails toautomatically read the Nastar engineeringparameters.

This problem may be caused by the lowspeed of loading the Google Earthcomponents. In this case, you need todouble-click System Function > SatelliteView again.

TIPYou can also choose System Function >Satellite View from the navigation tree in theAnalysis Task Management window andright-click Open. The Satellite View windowis displayed.

The EarthViewWindow window displays sitesand cells, and the specified area is located.

It indicates that the system succeeds inautomatically reading the Nastarengineering parameters.

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.



32

Step 3 View the cell information.After you click a cell, the Google Earth displays the engineering parameter information aboutthe cell in a message box.

You can click the cell again to cancel the display of the message box.

----End

3.6.2 Querying Analysis Results Through the GIS WindowThis section describes how to query analysis results through the Geographic Information System(GIS) window. The Nastar can quickly display BTS and performance analysis results (forexample, VIP analysis results) in the GIS window.

Prerequisitesl You have logged in to the Nastar client.l You are authorized to use the GIS.

ContextThe 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.l Currently, the Nastar can display the following analysis results on a map:

– GSM neighboring cell analysis results, GSM VIP analysis results, GSM networkgeographic analysis results, and GSM/UMTS neighboring cell analysis results

– UMTS intra-frequency neighboring cell analysis results, UMTS VIP analysis results,UMTS pilot pollution analysis results, UMTS network geographic analysis results, andUMTS/GSM neighboring cell analysis results

– CDMA intra-frequency neighboring cell analysis results, CDMA VIP analysis results,and CDMA pilot pollution analysis results

– LTE VIP analysis

Click on the toolbar in the GIS window (that is Network Geographic Observationwindow) to view the legend information. It shows the display effect of each type of analysisresult.

Procedure

Step 1 Click on the toolbar on the upper left corner of the Nastar client window. The GIS windowis displayed.

After the GIS window is displayed, click to hide the GIS window.

Step 2 Load engineering parameters.For details, see 3.7.3 Loading Site Information. For details about the operations in the GISwindow, see 3.7 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 windowregards the selected cell as a center to display the geographic data.



33

Step 4 Query cell information.

Click to select a cell. Then, the engineering parameters of the cell are displayed in the areain the right pane of the GIS window.

----End

3.7 Managing the GIS WindowYou can import the map files in .wor, .tab or .sxwu format and view the site information in theGIS window by using the engineering parameters. In addition, you can perform the followingoperations in the GIS window through the GIS toolbar, such as move/center/zoom in on/zoomout on a map and measure the distance between two points on the map.

ContextNOTE

The GIS window is the Network Geographic Observation window. You can click button in the upperleft corner of the Nastar client to open the window.

3.7.1 Importing a Maphis section describes how to import a map. You can import the map files in .wor, .tab, or .sxwuformat to simulate the geographic environment, thus facilitating the analysis and location ofnetwork problems.T

Prerequisitesl You have logged in to the Nastar client.l You are authorized to use the GIS.

ContextThe 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 areslow. It is recommended to convert the map files in .wor or .tab format to the map filesin .sxwu format by referring to 3.7.2 Converting the Map File Format. You can importthe map files in .sxwu format to improve the importing speed and the operation efficiency.

NOTE

The Nastar does not support importing the map in .tab format whose data source is in picture format.

l 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 upthe importing process.

CAUTIONWhen you perform operations in the GIS window, you are advised not to import or load mapfiles repeatedly. This is to prevent any unknown impact.



34

Procedure

Step 1 Select a mode to import map files depending on the actual situation.

If You Want to ... Then ...

Import a map file for the first time For details, see Step 2 to Step 4.

Step 2 Click on the toolbar. The Open Map... 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 ProcedureDeleting the geography layer. Click Layer Management icon on the toolbar, select thegeography layer to be deleted, click Remove.

3.7.2 Converting the Map File FormatThis section describes how to convert a map file in .wor or .tab format to .sxwu to improve theefficiency of importing map files.


ContextIt takes a long time to import a map file in .wor or .tab format. If users on multiple clients attemptto 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 .sxwuand import the file because the Nastar can quickly identify and import map files in .sxwu formatand allows multiple users to share the map files in .sxwu format. This greatly improves theefficiency 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.



35

The Nastar starts importing the map file. If the size of the map file is large, the format conversionspeed 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 InformationThis section describes how to load the site information. You can load the engineering parametersto the GIS so that the site information of the network can be displayed in the GIS window.

Prerequisitesl You have logged in to the Nastar client.

l You are authorized to use the GIS.

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 musthave imported the engineering parameters of the GSM network.

ContextWhen you open the client every time, you must load the site information again to view the siteinformation 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 Procedurel Displaying or hiding the site icon.

You can select or clear the check box before the Site layer navigation tree in the left paneof the GIS window.

l Setting the display effect.

Right-click Site Layer > The layer to be set on the navigation tree in the left pane of theGIS window, and then choose Sector Display from the shortcut menu to set the displayeffect of the sector, such as the size, dot, and color; choose Site Display from the shortcutmenu to set the display effect of the site, such as the size, dot, and color.

l Deleting the site layer.



36

Click layer management icon on the toolbar, select the site layer to be deleted, clickRemove.

l Setting the opacity of the site layer.

Click layer management icon on the toolbar, select the site layer to be deleted, setOpacity.

3.7.4 Filtering CellsThis 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. Thefiltered cells are geographically displayed in highlighted colors to be differentiated from othercells. In addition, the filtered cells can be saved as a cell group.

Prerequisitesl You have logged in to the Nastar client.l You are authorized to use the GIS.l The engineering parameters are imported to the Nastar.

ContextBefore filtering cells, you must ensure that the engineering parameters are consistent with theconfiguration data.

Procedure

Step 1 Draw polygons to define the areas to be filtered.

1. Click on the toolbar.2. Click the GIS work platform to add points to the polygon one by one.

CAUTIONThe lines of a polygon must not intersect. Otherwise, certain selected areas may be missedout.

If only one point of a line in the polygon is determined, the line is displayed as a brokenblue line. It indicates that you are drawing this line. If two points of a line in the polygonare determined, the line is displayed as a solid blue line. It indicates that you have finisheddrawing 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 systemand engineering parameter field.



37

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 filtercells either through a certain field or two fields. The relation between the two fields can beset 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 GISwindow.

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 theinformation about the NE group through the NE group management function.

----End

3.7.5 Searching CellsThis section describes how to search cells. You can using the search function to locate the cellin the GIS window quickly.

Prerequisitesl You have logged in to the Nastar client.l You are authorized to use the GIS.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



38

3.7.6 Moving/Zooming In On/Zooming Out On/Refreshing/FullyDisplaying a Map

This section describes how to adjust a map. You can zoom in or zoom out on a map to changethe map size, move a map, and display all the objects in the map window. In addition, you canrestore the map window to the default status through the refreshing function.

Prerequisites

Importing a map has been performed.

Procedurel 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 ofthe mouse pointer.

1. 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.

2. Click the map.TIPYou can scroll the mouse wheel forward or backward to zoom in or zoom out on the map.

l Move the map.

When you move a map, the size of the map does not change.

1. Click on the toolbar.

2. Move the mouse pointer on the map and drag the map to the required direction.

l View the panoramic scene of a map.

After you click , the system displays all the objects in the map window.

l Refresh a map.

After you click , the colors and connection lines of the site icons and sector icons thatare highlighted because of the network geographical application are cleared.

----End

3.7.7 Measuring Distance on the MapThis section describes how to measure distance on the map. You can measure distance betweentwo points on the map by using the distance measurement tool.

PrerequisitesImporting a map has been performed.



39

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 blackconnection 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 displayedin 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 EffectThis section describes how to save the map display effect. You can export the display effect ofoverlapped 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 InterfaceThis section describes the interface for collecting basic data on the Nastar and the relevantparameters. You can refer to this section when you import configuration data, engineeringparameters, or maps.

3.8.1 Interface Description: GISThis section describes the GIS interface, that is Network Geographic Observation window.Before performing relevant operations, familiarize yourself with the functions of the areas onthe interface.

Figure 3-1 shows the GIS interface.



40

Figure 3-1 GIS interface

SN Item Description

(1) Toolbar Shows common GIS operation buttons.

(2) Layer area Allows users to perform operations on site layers orgeographic layers, such as selecting, clearing, ordeleting layers.

(3) Main area Shows cell relationships geographically.

At the bottom of the main area, it synchronouslydisplays the longitude and latitude of the locationwhere the pointer stays and the distance between twopoints during distance measurement.

(4) Parameter area Displays engineering parameter information ofselected cells.

3.8.2 Parameters for Creating or Modifying a Data Collection TaskThis section describes the parameters related to data collection tasks. You can refer to thedescription when creating or modifying data collection tasks.


Parameter Value Range Description

Task Name Value range: [1.64] Indicates the name of a task.



41


Task Type - Choose Task Type > Data Collection > DataCollection.

ExecutionType

This parameter has twooptions: One-time andPeriodic.

l One-time task: The system executes a task onceonly at the specified time.

l Periodic task: The system executes a taskperiodically at the preset time.

Start time - Indicates the start time for a task.

DST You can select or clearthe check box next tothe option.

Indicates whether to use daylight saving time(DST).

Runimmediately

You can select or clearthe check box next tothe option.

If you select this option, Start time becomesunavailable and the task will be executedimmediately after the setting.

ExecutionInterval

Value range:[1.527040]

Indicates the interval between periodic tasks. Aninterval has two dimensions: duration and unit.

ExecutionTimes

Value range: [0,65535] Indicates the number of times that a periodic task isexecuted.0 indicates that the execution times are not limited.

End time The value of thisparameter must be laterthan Start time andearlier than 12/31/203823:59:59.

Indicates the end time for a periodic task.

OSS Name Select a parametervalue from the drop-down list box.

Indicates the name of an EMS.



42


Data Type Select an option fromthe drop-down list box.The options vary withthe OSS version. Fordetails, see thefollowing description:the data typescorresponding to theOSS of the M2000V200R008, M2000V200R009, M2000V200R010 and M2000V200R011,M2000V200R011C00CP2302,M2000V200R011C01CP2302,M2000V200R012 areConfig Data, GSMMeasure Task File forNeighbor Cell Data,GSM Frqlog Data,Performance Data,Any Data, and LTECFG Data.

Indicates the type of the data that is collected fromthe EMS to the Nastar.

Collect AllNE

You can select or notselect the option.

If you select this option, you can select all the NEs.When the NEs change, the system automaticallyupdates the NEs every four hours.

Collect ByNE Type


If you select this option, you can select the NEs bythe NE type. When the NEs under the selected NEtype change, the system automatically updates theNEs under the selected NE type every four hours.After you select this option, you can only select allNEs under an NE type but cannot select some NEsunder an NE type.

Filter NE - Allows you to type keywords to filter NEs.

Specify thetime range


Indicates whether to collect data during thespecified time period.

Start Time - Indicates the start time of the data collection period.

End Time - Indicates the end time of the data collection period.

Related Tasks3.2 Collecting Configuration Data6.3.1 Creating a GSM Performance Data Collection Task



43

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 youlogin in to the Nastar client.

SymptomWhen a user logs in to the Nastar client, the GIS tab page is not displayed. As a result, the GISfunction cannot be used.

CauseIf the original client is removed after the new client is configured, it will bring on the problem.

The PC where the Nastar client is installed is not configured with the Microsoft .NETFramework.

Operation ProcedureYou can deal with it by the following methods.l Download and install Microsoft .NET Framework v2.0 and a later version from the Internet.l Reinstall the Nastar client.



44

4 Subscribing to GSM Data Sources

About This Chapter

This section describes how to enable data source switches by using the data source subscriptionfunction before performing various Global System for Mobile Communications (GSM) themeanalysis functions. After required data source switches are enabled, the Nastar can collectrequired data from network elements (NEs). This function is the prerequisite for all Nastar themeanalysis functions.

4.1 Basic Knowledge of GSM Data Source SubscriptionThis section describes the functions and usage scenarios of Global System for MobileCommunications (GSM) 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 datasource switches in batches for all theme analysis functions on network elements (NEs) throughthe data source subscription function. This ensures that NEs can collect the required analysisdata 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 switchstatus on the live network to verify that all required data source switches are enabled. If a requireddata source switch is not enabled, it is recommended that common users apply to theadministrator who can centrally enable the corresponding switch.

4.4 GUI Description: Subscribing to GSM Data SourceThe GUI related to subscribing to GSM data sources is composed of four tabs: Set DataSubscription, Query Network Data Subscription, VIP Signaling Tracing Setting, and VIPSignaling Tracing Status. Before performing relevant operations, familiarize yourself with thefunctions of the areas on the GUI.

iManager NastarNetwork Optimization User Guide (GSM) 4 Subscribing to GSM Data Sources


45

4.1 Basic Knowledge of GSM Data Source SubscriptionThis section describes the functions and usage scenarios of Global System for MobileCommunications (GSM) data source subscription.

DescriptionData 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 requireddata from the NEs.

For details about the functions and usage scenarios of data source subscription, see Table 4-1.

Table 4-1 Description of GSM data source subscription

Theme RequiredDataSource

Whether toEnable DataSourceSubscription

Function

GSMMRanalysis

Performance data

No -

GSMneighboring cellanalysis

Performance data,neighboringcellmeasurement data

No -

GSMfrequencyanalysis

Performance data,neighboringcellmeasurement data

No -

GSMuplinkinterferenceanalysis

Uplinkinterferencedata

No -

GSM/UMTSneighboring cellanalysis

Performance data

No -



46

Theme RequiredDataSource

Whether toEnable DataSourceSubscription

Function

GSMcomplaintanalysissupport

Call historyrecord(CHR) data

Yes Used to enable the function of obtaining BSC-level CHR data and the function of requestingmobile stations (MSs) to report InternationalMobile Subscriber Identities (IMSIs).

GSMVIPanalysis

GSMcellperformanceanalysis

GSMterminalinventoryanalysis

GSMnetworkgeographicanalysis

MR data,CHR data

Yes The following data will be subscribed to:l GSM MR network geographic data, used to

enable the BSC-level or BTS-level MRmeasurement function.

l GSM CHR network geographic data, used toenable the function of obtaining BSC-levelCHR data and the function of MSs to reportIMSIs.

Usage ScenarioData source subscription is a function with a high security level. The following two types ofusers 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.l Common users: A common user is authorized to query the status of data source switches

and set data source switches (Common users can be assigned operation permissions to querythe status of data source switches and set data source switches.).

NOTE

You can assign Subscription Management rights to common users by choosingSecurity > SecurityManagement. Then, common users are authorized to query and set the data source switch.If the status of the data sources in the live network does not meet the analysis requirements, it is recommendedthat common users apply to the administrator who can centrally enable the corresponding switch.



47

Figure 4-1 describes the usage scenarios for the two types of users performing data sourcesubscription.

Figure 4-1 Usage scenario

Table 4-2 Description of usage scenarios

User UsageScenario

Description Example

Administrator

Initialsetting

An administrator user isauthorized to collect Nastar usageinformation on the managednetworks when the Nastar isinitially used. In addition, the useris authorized to enable data sourceswitches in batches for varioustheme analysis functions.

Managed networks: network Aand network BInvolved theme analysis function:VIP analysisSelect all cells on networks A andB, and set the data sourcesubscription switch to ON for theVIP analysis of all cells.



48

User UsageScenario

Description Example

Routinemaintenance

Maintenance information can beobtained in either of the followingmethods:l The administrator periodically

queries the status of datasource switches on the livenetwork and compares thestatus with the historical statusset on the Nastar. If a datasource switch is set to ON onthe Nastar but it is set to OFFon the live network, enable thedata source subscriptionfunction again to set the datasource switch to ON.

l If a common user finds that thestatus of a data source switchon the live network does notmeet analysis requirements,the administrator enables thedata source subscriptionfunction again to enable thedata source switch.

-

Common user

Routinequery

Common users can query whetherthe data source status on the livenetwork meets analysisrequirements before performingvarious theme analysis End to End(E2E) tasks. If the data sourcestatus does not meet analysisrequirements, common users canrequest the administrator to enablethe required data source switches.

A common user queries the datasource status on network A. Afterquerying, the user finds that thedata source switch for VIPanalysis in cell a is set to OFF,which does not meet analysisrequirements. Therefore, the userrequests the administrator toenable this switch.After receiving the application,the administrator sets the datasource switch for VIP analysis incell 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 datasource switches in batches for all theme analysis functions on network elements (NEs) throughthe data source subscription function. This ensures that NEs can collect the required analysisdata for the Nastar.



49

Prerequisitesl You have logged in to the Nastar client as an administrator user.l You are authorized to set data source switches.l The Operating Support System (OSS) and NEs related to analysis tasks are created. For

details, see 2.2 Creating OSSs and the Managed NEs.l The configuration data has been imported into the Nastar database. For details, see 3.3

Importing Configuration Data.

ContextBefore setting data source switches, the administrator must learn about NE information andNastar usage information of the managed networks to enable data source switches in batches fortheme analysis functions.

Procedure

Step 1 In the navigation tree on the left of the Analysis Task Management window, double-clickSystem Function > Subscription Management.

TIPYou can also choose System Function > Subscription Management from the navigation tree in theAnalysis Task Management window and right-click Open. The Subscription Management window isdisplayed.

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 isdisplayed synchronously. During initial setting, the status of all data source switches is OFF orUnsupported.

Step 4 On the Set Data Subscription tab page, click Set. The Set Performance Subscription dialogbox 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) analysisfunction, and cell performance analysis function. Therefore, the status of data source switches for these themeanalysis functions must be the same. For details, see the description below the Set PerformanceSubscription dialog box.

Step 6 Optional: Set the VIP signaling tracing switch.

NOTE

This step applies only to GSM subscription and UMTS subscription.



50

1. On the VIP Signaling Tracing Setting tab, click ON. The VIP Switch Setting dialog boxis displayed.

2. In the VIP group user navigation tree, select VIP users to set.You can hold down shift to select VIP subscribers. Right-click and choose Select from theshortcut menu to select the highlighted VIP subscribers.

You can also select Select None from the shortcut menu to clear the selected VIPsubscribers.

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 ProcedureAfter the required data sources are subscribed to, click Refresh. The data source subscriptionstatus on NEs in the Nastar database is refreshed.

4.3 Querying the Data Source Switch Status on the LiveNetwork (As a Common User)

Before performing a theme analysis task on the Nastar, you must query the data source switchstatus on the live network to verify that all required data source switches are enabled. If a requireddata source switch is not enabled, it is recommended that common users apply to theadministrator who can centrally enable the corresponding switch.

Prerequisitesl You have logged in to the Nastar client.l You are authorized to query the data source switch status and set the switch status.l The Operating Support System (OSS) and network elements (NEs) related to analysis tasks

are created. For details, see 2.2 Creating OSSs and the Managed NEs.l The configuration data has been imported into the Nastar database. For details, see 3.3

Importing Configuration Data.

Procedure

Step 1 In the navigation tree on the left of the Analysis Task Management window, double-clickSystem 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 tablein the lower right area.



51

Table 4-3 describes the status of data source switches.

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 statusmeets the Nastar analysis requirements.

OFF Indicates that a data source switch is disabled on an NE and the statusdoes not meet the Nastar analysis requirements.

Unknown

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.

Unsupported

Indicates that the Nastar does not allow users to query the status of a datasource 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 theUnsupported 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 sourceswitch 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 GSM Data SourceThe GUI related to subscribing to GSM data sources is composed of four tabs: Set DataSubscription, Query Network Data Subscription, VIP Signaling Tracing Setting, and VIPSignaling Tracing Status. Before performing relevant operations, familiarize yourself with thefunctions of the areas on the GUI.

Switch SettingsThis tab sets the switch of the GSM data source. For details, see Figure 4-2.



52

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 ofthe data source for each theme analysis.By clicking Refresh, you can refresh the subscriptionstatus of the data source for each theme analysis.You can set three subscription states: ON, OFF, andNo Modification. For details, see 4.2 Setting DataSource Switches (As an Administrator User).

(3) NE list area The NE settings for each theme analysis are displayedin a list.TIP

You can select multiple records by holding down Ctrl.

(4) Operation informationlist area

In this area, you can view the setting of the data sourceswitch.

(5) Area for displayingdata source statusicons

Icons show the switch status of the data source. Fordetails, see Table 4-4.

Switch Status on the Current NetworkThis tab displays the switch status of the GSM data source on the current network. For details,see Figure 4-3.



53

Figure 4-3 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 Set Data Subscription, you donot need to select the NEs again in the NE navigation tree.

(2) Button area By clicking Query, you can query the data sourceswitch status of each NE on the live network.

(3) NE list area The data source switch status of each NE on the livenetwork is displayed in a list.TIP


(4) Operation informationlist

This area displays the result of querying the datasource switch.

(5) Area for displayingdata source statusicons


Settings of VIP Signaling Tracing SwitchThis tab sets the VIP signaling tracing switch. For details, see Figure 4-4.

Figure 4-4 Settings of VIP signaling tracing switch



54

SN Item Description

(1) NE navigation tree You can select NEs to set VIP signaling tracing in theNE navigation tree.NOTE

Because you select NEs in area (2) and the system takes theselection in area (2) in priority, you need not select NEs inthis area.

(2) Button area By clicking ON, select VIP subscribers and NEs toset VIP signaling tracing. After you click Confirm,the system enables the VIP signaling tracing switchfor selected NEs.After you click OFF, the system disables the VIPsignaling tracing switch for selected NEs.

(3) VIP signaling tracingNE list area

The basic information about NEs for which you haveset VIP signaling tracing is displayed in a list.TIP



This area displays the result of enabling or disablingVIP signaling tracing for NEs.

(5) Area for displayingdata source status icons


VIP Signaling Tracing Switch Status on the Current NetworkThis tab displays the VIP signaling tracing switch status of NEs on the current network. Fordetails, see Figure 4-5.

Figure 4-5 VIP signaling tracing switch status on the current network



55

SN Item Description

(1) NE navigation tree You can select NEs to query in the NE navigationtree.NOTE

If you have selected NEs in VIP Signaling TracingSetting, you do not need to select the NEs again in the NEnavigation tree.

(2) Button area By clicking Query, you can query the VIP signalingtracing switch status of each NE on the currentnetwork.

(3) VIP signaling tracingNE list area

The data source switch status of NEs for which youhave set VIP signaling tracing on the live network isdisplayed in a list.TIP



This area displays the result of querying the datasource switch.

(5) Area for displayingdata 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 foranalysis 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.

Unknown

The data source switch of an NE on the current network is unknown. TheNastar cannot detect the data source status of the NE. The possible causesare 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.

Unsupported

The Nastar does not display the data source switch status of an NE on thecurrent network. For example, if an NE is of the base station controller(BSC) level but the data source switch on the current network supportsonly objects at the cell level, the data source switch status of the NE isdisplayed as Unsupported.



56

5 Appendix: MML Command Reference

This section describes the MML commands involved when the Nastar implements the GSM datasource subscription function or delivers E2E tasks. For details about the MML commands, seethe Nastar Data Source Subscription MML Command List Overview of GSM.

iManager NastarNetwork Optimization User Guide (GSM) 5 Appendix: MML Command Reference


57

6 GSM MR Analysis

About This Chapter

The GSM MR analysis function enables you to obtain GSM measurement report (MR) analysisdata, create GSM MR analysis tasks, query GSM MR analysis results, and export GSM MRanalysis reports from the Nastar. Through this function, the Nastar directly displays radio linkinformation and provides analysis of and suggestions on wireless network problems for quicklylocating problems.

6.1 Basic Knowledge of GSM MR AnalysisThis section provides the basic knowledge of GSM measurement report (MR) analysis, such asthe MR analysis function, TopN counters, and MR theme analysis types. The basic knowledgehelps you perform GSM MR analysis.

6.2 Process of GSM MR AnalysisThis section describes the process of GSM measurement report (MR) analysis.

6.3 Obtaining GSM MR Analysis DataThis section describes how to enable the Nastar to obtain GSM measurement report (MR)analysis data. You can create a neighboring cell measurement data E2E task to turn on someperformance counters switch, create a collection task to enable the Nastar to collect analysis dataand create a data import task so that the Nastar imports the collected analysis data into thedatabase.

6.4 Creating GSM MR Analysis TasksThis section describes how to create GSM MR analysis tasks. After you create a GSM MRanalysis task, the Nastar periodically analyzes GSM performance data, GSM configuration data,and engineering parameters in the Nastar database. By querying analysis results, you can learnabout the status of the entire radio network so that problems can be located and solved efficiently.

6.5 Querying GSM MR Overview Analysis ResultsThis section describes how to query the GSM measurement report (MR) overview report. AnMR report includes the following information about a measurement cell: uplink and downlinklevels, uplink and downlink quality, timing advance (TA), and link balance. You can learn theTRX and cell coverage, radio link quality, and subscriber distribution directly from theinformation in the analysis results. A GSM MR overview report consists of GSM BSC analysisresults, GSM cell group analysis results, TopN TRX analysis results, and GSM MR themeanalysis results.

6.6 Querying GSM MR Results

iManager NastarNetwork Optimization User Guide (GSM) 6 GSM MR Analysis


58

This section describes how to query GSM measurement report (MR) results. Through thisfunction, you can query the detailed information about TopN TRXs and TRXs that meet thefilter conditions of the cell where multiple TopN TRXs or TRXs that meet the filter conditionsexist.

6.7 Comparing GSM MR Analysis ResultsThis section describes how to compare the GSM Measurement Report (MR) analysis results.After the network is optimized or the equipment is upgraded, you can compare two GSM MRanalysis results generated in two time segments to check the differences between the values ofthe same counters in two time segments. This function helps you learn about the detailed networkperformance differences in two time segments and quickly evaluate the network optimizationeffect.

6.8 Exporting GSM MR Overview ReportsThis section describes how to export GSM MR overview reports. You can export GSM MRoverview analysis results as .csv files.

6.9 Technical Specifications for GSM MR AnalysisThis section describes the technical specifications for GSM MR analysis.

6.10 Reference for the GSM MR Analysis GUIThis section describes the interface for GSM MR analysis and the relevant parameters. Beforeperforming relevant operations, familiarize yourself with GSM MR analysis functions.



59

6.1 Basic Knowledge of GSM MR AnalysisThis section provides the basic knowledge of GSM measurement report (MR) analysis, such asthe MR analysis function, TopN counters, and MR theme analysis types. The basic knowledgehelps you perform GSM MR analysis.

6.1.1 GSM MR AnalysisThis section describes the GSM MR analysis function. A GSM measurement report (MR)includes the following information about the measurement cell: uplink level, downlink level,uplink quality, downlink quality, timing advance (TA) distribution, and link balanceinformation. The information in MRs helps you learn the coverage, quality, and user distributionof TRXs and cells. In addition, the Nastar processes the required information and displays radiolink information directly, helping you solve network problems.

MR Overview Analysis ResultsThe MR overview analysis results include the overview information about the radio networkperformance, the distribution of TopN TRXs and TRXs that meet the filter conditions of eachBSC and cell group, the TopN TRXs for which the value of each radio link counter is the lowest,and the classification of the TRXs that meet the filter conditions based on theme analysis.

NOTETopN TRXs indicate the N TRXs (currently, the default value of TopN is 99) with the poorest performanceindicated by a selected radio link counter.

You can view the daily MR overview analysis results to learn about the information about theTRXs that meet the filter conditions of each BSC, each cell group, and the entire network. Youcan also check for other problem in the cell where a TRX that meet the filter conditions or TopNTRXs are located and analyze these TRXs that meet the filter conditions.

The problem analysis themes are as follows:l Weak coverage analysis. TRXs with a low TA value, a low level, and poor signal quality

are listed.l Interfered cells. Cells with a high level and poor quality are listed.l Over coverage analysis. You can compare the TA values and the number of MRs to analyze

the traffic distribution and to check whether the cell is an over coverage cell.l Unbalanced uplink and downlink. The cells in which the uplink and downlink levels are

greatly unbalanced.l Other problems. Problems on the network, such as a few of generated MRs, no traffic, and

low traffic, are listed.

The analysis results can be displayed in a table or a bar chart to provide the radio link quality,level, traffic distance distribution, and link balance. Analysis of the problems and suggestionsare provided to help you quickly analyze and locate the quality problems that occur on thewireless network.

MR QueryDuring network performance analysis and optimization, when problem cells (such as a cellwhose call drop rate is high or number of handover failures is large) are found, you can query



60

the MR information about these cells and the radio links of the TRXs in the cells through theNastar.

You can set the time and cell objects before the query. The MR information about these cells isdisplayed in the result window. In addition, you can enable the Nastar to further query the TRXinformation. Through the comparison and query of different TRXs in cells, you can locate morecomplicated network problems effectively.

The query results are displayed in a table or a bar chart to provide the radio link quality andsubscriber distribution of each TRX.

MR Comparison Analysis

After network upgrade and optimization such as the adjustment of antennas and modificationof parameter settings, you can compare the quality and coverage of the entire network, BSCs,cell groups, or cells with the quality and coverage obtained before the network upgrade andoptimization, or you can compare the quality and coverage of different time segments duringnetwork upgrade and optimization.

The comparison analysis results are displayed in a table or a bar chart.

6.1.2 TopN KPIsThis section describes TopN KPIs related to the performance analysis. The KPIs include averagequality of the received signals at uplink and downlink, average levels received at uplink anddownlink, timing advance (TA) average distribution, and uplink and downlink balance.

Received Signal Quality

The quality of received signals is divided into seven classes from 1 to 7 according to the bit errorrate. Each class corresponds to different bit error rates. Higher class indicates poorer quality ofreceived signals. Class 1 indicates the minimum bit error rate and the best quality of receivedsignals. Class 7 indicates the maximum bit error rate and the poorest quality of received signals.

Table 6-1 describes the relation between the quality classes of received signals and the bit errorrate.

Table 6-1 Relation between the quality classes of the received signals and bit error rate

QualityClass ofReceivedSignals

Bit Error Rate (%)

1 [0.2, 0.4)

2 [0.4, 0.8)

3 [0.8, 1.6)

4 [1.6, 3.2)

5 [3.2, 6.4)

6 [6.4, 12.8)



61

QualityClass ofReceivedSignals

Bit Error Rate (%)

7 ≥ 12.8

Received LevelThe received signal level is divided into seven classes according to level values. Each classcorresponds to different ranges of received levels. Class 1 indicates the lowest received leveland class 7 indicates the highest received level.

Table 6-2 describes the relation between the received levels and the seven classes.

Table 6-2 Relation between the received levels and the seven classes

Class ofReceivedLevel

Received Level (dBm)

1 (-100, -95]

2 (-95, -90]

3 (-90, -85]

4 (-85, -80]

5 (-80, -75]

6 (-75, -70]

7 > -70

TA(Timing Advance)Timing advance (TA) is a counter used to describe the distance with time and is used for coverageanalysis. The header of a measurement report (MR) sent from a mobile station (MS) to a BTScarries the delay measured by the MS. After obtaining the delay, the BTS monitors the timewhen a call reaches and sends an instruction to the MS on a downlink channel every 480 ms tospecify the advanced sending time for the MS. This time is termed TA, ranging from 0 to 63.The MRs usually contain TA values ranging from 0 to 10. The MRs contain TA values higherthan 10 are incremented by certain TA ranges. In a TA distribution chart generated on the basisof GSM MR analysis results, each bar chart shows the percentage of the number of MRs withina TA range to the total number of MRs.

Uplink and Downlink BalanceThe MR received by the BSC contains the uplink receive level and downlink receive level. Theresult (in dB), which is obtained by subtracting the uplink receive level and the sensitivitydifference between the MS and the BTS from the downlink receive level, is divided into 11



62

classes from 1 to 11. Table 6-3 describes the relations between classes and values of the Uplinkand Downlink Balance Level counter.

Table 6-3 Description of link balance classes

Uplink andDownlinkBalanceClass

Downlink Receive Level- Uplink Receive Level- 6 (dB)

1 ≤ -15

2 -14, -13, -12, -11

3 -10, -9, -8

4 -7, -6, -5

5 -4, -3, -2

6 -1, 0, 1

7 2, 3, 4

8 5, 6, 7

9 8, 9, 10

10 11, 12, 13, 14

11 ≥ 15

NOTE

The number 6 in the formula "Downlink receive level - Uplink receive level - 6 (dB)" refers to the sensitivitydifference between the MS and the BTS.

If the statistical result indicates that the uplink and downlink are mostly in balance class 1, thedownlink loss is excessively high or the downlink transmit power is excessively low. If thestatistical result indicates that the uplink and downlink are mostly in balance class 11, the uplinkloss is excessively high or the uplink transmit power is excessively low. According to thestatistical result, you can locate the faults that may occur on the transmit and receive channels,such as the TRX or antenna feeder.

6.1.3 GSM MR Theme AnalysisThis section describes the themes involved in the GSM MR theme analysis, such as uplinkinterference, downlink interference, uplink weak coverage, downlink weak coverage, TRX weakcoverage, over coverage, link balance (uplink problem), link balance (downlink problem), andother problems. This section also provides the solutions to these problems.

The MR theme analysis is classified into nine types based on themes. The system providesdifferent operation suggestions for each type of MR theme analysis. For details, see Table6-4.



63

Table 6-4 Themes and operation suggestions

Theme Description Suggestion

Uplinkinterference

The uplink interferenceresults in high level andpoor quality.

Change the ARFCN and check whether radiointerference sources exist in the coverage area.After the ARFCN is changed, enable the uplinkinterference analysis function to analyze theinterference according to the uplink frequencydistribution that is measured by TRXs.

Downlinkinterference

The downlink interferenceresults in high level andpoor quality.

Change the ARFCN and check whether radiointerference sources exist in the coverage area.After the ARFCN is changed, use an MS to searchfor frequencies within the cell coverage area wherethe TRX is transmitted, and view the downlinkfrequency status.

Uplinkweakcoverage

The signal loss on theuplink of the TRX is large.

Check the cables connecting the combiner and theTRX, and cable connections in the antenna system.Ensure that the cable connections are proper andsecure, and then locate the fault by changing thecable ports, combiner, or TRX.

Downlinkweakcoverage

The signal loss on thedownlink of the TRX islarge.

Move an MS to a place near the TRX to measurethe actual power of the TRX. Check whether thedownlink level of the TRX is low. If the downlinklevel of the TRX is low, check the cableconnections between the combiner and the TRX,and cable connections in the antenna system. Then,check the level at the TRX entry and output entryof the combiner by using the power meter to locatethe fault.

TRX weakcoverage

l The signal loss on theuplink and downlink ofthe TRX is large.

l The TRX coverage isremote, which causespoor uplink quality.

l The TRX coverage isremote, which causespoor downlink quality.

l Check the cables connecting the combiner andthe TRX, and cable connections in the antennasystem. Ensure that the cable connections areproper and secure, and then locate the fault bychanging the cable ports, combiner, or TRX.

l Check whether the actual azimuth of theantenna is the same as the antenna azimuth indesign. If the antenna is omni-directional,check whether the coverage is large.

Overcoverage

l The TRX has the overcoverage problem.

l The TRX coverage isremote, which causespoor uplink ordownlink quality.

l Check whether there are missing neighboringcells and cells whose coverage is remote.

l Check whether the actual azimuth of theantenna is the same as the antenna azimuth indesign. If the antenna is omni-directional,check whether the coverage is large.



64

Theme Description Suggestion

Linkbalance(uplinkproblem)

l Uplink and downlinklevels are unbalanced,and the downlink levelis higher than theuplink level.

l The great signal losson the uplink of theTRX results in lowBTS receive level andpoor quality.

l Check whether the coverage complies with theplanning and whether the output power of theTRX and CDU is normal. You can adjust theuplink receive threshold and the grade of thedownlink static power to balance uplink anddownlink levels.

l Check the cables connecting the combiner andthe TRX, and cable connections in the antennasystem. Ensure that the cable connections areproper and secure, and then locate the fault bychanging the cable ports, combiner, and TRX.

Linkbalance(downlinkproblem)

l Uplink and downlinklevels are unbalanced,and the uplink level ishigher than thedownlink level.

l The great signal losson the downlink of theTRX results in low MSreceive level and poorquality.

l Check whether the coverage complies with theplanning and whether the output power of theTRX and CDU is normal. You can adjust theuplink receive threshold and the level of thedownlink static power to balance uplink anddownlink levels.

l Move an MS to a place near the TRX to checkwhether the downlink level of the TRX is low.If the downlink level of the TRX is low, checkthe cables connecting the combiner and theTRX and cable connections in the antennasystem and check the level at the TRX entry andoutput entry of the combiner by using the powermeter to locate the fault.

Otherproblems

l The performance ofthe receive level of theTRX is abnormal.

l The number of MRs issmall.

Check whether the hardware or software of theTRX is faulty and whether only a few MRs arereported, and analyze the reason for the generationof a small number of MRs.

6.2 Process of GSM MR AnalysisThis section describes the process of GSM measurement report (MR) analysis.

Figure 6-1 shows the process of GSM MR analysis.



65

Figure 6-1 Process of GSM MR analysis

Table 6-5 describes each procedure shown in Figure 6-1.

Table 6-5 Process of GSM MR analysis

No. Procedure Description

2 Create a GSMperformancedata collectiontask

You need to choose Maintenance > Task Management on theNastar client to open the Task Management window and thencreate a GSM performance data collection task. After the task iscreated, the Nastar periodically obtains the GSM performancedata from the M2000 and then saves the data in files on the Nastarserver.

3 Create a GSMperformancedata importtask

You need to choose Maintenance > Task Management on theNastar client to open the Task Management window, and thencreate a GSM performance data import task. After the tasks arecreated, the Nastar periodically imports the GSM performancedata saved on the Nastar server into the database.



66


4 Check theintegrity ofGSM MRanalysis data

You can double-click System Function > Data Query in theAnalysis Task Management window on the Nastar client toopen the Query Data dialog box and then check that all therequired GSM MR analysis data is imported into the database.

5 Create a GSMMR analysistask

In the Analysis Task Management window on the Nastar client,you can create a GSM MR analysis task. After the task is created,the Nastar retrieves the GSM performance data and GSMconfiguration data periodically from the database, analyzes theretrieved data, and then generates analysis results.

6 l Query GSMMRoverviewanalysisresults

l Query GSMMR analysisresults

l CompareGSM MRanalysisresults

You can view the analysis results of the GSM MR analysis tasksthat are successfully performed and compare the resultsgenerated in different time segments.

7 Export GSMMR overviewanalysis reports

You can enable the Nastar client to export GSM MR analysisresults as report files.

6.3 Obtaining GSM MR Analysis DataThis section describes how to enable the Nastar to obtain GSM measurement report (MR)analysis data. You can create a neighboring cell measurement data E2E task to turn on someperformance counters switch, create a collection task to enable the Nastar to collect analysis dataand create a data import task so that the Nastar imports the collected analysis data into thedatabase.



67

ContextNOTE

You can create a GSM neighboring cell measurement data E2E task to enable the following performancecounters on the M2000 client:

l Number of MRs per Cell

l Neighbor Cell Level Measurement per Cell

l GSM Cell to GSM Cell Outgoing Handover Measurement

l Uplink-and-Downlink Balance Measurement per TRX

l Number of MRs based on TA per TRX

l TCHF Receive Level Measurement per TRX

l TCHH Receive Level Measurement per TRX

If the preceding performance counters are already enabled, you do not need to create a GSM neighboringcell measurement data E2E task.

6.3.1 Creating a GSM Performance Data Collection TaskAfter you create a GSM performance data collection task on the Nastar, the Nastar periodicallycollects NE performance data on the M2000 and saves the data in a specified path for futureGSM MR analysis.


Contextl A GSM performance data collection task is a user-defined timing task.

l A GSM performance data collection task can be executed only once or periodically. Theoptions of the execution period are Minute, Hour, Day, Week, and Month.

Procedure


Step 2 Click Create. The New Task dialog box is displayed.TIP

Choose Task Type > Data Collection from the navigation tree and double-click Data Collection. TheNew Task dialog box is displayed. Task Type is set to Data Collection by default.

Step 3 Set the basic information about the task.

1. In the Task Name field, enter the name of the task.

2. Select Data Collection > Data Collection in Task Type.

3. Click Once or Period in the Run Type pane.

Step 4 Click Next.

1. Click and select the start time of the task in the displayed Time Setting dialog box.



68

NOTE

l Start Time must be later than the current time of the server.

l If Run Type of the task is set to Once, the Start Time parameter is unavailable after you selectthe Run At Once check box. This task is executed immediately after it is created.

2. Perform corresponding operations according to the task running type, which is once orperiodical.

If You Need to... Then...

The value of Run Type is Once Perform Step 5.

The value of Run Type is Period a. In the Period Setting field, set a taskexecution period.NOTE

You can be advised to set half an hour orone hour as a task execution period forcollecting performance data.

b. Perform Step 5.

Step 5 Click Next. In the Basic Information field and the Task Parameter field, set relevantparameters.1. From the OSS drop-down list, select the name of the OSS that manages the NE to be

analyzed.2. Select Performance data from the Data Type drop-down list box.3. Set the parameters in the Task Parameter field.


The OSS selected from theOSS drop-down list takesM2000V200R008,M2000V200R009,M2000V200R010,M2000V200R011,M2000V200R011C00CP2302,M2000V200R011C01CP2302,or M2000V200R012 as the OSSdata interface type.

l Sort the objects in the navigation tree by OSS orsubnet. Then, select one or more NEs. The relateddata of the NEs in the selected OSS systems orsubnets are periodically collected to a certaindirectory of the Nastar.

l Select Specify the time range and set Starttime and End time to collect related data from theM2000 side periodically or once within thespecified time period. Then, save the data under aspecified directory of the Nastar.


----End

Related References3.8.2 Parameters for Creating or Modifying a Data Collection Task



69

6.3.2 Creating a Data Import TaskThis section describes how to create a data import task. The Nastar periodically imports theanalysis data such as the performance data, VIP analysis data, and cell performance analysisdata on the Nastar server into the database to perform various theme analysis tasks.


Contextl A data import task is a user-defined scheduled task. You can create only one user-defined

scheduled task of the same type.

l The data import task can only be executed periodically. The unit of the task execution periodcan be Hours, Days, Weeks, or Months. The data import task of the same type can onlybe created once on the Nastar. After the task is created, the Nastar automatically importsdata at the preset time.

l 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.

l You need to create data import tasks of different types based on the type of an analysis task.Table 6-6 shows the mapping between analysis task types and types of data import tasks.

Table 6-6 Mapping Between Analysis Task Types and Types of Data Import Tasks

Analysis TaskType

Data Import Task Type Manual Creation/AutomaticCreation

GSM MR Analysis Import GSM PerformanceAnalysis Data

Manual creation

GSM NeighboringCell Analysis

Import GSM PerformanceAnalysis Data and ImportGSM Measure Task File forNeighboring Cell

Manual creation

GSM/UMTSNeighboring CellAnalysis

Import GSM PerformanceAnalysis Data

Manual creation

GSM FrequencyAnalysis


Manual creation

GSM UplinkInterferenceAnalysis

Import GSM UplinkInterference Analysis Data

Manual creation

GSM VIP Analysis Import GSM VIP AnalysisData

Manual creation



70

Analysis TaskType


GSM ComplaintAnalysis Support

- -

GSM CellPerformanceAnalysis

Import GSM CellPerformance Analysis Data

Manual creation

GSM TerminalInventory Analysis

Import GSM TerminalInventory Analysis Data

Manual creation

GSM NetworkGeographicAnalysis

l Import GSM NetworkGeographic ObservationAnalysis CHR Data

l Import GSM NetworkGeographic ObservationAnalysis MR Data

Manual creation

UMTS UplinkInterferenceAnalysis

Import UMTS UplinkInterference Analysis Data

Manual creation

UMTS Intra-FrequencyNeighboring CellAnalysis

Import UMTS Intra-Frequency Neighboring CellAnalysis Data

Manual creation

UMTS/GSMNeighboring CellAnalysis

Import UMTS/GSMNeighboring Cell AnalysisData

Manual creation

UMTS CoverageAnalysis

Import UMTS CoverageAnalysis Data

Manual creation

UMTS VIPAnalysis

Import UMTS VIP AnalysisData

Manual creation

UMTS ComplaintAnalysis Support

- -

UMTS PilotPollution Analysis

Import UMTS Pilot PollutionAnalysis Data

Manual creation

UMTS CellPerformanceAnalysis

Import UMTS CellPerformance Analysis Data

Manual creation

UMTS TerminalInventory Analysis

Import UMTS TerminalInventory Analysis Data

Manual creation



71

Analysis TaskType


UMTS NetworkGeographicAnalysis

l Import UMTS NetworkGeographic ObservationAnalysis CHR Data

l Import UMTS NetworkGeographic ObservationAnalysis MR Data

Manual creation

CDMA UplinkInterferenceRanking Analysis

Import CDMA UplinkInterference Analysis - TopNAnalysis Data

Manual creation

CDMA UplinkInterferenceSpectrum Analysis

Import CDMA UplinkInterference Analysis -Spectrum Analysis Data

Manual creation

CDMA Intra-FrequencyNeighboring CellAnalysis

l Import CDMA Intra-Frequency NeighboringCell Analysis Data (1X)

l Import CDMA Intra-Frequency NeighboringCell Analysis Data(EVDO)

Manual creation

CDMA ComplaintAnalysis Support

- -

CDMA PilotPollution Analysis

l Import CDMA PilotPollution Analysis Data(1X)

l Import CDMA PilotPollution Analysis Data(EVDO)

Manual creation

CDMA CoverageAnalysis

l Import CDMA CoverageAnalysis Data (1X)

l Import CDMA CoverageAnalysis Data (EVDO)

Manual creation

CDMA CellPerformanceAnalysis

Import CDMA CellPerformance Analysis Data

Manual creation

CDMA VIPAnalysis

Import CDMA VIP analysisdata import function

Manual creation

LTE CoverageAnalysis

Import LTE CoverageAnalysis Data

Manual creation

LTE VIP Analysis Import LTE VIP AnalysisData

Manual creation



72

Analysis TaskType


LTE TerminalInventory AnalysisTasks

Import LTE TerminalInventory Analysis Data

Manual creation

LTE CellPerformanceAnalysis

Import LTE Cell PerformanceAnalysis Data

Manual creation

LTE ComplaintAnalysis Support

- -

LTE Cell FaultDiagnosisAnalysis

- -

Procedure




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 6-6.

3. Select the execution type of the data import task from Execution Type. You can only selectPeriodic.



NOTE

Begin Time must be later than the current server time.

2. Set the task execution period in Period Setting.


----End

Follow-up ProcedureYou can select a data import task from the task list in the Task Management window and thenperform operations as required.



73


Delete a task Click Delete.NOTEl 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 orresume a task

Perform operations in either of the following modes:l Manual mode

Right-click the task, and then choose Suspend or Resume fromthe shortcut menu.

l Automatic modeRight-click the task, and then choose Timely Suspend/Resumefrom the shortcut menu. In the Timely Suspend/Resume dialogbox, set Suspend Time and Resume Time.

NOTEOnly the tasks in the Idle state can be suspended, and only the tasks in theSuspend state can be resumed.

Cancel the executionof a task

Right-click the task, and then choose Cancel from the shortcut menu.After the operation is successful, the task status is changed fromRunning to Idle.NOTE

Only the tasks in the Running state can be cancelled.

6.3.3 Checking the Integrity of Analysis DataThis section describes how to check the integrity of analysis data. Before creating an analysistask, you need to check that the Nastar has imported the required analysis data into the database.


l The data import task is performed.

ContextYou need to query the data of different types according to the type of an analysis task. Table6-7 shows the mapping between analysis task types and data types.

Table 6-7 Mapping Between Analysis Task Types and Data Types

Analysis Task Type Data Type

GSM MR Analysis Task GSM configuration data and GSM MR analysis data

GSM Neighboring CellAnalysis Task

GSM configuration data, GSM neighboring cell analysis dataand engineering parameters



74


GSM/UMTS NeighboringCell Analysis Task

GSM configuration data, GSM/UMTS neighboring cellanalysis data and engineering parameters

GSM Frequency AnalysisTask

GSM configuration data, GSM frequency analysis data andengineering parameters

GSM Uplink InterferenceAnalysis Task

GSM configuration data and GSM uplink interferenceanalysis data

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

GSM Complaint AnalysisSupport Task

GSM configuration data and engineering parameters

GSM Cell PerformanceAnalysis Task

GSM configuration data and GSM cell performance analysisdata

GSM Terminal InventoryAnalysis Task

GSM configuration data and GSM terminal inventoryanalysis data

GSM Network GeographicAnalysis Task

GSM configuration data, property matrix, GSM networkgeographic observation CHR analysis data, GSM networkgeographic observation MR analysis data, and engineeringparameters

UMTS Uplink InterferenceAnalysis Task

UMTS configuration data and UMTS uplink interferenceanalysis data

UMTS Intra-FrequencyNeighboring Cell AnalysisTask

UMTS configuration data, UMTS neighboring cell analysisdata and engineering parameters

UMTS/GSM NeighboringCell Analysis Task

UMTS configuration data, UMTS/GSM neighboring cellanalysis data and engineering parameters

UMTS Coverage AnalysisTask

UMTS configuration data and UMTS coverage analysis data

UMTS VIP Analysis Task UMTS configuration data and UMTS VIP analysis data andengineering parameters

UMTS Complaint AnalysisSupport Task

UMTS configuration data and engineering parameters

UMTS Pilot PollutionAnalysis Task

UMTS configuration data and UMTS pilot pollution analysisdata

UMTS Cell PerformanceAnalysis Task

UMTS configuration data and UMTS cell performanceanalysis data

UMTS Terminal InventoryAnalysis Task

UMTS configuration data and UMTS terminal inventoryanalysis data



75


UMTS Network GeographiAnalysis Task

UMTS configuration data, property matrix, UMTS networkgeographic observation CHR analysis data, UMTS networkgeographic observation MR analysis data, and engineeringparameters

CDMA Uplink InterferenceAnalysis Task

CDMA configuration data, CDMA uplink interferenceranking analysis data, and CDMA uplink interferencespectrum analysis data

CDMA Intra-FrequencyNeighboring Cell AnalysisTask

CDMA configuration data and CDMA neighboring cellanalysis data (1X services), CDMA neighboring cell analysisdata (EVDO services) and engineering parameters

CDMA Complaint AnalysisSupport Task

CDMA configuration data and engineering parameters

CDMA Pilot PollutionAnalysis Task

CDMA configuration data and CDMA pilot pollutionanalysis data (1X services) or CDMA pilot pollution analysisdata (EVDO services)

CDMA Coverage AnalysisTask

CDMA configuration data and CDMA coverage analysis data(1X services) or CDMA coverage analysis data (EVDOservices)

CDMA Cell PerformanceAnalysis Task

CDMA configuration data and CDMA cell performanceanalysis data

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

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

LTE VIP Analysis Task LTE configuration data and LTE VIP analysis data andengineering parameters

LTE Terminal InventoryAnalysis Task

LTE configuration data and LTE terminal inventory analysisdata

LTE Cell PerformanceAnalysis Task

LTE configuration data and LTE cell performance analysisdata

LTE Complaint AnalysisSupport Task

LTE configuration data and engineering parameters

LTE Cell Fault DiagnosisAnalysis Task

-

Procedure

Step 1 Double-click System Function > Data Query from the navigation tree in the Analysis TaskManagement window. The Query Data window is displayed.



76

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 6-7.

Step 3 Set Select Condition.Select Condition is optional. You can set the time range only after selecting Is time limitrequired.

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

6.4 Creating GSM MR Analysis TasksThis section describes how to create GSM MR analysis tasks. After you create a GSM MRanalysis task, the Nastar periodically analyzes GSM performance data, GSM configuration data,and engineering parameters in the Nastar database. By querying analysis results, you can learnabout the status of the entire radio network so that problems can be located and solved efficiently.

Prerequisitesl You have logged in to the Nastar client.l Analysis data and configuration data are imported into the Nastar database. For details, see

6.3.3 Checking the Integrity of Analysis Data.

Contextl An analysis task can be performed once or periodically. A periodic task is performed by

days, or weeks.l 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.

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 TaskManagement 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 windowand right-click New. The New Task dialog box is displayed.

Step 2 Set the basic task information such as Task Name, Task Type, and Remarks.

Step 3 Click Next.



77

Step 4 Select BSC 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 therequired object.

Step 5 On the Set parameters tab page, set the parameters related to the abnormal TRXs for the GSMMR analysis task.

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,thestart time of the task and busy hour range.

Task Type is set to Period Set Set Periodic Task, Set Busy Hour forPeriodic Task.

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, bluecells indicate that theme data at the current time is normal, yellow cells indicate that configurationdata at the current time is normal, and green cells indicate that both theme data and configurationdata at the current time is normal. The method for specifying the time range varies according tothe selected analysis object.

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 *** AnalysisData tab page.

l Method 2: Specify the analysis time range bypressing and dragging the mouse in the table on the*** Analysis Data tab page. The time in TimeRange will automatically refresh to the specifiedtime.

NOTEl If no theme data is available in the specified time range,

and if no configuration data is available before the endtime for an analysis task, the task will fail.

l Press and hold the mouse to specify the continuous periodin a line of the table on the *** Analysis Data tab page.

l Press and hold Ctrl+Shift to select multiple lines of datafor analysis.

2. Set Execution Delay.

NE Group is selected Set Time Range and Execution Delay.



78

Step 9 Click Complete.

----End

Follow-up ProcedureYou can select an analysis task from the task list in the Analysis Task Management windowand then perform operations as required.

TIPYou can choose Theme Function > *** Analysis Task from the navigation tree on the left of the AnalysisTask Management window.

Here, *** indicates the name of a specific analysis task.


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

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

Suspended a taskSelect a task in the Waiting state, and click , or right-clickSuspended.

Restore a suspendedtask Select a task in the Suspended state, and click , or right-click

Resume.

Save as the tasks Right-click Save As to export the task information.

RefreshClick , or right-click Refresh to refresh the task status.

Related References6.10.3 Parameters for Creating and Modifying GSM MR Analysis Tasks

6.5 Querying GSM MR Overview Analysis ResultsThis section describes how to query the GSM measurement report (MR) overview report. AnMR report includes the following information about a measurement cell: uplink and downlinklevels, uplink and downlink quality, timing advance (TA), and link balance. You can learn theTRX and cell coverage, radio link quality, and subscriber distribution directly from theinformation in the analysis results. A GSM MR overview report consists of GSM BSC analysisresults, GSM cell group analysis results, TopN TRX analysis results, and GSM MR themeanalysis results.



79

Follow-up ProcedureNOTE

When you check a theme analysis result in the GSM MR Analysis Task, GSM Cell Performance AnalysisTask, GSM Uplink Interference Analysis Task, GSM Frequency Analysis Task, or GSM Neighboring CellAnalysis Task, the Nastar can enable you to navigate to the analysis results of different tasks if other themeshave analysis results of specified cells and time segments. Right-click a cell and choose Jump To > GSM*** Analysis Task from the shortcut menu to view the analysis results ( *** indicates the five analysistasks).

6.5.1 Querying GSM BSC Analysis ResultsThis function describes how to query GSM BSC analysis results. Based on each radio linkcounter, you can query the number of TopN TRXs, number of TRXs that meet the filterconditions and average value of each radio link counter of a BSC to be analyzed. In addition,you can query the average value of each radio link counter of each TopN TRX and TRX thatmeet the filter condition.

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM MR analysis task reaches 100%.l During the creation of the GSM MR analysis task, BSC is selected on the Ne Selection tab

page. For details, see 6.4 Creating GSM MR Analysis Tasks.

Procedure

Step 1 Choose Theme Function > GSM MR Analysis Task from the navigation tree on the left of theAnalysis Task Management window.If you choose Theme Function, the task list on the right displays all the analysis tasks.

Step 2 Select a task from the task list in the upper right pane.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.If a theme analysis task is executed more than 30 days, only result records of the latest 30 daysare displayed in the analysis result list. For example, the start time of a created MR analysis taskis September 1, 2010. If the task is executed more than 30 days (if the task execution period is12 hours, the task is executed more than 60 times), the result record on September 1, 2010 willbe deleted and the result records of 30 days from September 2, 2010 to October 1, 2010 arereserved when the task is executed on October 1, 2010.

Step 4 Double-click an analysis result, or right-click an analysis result and choose View AnalysisTask from the shortcut menu. The GSM MR Overview Report window is displayed.

NOTEOnly the analysis result whose Result Status is Successful can be queried.

Step 5 In the GSM MR Overview Report window, query BSC overview results.l You can perform the following operations to query the number of TopN TRXs, number of

TRXs that meet the filter conditions and average value of each radio link counter of eachBSC.

1. Click the BSC Overview Report node in the navigation tree in the GSM MR OverviewReport window.



80

2. In Area (3), query the number of TopN TRXs and number of TRXs that meet the filterconditions of each BSC. In Area (3), the columns from TRX Count for Average UplinkReceive Quality to TRX Count for Uplink Interference display the number of TopNTRXs;the seven columns that follow TRX Count for Uplink Interference display thenumber of TRXs that meet the filter conditions..In Area (4), query the average value of each radio link counter of each BSC.In Areas (3) and (4), you can press Ctrl+F to search for and locate an object.In Area (5), view the information selected in Areas (3) and (4) in a bar chart. You candouble-click the chart to zoom in and then double-click the chart again to restore it tothe normal size.In Area (5), you can right-click the bar chart and then choose an option from the shortcutmenu to perform the corresponding operation, such as modifying the attributes of thechart, and resizing, saving, and printing the chart.For details about the area division, see 6.10.1 Interface Description: GSM MRAnalysis.

l You can perform the following operations to query the average value of each radio linkcounter of each TopN TRX and each TRX that meet the filter condition.

1. In the GSM MR Overview Report window, click the BSC Overview Report node inthe navigation tree, and then select a counter node.

2. Perform appropriate operations as required.

If... Then...

Compared with themeasurement result ofthe last period, thenumber of TopNTRXs or the numberof TRXs that meet thefilter conditions for acounter increases.

An UP arrow is displayed next to the corresponding countername in Area (2) and the number of increased TopN TRXsor TRXs that meet the filter conditions is displayed.The information about the increased TopN TRXs isdisplayed in Area (3) and highlighted in yellow.



81

If... Then...

A counter node isselected

a. Select the information about a TopN TRX in Area (3).Area (3) displays the information about the TopN TRXsthat meet the condition of the counter.

b. In Area (4), query the average value of each radio linkcounter of all TRXs in the cell where the TopN TRXselected in Area (3) is located in the first line; then, querythe average value of each radio link counter of each TRXin the cell where the selected TopN TRX is located inother lines.In Area (5), view the information selected in Areas (3)and (4) in a bar chart.l In Area (5), you can right-click the bar chart and then

choose an option from the shortcut menu to performthe corresponding operation, such as modifying theattributes of the chart, and resizing, saving, andprinting the chart.

l You can double-click the bar chart in Area (5) tozoom in and then double-click the chart again torestore it to the normal size.

In Areas (3) and (4), you can press Ctrl+F to search for and locate an object.

For details about the area division, see 6.10.1 Interface Description: GSM MRAnalysis.

----End

Follow-up ProcedureYou can right-click in Areas (3) and (4) and then choose Save As from the shortcut menu tosave the current query results as a .csv file.

Related References6.10.4 Parameters for Querying GBSC Reports

6.5.2 Querying GSM Cell Group Analysis ResultsThis section describes how to query GSM cell group analysis results. Based on each radio linkcounter, you can query the number of TopN TRXs, number of TRXs that meet the filterconditions and average value of each radio link counter in the cell groups to be analyzed. Inaddition, you can query the average value of each radio link counter of each TopN TRX andTRX that meet the filter condition.


l The progress bar of the GSM MR analysis task reaches 100%.



82

l During the creation of the GSM MR analysis task, Cell Group is selected on the NeSelection tab page. For details, see 6.4 Creating GSM MR Analysis Tasks.

Procedure

Step 1 Click the GSM MR Analysis Task node in the navigation tree on the left of the Analysis TaskManagement window.If you choose Theme Function, the task list on the right displays all the analysis tasks.





Step 5 View the cell group report in the GSM MR Overview Report window.l You can perform the following operations to query the number of TopN TRXs, number of

TRXs that meet the filter conditions and average value of each radio link counter in each cellgroup.

1. Click the Cell Group Overview Report node in the navigation tree in the GSM MROverview Report window.

2. In Area (3), query the number of TopN TRXs and number of TRXs that meet the filterconditions in each cell group. In Area (3), the columns from TRX Count for AverageUplink Receive Quality to TRX Count for Uplink Interference display the numberof TopN TRXs; the seven columns that follow TRX Count for Uplink Interferencedisplay the number of TRXs that meet the filter conditions.In Area (4), query the average value of each radio link counter in each cell group.In Areas (3) and (4), you can press Ctrl+F to search for and locate an object.In Area (5), view the information selected in Areas (3) and (4) in a bar chart. You candouble-click the chart to zoom in and then double-click the chart again to restore it tothe normal size.In Area (5), you can right-click the bar chart and then choose an option from the shortcutmenu to perform the corresponding operation, such as modifying the attributes of thechart, and resizing, saving, and printing the chart.For details about the area division, see 6.10.1 Interface Description: GSM MRAnalysis.

l You can perform the following operations to query the average value of each radio linkcounter of each TopN TRX and TRX that meet the filter condition.

1. In the GSM MR Overview Report window, click the Cell Group Overview Reportnode in the navigation tree, and then select a counter node.



83

The name of a counter node consists of the name of a radio link counter and the numberof TopN TRXs.

2. Perform appropriate operations as required.

If... Then...

Compared with themeasurement result ofthe last period, thenumber of TopNTRXs or the numberof TRXs that meet thefilter conditions for acounter increases.

An UP arrow is displayed next to the corresponding countername in Area (2) and the number of increased TopN TRXsor TRXs that meet the filter conditions is displayed.The information about the increased TopN TRXs isdisplayed in Area (3) and highlighted in yellow.

A counter node isselected

a. Select the information about a TopN TRX in Area (3).Area (3) displays the information about the TopN TRXsthat meet the condition of the counter.

b. In Area (4), query the average value of each radio linkcounter of all TRXs in the cell where the TopN TRXselected in Area (3) is located in the first line; then, querythe average value of each radio link counter of each TRXin the cell where the selected TopN TRX is located inother lines.In Area (5), view the information selected in Areas (3)and (4) in a bar chart.l In Area (5), you can right-click the bar chart and then

choose an option from the shortcut menu to performthe corresponding operation, such as modifying theattributes of the chart, and resizing, saving, andprinting the chart.

l You can double-click the bar chart in Area (5) tozoom in and then double-click the chart again torestore it to the normal size.

In Areas (3) and (4), you can press Ctrl+F to search for and locate an object.For details about the area division, see 6.10.1 Interface Description: GSM MRAnalysis.

For details about the parameters, see 6.10.5 Parameters for Querying the GSM Cell GroupReports.

----End


Related References6.10.5 Parameters for Querying the GSM Cell Group Reports



84

6.5.3 Querying GSM TopN TRX Analysis ResultsThis section describes how to query GSM TopN TRXs. You can query the information aboutTopN TRXs (currently, N equals to 10) with the poorest performance indicated by a selectedradio link counter.

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM measurement report (MR) analysis task reaches 100%.

Procedure






Step 5 Click a counter node under the TopN node in the navigation tree in the GSM MR OverviewReport window, and then query the analysis results of TopN TRXs.l The information about the selected N TRXs with poorest performance is displayed in Area

(3). N indicates the value of TopN that is set on the Parameter Settings tab during creationof a GSM MR analysis task. If TopN is set to 20, the information about the selected 20 TRXswith poorest performance is displayed.In Areas (3) and (4), you can press Ctrl+F to search for and locate an object.You can select the information about one TopN TRX in Area (3). Then, in Area (4), you canquery the average value of each radio link counter of all TRXs in the cell where the TopNTRX selected in Area (3) is located in the first line and query the average value of each radiolink counter of each TRX in the cell where the TopN TRX is located in other lines. In addition,you can query the information selected in Areas (3) and (4) in the bar chart in Area (5).

l You can double-click the bar chart in Area (5) to zoom in and then double-click the chartagain to restore it to the normal size.In Area (5), you can right-click the bar chart and then choose an option from the shortcutmenu to perform the corresponding operation, such as modifying the attributes of the chart,and resizing, saving, and printing the chart.

l For details about the area division, see 6.10.1 Interface Description: GSM MR Analysis.



85

l For details about parameters, see 6.10.6 Parameters for Querying the GSM TopN TRXReports.

----End


Related References6.10.6 Parameters for Querying the GSM TopN TRX Reports

6.5.4 Querying GSM MR Filter Condition Analysis ReportsThis section describes how to query the analysis reports of the GSM MR filter condition analysis.You can query the information about all TRXs that meet the conditions of an MR filter condition.

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM MR analysis task reaches 100%.

Procedure

Step 1 Click the GSM MR Analysis Task node from the navigation tree in the Task Managementwindow.If you choose Theme Function, the task list on the right displays all the analysis tasks.





Step 5 Click a theme node under the Filter Condition node in the navigation tree in the GSM MROverview Report window, and then query the theme analysis results.l Area (3) displays the information about all TRXs that meet the filter conditions.

In Areas (3) and (4), you can press Ctrl+F to search for and locate an object.You can select the information about a TRX that meet the filter condition in Area (3). Then,in Area (4), you can query the average value of each radio link counter of all TRXs in thecell where the TRX selected in Area (3) is located in the first line and query the average value



86

of each radio link counter of each TRX in the cell where the TRX is located in other lines.In addition, you can query the information selected in Areas (3) and (4) in the bar chart inArea (5).

l You can double-click the bar chart in Area (5) to zoom in and then double-click the chartagain to restore it to the normal size.In Area (5), you can right-click the bar chart and then choose an option from the shortcutmenu to perform the corresponding operation, such as modifying the attributes of the chart,and resizing, saving, and printing the chart.

l For details about the area division, see 6.10.1 Interface Description: GSM MR Analysis.l For details about parameters, see 6.10.6 Parameters for Querying the GSM TopN TRX

Reports.

----End


Related References6.10.7 Parameters for Querying the GSM MR Filter Condition Analysis Reports

6.6 Querying GSM MR ResultsThis section describes how to query GSM measurement report (MR) results. Through thisfunction, you can query the detailed information about TopN TRXs and TRXs that meet thefilter conditions of the cell where multiple TopN TRXs or TRXs that meet the filter conditionsexist.

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM MR analysis task reaches 100%.

Procedure

Step 1 Choose Theme Function > GSM MR Analysis Task from the navigation tree on the left of theAnalysis Task Management window.If you choose Theme Function, the task list on the right displays all the analysis tasks.





87

Step 4 Right-click the analysis result, and then choose MR Query from the shortcut menu.


Step 5 Select one or multiple cells to be queried in the displayed window.

Step 6 Click OK. The GSM MR Query Results window is displayed.

Step 7 Query analysis results in the GSM MR Query Results window.

l In Area (7), query the average value of each radio link counter by cell.

In Areas (7) and (8), you can press Ctrl+F to search for and locate an object.

l Select the information about a cell in Area (7), view the average value of each radio linkcounter of all TRXs of the selected cell in Area (8), and then view the information selectedin Areas (7) and (8) in a bar chart in Area (9).

l You can double-click the bar chart in Area (9) to zoom in and then double-click the chartagain to restore it to the normal size.

In Area (9), you can right-click the bar chart and then choose an option from the shortcutmenu to perform the corresponding operation, such as modifying the attributes of the chart,and resizing, saving, and printing the chart.

l For details about the area division principles, see 6.10.1 Interface Description: GSM MRAnalysis. For details about parameters, see 6.10.8 Parameters for Querying the MRAnalysis Results of GSM Cells.

----End


Related References6.10.8 Parameters for Querying the MR Analysis Results of GSM Cells

6.7 Comparing GSM MR Analysis ResultsThis section describes how to compare the GSM Measurement Report (MR) analysis results.After the network is optimized or the equipment is upgraded, you can compare two GSM MRanalysis results generated in two time segments to check the differences between the values ofthe same counters in two time segments. This function helps you learn about the detailed networkperformance differences in two time segments and quickly evaluate the network optimizationeffect.


l Task Type of the GSM MR analysis task is set to Cycle Task. For details, see 6.4 CreatingGSM MR Analysis Tasks.



88

Procedure



Step 3 Select two analysis results from the result list in the lower right pane.If a theme analysis task is executed more than 30 days, only result records of the latest 30 daysare displayed in the analysis result list. For example, the start time of a created MR analysis taskis September 1, 2010. If the task is executed more than 30 days (if the task execution period is12 hours, the task is executed more than 60 times), the result record on September 1, 2010 willbe deleted and the result records of 30 days from September 2, 2010 to October 1, 2010 arereserved when the task is executed on October 1, 2010.

Step 4 Right-click the analysis results, and then choose Comparison Analysis from the shortcut menu.


Step 5 Select one or multiple cells to be queried in the displayed window.

Step 6 Click OK. The GSM MR Comparison Analysis window is displayed.

Step 7 Perform the following operations according to the actual configuration.

If... Then...

Ne Selection for the current GSM MRanalysis task is set to BSC

1. Select Cell, BSC, or All from the upper area inthe navigation tree.

2. Select one or multiple objects from the navigationtree.

Ne Selection for the current GSM MRanalysis task is set to Cell Group

1. Select All, Cell Group, or Cell from the upperarea in the navigation tree.

2. Select one or multiple objects from the navigationtree.

Press Ctrl+F to search for and locate an object in the navigation tree.

Step 8 Click OK. The GSM MR Comparison Report dialog box is displayed.

Step 9 View analysis results in the GSM MR Comparison Report window.l View the difference between radio link counters of each object in two time segments in Area

(12).In the list of Area (12), the counter display color varies according to the counter status. If thecounter deteriorates, it is displayed in red. If the counter is normal, it is displayed in green.If no measurement result for the counter is obtained or that the counter status is not changed,the counter is displayed in gray.

l After you select an object from Area (12), the statistical information about the selected objectis displayed in a bar chart in Area (13).



89

l Double-click the bar chart in Area (13) to zoom in and then double-click the chart again torestore it to the normal size.In Area (13), you can right-click the chart and then choose an option from the shortcut menuto perform the corresponding operation, such as modifying the attributes of the chart, andresizing, saving, and printing the chart.

l For details about the area division principles, see 6.10.1 Interface Description: GSM MRAnalysis.

l For details about the related parameters, see 6.10.9 Parameters for Comparing GSM MRAnalysis Results.

----End

Follow-up ProcedureExport query results. You can right-click in Areas (12) and (13) and then choose Save As fromthe shortcut menu to save the current query results as a .csv file.

Related References6.10.9 Parameters for Comparing GSM MR Analysis Results

6.8 Exporting GSM MR Overview ReportsThis section describes how to export GSM MR overview reports. You can export GSM MRoverview analysis results as .csv files.

Prerequisitesl You have logged in to the Nastar client.l The GSM MR Overview Report is opened. For details, see 6.5.1 Querying GSM BSC

Analysis Results.

ContextYou can export GSM MR overview reports in either of the following mode:l Exporting MR analysis results of all the analyzed cellsl Exporting MR analysis results of all the analyzed frequencies

Procedurel Export MR analysis results of all the cells.

1. Click in the GSM MR Overview Report window. The Save dialog box isdisplayed.

2. 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. Youcan 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 oneexport tasks are created, other tasks are in the waiting state and can be executedonly after the running task is executed completely or canceled.



90

– You can click on the right of the progress bar to cancel an export task in thewaiting or running state so that the task is terminated and deleted from the tasklist. You can click on the right of the progress bar to delete an export task inthe 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 informationabout an export task in the completed state.

l Export MR analysis results of all the frequencies.

1. Click in the GSM MR Overview Report window. The Save dialog box isdisplayed.

2. 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. Youcan 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 oneexport tasks are created, other tasks are in the waiting state and can be executedonly after the running task is executed completely or canceled.

– You can click on the right of the progress bar to cancel an export task in thewaiting or running state so that the task is terminated and deleted from the tasklist. You can click on the right of the progress bar to delete an export task inthe 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 informationabout an export task in the completed state.

----End

6.9 Technical Specifications for GSM MR AnalysisThis section describes the technical specifications for GSM MR analysis.

Item Task Management Capacity

Number of NE objects supportedby one analysis task

<= 1,000 cells

Number of concurrent tasks <= 5NOTE

The Nastar server can run a maximum of ten analysis taskssimultaneously. If only a certain type of theme analysis tasks arerunning on the Nastar, a maximum of five analysis tasks of thistype can be executed simultaneously.

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 becreated of one task type

<= 50



91

6.10 Reference for the GSM MR Analysis GUIThis section describes the interface for GSM MR analysis and the relevant parameters. Beforeperforming relevant operations, familiarize yourself with GSM MR analysis functions.

6.10.1 Interface Description: GSM MR AnalysisThis section describes the interfaces for GSM MR analysis. The interfaces for GSM MR analysisconsist of MR Overview Report, MR Query, and MR Comparison Analysis. Beforeperforming relevant operations, familiarize yourself with the rules for dividing areas on theinterface.

Interface for MR Report and Interface DescriptionThe MR comprehensive analysis results can be displayed in table or in histogram mode, as shownin Figure 6-2.

Figure 6-2 MR Overview Report


(1) Button area Two buttons are provided to export all thecell data and all the TRX data.



92


(2) Navigation tree of MR overview report You can accurately locate the objects of theMR report on the navigation tree.

(3) Area for TopN TRXs or TRXs that meetthe filter conditions

Displays the information about the TopNTRXs or TRXs that meet the filter conditionsin table.

Different information is displayed indifferent situations. For details, see thedescription of relevant task pages.

(4) Area for TRXs Displays the information about the TRXs intable.

Different information is displayed indifferent situations. For details, see thedescription of relevant task pages.

The system supports the function ofhighlighting MR summary reports indifferent colors. If a TRX is faulty, this TRXis highlighted in red.

(5) Area for counter charts Displays the counter information about theselected objects in histogram mode.

(6) Task information list Displays the basic information about thistask in table.

Interface for Displaying MR Results and Interface DescriptionThe MR results of a cell can be displayed in table or in histogram mode, as shown in Figure6-3.



93

Figure 6-3 MR Query Result


(7) Area for Cells Displays the MRs of all cells in table.

(8) Area for TRXs Displays the values of all TRXs of the selected cells in table.

The system supports the function of highlighting MR results incolors. If a TRX is faulty, this TRX is highlighted in red.

(9) Area for counter charts Displays the counter information about the selected objects inhistogram mode.

(10) Task information list Displays the basic information about this task in table.

(11) Cell information list Displays the basic information about the cells corresponding tothe selected TRXs in table.

Interface for MR Comparison Analysis and Interface DescriptionThe MR comparison results of a cell can be displayed in table or in histogram mode, as shownin Figure 6-4.



94

Figure 6-4 MR Comparison Report


(12) Area for counter summary information Displays the differences of all summarizedcounters of each object within two periods intable.

The Nastar can display the compared countervalues that indicate performance trends in thetable in colors. Red indicates that theperformance deteriorates; green indicates thatthe performance improves; gray indicates thatno comparison result exists or that theperformance does not change.

(13) Area for counter charts Displays the counter information about theselected objects in histogram mode.




95

Parameter DescriptionParameter Value Range Description



ExecutionType







Runimmediately



ExecutionInterval



ExecutionTimes








96




Collect AllNE



Collect ByNE Type











97

6.10.3 Parameters for Creating and Modifying GSM MR AnalysisTasks

This section describes the parameters for creating and modifying GSM MR analysis tasks. Youcan refer to the description when creating or modifying a GSM MR analysis task.

Task Common InformationParameter Description

Task Name Indicates the name of an analysis task.The value range is as follows:l A maximum of 60 charactersl Characters not allowed: ` ~ ! @ # $ % ^ & * ( ) + = { } [ ] \ | ; ' : , . ? / < >

"l Unique and not nulll Case sensitive

Task Type Choose the task type from the navigation tree.

Remarks Provides the description of the task.Value range:l A maximum of 200 charactersl The following characters are not allowed: ~ ! # $ % ^ * + = | \ / , ' `

Task Time InformationParameter Description

Task Type l One-time: The system executes the created tasks only once atthe specified time.

l Period: The system executes the created tasks periodically atthe preset time.

One-timetask

TimeRange

Only the data generated between the start time and the end timewill be analyzed.The start time should precede the end time, and the end timeshould precede the locale system time.

Delayed If you do not select it, the system will execute the taskimmediately.If you select it, the system will execute the task at the time of theExecution Delay.

Execution Delay

Indicates the specified execution time of the task.The parameter should not precede the end time of the TimeRange.



98


Periodictask

StartTime

Indicates date for starting a task. The start time should be laterthan the current server time.l If the period is one hour, the task is performed at 00:00 at the

set date.l If the period is one day, the task is performed at 00:00 at the

next day after the set date.l If the period is one week, the task is performed at 00:00 at the

first day in the next week after the set date.

Execution Delay

Indicates the time delayed for running a task.Value range: 1 to 24. Unit: hour.The parameter must be used with Start Time. After this parameteris set, the Nastar will execute the task certain hours later than00:00 of the specified day in Start Time.NOTE

To ensure that data can be obtained completely after the task execution,you need to set the time of execution delay.

Period Indicates the interval between periodic tasks.

Numberofexecution times

Indicates the times that a periodic task is executed. If thisparameter is set to 0, you can infer that the task is executed all thetime.Value range: 0 to 9999. This parameter is valid for only periodictasks.

Busy timesetting

All Day The data generated in the whole day will be analyzed.

BusyHour

Only the data generated in the selected period of one day will beanalyzed.

NE Selection InformationParameter Description

NE If you select this option, the navigation tree displays all the NEs of the entirenetwork.

NE Group If you select this option, the navigation tree displays all the NE groups ofthe entire network.



99

Parameter Setting InformationParameter Description

Uplink Quality ≥ X MR ofa Value (%) ≥ Y, MRs ≥ Z

If the number of MRs, in which the level of uplink quality isnot smaller than X, is greater than Y% of the total number ofMRs, the TRX is problematic, and the MRs is not smaller thanZ.X indicates the level of uplink quality. It is an integer between1 and 7. The default value is 4.Y indicates the threshold. It is an integer from 1 to 100. Thedefault value is 10.Z indicates the threshold. It is an integer from 1 to 9999. Thedefault value is 200.

Downlink Quality ≥ X MRof a Value (%) ≥ Y, MRs≥ Z

If the number of MRs, in which the level of downlink qualityis not smaller than X, is greater than Y% of the total numberof MRs, the TRX that meet the filter condition, and the MRsis not smaller than Z.X indicates the level of downlink quality. It is an integerbetween 1 and 7. The default value is 4.Y indicates the threshold. It is an integer from 1 to 100. Thedefault value is 10.Z indicates the threshold. It is an integer from 1 to 9999. Thedefault value is 200.

Uplink Level ≤ X MR ofdBm (%) ≥ Y, MRs ≥ Z

If the number of MRs, in which the value of uplink level is notgreater than X (dBm), is greater than Y% of the total numberof MRs, the TRX that meet the filter condition, and the MRsis not smaller than Z.X indicates the value of uplink level. It can be -100, -95, -90,-85, -80, -75, or -70. The default value is -90.Y indicates the threshold. It is an integer from 1 to 100. Thedefault value is 70.Z indicates the threshold. It is an integer from 1 to 9999. Thedefault value is 200.

Downlink Level ≤ X MR ofdBm (%) ≥ Y, MRs ≥ Z

If the number of MRs, in which the value of downlink level isnot greater than X (dBm), is greater than Y% of the totalnumber of MRs, the TRX that meet the filter condition, andthe MRs is not smaller than Z.X indicates the value of downlink level. It can be -100, -95,-90, -85, -80, -75, or -70. The default value is -90.Y indicates the threshold. It is an integer from 1 to 100. Thedefault value is 40.Z indicates the threshold. It is an integer from 1 to 9999. Thedefault value is 200.



100


TA ≥ X MR of a Value (%)≥ Y, MRs ≥ Z

If the number of MRs, in which the TA value is not smallerthan X, is greater than Y% of the total number of MRs, the TRXthat meet the filter condition, and the MRs is not smaller thanZ.X indicates the TA value. It is an integer from 1 to 30 or canbe 32, 34, 36, 38, 40, 45, 50, 55, or 64. The default value is 6.Y indicates the threshold. It is an integer from 1 to 100. Thedefault value is 50.Z indicates the threshold. It is an integer from 1 to 9999. Thedefault value is 200.

Downlink Level - UplinkLevel < X MR of dB (%) ≥Y, MRs ≥ Z

If the number of MRs, in which the difference between thedownlink level and uplink level is smaller than X (dB), isgreater than Y% of the total number of MRs, the TRX that meetthe filter condition, and the MRs is not smaller than Z.X indicates the level difference. It can be -15, -10, -6, -3, or -1.The default value is -15.Y indicates the threshold. It is an integer from 1 to 100. Thedefault value is 40.Z indicates the threshold. It is an integer from 1 to 9999. Thedefault value is 200.

Downlink Level - UplinkLevel > X MR of dB (%) ≥Y, MRs ≥ Z

If the number of MRs, in which the difference between thedownlink level and uplink level is greater than X (dB), isgreater than Y% of the total number of MRs, the TRX that meetthe filter condition, and the MRs is not smaller than Z.X indicates the level difference. It can be 1, 3, 6, 10, or 15. Thedefault value is 15.Y indicates the threshold. It is an integer from 1 to 100. Thedefault value is 40.Z indicates the threshold. It is an integer from 1 to 9999. Thedefault value is 200.

TopN =X, MRs ≥ Z Indicates the number of TopN counters. You can query theinformation about X TRXs whose performance is the poorestas indicated by the selected counter, and the MRs is not smallerthan Z.X indicates the number of TopN counters. It is an integer from1 to 99. The default value is 99.Z indicates the threshold. It is an integer from 1 to 9999. Thedefault value is 200.

Related Tasks6.4 Creating GSM MR Analysis Tasks



101

6.10.4 Parameters for Querying GBSC ReportsThis section describes the parameters related to querying the GBSC reports. You can refer tothese parameters when querying the GBSC reports.

NOTE

For details about the rules for dividing areas, see 6.10.1 Interface Description: GSM MR Analysis.

Parameters for Querying TRXs on the Entire Network

Area (3) displays the number of TopN TRXs and TRXs that meet the filter conditions in eachGBSC on the entire network. For details, see Table 6-8.

Table 6-8 Parameters related to the TRXs on the entire network (1)


BSC ID Indicates the ID of a BSC.

BSC Name Indicates the name of a BSC, for example, BSC_1.

TRX Count for Average UplinkReceive Quality

Indicates the number of TRXs with the average receivedsignal quality values of the BTSs exceeding thethreshold.

TRX Count for Average DownlinkReceive Quality

Indicates the number of TRXs with the average receivedsignal quality values of the MSs exceeding thethreshold.

TRX Count for Average UplinkReceive Level

Indicates the number of TRXs with the average receivedlevels of the BTSs exceeding the threshold.

TRX Count for Average DownlinkReceive Level

Indicates the number of TRXs with the average receivedlevels of the MSs exceeding the threshold.

TRX Count for Average TADistribution

Indicates the number of TRXs with the values ofAverage TA Distribution exceeding the threshold.

TRX Count for Link Balance Indicates the number of TRXs with the values of LinkBalance exceeding the threshold.

Filter condition Indicates the number of TRXs that meet the filterconditions.

Area (4) displays the information about all the TRXs in each GBSC on the entire network. Fordetails, see Table 6-9.






102



Total Number of MeasurementReports

Indicates the number of MRs transferred over the channel.

Average Uplink Receive Quality Indicates the value of the average received signal quality(full rate) of the BTS.

Average Downlink ReceiveQuality

Indicates the value of the average received signal quality(full rate) of the MS.

Average Uplink Receive Level Indicates the average received level (full rate) of the BTS.

Average Downlink ReceiveLevel

Indicates the average received level (full rate) of the MS.

Average TA Distribution Indicates the weighted average TA that the MS uses toadvance its timings of transmissions to the BTS.

Link Balance Indicates the dB value calculated through this expression:Average received level of the MS - Average receivedlevel of the BTS - Difference between the values of theaverage sensitivity of the MS and BTS.

Parameters for Querying TRXs in a GBSCThe TRX frequencies in the GBSC are sorted by the counter in area (3). For details, see Table6-10.

Table 6-10 Parameters related to the TRXs in a GBSC (1)




Cell ID Indicates the number of the cell that the TRX belongsto.

Cell Name Indicates the name of the cell that the TRX belongs to.

TRX ID Indicates the number of the TRX controlled by the BSC.

TRX Name Indicates the name of the TRX controlled by the BSC.


Indicates the number of MRs transferred over thechannel.

Average Uplink Receive Quality Indicates the average quality of received signals of theBTSs corresponding to the TopN TRXs or TRXs thatmeet the filter conditions controlled by the BSC.



103



Indicates the average quality of received signals of theMSs corresponding to the TopN TRXs or TRXs thatmeet the filter conditions controlled by the BSC.

Average Uplink Receive Level Indicates the average received levels of the BTSscorresponding to the TopN TRXs or TRXs that meetthe filter conditions controlled by the BSC.

Average Downlink Receive Level Indicates the average received levels of the MSscorresponding to the TopN TRXs or TRXs that meetthe filter conditions controlled by the BSC.


Link Balance Indicates the dB value calculated through thisexpression: Average received level of the MScorresponding to the TopN TRX or TRX that meet thefilter condition controlled by the BSC - Averagereceived level of the BTS corresponding to the TopNTRX or TRX that meet the filter condition controlledby the BSC - Difference between the values of theaverage sensitivity of the MS and BTS.

Area (4) displays the information about all TRXs in the cell to which the TopN TRXs or TRXsthat meet the filter conditions selected in Area (3) belong. For details, see Table 6-11.

Table 6-11 Parameters related to the TRXs in a GBSC (2)




Cell ID Indicates the number of the cell that the TRX belongs to.

Cell Name Indicates the name of the cell that the TRX belongs to.

TRX ID Indicates the number of the TRX controlled by the BSC.

TRX Name Indicates the name of the TRX controlled by the BSC.



Average Uplink ReceiveQuality

Indicates the average quality of received signals of the BTSscorresponding to all TRXs.


Indicates the average quality of received signals of the MSscorresponding to all TRXs.



104


Average Uplink Receive Level Indicates the average received levels of the BTSscorresponding to all TRXs.


Indicates the average received levels of the MSscorresponding to all TRXs.


Link Balance Indicates the dB value calculated through this expression:Average received level of the MS corresponding to eachTRX - Average received level of the BTS corresponding toeach TRX - Difference between the values of the averagesensitivity of the MS and BTS.

Parameters related to the basic informationArea (6) displays the information about the queried performance analysis task. For details, seeTable 6-12.

Table 6-12 Parameters related to the task information


Task Name Indicates the name of the queried performance analysis task.

Start Time Indicates the time that the Nastar starts generating a task report.

End Time Indicates the time that the Nastar stops generating a task report.

Task Creator Indicates the creator's name of the queried performance analysistask.

Related Tasks6.5.1 Querying GSM BSC Analysis Results

6.10.5 Parameters for Querying the GSM Cell Group ReportsThis section describes the parameters for querying the GSM cell group reports. You can referto the description when querying the GSM cell group reports.

NOTE


Parameters Related to Querying the TRXs on the Entire NetworkThe number of TopN TRXs and TRXs that meet the filter conditions in each cell group isdisplayed in Area (3). For details, see Table 6-13.



105



NE ID Indicates the ID of a cell group.

Object Name Indicates the name of a cell group, for example, CELL_1.

TRX Count for AverageUplink Receive Quality

Indicates the number of TopN TRXs with the average qualityvalues of the received signals of the BTSs exceeding thethreshold.

TRX Count for AverageDownlink Receive Quality

Indicates the number of TopN TRXs with the average qualityvalues of the received signals of the MSs exceeding thethreshold.

TRX Count for AverageUplink Receive Level

Indicates the number of TopN TRXs with the averagereceived levels of the BTSs exceeding the threshold.

TRX Count for AverageDownlink Receive Level

Indicates the number of TopN TRXs with the averagereceived levels of the MSs exceeding the threshold.

TRX Count for Average TADistribution

Indicates the number of TopN TRXs with the values ofAverage TA Distribution exceeding the threshold.

TRX Count for Link Balance Indicates the number of TopN TRXs with the values of LinkBalance exceeding the threshold.

TRX Count for UplinkInterference

Indicates the number of problematic TRXs meeting therequirements of the Uplink Interference topic.

TRX Count for DownlinkInterference

Indicates the number of problematic TRXs meeting therequirements of the Downlink Interference topic.

TRX Count for Uplink WeakCoverage

Indicates the number of problematic TRXs meeting therequirements of the Uplink Weak Coverage topic.

TRX Count for DownlinkWeak Coverage

Indicates the number of problematic TRXs meeting therequirements of the Downlink Weak Coverage topic.

TRX Count for TRX WeakCoverage

Indicates the number of problematic TRXs meeting therequirements of the Weak TRX Coverage topic.

TRX Count for OverCoverage

Indicates the number of problematic TRXs meeting therequirements of the Over-Distance Coverage topic.

TRX Count for Link Balance(Uplink Problem)

Indicates the number of problematic TRXs meeting therequirements of the Link Balance (Uplink Problem) topic.

TRX Count for Link Balance(Downlink Problem)

Indicates the number of problematic TRXs meeting therequirements of the Link Balance (Downlink Problem) topic.

TRX Count for OtherProblems

Indicates the number of problematic TRXs meeting therequirements of the Other Problem topic.

The calculation result of the TRXs in each cell group on the entire network is displayed in Area(4). For details, see Table 6-14.



106



Cell Group ID Indicates the ID of a cell group.

Cell Group Name Indicates the name of a cell group, for example, CELL_1.

Total Number ofMeasurement Reports



Indicates the average quality of received signals of the BTS.


Indicates the average quality of received signals of the MS.

Average Uplink ReceiveLevel

Indicates the average received level of the BTS.


Indicates the average received level of the MS.

Average TA Distribution Indicates the weighted average TA that is used by the MS toadvance its timings of transmissions to the BTS.

Link Balance Indicates the dB value calculated through this expression:Average received level of the MS - Average received level ofthe BTS - Difference between the values of the averagesensitivity of the MS and BTS.

Parameters Related to Querying TRXs in a Cell GroupThe TRX frequencies meeting the requirements of the topic are displayed in Area (3). For details,see Table 6-15.

Table 6-15 Parameters related to the TRXs in a cell group (1)


Cell Group ID Indicates the ID of a cell group.

Cell Group Name Indicates the name of a cell group, for example, CELL_1.

Cell ID Indicates the ID of the cell where a TRX is located.

Cell Name Indicates the name of the cell where a TRX is located.

TRX ID Indicates the number of a TRX in a cell group.

TRX Name Indicates the name of a TRX in a cell group.





107


Average UplinkReceive Quality

Indicates the average quality of received signals of the BTScorresponding to a TopN TRX or TRX that meet the filterconditions in the cell group.

Average DownlinkReceive Quality

Indicates the average quality of received signals of the MScorresponding to a TopN TRX or TRX that meet the filterconditions in the cell group.

Average UplinkReceive Level

Indicates the average received level value of the BTScorresponding to a TopN TRX or TRX that meet the filterconditions in the cell group.

Average DownlinkReceive Level

Indicates the average received level value of the MS correspondingto a TopN TRX or TRX that meet the filter conditions in the cellgroup.

Average TADistribution

Indicates the weighted average TA that is used by the MS toadvance its timings of transmissions to the BTS.

Link Balance Indicates the dB value, corresponding to a TopN TRX orproblematic TRX in the cell group, calculated through thisexpression: Average received level of the MS corresponding to theTopN TRX or TRX that meet the filter conditions - Averagereceived level of the BTS corresponding to the TopN TRX or TRXthat meet the filter conditions - Difference between the values ofthe average sensitivity of the MS and BTS.

All the TRXs in the cell where the selected TopN TRX or TRX that meet the filter conditionsresides are displayed in Area (3). For details, see Table 6-16.

Table 6-16 Parameters related to the TRXs in a cell group (2)






TRX ID Indicates the number of a TRX in a cell group.

TRX Name Indicates the name of a TRX in a cell group.




Indicates the average quality of received signals of the BTScorresponding to each TRX.



108



Indicates the average quality of received signals of the MScorresponding to each TRX.


Indicates the average received level of the BTS correspondingto each TRX


Indicates the average received level of the MS correspondingto each TRX.


Link Balance Indicates the dB value calculated through this expression:Average received level of the MS corresponding to each TRX- Average received level of the BTS corresponding to eachTRX - Difference between the values of the average sensitivityof the MS and BTS.

Parameters Related to the Basic Information

The information about a selected performance analysis task is displayed in Area (6). For details,see Table 6-17.



Task Name Indicates the name of a selected performance analysis task.

Begin Time Indicates the time when the Nastar starts to generate a taskreport.

End Time Indicates the time when the Nastar stops to generate a taskreport.

Task Creator Indicates the creator's name of the queried performanceanalysis task.

Related Tasks6.5.2 Querying GSM Cell Group Analysis Results

6.10.6 Parameters for Querying the GSM TopN TRX ReportsThis section describes the parameters for querying the GSM TopN TRX reports. You can referto the description when querying the GSM TopN carrier reports.

NOTE




109

Parameters Related to Querying TopN TRXs

In Area (3), the system displays the information about the 10 TRXs of which the selected counterindicates the poorest performance. For details, see Table 6-18.

Table 6-18 Parameters related to the TopN TRXs (1)




Cell ID Indicates the ID of the cell where a TopN TRX is located.

Cell Name Indicates the name of the cell where a TopN TRX is located.

TRX ID Indicates the number of a TopN TRX.

TRX Name Indicates the name of a TopN TRX.


Indicates the number of MRs transferred over the full-ratechannel.


Indicates the average quality of received signals of the BTScorresponding to the TopN TRX.


Indicates the average quality of received signals of the MScorresponding to the TopN TRX.


Indicates the average received level of the BTS correspondingto the TopN TRX.


Indicates the average received level of the MS correspondingto the TopN TRX.


Link Balance Indicates the dB value calculated through this expression:Average received level of the MS corresponding to the TopNTRX - Average received level of the BTS corresponding tothe TopN TRX - Difference between the values of the averagesensitivity of the MS and BTS.

If you select a record of a TopN TRX in Area (3), the system displays the frequencies of all theTRXs in the cell where the selected TopN TRX resides in Area (4). For details, see Table6-19.

Table 6-19 Parameters related to the TopN TRXs (2)





110





TRX ID Indicates the number of a TRX.

TRX Name Indicates the name of a TRX.

Total Number ofMeasurement Reports forFull Rate







Indicates the average received level of the BTS correspondingto each TRX.


Indicates the average received level of the MS correspondingto each TRX.


Link Balance Indicates the dB value calculated through this expression:Average received level of the MS corresponding to each TRX- Average received level of the BTS corresponding to eachTRX - Difference between the values of the averagesensitivity of the MS and BTS.

Parameters Related to the Basic InformationIn Area (6), the system displays the information about a selected performance analysis task. Fordetails, see Table 6-20.



TaskName Indicates the name of a selected performance analysis task.

BEGINTIME Indicates the time when the Nastar starts to generate a taskreport.

ENDTIME Indicates the time when the Nastar stops to generate a taskreport.



111



Related Tasks6.5.3 Querying GSM TopN TRX Analysis Results

6.10.7 Parameters for Querying the GSM MR Filter ConditionAnalysis Reports

This section describes the parameters for querying the reports of the GSM MR filter conditionanalysis. You can refer to the description when querying the GSM MR filter condition analysisreports.

NOTE


Parameters Related to Querying TRXs Involved in Filter Condition Analysis

The information about all the TRXs involved in topic analysis is displayed in Area (3). Fordetails, see Table 6-21.

Table 6-21 Parameters related to the TRXs involved in topic analysis (1)




Cell ID Indicates the ID of the cell where a TRX that meet the filtercondition is located.

Cell Name Indicates the name of the cell where a TRX that meet the filtercondition is located.

TRX ID Indicates the number of a TRX that meet the filter condition.

TRX Name Indicates the name of a TRX that meet the filter condition.




Indicates the average quality of received signals of the BTScorresponding to the TRX that meet the filter condition.


Indicates the average quality of received signals of the MScorresponding to the TRX that meet the filter condition.


Indicates the average received level of the BTS corresponding tothe TRX that meet the filter condition.



112



Indicates the average received level of the MS corresponding tothe TRX that meet the filter condition.


Link Balance Indicates the dB value calculated through this expression:Average received level of the MS corresponding to the TRX thatmeet the filter condition - Average received level of the BTScorresponding to the TRX that meet the filter condition -Difference between the values of the average sensitivity of the MSand BTS.

If you select a record of a TRX that meet the filter condition in Area (3), the frequencies of allthe TRXs in the cell where the selected a TRX that meet the filter condition resides is displayedin Area (4). For details, see Table 6-22.

Table 6-22 Parameters related to the TRXs involved in topic analysis (2)






TRX ID Indicates the number of a TRX.









Indicates the average received level of the BTS corresponding toeach TRX.


Indicates the average received level of the MS corresponding toeach TRX.




113


Link Balance Indicates the dB value calculated through this expression:Average received level of the MS corresponding to each TRX -Average received level of the BTS corresponding to each TRX -Difference between the values of the average sensitivity of the MSand BTS.

Parameters Related to the Basic InformationThe information about a selected performance analysis task is displayed in Area (6). For details,see Table 6-23.



TaskName Indicates the name of a performance analysis task.




Related Tasks6.5.4 Querying GSM MR Filter Condition Analysis Reports

6.10.8 Parameters for Querying the MR Analysis Results of GSMCells

This section describes the parameters for querying the MR analysis results of one or more GSMcells. You can refer to the description when querying the MR analysis results of GSM cells.

NOTE


Parameters Related to Querying TopN TRXs and TRXs that meet the filterconditions in the MR Analysis Results

The calculation result of the TRXs in each cell is displayed in Area (7). For details, see Table6-24.



114

Table 6-24 Parameters related to querying TRXs in the MR analysis results of GSM cells


BSC ID Indicates the ID of the BSC that a TRX belongs to.






Average UplinkReceive Quality

Indicates the calculation result of the average quality values of thereceived signals of the BTSs corresponding to all the TRXs.


Indicates the calculation result of the average quality values of thereceived signals of the MSs corresponding to all the TRXs.

Average UplinkReceive Level

Indicates the calculation result of the average received levels of theBTSs corresponding to all the TRXs.


Indicates the calculation result of the average received levels of theMSs corresponding to all the TRXs.

Average TADistribution

Indicates the weighted average TA that is used by the MS toadvance its timings of transmissions to the BTS.

Link Balance Indicates the dB value calculated through this expression: Averagereceived level of the MSs corresponding to all the TRXs - Averagereceived level of the BTSs corresponding to all the TRXs -Difference between the values of the average sensitivity of the MSand BTS.

If you select a record of a summarized TRX in Area (7), the information about all the TRXs inthe selected cell is displayed in Area (8). For details, see Table 6-25.

Table 6-25 Parameters related to querying TRXs in the MR analysis results of GSM cells (2)


BSC ID Indicates the ID of the BSC that a TRX belongs to.

BSC Name Indicates the name of the BSCs that a TRX of the selected cellbelongs to, for example, BSC_1.



TRX ID Indicates the number of a TRX in the selected cell.




115





Indicates the calculation result of the average received signalquality values of the BTSs corresponding to all the TRXs.


Indicates the calculation result of the average received signalquality values of the MSs corresponding to all the TRXs.


Indicates the calculation result of the average levels of the BTSscorresponding to all the TRXs.


Indicates the calculation result of the average received levels ofthe MSs corresponding to all the TRXs.


Link Balance Indicates the dB value calculated through this expression:Average received level of the MSs corresponding to all the TRXs- Average received level of the BTSs corresponding to all theTRXs - Difference between the values of the average sensitivityof the MS and BTS.

Parameters Related to the Basic InformationThe information about a selected performance analysis task is displayed in Area (10). For details,see Table 6-26.



TaskName Indicates the name of a selected performance analysis task.




The information about the cell corresponding to the selected TRX is displayed in Area (11). Fordetails, see Table 6-27.



116

Table 6-27 Parameters related to the cell information


Cell ID Indicates the internal ID of the cell where the selected TRX islocated.

Cell Name Indicates the name of the cell where the selected TRX islocated.

LAC Indicates the location area code of the cell where the selectedTRX is located.

CI Indicates the ID of the cell where the selected TRX is located.

BCCH Indicates the frequency transmitted on the BCCH.

BCC Indicates the color code of a base station.

NCC Indicates the network color code.

Cell Layer Indicates the layer where the cell is located.

Cell Priority Indicates the cell priority.

Supporting Half Rate Indicates whether half rate is supported.

Frequency Hopping Type Indicates the type of the frequency hopping, such as the RFhopping and baseband frequency hopping.

Supporting GPS Indicates whether the GPRS service is supported.

Supporting EDGE Indicates whether the EDGE service is supported.

Supporting ConcentricCircle

Indicates whether the intelligent underlay-overlay cellfunction is supported.

Base Station Type Indicates the BTS type.

Related Tasks6.6 Querying GSM MR Results

6.10.9 Parameters for Comparing GSM MR Analysis ResultsThis section describes the parameters related to comparing GSM MR analysis results. You canrefer to these parameters when comparing GSM MR analysis results.


Object Name Names of the objects to which two MR results to be comparedbelong



117


First Total Number ofMeasurement Reports

Indicates the number of MRs in the previous period.

Second Total Number ofMeasurement Reports

Indicates the number of MRs in the next period.

Difference of TotalMeasurement Reports

Indicates the differences of the number of MRs in the previousand next periods.

First Average UplinkReceive Quality

Indicates the average quality of received signals of the BTSscorresponding to all the TRXs in the previous period.

Second Average UplinkReceive Quality

Indicates the average quality of received signals of the BTSscorresponding to all the TRXs in the next period.

Average Uplink ReceiveQuality Difference

Indicates the differences of the average received signal qualityvalues of the BTSs corresponding to all the TRXs in the previousand next periods.

First Average DownlinkReceive Quality

Indicates the average quality of received signals of the MSscorresponding to all the TRXs in the previous period.

Second AverageDownlink ReceiveQuality

Indicates the average quality of received signals of the MSscorresponding to all the TRXs in the next period.

Average DownlinkReceive QualityDifference

Indicates the differences of the average received signal qualityvalues of the MSs corresponding to all the TRXs in the previousand next periods.

First Average UplinkReceive Level

Indicates the average received signal levels of the BTSscorresponding to all the TRXs in the previous period.

Second Average UplinkReceive Level

Indicates the average received signal levels of the BTSscorresponding to all the TRXs in the next period.


Indicates the differences of the average received signal levels ofthe BTSs corresponding to all the TRXs in the previous and nextperiods.

First Average DownlinkReceive Level

Indicates the average received signal levels of the MSscorresponding to all the TRXs in the previous period.

Second AverageDownlink Receive Level

Indicates the average received signal levels of the MSscorresponding to all the TRXs in the next period.

Average DownlinkReceive LevelDifference

Indicates the differences of the average received signal levels ofthe MSs corresponding to all the TRXs in the previous and nextperiods.

First Average TADistribution

Indicates the weighted average TA that the MS uses to advanceits timings of transmissions to the BTS in the previous period.

Second Average TADistribution

Indicates the weighted average TA that the MS uses to advanceits timings of transmissions to the BTS in the next period.



118


Average TA DistributionDifference

Indicates the difference of the weighted average TAs that the MSuses to advance its timings of transmissions to the BTS in theprevious and next periods.

First Link Balance Indicates the dB value in the previous period, which is calculatedthrough this expression: Average received level of the MScorresponding to each TRX - Average received level of the BTScorresponding to each TRX - Difference between the values ofthe average sensitivity of the MS and BTS.

Second Link Balance Indicates the dB value in the next period, which is calculatedthrough this expression: Average received level of the MScorresponding to each TRX - Average received level of the BTScorresponding to each TRX - Difference between the values ofthe average sensitivity of the MS and BTS.

Link Balance Difference Indicates the difference between the value of First Link Balanceand the value of Second Link Balance.

Related Tasks6.7 Comparing GSM MR Analysis Results



119

7 GSM Neighboring Cell Analysis

About This Chapter

The GSM neighboring cell analysis function enables you to obtain GSM neighboring cellanalysis data, create GSM neighboring cell analysis tasks, query and export GSM neighboringcell analysis results, query and export possible GSM neighboring cell analysis results, queryanalysis results of GSM intra-frequency neighboring cells, and query analysis results of GSMco-BCCH and co-BSIC cells. The Nastar supports the analysis of defined and undefined GSMneighboring cells. By using this function, you can identify and handle the problems of redundantor missing neighboring cell configuration of a cell. Through this function, the Nastar directlydisplays the required information, helping you solve network quality problems that are causedby the redundant or missing neighboring cell configuration.

7.1 Basic Knowledge of GSM Neighboring Cell AnalysisThis section provides the basic knowledge of GSM neighboring cell analysis, such as theneighboring cell analysis functions and algorithms for neighboring cell analysis. The basicknowledge helps you perform the operations related to GSM neighboring cell analysis.

7.2 Process of GSM Neighboring Cell AnalysisThis section describes the process of the GSM neighboring cell analysis.

7.3 Obtaining GSM Neighboring Cell Analysis DataThis section describes how to enable the Nastar to obtain GSM neighboring cell analysis data.You can create an E2E task to enable the Nastar to collect analysis data and create a data importtask so that the Nastar imports the collected analysis data into the database.

7.4 Creating GSM Neighboring Cell Analysis TaskThis section describes how to create GSM neighboring cell analysis tasks. After you create aGSM neighboring cell analysis task, the Nastar periodically analyzes GSM performance data,GSM configuration data, and engineering parameters in the Nastar database. By queryinganalysis results, you can learn about the status of the entire radio network so that problems canbe located and solved efficiently.

7.5 Querying GSM Neighboring Cell Analysis ResultsThis section describes how to query GSM neighboring cell analysis results. By viewing themissing and redundant neighboring cell configuration of a cell, you can add neighboring cellsthat are missing and delete redundant neighboring cells.

7.6 Querying GSM Possible Neighboring Cell Analysis Results

iManager NastarNetwork Optimization User Guide (GSM) 7 GSM Neighboring Cell Analysis


120

This section describes how to query GSM possible neighboring cell analysis results. Throughthis function, you can quickly identify all GSM possible neighboring cells of UMTS cells andoptimize neighboring relations based on the analysis results.

7.7 Querying GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis ResultsThis section describes how to query GSM co-BCCH and co-BSIC neighboring cell analysisresults. Among the cells that are configured as neighboring cells for the selected cell, or amongthe cells that are close to the selected cell, you can query the cells that share the same BCCHARFCN and same BSIC with the selected cell. The query results help to determine whether theBCCH ARFCN or BSIC of the selected cell needs to be changed.

7.8 Querying GSM Intra-Frequency Neighboring Cell Analysis ResultsThis section describes how to query GSM intra-frequency neighboring cell analysis reports.Through this function, you can query whether neighboring cells sharing the same BCCH ARFCNwith the current measurement cell exist. In addition, you can determine whether to modify theBCCH ARFCN of the current measurement cell based on the query results.

7.9 Exporting GSM Neighboring Cell Analysis ReportsThis section describes how to export GSM neighboring cell analysis reports. You can exportGSM neighboring cell analysis results for optimizing neighboring relations in networks.

7.10 Exporting GSM Possible Neighboring Cell Analysis ReportsThis section describes how to export GSM possible neighboring cell analysis reports. You canexport the queried possible neighboring cell analysis results from the Nastar, which helps inoptimizing neighboring relations in networks.

7.11 Technical Specifications for GSM Neighboring Cell AnalysisThis section describes the technical specifications for GSM neighboring cell analysis.

7.12 Reference for the GSM Neighboring Cell Analysis GUIThis section describes the interface for GSM neighboring cell analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofthe GSM neighboring cell analysis.



121

7.1 Basic Knowledge of GSM Neighboring Cell AnalysisThis section provides the basic knowledge of GSM neighboring cell analysis, such as theneighboring cell analysis functions and algorithms for neighboring cell analysis. The basicknowledge helps you perform the operations related to GSM neighboring cell analysis.

7.1.1 GSM Neighboring Cell Analysis FunctionThis section describes the GSM neighboring cell analysis function. The GSM neighboring cellanalysis function aggregates and analyzes the measurement reports and events reported by MSs,and then checks whether the neighboring cells of a serving cell are redundant, missing, or incross coverage. Direct display of the information provided by this function can help you solvenetwork quality problems that are caused by the redundant or missing neighboring cells or crosscoverage.

GSM Neighboring Cell AnalysisGSM neighboring cell analysis data comes from the measurement report of an MS on measuringthe ARFCNs in the BA2 list. The ARFCNs in the BA2 list include BCCH ARFCNs of definedneighboring cells and BCCH ARFCNs of undefined neighboring cells. Figure 7-1 shows theprocess of measuring the ARFCNs in the BA2 list.

Figure 7-1 Process of measuring the ARFCNs in the BA2 list

First, create an end-to-end task on the Nastar and deliver the BCCH ARFCNs of undefinedneighboring cells to an NE. Upon receipt of the relevant message, the NE sends the informationabout the ARFCNs to MSs in the serving cells. Before performing the neighboring cell analysis,check whether any defined neighboring cell of the measurement cell shares the same ARFCN



122

and the same BSIC with other neighboring cells. If a defined neighboring cell or an undefinedneighboring cell close to the measurement cell shares the same ARFCN and the same BSIC withother neighboring cells, the network stability and accuracy of neighboring cell analysis cannotbe guaranteed.

Then, MSs in the serving cells measure the ARFCNs in the BA2 list during calls and sendmeasurement reports to the BSC. The BSC collects the statistics of measurement reportsaccording to cells and neighboring cells. It collects information about BCCH and BSIC ofundefined and defined neighboring cells and the times of reaching the threshold of absolute leveldifference, the times of reaching the threshold of relative level difference, and number of MRsin the service cells.

Finally, the Nastar performs GSM neighboring cell analysis based on the statistics and generatesan analysis result. According to the analysis result, you can add missing neighboring cells anddelete redundant neighboring cells. Then, the Nastar generates a result file after neighboring cellanalysis, which records suggestions on neighboring cell optimization.

The GSM neighboring cell analysis result can be exported in CSV format.

In addition, the Nastar can display GSM neighboring cell analysis results and possibleneighboring cell analysis results on maps and highlight test cells, missing neighboring cells,redundant neighboring cells, defined and undefined neighboring cells in different colors. Thisfunction helps users query neighboring relationships.

Requirements for the Network

The network must be stable during the period of performance data for GSM neighboring cellanalysis. Otherwise, the accuracy of the analysis cannot be guaranteed. Table 7-1 describes thenetwork changes and their impacts.

Table 7-1 Network changes and their impacts

Network Change Impact

Adding or deleting BTSs Affects the cell handover and network coverage. In this case, theanalysis result cannot correctly reflect the current network status.

Changes of antenna datasuch as the changes of theazimuth, tilt angle, andheight

Results in the changes of the cell coverage and networkinterference.

Change of the transmitpower and the relatedparameters such as thediscontinuoustransmission and powercontrol


Change of frequencyplanning. For example, anew frequency planningis added to the network.

The change of the configuration data affects the identification ofdefined neighboring cells and undefined neighboring cells. In thiscase, the analysis result cannot correctly reflect the currentnetwork status. You are advised to keep the network stable duringthe data collection period.



123


Change of handoverrelations and handoverparameters

Affects the statistical results during the period of collecting andoptimizing the neighboring relationship data.

Change of BSC topologyor other NE topology

The BSC is responsible for collecting statistic results. Thus, themeasurement task cannot be normally performed if the networktopology is changed. Users are advised to keep the networktopology unchanged during the data collection period.

7.1.2 Algorithms for GSM Neighboring Cell AnalysisThis section describes the algorithms for GSM neighboring cell analysis, such as the algorithmsused to check missing neighboring cells and redundant neighboring cells.

Based on the measurement reports reported by the MS, the Nastar calculates the overall scoreand then ranks the defined and undefined GSM neighboring cells. According to the ranks ofGSM neighboring cells and result charts, users can analyze the neighboring cells depending onthe actual network situation, and then provide operation suggestions on configuring the missingGSM neighboring cells and deleting redundant GSM neighboring cells.

Algorithms for GSM neighboring cell analysis are as follows:

1. Calculating the integrated priority of all neighboring cells of the serving cell

In GSM neighboring cell analysis, the number of neighboring cell measurement reports inwhich the relative signal level threshold is exceeded and the number of those in which theabsolute signal level threshold is exceeded are both counted. A system algorithm is usedto calculate the overall priorities.

2. Determining missing neighboring cells

If the sequence number of an undefined GSM neighboring cell is smaller than or equal toNeighboring Cell Rank No.1 specified when a GSM neighboring cell analysis task iscreated, this undefined GSM neighboring cell is regarded as a missing neighboring cell.

3. Determining redundant neighboring cells

l You are advised to reserve the defined GSM neighboring cell whose number of MRsis 0 because of faulty NEs.

l If the number of handover requests of a defined GSM neighboring cell and the relativepercent are 0 or empty, this defined GSM neighboring cell is regarded as a redundantneighboring cell.

l If the number of handover requests of a defined GSM neighboring cell is smaller thanor equal to the value of HO Request Number Threshold, or the relative percent issmaller than or equal to the value of Relative Percentage Threshold, and the numberof neighboring cells of the serving cell is greater than the value of Constraint ofNeighboring Cell Table Length, or the number of neighboring cell measurementARFCNs included in the BA2 table is greater than the value of Constraint of BA2Table Length, this defined GSM neighboring cell is regarded as a redundantneighboring cell. All the threshold values are set when a GSM neighboring cell analysistask is created.



124

7.2 Process of GSM Neighboring Cell AnalysisThis section describes the process of the GSM neighboring cell analysis.

Figure 7-2 shows the process of GSM neighboring cell analysis.

Figure 7-2 Process of GSM neighboring cell analysis




125

Table 7-2 Process of GSM neighboring cell analysis


1 Creating GSMNeighboring CellMeasurement DataE2E Tasks

You need to choose Maintenance > E2E TaskManagement on the Nastar client to open the E2E TaskManagement window and then create a E2E task. After youcreate the task, the Nastar sends the commands to M2000 forenabling the performance counters.

2 Creating a GSMMeasure Task Filefor Neighbor CellData CollectionTask

You need to choose Maintenance > Task Management onthe Nastar client to open the Task Management window andthen create a GSM measure task file for neighbor cell datacollection task. After the task is created, the Nastarperiodically obtains the GSM measure task file for neighborcell data from the M2000 and then saves the data in files onthe Nastar server.

3 Creating a GSMPerformance DataCollection Task

You need to choose Maintenance > Task Management onthe Nastar client to open the Task Management window andthen create a GSM performance data collection task. Afterthe task is created, the Nastar periodically obtains the GSMperformance data from the M2000 and then saves the data infiles on the Nastar server.

4 Creating a GSMPerformance DataImport Task/Creating a GSMNeighboring CellMeasurement FileImport Task

You need to choose Maintenance > Task Management onthe Nastar client to open the Task Management window,and then create a GSM performance data import task and aGSM neighboring cell measurement file import task. Afterthe tasks are created, the Nastar periodically imports theGSM performance data and GSM neighboring cellmeasurement files saved on the Nastar server into thedatabase.

5 Checking theIntegrity ofAnalysis Data

In the Analysis Task Management window on the Nastarclient, double-click System Function > Data Query. In theQuery data dialog box, check whether all the data requiredfor GSM neighboring cell analysis is imported into thedatabase.

6 Creating GSMNeighboring CellAnalysis Task

In the Analysis Task Management window on the Nastarclient, a user can create GSM neighboring cell analysis tasks.After periodically obtaining the related performance data,neighboring cell measurement data, and configuration datafrom the Nastar database, the Nastar analyzes data and thengenerates the analysis result.



126


7 l Querying GSMNeighboringCell AnalysisResults

l Querying GSMPossibleNeighboringCell AnalysisResults

l Querying GSMCo-BCCH andCo-BSICNeighboringCell AnalysisResults

l Querying GSMIntra-FrequencyNeighboringCell AnalysisResults

You can view the analysis results of the neighboring cellanalysis tasks that are successfully performed. Based on theanalysis results, you can add missing neighboring cells anddelete redundant neighboring cells.

8 Exporting GSMNeighboring CellAnalysis Reports

You can export the result files of GSM neighboring cellanalysis through the Nastar client.

7.3 Obtaining GSM Neighboring Cell Analysis DataThis section describes how to enable the Nastar to obtain GSM neighboring cell analysis data.You can create an E2E task to enable the Nastar to collect analysis data and create a data importtask so that the Nastar imports the collected analysis data into the database.

7.3.1 Creating GSM Neighboring Cell Measurement Data E2ETasks

After a user creates an E2E task on the Nastar, the Nastar sends MML commands to the relatedNE through the M2000. The NE then performs the task and reports the measurement result tothe M2000.


l The OSS and NEs related to the analysis task are created. For details, see 2.2 CreatingOSSs and the Managed NEs.

l Configuration data is imported into the Nastar database. For details, see 3.3 ImportingConfiguration Data.



127

l The data source is subscribed and the status is On.

Context

You are advised to observe the E2E task for five minutes to check whether the task is executednormally after you create the E2E task by performing the following steps. If Status of the E2Etask is still Running after five minutes, it indicates that the E2E task is executed normally. IfStatus of the E2E task is Complete or Failed after five minutes, it indicates that the E2E taskfails to be executed. Note that the Nastar monitors the tasks by checking the task status on theM2000 at an interval of five minutes.

CAUTIONBefore refarming, stop the running neighboring GSM cell measurement data E2E task to avoidimpact on NEs.

Procedure

Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window isdisplayed.

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, orright-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 OSS Name drop-down list box, select an OSS for the task.

3. In the E2E Task Management > E2E Task List, choose *** Analysis Data Task.

Step 4 Click Next.

Step 5 Set Run Type, Time Setting, and Cycle Setting for the task.You need to set Cycle Setting only when Run Type is set to Period.

Step 6 Click Next.

Step 7 On the Measure Task tab page, set Duration Time (Minute), Period, and Measure Step.

l Duration Time (Minute) indicates the total duration of the measurement task execution.

l Period indicates the interval at which each group of ARFCNs is measured.

l Measure Step indicates the number of ARFCNs in a group.

NOTE

The measurement duration cannot exceed 24 hours.

Step 8 Select a cell to be analyzed from the object navigation tree.



128

NOTE

l Only the cells activated on the M2000 can be selected.

l BA2 quantity:** of the cell name indicates the quantity of the BA2 of the cell. The BA2 list containsa maximum of 32 ARFCNs.

The Nastar supports the function of searching for objects in the object navigation tree. After youclick an object in the navigation tree, you can press Ctrl+F to search for and locate an object.

Step 9 Click Frequency Analysis.

The Nastar traverses the three-level neighboring cells of the selected cell. Then, the Nastaranalyzes the BCCH ARFCNs of the traversed neighboring cells and highlights these BCCHARFCNs in the frequency selection area in gray to provide reference for selecting measurementARFCNs.

Traversing of the three-level neighboring cells indicates that the Nastar searches for theneighboring cell (neighboring cell A) of the selected cell, the neighboring cell (neighboring cellsB) of neighboring cell A, and the neighboring cell (neighboring cells C) of neighboring cell B.All traversed neighboring cells A, B, and C are neighboring cells obtained through the traversingof the three-level neighboring cells.

Step 10 Select ARFCNs for the BA2 list in the frequency selection area.

After you select frequencies for the BA2 list, the levels of neighboring cells are measured in acell based on the selected ARFCNs so that possible missing neighboring cells can be determined.The BA2 list contains a maximum of 32 ARFCNs. If the number of selected ARFCNs exceeds32, the ARFCNs in the BA2 list are modified periodically and cyclically.

The selected ARFCNs are grouped according to the value of Measure Step and you can viewthe groups in the Selected Frequency area.

Step 11 Set the soft parameters of the neighboring cell measurement data task.

1. Click the Soft Parameter tab.2. Select Soft Parameter Setting.3. Set the threshold of each soft parameter.

For the detailed description of soft parameters, see 7.12.3 Parameters of GSMNeighboring Cell E2E Tasks.

Step 12 Click Complete.The added GSM neighboring cell measurement data task is displayed in the task list.

----End

Follow-up ProcedureIn the task list on the right of the E2E Task Management window, select one analysis data E2Etask to view, delete, refresh, or cancel it.


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.



129


Refresh the selected task Click Refresh.

Cancel the selected task Right-click a task from the task list in the right pane of the E2ETask Management window, and then choose Cancel from theshortcut menu.NOTE

The E2E tasks in the running or waiting state can be cancelled.

Related References7.12.3 Parameters of GSM Neighboring Cell E2E Tasks7.12.3 Parameters of GSM Neighboring Cell E2E Tasks

7.3.2 Creating a GSM Measure Task File for Neighbor Cell DataCollection Task

After you create a GSM measure task file for neighbor cell data collection task on the Nastar,the Nastar periodically collects measure task file for neighbor cell data on the M2000 and savesthe data in a specified path for future GSM network analysis.

Prerequisitesl You have logged in to the Nastar client.l You have created an end-to-end task for collecting GSM neighboring cell data. In addition,

GSM measure task file for neighbor cell data already exists on the M2000. For details, see7.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks.

Contextl A GSM measure task file for neighbor cell data collection task is a user-defined timing

task.l A GSM measure task file for neighbor cell data collection task can be executed only once

or periodically. The options of the execution period are Minute, Hour, Day, Week, andMonth.

Procedure




Step 3 Set the basic information about the task.1. In the Task Name field, enter the name of the task.2. Select Data Collection > Data Collection in Task Type.3. Click Once or Period in the Run Type pane.



130

Step 4 Click Next.


NOTE







You can set half an hour or one hour as atask execution period for collectingmeasure task file for neighbor cell data.

b. Perform Step 5.

Step 5 Click Next. In the Basic Information field and the Task Parameter field, set relevantparameters.

1. From the OSS Name drop-down list, select the name of the OSS that manages the NE tobe analyzed.

2. Select GSM Measure Task File for Neighbor Cell Data from the Data Type drop-downlist box.

3. Set the parameters in the Task Parameter field.TIP

l Select one or more NEs, thus the related data of the NEs are periodically collected to a certaindirectory of the Nastar.

l Select Specify the time range and set Start time and End time to collect related data from theM2000 side periodically or once within the specified time period. Then, save the data under aspecified directory of the Nastar.


----End

7.3.3 Creating a GSM Performance Data Collection TaskAfter you create a GSM performance data collection task on the Nastar, the Nastar periodicallycollects NE performance data on the M2000 and saves the data in a specified path for futureGSM neighboring cell analysis.




131

l You have created an end-to-end task for collecting GSM neighboring cell data. In addition,GSM performance data already exists on the M2000. For details, see 7.3.1 Creating GSMNeighboring Cell Measurement Data E2E Tasks.

Contextl A GSM performance data collection task is a user-defined timing task.l A GSM performance data collection task can be executed only once or periodically. The

options of the execution period are Minute, Hour, Day, Week, and Month.

Procedure





Step 4 Click Next.


NOTE








b. Perform Step 5.

Step 5 Click Next. In the Basic Information field and the Task Parameter field, set relevantparameters.1. From the OSS drop-down list, select the name of the OSS that manages the NE to be

analyzed.2. Select Performance data from the Data Type drop-down list box.



132

3. Set the parameters in the Task Parameter field.






----End




scheduled task of the same type.l The data import task can only be executed periodically. The unit of the task execution period

can be Hours, Days, Weeks, or Months. The data import task of the same type can onlybe created once on the Nastar. After the task is created, the Nastar automatically importsdata at the preset time.




Analysis TaskType



Manual creation



133

Analysis TaskType




Manual creation



Manual creation



Manual creation



Manual creation


Manual creation


- -



Manual creation



Manual creation




Manual creation



Manual creation



Manual creation



Manual creation



Manual creation



134

Analysis TaskType


UMTS VIPAnalysis


Manual creation


- -



Manual creation



Manual creation



Manual creation




Manual creation



Manual creation



Manual creation




Manual creation


- -




Manual creation



135

Analysis TaskType





Manual creation



Manual creation

CDMA VIPAnalysis


Manual creation



Manual creation


Manual creation



Manual creation



Manual creation


- -


- -

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 7-3.3. Select the execution type of the data import task from Execution Type. You can only select

Periodic.





136

NOTE




----End




















137



































138
































-



139

Procedure


TIP







----End

7.4 Creating GSM Neighboring Cell Analysis TaskThis section describes how to create GSM neighboring cell analysis tasks. After you create aGSM neighboring cell analysis task, the Nastar periodically analyzes GSM performance data,GSM configuration data, and engineering parameters in the Nastar database. By queryinganalysis results, you can learn about the status of the entire radio network so that problems canbe located and solved efficiently.


l Analysis data and configuration data are imported into the Nastar database. For details, see7.3.5 Checking the Integrity of Analysis Data.

Contextl An analysis task can be performed only once.

l A maximum of 50 tasks of this type can be created, and a maximum of data of seven dayscan be involved in an analysis task.

Procedure

Step 1 Click in the Analysis Task Management window. The New Task dialog box is displayed.



140

TIP




Step 3 Click Next.




Step 5 Set Neighboring Cell Analysis Parameters, Possible Neighboring Cell AnalysisParameters, and Result Show Parameters on the Set parameters tab page.

Step 6 Click Next.

Step 7 Set the Task Type to One-time.





141

If... Then...








2. Set Execution Delay.3. Optional: On the Set Busy Hours tab, select Busy

Hour, and set the start time and end time of the busyhour.

NE Group is selected 1. Set Time Range and Execution Delay.2. Optional: On the Set Busy Hours tab, select Busy



----End









142




Resume.



Related References7.12.5 Parameters for Creating and Modifying GSM Neighboring Cell Analysis Tasks

7.5 Querying GSM Neighboring Cell Analysis ResultsThis section describes how to query GSM neighboring cell analysis results. By viewing themissing and redundant neighboring cell configuration of a cell, you can add neighboring cellsthat are missing and delete redundant neighboring cells.

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM neighboring cell analysis task has reached 100%.

Procedure

Step 1 Choose Theme Function > GSM Neighboring Cell Analysis Task in the navigation tree onthe left of the Analysis Task Management window.

Step 2 Select a GSM neighboring cell analysis task from the task list on the upper right of the AnalysisTask 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 on the lower right of the Analysis TaskManagement window.

Step 4 Right-click the analysis result, and then choose View Analysis Result from the shortcut menu.The GSM Neighboring Cell Analysis window is displayed.You can also double-click the selected analysis result to open the GSM Neighboring CellAnalysis window.


Step 5 In the GSM Neighboring Cell Analysis window, query the analysis results of GSM neighboringcells.

1. Select a measurement cell from the cell list on the left of the displayed window.



143

2. Query all defined and undefined neighboring cells of the selected measurement cell in theDefined Neighboring Cell and Undefined Neighboring Cell areas respectively.After ranking the neighboring cells of the selected measurement cell based on the integratedpriority, the Nastar displays the integrated priority percentages of the first 32 neighboringcells in the chart area in the lower part of the window. You can set the parameters in thedrop-down list box on the upper right of this area to display the statistical values of differentparameters of the first 32 neighboring cells in a line chart.For details about parameters, see 7.12.6 Parameters for Querying GSM NeighboringCell Analysis Results.You can double-click any area in the Defined Neighboring Cell or UndefinedNeighboring Cell area to zoom in on the list and then double-click the list again to restoreit to the normal size.

3. If User Modify is selected for a row in the Defined Neighboring Cell or UndefinedNeighboring Cell area, the Nastar automatically saves the modified list so that you canview the modified information the next time you open the analysis report. If no modificationis made, the Nastar displays the list in the database the next time you open the analysisreport. The file with the modification automatically saved is stored in the installation pathof the client. This file is deleted automatically when the corresponding task is deleted.If the possible neighboring cell table of the neighboring cell analysis report is modified(see the description in 7.6 Querying GSM Possible Neighboring Cell AnalysisResults), the information in the undefined neighboring cell list is replaced with theinformation about the most possible neighboring cell selected in the preceding possibleneighboring cell analysis the next time the neighboring cell analysis report is opened. Thefollowing fields in the report are updated: Undefined Neighboring Cell Name, CGI,Service Type of Neighboring Cell, and Distance (km).

NOTE


----End

Follow-up ProcedureExport query results. You can right-click any list in the GSM Neighboring Cell Analysiswindow and then choose Save As from the shortcut menu to save the current query results asa .csv file.

Related References7.12.6 Parameters for Querying GSM Neighboring Cell Analysis Results

7.6 Querying GSM Possible Neighboring Cell AnalysisResults

This section describes how to query GSM possible neighboring cell analysis results. Throughthis function, you can quickly identify all GSM possible neighboring cells of UMTS cells andoptimize neighboring relations based on the analysis results.



144


l The progress bar of the GSM neighboring cell analysis task reaches 100%.

Procedure




Step 4 Right-click the analysis result, and then choose Possible Neighboring Cell Analysis from theshortcut menu. The GSM Possible Neighboring Cell Analysis window is displayed.


Step 5 In the GSM Possible Neighboring Cell Analysis window, query the analysis results of possibleGSM neighboring cells.

1. Select a measurement cell in the left pane.

You can press Ctrl+F to search for an object.

2. Query the possible neighboring cells of the selected measurement cell in the right pane.

If Whether to Use is selected, it indicates that the current possible neighboring cell is usedas the best possible neighboring cell of the measurement cell and the information in thecorresponding field in the right pane is replace with the information about the possibleneighboring cell in the left pane. For details about parameters, see 7.12.7 Parameters forQuerying GSM Possible Neighboring Cell Analysis Results.

Click to add possible neighboring cells for the current measurement cell.

If the possible neighboring cell table of a neighboring cell analysis report is modified, theinformation in the undefined neighboring cell list is replaced with the information aboutthe most possible neighboring cell selected in the preceding Possible Neighboring CellAnalysis function the next time the neighboring cell analysis report is opened. Thefollowing fields in the report are updated: Undefined Neighboring Cell Name, CGI,Service Type of Neighboring Cell, and Distance (km).

----End

Follow-up ProcedureExport query results. You can right-click in the result list and then choose Save As from theshortcut menu to save the current query results as a .csv file.

Related References7.12.7 Parameters for Querying GSM Possible Neighboring Cell Analysis Results



145

7.7 Querying GSM Co-BCCH and Co-BSIC NeighboringCell Analysis Results

This section describes how to query GSM co-BCCH and co-BSIC neighboring cell analysisresults. Among the cells that are configured as neighboring cells for the selected cell, or amongthe cells that are close to the selected cell, you can query the cells that share the same BCCHARFCN and same BSIC with the selected cell. The query results help to determine whether theBCCH ARFCN or BSIC of the selected cell needs to be changed.

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM neighboring cell analysis task reaches 100%.

ProcedureStep 1 Choose Theme Function > GSM Neighboring Cell Analysis Task from the navigation tree

on the left of the Analysis Task Management window.



Step 4 Right-click the analysis result, and then choose Co-BCCH & Co-BSIC Checking from theshortcut menu. The Co-BCCH & Co-BSIC Check Result window is displayed.


Step 5 In the Co-BCCH & Co-BSIC Check Result window, query the co-BCCH and co-BSICneighboring cell analysis results of all cells involved in the current analysis task.You can press Ctrl+F to search for an object.

----End

Follow-up ProcedureExport query results. You can right-click in the Co-BCCH & Co-BSIC Check Result windowand then choose Save As from the shortcut menu to save the current query results as a .csv file.

Related References7.12.8 Parameters for Querying GSM Co-BCCH and Co-BSIC Neighboring Cell AnalysisResults

7.8 Querying GSM Intra-Frequency Neighboring CellAnalysis Results

This section describes how to query GSM intra-frequency neighboring cell analysis reports.Through this function, you can query whether neighboring cells sharing the same BCCH ARFCN



146

with the current measurement cell exist. In addition, you can determine whether to modify theBCCH ARFCN of the current measurement cell based on the query results.


l The progress bar of the GSM neighboring cell analysis task reaches 100%.

Procedure




Step 4 Right-click the analysis result, and then choose Neighboring Cells Co-BCCH Analysis fromthe shortcut menu. The Neighboring Cells Co-BCCH Analysis Result window is displayed.


Step 5 In the Neighboring Cells Co-BCCH Analysis Result window, query the intra-frequencyneighboring cell analysis results of all cells involved in the current analysis task.You can press Ctrl+F to search for an object.

----End

Follow-up ProcedureExport query results. You can right-click in the Neighboring Cells Co-BCCH AnalysisResult window and then choose Save As from the shortcut menu to save the current query resultsas a .csv file.

Related References7.12.9 Parameters for Querying GSM Intra-frequency Neighboring Cell Analysis Results

7.9 Exporting GSM Neighboring Cell Analysis ReportsThis section describes how to export GSM neighboring cell analysis reports. You can exportGSM neighboring cell analysis results for optimizing neighboring relations in networks.


l You have queried the GSM neighboring cell reports. For details, see 7.5 Querying GSMNeighboring Cell Analysis Results.



147

Procedurel Perform the following operations as required:


Export neighboring cell overviewinformation Click in the GSM Neighboring Cell

Analysis window.

The main information contained in the files isTask Name, Creator, Result Set Begin Time,Result Set End Time, and related informationabout the measurement cells.

Export neighboring cell analysis resultsof test cell Click in the GSM Neighboring Cell

Analysis window.

The main information contained in the files isTask Name, Creator, Result Set Begin Time,Result Set End Time, BSC Where Test Cell IsLocated, Test Cell ID, and DefinedNeighboring Cell and Name.

Export possible neighboring cellanalysis results Click in the GSM Neighboring Cell

Analysis window.

The main information contained in the files isBSC Name, Test Cell Name, Test Cell BCCH,Test Cell BSIC, Test Cell CGI, NeighboringCell BCCH, Possible Neighboring CellName, and the information related to thepossible neighboring cells of measurementcells.



148


Export all the neighboring cell analysisresults

1. Click in the GSM Neighboring CellAnalysis window. The Save dialog box isdisplayed.If the analysis result data amount of all theneighboring cells is large, you need to waitfor a while before the dialog box isdisplayed.

2. Specify a save path for the file. Then, clickSave.

3. In the displayed OK dialog box, confirmwhether to add or delete the bidirectionalneighboring cells.l Click Yes to include the modified

records (for which User Modify areselected) in the exported neighboringcell analysis result.In this case, a column named IsBidirectional Neighboring Cell isadded to the exported result. Y is filledin this column for all the bidirectionalneighboring cells. In addition, thebidirectional neighboring cell recordsare added to the end of the result table.For example, in the definedneighboring cell list of measurementcell A, neighboring cell B is aredundant neighboring cell of cell A. IfUser Modify is selected, it indicatesthat cell A and cell B are redundantneighboring cells of each other. It isrecommended that bidirectionalneighboring cells be deleted. Thisrecord is exported to the neighboringcell analysis result.

l Click No to ignore the modifiedrecords in the neighboring cell analysisresult. In this case, these records are notexported to the result file.

You are allowed to save all theneighboring cell analysis results as .cvsfiles on the basis of BSC. The neighboringcell analysis results of each BSCcorrespond to one .cvs file.The naming convention is FileName_task name_NE name_NCS.cvs.



149

The progress of an export task is displayed in the Exported File List dialog box. You canperform 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 exporttasks are created, other tasks are in the waiting state and can be executed only after therunning task is executed completely or canceled.

– You can click on the right of the progress bar to cancel an export task in the waitingor running state so that the task is terminated and deleted from the task list. You canclick on the right of the progress bar to delete an export task in the completed stateso that the task is deleted from the task list.

– You can click on the right of the progress bar to view detailed information aboutan export task in the completed state.

NOTE

l Exporting neighboring cell overview information is to export the information about all themeasurement cells involved in the selected analysis task.

l Exporting neighboring cell optimization results of a measurement cell is to export the informationabout the defined and undefined neighboring cells of a specific measurement cell.

l Exporting possible neighboring cell analysis results is to export the information about the possibleneighboring cells of a specific measurement cell.

l Exporting all the neighboring cell analysis results is to export the information about the definedand undefined neighboring cells of all measurement cells.

----End

7.10 Exporting GSM Possible Neighboring Cell AnalysisReports

This section describes how to export GSM possible neighboring cell analysis reports. You canexport the queried possible neighboring cell analysis results from the Nastar, which helps inoptimizing neighboring relations in networks.

Prerequisitesl You have logged in to the Nastar client.l You have queried the GSM possible neighboring cell analysis reports. For details, see 7.6

Querying GSM Possible Neighboring Cell Analysis Results.

ContextAnalysis reports are exported as .csv files.

Procedure

Step 1 Click in the GSM Possible Neighboring Cell Analysis window. The GSM PossibleNeighboring Cell Analysis dialog box is 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

perform other operations during the execution of the export task.



150


– You can click on the right of the progress bar to cancel an export task in the waitingor 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 thatthe task is deleted from the task list.

– You can click on the right of the progress bar to view detailed information about anexport task in the completed state.

l The exported file contains the information on the left of the GSM Possible NeighboringCell Analysis window.

----End

7.11 Technical Specifications for GSM Neighboring CellAnalysis

This section describes the technical specifications for GSM neighboring cell analysis.



<= 10,000 cells





Number of E2E One-time tasksby one OSS (all the themes)

<= 200

Number of GSM NeighboringCell Analysis Data E2E Tasks

<= 10


<= 50

7.12 Reference for the GSM Neighboring Cell Analysis GUIThis section describes the interface for GSM neighboring cell analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofthe GSM neighboring cell analysis.



151

7.12.1 Interface Description: GSM Neighboring Cell AnalysisThis section describes the interface for GSM neighboring cell analysis. Before performingrelevant operations, familiarize yourself with the rules for dividing areas on the interface.

The neighboring cell analysis results can be displayed in table or in histogram mode, as shownin Figure 7-3.

Figure 7-3 Interface for the neighboring cell analysis


(1) List of current measurement cellinformation

Displays the information about the currentmeasurement cell.

(2) List of defined neighboring cells Displays all the defined neighboring cells ofthe cell selected in Area (1)

(3) List of undefined neighboring cells Displays all the undefined neighboring cells ofthe cell selected in Area (1)



152


(4) Chart area Displays the information about all theneighboring cells of the selected measurementcell in histogram mode or in line chart

NOTEl If the names of two or more cells are the same,

the cell names on the X-Axis are displayed asCellName(BCCH,BSIC).

l If the cell names cannot be found, the cellnames on the X-Axis are displayed as(BCCH,BSIC).

(5) Button area Four buttons are provided to export allinformation about the neighboring cell, theneighboring cell optimization results of themeasurement cell, the analysis results ofpossible neighboring cells, and allneighboring cell optimization results.

7.12.2 Interface Description: GSM Possible Neighboring CellAnalysis

This section describes the interface for GSM possible neighboring cell analysis. Beforeperforming relevant operations, familiarize yourself with the functions of the areas on theinterface.

The possible neighboring cell analysis result is displayed in tables, which consist of a possibleneighboring cell overview table and a possible neighboring cell confirmation table, as shown inFigure 7-4.



153

Figure 7-4 Interface of analyzing GSM possible neighboring cells


(1) Possible neighboring cell overview table Displays the aggregation information ofpossible neighboring cells of all the cellsinvolved in the task in a table.

(2) Possible neighboring cell confirmationtable

Displays all the possible neighboring cellsof the cells selected in Area (1).

7.12.3 Parameters of GSM Neighboring Cell E2E TasksThis section describes the parameters for creating GSM E2E tasks. You can refer to thedescription when creating a GSM E2E task.


Basicinformation

Task Name Indicates the name of a neighboring cellmeasurement task.

OSS Name Indicates the name of the OSS related to the task.

E2E Task List Select the GSM Neighboring Cell Analysis DataTask node.



154


Run Type l Once: The system executes the created tasks onlyonce at the specified time.

l Period: The system executes the created tasks atthe preset time.

Start Time Indicates the time when the task starts to run.The start time must be later than the current time. Bydefault, the start time is five minutes later than thecurrent system time.

Cycle Indicates the interval between periodic tasks. Thisparameter involves the period unit and the interval.l Unit: day.l Interval: 1.This parameter is valid for only periodic tasks.NOTE

The Nastar does not support the configuration of periodicunit and duration of the periodic task.

Execute Times Indicates the times that a periodic task is executed.The value is an integer from 1 to 15.This parameter is valid for only periodic tasks.

Measurementinformation

Duration Time(Minute)

Indicates the total duration which a measurementtask is performed.The value is an integer from 1 to 1430.The duration time must be later than the timecalculated by (Measurement period ×15) × ([Totalnumber of test ARFCNs ÷ measurement step + 1]) +15.

Period Interval between the ARFCNs of each group.The value is an integer from 1 to 48. The unit is *15(minute), that is, the value must be multiples of 15minutes.For example, if this parameter is set to 2, themeasurement time of each ARFCN is 2×15 minutes,that is, 30 minutes.

Measure Step Indicates the number of ARFCNs in the same group.The value is an integer from 1 to 31.The measurement step must be less than or equal tothe minimum rest step of the selected cell.

Cell Object Indicates the cell related to the neighboring cellmeasurement task.



155


frequencyInformation

Indicates the set of ARFCNs to be measured. TheARFCNs are classified by group. The number ofARFCNs of each group is determined by MeasureStep.NOTEl You can select a maximum of 762 ARFCNs for a cell.

If the number exceeds 762, the NE returns an errormessage after the corresponding MML command isexecuted, indicating that the task creation ormodification fails.

l Before setting this parameter, you must set MeasureStep.

Soft parameterinformation

Soft ParameterSetting

If you select this option, the soft parameters that youset are valid for this measurement task.

RSSThres The value is an integer from 0 to 127.When the difference between the levels of theneighboring cell and the serving cell in the MR isgreater than this value, the relevant traffic statisticalcounter is incremented by one.

ASSThres The value is an integer from 0 to 63.When the level of the neighboring cell in the MR isgreater than this value, the relevant traffic statisticalcounter is incremented by one.

NCELLINTERFLEVELTHRES 1-7

You can set the thresholds of interference level forseven neighboring cells.The value is an integer from 0 to 127.When the difference between the levels of theneighboring cell and the serving cell in the MR isgreater than this value, the relevant traffic statisticalcounter is incremented by one.

NOTE

l Level refers to the strength of the received or transmitted signal. It is generally used in power controland handover algorithm.

l ASSThres and RSSThres evaluate the reasonableness of the neighbor cell. According to the actualrequirements, you can modify the two values to adjust the evaluation standard.

l ADJINLVThres1 to ADJINLVThres7 evaluates the CIR distribution of neighboring cells and servingcells and the ratio among each segment. This parameter in combination with frequency configurationanalysis indicates the severity level of each frequency interference, and thus can be used to adjust theC/I distribution segment of neighboring cells and serving cells.Carrier-to-interference ratio distribution refers to the distribution of the power of the carrier signalsand the power of the interference signals, that is, C/I distribution.

Related Tasks7.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks



156

7.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks


Parameter DescriptionParameter Value Range Description



ExecutionType







Runimmediately



ExecutionInterval



ExecutionTimes








157




Collect AllNE



Collect ByNE Type











158

7.12.5 Parameters for Creating and Modifying GSM NeighboringCell Analysis Tasks

This section describes the parameters for creating and modifying GSM neighboring cell analysistasks. You can refer to the description when creating and modifying a GSM neighboring cellanalysis task.







Task Type One-time: The system executes the created tasks only once at the specifiedtime.

Time Range Only the data generated between the start time and the end time will beanalyzed.The start time should precede the end time, and the end time should precedethe 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 ExecutionDelay.

ExecutionDelay

Indicates the specified execution time of the task.The parameter should not precede the end time of the Time Range.



159





Neighboring Cell Rank No.1 Indicates the lower threshold of the neighboring cell sequence.All the undefined neighboring cells whose sequence numbersare smaller than or equal to the value of this parameter areregarded as missing neighboring cells.This parameter can be set to any integer from 1 to 32. Thedefault value is 10.

Constraint of BA2 TableLength

Indicates the limitation on the number of test ARFCNs ofneighboring cells.This parameter can be set to any integer from 1 to 32. Thedefault value is 20.

Constraint of NeighboringCell Table Length

Indicates the limitation on the number of neighboring cells.This parameter can be set to any integer from 1 to 64. Thedefault value is 50.This parameter and Constraint for BA2 Table Len are usedto determine the redundant neighboring cells. If these twoconditions are not met, the system searches for redundantneighboring cells constantly until the two conditions are met.

HO Request NumberThreshold

The neighboring cells where the number of handover requestsis smaller than the value of this parameter are regarded asredundant neighboring cells.This parameter can be set to any integer from 0 to 9999. Thedefault value is 10.

Relative PercentageThreshold

The neighboring cells whose relative percentage is smallerthan the value of this parameter are regarded as redundantneighboring cells.This parameter can be set to any integer from 0 to 100. Thedefault value is 1. The unit is %.

All Direction Gain Indicates the omnidirectional gain of an antenna.This parameter can be set to any integer from 0 to 15. Thedefault value is 11. The unit is dBi.



160


Specified Direction Gain Indicates the directional gain of an antenna.This parameter can be set to any integer from 0 to 25. Thedefault value is 17. The unit is dBi.

Display the Number ofUndefined NeighboringCells

Indicates that only the TopN undefined neighboring cells aredisplayed.N can be any integer from 20 to 50. The default value is 30.

Related Tasks7.4 Creating GSM Neighboring Cell Analysis Task

7.12.6 Parameters for Querying GSM Neighboring Cell AnalysisResults

This section describes the parameters for querying GSM neighboring cell analysis results. Youcan refer to the description when querying GSM neighboring cell analysis results.

Information About a Test CellParameter

Range

Unit

Description

BSCWhereTest CellIsLocated

1 to 32characters

N/A

Indicates the name of the BSC that a test cell belongs to, forexample, BSC_1.

Test CellName

1 to 64characters

N/A

Indicates the name of a test cell, for example, Cell_1.

TotalNumberofMeasurementReports

[0,+∞)

Number

Indicates the total number of MRs received by a test cell.

NumberofRedundantNeighboring Cells

[0,+∞)

Number

Indicates the number of redundant neighboring cells for theselected test cell.



161

Parameter

Range

Unit

Description

Percentage ofMeasurementReport onRedundantNeighboring Cells(%)

[0.00,100.00]

% Indicates the sum of the integrated priority percentages of allredundant neighboring cells for the selected test cell.

NumberofUnconfiguredNeighboring Cells

[0,+∞)

Number

Indicates the number of missing neighboring cells for theselected test cell.

Percentage ofMeasurementReport onNotConfiguredNeighboring Cells(%)

[0.00,100.00]

% Indicates the sum of the integrated priority percentages of allmissing neighboring cells for the selected test cell.

LAC [1,65533],[65535]

N/A

Indicates the location area code of the selected test cell.LAC is a part of CGI and uniquely identifies a GSM cell.

CI [0,65535]

N/A

Indicates the identification code of the selected test cell.



162

Parameter

Range

Unit

Description

BCCH [0,1023]1 to124:belongto P-GSM;128 to251:belongtoGSM850; 0,975 to1023:belongto E-GSM;955 to974:belongto R-GSM;811 to885:belongtoDCS1800;512 to810:belongtoDCS1800whenthehighbandsupportsDCS1800;512 to810:belongtoPCS1900

N/A

Indicates the broadcast control channel for the selected test cell.



163

Parameter

Range

Unit

Description

whenthehighbandsupportsPCS1900.

BSIC Consists ofthefollowingparts:NCC[0,7]BCC[0,7]BSIC=NCC*10+BCC

N/A

Indicates the base station identity code of the selected test cell.

Test CellID

[0 to2047]

N/A

Indicates the ID of the selected test cell.

Defined Neighboring CellParameter

Range Unit

Description

DefinedNeighboring CellName

1 to 64characters

N/A

Indicates the name of a defined neighboring cell for theselected test cell.



164

Parameter

Range Unit

Description

CGI MCC-MNC-LAC-CIMCC[000,999]MNC[00,99]LAC[0,65535]CI[0,65535]

N/A

Indicates the global ID of a neighboring cell.

Neighboring CellBCCH

[0,1023]1 to 124:belong to P-GSM; 128to 251:belong toGSM850;0, 975 to1023:belong toE-GSM;955 to 974:belong toR-GSM;811 to 885:belong toDCS1800;512 to 810:belong toDCS1800when thehigh bandsupportsDCS1800;512 to 810:belong toPCS1900when thehigh bandsupportsPCS1900.

N/A

Indicates the broadcast control channel for a neighboringcell.



165

Parameter

Range Unit

Description

Neighboring CellBSIC

Consists ofthefollowingparts:NCC[0,7]BCC [0,7]BSIC=NCC*10+BCC

N/A

Indicates the base station identity code for a neighboringcell.

ServiceType ofNeighboring Cell

N/A N/A

Indicates the service type provided by a GSM neighboringcell, including indoor site and outdoor site. Learning aboutthe service type provided by a GSM neighboring cell helpsprevent important neighboring cells from being deleted.

SuggestedOperation

Redundantneighboring cell, Intra-frequencyneighboring cell, Nooperation

N/A

Indicates the operation suggestions on a neighboring cell.

UserModify

N/A N/A

Indicates whether the modification is recommended.If this option is selected, you are advised to performmodification according to Suggested Operation. Otherwise,no modification is recommended.

Integrated PriorityTH (%)

[0.00,100.00]

% Indicates the percentage of the total number of MRs relatedto a test cell to the number of MRs related to the neighboringcell level that is higher than the relative level and theabsolute level.Integrity Priority TH = Number of MRs related to theneighboring cell level that is higher than the relative leveland the absolute level/Total number of MRs related to a testcell x 100%

Priority [0,+∞) N/A

Indicates the sequence number of a neighboring cell amongall neighboring cells for the selected test cell according toits integrated priority.

NumberofHandoverRequests

[0,+∞) Number

Indicates the number of handover requests from the currentserving cell to another cell.

NumberofHandover Failures

[0,+∞) Number

Indicates the number of handover failures among allhandover requests from the current serving cell to anothercell.



166

Parameter

Range Unit

Description

Handover SuccessRate (%)

[0.00,100.00]

% Indicates the handover success rate from the current servingcell to another cell.Outgoing cell handover success rate = Number of successfuloutgoing cell handovers/Number of outgoing cell handoverrequests x 100%

RelativePercentage (%)

[0.00,100.00]

% Indicates the proportion of the total handover attempts fromthe current serving cell to a neighboring cell to the totalhandover attempts from the current serving cell to anyneighboring cells.Relative percentage = Total number of handover attemptsfrom the current serving cell to a neighboring cell/Totalnumber of handover attempts from the current serving cellto any neighboring cells x 100%

Distance(km)

[0,+∞) km Indicates the distance from the selected test cell to aneighboring cell.

In BATime(min)

[1,+∞) minute

Indicates the duration for measuring a neighboring cell.

NumberofNeighboring CellMeasurementReports

[0,+∞) Number

Indicates the total number of MRs of a neighboring cell.

TotalMRs ofThisFrequency in BATime

[0,+∞) Number

Indicates the total number of MRs recorded in the BA tableduring frequency point polling in the serving cell.

SourceCellSignalStrength(dBm)

N/A dBm

Indicates the average signal strength of the selected test cellthat serves as the source handover cell.

Neighboring CellSignalStrength(dBm)

N/A dBm

Indicates the average signal strength of a neighboring cell.



167

Parameter

Range Unit

Description

Mean S-NDifference (dB)

N/A dB Indicates the average difference between the signal strengthof the selected test cell serving as the source handover celland the signal strength of a neighboring cell.

>Relative THMRs

[0,+∞) Number

Indicates the number of MRs related to the information thatthe value of Mean S-N Difference is greater than the relativelevel threshold.

>Absolute THMRs

[0,+∞) Number

Indicates the number of MRs containing information thatthe signal strength of a neighboring cell is greater than theabsolute level threshold.

Undefined Neighboring CellParameter

Range Unit

Description

UndefinedNeighboring CellName

1 to 64characters

N/A

Indicates the name of an undefined neighboring cell for theselected test cell.

CGI Consists ofthe followingparts:MCC[000 to999]MNC[000 to999]LAC[1,65533],[65535]CI [0,65535]

N/A

Indicates the global ID of a neighboring cell.



168

Parameter

Range Unit

Description


[0,1023]1 to 124:belong to P-GSM; 128 to251: belongto GSM850;0, 975 to1023: belongto E-GSM;955 to 974:belong to R-GSM; 811 to885: belongto DCS1800;512 to 810:belong toDCS1800when thehigh bandsupportsDCS1800;512 to 810:belong toPCS1900when thehigh bandsupportsPCS1900.

N/A

Indicates the broadcast control channel for a neighboringcell.


Consists ofthe followingparts:NCC[0,7]BCC [0,7]BSIC=NCC*10+BCC

N/A

Indicates the base station identity code for a neighboringcell.

ServiceType ofNeighboring Cell

N/A N/A

Indicates the service type provided by a GSM neighboringcell, including indoor site and outdoor site. Learning aboutthe service type provided by a GSM neighboring cell helpsprevent important neighboring cells from being deleted.

SuggestedOperation

Missingneighboringcell, Nooperation

N/A

Indicates the operation suggestions on a neighboring cell.



169

Parameter

Range Unit

Description

UserModify

N/A N/A

Indicates whether the modification is recommended.If this option is selected, you are advised to performmodification according to Suggested Operation.Otherwise, no modification is recommended.

Integrated PriorityTH (%)

[0.00,100.00]

% Indicates the integrated priority of a neighboring cell, thatis, the percentage of total number of MRs related to the testcell to the number of MRs related to the neighboring celllevel higher than the relative level and the absolute level.


Indicates the sequence number of a neighboring cellamong all neighboring cells for the selected test cellaccording to its integrated priority.

Distance(km)


In BATime(min)

[0,+∞) minute

Indicates the duration for measuring a neighboring cell.

NumberofNeighboring CellMeasurementReports

[0,+∞) Number

Indicates the number of MRs related to a neighboring cell.

TotalMRs ofThisFrequency in BATime

[0,+∞) Number

Indicates the total number of MRs recorded in the BA tableduring frequency point polling in the serving cell.

SourceCellSignalStrength(dBm)

N/A dBm

Indicates the average signal strength of the selected testcell.

Neighboring CellSignalStrength(dBm)

N/A dBm

Indicates the average signal strength of a neighboring cell.

Mean S-NDifference (dB)

N/A dB Indicates the average difference between the signalstrength of the selected test cell and the signal strength ofa neighboring cell.



170

Parameter

Range Unit

Description

>RelativeTH MRs

[0,+∞) Number

Indicates the number of MRs containing information thatthe difference between the signal strength of a neighboringcell and the signal strength of the test cell is greater thanthe relative level threshold.

>AbsoluteTH MRs

[0,+∞) Number

Indicates the number of MRs containing the signal strengthof neighboring cells greater than the absolute levelthreshold.

Related Tasks7.5 Querying GSM Neighboring Cell Analysis Results

7.12.7 Parameters for Querying GSM Possible Neighboring CellAnalysis Results

This section describes the parameters for querying GSM possible neighboring cell analysisresults. You can refer to the description when querying GSM possible neighboring cell analysisresults.

Possible Neighboring Cell Overview TableParameter

Range Unit

Description


1 to 32 characters N/A

Indicates the name of the BSC that a test cell belongsto, for example, ERM3H201.

Test CellName


Indicates the name of the test serving cell, forexample, Cell_1.



171

Parameter

Range Unit

Description

Test CellBCCH

[0,1023]1 to 124: belong to P-GSM; 128 to 251:belong to GSM850;0, 975 to 1023:belong to E-GSM;955 to 974: belong toR-GSM; 811 to 885:belong to DCS1800;512 to 810: belong toDCS1800 when thehigh band supportsDCS1800; 512 to810: belong toPCS1900 when thehigh band supportsPCS1900.

N/A

Indicates the broadcast control channel for a testcell.

Test CellBSIC

Consists of thefollowing parts:NCC[0,7]BCC [0,7]BSIC=NCC*10+BCC

N/A

Indicates the base station identity code of a test cell.

Test CellCGI

Consists of thefollowing parts:MCC[000 to 999]MNC[000 to 999]LAC[1,65533],[65535]CI[0,65535]

N/A

Indicates the global ID of a test cell, for example,286-01-33034-50712.



172

Parameter

Range Unit

Description


[0,1023]1 to 124: belong to P-GSM; 128 to 251:belong to GSM850;0, 975 to 1023:belong to E-GSM;955 to 974: belong toR-GSM; 811 to 885:belong to DCS1800;512 to 810: belong toDCS1800 when thehigh band supportsDCS1800; 512 to810: belong toPCS1900 when thehigh band supportsPCS1900.

N/A

Indicates the broadcast control channel for a testneighboring cell.



N/A

Indicates the base station identity code of a testneighboring cell.

Neighboring CellCGI

Consists of thefollowing parts:MCC[000 to 999]MNC[000 to 999]LAC [1,65533],[65535]CI [0,65535]

N/A

Indicates the global ID of the selected possibleneighboring cell.

Neighboring BSC


Indicates the name of the BSC that the selectedpossible neighboring cell belongs to.

Neighboring CellName


Indicates the name of the selected possibleneighboring cell.

NeighboringDistance(km)

[0,+∞) km

Indicates the distance from the test cell to theselected possible neighboring cell.



173

Parameter

Range Unit

Description

Neighboring CellLoopNumber

0,1,2,3,99 N/A

Indicates the number of laps between the selectedpossible neighboring cell and the test cell, that is,the number of cells between the selected possibleneighboring cell and the test cell.

AngleFromNeighboring Cell(°)

[0°,360°] Degree

Indicates the relative angle between the selectedpossible neighboring cell and the test cell.

PredictedDLSignalStrength(dBm)

N/A dBm

Indicates the signal strength of the selected possibleneighboring cell based on the dimensioning.

ObtainFromConfigurationData

Yes or No N/A

Indicates whether the selected possible neighboringcell is obtained from the configuration data.

NumberofPossibleNeighboring Cellsin thePossibleNeighboring CellPairs

[0,+∞) Number

Indicates the number of possible neighboring cells.

Integrated Priority(%)

[0,100%] N/A

Indicates the percentage of integrated priority.


Indicates the sequence number of a possibleneighboring cell among all possible neighboringcells for the selected test cell according to itsintegrated priority.



174

Possible Neighboring Cell Confirmation TableParameter

Range

Unit

Description

Enable N/A N/A Indicates whether to select the current possible neighboring cellas the most possible neighboring cell for the test cell.If the parameter is selected, the current possible neighboring cellserves as the most possible neighboring cell for the test cell. Inaddition, you must replace information about the selected possibleneighboring cell in the possible neighboring cell confirmationtable with information in the possible neighboring cell overviewtable.Possible Neighboring Cell CGI replaces Neighboring Cell CGI.Possible Neighboring Cell BSC Name replaces Neighboring BSC.Name of Possible Neighboring Cell replaces Neighboring CellName.Distance of Possible Neighboring Cell(km) replaces NeighboringDistance(km).Number of Possible Neighboring Cell Laps replaces NeighboringCell Loop Number.Relative Angle of Neighboring Cell(°) replaces Angle formNeighboring Cell Direction.Predicted Signal Strength of Neighboring Cell(dBm) replacesPredicted DL Signal Strength.Obtain From Configuration Data replaces Get from config data.If this parameter is not selected, it indicates that the most possibleneighboring cell is not determined. In addition, the system clearsall the information in the following fields in the possibleneighboring cell overview table:Neighboring Cell CGINeighboring Cell NameNeighboring Distance(km)Neighboring Cell Loop NumberAngle form Neighboring Cell DirectionPredicted DL Signal StrengthObtain From Configuration Data



175

Parameter

Range

Unit

Description

PossibleNeighboring CellCGI

Consistsofthefollowingparts:MCC[000to999]MNC[000to999]LAC[1,65533],[65535]CI[0,65535]

N/A Indicates the global ID of a possible neighboring cell.

BSCWheretheSelectedPossibleNeighboring CellIsLocated

1 to32characters

N/A Indicates the name of the BSC that a possible neighboring cellbelongs to.

Name ofPossibleNeighboring Cell

1 to64characters

N/A Indicates the name of a possible neighboring cell.



176

Parameter

Range

Unit

Description

DistanceofPossibleNeighboring Cell(km)

[0,+∞)

km Indicates the distance from the test cell to a possible neighboringcell.

NumberofPossibleNeighboring CellLaps

0,1,2,3,99

N/A Indicates the number of laps between the test cell and a possibleneighboring cell, that is, the number of cells between the test celland a possible neighboring cell.

RelativeAngle ofNeighboring Cell(°)

[0°,360°]

Degree

Indicates the relative angle between the test cell and a possibleneighboring cell.

PredictedSignalStrengthofNeighboring Cell(dBm)

N/A dBm

Indicates the signal strength of a possible neighboring cell basedon the dimensioning.

ObtainFromConfigurationData

YesorNo

N/A Indicates whether possible neighboring cells are obtained from theconfiguration data.

Related Tasks7.6 Querying GSM Possible Neighboring Cell Analysis Results

7.12.8 Parameters for Querying GSM Co-BCCH and Co-BSICNeighboring Cell Analysis Results

This section describes the parameters for querying GSM co-BCCH and co-BSIC neighboringcell analysis results. You can refer to the description when querying GSM co-bcch and co-bsicneighboring cell analysis results.



177

ParameterParameter

Range Unit

Description



Indicates the name of the BSC that a test cell belongsto, for example, BSC_1.

Test CellName



Test CellCGI

Consists of thefollowing parts:MCC[000 to 999]MNC[000 to 999]LAC[1,65533]CI[0,65535]

N/A

Indicates the global ID of a test cell.

Test CellBCCH

[0,1023]1 to 124: belong toP-GSM; 128-251:belong toGSM850; 0, 975 to1023: belong to E-GSM; 955 to 974:belong to R-GSM;811 to 885: belongto DCS1800; 512to 810: belong toDCS1800 whenthe high bandsupportsDCS1800; 512 to810: belong toPCS1900 when thehigh band supportsPCS1900.

N/A

Indicates the broadcast control channel for a test cell.

Test CellBSIC


N/A




Indicates the name of a neighboring cell for theselected test cell.



178

Parameter

Range Unit

Description

Neighboring CellCGI

Consists of thefollowing items:MCC[000 to 999]MNC[000 to 999]LAC [1,65533]CI [0,65535]

N/A

Indicates the global ID of a neighboring cell for theselected test cell.

AngleformNeighboring CellDirection(°)

[0°,360°] Degree

Indicates the relative angle between the test cell anda neighboring cell.

Distance(km)

[0,+∞) km Indicates the distance between the test cell and aneighboring cell.


[0,+∞) Number

Indicates the number of handover requests from thecurrent serving cell to another cell.

Related Tasks7.7 Querying GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis Results

7.12.9 Parameters for Querying GSM Intra-frequency NeighboringCell Analysis Results

This section describes the parameters for querying GSM intra-frequency neighboring cellanalysis results. You can refer to the description when querying GSM intra-frequencyneighboring cell analysis results.

Parameter

Parameter

Range Unit

Description


1 to 32characters

N/A

Indicates the name of the BSC that a test cell belongsto, for example, BSC_1.

Test CellName

1 to 64characters

N/A




179

Parameter

Range Unit

Description

Test CellCGI

Consists of thefollowing parts:MCC[000 to999]MNC[000 to999]LAC[1,65533]CI[0,65535]

N/A


Test CellBCCH

[0,1023]1 to 124: belongto P-GSM; 128to 251: belong toGSM850; 0, 975to 1023: belongto E-GSM; 955to 974: belong toR-GSM; 811 to885: belong toDCS1800; 512to 810: belong toDCS1800 whenthe high bandsupportsDCS1800; 512to 810: belong toPCS1900 whenthe high bandsupportsPCS1900.

N/A


Test CellBSIC

Consists of thefollowing parts:NCC[0,7]BCC[0,7]BSIC=NCC*10+BCC

N/A



1 to 64characters

N/A

Indicates the name of a neighboring cell for the selectedtest cell.

BSCWhereNeighboring CellIsLocated

1 to 32characters

N/A

Indicates the name of the BSC that a neighboring cellfor the selected test cell belongs to.



180

Parameter

Range Unit

Description

Neighboring CellCGI

Consists of thefollowing items:MCC[000 to999]MNC[000 to999]LAC [1,65533]CI [0,65535]

N/A

Indicates the global ID of a neighboring cell for theselected test cell.


[0,1023]1 to 124: belongto P-GSM;128-251: belongto GSM850; 0,975 to 1023:belong to E-GSM; 955 to974: belong toR-GSM; 811 to885: belong toDCS1800; 512to 810: belong toDCS1800 whenthe high bandsupportsDCS1800; 512to 810: belong toPCS1900 whenthe high bandsupportsPCS1900.

N/A

Indicates the broadcast control channel for aneighboring cell for the selected test cell.


Consists of thefollowing parts:NCC[0,7]BCC[0,7]BSIC=NCC*10+BCC

N/A

Indicates the base station identity code of a neighboringcell for the selected test cell.

Distance(km)



[0,+∞) Number

Indicates the number of handover requests from thecurrent serving cell to another cell.



181

Related Tasks7.8 Querying GSM Intra-Frequency Neighboring Cell Analysis Results



182

8 GSM/UMTS Neighboring Cell Analysis

About This Chapter

The GSM/UMTS neighboring cell analysis function enables you to obtain GSM/UMTSneighboring cell analysis data, create GSM/UMTS neighboring cell analysis tasks, query GSM/UMTS neighboring cell analysis results, and export GSM/UMTS neighboring cell analysisresults from the Nastar. The Nastar supports the function of identifying redundant and missinginter-RAT neighboring cells. This helps to solve the network quality problems caused byredundant and missing neighboring cell configuration.

8.1 Basic Knowledge of GSM/UMTS Neighboring Cell AnalysisThis section provides the basic knowledge of GSM/UMTS neighboring cell analysis, such asthe GSM/UMTS neighboring cell analysis function and algorithms for neighboring cell analysis.The basic knowledge helps you perform the operations related to GSM/UMTS neighboring cellanalysis.

8.2 Process of GSM/UMTS Neighboring Cell AnalysisThis section describes the process of GSM/UMTS neighboring cell analysis.

8.3 Obtaining GSM/UMTS Neighboring Cell Analysis DataThis section describes how to enable the Nastar to obtain GSM/UMTS neighboring cell analysisdata. You can create an E2E task to enable the Nastar to collect analysis data and create a dataimport task so that the Nastar imports the collected analysis data into the database.

8.4 Creating GSM/UMTS Neighboring Cell Analysis TasksThis section describes how to create GSM/UMTS neighboring cell analysis tasks. After youcreate a GSM/UMTS neighboring cell analysis task, the Nastar periodically analyzes GSM/UMTS performance data, GSM configuration data, and engineering parameters in the Nastardatabase. By querying the analysis results, you can identify redundant inter-RAT neighboringcells and missing inter-RAT neighboring cells so that problems can be located and solvedefficiently.

8.5 Querying GSM/UMTS Neighboring Cell Analysis ResultsThis section describes how to query GSM/UMTS neighboring cell analysis results. Through thisfunction, you can query all the defined and undefined UMTS neighboring cells of a GSM cellunder a BSC. In addition, the Nastar calculates the integrated priority of neighboring cellsaccording to the related algorithm and ranks the neighboring cells, helping you locate redundantand missing neighboring cells in the inter-RAT neighboring cells.

8.6 Querying GSM/UMTS Possible Neighboring Cell Analysis Results

iManager NastarNetwork Optimization User Guide (GSM) 8 GSM/UMTS Neighboring Cell Analysis


183

This section describes how to query GSM/UMTS possible neighboring cell analysis results.Through this function, you can quickly identify all GSM possible neighboring cells in the UMTSnetwork and optimize neighboring relations based on the analysis results.

8.7 Exporting GSM/UMTS Neighboring Cell Analysis ReportsThis section describes how to export GSM/UMTS neighboring cell analysis reports. You canexport the queried GSM/UMTS neighboring cell analysis results from the Nastar, which helpsin optimizing neighboring relations in networks.

8.8 Exporting GSM/UMTS Possible Neighboring Cell Analysis ReportsThis section describes how to export GSM/UMTS possible neighboring cell analysis reports.You can export the queried possible neighboring cell analysis results from the Nastar, whichhelps in optimizing the neighboring relations in networks.

8.9 Technical Specifications for GSM/UMTS Neighboring Cell AnalysisThis section describes the technical specifications for GSM/UMTS neighboring cell analysis.

8.10 Reference to the GSM/UMTS Neighboring Cell Analysis InterfaceThis section describes the interface for GSM/UMTS neighboring cell analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM/UMTS neighboring cell analysis.



184

8.1 Basic Knowledge of GSM/UMTS Neighboring CellAnalysis

This section provides the basic knowledge of GSM/UMTS neighboring cell analysis, such asthe GSM/UMTS neighboring cell analysis function and algorithms for neighboring cell analysis.The basic knowledge helps you perform the operations related to GSM/UMTS neighboring cellanalysis.

8.1.1 GSM/UMTS Neighboring Cell AnalysisThis section describes the GSM/UMTS neighboring cell analysis function. Through thisfunction, the Nastar summarizes the measurement reports (MRs) and events reported byterminals and analyzes inter-RAT neighboring cells to check for the redundant and missingneighboring cell configurations and cross coverage. This helps to improve the network quality.

Inter-RAT Neighboring Cell AnalysisAfter you set the conditions for checking the redundant or missing neighboring cellconfigurations, 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 UMTS neighboringcells, undefined UMTS neighboring cells, redundant UMTS neighboring cells, and missingUMTS neighboring cells are illustrated in different colors.

The Nastar can export analysis results of inter-RAT neighboring cells to a file. In the inter-RATneighboring cell analysis result window, you can export the result file of inter-RAT neighboringcell analysis after adding the missing neighboring cells and deleting the redundant neighboringcells. The result file provides the related optimization suggestions.

The GSM/UMTS neighboring cell analysis results can be exported to a .csv, .xls, or .xlsx file.

Requirements for the NetworkThe network must be stable during the period of performance data for GSM/UMTS neighboringcell analysis. Otherwise, the analysis results may be inaccurate. Table 8-1 describes the networkchanges and their impacts.



Addition or deletion ofBTSs

Affects the network coverage and handovers between cells. Inthis case, the analysis results cannot accurately reflect the currentnetwork status.

Change of antenna data,such as azimuth, tiltangle, or height




185


Changes of transmitpower and power-relatedparameters such asdiscontinuoustransmission and powercontrol


Change of frequencyplanning (for example, anew frequency planningscheme is implementedon the network.)

The change of the configuration data affects the identification ofdefined and undefined neighboring cells. In this case, the analysisresults cannot accurately reflect the current network status. Youare advised to keep the network stable during data collection.

Changes of handoverrelations and parameters

Affects the statistical results during the period of collecting thedata about neighboring relations and the period of optimizingneighboring relations.

Change of BSC topologyor other NE topology

The BSC is responsible for collecting statistical results.Therefore, the measurement task will not be performed properlyif the network topology is changed. You are advised to keep thenetwork topology unchanged during data collection.

8.1.2 Algorithms for GSM/UMTS Neighboring Cell AnalysisThis section describes the algorithms for GSM/UMTS neighboring cell analysis, such as thealgorithms used to check missing neighboring cells and redundant neighboring cells.

Based on the measurement reports (MRs) reported by UEs, the Nastar calculates the overallscore and then ranks the defined and undefined UMTS neighboring cells. According to theranking of UMTS neighboring cells and result analysis charts, you can enable the Nastar toanalyze the neighboring cells depending on the actual network situation, and then providesuggestions on missing UMTS neighboring cells to be added and redundant UMTS neighboringcells to be deleted.

The algorithms for GSM/UMTS neighboring cell analysis are as follows:

1. Calculate the integrated priority of all the UMTS neighboring cells of a serving cell.

In GSM/UMTS neighboring cell analysis, a system algorithm is used to calculate the overallpriorities based on factors such as the number of UMTS neighboring cell measurementreports, measurement time, and number of serving cell measurement reports.

2. Determine missing neighboring cells.

When the sequence number of an undefined UMTS neighboring cell is smaller than orequal to the value of Neighboring Cell Count Setting that is set when a GSM/UMTSneighboring cell analysis task is created, the UMTS neighboring cell is regarded as amissing neighboring cell.

3. Determine redundant neighboring cells.

When the sequence number of a defined UMTS neighboring cell is greater than the valueof Neighboring Cell Count Setting that is set when a GSM/UMTS neighboring cell



186

analysis task is created, the UMTS neighboring cell is regarded as a redundant neighboringcell.

8.2 Process of GSM/UMTS Neighboring Cell AnalysisThis section describes the process of GSM/UMTS neighboring cell analysis.

Figure 8-1 shows the process of GSM/UMTS neighboring cell analysis.

Figure 8-1 Process of GSM/UMTS neighboring cell analysis



187


Table 8-2 Process of GSM/UMTS neighboring cell analysis


1 Create a GSM/UMTSneighboring cellmeasurement dataE2E task

You need to choose Maintenance > E2E TaskManagement on the Nastar client to open the E2E TaskManagement window and then create a E2E task. After youcreate the task, the Nastar sends the commands to M2000 tostart the GSM/UMTS neighboring cell measurement task andrecording measurement results.

2 Create a GSMperformance datacollection task


3 Create a GSMperformance dataimport task

You need to choose Maintenance > Task Management onthe Nastar client to open the Task Management window andthen create a GSM performance data import task. After thetask is created, the Nastar periodically imports the GSMperformance data files saved on the Nastar server into thedatabase.

4 Check the integrityGSM/UMTSneighboring cellanalysis data

You can double-click System Function > Data Query in theAnalysis Task Management window on the Nastar client toopen the Query Data dialog box and then check that all therequired GSM/UMTS neighboring cell analysis data isimported into the database.

5 Create a GSM/UMTSneighboring cellanalysis task

In the Analysis Task Management window on the Nastarclient, you can create a GSM/UMTS neighboring cellanalysis task. After you create the task, the Nastar retrievesthe GSM performance data and GSM configuration dataperiodically from the database, analyzes the retrieved data,and then generates analysis results.

6 l Query GSM/UMTSneighboring cellanalysis results

l Query possibleGSM/UMTSneighboring cellanalysis results

You can view the analysis results of the GSM/UMTSneighboring cell analysis tasks that are successfullyperformed and add missing neighboring cells and deleteredundant neighboring cells accordingly.

7 Export GSM/UMTSneighboring cellanalysis reports

You can enable the Nastar client to export GSM/UMTSneighboring cell analysis results as report files.



188

8.3 Obtaining GSM/UMTS Neighboring Cell Analysis DataThis section describes how to enable the Nastar to obtain GSM/UMTS neighboring cell analysisdata. You can create an E2E task to enable the Nastar to collect analysis data and create a dataimport task so that the Nastar imports the collected analysis data into the database.

8.3.1 Creating GSM/UMTS Neighboring Cell Measurement DataE2E Tasks


Prerequisitesl You have logged in to the Nastar client.l The OSS and NEs related to the analysis task are created. For details, see 2.2 Creating

OSSs and the Managed NEs.l Configuration data is imported into the Nastar database. For details, see 3.3 Importing

Configuration Data.l Start the GU neighboring cell interoperability switch on the LMT or the M2000.

ContextYou are advised to observe the E2E task for five minutes to check whether the task is executednormally after you create the E2E task by performing the following steps. If Status of the E2Etask is still Running after five minutes, it indicates that the E2E task is executed normally. IfStatus of the E2E task is Complete or Failed after five minutes, it indicates that the E2E taskfails to be executed. Note that the Nastar monitors the tasks by checking the task status on theM2000 at an interval of five minutes.

Procedure




Step 3 Set the basic task information.1. In the Task Name field, enter the name of the analysis data E2E task.2. In the OSS Name drop-down list box, select an OSS for the task.3. In the E2E Task Management > E2E Task List, choose *** Analysis Data Task.

Step 4 Click Next.

Step 5 On the Measurement Task tab page, set the measurement parameters and cycle task, and selectthe NE to be analyzed from the NE list.



189


Step 6 Click Next.

Step 7 Set ARFCNs and scrambling codes for a cell in Result of setting.

All the selected cells will be measured by Nastar system.

l Click Configuration Query. All the ARFCNs and scrambling codes of the UMTSneighboring cells of a measurement cell are displayed and selected.

l Click Automatic Analysis. All the ARFCNs and scrambling codes of the surrounding UMTSneighboring cells of a measurement cell are displayed and selected.

NOTE

The records in red are beyond the NE's measurement range. By default, they are not selected. You canresolve this problem by reducing the number of measured ARFCNs or scrambling codes.

l Click Set in batches. The Set ARFCN and scrambling code dialog box is displayed. AddARFCNs and scrambling codes to be measured for all cells. A maximum of 3 ARFCNs canbe selected.

l After you click a certain record in the cell list, the system highlights the select cell in blue.Then, click Adjust Cell. The Set ARFCN and scrambling code dialog box is displayed.Add ARFCNs and scrambling codes to be measured for the selected cell.

NOTE

l The Adjust Cell function takes effect only for the selected cells which are highlighted in blue.

l You can also select multiple cells by pressing and holding Ctrl or Shift, thus make all the selectedcells highlighted in blue.

l Click Export Result. All information in Result of setting is exported as a .csv, .xls, or .xlsxfile.

Step 8 Click Finish.The added GSM/UMTS neighboring cell measurement data task is displayed in the task list.

----End









190




Related References8.10.3 Parameters of GSM/UMTS Neighboring Cell Data E2E Tasks

8.3.2 Creating a GSM Performance Data Collection TaskAfter you create a GSM performance data collection task on the Nastar, the Nastar periodicallycollects NE performance data on the M2000 and saves the data in a specified path for futureGSM/UMTS neighboring cell analysis.


l You have created an end-to-end task for collecting GSM/UMTS neighboring cellmeasurement data. In addition, GSM performance data already exists on the M2000. Fordetails, see 8.3.1 Creating GSM/UMTS Neighboring Cell Measurement Data E2ETasks.

Contextl A GSM performance data collection task is a user-defined timing task.

l A GSM performance data collection task can be executed only once or periodically. Theoptions of the execution period are Minute, Hour, Day, Week, and Month.

Procedure





1. In the Task Name field, enter the name of the task.

2. Select Data Collection > Data Collection in Task Type.

3. Click Once or Period in the Run Type pane.

Step 4 Click Next.




191

NOTE








b. Perform Step 5.


1. From the OSS drop-down list, select the name of the OSS that manages the NE to beanalyzed.

2. Select Performance data from the Data Type drop-down list box.







----End




192








Analysis TaskType



Manual creation



Manual creation



Manual creation



Manual creation



Manual creation


Manual creation


- -



Manual creation



193

Analysis TaskType




Manual creation




Manual creation



Manual creation



Manual creation



Manual creation



Manual creation

UMTS VIPAnalysis


Manual creation


- -



Manual creation



Manual creation



Manual creation




Manual creation



Manual creation



194

Analysis TaskType




Manual creation




Manual creation


- -




Manual creation




Manual creation



Manual creation

CDMA VIPAnalysis


Manual creation



Manual creation


Manual creation



Manual creation



Manual creation


- -



195

Analysis TaskType



- -

Procedure





Periodic.



NOTE




----End









196











Prerequisitesl You have logged in to the Nastar client.l The data import task is performed.















197


































198






















-

Procedure


TIP






199




----End

8.4 Creating GSM/UMTS Neighboring Cell Analysis TasksThis section describes how to create GSM/UMTS neighboring cell analysis tasks. After youcreate a GSM/UMTS neighboring cell analysis task, the Nastar periodically analyzes GSM/UMTS performance data, GSM configuration data, and engineering parameters in the Nastardatabase. By querying the analysis results, you can identify redundant inter-RAT neighboringcells and missing inter-RAT neighboring cells so that problems can be located and solvedefficiently.



Contextl An analysis task can be performed only once.l A maximum of 50 tasks of this type can be created, and a maximum of data of seven days


Procedure





Step 3 Click Next.




Step 5 Set Neighboring Cell Analysis Parameters, Possible Neighboring Cell AnalysisParameters, and Result Show Parameters on the Set parameters tab page.

Step 6 Click Next.



200


If... Then...





If... Then...











----End




201








Resume.



Related References8.10.5 Parameters for Creating and Modifying GSM/UMTS Neighboring Cell Analysis Tasks

8.5 Querying GSM/UMTS Neighboring Cell AnalysisResults

This section describes how to query GSM/UMTS neighboring cell analysis results. Through thisfunction, you can query all the defined and undefined UMTS neighboring cells of a GSM cellunder a BSC. In addition, the Nastar calculates the integrated priority of neighboring cellsaccording to the related algorithm and ranks the neighboring cells, helping you locate redundantand missing neighboring cells in the inter-RAT neighboring cells.


l The progress bar of the GSM/UMTS neighboring cell analysis task reaches 100%.

Procedure

Step 1 Click the GSM/UMTS Possible Neighboring Cell Analysis node in the navigation tree in theAnalysis Task Management window.

Step 2 Select a GSM neighboring cell analysis task from the task list on the upper right of the AnalysisTask Management window.



202

The analysis results of the selected task are displayed in the lower right pane.


Step 4 Right-click the analysis result, and then choose View Analysis Result from the shortcut menu.The GSM/UMTS Neighboring Cell Analysis Task window is displayed.You can also double-click the selected analysis result to open the GSM/UMTS NeighboringCell Analysis Task window.


Step 5 Query the GSM neighboring cell analysis results in the GSM/UMTS Neighboring CellAnalysis Task window. Select a cell from the measurement cell list in Area (2)

1. Select a measurement cell from the cell list on the left of the displayed window.2. In the UMTS neighboring cell list in the right pane, query all defined and undefined

neighboring cells of the selected measurement cell.After ranking the neighboring cells of the selected measurement cell based on the integratedpriority, the Nastar displays the integrated priority percentages of the first 32 neighboringcells in the chart area in the lower part of the window. You can set the parameters in thedrop-down list box on the upper right of this area to display the statistical values of differentparameters of the first 32 neighboring cells in line charts.For details about parameters, see 8.10.6 Parameters for Querying the Analysis Reportsof GSM/UMTS Neighboring Cells.You can double-click any area of the UMTS neighboring cell list to zoom in on the list andthen double-click the list again to restore it to the normal size.

3. If User Modify is selected for a row in the UMTS neighboring cell list, the Nastarautomatically saves the modified list so that you can view the modified information thenext time you open the analysis report.If no modification is made, the Nastar displays the list in the database the next time youopen the analysis report. The file with the modification automatically saved is stored in theinstallation path of the client. This file is deleted automatically when the correspondingtask is deleted.If the possible neighboring cell table of the neighboring cell analysis report is modified(see the description in 8.6 Querying GSM/UMTS Possible Neighboring Cell AnalysisResults), the information about the undefined neighboring cells in the UMTS neighboringcell list is replaced with the information about the most possible neighboring cell selectedin the preceding possible neighboring cell analysis the next time the neighboring cellanalysis report is opened. The following fields in the report are updated: NeighboringUMTS Cell Name, RNC ID, CI, and Distance (km).

----End

Follow-up ProcedureExport query results. You can right-click any list in the Neighboring GSM/UMTS CellAnalysis window and then choose Save As from the shortcut menu to save the current queryresults as a .csv, .xls, or .xlsx file.

Related References8.10.6 Parameters for Querying the Analysis Reports of GSM/UMTS Neighboring Cells



203

8.6 Querying GSM/UMTS Possible Neighboring CellAnalysis Results

This section describes how to query GSM/UMTS possible neighboring cell analysis results.Through this function, you can quickly identify all GSM possible neighboring cells in the UMTSnetwork and optimize neighboring relations based on the analysis results.

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM/UMTS neighboring cell analysis task reaches 100%.

Procedure

Step 1 Click the GSM/UMTS Possible Neighboring Cell Analysis node in the navigation tree in theAnalysis Task Management window.

Step 2 Select a GSM/UMTS neighboring cell analysis task from the task list on the upper right of theAnalysis Task Management window.The analysis results of the selected task are displayed in the lower right pane.


Step 4 Right-click the analysis result, and then choose Possible Neighboring Cell Analysis from theshortcut menu. The GSM/UMTS Possible Neighboring Cell Analysis Task window isdisplayed.


Step 5 In the GSM/UMTS Possible Neighboring Cell Analysis Task window, query the analysisresults of possible GSM/UMTS neighboring cells.

1. Select a measurement cell in the left pane.You can press Ctrl+F to search for an object.

2. Query the possible UMTS neighboring cells of the selected measurement cell in the rightpane.For details about parameters, see 7.12.7 Parameters for Querying GSM PossibleNeighboring Cell Analysis Results.

Click to add possible neighboring cells for the current measurement cell.To export all information in the possible neighboring cell overview table, see 8.8 ExportingGSM/UMTS Possible Neighboring Cell Analysis Reports.

----End

Follow-up ProcedureExport query results. You can right-click in the result list and then choose Save As from theshortcut menu to save the current query results as a .csv, .xls, or .xlsx file.



204

Related References8.10.7 Parameters for Querying the Analysis Reports of GSM/UMTS Possible NeighboringCells

8.7 Exporting GSM/UMTS Neighboring Cell AnalysisReports

This section describes how to export GSM/UMTS neighboring cell analysis reports. You canexport the queried GSM/UMTS neighboring cell analysis results from the Nastar, which helpsin optimizing neighboring relations in networks.

Prerequisitesl You have logged in to the Nastar client.l You have queried the GSM/UMTS neighboring cell analysis reports. For details, see 8.5

Querying GSM/UMTS Neighboring Cell Analysis Results.

ContextAnalysis reports are exported as .csv, .xls, or .xlsx files.



Export Overview TableClick in the GSM/UMTS NeighboringCell Analysis Task window.

The main information contained in the files istask name, creator, Result Set Begin Time,Result Set End Time, and related informationabout the test cells.

Export Neighboring Cell AnalysisResults of Test Cell Click in the GSM/UMTS Neighboring

Cell Analysis Task window.

The main information contained in the files istask name, creator, Result Set Begin Time,Result Set End Time, BSC serving the test cell,number and name of the test cell, and definedand undefined UMTS neighboring cells.



205


Export All Neighboring Cell AnalysisResults

1. Click in the GSM/UMTSNeighboring Cell Analysis Task window.The Save dialog box is displayed.If the analysis result data amount of all theneighboring cells is large, you need to waitfor a while before the dialog box isdisplayed.

2. Specify a save path for the file. Then, clickSave.You are only allowed to save all theneighboring cell analysis results as .xlsor .xlsx files on the basis of BSC. Theneighboring cell analysis results of eachBSC correspond to one .xls or .xlsx file.The naming convention is task name_NEname_NCS.xls or task name_NEname_NCS.xlsx.

The progress of an export task is displayed in the Exported File List dialog box. You canperform other operations during the execution of the export task.


– You can click on the right of the progress bar to cancel an export task in the waitingor running state so that the task is terminated and deleted from the task list. You canclick on the right of the progress bar to delete an export task in the completed stateso that the task is deleted from the task list.


NOTE

l Exporting overview table is to export the information about all the test cells involved in theselected analysis task.

l Exporting neighboring cell analysis results of test cell is to export the information about thedefined and undefined neighboring cells of a specific test cell.

l Exporting all neighboring cell analysis results is to export the information about the defined andundefined neighboring cells of all test cells.

----End



206

8.8 Exporting GSM/UMTS Possible Neighboring CellAnalysis Reports

This section describes how to export GSM/UMTS possible neighboring cell analysis reports.You can export the queried possible neighboring cell analysis results from the Nastar, whichhelps in optimizing the neighboring relations in networks.


l You have queried the GSM/UMTS possible neighboring cell analysis reports. For details,see 8.6 Querying GSM/UMTS Possible Neighboring Cell Analysis Results.

ContextAnalysis reports are exported as .csv, .xls, or .xlsx files.

Procedure

Step 1 Click in the GSM/UMTS Possible Neighboring Cell Analysis window. The Save dialogbox is 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 canperform other operations during the execution of the export task.





l The exported file contains the information on the left of the GSM Possible NeighboringCell Analysis window.

----End

8.9 Technical Specifications for GSM/UMTS NeighboringCell Analysis

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



207



<= 10,000 cells






<= 200

Number of GSM/UMTSNeighboring Cell Analysis DataE2E One-time Tasks

<= 20


<= 50

8.10 Reference to the GSM/UMTS Neighboring CellAnalysis Interface

This section describes the interface for GSM/UMTS neighboring cell analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM/UMTS neighboring cell analysis.

8.10.1 Interface Description: GSM/UMTS Neighboring CellAnalysis

This section describes the interface for GSM/UMTS neighboring cell analysis. Beforeperforming relevant operations, familiarize yourself with the rules for dividing areas on theinterface.

The GSM/UMTS neighboring cell analysis results can be displayed in table or in histogrammode, as shown in Figure 8-2.



208

Figure 8-2 Interface for the GSM/UMTS neighboring cell analysis


(1) List of current test cellinformation

Displays the information about the current test cell.

(2) Neighboring cell list Displays all the neighboring UMTS cells of the cellselected in Area (1).

(3) Image area Displays the information about all the neighboringUMTS cells of the selected test cell in the combinationof column charts and line charts.

(4) Button area Three buttons are provided to export overview table,neighboring cell analysis results of test cell, and allneighboring cell analysis results.

8.10.2 Interface Description: GSM/UMTS Possible NeighboringCell Analysis

This section describes the interface for GSM/UMTS possible neighboring cell analysis. Beforeperforming relevant operations, familiarize yourself with the functions of the areas on theinterface.

The possible neighboring cell analysis result is displayed in tables, which consist of a possibleneighboring cell overview table and a possible neighboring cell confirmation table, as shown inFigure 8-3.



209

Figure 8-3 Interface of analyzing GSM/UMTS possible neighboring cells


(1) Possibleneighboring celloverview table

Displays the aggregation information of UMTS possibleneighboring cells of all the cells involved in the task in a table.

(2) Possibleneighboring cellconfirmation table

Displays all the UMTS possible neighboring cells of the cellselected in Area (1).

8.10.3 Parameters of GSM/UMTS Neighboring Cell Data E2E TasksThis section describes the parameters for creating GSM E2E tasks. You can refer to thedescription when creating a GSM E2E task.


Basicinformation

Task Name Indicates the name of a GSM/UMTS neighboringcell measurement task.


E2E Task List Select the GSM/UMTS Neighboring Cell AnalysisData Task node.


Begin Time Indicates the time when the task starts to run.The start time must be later than the current time. Bydefault, the start time is five minutes later than thecurrent system time.

Period Interval between the ARFCNs of each group.



210


Step Indicates the number of ARFCNs in the same group.The value is an integer from 1 to 32.The measurement step must be less than or equal tothe minimum rest step of the selected cell.


Indicates the total duration which a measurementtask is performed.The value is an integer from 2 to 95. The unit is *15(minute), that is, the value must be multiples of 15minutes.

Cycle Indicates the interval between periodic tasks.

Execute Times Indicates the times that a periodic task is executed.If this parameter is set to 0, you can infer that the taskis executed all the time.The value is an integer from 0 to 30.

NE Object Indicates the NE object related to the GSM/UMTSneighboring cell data task.

Related Tasks8.3.1 Creating GSM/UMTS Neighboring Cell Measurement Data E2E Tasks






ExecutionType









211


Runimmediately



ExecutionInterval



ExecutionTimes








Collect AllNE





212


Collect ByNE Type









8.10.5 Parameters for Creating and Modifying GSM/UMTSNeighboring Cell Analysis Tasks

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








213





ExecutionDelay






Neighboring Cell CountSetting

Indicates the threshold of the neighboring cell sequencenumber. All the undefined neighboring cells whose sequencenumbers are smaller than or equal to the value of thisparameter are regarded as missing neighboring cells. All thedefined neighboring cells whose sequence numbers are largerthan the value of this parameter are regarded as redundantneighboring cells.This parameter can be set to any integer from 3 to 32. Thedefault value is 26.

Omni gain Indicates the omnidirectional gain of an antenna.This parameter can be set to any integer from 0 to 15. Thedefault value is 11.Unit: dBi



214


Directional gain Indicates the directional gain of an antenna.This parameter can be set to any integer from 0 to 25. Thedefault value is 17.Unit: dBi

Number of undefinedneighboring cells to bedisplayed

Indicates that only the TopN undefined neighboring cells aredisplayed.N can be any integer from 20 to 50. The default value is 30.

Related Tasks8.4 Creating GSM/UMTS Neighboring Cell Analysis Tasks

8.10.6 Parameters for Querying the Analysis Reports of GSM/UMTS Neighboring Cells

This section describes the parameters for querying the analysis reports of GSM/UMTSneighboring cells. You can refer to the description when querying the analysis reports of GSM/UMTS neighboring cells.

Description of Parameters About a Test CellParameter Description

BSC Where Test CellIs Located

Indicates the name of the BSC that a test cell belongs to, for example,BSC_1.

Test Cell Name Indicates the name of a test cell, for example, Cell_1.

FDD REP QUANT Indicates the signal receiving indicator of the UMTS neighboring cellreported in the FDD cell test report, for example, Ec/NO or RSCP.

Total Number ofMRs

Indicates the total number of MRs received by a test cell.

Number ofRedundantNeighboring Cells

Indicates the number of redundant neighboring UMTS cells of thecurrent test cell.

Percentage of MRson RedundantNeighboring Cells(%)

Indicates the sum of the integrated priority of the redundantneighboring UMTS cells of the current test cell.

Number of MissingNeighboring Cells

Indicates the number of missing neighboring UMTS cells of thecurrent test cell.



215


Percentage of MRson MissingNeighboring Cells(%)

Indicates the sum of the integrated priority of the missing neighboringUMTS cells of the current test cell.

LAC Indicates the location area code of the current test cell.

CI Indicates the identification code of the current test cell.

BCCH Indicates the broadcast control channel of the current test cell.

BSIC Indicates the base station identity code of the current test cell.

Service Type of TestCell

Indicates the service type of the current test cell, such as indoor siteand outdoor site. Learning the service type of the test cell preventsimportant neighboring cells from being mistakenly deleted.

Test Cell ID Indicates the ID of the current test cell.

Description of Parameters About the Neighboring UMTS CellsParameter Description

Neighboring UMTSCell Name

Indicates the name of a defined or undefined neighboring UMTS cellof the current test cell.

RNC ID Indicates the ID of the RNC that the neighboring UMTS cell belongsto.

UMTS CI Indicates the cell identity of a neighboring UMTS cell.

Downlink ARFCN Indicates the downlink ARFCNs of a neighboring UMTS cell.

P-SC Indicates the primary scrambling code of a neighboring UMTS cell.

DefinedNeighboring Cell

Indicates whether the selected cell is the defined neighboring cell ofthe current test cell.

Suggested Operation Indicates the operation suggestions that the Nastar provides.The options are Missing Neighboring Cell, RedundantNeighboring Cell, or NA.

User Modify Indicates whether the user operations are recommended.If this option is selected, you are advised to perform modificationaccording to Suggested Operation. Otherwise, no user operation isrecommended.

Total Score Indicates the total score of each neighboring cell based on themeasurement result according to the neighboring cell algorithm.

Integrated Priority Indicates the integrated priority of the neighboring UMTS cell.



216


Service Type ofNeighboring Cell

Indicates the service type of a neighboring UMTS cell, such as indoorsite and outdoor site. Learning the service type of the neighboringUMTS cell prevents important neighboring cells from beingmistakenly deleted.

Distance (km) Indicates the distance from the current test cell to a neighboringUMTS cell.

Test Duration in BAList (minute)

Indicates the duration that a neighboring UMTS cell is measured.

UMTS NeighboringCell RSCP(dBm)/ECNO(dB)

Indicates the average RSCP/ECNO of UMTS neighboring cells. TestFDD REP QUANT to decide whether the data reported by UMTSneighboring cell is the RSCP or the ECNO.

Source Cell SignalStrength (dBm)

Indicates the average signal strength of the selected test cell.

Number of MRs withUMTS Cell

Indicates the number of MRs including the UMTS neighboring cell.

Number of MRs withUMTS Cell RankingFirst

Indicates the number of times a UMTS cell ranking No.1 in theneighboring cell list of MR.

Related Tasks8.5 Querying GSM/UMTS Neighboring Cell Analysis Results

8.10.7 Parameters for Querying the Analysis Reports of GSM/UMTS Possible Neighboring Cells

This section describes the parameters for querying the analysis reports of GSM/UMTS possibleneighboring cells. You can refer to the description when querying the analysis reports of GSM/UMTS possible neighboring cells.

Description of Parameters in the Possible Neighboring Cell Overview Table


Test Cell Name Indicates the name of the test serving cell, for example, Cell_1.

FDD REP QUANT Indicates the signal receiving indicator of the UMTS neighboring cellreported in the FDD cell test report, for example, Ec/NO or RSCP.

Test Cell CGI Indicates the global ID of a test cell, for example,286-01-33034-50712.

Test Cell BCCH Indicates the broadcast control channel of a test cell.

Test Cell BSIC Indicates the base station identity code of a test cell.



217


Neighboring CellDownlink ARFCN

Indicates the measured downlink ARFCNs of a neighboring UMTScell.

Neighboring Cell P-SC

Indicates the measured primary scrambling code of a neighboringUMTS cell.

RNC ID of theSelected PossibleNeighboring Cell

Indicates the number of the RNC that the selected possibleneighboring UMTS cell belongs to.

Name of the SelectedPossible NeigboringCell

Indicates the name of the selected possible neighboring UMTS cell.

Neighboring Cell CI Indicates the cell identity code of the selected possible neighboringUMTS cell.

Distance(km) Indicates the distance from the test cell to the selected possible UMTSneighboring cell.

Relative Angle ofNeigboring Cell (°)

Indicates the relative angle between the selected possible neighboringUMTS cell and the test cell.

Predicted SignalStrength (dBm)

Indicates the signal strength of the selected possible UMTSneighboring cell based on the dimensioning.

Obtain FromConfiguration Data

Indicates whether the selected possible neighboring UMTS cell isobtained from the configuration data.

Number ofNeighboring CellLaps

Indicates the number of laps between the selected possible UMTSneighboring cell and the test cell, that is, the number of cells betweenthe selected possible neighboring UMTS cell and the test cell.

Number of PossibleNeighboring Cells inthe PossibleNeighboring CellPairs

Indicates the number of possible neighboring cells in the possibleneighboring UMTS cell pair.

Total Score Indicates the total score of each neighboring cell based on themeasurement result according to the neighboring cell algorithm.

UMTS NeighboringCell RSCP(dBm)/ECNO(dB)

Indicates the average RSCP/ECNO of UMTS neighboring cells. TestFDD REP QUANT to decide whether the data reported by UMTSneighboring cell is the RSCP or the ECNO.

Source Cell SignalStrength (dBm)

Indicates the average signal strength of the selected test cell.

Number ofNeighboring CellMeasurementReports

Indicates the number of MRs of a UMTS neighboring cell.



218


Number of Times aNeighboring CellRanks Number 1 inMRs

Indicates the number of times a UMTS cell ranking No.1 in theneighboring cell list of MR.



219

Description of Parameters in the Possible Neighboring Cell Confirmation TableParameter Description

Whether to Use Indicates whether to select the current possible neighboring UMTScell as the most possible neighboring cell of the test cell.l If the parameter is selected, it indicates that the current possible

neighboring UMTS cell serves as the most possible neighboringUMTS cell of the test cell. In addition, you need to replace theinformation about the selected possible neighboring cell in thepossible neighboring cell confirmation table with thecorresponding information in the possible neighboring celloverview table.– Name of the Selected Possible Neighboring Cell replaces

Neighboring Cell Name.– RNC ID of the Selected Possible Neighboring Cell replaces

Neighboring RNC.– CI replaces Neighboring Cell CI.– Distance(km) replaces Distance(km).– Relative Angle of Neighboring Cell(°) replaces Relative

Angle of Neighboring Cell(°).– Predicted Signal Strength (dBm) replaces Predicted Signal

Strength (dBm).– Obtain From Configuration Data replaces Obtain From

Configuration Data.– Number of Neighboring Cell Laps replaces Number of

Neighboring Cell Laps.l If this parameter is not selected, it indicates that the most possible

neighboring cell is not determined. In addition, the system clearsall the information in the following fields in the possibleneighboring cell overview table:– Name of the Selected Possible Neighboring Cell– RNC ID of the Selected Possible Neighboring Cell– Neighboring Cell CI– Number of Neighboring Cell Laps– Relative Angel of Neighboring Cell (°)– Predicted Signal Strength (dBm)– Obtain From Configuration Data– Number of Neighboring Cell Laps

Name of PossibleNeighboring Cell

Indicates the cell name of a possible neighboring UMTS cell.

RNC ID Indicates the ID of the RNC that a possible neighboring UMTS cellbelongs to.

CI Indicates the cell identity of a possible neighboring UMTS cell.



220


Distance(km) Indicates the distance from the test cell to a possible neighboringUMTS cell.

Relative Angle ofNeighboring Cell(°)

Indicates the relative angle between the test cell and a possibleneighboring UMTS cell.

Predicted SignalStrength (dBm)

Indicates the signal strength of a possible neighboring UMTS cellbased on the dimensioning.

Obtain FromConfiguration Data

Indicates whether the possible neighboring UMTS cell is obtainedfrom the configuration data.

Number of PossibleNeighboring CellLaps

Indicates the number of laps between the test cell and a possibleneighboring UMTS cell, that is, the number of cells between the testcell and a possible neighboring UMTS cell.

Related Tasks8.6 Querying GSM/UMTS Possible Neighboring Cell Analysis Results



221

9 GSM Frequency Analysis

About This Chapter

The GSM frequency analysis function enables you to obtain GSM frequency analysis data, createGSM frequency analysis tasks, query and export GSM frequency analysis results, and query andexport GSM frequency optimization results. The Nastar provides the interference matrix analysisfunction 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 frequencyoptimization scheme based on frequency interference matrix and judge the usability of thescheme based on frequency optimization results. You are advised to perform neighboring cellanalysis before starting frequency analysis. This helps to improve the accuracy of neighboringcell identification and enable the Nastar to generate a correct interference model.

9.1 Basic Knowledge of GSM Frequency AnalysisThis section describes the basic knowledge of GSM frequency analysis, including frequencyanalysis function, frequency analysis process, frequency optimization process, and GSMARFCN spacing rules. The basic knowledge helps you perform GSM frequency analysis andoptimization.

9.2 Process of GSM Frequency AnalysisThis section describes the process of GSM frequency analysis.

9.3 Obtaining GSM Frequency Analysis DataThis section describes how to enable the Nastar to obtain GSM frequency analysis data. Youcan create an E2E task to enable the Nastar to collect analysis data and create a data import taskso that the Nastar imports the collected analysis data into the database.

9.4 Creating GSM Frequency Analysis TasksThis section describes how to create GSM frequency analysis tasks. After you create a GSMfrequency analysis task, the Nastar periodically analyzes GSM performance data, GSMneighboring cell measurement data, GSM configuration data, and engineering parameters in theNastar database. By querying analysis results, you can learn about the status of the entire radionetwork so that problems can be located and solved efficiently.

9.5 Querying GSM Frequency Analysis ResultsThis section describes how to query GSM frequency analysis reports. GSM frequency analysisresults contain the measurement cell overview information, interference matrix informationabout GSM cells, and frequency interference matrix information about GSM cells. Based on theinterference matrix information and frequency interference matrix information in the analysis

iManager NastarNetwork Optimization User Guide (GSM) 9 GSM Frequency Analysis


222

results, you can identify the cells and ARFCNs that cause strong interference and the cells andARFCNs that are greatly affected by the interference on the network.

9.6 Querying GSM Frequency Optimization ResultsThis section describes how to query GSM frequency optimization results. You can either enablethe Nastar to automatically perform frequency optimization or manually set relevant parameterson the Nastar to perform frequency optimization.

9.7 Exporting GSM Frequency Analysis ReportsThis section describes how to export GSM frequency analysis reports. You can export the queriedfrequency analysis results as .csv, .xls or .xlsx files and import these files into the other softwarefor solving cell frequency interference problems in networks.

9.8 Exporting GSM Frequency Optimization ReportsThis section describes how to export GSM frequency optimization reports. You can export thequeried frequency optimization results as .csv, .xls, or .xlsx files for further comparison andanalysis.

9.9 Technical Specifications for GSM Frequency AnalysisThis section describes the technical specifications for GSM frequency analysis.

9.10 Reference for the GSM Frequency Analysis GUIThis section describes the interface for GSM frequency analysis and the relevant parameters.Before performing relevant operations, familiarize yourself with the GSM frequency analysisfunctions.

9.11 How Do I Handle the Failure to Execute a GSM Frequency Analysis Task Whose ProgressBar Stays at 13% or 75% But the Task Status is Displayed As Finished?This section describes the cause of the failure to execute a GSM frequency analysis task andhow to solve the problem.



223

9.1 Basic Knowledge of GSM Frequency AnalysisThis section describes the basic knowledge of GSM frequency analysis, including frequencyanalysis function, frequency analysis process, frequency optimization process, and GSMARFCN spacing rules. The basic knowledge helps you perform GSM frequency analysis andoptimization.

9.1.1 GSM Frequency Analysis FunctionThe GSM frequency analysis function provides analysis of interference matrices formeasurement cells and frequencies. GSM frequency analysis can generate interference matricesof analyzed cells, which can be exported for ARFCN analysis on other tools. GSM frequencyanalysis enables users to optimize cells with poor quality of service (QoS) by ARFCN (one byone) in combination with the frequency configuration scheme of the network.

GSM Frequency Analysis

The Nastar provides the interference traffic of each neighboring cell of a measurement cell andprovides the interference matrix of each cell in a report.

The generated interference matrices are based on the real traffic volume of the network. In thismanner, the Nastar can accurately calculate the ratio of the interference traffic to the cell trafficduring frequency adjustment.

Before performing frequency analysis, check whether any defined neighboring cell of themeasurement cell shares the same ARFCN and the same BSIC with other neighboring cells. Ifa defined neighboring cell or an undefined neighboring cell close to the measurement cell sharesthe same BCCH ARFCN and the same BSIC with other neighboring cells, the network stabilityand accuracy of frequency analysis are affected.

GSM frequency analysis results can be exported as .csv files, .xls files, or .xlsx files. In addition,the GSM interference matrix data can be exported as a .txt file and then imported into the Celloptsoftware for re-planning network frequencies.

Requirements for the Network

The network must be relatively stable during the period of performance data for frequencyanalysis. Otherwise, the accuracy of the frequency analysis cannot be guaranteed. Table 9-1describes the network changes and their impacts.



Addition or deletion ofBTSs

Affects the network coverage and handovers between cells. Inthis case, analysis results cannot accurately reflect the currentnetwork status.

Change of antenna data,such as azimuth, tiltangle, or height

Results in changes of cell coverage and network interference.



224


Changes of transmitpower and parametersrelated to power such asdiscontinuoustransmission and powercontrol

Results in changes of cell coverage and network interference.

Change of frequencyplanning (for example, anew frequency planningscheme is implementedon the network.)

The change of configuration data affects the identification ofdefined cells and undefined cells. In this case, analysis resultscannot accurately reflect the current network status. You areadvised to keep the network stable during data collection.

Change of handoverrelations and parameters

Affects the statistical results during the period of collecting thedata about neighboring relations and the period of optimizingneighboring relations.

Change of BSC topologyor other networktopology

The BSC is responsible for collecting statistical results.Therefore, the measurement task will not be performed properlyif the network topology is changed. You are advised to keep thenetwork topology unchanged during data collection.

9.1.2 Introduction to Process of GSM Frequency AnalysisThis section describes the process of GSM frequency analysis, which helps you conductfrequency analysis more efficiently.

The mechanism of GSM frequency analysis is as follows: The Nastar identifies the interferencebetween a measurement cell and its intra-frequency cells and cells on adjacent ARFCNs,evaluates the frequency planning results, and then analyzes the cells and ARFCNs with stronginterference on the current network. For details about the mechanism, see Figure 9-1.



225

Figure 9-1 Process of GSM frequency analysis

9.1.3 Process of GSM Frequency OptimizationThis section describes the process of GSM frequency optimization, which helps you conductfrequency optimization more efficiently.

The mechanism for frequency optimization is as follows: The Nastar identifies the frequencyinterference when a measurement cell in a frequency interference matrix is configured with thecurrent BCCH and TCH among the candidate ARFCNs. Then, it assigns a proper BCCH andproper TCHs for each measurement cell. For details about the mechanism, see Figure 9-2.



226

Figure 9-2 Process of GSM frequency optimization

9.1.4 GSM ARFCN Spacing RulesThis section describes the spacing rules for GSM absolute radio frequency channel numbers(ARFCNs), which facilitates frequency optimization.

Table 9-2 shows the spacing rules for GSM ARFCNs.

NOTE

l The ARFCNs that violate co-site spacing rules are highlighted in pink with the legend . The

ARFCNs that violate co-cell spacing rules are highlighted in red with the legend . The ARFCNs

that violate neighboring cell spacing rules are highlighted in orange with the legend .

l The ARFCNs are highlighted by their class priorities in the following descending order: co-cell ARFCNs,co-site ARFCNs, and neighboring cell ARFCNs. If an ARFCN violates multiple spacing rules, this ARFCNis highlighted in the color based on its highest class priority.

l Assume that the ARFCN spacing is set to N.

l For and , the range of ARFCNs that violate spacing rules is [CurrentARFCN - N + 1, Current ARFCN + N - 1].

l For , the range of ARFCNs that violate spacing rules is [Current ARFCN - N + 1, currentARFCN) and (Current ARFCN, Current ARFCN + N - 1].

l If N is 0, ARFCN values are not limited.



227

Table 9-2 Description of GSM ARFCN spacing rules

Class

Subclass

Description Example

Co-site

BetweenBCCHARFCNs

If a BCCH ARFCN ofa cell violates anARFCN spacing rulefor a BCCH ARFCN ofthe selected co-site cell,this BCCH ARFCN ishighlighted in pink inBCCH.

Scenario: Three co-site cells are Cell A, Cell B, andCell C. The BCCH ARFCN spacing is set to 2.CellB_BCCH=16 and CellC_BCCH=20.Purpose: To set BCCH ARFCNs for Cell A.Result: According to the ARFCN spacing rule,CellA_BCCH must not be set to 15, 16, 17, 19, 20,or 21. If these ARFCNs are present in the candidateBCCH ARFCNs of Cell A, these ARFCNs arehighlighted in pink, indicating that these ARFCNsviolate the BCCH ARFCN spacing rule for co-sitecells. These ARFCNs are not recommended.

BetweenTCHARFCNs

If a TCH ARFCN of acell violates an ARFCNspacing rule for a TCHARFCN of the selectedco-site cell, this TCHARFCN is highlightedin pink in TCH.

Scenario: Three co-site cells are Cell A, Cell B, andCell C. The TCH ARFCN spacing is set to 2.CellB_TCH=8, 21, and CellC_TCH=4, 13.Purpose: To set TCH ARFCNs for Cell A.Result: According to the ARFCN spacing rule,CellA_TCH must not be set to 3, 4, 5, 7, 8, 9, 12, 13,14, 20, 21, or 22. If these ARFCNs are present in thecandidate TCH ARFCNs of Cell A, these ARFCNsare highlighted in pink, indicating that theseARFCNs violate the TCH ARFCN spacing rule forco-site cells. These ARFCNs are not recommended.

BetweenBCCHARFCNsandTCHARFCNs

l If a TCH ARFCN ofa cell violates aspacing rulebetween BCCHARFCNs and TCHARFCNs for aBCCH ARFCN ofthe selected co-sitecell, this TCHARFCN ishighlighted in pinkin TCH.

l If a BCCH ARFCNviolates a spacingrule between BCCHARFCNs and TCHARFCNs for a TCHARFCN of theselected co-site cell,this BCCH ARFCNis highlighted inpink in BCCH.

Scenario: Three co-site cells are Cell A, Cell B, andCell C. The spacing between BCCH ARFCNs andTCH ARFCNs is set to 2. CellB_BCCH=16,CellC_BCCH=20, CellB_TCH=8, 21, andCellC_TCH=4, 13.Purpose: To set a BCCH ARFCN and TCHARFCNs for Cell A.Result: According to the ARFCN spacing rule,CellA_TCH must not be set to 15, 16, 17, 19, 20, or21; CellA_BCCH must not be set to 3, 4, 5, 7, 8, 9,12, 13, 14, 20, 21, or 22. If these ARFCNs arepresent in the candidate TCH ARFCNs andcandidate BCCH ARFCNs of Cell A, theseARFCNs are highlighted in pink, indicating thatthese ARFCNs violate the spacing rule betweenBCCH ARFCNs and TCH ARFCNs for co-sitecells. These ARFCNs are not recommended.



228

Class

Subclass

Description Example

Co-cell

BetweenBCCHARFCNs

Each cell has only oneBCCH ARFCN.Therefore, no spacingrule is required forBCCH ARFCN of onecell. The defaultspacing is 0, whichmeans no limitation onARFCNs.

-

BetweenTCHARFCNs

If a TCH ARFCNviolates an ARFCNspacing rule for a TCHARFCN of the selectedcell, this TCH ARFCNis highlighted in red inTCH.

Scenario: The selected cell is Cell A. The co-cellTCH ARFCN spacing is set to 2. CellA_TCH=27,51, 61.Purpose: To set new TCH ARFCNs for Cell A.Result: According to the ARFCN spacing rule,CellA_TCH must not be set to 26, 28, 50, 52, 60, or62. If these ARFCNs are present in the candidateTCH ARFCNs of Cell A, these ARFCNs arehighlighted in red, indicating that these ARFCNsviolate the co-cell TCH ARFCN spacing rule. TheseARFCNs are not recommended.


l If a TCH ARFCNviolates a spacingrule between BCCHARFCNs and TCHARFCNs for theBCCH ARFCN ofthe selected cell,this TCH ARFCN ishighlighted in red inTCH.

l If a BCCH ARFCNviolates a spacingrule between BCCHARFCNs and TCHARFCNs for a TCHARFCN of theselected cell, thisBCCH ARFCN ishighlighted in red inBCCH.

Scenario: The selected cell is Cell A. The spacingbetween the BCCH ARFCN and TCH ARFCNs ofone cell is set to 2. CellA_BCCH=15 andCellA_TCH=27, 51, 61.Purpose: To set a BCCH ARFCN and TCHARFCNs for Cell A.Result: According to the ARFCN spacing rule,CellA_TCH must not be set to 14 or 16.CellA_BCCH must not be set to 26, 28, 50, 52, 60,or 62. If these ARFCNs are present in the candidateTCH ARFCNs and candidate BCCH ARFCNs ofCell A, these ARFCNs are highlighted in red,indicating that these ARFCNs violate the spacingrule between the BCCH ARFCN and TCH ARFCNsfor one cell. These ARFCNs are not recommended.



229

Class

Subclass

Description Example

Neighboringcell

BetweenBCCHARFCNs

If a BCCH ARFCNviolates an ARFCNspacing rule for theBCCH ARFCN of adefined neighboringcell of the selected cell,this BCCH ARFCN ishighlighted in orange inBCCH.

Scenario: The serving cell is Cell A, and its definedneighboring cells are Cell B, Cell C, and Cell D. Thespacing for BCCH ARFCNs between the servingcell and its neighboring cells is set to 2.CellB_BCCH=16, CellC_BCCH=19, andCellD_BCCH=27.Purpose: To set BCCH ARFCNs for Cell A.Result: According to the ARFCN spacing rule,CellA_BCCH must not be set to 15, 16, 17, 18, 19,20, 26, 27, or 28. If these ARFCNs are present in thecandidate BCCH ARFCNs of Cell A, theseARFCNs are highlighted in orange, indicating thatthese ARFCNs violate spacing rules for BCCHARFCNs between the serving cell and itsneighboring cells. These ARFCNs are notrecommended.

BetweenTCHARFCNs

If a TCH ARFCNviolates an ARFCNspacing rule for a TCHARFCN of a definedneighboring cell of theselected cell, this TCHARFCN is highlightedin orange in TCH.

Scenario: The serving cell is Cell A, and its definedneighboring cells are Cell B, Cell C, and Cell D. Thespacing for BCCH ARFCNs between the servingcell and its neighboring cells is set to 2.CellB_TCH=16, 19, CellC_TCH=27, 45, andCellD_TCH=87, 102.Purpose: To set TCH ARFCNs for Cell A.Result: According to the ARFCN spacing rule,CellA_TCH must not be set to 15, 16, 17, 18, 19, 20,26, 27, 28, 44, 45, 46, 86, 87, 88, 101, 102, or 103.If these ARFCNs are present in the candidate TCHARFCNs of Cell A, these ARFCNs are highlightedin orange, indicating that these ARFCNs violate thespacing rule for TCH ARFCNs between the servingcell and its neighboring cells. These ARFCNs arenot recommended.



230

Class

Subclass

Description Example


l If a TCH ARFCNviolates a spacingrule between BCCHARFCNs and TCHARFCNs for theBCCH ARFCN of adefinedneighboring cell ofthe selected cell,this TCH ARFCN ishighlighted inorange in TCH.

l If a BCCH ARFCNviolates a spacingrule between BCCHARFCNs and TCHARFCNs for a TCHARFCN of adefinedneighboring cell ofthe selected cell,this BCCH ARFCNis highlighted inorange in BCCH.

Scenario: The serving cell is Cell A, and its definedneighboring cells are Cell B, Cell C, and Cell D. TheARFCN spacing between the serving cell and itsneighboring cells is set to 2. CellB_BCCH=16,CellC_BCCH=19, CellD_BCCH=27,CellB_TCH=16, 19, CellC_TCH=27, 45, andCellD_TCH=87, 102.Purpose: To set a BCCH ARFCN and TCHARFCNs for Cell A.Result: According to the ARFCN spacing rule,CellA_BCCH must not be set to 15, 16, 17, 18, 19,20, 26, 27, 28, 44, 45, 46, 86, 87, 88, 101, 102, or103. CellA_TCH must not be set to 15, 16, 17, 18,19, 20, 26, 27, or 28. If these ARFCNs are presentin the candidate TCH ARFCNs and candidateBCCH ARFCNs of Cell A, these ARFCNs arehighlighted in orange, indicating that these ARFCNsviolate spacing rules between BCCH ARFCNs andTCH ARFCNs for the serving cell and itsneighboring cells. These ARFCNs are notrecommended.

9.2 Process of GSM Frequency AnalysisThis section describes the process of GSM frequency analysis.

Figure 9-3 shows the process of GSM frequency analysis.



231

Figure 9-3 Process of GSM frequency analysis




232

Table 9-3 Description on process of GSM frequency analysis


1 Create a GSMneighboring cellmeasurement dataE2E task

You need to choose Maintenance > E2E TaskManagement on the Nastar client to open the E2E TaskManagement window and then create a E2E task. After youcreate the task, the Nastar sends the commands to M2000 forenabling the performance counters.

2 Creating a GSMMeasure Task Filefor Neighbor CellData CollectionTask

You need to choose Maintenance > Task Management onthe Nastar client to open the Task Management window andthen create a GSM measure task file for neighbor cell datacollection task. After the task is created, the Nastarperiodically obtains the GSM measure task file for neighborcell data from the M2000 and then saves the data in files onthe Nastar server.

3 Create a GSMperformance datacollection task


4 Create a GSMperformance dataimport task/Createa GSMneighboring cellmeasurement taskfile import task

You need to choose Maintenance > Task Management onthe Nastar client to open the Task Management window andthen create a GSM performance data import task and a GSMneighboring cell measurement task file import task. After thetasks are created, the GSM performance data in files and datain GSM neighboring cell measurement task files saved on theNastar server are imported into the database periodically.

5 Check the integrityof GSM frequencyanalysis data

You can double-click System Function > Data Query in theAnalysis Task Management window on the Nastar client toopen the Query Data dialog box and then check whether allthe required GSM frequency analysis data is imported intothe database.

6 Create a GSMfrequency analysistask

In the Analysis Task Management window on the Nastarclient, you can create a GSM neighboring cell analysis task.After you create the task, the Nastar periodically retrieves theGSM performance data, GSM neighboring cell measurementdata, and GSM configuration data from the database,analyzes the retrieved data, and then generates the analysisresults.

7 l View GSMfrequencyanalysis results

l View GSMfrequencyoptimizationresults

After a GSM frequency analysis task is executedsuccessfully, you can view the analysis results, identify thestrongly interfered cells and ARFCNs, and evaluate thefrequency planning results.



233


8 l Export GSMfrequencyanalysis report

l Export GSMfrequencyoptimizationreport

You can export GSM frequency analysis reports through theNastar client.

9.3 Obtaining GSM Frequency Analysis DataThis section describes how to enable the Nastar to obtain GSM frequency analysis data. Youcan create an E2E task to enable the Nastar to collect analysis data and create a data import taskso that the Nastar imports the collected analysis data into the database.

9.3.1 Creating GSM Neighboring Cell Measurement Data E2ETasks



l The OSS and NEs related to the analysis task are created. For details, see 2.2 CreatingOSSs and the Managed NEs.

l Configuration data is imported into the Nastar database. For details, see 3.3 ImportingConfiguration Data.


Context


CAUTIONBefore refarming, stop the running neighboring GSM cell measurement data E2E task to avoidimpact on NEs.



234

ProcedureStep 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is

displayed.



Step 3 Set the basic task information.1. In the Task Name field, enter the name of the analysis data E2E task.2. In the OSS Name drop-down list box, select an OSS for the task.3. In the E2E Task Management > E2E Task List, choose *** Analysis Data Task.

Step 4 Click Next.

Step 5 Set Run Type, Time Setting, and Cycle Setting for the task.You need to set Cycle Setting only when Run Type is set to Period.

Step 6 Click Next.

Step 7 On the Measure Task tab page, set Duration Time (Minute), Period, and Measure Step.l Duration Time (Minute) indicates the total duration of the measurement task execution.l Period indicates the interval at which each group of ARFCNs is measured.l Measure Step indicates the number of ARFCNs in a group.

NOTE

The measurement duration cannot exceed 24 hours.

Step 8 Select a cell to be analyzed from the object navigation tree.NOTE

l Only the cells activated on the M2000 can be selected.l BA2 quantity:** of the cell name indicates the quantity of the BA2 of the cell. The BA2 list contains

a maximum of 32 ARFCNs.


Step 9 Click Frequency Analysis.

The Nastar traverses the three-level neighboring cells of the selected cell. Then, the Nastaranalyzes the BCCH ARFCNs of the traversed neighboring cells and highlights these BCCHARFCNs in the frequency selection area in gray to provide reference for selecting measurementARFCNs.

Traversing of the three-level neighboring cells indicates that the Nastar searches for theneighboring cell (neighboring cell A) of the selected cell, the neighboring cell (neighboring cellsB) of neighboring cell A, and the neighboring cell (neighboring cells C) of neighboring cell B.All traversed neighboring cells A, B, and C are neighboring cells obtained through the traversingof the three-level neighboring cells.

Step 10 Select ARFCNs for the BA2 list in the frequency selection area.

After you select frequencies for the BA2 list, the levels of neighboring cells are measured in acell based on the selected ARFCNs so that possible missing neighboring cells can be determined.



235

The BA2 list contains a maximum of 32 ARFCNs. If the number of selected ARFCNs exceeds32, the ARFCNs in the BA2 list are modified periodically and cyclically.

The selected ARFCNs are grouped according to the value of Measure Step and you can viewthe groups in the Selected Frequency area.

Step 11 Set the soft parameters of the neighboring cell measurement data task.

1. Click the Soft Parameter tab.

2. Select Soft Parameter Setting.

3. Set the threshold of each soft parameter.

For the detailed description of soft parameters, see 9.10.3 Parameters of GSMNeighboring Cell E2E Tasks.

Step 12 Click Complete.The added GSM neighboring cell measurement data task is displayed in the task list.

----End

Follow-up Procedure

In the task list on the right of the E2E Task Management window, select one analysis data E2Etask to view, delete, refresh, or cancel it.








Related References9.10.3 Parameters of GSM Neighboring Cell E2E Tasks

9.3.2 Creating a GSM Measure Task File for Neighbor Cell DataCollection Task

After you create a GSM measure task file for neighbor cell data collection task on the Nastar,the Nastar periodically collects measure task file for neighbor cell data on the M2000 and savesthe data in a specified path for future GSM network analysis.



236


GSM measure task file for neighbor cell data already exists on the M2000. For details, see9.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks.

Contextl A GSM measure task file for neighbor cell data collection task is a user-defined timing

task.l A GSM measure task file for neighbor cell data collection task can be executed only once

or periodically. The options of the execution period are Minute, Hour, Day, Week, andMonth.

ProcedureStep 1 Choose Maintenance > Task Management. The Task Management window is displayed.




Step 4 Click Next.

1. Click and select the start time of the task in the displayed Time Setting dialog box.NOTE

l Start Time must be later than the current time of the server.l If Run Type of the task is set to Once, the Start Time parameter is unavailable after you select

the Run At Once check box. This task is executed immediately after it is created.





You can set half an hour or one hour as atask execution period for collectingmeasure task file for neighbor cell data.

b. Perform Step 5.




237

1. From the OSS Name drop-down list, select the name of the OSS that manages the NE tobe analyzed.

2. Select GSM Measure Task File for Neighbor Cell Data from the Data Type drop-downlist box.

3. Set the parameters in the Task Parameter field.TIP

l Select one or more NEs, thus the related data of the NEs are periodically collected to a certaindirectory of the Nastar.

l Select Specify the time range and set Start time and End time to collect related data from theM2000 side periodically or once within the specified time period. Then, save the data under aspecified directory of the Nastar.


----End

9.3.3 Creating a GSM Performance Data Collection TaskAfter you create a GSM performance data collection task on the Nastar, the Nastar periodicallycollects NE performance data on the M2000 and saves the data in a specified path for futureGSM frequency analysis.


GSM performance data already exists on the M2000. For details, see 9.3.1 Creating GSMNeighboring Cell Measurement Data E2E Tasks.

Contextl A GSM performance data collection task is a user-defined timing task.l A GSM performance data collection task can be executed only once or periodically. The

options of the execution period are Minute, Hour, Day, Week, and Month.

Procedure





Step 4 Click Next.




238

NOTE








b. Perform Step 5.


1. From the OSS drop-down list, select the name of the OSS that manages the NE to beanalyzed.

2. Select Performance data from the Data Type drop-down list box.







----End




239








Analysis TaskType



Manual creation



Manual creation



Manual creation



Manual creation



Manual creation


Manual creation


- -



Manual creation



240

Analysis TaskType




Manual creation




Manual creation



Manual creation



Manual creation



Manual creation



Manual creation

UMTS VIPAnalysis


Manual creation


- -



Manual creation



Manual creation



Manual creation




Manual creation



Manual creation



241

Analysis TaskType




Manual creation




Manual creation


- -




Manual creation




Manual creation



Manual creation

CDMA VIPAnalysis


Manual creation



Manual creation


Manual creation



Manual creation



Manual creation


- -



242

Analysis TaskType



- -

Procedure





Periodic.



NOTE




----End









243


























244


































245






















-

Procedure


TIP






246




----End

9.4 Creating GSM Frequency Analysis TasksThis section describes how to create GSM frequency analysis tasks. After you create a GSMfrequency analysis task, the Nastar periodically analyzes GSM performance data, GSMneighboring cell measurement data, GSM configuration data, and engineering parameters in theNastar database. By querying analysis results, you can learn about the status of the entire radionetwork so that problems can be located and solved efficiently.





Procedure





Step 3 Click Next.




Step 5 On the Set parameters tab page, set Frequency Analysis Parameter.

Step 6 Click Next.




247



If... Then...








2. Set Execution Delay.3. Optional: On the Set Busy Hours tab, select Busy


NE Group is selected 1. Set Time Range and Execution Delay.2. Optional: On the Set Busy Hours tab, select Busy



----End






248






Resume.



Related References9.10.5 Parameters for Creating and Modifying GSM Frequency Analysis Tasks

9.5 Querying GSM Frequency Analysis ResultsThis section describes how to query GSM frequency analysis reports. GSM frequency analysisresults contain the measurement cell overview information, interference matrix informationabout GSM cells, and frequency interference matrix information about GSM cells. Based on theinterference matrix information and frequency interference matrix information in the analysisresults, you can identify the cells and ARFCNs that cause strong interference and the cells andARFCNs that are greatly affected by the interference on the network.

Procedure

Step 1 Choose Theme Function > GSM Frequency Analysis Task from the navigation tree on theleft of the Analysis Task Management window.

Step 2 Select a GSM frequency analysis task from the task list on the upper right of the Analysis TaskManagement window.The analysis results of the selected task are displayed in the analysis result list in lower rightpane.


Step 4 Right-click the analysis result, and then choose View Analysis Result from the shortcut menu.The GSM Frequency Analysis window is displayed.You can also double-click the selected analysis result to open the GSM Frequency Analysiswindow.



249


Step 5 View the list of measurement cells in the left pane in the displayed window.

Through this function, you can query the analysis overview information about all cells involvedin a frequency analysis task and query the interference of a measurement cell caused by intra-frequency or adjacent-frequency neighboring cells and the interference of intra-frequency oradjacent-frequency neighboring cells caused by a measurement cell. The Nastar automaticallysorts cells by interference to provide a basis of frequency analysis for measurement cells.

For details about the parameters, see 9.10.6 Parameters for Querying GSM FrequencyAnalysis Results.

Step 6 Query the analysis results of the cell interference matrix on the Interference Matrix tab page.

Based on the analysis results of GSM cell interference matrix, you can query the traffic affectedby co-channel or adjacent-channel interference of a measurement cell on its neighboring cellsand percentage of traffic affected by co-channel or adjacent-channel interference. In addition,you can query the traffic affected by co-channel or adjacent-channel interference of eachneighboring cell on a measurement cell and percentage of traffic affected by co-channel oradjacent-channel interference. The analysis results help you learn the interference between cells,providing reference for frequency optimization.


Step 7 Query the analysis results of frequency interference matrix on the Frequency InterferenceMatrix tab page.

Based on the analysis results of GSM cell frequency interference matrix, you can query thetraffic affected by the interference of BCCH ARFCNs between a measurement cell and itsneighboring cells. When querying the interference matrix, you can query the traffic affected bythe interference between the BCCH ARFCNs of a measurement cell and its intra-frequency andupper and lower adjacent-frequency neighboring cells.


NOTE


----End

9.6 Querying GSM Frequency Optimization ResultsThis section describes how to query GSM frequency optimization results. You can either enablethe Nastar to automatically perform frequency optimization or manually set relevant parameterson the Nastar to perform frequency optimization.



250

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM frequency analysis task has reached 100%.

Contextl Automatic frequency optimization: Instead of manual selection of ARFCNs, the Nastar

automatically selects ARFCNs to be optimized. This effectively improves the efficiencyof frequency optimization and reduces user operations.

l Manual frequency optimization: After selecting some cells in the interference matrix relatedto a frequency analysis task and setting algorithm parameters related to frequencyoptimization, you can enable the Nastar to analyze the frequency interference of the BCCHARFCN and TCH ARFCNs selected from the candidate ARFCNs of a measurement cellaccording to the settings. This helps you select appropriate BCCH ARFCNs and TCHARFCNs for measurement cells.

Procedure

Step 1 Choose Theme Function > GSM Frequency Analysis Task from the navigation tree on theleft of the Analysis Task Management window.

Step 2 Select a GSM frequency analysis task from the task list on the upper right of the Analysis TaskManagement window.The analysis results of the selected task are displayed in the lower right pane.


Step 4 Right-click the analysis result, and then choose Frequency Optimization from the shortcutmenu. The GSM Frequency Optimization window is displayed.


If you have queried the GSM frequency optimization report, the default settings of queryconditions in the displayed dialog box are the same as the settings of the last time. The defaultsettings of query conditions are saved in the \client\plugins\NastarPA\style\conf\FreqConfdirectory. The query conditions of each frequency analysis task are saved in a file.

Step 5 Set the parameters related to frequency optimization on the Algorithm Parameters tab page,and then click OK.l Double-click a cell in the ARFCN Spacing Rule Setting area to set the rules for separating

ARFCNs. For details about rules, see 9.1.4 GSM ARFCN Spacing Rules.

l Click on the right of the BCCH ARFCN Range Setting, TCH ARFCN RangeSetting, or VIP Cell Group Setting area, and then select candidate BCCH ARFCNs or TCHARFCNs and VIP cell groups.The Nastar supports frequency analysis and optimization in the case that identical candidateARFCNs of BCCH ARFCNs and TCH ARFCNs can be configured during the setting ofBCCH ARFCN and TCH ARFCN ranges. The identical candidate ARFCNs cannot beautomatically filtered out.The Nastar supports the function of rendering ARFCNs according to frequency spacing rules.For details, see 9.1.4 GSM ARFCN Spacing Rules.



251

l Select either of the following frequency configurations in Base on What ConfiguredFrequency.

– Original: indicates that the current frequency configuration on the network is used forfrequency optimization.

– Last Modified: indicates that the frequency configuration modified last time is used forfrequency optimization.

Step 6 View analysis results in the GSM Frequency Optimization dialog box.

1. Select a cell from the cell list on the left of the displayed window.

You can press Ctrl+F to search for an object.

2. Select an appropriate frequency optimization mode as required.


Enable automatic frequency optimization Perform 6.3 through 6.4.

Enable manual frequency optimization Perform 6.5 through 6.6.

3. Click on the upper left of the window. The GSM Automatic FrequencyOptimization dialog box is displayed.

4. On the Optimize Parameters tab page, specify Phase Optimize Range, ARFCN Type,and Optimize Loop Count. Then, click OK.

5. On the BCCH tab page, query the configured BCCH ARFCN and candidate BCCHARFCNs of the selected cell. On the TCH tab page, query the configured TCH ARFCNsand candidate TCH ARFCNs of the selected cell.

Based on the settings of algorithm parameters, the Nastar calculates and determines theARFCNs that meet co-cell configuration rules, ARFCNs that meet co-site configurationrules, and ARFCNs that meet neighboring cell configuration rules, providing basicinformation for frequency optimization.

In the chart area in the lower part of the window, legends in different colors show theinterfered traffic, traffic that causes interference to other cells, total interfered traffic lasttime, total original interfered traffic, and total interfered traffic of the selected cell.Current indicates the information about ARFCNs of the serving cell. Adjacent indicatesthe information about ARFCNs of the neighboring cell.

Click on the upper left of the window. In the displayed Frequency Usage Analysisdialog box, view the usage of current BCCH ARFCNs and TCH ARFCNs to ensure thefrequency usage.

6. Optional: You can perform operations on the BCCH or TCH tab page as required.


Add an ARFCN a. Select an unconfigured ARFCN, and then select it inthe corresponding check box in the Configured

column or click on the upper left of the window.

b. Click on the upper left of the window to make allthe settings take effect.



252


Delete an ARFCN a. Select a configured ARFCN, and then select it in thecorresponding check box in the Configured column

or click on the upper left of the window.

b. Click on the upper left of the window to make allthe settings take effect.

After the submit operation, you can click or on the upper left of the window tonavigate through the interfaces for displaying the interference of the ARFCNs before andafter the submit operation. This helps you analyze the variation of the interference of theARFCNs before and after frequency optimization, determining the probability ofperforming frequency optimization.

NOTE

l If an ARFCN is already configured as the BCCH ARFCN for the selected measurement cell,according to Spacing Rules of ARFCNs, this ARFCN cannot be configured as the TCH ARFCNeven if it is within the range of candidate TCH ARFCNs. Otherwise, the Nastar displays an errormessage, indicating that the ARFCN is already configured.

l If an ARFCN is configured as the TCH ARFCN for a measurement cell, the neighboring ARFCNsof the configured TCH ARFCN cannot be configured as TCH ARFCNs.

l If you add an ARFCN that violates frequency spacing rules, a dialog box is displayed. In thiscase, you need to click Yes to add the ARFCN.

----End


Related References9.10.7 Parameters for Querying GSM Frequency Optimization Results

9.7 Exporting GSM Frequency Analysis ReportsThis section describes how to export GSM frequency analysis reports. You can export the queriedfrequency analysis results as .csv, .xls or .xlsx files and import these files into the other softwarefor solving cell frequency interference problems in networks.

Prerequisitesl You have logged in to the Nastar client.l You have queried the GSM frequency analysis reports. For details, see 9.5 Querying GSM

Frequency Analysis Results.




253


Export frequency overviewinformation Click in the GSM Frequency Analysis

window.

Export the interference informationabout a specified cell Click in the GSM Frequency Analysis

window.

Export the detailed information aboutthe interference matrix on the entirenetwork

Click in the GSM Frequency Analysiswindow.

NOTEIn File Type, select .txt. The exported data can bedirectly imported into the Cellopt software for re-planning network frequencies.

If the BTS name of the serving cell and the BTSname of the interfered cell are blank, the Nastardoes not search for the related information fromengineering parameters and configuration data. Inthis case, you need to check the integrity of theengineering parameters and configuration data.

Export checked result of interferencematrix Click in the GSM Frequency Analysis

window.

Export possible neighboring cellanalysis results Click in the GSM Frequency Analysis

window.

Export an interference comparisonanalysis report

1. Click in the GSM FrequencyAnalysis window. The Select Two Taskto Compare dialog box is displayed.

2. Click to choose the names of the twotasks.

3. Click OK. The Interference CompareResult dialog box is displayed.The following tab pages are present on thedisplayed dialog box: OverviewCompare, BSC Compare, and CellCompare.

4. Right-click the query result, and thenchoose Save As to save the query result.

– The progress of an export task is displayed in the Exported File List dialog box. Youcan perform other operations during the execution of the export task.



254

– Only one export task can be executed at a time on one client. If more than one exporttasks are created, other tasks are in the waiting state and can be executed only afterthe running task is executed completely or canceled.

– You can click on the right of the progress bar to cancel an export task in thewaiting 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 thecompleted state so that the task is deleted from the task list.


– The analysis result is exported as a .csv, .xls and .xlsx file.

NOTE

l Exporting neighboring cell overview information is to export the information about all themeasurement cells involved in the selected analysis task.

l Exporting the interference information about a specific cell is to export the information aboutthe mutual interference between a measurement cell and its neighboring cells and the frequencyinterference matrix of the measurement cell.

l Exporting the detailed information about the interference matrixes on the entire network is toexport the information about frequency interference matrixes involved in all the measurementcells.

l Exporting checked result of interference matrix is to measured the accuracy of the interferencematrix information generated by the Nastar system from the multiple dimensions.

l Exporting possible neighboring cell analysis results is to export the information about the possibleneighboring cells of all the measurement cells.

----End

9.8 Exporting GSM Frequency Optimization ReportsThis section describes how to export GSM frequency optimization reports. You can export thequeried frequency optimization results as .csv, .xls, or .xlsx files for further comparison andanalysis.

Prerequisitesl You have logged in to the Nastar client.l You have queried the GSM frequency optimization reports. For details, see 9.6 Querying

GSM Frequency Optimization Results.

Procedure

Step 1 Click in the GSM Frequency Optimization window. 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.The progress of an export task is displayed in the Exported File List dialog box. You can performother 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 tasksare created, other tasks are in the waiting state and can be executed only after the runningtask is executed completely or canceled.



255

l You can click on the right of the progress bar to cancel an export task in the waiting orrunning 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 taskis deleted from the task list.

l You can click on the right of the progress bar to view detailed information about anexport task in the completed state.

Step 3 Optional: Export frequency analysis prediction reports.Exporting frequency analysis prediction reports is to export prediction reports before and aftera specific measurement cell is optimized.

1. Click in the Frequency Optimization window. The Interference Compare Resultdialog box is displayed.

The following tab pages are present on the displayed dialog box: Overview Compare,BSC Compare, and Cell Compare.

2. Right-click the query result and then choose Save As from the shortcut menu. The Savedialog box is displayed.

3. Set the file name and specify the save path and file type. Then, click Save.

----End

9.9 Technical Specifications for GSM Frequency AnalysisThis section describes the technical specifications for GSM frequency analysis.



<= 5,000 cells


The Nastar server can run a maximum of five analysis taskssimultaneously. If only a certain type of theme analysis tasks arerunning on the Nastar, a maximum of five analysis tasks of thistype can be executed simultaneously.




<= 200


<= 50



256

9.10 Reference for the GSM Frequency Analysis GUIThis section describes the interface for GSM frequency analysis and the relevant parameters.Before performing relevant operations, familiarize yourself with the GSM frequency analysisfunctions.

9.10.1 Interface Description: GSM Frequency AnalysisThis section describes the interface for GSM frequency analysis. Before performing relevantoperations, familiarize yourself with the rules for dividing areas on the interface.

The frequency analysis results can be displayed in a table. The list of summary information aboutthe measurement cells, list of information about interference matrix, and list of information aboutfrequency interference matrix are contained, as shown in Figure 9-4 and Figure 9-5.

Figure 9-4 Frequency analysis interface (1)



257


(1) Measurement Cell Overview Information Displays the information about all task-related measurement cells.

For details, see 9.10.6 Parameters forQuerying GSM Frequency AnalysisResults.

(2) Neighboring Cell-Measurement CellInterference Matrix Detail

Displays the traffic interfered by theneighboring cells of the measurement cellselected in Area (1).


(3) Measurement Cell-Neighboring CellInterference Matrix Detail

Displays the traffic affected by theinterference from the measurement cellselected in Area (1) to the defined andundefined neighboring cells.




258

Figure 9-5 Frequency analysis interface (2)


(4) Button area Six buttons are provided to export the overviewinformation about frequency analysis, theinterference of specified cell, the interferencematrix, checked result of interferencematrix,the possible neighboring cell analysisresults, and the interference compare analysis.

(5) Frequency Interference Matrix Displays the traffic affected by the interferencebetween the measurement cell selected in Area(1) and its neighboring cells by frequencies.




259


(6) BCCH Configured Frequency Cell List Displays the interfered traffic between themeasurement cell and its neighboring cells onthe same BCCH or between the measurementcell and its neighboring cells with the adjacentBCCH when the frequency selected in Area (4)is set to be the BCCH of the measurement cell.


9.10.2 Interface Description: GSM Frequency OptimizationThis section describes the interface for GSM frequency optimization. You can familiarizeyourself with each area to facilitate the operations on this interface.

The frequency optimization results can be tabulated into general information, BCCHinformation, and TCH information, respectively. Figure 9-6 shows the interface.

Figure 9-6 Frequency optimization interface



260

SN Name Description

(1) General information Shows the information about all themeasurement cells selected in the current task.

(2) Button area Provides 10 buttons to implement thefollowing functions respectively: addingARFCNs, deleting ARFCNs, returning to theprevious operation results, switching to thenext operation results, exporting frequencyoptimization results, submitting the operation,checking frequency spectrum usage,comparing and analyzing interference,enabling automatic frequency optimization,and disabling automatic frequencyoptimization.

(3) BCCH information and TCH information l The BCCH table shows all the configuredand candidate BCCHs of the measurementcell selected in area (1).

l The TCH table shows all the configuredand candidate TCHs of the measurementcell selected in area (1).

At the top of the ARFCN, Total InterferenceTraffic, Interfered Traffic, ExternalInterference Traffic, Interference Trafficto VIP Cells, Latest Total InterferenceTraffic, and Original Total InterferenceTraffic columns, set the ascending order ordescending order. Area (4) displays theimages in a new order.

(4) Image area Shows the information about frequencyinterference in the selected cell in acombination of bar charts and line charts.

l Current indicates the information aboutARFCNs of the serving cell.

l Adjacent indicates the information aboutARFCNs of the neighboring cell.

(5) Legends of the highlighting function Displays information about ARFCNs thatviolate the co-cell, co-site, or neighboring cellfrequencies rules in different colors.



261

SN Name Description

(6) Algorithm parameter area Displays the algorithm parameters set whenfrequency optimization is queried. Rules forspacing between frequencies, and VIP cellgroups are contained in this area.

By default, this area is hidden. You need to

click on the right of the window to displaythis area.

9.10.3 Parameters of GSM Neighboring Cell E2E TasksThis section describes the parameters for creating GSM E2E tasks. You can refer to thedescription when creating a GSM E2E task.


Basicinformation

Task Name Indicates the name of a neighboring cellmeasurement task.


E2E Task List Select the GSM Neighboring Cell Analysis DataTask node.

Run Type l Once: The system executes the created tasks onlyonce at the specified time.

l Period: The system executes the created tasks atthe preset time.

Start Time Indicates the time when the task starts to run.The start time must be later than the current time. Bydefault, the start time is five minutes later than thecurrent system time.

Cycle Indicates the interval between periodic tasks. Thisparameter involves the period unit and the interval.l Unit: day.l Interval: 1.This parameter is valid for only periodic tasks.NOTE

The Nastar does not support the configuration of periodicunit and duration of the periodic task.

Execute Times Indicates the times that a periodic task is executed.The value is an integer from 1 to 15.This parameter is valid for only periodic tasks.



262




Indicates the total duration which a measurementtask is performed.The value is an integer from 1 to 1430.The duration time must be later than the timecalculated by (Measurement period ×15) × ([Totalnumber of test ARFCNs ÷ measurement step + 1]) +15.

Period Interval between the ARFCNs of each group.The value is an integer from 1 to 48. The unit is *15(minute), that is, the value must be multiples of 15minutes.For example, if this parameter is set to 2, themeasurement time of each ARFCN is 2×15 minutes,that is, 30 minutes.

Measure Step Indicates the number of ARFCNs in the same group.The value is an integer from 1 to 31.The measurement step must be less than or equal tothe minimum rest step of the selected cell.

Cell Object Indicates the cell related to the neighboring cellmeasurement task.

frequencyInformation

Indicates the set of ARFCNs to be measured. TheARFCNs are classified by group. The number ofARFCNs of each group is determined by MeasureStep.NOTEl You can select a maximum of 762 ARFCNs for a cell.

If the number exceeds 762, the NE returns an errormessage after the corresponding MML command isexecuted, indicating that the task creation ormodification fails.

l Before setting this parameter, you must set MeasureStep.

Soft parameterinformation

Soft ParameterSetting

If you select this option, the soft parameters that youset are valid for this measurement task.

RSSThres The value is an integer from 0 to 127.When the difference between the levels of theneighboring cell and the serving cell in the MR isgreater than this value, the relevant traffic statisticalcounter is incremented by one.

ASSThres The value is an integer from 0 to 63.When the level of the neighboring cell in the MR isgreater than this value, the relevant traffic statisticalcounter is incremented by one.



263


NCELLINTERFLEVELTHRES 1-7

You can set the thresholds of interference level forseven neighboring cells.The value is an integer from 0 to 127.When the difference between the levels of theneighboring cell and the serving cell in the MR isgreater than this value, the relevant traffic statisticalcounter is incremented by one.

NOTE

l Level refers to the strength of the received or transmitted signal. It is generally used in power controland handover algorithm.

l ASSThres and RSSThres evaluate the reasonableness of the neighbor cell. According to the actualrequirements, you can modify the two values to adjust the evaluation standard.

l ADJINLVThres1 to ADJINLVThres7 evaluates the CIR distribution of neighboring cells and servingcells and the ratio among each segment. This parameter in combination with frequency configurationanalysis indicates the severity level of each frequency interference, and thus can be used to adjust theC/I distribution segment of neighboring cells and serving cells.

Carrier-to-interference ratio distribution refers to the distribution of the power of the carrier signalsand the power of the interference signals, that is, C/I distribution.

Related Tasks9.3.1 Creating GSM Neighboring Cell Measurement Data E2E Tasks






ExecutionType









264


Runimmediately



ExecutionInterval



ExecutionTimes








Collect AllNE





265


Collect ByNE Type









9.10.5 Parameters for Creating and Modifying GSM FrequencyAnalysis Tasks

This section describes the parameters for creating and modifying GSM frequency analysis tasks.You can refer to the description when creating or modifying a GSM frequency analysis task.








266





ExecutionDelay






Display the Number ofUndefined NeighboringCells

Indicates that only the TopN frequencies of undefinedneighboring cells are displayed.N can be any integer from 20 to 999. The default value is 30.

Intra-FrequencyInterference C/I >

Indicates the threshold of intra-frequency interference.This parameter can be set to any integer from 6 to 15. Thedefault value is 12.Unit: dB

Adjacent-ChannelInterference C/A >

Indicates the threshold of adjacent-channel interference.This parameter can be set to any integer from -12 to 0. Thedefault value is -6.Unit: dB



267


ALL Direction Gain Indicates the omnidirectional gain of an antenna.This parameter can be set to any integer from 0 to 15. Thedefault value is 11.Unit: dBi

Specified Direction Gain Indicates the directional gain of an antenna.This parameter can be set to any integer from 0 to 25. Thedefault value is 17.Unit: dBi

Max Distance of Co-BCCHand BSIC Check ofNeighboring Cells(km)

Indicates the maximum distance the Nastar searches for cellsthat share the same BCCH ARFCN and the same BSIC withthe measurement cell.This parameter can be set to any floating-point value from 0.0to 20.0. The default value is 5.0.Unit: km

Frequency AnalysisAlgorithm

Supports Relating BA2 and Not Relating BA2 algorithms.In normal cases, Relating BA2 is recommended. If thenumber of BCCH ARFCNs is smaller than 32, and if theBCCH ARFCNs in the modified BA2 list are used, you canselect Not Relating BA2 to perform the frequency analysis.This improves the analysis efficiency and reliability.

Typical Site Distance(km) Indicates the distance between typical sites. Based on thisdistance, the system calculates a threshold to filter analysisresults.Value range: [0.1,35.0]. Default value: 0.5.Unit: km.

Related Tasks9.4 Creating GSM Frequency Analysis Tasks

9.10.6 Parameters for Querying GSM Frequency Analysis ResultsThis section describes the parameters for querying GSM frequency analysis results. You canrefer to the description when querying GSM frequency analysis results.

Test Cell Overview InformationParameter

Range Unit

Description

BSCName

1 to 32characters

N/A

Indicates the name of the BSC that a test cell belongs to,for example, BSC_1.



268

Parameter

Range Unit

Description

Test Cell 1 to 64characters

N/A


Test CellCGI

Consists ofthe followingparts:MCC[000 to999]MNC[000 to999]LAC[1,65533],[65535]CI [0,65535]

N/A


BCCH [0,1023]1 to 124:belong to P-GSM; 128 to251: belong toGSM850; 0,975 to 1023:belong to E-GSM; 955 to974: belong toR-GSM; 811to 885: belongto DCS1800;512 to 810:belong toDCS1800when the highband supportsDCS1800;512 to 810:belong toPCS1900when the highband supportsPCS1900.

N/A


BSIC Consists ofthe followingparts:NCC[0,7]BCC[0,7]BSIC=NCC*10+BCC

N/A




269

Parameter

Range Unit

Description

Numberof Co-BCCH-definedNeighbors andNeighbors ofTestedCells'DefinedNeighbors

[0,+∞) Number

Total number of co-BCCH neighboring cells = Numberof co-BCCH neighboring cells for the test cell + Numberof co-BCCH neighboring cells for the neighboring cells

ProbableCo-InterferencedTrafficbyneighbor

[0,+∞) N/A

Indicates the number of MRs received by the test cell fromthe neighboring cells that share the same BCCH ARFCNwith the test cell.

ProbableAdj-InterferencedTrafficbyneighbor

[0,+∞) N/A

Indicates the number of MRs received by the test cell fromthe neighboring cells that have neighboring ARFCNs ofthe BCCH ARFCN of the test cell.

ProbableCo-InterferencedTraffic toneighbor

[0,+∞) N/A

Indicates the number of MRs received by the neighboringcells that share the same BCCH ARFCN with the test cell.

ProbableAdj-InterferencedTraffic toneighbor

[0,+∞) N/A

Indicates the number of MRs received by the neighboringcells that have neighboring ARFCNs of the BCCHARFCN of the test cell.



270

Parameter

Range Unit

Description

TotalNumberofMeasurementReportson TestCells

[0,+∞) Number

Indicates the total number of downlink MRs received bythe test cell within the measurement period.

Proximate Co-ChannelNeighboring CellDistance(km)

[0,+∞) km Indicates the distance from the test cell to the nearest intra-frequency neighboring cell.

Neighboring Cell-Test Cell Interference Matrix DetailParameter

Range Unit

Description

Interference Cell

1 to 64characters

N/A

Indicates the name of a cell that causes interference to thetest cell.



271

Parameter

Range Unit

Description

Interference CellBCCHFrequency

[0,1023]1 to 124:belong to P-GSM; 128 to251: belong toGSM850; 0,975 to 1023:belong to E-GSM; 955 to974: belong toR-GSM; 811to 885: belongto DCS1800;512 to 810:belong toDCS1800when the highband supportsDCS1800; 512to 810: belongto PCS1900when the highband supportsPCS1900.

N/A

Indicates the broadcast control channel for an interferingcell.

Interference CellBSIC

Consists of thefollowingparts:NCC[0,7]BCC[0,7]BSIC=NCC*10+BCC

N/A

Indicates the base station identity code of an interferingcell.

Neighboring CellProperty

Definedneighboringcell,Undefinedneighboringcell

N/A

Indicates the attributes of an interfering cell.

OverlappingTraffic

[0,+∞) N/A

Indicates the number of MRs received by the test cellfrom the intra-frequency neighboring cells and adjacent-channel neighboring cells.



272

Parameter

Range Unit

Description

Percentage of Co-InterferencedTrafficbyNeighbor(%)

[0,100.00] % If the BCCH ARFCN of the test cell is set to be the sameas that of a neighboring cell, the value of this parameteris calculated according to the following formula:Percentage of Co-Interference Traffic by Neighbor(%) =Traffic affected by the interference from a co-channelneighboring cell to the test cell/Number of reportsgenerated by the test cell during the measurement periodx 100%

Percentage ofAdj-InterferencedTrafficbyNeighbor(%)

[0,100.00] % If the BCCH of the test cell is set to the frequency adjacentto the BCCH of a neighboring cell, the value of thisparameter is calculated according to the formula:Percentage of Adj-Interferenced Traffic by Neighbor(%)= Traffic affected by the interference from an adjacent-channel neighboring cell to the test cell/Number ofreports generated by the test cell during measurementperiod x 100%

ProbableCo-InterferencedTrafficbyNeighbor

[0,+∞) N/A

Indicates the total traffic affected by the interference froma neighboring cell to the test cell when the BCCHARFCN of the test cell is the same as that of theneighboring cell.

ProbableAdj-InterferencedTrafficbyNeighbor

[0,+∞) N/A

Indicates the total traffic affected by the interference froma neighboring cell to the test cell when the BCCHARFCN of the test cell is a neighboring ARFCN for theBCCH ARFCN of the neighboring cell.

Distance(km)

[0,+∞) km Indicates the distance from the test cell to a neighboringcell.

Test Cell-Neighboring Cell Interference Matrix DetailParameter

Range Unit

Description

Interfered Cell


Indicates the name of a cell interfered by the testcell



273

Parameter

Range Unit

Description

Interfered CellBCCH

[0,1023]1 to 124: belong to P-GSM; 128 to 251: belongto GSM850; 0, 975 to1023: belong to E-GSM;955 to 974: belong to R-GSM; 811 to 885: belongto DCS1800; 512 to 810:belong to DCS1800when the high bandsupports DCS1800; 512to 810: belong toPCS1900 when the highband supports PCS1900.

N/A

Indicates the broadcast control channel for aninterfered cell.

Interfered CellBSIC

Consists of the followingparts:NCC[0,7]BCC[0,7]BSIC=NCC*10+BCC

N/A

Indicates the base station identity code of aninterfered cell.


Defined neighboringcell, Undefinedneighboring cell

N/A

Indicates the attributes of an interfered cell,such as Defined Neighboring Cell andUndefined Neighboring Cell.

OverlappingTraffic

[0,+∞) N/A

Indicates the number of MRs received by theintra-frequency neighboring cells and adjacent-channel neighboring cells from the test cell.

Percentage of Co-InterferencedTraffic toNeighbor(%)

[0,100.00] % If the BCCH ARFCN of the test cell is set to bethe same as that of a neighboring cell, the valueof this parameter is calculated according to theformula: Percentage of Co-Interference Trafficto Neighbor(%) = Traffic affected by theinterference from the test cell to the co-channelneighboring cell/Number of reports generatedby the test cell during measurement period x100%

Percentage ofAdj-InterferencedTraffic toNeighbor(%)

[0,100.00] % If the BCCH ARFCN of the test cell is set to thefrequency adjacent to the BCCH of aneighboring cell, the value of this parameter iscalculated according to the formula: Percentageof Adj-Interference Traffic to Neighbor(%) =Traffic affected by the interference from the testcell to the adjacent-channel neighboring cell/Number of reports generated by the test cellduring measurement period x 100%



274

Parameter

Range Unit

Description

ProbableCo-InterferencedTraffic toNeighbor

[0,+∞) N/A

Indicates the total traffic affected by theinterference from the test cell to a neighboringcell when the BCCH ARFCN of the test cell isthe same as that of the neighboring cell.

ProbableAdj-InterferencedTraffic toNeighbor

[0,+∞) Indicates the total traffic affected by theinterference from the test cell to a neighboringcell when the BCCH ARFCN of the test cell isa neighboring ARFCN for the BCCH ARFCNof the neighboring cell.

Distance(km)

[0,+∞) km

Indicates the distance from the test cell to aninterfered cell.

Frequency Interference MatrixParameter

Range Unit

Description

BCCHFrequency

[0,1023]1 to 124: belong to P-GSM; 128 to 251: belongto GSM850; 0, 975 to1023: belong to E-GSM;955 to 974: belong to R-GSM; 811 to 885: belongto DCS1800; 512 to 810:belong to DCS1800 whenthe high band supportsDCS1800; 512 to 810:belong to PCS1900 whenthe high band supportsPCS1900.

N/A

Indicates the BCCH ARFCNs of the definedand undefined neighboring cells of the test cell

Traffic ofTest CellCausedbyNeighboring CellInterference

[0,+∞) N/A

If this ARFCN of the test cell is set to the BCCHARFCN, the value of this parameter is the totalvolume of the interfered traffic of the test cell.The interfered traffic is caused by the co-channel and adjacent-channel neighboringcells for the test cell.



275

Parameter

Range Unit

Description

Traffic ofNeighboring CellCausedby TestCellInterference

[0,+∞) N/A

If this ARFCN of the test cell is set to the BCCHARFCN, the value of this parameter is the totalvolume of the interfered traffic of the co-channel and adjacent-channel neighboringcells. The interfered traffic is caused by the testcell.

Proximate Co-ChannelNeighboring CellDistance(km)

[0,+∞) km

If this ARFCN of the test cell is set to the BCCHARFCN, the value of this parameter is thedistance from the test cell to the nearest intra-frequency neighboring cell.

BCCH Configured Frequency Cell ListParameter

Range Unit

Description

Interference CellBCCHFrequency

[0,1023]1 to 124: belong to P-GSM; 128 to 251: belongto GSM850; 0, 975 to1023: belong to E-GSM;955 to 974: belong to R-GSM; 811 to 885: belongto DCS1800; 512 to 810:belong to DCS1800 whenthe high band supportsDCS1800; 512 to 810:belong to PCS1900 whenthe high band supportsPCS1900.

N/A

Indicates the broadcast control channel for aninterfering cell.

Interference CellBSIC

Consists of the followingparts:NCC[0,7]BCC[0,7]BSIC=NCC*10+BCC

N/A

Indicates the base station identity code of aninterfering cell.



276

Parameter

Range Unit

Description

Interference CellID

[0 to 2047] N/A

Indicates the number of an interfering cell.

Interference CellName


Indicates the name of a cell that causesinterference to the test cell.


Defined neighboring cell,Undefined neighboringcell

N/A

Indicates the attributes of an interfering cell,such as Defined Neighboring Cell andUndefined Neighboring Cell.

Percentage of Co-InterferencedTrafficbyneighbor(%)

[0,100.00] % If the BCCH ARFCN of the test cell is the sameas that of a neighboring cell, the value of thisparameter is calculated according to theformula: Value = Traffic affected by theinterference from the co-channel neighboringcell to the test cell/Number of reports generatedby the test cell during the measurement periodx 100%

Percentage ofAdj-InterferencedTrafficbyneighbor(%)

[0,100.00] % If the BCCH ARFCN of the test cell is set to aneighboring ARFCN for the BCCH ARFCN ofa neighboring cell, the value of this parameteris calculated according to the formula: Value =Traffic affected by the interference from theadjacent-channel neighboring cell to the testcell/Number of reports generated by the testcell during the measurement period x 100%

ProbableCo-InterferencedTrafficbyneighbor

[0,+∞) N/A

Indicates the total traffic affected by theinterference from a neighboring cell to the testcell when the BCCH ARFCN of the test cell isthe same as that of the neighboring cell.

ProbableAdj-InterferencedTrafficbyneighbor

[0,+∞) N/A

Indicates the total traffic affected by theinterference from a neighboring cell to the testcell when the BCCH ARFCN of the test cell isa neighboring ARFCN for the BCCH ARFCNof the neighboring cell.



277

Parameter

Range Unit

Description

Percentage of Co-InterferencedTraffic toneighbor(%)

[0,100.00] % If the BCCH of the test cell is set to be the sameas that of a neighboring cell, the value of thisparameter is calculated according to theformula: Value = Traffic affected by theinterference from the test cell to the co-channelneighboring cell/Number of reports generatedby the test cell during the measurement periodx 100%

Percentage ofAdj-InterferencedTraffic toneighbor(%)

[0,100.00] % If the BCCH ARFCN of the test cell is set to aneighboring ARFCN for the BCCH ARFCN ofa neighboring cell, the value of this parameteris calculated according to the formula: Value =Traffic affected by the interference from thetest cell to the adjacent-channel neighboringcell/Number of reports generated by the testcell during the measurement period x 100%

ProbableCo-InterferencedTraffic toneighbor

[0,+∞) N/A

Indicates the total traffic affected by theinterference from the test cell to a neighboringcell when the BCCH ARFCN of the test cell isthe same as that of the neighboring cell.

ProbableAdj-InterferencedTraffic toneighbor

[0,+∞) N/A

Indicates the total traffic affected by theinterference from the test cell to a neighboringcell when the BCCH ARFCN of the test cell isa neighboring ARFCN for the BCCH ARFCNof the neighboring cell.

Distance(km)

[0,+∞) km

Indicates the distance from the test cell to aneighboring cell.

Related TasksQuerying GSM Cell Frequency Interference Matrix Analysis Results

9.10.7 Parameters for Querying GSM Frequency OptimizationResults

This section describes the parameters for querying GSM frequency optimization results. Youcan refer to the description when querying GSM frequency optimization results.



278

Current Measurement CellParameter

Range Unit

Description

BSCName


Indicates the name of the BSC that a test cellbelongs to, for example, BSC_1.

CellName


Indicates the name of a test cell, for example,Cell_1.

BCCH [0,1023]1 to 124: belong to P-GSM; 128 to 251:belong to GSM850;0, 975 to 1023:belong to E-GSM;955 to 974: belong toR-GSM; 811 to 885:belong to DCS1800;512 to 810: belong toDCS1800 when thehigh band supportsDCS1800; 512 to810: belong toPCS1900 when thehigh band supportsPCS1900.

N/A

Indicates the broadcast control channel for a testcell.

LAC [1,65533],[65535] N/A

Indicates the location area code of the selected testcell.

CI [0,65535] N/A

Indicates the identification code of the selected testcell.

TCH N/A N/A

Indicates traffic channels for the selected test cell.

Total MR [0,+∞) Number

Indicates the total number of MRs of the servingcell.

BCCH/TCH ARFCNsParameter

Range

Unit

Description

Configured

Yes,No

N/A Indicates whether the current ARFCN is configured as the BCCHARFCN or a TCH ARCFN of the selected test cell.



279

Parameter

Range

Unit

Description

ARFCN N/A N/A Indicates the configured and candidate BCCH ARFCNs and TCHARFCNs of the test cell.

Cell withtheStrongestInterference

N/A N/A Indicates the name of the cell that has the strongest interferenceover the test cell.

CellMeasured or Not

Yes,No

N/A Indicates whether the cell with the strongest interference over thetest cell is within the interference matrix, that is, whether the cellwith the strongest interference is measured.The value can be Yes or No.Yes indicates that the cell with the strongest interference over thetest cell is within the interference matrix, that is, the cell with thestrongest interference is measured. In such a case, ExternalInterference Traffic of this ARFCN is reliable.

No indicates that the cell with the strongest interference over thetest cell is not within the interference matrix, that is, the cell withthe strongest interference is not measured. In such a case, ExternalInterference Traffic of this ARFCN is unreliable.

MaximumInterferenceTraffic

[0,+∞)

N/A Indicates the maximum interference traffic received by the test cellwhen the BCCH ARFCN or a TCH ARFCN of the test cell isconfigured as the current candidate ARFCN.

TotalInterferenceTraffic

[0,+∞)

N/A Indicates the total interference traffic received from and caused toother cells when the BCCH ARFCN or a TCH ARFCN of the testcell is configured as the current candidate ARFCN.

Interfered Traffic

[0,+∞)

N/A Indicates the total interference traffic received from other cellswhen the BCCH/TCH of the test cell is configured as the currentcandidate ARFCN.

ExternalInterferenceTraffic

[0,+∞)

N/A Indicates the total interference traffic caused to other cells whenthe BCCH ARFCN or a TCH ARFCN of the test cell is configuredas the current candidate ARFCN.

InterferenceTraffic toVIP Cells

[0,+∞)

N/A Indicates the total interference traffic caused to other VIP cellswhen the BCCH ARFCN or a TCH ARFCN of the test cell isconfigured as the current candidate ARFCN.



280

Parameter

Range

Unit

Description

LatestTotalInterferenceTraffic

[0,+∞)

N/A Indicates the total interference traffic received from and caused toother cells when the BCCH ARFCN or a TCH ARFCN of the testcell is configured as the current candidate ARFCN after the latestfrequency optimization is performed.

OriginalTotalInterferenceTraffic

[0,+∞)

N/A Indicates the total interference traffic received from and caused toother cells when the BCCH ARFCN or a TCH ARFCN of the testcell is configured as the ARFCN of the live network.

Related Tasks9.6 Querying GSM Frequency Optimization Results

9.11 How Do I Handle the Failure to Execute a GSMFrequency Analysis Task Whose Progress Bar Stays at 13%or 75% But the Task Status is Displayed As Finished?

This section describes the cause of the failure to execute a GSM frequency analysis task andhow to solve the problem.

SymptomThe progress bar of a running GSM frequency analysis task stays at 13% or 75%. The executionresult is Failed, but the task status is Finished.

Error information is displayed in task logs. To check error information, do as follows:

l Log in to the Nastar server and query DS running logs. The following or similar errorinformation is displayed:02-23 13:32:08,687 Thread-12475 : Task id: 1307 Task type id: 104 Task result id: 2811 02-23 13:32:08,687 Thread-12475 : Stored procedure: call process_gsmfrequency(?,?,?,?,?,?) 02-23 14:05:13,965 Thread-12475 : xavier:rstatus-600 02-23 14:05:13,965 Thread-12475 : analysisData rstatus is : -600 02-23 14:05:13,966 Thread-12475 : 0223BSC6000-8:end to analysis data 02-23 14:05:14,541 Thread-12475 : 0223BSC6000-8:task end 02-23 14:05:14,541 Thread-12475 : task Complete running Queue size:1

NOTEThe DS logs are saved in /opt/Nastar/ds/var/logs on the Nastar of a version earlier thanV600R008C00SPC300. The DS logs are saved in /opt/Nastar/var/logs/ds/default/ on the Nastar ofV600R008C00SPC300 or a later version.

l Open /opt/oracle/oradb/diag/rdbms/imapdb/imapdb/trace/ on the Nastar server andquery logs in the alert_imapdb.log file. The following or similar information is displayed:ORA-00600: internal error code, arguments: [15160], [], [], [], [], [], [], []



281

CauseThe preceding logs indicate that the Oracle database experiences the error ORA-00600. Thiserror is caused by the defect of the Oracle database software. The solution to this defect has beenincorporated into Oracle 11.2.0.1. However, this defect still exists in the Oracle version usedwith the Nastar.

TroubleshootingTo solve this problem, do as follows:

1. Log in to the Nastar server as user oracle.2. Run the following command to open the Oracle database:

sqlplus / as sysdba3. Run the following command to set parameter values in the Oracle database:

Alter system set "_optimizer_null_aware_antijoin"=false;Alter system set "_OPTIMIZER_PUSH_PRED_COST_BASED" =false;

4. Log in to the Nastar client.5. Run the GSM frequency analysis task again.



282

10 GSM Uplink Interference Analysis

About This Chapter

The GSM uplink interference analysis function enables you to obtain GSM uplink interferenceanalysis data, create GSM uplink interference analysis tasks, and query GSM uplink interferenceanalysis reports. By analyzing uplink level of cells, the Nastar displays the signal strength of themeasurement ARFCNs of some cells in the analysis results, helping you select appropriateARFCNs according to the actual situation.

10.1 Basic Knowledge of GSM Uplink Interference AnalysisThis section provides the basic knowledge of GSM uplink interference analysis. The GSM uplinkinterference analysis function is used to analyze the diverse average interference strength andmain average interference strength of uplink levels. In the network planning, this functionenables network planning engineers to look for the frequency resources that are not interferedon the network. In network optimization, this function enables network planning engineers tolook for the frequency resources with better quality for the cells with interference sourcesaccording to the analysis of measurement results. In network monitoring, this function can beused to monitor the interference levels of the network.

10.2 Process of GSM Uplink Interference AnalysisThis section describes the process of GSM uplink interference analysis.

10.3 Obtaining GSM Uplink Interference Analysis DataThis section describes how to enable the Nastar to obtain GSM uplink interference analysis data.You can create an E2E task to enable the Nastar to collect analysis data and create a data importtask so that the Nastar imports the collected analysis data into the database.

10.4 Creating GSM Uplink Interference Analysis TasksThis section describes how to create GSM uplink interference analysis tasks. After you createan uplink interference analysis task, the Nastar periodically analyzes GSM configuration data,GSM uplink interference data, and engineering parameters in the Nastar database. By queryinganalysis results, you can learn about the received signal strength of the measurement frequencyof a cell, which provides references for selecting a proper operating frequency.

10.5 Querying GSM Uplink Interference Analysis ResultsThis section describes how to query GSM uplink interference analysis results. Through thisfunction, you can learn the received signal strength of the measured ARFCNs of some cells andselect appropriate operating ARFCNs.

10.6 Technical Specifications for GSM Uplink Interference Analysis

iManager NastarNetwork Optimization User Guide (GSM) 10 GSM Uplink Interference Analysis


283

This section describes the technical specifications for GSM uplink interference analysis.

10.7 Reference for the GSM Uplink Interference Analysis GUIThis section describes the interface for GSM uplink interference analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM uplink interference analysis.



284

10.1 Basic Knowledge of GSM Uplink Interference AnalysisThis section provides the basic knowledge of GSM uplink interference analysis. The GSM uplinkinterference analysis function is used to analyze the diverse average interference strength andmain average interference strength of uplink levels. In the network planning, this functionenables network planning engineers to look for the frequency resources that are not interferedon the network. In network optimization, this function enables network planning engineers tolook for the frequency resources with better quality for the cells with interference sourcesaccording to the analysis of measurement results. In network monitoring, this function can beused to monitor the interference levels of the network.

The uplink interference analysis aims at testing uplink levels. The analysis results reflect thestrength of the signals received by the measurement cell at the measurement ARFCNs. Engineerscan select appropriate operating frequencies according to analysis results.

Huawei's BTSs can scan the received levels at uplink of all frequencies in the followingfrequency bands: GSM850 frequency band (869 MHz to 893 MHz), GSM900 frequency band(890 MHz to 915 MHz), GSM1800/PCS1900 frequency band (1805 MHz to 1880 MHz/1930MHz to 1989 MHz), E-GSM extended frequency band (880 MHz to 890 MHz), and R-GSMextended frequency band (876 MHz to 880 MHz). That is, Huawei's BTSs can scan the strengthof the interference signals in the frequency bands ranging from 876 MHz to 915 MHz and from1805 MHz to 1880 MHz.

The principles of the frequency analysis for the BTS of the Huawei BTS3X series are as follows:In the case that normal calls are not affected, the uplink interference analysis function is used toperform the cycling test by using the IDLE frame of a TCH within the measurement cell andscan the received levels at uplink of the specified frequencies (When the BSC allocates thischannel, the TCH at the TRX where the BCCH is configured is preferred).

The TCH channel adopts the structure of 26 multiframes. Each TCH multiframe contains anIDLE frame. The period of the IDLE frame on the TCH channel is 120 ms, which is calculatedin the formula: 26 multiframes x 0.577 (Burst length) x 8 (TDMA frame) = 120 ms. In practice,each frequency is measured 10 times, and about one minute is spent on measuring 50 frequencies.An uplink interference analysis task records a maximum of 124 measurement frequencies. Thus,about three minutes is spent on measuring these 124 frequencies.

After you set the conditions of uplink interference analysis, the Nastar starts to analyze the uplinkinterference for the selected cells. The analysis results are displayed in a histogram or line chartto show the diverse average interference strength and main average interference strength of eachfrequency at different time and in different colors.

10.2 Process of GSM Uplink Interference AnalysisThis section describes the process of GSM uplink interference analysis.

Figure 10-1 shows the process of GSM uplink interference analysis.



285

Figure 10-1 Process of GSM uplink interference analysis


Table 10-1 Process of GSM uplink interference analysis


1 Create a GSMuplinkInterferenceanalysis data E2Etask

You need to choose Maintenance > E2E TaskManagement on the Nastar client to open the E2E TaskManagement window and then create a E2E task. After youcreate the task, the Nastar issues MML commands to theM2000, and then the M2000 issues the received MMLcommands to the corresponding NE. At last, the NE performsthe measurement task.



286


2 Create an uplinkinterferenceanalysis dataimporting task

You need to choose Maintenance > Task Management onthe Nastar client to open the Task Management window,and then create an uplink interference analysis data importingtask. After the task is created, the Nastar periodically importsthe files containing uplink interference analysis data savedon the Nastar server to the database.

3 Check the integrityof uplinkinterferenceanalysis data

In the Analysis Task Management window on the Nastarclient, double-click System Function > Data Query. In theData Query window, check whether all the data required forGSM uplink interference analysis is imported into thedatabase.

4 Create an uplinkinterferenceanalysis task

In the Analysis Task Management window on the Nastarclient, you can create an uplink interference analysis task.After you create the task, the Nastar periodically obtains therequired uplink interference analysis data and GSMconfiguration data from the Nastar database, and thengenerates an analysis report through the analysis.

5 Query uplinkinterferenceanalysis results

You can browse the analysis result after the uplinkinterference analysis task is successfully performed. TheNastar ranks interference signals on the BCCH and TCHfrequencies in all cells and determines whether the uplinksignal interference exists in some cells, thus providingreferences for you to select proper operating frequencies.

10.3 Obtaining GSM Uplink Interference Analysis DataThis section describes how to enable the Nastar to obtain GSM uplink interference analysis data.You can create an E2E task to enable the Nastar to collect analysis data and create a data importtask so that the Nastar imports the collected analysis data into the database.

10.3.1 Creating GSM Uplink Interference Analysis Data E2E TasksAfter a user creates an E2E task on the Nastar, the Nastar sends MML commands to the relatedNE through the M2000. The NE then performs the task and reports the measurement result tothe M2000.



Configuration Data.



287

Context


Procedure






2. In the OSS Name drop-down list box, select an OSS for the task.


Step 4 Click Next.

Step 5 Set Run Type, Time Setting, and Cycle Setting.Cycle Setting needs to be set only when Execution Type is set to Cycle Task.

Step 6 Click Next.

Step 7 Set the E2E analysis task.

1. In the Time(Minute) field, set the total duration that a measurement task is performed.

2. In Cell Parameter Setting, select the cells and frequency bands to be measured.

a. Select the frequency band used by the cell from the Frequency Segment drop-downlist box.

b. In the object navigation tree, set the cells related to the task. A maximum of 124 objectscan be selected.

3. Set the ARFCNs to be measured in Frequency Parameter Setting.

a. You can select the required frequency type from the Frequency Type drop-down listbox.

b. Optional: If you set Frequency Type to User Defined in The FrequencySegment, select the ARFCNs to be measured from the ARFCN list. The selectedARFCNs are displayed in orange.

Step 8 Click Complete.The added GSM uplink interference analysis data E2E task is displayed in the task list.

----End



288



View the selected task Click Attribute.






Related References10.7.2 Parameters of GSM Uplink Interference Analysis E2E Tasks10.7.2 Parameters of GSM Uplink Interference Analysis E2E Tasks










289


Analysis TaskType



Manual creation



Manual creation



Manual creation



Manual creation



Manual creation


Manual creation


- -



Manual creation



Manual creation




Manual creation



Manual creation



Manual creation



290

Analysis TaskType




Manual creation



Manual creation

UMTS VIPAnalysis


Manual creation


- -



Manual creation



Manual creation



Manual creation




Manual creation



Manual creation



Manual creation




Manual creation


- -



291

Analysis TaskType





Manual creation




Manual creation



Manual creation

CDMA VIPAnalysis


Manual creation



Manual creation


Manual creation



Manual creation



Manual creation


- -


- -

Procedure




For details about how to set Task Type, see Table 10-2.



292




NOTE




----End


















293


































294


































295





-

Procedure


TIP







----End

10.4 Creating GSM Uplink Interference Analysis TasksThis section describes how to create GSM uplink interference analysis tasks. After you createan uplink interference analysis task, the Nastar periodically analyzes GSM configuration data,GSM uplink interference data, and engineering parameters in the Nastar database. By queryinganalysis results, you can learn about the received signal strength of the measurement frequencyof a cell, which provides references for selecting a proper operating frequency.







296

Procedure





Step 3 Click Next.




Step 5 On the Parameters tab page, set Uplink Interference Analysis Parameter.

Step 6 Click Next.




If... Then...











297

If... Then...



----End









Resume.



Related References10.7.3 Parameters for Creating and Modifying GSM Uplink Interference Analysis Tasks10.7.3 Parameters for Creating and Modifying GSM Uplink Interference Analysis Tasks

10.5 Querying GSM Uplink Interference Analysis ResultsThis section describes how to query GSM uplink interference analysis results. Through thisfunction, you can learn the received signal strength of the measured ARFCNs of some cells andselect appropriate operating ARFCNs.



298

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM uplink interference analysis task reaches 100%.

Procedure

Step 1 Choose Theme Function > GSM Uplink Interference Analysis Task from the navigation treeon the left of the Analysis Task Management window.If you click the Theme Function node, the task list in the right pane displays all the analysistasks.

Step 2 Select a GSM uplink interference analysis task from the task list on the upper right of theAnalysis Task Management window.The analysis results of the selected task are displayed in the lower right pane.


Step 4 Double-click an analysis result, or right-click an analysis result and choose View AnalysisResult from the shortcut menu. The GSM Uplink Frequency Interference Analysis windowis displayed.


Step 5 Select the information about a measurement cell from the list on the left of the GSM UplinkFrequency Interference Analysis window, and then browse Test Frequency InterferenceStrengthand Uplink Frequency Scanning Result of the selected measurement cellin the rightpane.l On the right pane:

– The bar chart shows the interference strength of all the measured ARFCNs in selectedcell at a certain time.

– The line chart shows the interference strength of a certain ARFCN in the selected cellduring the measurement period.

– You can right-click a chart and then choose an option from the shortcut menu to performthe corresponding operation, such as modifying the attributes of the chart, and resizing,saving, and printing the chart.

NOTE


----End

Follow-up ProcedureExport query results. You can right-click the list on the left of the GSM Uplink FrequencyInterference Analysis window and then choose Save As from the shortcut menu to save thecurrent query results as a .csv, .xls, or .xlsx file.



299

Related References10.7.4 Parameters for Querying GSM Uplink Interference Analysis Results10.7.4 Parameters for Querying GSM Uplink Interference Analysis Results

10.6 Technical Specifications for GSM Uplink InterferenceAnalysis

This section describes the technical specifications for GSM uplink interference analysis.



<= 500 cells






<= 200

Number of GSM UplinkInterference Analysis Data E2ETasks

<= 10


<=50

10.7 Reference for the GSM Uplink Interference AnalysisGUI

This section describes the interface for GSM uplink interference analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM uplink interference analysis.

10.7.1 Interface Description: GSM Uplink Interference AnalysisThis section describes the interface for GSM uplink interference analysis. Before performingrelevant operations, familiarize yourself with the functions of the areas on the interface.

The analysis results of the uplink interference can be displayed in tables or in counter charts, asshown in Figure 10-2.



300

Figure 10-2 Interface for the overview of the uplink interference of cells


(1) Cell information list Displays the basic information about all the cellsinvolved in an analysis task in a table.

(2) Test Frequency interference Strength Displays the interference strength of all themeasured frequencies in the measurement cell ata certain time.

Each value on the vertical coordinate is the sumof 110 and the interference strength of themeasured frequency, which ensures that thevalues on the vertical coordinate are positive.

(3) Uplink Frequency Scanning Result Displays the interference strength of a certainfrequency in the selected cell during themeasurement period.

For details about the parameters on the interface, see 10.7.4 Parameters for Querying GSMUplink Interference Analysis Results.

10.7.2 Parameters of GSM Uplink Interference Analysis E2E TasksThis section describes the parameters for creating GSM E2E tasks. You can refer to thedescription when creating a GSM E2E task.



301

Common InformationParameter Description

Task Name Indicates the name of an E2E task.


E2E Task List Choose the E2E task type from the list.

Run Type l Once: The system executes the created tasks only once at thespecified time.

l Period: The system executes the created tasks at the presettime.

Start Time Indicates the time when the task starts to run.The start time must be later than the current time.

Cycle Indicates the interval between periodic tasks.

Execute Time Indicates the times that a periodic task is executed. If thisparameter is set to 0, you can infer that the task is executed allthe time.Value range: 0 to 65535.


Time (Minute) Indicates the total duration that a measurement task isperformed.The value is an integer from 5 to 1440.

NE Type Indicates the NE type M2000 supports.



302


Frequency Segment Indicates the frequency band used by a cell.When NE Type is BSC6000,the M2000 supports the scanningof the following frequency bands:l E-GSM900l DCS1800l PCS1900l P-GSM900l R-GSM900l GSM850When NE Type is BSC6900,the M2000 supports the scanningof the following frequency bands:l E-GSM900l DCS1800l PCS1900l P-GSM900l R-GSM900l GSM850

Cell Object Indicates the name of a cell related to the uplink interferenceanalysis task.

Frequency Type Indicates the types of the test ARFCNs. The options are asfollows:l All Frequency In The Frequency Segment

Indicates that all the ARFCNs in the selected frequencyband are measured.

l All Configuration Frequency In the Selected CellsIndicates the union of the ARFCNs of the selected cell.

l The User Selected Frequency In the Frequency SegmentIndicates that you need to manually select the ARFCNs tobe measured.

Related Tasks10.3.1 Creating GSM Uplink Interference Analysis Data E2E Tasks10.3.1 Creating GSM Uplink Interference Analysis Data E2E Tasks

10.7.3 Parameters for Creating and Modifying GSM UplinkInterference Analysis Tasks

This section describes the parameters for creating and modifying GSM uplink-interferenceanalysis tasks. You can refer to the description when creating or modifying a GSM uplink-interference analysis task.



303










ExecutionDelay



BSC If you select this option, the navigation tree displays all the NEs of the entirenetwork.




304


Interference AnalysisFrequency Band of theCurrent Call

Indicates the band of the current cell.The value of this parameter can be PGSM 900, EGSM 900,RGSM 900, DCS 1800, PCS 1900, and GSM 850. Thedefault value is PGSM 900.

Minimum DiversityThreshold

Indicates the threshold of the average interference strength ofthe uplink diversity antenna.This parameter can be set to any integer from -115 to 0. Thedefault value is -115.Unit: dBm

Minimum Main Threshold Indicates the threshold of the average interference strength ofthe uplink main antenna.This parameter can be set to any integer from -115 to 0. Thedefault value is -115.Unit: dBm

Frequency Type Setting Indicates an ARFCN type.The value can be BCCH or TCH.

Average CalculationAlgorithm

Indicates the method for calculating the average value.The value can be Signal Strength Average or PowerAverage. If the parameter is set to Signal StrengthAverage, the average value is calculated directly based on thesignal strength. If the parameter is set to Power Average, theaverage value is calculated based on the power that isconverted from the signal strength and then the average valueis converted to a value in the unit of signal strength.

Related Tasks10.4 Creating GSM Uplink Interference Analysis Tasks10.4 Creating GSM Uplink Interference Analysis Tasks

10.7.4 Parameters for Querying GSM Uplink Interference AnalysisResults

This section describes the parameters for querying GSM uplink interference analysis results.You can refer to the description when querying GSM uplink interference analysis results.



305

OverviewParameter

Range

Unit

Description

BSCName

1 to32characters

N/A Indicates the name of a BSC, for example, BSC_1.

CellName

1 to64characters

N/A Indicates the name of the cell that a measured TRX belongs to.

Frequency

N/A N/A Indicates the frequency of a measured TRX.

Type BCCH,TCH

N/A Indicates the type of a measured TRX. The options are BCCH andTCH.

DiverseAverageInterferenceStrength(dBm)

N/A dBm

Indicates the average diversity interference strength of a measuredTRX.

MainAverageInterferenceStrength(dBm)

N/A dBm

Indicates the average main interference strength of a measuredTRX.

ParametersParameter

Range

Unit

Description

CellName

1 to64characters

N/A Indicates the name of the cell that a measured TRX belongs to.



306

Parameter

Range

Unit

Description

BSCName

1 to32characters

N/A Indicates the name of a BSC, for example, BSC_1.

TimeScope

N/A N/A Indicates the time range in which an uplink interference analysistask is performed.

BCCHFrequency

N/A N/A Indicates a BCCH ARFCN of the selected cell.

FrequencyHoppingMode

NoneFH,basebandFH,RFFH,BCCH-involvedbasebandFH

N/A Indicates the type of the frequency hopping.

TCH List N/A N/A Indicates all TCH ARFCNs of the selected cell.

TimePoint

N/A N/A Indicates the counter bar chart of the selected cell at a certain time.

Sort Type Frequency,Diversity,Main

N/A Indicates the data sequence mode in the bar chart.Diversity indicates the average diversity interference strength.Main indicates the average main interference strength.

Date N/A Day Indicates the time range of analysis result data in the selected cell.

Frequency

N/A N/A Indicates the trend of the strength of a frequency in the selectedcell in a certain time segment. The trend is displayed on a linechart.



307

Related Tasks10.5 Querying GSM Uplink Interference Analysis Results10.5 Querying GSM Uplink Interference Analysis Results



308

11 GSM Terminal Inventory Analysis

About This Chapter

This section describes the GSM terminal inventory analysis tasks, including the management ofterminal Information and terminal inventory analysis tasks and the query and export of terminalinventory 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 performanceand guide subscribers to purchase terminals with good performance. In this case, subscriberscan obtain stable services, and the subscriber satisfaction can be improved.

11.1 Basic Knowledge of GSM Terminal Inventory AnalysisThis section describes the basic knowledge of GSM terminal inventory analysis. The GSMterminal inventory analysis function enables the Nastar to analyze the performance of varioustypes of terminals and subscriber behavior from the perspective of terminals based on CHR dataon the live network.

11.2 GSM Terminal Inventory Analysis ProcessThis section describes the GSM terminal inventory analysis process.

11.3 Managing Terminal InformationThis section describes how to manage terminal information. The terminal management functionenables you to add terminal types and set up the management record for the added terminal typesas required for terminal performance analysis. In addition, you can modify the properties of anexisting terminal type, delete, or export a terminal type.

11.4 Obtaining GSM Terminal Inventory Analysis DataThis section describes how to enable the Nastar to obtain GSM terminal inventory analysis data.You can create an E2E task to enable the Nastar to collect analysis data and create a data importtask so that the Nastar imports the collected analysis data into the database.

11.5 Creating a GSM Terminal Inventory Analysis TaskThis section describes how to create a GSM terminal inventory analysis task. After you createa GSM terminal inventory analysis task, the Nastar obtains and analyzes the call records of allsubscribers for the selected NEs. You can query the analysis results to know about terminalinventory information and terminal performance information on the live network.

11.6 Querying GSM Terminal Inventory Analysis Results

iManager NastarNetwork Optimization User Guide (GSM) 11 GSM Terminal Inventory Analysis


309

This section describes how to query GSM terminal inventory analysis results. The analysisresults help you collect statistics on terminal inventory information and analyze related KPIs tolearn about the performance of various types of terminals on a GSM network.

11.7 Exporting GSM Terminal Inventory Analysis ReportsThis section describes how to export GSM terminal inventory analysis reports. You can exportthe queried terminal inventory analysis results and terminal performance analysis results as .csvfiles.

11.8 Technical Specifications for GSM Terminal Inventory AnalysisThis section describes the technical specifications for GSM Terminal Inventory Analysis.

11.9 Reference to the GSM Terminal Inventory Analysis InterfaceThis section describes the interface for GSM terminal inventory analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM terminal analysis.



310

11.1 Basic Knowledge of GSM Terminal Inventory AnalysisThis section describes the basic knowledge of GSM terminal inventory analysis. The GSMterminal inventory analysis function enables the Nastar to analyze the performance of varioustypes of terminals and subscriber behavior from the perspective of terminals based on CHR dataon the live network.

Function and Usage ScenarioCall records of subscribers can reflect the access performance, service retainability, and intra-RAT handover performance of terminals. KPIs related to delay, service quality, and traffic canreflect the terminal capability.

Nastar terminal inventory analysis provides the following functions:l The Nastar displays the distribution of terminals on the live network by different

dimensions such as vendor or terminal model.l 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 todetermine whether the poor terminal performance is caused by a terminal defect or isaffected by special cells (for example, GSM cells near a TD-SCDMA network). Based onaggregation results of service-level KPIs, you can analyze each service and queried resultsto 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 theperformance of various types of terminals, analyze inventory information of various types ofterminals on the live network, and identify and analyze GSM traffic problems related to dual-mode terminals.

Basic Concept: IMEIInternational 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.l Final assembly code (FAC): consists of two digits and is used to identify a vendor.l 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.l 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 MStype, 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 arecomposed of TAC and FAC. In the Nastar window, IMEI-TAC refers to these eight digits.

11.2 GSM Terminal Inventory Analysis ProcessThis section describes the GSM terminal inventory analysis process.

Figure 11-1 shows the process of GSM terminal inventory analysis.



311

Figure 11-1 Process of terminal inventory analysis

Table 11-1 describes the items in the flowchart.



312

Table 11-1 Description of the terminal inventory analysis process


1 Manageterminal types

In the Analysis Task Management window on the Nastar client,you can switch to the terminal type management window to setthe information about the terminal types on the network. Theterminal information includes the IMEI-TAC, vendor, terminalmodel, chip model, terminal type, terminal technology and datatransfer. After the information is set, the Nastar can display theterminal information accordingly based on the detected IMEI-TAC when creating a terminal inventory analysis task. Thishelps users analyze the terminal efficiently.

2 Query NE datainformation

In the Analysis Task Management window on the Nastar client,you can switch to the data query window to query whether theraw data(It contains GSM configuration data and GSM terminalinventory analysis data.) required for the terminal inventoryanalysis is imported to the database.

3 Create aterminalinventoryanalysis E2Etask

On the Nastar client, choose Maintenance > E2E TaskManagement to open the E2E Task Management window,and then create a E2E task. After you create the task, the Nastarissues rule files to the M2000, and then the M2000 sends the rulefiles to the related SAU. Then, the SAU performs themeasurement task.

4 Create aterminalinventoryanalysis dataimport task

You need to choose Maintenance > Task Management on theNastar client to open the Task Management window, and thencreate a GSM terminal inventory analysis data import task. Afterthe tasks are created, the Nastar periodically imports the terminaldata files saved on the Nastar server into the database.

5 Create aterminalinventoryanalysis task

In the Analysis Task Management window on the Nastar client,you can create terminal inventory analysis tasks. After obtainingthe related analysis data from the database, the Nastar analyzesdata and then generates the analysis result.

6 Query terminalinventoryanalysis results

You can view the analysis results of the tasks that aresuccessfully performed.

7 Exportterminalinventoryanalysis reports

You can export the result files through the one-key method inthe analysis result query interface.

11.3 Managing Terminal InformationThis section describes how to manage terminal information. The terminal management functionenables you to add terminal types and set up the management record for the added terminal typesas required for terminal performance analysis. In addition, you can modify the properties of anexisting terminal type, delete, or export a terminal type.



313

Prerequisitesl You have logged in to the Nastar client.l You are authorized to manage terminal types.

ContextA 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, TerminalTechnology, and Data Transfer, as shown in Table 11-2. The match sequence of columns isspecified and automatic matching of columns is not supported.

Table 11-2 Example of a terminal type file

IMEI-TAC

Vendor Terminalmodel

ChipModel

TerminalType

TerminalTechnology

DataTransfer

86000400 Lenovo TD800 Huawei8 MS UMTS GPRS/EDGE/HSDPA

86004300 SAMSUNG

GT-I6320C

Huawei9 MS UMTS GPRS/EDGE

Procedure

Step 1 In the navigation tree on the left of the Analysis Task Management window, double-clickSystem Function > Terminal Type Management.

TIP

You can also select and right-click System Function > Terminal Type Management, and chooseOpen 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:Cellphone, Computer, Family gateway, and Wireless PSTN), Terminal Technology (values:GSM, UMTS, GSM/UMTS, and LTE), and Data Transfer (values: GPRS/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.



314


Customize a terminalproperty by adding it

1. In the Terminal Type Management window, right-clickthe table heading and choose Custom Column from theshortcut menu. The Custom Column dialog box isdisplayed.

2. In the Attribute area, click Add to add a property, and clickOK.

3. In the Attribute area, select the newly added property. Inthe Value area, click Add to add a value for this property.Click OK.

Customize a terminalproperty by importing aterminal property file

1. In the Terminal Type Management window, right-clickthe table heading and choose Custom Column from theshortcut menu. The Custom Column dialog box isdisplayed.

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.


Set the terminal type byadding it

1. Click New in the lower-right corner of the window. TheTerminal Type Management-New dialog box is displayed.

2. Set related parameters.Among the parameters, IMEI-TAC, Vendor, andTerminal model are mandatory. For details about theparameters, see 11.9.2 Parameters for Creating andModifying the Terminal Type.

3. Click OK.



315


Set the terminal type byimporting a terminal typefile

1. Click Import in the lower-right corner of the window. TheOpen 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 andif this file contains multiple worksheets, a message isdisplayed 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, clickOK.

l If the imported information is correct but certain recordsare identical with the existing records in the system, theConfirm dialog box is displayed. In this case, clickYes to overwrite the existing records and import newrecords.You can also click No in the displayed Confirm dialogbox to ignore the duplicate records and import theadditional records.

l If certain abnormal records exist in the information to beimported, the current file cannot be imported. In this case,the system displays the number of abnormal records.

4. Click OK.

----End

Follow-up ProcedureIn the Terminal Type Management window, perform various operations as required.


Modify a terminalproperty and itsvalue

1. In the Terminal Type Management window, right-click the tableheading and choose Custom Column from the shortcut menu. TheCustom Column dialog box is displayed.

2. In the Attribute area, select a property, and click Edit to change thename of the property.

3. In the Attribute area, select a property. In the Value, select a value,and click Edit to modify the value of this property.



316


Delete a terminalproperty and itsvalue

You are allowed to delete only user-defined properties.1. In the Terminal Type Management window, right-click the table

heading and choose Custom Column from the shortcut menu. TheCustom Column dialog box is displayed.

2. In the Attribute area, select a property. In the Value, select a value,and click Delete to delete the value of this property.

3. In the Attribute 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 terminalproperty and itsvalue


2. Click Export.3. In the Save dialog box, set a file name and specify a save path and

file type. Then, click Save.

Set the displayeffect of terminalinformation


2. Set (Add, Edit, or Delete) the terminal information.3. Click OK.

Modifyinformation abouta terminal type

1. In the Terminal Type Management window, select a piece ofterminal type information, and click Edit. The Terminal TypeManagement-Modify dialog box is displayed.

2. Modify the related parameters.The vendor and terminal model cannot be empty and the IMEI-TACcannot be changed.For details about the parameters, see 11.9.2 Parameters forCreating and Modifying the Terminal Type.

3. Click OK.If a terminal type is used by certain tasks, the modification does notaffect the ongoing tasks. If a terminal type is used by a periodic task,the related information is updated in the next period after themodification.

Delete a terminaltype

1. In the Terminal Type Management window, select one piece ormultiple pieces of terminal type information, and click Delete.

2. In the displayed Confirm dialog box, click Yes.If a terminal type is used by certain tasks, the modification does notaffect the ongoing tasks. If a terminal type is used by a periodic task,the related information is updated in the next period after themodification.



317


Export terminaltype informationand save theinformation ina .csv file

1. In the Terminal Type Management window, select one piece ormultiple pieces of terminal type information, and click Export.

2. In the Save dialog box, set a file name and specify a save path andfile type. Then, click Save.

NOTEYou can also right-click any area in the Terminal Type Management windowand choose Save as from the shortcut menu to export all terminal typeinformation.

If an exported file is in the .CSV format, do not edit it in Excel. It is advised thatyou edit it using Windows Notepad. Otherwise, the file cannot be importedcorrectly.

Related References11.9.2 Parameters for Creating and Modifying the Terminal Type

11.4 Obtaining GSM Terminal Inventory Analysis DataThis section describes how to enable the Nastar to obtain GSM terminal inventory analysis data.You can create an E2E task to enable the Nastar to collect analysis data and create a data importtask so that the Nastar imports the collected analysis data into the database.

11.4.1 Creating GSM Terminal Inventory Data Analysis E2E TasksThis section describes how to create a E2E task. After you create an E2E task, the Nastar issuesrule files to the M2000 and then the M2000 sends rule files to the related SAU. The SAU performsthe 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 fromthe SAU to the Nastar.



Configuration Data.l The data source is subscribed and the status is On.

Context




318

Procedure




Step 3 Set the basic task information.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.

Step 4 Click Next.

Step 5 Set Begin Time and End Time, and select one or multiple NEs from the NE list.

CAUTIONYou must consider the time zone difference between the Nastar and the SAU when setting thetask execution range. For example: The Nastar delivers an E2E task to be executed from 04:00to 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 Nastarserver after 06:00 in the local time on the Nastar server. Therefore, the Nastar completes E2Etasks 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.


Step 6 Click Next.

Step 7 Set the exception value for each KPI in the exception value setting list.


----End









319












Analysis TaskType



Manual creation



Manual creation



Manual creation



320

Analysis TaskType




Manual creation



Manual creation


Manual creation


- -



Manual creation



Manual creation




Manual creation



Manual creation



Manual creation



Manual creation



Manual creation

UMTS VIPAnalysis


Manual creation


- -



Manual creation



321

Analysis TaskType




Manual creation



Manual creation




Manual creation



Manual creation



Manual creation




Manual creation


- -




Manual creation




Manual creation



Manual creation

CDMA VIPAnalysis


Manual creation



322

Analysis TaskType




Manual creation


Manual creation



Manual creation



Manual creation


- -


- -

Procedure









NOTE




----End



323




















324




































325






























-



326

Procedure


TIP







----End

11.5 Creating a GSM Terminal Inventory Analysis TaskThis section describes how to create a GSM terminal inventory analysis task. After you createa GSM terminal inventory analysis task, the Nastar obtains and analyzes the call records of allsubscribers for the selected NEs. You can query the analysis results to know about terminalinventory information and terminal performance information on the live network.





Procedure






327


Step 3 Click Next.




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









Resume.



11.6 Querying GSM Terminal Inventory Analysis ResultsThis section describes how to query GSM terminal inventory analysis results. The analysisresults help you collect statistics on terminal inventory information and analyze related KPIs tolearn about the performance of various types of terminals on a GSM network.



328

Prerequisitesl You have logged in to the Nastar client.l You are authorized to perform the terminal inventory analysis function.l A terminal inventory analysis task is executed successfully.

Procedure

Step 1 In the navigation tree on the left of the Analysis Task Management window, click GSMTerminal Inventory Analysis Task.If you choose Theme Function, the task list on the right displays all the analysis tasks.


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 AnalysisResults from the shortcut menu. The GSM Terminal Inventory Analysis Task window isdisplayed.


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 thelive network, select Vendor in Analysis Dimension.

2. In Top N, 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 themost occupancy, set Top N 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 distributionproportion 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 certaintype of terminals in the Terminal Type Management window and if this property isselected as an analysis item, this property is identified by [IMEI-TAC].

4. Query statistical results in the table.Information in the table is consistent with that in the pie chart. You can query the numberof terminals of a certain type and the proportion of these terminals on the live network byan analysis item.

You can right-click statistical results and choose Save As from the shortcut menu to exportstatistical results as a .csv 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 GSM performance KPI.2. Query the values of terminal performance KPIs for each type of terminals in the upper-

right table.



329

3. Select a terminal type in the upper-right table, and query the values of KPIs for this typeof terminals in each cell in the lower-right table.

----End

11.7 Exporting GSM Terminal Inventory Analysis ReportsThis section describes how to export GSM terminal inventory analysis reports. You can exportthe queried terminal inventory analysis results and terminal performance analysis results as .csvfiles.

Prerequisitesl You have logged in to the Nastar client.l You have queried GSM terminal inventory analysis results. For details, see 11.6 Querying

GSM Terminal Inventory Analysis Results.

Procedurel Export terminal inventory analysis reports.

1. On the Terminal Inventory Analysis tab page of the GSM Terminal InventoryAnalysis Task window, click Export Inventory Analysis Report. The Save dialogbox is displayed.

2. Set a file name and specify a save path and file type. Then, click Save.The system exports terminal inventory analysis reports of all analysis dimensions.

l Export a terminal performance analysis report for a specified type of terminals.1. On the Terminal Performance Analysis tab page of the GSM Terminal Inventory

Analysis Task window, select a certain type of terminals.2. Click Export Performance Analysis Report for the Selected Terminal. The Save

dialog box is displayed.3. Set a file name and specify a save path and file type. Then, click Save.

----End

11.8 Technical Specifications for GSM Terminal InventoryAnalysis

This section describes the technical specifications for GSM Terminal Inventory Analysis.



<= 10,000 cells





330





<= 200


<= 50

11.9 Reference to the GSM Terminal Inventory AnalysisInterface

This section describes the interface for GSM terminal inventory analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM terminal analysis.

11.9.1 Interface Description: GSM Terminal Inventory AnalysisThis section describes the Terminal Inventory Analysis and Terminal PerformanceAnalysis tab pages of GSM terminal inventory analysis. Before performing relevant operations,familiarize yourself with the functions of the areas on these tab pages.

Description of the Terminal Inventory Analysis Tab PageThis tab page displays the terminal inventory on the live network in tables and charts, as shownin Figure 11-2.



331

Figure 11-2 Terminal Inventory Analysis tab page

SN Item Description

(1) Toolbar Provides two buttons for exporting inventory analysis reports andperformance analysis reports of specific terminals.

(2) Statistical barchart

Displays the distribution proportion of each type of terminals onthe live network by a certain dimension in a pie chart. The pie chartis displayed on the left, and the legends for the pie chart aredisplayed on the right.

(3) Statistical table Displays the number and distribution proportion of each type ofterminals on the live network by a certain dimension in a table.

Description of the Terminal Performance Analysis Tab PageFigure 11-3 shows the Terminal Performance Analysis tab page.



332

Figure 11-3 Terminal Performance Analysis tab page

SN Item Description

(1) KPI navigation tree Displays KPIs by category in the navigation tree. All KPIs areselected by default.

(2) KPI value forterminal type

Displays the values of KPIs related to each type of terminals.

(3) KPI value forterminal type in a cell

Displays the values of KPIs related to a certain type ofterminals in each cell.

11.9.2 Parameters for Creating and Modifying the Terminal TypeThis section describes the parameters for creating and modifying the terminal type. You canrefer to this section when you create and modify the terminal type.



333

Description of Parameters Related to Terminals


IMEI-TAC Indicates the first eight digits of the InternationalMobile Equipment Identity (IMEI) that identifiesthe type of a terminal. The parameter ismandatory.

Vendor Indicates the vendor of a terminal. The parameteris mandatory.

Terminal Model Indicates the model of a terminal. The parameteris mandatory.

Chip Model Indicates the chip model of a terminal.

Terminal Technology Indicates the system supported by a terminal. Inthe system are GSM, UMTS, GSM/UMTS, andLTE.

Data Transfer Indicates the transmission mode of data servicessupported 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 areCell phone, Computer, Family gateway, andWireless PSTN.

NOTE

The system does not automatically display the manufacturers and models of terminals. Only themanufacturers and models that are registered in the terminal type management are displayed.

Related Tasks11.3 Managing Terminal Information

11.9.3 Parameters for GSM Terminal Inventory Analysis Data E2ETasks

This section describes the parameters for creating GSM E2E tasks. You can refer to thedescription when creating a GSM E2E task.

Common Information






334


Begin Time Indicates the time when the task is executed.The begin time must be later than the current time.

End Time Indicates the time when the task stops running.

BSC List Indicates the NE object related to the task.It shows the configured NE information on the Nastar by BSCList > OSS Name > NE Name.

Special Parameter


Service Type Indicates service types of the terminal inventory analysis. It onlyincludes the CS service.

KPI Indicates the name of the KPIs.

Criterion Indicates the relation of the KPI and the threshold.

Threshold Specifies the value of KPI threshold.In the analysis report of the corresponding task, if the KPI value ofa corresponding user does not reach the threshold, it is consideredthat this is a problem KPI or deteriorated KPI.This parameter can be null. That is, no threshold is provided.

11.9.4 Parameters for Creating or Modifying GSM TerminalInventory Analysis Tasks

This section describes the parameters for creating or modifying GSM terminal inventory analysistasks. You can refer to the description when creating or modifying a GSM terminal inventoryanalysis task.

Task Common Information






335








ExecutionDelay





11.9.5 Parameters for Querying GSM Terminal Inventory AnalysisResults

This section describes the parameters for querying GSM terminal inventory analysis results.You can refer to the description when querying GSM terminal inventory analysis results.



336

OverviewParameter

Range

Unit

Description

IMEI-TAC

Eightdigits

N/A Indicates the combination of the type approval code (TAC) andthe final assembly code (FAC) in an International MobileEquipment Identity (IMEI). An IMEI consists of 15 digits anduniquely identifies a terminal in the world. In an IMEI, the TACrefers to the first six digits, and the FAC refers to the seventh andeighth digits. The combination of TAC and FAC uniquelyidentifies a terminal.

TerminalCount

[0,+∞)

Number

Indicates the number of terminals with the same IMEI-TAC anddifferent IMEIs within the statistical range.

Vendor N/A N/A Indicates the terminal vendor, for example, Nokia and iPhone.

TerminalModel

N/A N/A Indicates the terminal model, for example, iPhone4.

ChipModel

N/A N/A Indicates the terminal chip model.

TerminalTechnology

N/A N/A Indicates the format that the terminal supports, for example, GSMand UMTS.

TerminalType

N/A N/A Indicates the terminal type, for example, common terminal,intelligent terminal, and data card.

DataTransfer

N/A N/A Indicates the data transfer mode that the terminal uses, forexample, HSDPA and HSUPA.

SustainUtranFDDTerminal

[0,+∞)

Number

Indicates the number of terminals that have the same IMEI-TACand different IMEIs and support UTRAN FDD within thestatistical range.

SustainUtranTDDTerminal

[0,+∞)

Number

Indicates the number of terminals that have the same IMEI-TACand different IMEIs and support UTRAN TDD within thestatistical range.

SustainVAMOSTerminal

[0,+∞)

Number

Indicates the number of terminals that have the same IMEI-TACand different IMEIs and support VAMOS within the statisticalrange.

Numberof CallSetupRequests

[0,+∞)

Number

Indicates the number of originated call and terminated call setuprequests initiated by a terminal, that is, the number of voice servicecall setup requests (Channel request signaling) initiated by theterminal in the case that IMEIs are correctly identified.



337

Parameter

Range

Unit

Description

NumberofAbnormal CallSetups

[0,+∞)

Number

Indicates the number of abnormal originated call and terminatedcall setups.If a terminal receives a Connect Acknowledge message or aDisconnect message and the call is terminated by the peer terminal,the call is set up successfully.If a terminal receives a Clear command message and the call isproperly released by the network, local terminal, or peer terminal,the call is set up successfully.If an inter-BSC handover occurs during the call setup process andthe call fails to be set up in the destination BSC, the Nastar recordsthat the call is released abnormally.

Proportion ofAbnormal CallSetup(%)

[0,100]

% Indicates the proportion of abnormal originated call andterminated call setups.Proportion of abnormal call setups = Number of abnormal callsetups/Number of call setup requests x 100%

NumberofOriginated CallSetupRequests

[0,+∞)

Number

Indicates the number of originated call setup requests, that is, thenumber of voice service call setup requests (Channel requestsignaling) in the case that IMEIs are correctly identified.

NumberofAbnormalOriginated CallSetups

[0,+∞)

Number

Indicates the number of abnormal originated call setups.If the terminal receives a Connect Acknowledge signaling or theDisconnect signaling and the call is terminated by the peerterminal, the call setup is successful.If the terminal receives a Clear command message and the call isnormally released by the network, local terminal, or peer terminal,the call setup is successful.If inter-BSC handover occurs during the call setup process and thecall fails to be set up in the destination BSC, the Nastar recordsthat the call is released abnormally.

Proportion ofAbnormalOriginated CallSetup(%)

[0,100]

% Indicates the proportion of abnormal originated call setups.Proportion of abnormal originated call setups = Number ofabnormal originated call setups/Number of originated call setuprequests x 100%



338

Parameter

Range

Unit

Description

NumberofTerminated CallSetupRequests

[0,+∞)

Number

Indicates the number of terminated call setup requests, that is, thenumber of voice service call setup requests (Channel requestsignaling) in the case that IMEIs are correctly identified.

NumberofAbnormalTerminated CallSetups

[0,+∞)

Number

Indicates the number of abnormal terminated call setups.If a terminal receives a Connect Acknowledge message or aDisconnect message and the call is terminated by the peer terminal,the call is set up successfully.If a terminal receives a Clear command message and the call isproperly released by the network, local terminal, or peer terminal,the call is set up successfully.If an inter-BSC handover occurs during the call setup process andthe call fails to be set up in the destination BSC, the Nastar recordsthat the call is released abnormally.

Proportion ofAbnormalTerminated CallSetup(%)

[0,100]

% Indicates the proportion of abnormal terminated call setups.Proportion of abnormal terminated call setups = Number ofabnormal terminated call setups/Number of terminated call setuprequests

NumberofAbnormal CallReleases

[0,+∞)

Number

Indicates the total number of abnormal call releases after theterminal uses the voice service to access the network. The call isabnormally released if any of the following situations occurs:1. The Disconnect message carries an abnormal cause (not Normalsignaling) when the call is released.2. The terminal receives the Clear command message, and the callis abnormally released by the network, local terminal, or peerterminal.3. An inter-BSC handover fails.4. An intra-BSC handover fails.5. The BSC is abnormal.6. The MSC is abnormal.

Proportion ofAbnormal CallRelease(%)

[0,100]

% Indicates the proportion of abnormal call releases after the terminaluses the voice service to access the network.Proportion of abnormal call releases = Number of abnormal callreleases/Number of call release requestsThe number of call release requests refers to the times the terminalsends a Disconnect message.



339

Parameter

Range

Unit

Description

NumberofOriginated ShortCalls

[1,+∞)

Number

Indicates the number of measurement reports (MRs) on theoriginated calls with the duration that is less than the specifiedthreshold. The call duration is from the time when the terminalreceives a Connect Acknowledge message to the time when theterminal sends a Disconnect message. The Nastar does not analyzethe CHRs on calls involved in inter-BSC handovers because theentire duration of the calls cannot be obtained.

Proportion ofOriginated ShortCall(%)

[0,100]

% Indicates the proportion of MRs on the originated calls with theduration that is less than the specified threshold to all MRs.Proportion of originated short calls = Number of originated shortcalls/Number of MRs with valid originated call duration

NumberofTerminated ShortCalls

[1,+∞)

Number

Indicates the number of MRs on the terminated calls with theduration that is less than the specified threshold. The call durationis from the time when the terminal receives a ConnectAcknowledge message to the time when the terminal sends aDisconnect message. The Nastar does not analyze the CHRs oncalls involved in inter-BSC handovers because the entire durationof the calls cannot be obtained.

Proportion ofTerminated ShortCall(%)

[0,100]

% Indicates the proportion of MRs on the terminated calls with theduration that is less than the specified threshold to all MRs.Proportion of terminated short calls = Number of terminated shortcalls/Number of MRs with valid terminated call duration

Proportion ofAbnormal VoiceServiceRelease(s)

[1,+∞)

s Proportion of abnormal voice service releases = Total traffic/Number of abnormal voice service releasesThe total traffic refers to the duration from the time when theterminal receives a Connect Acknowledge to the time when theterminal sends a Disconnect message.

Numberof Intra-RAT HORequests

[0,+∞)

Number

Indicates the number of intra-RAT handover requests initiated bythe terminal.

NumberofAbnormal Intra-RATHOs

[0,+∞)

Number

Indicates the number of abnormal intra-RAT handovers.



340

Parameter

Range

Unit

Description

Proportion ofAbnormal Intra-RAT HO(%)

[0,100]

% Indicates the proportion of abnormal intra-RAT handovers.Proportion of abnormal intra-RAT handovers = Number ofabnormal intra-RAT handovers/Number of intra-RAT handoverrequests x 100%

NumberofAbnormalReleasesDuringIntra-RAT HO

[0,+∞)

Number

Indicates the number of abnormal call releases during the intra-RAT handover.

Numberof Inter-RATOutgoingHORequests

[0,+∞)

Number

Indicates the number of terminal requests for the handover from acell on a GSM network to a cell on another network.

NumberofAbnormal Inter-RATOutgoingHOs

[0,+∞)

Number

Indicates the number of abnormal terminal handovers from a cellon a GSM network to a cell on another network.

Proportion ofAbnormal Inter-RATOutgoingHO(%)

[0,100]

% Indicates the proportion of abnormal terminal handovers from acell on a GSM network to a cell on another network.Proportion of abnormal outgoing inter-RAT handovers = Numberof abnormal outgoing inter-RAT handovers/Number of outgoinginter-RAT handover requests x 100%

NumberofAbnormalReleasesDuringInter-RATOutgoingHO

[0,+∞)

Number

Indicates the number of abnormal call releases during the handoverof the terminal from a cell on a GSM network to a cell on anothernetwork.



341

Parameter

Range

Unit

Description

Numberof Inter-RATIncomingHORequests

[0,+∞)

Number

Indicates the number of terminal requests for the handover from acell on another network to a cell on a GSM network.

NumberofAbnormal Inter-RATIncomingHOs

[0,+∞)

Number

Indicates the number of abnormal terminal handovers from a cellon another network to a cell on a GSM network.

Proportion ofAbnormal Inter-RATIncomingHO(%)

[0,100]

% Indicates the proportion of abnormal terminal handovers from acell on another network to a cell on a GSM network.Proportion of abnormal incoming inter-RAT handovers = Numberof abnormal incoming inter-RAT handovers/Number of incominginter-RAT handover requests x 100%

NumberofReportsfor Inter-RATIncomingHODelay

[0,+∞)

Number

Indicates the number of MRs with valid incoming inter-RAThandover delays. The Nastar cannot collect statistics on the delaysof failed incoming inter-RAT handovers.Incoming inter-RAT handover delay = Handover completion time- Handover request time

AverageDelay forInter-RATIncomingHO(s)

[0,+∞)

s Indicates the average delay for the handover from a cell on anothernetwork to a cell on a GSM network.Average delay for incoming inter-RAT handover = Delay of allsuccessful incoming inter-RAT handovers/Number of MRs withvalid incoming inter-RAT handover delays

NumberofReportsforOriginated CallSetupDelay

[0,+∞)

Number

Indicates the number of MRs with valid interval between the timewhen the terminal sends a Channel Request message to originatea call and the time when the terminal receives an Alerting message.The Nastar does not collect statistics on the delay for calls involvedin inter-BSC handovers.



342

Parameter

Range

Unit

Description

AverageDelay forOriginated CallSetup(s)

[0,+∞)

s Indicates the average interval between the time when the terminalsends a Channel Request message to originate a call and the timewhen the terminal receives an Alerting message.

Proportion of LongDelay forOriginated CallSetup(%)

[0,100]

% Indicates the proportion of MRs in which the originated call setupdelay is greater than the specified threshold.Proportion of long delay for originated call setup = Number ofMRs in which the originated call setup delay is greater than thespecified threshold/Number of MRs with originated call setupdelay x 100%

NumberofReportsforTerminated CallSetupDelay

[0,+∞)

Number

Indicates the number of MRs with valid interval between the timewhen the terminal sends a Channel Request message to terminatea call and the time when the terminal receives an Alerting message.The Nastar does not collect statistics on the delay for calls involvedin inter-BSC handovers.

AverageDelay forTerminated CallSetup(s)

[0,+∞)

s Indicates the average interval between the time when the terminalsends a Channel Request message to terminate a call and the timewhen the terminal receives an Alerting message.

Proportion of LongDelay forTerminated CallSetup(%)

[0,100]

% Indicates the proportion of MRs in which the terminated call setupdelay is greater than the specified threshold.Proportion of long delay for terminated call setup = Number ofMRs in which the terminated call setup delay is greater than thespecified threshold/Number of MRs with terminated call setupdelay x 100%

Numberof ULVQIReports

[0,+∞)

Number

Indicates the number of MRs with valid uplink Voice QualityIndicator (VQI) of the voice service.As the Mean Opinion Score (MOS), VQI reflects the voice qualityduring the call process. The VQI value ranges from 1 to 5. Thegreater the VQI value, the better the voice quality.

AverageUL VQI

[1.00,5.00]

N/A Average uplink VQI value = Total value of uplink VQIs/Numberof MRs with valid uplink VQI

Proportion of PoorUL VQIReport(%)

[0,100]

% Indicates the proportion of MRs in which the uplink VQI value issmaller than the specified threshold.Proportion of MRs with poor uplink VQI = Number of MRs inwhich the uplink VQI value is smaller than the specified threshold/Number of MRs with uplink VQI x 100%



343

Parameter

Range

Unit

Description

Numberof ULHQIReports

[0,+∞)

Number

Indicates the number of MRs with valid uplink High QualityIndicator (HQI) of the voice service.HQI reflects the voice quality during the call process. The HQIvalue ranges from 0 to 7. The smaller the HQI value, the better thevoice quality.In the CHRs of BSC6900 V900R011 and later BSC versions:HQI value = Number of MRs with grade 0 to grade 3 receivequality/Number of MRs with grade 0 to grade 7 receive quality x100%In the CHRs of BSC6000 V900R008:HQI value = Number of MRs with grade 0 to grade 5 receivequality/Number of MRs with grade 0 to grade 7 receive quality x100%

AverageUL HQI

[0,100]

% Indicates the average uplink HQI value obtained on the basis ofMRs with valid uplink HQI within the statistical range and time.Average uplink HQI value = Total value of uplink HQIs/Numberof MRs with uplink HQI

Proportion of PoorUL HQIReport(%)

[0,100]

% Indicates the proportion of MRs in which the uplink HQI value issmaller than the specified threshold within the statistical range andtime.Proportion of MRs with poor uplink HQI = Number of MRs inwhich the uplink HQI is smaller than the specified threshold/Number of MRs with uplink HQI x 100%

Numberof DLHQIReports

[0,+∞)

Number

Indicates the number of MRs with valid downlink HQI of the voiceservice.HQI reflects the voice quality during the call process. The HQIvalue ranges from 0 to 7. The smaller the HQI value, the better thevoice quality.In the CHRs of BSC6900 V900R011 and later BSC versions:HQI value = Number of MRs with grade 0 to grade 3 receivequality/Number of MRs with grade 0 to grade 7 receive quality x100%In the CHRs of BSC6000 V900R008:HQI value = Number of MRs with grade 0 to grade 5 receivequality/Number of MRs with grade 0 to grade 7 receive quality x100%

AverageDL HQI(%)

[0,100]

% Indicates the average downlink HQI value obtained on the basisof MRs with valid downlink HQI within the statistical range andtime.Average downlink HQI value = Total value of downlink HQIs/Number of MRs with downlink HQI



344

Parameter

Range

Unit

Description

Proportion of PoorDL HQIReport(%)

[0,100]

% Indicates the proportion of MRs in which the downlink HQI valueis smaller than the specified threshold within the statistical rangeand time.Proportion of MRs with poor downlink HQI = Number of MRs inwhich the downlink HQI value is smaller than the specifiedthreshold/Number of MRs with downlink HQI x 100%

Proportion of ULCrosstalk(%)

[0,100]

% Indicates the proportion of calls with uplink one-way audio.Proportion of calls with uplink one-way audio = Number ofsuccessful calls with uplink one-way audio/Total number ofsuccessful calls x 100%The uplink one-way audio check detects only one-way audio onthe BSS internal channel between the BTS and the TC board butcannot detect one-way audio over the Um interface and Ainterface.Principle of the uplink one-way audio check:The DSP on the TC board of the BSC periodically collectsstatistics on the ratio of error uplink TRAU frames. When the ratioof error uplink TRAU frames reaches the threshold, the BSSdetermines that low-level one-way audio occurs on the uplink andstarts the confirmation mechanism. The BSC notifies the BTS tosend a test TRAU frame, one-way audio occurs on the uplink voicechannel if the TS does not receive the test TRAU frame within thespecified time.The total number of successful calls refers to the number ofsuccessful call setups within the statistical range, including thenumber of successful channel assignments during inter-BSCincoming handovers.



345

Parameter

Range

Unit

Description

Proportion of DLCrosstalk(%)

[0,100]

% Indicates the proportion of calls with downlink one-way audio.Proportion of calls with downlink one-way audio = Number ofsuccessful calls with downlink one-way audio/Total number ofsuccessful calls x 100%The downlink one-way audio check detects only one-way audioon the BSS internal channel between the BTS and the TC boardbut cannot detect one-way audio over the Um interface and Ainterface.Principle of the downlink one-way audio check:The DSP on the DTRU of the BTS periodically collects statisticson the ratio of error downlink TRAU frames. When the ratio oferror downlink TRAU frames reaches the threshold, the BSSdetermines that low-level one-way audio occurs on the downlinkand starts the confirmation mechanism. The BSC notifies the TCboard to send a test TRAU frame, one-way audio occurs on thedownlink voice channel if the BTS does not receive the test TRAUframe within the specified time.The total number of successful calls refers to the number ofsuccessful call setups within the statistical range, including thenumber of successful channel assignments during inter-BSCincoming handovers.

Proportion of ULOne-WayAudio(%)

[0,100]

% Indicates the proportion of calls with no audio on both the uplinkand the downlink.Proportion of calls with no audio on both the uplink and thedownlink = Number of calls with downlink one-way audio anduplink one-way audio/Total number of successful calls x 100%

Proportion of DLOne-WayAudio(%)

[0,100]

% Indicates the proportion of calls with uplink crosstalk.Proportion of calls with uplink crosstalk = Number of calls withuplink crosstalk/Total number of successful calls x 100%The uplink crosstalk check detects only crosstalk on the BSSinternal channel between the BTS and the TC board but cannotdetect crosstalk over the Um interface and A interface.Principle of the uplink crosstalk check:The DSP of the BTS inserts call unique IDs into the idle bits ofuplink voice TRAU frames during the call process. The DSP ofthe TC board decodes the call unique IDs and checks theconsistency of the call unique IDs with the call unique ID in theDSP of the TC board. If all call unique IDs in the uplink voiceTRAU frames are inconsistent with the call unique ID in the DSPof the TC board within the check period, uplink crosstalk occurs.



346

Parameter

Range

Unit

Description

Proportion of NoAudio(%)

[0,100]

% Indicates the proportion of calls with uplink crosstalk.Proportion of calls with downlink crosstalk = Number of calls withdownlink crosstalk/Total number of successful calls x 100%The downlink crosstalk check detects only crosstalk on the BSSinternal channel between the BTS and the TC board but cannotdetect crosstalk over the Um interface and A interface.Principle of the downlink crosstalk check:The DSP of the TC board inserts call unique IDs into the idle bitsof downlink voice TRAU frames during the call process. The DSPof the BTS decodes the call unique IDs and checks the consistencyof the call unique IDs with the call unique ID in the DSP of theBTS. If all call unique IDs in the downlink voice TRAU framesare inconsistent with the call unique ID in the DSP of the BTSwithin the check period, downlink crosstalk occurs.

NumberofReportsfor VoiceServiceDuration

[0,+∞)

Number

Indicates the number of MRs with valid voice service duration.The voice service duration is the TCH occupation duration fromthe time when the TCH is assigned to the time when the TCH isreleased.

AverageVoiceServiceDuration(s)

[0,+∞)

s Indicates the average duration of the voice service. The voiceservice duration in the MR is from the time when the TCH isassigned to the time when the TCH is released.Average voice service duration = TCH occupation duration/Number of MRs with voice service duration

Numberof VoiceServiceDurationReportsforTerminalsSupportingUTRANFDD

[0,+∞)

Number

Indicates the number of MRs with valid voice service duration ofterminals that support UTRAN FDD.The voice service duration is the TCH occupation duration fromthe time when the TCH is assigned to the time when the TCH isreleased.



347

Parameter

Range

Unit

Description

AverageVoiceServiceDurationforTerminalsSupportingUTRANFDD(s)

[0,+∞)

s Indicates the average voice service duration for terminals thatsupport UTRAN FDD. The voice service duration in the MR isfrom the time when the TCH is assigned to the time when the TCHis released.Average voice service duration = TCH occupation duration/Number of MRs with voice service duration

Numberof VoiceServiceDurationReportsforTerminalsSupportingUTRANTDD

[0,+∞)

Number

Indicates the number of MRs with valid voice service duration ofterminals that support UTRAN TDD.The voice service duration is the TCH occupation duration fromthe time when the TCH is assigned to the time when the TCH isreleased.

AverageVoiceServiceDurationforTerminalsSupportingUTRANTDD(s)

[0,+∞)

s Indicates the average voice service duration for terminals thatsupport UTRAN TDD. The voice service duration in the MR isfrom the time when the TCH is assigned to the time when the TCHis released.Average voice service duration = TCH occupation duration/Number of MRs with voice service duration

Cell InformationParameter

Range

Unit

Description

BSCID 1 to32characters

N/A Indicates the name of the BSC where the terminal is located.



348

Parameter

Range

Unit

Description

CellName

1 to64characters

N/A Indicates the name of the cell where the terminal is located.


N/A Indicates the global identity of the cell where the terminal islocated.

NOTEFor details about other parameters, see the overview table.



349

12 GSM VIP Analysis

About This Chapter

The GSM VIP analysis function enables you to obtain GSM VIP analysis data, create GSM VIPanalysis tasks, and query GSM VIP analysis results from the Nastar. By monitoring the KPIsrelated to the quality of service (QoS) of VIP subscribers, the Nastar helps you identify and solvethe network problems that may cause VIP complaints so that the service quality of VIPsubscribers is ensured and the satisfaction of VIP subscribers is improved.This function can beused to quickly locate and resolve problems. Normally there is no way to avoid that some userdata such as International Mobile Subscriber Identity (IMSI) will be used during thetroubleshooting. However, this function provides an anonymous data processing method. Youare obligated to take considerable measures, in compliance with the laws of the countriesconcerned and the user privacy policies of your company, to ensure that the personal data ofusers is fully protected.

12.1 Basic Knowledge of GSM VIP AnalysisThis section describes the basic knowledge of GSM VIP analysis, including GSM VIP analysisfunction and authority policies for GSM VIP analysis.

12.2 Process of GSM VIP AnalysisThis section describes the process of GSM VIP analysis.

12.3 Managing GSM VIP groupsThis section describes how to manage GSM VIP groups. The function of managing GSM VIPgroups enables you to create VIP groups so that you can monitor the service quality of VIPsubscribers in a VIP group, and modify, delete, and export the existing VIP groups.

12.4 Obtaining GSM VIP Analysis DataThis section describes how to enable the Nastar to obtain GSM VIP analysis data. You can createan E2E task to enable the Nastar to collect analysis data and create a data import task so that theNastar imports the collected analysis data into the database.

12.5 Setting a Mailbox for Sending Analysis ReportsAfter a mailbox for sending analysis reports is set, the Nastar can send the generated analysisreports to the specified mailboxes through the mailbox.

12.6 Creating GSM VIP Analysis TasksThis section describes how to create GSM VIP analysis tasks. After a GSM VIP analysis taskis created, the Nastar aggregates and analyzes the service call report quantity, traffic, and KPIsof a VIP subscriber or a VIP group. This helps to solve subscriber-level network optimization

iManager NastarNetwork Optimization User Guide (GSM) 12 GSM VIP Analysis


350

problems so that service quality of VIP subscribers is ensured and VIP subscriber satisfactionis improved.

12.7 Querying GSM VIP Analysis ResultsThis section describes how to query GSM VIP analysis results. By monitoring the number ofservice call reports, traffic, and KPIs of the selected VIP subscriber, you can learn about thequality of service (QoS) of the VIP subscriber and identify and solve the network problems thatmay cause VIP complaints.

12.8 Querying GSM VIP Trend Analysis ResultsThe Nastar provides functions for querying the analysis results of GSM VIP trends, such assetting trend analysis parameters, querying trend analysis results, and drilling down throughtrend analysis results. By analyzing the trends based on periodic analysis results, the Nastar helpsnetwork optimization engineers identify the KPI change trends during the monitoring andoptimization VIP KPIs. This implements further problem analysis and location.

12.9 Technical Specifications for GSM VIP AnalysisThis section describes the technical specifications for GSM VIP analysis.

12.10 Reference to the GSM VIP Analysis InterfaceThis section describes the interface for GSM VIP analysis and the relevant parameters. Beforeperforming relevant operations, familiarize yourself with the functions of GSM VIP analysis.



351

12.1 Basic Knowledge of GSM VIP AnalysisThis section describes the basic knowledge of GSM VIP analysis, including GSM VIP analysisfunction and authority policies for GSM VIP analysis.

12.1.1 GSM VIP Analysis FunctionThe GSM VIP analysis function enables the Nastar to routinely monitor service KPIs of theselected VIP subscribers on the network. The reports based on the routine monitoring help youknow the service quality experienced by VIP subscribers. This helps network optimizationengineers identify and solve potential network problems in advance, improving VIP subscribersatisfaction.

VIP AnalysisThe Nastar obtains the information about IMSIs reported by MSs during communications andfinally helps solve the problems related to the subscriber-level network optimization throughaggregation and analysis of KPIs (including service-level KPIs in CS domain and KPIs of activecells) by VIP group and VIP subscriber.l Aggregation and analysis of KPIs by VIP group help network optimization engineers

monitor the services of subscribers in important groups in a centralized, convenient, andtimely manner. This improves the operation efficiency and reduces the operationexpenditure. In addition, this function helps operators identify problem VIP groups andproblem VIP subscribers so that they can analyze and solve the problems in advance.

l Aggregation and analysis of KPIs by VIP subscriber provide an analysis of KPI changetrends related to subscriber experience and behavior. For example, analysis of change trendsof voice business access delay chart, analysis of change trends of voice business setup delaychart are provided. The trend analysis based on different types helps network optimizationengineers quickly identify the worst and best service quality of VIP subscribers and changetrends of service quality during a certain period.

The Nastar also provides an in-depth analysis for the VIP subscribers whose raw data is collectedin advance. If the KPIs of some VIP subscribers in a group deteriorate but the problem cannotbe located on site, the Nastar helps network optimization engineers retrieve the detailed callreports of these VIP subscribers within a specified period. By analyzing these reports, thenetwork 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 beforelink release and exception causes to locate problems.

Aggregation and analysis of KPIs of active cells by VIP group and VIP subscriber help networkoptimization engineers learn about the main active areas of VIP subscribers on the network. Ifthere are any network problems in these active areas, the network optimization engineers canquickly identify the key cells that need to be preferentially handled to solve these networkproblems and solve the problem of the service quality deterioration caused by these networkproblems in time.

VIP Change TrendBy analyzing the KPI change trends of VIP subscribers based on periodic analysis results, theNastar helps network optimization engineers identify the KPI change trends during themonitoring and optimization of VIP KPIs. This helps in further problem analysis and location.



352

Nastar versions earlier than V600R009 do not support VIP trend analysis. In these versions, thenetwork optimization engineers must aggregate the analysis results and draw trend chartsmanually after saving the analysis results, which leads to low work efficiency. In NastarV600R009, the VIP trend analysis function is provided, which effectively improves the workefficiency of network optimization engineers.

This function can be used for only periodic VIP analysis tasks, which are executed hourly, daily,or weekly.

Synchronous Display of VIP Active Cells in the GISUsed with the GIS, the VIP analysis function enables the Nastar to display active cells on a mapand render active cells by type. The Nastar can also display active cells and the GISsynchronously for users to quickly locate a cell, improving the problem analysis and locationefficiency for network optimization engineers.

LimitationsThe GSM VIP analysis function allows NEs to report raw call data of important VIP subscribersto the Nastar. The amount of raw data is huge. Therefore, a limitation must be imposed to preventsystem overload in the case of concurrent operations by a large number of users. In the case ofanalysis by VIP group, the Nastar can analyze data of 30,000 VIP subscribers (that is, the numberof VIP subscribers in all VIP groups that are selected for the analysis cannot exceed 30,000). Inthe 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 datacannot exceed 2,000).

The KPI analysis function for active cells of GSM VIP subscribers enables the Nastar to displaythe geographic distribution of active cells. Correct engineering parameters must be imported toensure the display effect.

12.1.2 Authority Policies for GSM VIP AnalysisThe Nastar provides secure authority management policies to ensure the security of privateinformation for subscribers. The authority management policies enable different types of usersto have different operation rights for the security of their private information.

Introduction to Authority Typesl 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 tothe management domain of a user or a user group, the user or users in the group have theview rights to this security object.For details about how to enable view rights for users, see the description in "Managementdomain of user" in Creating an Nastar User Account.

l Operation rights allow users to perform an operation. If a user has operation rights, the usercan perform a specific operation. Here, operation rights include query rights to VIP analysistasks, operation rights to VIP analysis tasks, management rights to VIP groups, and rightsto create, modify, and delete subnets.Operation rights are associated with the management domain. A user can perform theoperation corresponding to the operation rights for only the objects in the managementdomain of the user.



353

– Query rights to VIP analysis tasks: If a Nastar user has the rights, the user can querythe 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 deletesubnets, 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 "Operationrights of user" in Creating an Nastar User Account.

Introduction to Authority PoliciesThe 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 deleteinformation about VIP groups created by any user.

l 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 deletesubnets.For details, see Scenario 1 in Table 12-1.

– To modify, query, or delete information about VIP groups created by the user in theadministrator 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 theadministrator group or security administrator group must have operation rights and viewrights to VIP groups.For details, see Scenario 6 in Table 12-1.

– To query information VIP groups created by other users, the user in the administratorgroup or security administrator group must have view rights to VIP groups.For details, see Scenario 7 in Table 12-1.

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.

l Users not in the administrator group:– 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 rightsto VIP analysis tasks. (The authority policies for this type of user to modify and deleteVIP analysis tasks in this situation are the same as those to create VIP analysis tasks.)For details, see Scenario 2 in Table 12-1.

– To create a VIP analysis task involving VIP groups created by other users, the user inthe administrator group or security administrator group must have view rights to VIPgroups created by other users and have operation rights to VIP analysis tasks. (Theauthority policies for this type of user to modify and delete VIP analysis tasks in thissituation are the same as those to create VIP analysis tasks.)



354

For details, see Scenario 3 in Table 12-1.– 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.For details, see Scenario 4 in Table 12-1.

– To query VIP analysis tasks created by other users, the user in the administrator groupor security administrator group must have view rights to VIP groups created by otherusers and have query rights to VIP analysis tasks.For details, see Scenario 5 in Table 12-1.

l To ensure the security of private information for subscribers, asterisks (****) are used toshield the last four digits of IMSI and MS Number in VIP analysis results.

Example of Authority PoliciesAuthority policies vary according to the specific scenario. Table 12-1 describes the authoritypolicies in different scenarios.

NOTE

"User" in Table 12-1 refers to a user in the administrator group or security administrator group.

Table 12-1 Example of authority policies

Scenario Operation Procedure

Scenario 1User A needs to create three VIP groups,namely, VIP_a, VIP_b, and VIP_c.

1. Log in to the Nastar client as a user, forexample, user admin.

2. Assign user A rights to manage VIP groupsand rights to create, modify, and deletesubnets.In the Select Operation Rights dialog box,add Create Subnet, Delete Subnet, andModify Subnet under Operation > TopoManagement, and VIP GroupManagement under Operation > NastarPA to Selected Rights, and click OK. Fordetails, 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 12.3 Managing GSM VIP groups.



355


Scenario 2User A needs to create a VIP analysis tasknamed X. Only the three VIP groups(VIP_a, VIP_b, and VIP_c) created byuser A are involved in this analysis task.


2. Assign user A operation rights to VIPanalysis tasks.In the Select Operation Rights dialog box,add Operation > Nastar PA > GSM VIPAnalysis to Selected Rights, and click OK.For details, see Creating an Nastar UserAccount.

3. Log in to the client as user A.4. Create a VIP analysis task named X.

For details about how to create VIP analysistasks, see 12.6 Creating GSM VIP AnalysisTasks.

Scenario 3User A needs to create a VIP analysis tasknamed Y. Two VIP groups (VIP_d andVIP_e) created by user B are involved inthis analysis task.


2. Assign user A view rights to VIP_d andVIP_e.In the Select Domain dialog box, addVIP_d and VIP_e under All Objects >Network Device > Object Set > SubnetDevice Set to Selected devices and objectsets, and click OK. For details, see Creatingan Nastar User Account.

3. Assign user A operation rights to VIPanalysis tasks.In the Select Operation Rights dialog box,add Operation > Nastar PA > GSM VIPAnalysis to Selected Rights, and click OK.For details, see Creating an Nastar UserAccount.

4. Log in to the client as user A.5. Create a VIP analysis task named Y.

For details about how to create VIP analysistasks, see 12.6 Creating GSM VIP AnalysisTasks.

Scenario 4User A needs to query analysis task Xcreated by user A.

Log in to the client as user A.



356


Scenario 5User B needs to query analysis task Xcreated by user A. Three VIP groups(VIP_a, VIP_b, and VIP_c) created byuser A are involved in this analysis task.


2. Assign user B view rights to VIP_a, VIP_b,and VIP_c.In the Select Domain dialog box, addVIP_a, VIP_b, and VIP_c under AllObjects > Network Device > Object Set >Subnet Device Set to Selected devices andobject sets, and click OK. For details, seeCreating an Nastar User Account.

3. Assign user B view rights to VIP analysistasks.In the Select Operation Rights dialog box,add Operation > Nastar PA > GSM VIPAnalysis Task View to Selected Rights, andclick OK. For details, see Creating an NastarUser 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 analysisresults and VIP trend analysis results, see12.7 Querying GSM VIP AnalysisResults and 12.8 Querying GSM VIPTrend Analysis Results.

Scenario 6User B needs to modify detailedinformation about VIP groups VIP_a,VIP_b, and VIP_c created by user A.



3. Assign user B management rights to VIPgroups.In the Select Operation Rights dialog box,add Operation > Nastar PA > VIP GroupManagement to Selected Rights, and clickOK. For details, see Creating an Nastar UserAccount.

4. Log in to the client as user B.5. In the VIP Group Management window,

modify detailed information about these VIPgroups.



357


Scenario 7User B needs to query detailed informationabout VIP groups VIP_a, VIP_b, andVIP_c created by user A.



3. Log in to the client as user B.4. In the VIP Group Management window,

double-click each VIP group to querydetailed information.

12.2 Process of GSM VIP AnalysisThis section describes the process of GSM VIP analysis.

Figure 12-1 shows the process of GSM VIP analysis.

NOTE

Required rights must be assigned to users to properly perform VIP analysis tasks. For details about authoritypolicies, see 12.1.2 Authority Policies for GSM VIP Analysis.



358

Figure 12-1 Process of GSM VIP analysis


Table 12-2 Description of GSM VIP analysis process


1 Manage GSM VIPgroups

In the Analysis Task Management window on the Nastarclient, you can enter the VIP group management window tocreate VIP groups and subscribers required for VIP analysis.After creating VIP groups and subscribers, the Nastarperforms VIP analysis by VIP subscriber or VIP group.



359


2 Create a GSM VIPanalysis data E2Etask

You can choose Maintenance > E2E Task Managementon the Nastar client to open the E2E Task Managementwindow and then create a E2E task. After you create the task,the Nastar issues rule files to the M2000, and then the M2000sends the rule files to the related SAU. Then, the SAUperforms the measurement task.

3 Create a GSM VIPanalysis dataimport task

You can choose Maintenance > Task Management on theNastar client to open the Task Management window andthen create a GSM VIP analysis data import task. After thetask is created, the Nastar periodically imports the GSM VIPdata files saved on the Nastar server into the database.

4 Check the integrityof GSM VIPanalysis data

You can double-click System Function > Data Query in theAnalysis Task Management window on the Nastar client toopen the Query Data dialog box and then verify that all therequired GSM VIP analysis data is imported into thedatabase.

5 Create a GSM VIPanalysis task

In the Analysis Task Management window on the Nastarclient, you can create a GSM VIP analysis task. After the taskis created, the Nastar periodically retrieves GSM VIPanalysis data and GSM configuration data from the database,analyzes the retrieved data, and then generates analysisresults.

6 Query GSM VIPanalysis results

You can view the analysis results of the GSM VIP analysistasks that are executed successfully and also performcomprehensive analysis on maps.

12.3 Managing GSM VIP groupsThis section describes how to manage GSM VIP groups. The function of managing GSM VIPgroups enables you to create VIP groups so that you can monitor the service quality of VIPsubscribers in a VIP group, and modify, delete, and export the existing VIP groups.

ContextIMSI refers to the international mobile subscriber identity. The IMSI is a 15-digit string formedby digits 0 to 9. The structure of the IMSI from the left to the right is MCC+MNC+MSIN. TheMNC and the MSIN forms the NMSI.

Where:l MCC refers to the mobile country code of a mobile subscriber.l MNC refers to the mobile network code, namely, the PLMN code of a mobile subscriber.

PLMN refers to the public land mobile network.l MSIN refers to the mobile subscriber identification number.



360

l NMSI refers to the national mobile subscriber identification. This identification canuniquely 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 12-3. The match sequence of columns is restricted andautomatic matching of columns is not supported.

Table 12-3 Example of a VIP group file

VIPGroup

NumberofMembers

Level Creator CreationTime

Description

Group1 50 High admin 2010-05-1008:30:10

Second leveldirector of **Group

Group2 100 Low admin 2010-05-1109:40:50

Projectmanager of **Group

The import and export of VIP group files in .csv, .xls, and .xlsx formats are supported.

NOTE

Generally, obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar.

If telecom operators have high requirements for user information security and the anonymous policy isenabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, andIMEI contained in the analysis data will be encrypted. To protect the security-sensitive user information,the Nastar no longer allows you to enter the plaintext IMSI and MSISDN. In this situation, you need tocontact telecom operators to obtain the encrypted IMSI and MSISDN. Telecom operators can visit http://support.huawei.com and choose Software Center > Controlled Tool(Mini-tool Software) > Core NetworkProduct Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt userinformation.

Procedure

Step 1 Double-click Function List > System Function > VIP Group Management from thenavigation tree in the Analysis Task Management window. The VIP Group Managementdialog box is displayed.

TIP

You can also choose Function List > System Function > VIP Group Management from the navigationtree in the Analysis Task Management window and right-click Open. The VIP Group Managementwindow is displayed.

Step 2 On the GSM VIP tab page, create a VIP group.l Create a VIP group by adding a new VIP group.

1. Click New. The GSM VIP Group Management-Create VIP Group dialog box isdisplayed.

2. Set Group Name, Class, and Description.If the asterisk (*) is present on the right of a parameter, it indicates that the setting ofthis parameter is mandatory.



361

3. In the Members list, you can add, import, export modify, and delete a VIP group.

If... Then...

Create a VIP subscriber a. Click Create. The VIP User Managementdialog box is displayed.

b. Set User Name, Phone, IMSI, andDescription.If the asterisk (*) is present on the right of aparameter, it indicates that the setting of thisparameter is mandatory.For details about parameters, see 12.10.3Parameters for Creating and ModifyingGSM VIP Subscribers/VIP Groups.

c. Click OK.

Import VIP subscriberinformation

Click Import.If an .xls or .xlsx file is imported and the filecontains multiple sheets, a message is displayedfor you to select the sheet to be imported.If file import fails, a message is displayed for youto show the failure cause. You can modify the fileas required and import it again.

Export VIP subscriberinformation

Click Export.The VIP subscriber information is exported asa .csv, .xls, or .xlsx file.NOTE

If an exported file is in the .CSV format, do not edit it inExcel. It is advised that you edit it using WindowsNotepad. Otherwise, the file cannot be importedcorrectly.

Modify VIP subscriberinformation

In the Members list, select one VIP subscriberthen click Modify to set parameters related to theVIP subscriber again. You can modify the username, MS number, and description information,but cannot modify the IMSI.For details about parameters, see 12.10.3Parameters for Creating and Modifying GSMVIP Subscribers/VIP Groups.

Delete a VIP subscriber In the Members list, select one or multiple VIPsubscribers.Click Delete.

4. 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.



362

If an .xls or .xlsx file is imported and the file contains multiple sheets, a message isdisplayed for you to select the sheet to be imported.

NOTE

l If multiple lines of information about Priority and Description for a VIP group areinconsistent in the imported VIP group file, the system imports the last line of informationand displays the information in Priority and Description on the GSM VIP Group tab page.It is recommended that the description and priority information in different lines regardinga VIP group be the same when you define the VIP group information.

l If the Priority column is empty, Medium is displayed by default.

3. Click Modify. The GSM VIP Group Management-Modify VIP Group dialog boxis displayed.

4. You can add, import, export modify, and delete a VIP group, for details, see Table.5. Click OK.

----End

Follow-up ProcedureOn the GSM VIP Group tab page, select the information about a VIP group, and then performthe operations as required.

If... Then...

Modify a VIP group Click Modify to set parameters related to the VIP groupagain.For details about parameters, see 12.10.3 Parametersfor Creating and Modifying GSM VIP Subscribers/VIP Groups.NOTE

If the VIP group is used by other tasks, the modification doesnot affect the ongoing tasks. If the VIP group is used by aperiodic task, the related information is updated in the nextperiod after the modification.

Export a VIP group Click Export.

Delete a VIP group Click Delete.NOTE

If the VIP group is used by other tasks, the modification doesnot affect the ongoing tasks. If the VIP group is used by aperiodic task, the related information is updated in the nextperiod after the modification.

View the information aboutmembers of a VIP group

Double-click a VIP group to view members of the VIPgroup.

Related References12.10.3 Parameters for Creating and Modifying GSM VIP Subscribers/VIP Groups



363

12.4 Obtaining GSM VIP Analysis DataThis section describes how to enable the Nastar to obtain GSM VIP analysis data. You can createan E2E task to enable the Nastar to collect analysis data and create a data import task so that theNastar imports the collected analysis data into the database.

12.4.1 Creating GSM VIP Analysis Data E2E TasksThis section describes how to create a E2E task. After you create an E2E task, the Nastar issuesrule files to the M2000 and then the M2000 sends rule files to the related SAU. The SAU performsthe 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 fromthe SAU to the Nastar.





The following rules apply when users select VIP subscriber groups to create E2E VIP analysistasks under a certain network format:l For summarization analysis, a Nastar server supports a maximum of 30,000 VIP subscribers

selected for all concurrent E2E tasks created under each network format.l For thoroughly analysis, a Nastar server supports a maximum of 2000 VIP subscribers

selected for all concurrent E2E tasks created under each network format.

Procedure







364

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.

Step 4 Click Next.




Step 6 Click Next. In the VIP group list, select one or multiple VIP groups, and then select ReportRaw Data as required.If you select Report Raw Data, it indicates that the Nastar also displays the collected raw calldata when displaying the VIP KPI aggregation information.

Step 7 Click Complete.The added E2E task is displayed in the task list.

----End

Follow-up Procedure

In the task list on the right of the E2E Task Management window, select one analysis data E2Etask to view, delete, refresh, or cancel it.










365

Related References12.10.4 Parameters of GSM VIP Analysis Data E2E Tasks




scheduled task of the same type.

l The data import task can only be executed periodically. The unit of the task execution periodcan be Hours, Days, Weeks, or Months. The data import task of the same type can onlybe created once on the Nastar. After the task is created, the Nastar automatically importsdata at the preset time.




Analysis TaskType



Manual creation



Manual creation



Manual creation



Manual creation



Manual creation



366

Analysis TaskType



Manual creation


- -



Manual creation



Manual creation




Manual creation



Manual creation



Manual creation



Manual creation



Manual creation

UMTS VIPAnalysis


Manual creation


- -



Manual creation



Manual creation



Manual creation



367

Analysis TaskType





Manual creation



Manual creation



Manual creation




Manual creation


- -




Manual creation




Manual creation



Manual creation

CDMA VIPAnalysis


Manual creation



Manual creation


Manual creation



368

Analysis TaskType




Manual creation



Manual creation


- -


- -

Procedure









NOTE




----End




369














12.4.3 Checking the Integrity of VIP Analysis DataThis section describes how to check the integrity of analysis data. Before creating an analysistask, you need to check that the Nastar has imported the required analysis data into the database.


ContextThe 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.



370



Step 5 Select the VIP group to be queried in the VIP group navigation tree.


l The Overview tab page displays NEs with data and the data time range (start time and endtime) 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 thatno 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 taskis normal, but no relevant analysis data is displayed, contact Huawei technical support personnel.

----End

12.5 Setting a Mailbox for Sending Analysis ReportsAfter a mailbox for sending analysis reports is set, the Nastar can send the generated analysisreports to the specified mailboxes through the mailbox.

Prerequisites

You have logged in to the Nastar client.

Procedure

Step 1 Choose Maintenance > E-mail Sending Setting. The Email Sending Setting window isdisplayed.

Step 2 Set the parameters for the mailbox.For details about parameters, see 12.10.7 Parameters for Setting the Mailbox of AnalysisResults.

Step 3 Click OK.

----End

Follow-up ProcedureWhen creating a VIP analysis task, you can select the mailbox that is already set or select anFTP server to send VIP analysis reports.

Related References12.10.7 Parameters for Setting the Mailbox of Analysis Results



371

12.6 Creating GSM VIP Analysis TasksThis section describes how to create GSM VIP analysis tasks. After a GSM VIP analysis taskis created, the Nastar aggregates and analyzes the service call report quantity, traffic, and KPIsof a VIP subscriber or a VIP group. This helps to solve subscriber-level network optimizationproblems so that service quality of VIP subscribers is ensured and VIP subscriber satisfactionis improved.


12.4.3 Checking the Integrity of VIP Analysis Data.


hours, days, or weeks.l A maximum of 50 tasks of this type can be created, and a maximum of data of seven days


Procedure





Step 3 Click Next.

Step 4 Select one or multiple VIP groups.

Step 5 On the VIP KPI 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.


If... Then...

Task Type is set to One-time Set the time range and the start time of thetask.

Task Type is set to Period Set the start time, the period, and the numberof execution times.



372

Step 8 Click Next.

Step 9 Optional: Set relevant parameters on the Sending Analysis Reports Setting tab page to enablethe Nastar to automatically send VIP analysis results to multiple mailboxes through e-mail.l Select Auto-send analysis reports by email.l Set the parameters of Sending Content. The default value is Statistical report.l Set the parameters of Address. Click Add to select the mailboxes for sending the reports.

NOTE

In the Analysis Task Management window, double-click System Function > Auto Distribute UserManagement to set the mailbox for sending VIP analysis results. Alternatively, you can clickCreate to create a new mailbox or click Import to import the information about the existing mailboxesin batches.

l Email Subject and Email Content retain the default values and cannot be modified.


----End









Resume.



Related References12.10.5 Parameters for Creating and Modifying GSM VIP Analysis Tasks



373

12.7 Querying GSM VIP Analysis ResultsThis section describes how to query GSM VIP analysis results. By monitoring the number ofservice call reports, traffic, and KPIs of the selected VIP subscriber, you can learn about thequality of service (QoS) of the VIP subscriber and identify and solve the network problems thatmay cause VIP complaints.

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM VIP analysis task reaches 100%.

Procedure

Step 1 Click the GSM VIP Analysis Task node in the navigation tree in the Analysis TaskManagement window.If you click the Theme Function node, the task list in the right pane displays all analysis tasks.


Step 3 Select an analysis result from the result list on the lower right of the window.If a theme analysis task is executed more than 30 days, only result records of the latest 30 daysare displayed in the analysis result list. For example, the start time of a created VIP analysis taskis September 1, 2010. If the task is executed more than 30 days (if the task execution period is12 hours, the task is executed more than 60 times), the result record on September 1, 2010 willbe deleted and the result records of 30 days from September 2, 2010 to October 1, 2010 arereserved when the task is executed on October 1, 2010.

Step 4 Double-click an analysis result, or right-click an analysis result and choose View AnalysisResult from the shortcut menu. The GSM VIP Analysis Task window is displayed.


Step 5 View the GSM VIP analysis results in the GSM VIP Analysis Task window.

1. Select an object type to be queried on the right of the toolbar, including ALL, Group, orUser.

2. Select a VIP subscriber record or records of a VIP group from the list in the left pane.3. View the detailed information about relevant KPIs and their variation trends in charts on

the CS Service KPI and Active Cell tab pages.For details about the parameters, see 12.10.6 Parameters for Querying GSM VIPAnalysis Results.l The charts that show KPI variation trends can be displayed on the CS Service KPI tab

page only after a VIP subscriber is selected as an analysis object.You can double-click a chart to zoom in and then double-click the chart again to restoreit to the normal size.

l On the Active Cell tab page, query active cell analysis results of the selected VIP groupor VIP subscriber.



374

Click in the upper part of the VIP group overview table, and click in the upperleft of the Nastar client window to open the Network Geographic Observationwindow.– 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 Networksystem_Task name. The added node contains subnode Active Cell and various KPInodes. For details about the KPIs, see Description of Parameters Related to ActiveCell KPIs in 12.10.6 Parameters for Querying GSM 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 oneanalysis result window. Only one theme node is displayed in the navigation treeon the left of the GIS window and corresponds to the VIP analysis results relatedto one network system.

– If the VIP analysis result window that is synchronously displayed with the GISwindow is closed, the theme node corresponding to the VIP analysis task isautomatically deleted from the navigation tree on the left of the GIS window,and the rendering layer corresponding to the VIP analysis results is alsoautomatically deleted from the map area on the right.

– When you open the GIS window initially, active cell nodes and KPI nodes under atheme node are not selected by default. The geographic information can be displayedonly after a node under the theme node is selected.

– After you select the Active Cell node under a theme node in the navigation tree onthe left of the GIS window, all active cells related to the VIP groups or VIPsubscribers involved in the currently selected analysis task are rendered in the maparea 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 GISwindow. Only one active cell can be selected at a time.

– If multiple VIP analysis result windows related to different network systems areopened and the GIS synchronous display function is enabled, multiple renderlayers are automatically loaded in the map on the right after you select active cellnodes or KPI nodes under multiple theme nodes in the navigation tree on the leftof the GIS window. After you clear the check boxes before the nodes, the renderlayers are automatically deleted from the map.

– After you select a KPI node under a theme node in the navigation tree on the left ofthe GIS window, all active cells corresponding to the KPI for the VIP groups or VIPsubscribers involved in the currently selected analysis task are rendered in segmentin the map area on the right.

– The selected KPI corresponds to a layer. You can click to open the LayerManagement dialog box and query the layer information.

– The system collects KPI results corresponding to each cell and dynamicallyseparates these results into N parts (a maximum of five parts) on average to renderthem in different colors. Each KPI result segment is rendered by one color.

Step 6 Start further analysis for one VIP subscriber.If certain KPIs of a VIP subscriber are abnormal according to the query result, further analysisis required. You can select the basic information of the VIP subscriber and then choose Deep



375

Analysis from the shortcut menu, or click button to start the complaint analysis supportfunction for further analysis.

For the description of the related parameters, see 13.7.4 Parameters for Querying GSMComplaint Analysis Support Results.

NOTE

KPIs in GSM VIP analysis results are statistical KPIs. If combined call records related to inter-BSChandovers fail to be analyzed, these call records are not collected for KPI statistics. Call records that arecombined successfully are displayed in the further analysis window. Therefore, the statistical results ofKPI analysis may be inconsistent with the statistical results of further analysis in some scenarios. In normalcases, the number of call records in further analysis is equal to or greater than the number of call recordsin KPI analysis.

----End

Follow-up ProcedureExport query results. You can right-click in the result list and then choose Save As from theshortcut menu to save the current query results as a .csv file.

Related References12.10.6 Parameters for Querying GSM VIP Analysis Results

12.8 Querying GSM VIP Trend Analysis ResultsThe Nastar provides functions for querying the analysis results of GSM VIP trends, such assetting trend analysis parameters, querying trend analysis results, and drilling down throughtrend analysis results. By analyzing the trends based on periodic analysis results, the Nastar helpsnetwork optimization engineers identify the KPI change trends during the monitoring andoptimization VIP KPIs. This implements further problem analysis and location.

Prerequisitesl You have logged in to the Nastar client.l A periodic GSM VIP analysis task is created.

ProcedureStep 1 Choose GSM 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 analysis tasks.

Step 2 Select a record of the period 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 Right-click the selected analysis result from the analysis result list in the lower right pane, andchoose Trend Analysis from the shortcut menu. The Trend Analysis Setting window isdisplayed.If a theme analysis task is executed for more than 30 days, the result records of only the last 30days for the task are displayed in the analysis result list. For example, the start time of a createdVIP analysis task is September 1, 2010. If the task is executed for more than 30 days (if the taskperiod is 12 hours, the task is executed for more than 60 times), the result record on September



376

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 12-5.

Table 12-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 taskare displayed. By default, all VIP groups selected during the creation ofa 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 createdperiodic task, Time dimension is set to Day.

l Continuous period indicates that the KPI trends during a continuousperiod are analyzed. If Time dimension is set to Day or Week, set thestart date and end date. If Time dimension is set to Hour, set the startdate and end date and specify exact hours for the dates.

l Specified period indicates that the KPI trends during multiplecontinuous periods are analyzed.

NOTEThe number of the analysis results in the selected time range can not be more than30.



377

Tab Page Setting Description

Set FilterCriteria

Obtains required subscribers for analysis.For example, if you want to obtain subscribers whose total number ofinitial access requests is greater than 10 and number of abnormal callreleases 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 andNumber 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 accessrequests greater than 10 and the value of Number of abnormal callreleases greater than 2.

6. In the lower part of the Counter tab page, set the And and Orrelationships between the selected KPIs.For example, set the And relationship for Total number of initialaccess 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 GSM 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 informationabout all periodic tasks. Detailed time information and value are displayed after you clicka point in a chart. For details about the trend analysis chart, see 12.10.2 Interface for GSMVIP 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 thespecified 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 withinthe specified period, you can drill down through the detailed analysis results for this KPI duringa certain period using the time drilldown function.

Click Drill Down Results and choose the analysis period to switch to the VIP analysis resultwindow.

----End



378

Follow-up Procedurel Click Export... on the toolbar to export trend analysis reports in .csv format of the following

dimensions: All, VIP group, and VIP subscriber.l Click Trend Analysis Attributes on the toolbar to query the trend analysis attributes.

12.9 Technical Specifications for GSM VIP AnalysisThis section describes the technical specifications for GSM VIP analysis.


Number of subscribers supportedby one analysis task

l For summarization analysis, a Nastar server supportsa maximum of 30,000 VIP subscribers selected for allconcurrent E2E tasks created under each networkformat.

l For thoroughly analysis, a Nastar server supports amaximum of 2000 VIP subscribers selected for allconcurrent E2E tasks created under each networkformat.



Number of VIP groups <= 100

Number of VIP subscribers <= 30,000

Number of VIP subscribers thatreport data sources

<= 2,000


Response time of task execution <= 60 minutes


<= 200


<= 50

12.10 Reference to the GSM VIP Analysis InterfaceThis section describes the interface for GSM VIP analysis and the relevant parameters. Beforeperforming relevant operations, familiarize yourself with the functions of GSM VIP analysis.



379

12.10.1 Interface Description: GSM VIP AnalysisThis section describes the interface for GSM VIP analysis. Before performing relevantoperations, familiarize yourself with the functions of the areas on the interface.

The VIP analysis results are displayed in charts and tables, as shown in Figure 12-2.

Figure 12-2 VIP analysis interface

No. Name Item

(1) Button area Provides the function of exporting the aggregationinformation about VIP groups.

(2) VIP group overview table Displays the aggregation information aboutabnormal KPIs of all the VIP subscribers or VIPgroups involved in the task in a table.



380

No. Name Item

(3) Area for selecting object types Provides options for displaying the aggregationinformation 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 aggregationinformation about abnormal KPIs of all theVIP subscribers in a certain VIP group isdisplayed in Area (2).

l Aggregation based on VIP groupsWhen you select this mode, the aggregationinformation about abnormal KPIs of all theVIP subscribers in all VIP groups is displayedin Area (2).

(4) CS service KPI information table Displays the service KPI values or aggregationvalues in CS domain corresponding to the VIPsubscribers or VIP groups selected in Area (2).

(5) CS service KPI variation trend chart Displays the variation trend of a certain KPI of aVIP subscriber selected in Area (2) when youselect the aggregation of abnormal KPIs based onVIP subscribers in Area (3).

(6) Active cell information table Displays the analysis result of active cellscorresponding to the VIP subscribers or VIPgroups selected in Area (2).

12.10.2 Interface for GSM VIP Trend AnalysisThis section describes the interface for GSM VIP trend analysis. Before performing relevantoperations, familiarize yourself with the functions of the areas on the interface.

VIP trend analysis results are displayed in charts and tables, as shown in Figure 12-3.



381

Figure 12-3 VIP trend analysis interface

SN Item Description

(1) Button area Provides three buttons, which are used to query trend analysisattributes, export raw trend analysis data, and drill downthrough trend analysis results, respectively.



382

SN Item Description

(2) User selectionarea

When All is selected for Filter, the WebUI displays all usersfor which trend analysis is performed in the form of anavigation tree (All > User Group > User), in which:

l Group displays the level information about this user group.l User displays MSISDNs and IMSIs of users.

When Filter is set to other values, the WebUI displays onlyuser information that matches the filter criteria. You can set thefilter criteria according to Table 12-5.

(3) KPI selectionarea

Enables you to select KPIs whose trend analysis results needto be displayed.

(4) Trend analysischart

Displays KPI change trends during each period for the selectedusers.

l User and time dimension information is displayed at the topof 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 informationby time.

(5) Trend analysistable

Displays detailed KPI information during each period for theselected users. The KPI information in this table is displayedsynchronously with the change trend chart.

l User and time dimension information is displayed at the topof the tab page.

l Parameters in the table are period, KPI 1, KPI 2, ..., and KPIN.

12.10.3 Parameters for Creating and Modifying GSM VIPSubscribers/VIP Groups

This section describes the parameters for creating and modifying GSM VIP subscribers and VIPgroups. You can refer to the description when creating and modifying a GSM VIP subscriberand VIP group.



383

Description of Parameters Related to VIP SubscribersParameter Item

User Name Indicates the name of a VIP subscriber.The value range is as follows:l A maximum of 128 charactersl Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `"<>?:l Not nulll Duplicated allowed (a VIP subscriber is allowed to use multiple SIM card)l Case sensitive

MS Number Indicates the number of a UE used bya VIP subscriber.The value range is as follows:l A combination of 0-digit to 20-

digit numerals from 0 to 9l Duplicated allowed

NOTEGenerally, obtain the IMSI and MSISDNof a VIP user and enter them into theNastar.If telecom operators have highrequirements for user informationsecurity and the anonymous policy isenabled on the network where the Nastaris deployed, all user information such asIMSI, MSISDN, and IMEI contained inthe analysis data will be encrypted. Toprotect the security-sensitive userinformation, the Nastar no longer allowsyou to enter the plaintext IMSI andMSISDN. In this situation, you need tocontact telecom operators to obtain theencrypted IMSI and MSISDN. Telecomoperators can visit http://support.huawei.com and chooseSoftware Center > Controlled Tool(Mini-tool Software) > Core NetworkProduct Line > Wireless-OSS >iManager M2000-II > HMACUtil toobtain the tool to encrypt userinformation.

IMSI Indicates the International MobileSubscriber Identity (IMSI) of a VIPsubscriber.Value range: A combination of 15-digit numerals from 0 to 9

Description Indicates the description of the VIP subscriber.The value range is as follows:l A maximum of 250 charactersl Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `"<>?:



384

Description of Parameters Related to VIP GroupsParameter Item

Group Name Indicates the name of a VIP group.The value range is as follows:l A maximum of 128 charactersl Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `"<>?:l Unique and not nulll Case sensitive

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 Indicates the description of the VIP group.The value range is as follows:l A maximum of 250 charactersl Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `"<>?:

Members Indicates the information about members in the VIP group.

Related Tasks12.3 Managing GSM VIP groups

12.10.4 Parameters of GSM VIP Analysis Data E2E TasksThis section describes the parameters for creating GSM E2E tasks. You can refer to thedescription when creating a GSM E2E task.






NE List Indicates the NE object related to the task.It shows the configured NE information on the Nastar by NEList > OSS Name > NE Name.



385

Special ParametersParameter Description

Selected If you select this parameter, the content in the Report RawData field corresponding to the VIP group can be 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 thecollection of the KPI aggregation information of all VIP objectsof the selected VIP groups, thus helping to analyze problemsthoroughly.

Description Indicates the description of the VIP group.

Related Tasks12.4.1 Creating GSM VIP Analysis Data E2E Tasks

12.10.5 Parameters for Creating and Modifying GSM VIP AnalysisTasks

This section describes the parameters for creating and modifying GSM VIP analysis tasks. Youcan refer to the description when creating and modifying a GSM VIP analysis task.








386




One-timetask

TimeRange



Execution Delay


Periodictask

StartTime





Execution Delay








387

VIP InformationParameter Description

Group Name Indicates the name of a VIP group.

Number ofMembers

Indicates the number of members in the VIP group.

Report RawData

Indicates that the raw call data is also collected during the collection of theKPI aggregation information of all VIP objects of the selected VIP groups,thus helping to analyze problems thoroughly.

Last updatetime

l When the IMSI information of the VIP E2E tasks in the running state ischanged, it displayed the time when the IMSI information is changed.

l When the VIP E2E task is new, it displayed NA.

Description Indicates the description of the VIP group.

Type The VIP analysis tasks involve the service type.This field is read-only.

KPI name Indicates the name of a KPI.This field is read-only.


Threshold Indicates the threshold of a KPI.In the analysis report of the corresponding task, if the KPI value of acorresponding user does not reach the threshold, it is considered that this isa problem KPI or deteriorated KPI.This parameter can be null. That is, no threshold is provided.

Email Sending InformationParameter Description

Auto-send analysis reports byemail

After you select this option, the system delivers the VIPanalysis result file to the mailboxes of the specifiedusers.

Sending Content Indicates the report type. The default value is StatisticalReport.

Address Indicates the mailbox to which the file is to be sent.

Subject Indicates the title of an email.Users are not allowed to change the value of thisparameter.



388


Content Indicates the contents of an email.Users are not allowed to change the value of thisparameter.

Related Tasks12.6 Creating GSM VIP Analysis Tasks

12.10.6 Parameters for Querying GSM VIP Analysis ResultsThis section describes the parameters for querying GSM VIP analysis results. You can refer tothe description when querying GSM VIP analysis results.

KPIs in CS domainParameter

Range

Unit

Description

TotalNumberof InitialAccessRequests

[0,+∞)

Number

Indicates the total number of voice call access requests (channelrequests) when obtaining IMSIs.

TotalNumberofSuccessful CallSetups

[0,+∞)

Number

Indicates the total number of successful voice call setups.Subscriber-level successful voice call setups are evaluated by thesubscriber experience, including the following:1. The Connect Acknowledge message or the Disconnect messageis received properly, and a call is terminated by the peer MS.2. The Clear command message is received, and a call is releasedproperly by the network or the local/peer MS.

CallSetupSuccessRate (%)

[0.00,100.00]

% Indicates the voice call setup success rate.Call Setup Success Rate = Total number of successful voice callsetups/Total number of initial voice call access requests x 100%



389

Parameter

Range

Unit

Description


[0,+∞)

Number

Indicates the total number of abnormal voice call releases.A voice call that is set up successfully is regarded as abnormalrelease in one of the following situations:1. The Disconnect message contains abnormal cause (signaling)during call release.2. The Clear command message is received, and the call is releasedabnormally by the network or the local/peer MS.3. An outgoing BSC handover fails.4. An intra-BSC handover fails.5. The BSC releases the call abnormally.6. The MSC releases the call abnormal.

NumberofAbnormal CallRate (%)

[0.00,100.00]

% Indicates the abnormal voice call release rate.Abnormal voice call release rate = Total number of abnormal callreleases after the successful call setup/Total number of voice callsconnected after successuful setup x 100%

AverageOriginated-callAccessDelays(seconds)

N/A Second

Indicates the average access duration for an originated-call.The originated-call access duration refers to the duration fromChannel Request to Assignment Complete during call setup.Average originated-call access duration = Total originated-callaccess duration/Total number of collected originated-call accessdurationsWhere,Access duration for an originated-call = Assignment Completetime - Channel Request time

AverageOriginated-callSetupDelay(seconds)

N/A Second

Indicates the average duration for setting up an originated-call.The originated-call setup duration refers to the duration fromChannel Request to Alerting.Average originated-call setup duration = Total originated-callsetup duration/Total number of collected originated-call setupdurationsWhere,Duration for setting up an originated-call = Alerting time - ChannelRequest time



390

Parameter

Range

Unit

Description

AverageTerminated-callAccessDelays(seconds)

N/A Second

Indicates the average access duration for a terminated-call.The terminated-call access duration refers to the duration fromChannel Request to Assignment Complete during call setup.Average terminated-call access duration = Total terminated-callaccess duration/Total number of collected terminated-call accessdurationsWhere,Access duration for a terminated-call = Assignment Completetime - Channel Request time

AverageTerminated-callSetupDelay(seconds)

N/A Second

Indicates the average duration for setting up a terminated-call.The terminated-call setup duration refers to the duration fromChannel Request to Alerting.Average terminated-call setup duration = Total terminated-callsetup duration/Total number of collected terminated-call setupdurationsWhere,Duration for setting up a terminated-call = Alerting time - ChannelRequest time

AverageDuration(seconds)

[0,+∞)

Second

Indicates the average duration for initiating a voice callsuccessfully.This parameter indicates the average call duration.Duration for a call = Disconnect time - Connect Acknowledge time

Numberof ShortCalls

[0,+∞)

Time

Indicates the number of short voice calls.This parameter specifies call release initiated by subscribers dueto one-way audio, crosstalk, or crank calls.If the actual voice call duration is shorter than the short callthreshold (specified in Service Average Duration during taskcreation, the call is considered as a short call.



391

Parameter

Range

Unit

Description

UplinkOne-WayAudioRate (%)

[0.00,100.00]

% Indicates the proportion of one-way audio on the uplink related tovoice services.Proportion of Uplink one-way audio for voice services = Totalnumber of times Uplink one-way audio/Total number ofsuccessful call setups x 100%This parameter can only show the one-way audio caused by BSSinternal channel (between the BTS and the TC subrack) fault. One-way audio caused by Um interface problems or A interfaceproblems is not contained.The principle for detecting uplink one-way audio is as follows:The DSP on a DPU board of the BSC periodically measures frameerror rate for the TRAU frames transmitted on the uplink. If theframe error rate reaches the threshold, the BSS regards thissituation as primary uplink one-way audio and starts theacknowledgment mechanism. Then, the BSC instructs the BTS tosend a test TRAU frame. If the TC subrack does not receive thetest frame within the specified period, the BSS regards thissituation as uplink one-way audio.

Downlink One-WayAudioRate (%)

[0.00,100.00]

% Indicates the proportion of one-way audio on the downlink relatedto voice services.Proportion of Downlink one-way audio for voice services = Totalnumber of times Downlink one-way audio/Total number ofsuccessful call setups x 100%This parameter can only show the one-way audio caused by BSSinternal channel (between the BTS and the TC subrack) fault. One-way audio caused by Um interface problems or A interfaceproblems is not contained.The principle for detecting downlink one-way audio is as follows:The DSP on a DTRU board of the BTS periodically measuresframe error rate for the TRAU frames transmitted on the downlink.If the frame error rate reaches the threshold, the BSS regards thissituation as primary uplink one-way audio and starts theacknowledgment mechanism. Then, the BSC instructs the TCsubrack to send a test TRAU frame to the BTS. If the BTS doesnot receive the test frame within the specified period, the BSSregards this situation as downlink one-way audio.

Uplink/Downlink noAudioRate (%)

[0.00,100.00]

% Indicates the proportion of no audio on both the uplink anddownlink related to voice services.Proportion of Uplink/Downlink no audio for voice services =Number of times Uplink no audio and Downlink no audio for voiceservices/Total number of successful call setups x 100%



392

Parameter

Range

Unit

Description

UplinkCrosstalkRate (%)

[0.00,100.00]

% Indicates the proportion of crosstalk on the uplink related to voiceservices.Proportion of Uplink crosstalk for voice services = Total numberof Uplink crosstalk/Total number of successful call setups x 100%This counter can only show the crosstalk caused by BSS internalchannel (between the BTS and the TC subrack) fault. The crosstalkcaused by the Um interface problem or A interface problem cannotbe detected.The principle for detecting the crosstalk on the uplink is as follows:The DSP on a board of the BTS inserts the unique identificationinto the idle bit in a TRAU frame on the uplink. Then, the DSP ona board in the TC subrack decodes and verifies the consistency ofunique call identification. If the DSP detects the inconsistency ofunique call identification for several consecutive times, the BSSregards this situation as uplink crosstalk.

DownlinkCrosstalkRate (%)

[0.00,100.00]

% Indicates the proportion of crosstalk on the downlink related tovoice services.Proportion of Downlink crosstalk for voice services = Totalnumber of Downlink crosstalk/Total number of successful callsetups x 100%This counter can only show the crosstalk caused by BSS internalchannel (between the BTS and the TC subrack) fault. The crosstalkcaused by the Um interface problem or A interface problem cannotbe detected.The principle for detecting the crosstalk on the downlink is asfollows: The DSP on a board in the TC subrack inserts the uniqueidentification into the idle bit in a TRAU frame on the downlink.Then, the DSP on a board in the BTS decodes and verifies theconsistency of unique call identification. If the DSP detects theinconsistency of unique call identification for several consecutivetimes, the BSS regards this situation as downlink crosstalk.

AverageUplinkHQI

[0.00,100.00]

% Indicates the average uplink High Quality Indicator (HQI) relatedto voice services.HQI reflects the voice quality level, including eight levels from 0to 7. Level 0 indicates the best voice quality.In the CHR for BSC6900 V900R011 and later versions:HQI = Number of MRs containing receive quality from 0 to 3/Number of MRs containing receive quality from 0 to 7 x 100%In the CHR for BSC6000 V900R008:HQI = Number of MRs containing receive quality from 0 to 5/Number of MRs containing receive quality from 0 to 7 x 100%



393

Parameter

Range

Unit

Description

AverageDownlink HQI

[0.00,100.00]

% Indicates the average downlink HQI related to voice services.HQI reflects the voice quality level, including eight levels from 0to 7. Level 0 indicates the best voice quality.In the CHR for BSC6900 V900R011 and later versions:HQI = Number of MRs containing receive quality from 0 to 3/Number of MRs containing receive quality from 0 to 7 x 100%In the CHR for BSC6000 V900R008:HQI = Number of MRs containing receive quality from 0 to 5/Number of MRs containing receive quality from 0 to 7 x 100%

AverageUplinkVQI

[1.00,5.00]

N/A Indicates the average uplink Voice Quality Index (VQI) related tovoice services.VQI is the Mean Opinion Score (MOS) and indicates the qualityof voice calls. The greater the VQI value is, the better the voicecall quality is. Value range: [1, 5]Average Uplink VQI of voice service = Total Uplink VQI/Totalnumber of Uplink VQI tests

Numberof Inter-RATOutgoingHOCommands

[0,+∞)

Number

Indicates the number of times handover from the GSM network toa different network is initiated during voice services. The counterincreased by 1 every time the BSC successfully sends a handovercommand.

NumberofSuccessful Inter-RATOutgoingHOs

[0,+∞)

Number

Indicates the number of successful handovers from the GSMnetwork to a different network during voice services.

Numberof CallDropsDuringInter-RATOutgoingHO

[0,+∞)

Number

Indicates the number of call drops during handovers from the GSMnetwork to a different network in voice services. That is, thenumber of times the MSC clear CMD message is received duringhandovers.



394

Parameter

Range

Unit

Description

Numberof Inter-RATIncomingHOCommands

[0,+∞)

Number

Indicates the number of times handover from a different networkto the GSM network is initiated during voice services.

NumberofSuccessful Inter-RATIncomingHOs

[0,+∞)

Number

Indicates the number of successful handovers from a differentnetwork to the GSM network is initiated during voice services.

Active cell KPIsParameter

Range

Unit

Description

BSCName

N/A N/A Indicates the name of the BSC that an active cell belongs to.

CellName

N/A N/A Indicates the name of an active cell.



395

Parameter

Range

Unit

Description


N/A Indicates the global ID of an active cell.

Numberof CallAccesses

[0,+∞)

Number

Indicates the number of signaling accesses of a VIP group or a VIPsubscriber in an active cell.The method for collecting statistics on this counter is the same asthat on Service Total number of initial access requests.

NumberofAbnormal CallAccesses

[0,+∞)

Number

Indicates the number of abnormal signaling accesses of a VIPgroup or a VIP subscriber in an active cell.Number of abnormal call setup = Number of call accesses -Number of successful call setupsThe method for collecting statistics on this counter is the same asthat on Service Total number of successful call setups.

Numberof CallReleases

[0,+∞)

Number

Indicates the number of signaling releases of a VIP group or a VIPsubscriber in an active cell.The method for collecting statistics on this counter is the same asthat on Service Total number of successful call setups.


[0,+∞)

Number

Indicates the number of abnormal signaling releases of a VIPgroup or a VIP subscriber in an active cell.The method for collecting statistics on this counter is the same asthat on Service Number of Abnormal Call Releases.



396

Related Tasks12.7 Querying GSM VIP Analysis Results

12.10.7 Parameters for Setting the Mailbox of Analysis ResultsThis section describes the parameters for setting the mailbox of analysis results. You can referto this part when you set mailboxes.


SMTP Host Name orAddress

Refers to the address of the sending email server.The address can be either an IP address or a domain name. Forexample, 10.0.0.1 or mail.yourdomain.com.

outgoing email address Refers to the email of the sender.

Authenticate user name andpassword

Indicates that the authentication is required when you log in tothe email server.If you select this option, you need to set User Name andPassword. If you do not select this option, the User Name andPassword are unavailable.

User Name Refers to the user name used to log in to the email sendingserver.

Password Refers to the password used to log in to the email sendingserver.

Related Tasks12.5 Setting a Mailbox for Sending Analysis Reports



397

13 GSM Complaint Analysis Support

About This Chapter

The GSM complaint analysis support function enables you to create complaint analysis supporttasks, query complaint analysis support results, and export complaint analysis support reportsfrom the Nastar. After receiving a subscriber complaint, the Nastar can quickly searches for allcall records of the complaint subscriber in a problem cell based on the known problem cell andInternational Mobile Subscriber Identity (IMSI) of the complaint subscriber, and called numberof 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 complaintproblems. Normally there is no way to avoid that some user data such as International MobileSubscriber Identity (IMSI) will be used during the troubleshooting. However, this functionprovides an anonymous data processing method. You are obligated to take considerablemeasures, in compliance with the laws of the countries concerned and the user privacy policiesof your company, to ensure that the personal data of users is fully protected.

13.1 Basic Knowledge of GSM Complaint Analysis SupportThis section describes the basic knowledge of GSM complaint analysis support, including GSMcomplaint analysis support function and authority policies for GSM complaint analysis support.

13.2 Process of GSM Complaint Analysis SupportThis section describes the process of GSM complaint analysis support.

13.3 Creating GSM Complaint Analysis Support TasksThis section describes how to create GSM complaint analysis support tasks. After receiving aGSM subscriber complaint, you can create a GSM complaint analysis support task on the Nastarto search for the subscriber call records related to the complaints based on the problem cell andinternational mobile subscriber identity (IMSI) of the complaint subscriber. This helps youanalyze and locate problems.

13.4 Querying GSM Complaint Analysis Support ResultsThis section describes how to query GSM complaint analysis support results. Through thisfunction, you can view subscriber call records and detailed information about each record. TheNastar provides information about the MS capability, access and release, and service qualityregarding each call record to assist you in determining the network location where problemsoccur and the possible causes.

13.5 Exporting GSM Complaint Analysis Support Reports

iManager NastarNetwork Optimization User Guide (GSM) 13 GSM Complaint Analysis Support


398

This section describes how to export GSM complaint analysis support reports. You can exportthe queried complaint analysis support results as .xls or .xlsx files as required, which helps indetermining the network location where the problem occurs and the possible causes.

13.6 Technical Specifications for GSM Complaint Analysis SupportThis section describes the technical specifications for GSM complaint analysis support.

13.7 Reference to the GSM Complaint Analysis Support InterfaceThis section describes the interface for GSM complaint analysis support and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM complaint analysis support.



399

13.1 Basic Knowledge of GSM Complaint Analysis SupportThis section describes the basic knowledge of GSM complaint analysis support, including GSMcomplaint analysis support function and authority policies for GSM complaint analysis support.

13.1.1 GSM Complaint Analysis Support FunctionThis section describes how to use the Nastar to perform GSM complaint analysis support basedon call records of GSM subscribers before and after complaints. This helps to locate and solvecomplaint problems.

Complaint Analysis SupportThe 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 ina specified area, assisting in locating and solving problems. The complaint analysis supportconsists 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 ofdetailed information about call reports of complaint subscribers, analysis of procedure beforesignaling release in call reports of complaint subscribers, and analysis of active cells in callreports 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-exception, setup failure, abnormal release, QoSproblem, and other. For details about cause types, see Table 13-1.

Table 13-1 Cause type and related description

Cause Type Description

Non-exception Indicates that the call is normally released.

Setup Failure Indicates that the call fails to be set up.

Abnormal Release Indicates that the call is abnormally releasedbecause of abnormal release of the TCH.

QoS Problem Indicates that the call is normally released andone-way audio, crosstalk occurs or HQI smallerthan 50 during the call process.

Other Indicates that the call is released because ofother exceptions.

l The aggregation and analysis of information about call reports of complaint subscribers

provide an overview of information about all the filtered call reports. The informationincludes the access time, access cell, release time, release cell, IMSI, IMEI, and serviceduration. This function helps network engineers quickly identify abnormal call reports (forexample, too-short-time call reports) and preliminarily learn about the situation ofcomplaint subscribers.

l The analysis of detailed information about call reports of complaint subscribers providesthe detailed information about all the filtered call reports. The information includes the



400

subscriber information, call access information, call release information, and handoverinformation. This function helps network engineers learn the key events that occur duringcalls, service usage, and measurement reports (MRs) before signaling release, accuratelyand quickly assisting in problem location.

l The analysis of procedure before signaling release in call reports of complaint subscribersprovides the detailed procedure before signaling release of all the filtered subscribers. Thisfunction helps network engineers locate problems based on the information before signalingrelease.

LimitationsThe GSM complaint analysis support function requires raw call records of complaint subscribers.The amount of raw data is huge. Therefore, a limitation must be imposed to prevent systemoverload in the case of concurrent operations by a large number of users. Therefore, if IMSI isused to identify complaint subscribers, the maximum number of complaint subscribers selectedin a complaint analysis support task cannot exceed 2,000; if peer MSISDN is used to identifycomplaint subscribers, the maximum number of complaint subscribers selected in a complaintanalysis support task cannot exceed 200.

NOTE

The maximum number of complaint subscribers allowed in a complaint analysis support task is differentwhen 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 IMSIis 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 ofcomplaint 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 whosepeer MSISDN field contains keywords can be obtained. In this manner, the integrity of analysis data isensured, 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 taskwhen the peer MSISDN is used to identify complaint subscribers is smaller than that in the case when IMSIis used to identify complaint subscribers.

13.1.2 Authority Policies for GSM Complaint Analysis SupportThe Nastar provides secure authority management policies to ensure the security of privateinformation for subscribers. The authority management policies enable different types of usersto have different operation rights for the security of their private information.

Introduction to Authority Typesl 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 tothe management domain of a user or a user group, the user or users in the group have theview rights to this security object.For details about how to enable view rights for users, see the description in "Managementdomain of user" in Creating an Nastar User Account.

l Operation rights allow users to perform an operation. If a user has operation rights, the usercan perform a specific operation. Here, operation rights include query rights to complaintanalysis support tasks and operation rights to complaint analysis support tasks.Operation rights are associated with the management domain. A user can perform theoperation corresponding to the operation rights for only the objects in the managementdomain of the user.



401

– Query rights to complaint analysis support tasks: If a Nastar user has the rights, the usercan query the authorized complaint analysis support tasks.

– Operation rights to complaint analysis support tasks: If a Nastar user has the rights, theuser 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 "Operationrights of user" in Creating an Nastar User Account.

Introduction to Authority PoliciesThe 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 createcomplaint analysis support tasks, and query or delete complaint analysis support taskscreated by any user.

l Users not in the administrator group:– To create complaint analysis support tasks, the user in the administrator group or

security administrator group must have operation rights to complaint analysis supporttasks.For details, see Scenario 1 in Table 13-2.

– To query or delete information about complaint analysis support tasks created by theuser in the administrator group or security administrator group, the user does not needother rights.For details, see Scenario 2 in Table 13-2.

– To delete complaint analysis support tasks created by others, the user in theadministrator group or security administrator group must have query rights andoperation rights to complaint analysis support tasks.For details, see Scenario 3 in Table 13-2.

– To query information about complaint analysis support tasks created by the user in theadministrator group or security administrator group, the user must have query rights tocomplaint analysis support tasks.For details, see Scenario 4 in Table 13-2.

NOTE

After a user is assigned permission to query complaint analysis support tasks, the user can queryall complaint analysis support tasks created by any user.

Example of Authority PoliciesAuthority policies vary according to the specific scenario. Table 13-2 describes the authoritypolicies in different scenarios.

NOTE

"User" in Table 13-2 refers to a user in the administrator group or security administrator group.



402

Table 13-2 Example of authority policies


Scenario 1User A needs to create a complaint analysissupport task named X.


2. Assign user A operation rights to complaintanalysis support tasks.In the Select Operation Rights dialog box,add Operation > Nastar PA > GSMComplaint Assistant Analysis to SelectedRights, and click OK. For details, seeCreating an Nastar User Account.

3. Log in to the client as user A.4. Create a complaint analysis support task

named X.For details about how to create complaintanalysis support tasks, see 13.3 CreatingGSM Complaint Analysis Support Tasks.

Scenario 2User A needs to query or delete analysistask X created by user A.

Log in to the client as user A.

Scenario 3User B needs to delete analysis task Xcreated by user A.


2. Assign user B query rights to complaintanalysis support tasks.In the Select Operation Rights dialog box,add Operation > Nastar PA > GSMComplaint Analysis Support Task View toSelected Rights, and click OK. For details,see Creating an Nastar User Account.

3. Assign user B operation rights to complaintanalysis support tasks.In the Select Operation Rights dialog box,add Operation > Nastar PA > GSMComplaint Assistant Analysis to SelectedRights, and click OK. For details, seeCreating an Nastar User Account.

4. Log in to the client as user B.5. Delete analysis task X.

For details about how to delete complaintanalysis support tasks, see Follow-upProcedure in 13.3 Creating GSMComplaint Analysis Support Tasks.



403


Scenario 4User B needs to query analysis task Xcreated by user A.


2. Assign user B query rights to complaintanalysis support tasks.In the Select Operation Rights dialog box,add Operation > Nastar PA > GSMComplaint Analysis Support Task View toSelected Rights, and click OK. For details,see Creating an Nastar User Account.

3. Log in to the client as user B.4. Query analysis results of complaint analysis

support task X.For details about how to query complaintanalysis support results, see 13.4 QueryingGSM Complaint Analysis SupportResults.

13.2 Process of GSM Complaint Analysis SupportThis section describes the process of GSM complaint analysis support.

Figure 13-1 shows the process of GSM complaint analysis support.

NOTE

Required rights must be assigned to users to properly perform complaint analysis support tasks. For detailsabout authority policies, see 13.1.2 Authority Policies for GSM Complaint Analysis Support.

Figure 13-1 Process of GSM complaint analysis support



404


Table 13-3 Description of GSM complaint analysis support process


1 Create a GSMcomplaintanalysissupport task

In the Analysis Task Management window on the Nastar client,you can create a GSM complaint analysis support task. After thetask is created, the Nastar retrieves analysis data related to thecomplaint analysis support from the database, analyzes the data,and then generates analysis results.

2 Query GSMcomplaintanalysissupport results

You can view the analysis results of the complaint analysissupport tasks that are executed successfully and also performcomprehensive analysis on maps.

3 Export GSMcomplaintanalysissupport reports

You can enable the Nastar client to export GSM complaintanalysis support results as report files.

13.3 Creating GSM Complaint Analysis Support TasksThis section describes how to create GSM complaint analysis support tasks. After receiving aGSM subscriber complaint, you can create a GSM complaint analysis support task on the Nastarto search for the subscriber call records related to the complaints based on the problem cell andinternational mobile subscriber identity (IMSI) of the complaint subscriber. This helps youanalyze and locate problems.


l The information about the complaint subscriber is collected.

l The configuration data must be imported before creating the task. If not, the NE selectiontree is none.

NOTE



Contextl A GSM complaint analysis support task can be performed only once.



405

l A maximum of 200 tasks of this type can be created, and a maximum of data of historyseven days can be involved in an analysis task.

l The IMSI file of the complaint subscriber to be imported contains only the IMSI column,as shown in Table 13-4.

Table 13-4 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

Number column, as shown in Table 13-5.

Table 13-5 Example of a GSM complaint subscriber peer number file

Peer Number

015839017891

051385852201

02136039950

Procedure





Step 3 Click Next.

Step 4 In the Analyse Type, GSM Complaint Analysis Type is chosen by default.

NOTEIf you select GSM/UMTS Complaint Analysis Type, you can perform GSM/UMTS complaint analysissupport. For details about how to create a GSM/UMTS complaint analysis support task, see Creating a GSM/UMTS Complaint Analysis Support Task.

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.



406

4. Optional: Click Delete to delete the cells you have chosen.

Step 6 In the Filter Users area, perform the following operations:l Add the calling IMSI to search for the calling MS.

1. Select IMSI.2. Click Add. In the displayed Add User dialog box, enter the IMSI of the subscriber.3. Click OK.

NOTE

l A maximum of 2000 IMSI numbers can be entered.

l You can enter the 15-digit characters (0 to 9 and A to F).

4. Optional: Click Delete to delete the IMSI numbers you have chosen.l Add the peer MSISDN to search for the called MS.

1. Select Peer Number.2. Click Add. In the displayed Add User dialog box, enter the MSISDN of the called MS.3. Click Enter.

NOTEA maximum of 200 called MS numbers can be entered.

4. Optional: Click Delete to delete the called MS numbers you have chosen.l You can also search for the required subscriber by importing the existing subscriber

information.

1. Click Import. The Open dialog box is displayed.2. Select the edited IMSI file of a complaint subscriber or an MSISDN file of the called

subscriber, and then click Open.3. Perform the operations as prompted.

If... Then...

The imported information is correctand no identical records exist

In the displayed dialog box, click OK.

The imported information is correctand identical records exist

In the displayed OK dialog box, click Yes toimport the new records that will overwriteidentical records.

Abnormal records exist in theimported information

Current files cannot be imported and theNastar displays a message, indicating thenumber of abnormal records.l Click Export Check Result to export

check results from the Nastar so that youcan make modifications based on theerror information to complete the currentimport 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.



407


----End









Resume.



Related References13.7.3 Parameters for Creating and Modifying GSM Complaint Analysis Support Tasks

13.4 Querying GSM Complaint Analysis Support ResultsThis section describes how to query GSM complaint analysis support results. Through thisfunction, you can view subscriber call records and detailed information about each record. TheNastar provides information about the MS capability, access and release, and service qualityregarding each call record to assist you in determining the network location where problemsoccur and the possible causes.


l The progress bar of the GSM complaint analysis support task reaches 100%.



408

Procedure

Step 1 Click the GSM Complaint Analysis Support Task node in the navigation tree in the AnalysisTask Management window.If you click the Theme Function node, the task list in the right pane displays all the analysistasks.

Step 2 Select a GSM complaint analysis support task from the task list on the upper right of the AnalysisTask Management window.The analysis results of the selected task are displayed in the lower right pane.


Step 4 Right-click the result and choose View Analysis Result from the shortcut menu. The GSMComplaint Analysis Support Task window is displayed.You can also double-click the result to open the GSM Complaint Analysis Support Taskwindow.


Step 5 In the navigation tree on the left of the GSM Complaint Analysis Support Task window, selecta 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 callrecords 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 recordsof 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 quicklysearch for and locate the required call record.

For detailed description of cause types, see 13.1.1 GSM Complaint Analysis SupportFunction.

Step 6 On the Overview tab page, query the overview information about the filtered call records andselect 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 13.7.4 Parameters for QueryingGSM Complaint Analysis Support Results.

l indicates that the call record in this line is abnormal.

l indicates the cause type of this call in the navigation tree is Other and the exceptionstatus is unknown.

l 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 occursduring a call, the Nastar combines the records related to one call and displays a combinedCHR in the overview table. You can double-click a combined CHR to open the CHR list tabpage corresponding to the combined CHR and query detailed information. The tab page isnamed IMSI***_Serial number, where *** refers to the IMSI number.



409

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 thedetails of all the filtered call records. The details include information about the subscriber, callaccess or call release, and handover.

Step 8 On the Signaling Procedure Before Call Release tab page, query the detailed signalingprocedure before call release for the selected call record.l Signaling information table: contains 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 signalinginformation is displayed in a navigation tree, which contains the meanings of fieldsrepresented by specific bytes. In addition, the Nastar automatically parses the enumeratedvalues or variant values represented by fields in a message according to protocols.

For details about the signaling procedure chart, see Description of the Signaling ProcedureBefore Call Release Tab Page.

NOTE

The integrality of the displayed signaling procedures depends on the signaling procedure informationrecorded by the NEs before call release.

Step 9 On the Measurement Information tab page, query the detailed measurement informationbefore 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, see Description of the MeasurementInformation Tab Page.

Step 10 Optional: Query the complaint analysis support results on the GIS window.

Click in the upper part of the VIP group overview table, and click in the upper left ofthe Nastar client window to open the Display the Nastar Network based on longitude andlatitude 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_Taskname. 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 oneanalysis result window. Only one theme node is displayed in the navigation tree on theleft of the GIS window and corresponds to the complaint analysis support results relatedto one network system.

– If a combined complaint analysis support result windows is displayed as one networksystem, the GIS window can display information of the combined analysis result windowunder the node of the network system.



410

– If the complaint analysis support result window that is synchronously displayed with theGIS window is closed, the theme node corresponding to the complaint analysis supporttask is automatically deleted from the navigation tree on the left of the GIS window, andthe rendering layer corresponding to the complaint analysis support results is alsoautomatically deleted from the map area on the right.

l When you open the GIS window initially, the access and release cells of all the call recordsare 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 therelated node.

– If cells whose engineering parameters are not imported exist, a message is displayed onthe right of the window.

----End

Follow-up ProcedureExport query results. You can right-click in the result list and then choose Save As from theshortcut menu to save the current query results as a .xml, .txt, .xls, or .xlsx file.

Related References13.7.4 Parameters for Querying GSM Complaint Analysis Support Results

13.5 Exporting GSM Complaint Analysis Support ReportsThis section describes how to export GSM complaint analysis support reports. You can exportthe queried complaint analysis support results as .xls or .xlsx files as required, which helps indetermining the network location where the problem occurs and the possible causes.

Prerequisitesl You have logged in to the Nastar client.l You have queried the GSM complaint analysis support reports. For details, see 13.4

Querying GSM Complaint Analysis Support Results.

Procedurel Export a complaint analysis support overview report.

NOTE

An exported complaint analysis support overview report contains the following three result files inthe default .xlsx format:

l Statistical result file obtained by the aggregation mode IMSI-Cause type in the overviewnavigation 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 overviewnavigation tree. The file naming convention is Overview tree_Cause type-IMSI.xlsx.

l Aggregation result file for complaint analysis support summary in the overview table. The filenaming convention is Overview table_Summary.xlsx.

1. Click in the GSM Complaint Analysis Support window. The Save dialog boxis displayed.



411

2. Set the folder and specify the save path and file type. Then, click Save.

l Export a complaint analysis support data report.

1. In the GSM Complaint Analysis Support window, click . The Save dialog boxis displayed.

2. Set the folder and specify the save path and file type. Then, click Save.An exported data report contains overview table information, subscriber information,call access information, call release information, and handover information.

You can also right-click the complaint analysis support overview table and then chooseExport complaint analysis support data report from the shortcut menu to export acomplaint analysis support data report.

----End

13.6 Technical Specifications for GSM Complaint AnalysisSupport

This section describes the technical specifications for GSM complaint analysis support.


Number of subscribers supportedby one analysis task

<= 2,000



Time range of analysis data <= Past 7 days



<= 200


<= 200

13.7 Reference to the GSM Complaint Analysis SupportInterface

This section describes the interface for GSM complaint analysis support and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM complaint analysis support.



412

13.7.1 Interface Description: GSM Complaint Analysis SupportThis section describes the interface for GSM complaint analysis support. Before performingrelevant operations, familiarize yourself with the functions of the areas on the interface.

The complaint analysis support results are displayed in charts and tables, as shown in Figure13-2.

Figure 13-2 Complaint analysis support interface


(1) Button area Two buttons are provided to export complaint analysis supportoverview report and complaint analysis support data report.

(2) Navigation tree ofthe call report causetype overview ofcomplaintsubscribers

The navigation tree of the call report cause type overview ofcomplaint subscribers provides two display modes, namely,Cause type-IMSI and IMSI-Cause type.

(3) Call report overviewtable

Provides options for displaying the information of all thefiltered call reports in Area (2). The information includesaccess time, access cell, release time, release cell, IMSI, IMEI,service duration and link establishment type.



413


(4) Signaling procedurebefore call releasetable\Measurementinformation beforecall release table

Allows users to query the detailed signaling procedure andmeasurement information before call release of all thesubscribers that are filtered out.

For details, see Description of the Signaling ProcedureBefore Call Release Tab Page and Description of theMeasurement Information Tab Page.

(5) Tables related tosubscribers,signaling access/release, andhandover

Provide options for displaying the detailed information of allthe filtered call reports in Area (2).

13.7.2 Interface for Signaling Procedure Before Call Release andMeasurement Information in the GSM Complaint AnalysisSupport Window

This section describes the function of each area on the Signaling Procedure Before CallRelease and Measurement Information tab pages in the GSM complaint analysis supportwindow.

Description of the Signaling Procedure Before Call Release Tab PageThe signaling procedure before call release is displayed in charts and tables, as shown in Figure13-3.



414

Figure 13-3 Signaling Procedure Before Call Release

SN Item Description

(1) Signalinginformationtable

Contains signaling information transmitted between NEs during acall, including the signaling time, signaling direction, signaling type,and contents. Information in this table is displayed synchronouslywith the signaling procedure chart.



415

SN Item Description

(2) Signalingprocedurechart

Shows the signaling interaction between NEs during a call. This chartis displayed synchronously with the information in the signalinginformation table.

l The signaling time is displayed on the left of the chart. The timeformat is HH:MM:SS.Tick, where Tick is the unit of the time. 1Tick equals to 10 ms.

l NEs are displayed at the top of the chart. Um interface is acommunication interface between the MS and the BTS. Abisinterface is a communication interface between the BTS and theBSC. A interface is a communication interface between the BSCand the MSC.

l Characters on the chart refer to the signaling number and name.Solid lines refer to the standard signaling, dashed lines refer tothe non-standard signaling, and arrows indicate the signalingdirection.

You can refer to the standard signaling specifications to know thedetailed signaling information.

Description of the Measurement Information Tab PageThis tab page contains a detailed measurement report table and a KPI change trend chart, asshown in Figure 13-4.

Figure 13-4 Measurement Information tab page



416

SN Item Description

(1) Detailedmeasurementreport table

Contains detailed information about measurement reports (MRs)before call release, including the measurement time, measurementobject, measurement object type, BCCH, BSIC, and KPIs.

(2) KPI changetrend chart

Shows the change trends of TA, DLRxLevel, DLRxQuality/Level,ULRxQuality/Level, and MS/BTS Power.

Each trend chart consists of the following four parts from left to right:l Titlel Y-axis, displaying only the maximum value and minimum valuel KPI change trend chart, displaying the change trends of KPIs in

a maximum of 20 MRsl Legend

Table 13-6 describes the change trend of each KPI.

Table 13-6 Description of KPI change trend

KPI Usage Description

TA Helps identify abnormal releasescaused by poor coverage.

Displayed as a bar chart. The valueranges from 0 to 63.

DLRxLevel Displayed as a broken line graph. Thevalue ranges from -47 to -110.

DLRxQuality/Level

Helps identify abnormal releasescaused by uplink or downlinkinterference.

RxQuality: displayed as a bar chart.The value ranges from 0 to 7.RxLevel: displayed as a broken linegraph. The value ranges from -47 to-110.

ULRxQuality/Level

RxQuality: displayed as a bar chart.The value ranges from 0 to 7.RxLevel: displayed as a broken linegraph. The value ranges from -47 to-110.

MS/BTSPower

Helps identify abnormal releasescaused by unbalanced uplink anddownlink by analyzing this KPI withDLRxQuality/Level andULRxQuality/Level.

BTS Power: displayed as a bar chart.The value ranges from 0 to 15. MSPower: displayed as a broken linegraph. The value ranges from 0 to 30.



417

13.7.3 Parameters for Creating and Modifying GSM ComplaintAnalysis Support Tasks

This section describes the parameters for creating and modifying GSM complaint analysissupport tasks. You can refer to this description when creating and modifying a GSM complaintanalysis task.

Task Common Information






Task Time Information




Parameter Setting Information


Filter NEs Choose the NEs to be analyzed.

Filter User The filtering condition can be IMSI or Peer Number.



418

Related Tasks13.3 Creating GSM Complaint Analysis Support Tasks

13.7.4 Parameters for Querying GSM Complaint Analysis SupportResults

This section describes the parameters for querying GSM complaint analysis support results. Youcan refer to the description when querying GSM complaint analysis support results.

Call Report Overview TableNOTE



Parameter

Range

Unit

Description

SerialNumber

(0,2^31-1)

N/A Indicates the serial number of a CHR in the call report overviewtable. Serial number is a keyword of a call record. It is an internalidentification in the Nastar and can uniquely identify a call record.

Combined

N/A N/A Indicates whether a CHR is combined.The Nastar supports the combination of inter-BSC CHRs. If ayellow icon is displayed in this column, the CHR is combined.

Abnormal

N/A N/A Indicates whether a call record is abnormal.If a red excalmatory mark icon is displayed in this column, the callrecord is abnormal.If a yellow interrogation mark icon is displayed in this column, thecause type of this call in the navigation tree is Other and theexception status is unknown.



419

Parameter

Range

Unit

Description

Abnormal Cause

N/A N/A Indicates the abnormal cause in the Channel Request message.Call setup failure:1. Um interface quality problem/MS fault2. System resource congestion3. Transmission fault4. CN fault5. Other causesAbnormal call release:1. Call drop due to HO failure2. Call drop due to high TA3. Call drop due to poor UL level on TCH4. Call drop due to UL interference on TCH5. Call drop due to poor UL quality on TCH6. Call drop due to sudden UL level decrease7. Call drop due to poor DL level on TCH8. Call drop due to DL interference on TCH9. Call drop due to poor DL quality on TCH10. Call drop due to sudden DL level decrease11. Call drop due to poor UL/DL level on TCH12. Call drop due to UL/DL interference on TCH13. Call drop due to poor UL/DL quality on TCH14. Call drop due to other Um interface problems15. Call drop due to transmission fault16. Call drop due to CN fault17. Peer call drop18. Call drop due to other causesService quality problems:1. Poor quality of Um interface1. UL one-way audio2. DL one-way audio3. Mute call4. UL crosstalk5. DL crosstalk

Network GSM

N/A Indicates the network that generates the call records.



420

Parameter

Range

Unit

Description

AccessCause

N/A N/A Indicates the signaling access type.Access types are as follows:Originated-non-SMS (AC_ORIGIN_CALL_NO_SMS)Originated SMS (AC_ORIGIN_CALL_SMS)Terminated-call (AC_ANSWER_TO_PAGING)Call reestablishment (AC_CALL_RE_ESTABLISH)Emergency call (AC_EMERGENCY_CALL)Location update (AC_LOCATION_UPDATE)IMSI detach (AC_IMSI_DETACH)Packet service (AC_PACKET_CALL)LMU service (AC_LMU_ESTABLISH)SS service (AC_SS_ESTABLISH)VGCS service (AC_VGCS_ESTABLISH)VBS service (AC_VBCS_ESTABLISH)LCS service (AC_LCS_ESTABLISH)Other services (AC_RESERVED)Incoming BSC handover (AC_IN_BSC_HO)Notification response (AC_NOTIFICATION_RSP)Immediate setup (AC_IMM_SET_UP)RR initialization (AC_RR_INITIALISATION_REQ)Talker indication (AC_TALKER_INDICATION)VGCS access (AC_VGCS_VBS_VPCS)Terminated-non-SMS (AC_ANSWER_TO_PAGING_CALL)Terminated-SMS (AC_ANSWER_TO_PAGING_SMS)Normal location update (AC_LOCATION_UPDATE_NOR-MAL)Periodical location update (AC_LOCATION_UPDATE_PERI-ODIC)IMSI attach (AC_LOCATION_UPDATE_ATTACH)

AccessTime

N/A N/A Indicates the signaling access time during a call, that is, the timewhen the Channel Request message is received.

AccessCell

N/A N/A Indicates the name of the cell at the time of signaling access.The format for displaying an access cell is as follows: BSC name:cell name (BSC OPC: cell ID). The BSC name and cell name canbe obtained from configuration data. If the BSC name and cellname cannot be queried, they are not displayed.BSC OPC refers to the source signaling point configured for theBSC.



421

Parameter

Range

Unit

Description

ReleaseTime

N/A N/A Indicates the signaling release time during a call.

ReleaseCell

N/A N/A Indicates the name of the cell at the time of signaling release.The format for displaying a release cell is as follows: BSC name:cell name (BSC OPC: cell ID). The BSC name and cell name canbe obtained from configuration data. If the BSC name and cellname cannot be queried, they are not displayed.

IMSI 000000000000000-999999999999999

N/A Indicates the identity number of the international mobilesubscriber.IMSI is an abbreviation for International Mobile SubscriberIdentity.

IMEI 000000000000000-999999999999999

N/A Indicates the international mobile station equipment identity.IMEI is an abbreviation for International Mobile EquipmentIdentity.

PeerMSISDN

N/A N/A Indicates the mobile phone number of the peer subscriber.

Duration [0,+∞)

Second

Indicates the service duration, including call duration andsignaling duration.Service duration = Release time - Access time

ServiceDuration

[0,+∞)

Second

Indicates the call duration.Call duration = Time for receiving DisConnect - Time forreceiving Connect Acknowledge



422

Parameter

Range

Unit

Description

CallSetupResult

N/A N/A Indicates the call setup result, including normal setup andabnormal setup.Display rule: Call Setup Result/Cause of abnormal call setup/Subcause of abnormal call setup (These parameters are displayedin the Call Release area in the right pane.)1. Normal: The Connect ACK message is received, and an MSenter the normal call phase.2. The Disconnect message is received, and the call is terminatedby the peer MS.3. The call is released by the source BSC during an outgoing BSChandover.Abnormal call setup:1. Abnormal release before connection2. Rejected by the CN3. TCH assignment failure4. Abnormal call release by a signaling channel5. Abnormal call release by a TCH6. Setup indication timeout7. Immediate assignment rejected8. BSC release9. MSC release10. Authentication rejected11. Authentication failure12. Cipher Mode rejected13. Incoming BSC handover failure

CallReleaseResult

N/A N/A Indicates the call release result, including normal release andabnormal release.Normal call termination:1. Normal: The DisConnect message is received. A call enters thenormal release phase.2. The Clear command message is received, and a call is releasedproperly by the network or the local/peer MS.3. An outgoing BSC handover or an inter-RAT handover issuccessful.Abnormal call termination-Abnormal call termination by TCHs1. Outgoing BSC handover failure2. Intra-BSC handover failure3. BSC release4. MSC release



423

SubscribersParameter

Range

Unit

Description

IMSI 000000000000000-999999999999999

N/A Indicates the international mobile subscriber identity.

IMEI 000000000000000-999999999999999

N/A Indicates the international mobile station equipment identity.

PeerMSISDN

N/A N/A Indicates the mobile phone number of the peer subscriber.

Call AccessParameter

Range

Unit

Description

AccessTime

N/A N/A Indicates the signaling access time during a call, that is, the timewhen the Channel Request message is received.

AccessTA

[0,63]

N/A Indicates the TA value during the signaling access.

AccessCell

N/A N/A Indicates the name of the cell at the time of signaling access.The format for displaying an access cell is as follows: BSC name:cell name (BSC OPC: cell ID). The BSC name and cell name canbe obtained from configuration data. If the BSC name and cellname cannot be queried, they are not displayed.BSC OPC refers to the source signaling point configured for theBSC.

AccessCarrier

[0,71]

N/A Indicates the TRX number during signaling access.



424

Parameter

Range

Unit

Description

Accesschannel

[0,7] N/A Indicates the channel number during signaling access.

Accesscause

N/A N/A Indicates the cause in the signaling access request message.This value is the same as Access Type in the overview table.

CallSetupResult

N/A N/A Indicates the call setup result.This value is the same as the first-level cause in Call Setup Resultin the overview table.

Cause ofabnormalcall setup

N/A N/A Indicates the cause of abnormal signaling access.This value is the same as the second-level cause for exceptions inCall Setup Result in the overview table.

Subcauseofabnormalcall setup

N/A N/A Indicates the detailed cause of abnormal signaling access.This value is the same as the third-level cause for exceptions inCall Setup Result in the overview table.

Call ReleaseParameter

Range

Unit

Description

ReleaseTime

N/A N/A Indicates the signaling release time, that is the time when theChannel Release message is received.

ReleaseCell

N/A N/A Indicates the name of the cell at the time of signaling release.The format for displaying a release cell is as follows: BSC name:cell name (BSC OPC: cell ID). The BSC name and cell name canbe obtained from configuration data. If the BSC name and cellname cannot be queried, they are not displayed.BSC OPC refers to the source signaling point configured for theBSC.

ReleaseCarrier

[0,71]

N/A Indicates the TRX number during signaling release.

CallReleaseResult

N/A N/A Indicates the call release result.This value is the same as the first-level cause in Call Release Resultin the overview table.

Cause ofabnormalcallcompletion

N/A N/A Indicates the cause of abnormal signaling release.This value is the same as the second-level cause for exceptions inCall Release Result in the overview table.



425

Parameter

Range

Unit

Description

Subcauseofabnormalcallcompletion

N/A N/A Indicates the detailed cause of abnormal signaling release.This value is the same as the third-level cause for exceptions inCall Release Result in the overview table.

UL one-wayaudioduring acall

Yes,No

N/A Indicates whether the uplink one-way audio occurs during a call.This parameter can only show the one-way audio caused by BSSinternal channel (between the BTS and the TC subrack) fault. One-way audio caused by Um interface problems or A interfaceproblems is not contained.The principle for detecting uplink one-way audio is as follows:The DSP on a DPU board of the BSC periodically measures frameerror rate for the TRAU frames transmitted on the uplink. If theframe error rate reaches the threshold, the BSS regards thissituation as primary uplink one-way audio and starts theacknowledgment mechanism. Then, the BSC instructs the BTS tosend a test TRAU frame. If the TC subrack does not receive thetest frame within the specified period, the BSS regards thissituation as uplink one-way audio.

DL one-wayaudioduring acall

Yes,No

N/A Indicates whether the downlink one-way audio occurs during acall.This parameter can only show the one-way audio caused by BSSinternal channel (between the BTS and the TC subrack) fault. One-way audio caused by Um interface problems or A interfaceproblems is not contained.The principle for detecting downlink one-way audio is as follows:The DSP on a DTRU board of the BTS periodically measuresframe error rate for the TRAU frames transmitted on the downlink.If the frame error rate reaches the threshold, the BSS regards thissituation as primary uplink one-way audio and starts theacknowledgment mechanism. Then, the BSC instructs the TCsubrack to send a test TRAU frame to the BTS. If the BTS doesnot receive the test frame within the specified period, the BSSregards this situation as downlink one-way audio.



426

Parameter

Range

Unit

Description

UL callcrosstalk

Yes,No

N/A Indicates whether the uplink call crosstalk occurs during a call.This counter can only show the crosstalk caused by BSS internalchannel (between the BTS and the TC subrack) fault. The crosstalkcaused by the Um interface problem or A interface problem cannotbe detected.The principle for detecting the crosstalk on the uplink is as follows:The DSP on a board in the BTS inserts the unique identificationinto the idle bit in a TRAU frame on the uplink. Then, the DSP ona board in the TC subrack decodes and verifies the consistency ofunique call identification. If the DSP detects the inconsistency ofunique call identification for several consecutive times, the BSSregards this situation as uplink crosstalk.

DL callcrosstalk

Yes,No

N/A Indicates whether the downlink call crosstalk occurs during a call.This parameter can only show the one-way audio caused by BSSinternal channel (between the BTS and the TC subrack) fault.Crosstalk caused by Um interface problems or A interfaceproblems is not contained.The principle for detecting the crosstalk on the downlink is asfollows: The DSP on a board in the TC subrack inserts the uniqueidentification into the idle bit in a TRAU frame on the downlink.Then, the DSP on a board in the BTS decodes and verifies theconsistency of unique call identification. If the DSP detects theinconsistency of unique call identification for several consecutivetimes, the BSS regards this situation as downlink crosstalk.

UL callHQI

[0.00,100.00]

% Indicates the average uplink HQI related to voice services.HQI reflects the voice quality level, including eight levels from 0to 7. Level 0 indicates the best voice quality.In the CHR for BSC6900 V900R011 and later versions:HQI = Number of MRs containing receive quality from 0 to 3/Number of MRs containing receive quality from 0 to 7 x 100%In the CHR for BSC6000 V900R008:HQI = Number of MRs containing receive quality from 0 to 5/Number of MRs containing receive quality from 0 to 7 x 100%

DL callHQI

[0.00,100.00]

% Indicates the average downlink HQI related to voice services.HQI reflects the voice quality level, including eight levels from 0to 7. Level 0 indicates the best voice quality.In the CHR for BSC6900 V900R011 and later versions:HQI = Number of MRs containing receive quality from 0 to 3/Number of MRs containing receive quality from 0 to 7 x 100%In the CHR for BSC6000 V900R008:HQI = Number of MRs containing receive quality from 0 to 5/Number of MRs containing receive quality from 0 to 7 x 100%



427

Parameter

Range

Unit

Description

UL callVQI

[1.00,5.00]

N/A Indicates whether the uplink voice quality indicator occurs duringa call.VQI is the Mean Opinion Score (MOS) and indicates the qualityof voice calls. The greater the VQI value is, the better the voicecall quality is. Value range: [1, 5]Average UL VQI of voice service = Total UL VQI/Total numberof UL VQI tests

DL callVQI

[1.00,5.00]

N/A Indicates whether the downlink voice quality indicator occursduring a call.VQI is the Mean Opinion Score (MOS) and indicates the qualityof voice calls. The greater the VQI value is, the better the voicecall quality is. Value range: [1, 5]Average UL VQI of voice service = Total UL VQI/Total numberof UL VQI tests

HandoverParameter

Range

Unit

Description

Numberofhandoverrecords

[0,20]

Number

Indicates the number of handovers during a call.

Handoverinitiatingtime

N/A N/A Indicates the time when a handover is initiated, that is, the timecorresponding to Handover CMD.

HOinitiationcause

N/A Indicates the cause of initiating a handover.

Handover sourcecell

N/A N/A Indicates the name of the source cell where the handover isinitiated.The format for displaying a cell is as follows: BSC name: cell name(BSC OPC: cell ID). The BSC name and cell name can be obtainedfrom configuration data. If the BSC name and cell name cannot bequeried, they are not displayed.BSC OPC refers to the source signaling point configured for theBSC.



428

Parameter

Range

Unit

Description

Handover targetcell

N/A N/A Indicates the name of the target cell where the handover is initiated.The format for displaying a cell is as follows: BSC name: cell name(BSC OPC: cell ID). The BSC name and cell name can be obtainedfrom configuration data. If the BSC name and cell name cannot bequeried, they are not displayed.BSC OPC refers to the source signaling point configured for theBSC.

Handover result

N/A N/A Indicates whether a handover is successful and indicates the causeif the handover fails.Handover success: NormalHandover failure cause: Return to the original channel after thehandover failure; BSC release; MSC exception

Related Tasks13.4 Querying GSM Complaint Analysis Support Results



429

14 GSM Cell Performance Analysis

About This Chapter

The GSM cell performance analysis function enables you to obtain GSM cell performanceanalysis data, create GSM cell performance analysis tasks, query GSM cell performance analysisresults, and export GSM cell performance analysis reports from the Nastar. By providing calldata of abnormal users in problem cells, the Nastar assists you in analyzing the root cause ofabnormal calls. This helps to provide better services and improve user satisfaction. This functioncan be used to quickly locate and resolve problems. Normally there is no way to avoid that someuser data such as International Mobile Subscriber Identity (IMSI) will be used during thetroubleshooting. However, this function provides an anonymous data processing method. Youare obligated to take considerable measures, in compliance with the laws of the countriesconcerned and the user privacy policies of your company, to ensure that the personal data ofusers is fully protected.

ContextNOTE

The GSM cell performance analysis function cannot analyze data of the BSC6000 V900R008.

14.1 Basic Knowledge of GSM Cell Performance AnalysisThis section describes the basic knowledge of the GSM cell performance analysis function,which facilitates identification of problem cells and enables the Nastar to retrieve the data ofabnormal calls in problem cells. In this manner, the Nastar assists in identifying the causes ofproblem cells, hence facilitating in-depth problem analysis.

14.2 Process of GSM Cell Performance AnalysisThis section describes the process of GSM cell performance analysis.

14.3 Obtaining GSM Cell Performance Analysis DataThis section describes how to enable the Nastar to obtain GSM cell performance analysis data.You can create an E2E task to enable the Nastar to collect analysis data and create a data importtask so that the Nastar imports the collected analysis data into the database.

14.4 Creating GSM Cell Performance Analysis TasksThis section describes how to create GSM cell performance analysis tasks. After you create aGSM 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.

iManager NastarNetwork Optimization User Guide (GSM) 14 GSM Cell Performance Analysis


430

14.5 Querying GSM Cell Performance Analysis ResultsThis section describes how to query GSM cell performance analysis results. After the analysisof abnormal call records of problem cells, the Nastar displays analysis results includingexception causes and bottom subscribers in an analysis report, helping you locate and solveproblems related to cell performance.

14.6 Exporting GSM Cell Performance Analysis ReportsThis section describes how to export GSM cell performance analysis reports. You can exportthe queried cell performance analysis results as .xls or .xlsx files, which helps in locating problemcells in networks.

14.7 Technical Specifications for GSM Cell Performance AnalysisThis section describes the technical specifications for GSM cell performance analysis.

14.8 Reference to the GSM Cell Performance Analysis InterfaceThis section describes the interface for GSM cell performance analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM cell performance analysis.



431

14.1 Basic Knowledge of GSM Cell Performance AnalysisThis section describes the basic knowledge of the GSM cell performance analysis function,which facilitates identification of problem cells and enables the Nastar to retrieve the data ofabnormal calls in problem cells. In this manner, the Nastar assists in identifying the causes ofproblem cells, hence facilitating in-depth problem analysis.

Generally, the whole-to-partial analysis method is used during network optimization orperformance analysis. That is, the Nastar locates and analyzes network problems by monitoringperformance 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, theNastar performs in-depth analysis on the bottom problem cells.

At present, the Nastar can perform cell-level analysis for performance data. The Nastar canprovide detailed and in-depth analysis on problem cells.

The functions provided by the Nastar are as follows:l The Nastar analyzes abnormal call records based on BSCs or NE groups and provides

bottom causes of problem cells. This helps network engineers to identify the detailed causesof the exception, hence improving work efficiency.

l After the main exceptions of problem cells are identified, the Nastar provides users withan in-depth understanding of bottom users with poor KPIs by providing the function ofanalyzing bottom problem users in cells. This function helps network engineers to locatebottom users of an exception type in problem cells. In this manner, network engineers cansolve the problems of bottom users, hence improving cell performance.

l If problem cells are not identified, the Nastar performs exception analysis of a large numberof 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.

NOTE

The statistical result of the cell performance analysis function that the Nastar provides is different from theperformance measurement statistics.

l The Nastar's statistical result is based on user experience, while the performance measurement resultis based on network device performance data. The results are different because they are measureddifferently.

l The cell performance analysis function that the Nastar provides enables in-depth analysis of poor-quality cells, while products such as the M2000 and PRS collect network KPI statistics and help youdetect poor-quality cells.

14.2 Process of GSM Cell Performance AnalysisThis section describes the process of GSM cell performance analysis.

Figure 14-1 shows the process of GSM cell performance analysis.



432

Figure 14-1 Process of GSM cell performance analysis operations


Table 14-1 Description on process of GSM cell performance analysis operations


1 Create a GSM cellperformanceanalysis data E2Etask

You need to choose Maintenance > E2E TaskManagement on the Nastar client to open the E2E TaskManagement window and then create a E2E task. After youcreate the task, the Nastar issues rule files to the M2000, andthen the M2000 sends the rule files to the related SAU. Then,the SAU performs the measurement task.



433


2 Create a GSM cellperformance dataimport task

You need to choose Maintenance > Task Management onthe Nastar client to open the Task Management window andthen create a GSM cell performance data import task. Afterthe task is created, the Nastar periodically imports the GSMperformance data files saved on the Nastar server to thedatabase.

3 Check the integrityof GSM cellperformanceanalysis data

You can double-click System Function > Data Query in theAnalysis Task Management window on the Nastar client toopen the Query Data dialog box and then check whether allthe required GSM cell performance analysis data is importedinto the database.

4 Create a GSM cellperformanceanalysis task

In the Analysis Task Management window on the Nastarclient, you can create a GSM cell performance analysis task.After you create the task, the Nastar retrieves the GSM cellperformance analysis data and GSM configuration data fromthe database, analyzes the retrieved data, and then generatesthe analysis results.

5 Query GSM cellperformanceanalysis results

After a GSM cell performance analysis task is executedsuccessfully, you can view the analysis results.

6 Export GSM cellperformanceanalysis report

You can export GSM cell performance analysis reportsthrough the Nastar client.

14.3 Obtaining GSM Cell Performance Analysis DataThis section describes how to enable the Nastar to obtain GSM cell performance analysis data.You can create an E2E task to enable the Nastar to collect analysis data and create a data importtask so that the Nastar imports the collected analysis data into the database.

14.3.1 Creating GSM Cell Performance Data Analysis E2E TasksThis section describes how to create a E2E task. After you create an E2E task, the Nastar issuesrule files to the M2000 and then the M2000 sends rule files to the related SAU. The SAU performsthe 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 fromthe SAU to the Nastar.



Configuration Data.



434


Context


Procedure







Step 4 Click Next.


CAUTIONYou must consider the time zone difference between the Nastar and the SAU when setting thetask execution range. For example: The Nastar delivers an E2E task to be executed from 04:00to 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 Nastarserver after 06:00 in the local time on the Nastar server. Therefore, the Nastar completes E2Etasks 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.


Step 6 Click Next.


----End



435









Related References14.8.2 Parameters for GSM Cell Performance Analysis Data E2E Tasks










436


Analysis TaskType



Manual creation



Manual creation



Manual creation



Manual creation



Manual creation


Manual creation


- -



Manual creation



Manual creation




Manual creation



Manual creation



Manual creation



437

Analysis TaskType




Manual creation



Manual creation

UMTS VIPAnalysis


Manual creation


- -



Manual creation



Manual creation



Manual creation




Manual creation



Manual creation



Manual creation




Manual creation


- -



438

Analysis TaskType





Manual creation




Manual creation



Manual creation

CDMA VIPAnalysis


Manual creation



Manual creation


Manual creation



Manual creation



Manual creation


- -


- -

Procedure




For details about how to set Task Type, see Table 14-2.



439




NOTE




----End


















440


































441


































442





-

Procedure


TIP







----End

14.4 Creating GSM Cell Performance Analysis TasksThis section describes how to create GSM cell performance analysis tasks. After you create aGSM 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.


l Analysis data and configuration data are imported into the Nastar database. For details, see14.3.3 Checking the Integrity of Analysis Data.

Contextl An analysis task can be performed only once.

l A maximum of 50 tasks of this type can be created, and a maximum of data of seven dayscan be involved in an analysis task.



443

Procedure





Step 3 Click Next.




Step 5 Click Next.




If... Then...











444

If... Then...



----End









Resume.



Related References14.8.3 Parameters for Creating or Modifying GSM Cell Performance Analysis Tasks

14.5 Querying GSM Cell Performance Analysis ResultsThis section describes how to query GSM cell performance analysis results. After the analysisof abnormal call records of problem cells, the Nastar displays analysis results includingexception causes and bottom subscribers in an analysis report, helping you locate and solveproblems related to cell performance.



445

Prerequisitesl You have logged in to the Nastar client.l The progress bar of the GSM cell performance analysis task has reached 100%.

Procedure

Step 1 Click the Theme Function > GSM Cell Performance Analysis Task node in the navigationtree in the Analysis Task Management window.If you choose Theme Function, the task list on the right displays all the analysis tasks.

Step 2 Select a GSM cell performance analysis task from the task list on the upper right of the AnalysisTask Management window.The analysis results of the selected task are displayed in the lower right pane.


Step 4 Right-click the analysis result, and then choose View Analysis Result from the shortcut menu.The GSM Cell Performance Analysis Task window is displayed.You can also double-click the selected analysis result to open the GSM Cell PerformanceAnalysis Task window.


Step 5 View the GSM cell performance analysis results in the GSM Cell Performance AnalysisTask 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 to search for andlocate the cell.

2. The areas on the right and in the middle of the window show counter overview informationabout the selected cell and ranking of counters.

You can click any line in the list and then press Ctrl+F to search for and locate an object.

l A table in the middle area of the window displays the number of records of eachexception type in a cell and the percentage of an exception type to all exception types.A pie chart in the lower area of the window displays the percentage of each exceptiontype.Currently, the Nastar performs cell performance analysis on only the exception typesrelated to voice services. The exception types related to voice services are classifiedinto call setup failure, abnormal call release, and service quality problem.If you choose an NE object node from the navigation tree in the left pane, the defaultvalue of Service Type is Voice service and the default value of Exception Type isAll in the upper area of the exception distribution chart. The exception distribution chartdisplays the proportion of each exception type related to voice services. You can alsoselect Call setup failure, Abnormal call release, or Qos problem from the ExceptionType drop-down list box to display distribution charts of detailed exception types byexception type.

l In the area on the right, the bottom subscribers identified by IMSIs, bottom cells andbottom Trxs are illustrated in tables. The tables show the IMSIs(or Cell Names orTRXIDs), the number of exception records and the percentage of each exception type.



446

By default, the system displays 10 records. The default number can be modified.

NOTE

Bottom Exceptional Cells in the Show drop-down list is valid only when the overview node orNE node in the object navigation tree is selected. Bottom Exceptional Trxs in the Show drop-down list is valid only when a cell 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 theshortcut menu to perform the corresponding operation, such as modifying the attributesof the chart, and resizing, saving, and printing the chart.

Step 6 Start further analysis for one exception type.

l Select a cell or a BSC node in the navigation tree in the left pane, and right-click StartFurther Analysis. Then, the system will display all the exception records of the selected cellor the selected BSC.

l In the middle area, choose an exception type and click . Then, the system willdisplay 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, a cell or a Trx and click . Then, thesystem will display all the exception records of the selected subscriber or the selected cell ofthe exception type.

NOTE


----End


Related References14.8.4 Parameters for Querying GSM Cell Performance Analysis Results

14.6 Exporting GSM Cell Performance Analysis ReportsThis section describes how to export GSM cell performance analysis reports. You can exportthe queried cell performance analysis results as .xls or .xlsx files, which helps in locating problemcells in networks.


l You have queried the GSM cell performance analysis reports. For details, see 14.5Querying GSM Cell Performance Analysis Results.



447

Procedure

Step 1 Click in the GSM Cell Performance Analysis Task window. The Save dialog box isdisplayed.

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

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 therunning task is executed completely or canceled.




l The exported analysis results are classified into analysis results of bottomN exceptionsubscribers obtained from cell performance analysis and exception overview results obtainedfrom cell performance analysis. These types of analysis results are contained in two filesseparately.

----End

14.7 Technical Specifications for GSM Cell PerformanceAnalysis

This section describes the technical specifications for GSM cell performance analysis.



<= 2,048 cells






<= 200


<= 50



448

14.8 Reference to the GSM Cell Performance AnalysisInterface

This section describes the interface for GSM cell performance analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM cell performance analysis.

14.8.1 Interface Description: GSM Cell Performance AnalysisThis section describes the GSM cell performance analysis. Before performing relevantoperations, 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 14-2.

Figure 14-2 Interface of GSM cell performance analysis


(1) Button area Aggregation information about cell exceptionanalysis results can be exported.

(2) Search panel You can precisely locate a cell object through thesearch condition.



449


(3) Cell object navigation tree Cell objects whose analysis results are to bedisplayed can be searched through the navigationtree.

The navigation tree node is named in the format ofNE object name (Number of exceptionrecords). In this case, the exceptional records ofeach NE are displayed intuitively.

(4) List of exception types of cells Exception types, number of exception records, andproportion of each exception type are displayed intables.

(5) Pie chart of exception types of cells Causes and proportions of each type of exceptionsare displayed in pie charts.

(6) List of bottom cells Bottom cells and bottom users or bottom Trxs ofselected cell objects as well as number of exceptionrecords are displayed in tables.

14.8.2 Parameters for GSM Cell Performance Analysis Data E2ETasks

This section describes the parameters for creating GSM E2E tasks. You can refer to thedescription when creating a GSM E2E task.









450

Special ParameterParameter Description

Service Type Indicates service types of the cell performance analysis. It onlyincludes the voice service.

Exception Type Indicates exception type of the voice service.

KPI Indicates the name of the KPIs.


Threshold Indicates the threshold of a KPI.In the analysis report of the corresponding task, if the KPI value ofa corresponding user does not reach the threshold, it is consideredthat this is a problem KPI or deteriorated KPI.

Related Tasks14.3.1 Creating GSM Cell Performance Data Analysis E2E Tasks

14.8.3 Parameters for Creating or Modifying GSM Cell PerformanceAnalysis Tasks

This section describes the parameters for creating or modifying GSM cell performance analysistasks. You can refer to the description when creating or modifying a GSM cell performanceanalysis task.








451





ExecutionDelay





Related Tasks14.4 Creating GSM Cell Performance Analysis Tasks

14.8.4 Parameters for Querying GSM Cell Performance AnalysisResults

This section describes the parameters for querying GSM cell performance analysis results. Youcan refer to the description when querying GSM cell performance analysis results.

Exception type overview tableParameter

Range Unit

Description

ServiceType

Voice services N/A

Indicates the type of an abnormal service.GSM cell performance analysis supports only theanalysis of CS voice services.



452

Parameter

Range Unit

Description

Exception Type

Call setup failureAbnormal callreleaseService qualityproblem

N/A

Indicates the exception type.1. A call setup fails in the following situation: TheConnect Acknowledge message is not received duringa voice call, and the call setup process is not terminatedby subscribers or the network (for example, the call isterminated by a subscriber or is rejected by the peernetwork during call setup).2. A call is released abnormally in the followingsituation: A call is set up successfully and is connected(that is, the Connect Acknowledge message isreceived), but the call is released without receiving theDisconnect or Handover succeeded message.3. The principle for determining service qualityproblems is as follows: A call is set up successfully andis connected (that is, the Connect Acknowledgemessage is received), and the call is released properly(that is, the Disconnect or Handover succeededmessage is received). However, the call is releasedabnormally due to voice quality problems such as poorUm interface quality, one-way audio, or crosstalk.



453

Parameter

Range Unit

Description

DetailedException Type

Call setupfailure:Um interfacequality problem/MS fault SystemresourcecongestionTransmissionfaultCN faultOther causesAbnormal callrelease:Call drop due toHO failureCall drop due toUm interfaceproblemsCall drop due totransmissionfaultCall drop due toCN faultPeer call dropCall drop due toOther causesService qualityproblem:Poor Uminterface qualityUL one-wayaudioDL one-wayaudioNo audioUL crosstalkDL crosstalk

N/A

Indicates the exception subtypes of various abnormalservice types.

NumberofReports

[0,+∞) Number

Indicates the number of abnormal call records relatedto an exception type.

Ratio(%) [0.00,100.00] % Indicates the proportion of call records related to anexception type to all abnormal call records.



454

Parameter

Range Unit

Description

FurtherAnalysis

N/A N/A

After you click the Further Analysis button, allabnormal call records related to the selected exceptiontype for the current NE object are displayed.

Exception type ranking tableParameter

Range

Unit

Description

Show BottomExceptionUsersBottomExceptioncellsBottomExceptionTrxs

N/A Selects the mode for displaying top abnormal objects.

Quantity [0,50]

Number

Sets the number of top abnormal objects to be displayed.

Ratio(%) [0.00,100.00]

% Indicates the proportion of abnormal call records in an exceptioncell or of an exception user to all abnormal records or of anexception Trx to all abnormal records.

Related Tasks14.5 Querying GSM Cell Performance Analysis Results



455

15 GSM Network Geographic Analysis

About This Chapter

GSM network geographic analysis involves obtaining GSM network geographic analysis data,creating a GSM network geographic analysis task, viewing the GSM network geographicanalysis result. The Nastar displays the relevant information on the map based on the datacollected for the entire network to show the distribution of network coverage, traffic, andabnormal events in an intuitive and comprehensive manner.

15.1 Basic Knowledge of GSM Network Geographic AnalysisThe GSM network geographic analysis function enables the Nastar to locate and display requiredinformation on a map based on measurement report (MR) data, call history record (CHR) data,and property matrix related to mobile subscribers. This function helps operators identify problemareas on the network, reducing drive test costs.

15.2 GSM network geographic Analysis ProcessThis section describes the GSM network geographic analysis process.

15.3 Obtaining GSM Network Geographic Analysis DataThis section describes how to enable the Nastar to obtain GSM network geographic analysisdata. With this function, users can import the property matrix used for network geographiclocalization into the Nastar database, create E2E tasks to collect and analyze data, and createdata import tasks to import the collected analysis data into the database.

15.4 Creating GSM Network Geographic Analysis TasksThis section describes how to create GSM network geographic analysis tasks. After you createand then execute a GSM network geographic analysis task, the Nastar displays requiredinformation such as the distribution of network coverage, traffic, and abnormal events on themap, based on the collected measurement report (MR) and call history record (CHR) data of theselected NE in an intuitive and a comprehensive manner.

15.5 Querying GSM Network Geographic Analysis ResultsThis section describes how to query GSM network geographic analysis results. After you executea GSM network geographic analysis task, the Nastar displays required information on the mapbased on the collected measurement report (MR) and call history record (CHR) data of theselected NE and the property matrix imported into the Nastar database to show the distributionof network coverage, traffic, and abnormal events in an intuitive and comprehensive manner.

15.6 Technical Specifications for GSM Network Geographic ObservationThis section describes the technical specifications for GSM Network Geographic Observation.

iManager NastarNetwork Optimization User Guide (GSM) 15 GSM Network Geographic Analysis


456

15.7 Reference to the GSM Network Geographic Analysis InterfaceThis section describes the interface for GSM network geographic analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM network geographic analysis.



457

15.1 Basic Knowledge of GSM Network GeographicAnalysis

The GSM network geographic analysis function enables the Nastar to locate and display requiredinformation on a map based on measurement report (MR) data, call history record (CHR) data,and property matrix related to mobile subscribers. This function helps operators identify problemareas on the network, reducing drive test costs.

Function DescriptionCompared with the traditional planning software, the Nastar can display and locate data collectedfrom the live network on a map using the GSM network geographic analysis function. Thisfunction enables the Nastar to display the distribution of coverage, traffic, and abnormal eventson the live network comprehensively.

The GSM network geographic analysis function provides the following functions:l Network coverage geographic analysis supports the geographic rendering for the following

indicators: Serving Cell, UL Coverage Strength, DL Coverage Strength, UL Poor QualityLow Level, DL Poor Quality Low Level, UL Interference Area, DL Interference Area,LAC Area, and Area Without Dominant Cell.Compared with the traditional simulation, the network coverage geographic analysisenables the Nastar to display the actual coverage of serving cells, helping operators identifyareas with coverage problems, such as weak coverage.

l Network traffic geographic analysis supports the geographic rendering for the followingindicators: Traffic Distribution of Voice Services and Traffic of bad RxQual area.The network traffic geographic analysis enables the Nastar to display the traffic distributionof each area on a map, helping operators identify heavy-traffic areas.

l Network event geographic analysis supports the geographic rendering for the followingindicators: Number of Service Call Drops and Number of Failed HOs.The event geographic analysis enables the Nastar to display the location where a call setupfails 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 GSM network geographic analysis function provides the following functions:l Identifies areas with heavy traffic to help site deployment.l Evaluates network quality to help quickly identify network problems.

LimitationThe GSM network geographic analysis function enables the Nastar to analyze and collectstatistics on MRs and abnormal calls of all subscribers on a network. A limitation is set for theamount of data to be analyzed. This prevents system overload in the case of heavy traffic or ifthe analysis is performed for a long time. For the DL580 server, the Nastar can collect statisticson and analyze data of not more than 6,000 cells. For the DL980 server, the Nastar can collectstatistics on analyze data of not more than 10,000 cells.

15.2 GSM network geographic Analysis ProcessThis section describes the GSM network geographic analysis process.



458

Figure 15-1 shows the process of the GSM network geographic analysis.

Figure 15-1 Process of GSM network geographic analysis


Table 15-1 Description of GSM network geographic analysis process


1 Import propertymatrix

You can choose Maintenance > Property MatrixManagement on the Nastar client or in the navigation treeon the left of the Analysis Task Management window,double-click System Function > Property MatrixManagement to open the Property Matrix Managementwindow and then import property matrix to the Nastardatabase for network geographic analysis.



459


2 Create a GSMnetworkgeographicanalysis data E2Etask

You can choose Maintenance > E2E Task Managementon the Nastar client to open the E2E Task Managementwindow and then create a E2E task. After you create the task,the Nastar issues rule files to the M2000, and then the M2000sends the rule files to the related SAU. Then, the SAUperforms the measurement task.

3 Create a GSMnetworkgeographicanalysis dataimport task

You can choose Maintenance > Task Management on theNastar client to open the Task Management window andthen create a GSM network geographic observation analysisCHR data import task and a GSM network geographicobservation analysis MR data import task. After the task iscreated, the Nastar periodically imports the GSM networkgeographic observation analysis CHR data and the GSMnetwork geographic observation analysis MR data files savedon the Nastar server into the database.

4 Check the integrityof GSM networkgeographicanalysis data

You can double-click Function List > System Function >Data Query in the Analysis Task Management window onthe Nastar client to open the Query Data dialog box and thenverify that all the required GSM network geographicobservation analysis CHR data and GSM networkgeographic observation analysis MR data are imported intothe database.

5 Create a GSMnetworkgeographicanalysis task

You can create a GSM network geographic analysis task inthe Analysis Task Management window. After the task iscreated, the Nastar periodically retrieves GSM networkgeographic analysis data and GSM configuration data fromthe database, analyzes the retrieved data, and then generatesanalysis results.

6 Query GSMnetworkgeographicanalysis results

After a GSM network geographic analysis task is executedsuccessfully, you can query the analysis results in grids in theNetwork Geographic Observation window, and view thegeographic layers of counters.

15.3 Obtaining GSM Network Geographic Analysis DataThis section describes how to enable the Nastar to obtain GSM network geographic analysisdata. With this function, users can import the property matrix used for network geographiclocalization into the Nastar database, create E2E tasks to collect and analyze data, and createdata import tasks to import the collected analysis data into the database.

15.3.1 Import Property MatrixProperty 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 theactual receive signal level in measurement reports (MRs) to determine the position of eachsubscriber on the map.



460

Prerequisitesl You have logged in to the Nastar client.l The configuration data has been imported into the Nastar database. For details, see 3.3

Importing Configuration Data.l A property matrix file is obtained.

ProcedureStep 1 Choose Maintenance > Property Matrix Management. The Property Matrix

Management window is displayed.TIP

In the navigation tree on the left of the Analysis Task Management window, double-click SystemFunction > Property Matrix Management. Also you can also choose System Function > PropertyMatrix Management from the navigation tree in the Analysis Task Management window and right-clickOpen. The Property Matrix Management window is displayed.

Step 2 Click the *** Property Matrix tab, and then query the property matrix that is already importedor 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 notimported.If the network geographic analysis is required for some NEs but the property matrix of theseNEs is not imported into the Nastar database, import the property matrix and then performthe network 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 tofilter 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 To-Be-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 checkpasses 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 refreshedin the Property Matrix column.

----End



461

15.3.2 Creating GSM Network Geographic Analysis Data E2E TasksThis section describes how to create a E2E task. After you create an E2E task, the Nastar issuesrule files to the M2000 and then the M2000 sends rule files to the related SAU. The SAU performsthe 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 fromthe SAU to the Nastar.





Procedure




Step 3 Set the basic task information.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.

Step 4 Click Next.




462



Step 6 Click Next.

Step 7 Set Traffic of bad RxQual area, Low Receive Quality and Low Level on the Downlink,Low Receive Quality and Low Level on the Uplink, and Definition of No Dominant Cell.


----End













463







Analysis TaskType



Manual creation



Manual creation



Manual creation



Manual creation



Manual creation


Manual creation


- -



Manual creation



Manual creation



464

Analysis TaskType





Manual creation



Manual creation



Manual creation



Manual creation



Manual creation

UMTS VIPAnalysis


Manual creation


- -



Manual creation



Manual creation



Manual creation




Manual creation



Manual creation



465

Analysis TaskType




Manual creation




Manual creation


- -




Manual creation




Manual creation



Manual creation

CDMA VIPAnalysis


Manual creation



Manual creation


Manual creation



Manual creation



Manual creation


- -



466

Analysis TaskType



- -

Procedure





Periodic.



NOTE




----End









467


























468


































469






















-

Procedure


TIP






470




----End

15.4 Creating GSM Network Geographic Analysis TasksThis section describes how to create GSM network geographic analysis tasks. After you createand then execute a GSM network geographic analysis task, the Nastar displays requiredinformation such as the distribution of network coverage, traffic, and abnormal events on themap, based on the collected measurement report (MR) and call history record (CHR) data of theselected NE in an intuitive and a comprehensive manner.

Prerequisitesl You have logged in to the Nastar client.l GSM network geographic observation CHR analysis data, GSM network geographic

observation MR analysis data, GSM configuration data, engineering parameters, andproperty matrix are imported into the Nastar database. For details, see 15.3.4 Checkingthe Integrity of Analysis Data.


days.l A maximum of 10 tasks of this type can be created, and a maximum of data of seven days


Procedure





Step 3 Click Next.




Step 5 Click Next.



471


If... Then...





If... Then...











----End




472








Resume.



Related References15.7.3 Parameters for Creating and Modifying GSM Network Geographic Analysis Tasks

15.5 Querying GSM Network Geographic Analysis ResultsThis section describes how to query GSM network geographic analysis results. After you executea GSM network geographic analysis task, the Nastar displays required information on the mapbased on the collected measurement report (MR) and call history record (CHR) data of theselected NE and the property matrix imported into the Nastar database to show the distributionof network coverage, traffic, and abnormal events in an intuitive and comprehensive manner.

Prerequisitesl You have logged in to the Nastar client.l You are authorized to use the Geographic Information System (GIS).l The required engineering parameters are imported into the Nastar.l The progress of the GSM network geographic analysis task has reached 100%.l The required map file is obtained.

Procedure

Step 1 Choose Theme Function > GSM network geographic Observation Analysis Task from thenavigation tree on the left of the Analysis Task Management window.If you choose Theme Function, the right task list displays all analysis tasks.



473

Step 2 Select a GSM network geographic analysis task from the task list in the upper right of theAnalysis 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 TaskManagement window.

Step 4 Right-click the analysis result and choose Network Geographic Observation from the shortcutmenu. The Network Geographic Observation window is displayed.You can also double-click the selected analysis result to open the Network GeographicObservation window.

NOTE

Only the analysis result whose Result Status is Successful can be queried.

Step 5 Query the GSM network geographic analysis result in the Network GeographicObservation window.

1. Optional: Click to import the map file.For details, see 3.7.1 Importing a Map.

2. Click to load site information.For details, see 3.7.3 Loading Site Information.

3. In the left navigation tree, choose the network geographic analysis node.

The geographic data of the selected theme analysis is displayed synchronously on the maplocated on the right of the window.

4. Select a geographic analysis theme node, and right-click Display to open the Display -*** dialog box.In the displayed dialog box, set information about illustration and NEs. *** indicates thename of the theme node.

On the NE tab page, you can click any node in the navigation tree and then press Ctrl+Fto search for and locate the required object.

NOTE

When querying the Traffic of Bad RxQual Area, you can set the proportion of traffic with poorquality to analyse the traffic volume with poor quality.

5. Optional: In the button area in the upper left of the window, click to open the LayerManagement dialog box and set map layers.

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 theright of the layer list to adjust the map layer overlap sequence. You can also determinewhether a map layer is displayed or not and set the transparency of the map layer to bedisplayed 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 toset the legends and NEs to be displayed on the map layer.



474

6. In the geographic display area in the middle of the window, view abnormal events and therelevant theme information on the map in grid view mode.

l Select a grid to view detailed information in the detailed information display area onthe right of the window.

TIP

l When you select Traffic Distribution of Voice Services or Traffic of Bad RxQual Areaunder the Geographic Network Traffic node, the top 3 cells with the heaviest traffic in thecurrent grid are displayed.

l When you select Traffic Distribution of Voice Services under the Geographic NetworkTraffic node, the busy hours in the current grid are displayed.

l In the button area on the upper left of the window, perform the following operations, asshown in Table 15-4.

Table 15-4 Functions of buttons

Button Description

Enables you to open the legend to view the counter value rangecorresponding to a color.You can also set the legend in the Layer Management dialogbox.

or Enables you to switch between Select Tool and Hand Tool.

Enables the Nastar to measure the distance.For details, see 3.7.7 Measuring Distance on the Map.

or Enables you to zoom in or zoom out on the map.For details, see 3.7.6 Moving/Zooming In On/Zooming OutOn/Refreshing/Fully Displaying a Map.

Enables the Nastar to display the map in full screen.For details, see 3.7.6 Moving/Zooming In On/Zooming OutOn/Refreshing/Fully Displaying a Map.

Enables the Nastar to refresh the map.For details, see 3.7.6 Moving/Zooming In On/Zooming OutOn/Refreshing/Fully Displaying a Map.

Enables the Nastar to save a map.For details, see 3.7.8 Saving the Map Display Effect.

and Enables the Nastar to filter cells.For details, see 3.7.4 Filtering Cells.

Enables the Nastar to search for cells.For details, see 3.7.5 Searching Cells.

----End



475

Related References15.7.4 Parameters for Querying GSM Network Geographic Analysis Results

15.6 Technical Specifications for GSM Network GeographicObservation

This section describes the technical specifications for GSM Network Geographic Observation.



l <= 6,000 carriers (HP580)l <= 12,000 carriers (HP785)






<= 200


<= 10

15.7 Reference to the GSM Network Geographic AnalysisInterface

This section describes the interface for GSM network geographic analysis and the relevantparameters. Before performing relevant operations, familiarize yourself with the functions ofGSM network geographic analysis.

15.7.1 Interface Description: GSM Network Geographic AnalysisThis section describes the window for GSM network geographic analysis. Before performingoperations, you need to understand the functions of the areas in the window.

The results of network geographic analysis are displayed in grids, as shown in Figure 15-2.



476

Figure 15-2 Window for network geographic analysis

SN Name Description

1 Navigation tree forgeographic analysis themes

In the navigation tree, you can select a themenode for geographic analysis. Thecorresponding geographic data about thistheme is displayed in area 3.

2 Button area You can search and locate cell objects by keyword.

3 Area for displayinggeographic analysis results

You can view the results of related themes ingrids.

After selecting a grid, you can view detailedinformation about this grid such as the sitename, longitude, and latitude in area 4.

4 Area for displayingdetailed information

You can view detailed information about theselected grid.

15.7.2 Parameters for Creating GSM Network Geographic AnalysisData E2E Tasks

This section describes the parameters for creating GSM network geographic analysis data E2Etasks. You can refer to the description when creating a GSM network geographic analysis dataE2E task.



477







Special ParameterParameter Description

Downlink Receive Quality>= X

Indicates the threshold for determining poor coverage qualityon the downlink.The Nastar obtains only the data with the downlink receivequality level greater than or equal to X.X is the level of downlink receive quality. Value range: aninteger from 0 to 7. Default value: 6.

Downlink Receive Quality>= X And DownlinkReceive Level (dBm) <= Y

Indicates the threshold for determining poor coverage qualityand low coverage signal strength on the downlink.The Nastar obtains only the data with the downlink receivequality level greater than or equal to X and with the downlinkreceive level smaller than or equal to Y.X is the level of downlink receive quality. Value range: aninteger from 0 to 7. Default value: 6.Y is the downlink receive level. Value range: –110.0 to 0.0.Default value: –95.

Uplink Receive Quality >=X And Uplink ReceiveLevel (dBm) <= Y

Indicates the threshold for determining poor coverage qualityand low coverage signal strength on the uplink.The Nastar obtains only the data with the uplink receive qualitylevel greater than or equal to X and with the uplink receive levelsmaller than or equal to Y.X is the level of uplink receive quality. Value range: an integerfrom 0 to 7. Default value: 6.Y is the uplink receive level. Value range: –110.0 to 0.0. Defaultvalue: –95.



478


Absolute DownlinkReceive Level Differencebetween the Serving Celland a Neighboring Cell(dB) < X And Number ofNeighboring Cells MeetingCriteria >= Y

Determines no dominant cell.If the absolute value of the downlink receive level differencebetween the serving cell is smaller than X and with the numberof neighboring cells meeting criteria greater than or equal toY, the serving cell is considered as no dominant cell.The Value range of X: an integer from 1 to 20. Default value:5.The Value range of Y: an integer from 1 to 6. Default value: 2.

15.7.3 Parameters for Creating and Modifying GSM NetworkGeographic Analysis Tasks

This section describes the parameters for creating and modifying GSM network geographicanalysis tasks. You can refer to the description when creating or modifying a GSM networkgeographic analysis task.











479


One-timetask

TimeRange



Execution Delay


Periodictask

StartTime





Execution Delay






Busy timesetting

All Day The data generated in the whole day will be analyzed.

BusyHour

Only the data generated in the selected period of one day will beanalyzed.



480




Related Tasks15.4 Creating GSM Network Geographic Analysis Tasks

15.7.4 Parameters for Querying GSM Network GeographicAnalysis Results

This section describes the parameters for querying GSM network geographic analysis results.You can refer to the description when querying GSM network geographic analysis results.

Network Coverage Geographic ObservationParameter

Range

Unit

Description

ServingCell

N/A N/A The traffic map is rendered according to the cells that serve asprimary serving cells most frequently in MRs in the raster view.If some cells serve as primary serving cells for the same numberof times, the traffic map is rendered according to the primaryserving cell in the MR last reported.

ULCoverageStrength

N/A dBm

The traffic map is rendered according to the average uplink receivesignal strength in MRs in the raster view.

DLCoverageStrength

N/A dBm

The traffic map is rendered according to the average downlinkreceive signal strength in MRs in the raster view.

UL PoorQualityLowLevel

N/A % The traffic map is rendered according to the percentage of the MRswith poor uplink quality (quality level higher than a specifiedthreshold, default value is 6) and low uplink level (receive signalstrength lower than a specified threshold, default value is -95 dBm)to the total number of MRs in the raster view.

DL PoorQualityLowLevel

N/A % The traffic map is rendered according to the percentage of the MRswith poor downlink quality (quality level higher than a specifiedthreshold, default value is 6) and low downlink level (receivesignal strength lower than a specified threshold, default value is-95 dBm) to the total number of MRs in the raster view.



481

Parameter

Range

Unit

Description

ULInterference Area

N/A % The traffic map is rendered according to the percentage of theuplink interference MRs to the total number of MRs in the rasterview.

DLInterference Area

N/A % The traffic map is rendered according to the percentage of thedownlink interference MRs to the total number of MRs in the rasterview.

LACArea

N/A % The traffic map is rendered according to the percentage of the MRscontaining serving cells corresponding to the LAC occurring mostfrequently to the total number of MRs in the raster view.

AreaWithoutDominant Cell

N/A % The traffic map is rendered according to the percentage of the MRscontaining no dominant cell to the total number of MRs in theraster view.If the number of neighboring cells with not more than 5 dB signallevel difference for the serving cell is equal to or greater than aspecified threshold (default value, 2), this area is considered as anarea without a dominant cell.

Geographic Network Traffic

Parameter

Range

Unit

Description

TrafficDistribution ofVoiceServices

N/A Number

The traffic map is rendered according to the traffic volume (unit:number of MRs) of voice services (default service, AMR) in theraster view.

Traffic ofBadRxQualArea

N/A Number

If the percentage of the MRs containing voice services whosequality level is lower than a specified threshold (default value, 6)to the total number of MRs in the raster view is higher than aspecified threshold (default value, 10%), the traffic map isrendered according to the traffic volume (unit: number of MRs) ofvoice services with poor signal quality in the raster view.

NOTEYou can modify these default values when creating a GSM Network Geographic Analysis Data E2E Task,and Open the Network Geographic Observation Window for completed tasks, choose GeographicNetwork Traffic > Traffic of Bad RxQual Area and double-click. Modify the default percentage valuewhich mentioned above on the Parameter tab page in the Display - Traffic of Bad RxQual Area dialogbox.



482

Network Event DistributionParameter

Range

Unit

Description

NumberofServiceCallDrops

N/A Number

The traffic map is rendered according to the number of call dropsin the raster view.

Numberof FailedHOs

N/A Number

The traffic map is rendered according to the number of failedhandovers in the raster view.

Related Tasks15.5 Querying GSM Network Geographic Analysis Results



483

Documents

iManager Nastar Network Optimization User Guide (GSM)(V600R009_06)(PDF)-En