Nastar Operator Guide

Nastar V600R008
Operator Guide
Issue Date 03 2010-06-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 03 (2010-06-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Nastar Operator Guide
About This Document
About This Document

Intended Audience
The intended audiences of this document are:
l l
Network planning and optimization engineers Operation and maintenance (OM) engineers
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Changes in Issue 03 (2010-06-30)

This is the third release.

This is the second release.

This is the initial release.
Issue 03 (2010-06-30)
iii
Contents
Contents
About This Document...................................................................................................................iii 1 Overview of the Nastar Performance Analysis System......................................................1-1
1.1 Introduction to the Nastar Performance Analysis System...............................................................................1-2 1.2 Position of the Nastar on the network.............................................................................................................1-7 1.3 Performance Analysis Process........................................................................................................................1-8
2 Getting Started............................................................................................................................2-1
2.1 Logging In to the Nastar..................................................................................................................................2-3 2.1.1 Login Modes..........................................................................................................................................2-3 2.1.2 Login Process.........................................................................................................................................2-4 2.2 Changing the Password of the Current User...................................................................................................2-6 2.3 Customizing the Client GUI Effect.................................................................................................................2-6 2.3.1 Setting the Font Size..............................................................................................................................2-6 2.3.2 Setting the Information Output Area......................................................................................................2-7 2.3.3 Setting the Number Format of the Client...............................................................................................2-8 2.3.4 Setting the Time and Date Formats of the Client...................................................................................2-9 2.3.5 Setting the Toolbar...............................................................................................................................2-10 2.4 Locking the Client.........................................................................................................................................2-11 2.5 Unlocking the Client.....................................................................................................................................2-12 2.6 Broadcast Messages......................................................................................................................................2-13 2.6.1 Setting Broadcast Parameters...............................................................................................................2-13 2.6.2 Sending Broadcast Messages...............................................................................................................2-13 2.7 Displaying the Current Window in Full Screen Mode..................................................................................2-14 2.8 Setting the Alarm Sound at Network Disconnection....................................................................................2-14 2.9 Checking Whether the Client Needs Upgrade..............................................................................................2-15 2.10 Setting the Interval of Client Upgrade Check.............................................................................................2-15 2.11 Managing the Nastar License......................................................................................................................2-16 2.11.1 Querying the Nastar License..............................................................................................................2-16 2.11.2 Updating the Nastar License..............................................................................................................2-16 2.12 Engineering Parameter Management..........................................................................................................2-17 2.12.1 Importing/Exporting Engineering Parameters...................................................................................2-17 2.12.2 Querying Engineering Parameters.....................................................................................................2-19 2.13 Creating Custom NE Groups.......................................................................................................................2-20 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Contents
2.14 Querying NE Data.......................................................................................................................................2-23 2.15 Reference for the Performance Analysis System GUI................................................................................2-24 2.15.1 Interface Description: Nastar Client...................................................................................................2-24 2.15.2 Nastar Menu Functions Reference.....................................................................................................2-26 2.15.3 Keyboard Shortcuts............................................................................................................................2-29 2.15.4 Parameters for Creating or Modifying the Server Information..........................................................2-31 2.15.5 Parameters for Setting the Output GUI..............................................................................................2-32 2.15.6 Parameters for Setting the Time and Date Formats...........................................................................2-33 2.15.7 Parameters for Querying the Nastar License .....................................................................................2-35 2.15.8 Parameters for Setting Broadcast Parameters....................................................................................2-36 2.15.9 Parameters for Printing.......................................................................................................................2-36 2.15.10 Parameters for Importing and Exporting Engineering Parameters..................................................2-38 2.15.11 Parameters for Creating and Modifying Custom NE Groups..........................................................2-43 2.16 FAQs about the Client Operations..............................................................................................................2-43 2.16.1 How Can I View the Complete Text?................................................................................................2-44 2.16.2 The Left Mouse Button Not Respond................................................................................................2-44 2.16.3 The Help Window Not Respond........................................................................................................2-44 2.16.4 Some Records Not Selected When I Select Multiple Records...........................................................2-45 2.16.5 The Nastar Client Cannot Read the File to Be Printed......................................................................2-45 2.16.6 Menu Items Gray and Unavailable.....................................................................................................2-45
3 Monitoring the Nastar Server..................................................................................................3-1

3.1 Setting the Monitoring Parameters..................................................................................................................3-2 3.1.1 Setting the Parameters for the Nastar Server Monitoring...................................................................... 3-2 3.1.2 Setting the Parameters for the Nastar Server Hard Disk Monitoring.....................................................3-3 3.1.3 Setting the Parameters for the Nastar Server Database Monitoring.......................................................3-3 3.1.4 Setting the Parameters for the Nastar Server Service Monitoring......................................................... 3-4 3.2 Monitoring the Status of the Nastar Server.....................................................................................................3-4 3.2.1 Monitoring the Nastar Server Service Status.........................................................................................3-5 3.2.2 Monitoring the Nastar Server Process Status.........................................................................................3-5 3.2.3 Monitoring the Nastar Server Hard Disk Status.....................................................................................3-6 3.2.4 Monitoring the Nastar Server Database Status...................................................................................... 3-6 3.2.5 Monitoring the Nastar Server Status......................................................................................................3-7 3.2.6 Viewing the Information about Nastar Server Components..................................................................3-7 3.2.7 Refreshing the Monitoring Information.................................................................................................3-7 3.2.8 Saving the Monitoring Information........................................................................................................3-8 3.3 Reference of the System Monitoring GUI...................................................................................................... 3-8 3.3.1 Parameters for Setting Monitoring Parameters of the Nastar Server.....................................................3-9 3.3.2 Parameters for Monitoring the Nastar Server Service Status...............................................................3-16 3.3.3 Parameters for Monitoring the Nastar Server Process Status...............................................................3-17 3.3.4 Parameters for Monitoring the Nastar Server Hard Disk Status..........................................................3-17 3.3.5 Parameters for Monitoring the Nastar Server Database Status............................................................3-18 3.3.6 Parameters for Monitoring the Nastar Server Status............................................................................3-19 vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
Contents
3.3.7 Parameters for Viewing the Information about Nastar Server Components........................................3-20
4 Security Management................................................................................................................4-1
4.1 Introduction to Security Management.............................................................................................................4-2 4.1.1 Security Management.............................................................................................................................4-2 4.1.2 Concepts of Nastar Security...................................................................................................................4-2 4.1.3 Nastar User Rights Management Policies..............................................................................................4-4 4.1.4 Operation Rights List for the Nastar Application..................................................................................4-4 4.2 Setting Security Policies of Nastar Users........................................................................................................4-7 4.2.1 Setting the Nastar Login Mode..............................................................................................................4-7 4.2.2 Setting the Access Control List..............................................................................................................4-8 4.2.3 Setting the Password Policy...................................................................................................................4-9 4.2.4 Setting the Account Policy...................................................................................................................4-10 4.3 Creating Nastar Users and Assigning Permissions.......................................................................................4-10 4.3.1 Procedure for Creating Nastar Users....................................................................................................4-10 4.3.2 Creating an Operation Set....................................................................................................................4-11 4.3.3 Creating a User Group..........................................................................................................................4-12 4.3.4 Creating a Nastar User Account...........................................................................................................4-13 4.3.5 Examples for Creating Nastar Users and Assigning Permissions........................................................4-14 4.4 Comparing the Nastar User Rights................................................................................................................4-16 4.5 Querying the Authorization...........................................................................................................................4-16 4.6 Modifying a Nastar User...............................................................................................................................4-17 4.6.1 Resetting the Password of a Nastar User.............................................................................................4-17 4.6.2 Modifying an Operation Set.................................................................................................................4-18 4.6.3 Modifying a User Group......................................................................................................................4-19 4.6.4 Modifying the Information about a Nastar User..................................................................................4-20 4.7 Managing Nastar Operation Sets...................................................................................................................4-21 4.7.1 Nastar Operation Sets...........................................................................................................................4-21 4.7.2 Creating an Operation Set....................................................................................................................4-22 4.7.3 Modifying an Operation Set.................................................................................................................4-23 4.7.4 Deleting an Operation Set....................................................................................................................4-24 4.7.5 Exporting or Importing Operation Sets................................................................................................4-25 4.8 Monitoring a Nastar User..............................................................................................................................4-27 4.8.1 Monitoring the Nastar User Sessions...................................................................................................4-27 4.8.2 Forcing a User to Quit a Session..........................................................................................................4-29 4.8.3 Unlocking a User Account...................................................................................................................4-29 4.8.4 Sending Messages to Online Users......................................................................................................4-30 4.9 Reference of the Security Management GUI................................................................................................4-30 4.9.1 Parameters for Setting a Nastar Password Policy................................................................................4-31 4.9.2 Parameters for Setting a Nastar Account Policy..................................................................................4-35 4.9.3 Parameters for Creating a User............................................................................................................4-36 4.9.4 Parameters for Creating a Nastar User Group......................................................................................4-41 4.9.5 Parameters for Creating an Operation Set............................................................................................4-43 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
Nastar Operator Guide 4.9.6 Parameters for Setting the Nastar User Information............................................................................4-44 4.9.7 Parameters for Setting the Nastar User Group Information.................................................................4-47 4.9.8 Parameters for Assigning Operation Rights to Nastar Users and User Groups...................................4-48
5 Log Management........................................................................................................................5-1
5.1 Getting to Know Log Management.................................................................................................................5-2 5.1.1 Log Management Function....................................................................................................................5-2 5.1.2 Log Types...............................................................................................................................................5-2 5.2 Managing Operation Logs...............................................................................................................................5-6 5.2.1 Querying Operation Logs.......................................................................................................................5-6 5.2.2 Collecting Statistics on Operation Logs.................................................................................................5-8 5.3 Managing System Logs...................................................................................................................................5-8 5.3.1 Querying System Logs...........................................................................................................................5-9 5.3.2 Collecting Statistics on System Logs...................................................................................................5-10 5.4 Managing Security Logs...............................................................................................................................5-11 5.4.1 Querying Security Logs.......................................................................................................................5-11 5.4.2 Collecting Statistics on Security Logs.................................................................................................5-13 5.5 Setting Log Templates..................................................................................................................................5-14 5.6 Managing Log Data.......................................................................................................................................5-15 5.6.1 Dumping Nastar Logs..........................................................................................................................5-16 5.6.2 Setting Nastar Log Export....................................................................................................................5-16 5.7 Reference of the Log Management GUI.......................................................................................................5-17 5.7.1 Security Log List..................................................................................................................................5-18 5.7.2 Parameters for Querying Operation Logs............................................................................................5-25 5.7.3 Parameters for Collecting Statistics on Operation Logs......................................................................5-28 5.7.4 Parameters for Querying System Logs.................................................................................................5-30 5.7.5 Parameters for Collecting Statistics on System Logs...........................................................................5-31 5.7.6 Parameters for Querying Security Logs...............................................................................................5-33 5.7.7 Parameters for Collecting Statistics on Security Logs.........................................................................5-35 5.7.8 Parameters for Querying Device Logs.................................................................................................5-38 5.7.9 Parameters for Setting Log Dump and Export.....................................................................................5-38
6 GIS Management.......................................................................................................................6-1
6.1 Viewing Analysis Results by Using the Google Earth...................................................................................6-2 6.2 Viewing Analysis Results Through the GIS Window....................................................................................6-3 6.3 Managing the GIS Window.............................................................................................................................6-4 6.3.1 Importing a Map.....................................................................................................................................6-5 6.3.2 Loading Site Information.......................................................................................................................6-6 6.3.3 Filtering Cells.........................................................................................................................................6-7 6.3.4 Moving/Zooming In On/Zooming Out On/Refreshing/Fully Displaying a Map...................................6-8 6.3.5 Measuring Distance on the Map.............................................................................................................6-9 6.3.6 Saving the Map Display Effect..............................................................................................................6-9
7 OSS Management.......................................................................................................................7-1
viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
Contents
7.1 Basic Knowledge of OSS Management..........................................................................................................7-2 7.2 Creating an OSS..............................................................................................................................................7-2 7.3 Viewing the Attributes of an OSS...................................................................................................................7-4 7.4 Modifying the Attributes of an OSS............................................................................................................... 7-4 7.5 Reference for the OSS Management GUI.......................................................................................................7-5 7.5.1 Interface Description: OSS Management...............................................................................................7-5 7.5.2 Parameters for Setting the Object Attributes of OSS Management.......................................................7-7
8 GSM Centralized Task Management.....................................................................................8-1

8.1 Basic Knowledge of Centralized Task Management......................................................................................8-3 8.1.1 Types of Timing Tasks...........................................................................................................................8-3 8.1.2 System Timing Tasks.............................................................................................................................8-4 8.1.3 User Timing Task...................................................................................................................................8-4 8.1.4 Task Scheduling Parameters.................................................................................................................. 8-4 8.1.5 States of a Timing Task..........................................................................................................................8-5 8.1.6 Customizing the Interface for Managing Timing Tasks........................................................................ 8-6 8.2 Creating a GSM User-Defined Timing Task.................................................................................................. 8-7 8.2.1 Creating a Data Collection Task............................................................................................................ 8-7 8.2.2 Creating a Task of Importing GSM Performance Data........................................................................8-13 8.2.3 Creating a Task of Importing GSM Configuration Data......................................................................8-16 8.2.4 Creating a Task of Importing GSM Uplink ARFCN Scanning Data...................................................8-18 8.2.5 Creating a Task of Importing GSM Measurement-Task Data.............................................................8-20 8.2.6 Creating a Task of Importing GSM/UMTS Neighboring-Cell Analysis Data.....................................8-23 8.2.7 Creating a Task of Importing GSM VIP Analysis Data.......................................................................8-25 8.2.8 Creating a Task of Importing GSM Cell Performance Analysis Data.................................................8-27 8.2.9 Creating a Task of Importing GSM Engineering Parameters..............................................................8-30 8.3 Modifying a GSM User-Defined Timing Task.............................................................................................8-32 8.3.1 Modifying a Data Collection Task.......................................................................................................8-33 8.3.2 Modifying a Task of Importing GSM Performance Data....................................................................8-33 8.3.3 Modifying a Task of Importing GSM Configuration Data..................................................................8-34 8.3.4 Modifying a Task of Importing GSM Uplink ARFCN Scanning Data...............................................8-35 8.3.5 Modifying a Task of Importing GSM Measurement-Task File Data...................................................8-35 8.3.6 Modifying a Task of Importing GSM/UMTS Neighboring-Cell Analysis Data.................................8-36 8.3.7 Modifying a Task of Importing GSM VIP Analysis Data...................................................................8-37 8.3.8 Modifying a Task of Importing GSM Cell Performance Analysis Data..............................................8-37 8.3.9 Modifying a Task of Importing GSM Engineering Parameters...........................................................8-38 8.4 Modifying a GSM Data Deletion Task.........................................................................................................8-39 8.4.1 Modifying the Task of Deleting GSM History Data............................................................................8-39 8.4.2 Modifying the Task of Deleting GSM Performance Data...................................................................8-40 8.4.3 Modifying the Task of Deleting GSM Configuration Data.................................................................8-41 8.4.4 Modifying a Task of Deleting GSM Uplink ARFCN Scanning Data..................................................8-42 8.4.5 Modifying a Task of Deleting GSM Measurement-Task File Data.....................................................8-42 8.4.6 Modifying a Task of Deleting GSM/UMTS Neighboring-Cell Analysis Data...................................8-43 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
Nastar Operator Guide 8.4.7 Modifying a Task of Deleting GSM VIP Analysis Data.....................................................................8-44 8.4.8 Modifying a Task of Deleting GSM Cell Performance Analysis Data................................................8-45
8.5 Modifying the Task of Backing Up Data......................................................................................................8-45 8.6 Setting the Suspend or Resume Time of a Timing Task...............................................................................8-46 8.7 Viewing Timing Tasks..................................................................................................................................8-47 8.7.1 Browsing the Information of Timing Tasks.........................................................................................8-47 8.7.2 Checking the Task Progress.................................................................................................................8-48 8.7.3 Checking the Task Execution...............................................................................................................8-48 8.8 Reference for the GSM Centralized Task Management GUI.......................................................................8-49 8.8.1 Interface Description: Centralized Task Management.........................................................................8-50 8.8.2 Parameter for Setting Task Filter Conditions.......................................................................................8-51 8.8.3 Parameter for Setting Common Parameters for Timing Tasks............................................................8-52 8.8.4 Parameter for Setting the Time of a Common Periodic Task..............................................................8-53 8.8.5 Parameter for Setting the Time of a Common One-Time Task...........................................................8-54 8.8.6 Parameters for Creating or Modifying a Data Collection Task............................................................8-55 8.8.7 Parameters for Modifying the Task of Deleting History Data.............................................................8-57 8.8.8 Parameters for Modifying the Task of Deleting GSM Performance Data...........................................8-58 8.8.9 Parameters for Modifying the Task of Deleting GSM Configuration Data.........................................8-58 8.8.10 Parameters for Modifying the Task of Deleting the GSM Uplink ARFCN Scanning Data..............8-59 8.8.11 Parameters for Modifying the Task of Deleting the GSM Measurement-Task File Data.................8-59 8.8.12 Parameters for Modifying the Task of Deleting the GSM/UMTS Neighboring-Cell Analysis Data .......................................................................................................................................................................8-60 8.8.13 Parameters for Modifying the Task of Deleting GSM VIP Analysis Data........................................8-60 8.8.14 Parameters for Modifying the Task of Deleting GSM Cell Performance Analysis Data..................8-61 8.8.15 Parameters for Modifying the Task of Backing Up Data...................................................................8-61 8.8.16 Parameters for Setting the Time of a Timing Task............................................................................8-62
9 GSM MR Analysis.....................................................................................................................9-1
9.1 Basic Knowledge of GSM MR Analysis........................................................................................................9-3 9.1.1 GSM MR Analysis Function..................................................................................................................9-3 9.1.2 TopN KPIs..............................................................................................................................................9-4 9.1.3 GSM MR Topics....................................................................................................................................9-7 9.2 Process of GSM MR Analysis........................................................................................................................9-8 9.3 Managing GSM MR Analysis Tasks............................................................................................................9-10 9.3.1 Creating GSM E2E Tasks....................................................................................................................9-11 9.3.2 Creating a GSM MR Analysis Task.....................................................................................................9-15 9.3.3 Modifying a GSM MR Analysis Task.................................................................................................9-17 9.3.4 Checking a GSM MR Analysis Task...................................................................................................9-17 9.4 Querying the GSM MR Overview Report....................................................................................................9-19 9.4.1 Querying the GBSC Report..................................................................................................................9-19 9.4.2 Querying the GSM Cell Group Report................................................................................................9-22 9.4.3 Querying a GSM TopN TRX Report...................................................................................................9-25 9.4.4 Querying a GSM MR Topic Analysis Report......................................................................................9-27 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
Contents
9.5 Querying the MR Results of GSM Cells.......................................................................................................9-28 9.6 Comparing the GSM MR Analysis Results..................................................................................................9-30 9.7 Exporting the GSM MR Overview Reports..................................................................................................9-31 9.8 Reference for the GSM MR Analysis GUI...................................................................................................9-32 9.8.1 Interface Description: GSM MR Analysis...........................................................................................9-33 9.8.2 Parameters for Creating GSM E2E Tasks............................................................................................9-36 9.8.3 Parameters for Creating and Modifying GSM MR Analysis Tasks.....................................................9-42 9.8.4 Parameters for Querying GBSC Reports.............................................................................................9-45 9.8.5 Parameters for Querying the GSM Cell Group Reports......................................................................9-53 9.8.6 Parameters for Querying the GSM TopN TRX Reports......................................................................9-61 9.8.7 Parameters for Querying the GSM MR Topic Analysis Reports.........................................................9-67 9.8.8 Parameters for Querying the MR Analysis Results of GSM Cells......................................................9-73 9.8.9 Parameters for Comparing GSM MR Analysis Results.......................................................................9-79
10 GSM Neighboring Cell Analysis........................................................................................10-1

10.1 Basic Knowledge of GSM Neighboring Cell Analysis...............................................................................10-3 10.1.1 GSM Neighbor Cell Analysis Function.............................................................................................10-3 10.1.2 Algorithms for the GSM Neighboring Cell Analysis.........................................................................10-4 10.2 Procedure for Using GSM Neighboring Cell Analysis...............................................................................10-6 10.3 Managing GSM Neighboring Cell Analysis Tasks.....................................................................................10-8 10.3.1 Creating GSM E2E Tasks..................................................................................................................10-8 10.3.2 Creating a GSM Neighboring Cell Analysis Task...........................................................................10-12 10.3.3 Modifying a GSM Neighboring Cell Analysis Task........................................................................10-15 10.3.4 Checking a GSM Neighboring Cell Analysis Task.........................................................................10-16 10.4 Querying GSM Neighboring Cell Analysis Reports.................................................................................10-17 10.5 Querying GSM Possible Neighboring Cell Analysis Reports..................................................................10-19 10.6 Exporting GSM Neighboring Cell Analysis Reports................................................................................10-21 10.7 Exporting GSM Possible Neighboring Cell Analysis Reports..................................................................10-25 10.8 Reference for the GSM Neighboring Cell Analysis GUI..........................................................................10-25 10.8.1 Interface Description: GSM Neighboring Cell Analysis.................................................................10-26 10.8.2 Interface Description: Possible Neighboring GSM Cell Analysis...................................................10-27 10.8.3 Parameters for Creating GSM E2E Tasks........................................................................................10-28 10.8.4 Parameters for Creating and Modifying Neighboring GSM Cell Analysis Tasks...........................10-34 10.8.5 Parameters for Querying the Analysis Reports of Neighboring GSM Cells....................................10-37 10.8.6 Parameters for Querying the Analysis Reports of Possible Neighboring GSM Cells.....................10-40
11 Neighboring GSM/UMTS Cell Analysis...........................................................................11-1

11.1 Basic Knowledge of Neighboring GSM/UMTS Cell Analysis..................................................................11-3 11.1.1 Neighboring GSM/UMTS Cell Analysis...........................................................................................11-3 11.1.2 Algorithm for the Neighboring GSM/UMTS Cell Analysis..............................................................11-4 11.2 Process of Neighboring GSM/UMTS Cell Analysis...................................................................................11-5 11.3 Managing Neighboring GSM/UMTS Cell Analysis Tasks.........................................................................11-8 11.3.1 Creating GSM E2E Tasks..................................................................................................................11-8 11.3.2 Creating a Neighboring GSM/UMTS Cell Analysis Task...............................................................11-12 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
Nastar Operator Guide 11.3.3 Modifying Neighboring GSM/UMTS Cell Analysis Tasks.............................................................11-15 11.3.4 Querying Neighboring GSM/UMTS Cell Analysis Tasks...............................................................11-16
11.4 Querying Neighboring GSM/UMTS Cell Analysis Reports.....................................................................11-18 11.5 Querying Possible Neighboring GSM/UMTS Cell Analysis Reports......................................................11-19 11.6 Exporting Neighboring GSM/UMTS Cell Analysis Reports....................................................................11-21 11.7 Exporting Possible Neighboring GSM/UMTS Cell Analysis Reports.....................................................11-23 11.8 Reference to the Neighboring GSM/UMTS Cell Analysis Interface........................................................11-23 11.8.1 Parameters for Creating GSM E2E Tasks........................................................................................11-24 11.8.2 Parameters for Creating and Modifying Neighboring GSM/UMTS Cell Analysis Tasks...............11-29 11.8.3 Parameters for Querying the Analysis Reports of Neighboring GSM/UMTS Cells.......................11-31 11.8.4 Parameters for Querying the Analysis Reports of Possible Neighboring GSM/UMTS Cells.........11-33
12 GSM Frequency Analysis.....................................................................................................12-1

12.1 Basic Knowledge of GSM Frequency Analysis..........................................................................................12-3 12.1.1 GSM Frequency Analysis Function...................................................................................................12-3 12.1.2 Process of GSM Frequency Analysis.................................................................................................12-4 12.1.3 Process of GSM Frequency Optimization..........................................................................................12-5 12.1.4 Spacing Rules of GSM ARFCNs.......................................................................................................12-6 12.2 Procedure for Using GSM Frequency Analysis..........................................................................................12-7 12.3 Managing GSM Frequency Analysis Tasks................................................................................................12-9 12.3.1 Creating GSM E2E Tasks..................................................................................................................12-9 12.3.2 Creating a GSM Frequency Analysis Task......................................................................................12-14 12.3.3 Modifying a GSM Frequency Analysis Task...................................................................................12-16 12.3.4 Checking a GSM Frequency Analysis Task....................................................................................12-16 12.4 Querying GSM Frequency Analysis Reports............................................................................................12-18 12.4.1 Querying the Interference Matrix Report of GSM Measurement Cells...........................................12-18 12.4.2 Querying the Report of the GSM Cell Interference Matrix.............................................................12-19 12.4.3 Querying the Report of the GSM Cell Frequency Interference Matrix...........................................12-20 12.5 Querying the GSM Frequency Optimization Report................................................................................12-21 12.6 Exporting GSM Interference Analysis Reports........................................................................................12-24 12.7 Exporting GSM Frequency Optimization Reports....................................................................................12-25 12.8 Reference for the GSM Frequency Analysis GUI.....................................................................................12-26 12.8.1 Interface Description: GSM Frequency Analysis............................................................................12-26 12.8.2 Interface Description: GSM Frequency Optimization.....................................................................12-28 12.8.3 Parameters for Creating GSM E2E Tasks........................................................................................12-30 12.8.4 Parameters for Creating and Modifying GSM Frequency Analysis Tasks......................................12-36 12.8.5 Parameters for Querying the Overview Report of the GSM Test Cells...........................................12-37 12.8.6 Parameters for Querying the Report of GSM Cell Interference Matrix...........................................12-38 12.8.7 Parameters for Querying the Report of the GSM Cell Frequency Interference Matrix...................12-40 12.8.8 Parameters for Querying GSM Frequency Optimization Reports...................................................12-42
13 GSM Uplink Interference Analysis....................................................................................13-1

13.1 Basic Knowledge of GSM Uplink Interference Analysis...........................................................................13-2 13.2 Procedure for Using GSM Uplink Interference Analysis...........................................................................13-2 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
Contents
13.3 Managing GSM Uplink Interference Analysis Tasks.................................................................................13-4 13.3.1 Creating GSM E2E Tasks..................................................................................................................13-5 13.3.2 Creating a GSM Uplink Interference Analysis Task..........................................................................13-9 13.3.3 Modifying a GSM Uplink Interference Analysis Task....................................................................13-11 13.3.4 Checking a GSM Uplink Interference Analysis Task......................................................................13-12 13.4 Querying a GSM Uplink Interference Analysis Report............................................................................13-13 13.5 Reference for the GSM Uplink Interference Analysis GUI......................................................................13-15 13.5.1 Interface Description: GSM Uplink Interference Analysis..............................................................13-15 13.5.2 Parameters for Creating GSM E2E Tasks........................................................................................13-16 13.5.3 Parameters for Creating and Modifying GSM Uplink Interference Analysis Tasks.......................13-22 13.5.4 Parameters for Querying the Uplink Interference Analysis Reports of GSM Cells........................13-23
14 GSM VIP Analysis.................................................................................................................14-1

14.1 Basic Knowledge of GSM VIP Analysis....................................................................................................14-2 14.2 GSM VIP Analysis Process.........................................................................................................................14-3 14.3 Managing GSM VIP Analysis Tasks..........................................................................................................14-5 14.3.1 Managing GSM VIP Groups..............................................................................................................14-6 14.3.2 Creating GSM E2E Tasks..................................................................................................................14-9 14.3.3 Creating GSM VIP Analysis Tasks..................................................................................................14-14 14.3.4 Modifying GSM VIP Analysis Tasks..............................................................................................14-16 14.3.5 Checking GSM VIP Analysis Tasks................................................................................................14-16 14.4 Querying GSM VIP Analysis Reports......................................................................................................14-18 14.5 Exporting GSM VIP Analysis Reports.....................................................................................................14-20 14.6 Reference to the GSM VIP Analysis Interface.........................................................................................14-20 14.6.1 Parameters for Creating and Modifying GSM VIP Subscribers/VIP Groups..................................14-20 14.6.2 Parameters for Creating GSM E2E Tasks........................................................................................14-22 14.6.3 Parameters for Creating and Modifying GSM VIP Analysis Tasks................................................14-27 14.6.4 Parameters for Querying GSM VIP Analysis Reports.....................................................................14-30
15 GSM Complaint Analysis Support.....................................................................................15-1

15.1 Basic Knowledge of GSM Complaint Analysis Support............................................................................15-3 15.2 GSM Complaint Analysis Support Process................................................................................................15-4 15.3 Managing GSM Complaint Analysis Support Tasks..................................................................................15-5 15.3.1 Creating GSM Complaint Analysis Support Tasks............................................................................15-5 15.3.2 Modifying GSM Complaint Analysis Support Tasks........................................................................15-8 15.3.3 Checking GSM Complaint Analysis Support Tasks..........................................................................15-9 15.4 Querying GSM Complaint Analysis Support Reports..............................................................................15-10 15.5 Exporting GSM Complaint Analysis Support Reports.............................................................................15-11 15.6 Reference to the GSM Complaint Analysis Support Interface.................................................................15-12 15.6.1 Parameters for Creating and Modifying GSM Complaint Analysis Support Tasks........................15-12 15.6.2 Parameters for Querying GSM Complaint Analysis Support Reports.............................................15-13
16 GSM Cell Performance Analysis........................................................................................16-1

16.1 Basic Knowledge of GSM Cell Performance Analysis..............................................................................16-2 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
16.2 GSM Cell Performance Analysis Process ..................................................................................................16-2 16.3 Managing GSM Cell Performance Analysis Tasks.....................................................................................16-4 16.3.1 Creating GSM E2E Tasks..................................................................................................................16-5 16.3.2 Creating GSM Cell Performance Analysis Tasks..............................................................................16-9 16.3.3 Modifying GSM Cell Performance Analysis Tasks.........................................................................16-11 16.3.4 Checking GSM Cell Performance Analysis Tasks..........................................................................16-12 16.4 Querying GSM Cell Performance Analysis Reports.................................................................................16-13 16.5 Exporting GSM Cell Performance Analysis Reports................................................................................16-15 16.6 Reference to the GSM Cell Performance Analysis Interface....................................................................16-16 16.6.1 Parameters for Creating GSM E2E Tasks........................................................................................16-16 16.6.2 Parameters for Creating or Modifying GSM Cell Performance Analysis Tasks.............................16-21 16.6.3 Parameters for Querying the GSM Cell Performance Analysis Report...........................................16-22
17 UMTS Centralized Task Management..............................................................................17-1

17.1 Basic Knowledge of UMTS Centralized Task Management......................................................................17-3 17.1.1 Types of Timing Tasks.......................................................................................................................17-3 17.1.2 System Timing Tasks.........................................................................................................................17-4 17.1.3 User Timing Task...............................................................................................................................17-4 17.1.4 Task Scheduling Parameters.............................................................................................................. 17-4 17.1.5 States of a Timing Task......................................................................................................................17-5 17.1.6 Customizing the Interface for Managing Timing Tasks.................................................................... 17-6 17.2 Creating a UMTS User-Defined Timing Task............................................................................................17-7 17.2.1 Creating a Task of Importing UMTS Uplink-Interference Data........................................................17-8 17.2.2 Creating a Task of Importing UMTS Neighboring-Cell Analysis Data..........................................17-10 17.2.3 Creating a Task of Importing UMTS/GSM Neighboring-Cell Analysis Data.................................17-13 17.2.4 Creating a Task of Importing UMTS Configuration Data...............................................................17-15 17.2.5 Creating a Task of Importing UMTS Coverage Analysis Data.......................................................17-18 17.2.6 Creating a Task of Importing UMTS VIP Analysis Data................................................................17-20 17.2.7 Creating a Task of Importing UMTS Pilot Pollution Analysis Data...............................................17-22 17.2.8 Creating a Task of Importing UMTS Cell Performance Analysis Data...........................................17-25 17.2.9 Creating a Task of Importing UMTS Engineering Parameters........................................................17-27 17.3 Modifying a UMTS User-Defined Timing Task.......................................................................................17-30 17.3.1 Modifying a Task of Importing UMTS Uplink Interference Data...................................................17-30 17.3.2 Modifying a Task of Importing UMTS Neighboring-Cell Analysis Data.......................................17-31 17.3.3 Modifying a Task of Importing UMTS/GSM Neighboring-Cell Analysis Data.............................17-32 17.3.4 Modifying a Task of Importing UMTS Configuration Data............................................................17-32 17.3.5 Modifying a Task of Importing UMTS Coverage Analysis Data....................................................17-33 17.3.6 Modifying a UMTS VIP Analysis Data Import Task......................................................................17-34 17.3.7 Modifying a Task of Importing UMTS Pilot Pollution Analysis Data............................................17-34 17.3.8 Modifying a Task of Importing UMTS Cell Performance Analysis Data.......................................17-35 17.3.9 Modifying a Task of Importing UMTS Engineering Parameters.....................................................17-36 17.4 Modifying a UMTS Data Deletion Task...................................................................................................17-36 17.4.1 Modifying the Task of Deleting GSM History Data........................................................................17-37 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
Contents
17.4.2 Modifying a Task of Deleting UMTS Uplink Interference Data.....................................................17-38 17.4.3 Modifying the Task of Deleting UMTS Neighboring-Cell Analysis Data......................................17-39 17.4.4 Modifying the Task of Deleting UMTS/GSM Neighboring-Cell Analysis Data............................17-39 17.4.5 Modifying the Task of Deleting UMTS Configuration Data...........................................................17-40 17.4.6 Modifying the Task of Deleting UMTS Coverage Analysis Data...................................................17-41 17.4.7 Modifying a Task of Deleting UMTS VIP Analysis Data...............................................................17-41 17.4.8 Modifying a Task of Deleting UMTS Pilot Pollution Analysis Data..............................................17-42 17.4.9 Modifying a Task of Deleting UMTS Cell Performance Analysis Data.........................................17-43 17.5 Modifying the Task of Backing Up Data..................................................................................................17-44 17.6 Setting the Suspend or Resume Time of a Timing Task...........................................................................17-44 17.7 Viewing Timing Tasks..............................................................................................................................17-45 17.7.1 Browsing the Information of Timing Tasks.....................................................................................17-45 17.7.2 Checking the Task Progress.............................................................................................................17-46 17.7.3 Checking the Task Execution...........................................................................................................17-46 17.8 Reference to the UMTS Centralized Task Management Interface...........................................................17-47 17.8.1 Interface Description: Centralized Task Management.....................................................................17-48 17.8.2 Parameter for Setting Task Filter Conditions...................................................................................17-50 17.8.3 Parameter for Setting Common Parameters for Timing Tasks........................................................17-51 17.8.4 Parameter for Setting the Time of a Common Periodic Task..........................................................17-52 17.8.5 Parameter for Setting the Time of a Common One-Time Task.......................................................17-53 17.8.6 Parameters for Modifying the Task of Deleting History Data.........................................................17-53 17.8.7 Parameters for Modifying the Task of Deleting UMTS Uplink Interference Data..........................17-54 17.8.8 Parameters for Modifying the Task of Deleting Neighboring UMTS Cell Analysis Data..............17-55 17.8.9 Parameters for Modifying the Task of Deleting UMTS/GSM Neighboring-Cell Analysis Data....17-55 17.8.10 Parameters for Modifying the Task of Deleting UMTS Configuration Data.................................17-55 17.8.11 Parameters for Modifying the Task of Deleting UMTS Coverage Analysis Data.........................17-56 17.8.12 Parameters for Modifying the Task of Deleting UMTS VIP Analysis Data..................................17-56 17.8.13 Parameters for Modifying the Task of Deleting UMTS Pilot Pollution Analysis Data.................17-57 17.8.14 Parameters for Modifying the Task of Deleting UMTS Cell Performance Analysis Data............17-57 17.8.15 Parameters for Modifying the Task of Backing Up Data...............................................................17-58 17.8.16 Parameters for Setting the Time of a Timing Task........................................................................17-58
18 UMTS Uplink Interference Analysis.................................................................................18-1

18.1 Basic Knowledge of UMTS Uplink-Interference Analysis........................................................................18-3 18.2 Process of UMTS uplink interference Analysis..........................................................................................18-3 18.3 Managing UMTS Uplink Interference Analysis Tasks...............................................................................18-5 18.3.1 Creating UMTS E2E Tasks................................................................................................................18-5 18.3.2 Creating a UMTS Uplink Interference Analysis Task.......................................................................18-7 18.3.3 Modifying a UMTS Uplink-Interference Analysis Task...................................................................18-9 18.3.4 Checking a UMTS Uplink Interference Analysis Task....................................................................18-10 18.4 Querying a UMTS Uplink Interference Analysis Report..........................................................................18-11 18.5 Reference for the UMTS Uplink Interference Analysis GUI....................................................................18-13 18.5.1 Interface for UMTS Uplink Interference Analysis...........................................................................18-13 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
Nastar Operator Guide 18.5.2 Parameters for Creating UMTS E2E Tasks.....................................................................................18-14 18.5.3 Parameters for Creating or Modifying a UMTS Uplink Interference Analysis Task......................18-16 18.5.4 Parameters for Querying the Uplink Interference Analysis Reports of UMTS Cells......................18-17
19 UMTS Co-Frequency Neighboring Cell Analysis...........................................................19-1

19.1 Basic Knowledge of UMTS Co-Frequency Neighboring Cell Analysis.................................................... 19-3 19.1.1 UMTS Co-Frequency Neighboring Cell Analysis Function..............................................................19-3 19.1.2 UMTS Co-Frequency Neighboring Cell Analysis Algorithms..........................................................19-4 19.2 Process of UMTS Co-Frequency Neighboring Cell Analysis.................................................................... 19-5 19.3 Managing UMTS Neighboring Cell Analysis Tasks.................................................................................. 19-6 19.3.1 Creating UMTS E2E Tasks................................................................................................................19-7 19.3.2 Creating a UMTS Co-Frequency Neighboring Cell Analysis Task...................................................19-9 19.3.3 Modifying a UMTS Co-Frequency Neighboring Cell Analysis Task.............................................19-11 19.3.4 Checking a UMTS Co-Frequency Neighboring Cell Analysis Task...............................................19-12 19.4 Querying a UMTS Co-Frequency Neighboring Cell Analysis Report.....................................................19-13 19.5 Exporting a UMTS Co-Frequency Neighboring Cell Analysis Report....................................................19-15 19.6 Reference for the UMTS Co-Frequency Neighboring Cell Analysis GUI...............................................19-17 19.6.1 Interface Description: UMTS Co-Frequency Neighboring-Cell Analysis.......................................19-17 19.6.2 Parameters for Creating UMTS E2E Tasks.....................................................................................19-19 19.6.3 Parameters for Creating and Modifying UMTS Co-Frequency Neighboring Cell Analysis Tasks .....................................................................................................................................................................19-20 19.6.4 Parameters for Querying UMTS Co-Frequency Neighboring Cell Analysis Reports.....................19-21
20 Neighboring UMTS/GSM Cell Analysis...........................................................................20-1

20.1 Basic Knowledge of Neighboring UMTS/GSM Cell Analysis.................................................................. 20-3 20.1.1 Neighboring UMTS/GSM Cell Analysis...........................................................................................20-3 20.1.2 Algorithm for the Neighboring UMTS/GSM Cell Analysis..............................................................20-4 20.2 Process of Neighboring UMTS/GSM Cell Analysis...................................................................................20-5 20.3 Managing Neighboring UMTS/GSM Cell Analysis Tasks.........................................................................20-6 20.3.1 Creating UMTS E2E Tasks................................................................................................................20-7 20.3.2 Creating a Neighboring UMTS/GSM Cell Analysis Task.................................................................20-9 20.3.3 Modifying Neighboring UMTS/GSM Cell Analysis Tasks.............................................................20-12 20.3.4 Querying Neighboring UMTS/GSM Cell Analysis Tasks...............................................................20-13 20.4 Querying Neighboring UMTS/GSM Cell Analysis Reports.....................................................................20-14 20.5 Querying Possible Neighboring UMTS/GSM Cell Analysis Reports......................................................20-16 20.6 Exporting Neighboring UMTS/GSM Cell Analysis Reports....................................................................20-17 20.7 Exporting Possible Neighboring UMTS/GSM Cell Analysis Reports.....................................................20-19 20.8 Reference to the Neighboring UMTS/GSM Cell Analysis Interface........................................................20-19 20.8.1 Parameters for Creating UMTS E2E Tasks.....................................................................................20-20 20.8.2 Parameters for Creating and Modifying Neighboring UMTS/GSM Cell Analysis Tasks...............20-21 20.8.3 Parameters for Querying the Analysis Reports of Neighboring UMTS/GSM Cells.......................20-23 20.8.4 Parameters for Querying the Analysis Reports of Possible Neighboring UMTS/GSM Cells.........20-25
21 UMTS Coverage Analysis....................................................................................................21-1

21.1 Basic Knowledge of UMTS Coverage Analysis.........................................................................................21-2 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
Contents
21.2 Process of UMTS Coverage Analysis.........................................................................................................21-2 21.3 Managing a UMTS Coverage Analysis Task..............................................................................................21-4 21.3.1 Creating UMTS E2E Tasks................................................................................................................21-4 21.3.2 Creating a UMTS Coverage Analysis Task.......................................................................................21-6 21.3.3 Modifying a UMTS Coverage Analysis Task....................................................................................21-8 21.3.4 Checking a UMTS Coverage Analysis Task......................................................................................21-9 21.4 Querying a UMTS Coverage Analysis Report..........................................................................................21-10 21.5 Exporting a UMTS Coverage Analysis Report.........................................................................................21-12 21.6 Reference for the UMTS Coverage Analysis GUI....................................................................................21-13 21.6.1 Interface for UMTS Coverage Analysis...........................................................................................21-13 21.6.2 Parameters for Creating UMTS E2E Tasks.....................................................................................21-15 21.6.3 Parameters for Creating and Modifying UMTS Coverage Analysis Tasks.....................................21-17 21.6.4 Parameters for Querying UMTS Coverage Analysis Reports..........................................................21-18
22 UMTS VIP Analysis..............................................................................................................22-1

22.1 Basic Knowledge of UMTS VIP Analysis..................................................................................................22-2 22.2 UMTS VIP Analysis Process......................................................................................................................22-3 22.3 Managing UMTS VIP Analysis Tasks........................................................................................................22-5 22.3.1 Managing UMTS VIP Groups...........................................................................................................22-6 22.3.2 Creating UMTS E2E Tasks................................................................................................................22-9 22.3.3 Creating UMTS VIP Analysis Tasks...............................................................................................22-11 22.3.4 Modifying UMTS VIP Analysis Tasks............................................................................................22-13 22.3.5 Checking UMTS VIP Analysis Tasks..............................................................................................22-14 22.4 Querying UMTS VIP Analysis Reports....................................................................................................22-15 22.5 Exporting UMTS VIP Analysis Reports...................................................................................................22-17 22.6 Reference to the UMTS VIP Analysis Interface.......................................................................................22-18 22.6.1 Interface Description: UMTS VIP Analysis....................................................................................22-18 22.6.2 Parameters for Creating and Modifying UMTS VIP Subscribers/VIP Groups...............................22-20 22.6.3 Parameters for Creating UMTS E2E Tasks.....................................................................................22-21 22.6.4 Parameters for Creating and Modifying UMTS VIP Analysis Tasks..............................................22-23 22.6.5 Parameters for Querying UMTS VIP Analysis Reports..................................................................22-25
23 UMTS Complaint Analysis Support..................................................................................23-1

23.1 Basic Knowledge of UMTS Complaint Analysis Support..........................................................................23-3 23.2 UMTS Complaint Analysis Support Process..............................................................................................23-4 23.3 Managing UMTS Complaint Analysis Support Tasks................................................................................23-5 23.3.1 Creating UMTS Complaint Analysis Support Tasks.........................................................................23-6 23.3.2 Modifying UMTS Complaint Analysis Support Tasks......................................................................23-8 23.3.3 Checking UMTS Complaint Analysis Support Tasks........................................................................23-9 23.4 Querying UMTS Complaint Analysis Support Reports............................................................................23-10 23.5 Exporting UMTS Complaint Analysis Support Reports...........................................................................23-12 23.6 Reference to the UMTS Complaint Analysis Support Interface...............................................................23-12 23.6.1 Parameters for Creating and Modifying UMTS Complaint Analysis Support Tasks......................23-13 23.6.2 Parameters for Querying UMTS Complaint Analysis Support Reports..........................................23-14 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
24 UMTS Pilot Pollution Analysis...........................................................................................24-1

24.1 Basic Knowledge of UMTS Pilot Pollution Analysis.................................................................................24-3 24.2 UMTS Pilot Pollution Analysis Process.....................................................................................................24-3 24.3 Managing UMTS Pilot Pollution Analysis Tasks.......................................................................................24-5 24.3.1 Creating UMTS E2E Tasks................................................................................................................24-6 24.3.2 Creating UMTS Pilot Pollution Analysis Tasks................................................................................24-8 24.3.3 Modifying UMTS Pilot Pollution Analysis Tasks...........................................................................24-10 24.3.4 Checking UMTS Pilot Pollution Analysis Tasks.............................................................................24-10 24.4 Querying UMTS Pilot Pollution Analysis Reports...................................................................................24-12 24.5 Exporting UMTS Pilot Pollution Analysis Reports..................................................................................24-13 24.6 Reference to the UMTS Pilot Pollution Analysis Interface......................................................................24-13 24.6.1 Interface Description: UMTS Pilot Pollution Analysis....................................................................24-14 24.6.2 Parameters for Creating UMTS E2E Tasks.....................................................................................24-15 24.6.3 Parameters for Creating and Modifying UMTS Pilot Pollution Analysis Tasks.............................24-16 24.6.4 Parameters for Querying UMTS Pilot Pollution Analysis Reports..................................................24-17
25 UMTS Cell Performance Analysis......................................................................................25-1

25.1 Basic Knowledge of UMTS Cell Performance Analysis............................................................................25-2 25.2 UMTS Cell Performance Analysis Process................................................................................................25-6 25.3 Managing UMTS Cell Performance Analysis Tasks..................................................................................25-8 25.3.1 Creating UMTS E2E Tasks................................................................................................................25-9 25.3.2 Creating UMTS Cell Performance Analysis Tasks..........................................................................25-11 25.3.3 Modifying UMTS Cell Performance Analysis Tasks......................................................................25-13 25.3.4 Checking UMTS Cell Performance Analysis Tasks........................................................................25-13 25.4 Querying UMTS Cell Performance Analysis Reports..............................................................................25-15 25.5 Exporting UMTS Cell Performance Analysis Reports.............................................................................25-16 25.6 Reference to the UMTS Cell Performance Analysis Interface.................................................................25-17 25.6.1 Parameters for Creating UMTS E2E Tasks.....................................................................................25-17 25.6.2 Parameters for Creating or Modifying UMTS Cell Performance Analysis Tasks...........................25-19 25.6.3 Parameters for Querying the UMTS Cell Performance Analysis Report........................................25-20
26 CDMA Centralized Task Management.............................................................................26-1

26.1 Basic Knowledge of CDMA Centralized Task Management.....................................................................26-3 26.1.1 Types of Timing Tasks.......................................................................................................................26-3 26.1.2 System Timing Tasks.........................................................................................................................26-4 26.1.3 User Timing Task...............................................................................................................................26-4 26.1.4 Task Scheduling Parameters..............................................................................................................26-4 26.1.5 States of a Timing Task......................................................................................................................26-5 26.1.6 Customizing the Interface for Managing Timing Tasks....................................................................26-6 26.2 Creating a CDMA User-Defined Timing Task...........................................................................................26-7 26.2.1 Creating a Task of Importing CDMA VIP KPI Analysis Data..........................................................26-8 26.2.2 Creating a Task of Importing CDMA Uplink-Interference-Ranking Analysis Data.......................26-10 26.2.3 Creating a Task of Importing the CDMA Uplink-Interference-Spectrum Analysis Data...............26-13 26.2.4 Creating a Task of Importing CDMA Neighboring-Cell Analysis Data..........................................26-15 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
Contents
26.2.5 Creating a Task of Importing CDMA Pilot Pollution Analysis Data..............................................26-18 26.2.6 Creating a Task of Importing CDMA Coverage Analysis Data......................................................26-20 26.2.7 Creating a Task of Importing CDMA Cell Performance Analysis Data..........................................26-22 26.2.8 Creating a Task of Importing CDMA VIP KPI Analysis Data........................................................26-25 26.2.9 Creating a Task of Importing CDMA Configuration Data..............................................................26-27 26.3 Modifying a CDMA User-Defined Timing Task......................................................................................26-29 26.3.1 Modifying a Task of Importing CDMA VIP KPI Analysis Data....................................................26-30 26.3.2 Modifying a Task of Importing CDMA Uplink-Interference-Ranking Analysis Data....................26-31 26.3.3 Modifying a Task of Importing CDMA Uplink-Interference-Spectrum Analysis Data..................26-32 26.3.4 Modifying a Task of Importing CDMA Neighboring Cell Analysis Data......................................26-32 26.3.5 Modifying a Task of Importing CDMA Pilot Pollution Analysis Data...........................................26-33 26.3.6 Modifying a Task of Importing CDMA Coverage Analysis Data...................................................26-34 26.3.7 Modifying a Task of Importing CDMA Cell Performance Analysis Data......................................26-34 26.3.8 Modifying a Task of Deleting CDMA VIP KPI Analysis Data.......................................................26-35 26.3.9 Modifying a Task of Importing CDMA Configuration Data...........................................................26-36 26.4 Modifying a CDMA Data Deletion Task..................................................................................................26-36 26.4.1 Modifying the Task of Deleting GSM History Data........................................................................26-37 26.4.2 Modifying a Task of Deleting CDMA VIP KPI Analysis Data.......................................................26-38 26.4.3 Modifying a Task of Deleting CDMA Uplink-Interference-Ranking Analysis Data......................26-39 26.4.4 Modifying a Task of Deleting CDMA Uplink-Interference-Spectrum Analysis Data....................26-39 26.4.5 Modifying a Task of Deleting CDMA Neighboring Cell Analysis Data.........................................26-40 26.4.6 Modifying a Task of Deleting CDMA Pilot Pollution Analysis Data.............................................26-41 26.4.7 Modifying a Task of Deleting CDMA Coverage Analysis Data.....................................................26-41 26.4.8 Modifying a Task of Deleting CDMA Cell Performance Analysis Data.........................................26-42 26.4.9 Modifying a Task of Deleting CDMA VIP KPI Analysis Data.......................................................26-43 26.4.10 Modifying a Task of Deleting CDMA Configuration Data...........................................................26-44 26.5 Modifying the Task of Backing Up Data..................................................................................................26-44 26.6 Setting the Suspend or Resume Time of a Timing Task...........................................................................26-45 26.7 Viewing Timing Tasks..............................................................................................................................26-46 26.7.1 Browsing the Information of Timing Tasks.....................................................................................26-46 26.7.2 Checking the Task Progress.............................................................................................................26-47 26.7.3 Checking the Task Execution...........................................................................................................26-47 26.8 Reference to the CDMA Centralized Task Management Interface..........................................................26-48 26.8.1 Interface Description: Centralized Task Management.....................................................................26-48 26.8.2 Parameter for Setting Task Filter Conditions...................................................................................26-50 26.8.3 Parameter for Setting Common Parameters for Timing Tasks........................................................26-51 26.8.4 Parameter for Setting the Time of a Common Periodic Task..........................................................26-52 26.8.5 Parameter for Setting the Time of a Common One-Time Task.......................................................26-53 26.8.6 Parameters for Modifying the Task of Deleting History Data.........................................................26-53 26.8.7 Parameters for Modifying the Task of Backing Up Data.................................................................26-54 26.8.8 Parameters for Setting the Time of a Timing Task..........................................................................26-54
27 CDMA Uplink Interference Analysis................................................................................27-1

Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
27.1 Basic Knowledge of CDMA Uplink-Interference Analysis........................................................................27-3 27.2 Process of CDMA Uplink Interference Analysis........................................................................................27-3 27.3 Managing CDMA Uplink Interference Analysis Tasks..............................................................................27-6 27.3.1 Creating a CDMA E2E Task..............................................................................................................27-7 27.3.2 Creating a CDMA Uplink-Interference-Ranking Analysis Task.......................................................27-9 27.3.3 Creating a CDMA Uplink-Interference-Spectrum Analysis Task...................................................27-11 27.3.4 Modifying a CDMA Uplink-Interference-Ranking Analysis Task..................................................27-13 27.3.5 Modifying a CDMA Uplink-Interference-Spectrum Analysis Task................................................27-13 27.3.6 Checking a CDMA Uplink-Interference-Ranking Analysis Task...................................................27-14 27.3.7 Checking a CDMA Uplink-Interference-Spectrum Analysis Task..................................................27-16 27.4 Querying the CDMA Uplink-Interference-Ranking Analysis Report......................................................27-17 27.5 Querying the CDMA Uplink-Interference-Spectrum Analysis Report.....................................................27-19 27.6 Reference for the CDMA Uplink Interference Analysis GUI...................................................................27-20 27.6.1 Interface Description: CDMA Uplink-Interference-Ranking Analysis...........................................27-21 27.6.2 Interface Description: CDMA Uplink-Interference-Spectrum Analysis..........................................27-22 27.6.3 Parameters of CDMA E2E Tasks.....................................................................................................27-23 27.6.4 Parameters for Creating and Modifying CDMA Uplink-Interference-Ranking Analysis Tasks.....27-24 27.6.5 Parameters for Creating and Modifying CDMA Uplink-Interference-Spectrum Analysis Tasks...27-25 27.6.6 Parameters for Querying the Uplink-Interference-Ranking Analysis Reports of CDMA Cells......27-26 27.6.7 Parameters for Querying the Uplink-Interference-Spectrum Analysis Reports of CDMA Cells....27-27
28 CDMA Co-Frequency Neighboring Cell Analysis..........................................................28-1

28.1 Basic Knowledge of CDMA Neighboring Cell Analysis...........................................................................28-3 28.1.1 CDMA Co-Frequency Neighboring Cell Analysis Functions...........................................................28-3 28.1.2 CDMA Neighboring Cell Analysis Algorithms.................................................................................28-4 28.2 Process of CDMA Co-Frequency Neighboring-Cell Analysis...................................................................28-5 28.3 Managing CDMA Neighboring Cell Analysis Tasks.................................................................................28-6 28.3.1 Creating a CDMA E2E Task..............................................................................................................28-7 28.3.2 Creating a CDMA Co-Frequency Neighboring Cell Analysis Task..................................................28-9 28.3.3 Modifying a CDMA Co-Frequency Neighboring Cell Analysis Task............................................28-11 28.3.4 Checking a CDMA Co-Frequency Neighboring Cell Analysis Task..............................................28-12 28.4 Query a CDMA Co-Frequency Neighboring Cell Analysis Report.........................................................28-13 28.5 Exporting a CDMA Co-Frequency Neighboring Cell Analysis Report...................................................28-15 28.6 Reference for the CDMA Neighboring Cell Analysis GUI......................................................................28-18 28.6.1 Interface Description: CDMA Co-Frequency Neighboring Cell Analysis......................................28-18 28.6.2 Parameters of CDMA E2E Tasks.....................................................................................................28-20 28.6.3 Parameters for Creating and Modifying CDMA Co-Frequency Neighboring Cell Analysis Tasks .....................................................................................................................................................................28-20 28.6.4 Parameters for Querying CDMA Co-Frequency Neighboring Cell Analysis Reports....................28-22
29 CDMA Complaint Analysis Support.................................................................................29-1

29.1 Basic Knowledge of CDMA Complaint Analysis Support.........................................................................29-2 29.2 Process of CDMA Complaint Analysis Support.........................................................................................29-2 29.3 Managing CDMA Complaint Analysis Support Tasks...............................................................................29-3 xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
Contents
29.3.1 Creating CDMA Complaint Analysis Support Tasks........................................................................29-3 29.3.2 Modifying CDMA Complaint Analysis Support Tasks.....................................................................29-5 29.3.3 Checking CDMA Complaint Analysis Support Tasks.......................................................................29-6 29.4 Querying a Complaint Analysis Support Report.........................................................................................29-7 29.5 Reference for the CDMA Complaint Analysis Support GUI..................................................................... 29-8 29.5.1 Interface for CDMA Complaint Analysis Support............................................................................ 29-9 29.5.2 Parameters for Creating and Modifying CDMA Complaint Analysis Tasks...................................29-10 29.5.3 Parameters for Querying a CDMA Complaint Analysis Support Report........................................29-11
30 CDMA Pilot Pollution Analysis..........................................................................................30-1

30.1 Basic Knowledge of CDMA Pilot Pollution Analysis................................................................................30-3 30.2 CDMA Pilot Pollution Analysis Process.................................................................................................... 30-3 30.3 Managing CDMA Pilot Pollution Analysis Tasks......................................................................................30-5 30.3.1 Creating a CDMA E2E Task..............................................................................................................30-6 30.3.2 Creating CDMA Pilot Pollution Analysis Tasks................................................................................30-8 30.3.3 Modifying CDMA Pilot Pollution Analysis Tasks..........................................................................30-10 30.3.4 Checking CDMA Pilot Pollution Analysis Tasks............................................................................30-11 30.4 Querying CDMA Pilot Pollution Analysis Reports..................................................................................30-12 30.5 Exporting CDMA Pilot Pollution Analysis Reports.................................................................................30-13 30.6 Reference for the CDMA Pilot Pollution Analysis...................................................................................30-14 30.6.1 Parameters of CDMA E2E Tasks.....................................................................................................30-15 30.6.2 Parameters for Creating and Modifying CDMA Pilot Pollution Analysis Tasks............................30-15 30.6.3 Parameters for Querying CDMA Pilot Pollution Analysis Reports.................................................30-16
31 CDMA Coverage Analysis...................................................................................................31-1

31.1 Basic Knowledge of CDMA Coverage Analysis........................................................................................31-3 31.2 CDMA Coverage Analysis Process............................................................................................................ 31-4 31.3 Managing CDMA Coverage Analysis Tasks..............................................................................................31-6 31.3.1 Creating a CDMA E2E Task..............................................................................................................31-7 31.3.2 Creating CDMA Coverage Analysis Tasks....................................................................................... 31-9 31.3.3 Modifying CDMA Coverage Analysis Tasks..................................................................................31-11 31.3.4 Checking CDMA Coverage Analysis Tasks....................................................................................31-12 31.4 Querying CDMA Coverage Analysis Reports..........................................................................................31-13 31.5 Exporting CDMA Coverage Analysis Reports.........................................................................................31-15 31.6 Reference for the CDMA Coverage Analysis Interface............................................................................31-16 31.6.1 Parameters of CDMA E2E Tasks.....................................................................................................31-16 31.6.2 Parameters for Creating and Modifying CDMA Coverage Analysis Tasks....................................31-17 31.6.3 Parameters for Querying CDMA Coverage Analysis Reports.........................................................31-18
32 CDMA Cell Performance Analysis.....................................................................................32-1

32.1 Basic Knowledge of CDMA Cell Performance Analysis...........................................................................32-3 32.2 CDMA Cell Performance Analysis Process................................................................................................32-3 32.3 Managing CDMA Cell Performance Analysis Tasks.................................................................................32-5 32.3.1 Creating a CDMA E2E Task..............................................................................................................32-6 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
Nastar Operator Guide 32.3.2 Creating CDMA Cell Performance Analysis Tasks...........................................................................32-8 32.3.3 Modifying CDMA Cell Performance Analysis Tasks.....................................................................32-10 32.3.4 Checking CDMA Cell Performance Analysis Tasks.......................................................................32-11
32.4 Querying CDMA Cell Performance Analysis Reports.............................................................................32-12 32.5 Exporting CDMA Cell Performance Analysis Reports............................................................................32-14 32.6 Reference for the CDMA Cell Performance Analysis Interface...............................................................32-15 32.6.1 Parameters of CDMA E2E Tasks.....................................................................................................32-15 32.6.2 Parameters for Creating and Modifying CDMA Cell Performance Analysis Tasks.......................32-16 32.6.3 Parameters for Querying CDMA Cell Performance Analysis Reports............................................32-17
33 CDMA VIP Analysis.............................................................................................................33-1

33.1 Basic Knowledge of CDMA VIP Analysis.................................................................................................33-2 33.2 Process of CDMA VIP Analysis.................................................................................................................33-3 33.3 Managing CDMA VIP Analysis Tasks.......................................................................................................33-4 33.3.1 Managing CDMA VIP Groups..........................................................................................................33-5 33.3.2 Creating a CDMA E2E Task..............................................................................................................33-7 33.3.3 Creating a CDMA VIP Analysis Task.............................................................................................33-10 33.3.4 Modifying a CDMA VIP Analysis Task..........................................................................................33-12 33.3.5 Viewing a CDMA VIP Analysis Task.............................................................................................33-12 33.4 Querying CDMA VIP Analysis Reports...................................................................................................33-14 33.5 Exporting CDMA VIP Analysis Reports..................................................................................................33-15 33.6 Reference for the CDMA VIP Analysis GUI............................................................................................33-16 33.6.1 Parameters for Creating and Modifying CDMA VIP Subscribers and VIP Groups........................33-16 33.6.2 Parameters of CDMA E2E Tasks.....................................................................................................33-17 33.6.3 Parameters for Creating and Modifying CDMA VIP Analysis Tasks.............................................33-18 33.6.4 Parameters for Querying CDMA VIP Analysis Reports.................................................................33-20
xxii
Issue 03 (2010-06-30)
Figures
Figures
Figure 1-1 Software modules of the Nastar..........................................................................................................1-5 Figure 1-2 Modules of the server software of the Nastar.....................................................................................1-6 Figure 1-3 Position of the Nastar on the network................................................................................................1-7 Figure 1-4 Process of Nastar performance analysis.............................................................................................1-9 Figure 2-1 GUI of the Nastar client....................................................................................................................2-25 Figure 7-1 Interface of OSS management............................................................................................................7-6 Figure 8-1 State transition of a timing task..........................................................................................................8-5 Figure 8-2 Integrated Task Management interface............................................................................................8-50 Figure 9-1 Process of GSM MR analysis.............................................................................................................9-9 Figure 9-2 MR Overview Report.......................................................................................................................9-33 Figure 9-3 MR Query Result..............................................................................................................................9-35 Figure 9-4 MR Comparison Report....................................................................................................................9-36 Figure 10-1 Algorithms for the GSM neighboring cell analysis........................................................................10-5 Figure 10-2 Process of GSM neighboring cell analysis.....................................................................................10-6 Figure 10-3 Interface for the neighboring cell analysis....................................................................................10-26 Figure 10-4 Interface of analyzing possible neighboring GSM cells...............................................................10-28 Figure 11-1 Process of neighboring GSM/UMTS cell analysis.........................................................................11-6 Figure 12-1 Flow chart for frequency analysis...................................................................................................12-5 Figure 12-2 Flow chart for frequency optimization...........................................................................................12-6 Figure 12-3 Process of GSM frequency analysis...............................................................................................12-7 Figure 12-4 Frequency analysis interface (1)...................................................................................................12-27 Figure 12-5 Frequency analysis interface (2)...................................................................................................12-28 Figure 12-6 Frequency optimization interface.................................................................................................12-29 Figure 13-1 Process of GSM uplink interference analysis.................................................................................13-3 Figure 13-2 Interface for the overview of the uplink interference of cells......................................................13-15 Figure 13-3 Interface for the uplink interference analysis of a cell.................................................................13-16 Figure 14-1 Process of GSM VIP analysis.........................................................................................................14-4 Figure 15-1 Process of GSM complaint analysis support..................................................................................15-4 Figure 16-1 Process of GSM cell performance analysis....................................................................................16-3 Figure 17-1 State transition of a timing task......................................................................................................17-6 Figure 17-2 Integrated Task Management interface........................................................................................17-49 Figure 18-1 Workflow of uplink interference analysis......................................................................................18-4 Figure 18-2 Interface for the uplink-interference analysis of a cell.................................................................18-14 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Figures
Nastar Operator Guide Figure 19-1 Workflow of co-frequency neighboring cell analysis....................................................................19-5 Figure 19-2 UMTS co-frequency neighboring-cell analysis interface.............................................................19-18
Figure 20-1 Process of neighboring UMTS/GSM cell analysis.........................................................................20-5 Figure 21-1 Workflow of coverage analysis......................................................................................................21-3 Figure 21-2 Interface for the coverage analysis (1)..........................................................................................21-13 Figure 21-3 Interface for the coverage analysis (2)..........................................................................................21-14 Figure 21-4 Interface for the coverage analysis (3)..........................................................................................21-15 Figure 22-1 Process of UMTS VIP analysis......................................................................................................22-4 Figure 22-2 VIP analysis interface...................................................................................................................22-19 Figure 23-1 Process of UMTS complaint analysis support................................................................................23-5 Figure 24-1 Process of UMTS pilot pollution analysis......................................................................................24-4 Figure 24-2 Pilot pollution analysis interface.................................................................................................. 24-14 Figure 25-1 Process of UMTS cell performance analysis..................................................................................25-7 Figure 26-1 State transition of a timing task......................................................................................................26-6 Figure 26-2 Integrated Task Management interface........................................................................................ 26-49 Figure 27-1 Workflow of uplink interference analysis......................................................................................27-4 Figure 27-2 Interface for the uplink-interference-ranking analysis................................................................. 27-22 Figure 27-3 Interface for the uplink-interference-spectrum analysis...............................................................27-23 Figure 28-1 Workflow of co-frequency neighboring-cell analysis....................................................................28-5 Figure 28-2 Interface for the co-frequency neighboring cell analysis............................................................. 28-19 Figure 29-1 Workflow of complaint analysis support........................................................................................29-2 Figure 29-2 Interface for the complaint analysis support (1).............................................................................29-9 Figure 29-3 Interface for the complaint analysis support (2)...........................................................................29-10 Figure 30-1 Process of CDMA pilot pollution analysis.....................................................................................30-4 Figure 31-1 Process of CDMA coverage analysis.............................................................................................31-5 Figure 32-1 Process of CDMA cell performance analysis.................................................................................32-4 Figure 33-1 Workflow of VIP analysis..............................................................................................................33-3
xxiv
Issue 03 (2010-06-30)
Tables
Tables
Table 1-1 Functions supported by the GSM, CDMA, UMTS, and LTE networks..............................................1-2 Table 1-2 The description of the Nastar analysis functions.................................................................................1-3 Table 1-3 Modules of the server software............................................................................................................1-6 Table 1-4 Functional units on the network...........................................................................................................1-8 Table 1-5 Process of Nastar performance analysis.............................................................................................1-10 Table 2-1 Level 2 menu items in different network systems.............................................................................2-22 Table 2-2 GUI description of the Nastar client..................................................................................................2-25 Table 2-3 File menu............................................................................................................................................2-26 Table 2-4 Maintenance menu.............................................................................................................................2-27 Table 2-5 Security menu.....................................................................................................................................2-27 Table 2-6 Tool menu..........................................................................................................................................2-28 Table 2-7 System menu......................................................................................................................................2-28 Table 2-8 Window menu....................................................................................................................................2-28 Table 2-9 Help menu..........................................................................................................................................2-29 Table 2-10 Controls and corresponding keyboard shortcuts..............................................................................2-29 Table 2-11 Shortcut keys....................................................................................................................................2-30 Table 3-1 Server Monitor...................................................................................................................................3-10 Table 3-2 Hard Disk Monitor.............................................................................................................................3-12 Table 3-3 Database Monitor...............................................................................................................................3-14 Table 3-4 Service Monitor..................................................................................................................................3-15 Table 4-1 Parts of a .csv file...............................................................................................................................4-26 Table 7-1 Interface description: OSS management..............................................................................................7-6 Table 8-1 Tasks divided according to execution period.......................................................................................8-3 Table 8-2 Tasks Divided According to Task Features.........................................................................................8-4 Table 8-3 Description of the task description parameters....................................................................................8-4 Table 8-4 Mapping between the Nastar theme functions and the corresponding data types...............................8-8 Table 8-5 Description of the Integrated Task Management interface................................................................8-51 Table 8-6 Time parameters of a timing task.......................................................................................................8-62 Table 9-1 Relation between the quality levels of the received signals and bit error rate.....................................9-5 Table 9-2 Relation between the received levels and levels..................................................................................9-5 Table 9-3 Description of link balance levels........................................................................................................9-6 Table 9-4 Topic categories and relevant operation suggestions...........................................................................9-7 Table 9-5 Process of GSM MR analysis..............................................................................................................9-9 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
Tables
Nastar Operator Guide Table 9-6 Parameters related to the TRXs on the entire network (1).................................................................9-45 Table 9-7 Parameters related to the TRXs on the entire network (2).................................................................9-47 Table 9-8 Parameters related to the TRXs in a GBSC (1)..................................................................................9-48 Table 9-9 Parameters related to the TRXs in a GBSC (2)..................................................................................9-49 Table 9-10 Parameters related to the task information.......................................................................................9-50 Table 9-11 Parameters related to the cell information........................................................................................9-50 Table 9-12 Topic categories and relevant operation suggestions.......................................................................9-51 Table 9-13 Parameters related to the TRXs on the entire network (1)...............................................................9-53 Table 9-14 Parameters related to the TRXs on the entire network (2)...............................................................9-55 Table 9-15 Parameters related to the TRXs in a cell group (1)..........................................................................9-56 Table 9-16 Parameters related to the TRXs in a cell group (2)..........................................................................9-57 Table 9-17 Parameters related to the task information.......................................................................................9-58 Table 9-18 Parameters related to the cell information........................................................................................9-59 Table 9-19 Topic categories and relevant operation suggestions.......................................................................9-60 Table 9-20 Parameters related to the TopN TRXs (1)........................................................................................9-62 Table 9-21 Parameters related to the TopN TRXs (2)........................................................................................9-63 Table 9-22 Parameters related to the task information.......................................................................................9-64 Table 9-23 Parameters related to the cell information........................................................................................9-64 Table 9-24 Topic categories and relevant operation suggestions.......................................................................9-65 Table 9-25 Parameters related to the problematic TRXs involved in topic analysis (1)....................................9-67 Table 9-26 Parameters related to the TRXs involved in topic analysis (2)........................................................9-69 Table 9-27 Parameters related to the task information.......................................................................................9-70 Table 9-28 Parameters related to the cell information........................................................................................9-70 Table 9-29 Topic categories and relevant operation suggestions.......................................................................9-71 Table 9-30 Parameters related to querying TRXs in the MR analysis results of GSM cells.............................9-73 Table 9-31 Parameters related to querying TRXs in the MR analysis results of GSM cells (2)........................9-75 Table 9-32 Parameters related to the task information.......................................................................................9-76 Table 9-33 Parameters related to the cell information........................................................................................9-76 Table 9-34 Topic categories and relevant operation suggestions.......................................................................9-77 Table 10-1 Network changes and their impacts.................................................................................................10-4 Table 10-2 Process of GSM neighboring cell analysis.......................................................................................10-6 Table 11-1 Network changes and their impacts.................................................................................................11-4 Table 11-2 Parameters in the calculation of integrated priority.........................................................................11-5 Table 11-3 Process of neighboring GSM/UMTS cell analysis..........................................................................11-7 Table 12-1 Network changes and their impacts.................................................................................................12-4 Table 12-2 Process of GSM frequency analysis.................................................................................................12-8 Table 13-1 Process of GSM uplink interference analysis..................................................................................13-3 Table 14-1 Process of GSM VIP analysis..........................................................................................................14-5 Table 14-2 VIP group file...................................................................................................................................14-7 Table 15-1 Cause type and related description...................................................................................................15-3 Table 15-2 Description of GSM complaint analysis support process................................................................15-5 Table 15-3 Complaint subscriber IMSI file........................................................................................................15-6
xxvi
Issue 03 (2010-06-30)
Tables
Table 16-1 Description of the GSM cell performance analysis process............................................................16-4 Table 17-1 Tasks divided according to execution period...................................................................................17-3 Table 17-2 Tasks Divided According to Task Features.....................................................................................17-4 Table 17-3 Description of the task description parameters................................................................................17-5 Table 17-4 Description of the Integrated Task Management interface............................................................17-49 Table 17-5 Time parameters of a timing task...................................................................................................17-59 Table 18-1 Description of the workflow of uplink interference analysis...........................................................18-4 Table 18-2 Mapping between the E2E tasks and the analysis tasks...................................................................18-6 Table 19-1 Network changes and their impacts.................................................................................................19-4 Table 19-2 Description of the workflow of co-frequency neighboring cell analysis.........................................19-6 Table 19-3 Mapping between the E2E tasks and the analysis tasks...................................................................19-8 Table 20-1 Network changes and their impacts.................................................................................................20-4 Table 20-2 Process of neighboring UMTS/GSM cell analysis..........................................................................20-6 Table 20-3 Mapping between the E2E tasks and the analysis tasks...................................................................20-8 Table 21-1 Description of the workflow of coverage analysis...........................................................................21-3 Table 21-2 Mapping between the E2E tasks and the analysis tasks...................................................................21-5 Table 22-1 Process of UMTS VIP analysis........................................................................................................22-5 Table 22-2 VIP group file...................................................................................................................................22-7 Table 22-3 Mapping between the E2E tasks and the analysis tasks.................................................................22-10 Table 23-1 Cause type and related description...................................................................................................23-3 Table 23-2 Description of UMTS complaint analysis support process..............................................................23-5 Table 23-3 Complaint subscriber IMSI file........................................................................................................23-6 Table 24-1 Description of UMTS pilot pollution analysis process....................................................................24-4 Table 24-2 Mapping between the E2E tasks and the analysis tasks...................................................................24-6 Table 25-1 Exception Types and Functions.......................................................................................................25-2 Table 25-2 Description of the UMTS cell performance analysis process..........................................................25-8 Table 25-3 Mapping between the E2E tasks and the analysis tasks.................................................................25-10 Table 26-1 Tasks divided according to execution period...................................................................................26-3 Table 26-2 Tasks Divided According to Task Features.....................................................................................26-4 Table 26-3 Description of the task description parameters................................................................................26-5 Table 26-4 Description of the Integrated Task Management interface............................................................26-49 Table 26-5 Time parameters of a timing task...................................................................................................26-55 Table 27-1 Description of the workflow of uplink interference analysis...........................................................27-5 Table 27-2 Mapping between E2E tasks and analysis tasks..............................................................................27-8 Table 28-1 Description of the workflow of co-frequency neighboring-cell analysis.........................................28-6 Table 28-2 Mapping between E2E tasks and analysis tasks..............................................................................28-8 Table 29-1 Description of the workflow of complaint analysis support............................................................29-3 Table 30-1 Description of CDMA pilot pollution analysis process...................................................................30-4 Table 30-2 Mapping between E2E tasks and analysis tasks..............................................................................30-7 Table 31-1 Common scenario and solution........................................................................................................31-4 Table 31-2 Description of the CDMA coverage analysis process......................................................................31-5 Table 31-3 Mapping between E2E tasks and analysis tasks..............................................................................31-8 Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Tables
Nastar Operator Guide Table 32-1 Description of the CDMA cell performance analysis process.........................................................32-5 Table 32-2 Mapping between E2E tasks and analysis tasks..............................................................................32-7 Table 33-1 Description of the workflow of VIP analysis...................................................................................33-4 Table 33-2 Mapping between E2E tasks and analysis tasks..............................................................................33-8
xxviii
Issue 03 (2010-06-30)
1 Overview of the Nastar Performance Analysis System
Overview of the Nastar Performance Analysis System
About This Chapter

The iManager Nastar performance analysis system is located on the same network as the EMS of an operator. The iManager Nastar performance analysis system collects topic data of NEs through the EMS data center and provides performance analysis for network optimization. The optimization results of the performance analysis can be saved as files and sent to the CME of Huawei or a third-party data configuration tool through the EMS. Based on the optimization results, you can modify the relevant parameters by using the data configuration tool and send the modified parameters to NEs. 1.1 Introduction to the Nastar Performance Analysis System The Nastar performance analysis system is a system that performs localization and analysis of quality-related problems on the radio network. This system supports multiple performance analysis such as coverage analysis, neighboring cell analysis, uplink-interference analysis, frequency analysis, complaint analysis support, and VIP analysis. 1.2 Position of the Nastar on the network The Nastar is located in a distributed client/server network and is connected to the M2000. 1.3 Performance Analysis Process This section describes the performance analysis process.
Issue 03 (2010-06-30)
1-1
1.1 Introduction to the Nastar Performance Analysis System

The Nastar performance analysis system is a system that performs localization and analysis of quality-related problems on the radio network. This system supports multiple performance analysis such as coverage analysis, neighboring cell analysis, uplink-interference analysis, frequency analysis, complaint analysis support, and VIP analysis.
Overview
The traditional network analysis system monitors the running status of networks by monitoring alarm information and analyzing performance reports. It analyzes networks on the basis of the alarm information and performance measurement statistics on network elements (NEs). The alarm information and measurement statistics, however, both reflect the running status of networks from the perspective of NEs. Therefore, they cannot provide evidences for expert and thorough radio network analysis and optimization. The Nastar obtains the data containing the characteristics of the radio network and analyzes the data. The data includes the MRs of radio links, pilot frequency measurement strength indicator, neighboring cell measurement data, uplink interference data, and user call history records (CHRs). By analyzing the data, the Nastar helps in locating and analyzing network problems and provides auxiliary solutions to the problems.
Product Function
The Nastar performance analysis system can be used together with the parameter management system and performance report system. The Nastar performance analysis system can be used for the routine maintenance, planning, and optimization of the radio network. Table 1-1 lists the functions supported by the GSM, CDMA, UMTS, and LTE networks. Table 1-1 Functions supported by the GSM, CDMA, UMTS, and LTE networks Technology Coverage analysis Neighboring cell analysis Uplink interference analysis Frequency analysis Complaint analysis support VIP analysis Terminal performance analysis
1-2
GSM
CDMA
UMTS
LTE -
Issue 03 (2010-06-30)
Technology Cell performance analysis Neighboring GSM/UMTS cell analysis Neighboring UMTS/GSM cell analysis Pilot pollution analysis
GSM
CDMA -
UMTS -
LTE -
Table 1-2 describes the functions of the Nastar. Table 1-2 The description of the Nastar analysis functions Analysis function Coverage analysis Description The information about the radio links involved in a customer's call in the test cell is included in the MR. The information pertains to the coverage, quality, and subscriber distribution of the carrier and cell. Coverage analysis can help network maintenance engineers analyze and locate a large number of network problems, such as weak cell coverage, cross coverage, poor QoS, imbalance between uplink and downlink. This function is performed to analyze neighboring cells based on the MRs of the actual calls of all the subscribers in the test cell. It supports the analysis of defined and undefined neighboring cells. It helps to identify and handle the problems, including redundant and missing neighboring cell configuration of a cell and improper priorities of neighboring cells. In addition, it can be performed to solve network QoS problems caused by redundant or missing neighboring cell configuration. In addition to intra-RAT neighboring cell analysis, the Nastar supports the neighboring cell analysis between the GSM network and the UMTS network, and between the GSM network and the TD-SCDMA network.
Neighboring analysis
Issue 03 (2010-06-30)
1-3
Analysis function Uplink interference analysis
Description This function is performed to analyze whether the values of the main and diversity Received Signal Strength Indicators (RSSIs) of the transmit and receive channels of a BTS are normal. Based on the display and analysis in the time domain, it helps Nastar operators analyze and identify reverse interference signal sources, and thus initially locate the BTS that is being interfered with and the cause of the interference. This function can be performed to analyze and identify interference in the frequency domain and help Nastar operators select the frequencies experiencing light interference. This function is performed to evaluate the impact of GSM frequency planning and analyze the cells and Absolute Radio Frequency Channel Numbers (ARFCNs) experiencing severe interference on the current network. If cells and ARFCNs experiencing server interference are detected during drive test (DT) analysis and traffic analysis, this function can be performed to find the frequencies that can be replaced. Therefore, network interference is decreased and network QoS is improved. Based on the interference traffic sequence of the available ARFCNs in an expansion cell, this function can also be used to find out the optimal frequencies to be added to the expansion cell. This is a basis for preparing a frequency plan for the network. Whenever terminal subscribers encounter network-related problems, they lodge a complaint with the operators. After receiving a complaint, the operator can perform this function to obtain the CHRs pertaining to the mobile user concerned. Then, the operator can analyze the cause of the problem and then locate and solve the problem. This helps to improve the efficiency of handling complaints, thus improving user satisfaction. This function is performed to filter the call records of VIP subscribers from the CHRs of the entire network and obtain the KPIs of the voice and data services of VIP subscribers. The KPIs include call drop rate, call setup delay, and forward and reverse data rate. By monitoring the QoS of VIP subscribers each day, the Nastar operators can find out the potential complaints of VIP subscribers and solve them in advance to ensure that network problems do not arise. This helps to provide better services for the VIP subscribers and improve their satisfaction. In addition, the Nastar can identify the regions and cells where the call activities of VIP subscribers are frequent based on the CHRs of the VIP subscribers. These cells are considered VIP cells. Mobile operators can ensure the performance of these cells to guarantee the QoS of VIP subscribers.
Frequency analysis
Complaint analysis support
VIP analysis
1-4
Issue 03 (2010-06-30)
Analysis function Pilot pollution analysis
Description The network systems based on the code division multiple access (CDMA) technology are self-interfered systems, in which interference seriously affects the performance and capacity of the network systems. In addition, the eliminating the interference caused by pilot pollution is crucial to the interference handling in the network systems. The Nastar provides the pilot pollution analysis based on actual calls, thus reducing DTs and improving the accuracy of problem location. Through the pilot pollution analysis function, the Nastar analyzes the cells where pilot pollution exists, the cells that cause interference, and the interference strength and displays the analysis results on a map. Users can collect statistics of KPIs such as call drop rate, access success rate, and handover success rate based on terminal models from the CHR data of the entire network. The Nastar can compare the performance data of the terminals and provide useful reference information for network operation and troubleshooting.
Terminal performance analysis
Software Architecture
As shown in Figure 1-1, the software architecture of the Nastar performance analysis system is divided into two parts:
l l
Server software Client software
Figure 1-1 Software modules of the Nastar
Figure 1-2 shows the modules of the server software of the Nastar.
Issue 03 (2010-06-30)
1-5
Figure 1-2 Modules of the server software of the Nastar
As shown in Figure 1-2, the server software of the Nastar consists of many functional modules. Through the CORBA software bus, these modules communicate with each other and also communicate with the corresponding modules of the client software. In addition, these modules access the server database of the Nastar through the database interface to perform operations on the database. Table 1-3 describes the modules. Table 1-3 Modules of the server software Module Name Task management subsystem Data processing subsystem Function The task management subsystem supports the functions of viewing and operating thematic analysis tasks. The task management subsystem is used to manage and maintain all the tasks of the entire system.
l
Supports the functions of collecting, parsing, importing, and preprocessing the original data and generating data that is suitable for service analysis. Supports the functions of managing, deleting, and backing up the original data. Supports the functions of managing, importing, and exporting the results of performance analysis.
Service analysis subsystem
Supports the functions of topic analysis tasks and displaying the performance analysis results on the client.
The client of the Nastar provides a graphical user interface (GUI) for you to perform topic analysis. The modules corresponding to the task management subsystem and service analysis subsystem are provided on the client to enable you to gain access to these two subsystems.
1-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
1.2 Position of the Nastar on the network

The Nastar is located in a distributed client/server network and is connected to the M2000. Figure 1-3 shows the position of the Nastar on the network. Figure 1-3 Position of the Nastar on the network
The communication between the functional units on the network is based on the TCP/IP protocol. The Nastar server and the M2000 must be in the same local area network (LAN), and their IP addresses must be on the same network segment. Table 1-4 describes the functional unities in the network.
Issue 03 (2010-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-7
Table 1-4 Functional units on the network Function Nastar Application Scenarios One of the multi-user telecommunication platforms developed by Huawei. It implements performance analyses such as coverage analysis, frequency analysis, neighboring cell analysis, uplink interference analysis, and user complaint auxiliary analysis for the radio network. Service Aware Unit. It implements the communication between operation and maintenance (OM) terminals and other boards of the base station controller. The main functions of the SAU are as follows:
l l l
SAU
Downloading data from the base station controller Pre-processing data and saving the pre-processed data Uploading the pre-processed data
For the base station controller, an extra SAU board is required for pre-processing the data required by the Nastar on the GSM/UMTS/ CDMA/TD-SCDMA network. For the OSS, an extra SAU server is required by the Nastar on the LTE network. Huawei M2000 A uniform management platform of Huawei mobile network. It manages the mobile NEs manufactured by Huawei. Connecting to the Nastar, it provides performance data, configuration data, pre-processed CHR data, and pre-processed MR data for the Nastar through FTP. Wireless Multiple wireless networks including GSM, UMTS, CDMA, TDSCDMA, and LTE networks.
NOTE
The SAU of the Nastar V600R008 (LTE technology) is deployed on the OSS side as a server, and thus it is not present in the preceding networking diagram.
1.3 Performance Analysis Process

This section describes the performance analysis process. Figure 1-4 shows the process of Nastar performance analysis.
1-8
Issue 03 (2010-06-30)
Figure 1-4 Process of Nastar performance analysis

Start Set a performance data collection task
Set an E2E task
Set an analysis data collection task
Set a data import task
Set the engineer parameters import task Set a performance analysis task View the analysis results of the task (Optional) Send the optimization results to the data configuration tool End
Table 1-5 describes the process of Nastar performance analysis.
Issue 03 (2010-06-30)
1-9
Table 1-5 Process of Nastar performance analysis Seria l No. 1 Procedure Create a configuration data collection task Description After the system installation is complete, the administrator can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a configuration data collection task. After the task is created, the Nastar periodically obtains the required configuration data from the NMS and saves the data as files on the Nastar server for future analysis. The administrator needs to create a periodic configuration data collection task when the Nastar is used for the first time. 2 Create an end-toend task You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task. After the task is created, the Nastar issues MML commands to the NMS, and then NMS issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a collection task corresponding to the analysis task. After the task is created, the Nastar periodically obtains the required performance data, uplink frequency scanning data, measurement data, and call records from the NMS, and saves the data as files on the Nastar server. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a data import task corresponding to the analysis task. After the task is created, the Nastar periodically imports the required files saved on the Nastar server, such as configuration data, performance data, uplink frequency scanning data, measurement data, and call records, to the database. You can create an engineer parameters import task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar imports the engineering parameters to the database. You can create a performance analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required performance data, uplink frequency scanning data, measurement data, and call records from the Nastar database, and then generates an analysis report through the analysis. You can view the results of the performance analysis tasks that are successfully performed after querying the analysis report.
Create a task for collecting the analysis data
Create a data import task
Create an engineer parameters import task Create a performance analysis task
View the results of a performance analysis task
1-10
Issue 03 (2010-06-30)
Seria l No. 8
Procedure Send the optimization results to the data configuration tool (optional)
Description The Nastar provides the function of exporting certain performance analysis optimization results as files. You can manually send the files to the Huawei data configuration tool. After checking the optimization results, the data configuration tool applies the optimization results to NEs.
Issue 03 (2010-06-30)
1-11
2 Getting Started
2
About This Chapter
Getting Started
This section describes the GUIs of the client of the Nastar performance analysis system and the common operations on the GUIs. 2.1 Logging In to the Nastar This section describes how to log in to the Nastar server, and how to log out the current user add exit the Nastar client. 2.2 Changing the Password of the Current User This section describes how to change the password of your account. It is suggested that you should change the password periodically to improve the password security of your account. 2.3 Customizing the Client GUI Effect You can customize the GUI effect of the Nastar client as required. 2.4 Locking the Client You can lock the client to prevent unauthorized operations. 2.5 Unlocking the Client This section describes how to unlock the locked Nastar client. 2.6 Broadcast Messages The broadcast message function includes setting the broadcast parameter and sending the broadcast message. The broadcase message function of the Nastar enables you to send messages to other users with ease. 2.7 Displaying the Current Window in Full Screen Mode You can use full-screen display to hide the menu bar, toolbar, output window, and status bar, thus expanding the display area of the main window. 2.8 Setting the Alarm Sound at Network Disconnection On the Nastar client, you can set the alarm sound. The sound is played by the sound box connected to the client when the Nastar client is disconnected from the network. 2.9 Checking Whether the Client Needs Upgrade You can perform this operation to check whether the version of the client matches that of the server. If the versions do not match, you must upgrade the client.
2 Getting Started
2.10 Setting the Interval of Client Upgrade Check After the server is upgraded, the server version and the client version do not match. Therefore, the client has to be upgraded accordingly. After the interval for upgrade checking is set, the Nastar periodically checks whether the client needs to be upgraded. 2.11 Managing the Nastar License Nastar licenses can restrict the number of manageable devices, and the availability duration of the Nastar. You need to manage the licenses periodically. 2.12 Engineering Parameter Management This section describes the project parameter management. The Nastar performance analysis system provides the function of managing project parameters for users. You can import project parameters according to the template as required, which facilitates the project implementation, network analysis, and network optimization, and guides the future construction based on the learned experience. 2.13 Creating Custom NE Groups This section describes how to create custom NE groups. The Nastar client provides the functions of creating, modifying, deleting, importing, and exporting custom NE groups. You can add certain NEs to an NE group so that the performance analysis can be performed for all the NEs in an NE group. 2.14 Querying NE Data The Nastar provides the function of querying NE data. Before creating an analysis task, you can check whether the data related to this analysis task has been imported into the Nastar database by querying the data, and check the time of the imported data. The information is the basis for the analysis task. 2.15 Reference for the Performance Analysis System GUI This section describes the parameters of the client of the Nastar performance analysis system, such as the parameters related to the client login. You can refer to the description for better operations on the Nastar client. 2.16 FAQs about the Client Operations This section describes how to rectify faults on client operations.
2-2
Issue 03 (2010-06-30)
2 Getting Started
2.1 Logging In to the Nastar

This section describes how to log in to the Nastar server, and how to log out the current user add exit the Nastar client. 2.1.1 Login Modes You can log in to the Starter Application client in Online mode or Offline mode. In online login mode, the Lightweight Directory Access Protocol (LDAP) server authenticates the entered user name and password. If no LDAP server is provided, you can log in to the client in offline mode. In this case, the Nastar server authenticates the login information. 2.1.2 Login Process Describes the procedure and precautions for logging in to the Nastar application program in Online Mode or Offline Mode.
2.1.1 Login Modes

You can log in to the Starter Application client in Online mode or Offline mode. In online login mode, the Lightweight Directory Access Protocol (LDAP) server authenticates the entered user name and password. If no LDAP server is provided, you can log in to the client in offline mode. In this case, the Nastar server authenticates the login information. The following describes the differences between Online mode and Offline mode. Mode User Name and Passwo rd Required . Authentication Description
Online mode
When you log in to the Starter Application client, the LDAP server authenticates the user name and password. When you log in to the Nastar application client, the Nastar server authenticates the user name and password.
Log in to the executed application by using the user name and password that are used to log in to the Starter Application client.
Offline mode
No required. Log in to the client directly.
The Nastar server authenticates the user name and password.
On the Starter Application client, when you log in to the Nastar application for the first time, the application remembers the user name and password. Thus, when you log in next time, the user name and password are entered automatically.
Issue 03 (2010-06-30)
2-3
2 Getting Started
2.1.2 Login Process

Describes the procedure and precautions for logging in to the Nastar application program in Online Mode or Offline Mode.
Online Mode
Describes the procedure and precautions for the operations in Online Mode.
Prerequisite
l l l
Workstations and servers are created on the single sign-on (SSO) client. The Lightweight Directory Access Protocol (LDAP) server to be logged in to runs normally. Adjust the values of the base and user configuration items in client\plugins \startapplication\style\conf\config.xml on the client. Ask the LDAP server administrator for the values of the configuration items. Make sure that the user is the same as that authenticated by the LDAP server.
Context
After the first successful login, the SSO client records the username and password used for the login. When the user attempts to log in to another server without logging out, the username and password are directly used for the login. This saves the user from entering the username or password when logging in to another client.
Procedure
Step 1 Run the SSO client software. In the Login dialog box, select an LDAP server from the server list. If no LDAP server information is available in the server list, you need to add server information to the list. 1. 2. 3. In the Login dialog box, click In Server List, click Add. In the Add Server Information dialog box, enter the name, host name (IP address), port number, and communication mode of the Nastar server.
NOTE
to the right of Server.
The Server List dialog box appears.
If the communication mode is set to Security(SSL), the communication mode of the client is set to Secure Socket Layer (SSL).
4.
Click OK in the Add Server Information dialog box and then in the Server List dialog box to go back to the Login dialog box.
Step 2 In the Login dialog box, select an LDAP server, enter the username and password for logging in to the server, and click Login. Step 3 On the SSO client, select a workstation and double-click the icon of the server to be logged in to.
2 Getting Started
Log in to the server represented by the server icon. ----End
Result
After the first successful login, the SSO client records the username and password used for the login. When the user attempts to log in to another server without logging out, the username and password are directly used for the login.
Offline Mode
Describes the procedure and precautions for the operations in Offline Mode.
Prerequisite
Workstations and servers are created on the single sign-on (SSO) client.
Context
After the first successful login to the server created on the SSO client, the SSO client records the username and password used for the login. Thus, the user acts as an SSO user. When the user attempts to log in to another server without logging out, the username and password are directly used for the login. This saves the user from entering the username and password when logging in to another client.
Procedure
Step 1 Run the SSO client software. In the Login dialog box, click Offline Mode. The lower-right corner of the SSO client screen indicates that no user logs in. See . Step 2 On the SSO client, select a workstation and double-click the icon of the server to be logged in to. The SSO client starts the Nastar application program represented by the server icon. In the login dialog box, enter the name of the server that the Nastar application program is to log in to and the corresponding username and password. When the login succeeds, the SSO client records the used username and password. Step 3 Return to the SSO client and double-click another server icon.
l l
The user logs in to the server without entering the username and password. The lower-right corner of the SSO client screen indicates that the user logs in. For example, if the login username is Administrator, the login status shown in is displayed.
----End
Result
After the first successful login to the server created on the SSO client, the SSO client records the username and password used for the login. Thus, the user acts an SSO user. When the user
2 Getting Started
attempts to log in to another server without logging out, the username and password are directly used for the login.
2.2 Changing the Password of the Current User

This section describes how to change the password of your account. It is suggested that you should change the password periodically to improve the password security of your account.
Context
The new password must comply with the password policy. For details on how to set the password policy, see 4.2.3 Setting the Password Policy.
Procedure
Step 1 Choose File > Change Password from the main menu. Step 2 In the Change Password dialog box, set the new password for the current user. Step 3 Click OK. Step 4 In the dialog box, click OK. ----End
2.3 Customizing the Client GUI Effect

You can customize the GUI effect of the Nastar client as required. 2.3.1 Setting the Font Size You can set the font size on the Nastar client. 2.3.2 Setting the Information Output Area The output window is at the bottom of the Nastar client. It displays the prompt messages and feedback information of the events that affect the running of the Nastar. 2.3.3 Setting the Number Format of the Client You can customize the number display format of the client, such as, the display mode of the system monitoring data. 2.3.4 Setting the Time and Date Formats of the Client You can set the time format, time mode, and date format that are displayed on the client. 2.3.5 Setting the Toolbar You can perform this task to set the shortcut buttons shown on the toolbar.
2.3.1 Setting the Font Size

You can set the font size on the Nastar client.
Context
After you set the font size, you need to log in to the Nastar client again for the setting to take effect.
2 Getting Started
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 From the navigation tree on the left of the Preferences window, select Font. Step 3 Select an option in Font Size.
NOTE
Font Size can be as follows:

l l l
Small: The font size is 11 pounds. Middle (Default): The font size is 12 pounds. Large: The font size is 13 pounds.
Step 4 Click OK. ----End
2.3.2 Setting the Information Output Area

The output window is at the bottom of the Nastar client. It displays the prompt messages and feedback information of the events that affect the running of the Nastar.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 From the navigation tree on the left of the Preferences window, select Output Window. Step 3 Set relevant parameters in the Output Window area, and then click OK. Step 4 You can perform the following operations in the information output area at the bottom of the interface. Option Copy Description 1. Choose the displayed output information. 2. Right-click and choose Copy to copy the information to the clipboard. Select All 1. Right-click in the output window and choose Select All. 2. Right-click again and choose Copy to copy all the displayed output information to the clipboard. Clear Right-click in the output window and choose Clear to clear all the displayed output information.
Issue 03 (2010-06-30)
2-7
2 Getting Started
Option Find
Description 1. Right-click in the output window and choose Find. 2. In the Find dialog box, type the key words to be searched for in Find what.
NOTE
l Match: To set whether the search content is case sensitive. The
default is case insensitive.

l Match whole word only: To perform a fuzzy search, clear
Match whole word only. To perform a precise search, select Match whole word only.
l Direction: To set the direction for a key word search.
Save As
Right-click to choose Save As. In the Save dialog box, save the current output to a .txt file. Right-click in the output window and choose Auto Scroll. The output information scrolls automatically to the latest information. Right-click in the output window again and choose Auto Scroll, the auto scroll is disabled. Right-click in the output window and choose Parameter Settings. The Output Window pane is displayed in the Preferences window.
Auto Scroll
Parameter Settings
----End
2.3.3 Setting the Number Format of the Client

You can customize the number display format of the client, such as, the display mode of the system monitoring data.
Context
l l
The settings take effect after you log in to the client again. After you modify the number settings, the display of the number may be changed. You can view the display effect in the Positive number text box and Negative number text box.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences dialog box, select Number from the navigation tree on the left. Step 3 Set the number display format in the Number Settings area.
2-8
Issue 03 (2010-06-30)

NOTE
2 Getting Started
l l l
Digits of decimal fraction: number of digits after the decimal. The value ranges from 0 to 3, and the default value is 2. Number separator: whether to use comma (,) to group the integer part of a number. The value can be null or comma. Start with 0: whether to add 0 before the decimal point. By default, 0 is added before the decimal point.
2.3.4 Setting the Time and Date Formats of the Client

You can set the time format, time mode, and date format that are displayed on the client.
Setting the Time Format of the Client

This section describes how to set the time format of the client.
Context
l
After you set the time format, you need to log in to the client again for the settings to take effect. Next time when you log in to the client, the Nastar client automatically uses the settings that you set last time. The time display effect that you set is displayed in the Time Format Notation area.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 From the navigation tree on the left of the Preferences window, expand the Region Settings node and choose Time. Step 3 In the Time Settings group box, set the time format. Step 4 Click OK. ----End
Setting the Date Format of the Client

This section describes how to set the date format of the client.
Context
l
After you set the date format, you need to restart the Nastar client again for the settings to take effect. Next time when you log in to the client, the Nastar client automatically uses the settings that you used last time. The date display effect that you set is displayed in Appearance Example.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-9
Issue 03 (2010-06-30)
2 Getting Started
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the navigation tree on the left of the Preferences window, expand the Region Setting node and select Date. Step 3 In the Date group box, set the date format.
NOTE
l l
Date Separator: symbol to separate the date. There are three symbols for you to select: "/", "-", and ".". The default is "/". Date Format: display format of the date. It can be set to "yyyy/MM/dd", "dd/MM/yyyy", or "MM/dd/ yyyy". The default is "MM/dd/yyyy".
Setting the Time Mode of the Client

This section describes how to set the time mode of the client to determine whether the time is displayed according to the Nastar server time or the NE time.
Context
The settings take effect after you log in to the client again.
l
After you set the time mode, you need to restart the Nastar client for the settings to take effect. Next time when you log in to the client, the Nastar client automatically uses the settings that you used last time.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the navigation tree on the left of the Preferences window, select Time Mode. Step 3 In the Time Mode group box, select Time Mode.
NOTE
l l
Server time mode: If you select this mode, the alarms are queried according to the server time. Client time mode: If you select this mode, the alarms are queried according to the client time. You are advised to retain the default value Client time mode.
2.3.5 Setting the Toolbar

You can perform this task to set the shortcut buttons shown on the toolbar.
2 Getting Started
Procedure
Step 1 Choose File > Custom Toolbar from the main menu. Step 2 In the Customize Toolbar dialog box, select System in the Toolbar Groups group box. Step 3 Click Advanced. The Toolbar dialog box displays the Toolbar Buttons group box.
NOTE
The Toolbar Buttons group box consists of two parts: Usable Tools and Customized Tools. All the buttons in Customized Tools are displayed on the toolbar, and the buttons in Usable Tools are not displayed on the toolbar. Click Advanced again. The Toolbar Buttons group box is hidden. Click Reset All to restore the Customized Tools to the initial state so that you can reset the toolbar. Click Reset to restore the toolbar buttons of the selected toolbar group to the initial state so that you can reset the toolbar buttons.
l l l
Step 4 In the Toolbar Buttons group box, set the buttons you want to display on the toolbar. l In the Usable Tools group box, select one button or hold down Ctrl or Shift to select multiple buttons you want to display. Click Customized Tools group box. l buttons you do not want to display. Click Usable Tools group box. Step 5 Click OK. ----End to move the selected buttons to the
In the Customized Tools group box, select one or hold down Ctrl or Shift to select multiple to move the selected buttons to the
2.4 Locking the Client

You can lock the client to prevent unauthorized operations.
Context
l l
This function is applicable to only the local client. In the Preferences dialog box, select Visible on Terminal Lock in the Locking Settings area. Thus, after the client is locked, the main window of the client is visible.
Procedure
Step 1 Choose File from the main menu to set the client to be locked manually or automatically. Step 2 The following table describes how to set the client to be locked manually or automatically.
Issue 03 (2010-06-30)
2-11
2 Getting Started
Lock Mode Automatically
Operations If the client does not receive any operation commands within the specified period, it can be locked automatically. To enable this function, perform the following operations: 1. Choose File > Preferences. 2. Select Lock Settings in the navigation tree in the left pane of the Preferences dialog box. In the Locking Interval area, select Automatically Locked. 3. Enter the lock time for the Automatically Locked mode. 4. Click OK. 5. In the Information dialog box, click OK. The client is locked automatically when the specified time arrives.
Manually
If you do not perform operations on the Nastar client for a period, you can lock the client to prevent others from performing illegal operations on the Nastar client. You can lock the client manually by using the following method:
l l
Choose File > Lock Terminal from the menu bar. Click on the toolbar.
----End
2.5 Unlocking the Client

This section describes how to unlock the locked Nastar client.
Context
CAUTION
If your user account is in the Administrators user group and you unlock a user account of someone else, the unlocked account is logged out, and the previous operation data is lost. If you unlock your own account, the Nastar becomes operable after the account is unlocked.
Procedure
Step 1 When the client is locked, press Ctrl+Alt+U. Step 2 In the Unlock dialog box, enter the user name and the password, and then click OK. ----End
2 Getting Started
2.6 Broadcast Messages

The broadcast message function includes setting the broadcast parameter and sending the broadcast message. The broadcase message function of the Nastar enables you to send messages to other users with ease. 2.6.1 Setting Broadcast Parameters Setting the broadcast parameters on the Nastar client refers to setting the number of latest messages and the total number of stored messages, that is, setting the number of broadcast messages to be displayed on the client and the total number of broadcast messages to be cached in the server. 2.6.2 Sending Broadcast Messages This section describes how to send broadcast messages from the client.
2.6.1 Setting Broadcast Parameters

Setting the broadcast parameters on the Nastar client refers to setting the number of latest messages and the total number of stored messages, that is, setting the number of broadcast messages to be displayed on the client and the total number of broadcast messages to be cached in the server.
Context
The task of the following procedure is to set broadcast parameters and apply them to the current client.
Procedure
Step 1 Choose Tools > Broadcast Message from the main menu. Step 2 In the Broadcast Message dialog box, click Options. Step 3 In the Broadcast Messages Options dialog box, enter the values in Displayed message count and Saved message count, click Save. Step 4 Click OK. ----End
2.6.2 Sending Broadcast Messages

This section describes how to send broadcast messages from the client.
Context
l
A client can receive the broadcast messages sent by itself. A message is displayed in the output window. You have the permissions to set broadcast message parameters and send broadcast messages. The online Nastar client can receive the broadcast messages.
Issue 03 (2010-06-30)
2 Getting Started
Procedure
Step 1 Choose Tools > Broadcast Message from the main menu. Step 2 In the Broadcast Message dialog box, enter the message content in the Sending message field.
NOTE
l l
A broadcast message cannot be null, and cannot exceed 128 characters. The system automatically adds line feeds according to the length of broadcast messages.
Step 3 Click Send. When the sending is complete, the Message dialog box is displayed on other clients. Users can click Detail to view the message. Step 4 In the Information dialog box, click OK. ----End
2.7 Displaying the Current Window in Full Screen Mode

You can use full-screen display to hide the menu bar, toolbar, output window, and status bar, thus expanding the display area of the main window.
Context
Press Esc to exit the full-screen mode.
Procedure
on the toolbar. Step 1 Click to switch to the full-screen mode. ----End
2.8 Setting the Alarm Sound at Network Disconnection

On the Nastar client, you can set the alarm sound. The sound is played by the sound box connected to the client when the Nastar client is disconnected from the network.
Context
The sound files of the Wav type can be recorded in two formats: PCM and Microsoft ADPCM. The sound files used for prompting network disconnection support only the sound files of the Wav type in the PCM format.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences dialog box, select Disconnection Sound from the navigation tree on the left. Step 3 In the Disconnection Sound group box, select Enable.
2 Getting Started
Step 4 Click Step 5 Click
. In the Open dialog box, select a sound file, and then click Open. to play the sound.
2.9 Checking Whether the Client Needs Upgrade

You can perform this operation to check whether the version of the client matches that of the server. If the versions do not match, you must upgrade the client.
Context
If the Nastar server is upgraded but the client is not upgraded, it may cause the version of the client does not match that of the server.
Procedure
Step 1 Choose Help > Check For Upgrades from the main menu to check whether the client version matches the server version. l l When the versions match, the client does not need to be upgraded. In this case, click OK. When the versions do not match, you must upgrade the client. In this case, perform the following operations to upgrade the client: 1. 2. 3. ----End Click OK. In the Update Wizard: Update Applications window, click Continue. The upgrade progress is displayed. In the Update Wizard: Update Applications window, click Finish.
2.10 Setting the Interval of Client Upgrade Check

After the server is upgraded, the server version and the client version do not match. Therefore, the client has to be upgraded accordingly. After the interval for upgrade checking is set, the Nastar periodically checks whether the client needs to be upgraded.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences dialog box, in the navigation tree on the left, select Upgrade. Step 3 Select the interval for upgrade checking in the Upgrade area. Step 4 Click OK. ----End
2 Getting Started
2.11 Managing the Nastar License

Nastar licenses can restrict the number of manageable devices, and the availability duration of the Nastar. You need to manage the licenses periodically. 2.11.1 Querying the Nastar License This section describes how to query the license file on the Nastar server through the Nastar client. 2.11.2 Updating the Nastar License This section describes how to replace the Nastar license file on the Nastar server through the client.
2.11.1 Querying the Nastar License

This section describes how to query the license file on the Nastar server through the Nastar client.
Procedure
Step 1 Choose Help > License Management > License Information from the main menu. Step 2 In the License Information dialog box, query the license information about resources and functions on the Resource control item and Function control item tabs. ----End
2.11.2 Updating the Nastar License

This section describes how to replace the Nastar license file on the Nastar server through the client.
Prerequisite
When updating a license, delete the license files that are not in use from the server directories license and licensebak, and then update the license.
Context
l l l
The type of the license applied for must be consistent with the version type. Before the licenses expire, the Nastar displays a warning periodically. The valid time for the license that is uniformly used in Nastar contains two fields: Expiry (Days) and End Time. If both the fields exist, the value of Expiry(Days) is valid.
Procedure
Step 1 Choose Help > License Management > License Information from the main menu. Step 2 In the License Information dialog box, click Update License. Step 3 In the Open dialog box, select the new license file, and then click Open.
2 Getting Started
Step 4 In the License Comparison Results dialog box, view the changes of the licenses, and then click OK. ----End
2.12 Engineering Parameter Management

This section describes the project parameter management. The Nastar performance analysis system provides the function of managing project parameters for users. You can import project parameters according to the template as required, which facilitates the project implementation, network analysis, and network optimization, and guides the future construction based on the learned experience. 2.12.1 Importing/Exporting Engineering Parameters This section describes how to import and export engineering parameters. You can export the engineering parameters in .csv, .xls, or .xlsx files to the Nastar database, which provides reference for certain algorithms of the performance analysis and for assistant analysis. You can also export all the engineering parameters in the Nastar database as .csv or .xls files to facilitate the query and management of engineering parameters. 2.12.2 Querying Engineering Parameters This section describes how to query engineering parameters. You can query the information about the imported engineering parameters of NEs.
2.12.1 Importing/Exporting Engineering Parameters

This section describes how to import and export engineering parameters. You can export the engineering parameters in .csv, .xls, or .xlsx files to the Nastar database, which provides reference for certain algorithms of the performance analysis and for assistant analysis. You can also export all the engineering parameters in the Nastar database as .csv or .xls files to facilitate the query and management of engineering parameters.
Prerequisite
l l
You have logged in to the Nastar client. You are authorized to manage the engineering parameters.
Context
The engineering parameters include mainly the cell engineering information, geographical information, and key configuration information. The engineering parameters can be imported to the database to provide reference for certain algorithms of the performance analysis and for assistant analysis. The engineering parameter template files in .csv, .xls, and .xlsx formats can be imported. To open .xlsx files, you must install Microsoft Office 2007.
Procedure
Step 1 Choose Function List > System Function > Engineering parameter management from the navigation tree in the Analysis Task Management window. Step 2 Import or export engineering parameters as required.
2 Getting Started
If You Want to ... Import engineering parameters Export engineering parameters
Then ... Perform Step 3. Perform Step 4.
Step 3 Perform the following operations to import engineering parameters: 1. In the Engineering parameter management window, click the *** engineering parameters tab and then click Import. *** refers to the network system such as GSM, CDMA, UMTS, or TD-SCDMA. 2. In the displayed Open dialog box, select an engineering parameter file, and then click Open. If an engineering parameter file in .xls or .xlsx format is selected and the file contains multiple worksheets, a prompt is displayed for you to select the worksheet to be imported. 3. Configure the column headers.
l
At the header of each column, you can 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 number/ configured columns headings/column headings in the engineering parameter file.
The column headers marked with the * character must be configured. Otherwise, the import operation is not allowed. If you need to modify an incorrectly configured column header, right-click the column header, clear the check box next to the original header, and then reconfigure the header. GSM system
The number of digits in the BCC and NCC values cannot exceed two. The values of the BCC, NCC, MNC, and MCC must not be null and must be unique. The values of LACs and CIs of two different cells cannot be both the same. Otherwise, the engineering parameter file cannot be imported to the database. It is recommended that the BCCH, BCC, NCC, and CGI information regarding each cell in the engineering parameters be the same as that in the configuration parameter files. Otherwise, cells cannot be accurately located during neighboring cell analysis or frequency analysis.
CDMA system The values of MSC ID, cell ID, and sector ID of a carrier must not be null. The values of MSC ID, cell ID, and sector ID of two different carriers cannot be all the same. Otherwise, the engineering parameter file cannot be imported to the database.
UMTS system The values of RNC ID and cell ID of a cell must not be null. The values of RNC ID and cell ID of two different cells cannot be both the same. Otherwise, the engineering parameter file cannot be imported to the database.
TD-SCDMA system The values of RNC ID and Cell ID of a cell must not be null. The values RNC ID and Cell ID of two different cells cannot be both the same. In addition, the RNC ID and Cell ID in the engineering parameters must be the same as those in the configuration
2-18
Issue 03 (2010-06-30)
2 Getting Started
parameter file. Otherwise, the engineering parameter file cannot be imported to the database. 4. 5. 6. Click OK. In the displayed Confirm dialog box, click OK after checking the number of added records, updated records, and failed records. Perform the operations as prompted.
l l
If the imported information is correct, click Close. If certain abnormal records exist in the imported information, the records that fail to be imported are highlighted in red.
Click Export Fail Record to export the failed records as a file so that you can make modifications based on the error information to complete the current import task. Click Close to complete the current import task.
Step 4 Perform the following operations to export engineering parameters: 1. In the Engineering parameter management window, click the *** engineering parameters tab and then click Export. *** refers to the network system such as GSM, CDMA, UMTS, or TD-SCDMA. Set a file name and specify the save path and file type in the displayed Save dialog box, and then click Save.
2.
----End
2.12.2 Querying Engineering Parameters

This section describes how to query engineering parameters. You can query the information about the imported engineering parameters of NEs.
Prerequisite
l l
You have logged in to the Nastar client. You have imported engineering parameters.
Procedure
Step 1 From the navigation tree in the left pane of the Analysis Task Management window, choose Function List > System Function > Engineering Parameter Management. Step 2 In the Engineering Parameter Management window, click the *** Engineering Parameters tab, and query the engineering parameter information about each NE.
l l
*** represents a network technology. It can be GSM, CDMA, or UMTS. By default, the engineering result list displays all the engineering parameter information that has been imported to the database. To view the required engineering parameter information, you can deselect all the objects in the left NE object navigation tree and then select the objects that you want to view. The system enables you to search for the objects in the navigation tree. You can right-click in the navigation area and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the objects that meet the search condition. You can select Case sensitive to ensure that the typed keywords are case sensitive.
Issue 03 (2010-06-30)
2-19
2 Getting Started
You can select Up or Down in the Direction area to define the search area. Step 3 Check engineering parameters. 1. 2. 3. Click Configuration Check. The Save dialog box is displayed. Set the path for saving the check result and the format of the check result file. Click Save. The system opens the check result automatically. The check result file contains three sheets.
l
The Engineering Parameter Only sheet displays the cells that are present in only the engineering parameter data. The Configuration Only sheet displays the cells that are present in only the configuration data. The Engineering Parameter and Configuration Shared sheet displays the cells that are present in both the engineering parameter data and the configuration data.
----End
Postrequisite
l
Delete engineering parameter. In the engineering parameters list on the right, select the engineering parameters to be deleted, and then click Delete. After you confirm, the selected engineering parameters are deleted.
Synchronize the engineering parameters with the configuration data as required.

NOTE
When the engineering parameters are imported to the Nastar database, the system updates the engineering parameters such as BSC name, BCCH information, BSIC, cell name, and BTS name according to the latest configuration data. If the configuration data is changed later, you must synchronize the engineering parameters with the configuration data manually or import the modified engineering parameter file to maintain the consistency between the configuration data and the engineering parameters.
To synchronize the engineering parameters with the configuration data, do as follows: 1. 2. In the Engineering Parameter Management window, click the *** Engineering Parameters tab. Click Configuration Synchronize button.
2.13 Creating Custom NE Groups

This section describes how to create custom NE groups. The Nastar client provides the functions of creating, modifying, deleting, importing, and exporting custom NE groups. You can add certain NEs to an NE group so that the performance analysis can be performed for all the NEs in an NE group.
Prerequisite
l l
You have logged in to the Nastar client. You are authorized to manage NE groups.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-06-30)
2-20
2 Getting Started
Context
The export of custom NE group files in .csv and .xls formats are supported.
Procedure
Step 1 Choose Function List > System Function > NE Group Management from the navigation tree in the Analysis Task Management window. The NE Group Management window is displayed. Step 2 Perform the following operations as required: If You Want to ... Create a custom NE group directly Create a custom NE group by importing one Step 3 Create a custom NE group directly. 1. Click the *** NE Group Management tab. Click New to open the NE Group Edit dialog box. *** refers to the network system such as GSM, CDMA, UMTS, or TD-SCDMA. 2. Set the relevant parameters.
l
The system enables you to search for the objects in the navigation tree. You can rightclick any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
For description of the parameters, see 2.15.11 Parameters for Creating and Modifying Custom NE Groups.
3. 1. 2.
Click OK. Click the *** NE Group Management tab, and then click Import. *** refers to the network system such as GSM, CDMA, UMTS, or TD-SCDMA. In the displayed Open dialog box, select an edited NE group file, and then click Open. If an NE group file in .xls format is selected and the file contains multiple worksheets, a prompt is displayed. In this case, select the worksheet to be imported.
NOTE
Step 4 Create a custom NE group by importing one.
If multiple lines of remarks regarding an NE group are inconsistent in the edited NE group file, the system displays the last line of remarks on the Note title bar of the NE Group Management window. It is recommended that the remarks in different lines regarding an NE group be consistent when you define NE group information.
3.
Click Import > ***. *** represents the level 2 menu item in the corresponding network system. Table 2-1 shows the mapping relation between network systems and level 2 menu items.
Issue 03 (2010-06-30)
2-21
2 Getting Started
Table 2-1 Level 2 menu items in different network systems Network System GSM Level 2 Menu Item
l l
Matched LAC CI Match Cell Name Matched LAC SAC Match Cell Name
UMTS
l l
CDMA TD-SCDMA
Matched BSCName BTSID CellID SectorID CarrierID

l l
Matched RNCID CellID Match Cell Name
4.
In the displayed Confirm dialog box, click OK after checking the number of added records, updated records, and failed records. indicates the NE group that is , , and In the Import *** NE Group dialog box, successfully imported, partially imported, and failed to be imported respectively. *** refers to the network system such as GSM, CDMA, UMTS, or TD-SCDMA.
5.
Perform the operations as prompted.

l
If the imported information is correct, only NE groups that are marked by displayed. In this case, click Close. or
are
If abnormal records exist in the imported information, NE groups that are marked by are displayed. In this case, perform the following operations: Click Export Fail Record to export the failed records as a file so that you can make modifications based on the error information to complete the current import task. Click Close to complete the current import task.
----End
Postrequisite
l
Viewing and modifying the attributes of a custom NE group 1. In the NE Group Management window, click the *** NE Group Management tab. Select an NE group, and then click Modify. The NE Group Edit dialog box is displayed. *** refers to the network system such as GSM, CDMA, UMTS, or TD-SCDMA. 2. 3. View the information about members of the custom NE group. If you want to modify some parameters, see step 3 to step 4. Modify the relevant parameters. The objects and remarks of an NE groups can be modified but the name of an NE groups cannot be modified. For description of the parameters, see 2.15.11 Parameters for Creating and Modifying Custom NE Groups.
2-22
Issue 03 (2010-06-30)
2 Getting Started
4.
Click OK.
NOTE
If the NE group is used by certain tasks, the modification does not affect the ongoing tasks. If the NE group is used by a periodic task, the related information is updated in the next period after the modification.
TIP
When you need to modify NE group information in batches, you can export the NE group information, make modifications, and then import the NE group information again.
l
Deleting custom NE groups 1. In the NE Group Management window, click the *** NE Group Management tab. Then, select one NE group and click Delete. *** refers to the network system such as GSM, CDMA, UMTS, or TD-SCDMA. 2. In the displayed Confirm dialog box, click OK.
NOTE
If the NE group is used by certain tasks, the modification does not affect the ongoing tasks. If the NE group is used by a periodic task, the related information is updated in the next period after the modification.
l
Exporting the custom NE group information to .csv or .xls files 1. In the NE Group Management window, click the *** NE Group Management tab. Then, click Export. *** refers to the network system such as GSM, CDMA, UMTS, or TD-SCDMA. 2. Set a file name and specify the save path and file type in the displayed Save dialog box, and then click Save. All information of the NE groups in the tab will be exported.
2.14 Querying NE Data

The Nastar provides the function of querying NE data. Before creating an analysis task, you can check whether the data related to this analysis task has been imported into the Nastar database by querying the data, and check the time of the imported data. The information is the basis for the analysis task.
Prerequisite
l l
You have logged in to the Nastar client. You have imported the data corresponding to an analysis task.
Procedure
Step 1 From the navigation tree in the left pane of the Analysis Task Management window, choose Function List > System Function > Data Query. Step 2 In the left pane of the Data Query window, set Data Type and Condition Selection, and then select an NE object from the NE object navigation tree. Condition Selection is optional. You need to select Required Time Limited before setting the time range. If the time is not limited, you need not set this option.
2 Getting Started
Step 3 Click Query in the lower-left corner. Then, you can determine whether the data related to the analysis task is imported into the Nastar database by viewing the information in the right pane. You can also view the time of the imported data. ----End
2.15 Reference for the Performance Analysis System GUI

This section describes the parameters of the client of the Nastar performance analysis system, such as the parameters related to the client login. You can refer to the description for better operations on the Nastar client. 2.15.1 Interface Description: Nastar Client This section describes the contents and functions of the Nastar client. 2.15.2 Nastar Menu Functions Reference This topic describes the menus of the Nastar and their functions. You can refer to this topic to determine the entry of a certain operation. 2.15.3 Keyboard Shortcuts The Nastar client provides keyboard shortcuts for some operations. You can perform these operations more quickly by using the keyboard shortcuts than using the mouse. 2.15.5 Parameters for Setting the Output GUI This section describes the parameters in the Output Window group box. You can refer to these parameters when you set output information. 2.15.6 Parameters for Setting the Time and Date Formats This section describes the parameters in the Time/Date dialog box. You can refer to these parameters when you set the client time/date style. 2.15.7 Parameters for Querying the Nastar License This section describes the parameters in the License Information dialog box. You can refer to these parameters when you view Nastar licenses information. 2.15.8 Parameters for Setting Broadcast Parameters This section describes the parameters in the Broadcast Messages Options dialog box. When setting the default broadcast message parameters, you can refer to this topic. 2.15.9 Parameters for Printing This section describes the parameters shown in the Print dialog box. You can refer to this topic to set parameters when printing. 2.15.10 Parameters for Importing and Exporting Engineering Parameters This section describes the parameters for importing and exporting the engineering parameters. You can refer to these parameters when importing and exporting the engineering parameters. 2.15.11 Parameters for Creating and Modifying Custom NE Groups This section describes the parameters for creating and modifying custom NE groups. You can refer to the parameter description when creating and modifying the custom NE groups.
2.15.1 Interface Description: Nastar Client

This section describes the contents and functions of the Nastar client.
2-24
Issue 03 (2010-06-30)
2 Getting Started
GUI Introduction
Figure 2-1 shows the displayed GUI after you log in to the Nastar client. Table 2-2 describes the items in Figure 2-1. Figure 2-1 GUI of the Nastar client
Table 2-2 GUI description of the Nastar client No. (1) (2) (3) (4) (5) Name Area of system tool buttons Function list navigation pane Menu items Area of theme analysis task list Area of theme analysis result list Description Describes the operation buttons of the Nastar client. Displays all the theme functions and system functions of the Nastar through a navigation tree. Describes the menus and related functions of the Nastar. Displays the theme analysis tasks that are created by users. Displays the corresponding theme analysis result when you select a certain theme analysis task in Area (4).
Issue 03 (2010-06-30)
2-25
2 Getting Started
System Tool Buttons

Icon Name Exit Logout Lock Terminal Description Exits the Nastar client. Logs out of the current user. When the client is locked, you cannot do any operations on the client, and you need to enter your password to unlock the client. If you click this icon, the menu bar, toolbar, output window, and status bar are hidden. Thus, you can expand the main window in full screen. Press ESC or click Close Full Screen to exit the full screen.
Full Screen
2.15.2 Nastar Menu Functions Reference

This topic describes the menus of the Nastar and their functions. You can refer to this topic to determine the entry of a certain operation. Table 2-3 File menu Menu Item Preferences Function To set display effects for the client. Display effects include the font size, output window action, time and date, automatic client lock, sound for disconnection, number format, time mode, upgrade, system login mode, topology status display, topology display setting, alarm color, alarm sound, alarm highlighting, and alarm/event addition. To customize the toolbar on the client, for example, setting which buttons are to be shown. To preview the topology view before printing it. To print the concerned contents by setting print parameters. To customize the page layout. This function applies to the users who browse the topology view offline.
Customize Toolbar Print Preview Print Page Setup
2-26
Issue 03 (2010-06-30)
2 Getting Started
Menu Item Lock Terminal Change Password Logout Exit
Function To lock the client manually. To change the password of the current Nastar user. To log out of the Nastar client but not close it. To log out of the Nastar client and close it.
Table 2-4 Maintenance menu Menu Item OSS Management E2E Task Management Function To manage Nastar information of the OSS and NEs. To manage Nastar E2E tasks.
Table 2-5 Security menu Menu Item Security Management Function To access the Security Management window for managing users, user groups, object sets, and operation sets. To monitor operations of the current users. To set the global ACL. Only the IP addresses in the ACL can access the Nastar. To set the global security policy of the Nastar, including the password policy and the account policy. Query Operation Logs Query System Logs To set the template or filtering conditions for browsing operation logs. This helps understand the information about user operations. To set the template or filtering conditions for browsing system logs. This helps understand the information about the important events that occurred during system running. To set the template or filtering conditions for browsing operation logs. This helps understand the information about security operations such as logging in, logging out, and unlocking. To set the template, or statistical items and filtering conditions for collecting statistics on or displaying operation logs.
User Operation Monitor ACL Security Policy Log Management
Query Security Logs
Operation Log Statistics
Issue 03 (2010-06-30)
2-27
2 Getting Started
Menu Item System Log Statistics Security Log Statistics
Function To set the template, or statistical items and filtering conditions for collecting statistics on or displaying system logs. To set the template, or statistical items and filtering conditions for collecting statistics on or displaying security logs.
Table 2-6 Tool menu Menu Item Task Management Broadcast Message Function To manage Nastar timing tasks in a unified manner. To access the Broadcast Message dialog box for sending broadcast messages.
Table 2-7 System menu Menu Item System Monitor Browser Function To access the System Monitor Browser window for browsing the system information such as services, processes, hard disks, and resources. To set the parameters for monitoring system resources, hard disks, databases, and services.
Settings
Table 2-8 Window menu Menu Item Full Screen Close Close All Minimize Function To display the window where the focus exists in fullscreen mode. To close the current window. To close all open windows. To minimize the current window. After a window is minimized, the related icon is displayed at the lower left corner of the client. To minimize all the open windows. After the windows are minimized, the related icon is displayed at the lower left corner of the client. To open or close the window tabbed bar.
Issue 03 (2010-06-30)
Minimize All
Toggle Window Tabbed Bar

2-28
2 Getting Started
Menu Item Toggle Message Output Area Cascade Tile Tile Horizontal Tile Vertical
Function To open or close the message output pane in the lower part of the window. To set whether to display the tab bar. To display all active tabs on the interface. Each tab occupies part of the interface space. To tile all the active windows horizontally. To tile all the active windows vertically.
Table 2-9 Help menu Menu Item Help Topics License Information Check For Upgrades About Function To view the Help. To display the license information and update the license. To manually check whether the Nastar client needs to be upgraded. To view the information on the version, components, and license of the Nastar.
2.15.3 Keyboard Shortcuts

The Nastar client provides keyboard shortcuts for some operations. You can perform these operations more quickly by using the keyboard shortcuts than using the mouse.
Keyboard Shortcuts of Controls on GUIs

Table 2-10 describes keyboard shortcuts of controls on GUIs. You can use keyboard shortcuts instead of the mouse to perform operations on GUIs conveniently. Table 2-10 Controls and corresponding keyboard shortcuts Control Menu Drop-down menu Description For any menu followed by an asterisk * (* represents a letter or number), you can press Alt+* to display the menu instead of choosing the menu. For any drop-down menu followed by an asterisk *, you can press * instead of choosing the menu when the menu is expanded.
Issue 03 (2010-06-30)
2-29
2 Getting Started
Control Button
Description
l
For any button followed by an asterisk * (* represents a letter or number), you can press Alt+* instead of clicking the button. When a dialog box is open and the focus is on a button, this button is the default button. If the focus is not on any button, OK is the default button. When the focus is on a button, you can press Enter or space bar instead of clicking the button. If the focus is on a control that does not respond when you press Enter, then the effect is the same when you press Enter or when you click the default button.
Drop-down list
When the focus is on a drop-down list, you can press the Down arrow key to expand the drop-down list. You can press the Up, Down arrow keys to switch between the options in a drop-down list, and press Enter to select the current option. If the focus is on an option button, you can press the space bar to select the option button. If the focus is on a check box, you can press the space bar to select or clear the check box. When the focus is on the navigation tree, you can press the Down arrow key or Up arrow key to switch between the nodes in the tree. And you can press the Left arrow key or Right arrow key to expand or collapse a node that contains subnodes. When there are multiple controls in a window, dialog box, or tab page, you can press Tab to switch from one control to another, and press Shift +Tab to switch to the previous control.
Option button Check box Navigation tree
Switching between controls
Other Key Combinations

Table 2-11 describes other key combinations provided by the Nastar client. You can use these key combinations to perform operations quickly. Table 2-11 Shortcut keys Operation Exit a dialog box or prompt Unlock a terminal Open the Help Exit the system Find Cut
2-30
Shortcut keys Esc Ctrl+Alt+U F1 Alt+F4 Ctrl+F Ctrl+X

2 Getting Started
Operation Paste Delete Save Display full screen Select all Close the current window Restore down (when the service window in the public window is maximized) Minimize the window (applied to the service window in the public window) Maximize the window (when the service window in the public window is restored)
Shortcut keys Ctrl+V Delete Ctrl+S F11 Ctrl+A Ctrl+F4 Ctrl+F5 Ctrl+F9 Ctrl+F10
NOTE
The common area is under the toolbar on the Nastar client interface.
2.15.4 Parameters for Creating or Modifying the Server Information

This topic describes the parameters in the Add Accessible Server Information and Modify Accessible Server Information dialog boxes. When creating or modifying the server information, you need to set these parameters.
Parameter Description
Parameter Name Description Description: Server Description: Host name or IP address of the Nastar server. Settings Value: This parameter is unique and mandatory. Value:
l
Enter the host name. The value is a string of 1-50 characters. Enter the IP address. Example: 10.0.0.0 and 10.255.255.255.
Issue 03 (2010-06-30)
2-31
2 Getting Started
Parameter Port
Description Description: Port through which the client and the Nastar server are connected.
Settings Value: The value range is 1-65535. Example: The default login ports of the Nastar server are:
l l
Common: 31037 Security(SSL): 31039
Mode
Description: Mode of the connection between the client and the Nastar server.
Value: Values:
l l
Common Security(SSL)
Server Type
Description: To open the GUI client or Web client.
Value: Values:
l
B/S: browser/server mode. In this mode, the Web client is opened. C/S: client/server mode. In this mode, the GUI client is opened.
Client Application
Description: Application of the GUI client to be executed.
Setting method: on the right of Client Click Application, and then select an executable client application from the local host. Setting method: Click on the right of Icon, and then select an icon from the local host.
Icon
Description: Icon of the server. After a server icon is created, the server is displayed as the icon.
2.15.5 Parameters for Setting the Output GUI

This section describes the parameters in the Output Window group box. You can refer to these parameters when you set output information.
2-32
Issue 03 (2010-06-30)
2 Getting Started
Parameters
Name Maximum Output Lines Description Description: The maximum lines that can be displayed in the output window. If the lines of output information exceed the maximum lines, the earliest input lines are deleted automatically and the maximum lines are displayed. Description: If you select this option and there is new output information, the output window scrolls to the new information automatically. If you deselect this option, you can only scroll to the new information manually. Description: If you select this option, the output information is dumped to a file according to the preset conditions. Description: Dump lines of output information. The value cannot exceed the value set in Maximum Output Lines. If the value exceeds the preset maximum value, the output information is dumped to the corresponding file automatically, and the dump lines are the same as that set in Dump Lines. Dump File Name Description: The dump path and dump file name of output information. Settings Value: Value range: 30-3000 Default value: 300
Automatically scroll to the new message
Value: -
Automatic dump
Value: -
Dump Lines
Value: Value range: 20-300 Default value: 20
Value: The files saved in TXT format. Cannot be null.
2.15.6 Parameters for Setting the Time and Date Formats

This section describes the parameters in the Time/Date dialog box. You can refer to these parameters when you set the client time/date style.
Issue 03 (2010-06-30)
2-33
2 Getting Started
Time Parameters
Name Time Format Description Description: HH:mm:ss and hh:mm:ss tt:
l l l l l
Settings Value: The default value is HH:mm:ss. The value can be HH:mm:ss or hh:mm:ss tt. Example: For example, 15:10:20, 03:10:20 PM.
HH indicates the 24-hour format. hh indicates the 12-hour format. mm indicates minutes. ss indicates seconds. tt indicates the suffix for morning or afternoon.
Time Indicator
Description: Format of the suffix for morning or afternoon.
Value: The value is AM/PM. Example: For example, 15:10:20, 03:10:20 PM.
Show time zone offset
Description: Indicates whether to show the time zone. If you select the check box, the time zone is displayed after the time.
Setting method: Check box. Example: For example, 15:10:20 +08:00. Setting method: Check box. Example: For example, 15:10:20 DST.
Show daylight saving time (DST)
Description: Indicates whether to show the daylight saving time. If you select the check box, the DST is displayed after the time.
Date Parameters
Name Date Separator Description Description: Symbol to separate the date. Settings Setting method: There are three symbols can be set to "/", "-", and ".". The default is "/". Example: For example, 01/01/2009.
2-34
Issue 03 (2010-06-30)
2 Getting Started
Name Date Format
Description Description: Display format of the date.
Settings Value: There are three format can be set to "yyyy/MM/dd", "dd/MM/yyyy", or "MM/dd/yyyy". The default is "dd/MM/yyyy". Example: For example, 01/01/2009.
2.15.7 Parameters for Querying the Nastar License

This section describes the parameters in the License Information dialog box. You can refer to these parameters when you view Nastar licenses information.
Parameters
Parameter Resource Control Item Resource Description Description: Names of authorization items. License capacity Description: Capacity defined in the license. License consumption Description: Capacity of the licenses consumed. License Expiration Time Description: Expiry time of each authorization item. Detailed Information Description: View details of authorization items. Server ID Description: Local server ID and authorization server ID displayed after you click Server ID Update License Description: Click the button to update license.
Issue 03 (2010-06-30)
2-35
2 Getting Started
Parameter Export License
Description Description: Click the button to export license.
Function Control Item
Function
Description: Names of authorization items.
Supported or Not
Description: The system supports the function or not.
2.15.8 Parameters for Setting Broadcast Parameters

This section describes the parameters in the Broadcast Messages Options dialog box. When setting the default broadcast message parameters, you can refer to this topic.
Parameters
Parameter Displayed message count Description Description: Number of latest messages displayed among history messages. Description: Number of messages saved to the local. Settings Value: Value ranges: 1-000. Value: Value ranges: 0-1000.
Saved message count
2.15.9 Parameters for Printing

This section describes the parameters shown in the Print dialog box. You can refer to this topic to set parameters when printing.
2-36
Issue 03 (2010-06-30)
2 Getting Started
Parameters
Tab General Parameter Print Service Description In this box, you can set the printer properties and select to print a document to file. Name, Status, Type and Info respectively refer to the name, status, type and the information of the selected printer. If it permits, you can click Properties to set the printer properties. Print To File shows that you can print a document to a file. Range of pages to be printed. Value range:
l l
Print Range
All: to print all pages. Pages: to print the specified pages.
Copies
Copies to be printed. Value range:

l
Number of copies: to print the specified copies. Collate: to print copies one by one. It is valid if you print more than one copy.
Page Setup
Media
Property of papers for print. Value range:

l l
Size: size of the papers for print. Source: source of the papers for print.
Orientation
Orientation in which pages are to be printed. Value range:

l l l
Portrait: print perpendicularly Landscape: print horizontally Reverse Portrait: print perpendicularly in reverse order Reverse Landscape: print horizontally in reverse order
Margins
Margins of pages to be printed. Value range:

l l l l
left(in): left margin of a page. right(in): right margin of a page. top(in): top margin of a page. bottom(in): bottom margin of a page.
Issue 03 (2010-06-30)
2-37
2 Getting Started
Tab Appearance
Parameter Color Appearance
Description Color of pages to be printed. Value range:

l l
Monochrome: to print in black and white. Color: to print in multiple colors other than black and white.
Quality
Quality of pages to be printed. Value range:

l l l
Draft: to print with low quality. Normal: to print with generic quality. High: to print with high quality.
Sides
Set whether to print on one side or on both sides. Value range:

l l
One Side: to print on one side of a paper. Tumble: to print on both sides of each paper and the shorter side upturns during printing. The printed pages are like a notepad. Duplex: to print on both sides of each paper and the longer side upturns during printing. The printed pages are like a book. For the double-sided printing, the printer may use different terms.
Job Attributes
Property of a print job.

l
Banner Page: page that contains titles of the job. Priority: priority of the print job. Job Name: name of the print job. User Name: name of the user that starts the print job.
l l l
2.15.10 Parameters for Importing and Exporting Engineering Parameters

This section describes the parameters for importing and exporting the engineering parameters. You can refer to these parameters when importing and exporting the engineering parameters.
2-38
Issue 03 (2010-06-30)
2 Getting Started
GSM Parameter Description

Parameter MSCName BSCName SiteName CellName MCC MNC LAC Description Indicates the name of an MSC. Indicates the name of a BSC. Indicates the name of a BTS. Indicates the name of a cell. Indicates the mobile country code. Indicates the mobile network code. Indicates the location area code of a cell. Value Range String String String String Integer Integer and only a two-digit number
l l
Optional/ Mandatory Optional Mandatory Mandatory
Mandatory Mandatory Mandatory
Integer Value range: 1 to 65533, 65535
CI BCCH
Indicates the cell identification. Indicates the broadcast control channel.
Integer
l l
Mandatory Mandatory
Integer Value range: 1 to 1023 Integer Value range: 1 to 8 Integer Value range: 1 to 8
BCC
Indicates the color code of a BTS. Indicates the network color code. Indicates the longitude where a cell is located, for example, 116.389722. Indicates the latitude where a cell is located, for example, 39.952778. Indicates the azimuth of an antenna. Indicates the traffic channel.
l l l l
Mandatory
NCC
Mandatory
Longitude
[-180.0, 180.0]
Mandatory
Latitude
[-90.0, 90.0]
Mandatory
Azimuth TCH
[0, 360] String
Mandatory Optional
Issue 03 (2010-06-30)
2-39
2 Getting Started
Parameter Is Outdoor
Description Indicates whether the cell is an outdoor cell. Indicates whether the cell is a directional cell.
Value Range
l l l l
Optional/ Mandatory Optional
0: No 1: Yes 0: No 1: Yes
Is Direct
Optional
CDMA Parameter Description

Parameter MSC_ID BSC_ID BTS_ID Cell_ID Sector_ID Longitude Description Indicates the number of an MSC. Indicates the number of a BSC. Indicates the number of a BTS. Indicates the number of a cell. Indicates the number of a sector. Indicates the longitude where a cell is located, for example, 116.389722. Indicates the latitude where a cell is located, for example, 39.952778. Indicates the azimuth of an antenna. Indicates the antenna gain. Value Range String Integer Integer Integer Integer [-180.0, 180.0] Optional/ Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory
Latitude
[-90.0, 90.0]
Mandatory
Azimuth AntennaGain (dBi)
[0, 360] Floating number
Mandatory Mandatory
UMTS Parameter Description

Parameter MSCName Description Indicates the name of an MSC. Value Range String Optional/ Mandatory Optional
2-40
Issue 03 (2010-06-30)
2 Getting Started
Parameter RNCId NodeBID NodeBName Cell ID CellName LAC RAC
Description Indicates the number of an RNC. Indicates the number of a NodeB. Indicates the name of a NodeB. Indicates the number of a cell. Indicates the name of a cell. Indicates the location area code of a cell. Indicates the route area code of a cell.
Value Range Integer Integer String Integer String Integer

l l
Optional/ Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory
Integer Value range: 1 to 255 Integer Value range: 1 to 65535
SAC
Indicates the service area code of a cell.
l l
Mandatory
UARFCNDOWNLINK UARFCNUPLINK P-SC Longitude
Indicates the downlink ARFCNs of a cell. Indicates the uplink ARFCNs of a cell. Indicates the primary scramble code of a cell. Indicates the longitude where a cell is located, for example, 116.389722. Indicates the latitude where a cell is located, for example, 39.952778. Indicates the azimuth of an antenna. Indicates whether the cell is an outdoor cell. Indicates whether the cell is a directional cell.
Integer Integer Integer [-180.0, 180.0]
Mandatory Optional Mandatory Mandatory
Latitude
[-90.0, 90.0]
Mandatory
Azimuth Is Outdoor
[0, 360]
l l l l
Mandatory Optional
0: No 1: Yes 0: No 1: Yes
Is Direct
Optional
Issue 03 (2010-06-30)
2-41
2 Getting Started
TD-SCDMA Parameter Description

Parameter RNC ID Description Indicates the number of an RNC. Value Range
l l
Optional/ Mandatory Mandatory
Integer Unique and existent in the existing network Integer Unique and existent in the existing network
NodeB ID
Indicates the number of a NodeB.
l l
Optional
NodeB Name Cell ID
Indicates the name of a NodeB. Indicates the number of a cell.
String
l l
Optional Mandatory
Integer Unique and existent in the existing network
Cell Name UARFCN
Indicates the name of a cell. Indicates the Universal Terrestrial Radio Access Network (UTRAN) Absolute Radio Frequency Channel Number (ARFCN). Indicates the location area code of a cell. Indicates the route area code of a cell. Indicates the primary scramble code of a cell. Indicates the longitude where a cell is located, for example, 116.389722. Indicates the latitude where a cell is located, for example, 39.952778. Indicates the azimuth of an antenna. Indicates whether the cell is an outdoor cell.
String Integer
Optional Mandatory
LAC RAC PSC Longitude
Integer Integer Integer [-180.0, 180.0]
Optional Optional Optional Mandatory
Latitude
[-90.0, 90.0]
Mandatory
Azimuth IsOutdoor
[0, 360]
l l
Mandatory Optional
yes no
2-42
Issue 03 (2010-06-30)
2 Getting Started
Parameter IsDirect
Description Indicates whether the cell is a directional cell.
Value Range
l l
Optional/ Mandatory Optional
yes no
2.15.11 Parameters for Creating and Modifying Custom NE Groups

This section describes the parameters for creating and modifying custom NE groups. You can refer to the parameter description when creating and modifying the custom NE groups.
Parameter NE Group Name Description Indicates the name of the NE group, for example, Cell_1. Value range:
l l l l
A maximum of 20 characters Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' ` Unique and not null Case sensitive
Remarks
Provides the description of an NE group. Value range:

l l
A maximum of 200 characters Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' `
2.16 FAQs about the Client Operations

This section describes how to rectify faults on client operations. 2.16.1 How Can I View the Complete Text? 2.16.2 The Left Mouse Button Not Respond 2.16.3 The Help Window Not Respond 2.16.4 Some Records Not Selected When I Select Multiple Records 2.16.5 The Nastar Client Cannot Read the File to Be Printed 2.16.6 Menu Items Gray and Unavailable
Issue 03 (2010-06-30)
2-43
2 Getting Started
2.16.1 How Can I View the Complete Text?

Question
In the text boxes that cannot be edited, the long text cannot be fully displayed. How can I view the whole text?
Answer
Hold and drag the left mouse key to select the text information and view it.
2.16.2 The Left Mouse Button Not Respond

Symptom
The left mouse button probably does not respond after the following operations: 1. 2. 3. Move the cursor onto a topological object. Click the left and right mouse buttons concurrently, and then the shortcut menu is displayed. Hold on these two buttons and move the cursor to another area. Release the buttons simultaneously. The shortcut menu is displayed. Move the cursor out of the shortcut menu. Check whether you can hold the left mouse button and drag the cursor to select something.
Procedure
Step 1 Right-click in any area to restore the left mouse button to its normal state. ----End
2.16.3 The Help Window Not Respond

Symptom
This problem may occur when doing the following operations: 1. 2. Choose Help > Topic from the main menu, and then the Help window is displayed. Perform some operations on the Nastar, and switch to the opened Help window during the operations. In this case, the Help window may have no response.
Procedure
Step 1 Finish the operation. For example, close all the opened dialog boxes. The Help window will be recovered. Step 2 To browse help during the operations, press F1 to open the Help window. ----End
2-44
Issue 03 (2010-06-30)
2 Getting Started
2.16.4 Some Records Not Selected When I Select Multiple Records

Symptom
In the window that displays an information table, drag the mouse to select multiple records continuously. Some records in the middle may not be selected.
Procedure
Step 1 Press and hold the left mouse button and move the mouse slowly to select records. Do not select too many records at a time. ----End
2.16.5 The Nastar Client Cannot Read the File to Be Printed

Symptom
The Nastar cannot read some files to be printed.
Possible Causes
The Nastar client is based on Java. Therefore, the print function calls the related Java interface. However, the Java print function is incompatible with the virtual printer of Office 2003. When you use the print function and select the virtual printer of Office 2003, the Java environment cannot read any file.
Procedure
Step 1 Do not use the virtual printer of Office 2003. ----End
2.16.6 Menu Items Gray and Unavailable

Symptom
After login, you find that part of the menu items are gray and unavailable on the client.
Possible Causes
l l
The current user has no operation rights to the menu items. The menu items are not supported in the current window. For example, Topology > Move to is gray and unavailable if no corresponding topology object is selected in the topology view.
Procedure
Step 1 You can apply for the operation right to the administrator as required.
2 Getting Started
Step 2 Learn the functions and operation conditions of the menu items and perform the operations when the conditions are satisfied. ----End
2-46
Issue 03 (2010-06-30)
3 Monitoring the Nastar Server
3
About This Chapter
Monitoring the Nastar Server
You can monitor the status (including the status of the service, hard disk and database) and the component information of the Nastar server as well as logs of the user operations performed on the system monitor client. 3.1 Setting the Monitoring Parameters You can set thresholds for the server monitoring, hard disk monitoring, database monitoring, and service monitoring. When the threshold is reached, the Nastar raises an alarm. 3.2 Monitoring the Status of the Nastar Server When monitoring the running status and resource status of the Nastar, you can obtain the health status of the Nastar in time, and handle the exceptions of the Nastar hardware and software in time. 3.3 Reference of the System Monitoring GUI This topic describes the parameters displayed on system monitoring GUIs.
Issue 03 (2010-06-30)
3-1
3.1 Setting the Monitoring Parameters

You can set thresholds for the server monitoring, hard disk monitoring, database monitoring, and service monitoring. When the threshold is reached, the Nastar raises an alarm. 3.1.1 Setting the Parameters for the Nastar Server Monitoring You can set the server monitoring parameters to monitor the performance (CPU usage and memory usage) of the Nastar server. When the CPU usage and memory usage reach the thresholds, alarms are generated. You can also set whether to display pop-up messages on the client. From pop-up messages, you can understand server performance exceptions in time. 3.1.2 Setting the Parameters for the Nastar Server Hard Disk Monitoring You can set the hard disk monitoring parameters to monitor the usage of the hard disk on the Nastar server. When the hard usage of the hard disk on the Nastar server reaches the threshold, a high hard disk usage alarm occurs. You can also set whether to display pop-up messages on the client. From pop-up messages, you can understand hard disk exceptions in time. 3.1.3 Setting the Parameters for the Nastar Server Database Monitoring You can set the database monitoring parameters to monitor the Nastar database usage. When the Nastar server database usage reaches the threshold for alarm generation, an alarm is generated. 3.1.4 Setting the Parameters for the Nastar Server Service Monitoring You can set the parameters for service monitoring to specify pop-up prompts and refresh interval for service monitoring. Thus, when the service is changed, the corresponding prompts are displayed. At the same time, the service status is periodically polled according to the refresh interval.
3.1.1 Setting the Parameters for the Nastar Server Monitoring

You can set the server monitoring parameters to monitor the performance (CPU usage and memory usage) of the Nastar server. When the CPU usage and memory usage reach the thresholds, alarms are generated. You can also set whether to display pop-up messages on the client. From pop-up messages, you can understand server performance exceptions in time.
Context
l
If the sampled times equal to the value of the CPU sustained overload times, when the CPU usage is larger than the threshold for alarm generation each time, the Nastar generates a high CPU usage alarm. When the CPU usage is smaller than the threshold for alarm clearance each time, the Nastar generates a corresponding cleared alarm. When the memory usage is larger than the threshold for alarm generation, a high memory usage alarm is generated. When the memory usage is smaller than the threshold for alarm clearance, a corresponding clearance alarm is generated. When the condition for generating a performance alarm is met, the corresponding icon on the Server Monitor tab turns red. If you enable the function of displaying pop-up messages, you can receive notifications of performance exceptions on the status bar on the client.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu.
Step 2 In the System Monitor Settings dialog box, click the Server Monitor tab. Step 3 Set the property values in the Server Monitor tab. Step 4 Click OK. ----End
3.1.2 Setting the Parameters for the Nastar Server Hard Disk Monitoring
You can set the hard disk monitoring parameters to monitor the usage of the hard disk on the Nastar server. When the hard usage of the hard disk on the Nastar server reaches the threshold, a high hard disk usage alarm occurs. You can also set whether to display pop-up messages on the client. From pop-up messages, you can understand hard disk exceptions in time.
Context
l
When the usage of the hard disk on the Nastar server reaches the threshold for alarm generation, a high hard disk usage alarm occurs. When the hard disk usage is smaller than the threshold for alarm clearance, the high hard disk usage alarm is cleared. When the condition for generating a high hard disk usage alarm is met, the corresponding icon on the Hard Disk Monitor tab turns red. If you enable the function of displaying popup messages, you can receive notifications of hard disk exceptions on the status bar on the client.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu. Step 2 In the System Monitor Settings dialog box, click the Hard Disk Monitor tab.
NOTE
The threshold for generating an alarm of lower severity is smaller than that for clearing an alarm of higher severity.
Step 3 Set the property values in the Hard Disk Monitor tab. Step 4 Click OK. ----End
3.1.3 Setting the Parameters for the Nastar Server Database Monitoring
You can set the database monitoring parameters to monitor the Nastar database usage. When the Nastar server database usage reaches the threshold for alarm generation, an alarm is generated.
Context
l
When the Nastar server database usage reaches the threshold, the Nastar raises an alarm. When the usage is smaller than the threshold, the corresponding clearance alarm is generated.
Issue 03 (2010-06-30)

l
When the condition for generating a high database usage alarm is met, the state icon on the Database Monitor tab turns red.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu. Step 2 In the System Monitor Settings dialog box, click the Database Monitor tab to set the property values. Step 3 Set the property values in the Database Monitor tab. Step 4 Click OK. ----End
3.1.4 Setting the Parameters for the Nastar Server Service Monitoring
You can set the parameters for service monitoring to specify pop-up prompts and refresh interval for service monitoring. Thus, when the service is changed, the corresponding prompts are displayed. At the same time, the service status is periodically polled according to the refresh interval.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu. Step 2 In the System Monitor Settings dialog box, click the Service Monitor tab. Step 3 Set the property values in the Service Monitor tab. Step 4 Click OK. ----End
3.2 Monitoring the Status of the Nastar Server

When monitoring the running status and resource status of the Nastar, you can obtain the health status of the Nastar in time, and handle the exceptions of the Nastar hardware and software in time. 3.2.1 Monitoring the Nastar Server Service Status By monitoring the service status of the Nastar server through viewing the information, such as the service name and service status, you can learn the running status of the Nastar server. Thus, you can detect and handle exceptions, and ensure the efficient running of the Nastar server. 3.2.2 Monitoring the Nastar Server Process Status By monitoring the process status of the Nastar server through viewing the information, such as the process name, process ID, and thread number, you can learn the process status of the Nastar server. Thus, you can detect and handle exceptions, and ensure the efficient running of the Nastar server. 3.2.3 Monitoring the Nastar Server Hard Disk Status By monitoring the hard disk status of the Nastar server through viewing the information, such as the total disk capacity and disk usage, you can learn the hard disk status of the Nastar server.
Thus, you can detect and handle exceptions, and ensure the efficient running of the Nastar server. If the hard disk usage is too high, you need to clear or expand the hard disk. 3.2.4 Monitoring the Nastar Server Database Status You can monitor the status of the Nastar server database to view the information, such as the database name, server name, and database status, to know the running status of the Nastar server. Thus, you can detect and handle exceptions, and ensure the efficient running of the Nastar server. 3.2.5 Monitoring the Nastar Server Status You can monitor the Nastar server status to view the system resource usage of the Nastar server that you log in to. Thus, you can find out and rectify faults in time, and ensure the efficient running of the Nastar server. 3.2.6 Viewing the Information about Nastar Server Components This function enables you to view the information of the components installed on the Nastar server that you log in to. 3.2.7 Refreshing the Monitoring Information To know the latest running status of the Nastar server, you need to refresh the monitoring information. The Nastar server also periodically refreshes the monitoring information according to the specified monitoring interval. 3.2.8 Saving the Monitoring Information For the convenience of future analysis of the information that is monitored at certain time, you can save the required monitoring information to the server.
3.2.1 Monitoring the Nastar Server Service Status

By monitoring the service status of the Nastar server through viewing the information, such as the service name and service status, you can learn the running status of the Nastar server. Thus, you can detect and handle exceptions, and ensure the efficient running of the Nastar server.
Context
If a service is stopped or abnormal, its status icon is displayed in red.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Service Monitor tab to view services on the server. Step 3 In the Service Monitor tab, right-click an service to choose Details.
NOTE
You can also double-click a service to access the Service Details dialog box.
Step 4 In the displayed Service Details dialog box, view the service details and dependencies between services. ----End
3.2.2 Monitoring the Nastar Server Process Status

By monitoring the process status of the Nastar server through viewing the information, such as the process name, process ID, and thread number, you can learn the process status of the
Nastar server. Thus, you can detect and handle exceptions, and ensure the efficient running of the Nastar server.
Context
Only the running processes are displayed in the monitored content.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Process Monitor tab. Step 3 View the server processes in the Process Monitor tab. ----End
3.2.3 Monitoring the Nastar Server Hard Disk Status

By monitoring the hard disk status of the Nastar server through viewing the information, such as the total disk capacity and disk usage, you can learn the hard disk status of the Nastar server. Thus, you can detect and handle exceptions, and ensure the efficient running of the Nastar server. If the hard disk usage is too high, you need to clear or expand the hard disk.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Hard Disk Monitor tab. Step 3 View the status of the server hard disk in the Hard Disk Monitor tab. Whether Status of an item is Normal depends on the preset threshold for alarm generation. When the hard disk usage of the item exceeds the threshold, Status changes to Abnormal. ----End
3.2.4 Monitoring the Nastar Server Database Status

You can monitor the status of the Nastar server database to view the information, such as the database name, server name, and database status, to know the running status of the Nastar server. Thus, you can detect and handle exceptions, and ensure the efficient running of the Nastar server.
Context
When the database space is insufficient, contact huawei technical support engineers to determine the extension solution.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Database Monitor tab.

NOTE
For the Oracle database, the database monitoring fields include Database Name, Total Data Space, Free Data Space, Total Data Space Usage, Total Space Usage, and Status.
Step 3 View the status of the Nastar server database in the Database Monitor tab. Whether Status of an item is Normal depends on the preset alarm threshold. When the database usage of the item exceeds the threshold, Status changes to Abnormal. ----End
3.2.5 Monitoring the Nastar Server Status

You can monitor the Nastar server status to view the system resource usage of the Nastar server that you log in to. Thus, you can find out and rectify faults in time, and ensure the efficient running of the Nastar server.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Server Monitor tab. Step 3 View the Nastar server status in the Server Monitor tab. ----End
3.2.6 Viewing the Information about Nastar Server Components

This function enables you to view the information of the components installed on the Nastar server that you log in to.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Component Information tab. Step 3 View the information of all the installed components in Component Information tab. ----End
3.2.7 Refreshing the Monitoring Information

To know the latest running status of the Nastar server, you need to refresh the monitoring information. The Nastar server also periodically refreshes the monitoring information according to the specified monitoring interval.
Context
l
When you refresh the current tab page, only the information on this tab page is refreshed. The information on other tab pages is not refreshed. When you switch tab pages, the information on these tab pages are refreshed immediately. Therefore, when you switch tab pages, the information is refreshed at the same time.
Issue 03 (2010-06-30)
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the tab of the monitoring information to be refreshed. Step 3 click Refresh. ----End
3.2.8 Saving the Monitoring Information

For the convenience of future analysis of the information that is monitored at certain time, you can save the required monitoring information to the server.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the tab of the monitoring information, and then click Save As.
NOTE
l l
The monitoring information can be saved in the format of TXT, HTML, CSV, or XML. The default format is XML.
Step 3 In the Save dialog box, select a storage path, enter the file name, and click Save. ----End
3.3 Reference of the System Monitoring GUI

This topic describes the parameters displayed on system monitoring GUIs. 3.3.1 Parameters for Setting Monitoring Parameters of the Nastar Server This topic describes the parameters of system monitor settings. You can use these parameters when you set the server thresholds. 3.3.2 Parameters for Monitoring the Nastar Server Service Status This topic describes the parameters of the query result displayed in the Service Monitor tab. You can use these parameters when you monitor the Nastar server service status 3.3.3 Parameters for Monitoring the Nastar Server Process Status This topic describes the parameters of the query result displayed in the Process Monitor tab. You can use these parameters when you monitor the Nastar server process status. 3.3.4 Parameters for Monitoring the Nastar Server Hard Disk Status This topic describes the parameters of the query result displayed in the Hard Disk Monitor tab. You can use these parameters when you monitor the Nastar server hard disk status. 3.3.5 Parameters for Monitoring the Nastar Server Database Status This topic describes the parameters of the query result displayed in the Database Monitor tab. You can use these parameters when you monitor the Nastar server database status. 3.3.6 Parameters for Monitoring the Nastar Server Status
This topic describes the parameters of the query result displayed in the Server Monitor tab. You can use these parameters when you monitoring the Nastar server status. 3.3.7 Parameters for Viewing the Information about Nastar Server Components This topic describes the parameters on the Component Information tab page. You can use these parameters when you view the information about Nastar server components.
3.3.1 Parameters for Setting Monitoring Parameters of the Nastar Server

This topic describes the parameters of system monitor settings. You can use these parameters when you set the server thresholds.
Issue 03 (2010-06-30)
3-9
Parameters
Table 3-1 Server Monitor Name Server Monitor Parameter Settings CPU sustained overload times (times) Description Description:
l
Settings Value: Value range: 10-400 Default value: 30
The number of consecutive sampling times is equal to CPU sustained overload times. The sampling interval is equal to Server status refresh interval. If the CPU usage sampled each time is larger than the generation threshold, it means that the CPU is consecutively overloaded. When the number of overload times reaches the specified value, a high CPU usage alarm is generated. If the CPU usage sampled at a time is smaller than the clearance threshold, the high CPU usage alarm is cleared.
Server status refresh interval (seconds)
Description: Refresh interval for server monitoring, that is, the CPU usage is sampled every x seconds.
Value: Value range: 2-60. Default value: 10.
3-10
Issue 03 (2010-06-30)
Name Server Monitor Threshold Settings CPU used rate (%)
Description Description: Used to set Threshold for Alarm Generation, Threshold for Alarm Clearance for the CPU usage alarm and whether to enable the bubble. Memory used rate (%) Used to set Threshold for Alarm Generation and Threshold for Alarm Clearance for the memory usage alarm.
l
Settings Value: Value range: 1-99. Default value: 90. Offset value range: 1-99. Default value: 70.
Value: Value range: 1-99. Default value: 95. Offset value range: 1-99. Default value: 85.
If the memory usage is larger than Threshold for Alarm Generation of Memory used rate, the Nastar generates a high memory usage alarm. If the memory usage is smaller than Threshold for Alarm Clearance of Memory used rate, the Nastar generates an alarm, prompting that the high memory usage alarm is cleared. When the function of bubble information is enabled, if the server is faulty, the system displays a bubble information.
Issue 03 (2010-06-30)
3-11
Table 3-2 Hard Disk Monitor Name Disk Monitor Parameter Settings Hard disk status refresh interval (seconds) Description Description: Refresh interval for hard disk monitoring. Description: All default thresholds of hard disk usage on the Nastar server.
l
Settings Value: Value range: 60-3600 Default value: 60 Value: Value range: 1-99 Default value:
l l l l
Disk Monitor Threshold Settings
Default value setting (%)
Warning: 60 Minor: 70 Major: 80 Critical: 90
When the hard disk usage is larger than Threshold for Alarm Generation of an alarm severity level, the Nastar generates a high hard disk usage alarm of this severity level. When the hard disk usage is smaller than Threshold for Alarm Clearance of an alarm severity level, the Nastar clears the high hard disk usage alarm of this severity level. When the function of bubble information is enabled, if the hard disk is faulty, the system displays a bubble information.
3-12
Issue 03 (2010-06-30)
Name Advanced Setting (%)
Description Description: Thresholds of all the hard disk usage on the Nastar server.
l
Settings Value: Value range: 1-99
When the hard disk usage is larger than Threshold for Alarm Generation of an alarm severity level, the Nastar generates a high hard disk usage alarm of this severity level. When the hard disk usage is smaller than Threshold for Alarm Clearance of an alarm severity level, the Nastar clears the high hard disk usage alarm of this severity level. When the function of bubble information is enabled, if the hard disk is faulty, the system displays a bubble information.
l If you select
NOTE Default Value, the Nastar uses the threshold specified in Default Value Setting.
l If you select
Customize Value, the Nastar uses customized thresholds of alarms.
Issue 03 (2010-06-30)
3-13
Table 3-3 Database Monitor Name Database Monitor Parameter Settings Database status refresh interval (seconds) Description Description: Interval of database refreshing. Settings Value: Value range: 300-3600 Default value: 300 Database Monitor Threshold Settings Default Value Setting (%) Description: All default thresholds of database usage on the Nastar server.
l
Value: Value range: 1-100 Default value:

l l l l
When the database usage is larger than Threshold of an alarm severity level, the Nastar generates a high database usage alarm of this severity level. When the database usage is smaller than Threshold of an alarm severity level, the Nastar clears the high database usage alarm of this severity level.
3-14
Issue 03 (2010-06-30)
Name Advanced Setting (%)
Description Description: Thresholds for the database usage alarms of different severities. You need to set these thresholds separately for each database on the Nastar server.
l
Settings Setting method: Set the following parameters for each database:
l
When the database usage is larger than Threshold of an alarm severity level, the Nastar generates a high database usage alarm of this severity level. When the database usage is smaller than Threshold of an alarm severity level, the Nastar clears the high database usage alarm of this severity level.
Default Value: use default thresholds for the database usage alarms of different severities. Customize Value: customize thresholds for the database usage alarms of different severities. Value range: 1-100 Default value:

Disabled Monitoring: Disable the database monitoring.
Table 3-4 Service Monitor Name Services Monitor Parameter Settings Service status refresh interval (seconds) Description Description: Interval of service refreshing. Settings Value: Value range: 60-3600 Default value: 60
Issue 03 (2010-06-30)
3-15
Name Service Monitor Screen Tip Settings Default Group
Description Description: Set whether to display the service status at the lower right corner of the Nastar system monitor client by or .
l If all the monitored
Settings Setting method: Select a service from the Service Name drop-down list. Select enable or disable in the corresponding Show Screen Tips dropdown list.
NOTE services are running, displayed. is
l if a monitored
service is stopped, is displayed.

l You can double-
click or to access the Service Monitor tab.
3.3.2 Parameters for Monitoring the Nastar Server Service Status

This topic describes the parameters of the query result displayed in the Service Monitor tab. You can use these parameters when you monitor the Nastar server service status
Parameters
Name Service Name Description Description: The name of a service. Process Name Description: The name of a process. Description Description: The description information of functions and interfaces provided by a service. Status Description: The status of a service.
3-16
Issue 03 (2010-06-30)
Name Start Mode
Description Description: The service start mode, including Automatic, Manual, and Disable. The Disable mode is available only for stopped services.
Start Time
Description: The time that the service is started.
Server Name
Description: The name of the server.
3.3.3 Parameters for Monitoring the Nastar Server Process Status

This topic describes the parameters of the query result displayed in the Process Monitor tab. You can use these parameters when you monitor the Nastar server process status.
Parameters
Name Process Name Description Description: Name of a process. Process ID Description: ID of a process. Handle Number Description: Number of handles used by a process. CPU Usage Rate(%) Description: CPU usage of a process. Used Memory(MB) Description: Sum of the virtual and physical memory usage of a process. Thread Number Description: Number of threads generated by a process.
3.3.4 Parameters for Monitoring the Nastar Server Hard Disk Status
This topic describes the parameters of the query result displayed in the Hard Disk Monitor tab. You can use these parameters when you monitor the Nastar server hard disk status.
Issue 03 (2010-06-30)
3-17
Parameters
Name File System Description Description: Hard disk partitions and their paths. Total Size(MB) Description: Total space of a specific partition, equals to the sum of Used Size and Free Size. Used Size(MB) Description: Used space of a specific partition. Free Size(MB) Description: Available space of a specific partition. Used Rate(%) Description: Current usage of a specific partition. Status Description: Current status of a specific partition, including normal and abnormal. If the usage is more than or equal to the maximum, the system displays Abnormal.
3.3.5 Parameters for Monitoring the Nastar Server Database Status

This topic describes the parameters of the query result displayed in the Database Monitor tab. You can use these parameters when you monitor the Nastar server database status.
Parameters
Name Database Name Description Description: Name of the database on the Nastar server. Total Data Space (MB) Description: Total data space. Free Data Space (MB) Description: Remaining data space. Table Space Usage (%) Description: Usage rate of the used table space of the database and total table space. This parameter is displayed when the database is the Oracle database.
3-18
Issue 03 (2010-06-30)
Name Status
Description Description: Database status, including normal and abnormal. If the database usage is more than or equal to the threshold, the system displays Abnormal.
3.3.6 Parameters for Monitoring the Nastar Server Status

This topic describes the parameters of the query result displayed in the Server Monitor tab. You can use these parameters when you monitoring the Nastar server status.
Parameters
Name Server Name Description Description: Name of the Nastar server. Server Status Description: Status of the Nastar server, including Active, Slave and Standby. OS Description: Operating system of the server. Total Physical Memory(MB) Description: Total physical memory space. Free Physical Memory(MB) Description: Remaining physical memory space. Total Swap Memory(MB) Description: Total virtual memory space. Free Swap Memory(MB) Description: Remaining virtual memory space. CPU Usage Rate(%) Description: CPU usage. Memory Usage(%) Description: The usage of the total memory space (including physical memory and virtual memory).
Issue 03 (2010-06-30)
3-19
3.3.7 Parameters for Viewing the Information about Nastar Server Components
This topic describes the parameters on the Component Information tab page. You can use these parameters when you view the information about Nastar server components.
Parameters
Name Component Description Description: Component name of the Nastar server. Version Description: Component version of the Nastar server. Description Description: Component description of the Nastar server.
3-20
Issue 03 (2010-06-30)
4 Security Management
4
About This Chapter
Security Management
Security management provides the functions of managing user rights and system security policies. These functions can prevent invalid users from performing malicious operations on the Nastar, thus ensuring data security of the Nastar. 4.1 Introduction to Security Management This section describes the functions, basic concepts, user permission management policy, and application operation permission list of the Nastar security management. 4.2 Setting Security Policies of Nastar Users You can set the password policy and account policy of the Nastar user, to enhance the security. 4.3 Creating Nastar Users and Assigning Permissions This section describes how to create Nastar users and assign rights to them. 4.4 Comparing the Nastar User Rights By comparing the rights of two Nastar users, you can understand the differences between their rights. 4.5 Querying the Authorization In the Nastar, you can query the users or user groups that certain operation rights are assigned to. 4.6 Modifying a Nastar User This section describes how to modify the password, general properties, managed domain, and operation rights of the Nastar user. 4.7 Managing Nastar Operation Sets This section describes how to create, modify, and delete operation sets. 4.8 Monitoring a Nastar User This section describes how to monitor Nastar user sessions and operations, force Nastar users to exit, unlock Nastar user accounts and send messages to online users. 4.9 Reference of the Security Management GUI This topic provides the reference information of the security management GUI.
Issue 03 (2010-06-30)
4-1
4.1 Introduction to Security Management

This section describes the functions, basic concepts, user permission management policy, and application operation permission list of the Nastar security management. 4.1.1 Security Management This section describes the security management functions of the Nastar. Proper configuration and use of the security management functions ensure secure running of the Nastar. 4.1.2 Concepts of Nastar Security When you perform security management tasks, you need to know some basic concepts, such as the user, user group, object set, operation set, ACL, managed domain, and operation right. Knowing these concepts helps you perform security management, 4.1.3 Nastar User Rights Management Policies You can manage user rights based on the rights management policies. By this means, the allocation of user rights is clearer, and the rights management is more simple. 4.1.4 Operation Rights List for the Nastar Application The operation right list describes operation rights of Nastar applications. You can refer to these parameters when you assign the operation rights for the Nastar users.
4.1.1 Security Management

This section describes the security management functions of the Nastar. Proper configuration and use of the security management functions ensure secure running of the Nastar. The security management of the Nastar is a set of functions used for users and user rights management. To log in to the Nastar and perform operations, you need to have the user account and rights of the Nastar. Through users and rights management, the operator can log in to the Nastar to perform operations such as monitoring and maintenance to prevent illegal access and operations on the Nastar. In the security management, users and user rights are managed. The security management involves the following functions:
l l l l l l l
Creating, modifying, and deleting users Creating, modifying, and deleting user groups Creating, modifying, and deleting operation sets Managing user rights, including the user managed domain, operation right Monitoring users Setting the ACL Setting the security policies of the Nastar, including the password policy, account policy
4.1.2 Concepts of Nastar Security

When you perform security management tasks, you need to know some basic concepts, such as the user, user group, object set, operation set, ACL, managed domain, and operation right. Knowing these concepts helps you perform security management,
4-2
Issue 03 (2010-06-30)
Concept User
Description The Nastar client users. A user and its password uniquely define the operation and management rights. Administrator is the default super user of the Nastar, who has the right to view all objects and has all operation rights.
User group
The user group refers to a collection of user accounts. Users that belong to a user group have all rights of the user group. Managing user rights based on user groups makes right management conveniently and clearly. The Nastar provides five default user groups: Administrators, SMManagers, Operators, Monitors, and Normal.
Managed domain
The managed domain refers to a range of security objects (including users and user groups) that can be managed by users or user groups. After logging in to the Nastar client, users can view only the security objects in the managed domains of them.
View rights
View rights indicates a user can view a security object on the Nastar. If the user can view a security object on the Nastar, it indicates that the user has the view right of the security object. The view right is related to the managed domain. Security objects are assigned to users or user groups, and thus these users or user groups have the view rights of these security objects.
Operation rights
Operation rights indicates that a user is allowed to perform specific operations. After the operation right is allocated to the user, it indicates that the user can execute the specific operation. Operation rights are classified into two types by operation object: network device operation rights and network management application operations rights. Operation rights are associated with the managed domain. Users can operate only the NEs in the managed domains of them based on their operation rights.
Operation set
The operation set refers to a collection of operation rights. The operation set is used to assign the viewing right to a user or user group. When an operation set is assigned to a user or a user group, the user or user group has the right to operate the devices. By default, the Nastar operation sets are classified into the following types by operation object:
l
AllDeviceOperations is of the network devices type. It contains the rights to operate all devices. AllApplicationOperations is of the network management applications type. It contains the rights to perform all network management operations except the operations on security applications.
Issue 03 (2010-06-30)
4-3
Concept Access control list
Description The access control list is used to allow the user to log in to the Nastar server by using the specified IP address or network segment. Thus, even if the user account and password are embezzled, the embezzler cannot use the embezzled account and password to log in to the Nastar server by using an IP address that is not included in the access control list. As a result, the Nastar security is improved. ACLs are classified into two types by effective scope:
l
System Access Control List: The ACL of the entire Nastar. All the users can log in to the Nastar only through specific IP addresses or network segments. User Access Control List: The ACL of a user. The current user can log in to the Nastar only through specific IP addresses or network segments.
4.1.3 Nastar User Rights Management Policies

You can manage user rights based on the rights management policies. By this means, the allocation of user rights is clearer, and the rights management is more simple.
l
Login right policy The user login right is the right to control Nastar user login Nastar, such as the period, IP address, and account. You need to set the security attributes for Nastar users.
Managed domain and operation right policies There are two kinds of rights to manage the NEs. One is the right to view the NEs; that is, it determines whether the Nastar user can view the NEs. This right is controlled through the managed domain. The other is the operation right. This right controls which operation that the Nastar user can perform on the NEs. To perform operations on the NEs, you must have the viewing right and operation right.
User group management policy The user group is a collection of user accounts. Users that belong to a user group have all rights of the user group. Managing user rights based on user groups makes right management conveniently and clearly. Multiple users may use the Nastar for maintenance. These users can be divided into several groups based on the managed NEs and operations. Members of each group can only perform specified operations in the specified domain. Based on operations, users can play different roles, including administrators, operators, monitors, and custom operators. User groups are set up based on roles. Users are then added to the corresponding user groups. This realizes unified management of user rights.
4.1.4 Operation Rights List for the Nastar Application

The operation right list describes operation rights of Nastar applications. You can refer to these parameters when you assign the operation rights for the Nastar users.
4-4
Issue 03 (2010-06-30)
System Maintenance Right List

Operation Right Operations of System Monitor Description Used to control the right to perform system monitoring in the Nastar. The user with this right can monitor the information such as the status of server processes and databases and modify system monitoring parameters. Used to control the right to expand the service database space of the Nastar server on the Nastar client. The user with this right can expand the service database space of the Nastar server on the client. Used to control the right to broadcast messages to online users in the Nastar. The user with this right can send and receive broadcast messages. Used to control the right to browse system monitor details in the Nastar. Used to browse system monitor details such as the status of services, processes and databases. Used to control the right to set broadcast message parameters in the Nastar. The user with this right can set the number of displayed broadcast messages and the number of the broadcast messages that are stored on the server. Used to control the right to manage system monitoring in the Nastar. The user with this right can perform system monitoring such as task management and data management. Used to control the right to create, modify, and delete timing tasks in the Nastar. The user with this right can create, modify, and delete timing tasks. Entry Choose System > System Monitor from the main menu.
Expand Database Space
Choose System > System Monitor > Browse from the main menu, and then click the Database Monitor tab.
Broadcast Messages
Choose Tools > Broadcast Message from the main menu.
Browse System Monitor Details
Choose System > System Monitor > Browse from the main menu.
Set Broadcast Message Parameters
Choose Tool > Broadcast Message. Click Options from the main menu.
Manage SystemMonitor
TaskManager Management
Choose Tool > Task Management from the main menu.
Issue 03 (2010-06-30)
4-5
Log Right List

Operation Right Log rights management Description Used to control the basic rights to manage logs in the Nastar. Users with this right can perform log operations only when they have the related rights such as the rights to query operation logs and set the operation log template.
NOTE If a user does not select the right to manage logs is not selected, when this user selects the related rights such as the rights to query operation logs and set the operation log template, the right to manage logs is automatically selected.
Entry -
Query Operation Logs
Used to control the right to query operation logs in the Nastar. The user with this right can set conditions to query and collect statistics on operation logs. Used to control the right to query system logs in the Nastar. The user with this right can set conditions to query and collect statistics on system logs. Used to control the right to set the operation log template in the Nastar. The user with this right can set the operation log template. Used to control the right to set the system log template in the Nastar. The user with this right can set the system log template.
Choose Security > Log from the main menu.
Query System Logs
Choose Security > Log from the main menu.
Set Operation Logs Template
Choose Security > Log from the main menu. In the window for querying logs, set template functions. Choose Security > Log from the main menu. In the window for querying logs, set template functions.
Set System Logs Template
Default Operation Set

Operation Set AllApplicationOperations Description By default, the Nastar provides the operation set of NMS applications type. The set contains the rights to perform all NMS operations except the operations on security management. Entry Choose Security > Security Management from the main menu, and then expand the Operation set node.
4-6
Issue 03 (2010-06-30)
4.2 Setting Security Policies of Nastar Users

You can set the password policy and account policy of the Nastar user, to enhance the security. 4.2.1 Setting the Nastar Login Mode The Nastar provides two login modes: multiuser mode and single-user mode. In normal state, the Nastar runs in multiuser mode. When you need to maintain the Nastar server, you can set the Nastar to run in single-user mode to avoid the interference from other users. 4.2.2 Setting the Access Control List By setting the system or current user access control list (ACL), you can allow the client or user to log in to the Nastar from the computer with specified IP address or network segment. 4.2.3 Setting the Password Policy To improve Nastar security, you can set the password policy to prevent the user from using insecure passwords. 4.2.4 Setting the Account Policy You can set the account policy to ensure account security.
4.2.1 Setting the Nastar Login Mode

The Nastar provides two login modes: multiuser mode and single-user mode. In normal state, the Nastar runs in multiuser mode. When you need to maintain the Nastar server, you can set the Nastar to run in single-user mode to avoid the interference from other users.
Context
Only the Administrator user can set the Nastar login mode.
CAUTION
Only the Administrator user can log in to the Nastar through a client and all the other users are forced to log out after the Nastar is switched from the multiuser mode to single-user mode. Switch to the multiuser mode after you complete the operations in the single-user mode to ensure that others can use the Nastar normally.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences dialog box, choose System Login Mode in the navigation tree on the left. Step 3 Set the Nastar login mode in the area on the right.
Issue 03 (2010-06-30)
4-7
Setting Login Mode Switch to a single-user mode
Operations Choose Single-user mode and click OK. In the Set Switch Delay dialog box, set the delay of login mode switch, and then click OK.
l
If the delay time is not 0, a dialog box is displayed. After the switch delay, the Nastar is switched to the single-user mode. If the delay time is 0, the warning dialog box is not displayed. The Nastar is switched to the single-user mode immediately.
on the status bar. The single-user Move the pointer to mode tip is displayed. It indicates that the Nastar works in single-user mode. Switch to a multiuser mode Choose Multiuser mode, and then click OK. The Nastar is switched to the multiuser mode immediately. Move the pointer to on the status bar. The multiuser mode tip is displayed. It indicates that the Nastar works in multiuser mode. ----End
4.2.2 Setting the Access Control List

By setting the system or current user access control list (ACL), you can allow the client or user to log in to the Nastar from the computer with specified IP address or network segment.
Context
l
The Administrator user has the permission to set the ACL of any user in the Nastar. The user in the security administrator group has the permission to set the ACLs of the other users except the Administrator. The system ACL allows all the Nastar users to log in to the Nastar only through the clients of the specific IP addresses or network segment. The user ACL is a subset of the system ACL. The user ACL is effective only for the current user.
WARNING
If there are multiple network adapters on the host where the client exists, you need to add the IP addresses of all network adapters to the ACL. This ensures that the Nastar client logs in normally.
Procedure
l
4-8
Set the system ACL.

1. 2.
Choose Security > ACL from the main menu. In the ACL dialog box, set the system ACL. Set the system ACL Add a system ACL item Operation Click Add. In the New System Access Control Item dialog box, set the information about the new system ACL item, and then click OK. 1. In the ACL dialog box, select the system ACL item to be modified, and then click Modify. 2. In the Modify System Access Control Item dialog box, modify the information about the ACL item, and then click OK. Delete a system ACL item In the ACL dialog box, select the system ACL item to be deleted, and then click Delete. In the Confirm dialog box, click Yes.
Modify a system ACL item
Use the user ACL. 1. 2. 3. Choose Security > Security Management from the main menu. In the Security Management navigation tree, expand the User node and then select a user. On the right of the interface, click the ACL tab and set the user ACL.
NOTE
l l
Use the system ACL: The ACL is not separately set for the user. Instead, the system ACL is used to control the IP addresses and network segments that the user can use for login. Use the current user ACL: The ACL is separately set for the user. The items in this user ACL must be selected from the system ACL. That is, this user ACL is a subset of the system ACL, and it functions for the current user only. Click Set ACL at the lower right corner of the ACL tab. In the displayed system ACL dialog box, modify the system ACL.
----End
4.2.3 Setting the Password Policy

To improve Nastar security, you can set the password policy to prevent the user from using insecure passwords.
Context
l l
The setting of the password policy takes effect for all Nastar users. The password policy specifies the password complexity, update period, and character restrictions. Using the password policy prevents users from setting a very simple password or using the same password for a long time.
Procedure
Step 1 Choose Security > Security Policy from the main menu.
Step 2 In the Security Policy dialog box, click the Password Policy tab. Step 3 Set the basic and advanced parameters of the password policy as required. For details about the parameters displayed on the Password Policy tab, see 4.9.1 Parameters for Setting a Nastar Password Policy. Step 4 Click OK. ----End
4.2.4 Setting the Account Policy

You can set the account policy to ensure account security.
Procedure
Step 1 Choose Security > Security Policy from the main menu. Step 2 In the Security Policy dialog box, click the Account Policy tab. Step 3 Set the account policy as required. For details about the parameters displayed on the Account Policy tab, see 4.9.2 Parameters for Setting a Nastar Account Policy. Step 4 Click OK. ----End
4.3 Creating Nastar Users and Assigning Permissions

This section describes how to create Nastar users and assign rights to them. 4.3.1 Procedure for Creating Nastar Users This section describes how to create Nastar users after the initial installation of the Nastar and during routine maintenance. 4.3.2 Creating an Operation Set The operation set is a collection of operations. Permissions on devices and applications can be assigned and managed in a unified manner based on operation sets. 4.3.3 Creating a User Group You can create a Nastar user group. The users with the same permissions assigned belong to the same user group. After you set the managed domain and operation rights for a user group, all users in this group have the rights. This helps you to assign rights to multiple users conveniently. 4.3.4 Creating a Nastar User Account You can create a user account of the Nastar and assign rights to Nastar users based on their responsibilities. 4.3.5 Examples for Creating Nastar Users and Assigning Permissions This topic presents two examples to describe how to create users and grant rights in different scenarios.
4.3.1 Procedure for Creating Nastar Users

This section describes how to create Nastar users after the initial installation of the Nastar and during routine maintenance.
Scenario Operations performed after the initial installation of the Nastar is successful
Procedure 1. Creating an Operation Set 2. Creating a Nastar User Group 3. Assigning the Managed Domain for a Nastar User Group 4. Assigning Operation Rights to a Nastar User Group 5. Creating a Nastar User Account 6. Adding a Nastar User to a User Group 7. Assigning the Managed Domain for a Nastar User 8. Assigning Operation Rights to a Nastar User 9. Assigning the User ACL
Description In this scenario, operation sets, and user groups have not been created and configured. Therefore, you need to create and configure them before creating users.
Operations performed during routine maintenance of the Nastar
1. Creating a Nastar User Account
In this scenario, operation sets, and 2. Adding a Nastar User to a User user groups are already created and configured. Therefore, you need to Group create Nastar users and add them to the user groups only.
4.3.2 Creating an Operation Set

The operation set is a collection of operations. Permissions on devices and applications can be assigned and managed in a unified manner based on operation sets.
Context
l l
Operation sets can be allocated to users or user groups. If an operation set is allocated to a user group, all members in the user group have the permissions of the operations included in the operation set. The Nastar provides two default operation sets: AllApplicationOperations and AllObjectOperations. AllObjectOperations is the operation set of network devices. AllApplicationOperations is the operation set of network management applications.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, right-click the Operation Set node and then choose New Operation Set. Otherwise, click New Operation Set. on the toolbar of the navigation tree, choose
Step 3 In the New Operation Set dialog box, set the properties of the new operation set.
Properties of Operation Set
Operations
Details of Operation On theDetails tab, enter the type, name, and description of the new set operation set.
NOTE Name is mandatory.
Members of Operation set
On the Members tab, perform the following operations: 1. Click Select. 2. Select an operation or operation set, and move it to Selected Rights.
l
You can click sets to Selected Rights.
to move all operations and operation
You can select operations or operation sets from the Available to move the Rights navigation tree, and then click selected operations or operation sets to Selected Rights.
3. Click OK.
NOTE
Click Copy member from operation set. In the Copy member from operation set dialog box, select operation sets and copy the members of these operation sets.
Step 4 In the New Operation Set dialog box, click OK. ----End
4.3.3 Creating a User Group

You can create a Nastar user group. The users with the same permissions assigned belong to the same user group. After you set the managed domain and operation rights for a user group, all users in this group have the rights. This helps you to assign rights to multiple users conveniently.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, right-click the User Group node and select New User Group. Step 3 In the New User Group dialog box, set the properties of the new user group. You must manually set the name of the user group. For the other properties of user group, you can set them after you create the user group successfully.
4-12
Issue 03 (2010-06-30)
User Group Properties User group name information Members of user group
Operations
On the Details tab, set the user group name, description, type and maximum sessions.
l
To add members, on the Details tab, click Add. In the Add User dialog box, set the members to be added to the user group. To delete members, on the Details tab, select the members to be deleted from Members, and then click Delete.
Management domain of user group Operation permissions of user group
On the Domain tab, click Select. In the Select Domain dialog box, set the management domain of the user group, and then click OK.
On the Operation Rights tab, click Select, in the Select Rights dialog box, set the operation rights of the user group, and then click OK.
NOTE
Click Copy Rights from User Group. In the Copy Rights from User Group dialog box, select user groups and copy the management domain rights and operation permissions of these user groups.
Step 4 In the New User Group dialog box, click OK. ----End
4.3.4 Creating a Nastar User Account

You can create a user account of the Nastar and assign rights to Nastar users based on their responsibilities.
Context
When you create a Nastar user, the property settings must comply with the password policy and the account policy.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management window in the Security Management navigation tree, right-click the User node and choose New User. Step 3 In the New User dialog box, set the properties of the new user. You must manually set the user name and password. For the other properties, you can use default values or set them after you create the user account successfully.
Issue 03 (2010-06-30)
4-13
User Properties Normal properties
Operations On the Details tab, set user properties, such as user name, description content, and password.
l
Owner group
To add owner groups, on the User Groups tab, click Add, select the user groups to which you want to add the user. To delete owner groups, on the User Groups tab, select the user groups to be deleted from the user group list, and then click Delete.
Management domain of user On the Domain tab, click Select. In the Select Domain dialog box, set the management domain of the user. Operation rights of user On the Operation Rights tab, click Select. In the Select Rights dialog box, set operation rights of the user. On the ACL tab, set the ACL for the user.
Access control list (ACL)
NOTE
Click Copy Rights from User. In the Copy Rights from User dialog box, select user groups and copy the management domain rights and operation permissions of these users.
Step 4 In the New User dialog box, click OK. ----End
4.3.5 Examples for Creating Nastar Users and Assigning Permissions

This topic presents two examples to describe how to create users and grant rights in different scenarios.
Example in Initial Configuration

Create a new office. Monitor and manage the devices in the new office through the Nastar in a centralized manner. The devices are divided into one part based on their locations (area A), and are monitored and maintained respectively. Accounts and rights must be granted for the personnel to monitor and maintain the devices through the Nastar. To create accounts and grant rights through the Nastar, proceed as follows: 1. Create operation sets. Operation rights can be granted in a unified manner through the operation sets. Based on roles, create a administrator's operation set, a operation set of the maintenance personnel, and a operation set of the monitor personnel. The operation sets provide operation rights. For details on how to create the operation sets, see 4.3.2 Creating an Operation Set. 2.
4-14
Create new user groups.

To facilitate management, the administrator adds six new user groups in addition to the existing four groups. The new user groups are as follows: User Group Administrators (area A) Description Responsible for network management of area A. This user group manages device set A, and has the rights for the administrator's operation set. Operators (area A) Responsible for maintaining the NEs in area A. This user group manages device set A, and has the rights for the operation set of the maintenance personnel. Monitors (area A) Responsible for monitoring the status of the NEs in area A. This user group manages device set A, and has the rights for the operation set of the monitor personnel.
For details on how to create user groups, see 4.3.3 Creating a User Group. 3. Create user accounts. Create accounts based on the employee situation. To ensure security, perform the following operations:
l l l
Set different login times based on the shifts. Bind IP addresses of area workstations to users. Change the user password when you are logging in for the first time.
For details on how to create user accounts, see 4.3.4 Creating a Nastar User Account. 4. Add users to user groups. Assign the user accounts to user groups based on the user roles. The user accounts have the managed domain and operation rights of the corresponding user groups. When the configuration is complete, the administrator can provide the accounts to relevant personnel.
Example in Routine Maintenance Scenario

Your department has a new employee who is responsible for using the Nastar to monitor the status of NEs. The procedure for assigning the user rights is as follows:
l
Create user accounts. To perform the operation, the employee needs to register a user account. The administrator creates user A for the employee. The administrator also sets the security attributes, such as the login duration and login IP addresses.
Add the Nastar User to a User Group Add user A to the monitor group. User A then inherits all the management and operation rights of the group.
When the operations are complete, the administrator can provide the accounts to the new employee.
4.4 Comparing the Nastar User Rights

By comparing the rights of two Nastar users, you can understand the differences between their rights.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management window, click navigation tree. on the top of the Security Management
Step 3 In the Select User for Compare dialog box, select a user from the left and right group boxes respectively.
NOTE
In the Nastar, you cannot compare the same user. If you select the same user in the left and right areas, the Compare button becomes unavailable.
Step 4 Click Compare. In the Compare User Rights Result dialog box, the Nastar can display user rights in the following two modes:
l l
Display all right: All user rights are displayed in the group box. Display only differences: Only the differences between user rights are displayed in the group box.
----End
4.5 Querying the Authorization

In the Nastar, you can query the users or user groups that certain operation rights are assigned to.
Context
The Administrators group contains all Nastar operation rights except the security management rights. In the query authorization dialog box, if you select an operation node or operation set node, the Authorized User/User Group area always displays the information that the operation rights are assigned to the Administrator group.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management window, click navigation tree. on the top of the Security Management
Step 3 In the Authorization Details dialog box, expand the root node or parent node in the navigation tree, and select a node.
After selection, the corresponding operations or operation sets are displayed in the Operation area. Step 4 In the Operation area, expand the root node or parent node, and then select an operation. On the right of the interface, the users and user groups that the operation rights are assigned to are displayed in the Authorization User/User Group area. ----End
4.6 Modifying a Nastar User

This section describes how to modify the password, general properties, managed domain, and operation rights of the Nastar user. 4.6.1 Resetting the Password of a Nastar User This section describes how the user in SMManagers reset the password of a Nastar user. 4.6.2 Modifying an Operation Set You can modify an operation set, such as the name and description of an operation set. You can also add operations to an operation set, or delete operations from an operation set. 4.6.3 Modifying a User Group This section describes how to modify the basic information about a Nastar user group, permissions, and manageable devices. 4.6.4 Modifying the Information about a Nastar User This section describes how to modify the basic information about a Nastar user, permissions, and manageable devices.
4.6.1 Resetting the Password of a Nastar User

This section describes how the user in SMManagers reset the password of a Nastar user.
Context
l l
The password setting must comply with the password policy. The SMManagers user can reset the passwords of other users (excluding the Administrator user). The password of the Administrator can be changed by only the Administrator through the Nastar client. If you forget your password, contact the user in SMManagers to reset the password.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 Under the navigation tree in the Security Management window, expand the User node. Rightclick the user whose password you want to reset, and then choose Reset Password. Step 3 In the Reset Password dialog box, set New Password and Confirm Password, and then click OK.
Issue 03 (2010-06-30)
4-17
NOTE
If User must change password for next login is selected, you need to change the password when you log in to the Nastar next time. Otherwise, you need not to change the user password when you log in to the Nastar next time.
Step 4 In the displayed dialog box, click OK. ----End
4.6.2 Modifying an Operation Set

You can modify an operation set, such as the name and description of an operation set. You can also add operations to an operation set, or delete operations from an operation set.
Context
l l l
You cannot modify the default operation set. Operation sets and operation permissions are already created in the Nastar. Only the users in Subdomain Security Administrator Group and Security Manager User Group have the right to modify operation sets.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, expand the Operation Set node, and then select an operation set. Modifying an Operation Set Modify normal properties Operations
Click the Details tab. Modify the operation set name and description (the type of operation set cannot be changed). After modification, click Apply in the lower part of the list box. Click the Members tab. At the bottom of the tab, click Select. In the Select Operation Set Member dialog box, set the member of the operation set, and then click OK. On the Applicable for tab, you can view only the users or user groups served by the operation set. The Applicable for tab displays the users or user groups served by the device set.
Set members of a operation set
Set parameters on the Applicable for tab page
4-18
Issue 03 (2010-06-30)
Modifying an Operation Set Allocate an operation set
Operations
To allocate an operation set to a user or user group, do as follows: 1. Expand the User or User Group node and choose a user or user group. 2. Click the Domain tab on the right of the interface. 3. Click Select. In the displayed Select Domain dialog box, add a device set to the user or user group. 4. Open the Security Management window. Click the Operation Rights tab on the right of the window. 5. Click Select. 6. Select network device operations or network management applications.
l
Network Device In the Select Domain dialog box, select a device set. In the Operations area, select the corresponding operation set.
Network Management Application In the Select Domain dialog box, choose Network Management Application in the navigation tree of authorized objects. In the Operations area, select the corresponding operation set.
7. Click Selected Rights. 8. Click Ok. ----End
to move the selected operation set to
4.6.3 Modifying a User Group

This section describes how to modify the basic information about a Nastar user group, permissions, and manageable devices.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, expand the User Group node. Select the user group to the modified. Step 3 In the area on the right , select a tab to modify the information about the user group.
Issue 03 (2010-06-30)
4-19
Modify Properties Modify general properties
Operation Click the Details tab. Modify the user group name, maximum sessions and description (the type of user group cannot be changed). After modification, click Apply. To add users, click Add on the Members tab. In Add User, add users. To delete users, select the user group and then click Delete. On the Members tab, view the users that belong to the user group.
Change users of the user group
Modify the managed On the Domain tab, click Select. In Select Domain dialog box, add or domain delete devices or device sets. Modify operation rights On the Operation Rights tab, click Select. In Select Rights dialog box, add or delete the permissions to operate network management applications and network device operate sets. Click the Current Session tab to view the online users of the user group.
Query current sessions ----End
4.6.4 Modifying the Information about a Nastar User

This section describes how to modify the basic information about a Nastar user, permissions, and manageable devices.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management window, in the Security Management navigation tree, expand the User node. Step 3 Select the user whose information you want to modify, and then modify the information about this user on a tab in the right area. Modify Properties Modify general properties Change the owner user group Operation Perform operations on the Details tab, modify user information(The dimmed controls are unavailable). To add a user group, click Add on the User Groups tab. In Add User Group, add a user group. To delete a user group, click Delete.
4-20
Issue 03 (2010-06-30)
Modify Properties
Operation
Modify the managed On the Domain tab, click Select. In Select Domain, you can perform domain the following operations:
l l
Add objects or object sets. Delete objects or object sets.
Modify operation rights
On the Operation Rights tab, click Select. In Select Rights, you can perform the following operations:
l
Add the permissions to operate NMS applications, object, object sets and so on. Delete the permissions to operate NMS applications, object, object sets and so on.
Modify the ACL
To set the IP addresses that the user can access, select Use the system ACL and Use the current user ACL on the ACL tab. To add, modify, or delete IP addresses or network segments, select ACL.
----End
4.7 Managing Nastar Operation Sets

This section describes how to create, modify, and delete operation sets. 4.7.1 Nastar Operation Sets This section describes the basic meaning and function of the operation set. 4.7.2 Creating an Operation Set The operation set is a collection of operations. Permissions on devices and applications can be assigned and managed in a unified manner based on operation sets. 4.7.3 Modifying an Operation Set You can modify an operation set, such as the name and description of an operation set. You can also add operations to an operation set, or delete operations from an operation set. 4.7.4 Deleting an Operation Set The operation set used no longer should be deleted immediately. 4.7.5 Exporting or Importing Operation Sets The Nastar supports the export and import of operation sets. You can arrange the operation sets in the Nastar by importing an operation set file.
4.7.1 Nastar Operation Sets

This section describes the basic meaning and function of the operation set. The Nastar operation set is a collection of operation rights provided by the Nastar. By default, the Nastar provides two operation sets: AllApplicationOperations and AllObjectOperations. If a user or user group can manage an operation set, it indicates that the user or user group has all the operation rights in the operation set.
The administrator can create a operation set, and then add the operation rights required in a service to the operation set. Thus, the administrator can assign the operation rights to the related user or user group in a centralized manner. In this way, the management cost of the administrator is greatly reduced.
4.7.2 Creating an Operation Set

The operation set is a collection of operations. Permissions on devices and applications can be assigned and managed in a unified manner based on operation sets.
Context
l l
Operation sets can be allocated to users or user groups. If an operation set is allocated to a user group, all members in the user group have the permissions of the operations included in the operation set. The Nastar provides two default operation sets: AllApplicationOperations and AllObjectOperations. AllObjectOperations is the operation set of network devices. AllApplicationOperations is the operation set of network management applications.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, right-click the Operation Set node and then choose New Operation Set. Otherwise, click New Operation Set. on the toolbar of the navigation tree, choose
Step 3 In the New Operation Set dialog box, set the properties of the new operation set. Properties of Operation Set Operations
Details of Operation On theDetails tab, enter the type, name, and description of the new set operation set.
NOTE Name is mandatory.
Members of Operation set
On the Members tab, perform the following operations: 1. Click Select. 2. Select an operation or operation set, and move it to Selected Rights.
l
You can click sets to Selected Rights.
to move all operations and operation
You can select operations or operation sets from the Available to move the Rights navigation tree, and then click selected operations or operation sets to Selected Rights.
3. Click OK.
4-22
Issue 03 (2010-06-30)

NOTE
Click Copy member from operation set. In the Copy member from operation set dialog box, select operation sets and copy the members of these operation sets.
Step 4 In the New Operation Set dialog box, click OK. ----End
4.7.3 Modifying an Operation Set

You can modify an operation set, such as the name and description of an operation set. You can also add operations to an operation set, or delete operations from an operation set.
Context
l l l
You cannot modify the default operation set. Operation sets and operation permissions are already created in the Nastar. Only the users in Subdomain Security Administrator Group and Security Manager User Group have the right to modify operation sets.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, expand the Operation Set node, and then select an operation set. Modifying an Operation Set Modify normal properties Operations
Click the Details tab. Modify the operation set name and description (the type of operation set cannot be changed). After modification, click Apply in the lower part of the list box. Click the Members tab. At the bottom of the tab, click Select. In the Select Operation Set Member dialog box, set the member of the operation set, and then click OK. On the Applicable for tab, you can view only the users or user groups served by the operation set. The Applicable for tab displays the users or user groups served by the device set.
Set members of a operation set
Set parameters on the Applicable for tab page
Issue 03 (2010-06-30)
4-23
Modifying an Operation Set Allocate an operation set
Operations
To allocate an operation set to a user or user group, do as follows: 1. Expand the User or User Group node and choose a user or user group. 2. Click the Domain tab on the right of the interface. 3. Click Select. In the displayed Select Domain dialog box, add a device set to the user or user group. 4. Open the Security Management window. Click the Operation Rights tab on the right of the window. 5. Click Select. 6. Select network device operations or network management applications.
l
Network Device In the Select Domain dialog box, select a device set. In the Operations area, select the corresponding operation set.
Network Management Application In the Select Domain dialog box, choose Network Management Application in the navigation tree of authorized objects. In the Operations area, select the corresponding operation set.
7. Click Selected Rights. 8. Click Ok. ----End
to move the selected operation set to
4.7.4 Deleting an Operation Set

The operation set used no longer should be deleted immediately.
Context
You are not allowed to modify default operation sets AllObjectOperations and AllApplicationOperations.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, double-click the Operation Set node. The table on the right displays all operation sets. Step 3 Select the operation sets you want to delete, right-click to choose Delete or click Delete at the bottom of the list.
Step 4 In the Confirm dialog box, click Yes. ----End
4.7.5 Exporting or Importing Operation Sets

The Nastar supports the export and import of operation sets. You can arrange the operation sets in the Nastar by importing an operation set file.
Context
l l l
Only the administrator has the permissions to export and import operation sets. The Nastar supports the export and import of .csv files. The Nastar supports the function of adding the information about operation sets in columns one by one. After a .csv file that contains the operation set information is imported to the Nastar, the information is displayed as operation sets of the Nastar. To add a column of operation set information to a .csv file, you need to fill in the following two types of information so that operation sets can be imported to the Nastar successfully:
Apart from the information that already exists in a .csv file, you must enter the name of the operation set in the first row of the column where operation sets are to be added. Apart from the information that already exists in a .csv file, if you want to add operation rights, enter an uppercase Y in the other rows of the column where operation sets are to be added. Y indicates that the information in the rows with Y is included in operation sets and is to be displayed in the Nastar.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 Click on the top of the Security Management navigation tree.
Step 3 Export and import operation sets. Export and import operation sets Export operation Sets Operation
1. Select Export operation Sets in the drop-down list. 2. In the Save dialog box, set the path and file name for saving the exported operation sets.
NOTE The number of the operation set files that are generated by the Nastar is the same as that of the existing operation set types.
3. Click Save.
Issue 03 (2010-06-30)
4-25
Export and import operation sets Import operation Sets
Operation
1. Select Import operation Sets in the drop-down list. 2. In the Open dialog box, select the file to be imported.
NOTE If the names of the operation sets in a column of a file are the same as those in the Nastar, the Nastar cannot import the operation set information of this column.
3. Click Open. ----End
Example
The following table describes the function of each part of a .csv file and helps you to understand specific operations. The following is a sample of an exported .csv file:
Table 4-1 Parts of a .csv file Colum n/Row Columns A to E Description NastarThis part displays the information about operation rights that is provided by default.
WARNING If service requirements are met, do not modify this part. If you modify it, the Nastar may run abnormally. If an exception occurs after modification, contact Huawei technical support engineers.
4-26
Issue 03 (2010-06-30)
Colum n/Row Column F
Description In column F, OpeSet_A indicates the exported operation sets. Y indicates a member that belongs to OpeSet_A in the Nastar. The following figure shows that the operations sets in a .csv file are displayed in the Nastar:
Columns G to the end
You can add an operation set to the tenth row according to service requirements, and fill Y in the corresponding column.
4.8 Monitoring a Nastar User

This section describes how to monitor Nastar user sessions and operations, force Nastar users to exit, unlock Nastar user accounts and send messages to online users. 4.8.1 Monitoring the Nastar User Sessions User sessions record the login time, group, and operation terminal. By monitoring the user sessions, you can know the users who have logged in to the system and force the users who may affect system security to log out as required, thus ensuring system security. 4.8.2 Forcing a User to Quit a Session You can force a Nastar user to quit session if the user performs dangerous operations or initiates illegal sessions. 4.8.3 Unlocking a User Account This section describes how the user with the right to unlock a user unlocks a locked user. 4.8.4 Sending Messages to Online Users You can send messages to the users of the specified sessions or all sessions. Thus, users in different regions can communicate with each other on the Nastar maintenance experience in real time.
4.8.1 Monitoring the Nastar User Sessions

User sessions record the login time, group, and operation terminal. By monitoring the user sessions, you can know the users who have logged in to the system and force the users who may affect system security to log out as required, thus ensuring system security.
Issue 03 (2010-06-30)
4-27
Context
l
A session refers to the connection established between the client and the server. The session starts when the user logs in to the client, and ends when the user logs out of the client. Multiple sessions can be created by using one Nastar user account. In the Nastar, a user account can be used to log in to multiple clients concurrently. You can set the maximum number of clients that a user account can log in to concurrently in Maximum of online users on the Details tab. If this user account is used to log in to a certain number of clients, the same number of sessions are established.
When the client uses multiple network adapters, the value of Operation Terminal is selected randomly among available IP addresses of the client.
Procedure
Step 1 Choose Security > User Session Monitoring from the main menu. Step 2 In the Monitor User Sessions window, view the information about login and other operations performed by Nastar users. Monitored Mode Session Monitor Operation In the Session Monitor area, you can view the information about online users and sessions.
NOTE
l After the Nastar server is restarted or the network is recovered from a
disconnection, you need to click Refresh to update the session monitoring table.
l If you select the local client in the Session Monitor area, Force User to
Exit becomes unavailable.
Operation Monitor
In the Operation Monitor area, you can view the information about operations corresponding to sessions. 1. In the Session Monitor area, select a session. 2. In the Operation Monitor area, select Filter. 3. In the Filter dialog box, set the filtering condition such as Operation, Operation Object, or Operation Result. The operation information that meets the filtering condition is displayed in the Operation Monitor area. 4. Double-click an operation record. In the Operation Details dialog box, view the monitored information.
NOTE The Operation Monitor area displays only the operations performed after the Monitor User Sessions window is opened. After a monitored user performs operations, the operation monitoring table is updated in real time.
----End
4-28
Issue 03 (2010-06-30)
4.8.2 Forcing a User to Quit a Session

You can force a Nastar user to quit session if the user performs dangerous operations or initiates illegal sessions.
Context
l
If you force a user to quit session, only the user corresponding to a session is logged out forcibly. For example, user A logs in to the same Nastar server through clients B and C. In this case, sessions D and E are generated. If you want to force the user A of session D to quit, session E of user A is not affected. Current users logged in cannot force themselves to quit from their corresponding sessions.
Procedure
Step 1 Choose Security > User Session Monitoring from the main menu. Step 2 From the session monitoring table, select the records of the sessions to quit forcibly, and then click Force User to Exit. Step 3 In the confirm dialog box, click Yes. ----End
4.8.3 Unlocking a User Account

This section describes how the user with the right to unlock a user unlocks a locked user.
Context
l l l
Only the SMManagers user has the permission to unlock a user. In the Nastar, a user can be unlocked manually or automatically. You can set the automatic unlocking time in Account Policy. Choose Security > Security Policy. In the displayed Security Policy dialog box, click the Account Policy tab, and then set Auto Unlock.
Procedure
Step 1 The Nastar supports the following user unlocking modes. Unlocking Mode Manual unlocking Operation Only the user with the rights of the SMManagers group can perform the following operations: 1. Choose Security > Security Management. 2. In the Security Management navigation tree, expand the User node. 3. Right-click the locked user account, and choose Unlock User. After that, the unlocked user can log in to the Nastar successfully.
Issue 03 (2010-06-30)
4-29
Unlocking Mode Automatic unlocking ----End
Operation The locked user can log in successfully only when the time reaches the preset automatic unlocking time.
4.8.4 Sending Messages to Online Users

You can send messages to the users of the specified sessions or all sessions. Thus, users in different regions can communicate with each other on the Nastar maintenance experience in real time.
Context
In the Nastar, the user of the current session cannot send messages to himself or herself.
Procedure
Step 1 Choose Security > User Session Monitoring from the main menu. Step 2 In the Monitor User Sessions area, send messages to the users of the specified sessions or all sessions. Sessions to Be Sent Operation A session Right-click a session and choose Send Message. Enter the message contents, and then click Send. Press the Ctrl + Shift to select multiple sessions. Right-click the selected sessions and choose Send Message. Enter the message contents, and then click Send. Use the combination key Ctrl+A to select all sessions. Right-click the selected sessions and choose Send Message. Enter the message contents, and then click Send.
Multiple sessions
All sessions
----End
4.9 Reference of the Security Management GUI

This topic provides the reference information of the security management GUI. 4.9.1 Parameters for Setting a Nastar Password Policy This section describes the parameters for setting a password policy. When setting a password policy, you can refer to this topic. 4.9.2 Parameters for Setting a Nastar Account Policy This section describes the parameters for the Account Policy tab. When setting an account policy, you can refer to this topic.
4.9.3 Parameters for Creating a User This section describes the parameters for creating a user account. When creating a user account, you can refer to this section. 4.9.4 Parameters for Creating a Nastar User Group This section describes the parameters for the New User Group dialog box. When creating a user group, you can refer to this topic. 4.9.5 Parameters for Creating an Operation Set This section describes the parameters for creating an operation set dialog box. When creating an operation set, you can refer to this topic. 4.9.6 Parameters for Setting the Nastar User Information This section describes the parameters for setting the general information about a user. When setting the general information about a user, you can refer to this section. 4.9.7 Parameters for Setting the Nastar User Group Information This section describes the parameters for setting the general information about a user group. When setting the general information about a user group, you can refer to this section. 4.9.8 Parameters for Assigning Operation Rights to Nastar Users and User Groups This section describes the parameters for assigning operation rights to users and user groups. When assigning operation rights to users and user groups, you can refer to this topic.
4.9.1 Parameters for Setting a Nastar Password Policy

This section describes the parameters for setting a password policy. When setting a password policy, you can refer to this topic.
Common parameters
Parameters Min. Length of common user password Min. Length of super user password Max. Length of password Description Description: Minimum length of a common user password. Description: Minimum length of the Administrator password. Description: Maximum length of a user password. Settings Value: Value range: 6-16. Default value: 8. Value: Value range: 6-16. Default value: 8. Value: Value range: 6-16. Default value: 16. Max. period for password repetition (month) Description: Maximum period (in months) for password repetition when a user changes a password. Value: Value range: 0-12. Default value: 0. The value 0 indicates that the password is not restricted by this security policy.
Issue 03 (2010-06-30)
4-31
Parameters Maximum validity period of the password (days)
Description Description: Maximum validity period of the password in the Nastar.
Settings Value: Value range: 1-999. Default value: 180. If you select the Unlimits check box on the right, the password is always valid.
Minimum validity period of the password (days)
Description: Minimum validity period of the password in the Nastar. If the password use period is shorter than the minimum validity period, the password cannot be changed. Description: Warning days when the password expires. Description: In the The Password Cannot Be Similar to History Passwords area, set the relationships between the password of the created user and the latest history passwords.
Value: Value range: 1-999. Default value: 10. If you select the Unlimits check box on the right, you can change a password at any time. Value: Value range: 1-30. Default value: 10. Setting method: Value: Number of history passwords that the current password cannot be similar to and Number of characters in history passwords that the current password cannot contain.
NOTE Before setting Number of history passwords that the current password cannot be similar to and Number of characters in history passwords that the current password cannot contain, select Enable. Entire password indicates whether the new password completely matches with the latest history passwords.
Number of days warning given before password expire The Password Cannot Be Similar to History Passwords
Advanced parameters
Parameters Min. Different characters between new and old password Description Description: The minimum number of different characters between the new password and the old password. Settings Value: Value range: 3-16. Default value: 3.
4-32
Issue 03 (2010-06-30)
Parameters Min. Letter
Description Description: Minimum letters in a password.
Settings Value: Value range: 0-16. Default value: 1. If you select the Letters are prohibited check box on the right, it indicates that you cannot enter letters.
Min. Uppercase
Description: Minimum uppercase letters in a password.
Value: Value range: 0-16. Default value: 0. If you select the Uppercase are prohibited check box on the right, it indicates that you cannot enter uppercase letters.
Min. Lowercase
Description: Minimum lowercase letters in a password.
Value: Value range: 0-16. Default value: 0. If you select the Lowercases are prohibited check box on the right, it indicates that you cannot enter lowercase letters.
Min. Numbers
Description: Minimum number of numerals in a password.
Value: Value range: 0-16. Default value: 1. If you select the Numbers are prohibited check box on the right, it indicates that you cannot enter numbers.
Min. Characters
Description: Minimum special characters in a password. Such characters as ~!@#$% ^&*()_+-={}|\\:\";'?,./` are special characters.
Value: Value range: 0-16. Default value: 0. If you select the Special characters are prohibited check box on the right, it indicates that you cannot enter characters.
Issue 03 (2010-06-30)
4-33
Parameters Max. Number of same consecutive characters between username and password
Description Description: Number of the adjacent characters that can be the same in the user name and password.
Settings Value: Value range:

l l
No requirement Password cannot contain a complete username Password cannot contain XX number of consecutive characters in username
Default value: No requirement. Password cannot contain a whole word in password dictionary Description: Whether a password contains a whole word in password dictionary.
NOTE The suffix of password dictionary file names is .dic. These .dic files are present inNastar_ROOT/etc/conf/ pwddic/ on the Nastar server.
The password meets the hacker language dictionary requirements
Description: The hacker language dictionary records the situation that the invalid user defines characters (digits, letters, symbols, and ASCII codes) as other meanings (rather than their own meanings) for login. For example, the invalid user defines abcde12345 as 12345abcde. The Nastar compares the password 12345abcde with the password sequence in the hacker language dictionary during login. If the same password exists, the Nastar forbids the user to log in by using the password abcde12345. Description: Whether a password can be in reverse order of the characters in a user name. Assume that the user name is ABC123. If you select this option, you cannot set the password of this user to 321CBA.
Password cannot be any username in reverse order
4-34
Issue 03 (2010-06-30)
Parameters The Password Cannot Contain Repeated Strings
Description Description: In the The Password Cannot Contain Repeated Strings area, set the relationship between the repeated character sequence and the number of repeats in the password.
Settings Value: Value: Number of repetitions and Number of characters in a repeated string.
NOTE Before setting Number of repetitions and Number of characters in a repeated string, select Enable.
4.9.2 Parameters for Setting a Nastar Account Policy

This section describes the parameters for the Account Policy tab. When setting an account policy, you can refer to this topic.
Parameters
Name Min. Length of user name Description Description: Minimum length of the user name. Settings Value: Value range: 1-32. Default value: 6. Auto unlock (minutes) Description: Auto unlocking time specified for a user account. Value: Value range: 1-1440 Default value: 30. Select Lock permanently on the right. Thus, a locked user account cannot be automatically unlocked.
NOTE Assume that the administrator account of the Nastar is locked. If the following conditions are met, you need to log in to the Nastar server to unlock the administrator account and then run svc_releaseUser Administrator on the CLI:
l No security administrator account
exists in the Nastar.

l Lock permanently is selected.
In the account policy dialog box, if Lock permanently and Do not lock superusers are selected, the administrator account always cannot be locked.
Issue 03 (2010-06-30)
4-35
Name Delay period after the login or unlocking failure (seconds) Illegal login XX times which caused auto locked
Description Description: Wait period before performing the same operation in the case that the login or unlocking fails. Description: Maximum number of login attempts (the login fails due to incorrect passwords) by using the account registered with the Nastar. When the number of attempts reaches the specified value, the Nastar locks this account automatically. The member of the security administrator group has the permission to unlock the account.
Settings Value: Value range: 0-9999. Default value: 3.
Value: Value range: 1-99. Default value: 3.
Super user not allowed to be locked
Description: Whether the superuser account can be locked.
Value: Value range: Select or deselect the check box. Default value: Deselect the check box.
Enable the user policy of no login within a period
Description: When the user does not log in for a specified period of time, the user account is deleted or hibernated. If the user select Suspend, the state of the user account is hibernated.
Value: Value range:

l l
Delete, Suspend 1-1000 Suspend 60
Default value:
l l
Unit: day
4.9.3 Parameters for Creating a User

This section describes the parameters for creating a user account. When creating a user account, you can refer to this section.
4-36
Issue 03 (2010-06-30)
Common parameters
Parameter Copy Rights from User Description Description: Copy rights from a user. This operation is inapplicable to the default user of the Nastar. After you click Copy Rights from User, the Nastar copies the domains and operation rights from the specified user and then loads them to the added user. Settings Setting method: 1. Click Copy Rights from User. 2. In the displayed Copy Rights from User dialog box, select a user. 3. Click OK.
Parameters on the Details tab

Parameter User name Description Description: Name of a user, which is specified when the user is created. Full Name Description: Full name of a user. Settings Value: Value range: 1-32.
NOTE The minimum value is determined by Min. Length of user name in Account Policy.
Unit: character. Value: Value range: 1-50. Unit: character. Description Description: Description of a user account, which is used to distinguish users. Password Description: User password. Value: Value range: 1-100. Unit: character.
Value: Value range: 1-16.

NOTE The password lengthe value is determined by Min. Length of common user password and Min. Length of super user password in Password Policy.
Unit: character.
Issue 03 (2010-06-30)
4-37
Parameter Confirm password
Description Description: -
Settings Setting method: The value of Confirm password must be the same as that of Password. Value: Value range: Select or deselect the check box.
User must change password for next login
Description: When logging in to the Nastar next time, the user is prompted to change the password. After password change, the user can log in to the Nastar successfully. Description: The user cannot change the password on the Nastar client. Description: The user whose account is suspended cannot log in to the Nastar. Description: Minimum validity period of the password in the Nastar.
User cannot change password
Value: Value range: Select or deselect the check box.
User account is disabled
Value: Value range: Select or deselect the check box.
Maximum password valid days
Value: Value range:

l
System maximum password valid days: The value depends on Max. Validity (days) in Password Policy. Custom: 180 by default. Value range: 0-999. 0 indicates that the parameter is not restricted.
Advanced parameters
Parameter Max. onlince number Description Description: Maximum number of online user accounts. Settings Setting method:
l
Deselect Unlimits, and then set this parameter.

The default value is 30. Value range: 0-255.
Select Unlimits. Thus, the same account can be used to log in to the Nastar for any times.
4-38
Issue 03 (2010-06-30)
Parameter Wait time before auto logout(minutes)
Description Description: If the user does not perform an operation within the specified period, the user is logged out automatically. Description: Security policy of the user account. The default policy is that the user account is disabled if the user does not log in to the Nastar within 60 days. Description: -
Settings Setting method:

l
Deselect Disable, and then set this parameter.

The default value is 10 minutes. Value range: 10-600.
Select Disable.
Enable inactive user policy
Setting method:
l
Select Enable inactive user policy.
By default, the time limit is one minute. The value ranges from 1 to 1000. The available operations are: Delete, Hibernate, and Unlimits.
Deselect Enable inactive user policy. Thus, the system security policy is used.
Enable period limit
Setting method:
l
Select Enable period limit.
The time settings include the start date, end date, start time and end time of each day. The date can be Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, and Saturday.
Deselect Enable period limit. The time segment is not restricted. The maximum time segment for logging in to the Nastar is from the current time to 23:59:59 on Dec. 31st, 2037.
Parameters on the User Groups tab

Parameter Add Description Description: The Add button. Settings Setting method: Click Add. In the displayed Add User Group dialog box, select the user group to be added. Setting method: On the User Groups tab, select one or more user groups, and then click Delete to delete the selected user groups.
Delete
Description: The Delete button.
Issue 03 (2010-06-30)
4-39
Parameters on the Domain tab

Parameter Display according group by the NE Description Description: To change the ne diplay on the Domain tab. Settings Setting method: Select or deselect the check box.
Show the administrative domain of the owner user group and itself
NOTE The entry for parameter selection is Security > Security Management. Expand a user node and choose a user. Then click the Domain tab on the right of the interface.
Setting method: Select or deselect the check box.

l
If the user selects the check box, Delete on the Domain tab is dimmed. The Domain tab displays the owner group and managed domain of the user. If the user deselects the check box, Delete on the Domain tab is available. The Domain tab displays the devices that the user can manage. To delete an existing device that is not needed, the user can select it and then click Delete.
Find
Description: The Find button.
Select
Description: The Select button.
Setting method: Click Select. In the displayed Select Domain dialog box, select the manage domain to be added. Setting method: On the Domain tab, select one or more nodes, and then click Delete to delete the selected nodes.
Delete
4-40
Issue 03 (2010-06-30)
Parameters on the Operation Rights tab

Parameter Show access from user group and itself
NOTE The entry for parameter selection is Security > Security Management. Expand a user node and choose a user. Click the Operation Rights tab on the right of the interface.
Description -
Settings Setting method: Select or deselect the check box.

l
If the user selects the check box, Delete on the Operation Rights tab is dimmed. The Operation Rights tab displays the owner group and managed operation right of the user. If the user deselects the check box, Delete on the Operation Rights tab is available. The Operation Rights tab displays the operation rights that the user can manage. To delete an existing operation right that is not needed, the user can select it and then click Delete.
Find
Description: The Find button.
Select
Setting method: Click Select. In the displayed Select Rights dialog box, select the operation rights of the object to be added. Setting method: On the Operation Rights tab, select one or more nodes, and then click Delete to delete the selected nodes.
Delete
Parameters on the ACL tab

For the parameter descriptions, see 4.2.2 Setting the Access Control List.
4.9.4 Parameters for Creating a Nastar User Group

This section describes the parameters for the New User Group dialog box. When creating a user group, you can refer to this topic.
Issue 03 (2010-06-30)
4-41
Common parameters
Parameter Copy Rights from User Group Description Description: Copy rights from a user group. This operation is inapplicable to the default user group of the Nastar. After you click Copy Rights from User Group, the Nastar copies the domains and operation rights from the specified user group and then loads them to the added user group. Settings Setting method: 1. Click Copy Rights from User Group. 2. In the displayed Copy Rights from User Group dialog box, select a user group. 3. Click OK.
Parameters on the Details tab

For the parameter descriptions, see 4.9.7 Parameters for Setting the Nastar User Group Information.
Parameters on the Domain tab

Parameter Group by device type Description Description: To change the device display on the Domain tab. Description: The Find button. Select Description: The Select button. Setting method: Click Select. In the displayed Select Domain dialog box, select the domains to be added. Setting method: On the Domain tab, select one or more nodes, and then click Delete to delete the selected nodes. Settings Setting method: Select or deselect the check box. -
Find
Delete
Parameters on the Operation Rights tab

Parameter Find Description Description: The Find button. Settings -
4-42
Issue 03 (2010-06-30)
Parameter Select
Description Description: The Select button.
Settings Setting method: Click Select. In the displayed Select Rights dialog box, select the operation rights to be added. Setting method: On the Operation Rights tab, select one or more nodes, and then click Delete to delete the selected nodes.
Delete
4.9.5 Parameters for Creating an Operation Set

This section describes the parameters for creating an operation set dialog box. When creating an operation set, you can refer to this topic.
Parameter description
Parameter Copy Members from Operation Set Description Description: Copy the members of an operation set other than AllApplicationOperations and AllDeviceOperations to the created operation set. Description: Operation type of the Nastar. Settings Value: Operation set other than AllApplicationOperations and AllDeviceOperations.
Details
Type
Value: Value range:

l l
Network Device Network Management Application
Name
Description: Name of an operation set.
Value: Value range: 1-100. Unit: character.
Descripti on
Description: Details about an operation set.
Member s
Select
Setting method: Click Select. In the displayed Select Operation Set Member dialog box, select the operations and operation sets to be added.
4-43
Issue 03 (2010-06-30)
Parameter Delete
Description Description: The Delete button.
Settings Setting method: On the Members tab, select one or more operations or operation sets, and then click Delete to delete the selected items.
4.9.6 Parameters for Setting the Nastar User Information

This section describes the parameters for setting the general information about a user. When setting the general information about a user, you can refer to this section.
Parameter User Name Description Description: Name of a user, which is specified when the user is created. Settings Value: Value range: 1-32.
NOTE The minimum value is determined by Min. Length of user name in Account Policy.
Unit: character. Full Name Description: Full name of a user. Value: Value range: 0-100. Unit: character. Description Description: Description of a user account, which is used to distinguish users. User Type Description: Type of the current user. User must change password for next login Description: When logging in to the Nastar next time, the user is prompted to change the password. After password change, the user can log in to the Nastar successfully. Description: The user cannot change the password on the Nastar client. Value: Value range: 0-100. Unit: character. Value: Value range: Local User and Remote User. Value: Value range: Yes and No.
User cannot change password
Value: Value range: Yes and No.
4-44
Issue 03 (2010-06-30)
Parameter Suspend Account
Description Description: The user whose account is suspended cannot log in to the Nastar.
Settings Value: Value range: Yes and No.

NOTE The restrictions on the operations associated with the Administrator account are as follows:
l After setting Suspend Account to Yes and
applying the value, the administrator is requested to exit the client immediately and the Administrator account cannot be used to log in again.
l If the value of Suspend Account is Yes and
the period during which the Administrator account is not used exceeds the period of the inactive policy of the user, the Administrator account is not deleted, but it cannot be used any more.
l To enable the Administrator account, run
svc_enableUser on the CLI of the Nastar server. If running the command is successful, the Administrator account can be used to log in through the client.
Password Validity Period
Description: Validity period of the user password.
Setting method: Click next to Password Validity Period, and then set the password validity period in the displayed Max Valid Days dialog box.
l
System maximum password valid days: 180 Custom: 0-999 (0 indicates that the password is always valid.) Default value: 180
The password validity period is in the unit of day. Maximum of Online Users Description: Maximum number of online user accounts. Setting method:
l
Deselect Unlimits, and then set this parameter.

The default value is 30. Value range: 0-255.
Select Unlimits. Thus, the same account can be used to log in to the Nastar for any times.
Issue 03 (2010-06-30)
4-45
Parameter Auto-Exit Wait (minutes)
Description Description: If the user does not perform an operation within the specified period, the user is logged out automatically.
Settings Setting method:

l
Deselect Disable auto-exit, and then set this parameter.

The default value is 10 minutes. Value range: 10-600.
Select Disable auto-exit.
Inactive User Policy
Description: Security policy of the user account. The default policy is that the user account is disabled if the user does not log in to the Nastar within 60 days.
Setting method: next to Inactive User Policy, and Click the set this parameter in the displayed Inactive User Policy dialog box.
l
Select Enable Inactive User Policy.
By default, the time limit is one minute. The value ranges from 1 to 1000. The available operations are: Delete, Suspend, and Unlimit.
Deselect Enable Inactive User Policy. Thus, the default security policy is used.
Time Segment for Login
Description: Time segment within which the user can log in to the Nastar.
Setting method: Click next to Time Segment for Login, and then set this parameter in the displayed Login Duration dialog box.
l
Select Enable Period Limit.
The time settings include the start date, end date, start time and end time of each day. The weekdays can be Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, and Saturday.
Deselect Enable Period Limit. The time segment is not restricted. The maximum time segment for logging in to the Nastar is from the current time to 23:59:59 on Dec. 31st, 2037.
Date of Latest Password Change Date of Latest Login
Description: Date when the user changes the password last time. Description: Date when the user successfully logs in to the Nastar last time.
4-46
Issue 03 (2010-06-30)
Parameter Date of Lastest Offline
Description Description: Date when the user successfully logs out last time. Description: Login state of the current user.
Settings -
Login State
Lock State
Description: Lock state of the current user.
4.9.7 Parameters for Setting the Nastar User Group Information

This section describes the parameters for setting the general information about a user group. When setting the general information about a user group, you can refer to this section.
Parameter Name Description Description: Name of a user group, which is specified when the user group is created. The default user group of the Nastar cannot be modified. Settings Value: Value range: 1-50. Unit: character.
NOTE
l The user group name consists of
characters or letters.
l The naming format xxx_xxx is
recommended.
Description
Description: Description of a user group, which is used to distinguish user groups.
Issue 03 (2010-06-30)
4-47
Parameter User Group Type
Description Description: Type of user group.
Settings Value: Value range: Super User Group, Security Manager User Group, Default User Group, Common User Group and Subdomain Security Administrator Group
NOTE
l Super User Group, Security
Manager User Group, and Default User Group are the user groups provided by the system. They cannot be changed.
l For a new user, the value has to be
Common User Group or Subdomain Security Administrator Group.

l The operation rights of users in the
subdomain security administrator group cannot be set.
Maximum Sessions
Description: Number of user sessions in the current user group. During a specific period, the number of login times of users in this user group can be restricted by using this parameter.
Value: Value range: 0-100, and Unlimits.
4.9.8 Parameters for Assigning Operation Rights to Nastar Users and User Groups
This section describes the parameters for assigning operation rights to users and user groups. When assigning operation rights to users and user groups, you can refer to this topic.
Interface Entries
You can access the Operation Rights dialog box through one of the following two entries:
l
When you create a user or user group, click the Operation Rights tab, and then click Select. In the Security Management navigation tree, select the created user or user group. In the area on the right, click the Operation Rights tab, and then click Select.
4-48
Issue 03 (2010-06-30)
Parameters
Name Authoriz ation Objects and Operatio ns Authoriz ation Objects Description Description: Object of the operation rights. The object selected in Authorization Objects determines the operation rights displayed in Operations. Setting Setting method: 1. In the navigation tree in Authorization, choose a node. Operations lists the operations of the object synchronously. 2. In the navigation tree in Operations, choose one or more operations and operation sets. 3. Click 4. Click OK. Operatio ns Description: Operation right list. The operation rights displayed in Operations are determined by the object selected in Selected Rights. Selected rights Description: Operation rights to be assigned to the Nastar user/user group. Setting method: Operations lists the operations of the object synchronously. .
Setting method: In the navigation tree in Operations, choose one or more operations and operation sets. to move the Click selected operations and operation sets to Selected Rights.
Issue 03 (2010-06-30)
4-49
5 Log Management
5
About This Chapter
Log Management
The log records the operations and important system events on the Nastar. You can use log management to query and collect statistics on logs. 5.1 Getting to Know Log Management You can browse the details of operation logs or system logs to know the user operations or system status. 5.2 Managing Operation Logs You can query statistics on operation logs of the Nastar to understand the operation status of the Nastar. 5.3 Managing System Logs You can query statistics on system logs of the Nastar to understand the running status of the Nastar. 5.4 Managing Security Logs You can query statistics on security logs of the Nastar to understand the security operation status of the Nastar. 5.5 Setting Log Templates You can save the specific query and statistics conditions in log templates. This helps you to query and collect statistics on logs conveniently. 5.6 Managing Log Data You can managing log data of the Nastar to understand the operation status of the Nastar. 5.7 Reference of the Log Management GUI This topic provides the reference information of the log management GUI.
Issue 03 (2010-06-30)
5-1
5 Log Management
5.1 Getting to Know Log Management

You can browse the details of operation logs or system logs to know the user operations or system status. 5.1.1 Log Management Function In log management, the system, security, and operation logs that are generated during Nastar running are recorded. You can query and logs to understand the Nastar running status, system security status, or specific user operation information. In addition, you can save results in a file or print results. 5.1.2 Log Types The Nastar has operation logs, system logs, security logs. The three types of logs record different log information.
5.1.1 Log Management Function

In log management, the system, security, and operation logs that are generated during Nastar running are recorded. You can query and logs to understand the Nastar running status, system security status, or specific user operation information. In addition, you can save results in a file or print results. Nastar log management includes the functions such as querying logs, managing log templates, saving logs, and printing logs.
5.1.2 Log Types

The Nastar has operation logs, system logs, security logs. The three types of logs record different log information.
Operation Logs
This topic describes the meaning, path, and parameters of operation logs. In operation logs, the maintenance personnel can view the user operation information that the Nastar records. In addition, by collecting statistics on operation logs, you can count the number of statistics items based on the statistics conditions.
Description
Operation logs record the information about the non-security operations that the user performs in the Nastar.
Path
Operation logs are stored in the database. You can query them through the client. The entry for querying operation logs through the client is Security > Log Management > Query Operation Logs. Operation logs can be dumped to a file from the database. The navigation path is Maintenance > Task Management. By default, the dump path of the operation logs is $Nastar/var/ThresholdExport/Log.
5 Log Management
After the operation logs are dumped, the Nastar generates the relative folder and log file.
l
Folder: The folder is named in the format YYMMDD in the dump path. "YYMMDD" indicates the date when the operation logs are dumped. Log file: The following two files are generated in the folder: YYMMDDHHMMSSoperation-log-dateThreshold_info.xml and YYMMDDHHMMSS-operation-logdateThreshold-Number.Filename extension. The file with the suffix _info.xml saves the configuration information of the dumped logs, and the file with the suffix Number.Filename extension saved the dumped logs.
NOTE
Operation logs can be dumped to a .csv or .xml file, and the file can be compressed to a .zip package.
Parameters
Parameter Name Parameter Meaning Operation Name Risk Level Name of an operation that a user performs on the Nastar. Levels of risks caused by the operations that are performed on the Nastar: Warning, Minor, and Warning. Nastar user. Type of an Nastar user. Time when an operation starts. It is accurate to second. Time when an operation ends. It is accurate to second.
Operation User User Type Start Time End Time
Operation Category Type of an Nastar operation. Operation Terminal IP address of the host where an operation is performed. Operation Object Operation Result Object that an operation is performed on. Result of an operation: succeeded, failed, partly succeeded, ongoing and canceled. Other useful information about an operation.
Details
System Logs
This topic describes the meaning, path, and parameters of system logs. In system logs, the maintenance personnel can view the system operation information that the Nastar records. In addition, you can collect statistics on system logs based on the log severity or source.
Issue 03 (2010-06-30)
5-3
5 Log Management
Description
System logs record the operations or tasks that the Nastar performs automatically, for example, scheduled tasks and system tasks.
Format
System logs are stored in the database. You can query them through the client. The entry for querying system logs through the client is Security > Log Management > Query System Logs. System logs can be dumped to a file from the database. The navigation path is Maintenance > Task Management. By default, the dump path of the system logs is $Nastar/var/ ThresholdExport/Log. After the system logs are dumped, the Nastar generates the relative folder and log file.
l
Folder: The folder is named in the format YYMMDD in the dump path. "YYMMDD" indicates the date when the system logs are dumped. Log file: The following two files are generated in the folder: YYMMDDHHMMSS-systemlog-dateThreshold_info.xml and YYMMDDHHMMSS-system-log-dateThresholdNumber.Filename extension. The file with the suffix _info.xml saves the configuration information of the dumped logs, and the file with the suffix -Number.Filename extension saved the dumped logs.
NOTE
System logs can be dumped to a .csv or .xml file, and the file can be compressed to a .zip package.
Parameters
Parameter Name Parameter Meaning Level Levels of risks caused by the operations performed on the Nastar: Warning, Minor, Risk. Module where the Nastar performs an operation. Time when an operation is performed. It is accurate to second.
Source Time
Basic Information Information about basic operations. Operation Result Details Result of an operation: succeeded, failed or unkonwn. Other useful information about an operation.
Security Logs
This topic describes the meaning, path, and parameters of security logs. In security logs, the maintenance personnel can view security information that the Nastar records. In addition, by collecting statistics on security logs, you can count the number of statistics items based on the statistics conditions.
5 Log Management
Description
Security logs record the security operations that the user performs in the Nastar, for example, login, logout, locking, and unlocking.
Path
Security logs are stored in the database. You can query them through the client. The entry for querying security logs through the client is Security > Log Management > Query Security Logs. Security logs can be dumped to a file from the database. The navigation path is Maintenance > Task Management. By default, the dump path of the security logs is $Nastar/var/ ThresholdExport/Log. After the security logs are dumped, the Nastar generates the relative folder and log file.
l
Folder: The folder is named in the format YYMMDD in the dump path. "YYMMDD" indicates the date when the security logs are dumped. Log file: The following two files are generated in the folder: YYMMDDHHMMSSsecurity-log-dateThreshold_info.xml and YYMMDDHHMMSS-security-logdateThreshold-Number.Filename extension. The file with the suffix _info.xml saves the configuration information of the dumped logs, and the file with the suffix Number.Filename extension saved the dumped logs.
NOTE
Security logs can be dumped to a .csv or .xml file, and the file can be compressed to a .zip package.
Parameters
Parameter Name Parameter Meaning Security Event Risk Level Event that is related toNastar security. Level of risks caused by the operations that are performed on the Nastar. There are three risk levels: Warning, Minor, and Warning. Nastar user. Type of anNastar user. Time when an operation is performed. It is accurate to second.
Operation User User Type Operation Time
Operation Terminal IP address of the host where an operation is performed. Operation Object Operation Result Details Object that an operation is performed on. Result of an operation: succeeded, failed or partly succeeded. Other useful information about an operation.
Issue 03 (2010-06-30)
5-5
5 Log Management
Parameter Name Parameter Meaning Event Type Type of an event.

NOTE Entry of this parameter: 1. Choose Security > Log Management > Security Log Statistics. 2. In the Statistic Filter dialog box, click the Statistical Items tab. 3. Select Event Type from the Statistic Item drop-down list.
5.2 Managing Operation Logs

You can query statistics on operation logs of the Nastar to understand the operation status of the Nastar. 5.2.1 Querying Operation Logs You can query operation logs to know the operation records of the Nastar. 5.2.2 Collecting Statistics on Operation Logs You can know the operation status by collecting statistics and analyzing operation logs. For example, you can know the period during which a maximum number of operations are performed, and the period during which operations are performed most frequently.
5.2.1 Querying Operation Logs

You can query operation logs to know the operation records of the Nastar.
Context
l
When you query operation logs by user name, only names of the users that have performed operations are displayed under Available Operation User in the Select Operation User dialog box. The statistics result is generated based on the existing data in the database. If the database is empty, there is no statistics result.
Procedure
Step 1 Choose Security > Log Management > Query Operation Logs from the main menu. Step 2 In the Filter window, set the filter conditions, and then click OK.
NOTE
You can also click Cancel, and then query logs in the Query Operation Logs window in the following ways:
l
Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to query logs. If no template exists in the Nastar, see 5.5 Setting Log Templates to create a template. Click Filter. Set the query conditions in the Filter, and the click OK to query logs.
Step 3 Right-click in the query window and perform the following operations:
5 Log Management
Operation Name Details
Operation Method Choose one log in the window, right-click and then choose Details, or double-click the alarm.
NOTE The Details dialog box displays the time, risk level, or results of the operation that generates the log.
Save All Records
1. Choose one log in the window, right-click and then choose Save All Records. 2. In the Save dialog box, select the path to save records, and then click Save.
NOTE The log records can only be exported as TXT, HTML, CSV, PDF or XLS files. The default file format is XLS file.
Save Selected Records
1. Choose one log in the window, right-click and then choose Save Selected Records. 2. In the Save dialog box, select the path to save records, and then click Save.
Save Appoint Records
1. Choose one log in the window, right-click and then choose Save Appoint Records. 2. In the Save Appoint Record dialog box, set the number of the row where the log exists, and then click OK.
NOTE In the Save Appoint Records dialog box, click on the right of File name. In the Save dialog box, select the path for saving the records. The log records can only be exported as TXT, HTML, CSV, PDF or XLS files. The default file format is XLS file.
Print All Records
1. Choose one log in the window, right-click and then choose Print All Records. 2. In the Print dialog box, set the print parameters, and then click Print.
Print Selected Records
1. Choose one log in the window, right-click and then choose Print Selected Records. 2. In the Print dialog box, set the print parameters, and then click Print.
Issue 03 (2010-06-30)
5-7
5 Log Management
Operation Name Print Appoint Records
Operation Method 1. Choose one log in the window, right-click and then choose Print Appoint Records. 2. In the Print Appoint Records dialog box, set the number of the row where the log exists, and then click OK. 3. In the Print dialog box, set the print parameters, and then click Print.
----End
5.2.2 Collecting Statistics on Operation Logs

You can know the operation status by collecting statistics and analyzing operation logs. For example, you can know the period during which a maximum number of operations are performed, and the period during which operations are performed most frequently.
Context
The statistics result is generated based on the existing data in the database. If the database is empty, there is no statistics result.
Procedure
Step 1 Choose Security > Log Management > Operation Log Statistics from the main menu. Step 2 In the Statistic Filter window, set statistical items and statistic condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Operation Log Statistics window in the following ways:
l
Click Template Statistic, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on operation logs. If no template exists in the Nastar, see 5.5 Setting Log Templates to create a template. Click Statistic Filter. Set Statistical Items and Filter Condition in the Statistic Filter window, and then click OK to collect statistics on operation logs.
----End
Result
In the Operation Log Statistics window, the statistical result is displayed. Perform the following operations as required:
l l
Click Print to print the statistical result. Click Save As to save the statistical result.
5.3 Managing System Logs

You can query statistics on system logs of the Nastar to understand the running status of the Nastar.
5 Log Management
5.3.1 Querying System Logs You can query system logs to know the important events that occur when the Nastar is running. 5.3.2 Collecting Statistics on System Logs You can know the system status by collecting statistics and analyzing the system log. For example, you can know the type of service that raises the most alarms.
5.3.1 Querying System Logs

You can query system logs to know the important events that occur when the Nastar is running.
Context
Procedure
Step 1 Choose Security > Log Management > Query System Logs from the main menu. Step 2 In the Filter window, set the filter conditions, and then click OK.
NOTE
You can also click Cancel, and then query logs in the Query System Logs window in the following ways:
l
Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to query logs. If no template exists in the Nastar, see 5.5 Setting Log Templates to create a template. Click Filter. Set the query conditions in the Filter window, and then click OK to query logs.
Step 3 Right-click in the query window and perform the following operations: Operation Name Details Operation Method Choose one log in the window, right-click and then choose Details, or double-click the alarm.
Save All Records
Issue 03 (2010-06-30)
5-9
5 Log Management
Operation Name Save Selected Records
Operation Method 1. Choose one log in the window, right-click and then choose Save Selected Records. 2. In the Save dialog box, select the path to save records, and then click Save.
Print All Records
Print Selected Records
1. Choose one log in the window, right-click and then choose Print Selected Records. 2. In the Print dialog box, set the print parameters, and then click Print.
Print Appoint Records
1. Choose one log in the window, right-click and then choose Print Appoint Records. 2. In the Print Appoint Records dialog box, set the number of the row where the log exists, and then click OK. 3. In the Print dialog box, set the print parameters, and then click Print.
----End
5.3.2 Collecting Statistics on System Logs

You can know the system status by collecting statistics and analyzing the system log. For example, you can know the type of service that raises the most alarms.
Context
5 Log Management
Procedure
Step 1 Choose Security > Log Management > System Log Statistics from the main menu. Step 2 In the Statistic Filter window, set statistical condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the System Log Statistics window in the following ways:
l
Click Template Statistic, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on system logs. If no template exists in the Nastar, see 5.5 Setting Log Templates to create a template. Click Statistic Filter. Set statistical condition in the Statistic Filter window, and then click OK to collect statistics on system logs.
----End
Result
In the System Log Statistics window, the statistical result is displayed. Perform the following operations as required.
l l
5.4 Managing Security Logs

You can query statistics on security logs of the Nastar to understand the security operation status of the Nastar. 5.4.1 Querying Security Logs You can query security logs to know the security operations of the Nastar. 5.4.2 Collecting Statistics on Security Logs You can know the security operations by collecting statistics and analyzing the security log. For example, you can know the period during which maximum number of security operations are performed, and the period during which operations are performed most frequently.
5.4.1 Querying Security Logs

You can query security logs to know the security operations of the Nastar.
Context
Procedure
Step 1 Choose Security > Log Management > Query Security Logs from the main menu. Step 2 In the Filter window, set the filter conditions, and then click OK.
5 Log Management
NOTE
You can also click Cancel, and then query logs in the Query Security Logs window in the following ways:
l
Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to query logs. If no template exists in the Nastar, see 5.5 Setting Log Templates to create a template. Click Filter. Set the query conditions in the Filter window, and the click OK to query logs.
Step 3 Right-click in the query window and perform the following operations: Operation Name Details Operation Method Choose one log in the window, right-click and then choose Details, or double-click the alarm.
Save All Records
Save Selected Records
1. Choose one log in the window, right-click and then choose Save Selected Records. 2. In the Save dialog box, select the path to save records, and then click Save.
Print All Records
5-12
Issue 03 (2010-06-30)
5 Log Management
Operation Name Print Selected Records
Operation Method 1. Choose one log in the window, right-click and then choose Print Selected Records. 2. In the Print dialog box, set the print parameters, and then click Print.
Print Appoint Records
1. Choose one log in the window, right-click and then choose Print Appoint Records. 2. In the Print Appoint Records dialog box, set the number of the row where the log exists, and then click OK. 3. In the Print dialog box, set the print parameters, and then click Print.
----End
5.4.2 Collecting Statistics on Security Logs

You can know the security operations by collecting statistics and analyzing the security log. For example, you can know the period during which maximum number of security operations are performed, and the period during which operations are performed most frequently.
Context
Procedure
Step 1 Choose Security > Log Management > Security Log Statistics from the main menu. Step 2 In the Statistic Filter window, set statistical items and filter condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Security Log Statistics window in the following ways:
l
Click Template Statistic, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on security logs. If no template exists in the Nastar, see 5.5 Setting Log Templates to create a template. Click Statistic Filter. Set Statistical Items and Filter Condition in the Statistic Filter window, and then click OK to collect statistics on security logs.
----End
Result
In the Security Log Statistics window, the statistical result is displayed. Perform the following operations as required.
l l
Issue 03 (2010-06-30)
5 Log Management
5.5 Setting Log Templates

You can save the specific query and statistics conditions in log templates. This helps you to query and collect statistics on logs conveniently.
Context
The operations on the log query template and log statistics template are similar.
Procedure
Step 1 Choose Security > Log Management from the main menu. Step 2 By using the displayed menus, you can choose Query Operation Logs, Query System Logs, Query Security Logs, Operation Log Statistics, System Log Statistics and Security Log Statistics. The following takes the operations of querying and collecting statistics templates on operation logs as examples. Task Create a template Operation 1. Choose Security > Log Management > Query Operation Logs. 2. In the Filter dialog box, click Cancel. For the operation of collecting statistics on logs, the Statistic Filter dialog box is displayed. Click Cancel. 3. In the Query Operation Logs window, click Template Filter and then choose New. For the operation of collecting statistics on logs, click Template Statistic in the window for collecting statistics on logs and then choose New. 4. In the Enter the Template Name dialog box, enter the template name, and then click OK. 5. In the filter dialog box, set the filtering conditions of template parameters, and then click OK.
5-14
Issue 03 (2010-06-30)
5 Log Management
Task Modify a template
Operation If there is already a log query template or a log statistics template in the Nastar, you can modify the template. Do as follows: 1. In the window for querying or collecting statistics on logs, click Template Filter. In the displayed menu list, choose Open. The Open dialog box is displayed. Select a template. 2. Modify different operations in the template.
l
Querying logs a. In the window for querying logs, click Filter. b. In the Filter dialog box, modify the querying conditions in the log template, and then click OK. c. In the window for querying logs, click Template Filter. In the displayed menu list, choose Save.
Collecting statistics a. In the window for collecting statistics on logs, click Statistic Filter. b. In the Statistic Filter dialog box, modify the statistics conditions in the log template, and then click OK. c. In the window for collecting statistics on logs, click Template Statistic. In the displayed menu list, choose Save.
Delete a template
If there is already a log query template or a log statistics template in the Nastar, you can delete the template. Do as follows: 1. Delete the operations in the template.
l l
In the window for querying logs, click Template Filter. In the window for collecting statistics on logs, click Template Statistic.
2. Click Delete. 3. In the displayed Delete dialog box, delete the specified template. 4. Click Delete. ----End
5.6 Managing Log Data

You can managing log data of the Nastar to understand the operation status of the Nastar. 5.6.1 Dumping Nastar Logs By setting Nastar log dump, you can periodically or instantly dump security logs, operation logs, and system logs of the Nastar. The dumped logs are saved in files and deleted from the database. This avoids database space insufficiency. 5.6.2 Setting Nastar Log Export
5 Log Management
By setting Nastar log export, you can periodically or instantly export security logs, operation logs, and export logs of the NMS. The export logs are saved in files. Thus, they cannot be deleted from the database.
5.6.1 Dumping Nastar Logs

By setting Nastar log dump, you can periodically or instantly dump security logs, operation logs, and system logs of the Nastar. The dumped logs are saved in files and deleted from the database. This avoids database space insufficiency.
Context
Each of the types NM Operation Log Dump, NM Security Log Dump and NM System Log Dump has a system task that is provided by the Nastar by default. You are not allowed to delete the system task, but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Type navigation tree, select the type of the logs to be dumped. Double-click the task in the right area.
NOTE
In the right area, right-click the log dump task and choose Run At Once. The log dump task is performed instantly.
Step 3 In the displayed Attribute dialog box, set the parameters on the Common Parameters and Extended Parameters tabs. For details, see 5.7.9 Parameters for Setting Log Dump and Export. Step 4 Click OK. ----End
5.6.2 Setting Nastar Log Export

By setting Nastar log export, you can periodically or instantly export security logs, operation logs, and export logs of the NMS. The export logs are saved in files. Thus, they cannot be deleted from the database.
Context
Each of the types NM Operation Log Export, NM Security Log Export and NM System Log Export has a system task that is provided by the Nastar by default. You are not allowed to delete the system task, but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
Step 1 Choose Maintenance > Task Management from the main menu. Step 2 In the Task Type navigation tree, select the type of the logs to be dumped. Double-click the task in the right area.

NOTE
5 Log Management
To perform the operations such as executing an export task instantly, suspending an task, and setting timing suspending and resuming, right-click the log export task in the right area and choose the corresponding menus.
Step 3 In the displayed Attribute dialog box, set the parameters on the Common Parameters and Extended Parameters tabs. For details, see 5.7.9 Parameters for Setting Log Dump and Export. Step 4 Click OK. ----End
5.7 Reference of the Log Management GUI

This topic provides the reference information of the log management GUI. 5.7.1 Security Log List Nastar security logs record security operations that the user performs on the Nastar. You can find out insecure operations performed on the Nastar by periodically browsing Nastar security logs. Browsing Nastar security logs also improves Nastar security. 5.7.2 Parameters for Querying Operation Logs This topic describes the parameters of the filtering conditions that are set for querying operation logs. When querying operation logs, you can refer to this topic to set the filtering conditions. 5.7.3 Parameters for Collecting Statistics on Operation Logs This topic describes the parameters of the filtering conditions that are set for collecting statistics on operation logs. When collecting statistics on operation logs, you can refer to this topic to set the filtering conditions. 5.7.4 Parameters for Querying System Logs This topic describes the parameters of the filtering conditions that are set for querying system logs. When querying system logs, you can refer to this topic to set the filtering conditions. 5.7.5 Parameters for Collecting Statistics on System Logs This topic describes the parameters of the filtering conditions that are set for collecting statistics on system logs. When setting the filtering conditions of system logs, you can refer to this topic. 5.7.6 Parameters for Querying Security Logs This topic describes the parameters of the filtering conditions that are set for querying security logs. When querying security logs, you can refer to this topic to set the filtering conditions. 5.7.7 Parameters for Collecting Statistics on Security Logs This topic describes the parameters of the filtering conditions that are set for collecting statistics on security logs. When collecting statistics on security logs, you can refer to this topic to set the filtering conditions. 5.7.8 Parameters for Querying Device Logs This topic describes the parameters of the filtering conditions that are set for browsing device logs. When browsing device logs, you can refer to this topic to set the filtering conditions. 5.7.9 Parameters for Setting Log Dump and Export This topic describes the parameters for setting log export and dump in the centralized task management. When you set log export and dump, you can refer to this topic to perform setting.
5 Log Management
5.7.1 Security Log List

Nastar security logs record security operations that the user performs on the Nastar. You can find out insecure operations performed on the Nastar by periodically browsing Nastar security logs. Browsing Nastar security logs also improves Nastar security.
Security log list

Security Event User Management Grant user access Reset Password User Group Management Grant usergroup access NE User Management Assign NE User Rights Force Users to Exit Risk Level Minor Minor Risk Minor Minor Minor Minor Risk Description To implement the function of managing users in the Nastar. To implement the function of assigning rights to users in the Nastar. To change the current password. The change takes effect at the next login. To implement the function of managing user groups in the Nastar. To implement the function of assigning rights to user groups in the Nastar. To implement the function of managing NE users in the Nastar. To implement the function of assigning rights to NE users in the Nastar. To force the user to log out of the Nastar if necessary to ensure network security.
CAUTION After forcible logout, the user needs to log in to the Nastar again.
Edit Security Policy Monitor Users
Risk Minor
To set the password policy and account policy. To monitor user sessions recorded by the Nastar. Viewing user operations helps the maintenance personnel to ensure that the Nastar runs normally. To unlock the locked user account. To implement the function of managing security rights by category in the Nastar. To change the NE user password. The change takes effect at the next login. To implement the function of managing device sets in the Nastar.
Unlock Users Security rights management Change NE User Password Device Set Management
Minor Minor Risk Minor
5-18
Issue 03 (2010-06-30)
5 Log Management
Security Event Operation Set Management Query Security Logs SecurityLog template setting
Risk Level Minor Minor Minor
Description To implement the function of managing operation sets in the Nastar. To query security logs. To customize the template for querying security logs. The maintenance personnel can use this template to conveniently query the same type of security logs. To implement the function of checking rights in the Nastar. To implement the function of checking combined rights in the Nastar. To query the static information about the Nastar. To log in to the Nastar server. To log out of the Nastar server. To view sessions of all online users of the Nastar. To view sessions of Nastar online users except administrators. To view the system mode in the Nastar. To view the session mode in the Nastar. To view the domain information in the Nastar. To view Nastar security objects such as users, user groups, and devices. To implement the function of querying NE users in the Nastar. To implement the function of inheriting rights by security object in the Nastar. To implement the function of querying domains by security object in the Nastar. To implement the function of querying compressed security objects in the Nastar. To implement the function of querying user groups in the Nastar.
Check access Check combined access Query static information Log in to the server Log out the server Get All Login Session Get user login sessions Get system mode Get session mode Get domain information Get security object Query NE user Get access by SO Query domain by SO Query compressed SO
Minor Minor Minor Minor Risk Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor
Get usergroup
Minor
Issue 03 (2010-06-30)
5-19
5 Log Management
Security Event Get usergroup information
Risk Level Minor
Description To implement the function of querying the information about user groups in the Nastar. To implement the function of querying all users in the Nastar. To inherit rights of the user group. In the Nastar, a user can inherit the rights of the user group that the user belongs to. To implement the function of querying all user information in the Nastar. To implement the function of querying all user group information in the Nastar. To implement the function of querying any users in the Nastar. To implement the function of querying all NE user information in the Nastar. To inherit rights of other users in the Nastar. To obtain a user name by ID in the Nastar. To obtain an ID by user name in the Nastar. To access the Nastar by using an external user account. To change a user password according to the network maintenance requirement. To revert a user password according to the network maintenance requirement. To unlock the locked terminal. To create NE users according to the network maintenance requirement and assign different permissions to the users for the purpose of convenient user management.
Get all users Get access by group
Minor Minor
Get account information Get all usergroup Get users Get NE user information Get access by user Get user name by id Get user id by name NB login Change password Revert password Unlock terminal Create NE user
Minor Minor Minor Minor Minor Minor Minor Minor Risk Risk Minor Minor
5-20
Issue 03 (2010-06-30)
5 Log Management
Security Event Delete NE user
Risk Level Risk
Description To delete unnecessary NE user accounts for the purpose of network security. Misoperations and damages may be caused when invalid users use the disclosed accounts to log in.
CAUTION After deleting a user account, you cannot use it to log in to an NE unless you have created the same user account again.
Modify user group description
Minor
To modify the user group description according to the network maintenance requirement. This helps the maintenance personnel to quickly understand the category that the user group belongs to. To modify the user group name according to the network maintenance requirement. After the modification, users with the same properties are merged into the modified user group. To create a user group. A user group includes users with similar properties. Creating a user group with custom permissions achieves the user management in a centralized manner. To delete unnecessary Nastar user groups to ensure security of the network and Nastar. To assign rights to users and user groups according to the network maintenance requirement. This facilitates network management. To revoke the rights granted to users and user groups according to the network maintenance requirement. This reduces network management rights. To implement the function of assigning rights to other users through rights paste in the Nastar. To implement the function of querying the right policy in the Nastar. To bind operation sets and device sets to a user. Unbind objects from a user.
Modify user group name
Minor
Create user group
Minor
Delete user group
Minor
Grant rights
Minor
Cancel rights
Minor
Paste rights
Minor
Query access policy Bind user Unbind user
Minor Minor Minor
Issue 03 (2010-06-30)
5-21
5 Log Management
Security Event Bind user group Unbind user group Create user
Risk Level Minor Minor Minor
Description To bind operation sets and device sets to a user group. Unbind objects from a user group. To create users according to the network maintenance requirement and assign different permissions to users for the purpose of convenient network management. To delete unnecessary user accounts for the purpose of network security. Misoperations and damages may be caused when invalid users use the disclosed accounts to log in.
CAUTION After deleting a user account, you cannot use it to log in to the Nastar except that you have created the same user account again.
Delete user
Risk
Modify user description Modify user login duration Modify account validity Modify user attribute Modify account LogOut Policy
Minor Minor Minor Minor Minor
To implement the function of modifying the user description in the Nastar. To implement the function of changing the user login time segment in the Nastar. To implement the function of modifying accounts in the Nastar. To implement the function of modifying user attributes in the Nastar. To implement the function of modifying the account logout policy (if a user does not perform operations in a long period, the user is logged out automatically) in the Nastar. To implement the function of changing the password expiry date in the Nastar. To allow the user to access the Nastar by using the specified IP addresses or IP address segments. To bind objects and operations to an NE user. To unbind objects and operations from an NE user.
Modify password expiry date Set user ACLs
Minor Minor
Bind NE user Unbind NE user
Minor Minor
5-22
Issue 03 (2010-06-30)
5 Log Management
Security Event Set security policies
Risk Level Minor
Description To set security policies according to the network maintenance requirement. This ensures that the Nastar runs securely and normally. To implement the function of querying child domains in the Nastar. To implement the function of changing an NE user password in the Nastar. To implement the function of changing the user password validity period in the Nastar. To implement the function of modifying user password status in the Nastar. To add IP addresses or IP address segments to the system ACL. Users are allowed to access the Nastar by using the specified IP addresses or IP address segments. To change IP addresses or IP address segments in the system ACL. Users are allowed to access the Nastar by using the specified IP addresses or IP address segments. To delete IP addresses or IP address segments from the system ACL. To plan and create a device set. After you assign the device set to a user or user group, the user or user group has the permissions to perform operations on the devices included in the device set. This helps assign and manage Nastar user permissions in a centralized manner. To modify a device set name according to the network maintenance requirement. Devices with the same properties are merged into the modified device set. To modified the device set description according to the network maintenance requirement. Devices with the same properties are merged into the modified device set.
Query child domain Change NE user password Change user password valid days Modify user password status Add system ACL
Minor Minor Minor
Minor Minor
Modify system ACL
Risk
Delete system ACL Create device set
Minor Minor
Modify device set name
Minor
Modify device set description
Minor
Issue 03 (2010-06-30)
5-23
5 Log Management
Security Event Add device set member
Risk Level Minor
Description To add devices to the specified device set according to the network maintenance requirement. To delete devices from the specified device set according to the network maintenance requirement. To delete unnecessary device sets in time. To bind a device set to another device set according to the network maintenance requirement. The user does not need to reconfigure properties for device sets with the same properties. To unbind a device set from another device set according to the network maintenance requirement. To create an operation set. After you assign the operation set to a user or user group, the user or user group has the permissions to perform the operations included in the operation set. This helps assign and manage Nastar user permissions in a centralized manner. To modified an operation set name according to the network maintenance requirement. Operations with the same properties are merged into the modified operation set. To modified the operation set description according to the network maintenance requirement. Operations with the same properties are merged into the modified operation set. To add operations to the specified operation set according to the network maintenance requirement. To delete operations from the specified operation set according to the network maintenance requirement. To delete unnecessary operation sets in time.
Delete device set member
Risk
Delete device set Bind device set to device set
Risk Minor
Unbind device set to device set Create operation set
Minor
Minor
Modify operation set name
Minor
Modify operation set description
Minor
Add operation set member
Minor
Delete operation set member
Risk
Delete operation set
Risk
5-24
Issue 03 (2010-06-30)
5 Log Management
Security Event Bind operation set to operation set
Risk Level Minor
Description To bind an operation set to another operation set according to the network maintenance requirement. The user does not need to reconfigure properties for operation sets with the same properties. To unbind an operation set from another operation set according to the network maintenance requirement. To assign a user group the permission to access subresources. To revoke the permission to access subresources from a user group. To assign a user the permission to access subresources. To revoke the permission to access subresources from a user. To implement the function of managing security users in the Nastar. To implement the function of managing security user groups in the Nastar. To implement the function of managing security device sets in the Nastar. To implement the function of managing security operation sets in the Nastar.
Unbind operation set to operation set Add subresource access to user group Delete subresource access from user group Add subresource access to user Delete subresource access from user Security User Management Security User Group Management Security Device Set Management Security Operation Set Management
Minor
Minor Minor Minor Minor Minor Minor Minor Minor
5.7.2 Parameters for Querying Operation Logs

This topic describes the parameters of the filtering conditions that are set for querying operation logs. When querying operation logs, you can refer to this topic to set the filtering conditions.
Filter condition
Name Operation User Description Description: To query data by user. Settings Setting method: Click . From the Select Operation User dialog box, select one or more items.
Issue 03 (2010-06-30)
5-25
5 Log Management
Name Operation Terminal
Description Description: To query by terminal.
Settings Setting method: Click . From the Operation Terminal dialog box, select one or more items. Setting method: From the Operation Result group box, select one or more items. Value:
l
Operation Result
Description: To query by operation result.
Succeeded means the operation is complete, and all the operation results are returned. Failed means the operation fails. Partly succeeded means the operation is complete, and some operation results are returned. Ongoing means the operation is being carried out, the result is not returned. Canceled means the operation is canceled.
Risk Level
Description: To query by risk level.
Setting method: From the Risk Level group box, select one or more items. Value: Warning, Minor and Risk
5-26
Issue 03 (2010-06-30)
5 Log Management
Name Time Range
Description Description: To query logs by time range. If the time range is not set, all logs generated at any time are queried. From means the start time, and To means the end time.
Settings Setting method: Select From and To checkbox on the left side, and then to enter the date and time directly in the text and set the time box, or click in the Date/Time Selection dialog box. Example: Example: Set the time range to "02/08/2009 00:00:00 02/09/2003 00:00:00".
NOTE To set the time format, choose File > Preferences from the main menu, expand Region Settings, and then choose the Time node. Set Time Format in the area on the right.
Detail Information Contains
Description: In the Query Operation Logs window, you can set whether to display the Details column of operation logs. In Detail Information Contains, enter the information to be displayed in the Details column. The Nastar filters operation logs based on the information provided in Detail Information Contains.
Setting method: Select the Detail Information Contains check box, and then enter the detailed information on the right of the text box.
Operation Name
Description: To query by operation.
Setting method: Click corresponding to Operation Name. From the Select Operation Name dialog box, select one or more items. Setting method: Click corresponding to Operation Object. From the Select Operation Object dialog box, select one or more items.
Operation Object
Description: To query by operation objects.
Issue 03 (2010-06-30)
5-27
5 Log Management
5.7.3 Parameters for Collecting Statistics on Operation Logs

This topic describes the parameters of the filtering conditions that are set for collecting statistics on operation logs. When collecting statistics on operation logs, you can refer to this topic to set the filtering conditions.
Statistical items
Name Statistic Row Description Description: Set the row heading of the statistical result table. Settings Setting method: Set one or two statistics items (You must select one statistics item at least and select two statistics items at most). The statistical results are sorted according to the statistical items. Setting method: Statistic item of Statistic column must be set. Value: The parameters include None, Operation User, User Type, Operation Name, Operation Category, Operation Terminal, Operation Result, and Operation Object. Value: -
Statistic Column
Description: Set the column heading of the statistical result table.
Statistic Item
Description: Set the row heading and column heading of the statistical result table.
Example
Description: Preview the style of the statistical result table.
Filter condition
Name Operation User Description Description: To collect statistics data by user. Settings Setting method: Click . From the Select Operation User dialog box, select one or more items. Setting method: Click . From the Select Operation Terminal dialog box, select one or more items.
Operation Terminal
Description: To collect statistics by terminal.
5-28
Issue 03 (2010-06-30)
5 Log Management
Name Operation Result
Description Description: To collect statistics by operation result.
Settings Setting method: From the Operation Result group box, select one or more items. Value:
l
Succeeded means the operation is complete, and all the operation results are returned. Failed means the operation is failed. Partly succeeded means the operation is complete, and some operation results are returned. Ongoing means the operation is being carried out, the result is not returned. Canceled means the operation is canceled.
Risk Level
Description: To collect statistics by operation level.
Setting method: From the Risk Level group box, select one or more items. Value: Warning, Minor and Risk
Time Range
Description: To collect statistics by time range. From means the start time, and To means the end time.
Setting method: Select From and To check boxes on the left side, and then enter the date and time directly in the text box, or click and set the time in the Date/Time Selection dialog box. Example: Example: Set the time range to "02/08/2009 00:00:00 02/09/2003 00:00:00".
Issue 03 (2010-06-30)
5-29
5 Log Management
Name Detail Information Contains
Description Description: In the Operation Log Statistics window, you can set whether to display the Details column of operation logs. In Detail Information Contains, enter the information to be displayed in the Details column. The Nastar filters operation logs based on the information provided in Detail Information Contains.
Settings Setting method: Select the Detail Information Contains check box, and then enter the detailed information on the right of the text box.
Operation Name
Description: To collect statistics by operation names.
Setting method: Click corresponding to Operation. From the Select Operation Name dialog box, select one or more items. Setting method: Click corresponding to Operation Object. From the Select Operation Object dialog box, select one or more items.
Operation Object
Description: To collect statistics by operation objects.
5.7.4 Parameters for Querying System Logs

This topic describes the parameters of the filtering conditions that are set for querying system logs. When querying system logs, you can refer to this topic to set the filtering conditions.
Filter condition
Name Source Description Description: To query logs by log source. Settings Setting method: Click . From the Source Select dialog box, select one or more items.
5-30
Issue 03 (2010-06-30)
5 Log Management
Name Level
Description Description: To query logs by log level.
Settings Setting method: From the Level group box, select one or more items. Value: Warning, Minor and Risk.
Time Range
Description: To query logs by time range. If the time range is not set, all logs generated at any time are queried. From means the start time, and To means the end time.
Setting method: Select From and To checkbox in the left side, and then enter the date and time directly in the text and set the time box, or click in the Date/Time Selection dialog box. Example: Example: Set the time range to "02/08/2009 00:00:00 02/09/2003 00:00:00".
Description: In the Query System Logs window, you can set whether to display the Details column of operation logs. In Detail Information Contains, enter the information to be displayed in the Details column. The Nastar filters operation logs based on the information provided in Detail Information Contains.
5.7.5 Parameters for Collecting Statistics on System Logs

This topic describes the parameters of the filtering conditions that are set for collecting statistics on system logs. When setting the filtering conditions of system logs, you can refer to this topic.
Issue 03 (2010-06-30)
5-31
5 Log Management
Statistical items
Name Statistic Row Description Description: Set the row heading of the statistical result table. Statistic Column Description: Set the column heading of the statistical result table. Statistic Item Description: Set the row heading and column heading of the statistical result table. Example Description: Preview the style of the statistical result table. Settings Setting method: The Statistic Item parameter under Statistic Row is mandatory. Setting method: The Statistic Item parameter under Statistic Column is mandatory. Value: The parameters include None, Level, and Source. Value: -
Filter condition
Name Source Description Description: To collect statistics logs by log source. Settings Setting method: Click . From the Select Source dialog box, select one or more items. Setting method: From the Level group box, select one or more items. Value: Warning, Minor and Risk.
Level
Description: To collect statistics by log level.
5-32
Issue 03 (2010-06-30)
5 Log Management
Name Time Range
Description Description: To collect statistics by time range. If the time range is not set, all logs generated at any time are queried. From means the start time, and To means the end time.
Settings Setting method: Select From and To checkbox in the left side, and then enter the date and time directly in the text and set the time box, or click in the Date/Time Selection dialog box. Example: Example: Set the time range to "02/08/2009 00:00:00 02/09/2003 00:00:00".
Description: In the System Log Statistics window, you can set whether to display the Details column of operation logs. In Detail Information Contains, enter the information to be displayed in the Details column. The Nastar filters operation logs based on the information provided in Detail Information Contains.
Setting method: Select the Detail Information Contains check box, and then enter the detailed information on the right of the check box.
5.7.6 Parameters for Querying Security Logs

This topic describes the parameters of the filtering conditions that are set for querying security logs. When querying security logs, you can refer to this topic to set the filtering conditions.
Filter condition
Name Operation User Description Description: To query data by user. Settings Setting method: Click . From the Select Operation User dialog box, select one or more items.
Issue 03 (2010-06-30)
5-33
5 Log Management
Name Operation Terminal
Description Description: To query by terminal.
Settings Setting method: Click . From the Select Operation Terminal dialog box, select one or more items. Setting method: From Result, select one or more items. Value:
l
Operation Result
Description: To query by operation result.
Succeeded means the operation is complete, and all the operation results are returned. Failed means the operation is failed. Partly succeeded means the operation is complete, and some operation results are returned.
Risk Level
Description: To query by risk levels.
Setting method: From the Risk Level group box, select one or more items. Value: Warning, Minor and Risk.
Time Range
Description: To query by time range. If the time range is not specified, all logs generated at any time are queried. From means the start time, and To means the end time.
Setting method: Select From and To checkbox in the left side, and then enter the date and time directly in the text and set the time box, or click in the Date/Time Selection dialog box. Example: Example: Set the time range to "02/08/2009 00:00:00 02/09/2003 00:00:00".
5-34
Issue 03 (2010-06-30)
5 Log Management
Name Detail Information Contains
Description Description: In the Query Security Logs window, you can set whether to display the Details column of operation logs. In Detail Information Contains, enter the information to be displayed in the Details column. The Nastar filters operation logs based on the information provided in Detail Information Contains.
Settings Setting method: Select the Detail Information Contains check box, and then enter the fields to be contained in Details on the right of the check box.
Security Event
Description: To query by security events.
Setting method: Click corresponding to Security Event. From the Select Security Event dialog box, select one or more items. Setting method: Click corresponding to Operation Object. From the Select Operation Object dialog box, select one or more items.
Operation Object
Description: To query by operation objects.
5.7.7 Parameters for Collecting Statistics on Security Logs

This topic describes the parameters of the filtering conditions that are set for collecting statistics on security logs. When collecting statistics on security logs, you can refer to this topic to set the filtering conditions.
Statistical items
Name Statistic Row Description Description: Set the row heading of the statistical result table. Settings Setting method: Set one statistics item at least and select two statistics items at most. The statistical results are sorted according to the statistical items.
Issue 03 (2010-06-30)
5-35
5 Log Management
Name Statistic Column
Description Description: Set the column heading of the statistical result table.
Settings Setting method: The Statistic Item parameter under Statistic Column is mandatory. Value: The parameters include None, Operation User, User Type, Security Event, Event Type, Operation Terminal, Operation Result, Operation Object, and Risk Level. Value: -
Statistic Item
Description: Set the row heading and column heading of the statistical result table.
Example
Description: Preview the style of the statistical result table.
Filter condition
Name Operation User Description Description: To collect statistics data by user. Settings Setting method: Click . From the Select Operation User dialog box, select one or more items. Setting method: Click . From the Select Operation Terminal dialog box, select one or more items. Setting method: From Result, select one or more items. Value:
l
Operation Terminal
Description: To collect statistics by terminals.
Operation Result
Description: To collect statistics by operation result.
Succeeded means the operation is complete, and all the operation results are returned. Failed means the operation is failed. Partly succeeded means the operation is complete, and some operation results are returned.
5-36
Issue 03 (2010-06-30)
5 Log Management
Name Risk Level
Description Description: To collect statistics by risk levels.
Settings Setting method: From the Risk Level group box, select one or more items. Setting method: Select From and To checkbox in the left side, and then enter the date and time directly in the text and set the time box, or click in the Date/Time Selection dialog box. Example: Example: Set the time range to "02/08/2009 00:00:00 02/09/2003 00:00:00".
Time Range
Description: To collect statistics by time range. If the time range is not specified, all logs generated at any time are queried. From means the start time, and To means the end time.
Description: In the Security Log Statistics window, you can set whether to display the Details column of operation logs. In Detail Information Contains, enter the information to be displayed in the Details column. The Nastar filters operation logs based on the information provided in Detail Information Contains.
Security Event
Description: To collect statistics by security events.
Setting method: Click corresponding to Security Event. From the Select Security Event dialog box, select one or more items. Setting method: Click corresponding to Operation Object. From the Select Operation Object dialog box, select one or more items.
Operation Object
Description: To collect statistics by operation objects.
Issue 03 (2010-06-30)
5-37
5 Log Management
5.7.8 Parameters for Querying Device Logs

This topic describes the parameters of the filtering conditions that are set for browsing device logs. When browsing device logs, you can refer to this topic to set the filtering conditions.
Parameters
Parameter Device Name Description Description: Name of the managed device. User Name Description: User name of the device managed by the NMS. Access Method Description: Mode for the user to access the device. Result Description: Result of the user operation on the device. Range Description: Time range when the user operates the device. User Command Description: Command of the user operation on the device. Settings Value: Value range: All or a specific device name. Value: Value range: All or a specific user name. Value: Value range: Modem, NMS, Proxy, Serial, Telnet, WWW, or All. Value: Value range: All, Failed, Succeeded, Unknown, or -. Value: Value range: The four combinations of Start Time|The First Record and End Time|The Last Record. Setting method: If you select Wildcard, you can perform a fuzzy search on the user commands.
5.7.9 Parameters for Setting Log Dump and Export

This topic describes the parameters for setting log export and dump in the centralized task management. When you set log export and dump, you can refer to this topic to perform setting.
Parameters
Parameter Commo n Base Info Description Description: You can change the task name and start time. Setting Value: -
5-38
Issue 03 (2010-06-30)
5 Log Management
Parameter Paramet ers Period Info
Description Description: This parameter indicates the task execution period and the number of task execution times. You cannot change the number of times for executing NMS log dump and export. In addition, you cannot change the period for executing NMS log dump. Description: You can compress export files to a .zip file. After compression, the source files are deleted. Description: This parameters indicates the format of the dump or export files of logs.
NOTE
l For log dump, this parameter is File Type. l For log export, this parameter is Export File
Setting Value: -
Extende d Paramet ers
Compres s After Export File File Type/ Export File Type
Value: -
Value: Values: CSV or XML.
Type.
File Save Path
Description: This parameter indicates the path for saving log dump and export files. You cannot change the path. Description: This parameter is available for dump tasks and unavailable for export tasks. When a dump task is executed, the logs older than this period are dumped.
Value: -
Days Holded in Database
Value: Value range: 1-90.
Issue 03 (2010-06-30)
5-39
5 Log Management
Parameter Export File Manage ment
Description Description:
l
Setting Value: -
Only holded XX Day(s): In the dump or export directory, the log files older than this period are deleted. Only holded XX File(s): In the dump or export directory, if the number of log files exceeds the value of this parameter, the Nastar deletes the oldest dump or export files until the number of log files in this directory becomes less than the value of this parameter. Only holded XX M of file: In the dump or export directory, if the total size of log files exceeds the value of this parameter, the Nastar deletes the oldest dump or export files until the total size of log files in this directory becomes less than the value of this parameter.
5-40
Issue 03 (2010-06-30)
6 GIS Management
6
About This Chapter
GIS Management
The Nastar can geographically display the performance analysis results through either the Geographic Information System (GIS) window or Google Earth. You can view the Nastar analysis result directly on the map, thus facilitating the service analysis. 6.1 Viewing Analysis Results by Using the Google Earth This section describes how to view analysis results by using the Google Earth. The Nastar can quickly display BTS and performance analysis results (for example, neighboring cell analysis result and VIP analysis result) on the Google Earth. The three-dimensional map enables you to easily view the network performance analysis results and reduces the workload of field survey. 6.2 Viewing Analysis Results Through the GIS Window This section describes how to view the analysis results through the GIS window. The Nastar can quickly display BTS and performance analysis results (for example, neighboring cell analysis result and VIP analysis result) in the GIS window. 6.3 Managing the GIS Window You can import the map files in .wor or .tab format and view the site information in the GIS window by using the engineering parameters. In addition, you can perform the following operations in the GIS window through the GIS toolbar, such as move/center/zoom in on/zoom out on a map and measure the distance between two points on the map.
Issue 03 (2010-06-30)
6-1
6 GIS Management
6.1 Viewing Analysis Results by Using the Google Earth

This section describes how to view analysis results by using the Google Earth. The Nastar can quickly display BTS and performance analysis results (for example, neighboring cell analysis result and VIP analysis result) on the Google Earth. The three-dimensional map enables you to easily view the network performance analysis results and reduces the workload of field survey.
Prerequisite
l l
You have logged in to the Nastar client. The PC is connected to the Internet.
Context
The principles for displaying the Nastar data on the Google Earth are as follows:
l
After the engineering parameters are read, the geographic data is displayed on the scale of 2,600 meters at heights and with the last cell in the engineering parameter list being in the center by default. The blue dot represents a site, the fan-shaped area whose border is in orange represents a GSM cell, and the fan-shaped area whose border is in red represents a UMTS cell. The Nastar data can be displayed on the Google Earth synchronously. The geographic data is displayed on the scale of 2,600 meters at heights with the selected cell being in the center. During the neighboring cell analysis, the fan-shaped area in blue represents the current test cell, and the fan-shaped area in other colors represents the neighboring cells. The colors are consistent with those of legends displayed in the neighboring cell analysis result. During the VIP analysis, the fan-shaped area in blue represents the VIP active cells.
NOTE
The description of operations related to the Google Earth is not provided in this document.
Procedure
Step 1 Choose Function List > System Function > Satellite View from the navigation tree in the Analysis Task Management window. The EarthViewWindow window is displayed. The system loads the Google Earth components through the Internet. After the loading is complete, the system automatically reads the engineering parameters in the Nastar system and displays the engineering parameters as labels on the Google Earth.
6-2
Issue 03 (2010-06-30)
6 GIS Management
If ... The EarthViewWindow window displays the home page of the Google Earth
Then ... It indicates that the system fails to automatically read the Nastar engineering parameters. This problem may be caused by the low speed of loading the Google Earth components. In this case, you need to choose Function List > System Function > Satellite View again.
The EarthViewWindow window displays sites It indicates that the system succeeds in automatically reading the Nastar and cells, and the specified area is located. engineering parameters. Step 2 Enable the Google Earth to display the Nastar data synchronously. After you click a cell in the engineering parameter list, neighboring cell analysis result, or VIP analysis result, the Google Earth regards the selected cell as a center, and then displays the geographic data on the scale of 2,600 meters at heights. Step 3 View the cell information. After you click a cell, the Google Earth displays the engineering parameter information about the cell in a message box. For detailed engineering parameters, see 2.15.10 Parameters for Importing and Exporting Engineering Parameters. You can click the cell again to cancel the display of the message box. ----End
6.2 Viewing Analysis Results Through the GIS Window

This section describes how to view the analysis results through the GIS window. The Nastar can quickly display BTS and performance analysis results (for example, neighboring cell analysis result and VIP analysis result) in the GIS window.
Prerequisite
l l
You have logged in to the Nastar client. You are authorized to use the GIS.
Context
The principles for displaying the Nastar data in the GIS window are as follows:
l
The blue dot represents a site, the fan-shaped area whose border is in orange represents a GSM cell, and the fan-shaped area whose border is in red represents a UMTS cell. The Nastar data can be displayed in the GIS window synchronously. The geographic data is displayed with the selected cell being in the center.
Issue 03 (2010-06-30)
6-3
6 GIS Management
l
During the neighboring cell analysis, the fan-shaped area in blue represents the current test cell, and the fan-shaped area in other colors represents the neighboring cells. The colors are consistent with those of legends displayed in the neighboring cell analysis result. During the VIP analysis, the fan-shaped area blinking in red and blue in circulated manner represents the VIP active cells.
Procedure
Step 1 Click the GIS tab in the lower left corner of the Nastar client to open the GIS window. Step 2 Load the engineering parameters. For details, see 6.3.2 Loading Site Information. For details about the operations of the GIS window, see 6.3 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, neighboring cell analysis result, or VIP analysis result, the GIS window regards the selected cell as a center to display the geographic data. Step 4 View the cell information. to select a cell. Then, the engineering parameters of the cell are displayed in the Click Parameters area in the right pane of the GIS window. For detailed engineering parameters, see 2.15.10 Parameters for Importing and Exporting Engineering Parameters. ----End
6.3 Managing the GIS Window

You can import the map files in .wor or .tab format and view the site information in the GIS window by using the engineering parameters. In addition, you can perform the following operations in the GIS window through the GIS toolbar, such as move/center/zoom in on/zoom out on a map and measure the distance between two points on the map.
Context
NOTE
The GIS window is displayed in the lower left corner of the Nastar client. You can click the GIS tab to open the GIS window.
6.3.1 Importing a Map This section describes how to import a map. You can import the map files in .wor or .tab format to simulate the geographic environment, thus facilitating the analysis and location of network problems. 6.3.2 Loading Site Information This section describes how to load the site information. You can load the engineering parameters to the GIS so that the site information of the network can be displayed in the GIS window. 6.3.3 Filtering Cells This section describes how to filter cells. You can filter cells based on the network system, specified engineering parameters, and specified areas to optimize only the specified cells. The filtered cells are geographically displayed in highlighted colors to be differentiated from other cells. In addition, the filtered cells can be saved as a cell group.
6 GIS Management
6.3.4 Moving/Zooming In On/Zooming Out On/Refreshing/Fully Displaying a Map This section describes how to adjust a map. You can zoom in or zoom out on a map to change the map size, move a map, and display all the objects in the map window. In addition, you can restore the map window to the default status through the refreshing function. 6.3.5 Measuring Distance on the Map This section describes how to measure distance on the map. You can measure distance between two points on the map by using the distance measurement tool. 6.3.6 Saving the Map Display Effect This section describes how to save the map display effect. You can export the display effect of overlapped layers in the map window as images in .bmp, .png, .gif, or .jpg format.
6.3.1 Importing a Map

This section describes how to import a map. You can import the map files in .wor or .tab format to simulate the geographic environment, thus facilitating the analysis and location of network problems.
Prerequisite
l l
You have logged in to the Nastar client. You are authorized to use the GIS.
Context
The Nastar provides two modes for importing map files:
l l
Mode 1: Importing a map file for the first time Mode 2: Loading a map file again (the map file was imported last time)
When you import a map file by using mode 1, the importing speed is slow. Therefore, if you have already imported a map file, you are advised to use mode 2 to speed up the importing process.
CAUTION
When you perform operations in the GIS window, you are advised not to import or load map files repeatedly. This is to prevent any unknown impact.
Procedure
Step 1 Select a mode to import map files depending on the actual situation. If You Want to ... Then ...
Import a map file for the first time For details, see Step 2 to Step 4. Load a map file again Click on the toolbar to load the map file that was imported last time.
Issue 03 (2010-06-30)
6-5
6 GIS Management
Step 2 Click
on the toolbar. The Choose... dialog box is displayed.
Step 3 Select a map file in .wor or .tab format. Step 4 Click Open. The system starts importing the map file. It takes some time to import a map file for the first time. Please wait. ----End
6.3.2 Loading Site Information

This section describes how to load the site information. You can load the engineering parameters to the GIS so that the site information of the network can be displayed in the GIS window.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to use the GIS. The required engineering parameters are imported to the Nastar. For example, when you need to load the site information of the GSM network, you must have imported the engineering parameters of the GSM network.
Procedure
Step 1 Select the mode for loading the site information depending on the actual situation. If You Want To ... Then ...
Load the site information for the first time For details, see Step 2 to Step 5. or load the site information again If you load the site information again, the existing site information will be deleted. Use the site information that is imported last time By default, the system automatically loads the site information that is imported last time. You need not load the site information again.
Step 2 Click
on the toolbar. The Choose sites dialog box is displayed.
Step 3 Choose the network system from the drop-down list box. Step 4 Select the site whose information needs to be loaded from the group box at the bottom. Step 5 Click OK. After the site information is loaded, an icon is displayed in the GIS window. ----End
Postrequisite
You can select or clear the check box before the Site layers navigation tree in the left pane of the GIS window to display or hide the site icon.
6 GIS Management
6.3.3 Filtering Cells

This section describes how to filter cells. You can filter cells based on the network system, specified engineering parameters, and specified areas to optimize only the specified cells. The filtered cells are geographically displayed in highlighted colors to be differentiated from other cells. In addition, the filtered cells can be saved as a cell group.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to use the GIS. The engineering parameters are imported to the Nastar.
Context
The Nastar supports the filtering by using the following engineering parameter fields: BTS ID, BTS name, cell ID, and cell name.
Procedure
Step 1 Draw polygons to define the areas to be filtered. 1. 2. Click on the toolbar.
Click the GIS work platform to add points to the polygon one by one.
CAUTION
The lines of a polygon must not intersect. Otherwise, certain selected areas may be missed out. If only one point of a line in the polygon is determined, the line is displayed as a broken blue line. It indicates that you are drawing this line. If two points of a line in the polygon are determined, the line is displayed as a solid blue line. It indicates that you have finished drawing this line. 3. 4. 5. After the last point is added, right-click the work platform to exit the drawing of polygon. Then, open the Input dialog box. Set the name of the polygon. Click OK to complete the drawing of polygon. The polygon and the polygon name are displayed on the GIS window. Step 2 Set filtering conditions to filter the cells in the specified area, with the specified network system and engineering parameter field. 1. 2. 3. 4.
Issue 03 (2010-06-30)
Click
on the toolbar. The Search dialog box is displayed.
Select the area to be filtered in Region. Select the network system in Network Technology. Set the fields of engineering parameters in the lower left corner of the dialog box.
6 GIS Management
Currently, the Nastar supports the filtering through the following engineering parameter fields: BTS ID, BTS name, cell ID, and cell name. You can filter cells either through a certain field or two fields. The relation between the two fields can be set to And or Or. Step 3 Click Search. The system starts to filter cells. The filtering results are displayed in the Search Result area. Step 4 Select or clear the check box in the Search Result area to determine whether to filter cells again. Step 5 Geographically display the filtered cells. Click Geographic(D). The cells selected in the Search Result area are highlighted in the GIS window. Step 6 Save the filtered cells as an NE group. 1. 2. 3. Click Save As a NE Group(S) to open the Save as an NE group dialog box. Set NE Group Name and add the remarks. Click OK. The cells selected in the Search Result area are saved as an NE group. You can view the information about the NE group through the NE group management function.
----End
6.3.4 Moving/Zooming In On/Zooming Out On/Refreshing/Fully Displaying a Map

This section describes how to adjust a map. You can zoom in or zoom out on a map to change the map size, move a map, and display all the objects in the map window. In addition, you can restore the map window to the default status through the refreshing function.
Prerequisite
Importing a map has been performed.
Procedure
l Zoom in and zoom out on the map. The Nastar enables you to zoom in and zoom out on the map by changing the position of the mouse pointer. 1. Click the corresponding icon on the tool bar to zoom in or zoom out on the map.

Click Click
TIP
, and then click the map, the map is zoom in. , and then click the map, the map is zoom out.
2.
Click the map.

You can scroll the mouse wheel forward or backward to zoom in or zoom out on the map.
Move the map. When you move a map, the size of the map does not change. 1. Click on the toolbar.
6-8
6 GIS Management
2. l
Move the mouse pointer on the map and drag the map to the required direction.
View the panoramic scene of a map. After you click , the system displays all the objects in the map window.
Refresh a map. After you click , the colors and connection lines of the site icons and sector icons that are highlighted because of the service geographical application are cleared.
----End
6.3.5 Measuring Distance on the Map

This section describes how to measure distance on the map. You can measure distance between two points on the map by using the distance measurement tool.
Prerequisite
Importing a map has been performed.
Procedure
Step 1 Click on the toolbar.
Step 2 Click a point on the map and use it as the starting point for measuring the distance. Then, the starting point is fixed. Press and hold the left mouse button, and then move the mouse. When the mouse pointer moves away from the starting point, the system displays a solid black connection line between the starting point and the mouse pointer. In the status bar in the right pane of the window, the distance between two points is displayed in the Distance(km) area in real time. Step 3 Double-click or right-click the map to complete the distance measurement. ----End
6.3.6 Saving the Map Display Effect

This section describes how to save the map display effect. You can export the display effect of overlapped layers in the map window as images in .bmp, .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
7 OSS Management
7
About This Chapter
OSS Management
This section describes the OSS management. The OSS management enables you to create objects to be managed, modify objects, and delete objects. The centralized task management subsystem updates the object data at the preset time according to the object changes in the navigation tree on the interface of OSS NE management. 7.1 Basic Knowledge of OSS Management This section describes the basic knowledge about the OSS management functions. You should grasp the basic knowledge before you perform management operations, which facilitates the management over network objects. 7.2 Creating an OSS This section describes how to create an OSS. Creating an OSS is actually to define a physical FTP server. The Nastar collects the required data from the OSS (FTP server) to the Nastar server. 7.3 Viewing the Attributes of an OSS This section describes how to view the attributes of an existing OSS of OSS management. 7.4 Modifying the Attributes of an OSS This section describes how to modify the attributes of an existing OSS of OSS management according to the new requirement. 7.5 Reference for the OSS Management GUI This section describes the parameters about the interface of OSS management and the parameters for setting the object attributes of OSS management. You can refer to the description when performing the relevant operations on the interface.
Issue 03 (2010-06-30)
7-1
7 OSS Management
7.1 Basic Knowledge of OSS Management

This section describes the basic knowledge about the OSS management functions. You should grasp the basic knowledge before you perform management operations, which facilitates the management over network objects. In the OSS management, objects present the physical or logical entities on the network. A physical or logical entity, namely, an object, can be an OSS or an NE.
l
OSS Operation Support System. It defines the interface protocol principle in the Nastar. The Nastar collects the required data from a specified FTP server according to the OSS attributes and saves the data as files in a specified path in the Nastar.
NE NEs are used to identify network devices, such as switches and routers. NEs can be classified into actual NEs and virtual NEs. Actual NEs are actual telecommunications devices of Huawei on the network. Virtual NEs are the NEs that do not actually exist or are telecommunications devices of other vendors on the network.
The OSS management subsystem provides the basic functions for managing objects. The centralized task management subsystem adds the objects to the GUI through the OSS management subsystem. The OSS management of the Nastar provides the following functions: creating an OSS, viewing and modifying the attributes of OSSs, and deleting the OSSs.
7.2 Creating an OSS

This section describes how to create an OSS. Creating an OSS is actually to define a physical FTP server. The Nastar collects the required data from the OSS (FTP server) to the Nastar server.
Prerequisite
You have logged in to the Nastar client.
Procedure
Step 1 Choose Maintenance > OSS Management. The OSS Management window is displayed. Step 2 Click New OSS. Step 3 Set the attribute parameters of the OSS.
CAUTION
The values of OSS Data Interface Type, OSS User Name, OSS Password, and OSS Server Port must be correct. Otherwise, the end-to-end task and data collection may fail.
7-2
Issue 03 (2010-06-30)
7 OSS Management
Step 4 Set the information about the FTP server.
CAUTION
The values of FTP Server IP, FTP Server Port, FTP User Name, FTP password, FTP Transfer Mode, and Protocol must be correct. Otherwise, the data collection may fail. Step 5 Click OK. Step 6 Optional: If you set OSS data interface type to the M2000 V200R008 or a later version, and the M2000 adopts the SLS system, perform the following steps to set slave servers: When the M2000 V200R008 or a later version adopts the SLS system, the data required by the system is distributed on different servers because of the huge network. During the creation of an OSS, you must create a master server before setting the slave servers. 1. 2. 3. 4. In the navigation tree in the left pane, select the created OSS (master server), and then click Slave Server. The Slave Server is displayed. Click Add. The Slave server information dialog box is displayed. After setting the information about the slave server, click OK. Repeat Step 6.1 through Step 6.3 to set the information about all the slave servers. Click Close.
----End
Postrequisite
l
Set the NEs managed by the OSS. 1. 2. In the navigation tree in the left pane of the OSS Management window, select an OSS, and then click NE Manager. The NE Selector dialog box is displayed. Set the NEs that are managed by the selected OSS. The left pane lists the NEs to be selected for the management of the OSS. The right pane lists the NEs that are selected for the management of the OSS.
In the left pane, you can double-click an NE to add it to the right pane. You can click pane. You can click You can click pane. You can click to move one or more NEs from the left pane to the right
to move all the NEs from the left pane to the right pane. to move one or more NEs from the right pane to the left
to move all the NEs from the right pane to the left pane.
Issue 03 (2010-06-30)
7-3
7 OSS Management
CAUTION
If an NE is not added to the right pane, the data of this NE cannot be collected to the Nastar server. 3. 4. Click OK. Set the SAU information. Only when the NE version is the BSC6000 V900R008C12SP21, the BSC6000 V900R008C12SP23, the BSC6000 V900R008C12SP25, the BSC6810 V200R010C01B061, or the BSC6810 V200R010C01SPC090, you must set the SAU information. The other versions do not need to set the information. In the navigation tree in the left pane of the OSS Management window, select an NE, and then click Modify. Set the SAU information in the SAU information area.
l
Delete an existing OSS. 1. In the navigation tree in the left pane of the OSS Management window, select an OSS to be deleted, and then click Delete. If the selected OSS contains subobjects, the system prompts you to delete all the subobjects before deleting this OSS. 2. In the displayed dialog box, click OK.
7.3 Viewing the Attributes of an OSS

This section describes how to view the attributes of an existing OSS of OSS management.
Prerequisite
l l
You have logged in to the Nastar client. Certain OSSs are created.
Procedure
Step 1 Choose Maintenance > OSS Management. The OSS Management window is displayed. Step 2 Select an OSS from the navigation tree in the left pane. Then, you can view the attributes of the OSS in the right pane. ----End
7.4 Modifying the Attributes of an OSS

This section describes how to modify the attributes of an existing OSS of OSS management according to the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. Certain OSSs are created.
7-4
7 OSS Management
Procedure
Step 1 Choose Maintenance > OSS Management. The OSS Management window is displayed. Step 2 Select an OSS whose attributes are to be modified from the navigation tree in the left pane, and then click Edit. Step 3 Modify the relevant attributes. Step 4 Click OK. ----End
7.5 Reference for the OSS Management GUI

This section describes the parameters about the interface of OSS management and the parameters for setting the object attributes of OSS management. You can refer to the description when performing the relevant operations on the interface. 7.5.1 Interface Description: OSS Management This section describes the interface of OSS management. Before perform the relevant operations, you need to familiarize yourself with the functions of each area on the interface. 7.5.2 Parameters for Setting the Object Attributes of OSS Management This section describes the parameters for creating or modifying the objects of OSS management. You can refer to the description when creating or modifying the objects of OSS management.
7.5.1 Interface Description: OSS Management

This section describes the interface of OSS management. Before perform the relevant operations, you need to familiarize yourself with the functions of each area on the interface. Figure 7-1 shows the interface of OSS management. Table 7-1 describes the items in Figure 7-1.
Issue 03 (2010-06-30)
7-5
7 OSS Management
Figure 7-1 Interface of OSS management
Table 7-1 Interface description: OSS management No. (1) (2) Name Navigation tree Toolbar Description Indicates that the objects in the navigation tree are sorted by OSS. Provides the buttons for creating and deleting OSSs, setting slave servers, managing NEs, modifying the attributes of the created OSSs, and so on. Displays the details of the OSS that you select in the navigation tree. Displays the details of the FTP server corresponding to the OSS that you select in the navigation tree.
(3) (4)
Area of OSS attributes Area of FTP server information
7-6
Issue 03 (2010-06-30)
7 OSS Management
7.5.2 Parameters for Setting the Object Attributes of OSS Management

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

Parameter OSS Name Description Indicates the name of an OSS to be created or modified. Value range:
l l
A maximum of 60 characters The following characters are not allowed: ~ ! @ # $ % ^ & * + =<>? Unique and cannot be null Case sensitive
l l
OSS Data Interface Type
Indicates the type of the interface between the EMS and the Nastar. Value range: M2000V2R6, M2000V2R8, M2000V2R9, M2000V2R10, OMC920V400R001 and OMC920V400R005 When the Nastar collects data from the OSS, this interface defines the relevant principles such as the path of the configuration data files and performance data files in the OSS and the naming rules of the files. Thus, the Nastar can collect the required files from the path specified by the OSS and saves the files in the specified path on the Nastar client.
NOTE When creating an OSS, you need to set the value of OSS Data Interface Type according to the data collection principles supported by the OSS. The OSSs of different version may support the same data collection principles.
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.
Description
It is the description of an OSS. Value range:

l l
A maximum of 128 characters The following characters are not allowed: ~ ! @ # $ % ^ & * + =<>? Case sensitive
Issue 03 (2010-06-30)
7-7
7 OSS Management
Parameters Related to the FTP Server

Parameter FTP Server IP Description Indicates the IP address of the FTP server where the file to be collected is located. This parameter cannot be null. FTP Server Port Indicates the port number of the FTP server where the file to be collected is located. This parameter can be set to any integer from 1 to 65535. The default value is 21. This parameter cannot be null. FTP User Name Indicates the user name used to log in to the FTP server. Value range:
l l
This parameter cannot be null. FTP Password Indicates the password used to log in to the FTP server. This parameter cannot be null. FTP Transfer Mode Protocol Indicates the transfer mode set for the FTP server. The parameter value can be Passive Mode or Active Mode.
l
SFTP: Indicates the encrypted FTP transfer, which requires the support from the FTP server. FTP: Indicates the non-encrypted FTP transfer, which is a general FTP mode.
Parameters Related to the SAU

Parameter SAU Infromation-IP Address SAU Infromation-Port Description Indicates the IP address of the SAU. This parameter cannot be null. Indicates the port number of the SAU for communicating with the M2000 server. This parameter can be set to any integer from 1024 to 99999. The default value is 50505. This parameter cannot be null.
7-8
Issue 03 (2010-06-30)
7 OSS Management
Parameter SAU Infromation-FTP Server Port
Description Indicates the port number of the FTP server where the file to be collected is located. This parameter can be set to any integer from 1 to 65535. The default value is 21. This parameter cannot be null.
SAU Infromation-FTP User Name
Indicates the user name used to log in to the FTP server. Value range:
l l
This parameter cannot be null. SAU Infromation-FTP Password Indicates the password used to log in to the FTP server. This parameter cannot be null.
Parameter Related to the slave server Attributes

Parameter FTP server IP Description Indicates the IP address of the slave server in the M2000 SLS system. The value of this parameter cannot be null. FTP server port Indicates the FTP service port. Value range: an integer from 0 to 65535. The default value is 21. If the parameter value is null, the system uses 0 as the port number. FTP user Indicates the valid user name of the FTP service in the M2000 SLS system. Value range:
l l
FTP password
Indicates the password of the FTP service in the M2000 SLS system.
Issue 03 (2010-06-30)
7-9
8 GSM Centralized Task Management
GSM Centralized Task Management
About This Chapter

The Nastar provides centralized management for the GSM timing tasks. By setting GSM timing tasks, you can collect data from the EMS periodically, save the data as a file in certain path on the Nastar system, and import the data from the file to the database periodically for future query and analysis. In addition, you can delete the data whose storage duration has expired from the database at the preset time to save resource space of the system. By using the function of GSM centralized task management, you can create, modify, delete, suspend, resume, or cancel a GSM timing task. In addition, you can view information such as status and progress of a task. 8.1 Basic Knowledge of Centralized Task Management Centralized task management involves the concepts such as types of timing tasks, parameters for task scheduling, and states of timing tasks. Learning the basic knowledge of the centralized task management helps you perform the operations related to the centralized task management. 8.2 Creating a GSM User-Defined Timing Task The Nastar allows you to create GSM timing tasks. Thus, you can create GSM timing tasks by setting common parameters and extended parameters based on the requirements of network maintenance. 8.3 Modifying a GSM User-Defined Timing Task The Nastar allows you to modify certain parameters of a GSM user-defined timing task. If the execution of a GSM user-defined timing task is complete, you cannot modify the task. 8.4 Modifying a GSM Data Deletion Task This section describes how to modify a GSM data deletion task. If data is periodically imported to the Nastar database, the database resources may be insufficient. By performing the GSM data deletion task, the Nastar can delete the data whose storage duration has expired from the database at the preset time to save system resources. A GSM data deletion task is a system timing task. You can modify only certain parameters of the task. To modify a GSM data deletion task, you must be a user in the administrator group. If the execution of a GSM data deletion task is complete, you cannot modify the task. 8.5 Modifying the Task of Backing Up Data This section describes how to modify certain information about the system-created task of backing up data. 8.6 Setting the Suspend or Resume Time of a Timing Task
You can set an automatic suspend time or an automatic resume time for a timing task. In this situation, the Nastar automatically suspends the task or resumes the task. 8.7 Viewing Timing Tasks Through the Nastar function of viewing timing tasks, you can view the status of all timing tasks in a centralized manner. This helps you adjust the concerned timing tasks according to actual conditions. 8.8 Reference for the GSM Centralized Task Management GUI This section describes the interface for the GSM centralized task management and related information such as the parameters used in the centralized task management. This help you understand the functions of the GSM centralized task management.
8-2
Issue 03 (2010-06-30)
8.1 Basic Knowledge of Centralized Task Management

Centralized task management involves the concepts such as types of timing tasks, parameters for task scheduling, and states of timing tasks. Learning the basic knowledge of the centralized task management helps you perform the operations related to the centralized task management. 8.1.1 Types of Timing Tasks The Nastar divides timing tasks into different types according to execution periods and task features. 8.1.2 System Timing Tasks The system timing task is created during the installation or upgrade of the Nastar system. User dbuser is the Creator of the system timing task. 8.1.3 User Timing Task A user timing task is a customized task that is created to maintain a network. 8.1.4 Task Scheduling Parameters The task scheduling parameters are the parameters related to the task execution type, consisting of task start time, task execution period, and execution times. 8.1.5 States of a Timing Task A timing task has four states: idle, running, suspended, and finished. 8.1.6 Customizing the Interface for Managing Timing Tasks This section describes how to customize the interface for managing timing tasks. The system can display timing tasks of the specified function type in the navigation tree or display the timing tasks that meet the conditions in the task list.
8.1.1 Types of Timing Tasks

The Nastar divides timing tasks into different types according to execution periods and task features.
Tasks Divided According to Execution Period

According to the execution periods of tasks, the Nastar divides the managed timing tasks into two types: one-time task and periodic task. Table 8-1 describes the meanings of two task types. Table 8-1 Tasks divided according to execution period Task Type One-time task Periodic task Description A task is performed only once at a specific time. A task is performed periodically after a specific time.
Tasks Divided According to Task Features

According to different task features, the Nastar divides the managed tasks into two types: system timing tasks and user timing tasks. Table 8-2 describes the meanings of each task type.
Table 8-2 Tasks Divided According to Task Features Task Type System Timing Tasks User Timing Tasks Description System timing tasks are necessary for the Nastar system to run properly. For details, see 8.1.2 System Timing Tasks. User timing tasks are the user-defined tasks that are created to meet the requirement of network maintenance. For details, see 8.1.3 User Timing Task.
8.1.2 System Timing Tasks

The system timing task is created during the installation or upgrade of the Nastar system. User dbuser is the Creator of the system timing task. The Nastar uses
NOTE
to indicate system timing tasks.
l l
Only users in the administrator group can manage and view the system timing tasks. Other users cannot manage or view the system timing tasks. The system timing tasks cannot be copied or deleted. Only some parameters of the system timing tasks can be modified.
8.1.3 User Timing Task

A user timing task is a customized task that is created to maintain a network.
l l
You can create, modify, delete, copy, suspend, and resume user timing tasks. The Nastar uses to indicate the user timing tasks.
8.1.4 Task Scheduling Parameters

The task scheduling parameters are the parameters related to the task execution type, consisting of task start time, task execution period, and execution times. Table 8-3 describes the task scheduling parameters. Table 8-3 Description of the task description parameters Parameter Task Type Description According to different task execution periods, the Nastar divides the execution types of the managed timing tasks into two types: periodic execution and one-time execution. The execution type of the system timing tasks is periodic execution. The execution type of the other user timing tasks can be periodic execution or one-time execution. Indicates start time of periodic tasks and one-time tasks set during task creation, including date and time. The start time of tasks should be later than the current server time.
Issue 03 (2010-06-30)
Task start time
8-4
Parameter Period
Description
l
Interval between periodic tasks. It has two enlistments: unit and duration. The task execution period can be represented by month, week, day, and hour. The period interval range is as follows: 1 to 12 for month, 1 to 52 for week, 1 to 366 for day, 1 to 8784 for hour.
Run Times
Indicates execution times of a periodic task. The execution times range from 0 to 65535. The value 0 indicates no limit.
For example, if the scheduling parameters of the data collection task are:
l l l l
Execution type = Periodicity Start time = 2006-10-21 09:07:28 Execution period = 1 day Period execution times = 0
Infer that the system starts to carry out the data collection task every day from 2006-10-21 09:07:28.
8.1.5 States of a Timing Task

A timing task has four states: idle, running, suspended, and finished. The states of a timing task change with different operations. For details, see Figure 8-1. Figure 8-1 State transition of a timing task
Issue 03 (2010-06-30)
8-5
State transition of a timing task is as follows:

l l l l l l
A timing task is in the idle state after it is initially created. An idle task is changed to the running state after being scheduled. An idle task is changed to the suspended state after being suspended. A running task is changed to the idle state after being cancelled. A suspended task is changed to the idle state after being resumed. If a task need not be scheduled after being performed, it is in the finished state. If it needs to be scheduled again, it returns to the idle state.
When a timing task is in the idle, suspended, or finished state, you can delete the timing task.
8.1.6 Customizing the Interface for Managing Timing Tasks

This section describes how to customize the interface for managing timing tasks. The system can display timing tasks of the specified function type in the navigation tree or display the timing tasks that meet the conditions in the task list.
Prerequisite
Procedure
Step 1 Choose Maintenance > Task Management, the Task Management window is displayed. Step 2 Perform different operations according to different customized requirement. Customized Requirement Operation
Customize the navigation tree. 1. Right-click in the navigation tree and choose Filter Type from the shortcut menu. The Filter Type dialog box is displayed. 2. Select the timing task type to be displayed. By default, all the timing task types that the current user is authorized to browse are displayed. Customize the task list 1. Right-click the task list and select Filter Task. The Task Filter Setting dialog box is displayed. 2. Set the User Name, Category, Task State, and Last Run Result as the filtering conditions. For detailed parameter description, refer to 8.8.2 Parameter for Setting Task Filter Conditions. Step 3 Click OK. ----End
8.2 Creating a GSM User-Defined Timing Task

The Nastar allows you to create GSM timing tasks. Thus, you can create GSM timing tasks by setting common parameters and extended parameters based on the requirements of network maintenance. 8.2.1 Creating a Data Collection Task A data collection task is performed to collect the performance data, configuration data. and interference data of the M2000 to a specified path on the Nastar at the preset time. 8.2.2 Creating a Task of Importing GSM Performance Data A task of importing GSM performance data is performed to import data from the performance data file in the specified directory on the server to the database at the preset time. 8.2.3 Creating a Task of Importing GSM Configuration Data A task of importing GSM configuration data is performed to import data from the configuration data file in the specified directory on the server to the database at the preset time. 8.2.4 Creating a Task of Importing GSM Uplink ARFCN Scanning Data A task of importing GSM uplink ARFCN scanning data is performed to import data from the uplink ARFCN scanning data file in the specified directory on the server to the database at the preset time. 8.2.5 Creating a Task of Importing GSM Measurement-Task Data A task of importing GSM measurement-task data is performed to import data from the measurement-task data file in the specified directory on the server to the database at the preset time. 8.2.6 Creating a Task of Importing GSM/UMTS Neighboring-Cell Analysis Data A task of importing GSM/UMTS neighboring-cell analysis data is performed to import data from the GSM/UMTS neighboring-cell analysis data file in the specified directory on the server to the database at the preset time. 8.2.7 Creating a Task of Importing GSM VIP Analysis Data A task of importing GSM VIP analysis data is performed to import data from the VIP data file in the specified directory on the server to the database at the preset time. 8.2.8 Creating a Task of Importing GSM Cell Performance Analysis Data A task of importing GSM cell performance analysis data is performed to import data from the cell performance analysis data file in the specified directory on the server to the database at the preset time. 8.2.9 Creating a Task of Importing GSM Engineering Parameters A task of importing GSM engineering parameters is performed to import data from the engineering parameter file in the specified directory on the server to the database at the preset time.
8.2.1 Creating a Data Collection Task

A data collection task is performed to collect the performance data, configuration data. and interference data of the M2000 to a specified path on the Nastar at the preset time.
Issue 03 (2010-06-30)
8-7
Prerequisite
l l
You have logged in to the Nastar client. The E2E task is created and the required performance data, configuration data, and interference data are available on the EMS. The file path for saving the collected data is provided.
Context
l l
A CDMA data collection task is a user-defined timing task. A data collection task can be executed once or periodically. The options of the execution period are Minute, Hour, Day, Week, and Month. The data granularity of data collection tasks is different from that of E2E tasks. Through data collection tasks, the Nastar collects the data of BSCs or RNCs. Through E2E tasks, the Nastar enables the data collection switches of specific cells so that the data of these cells can be collected. Table 8-4 describes the mapping between the Nastar theme functions and the types of data to be collected. Table 8-4 Mapping between the Nastar theme functions and the corresponding data types Nastar Function Theme Data to Be Collected Configuration data and performance data Configuration data, performance data, and neighboring cell measurement task files Configuration data and uplink ARFCN scanning data
GSM MR analysis task GSM neighboring cell analysis task GSM uplink interference analysis task GSM frequency analysis task GSM VIP analysis task GSM complaint analysis support task GSM cell performance analysis task GSM/UMTS neighboring analysis task cell
Configuration data and performance data Configuration data and VIP analysis data Configuration data, complaint analysis support data, and neighboring cell measurement task files Configuration data and cell performance data
Configuration data, performance data, and GSM/UMTS neighboring cell analysis data
8-8
Issue 03 (2010-06-30)
Nastar Function CDMA frequency neighboring analysis task
Theme intracell
Data to Be Collected Configuration data, neighboring cell data, and engineering parameters
CDMA uplink interference ranking analysis task CDMA uplink interference spectrum analysis task CDMA VIP analysis task CDMA complaint analysis support task CDMA pollution task pilot analysis
Configuration data and uplink interference data
Configuration data and uplink spectrum data
Configuration data, VIP analysis data, and engineering parameters Configuration data and complaint analysis support data Configuration data and pilot pollution analysis data
CDMA cell performance analysis task CDMA coverage analysis task UMTS uplink interference analysis task UMTS frequency neighboring analysis task intracell
Configuration data and cell performance analysis data
Configuration data and coverage data Configuration data
Configuration data
UMTS coverage analysis tasks UMTS pilot pollution analysis task UMTS VIP analysis task UMTS complaint analysis support task UMTS cell performance analysis task
Issue 03 (2010-06-30)
Configuration data Configuration data and pilot pollution analysis data Configuration data and VIP analysis data Configuration data and complaint analysis support data Configuration data and cell performance data
8-9
Nastar Function UMTS/GSM neighboring analysis task
Theme
Data to Be Collected Configuration data, performance data, and UMTS/GSM neighboring cell analysis data
cell
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
Choose Task Type > Data Collection from the navigation tree and double-click Data Collection. The New Task dialog box is displayed. The Task Type is set to Data Collection by default.
Step 3 Set the basic information about the task. 1. 2. 3. Type the name of the task in Task Name. Select the data collection task from Task Type. Select Once or Period in the Run Type area.
Step 4 Click Next to set the execution time. 1. Click . In the displayed Date/Time Selection dialog box, set the start time. You can also set the start time by editing the Start Time area.
NOTE
l l
Start Time must be later than the current server time. If Run Type is set to Once, the Start Time parameter is invalid after you select Run At Once. In addition, the task is performed immediately after the settings are complete.
2.
Perform operations based on Run Type.

l l
If Run Type is set to Once, perform Step 5. If Run Type is set to Period, perform Step 5 after you set Period and Run Times.
Configuration data: It is recommended that configuration data is collected once each day. GSM performance data: Collect GSM performance data is collected once each half hour or each hour based on the traffic statistics period. GSM neighboring cell measurement task files: It is recommended that GSM neighboring cell measurement task files are collected once each day. GSM uplink frequency scanning data: It is recommended that GSM uplink frequency scanning data is collected once each hour.
Step 5 Click Next. Then, set parameters such as OSS and Data Type.
8-10
Issue 03 (2010-06-30)
If ... Any of the following conditions is met: l M2000V2R6 is selected from the OSS drop-down list box and Config data is selected from the Data type drop-down list box l M2000V2R8 or M2000V2R9 is selected from the OSS drop-down list box and Config data, Neighboring Measurement Task File, or Frqlog Data is selected from the Data type dropdown list box M2000V2R8 or M2000V2R9 is selected from the OSS drop-down list box and Config data, Performance data, Neighboring Measurement Task File or Frqlog Data is selected from the Data type drop-down list box.
Then ... Select one or multiple OSSs in the navigation tree.
It indicates that ... The related data of all the NEs in the selected OSS are periodically collected to a specified path on the Nastar. The related data of the selected NEs is periodically collected to a specified path on the Nastar.
Select one or multiple NE object nodes under certain OSSs in the navigation tree.
Select one or multiple OSSs in the navigation tree.
The related data of all the NEs in the selected OSS are periodically collected to a specified path on the Nastar. The related data of the selected NEs is periodically collected to a specified path on the Nastar. The related data is periodically collected within the specified period or collected once from the M2000 to a specified path on the Nastar. The Nastar can access a specified file path on the M2000 and collect the related data to a specified path on the Nastar. All the related data are collected from the M2000 to the Nastar each time during a periodic collection task. The Nastar traverses all the files under the subdirectories in the path where the configured source data is saved and collects the data.
Select one or multiple NE object nodes under certain OSSs in the navigation tree. Select Specify the time range and set Start time and End time.
M2000V2R6, M2000V2R8, or M2000V2R9 is selected from the OSS drop-down list box and Any is selected from the Data type drop-down list box
Set the path for saving files on the M2000 and the Nastar and set the file name.
Select Get files repeatedly.
Select Get files all over.
Issue 03 (2010-06-30)
8-11
Step 6 Click Finish. The new task is displayed in the task list. ----End
Postrequisite
l
Deleting a task If required, you can delete created tasks to save system resources.
NOTE
l l l
You can delete only the tasks that are created by yourself. If you are a user in the administrator group, you can delete all the user-defined tasks. System tasks cannot be deleted. Running tasks cannot be deleted.
1. 2. 3. 4.
l
Choose Task Type from the navigation tree in the right pane of the Task Management window. Select one or more timing tasks from the task list in the right pane. Click Delete. In the Confirm dialog box, click Yes. Then, the task is deleted from the task list.
Suspending a task To delay the execution of a task, you can suspend a timing task that is in the idle state. 1. 2. Choose Task Type from the navigation tree in the right pane of the Task Management window. You can manually or automatically suspend a task that is in the idle state:
Suspending a task manually Select one or more timing tasks that are in the idle state from the task list in the right pane. Right-click and choose Suspend. In the Confirm dialog box, click Yes.
Suspending a task automatically Select a timing task to be suspended from the task list in the right pane. Right-click and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Suspend Time and set its value. Click OK. To set the time for automatically suspending a task, see 8.8.16 Parameters for Setting the Time of a Timing Task.
Resuming a task You can resume a suspended task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the tasks that are in the idle state can be scheduled by the system.
1. 2.
Choose Task Type from the navigation tree in the right pane of the Task Management window. You can manually or automatically resume a task that is in the suspended state:
Resuming a task manually

8-12
Select one or more timing tasks that are in the suspended state from the task list in the right pane. Right-click and choose Resume. In the Confirm dialog box, click Yes.
Resuming a task automatically Select a timing task to be resumed from the task list in the right pane. Right-click and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Resume Time and set its value. Click OK. To set the time for automatically resuming a task, see 8.8.16 Parameters for Setting the Time of a Timing Task.
Canceling a task You can cancel a running task. After a task is canceled, its state is changed from Running to Idle.
NOTE
You can cancel only the tasks that are created by yourself. If you are a user in the administrator group, you can cancel all the user-defined timing tasks.
1. 2. 3.
l
Choose Task Type from the navigation tree in the right pane of the Task Management window. Select one or more running tasks from the task list in the right pane. Right-click and choose Cancel. In the Confirm dialog box, click Yes. Then, the task state is changed from Running to Idle.
Viewing a log You can view the system log related to a collection task. For details, see 5.3.1 Querying System Logs.
8.2.2 Creating a Task of Importing GSM Performance Data

A task of importing GSM performance data is performed to import data from the performance data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The GSM performance data is collected to the Nastar server.
Context
l l
A task of importing GSM performance data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. The system allows you to create only one user-defined timing task of this type. The task of importing GSM performance data can be performed only after the related data collection task is complete. Otherwise, the integrity of the imported data may be affected. The formats of files to be imported vary according to collection mode.
l l
Issue 03 (2010-06-30)

If Data Type of a collection task is set to Any, the files in .zip format can be imported. If Data Type of a collection task is set to a type other than Any, the files in .gz format can be imported.
Procedure
TIP
You can choose Task Type > Import GSM Data from the navigation tree and then double-click Import GSM Performance Data. The New Task dialog box is displayed. The Task Type parameter is set to Import GSM Performance Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. Select the task of importing performance data from Task Type.
Step 4 Click Next to set the execution time. 1. Click

NOTE
. In the displayed Date/Time Selection dialog box, set the start time.
You can also set the start time by editing the Start Time area.
Start Time must be later than the current server time.
2.
Set Period and Run Times.
Step 5 Click Complete. The new task is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Choose Task Type from the navigation tree in the left pane of the Task Management window. Select the timing task from the task list in the right pane. Click Delete. In the Confirm dialog box, click Yes. Then, the task is deleted from the task list.
Suspending a task To delay the execution of a task, you can suspend a timing task that is in the idle state.
8-14
Issue 03 (2010-06-30)
1. 2.
Choose Task Type from the navigation tree in the right pane of the Task Management window. You can manually or automatically suspend a task that is in the idle state:
Suspending a task manually Select the timing task that is in the idle state from the task list in the right pane. Right-click and choose Suspend. In the Confirm dialog box, click Yes.
NOTE
1. 2.
Resuming a task manually Select the timing task that is in the suspended state from the task list in the right pane. Right-click and choose Resume. In the Confirm dialog box, click Yes.
NOTE
1. 2. 3.
l
Choose Task Type from the navigation tree in the right pane of the Task Management window. Select the running task from the task list in the right pane. Right-click and choose Cancel. In the Confirm dialog box, click Yes. Then, the task state is changed from Running to Idle.
Viewing a log You can view the system log related to an import task. For details, see 5.3.1 Querying System Logs.
Issue 03 (2010-06-30)
8-15
8.2.3 Creating a Task of Importing GSM Configuration Data

A task of importing GSM configuration data is performed to import data from the configuration data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The GSM configuration data is collected to the Nastar server.
Context
l l
A task of importing GSM configuration data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. The system allows you to create only one user-defined timing task of this type.
Procedure
TIP
You can choose Task Type > Import GSM Data from the navigation tree and then double-click Import GSM CFG Data. The New Task dialog box is displayed. The Task Type parameter is set to Import GSM CFG Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. From Task Type, select the task of importing configuration data.

NOTE
2.
Postrequisite
l
8-16
Issue 03 (2010-06-30)

NOTE
l l l
1. 2. 3. 4.
l
NOTE
1. 2.
Canceling a task
Issue 03 (2010-06-30)
You can cancel a running task. After a task is canceled, its state is changed from Running to Idle.
NOTE
1. 2. 3.
l
8.2.4 Creating a Task of Importing GSM Uplink ARFCN Scanning Data

A task of importing GSM uplink ARFCN scanning data is performed to import data from the uplink ARFCN scanning data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The GSM uplink ARFCN scanning data is collected to the Nastar server.
Context
l l
A task of importing GSM uplink ARFCN scanning data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. The system allows you to create only one user-defined timing task of this type.
Procedure
TIP
You can choose Task Type > Import GSM Data from the navigation tree and then double-click Import GSM Uplink Interference Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import GSM Uplink Interference Analysis Data by default.
Step 3 Set the basic information about the task. 1.

8-18
Type the name of the task in Task Name.

2.
From Task Type, select the task of importing the uplink ARFCN scanning data.
Step 4 Click Next to set the execution time. 1. Click . In the displayed Date/Time Selection dialog box, set the start time. You can also set the start time by editing the Start Time area.
NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Issue 03 (2010-06-30)
8-19

NOTE
1. 2.
NOTE
1. 2. 3.
l
8.2.5 Creating a Task of Importing GSM Measurement-Task Data

A task of importing GSM measurement-task data is performed to import data from the measurement-task data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The GSM measurement-task data is collected to the Nastar server.
Context
l
A task of importing GSM measurement-task data is a user-defined timing task.

8-20

l
The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. The system allows you to create only one user-defined timing task of this type.
Procedure
TIP
You can choose Task Type > Import GSM Data from the navigation tree and then double-click Import GSM Measurement Task File for Neighbor Cell. The New Task dialog box is displayed. The Task Type parameter is set to Import GSM Measurement Task File for Neighbor Cell by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. Select the task of importing measurement-task data from Task Type.

NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Suspending a task To delay the execution of a task, you can suspend a timing task that is in the idle state.
Issue 03 (2010-06-30)
8-21
1. 2.
Choose Task Type from the navigation tree in the right pane of the Task Management window. You can manually or automatically suspend a task that is in the idle state:
NOTE
1. 2.
NOTE
1. 2. 3.
l
8-22
Issue 03 (2010-06-30)
8.2.6 Creating a Task of Importing GSM/UMTS Neighboring-Cell Analysis Data

A task of importing GSM/UMTS neighboring-cell analysis data is performed to import data from the GSM/UMTS neighboring-cell analysis data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The GSM/UMTS neighboring-cell analysis data is collected to the Nastar server.
Context
l
A task of importing GSM/UMTS neighboring-cell analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. The system allows you to create only one user-defined timing task of this type.
Procedure
TIP
You can choose Task Type > Import GSM Data from the navigation tree and then double-click Import GSM/UMTS Neighboring Cell Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import GSM/UMTS Neighboring Cell Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. Select the task of importing GSM/UMTS neighboring-cell analysis data from Task Type.

NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
NOTE
1. 2.
Resuming a task automatically Select a timing task to be resumed from the task list in the right pane. Right-click and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Resume Time and set its value. Click OK.
8-24
Issue 03 (2010-06-30)
To set the time for automatically resuming a task, see 8.8.16 Parameters for Setting the Time of a Timing Task.
l
NOTE
1. 2. 3.
l
8.2.7 Creating a Task of Importing GSM VIP Analysis Data

A task of importing GSM VIP analysis data is performed to import data from the VIP data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to the GSM VIP analysis is saved on the Nastar server.
Context
l l
The task of importing GSM VIP analysis data is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month. For the tasks of one type, only one user-defined scheduled task of this type can be created.
Procedure
TIP
Choose Task Type > GSM Data Import > Import GSM VIP Analysis Data from the navigation tree. Double-click the node, the New Task dialog box is displayed. The parameter Task Type is set to Import GSM VIP Analysis Data by default.
Step 3 Set the basic information about the task.

1. 2.
Enter the name of the scheduled task in Task Name. Select the VIP analysis data import task from Task Type.
Step 4 Click Next to set the execution time. 1. Click . In the displayed Date/Time Selection dialog box, set the start time of the task. You can also set the start time by editing the Start Time area.
NOTE
2.
Step 5 Click Finish. The new VIP analysis data import task is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Resuming a task
8-26
You can resume a suspended task to the idle state. Then, the task can be scheduled by the system.
NOTE
1. 2.
NOTE
1. 2. 3.
l
8.2.8 Creating a Task of Importing GSM Cell Performance Analysis Data

A task of importing GSM cell performance analysis data is performed to import data from the cell performance analysis data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to the GSM cell performance analysis is saved on the Nastar server.
Issue 03 (2010-06-30)
Context
l l
The task of importing GSM cell performance analysis data is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month. For the tasks of one type, only one user-defined scheduled task of this type can be created.
Procedure
TIP
Choose Task Type > GSM Data Import > Import GSM Cell Performance Analysis Data from the navigation tree. Double-click the node, the New Task dialog box is displayed. The parameter Task Type is set to Import GSM Cell Performance Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Enter the name of the scheduled task in Task Name. Select the cell performance analysis data import task from Task Type.

NOTE
. In the displayed Date/Time Selection dialog box, set the start time of the task.
2.
Step 5 Click Finish. The new cell performance analysis data import task is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
8-28
Issue 03 (2010-06-30)

l
NOTE
1. 2.
NOTE
1. 2. 3.
Issue 03 (2010-06-30)
8-29

l
8.2.9 Creating a Task of Importing GSM Engineering Parameters

A task of importing GSM engineering parameters is performed to import data from the engineering parameter file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The GSM engineering parameters are collected to the Nastar server.
Context
l l
A task of importing GSM engineering parameters is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. The system allows you to create only one user-defined timing task of this type.
Procedure
TIP
Choose Task Type > GSM Data Import > GSM Engineering Parameter Import from the navigation tree. Double-click the node, the New Task dialog box is displayed. The Task Type parameter is set to GSM Engineering Parameter Import by default.
Step 3 Set the information about the task. 1. 2. Enter the name of timing task in Task Name. Select the task of importing performance data from Task Type.
Step 4 Click Next to set the time. 1. Click

NOTE
2.
Postrequisite
l
Delete a task. You can delete created tasks to save the system resources.
NOTE
l l l
Each user can delete only the tasks that are created by him. If you are a user in the administrator group, you can delete all the user-defined tasks. System tasks cannot be deleted. Running tasks cannot be deleted.
1. 2. 3. 4.
l
Choose Task Type from the navigation tree in the left pane of the Task Management window. Select a periodic task from the task list in the right part of the window. Click Delete. In the Confirm dialog box, click Yes. Then the task is deleted from the task list.
Suspend a task. To delay the execution of a task, you can suspend a timing task that is in the idle state. 1. 2. Choose Task Type from the navigation tree in the left pane of the Task Management window. You can manually or automatically suspend a task that is in the idle state:
Suspend a task manually. Select an existing timing tasks that are in the idle state from the task list in the right pane. Right-click the task and choose Suspend. In the Confirm dialog box, click Yes.
Suspend a task automatically. Select a timing task to be suspended from the task list in the right pane. Right-click and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Suspend Time and set its value. Click OK. To set the time for automatically suspending a task, see 8.8.16 Parameters for Setting the Time of a Timing Task.
Resume a task. You can restore a suspended task to wait for the dispatching. Then the status of the task is changed to idle.
NOTE
Only idle tasks can wait to be used.
1. 2.
Choose Task Type from the navigation tree in the left pane of the Task Management window. You can manually or automatically resume a task that is in the suspended state:
Resume a task manually. Select an existing timing tasks that are in the suspended state from the task list in the right pane. Right-click the task and choose Resume. In the Confirm dialog box, click Yes.
Resume a task automatically.

Issue 03 (2010-06-30)
Select a timing task to be resumed from the task list in the right pane. Right-click the task and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Resume Time and set its value. Click OK. To set the time for automatically resuming a task, see 8.8.16 Parameters for Setting the Time of a Timing Task.
l
Cancel a task. You can cancel a running task. The task status is changed to idle after being cancelled.
NOTE
1. 2. 3.
l
Choose Task Type from the navigation tree in the left pane of the Task Management window. Select an existing running task in the task list in the right pane. Right-click the task and choose Cancel. In the Confirm dialog box, click Yes. Then, the task state is changed from Running to Idle.
View a log. You can view the system log related to an import task. For details, see 5.3.1 Querying System Logs.
8.3 Modifying a GSM User-Defined Timing Task

The Nastar allows you to modify certain parameters of a GSM user-defined timing task. If the execution of a GSM user-defined timing task is complete, you cannot modify the task. 8.3.1 Modifying a Data Collection Task This section describes how to modify certain information about a data collection task. 8.3.2 Modifying a Task of Importing GSM Performance Data This section describes how to modify certain information about a task of importing GSM performance data. 8.3.3 Modifying a Task of Importing GSM Configuration Data This section describes how to modify certain information about a task of importing GSM configuration data. 8.3.4 Modifying a Task of Importing GSM Uplink ARFCN Scanning Data This section describes how to modify certain information about a task of importing GSM uplink ARFCN scanning data. 8.3.5 Modifying a Task of Importing GSM Measurement-Task File Data This section describes how to modify certain information about a task of importing GSM measurement-task file data. 8.3.6 Modifying a Task of Importing GSM/UMTS Neighboring-Cell Analysis Data This section describes how to modify certain information about a task of importing GSM/UMTS neighboring-cell analysis data. 8.3.7 Modifying a Task of Importing GSM VIP Analysis Data This section describes how to modify certain information about a task of importing GSM VIP analysis data.
8.3.8 Modifying a Task of Importing GSM Cell Performance Analysis Data This section describes how to modify certain information about a task of importing GSM cell performance analysis data. 8.3.9 Modifying a Task of Importing GSM Engineering Parameters This section describes how to modify certain information about a task of importing GSM engineering parameters.
8.3.1 Modifying a Data Collection Task

This section describes how to modify certain information about a data collection task.
Prerequisite
l l
You have logged in to the Nastar client. A data collection task is created.
Context
l l
A data collection task is a user-defined timing task. A data collection task can be executed once or periodically. The options of the execution period are Minute, Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Data Collection > Data Collection from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages.
NOTE
Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
If the task is running, the modification takes effect at the next execution.
----End
8.3.2 Modifying a Task of Importing GSM Performance Data

This section describes how to modify certain information about a task of importing GSM performance data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing GSM configuration data is created.
Issue 03 (2010-06-30)
Context
l l
A task of importing GSM performance data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import GSM Data > Import GSM Performance Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
8.3.3 Modifying a Task of Importing GSM Configuration Data

This section describes how to modify certain information about a task of importing GSM configuration data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing GSM configuration data is created.
Context
l l
A task of importing GSM configuration data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import GSM Data > Import GSM CFG Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.

NOTE
----End
8.3.4 Modifying a Task of Importing GSM Uplink ARFCN Scanning Data

This section describes how to modify certain information about a task of importing GSM uplink ARFCN scanning data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing GSM uplink ARFCN scanning data is created.
Context
l l
A task of importing GSM uplink ARFCN scanning data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import GSM Data > Import GSM Uplink Interference Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
8.3.5 Modifying a Task of Importing GSM Measurement-Task File Data

This section describes how to modify certain information about a task of importing GSM measurement-task file data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing GSM measurement-task file data is created.
Issue 03 (2010-06-30)
Context
l l
A task of importing GSM measurement-task data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import GSM Data > Import GSM Measurement Task File for Neighbor Cell from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
8.3.6 Modifying a Task of Importing GSM/UMTS NeighboringCell Analysis Data

This section describes how to modify certain information about a task of importing GSM/UMTS neighboring-cell analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing GSM/UMTS neighboring-cell analysis data is created.
Context
l
A task of importing GSM/UMTS neighboring-cell analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import GSM Data > Import GSM/UMTS Neighboring Cell Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK.
You can browse the latest information about the task in the task list.
NOTE
----End
8.3.7 Modifying a Task of Importing GSM VIP Analysis Data

This section describes how to modify certain information about a task of importing GSM VIP analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing GSM VIP analysis data is created.
Context
l l
The task of importing GSM VIP analysis data is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > GSM Data Import > Import GSM VIP Analysis Data from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can view the latest information in the task list.
NOTE
If the task is running, the modified data takes effect at the next execution.
----End
8.3.8 Modifying a Task of Importing GSM Cell Performance Analysis Data

This section describes how to modify certain information about a task of importing GSM cell performance analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing GSM cell performance analysis data is created.
Issue 03 (2010-06-30)
Context
l l
The task of importing GSM cell performance analysis data is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > GSM Data Import > Import GSM Cell Performance Analysis Data from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can view the latest information in the task list.
NOTE
----End
8.3.9 Modifying a Task of Importing GSM Engineering Parameters

This section describes how to modify certain information about a task of importing GSM engineering parameters.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing GSM engineering parameters is created.
Context
l l
A task of importing GSM engineering parameters is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > GSM Data Import > GSM Engineering Parameter Import from the navigation tree on the left. Step 3 Double-click or click Attribute to view the Attribute dialog box. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can browse the newest task information in the task list.

NOTE
----End
8.4 Modifying a GSM Data Deletion Task

This section describes how to modify a GSM data deletion task. If data is periodically imported to the Nastar database, the database resources may be insufficient. By performing the GSM data deletion task, the Nastar can delete the data whose storage duration has expired from the database at the preset time to save system resources. A GSM data deletion task is a system timing task. You can modify only certain parameters of the task. To modify a GSM data deletion task, you must be a user in the administrator group. If the execution of a GSM data deletion task is complete, you cannot modify the task. 8.4.1 Modifying the Task of Deleting GSM History Data This section describes how to modify certain information about the system-created task of deleting GSM history data. 8.4.2 Modifying the Task of Deleting GSM Performance Data This section describes how to modify certain information about the system-created task of deleting GSM performance data. 8.4.3 Modifying the Task of Deleting GSM Configuration Data This section describes how to modify certain information about the system-created task of deleting GSM configuration data. 8.4.4 Modifying a Task of Deleting GSM Uplink ARFCN Scanning Data This section describes how to modify certain information about the system-created task of deleting GSM uplink ARFCN scanning data. 8.4.5 Modifying a Task of Deleting GSM Measurement-Task File Data This section describes how to modify certain information about the system-created task of deleting GSM measurement-task file data. 8.4.6 Modifying a Task of Deleting GSM/UMTS Neighboring-Cell Analysis Data This section describes how to modify certain information about the system-created task of deleting GSM/UMTS neighboring-cell analysis data. 8.4.7 Modifying a Task of Deleting GSM VIP Analysis Data This section describes how to modify certain information about the system-created task of deleting GSM VIP analysis data. 8.4.8 Modifying a Task of Deleting GSM Cell Performance Analysis Data This section describes how to modify certain information about the system-created task of deleting GSM cell performance analysis data.
8.4.1 Modifying the Task of Deleting GSM History Data

This section describes how to modify certain information about the system-created task of deleting GSM history data.
Issue 03 (2010-06-30)
8-39
Prerequisite
l l
You have logged in to the Nastar client. You are a member of the Administrators user group.
Context
l
The task of deleting GSM history data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time, Execution Period, and The data files will be reserved in the server. Deleting history data refers to deleting the data files that are collected to certain file path on the Nastar server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Data Collection > Old Data Deletion from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages.
NOTE
NOTE
----End
8.4.2 Modifying the Task of Deleting GSM Performance Data

This section describes how to modify certain information about the system-created task of deleting GSM performance data.
Prerequisite
l l
Context
l
The task of deleting GSM performance data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time, Period, and Data Reserve Days. Deleting performance data refers to deleting the performance data collected to the NASTAR server.
8-40
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete GSM Data > GSM Performance Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
8.4.3 Modifying the Task of Deleting GSM Configuration Data

This section describes how to modify certain information about the system-created task of deleting GSM configuration data.
Prerequisite
l l
Context
l
The task of deleting GSM configuration data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time, Period, and Data Reserve Days. Deleting configuration data refers to deleting the configuration data collected to the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete GSM Data > GSM CFG Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
8.4.4 Modifying a Task of Deleting GSM Uplink ARFCN Scanning Data

This section describes how to modify certain information about the system-created task of deleting GSM uplink ARFCN scanning data.
Prerequisite
l l
Context
l
The task of deleting uplink ARFCN scanning data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time, Period, and Data Reserve Days. Deleting scanning data of the uplink frequencies refers to deleting the scanning data of the uplink frequencies collected to the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete GSM Data > GSM Uplink Interference Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
8.4.5 Modifying a Task of Deleting GSM Measurement-Task File Data

This section describes how to modify certain information about the system-created task of deleting GSM measurement-task file data.
Prerequisite
l l
8-42
Issue 03 (2010-06-30)
Context
l
The task of deleting GSM measurement-task file data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time, Period, and Data Reserve Days. Deleting data of neighboring measurement tasks refers to deleting the data of neighboring measurement tasks collected to the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete GSM Data > GSM Measurement Task File for Neighbor Cell Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
8.4.6 Modifying a Task of Deleting GSM/UMTS Neighboring-Cell Analysis Data

This section describes how to modify certain information about the system-created task of deleting GSM/UMTS neighboring-cell analysis data.
Prerequisite
l l
Context
l
The task of deleting GSM/UMTS neighboring-cell analysis data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time, Period, and Data Reserve Days. Deleting GSM/UMTS neighboring-cell analysis data refers to deleting the data of GSM/ UMTS neighboring cell analysis tasks collected to the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 Choose Task Type > Delete GSM Data > GSM/UMTS Neighboring Cell Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
8.4.7 Modifying a Task of Deleting GSM VIP Analysis Data

This section describes how to modify certain information about the system-created task of deleting GSM VIP analysis data.
Prerequisite
l l
You have logged in to the Nastar client. The current user is a member of the user group Administrators.
Context
l
The task of deleting GSM VIP analysis data is a system scheduled task. It can only be executed periodically. Only the parameters Start Time and Period of a GSM VIP analysis data deletion task can be modified. Deleting the VIP analysis data is performed to delete the expired VIP analysis data on the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete GSM Data > GSM VIP Analysis Data Maintenance from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can view the latest information in the task list.
NOTE
----End
8.4.8 Modifying a Task of Deleting GSM Cell Performance Analysis Data

This section describes how to modify certain information about the system-created task of deleting GSM cell performance analysis data.
Prerequisite
l l
Context
l
The task of deleting GSM cell performance analysis data is a system scheduled task. It can only be executed periodically. Only the parameters Start Time and Period of a GSM cell performance analysis data deletion task can be modified. Deleting the cell performance analysis data is performed to delete the expired cell performance analysis data on the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete GSM Data > GSM Cell Performance Analysis Data Maintenance from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can view the latest information in the task list.
NOTE
----End
8.5 Modifying the Task of Backing Up Data

This section describes how to modify certain information about the system-created task of backing up data.
Prerequisite
l l
Context
l
The task of backing up data is a system timing task. It can be executed only periodically.
Issue 03 (2010-06-30)

l
You can modify the following parameters of the task: Start Time, Execution Period, Full Backup Time, Backup Mode, and Backup Path. Periodic backup refers to perform full backup on certain day within the period, and perform incremental backup at other time. The Nastar services are not disrupted when you back up data.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Data Backup > Data Backup from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages.
NOTE
NOTE
----End
8.6 Setting the Suspend or Resume Time of a Timing Task

You can set an automatic suspend time or an automatic resume time for a timing task. In this situation, the Nastar automatically suspends the task or resumes the task.
Prerequisite
l l
You have logged in to the Nastar client. At least one suspended or idle timing task exists.
Context
l
The system suspends an idle task and delay the time for using this task. If the timing task is not in the idle state at the specified time, it fails to be suspended. In the specified time, the system resumes a suspended task and then the task is in the idle status and wait to be dispatched. If the timing task is not in the idle state at the specified time, it fails to be suspended. You are not allowed to set auto-suspend or auto-resume a running timing task.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the task type of which you plan to suspend/restore. Step 3 Select a task in the task list in the right pane. Right-click the task and select Suspend/Restore
Step 4 In the Timing Suspend/Resume dialog box, select Suspend Time or Resume Time as required. Step 5 Set the suspend time or resume time. For details of setting an automatic suspend time or an automatic restore time, refer to 8.8.16 Parameters for Setting the Time of a Timing Task. ----End
8.7 Viewing Timing Tasks

Through the Nastar function of viewing timing tasks, you can view the status of all timing tasks in a centralized manner. This helps you adjust the concerned timing tasks according to actual conditions. 8.7.1 Browsing the Information of Timing Tasks The Nastar offers the integrated task browsing function, which allows the authorized users to browse tasks. 8.7.2 Checking the Task Progress You can view the progress of all the sub-tasks of a specific task. 8.7.3 Checking the Task Execution You can view the last execution results of a timing task.
8.7.1 Browsing the Information of Timing Tasks

The Nastar offers the integrated task browsing function, which allows the authorized users to browse tasks.
Prerequisite
l l
You have logged in to the Nastar client. At least one timing task exists.
Context
l l
Common users can browse only user tasks but cannot browse system tasks. The administrator can browse all tasks.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree.
l l
In the task list, all the tasks are displayed. If you want to view the common parameters and extended parameters of each task, go to Step 3
Step 3 Double click a task, or select a task and click Attribute. The Attribute dialog box is displayed. In the Common Parameter tab and Extended Parameter tab, you can view the task details.

NOTE
l l
If State of a task is Finished, you can view the task information only. If State of a task is Idle, Suspend, or Running, you can modify the task details in the Attribute dialog box.
----End
8.7.2 Checking the Task Progress

You can view the progress of all the sub-tasks of a specific task.
Prerequisite
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the task whose progress you want to view. In the Progress column of the task list on the right, you can view the task execution information. ----End
8.7.3 Checking the Task Execution

You can view the last execution results of a timing task.
Prerequisite
l l
Context
l
During the creation of CME tasks, sub-tasks are created, which are executed in different phases. You can browse the execution progress of subtasks of CME tasks.
Procedure
l
View the execution conditions in the Prev Execution Result column in the task list in the right pane. You can check the result details in the Result Info area.
----End
8.8 Reference for the GSM Centralized Task Management GUI

This section describes the interface for the GSM centralized task management and related information such as the parameters used in the centralized task management. This help you understand the functions of the GSM centralized task management. 8.8.1 Interface Description: Centralized Task Management This section describes the Task Management interface and relevant parameters, which helps you perform the related operations. 8.8.2 Parameter for Setting Task Filter Conditions This section describes the parameters in the Task Filter Setting dialog box. When you set filter conditions for a task list, you can refer to this section. 8.8.3 Parameter for Setting Common Parameters for Timing Tasks This section describes the parameters on the Common Parameters tab on property panels of all timing tasks. When you modify a timing task, you can refer to this section. 8.8.4 Parameter for Setting the Time of a Common Periodic Task This section describes the time parameters in the New Task dialog box. When you set the time of a periodic task, you can refer to this section. 8.8.5 Parameter for Setting the Time of a Common One-Time Task This section describes the time parameter in the New Task dialog box. When you modify the time of a one-time task, you can refer to this section. 8.8.6 Parameters for Creating or Modifying a Data Collection Task This section describes the parameters related to data collection tasks. You can refer to the description when creating or modifying data collection tasks. 8.8.7 Parameters for Modifying the Task of Deleting History Data This section describes the parameters related to the task of deleting history data. You can refer to the description when modifying the task of deleting history data. 8.8.8 Parameters for Modifying the Task of Deleting GSM Performance Data This section describes the parameters related to the task of deleting GSM performance data. You can refer to the description when modifying the task of deleting GSM performance data. 8.8.9 Parameters for Modifying the Task of Deleting GSM Configuration Data This section describes the parameters related to the task of deleting GSM configuration data. You can refer to the description when modifying the task of deleting GSM configuration data. 8.8.10 Parameters for Modifying the Task of Deleting the GSM Uplink ARFCN Scanning Data This section describes the parameters related to the task of deleting the GSM uplink ARFCN scanning data. You can refer to the description when modifying the task of deleting the GSM uplink ARFCN scanning data. 8.8.11 Parameters for Modifying the Task of Deleting the GSM Measurement-Task File Data This section describes the parameters related to the task of deleting the GSM measurement-task file data. You can refer to the description when modifying a task of deleting the GSM measurement-task file data. 8.8.12 Parameters for Modifying the Task of Deleting the GSM/UMTS Neighboring-Cell Analysis Data
This section describes the parameters related to the task of deleting the GSM/UMTS neighboring-cell analysis data. You can refer to the description when modifying a task of deleting the GSM/UMTS neighboring-cell analysis data. 8.8.13 Parameters for Modifying the Task of Deleting GSM VIP Analysis Data This section describes the parameters related to the task of deleting GSM VIP analysis data. You can refer to the description when modifying the task of deleting GSM VIP analysis data. 8.8.14 Parameters for Modifying the Task of Deleting GSM Cell Performance Analysis Data This section describes the parameters related to the task of deleting GSM cell performance analysis data. You can refer to the description when modifying the task of deleting GSM cell performance analysis data. 8.8.15 Parameters for Modifying the Task of Backing Up Data This section describes the parameters related to the task of backing up data. You can refer to the description when modifying the task of backing up data. 8.8.16 Parameters for Setting the Time of a Timing Task This section describes the parameters of auto-suspend time and auto-resume time for timing tasks.
8.8.1 Interface Description: Centralized Task Management

This section describes the Task Management interface and relevant parameters, which helps you perform the related operations. After you log in to the server, the Task Management interface is displayed, as shown in Figure 8-2. Table 8-5 describes each element displayed in Figure 8-2. Figure 8-2 Integrated Task Management interface
8-50
Issue 03 (2010-06-30)
Table 8-5 Description of the Integrated Task Management interface No. (1) (2) Name Navigation tree Task result information panel Description You can precisely locate a timing task through the navigation tree. After a task is carried out, the task result is displayed. On the task result information panel, you can browse the result of the task last carried out. Only the result of the currently selected task is displayed on the task result information panel. If multiple tasks are selected in the task list, only the result of the firstly selected task is displayed. The buttons used for carrying out integrated task management are available on the button panel. You can browse the timing tasks that exist on the server side and the detailed information. In the task list, different colors are used for indicate different states of tasks (gray: complete; orange: suspended; blue: active; white: idle). The selected color of the task is darker than the previous color of the task.
(3)
Button panel
(4)
Task list
8.8.2 Parameter for Setting Task Filter Conditions

This section describes the parameters in the Task Filter Setting dialog box. When you set filter conditions for a task list, you can refer to this section.
Parameters
Parameter User Name Current User Description Description: Indicates the user that operates the client. Other Users Description: Indicates other users except the current user. Catego ry User Task Description: Indicates the task created by users. System Task Description: Indicates the task created by OMC during the system installation or upgrade.
Issue 03 (2010-06-30)
8-51
Parameter State Idle
Description Description: Indicates that the task waits for being performed by the system.
Running
Description: Indicates that the task is being performed by the system.
Suspend
Description: The task is not ready to be scheduled.
Finished
Description: Indicates that the task is completed by the system.
Last Run Result
Success
Description: Indicates that the task is successfully carried out.
Processing
Description: Indicates that the task is being processed by the system.
Partly Success Failed
Description: Indicates that the task is partly successfully carried out. Description: Indicates that the task fails to carry out.
Miss Run Time
Description: Indicates that the task misses the previous performed time. If the server is not running properly or the task is suspended before the execution, the task may miss the previous execution. Description: Indicates that the previous execution result in the server is lost caused by improper service or sudden power cut. Thus, after recovery, the previous execution result cannot be determined.
Unknown
8.8.3 Parameter for Setting Common Parameters for Timing Tasks

This section describes the parameters on the Common Parameters tab on property panels of all timing tasks. When you modify a timing task, you can refer to this section.
8-52
Issue 03 (2010-06-30)
Parameters
Parameter Task Name Description Description: Refers to the name of a timing task Value Range Value:
l
A maximum of 60 characters Allowed characters: English letters, numbers, -, and _ Unique and not null Case sensitive
l l
Run Type
Once
Description: If you select this option, the system runs the created task once at the defined time point.
Period
Description: If you select this option, the system runs the created task periodically.
Start Time
Description: This parameter sets the time for starting a task. The start time should be later than the time displayed on the server.
Value: If you have selected Run At Once, the Start Time parameter is invalid. The task is performed immediately after the related settings are complete. Value:
l
Period
Description: Interval between periodic tasks. It has two enlistments: unit and duration.
Tasks can be executed in hours and days. The valid values for periods are as follows: Day (1 to 366), Hour (1 to 366 x 24)
Run Times
Description: This parameter indicates the times that a periodic task is executed.
Value: 0-65535
8.8.4 Parameter for Setting the Time of a Common Periodic Task

This section describes the time parameters in the New Task dialog box. When you set the time of a periodic task, you can refer to this section.
Issue 03 (2010-06-30)
8-53
Parameters
Parameter Time Setting Start Time Description Description: Time range of a periodic task. Settings Setting method: You can set this parameter with the following two methods:
l
Enter the time in Start Time. to select the Click date and time in the Date/Time Selection dialog box.
Period Setting
Period
Description: Interval of periodic tasks. The value consists of numerals and units.
Value:
l
The period can be represented in either of the following units: months, weeks, days, hours. The value range for period should be as follows: Month (1 12), Week (1 - 52), Day (1 - 366), Hour (1 - 366 x 24).
Run Times
Description: Number of times for executing periodic tasks
Value: 0 - 65535
NOTE 0 indicates that the number of times for executing periodic tasks is not restricted.
8.8.5 Parameter for Setting the Time of a Common One-Time Task

This section describes the time parameter in the New Task dialog box. When you modify the time of a one-time task, you can refer to this section.
8-54
Issue 03 (2010-06-30)
Parameters
Name Time Setting Description Description: Time range of a one-time task. Settings Setting method: You can set the time with the following two methods:
l l
Enter the time in Start Time. Click to select the date and time in the Date/Time Selection dialog box.
NOTE If the Run At Once check box is selected, the task is performed immediately after you set the parameters.
8.8.6 Parameters for Creating or Modifying a Data Collection Task

This section describes the parameters related to data collection tasks. You can refer to the description when creating or modifying data collection tasks.
Parameter OSS Value Range Select a parameter value from the dropdown list box. Description Indicates the name of an EMS.
Issue 03 (2010-06-30)
8-55
Parameter Data Type
Value Range Select an option from the drop-down list box. The options vary with the OSS version. For details, see the following description:
l
Description Indicates the type of the data that is collected from the EMS to the Nastar.
The data types corresponding to the OSS of the M2000 V200R006 are Config data and Any. The data types corresponding to the OSS of the M2000 V200R008 and M2000 V200R009 are Config data, Neighboring Measurement Task File, Frqlog Data, Performance data, Any, and Adaption Layer Data. Period for collecting data. For example, if you set the value to 5 Minutes, the Nastar collects performance data from the EMS at intervals of five minutes.
Period
Select a parameter value from the dropdown list box. The options are 5 Minutes, 15 Minutes, 30 Minutes, 60 Minutes, 24 Hours. You can select or not select the option. -
Specify the time range Start Time End Time Source directory Source file Destination directory
Indicates whether to collect data during the specified time period. Indicates the start time of the data collection period. Indicates the end time of the data collection period. Indicates the path for storing files in the EMS. Indicates the name of the file to be collected from the EMS. Indicates the path for storing files on the Nastar.
8-56
Issue 03 (2010-06-30)
Parameter The following files will be collected from *** And save to the server path Get files repeatedly Get files all over
Value Range -
Description Indicates that the system collects the Source directory/Source file from the selected OSS. *** indicates the name of the OSS.
Indicates that the collected file are stored in $DATAROOT/oss_folder name containing the start time of a period/Destination directory/ Source file on the Nastar server. Indicates that all the data in the M2000 is collected to the Nastar each time when a periodic data collection task is performed. Indicates whether to traverse the files in subdirectories of the configured source data path. If this option is not selected, it indicates that the files are not traversed.
You can select or not select the option. You can select or not select the option.
8.8.7 Parameters for Modifying the Task of Deleting History Data

This section describes the parameters related to the task of deleting history data. You can refer to the description when modifying the task of deleting history data.
Parameter Config Data Range An integer from 1 to 100 Unit: day Performanc e Data An integer from 1 to 100 Unit: day Description Indicates the storage duration of the configuration data files in the relevant path on the Nastar server. The configuration data is limited to the GSM, CDMA, UMTS, and TD-SCDMA networks. Indicates the storage duration of the performance data files in the relevant path on the Nastar server. The performance data is limited to the GSM network, and the data related to all the analysis tasks of the CDMA, UMTS, and TD-SCDMA networks. Indicates the storage duration of the neighbor measurement task files in the relevant file path on the Nastar server. The neighbor measurement task files are limited to the GSM network.
Neighbor Measureme nt Task File
An integer from 1 to 100 Unit: day
Issue 03 (2010-06-30)
8-57
Parameter Frqlog Data
Range An integer from 1 to 100 Unit: day
Description Indicates the storage duration of the files containing the uplink ARFCN scanning data in the relevant file path on the Nastar server. The uplink ARFCN scanning data is limited to the GSM network.
8.8.8 Parameters for Modifying the Task of Deleting GSM Performance Data
This section describes the parameters related to the task of deleting GSM performance data. You can refer to the description when modifying the task of deleting GSM performance data.
Parameter Data Reserve Days Value Range 7, 15, 30 Unit: day Description Assume that N refers to the preset Data Reserve Days. All the performance data N days ago is deleted from the database. The latest date when the data needs to be deleted is calculated according to the save time of the latest data among all the performance data in the database. For example, among all the performance data in the database, if the save time of the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the performance data saved before 2009-03-24 from the database.
8.8.9 Parameters for Modifying the Task of Deleting GSM Configuration Data
This section describes the parameters related to the task of deleting GSM configuration data. You can refer to the description when modifying the task of deleting GSM configuration data.
8-58
Issue 03 (2010-06-30)
Parameter Data Reserve Days Value Range 100, 150, 200 Unit: day Description Assume that N refers to the preset Data Reserve Days. All the configuration data N days ago is deleted from the database. The latest date when the data needs to be deleted is calculated according to the save time of the latest data among all the configuration data in the database. For example, among all the configuration data in the database, if the save time of the latest data is 2009-03-31, and Data Reserve Days is set to 100, the system deletes all the configuration data saved before 2008-12-22 from the database.
8.8.10 Parameters for Modifying the Task of Deleting the GSM Uplink ARFCN Scanning Data
This section describes the parameters related to the task of deleting the GSM uplink ARFCN scanning data. You can refer to the description when modifying the task of deleting the GSM uplink ARFCN scanning data.
Parameter Data Reserve Days Value Range 7, 15, 30 Unit: day Description Assume that N refers to the preset Data Reserve Days. The scanning data of all the uplink frequencies N days ago is deleted from the database. The latest date when the data needs to be deleted is calculated according to the save time of the latest data among the scanning data of all the uplink frequencies in the database. For example, among the scanning data of all the uplink frequencies in the database, if the save time of the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the scanning data of uplink frequencies saved before 2009-03-24 from the database.
8.8.11 Parameters for Modifying the Task of Deleting the GSM Measurement-Task File Data
This section describes the parameters related to the task of deleting the GSM measurement-task file data. You can refer to the description when modifying a task of deleting the GSM measurement-task file data.
Issue 03 (2010-06-30)
8-59
Parameter Data Reserve Days Value Range 7, 15, 30 Unit: day Description Assume that N refers to the preset Data Reserve Days. The data of all the measurement task files N days ago is deleted from the database. The latest date when the data needs to be deleted is calculated according to the save time of the latest data among the data of all the measurement task files in the database. For example, among the data of all the measurement task files in the database, if the save time of the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes the data of all the measurement task files saved before 2009-03-24 from the database.
8.8.12 Parameters for Modifying the Task of Deleting the GSM/ UMTS Neighboring-Cell Analysis Data
This section describes the parameters related to the task of deleting the GSM/UMTS neighboring-cell analysis data. You can refer to the description when modifying a task of deleting the GSM/UMTS neighboring-cell analysis data.
Parameter Data Reserve Days Value Range 7, 15, 30 Unit: day Description Assume that N refers to the preset Data Reserve Days. The data of all the measurement task files N days ago is deleted from the database. The latest date when the data needs to be deleted is calculated according to the save time of the latest data among the data of all the measurement task files in the database. For example, among the data of all the measurement task files in the database, if the save time of the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes the data of all the measurement task files saved before 2009-03-24 from the database.
8.8.13 Parameters for Modifying the Task of Deleting GSM VIP Analysis Data
This section describes the parameters related to the task of deleting GSM VIP analysis data. You can refer to the description when modifying the task of deleting GSM VIP analysis data.
8-60
Issue 03 (2010-06-30)
Parameter Data Reserve Days Value Range 7, 15, 30, 45, 60, 90, 180 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the VIP analysis data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the VIP analysis data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the VIP analysis data saved before 2009-03-24 from the database.
8.8.14 Parameters for Modifying the Task of Deleting GSM Cell Performance Analysis Data
This section describes the parameters related to the task of deleting GSM cell performance analysis data. You can refer to the description when modifying the task of deleting GSM cell performance analysis data.
Parameter Data Reserve Days Value Range 7, 15, 30 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the cell performance analysis data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the cell performance analysis data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the cell performance analysis data saved before 2009-03-24 from the database.
8.8.15 Parameters for Modifying the Task of Backing Up Data

This section describes the parameters related to the task of backing up data. You can refer to the description when modifying the task of backing up data.
Parameter Full Backup Time Range SUN, MON, TUE, WED, THU, FRI, SAT Description Indicates the date when data backup is performed.
Issue 03 (2010-06-30)
8-61
Parameter Backup Mode Backup Path
Range ALL, INC -
Description Indicates the mode of the data backup. Indicates the save path of backup files. By default, the path is /export/home/backup.
8.8.16 Parameters for Setting the Time of a Timing Task

This section describes the parameters of auto-suspend time and auto-resume time for timing tasks. Table 8-6 lists the parameters of auto-suspend time and auto-resume time for timing tasks. Table 8-6 Time parameters of a timing task Name Suspend Time Description Description: The system suspends an idle task and delay the time for performing this task. If the timing task is not in the idle state at the specified time, the suspension fails. Settings Setting method: You can set the value manually. Alternatively, you can click and select the time from the time select panel. The default time format is DD/ MM/YYYY HH:MM:SS.
l l l l l l
yyyy stands for the year. MM stands for the month. DD stands for the date. HH stands for the hour. MM stands for the minute. SS stands for the second.
Resume Time
Description: In the specified time, the system resumes a suspended task and then the task is in the idle status and wait to be dispatched. If the timing task is not in the idle state at the specified time, the suspension fails.
Setting method: For details on how to set the resume time, refer to the description of the Suspend Time parameter.
8-62
Issue 03 (2010-06-30)
9 GSM MR Analysis
9
About This Chapter
GSM MR Analysis
This section describes the GSM MR analysis. The GSM analysis supports the management of MR analysis tasks, check of the MR overview report, check of the cell MR results, and comparison between MR analysis results. In addition, the GSM MR analysis supports the direct display of radio link information, provides analysis of and solutions to problems, and helps you to fast locate the relevant problems on the radio network. 9.1 Basic Knowledge of GSM MR Analysis This section describes the basic knowledge of the GSM measurement report (MR) analysis, such as the GSM MR analysis functions, function application scenarios, TopN counters, and types of MR topic analysis. The basic knowledge helps you to perform the operations of GSM MR analysis. 9.2 Process of GSM MR Analysis This section describes the process of GSM MR analysis. 9.3 Managing GSM MR Analysis Tasks This section describes how to manage the GSM MR analysis tasks. You can create, modify, delete, suspend, and resume GSM MR analysis tasks. You can also view the status and execution progress of a task. 9.4 Querying the GSM MR Overview Report This section describes how to query the report of the GSM MR overview. You can query the relevant MR reports as required. An MR report includes the following information about the measurement cell: uplink and downlink levels, quality, timing advance (TA), and link balance. You can know the transceiver (TRX) or cell coverage, quality, and user distribution directly from the information in the report. The GSM MR reports are classified into GBSC reports, GSM cell group reports, TopN TRX reports, and GSM MR topic analysis reports. 9.5 Querying the MR Results of GSM Cells This section describes how to query the MR results of one or more GSM cells. If the MR results indicate that certain cells have multiple TopN or problematic TRXs, you can query the details about the TopN or problematic TRXs in the MR results. 9.6 Comparing the GSM MR Analysis Results This section describes how to compare the results of the GSM MR analysis. After the network optimization and device upgrade, you can compare two MR analysis results generated in two
9 GSM MR Analysis
time segments to check the differences between the values of the same counters in the two time segments. Thus, you can ascertain the detailed network performance differences in the two time segments and quickly evaluate the network optimization results. 9.7 Exporting the GSM MR Overview Reports This section describes how to export the GSM MR overview reports. You can export the GSM MR overview results as .csv or .xls files. 9.8 Reference for the GSM MR Analysis GUI This section describes the interface for GSM MR analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with GSM MR analysis functions.
9-2
Issue 03 (2010-06-30)
9 GSM MR Analysis
9.1 Basic Knowledge of GSM MR Analysis

This section describes the basic knowledge of the GSM measurement report (MR) analysis, such as the GSM MR analysis functions, function application scenarios, TopN counters, and types of MR topic analysis. The basic knowledge helps you to perform the operations of GSM MR analysis. 9.1.1 GSM MR Analysis Function This section describes the GSM MR analysis function. The GSM MR includes the following information about the measurement cell: uplink and downlink levels, uplink and downlink quality, timing advance (TA) distribution, and link balance information. You can know the TRX and cell coverage, quality, and user distribution directly from the information. The processing and direct displaying of the radio link information by the system can help you to solve many network problems. 9.1.2 TopN KPIs This section describes TopN KPIs related to the performance analysis. The KPIs include average quality of the received signals at uplink and downlink (full rate), average quality of the received signals at uplink and downlink (half rate), average levels received at uplink and downlink (full rate), average levels received at uplink and downlink (half rate), timing advance (TA) average distribution, and uplink and downlink balance. 9.1.3 GSM MR Topics This section describes GSM MR topic analysis types such as the analysis of the uplink interference, downlink interference, uplink poor coverage, downlink poor coverage, TRX poor coverage, remote coverage, link balance (uplink problem), link balance (downlink problem), and other problems. This also describes the solution to these problems.
9.1.1 GSM MR Analysis Function

This section describes the GSM MR analysis function. The GSM MR includes the following information about the measurement cell: uplink and downlink levels, uplink and downlink quality, timing advance (TA) distribution, and link balance information. You can know the TRX and cell coverage, quality, and user distribution directly from the information. The processing and direct displaying of the radio link information by the system can help you to solve many network problems.
MR Overview Report
An MR overview report contains the following information: an overview of the radio network performance, the distribution of TopN TRXs and problematic TRXs of each BSC and cell group, the TopN TRX for which the value of each radio link counter is the lowest, and the classification of the problematic TRXs based on topic analysis. You can view the overview report routinely generated to check the information about the TopN TRXs and problematic TRXs of each BSC, each cell group, and the entire network, and check the causes of the problematic TRXs. You can also check whether other problematic TRXs exist in the cell that the selected TopN TRX or problematic TRX belongs to and analyze these TRXs. The problem analysis topics are as follows:
l
Weak coverage analysis. TRXs with a low TA value, low level, and poor quality are listed.
Issue 03 (2010-06-30)
9 GSM MR Analysis
l l
Interfered cells. Cells with high level and poor quality are listed. Over coverage analysis. You can compare the TA values and the number of MRs to analyze the traffic distribution and check whether the cell is a over-coverage cell. Unbalance of the uplink and downlink. The cells whose uplink and downlink are obviously unbalanced are listed. Other problems. Problems occurring on the network, such as small number of MRs and null or low traffic of a TRX, 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 recommended solutions are provided to help you to quickly analyze and locate the quality problems that occur in the radio network.
MR Query
During network performance analysis and optimization, when abnormal cells (such as a cell whose call drop rate is high or the number of failed handover attempts is great) are found, you can query the MR information about these cells and the radio links of the TRXs in the cells through the Nastar performance analysis system. You can set the time and cell objects before the query. The MR information about these cells is displayed in the window of results. In addition, you can use the Nastar performance analysis system to further query the TRX information. Through the comparison and query of different TRXs in cells, you can locate more complicated network problems effectively. The query results are displayed in a table or a bar chart to provide the radio link quality and user distribution of each TRX.
MR Comparison Analysis
After network upgrade and optimization such as the adjustment of antennas and modification of parameter settings, you can compare the quality and coverage of the entire network, BSC, cell group, or cell with the quality and coverage obtained before the network upgrade and optimization, or you can compare the quality and coverage of different time segments during the network upgrade and optimization. The comparison results are displayed in a table or a bar chart.
9.1.2 TopN KPIs

This section describes TopN KPIs related to the performance analysis. The KPIs include average quality of the received signals at uplink and downlink (full rate), average quality of the received signals at uplink and downlink (half rate), average levels received at uplink and downlink (full rate), average levels received at uplink and downlink (half rate), timing advance (TA) average distribution, and uplink and downlink balance.
Received Signal Quality

The quality of received signals is divided into seven levels from level 1 to level 7 according to the bit error rate. Each level corresponds to different bit error rates. Higher level indicates the poorer quality of the received signals. Level 1 indicates the minimum bit error rate and the best quality of the received signals. Level 7 indicates the maximum bit error rate and the poorest quality of the received signal.
9 GSM MR Analysis
Table 9-1 describes the relation between the quality levels of the received signals and the bit error rate. Table 9-1 Relation between the quality levels of the received signals and bit error rate. Quality Level of Received Signals 1 2 3 4 5 6 7 Bit Error Rate (%)
[0.2, 0.4) [0.4, 0.8) [0.8, 1.6) [1.6, 3.2) [3.2, 6.4) [6.4, 12.8) 12.8
Received Level
The received signal level is divided into seven levels according to level values. Each level corresponds to different ranges of received levels. Higher level indicates the higher received level. Level 1 indicates the lowest received level and level 7 indicates the highest received level. Table 9-2 describes the relation between the received levels and the levels. Table 9-2 Relation between the received levels and levels Level of Received Level 1 2 3 4 5 6 7 Received Level (dBm)
(-100, -95] (-95, -90] (-90, -85] (-85, -80] (-80, -75] (-75, -70] >-70
Issue 03 (2010-06-30)
9-5
9 GSM MR Analysis
TA
The TA is a counter used to describe the distance with time and is used for the coverage analysis. The header of the MR sent from a mobile station (MS) to a BTS is carried with the measurement delay of the MS. The BTS must monitor the time when a call reaches and send an instruction to the MS every 480 ms on the downlink channel to specify the advanced sending time for the MS. This time is termed TA, ranging from 1 to 63.
Uplink and Downlink Balance

The MR received by the BSC contains the uplink receive level and downlink receive level. The result (in dB), which is obtained by subtracting the uplink receive level and the sensitivity difference between the MS and the BTS from the downlink receive level, is classified into 11 levels from level 1 to level 11. Table 9-3 describes the relations between levels and values of the Uplink and Downlink Balance Level counter. Table 9-3 Description of link balance levels Uplink and Downlink Balance Level 1 2 3 4 5 6 7 8 9 10 11 Downlink Receive Level- Uplink Receive Level- 6 (dB)
-15 -14, -13, -12, -11 -10, -9, -8 -7, -6, -5 -4, -3, -2 -1, 0, 1 2, 3, 4 5, 6, 7 8, 9, 10 11, 12, 13, 14 15
NOTE
The number 6 in the formula "Downlink receive level - Uplink receive level - 6 (dB)" refers to the sensitivity difference between the MS and the BTS.
If the statistical result indicates that the uplink and downlink are mostly in balance level 1, the downlink loss is excessively high or the downlink transmit power is excessively low. If the statistical result indicates that the uplink and downlink are mostly in balance level 11, the uplink loss is excessively high or the downlink transmit power is excessively low. According to the statistical result, you can locate the faults that occur on the transmit and receive channels, such as the TRX or antenna feeder.
9 GSM MR Analysis
9.1.3 GSM MR Topics

This section describes GSM MR topic analysis types such as the analysis of the uplink interference, downlink interference, uplink poor coverage, downlink poor coverage, TRX poor coverage, remote coverage, link balance (uplink problem), link balance (downlink problem), and other problems. This also describes the solution to these problems. The GSM MR topics are classified into nine categories. The system provides different operation suggestions for each category. For details, see Table 9-4. Table 9-4 Topic categories and relevant operation suggestions Topic Uplink interferen ce Description The uplink-interference results in the high level and poor quality. Suggestion Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, enable the function of uplink-interference analysis to analyze the interference according to the uplink frequency distribution that is measured by TRXs. Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, use an MS to search for frequencies within the cell coverage where the TRX is transmitted, and observe the downlink frequency status. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX. Move an MS to a place near the TRX to measure the actual power of the TRX. Check whether the downlink level of the TRX is low. If the downlink level of the TRX is low, check the cable connections between the combiner and the TRX, and connections in the antenna system. Then, check the level at the TRX entry and output entry of the combiner by using the power meter to locate the fault.
l
Downlink interferen ce
The downlink interference results in the high level and poor quality.
Weak uplink coverage
The loss of the uplink TRX is excessive.
Weak downlink coverage
The loss of the downlink TRX is excessive.
Weak TRX coverage
The loss of the TRX is excessive. The TRX coverage is remote, which causes the low quality of the uplink. The TRX coverage is remote, which causes the low quality of the downlink.
Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX. Check whether the actual azimuth of the antenna is the same as the antenna azimuth in design. If the antenna is omni-directional, check whether the coverage is excessively large.
Issue 03 (2010-06-30)
9-7
9 GSM MR Analysis
Topic Remote coverage
Description
l l
Suggestion
l
Remote TRX coverage The TRX coverage is remote, which causes the low quality of the uplink and downlink. Uplink and downlink are not balanced. The downlink is stronger. The excessive loss of the uplink results in the low received level and poor signal quality of the BTS.
Check whether there are missing neighboring cells and cells whose coverage is remote. Check whether the actual azimuth of the antenna is the same as the antenna azimuth in design. If the antenna is omni-directional, check whether the coverage is excessively large. Check whether the coverage complies with the planning and whether the output power of the TRX and CDU is normal. You can adjust the uplink received threshold and the level of the downlink static power to balance the uplink and downlink. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX. Check whether the coverage complies with the planning and whether the output power of the TRX and CDU is normal. You can adjust the threshold of the receive power and the level of the static power on the uplink to balance the uplink and downlink. Move an MS to a place near the TRX to check the actual power of the TRX and check whether the downlink level of the TRX is low. If the downlink level of the TRX is low, check the cable connections between the combiner and the TRX and connections in the antenna system, and check the level at the TRX entry and output entry of the combiner by using the power meter to locate the fault.
Link balance (uplink)
Link balance (downlink )
Uplink and downlink are not balanced, and the uplink is stronger. The excessive loss of the downlink results in the low received level and poor signal quality of the MS.
Others
The performance of the TRX receive level is abnormal. The number of MRs is excessively small.
Check whether the hardware or software of the TRX is faulty and whether only a small number of MRs is reported. In addition, analyze whether the generation of a small number of MRs is proper.
9.2 Process of GSM MR Analysis

This section describes the process of GSM MR analysis. Figure 9-1 shows the general process of GSM MR analysis.
9-8
Issue 03 (2010-06-30)
9 GSM MR Analysis
Figure 9-1 Process of GSM MR analysis
Start
Set an E2E task
Set an MR analysis task
Query the GSM MR overview report
Query the MR results of the GSM cells
Compare the GSM MR analysis results
End
Table 9-5 describes the process of GSM MR analysis. Table 9-5 Process of GSM MR analysis Seria l No. 1 Procedure Querying NE data information Create an endto-end task corresponding to a neighboring cell analysis task Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the MR analysis is imported to the database. You can choose Mainentance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a neighboring cell analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE to start the measurement task for all objects.
NOTE Starting the measurement task for all objects needs to be performed only once. If this operation has been performed, you do not need to create an end-to-end task corresponding to a neighboring cell task again.
Issue 03 (2010-06-30)
9-9
9 GSM MR Analysis
Seria l No. 3
Procedure Create a performance data collecting task Create a performance data importing task Create an MR analysis task
Description You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a performance data collecting task. After the task is created, the Nastar periodically obtains the required performance data from M2000, and saves the data as files on the Nastar server. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a performance data importing task. After the task is created, the Nastar periodically imports the performance data files saved on the Nastar server to the database. You can create an MR analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required performance data from the Nastar database, and then generates an analysis report through the analysis. You can view the analysis results of the MR analysis tasks that are successfully performed and compare the results generated in different time segments.
Query the GSM MR overview report Query the MR results of the GSM cells Compare the GSM MR analysis results
9.3 Managing GSM MR Analysis Tasks

This section describes how to manage the GSM MR analysis tasks. You can create, modify, delete, suspend, and resume GSM MR analysis tasks. You can also view the status and execution progress of a task. 9.3.1 Creating GSM E2E Tasks This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 9.3.2 Creating a GSM MR Analysis Task This section describes how to create a GSM MR analysis task. By performing MR analysis tasks, the Nastar performance analysis system analyzes the relevant data in the database at the preset time. By checking the analysis results, you can ascertain the network status and fast locate and solve the network faults.
9 GSM MR Analysis
9.3.3 Modifying a GSM MR Analysis Task You can modify the attributes of a GSM MR analysis task to meet the new requirement. 9.3.4 Checking a GSM MR Analysis Task This section describes how to check a GSM MR analysis task. You can check the attributes, execution progress, and execution results of a GSM MR analysis task.
9.3.1 Creating GSM E2E Tasks

This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result.
Prerequisite
l l l
You have logged in to the Nastar client. The OSS and NEs related to the analysis task are created. The configuration data related to the analysis task is imported to the Nastar database.
Context
TIP
After creating an E2E task by following the procedures in this section, you are advised to observe the E2E task for five minutes to check whether the task is executed normally. If Status of the E2E task is still Running after five minutes, it indicates that the E2E task is executed normally. If Status of the E2E task is Complete or Failed after five minutes, it indicates that the E2E task fails to be executed. Note that the Nastar monitors the tasks by checking the task status on the M2000 at an interval of five minutes.
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Perform the following operations as required: If You Want to ... Add a GSM neighboring cell measurement task Add a GSM uplink frequency scan task Add a GSM VIP analysis task Add a GSM/UMTS neighboring cell data task Add a GSM cell performance data task Then ... Perform Step 4. Perform Step 5. Perform Step 6. Perform Step 7. Perform Step 8.
Step 4 Perform the following operations to add a GSM neighboring cell measurement task: 1.
Issue 03 (2010-06-30)
Set the basic information about the task.

9 GSM MR Analysis
a. b. c. 2. 3.
In the Task Name field, enter the name of the neighboring cell measurement task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Neighboring Cell Data Task.
Click Next. On the Measure Task tab page, set the time, objects, and ARFCNs of the neighboring cell measurement task. Set Begin Time, Persist Time (Minute), Period, and Measure Step.
l l l l
Begin Time indicates the start time of the measurement task. Persist Time (Minute) indicates the total duration of the measurement task execution. Period indicates the interval at which each group of ARFCNs is measured. Measure Step indicates the number of ARFCNs in a group.
4.
From the object navigation tree, select the cell related to the task. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
CAUTION
It is recommended that the number of test cells under one BSC does not exceed 200. If the recommended value is exceeded, certain cells may fail to report complete data. The upper threshold is 400. 5. Optional: Click Frequency Analysis to traverse the three level neighboring cells of the selected cell. The Nastar then analyzes the BCCH frequencies of the traversed neighboring cells and highlights these BCCH frequencies in the frequency selection area in gray to provide reference for measurement frequency analysis. Traversing of the three level neighboring cells indicates that the Nastar searches for the neighboring cells of the selected cell (neighboring cell A), the neighboring cells of neighboring cells A (neighboring cell B), and the neighboring cells of neighboring cells B (neighboring cell C). All traversed neighboring cells A, B, and C are neighboring cells obtained through the traversing of the three level neighboring cells. 6. Set the ARFCNs.
NOTE
Before setting the ARFCNs, set Measure Step. The ARFCNs that you select are organized into groups according to Measure Step that you set. For example, if Measure Step is set to 2 and the ARFCNs 59, 60, and 61 are selected, the ARFCNs are organized into two groups. One group consists of ARFCNs 59 and 60, and the other group consists of ARFCN 61. In a measurement period, the M2000 measures these ARFCN groups in turn. You can also modify the value of Measure Step to reorganize the ARFCNs after setting the ARFCNs.
7.
Optional: Set the soft parameters of the neighboring cell measurement task. a. b. Click the Soft Parameter tab. Select Soft Parameter Setting.
9-12
9 GSM MR Analysis
If you select this option, the soft parameters that you set are valid for this measurement task. c. Set the thresholds of the soft parameters as required. For the detailed description of the soft parameters, see 9.8.2 Parameters for Creating GSM E2E Tasks. 8. Click Finish. The added neighboring cell measurement task is displayed in the task list. Set the basic information about the task. a. b. c. 2. 3. In the Task Name field, enter the name of the uplink frequency scan task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Uplink Interference Analysis Data Task.
Step 5 Perform the following operations to create a GSM uplink frequency scan task: 1.
Click Next to set Time (Minute), that is, the total duration of the measurement task execution. In the Cell Parameter Setting area, select the cell and frequency band to be tested. a. b. From the Frequency Segment drop-down list box, select the frequency band that the cell uses. From the object navigation tree, select the cell related to the task. The system enables you to search for the objects in the navigation tree. You can rightclick any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
4.
In the Frequency Parameter Setting area, select the ARFCNs to be scanned. a. b. From the Frequency Type drop-down list, select the required frequency type. When Frequency Type is set to User Defined in The Frequency Segment, you need to select ARFCNs from the ARFCN list. Selected ARFCNs are displayed in gray.
5.
Click Finish. The added uplink frequency scan task is displayed in the task list. Set the basic information about the task. a. b. c. In the Task Name field, enter the name of the VIP analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM VIP Analysis Data Task.
Step 6 Perform the following operations to add a GSM VIP analysis task: 1.
2.
Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive.
Issue 03 (2010-06-30)
9-13
9 GSM MR Analysis
You can select Up or Down in the Direction area to determine the direction of the search. 3. Click Next. From the VIP group list, select one or multiple VIP groups and select Report Raw Data as required. If you select to report raw data, the original call record data is collected when the VIP KPI overview information is provided. Click Finish. The added VIP analysis task is displayed in the task list. Set the basic information about the task. a. b. c. 2. In the Task Name field, enter the name of the GSM/UMTS neighboring cell data task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM/UMTS Neighboring Cell Data Task.
4.
Step 7 Perform the following operations to add a GSM/UMTS neighboring cell data task: 1.
Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
3.
Click Finish. The added GSM/UMTS neighboring cell data task is displayed in the task list. Set the basic information about the task. a. b. c. In the Task Name field, enter the name of the cell performance analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Cell Performance Analysis Task.
Step 8 Perform the following operations to add a GSM cell performance analysis task: 1.
2.
3. 4.
Click Next and then set the exception value for each KPI in the exception value setting list. Click Finish. The added cell performance analysis task is displayed in the task list.
----End
Postrequisite
To view the attributes of a created E2E task, perform the following operations:
9 GSM MR Analysis
1. 2.
Select a task from the task list in the right pane of the E2E Task Management window, and then click Attribute. The Attribute dialog box is displayed. View the related parameters.
To delete an unnecessary E2E task, perform the following operations: 1. 2. Select a task from the E2E Task Management window, and then click Delete. In the displayed Confirm dialog box, click OK.
NOTE
The tasks in the Running state cannot be deleted.
The attributes of a created E2E task cannot be modified. If you want to change certain parameter values, you need to delete the original task and then create another one. To update the task list, click Refresh in the lower-right corner of the E2E Task Management window.
9.3.2 Creating a GSM MR Analysis Task

This section describes how to create a GSM MR analysis task. By performing MR analysis tasks, the Nastar performance analysis system analyzes the relevant data in the database at the preset time. By checking the analysis results, you can ascertain the network status and fast locate and solve the network faults.
Prerequisite
l l
You have logged in to the Nastar client. The import task is created and the data required for data analysis is imported in the Nastar database.
Context
l
An MR analysis task can be performed once or periodically. You can set the execution period of a periodical task to days. The system supports a maximum of 50 tasks of this type.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, Execution Type, and Note. Step 3 Click Next. Step 4 Set Task Configuration and Time Setting for Cycle Task Data/Time Setting for Once Task Data. If Once Task is selected in the previous step, you need to set only Data Time Scope. Step 5 Click Next. Step 6 Select one or multiple objects in the object navigation tree on the NE Object Selection tab page.
l
Choose BSC or Cell Group above the navigation tree to display the objects in the navigation tree as required.
Issue 03 (2010-06-30)
9 GSM MR Analysis
l
The system enables you to search for the objects in the navigation tree. You can click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to define the search area.
Step 7 Set MR-related parameters on the Parameter Setting tab page. Step 8 Click Complete. ----End
Postrequisite
l
Deleting a task You can delete an MR analysis task that is not required so that you can save system resources.
NOTE
1.
Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Select a task from the task list in the upper-right pane, and then click Click Yes in the displayed Confirm dialog box.
Suspending a task To delay the task execution, you can suspend an MR analysis task that is in the Idle state. After this operation, the MR analysis task is in the suspended state.
NOTE
The system can schedule only the MR analysis tasks that are not suspended.
1.
Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
Select a task from the task list in the upper-right pane, and then click Only the tasks whose Status is Idle can be suspended. Otherwise, the unavailable.
. button is
Resuming a task You can resume a suspended MR analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the MR analysis tasks that are in the idle state can be scheduled by the system.
1.
Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window.
9-16
9 GSM MR Analysis
If you choose Subject Function, the task list on the right displays all the performance analysis tasks. 2. Select a task from the task list in the upper-right pane, and then click .
The task can be performed only when its Status is Suspend. If the task is not in the suspended state, the button is unavailable.
9.3.3 Modifying a GSM MR Analysis Task

You can modify the attributes of a GSM MR analysis task to meet the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. A GSM MR analysis task is created.
Context
You are not allowed to modify the parameters of the task whose Status is Running or Complete. You can only view the information about the task.
Procedure
Step 1 Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the parameters, see 9.8.3 Parameters for Creating and Modifying GSM MR Analysis Tasks. For periodical tasks, you can modify the Note parameter in the basic information, the Begin Date, Cycle, Execution Times, and Time parameters in the time information, the information about the navigation tree of objects, and the Parameter Setting for Exceptional TRXs in the Case of MR Topic Analysis parameter. For the tasks that can be performed only once, you can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the navigation tree of objects, and the Parameter Setting for Exceptional TRXs in the Case of MR Topic Analysis parameter.
Step 4 Click Complete. ----End
9.3.4 Checking a GSM MR Analysis Task

This section describes how to check a GSM MR analysis task. You can check the attributes, execution progress, and execution results of a GSM MR analysis task.
9 GSM MR Analysis
Prerequisite
l l
You have logged in to the Nastar client. A GSM MR analysis task is created.
Procedure
Step 1 Click the GSM MR Analysis Task node from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If you need to ... Check the attributes of an MR analysis task. Then ... Select a task from the task list in the upper-right pane. Double-click the task or click .
You can view the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 9.3.3 Modifying a GSM MR Analysis Task. Check the execution progress of a task. Select a task from the task list in the upper-right pane. Then, you can view the execution progress of the task in the Progress column. Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can check the results of the performed tasks in the result list in the lower-right pane. You can check the GSM MR overview report and GSM cell MR results, and compare the GSM MR analysis results.
NOTE In the result list, if the result information about tasks that fail to be executed at a certain period already exists in the database, you can right-click the results, and then choose Analyze Result Again from the shortcut menu to analyze the results of this period again. Only the results of tasks that fail to be executed are analyzed again.
Check the task execution results.
----End
9-18
Issue 03 (2010-06-30)
9 GSM MR Analysis
Postrequisite
l
In the drop-down list boxes above the task list, you can set the filter conditions to filter the tasks by the task status, task execution type, and task type. You can also type the keyword of a task name in the text box. Then, the system searches for the tasks by the keyword. , you can restore the preset filtering conditions to the initial state, that is, By clicking all the task information is displayed.
The system enables you to search for task information. You can click any line in the task information list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search conditions, in the dialog box. Then, the system searches for the task information that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to define the search area.
9.4 Querying the GSM MR Overview Report

This section describes how to query the report of the GSM MR overview. You can query the relevant MR reports as required. An MR report includes the following information about the measurement cell: uplink and downlink levels, quality, timing advance (TA), and link balance. You can know the transceiver (TRX) or cell coverage, quality, and user distribution directly from the information in the report. The GSM MR reports are classified into GBSC reports, GSM cell group reports, TopN TRX reports, and GSM MR topic analysis reports. 9.4.1 Querying the GBSC Report This section describes how to query a GBSC report. You can query the distribution of TopN and problematic TRXs on the entire network and the number of TRXs under each GBSC. You can also query the TopN and problematic TRXs in each GBSC according to a certain radio link counter or analyze the problematic TRXs according to a topic. 9.4.2 Querying the GSM Cell Group Report This section describes how to query the GSM cell group report. You can query the distribution of TopN and problematic TRXs on the entire network and the calculation result of all the TRXs under each cell group. You can also query the TopN and problematic TRXs in each cell group according to certain radio link counter or analyze the problematic TRXs according to a topic. 9.4.3 Querying a GSM TopN TRX Report This section describes how to query a GSM TopN TRX report. You can query the information about N TRXs (currently, N = 10) whose performance is the poorest as indicated by the selected counter. 9.4.4 Querying a GSM MR Topic Analysis Report This section describes how to query a GSM MR topic analysis report. You can query the information about all the problematic TRXs that meet the requirements of certain MR topic.
9.4.1 Querying the GBSC Report

This section describes how to query a GBSC report. You can query the distribution of TopN and problematic TRXs on the entire network and the number of TRXs under each GBSC. You can also query the TopN and problematic TRXs in each GBSC according to a certain radio link counter or analyze the problematic TRXs according to a topic.
Issue 03 (2010-06-30)
9-19
9 GSM MR Analysis
Prerequisite
Procedure
Step 1 Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose MR Overview Report. The MR Overview Report window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Perform the following operations as required: Purpose Operation
Querying relevant information about the Choose BSC Overview Report from the TopN and problematic TRXs on the entire navigation tree in the MR Overview Report network window.
NOTE
l In Area (2), the system displays the number of
TopN and problematic TRXs in each GBSC on the entire network. In Area (3), the system displays the calculation result of all the TRXs in each GBSC. In Area (4), the system displays the information about the selected item in Area (3) on a bar chart. For the specific rules of dividing areas, see 9.8.1 Interface Description: GSM MR Analysis.
l You can double-click the bar chart in Area (4) to
zoom in the chart, and then double-click the chart again to restore the chart to the original size.
9-20
Issue 03 (2010-06-30)
9 GSM MR Analysis
Purpose Querying information about the TopN and problematic TRXs in a GBSC and analyzing the problematic TRXs according to a topic
Operation Choose BSC Overview Report > *** > *** from the navigation tree in the MR Overview Report window. The first *** indicates the GBSC name. A GBSC is named in the following format: NE name:NE ID. For example, BSC1:10. The second *** indicates the counter name or topic name. A counter is named in the following format: counter name(number of problematic TRXs). A topic is named in the following format: topic name(number of problematic TRXs). For example, uplink interference(10).
NOTE
l If the number of TopN or problematic TRXs for a
counter or topic is greater than that in the previous period, an upward arrow next to the corresponding counter name or topic name in Area (1) is found and the number of new TopN or problematic TRXs is displayed. The information about the new TopN or problematic TRXs is displayed in Area (2) and is highlighted in yellow.
l If you select a counter node, Area (2) sorts all the
TRXs in the selected GBSC according to the counter. If you select a TopN TRX in Area (2), the first line in Area (3) displays the calculation result of all the TRXs in the cell that the selected TopN TRX belongs to, and the other lines in Area (3) displays the information about each TRX in the cell. In Area (4), the system displays the information about the TRX selected in Area (3) on a bar chart.
l If you select a topic node, Area (2) lists all the
problematic TRXs that meets the requirements of the selected topic. If you select a problematic TRX in Area (2), the first line in Area (3) displays the calculation result of all the TRXs in the cell that the selected problematic TRX belongs to, and the other lines in Area (3) displays the information about each TRX in the cell. In Area (4), the system displays the information about the TRX selected in Area (3) on a bar chart.
zoom in the chart, and then double-click the chart again to restore the chart to the original size. For the specific rules of dividing areas, see 9.8.1 Interface Description: GSM MR Analysis.
Issue 03 (2010-06-30)
9-21
9 GSM MR Analysis
For details about the relevant parameters, see 9.8.4 Parameters for Querying GBSC Reports. ----End
Postrequisite
l
The system enables you to export the query results. Right-click the query result list and choose Save As. After setting the save path and filename, click Save. Then, the query results are saved as a CSV or XLS file. To query chart properties, and save, print, and resize the chart in the chart area, perform the following operations:
Right-click the chart, and then choose Property from the shortcut menu. In the displayed Chart Property dialog box, set the coordinate axes of and basic information about the chart. Right-click the chart, and then choose Save as from the shortcut menu. In the displayed Save dialog box, set the save path and file name, and then click Save to save the queried chart as a file on the local PC. Right-click the chart, and then choose Print from the shortcut menu. In the displayed Page Setup dialog box, set print properties, and then click OK. If the chart is not clear due to an excessive number of dots, right-click the chart, and then choose Zoom In > ***, Zoom Out > ***, or Auto Range > *** to adjust the size of the chart. Here, *** indicates a submenu item. It can be Both Axes, Horizontal Axis, or Vertical Axis, which indicates that you can adjust both axes, the horizontal axis, or the vertical axis, respectively.
The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Then, type the keywords, that is, the search conditions, in the dialog box. The system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to define the search area.
9.4.2 Querying the GSM Cell Group Report

This section describes how to query the GSM cell group report. You can query the distribution of TopN and problematic TRXs on the entire network and the calculation result of all the TRXs under each cell group. You can also query the TopN and problematic TRXs in each cell group according to certain radio link counter or analyze the problematic TRXs according to a topic.
Prerequisite
Procedure
Step 1 Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
9 GSM MR Analysis
Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose MR Overview Report. The MR Overview Report window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Perform the following operations as required: Purpose Operation
Querying relevant information about the Choose Cell Group Overview Report from the TopN and problematic TRXs on the entire navigation tree in the MR Overview Report network window.
NOTE
l In Area (2), the system displays the number of
TopN and problematic TRXs in each cell group on the entire network. In Area (3), the system displays the calculation result of all the TRXs in each cell group. In Area (4), the system displays the information about the selected item in Area (3) on a bar chart. For the specific rules of dividing areas, see 9.8.1 Interface Description: GSM MR Analysis.
zoom in the chart, and then double-click the chart again to restore the chart to the original size.
Issue 03 (2010-06-30)
9-23
9 GSM MR Analysis
Purpose
Operation
Querying information about the TopN Choose Cell Group Overview Report > *** > and problematic TRXs in a cell group and *** from the navigation tree in the MR analyzing the problematic TRXs Overview Report window. according to a topic The first *** indicates the name of a cell group. A cell group is named in the following format: group name:group number. For example, Cell1:10. The second *** indicates the name of a counter or topic. A counter is named in the following format: counter name(number of problematic TRXs). A topic is named in the following format: topic name(number of problematic TRXs). For example, uplink interference(10).
NOTE
l If the number of TopN or problematic TRXs for a
counter or topic is greater than that in the previous period, an upward arrow next to the corresponding counter name or topic name in Area (1) is found and the number of new TopN or problematic TRXs is displayed. The information about the new TopN or problematic TRXs is displayed in Area (2) and is highlighted in yellow.
l If you select a counter node, Area (2) sorts all the
TRXs in the selected cell group according to the counter. If you select a TopN TRX in Area (2), the first line in Area (3) displays the calculation result of all the TRXs in the cell that the selected TopN TRX belongs to, and the other lines in Area (3) displays the information about each TRX in the cell. In Area (4), the system displays the information about the TRX selected in Area (3) on a bar chart.
l If you select a topic node, Area (2) lists all the
problematic TRXs that meet the requirements of the selected topic. If you select a problematic TRX in Area (2), the first line in Area (3) displays the calculation result of all the TRXs in the cell that the selected problematic TRX belongs to, and the other lines in Area (3) displays the information about each TRX in the cell. In Area (4), the system displays the information about the TRX selected in Area (3) on a bar chart.
zoom in the chart, and then double-click the chart again to restore the chart to the original size. For the specific rules of dividing areas, see 9.8.1 Interface Description: GSM MR Analysis.
9-24
Issue 03 (2010-06-30)
9 GSM MR Analysis
For details about the relevant parameters, see 9.8.5 Parameters for Querying the GSM Cell Group Reports. ----End
Postrequisite
l
9.4.3 Querying a GSM TopN TRX Report

This section describes how to query a GSM TopN TRX report. You can query the information about N TRXs (currently, N = 10) whose performance is the poorest as indicated by the selected counter.
Prerequisite
Procedure
Step 1 Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane.
9 GSM MR Analysis
You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose MR Overview Report. The MR Overview Report window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Choose TopN > *** from the navigation tree in the MR Overview Report window.
l
Here, *** indicates a counter name. For example, Full-Rate Uplink Receive Level Grade. If the number of TopN TRXs for a TopN counter is greater than that in the previous period, an upward arrow next to the corresponding TopN counter name in Area (1) is found and the number of increased TopN TRXs is displayed. The information about the increased TopN TRXs is displayed in Area (2) and is highlighted in yellow.
Area (2) lists 10 TRXs whose performance is the poorest as indicated by the selected counter. If you select a TopN TRX in Area (2), the first line in Area (3) displays the calculation result of all the TRXs in the cell which the selected TopN TRX belongs to, and the other lines in Area (3) displays the information about all the TRXs in the cell. In Area (4), the system displays the information about the TRX selected in Area (3) on a bar chart. For the specific rules of dividing areas, see 9.8.1 Interface Description: GSM MR Analysis.
You can double-click the bar chart in Area (4) to zoom in the chart, and then double-click the chart again to restore the chart to the original size. For details about the relevant parameters, see 9.8.6 Parameters for Querying the GSM TopN TRX Reports.
----End
Postrequisite
l
9-26
Issue 03 (2010-06-30)

l
9 GSM MR Analysis
9.4.4 Querying a GSM MR Topic Analysis Report

This section describes how to query a GSM MR topic analysis report. You can query the information about all the problematic TRXs that meet the requirements of certain MR topic.
Prerequisite
Procedure
Step 1 Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose MR Overview Report. The MR Overview Report window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Choose Topic > *** from the navigation tree in the MR Overview Report window.
l l
Here, *** indicates the name of an MR topic, for example, Uplink Weak Coverage. If the number of problematic TRXs for a topic is greater than that in the previous period, an upward arrow next to the corresponding topic name in Area (1) is found and the number of increased problematic TRXs is displayed. The information about the increased problematic TRXs is displayed in Area (2) and is highlighted in yellow.
Area (2) lists the problematic TRXs meeting the requirements of the selected topic. If you select a problematic TRX in Area (2), the first line in Area (3) displays the calculation result of all the TRXs in the cell which the selected problematic TRX belongs to, and the other lines in Area (3) displays the information about each TRX in the cell. In Area (4), the system displays the information about the TRX selected in Area (3) on a bar chart. For the specific rules of dividing areas, see 9.8.1 Interface Description: GSM MR Analysis.
You can double-click the bar chart in Area (4) to zoom in the chart, and then double-click the chart again to restore the chart to the original size. For details about the relevant parameters, see 9.8.7 Parameters for Querying the GSM MR Topic Analysis Reports.
----End
9 GSM MR Analysis
Postrequisite
l
9.5 Querying the MR Results of GSM Cells

This section describes how to query the MR results of one or more GSM cells. If the MR results indicate that certain cells have multiple TopN or problematic TRXs, you can query the details about the TopN or problematic TRXs in the MR results.
Prerequisite
Procedure
Step 1 Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose MR Query. The Cell Object Selection dialog box is displayed.
9 GSM MR Analysis
This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select one or more cells to be queried. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to define the search area. Step 5 Click OK. The MR Query Results dialog box is displayed.
l
In Area (8), the system displays the calculation result of all the TRXs in each cell. If you select an item in Area (8), the system displays the information about each TRX in the cell that the selected item belongs to in Area (9). In Area (10), the system displays the information about the TRX selected in Area (9) on a bar chart. For details about the rules for dividing areas, see 9.8.1 Interface Description: GSM MR Analysis.
You can double-click the bar chart in Area (10) to zoom in the chart, and then double-click the chart again to restore the chart to the original size. For details about the parameters, see 9.8.8 Parameters for Querying the MR Analysis Results of GSM Cells.
----End
Postrequisite
l
The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Then, type the keywords, that is, the search conditions, in the dialog box. The system searches for the query result that meets the search condition.
Issue 03 (2010-06-30)
9 GSM MR Analysis
9.6 Comparing the GSM MR Analysis Results

This section describes how to compare the results of the GSM MR analysis. After the network optimization and device upgrade, you can compare two MR analysis results generated in two time segments to check the differences between the values of the same counters in the two time segments. Thus, you can ascertain the detailed network performance differences in the two time segments and quickly evaluate the network optimization results.
Prerequisite
Procedure
Step 1 Choose GSM MR Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of a selected task in the lower-right pane. Step 3 Right-click two results and choose MR Comparison Analysis. The Object Selection dialog box is displayed. This operation can be performed only when the Result Status of the task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select one or more objects.
l
If the current task is performed to analyze the cells under a BSC, you can select All, BSC, or Cell above the navigation tree to sort the objects. If the current task is performed to analyze the cells in a cell group, you can select All, Cell Group, or Cell above the navigation tree. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to define the search area.
Step 5 Click OK. The MR Comparison Analysis dialog box is displayed.

l
In Area (14), the system displays the differences between the values of the same counters of each object in two time segments. In Area (15), the system displays the information that is selected in Area (14) on a bar chart.
For the specific rules of dividing areas, see 9.8.1 Interface Description: GSM MR Analysis. The system can display the compared counter values that indicate performance trends in the table in different colors. Red indicates that the performance deteriorates; green
9-30
9 GSM MR Analysis
indicates that the performance improves; gray indicates that no query result exists or that the performance does not change.
l
You can double-click the bar chart in Area (15) to zoom in the chart, and then double-click the chart again to restore the chart to the original size. For details about the parameters, see 9.8.9 Parameters for Comparing GSM MR Analysis Results.
----End
Postrequisite
l
The system enables you to export the query results. Right-click the query result list and choose Save As.... After setting the save path and filename, click Save. Then, the query results are saved as a CSV or XLS file. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Then, type the keywords, that is, the search conditions, in the dialog box. The system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to define the search area.
9.7 Exporting the GSM MR Overview Reports

This section describes how to export the GSM MR overview reports. You can export the GSM MR overview results as .csv or .xls files.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the GSM MR overview reports.
Procedure
l Perform the following operations as required: If You Want to ... Then ...
Export the MR analysis results of all 1. Click in the GSM MR Overview the cells Report window. The Save As dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently.
Issue 03 (2010-06-30)
9-31
9 GSM MR Analysis
If You Want to ...
Then ...
Export the MR analysis results of all 1. Click in the GSM MR Overview the carriers Report window. The Save As dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. ----End
9.8 Reference for the GSM MR Analysis GUI

This section describes the interface for GSM MR analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with GSM MR analysis functions. 9.8.1 Interface Description: GSM MR Analysis This section describes the interfaces for GSM MR analysis. The interfaces for GSM MR analysis consist of MR Overview Report, MR Query, and MR Comparison Analysis. Before performing relevant operations, familiarize yourself with the rules for dividing areas on the interface. 9.8.2 Parameters for Creating GSM E2E Tasks This section describes the parameters for creating GSM E2E tasks. You can refer to the description when creating a GSM E2E task. 9.8.3 Parameters for Creating and Modifying GSM MR Analysis Tasks This section describes the parameters for creating and modifying GSM MR analysis tasks. You can refer to the description when creating or modifying a GSM MR analysis task. 9.8.4 Parameters for Querying GBSC Reports This section describes the parameters related to querying the GBSC reports. You can refer to these parameters when querying the GBSC reports. 9.8.5 Parameters for Querying the GSM Cell Group Reports This section describes the parameters for querying the GSM cell group reports. You can refer to the description when querying the GSM cell group reports. 9.8.6 Parameters for Querying the GSM TopN TRX Reports This section describes the parameters for querying the GSM TopN TRX reports. You can refer to the description when querying the GSM TopN carrier reports. 9.8.7 Parameters for Querying the GSM MR Topic Analysis Reports This section describes the parameters for querying the reports of the GSM MR topic analysis. You can refer to the description when querying the GSM MR topic analysis reports. 9.8.8 Parameters for Querying the MR Analysis Results of GSM Cells This section describes the parameters for querying the MR analysis results of one or more GSM cells. You can refer to the description when querying the MR analysis results of GSM cells. 9.8.9 Parameters for Comparing GSM MR Analysis Results
9 GSM MR Analysis
This section describes the parameters related to comparing GSM MR analysis results. You can refer to these parameters when comparing GSM MR analysis results.
9.8.1 Interface Description: GSM MR Analysis

This section describes the interfaces for GSM MR analysis. The interfaces for GSM MR analysis consist of MR Overview Report, MR Query, and MR Comparison Analysis. Before performing relevant operations, familiarize yourself with the rules for dividing areas on the interface.
Interface for MR Report and Interface Description

The MR comprehensive analysis results can be displayed in table or in histogram mode, as shown in Figure 9-2. Figure 9-2 MR Overview Report
No. Name (1) Navigation tree of MR overview report
Description You can accurately locate the objects of the MR report on the navigation tree. Displays the information about the TopN TRXs or problematic TRXs in table. Different information is displayed in different situations. For details, see the description of relevant task pages.
(2)
Area for TopN TRXs or problematic TRXs
Issue 03 (2010-06-30)
9-33
9 GSM MR Analysis
No. Name (3) Area for TRXs
Description Displays the information about the TRXs in table. Different information is displayed in different situations. For details, see the description of relevant task pages. The system supports the function of highlighting MR summary reports in different colors. If a TRX is faulty, this TRX is highlighted in red.
(4)
Area for counter charts
Displays the counter information about the selected objects in histogram mode. Displays the basic information about this task in table. Displays the basic information about the cells corresponding to the selected TRXs in table.
(5)
Task information list
(6)
Cell information list
(7)
Area for problematic TRXs and operation Displays current problematic TRXs and advice operation advice.
Interface for Displaying MR Results and Interface Description

The MR results of a cell can be displayed in table or in histogram mode, as shown in Figure 9-3.
9-34
Issue 03 (2010-06-30)
9 GSM MR Analysis
Figure 9-3 MR Query Result
No. Name (8) Area for TopN TRXs and problematic TRXs Area for TRXs
Description Displays the calculated values of all TRXs of each cell in table. Displays the values of all TRXs of the selected cells in table. The system supports the function of highlighting MR results in colors. If a TRX is faulty, this TRX is highlighted in red.
(9)
(10) Area for counter charts
Displays the counter information about the selected objects in histogram mode. Displays the basic information about this task in table. Displays the basic information about the cells corresponding to the selected TRXs in table.
(11) Task information list
(12) Cell information list
(13) Area for problematic TRXs and operation Displays current problematic TRXs and advice operation advice.
Issue 03 (2010-06-30)
9-35
9 GSM MR Analysis
Interface for MR Comparison Analysis and Interface Description

The MR comparison results of a cell can be displayed in table or in histogram mode, as shown in Figure 9-4. Figure 9-4 MR Comparison Report
No. Name
Description
(14) Area for counter summary information Displays the differences of all summarized counters of each object within two periods in table. The Nastar can display the compared counter values that indicate performance trends in the table in colors. Red indicates that the performance deteriorates; green indicates that the performance improves; gray indicates that no comparison result exists or that the performance does not change. (15) Area for counter charts Displays the counter information about the selected objects in histogram mode.
9.8.2 Parameters for Creating GSM E2E Tasks

This section describes the parameters for creating GSM E2E tasks. You can refer to the description when creating a GSM E2E task.
9 GSM MR Analysis
Description of the parameters of GSM neighboring cell measurement tasks

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a neighboring cell measurement task. Indicates the name of the OSS related to the task. Select the GSM Neighbor Cell Data Task node. Indicates the time when the task starts to run. The start time must be later than the current time. By default, the start time is five minutes later than the current system time. Persist Time (Minute) Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 65535. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15. Measurement 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 15 minutes. For example, if this parameter is set to 2, the measurement time of each ARFCN is 215 minutes, that is, 30 minutes. Measurement step length 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 to the minimum rest step of the selected cell. Cell Object Displays the frequency information. Indicates the cell related to the neighboring cell measurement task. Indicates the set of ARFCNs to be measured. The ARFCNs are classified by group. The number of ARFCNs of each group is determined by Measure Step.
NOTE
l You can select a maximum of 762 ARFCNs for a cell.
If the number exceeds 762, the NE returns an error message after the corresponding MML command is executed, indicating that the task creation or modification fails.
l Before setting this parameter, you must set Measure
Step.
Issue 03 (2010-06-30)
9-37
9 GSM MR Analysis
Parameter Soft parameter information Set the soft parameters. RSSThres
Description If you select this option, the soft parameters that you set are valid for this measurement task. The value is an integer from 0 to 127. When the difference between the levels of the neighboring cell and the serving cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one. ASSThres The value is an integer from 0 to 63. When the level of the neighboring cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one. NCELLINTERFLE VELTHRES 1-7 You can set the thresholds of interference level for seven neighboring cells. The value is an integer from 0 to 127. When the difference between the levels of the neighboring cell and the serving cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one.
NOTE
l l l
Level refers to the strength of the received or transmitted signal. It is generally used in power control and handover algorithm. ASSThres and RSSThres evaluate the reasonableness of the neighbor cell. According to the actual requirements, you can modify the two values to adjust the evaluation standard. ADJINLVThres1 to ADJINLVThres7 evaluates the CIR distribution of neighboring cells and serving cells and the ratio among each segment. This parameter in combination with frequency configuration analysis indicates the severity level of each frequency interference, and thus can be used to adjust the C/I distribution segment of neighboring cells and serving cells. Carrier-to-interference ratio distribution refers to the distribution of the power of the carrier signals and the power of the interference signals, that is, C/I distribution.
Description of the parameters of GSM uplink frequency scanning tasks

Parameter Basic information Task Name OSS Name E2E Task List Description Indicates the name of a uplink frequency scanning task. Indicates the name of the OSS related to the task. Select the GSM Uplink Interference Analysis Data Task node.
9-38
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter Measurement information Time (Minute)
Description Indicates the total duration that a measurement task is performed. The value is an integer from 5 to 1440. Band Indicates the frequency band used by a cell. The M2000 supports the scanning of the following frequency bands:
l l l l l l
DCS_1800 EGSM_900 GSM850 P_GSM900 PSC1900 R_GSM900
Cell Object Frequency Type
Indicates the name of a cell related to the uplink frequency scanning task. Indicates the types of the test ARFCNs. The options are as follows:
l
All Frequency In The Frequency Segment Indicates that all the ARFCNs in the selected frequency band are measured. All Configuration Frequency In the Selected Cells Indicates the union of the ARFCNs of the selected cell. The User Selected Frequency In the Frequency Segment Indicates that you need to manually select the ARFCNs to be measured.
Description of the parameters of GSM VIP analysis data tasks

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a VIP analysis data task. Indicates the name of the OSS related to the task. Select the GSM VIP Analysis Task node. Indicates the time when the VIP analysis data task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss.
Issue 03 (2010-06-30)
9-39
9 GSM MR Analysis
Parameter End Time
Description Indicates the time when the VIP analysis data task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Selected Indicates the NE object related to the VIP analysis data task. If you select this parameter, the content in the Report Raw Data field corresponding to the VIP group can be selected. Indicates the name of a VIP group. Indicates the number of members in the VIP group. Indicates that the raw call data is also collected during the collection of the KPI aggregation information of all VIP objects of the selected VIP groups, thus helping to analyze problems thoroughly. Indicates the description of the VIP group.
Group Name Number of Members Report Raw Data
Description
Description of the parameters of GSM/UMTS neighboring cell data tasks

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a GSM/UMTS neighboring cell data task. Indicates the name of the OSS related to the task. Select the GSM/UMTS Neighboring Cell Data Task node. Indicates the time when the GSM/UMTS neighboring cell data task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the GSM/UMTS neighboring cell data task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time.
9-40
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter NE Object
Description Indicates the NE object related to the GSM/ UMTS neighboring cell data task.
Parameters for the GSM cell performance analysis data task

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a cell performance analysis task Indicates the name of the OSS related to the task Select the GSM Cell Performance Data Task node. Indicates the time when the cell performance analysis task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the cell performance analysis task is stopped. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE object Service Type Exception Type Indicates the NE object related to the cell performance analysis task. Indicates service types involved during the exception determination, such as Voice Service. Indicates the exception types involved during the exception determination, such as Short service duration. Indicates the KPIs involved during the exception determination. Indicates the types of exception determination, such as >=. Indicates the exception threshold involved during the exception determination, such as 30. The value is an integer from 0 to 65535.
KPI Determination rule Exception Value
Issue 03 (2010-06-30)
9-41
9 GSM MR Analysis
9.8.3 Parameters for Creating and Modifying GSM MR Analysis Tasks

This section describes the parameters for creating and modifying GSM MR analysis tasks. You can refer to the description when creating or modifying a GSM MR analysis task.
Parameter Basic Information Task Name Description Indicates the name of an MR analysis task. Value range:
l l
A maximum of 128 characters The following characters are not allowed: ` ~ ! @ #$%^&*()+={}[]\|;':,.?/<>" Unique and not null Case sensitive
l l
Task Type Execution Type
You need to select GSM MR Analysis Task from the Task Type navigation tree.
l
Once task: The system executes the created tasks only once at the specified time. Period task: The system executes the created tasks at the preset time.
Note
Indicates the description of the task. Value range:

l l
A maximum of 500 characters The following characters are not allowed: ~ ! # $ %^*+=|\/,'`
Time Information
Begin Date
Indicates time for starting a task. The start time should be later than the current server time. You can either type the time value in this field, or click to select the date and time in the Date Selection dialog box. This parameter is valid for only periodic tasks.
Cycle
Indicates the interval between periodic tasks. This parameter involves the period unit and the interval.
l l
Unit: day. Interval: 1 to 9999.
This parameter is valid for only periodic tasks.
9-42
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter Execution Times
Description Indicates the times that a periodic task is executed. If this parameter is set to 0, you can infer that the task is executed all the time. Value range: 0 to 9999. This parameter is valid for only periodic tasks. Data Time Scope The start time should precede the end time. You can either type the time value in this field, or click to select the date and time in the Date Selection dialog box. This parameter is valid for only one-time tasks. Task Start At Indicates the start time for executing analysis tasks. The parameter value must be later than the end time of Data Time Scope. Time
l
All day: The task is executed every day during the selected time range. Specify: The task is executed during the specified time segment every day during the selected time range. The time segment cannot overlap. The start time of the next time segment must be later than or the same as the end time of the current time segment.
Object Information
BSC Cell Group
If you select this option, the navigation tree displays all the BSCs of the entire network. If you select this option, the navigation tree displays all the cell groups of the entire network. If the number of MRs, in which the level of uplink quality is not smaller than X, is greater than Y% of the total number of MRs, the TRX is problematic. X indicates the level of uplink quality. It is an integer between 1 and 7. The default value is 4. Y indicates the threshold. It is an integer from 1 to 100. The default value is 10.
Parameter Information
Uplink Quality X MR of a Value (%) Y
Downlink Quality X MR of a Value (%) Y
If the number of MRs, in which the level of downlink quality is not smaller than X, is greater than Y% of the total number of MRs, the TRX is problematic. X indicates the level of downlink quality. It is an integer between 1 and 7. The default value is 4. Y indicates the threshold. It is an integer from 1 to 100. The default value is 10.
Issue 03 (2010-06-30)
9-43
9 GSM MR Analysis
Parameter Uplink Level X MR of dBm (%) Y
Description If the number of MRs, in which the value of uplink level is not greater than X (dBm), is greater than Y % of the total number of MRs, the TRX is problematic. 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. The default value is 70. Downlink Level X MR of dBm (%) Y If the number of MRs, in which the value of downlink level is not greater than X (dBm), is greater than Y% of the total number of MRs, the TRX is problematic. 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. The default value is 40. TA X MR of a Value (%) Y If the number of MRs, in which the TA value is not smaller than X, is greater than Y% of the total number of MRs, the TRX is problematic. X indicates the TA value. It is an integer from 1 to 63. The default value is 6. Y indicates the threshold. It is an integer from 1 to 100. The default value is 50. Downlink Level Uplink Level > X MR of dB (%) Y If the number of MRs, in which the difference between the downlink level and uplink level is greater than X (dB), is greater than Y% of the total number of MRs, the TRX is problematic. 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. The default value is 40. Downlink Level Uplink Level < X MR of dB (%) Y If the number of MRs, in which the difference between the downlink level and uplink level is smaller than X (dB), is greater than Y% of the total number of MRs, the TRX is problematic. X indicates the level difference. It can be 1, 3, 6, 10, or 15. The default value is 15. Y indicates the threshold. It is an integer from 1 to 100. The default value is 40.
9-44
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter Total Number of MR < X
Description If the number of received MRs is smaller than X, the TRX is problematic. X indicates the threshold. It is an integer from 1 to 9999. The default value is 200. TopN =X Indicates the number of TopN counters. You can query the information about X TRXs whose performance is the poorest as indicated by the selected counter. X indicates the number of TopN counters. It is an integer from 1 to 99. The default value is 10.
9.8.4 Parameters for Querying GBSC Reports

This section describes the parameters related to querying the GBSC reports. You can refer to these parameters when querying the GBSC reports.
NOTE
For details about the rules for dividing areas, see 9.8.1 Interface Description: GSM MR Analysis.
Parameters for Querying TRXs on the Entire Network

Area (2) displays the number of TopN TRXs and problematic TRXs in each GBSC on the entire network. For details, see Table 9-6. Table 9-6 Parameters related to the TRXs on the entire network (1) Parameter BSC ID BSC Name TRX Count for Average Uplink Receive Quality (Full Rate) TRX Count for Average Downlink Receive Quality (Full Rate) TRX Count for Average Uplink Receive Quality (Half Rate) TRX Count for Average Downlink Receive Quality (Half Rate) Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the number of TopN TRXs with the average received signal quality (full rate) values of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average received signal quality (full rate) values of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the average received signal quality (half rate) values of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average received signal quality (half rate) values of the MSs exceeding the threshold.
Issue 03 (2010-06-30)
9-45
9 GSM MR Analysis
Parameter TRX Count for Average Uplink Receive Level (Full Rate) TRX Count for Average Downlink Receive Level (Full Rate) TRX Count for Average Uplink Receive Level (Half Rate) TRX Count for Average Downlink Receive Level (Half Rate) TRX Count for Average TA Distribution TRX Count for Link Balance TRX Count for Uplink Interference TRX Count for Downlink Interference TRX Count for Uplink Weak Coverage TRX Count for Downlink Weak Coverage TRX Count for Weak TRX Coverage TRX Count for Over-Distance Coverage TRX Count for Link Balance (Uplink Problem) TRX Count for Link Balance (Downlink Problem) TRX Count for Other Problems
Description Indicates the number of TopN TRXs with the average received levels (full rate) of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels (full rate) of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels (half rate) of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels (half rate) of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the values of Average TA Distribution exceeding the threshold. Indicates the number of TopN TRXs with the values of Link Balance exceeding the threshold. Indicates the number of problematic TRXs meeting the requirements of the Uplink Interference topic. Indicates the number of problematic TRXs meeting the requirements of the Downlink Interference topic. Indicates the number of problematic TRXs meeting the requirements of the Uplink Weak Coverage topic. Indicates the number of problematic TRXs meeting the requirements of the Downlink Weak Coverage topic. Indicates the number of problematic TRXs meeting the requirements of the Weak TRX Coverage topic. Indicates the number of problematic TRXs meeting the requirements of the Over-Distance Coverage topic. Indicates the number of problematic TRXs meeting the requirements of the Link Balance (Uplink Problem) topic. Indicates the number of problematic TRXs meeting the requirements of the Link Balance (Downlink Problem) topic. Indicates the number of problematic TRXs meeting the requirements of other topics.
Area (3) displays the information about all the TRXs in each GBSC on the entire network. For details, see Table 9-7.
9 GSM MR Analysis
Table 9-7 Parameters related to the TRXs on the entire network (2) Parameter BSC ID BSC Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Link Balance Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the number of MRs transferred over the full-rate channel. Indicates the number of MRs transferred over the halfrate channel. Indicates the value of the average received signal quality (full rate) of the BTS. Indicates the value of the average received signal quality (full rate) of the MS. Indicates the value of the average received signal quality (half rate) of the BTS. Indicates the value of the average received signal quality (half rate) of the MS. Indicates the average received level (full rate) of the BTS. Indicates the average received level (full rate) of the MS. Indicates the average received level (half rate) of the BTS. Indicates the average received level (half rate) of the MS. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS. Indicates the dB value calculated through this expression: Average received level of the MS - Average received level of the BTS - Difference between the values of the average sensitivity of the MS and BTS.
Parameters for Querying TRXs in a GBSC

If you select a counter node, the TRX frequencies in the GBSC are sorted by the counter in area (2). If you select a topic node, the problematic TRX frequencies meeting the requirements of the topic are displayed in area (2). For details, see Table 9-8.
Issue 03 (2010-06-30)
9-47
9 GSM MR Analysis
Table 9-8 Parameters related to the TRXs in a GBSC (1) Parameter BSC ID BSC Name Cell ID Cell Name TRX ID TRX Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the number of the cell that the TRX belongs to. Indicates the name of the cell that the TRX belongs to. Indicates the number of the TRX controlled by the BSC. Indicates the name of the TRX controlled by the BSC. Indicates the number of MRs transferred over the fullrate channel. Indicates the number of MRs transferred over the halfrate channel. Indicates the average quality of received signals (full rate) of the BTSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average quality of received signals (full rate) of the MSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average quality of received signals (half rate) of the BTSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average quality of received signals (half rate) of the MSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average received levels (full rate) of the BTSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average received levels (full rate) of the MSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average received levels (half rate) of the BTSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average received levels (half rate) of the MSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS.
9-48
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter Link Balance
Description Indicates the dB value calculated through this expression: Average received level of the MS corresponding to the TopN TRX or problematic TRX controlled by the BSC - Average received level of the BTS corresponding to the TopN TRX or problematic TRX controlled by the BSC - Difference between the values of the average sensitivity of the MS and BTS.
Area (3) displays the information about all TRXs in the cell to which the TopN TRXs or problematic TRXs selected in Area (2) belong. For details, see Table 9-9. Table 9-9 Parameters related to the TRXs in a GBSC (2) Parameter BSC ID BSC Name Cell ID Cell Name TRX ID TRX Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate)
Issue 03 (2010-06-30)
Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the number of the cell that the TRX belongs to. Indicates the name of the cell that the TRX belongs to. Indicates the number of the TRX controlled by the BSC. Indicates the name of the TRX controlled by the BSC. Indicates the number of MRs transferred over the full-rate channel. Indicates the number of MRs transferred over the half-rate channel. Indicates the average quality of received signals (full rate) of the BTSs corresponding to all TRXs. Indicates the average quality of received signals (full rate) of the MSs corresponding to all TRXs. Indicates the average quality of received signals (half rate) of the BTSs corresponding to all TRXs. Indicates the average quality of received signals (half rate) of the MSs corresponding to all TRXs. Indicates the average received levels (full rate) of the BTSs corresponding to all TRXs. Indicates the average received levels (full rate) of the MSs corresponding to all TRXs. Indicates the average received levels (half rate) of the BTSs corresponding to all TRXs.
9-49
9 GSM MR Analysis
Parameter Average Downlink Receive Level (Half Rate) Average TA Distribution Link Balance
Description Indicates the average received levels (half rate) of the MSs corresponding to all TRXs. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS. 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 MS and BTS.
Parameters related to the basic information

Area (5) displays the information about the queried performance analysis task. For details, see Table 9-10. Table 9-10 Parameters related to the task information Parameter Task Name Start Time End Time Task Creator Description Indicates the name of the queried performance analysis task. Indicates the time that the Nastar starts generating a task report. Indicates the time that the Nastar stops generating a task report. Indicates the creator's name of the queried performance analysis task.
Area (6) displays the information about the cell corresponding to the selected TRX. For details, see Table 9-11. Table 9-11 Parameters related to the cell information Parameter Cell Object ID Cell Name LAC CI BCCH BCC
9-50
Description Indicates internal ID of the cell where the selected TRX is located. Indicates name of the cell where the selected TRX is located. Indicates location area code of the cell where the selected TRX is located. Indicates the ID of the cell where the selected TRX is located. Indicates the frequency transmitted on the BCCH. Indicates the base station color code.
9 GSM MR Analysis
Parameter NCC Cell Layer Cell Prior Half Rate Supported Frequency Hopping Type GPS Supported EDGE Supported Concentric Circle Supported Base Station Type
Description Indicates the network color code. Indicates the layer where the cell is located. Indicates the cell priority. Indicates whether the half rate is supported. Indicates the type of the frequency hopping, such as the RF frequency hopping and baseband frequency hopping. Indicates whether the GPRS service is supported. Indicates whether the Edge service is supported. Indicates whether the intelligent underlay-overlay cell function is supported. Indicates the BTS type.
Area (7) displays the information about the problematic TRXs and the relevant operation advice. For details, see Table 9-12. Table 9-12 Topic categories and relevant operation suggestions Topic Uplink interferen ce Description The uplink-interference results in the high level and poor quality. Suggestion Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, enable the function of uplink-interference analysis to analyze the interference according to the uplink frequency distribution that is measured by TRXs. Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, use an MS to search for frequencies within the cell coverage where the TRX is transmitted, and observe the downlink frequency status. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX.
Issue 03 (2010-06-30)
9-51
9 GSM MR Analysis
Topic Weak downlink coverage
Description The loss of the downlink TRX is excessive.
Suggestion Move an MS to a place near the TRX to measure the actual power of the TRX. Check whether the downlink level of the TRX is low. If the downlink level of the TRX is low, check the cable connections between the combiner and the TRX, and connections in the antenna system. Then, check the level at the TRX entry and output entry of the combiner by using the power meter to locate the fault.
l
Weak TRX coverage
The loss of the TRX is excessive. The TRX coverage is remote, which causes the low quality of the uplink. The TRX coverage is remote, which causes the low quality of the downlink. Remote TRX coverage The TRX coverage is remote, which causes the low quality of the uplink and downlink. Uplink and downlink are not balanced. The downlink is stronger. The excessive loss of the uplink results in the low received level and poor signal quality of the BTS.
Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX. Check whether the actual azimuth of the antenna is the same as the antenna azimuth in design. If the antenna is omni-directional, check whether the coverage is excessively large. Check whether there are missing neighboring cells and cells whose coverage is remote. Check whether the actual azimuth of the antenna is the same as the antenna azimuth in design. If the antenna is omni-directional, check whether the coverage is excessively large. Check whether the coverage complies with the planning and whether the output power of the TRX and CDU is normal. You can adjust the uplink received threshold and the level of the downlink static power to balance the uplink and downlink. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX.
Remote coverage
l l
9-52
Issue 03 (2010-06-30)
9 GSM MR Analysis
Topic Link balance (downlink )
Description
l
Suggestion
l
Check whether the coverage complies with the planning and whether the output power of the TRX and CDU is normal. You can adjust the threshold of the receive power and the level of the static power on the uplink to balance the uplink and downlink. Move an MS to a place near the TRX to check the actual power of the TRX and check whether the downlink level of the TRX is low. If the downlink level of the TRX is low, check the cable connections between the combiner and the TRX and connections in the antenna system, and check the level at the TRX entry and output entry of the combiner by using the power meter to locate the fault.
Others
9.8.5 Parameters for Querying the GSM Cell Group Reports

This section describes the parameters for querying the GSM cell group reports. You can refer to the description when querying the GSM cell group reports.
NOTE
Parameters Related to Querying the TRXs on the Entire Network

The number of TopN TRXs and problematic TRXs in each cell group is displayed in Area (2). For details, see Table 9-13. Table 9-13 Parameters related to the TRXs on the entire network (1) Parameter Cell Group ID Cell Group Name TRX Count for Average Uplink Receive Quality (Full Rate) Description Indicates the ID of a cell group. Indicates the name of a cell group, for example, CELL_1. Indicates the number of TopN TRXs with the average quality values of the received signals (full rate) of the BTSs exceeding the threshold.
Issue 03 (2010-06-30)
9-53
9 GSM MR Analysis
Parameter TRX Count for Average Downlink Receive Quality (Full Rate) TRX Count for Average Uplink Receive Quality (Half Rate) TRX Count for Average Downlink Receive Quality (Half Rate) TRX Count for Average Uplink Receive Level (Full Rate) TRX Count for Average Downlink Receive Level (Full Rate) TRX Count for Average Uplink Receive Level (Half Rate) TRX Count for Average Downlink Receive Level (Half Rate) TRX Count for Average TA Distribution TRX Count for Link Balance TRX Count for Uplink Interference TRX Count for Downlink Interference TRX Count for Uplink Weak Coverage TRX Count for Downlink Weak Coverage TRX Count for Weak TRX Coverage TRX Count for OverDistance Coverage TRX Count for Link Balance (Uplink Problem)
Description Indicates the number of TopN TRXs with the average quality values of the received signals (full rate) of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the average quality values of the received signals (half rate) of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average quality values of the received signals (half rate) of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels (full rate) of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels (full rate) of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels (half rate) of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels (half rate) of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the values of Average TA Distribution exceeding the threshold. Indicates the number of TopN TRXs with the values of Link Balance exceeding the threshold. Indicates the number of problematic TRXs meeting the requirements of the Uplink Interference topic. Indicates the number of problematic TRXs meeting the requirements of the Downlink Interference topic. Indicates the number of problematic TRXs meeting the requirements of the Uplink Weak Coverage topic. Indicates the number of problematic TRXs meeting the requirements of the Downlink Weak Coverage topic. Indicates the number of problematic TRXs meeting the requirements of the Weak TRX Coverage topic. Indicates the number of problematic TRXs meeting the requirements of the Over-Distance Coverage topic. Indicates the number of problematic TRXs meeting the requirements of the Link Balance (Uplink Problem) topic.
9-54
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter TRX Count for Link Balance (Downlink Problem) TRX Count for Other Problems
Description Indicates the number of problematic TRXs meeting the requirements of the Link Balance (Downlink Problem) topic. Indicates the number of problematic TRXs meeting the requirements of the Other Problem topic.
The calculation result of the TRXs in each cell group on the entire network is displayed in Area (3). For details, see Table 9-14. Table 9-14 Parameters related to the TRXs on the entire network (2) Parameter Cell Group ID Cell Group Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Description Indicates the ID of a cell group. Indicates the name of a cell group, for example, CELL_1. Indicates the number of MRs transferred over the full-rate channel. Indicates the number of MRs transferred over the half-rate channel. Indicates the average quality of received signals (full rate) of the BTS. Indicates the average quality of received signals (full rate) of the MS. Indicates the average quality of received signals (half rate) of the BTS. Indicates the average quality of received signals (half rate) of the MS. Indicates the average received level (full rate) of the BTS. Indicates the average received level (full rate) of the MS. Indicates the average received level (half rate) of the BTS. Indicates the average received level (half rate) of the MS. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS.
Issue 03 (2010-06-30)
9-55
9 GSM MR Analysis
Description Indicates the dB value calculated through this expression: Average received level of the MS - Average received level of the BTS - Difference between the values of the average sensitivity of the MS and BTS.
Parameters Related to Querying TRXs in a Cell Group

If you select a counter node, the TRX frequencies in the selected cell group are sorted by the counter in area (2). If you select a topic node, the problematic TRX frequencies meeting the requirements of the topic are displayed in Area (2). For details, see Table 9-15. Table 9-15 Parameters related to the TRXs in a cell group (1) Parameter Cell Group ID Cell Group Name Cell ID Cell Name TRX ID TRX Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Description Indicates the ID of a cell group. Indicates the name of a cell group, for example, CELL_1. Indicates the ID of the cell where a TRX is located. Indicates the name of the cell where a TRX is located. Indicates the number of a TRX in a cell group. Indicates the name of a TRX in a cell group. Indicates the number of MRs transferred over the full-rate channel.
Indicates the number of MRs transferred over the half-rate channel.
Indicates the average quality of received signals (full rate) of the BTS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the average quality of received signals (full rate) of the MS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the average quality of received signals (half rate) of the BTS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the average quality of received signals (half rate) of the MS corresponding to a TopN TRX or problematic TRX in the cell group.
9-56
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Link Balance
Description Indicates the average received level value (full rate) of the BTS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the average received level value (full rate) of the MS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the average received level value (half rate) of the BTS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the average received level value (half rate) of the MS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS. Indicates the dB value, corresponding to a TopN TRX or problematic TRX in the cell group, calculated through this expression: Average received level of the MS corresponding to the TopN TRX or problematic TRX - Average received level of the BTS corresponding to the TopN TRX or problematic TRX Difference between the values of the average sensitivity of the MS and BTS.
All the TRXs in the cell where the selected TopN TRX or problematic TRX resides are displayed in Area (3). For details, see Table 9-16. Table 9-16 Parameters related to the TRXs in a cell group (2) Parameter BSC ID BSC Name Cell ID Cell Name TRX ID TRX Name Total Number of Measurement Reports for Full Rate Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the ID of the cell where a TRX is located. Indicates the name of the cell where a TRX is located. Indicates the number of a TRX in a cell group. Indicates the name of a TRX in a cell group. Indicates the number of MRs transferred over the full-rate channel.
Issue 03 (2010-06-30)
9-57
9 GSM MR Analysis
Parameter Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Link Balance
Description Indicates the number of MRs transferred over the half-rate channel. Indicates the average quality of received signals (full rate) of the BTS corresponding to each TRX. Indicates the average quality of received signals (full rate) of the MS corresponding to each TRX. Indicates the average quality of received signals (half rate) of the BTS corresponding to each TRX Indicates the average quality of received signals (half rate) of the MS corresponding to each TRX. Indicates the average received level (full rate) of the BTS corresponding to each TRX Indicates the average received level (full rate) of the MS corresponding to each TRX. Indicates the average received level (half rate) of the BTS corresponding to each TRX. Indicates the average received level (half rate) of the MS corresponding to each TRX. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS. 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 MS and BTS.
Parameters Related to the Basic Information

The information about a selected performance analysis task is displayed in Area (5). For details, see Table 9-17. Table 9-17 Parameters related to the task information Parameter Task Name Begin Time Description Indicates the name of a selected performance analysis task. Indicates the time when the Nastar starts to generate a task report.
9-58
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter End Time Task Creator
Description Indicates the time when the Nastar stops to generate a task report. Indicates the creator's name of the queried performance analysis task.
The information about the cell corresponding to the selected TRX is displayed in Area (6). For details, see Table 9-18. Table 9-18 Parameters related to the cell information Parameter Cell Object ID Cell Name LAC CI BCCH BCC NCC Cell Layer Cell Prior Half Rate Supported Frequency Hopping Type GPS Supported EDGE Supported Concentric Circle Supported Base Station Type Description Indicates the internal ID of the cell where the selected TRX is located. Indicates the name of the cell where the selected TRX is located. Indicates the location area code of the cell where the selected TRX is located. Indicates the ID of the cell where the selected TRX is located. Indicates the frequency transmitted on the BCCH. Indicates the color code of a base station. Indicates the network color code. Indicates the layer where the cell is located. Indicates the cell priority. Indicates whether half rate is supported. Indicates the type of the frequency hopping, such as the RF hopping and baseband frequency hopping. Indicates whether the GPRS service is supported. Indicates whether the EDGE service is supported. Indicates whether the intelligent underlay-overlay cell function is supported. Indicates the BTS type.
The information about the problematic TRXs and the relevant operation suggestions are displayed in Area (7). For details, see Table 9-19.
Issue 03 (2010-06-30)
9-59
9 GSM MR Analysis
Table 9-19 Topic categories and relevant operation suggestions Topic Uplink interferen ce Description The uplink-interference results in the high level and poor quality. Suggestion Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, enable the function of uplink-interference analysis to analyze the interference according to the uplink frequency distribution that is measured by TRXs. Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, use an MS to search for frequencies within the cell coverage where the TRX is transmitted, and observe the downlink frequency status. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX. Move an MS to a place near the TRX to measure the actual power of the TRX. Check whether the downlink level of the TRX is low. If the downlink level of the TRX is low, check the cable connections between the combiner and the TRX, and connections in the antenna system. Then, check the level at the TRX entry and output entry of the combiner by using the power meter to locate the fault.
l
Weak downlink coverage
The loss of the downlink TRX is excessive.
Weak TRX coverage
The loss of the TRX is excessive. The TRX coverage is remote, which causes the low quality of the uplink. The TRX coverage is remote, which causes the low quality of the downlink. Remote TRX coverage The TRX coverage is remote, which causes the low quality of the uplink and downlink.
Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX. Check whether the actual azimuth of the antenna is the same as the antenna azimuth in design. If the antenna is omni-directional, check whether the coverage is excessively large. Check whether there are missing neighboring cells and cells whose coverage is remote. Check whether the actual azimuth of the antenna is the same as the antenna azimuth in design. If the antenna is omni-directional, check whether the coverage is excessively large.
Remote coverage
l l
9-60
Issue 03 (2010-06-30)
9 GSM MR Analysis
Topic Link balance (uplink)
Description
l
Suggestion
l
Uplink and downlink are not balanced. The downlink is stronger. The excessive loss of the uplink results in the low received level and poor signal quality of the BTS.
Check whether the coverage complies with the planning and whether the output power of the TRX and CDU is normal. You can adjust the uplink received threshold and the level of the downlink static power to balance the uplink and downlink. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX. Check whether the coverage complies with the planning and whether the output power of the TRX and CDU is normal. You can adjust the threshold of the receive power and the level of the static power on the uplink to balance the uplink and downlink. Move an MS to a place near the TRX to check the actual power of the TRX and check whether the downlink level of the TRX is low. If the downlink level of the TRX is low, check the cable connections between the combiner and the TRX and connections in the antenna system, and check the level at the TRX entry and output entry of the combiner by using the power meter to locate the fault.
Link balance (downlink )
Others
9.8.6 Parameters for Querying the GSM TopN TRX Reports

This section describes the parameters for querying the GSM TopN TRX reports. You can refer to the description when querying the GSM TopN carrier reports.
NOTE
Parameters Related to Querying TopN TRXs

In Area (2), the system displays the information about the 10 TRXs of which the selected counter indicates the poorest performance. For details, see Table 9-20.
9 GSM MR Analysis
Table 9-20 Parameters related to the TopN TRXs (1) Parameter BSC ID BSC Name Cell ID Cell Name TRX ID TRX Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Link Balance Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the ID of the cell where a TopN TRX is located. Indicates the name of the cell where a TopN TRX is located. Indicates the number of a TopN TRX. Indicates the name of a TopN TRX. Indicates the number of MRs transferred over the full-rate channel. Indicates the number of MRs transferred over the half-rate channel. Indicates the average quality of received signals (full rate) of the BTS corresponding to the TopN TRX. Indicates the average quality of received signals (full rate) of the MS corresponding to the TopN TRX. Indicates the average quality of received signals (half rate) of the BTS corresponding to the TopN TRX. Indicates the average quality of received signals (half rate) of the MS corresponding to the TopN TRX. Indicates the average received level (full rate) of the BTS corresponding to the TopN TRX. Indicates the average received level (full rate) of the MS corresponding to the TopN TRX. Indicates the average received level (half rate) of the BTS corresponding to the TopN TRX. Indicates the average received level (half rate) of the MS corresponding to the TopN TRX. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS. Indicates the dB value calculated through this expression: Average received level of the MS corresponding to the TopN TRX - Average received level of the BTS corresponding to the TopN TRX - Difference between the values of the average sensitivity of the MS and BTS.
9-62
Issue 03 (2010-06-30)
9 GSM MR Analysis
If you select a record of a TopN TRX in Area (2), the system displays the frequencies of all the TRXs in the cell where the selected TopN TRX resides in Area (3). For details, see Table 9-21. Table 9-21 Parameters related to the TopN TRXs (2) Parameter BSC ID BSC Name Cell ID Cell Name TRX ID TRX Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the ID of the cell where a TRX is located. Indicates the name of the cell where a TRX is located. Indicates the number of a TRX. Indicates the name of a TRX. Indicates the number of MRs transferred over the full-rate channel. Indicates the number of MRs transferred over the half-rate channel. Indicates the average quality of received signals (full rate) of the BTS corresponding to each TRX. Indicates the average quality of received signals (full rate) of the MS corresponding to each TRX. Indicates the average quality of received signals (half rate) of the BTS corresponding to each TRX Indicates the average quality of received signals (half rate) of the MS corresponding to each TRX. Indicates the average received level (full rate) of the BTS corresponding to each TRX Indicates the average received level (full rate) of the MS corresponding to each TRX. Indicates the average received level (half rate) of the BTS corresponding to each TRX. Indicates the average received level (half rate) of the MS corresponding to each TRX. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS.
Issue 03 (2010-06-30)
9-63
9 GSM MR Analysis
Description 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 MS and BTS.

In Area (5), the system displays the information about a selected performance analysis task. For details, see Table 9-22. Table 9-22 Parameters related to the task information Parameter TaskName BEGINTIME ENDTIME Task Creator Description Indicates the name of a selected performance analysis task. Indicates the time when the Nastar starts to generate a task report. Indicates the time when the Nastar stops to generate a task report. Indicates the creator's name of the queried performance analysis task.
In Area (6), the system displays the information about the cell corresponding to the selected TRX. For details, see Table 9-23. Table 9-23 Parameters related to the cell information Parameter Cell Object ID Cell Name LAC CI BCCH BCC NCC
9-64
Description Indicates the internal ID of the cell where the selected TRX is located. Indicates the name of the cell where the selected TRX is located. Indicates the location area code of the cell where the selected TRX is located. Indicates the ID of the cell where the selected TRX is located. Indicates the frequency transmitted on the BCCH. Indicates the color code of a base station. Indicates the network color code.
9 GSM MR Analysis
Parameter Cell Layer Cell Prior Half Rate Supported Frequency Hopping Type GPS Supported EDGE Supported Concentric Circle Supported Base Station Type
Description Indicates the layer where the cell is located. Indicates the cell priority. Indicates whether the half rate is supported. Indicates the type of the frequency hopping, such as the RF hopping and baseband frequency hopping. Indicates whether the GPRS service is supported. Indicates whether the EDGE service is supported. Indicates whether the intelligent underlay-overlay cell function is supported. Indicates the BTS type.
In Area (7), the system displays the information about the problematic TRXs and the relevant operation suggestions. For details, see Table 9-24. Table 9-24 Topic categories and relevant operation suggestions Topic Uplink interferen ce Description The uplink-interference results in the high level and poor quality. Suggestion Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, enable the function of uplink-interference analysis to analyze the interference according to the uplink frequency distribution that is measured by TRXs. Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, use an MS to search for frequencies within the cell coverage where the TRX is transmitted, and observe the downlink frequency status. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX.
Issue 03 (2010-06-30)
9-65
9 GSM MR Analysis
l
Weak TRX coverage
Remote coverage
l l
9-66
Issue 03 (2010-06-30)
9 GSM MR Analysis
Description
l
Suggestion
l
Others
9.8.7 Parameters for Querying the GSM MR Topic Analysis Reports

This section describes the parameters for querying the reports of the GSM MR topic analysis. You can refer to the description when querying the GSM MR topic analysis reports.
NOTE
Parameters Related to Querying Problematic TRXs Involved in Topic Analysis

The information about all the problematic TRXs involved in topic analysis is displayed in Area (2). For details, see Table 9-25. Table 9-25 Parameters related to the problematic TRXs involved in topic analysis (1) Parameter BSC ID BSC Name Cell ID Cell Name TRX ID TRX Name
Issue 03 (2010-06-30)
Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the ID of the cell where a problematic TRX is located. Indicates the name of the cell where a problematic TRX is located. Indicates the number of a problematic TRX. Indicates the name of a problematic TRX.
9 GSM MR Analysis
Parameter Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Link Balance
Description Indicates the number of MRs transferred over the full-rate channel. Indicates the number of MRs transferred over the half-rate channel. Indicates the average quality of received signals (full rate) of the BTS corresponding to the problematic TRX. Indicates the average quality of received signals (full rate) of the MS corresponding to the problematic TRX. Indicates the average quality of received signals (half rate) of the BTS corresponding to the problematic TRX. Indicates the average quality of received signals (half rate) of the MS corresponding to the problematic TRX. Indicates the average received level (full rate) of the BTS corresponding to the problematic TRX. Indicates the average received level (full rate) of the MS corresponding to the problematic TRX. Indicates the average received level (half rate) of the BTS corresponding to the problematic TRX. Indicates the average received level (half rate) of the MS corresponding to the problematic TRX. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS. Indicates the dB value calculated through this expression: Average received level of the MS corresponding to the problematic TRX - Average received level of the BTS corresponding to the problematic TRX - Difference between the values of the average sensitivity of the MS and BTS.
If you select a record of a problematic TRX in Area (2), the frequencies of all the TRXs in the cell where the selected problematic TRX resides is displayed in Area (3). For details, see Table 9-26.
9-68
Issue 03 (2010-06-30)
9 GSM MR Analysis
Table 9-26 Parameters related to the TRXs involved in topic analysis (2) Parameter BSC ID BSC Name Cell ID Cell Name TRX ID TRX Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the ID of the cell where a TRX is located. Indicates the name of the cell where a TRX is located. Indicates the number of a TRX. Indicates the name of a TRX. Indicates the number of MRs transferred over the full-rate channel. Indicates the number of MRs transferred over the half-rate channel. Indicates the average quality of received signals (full rate) of the BTS corresponding to each TRX. Indicates the average quality of received signals (full rate) of the MS corresponding to each TRX. Indicates the average quality of received signals (half rate) of the BTS corresponding to each TRX. Indicates the average quality of received signals (half rate) of the MS corresponding to each TRX. Indicates the average received level (full rate) of the BTS corresponding to each TRX. Indicates the average received level (full rate) of the MS corresponding to each TRX. Indicates the average received level (half rate) of the BTS corresponding to each TRX. Indicates the average received level (half rate) of the MS corresponding to each TRX. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS.
Issue 03 (2010-06-30)
9-69
9 GSM MR Analysis
Description 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 MS and BTS.

The information about a selected performance analysis task is displayed in Area (5). For details, see Table 9-27. Table 9-27 Parameters related to the task information Parameter TaskName BEGINTIME ENDTIME Task Creator Description Indicates the name of a performance analysis task. Indicates the time when the Nastar starts to generate a task report. Indicates the time when the Nastar stops to generate a task report. Indicates the creator's name of the queried performance analysis task.
The information about the cell corresponding to the selected TRX is displayed in Area (6). For details, see Table 9-28. Table 9-28 Parameters related to the cell information Parameter Cell Object ID Cell Name LAC CI BCCH BCC NCC
9-70
Description Indicates the internal ID of the cell where the selected TRX is located. Indicates the name of the cell where the selected TRX is located. Indicates the location area code of the cell where the selected TRX is located. Indicates the ID of the cell where the selected TRX is located. Indicates the frequency transmitted on the BCCH. Indicates the color code of a base station. Indicates the network color code.
9 GSM MR Analysis
Parameter Cell Layer Cell Prior Half Rate Supported Frequency Hopping Type GPS Supported EDGE Supported Concentric Circle Supported Base Station Type
Description Indicates the layer where the cell is located. Indicates the cell priority. Indicates whether half rate is supported. Indicates the type of the frequency hopping, such as the RF hopping and baseband frequency hopping. Indicates whether the GPRS service is supported. Indicates whether the EDGE service is supported. Indicates whether the intelligent underlay-overlay cell function is supported. Indicates the BTS type.
The information about the problematic TRXs and the relevant operation suggestion are displayed in Area (7). For details, see Table 9-29. Table 9-29 Topic categories and relevant operation suggestions Topic Uplink interferen ce Description The uplink-interference results in the high level and poor quality. Suggestion Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, enable the function of uplink-interference analysis to analyze the interference according to the uplink frequency distribution that is measured by TRXs. Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, use an MS to search for frequencies within the cell coverage where the TRX is transmitted, and observe the downlink frequency status. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX.
Issue 03 (2010-06-30)
9-71
9 GSM MR Analysis
l
Weak TRX coverage
Remote coverage
l l
9-72
Issue 03 (2010-06-30)
9 GSM MR Analysis
Description
l
Suggestion
l
Others
9.8.8 Parameters for Querying the MR Analysis Results of GSM Cells

This section describes the parameters for querying the MR analysis results of one or more GSM cells. You can refer to the description when querying the MR analysis results of GSM cells.
NOTE
Parameters Related to Querying TopN TRXs and Problematic TRXs in the MR Analysis Results
The calculation result of the TRXs in each cell is displayed in Area (8). For details, see Table 9-30. Table 9-30 Parameters related to querying TRXs in the MR analysis results of GSM cells Parameter BSC ID BSC Name Cell ID Cell Name
Issue 03 (2010-06-30)
Description Indicates the ID of the BSC that a TRX belongs to. Indicates the name of a BSC, for example, BSC_1. Indicates the ID of the cell where a TRX is located. Indicates the name of the cell where a TRX is located.
9 GSM MR Analysis
Parameter Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Link Balance
Description Indicates the number of MRs transferred over the full-rate channel.
Indicates the number of MRs transferred over the half-rate channel.
Indicates the calculation result of the average quality values of the received signals (full rate) of the BTSs corresponding to all the TRXs. Indicates the calculation result of the average quality values of the received signals (full rate) of the MSs corresponding to all the TRXs. Indicates the calculation result of the average quality values of the received signals (half rate) of the BTSs corresponding to all the TRXs. Indicates the calculation result of the average quality values of the received signals (half rate) of the MSs corresponding to all the TRXs. Indicates the calculation result of the average received levels (full rate) of the BTSs corresponding to all the TRXs. Indicates the calculation result of the average levels (full rate) of the MSs corresponding to all the TRXs. Indicates the calculation result of the average received levels (half rate) of the BTSs corresponding to all the TRXs. Indicates the calculation result of the average received levels (half rate) of the MSs corresponding to all the TRXs. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS. 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 the TRXs Difference between the values of the average sensitivity of the MS and BTS.
If you select a record of a summarized TRX in Area (8), the information about all the TRXs in the selected cell is displayed in Area (9). For details, see Table 9-31.
9-74
Issue 03 (2010-06-30)
9 GSM MR Analysis
Table 9-31 Parameters related to querying TRXs in the MR analysis results of GSM cells (2) Parameter BSC ID BSC Name Cell ID Cell Name TRX ID TRX Name Total Number of Measurement Reports for Full Rate Total Number of Measurement Reports for Half Rate Average Uplink Receive Quality (Full Rate) Average Downlink Receive Quality (Full Rate) Average Uplink Receive Quality (Half Rate) Average Downlink Receive Quality (Half Rate) Average Uplink Receive Level (Full Rate) Average Downlink Receive Level (Full Rate) Average Uplink Receive Level (Half Rate) Average Downlink Receive Level (Half Rate) Average TA Distribution Description Indicates the ID of the BSC that a TRX belongs to. Indicates the name of the BSCs that a TRX of the selected cell belongs to, for example, BSC_1. Indicates the ID of the cell where a TRX is located. Indicates the name of the cell where a TRX is located. Indicates the number of a TRX in the selected cell. Indicates the name of a TRX. Indicates the number of MRs transferred over the full-rate channel. Indicates the number of MRs transferred over the half-rate channel. Indicates the calculation result of the average quality values of the received signals (full rate) of the BTSs corresponding to all the TRXs. Indicates the calculation result of the average quality values of the received signals (full rate) of the MSs corresponding to all the TRXs. Indicates the calculation result of the average received signal quality (half rate) values of the BTSs corresponding to all the TRXs. Indicates the calculation result of the average received signal quality (half rate) values of the MSs corresponding to all the TRXs. Indicates the calculation result of the average levels (full rate) of the BTSs corresponding to all the TRXs. Indicates the calculation result of the average received levels (full rate) of the MSs corresponding to all the TRXs. Indicates the calculation result of the average received levels (half rate) of the BTSs corresponding to all the TRXs. Indicates the calculation result of the average levels (half rate) of the MSs corresponding to all the TRXs. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS.
Issue 03 (2010-06-30)
9-75
9 GSM MR Analysis
Description 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 the TRXs - Difference between the values of the average sensitivity of the MS and BTS.

The information about a selected performance analysis task is displayed in Area (11). For details, see Table 9-32. Table 9-32 Parameters related to the task information Parameter TaskName BEGINTIME ENDTIME Task Creator Description Indicates the name of a selected performance analysis task. Indicates the time when the Nastar starts to generate a task report. Indicates the time when the Nastar stops to generate a task report. Indicates the creator's name of the queried performance analysis task.
The information about the cell corresponding to the selected TRX is displayed in Area (12). For details, see Table 9-33. Table 9-33 Parameters related to the cell information Parameter Cell Object ID Cell Name LAC CI BCCH BCC NCC Cell Layer
9-76
Description Indicates the internal ID of the cell where the selected TRX is located. Indicates name of the cell where the selected TRX is located. Indicates the location area code of the cell where the selected TRX is located. Indicates the ID of the cell where the selected TRX is located. Indicates the frequency transmitted on the BCCH. Indicates the color code of a base station. Indicates the network color code. Indicates the layer where the cell is located.
9 GSM MR Analysis
Parameter Cell Prior Half Rate Supported Frequency Hopping Type GPS Supported EDGE Supported Concentric Circle Supported Base Station Type
Description Indicates the cell priority. Indicates whether half rate is supported. Indicates the type of the frequency hopping, such as the RF hopping and baseband frequency hopping. Indicates whether the GPRS service is supported. Indicates whether the EDGE service is supported. Indicates whether the intelligent underlay-overlay cell function is supported. Indicates the BTS type.
The information about the problematic TRXs and the relevant operation suggestions are displayed in Area (13). For details, see Table 9-34. Table 9-34 Topic categories and relevant operation suggestions Topic Uplink interferen ce Description The uplink-interference results in the high level and poor quality. Suggestion Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, enable the function of uplink-interference analysis to analyze the interference according to the uplink frequency distribution that is measured by TRXs. Change the ARFCN and check whether radio interference sources exist in the coverage area. After the ARFCN is changed, use an MS to search for frequencies within the cell coverage where the TRX is transmitted, and observe the downlink frequency status. Check the cable connections between the combiner and the TRX, and connections in the antenna system. Ensure that the cable connections are proper and secure, and then locate the fault by changing the cable ports, combiner, and TRX.
Issue 03 (2010-06-30)
9-77
9 GSM MR Analysis
l
Weak TRX coverage
Remote coverage
l l
9-78
Issue 03 (2010-06-30)
9 GSM MR Analysis
Description
l
Suggestion
l
Others
9.8.9 Parameters for Comparing GSM MR Analysis Results

This section describes the parameters related to comparing GSM MR analysis results. You can refer to these parameters when comparing GSM MR analysis results.
Parameter Object Name First Total Number of Measurement Reports (Full Rate) Second Total Number of Measurement Reports (Full Rate) Difference of Total Measurement Reports (Full Rate) First Total Number of Measurement Reports (Half Rate)
Issue 03 (2010-06-30)
Description Names of the objects to which two MR results to be compared belong Indicates the number of MRs transferred over the full-rate channel in the previous period. Indicates the number of MRs transferred over the full-rate channel in the next period. Indicates the differences of the number of MRs transferred over the full-rate channel in the previous and next periods. Indicates the number of MRs transferred over the half-rate channel in the previous period.
9-79
9 GSM MR Analysis
Parameter Second Total Number of Measurement Reports (Half Rate) Difference of Total Measurement Reports (Half Rate) First Average Uplink Receive Quality (Full Rate) Second Average Uplink Receive Quality (Full Rate) Average Uplink Receive Quality Difference (Full Rate) First Average Downlink Receive Quality (Full Rate) Second Average Downlink Receive Quality (Full Rate) Average Downlink Receive Quality Difference (Full Rate) First Average Uplink Receive Quality (Half Rate) Second Average Uplink Receive Quality (Half Rate) Average Uplink Receive Quality Difference (Half Rate) First Average Downlink Receive Quality (Half Rate) Second Average Downlink Receive Quality (Half Rate)
Description Indicates the number of MRs transferred over the half-rate channel in the next period. Indicates the differences of the number of MRs transferred over the half-rate channel in the previous and next periods. Indicates the average quality of received signals (full rate) of the BTSs corresponding to all the TRXs in the previous period. Indicates the average quality of received signals (full rate) of the BTSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal quality (full rate) values of the BTSs corresponding to all the TRXs in the previous and next periods. Indicates the average quality of received signals (full rate) of the MSs corresponding to all the TRXs in the previous period. Indicates the average quality of received signals (full rate) of the MSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal quality (full rate) values of the MSs corresponding to all the TRXs in the previous and next periods. Indicates the average quality of received signals (half rate) of the BTSs corresponding to all the TRXs in the previous period. Indicates the average quality of received signals (half rate) of the BTSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal quality (half rate) values of the BTSs corresponding to all the TRXs in the previous and next periods. Indicates the average quality of received signals (half rate) of the MSs corresponding to all the TRXs in the previous period. Indicates the average quality of received signals (half rate) of the MSs corresponding to all the TRXs in the next period.
9-80
Issue 03 (2010-06-30)
9 GSM MR Analysis
Parameter Average Downlink Receive Quality Difference (Half Rate) First Average Uplink Receive Level (Full Rate) Second Average Uplink Receive Level (Full Rate) Average Uplink Receive Level Difference (Full Rate) First Average Downlink Receive Level (Full Rate) Second Average Downlink Receive Level (Full Rate) Average Downlink Receive Level Difference (Full Rate) First Average Uplink Receive Level (Half Rate) Second Average Uplink Receive Level (Half Rate) Average Uplink Receive Level Difference (Half Rate) First Average Downlink Receive Level (Half Rate) Second Average Downlink Receive Level (Half Rate) Average Downlink Receive Level Difference (Half Rate) First Average TA Distribution
Description Indicates the differences of the average received signal quality (half rate) values of the MSs corresponding to all the TRXs in the previous and next periods. Indicates the average received signal levels (full rate) of the BTSs corresponding to all the TRXs in the previous period. Indicates the average received signal levels (full rate) of the BTSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal levels (full rate) of the BTSs corresponding to all the TRXs in the previous and next periods. Indicates the average received signal levels (full rate) of the MSs corresponding to all the TRXs in the previous period. Indicates the average received signal levels (full rate) of the MSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal levels (full rate) of the MSs corresponding to all the TRXs in the previous and next periods. Indicates the average received signal levels (half rate) of the BTSs corresponding to all the TRXs in the previous period. Indicates the average received signal levels (half rate) of the BTSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal levels (half rate) of the BTSs corresponding to all the TRXs in the previous and next periods. Indicates the average received signal levels (half rate) of the MSs corresponding to all the TRXs in the previous period. Indicates the average received signal levels (half rate) of the MSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal levels (half rate) of the MSs corresponding to all the TRXs in the previous and next periods. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS in the previous period.
Issue 03 (2010-06-30)
9-81
9 GSM MR Analysis
Parameter Second Average TA Distribution Average TA Distribution Difference First Link Balance
Description Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS in the next period. Indicates the difference of the weighted average TAs that the MS uses to advance its timings of transmissions to the BTS in the previous and next periods. Indicates the dB value in the previous period, which is 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 MS and BTS. Indicates the dB value in the next period, which is 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 MS and BTS. Indicates the difference between the value of First Link Balance and the value of Second Link Balance.
Second Link Balance
Link Balance Difference
9-82
Issue 03 (2010-06-30)
10 GSM Neighboring Cell Analysis
10
GSM Neighboring Cell Analysis
About This Chapter

This section describes the GSM neighboring cell analysis. The GSM neighboring cell analysis supports the management of neighboring cell analysis tasks, check of the GSM neighboring cell analysis reports, and export of the GSM neighboring cell analysis reports. The Nastar performance analysis system supports the analysis of defined and undefined GSM neighboring cells. By using this function, you can identify and handle the problem of redundant or missing neighboring cell configuration of a cell. Direct display of the information can help you to solve network quality problems that are caused by the redundant or missing neighboring cell configuration. 10.1 Basic Knowledge of GSM Neighboring Cell Analysis This section describes the basic knowledge of the GSM neighboring cell analysis, such as the neighboring cell analysis functions, function application scenarios, and algorithms for neighboring cell analysis. The basic knowledge helps you to perform the operations of GSM neighboring cell analysis. 10.2 Procedure for Using GSM Neighboring Cell Analysis This section describes the process of the GSM neighboring cell analysis. 10.3 Managing GSM Neighboring Cell Analysis Tasks This section describes how to manage the GSM neighboring cell analysis tasks. You can create, modify, delete, suspend, and resume GSM neighboring cell analysis tasks. You can also view the status and execution progress of a task. 10.4 Querying GSM Neighboring Cell Analysis Reports This section describes how to query GSM neighboring cell analysis reports. You can check for the redundant or missing neighboring cells under certain BSCs, and then delete the redundant neighboring cells or add missing neighboring cells. 10.5 Querying GSM Possible Neighboring Cell Analysis Reports This section describes how to query GSM possible neighboring cell analysis reports. With this function, you can learn about all the possible neighboring cells of a GSM cell quickly based on the measurement result of the missing neighboring cell configuration and the analysis of engineering parameters and configuration data. 10.6 Exporting GSM Neighboring Cell Analysis Reports
This section describes how to export GSM neighboring cell analysis reports. You can export the neighboring cell analysis results as .csv or .xls files. In the future, Nastar will provide the function of importing these files to Huawei CME to improve the neighboring relations on the network. 10.7 Exporting GSM Possible Neighboring Cell Analysis Reports This section describes how to export GSM possible neighboring cell analysis reports. You can export the possible neighboring cell analysis results as .csv or .xls files to help improve the neighboring relations on the network. 10.8 Reference for the GSM Neighboring Cell Analysis GUI This section describes the interface for GSM neighboring cell analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of the GSM neighboring cell analysis.
10-2
Issue 03 (2010-06-30)
10.1 Basic Knowledge of GSM Neighboring Cell Analysis

This section describes the basic knowledge of the GSM neighboring cell analysis, such as the neighboring cell analysis functions, function application scenarios, and algorithms for neighboring cell analysis. The basic knowledge helps you to perform the operations of GSM neighboring cell analysis. 10.1.1 GSM Neighbor Cell Analysis Function This section describes the GSM neighboring cell analysis function. This function is used to analyze defined and undefined GSM neighboring cells. By performing this task, you can check and handle the problem of redundant and missing neighboring cell configuration of a cell. Direct display of the relevant analysis information can help you to solve network quality problems that are caused by the redundant and missing neighboring cell configuration. 10.1.2 Algorithms for the GSM Neighboring Cell Analysis This section describes the algorithms for the GSM neighboring cell analysis, such as the algorithms used to check missing neighboring cells and redundant neighboring cells.
10.1.1 GSM Neighbor Cell Analysis Function

This section describes the GSM neighboring cell analysis function. This function is used to analyze defined and undefined GSM neighboring cells. By performing this task, you can check and handle the problem of redundant and missing neighboring cell configuration of a cell. Direct display of the relevant analysis information can help you to solve network quality problems that are caused by the redundant and missing neighboring cell configuration.
Neighboring Cell Analysis

After you set the conditions for checking the redundant and missing neighboring cell configurations, the Nastar performance analysis system analyzes the neighboring cells of a selected cell. The analysis results are displayed on a bar chart. In the results, the defined neighboring cells, undefined neighboring cells, redundant neighboring cells, and missing neighboring cells are displayed in different colors. In addition, the Nastar performance analysis system enables you to export the results of the neighboring cell analysis as files. In the window of the neighboring cell analysis results, you can add missing neighboring cells, delete the redundant neighboring cells, and create the analysis result file. Then, the result file provides the optimization suggestions. You can export the results of the neighboring cell analysis as a CSV or XLS file. The CSV or XLS file can help you to optimize the neighboring cell relations on the network. Before the neighboring cell analysis, check whether a defined neighboring cell of the test cell is of co-BCCH and co-BSIC with other cells. If a defined neighboring cell or an undefined neighboring cell close to the measurement cell is of co-BCCH and co-BSIC with other cells, the network stability and accuracy of neighboring cell analysis cannot be guaranteed.
Requirements for the Network

The network must be stable during the period of collecting data for neighboring cell analysis. Otherwise, the accuracy of the analysis cannot be guaranteed. Table 10-1 describes the network changes and their impacts.
Table 10-1 Network changes and their impacts Network Change Adding or deleting BTSs Antenna data changes such as the changes of the azimuth, tilt angle, and height Changes of the transmit power and the related parameters such as the discontinuous transmission and power control Frequency planning change. For example, a new frequency planning is added to the network. Change of handover relations and parameters Change of BSC topology and other NE topology Impact Affects the cell handover and network coverage. In this case, the analysis result cannot correctly reflect the current network status. Results in the changes of the cell coverage and network interference.
Results in the changes of the cell coverage and network interference.
The change of the configuration data affects the identification of defined cells and undefined cells. In this case, the analysis result cannot correctly reflect the current network status. You are advised to keep the network stable during the data collection period. Affects the statistical results during the period of collecting and optimizing the neighboring relation data. The BSC is responsible for collecting statistical results. Thus, the measurement task cannot be normally performed if the network topology is changed. You are advised to keep the network topology unchanged during the data collection period.
10.1.2 Algorithms for the GSM Neighboring Cell Analysis

This section describes the algorithms for the GSM neighboring cell analysis, such as the algorithms used to check missing neighboring cells and redundant neighboring cells. The algorithms for the GSM neighboring cell analysis are used to check missing neighboring cells and redundant neighboring cells. For details, see Figure 10-1.
10-4
Issue 03 (2010-06-30)
Figure 10-1 Algorithms for the GSM neighboring cell analysis
The algorithms for checking the missing GSM neighboring cells are as follows: 1. Calculate the integrated priority of all the neighboring cells of the measurement cell. The neighboring cells are sorted in descending order of integrated priority. The sequence numbers of neighboring cells are inversely proportional to integrated priorities. If the sequence number of a neighboring cell is smaller than or equal to the value of No. 1, as shown in Area (1) in Figure 10-1, you can infer that the sequence number of this cell is relatively small among the neighboring cells of the measurement cell and that this cell is the direct neighboring cell of the measurement cell. You are advised to configure this cell as a neighboring cell. If the integrated priority of a neighboring cell is greater than TH or equal to TH, and the sequence number of this cell is between the value of No. 1 and the value of No. 2, as shown in Area (2) in Figure 10-1, you can infer that the sequence number of this cell is relatively small in a certain measurement period and that the level of the cell is higher than the relative level and absolute level. In this case, configure this cell as a neighboring cell. If an undefined cell meets either of the second and third requirements, configure the cell as a missing neighboring cell. Otherwise, do not adjust the cell. Calculate the integrated priority of the neighboring cells of the measurement cell. The neighboring cells are sorted in descending order of integrated priority. The sequence numbers of neighboring cells are inversely proportional to integrated priorities. If the sequence number of a neighboring cell is greater than the value of No. 2, as shown in Area (3) in Figure 10-1, you can infer that the sequence number of this cell is relatively large in a certain measurement period and that the level of the cell is rarely higher than the relative level and absolute level. In this case, regard this cell as a redundant neighboring cell and delete it. If an undefined cell meets the second requirement, regard this cell as a redundant neighboring cell and delete it. Otherwise, do not adjust the cell.
2.
3.
4.
l
The algorithms for checking the redundant GSM neighboring cells are as follows: 1.
2.
3.
Issue 03 (2010-06-30)
10.2 Procedure for Using GSM Neighboring Cell Analysis

This section describes the process of the GSM neighboring cell analysis. Figure 10-2 shows the general process of GSM neighboring cell analysis. Figure 10-2 Process of GSM neighboring cell analysis
Start
Set an E2E task
Set an EMS data collection task
Set a neighboring analysis task
Query the neighboring cell analysis report
Export the neighboring cell analysis report End
Table 10-2 describes the process of GSM neighboring cell analysis. Table 10-2 Process of GSM neighboring cell analysis Seria l No. 1 Procedure Querying NE data information Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the neighboring cell analysis is imported to the database.
10-6
Issue 03 (2010-06-30)
Seria l No. 2
Procedure Create an endto-end task corresponding to a neighboring cell analysis task
Description You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a neighboring cell analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a performance data collecting task and a neighboring cell measurement task files collecting task. After the tasks are created, the Nastar periodically obtains the required performance data and neighboring cell measurement task files from M2000, and saves the data as files on the Nastar server. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a performance data importing task. After the task is created, the Nastar periodically imports the performance data files saved on the Nastar server to the database. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a neighboring cell measurement task files importing task. After the task is created, the Nastar periodically imports the neighboring cell measurement task files saved on the Nastar server to the database. You can create a neighboring cell analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required performance data and neighboring measurement data from the Nastar database, and then generates an analysis report through the analysis. You can view the analysis results of the neighboring cell analysis tasks that are successfully performed, add missing neighboring cells, and delete redundant neighboring cells. You can export a frequency analysis report from the Nastar.
Create a performance data collecting task and a neighboring cell measurement task files collecting task Create a performance data importing task Create a neighboring cell measurement task files importing task Create a neighboring cell analysis task
Query neighboring cell analysis reports Export neighboring cell analysis reports
Issue 03 (2010-06-30)
10-7
10.3 Managing GSM Neighboring Cell Analysis Tasks

This section describes how to manage the GSM neighboring cell analysis tasks. You can create, modify, delete, suspend, and resume GSM neighboring cell analysis tasks. You can also view the status and execution progress of a task. 10.3.1 Creating GSM E2E Tasks This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 10.3.2 Creating a GSM Neighboring Cell Analysis Task This section describes how to create a GSM neighboring cell analysis task. By performing neighboring cell analysis tasks, the Nastar performance analysis system analyzes the relevant data in the database at the preset time. By checking the analysis results, you can ascertain the network status and fast locate and solve the network faults. 10.3.3 Modifying a GSM Neighboring Cell Analysis Task You can modify the attributes of a GSM neighboring cell analysis task to meet the new requirement. 10.3.4 Checking a GSM Neighboring Cell Analysis Task This section describes how to check a GSM neighboring cell analysis task. You can check the attributes, execution progress, and execution results of a GSM neighboring cell analysis task.

Prerequisite
l l l
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed.
Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Perform the following operations as required: If You Want to ... Add a GSM neighboring cell measurement task Add a GSM uplink frequency scan task Add a GSM VIP analysis task Add a GSM/UMTS neighboring cell data task Add a GSM cell performance data task Then ... Perform Step 4. Perform Step 5. Perform Step 6. Perform Step 7. Perform Step 8.
Step 4 Perform the following operations to add a GSM neighboring cell measurement task: 1. Set the basic information about the task. a. b. c. 2. 3. In the Task Name field, enter the name of the neighboring cell measurement task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Neighboring Cell Data Task.
l l l l
4.
CAUTION
It is recommended that the number of test cells under one BSC does not exceed 200. If the recommended value is exceeded, certain cells may fail to report complete data. The upper threshold is 400. 5. Optional: Click Frequency Analysis to traverse the three level neighboring cells of the selected cell. The Nastar then analyzes the BCCH frequencies of the traversed neighboring
Issue 03 (2010-06-30)
cells and highlights these BCCH frequencies in the frequency selection area in gray to provide reference for measurement frequency analysis. Traversing of the three level neighboring cells indicates that the Nastar searches for the neighboring cells of the selected cell (neighboring cell A), the neighboring cells of neighboring cells A (neighboring cell B), and the neighboring cells of neighboring cells B (neighboring cell C). All traversed neighboring cells A, B, and C are neighboring cells obtained through the traversing of the three level neighboring cells. 6. Set the ARFCNs.
NOTE
7.
Optional: Set the soft parameters of the neighboring cell measurement task. a. b. Click the Soft Parameter tab. Select Soft Parameter Setting. If you select this option, the soft parameters that you set are valid for this measurement task. c. Set the thresholds of the soft parameters as required. For the detailed description of the soft parameters, see 10.8.3 Parameters for Creating GSM E2E Tasks.
8.
Click Finish. The added neighboring cell measurement task is displayed in the task list.
Step 5 Perform the following operations to create a GSM uplink frequency scan task: 1. Set the basic information about the task. a. b. c. 2. 3. In the Task Name field, enter the name of the uplink frequency scan task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Uplink Interference Analysis Data Task.
4.
10-10
In the Frequency Parameter Setting area, select the ARFCNs to be scanned.

a. b. 5.
From the Frequency Type drop-down list, select the required frequency type. When Frequency Type is set to User Defined in The Frequency Segment, you need to select ARFCNs from the ARFCN list. Selected ARFCNs are displayed in gray.
Click Finish. The added uplink frequency scan task is displayed in the task list.
Step 6 Perform the following operations to add a GSM VIP analysis task: 1. Set the basic information about the task. a. b. c. 2. In the Task Name field, enter the name of the VIP analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM VIP Analysis Data Task.
3.
Click Next. From the VIP group list, select one or multiple VIP groups and select Report Raw Data as required. If you select to report raw data, the original call record data is collected when the VIP KPI overview information is provided.
4.
Click Finish. The added VIP analysis task is displayed in the task list.
Step 7 Perform the following operations to add a GSM/UMTS neighboring cell data task: 1. Set the basic information about the task. a. b. c. 2. In the Task Name field, enter the name of the GSM/UMTS neighboring cell data task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM/UMTS Neighboring Cell Data Task.
3.
Click Finish. The added GSM/UMTS neighboring cell data task is displayed in the task list.
Issue 03 (2010-06-30)
Set the basic information about the task.

a. b. c. 2.
In the Task Name field, enter the name of the cell performance analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Cell Performance Analysis Task.
3. 4.
----End
Postrequisite
To view the attributes of a created E2E task, perform the following operations: 1. 2. Select a task from the task list in the right pane of the E2E Task Management window, and then click Attribute. The Attribute dialog box is displayed. View the related parameters.
NOTE
10.3.2 Creating a GSM Neighboring Cell Analysis Task

This section describes how to create a GSM neighboring cell analysis task. By performing neighboring cell analysis tasks, the Nastar performance analysis system analyzes the relevant data in the database at the preset time. By checking the analysis results, you can ascertain the network status and fast locate and solve the network faults.
Prerequisite
l l
10-12
Context
l l
Tasks of this type can be performed only once. The system supports a maximum of 50 tasks of this type. The time range of the data to be analyzed cannot exceed 7 days.
Procedure
Step 1 Click in the Analysis Task Management window. The Analysis Task Management-New Task dialog box is displayed. Step 2 Set the basic task information such as Task Name , Task Type , and Note . The value of Execution Type can be only Once Task . Step 3 Click Next . Step 4 Set Time Setting for Once Task Data . Step 5 Click Next . Step 6 Select one or multiple objects in the object navigation tree on the Ne Selection tab page.
l
Choose BSC or Cell Group above the navigation tree to display the objects in the navigation tree as required. The system enables you to search for the objects in the navigation tree. You can click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Step 7 Set Neighboring Cell Analysis Parameters , Possible Nerghboring Cell Parameters , and
Result Show Parameters on the Parameter Setting tab page. Step 8 Click Complete . ----End
Postrequisite
l
Deleting a task You can delete a neighboring cell analysis task that is not required so that you can save system resources.
NOTE
1.
Choose GSM Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function , the task list on the right displays all the performance analysis tasks.
2. 3.
Suspending a task This section describes how to suspend a neighboring cell analysis task. To delay the task execution, you can suspend a neighboring cell analysis task that is in the Idle state. After this operation, the neighboring cell analysis task is in the suspended state.
NOTE
The system can schedule only the neighboring cell analysis tasks that are not suspended.
1.
2.
Select a task from the task list in the upper-right pane, and then click Only the tasks whose Status
10-14
Issue 03 (2010-06-30)
is Idle can be suspended. Otherwise, the

l
button is unavailable.
Resuming a task You can resume a suspended neighboring cell analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the neighboring cell analysis tasks that are in the idle state can be scheduled by the system.
1.
2.
Select a task from the task list in the upper-right pane, and then click The task can be performed only when its Status is Suspended . If the task is not in the suspended state, the button is unavailable.
10.3.3 Modifying a GSM Neighboring Cell Analysis Task

You can modify the attributes of a GSM neighboring cell analysis task to meet the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. A GSM neighboring cell analysis task is created.
Context
Procedure
Step 1 Choose GSM Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
. The

l
For details about the parameters, see 10.8.4 Parameters for Creating and Modifying Neighboring GSM Cell Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the navigation tree of objects, and the Neighboring Optimization Parameter parameter.
10.3.4 Checking a GSM Neighboring Cell Analysis Task

This section describes how to check a GSM neighboring cell analysis task. You can check the attributes, execution progress, and execution results of a GSM neighboring cell analysis task.
Prerequisite
l l
You have logged in to the Nastar client. A GSM neighboring cell analysis task is created.
Procedure
Step 1 Choose GSM Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: Purpose Checking the attributes of a neighboring cell analysis task Operation Select a task from the task list in the upperright pane. Double-click the task or click You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 10.3.3 Modifying a GSM Neighboring Cell Analysis Task. Checking the execution progress of the active task Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column. .
10-16
Issue 03 (2010-06-30)
Purpose Checking the task execution results
Operation Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view all the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
10.4 Querying GSM Neighboring Cell Analysis Reports

This section describes how to query GSM neighboring cell analysis reports. You can check for the redundant or missing neighboring cells under certain BSCs, and then delete the redundant neighboring cells or add missing neighboring cells.
Prerequisite
Procedure
Step 1 Click the GSM Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
Step 2 Select a task from the task list in the upper right pane. All the analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose GSM Neighboring Cell Analysis from the shortcut menu. The GSM Neighboring Cell Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell from the test cell list in Area (1) in the GSM Neighboring Cell Analysis window.
l
For the specific rules of area division, see 10.8.1 Interface Description: GSM Neighboring Cell Analysis. The defined neighboring cells of the selected cell are displayed in the defined neighboring cell list in Area (2). The undefined neighboring cells of the selected cell are displayed in the undefined neighboring cell list in Area (3). The Nastar determines the redundant neighboring cells, missing neighboring cells, cochannel neighboring cells, and neighboring cells requiring no operations according to the neighboring-cell analysis algorithms. It also provides the relevant operations. For details about the neighboring-cell analysis algorithms, see 10.1.2 Algorithms for the GSM Neighboring Cell Analysis. If User Modify is selected for a row in the defined neighboring cell list and undefined neighboring cell list, the Nastar saves the modified list automatically. Thus, you can view the modified information the next time you open the analysis report. If no modification is made, the Nastar displays the list in the database the next time you open the analysis report. The file with the modification automatically saved is stored in the installation path of the client. This file is deleted automatically when the corresponding task is deleted. If the possible neighboring cell table of the neighboring cell analysis report is modified (see the description in 10.5 Querying GSM Possible Neighboring Cell Analysis Reports), the information in the undefined neighboring cell list is replaced by the information about the most possible neighboring cell selected in the preceding possible neighboring cell analysis the next time the neighboring cell analysis report is opened. The following fields in the report are updated: Undefined Neighboring Cell Name, CGI, Service Type of Neighboring Cell, and Distance (km). You can double-click the defined neighboring cell list area or the undefined neighboring cell list to zoom in on the area, and then double-click the area again to restore the area to the original size.
In the lower pane, that is, Area (4), the undefined neighboring cells, defined neighboring cells, redundant neighboring cells, and missing neighboring cells are illustrated in different colors. You can select a parameter from the drop-down list box above Area (4). Then, the parameter values corresponding to each neighboring cell are displayed on a line chart. The chart in Area (4) displays only the top 32 neighboring cells with the highest integrated priorities.
----End
Postrequisite
l
The system enables you to export the query results. Right-click the query result list and choose Save As. After setting the save path and filename, click Save. Then, the query results are saved as a CSV or XLS file.
10-18

l
To query chart properties, and save, print, and resize the chart in the chart area, perform the following operations:
10.5 Querying GSM Possible Neighboring Cell Analysis Reports

This section describes how to query GSM possible neighboring cell analysis reports. With this function, you can learn about all the possible neighboring cells of a GSM cell quickly based on the measurement result of the missing neighboring cell configuration and the analysis of engineering parameters and configuration data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the function of possible neighboring cell analysis. The possible neighboring cell analysis task is executed successfully.
Procedure
Step 1 Click the GSM Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. All the analysis results of the selected task are displayed in the lower right pane.
Step 3 Right-click a result record and then choose Possible Neighboring Cell Analysis Result. The GSM Possible Neighboring Cell Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell from the possible neighboring cell overview table in the GSM Possible Neighboring Cell Analysis window.
l
For the specific rules of area division, see 10.8.2 Interface Description: Possible Neighboring GSM Cell Analysis. All the possible neighboring cells of the selected cell are displayed in the possible neighboring cell confirmation table on the right. If Is Adopt is selected for a possible neighboring cell, the possible neighboring cell serves as the most possible neighboring cell of the test cell. In addition, the information of the corresponding field in the possible neighboring cell overview table is replaced by the information about this possible neighboring cell in the possible neighboring cell confirmation table. For details, see 10.8.6 Parameters for Querying the Analysis Reports of Possible Neighboring GSM Cells.
To add a possible neighboring cell to a test cell, do as follows: 1. 2. above the possible neighboring cell confirmation table to open the GSM Click Possible Neighboring Cell Analysis dialog box. Select one or multiple cells from the Cell List navigation tree, and then click Confirm.
To export all information in the possible neighboring cell overview table, see 10.7 Exporting GSM Possible Neighboring Cell Analysis Reports. If the possible neighboring cell table of a neighboring cell analysis report is modified, the information in the undefined neighboring cell list is replaced by the information about the most possible neighboring cell selected in the preceding possible neighboring cell analysis the next time the neighboring cell analysis report is opened. The following fields in the report are updated: Undefined Neighboring Cell Name, CGI, Service Type of Neighboring Cell, and Distance (km).
----End
Postrequisite
l
The Nastar supports the export of the query results. Right-click the query result list and then choose Save As from the shortcut menu. After setting a file name and specifying the save path, click Save to save the query results to a .csv or .xls file. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
10-20
Issue 03 (2010-06-30)
10.6 Exporting GSM Neighboring Cell Analysis Reports

This section describes how to export GSM neighboring cell analysis reports. You can export the neighboring cell analysis results as .csv or .xls files. In the future, Nastar will provide the function of importing these files to Huawei CME to improve the neighboring relations on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the GSM neighboring cell analysis reports.
Procedure
l Perform the following operations as required: If You Want to ... Export the neighboring cell overview Then ... 1. Click in the GSM Neighboring Cell Analysis window. The Save As dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. The main information contained in the .csv or .xls files is task name, creator, start time of the result, end time of the result, and related information about the test cells. Export the neighboring cell optimization result of a test cell 1. Click in the GSM Neighboring Cell Analysis window. The Save As dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. The main information contained in the .csv or .xls files is task name, creator, start time of the result, end time of the result, BSC serving the test cell, number and name of the test cell, and defined neighboring cell and undefined neighboring cell information.
If You Want to ... Export the possible neighboring cell analysis result
Then ... 1. Click in the GSM Neighboring Cell Analysis window. The Save As dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. The main information contained in the .csv or .xls files is task name, creator, start time of the result, end time of the result, and related information about possible neighboring cells of the test cell.
10-22
Issue 03 (2010-06-30)
If You Want to ...
Then ...
Export all the possible neighboring cell 1. Click in the analysis results GSM Neighboring Cell Analysis window. The Save As dialog box is displayed. If the analysis result data amount of all the neighboring cells is large, you need to wait for a while before the dialog box is displayed. 2. Specify a save path for the file. Then, click Save. 3. In the displayed Confirm dialog box, confirm whether to add or delete the bidirectional neighboring cells.
l
Click Yes to include the modified records (for which User Modify are selected) in the exported neighboring cell analysis result. In this case, a column named Is Bidirectional Neighboring Cell is added to the exported result. Y is filled in this column for all the bidirectional neighboring cells. In addition, the bidirectional neighboring cell records are added to the end of the result table. For example, in the defined neighboring cell list of test cell A, neighboring cell B is a redundant neighboring cell of cell A. If User Modify is selected, it indicates that cell A and cell B are redundant neighboring cells of each other. It is recommended that bidirectional neighboring cells be deleted. This record is exported to the neighboring cell analysis result.
Click No to ignore the modified records in the neighboring cell analysis result. In this case, these records are not exported to the result file.
Issue 03 (2010-06-30)
10-23
If You Want to ...
Then ... You are only allowed to save all the neighboring cell analysis results as .xls files on the basis of BSC. The neighboring cell analysis results of each BSC correspond to one .xls file. The naming convention is task name_NE name_NCS.xls.
Export all the neighboring cell analysis 1. Click in the results in the CME format GSM Neighboring Cell Analysis window. The Save As dialog box is displayed. 2. Set the file name, file type, and save path. Then, click Save. The files are saved in folders.
l
The data of redundant neighboring relations and external redundant neighboring cells of each BSC is saved under the Save path/File name/CME/ data/ DELETE_GSMNA_CMEResult directory. The data of missing neighboring relations and external missing neighboring cells of each BSC is saved under the Save path/File name/CME/ data/ADD_GSMNA_CMEResult directory.
All the data can be exported to .xls files in the CME format so that the data can be imported to the CME and then be issued to NEs.
NOTE
l l l l
Exporting neighboring cell overview refers to exporting the information about all the test cells involved in the selected analysis task. Exporting the neighboring cell optimization result of a test cell refers to exporting the information about the defined and undefined neighboring cells of a specified test cell. Exporting the possible neighboring cell analysis result refers to exporting the information about the possible neighboring cells of a specified test cell. Exporting all the neighboring cell analysis results refers to exporting the information about the defined and undefined neighboring cells of all test cells.
----End
10-24
Issue 03 (2010-06-30)
10.7 Exporting GSM Possible Neighboring Cell Analysis Reports

This section describes how to export GSM possible neighboring cell analysis reports. You can export the possible neighboring cell analysis results as .csv or .xls files to help improve the neighboring relations on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the GSM possible neighboring cell analysis reports.
Context
Exporting the results of the possible neighboring cell analysis refers to the export of all the information in the possible neighboring cell overview table of the possible neighboring cell analysis report.
Procedure
Step 1 In the GSM Possible Neighboring Cell Analysis window, click neighboring cell overview table to open the Save As dialog box. above the possible
Step 2 Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. ----End
10.8 Reference for the GSM Neighboring Cell Analysis GUI

This section describes the interface for GSM neighboring cell analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of the GSM neighboring cell analysis. 10.8.1 Interface Description: GSM Neighboring Cell Analysis This section describes the interface for GSM neighboring cell analysis. Before performing relevant operations, familiarize yourself with the rules for dividing areas on the interface. 10.8.2 Interface Description: Possible Neighboring GSM Cell Analysis This section describes the interface for possible neighboring GSM cell analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 10.8.3 Parameters for Creating GSM E2E Tasks This section describes the parameters for creating GSM E2E tasks. You can refer to the description when creating a GSM E2E task. 10.8.4 Parameters for Creating and Modifying Neighboring GSM Cell Analysis Tasks This section describes the parameters for creating and modifying neighboring GSM cell analysis tasks. You can refer to the description when creating and modifying a neighboring GSM cell analysis task.
10.8.5 Parameters for Querying the Analysis Reports of Neighboring GSM Cells This section describes the parameters for querying the analysis reports of neighboring GSM cells. You can refer to the description when querying the analysis reports of neighboring GSM cells. 10.8.6 Parameters for Querying the Analysis Reports of Possible Neighboring GSM Cells This section describes the parameters for querying the analysis reports of possible neighboring GSM cells. You can refer to the description when querying the analysis reports of possible neighboring GSM cells.
10.8.1 Interface Description: GSM Neighboring Cell Analysis

This section describes the interface for GSM neighboring cell analysis. Before performing relevant 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 shown in Figure 10-3. Figure 10-3 Interface for the neighboring cell analysis
No. Name (1) List of current measurement cell information List of defined neighboring cells
Description Displays the information about the current measurement cell. Displays all the defined neighboring cells of the cell selected in Area (1)
(2)
10-26
Issue 03 (2010-06-30)
No. Name (3) List of undefined neighboring cells
Description Displays all the undefined neighboring cells of the cell selected in Area (1) Displays the information about all the neighboring cells of the selected measurement cell in histogram mode or in line chart
NOTE
l If the names of two or more cells are the same,
(4)
Chart area
the cell names on the X-Axis are displayed as CellName(BCCH,BSIC).

l If the cell names cannot be found, the cell names
on the X-Axis are displayed as (BCCH,BSIC).
(5)
Button area
Four buttons are provided to export all information about the neighboring cell, the neighboring cell optimization results of the measurement cell, the analysis results of possible neighboring cells, and all neighboring cell optimization results.
10.8.2 Interface Description: Possible Neighboring GSM Cell Analysis

This section describes the interface for possible neighboring GSM cell analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. The possible neighboring cell analysis result is displayed in tables, which consist of a possible neighboring cell overview table and a possible neighboring cell confirmation table, as shown in Figure 10-4.
Issue 03 (2010-06-30)
10-27
Figure 10-4 Interface of analyzing possible neighboring GSM cells
No. Name (1) Possible neighboring cell overview table
Description Displays the aggregation information of possible neighboring cells of all the cells involved in the task in a table. Displays all the possible neighboring cells of the cells selected in Area (1).
(2)
Possible neighboring cell confirmation table


Parameter Basic information Task Name OSS Name E2E Task List Description Indicates the name of a neighboring cell measurement task. Indicates the name of the OSS related to the task. Select the GSM Neighbor Cell Data Task node.
10-28
Issue 03 (2010-06-30)
Parameter Measurement information Start Time
Description Indicates the time when the task starts to run. The start time must be later than the current time. By default, the start time is five minutes later than the current system time. Persist Time (Minute) Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 65535. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15. Measurement 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 15 minutes. For example, if this parameter is set to 2, the measurement time of each ARFCN is 215 minutes, that is, 30 minutes. Measurement step length 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 to the minimum rest step of the selected cell. Cell Object Displays the frequency information. Indicates the cell related to the neighboring cell measurement task. Indicates the set of ARFCNs to be measured. The ARFCNs are classified by group. The number of ARFCNs of each group is determined by Measure Step.
NOTE
Step.
Soft parameter information
Set the soft parameters. RSSThres
If you select this option, the soft parameters that you set are valid for this measurement task. The value is an integer from 0 to 127. When the difference between the levels of the neighboring cell and the serving cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one.
Issue 03 (2010-06-30)
10-29
Parameter ASSThres
Description The value is an integer from 0 to 63. When the level of the neighboring cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one. NCELLINTERFLE VELTHRES 1-7 You can set the thresholds of interference level for seven neighboring cells. The value is an integer from 0 to 127. When the difference between the levels of the neighboring cell and the serving cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one.
NOTE
l l l

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Time (Minute) Description Indicates the name of a uplink frequency scanning task. Indicates the name of the OSS related to the task. Select the GSM Uplink Interference Analysis Data Task node. Indicates the total duration that a measurement task is performed. The value is an integer from 5 to 1440.
10-30
Issue 03 (2010-06-30)
Parameter Band
Description Indicates the frequency band used by a cell. The M2000 supports the scanning of the following frequency bands:
l l l l l l
l

Issue 03 (2010-06-30)
10-31
Parameter End Time
Description

10-32
Issue 03 (2010-06-30)
Parameter NE Object

Issue 03 (2010-06-30)
10-33
10.8.4 Parameters for Creating and Modifying Neighboring GSM Cell Analysis Tasks
This section describes the parameters for creating and modifying neighboring GSM cell analysis tasks. You can refer to the description when creating and modifying a neighboring GSM cell analysis task.
Parameter Basic information Task Name Description Indicates the name of a neighboring cell analysis task. Value range:
l l
A maximum of 60 characters Characters not allowed: ` ~ ! @ # $ % ^ & * ( ) +={}[]\|;':,.?/<>" Unique and not null Case sensitive
l l
Choose GSM Neighboring Cell Analysis Task from the navigation tree.
l
One-time task: The system executes the created tasks only once at the specified time. Periodic task: The system executes the created tasks at the preset time.
Note
Provides the description of the task. Value range:

l l
Time information
Begin Date
Indicates time for starting a task. The start time must be later than the current server time. You can either enter the time value in this field, or click and select the date and time in the Date Selection dialog box. This parameter is valid for only periodic tasks.
Cycle
l l
Unit: day Value range: 1 to 9999
This parameter is valid for only periodic tasks.
10-34
Issue 03 (2010-06-30)
Description Indicates the number of times a periodic task is executed. If this parameter is set to 0, you can infer that the task is executed all the time. Value range: 0 to 9999 This parameter is valid for only periodic tasks. Data Time Scope Indicates the time range of the data to be analyzed. If this parameter is set to a value earlier than the current time, the analysis task is executed immediately after the task is created. If this parameter is set to a value later than the current time, the analysis task will be executed at the time within the set time range. The start time must precede the end time. You can either enter the time value in this field, or and select the date and time in the Date click Selection dialog box. This parameter is valid for only one-time tasks. Task Start At Indicates the time when the analysis task is executed. The time specified in this field must not precede the end time specified in the Data Time Scope field. Time
l
All day: The task is executed every day within the selected time range. Specify: The task is executed at the specified period of time within the time range every day. Time periods cannot overlap. The start time of the next time segment must be later than or the same as the end time of the current time segment.
Object information
BSC Cell Group
If you select this option, the navigation tree displays all the BSCs of the entire network. If you select this option, the navigation tree displays all the cell groups of the entire network. Indicates the lower threshold of the neighboring cell sequence. All the undefined neighboring cells whose sequence numbers are smaller than or equal to the value of this parameter are regarded as missing neighboring cells. This parameter can be set to any integer from 1 to 32. The default value is 6.
Parameter information
Neighboring Cell Rank No.1
Issue 03 (2010-06-30)
10-35
Parameter Neighboring Cell Integrated Priority TH
Description Indicates the limitation on the number of undefined neighboring cells. This parameter can be set to any integer from 1 to 32. The default value is 6. Constraint for BA2 Table Len Indicates the limitation on the number of test ARFCNs of neighboring cells. This parameter can be set to any integer from 1 to 32. The default value is 20. Constraint for Neighboring Cell Table Len Indicates the limitation on the number of neighboring cells. This parameter can be set to any integer from 0 to 64. The default value is 50. This parameter and Constraint for BA2 Table Len are used to determine the redundant neighboring cells. If these two conditions are not met, the system searches for redundant neighboring cells constantly until the two conditions are met. Hand Over Times Constraint The neighboring cells where the number of handover requests is smaller than the value of this parameter are regarded as redundant neighboring cells. This parameter can be set to any integer from 0 to 9999. The default value is 10. Relative Percent Constraint The neighboring cells whose relative percentage is smaller than the value of this parameter are regarded as redundant neighboring cells. This parameter can be set to 0 to 100%. The default value is 5%. Omni Gain Indicates the omnidirectional gain of an antenna. This parameter can be set to any integer from 0 to 15. The default value is 11. Unit: dBi Directive Gain Indicates the directional gain of an antenna. This parameter can be set to any integer from 0 to 25. The default value is 17. Unit: dBi Display Number of Undefined Neighboring Cells Indicates that only the TopN undefined neighboring cells are displayed. N can be any integer from 20 to 50. The default value is 30.
10-36
Issue 03 (2010-06-30)
10.8.5 Parameters for Querying the Analysis Reports of Neighboring GSM Cells
This section describes the parameters for querying the analysis reports of neighboring GSM cells. You can refer to the description when querying the analysis reports of neighboring GSM cells.
NOTE
For details about the rules for dividing areas, see 10.8.1 Interface Description: GSM Neighboring Cell Analysis.
Parameters Related to the Information About a Test Cell

Parameter BSC Where Test Cell Is Located Test Cell Name Total Number of Measurement Reports Number of Redundant Neighboring Cells Percentage of Measurement Report on Redundant Neighboring Cells (%) Number of Not Configured Neighboring Cells Percentage of Measurement Report on Not Configured Neighboring Cells (%) LAC CI BCCH BSIC Test Cell ID Description Indicates the name of the BSC that a test cell belongs to, for example, BSC_1. Indicates the name of a test cell, for example, Cell_1. Indicates the total number of MRs received by a test cell.
Indicates the number of redundant neighboring cells of the selected test cell. Indicates the sum of the integrated priority of the redundant neighboring cells of the selected test cell in Area (2).
Indicates the number of missing neighboring cells of the selected test cell. Indicates the sum of the integrated priority of the missing neighboring cells of the selected test cell in Area (2).
Indicates the location area code of the selected test cell. Indicates the identification code of the selected test cell. Indicates the broadcast control channel of the selected test cell. Indicates the base station identity code of the selected test cell. Indicates the ID of the selected test cell.
Issue 03 (2010-06-30)
10-37
Parameters Related to Defined Neighboring Cells

Parameter Defined Neighboring Cell Name CGI Neighboring Cell BCCH Neighboring Cell BSIC Service Type of Neighboring Cell Suggested Operation Description Indicates the name of a defined neighboring cell of the selected test cell. Indicates the global ID of a defined neighboring cell. Indicates the broadcast control channel of a defined neighboring cell. Indicates the base station identity code of a defined neighboring cell. Indicates whether a defined neighboring cell and a test cell are controlled by different BSCs. Indicates the operation suggestions that the Nastar provides. The options are Redundant Neighboring Cell, Co-Channel Neighboring Cell, or No Operation. User Modify Indicates whether the user operations are recommended. If this option is selected, you are advised to perform modification according to Suggested Operation. Otherwise, no user operation is recommended. Request Number Failure Number Of Handover Successful Percent Of Handover Relative Percentage Indicates the number of handover requests from the current serving cell to another cell. Indicates the number of handover failures among all the handover requests from the current serving cell to another cell. Indicates the handover success rate from the current serving cell to another cell. Indicates the proportion of the total number of handovers that is performed from the current serving cell to a certain neighboring cell to the total number of handovers that is performed from the current serving cell to any neighboring cell. Indicates the integrated priority of a neighboring cell, which is calculated according to the following expression: Number of MRs related to the neighboring cell level that is higher than the relative level and absolute level/Total number of MRs of the test cell x 100%. Indicates the sequence number of a defined neighboring cell of the selected test cell. The sequence number is obtained after all the neighboring cells of the selected test cell are sorted according to the integrated priority. Indicates the distance from the selected test cell to a defined neighboring cell. Indicates the duration that a defined neighboring cell is measured.
Integrated Priority TH (%)
Priority
Distance (km) In BA Time (min)
10-38
Issue 03 (2010-06-30)
Parameter Number of Neighboring Cell Measurement Reports Source Cell Signal Strength (dBm) Neighboring Cell Signal Strength (dBm) Mean S-N Difference (dB) >Relative TH MRs
Description Indicates the number of MRs of a defined neighboring cell.
Indicates the average signal strength of the selected test cell. Indicates the average signal strength of a defined neighboring cell.
Indicates the average difference between the signal strength of the selected test cell and the signal strength of the defined neighboring cell. Indicates the number of MRs related to the information that the difference between the signal strength of the defined neighboring cell and the signal strength of the test cell is greater than the relative level threshold. Indicates the number of MRs related to the information that the signal strength of the defined neighboring cell is greater than the threshold of the absolute level.
>Absolute TH MRs
Parameters Related to Undefined Neighboring Cells

Parameter Undefined Neighboring Cell Name CGI Neighboring Cell BCCH Neighboring Cell BSIC Service Type of Neighboring Cell Suggested Operation Description Indicates the name of an undefined neighboring cell of the selected test cell. Indicates the global ID of an undefined neighboring cell. Indicates the broadcast control channel of an undefined neighboring cell. Indicates the base station identity code of an undefined neighboring cell. Indicates whether an undefined neighboring cell and a test cell are controlled by different BSCs. Indicates the operation suggestions that the Nastar provides. The options are Not Configured Neighboring Cell, Co-Channel Neighboring Cell, or No Operation.
Issue 03 (2010-06-30)
10-39
Parameter User Modify
Description Indicates whether the user operations are recommended. If this option is selected, you are advised to perform modification according to Suggested Operation. Otherwise, no user operation is recommended.
Integrated Priority TH (%)
Indicates the integrated priority of the neighboring cell, which is calculated according to the following expression: Number of MRs related to the neighboring cell level that is higher than the relative level and absolute level/Total number of MRs of the test cell x 100% Indicates the sequence number of an undefined neighboring cell of the selected test cell. The sequence number is obtained after all the neighboring cells of the selected test cell are sorted according to the integrated priority. Indicates the distance from the selected test cell to an undefined neighboring cell. Indicates the duration that an undefined neighboring cell is measured. Indicates the number of MRs of an undefined neighboring cell.
Priority
Distance (km) In BA Time (min) Number of Neighboring Cell Measurement Reports Source Cell Signal Strength (dBm) Neighboring Cell Signal Strength (dBm) Mean S-N Difference (dB) >Relative TH MRs
Indicates the average signal strength of the selected test cell. Indicates the average signal strength of an undefined neighboring cell.
Indicates the average difference between the signal strength of the selected test cell and the signal strength of the undefined neighboring cell. Indicates the number of MRs related to the information that the difference between the signal strength of the undefined neighboring cell and the signal strength of the test cell is greater than the relative level threshold. Indicates the number of MRs related to the information that the signal strength of the undefined neighboring cell is greater than the threshold of the absolute level.
>Absolute TH MRs
10.8.6 Parameters for Querying the Analysis Reports of Possible Neighboring GSM Cells
This section describes the parameters for querying the analysis reports of possible neighboring GSM cells. You can refer to the description when querying the analysis reports of possible neighboring GSM cells.

NOTE
For details about the rules for dividing areas, see 10.8.2 Interface Description: Possible Neighboring GSM Cell Analysis.
Description of Parameters in the Possible Neighboring Cell Overview Table

Parameter BSC Where Test Cell Is Located Test Cell Name Test Cell BCCH Test Cell BSIC Test Cell CGI Neighboring Cell BCCH Neghboring Cell BSIC Neghboring Cell CGI Neghboring Cell Name Neighboring Distance Neghboring Cell Loop Number Angle form Neighboring Cell Direction Predicted DL Signal Strength Get from config data Description Indicates the name of the BSC that a test cell belongs to, for example, ERM3H201. Indicates the name of the test serving cell, for example, Cell_1. Indicates the broadcast control channel of a test cell. Indicates the base station identity code of a test cell. Indicates the global ID of a test cell, for example, 286-01-33034-50712. Indicates the broadcast control channel of a test neighboring cell. Indicates the base station identity code of a test neighboring cell. Indicates the global ID of the selected possible neighboring cell. Indicates the name of the selected possible neighboring cell. Indicates the distance from the test cell to the selected possible neighboring cell. Indicates the number of laps between the selected possible neighboring cell and the test cell, that is, the number of cells between the selected possible neighboring cell and the test cell. Indicates the relative angle between the selected possible neighboring cell and the test cell. Indicates the signal strength of the selected possible neighboring cell based on the dimensioning. Indicates whether the selected possible neighboring cell is obtained from the configuration data.
Issue 03 (2010-06-30)
10-41
Description of Parameters in the Possible Neighboring Cell Confirmation Table

Parameter Whether to Use Description Indicates whether to select the current possible neighboring cell as the most possible neighboring cell of the test cell.
l
If the parameter is selected, it indicates that the current possible neighboring cell serves as the most possible neighboring cell of the test cell. In addition, you need to replace the information about the selected possible neighboring cell in the possible neighboring cell confirmation table with the corresponding information in the possible neighboring cell overview table.
Possible Neighboring Cell CGI replaces Neghboring Cell CGI. Possible Neighboring Cell BSC Name replaces Neghboring BSC. Name of Possible Neighboring Cell replaces Neghboring Cell Name. Distance of Possible Neighboring Cell(m) replaces Neighboring Distance. Number of Possible Neighboring Cell Laps replaces Neghboring Cell Loop Number. Relative Angle of Neighboring Cell() replaces Angle form Neighboring Cell Direction. Predicted Signal Strength of Neighboring Cell(dBm) replaces Predicted DL Signal Strength. Obtain From Configuration Data replaces Get from config data.
If this parameter is not selected, it indicates that the most possible neighboring cell is not determined. In addition, the system clears all the information in the following fields in the possible neighboring cell overview table:

Neghboring Cell CGI Neghboring Cell Name Neighboring Distance Neghboring Cell Loop Number Angle form Neighboring Cell Direction Predicted DL Signal Strength Get from config data
Possible Neighboring Cell CGI Possible Neighboring Cell BSC Name
Indicates the global ID of a possible neighboring cell.
Indicates the name of the BSC that a possible neighboring cell belongs to.
10-42
Issue 03 (2010-06-30)
Parameter Name of Possible Neighboring Cell Distance of Possible Neighboring Cell(m) Number of Possible Neighboring Cell Laps Relative Angle of Neighboring Cell() Predicted Signal Strength of Neighboring Cell (dBm) Obtain From Configuration Data
Description Indicates the name of a possible neighboring cell. Indicates the distance from the test cell to a possible neighboring cell. Indicates the number of laps between the test cell and a possible neighboring cell, that is, the number of cells between the test cell and a possible neighboring cell. Indicates the relative angle between the test cell and a possible neighboring cell. Indicates the signal strength of a possible neighboring cell based on the dimensioning.
Indicates whether the possible neighboring cell is obtained from the configuration data.
Issue 03 (2010-06-30)
10-43
11 Neighboring GSM/UMTS Cell Analysis
11
Neighboring GSM/UMTS Cell Analysis
About This Chapter

This section describes the neighboring GSM/UMTS cell analysis. The neighboring GSM/UMTS cell analysis supports the management of neighboring GSM/UMTS cell analysis tasks, check of the neighboring GSM/UMTS cell analysis reports, and export of the neighboring GSM/UMTS cell analysis reports. The Nastar supports the check of redundant and missing inter-RAT neighboring cells, and thus helps to solve the network quality problems caused by redundant and missing neighboring cell configuration. 11.1 Basic Knowledge of Neighboring GSM/UMTS Cell Analysis This section describes the basic knowledge of the neighboring GSM/UMTS cell analysis, such as the neighboring GSM/UMTS cell analysis function, application scenarios, and algorithms for neighboring cell analysis. The basic knowledge helps you perform the operations of neighboring GSM/UMTS cell analysis. 11.2 Process of Neighboring GSM/UMTS Cell Analysis This section describes the process of neighboring GSM/UMTS cell analysis. 11.3 Managing Neighboring GSM/UMTS Cell Analysis Tasks This section describes how to manage the neighboring GSM/UMTS cell analysis tasks. You can create, modify, delete, suspend, and resume neighboring GSM/UMTS cell analysis tasks. You can also view the status and execution progress of a task. 11.4 Querying Neighboring GSM/UMTS Cell Analysis Reports This section describes how to query neighboring GSM/UMTS cell analysis reports. With this function, you can query all the defined and undefined neighboring UMTS cells of a GSM cell under a BSC as required. In addition, you can calculate the integrated priority of neighboring cells according to the related algorithm and sort the neighboring cells, thus helping users locate redundant and missing neighboring cells in the inter-RAT neighboring cells. 11.5 Querying Possible Neighboring GSM/UMTS Cell Analysis Reports This section describes how to query possible neighboring GSM/UMTS cell analysis reports. With this function, you can learn about all the possible neighboring UMTS cells of a GSM cell quickly based on the measurement result of the missing neighboring cell configuration and the analysis of engineering parameters and configuration data, thus improving the neighboring relations on the network. 11.6 Exporting Neighboring GSM/UMTS Cell Analysis Reports
This section describes how to export neighboring GSM/UMTS cell analysis reports. You can export the neighboring GSM/UMTS cell analysis reports as .csv or .xls files to help improve the neighboring relations on the network. 11.7 Exporting Possible Neighboring GSM/UMTS Cell Analysis Reports This section describes how to export possible neighboring GSM/UMTS cell analysis reports. You can export the possible neighboring cell analysis results as .csv or .xls files to help improve the neighboring relations on the network. 11.8 Reference to the Neighboring GSM/UMTS Cell Analysis Interface This section describes the interface for neighboring GSM/UMTS cell analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of neighboring GSM/UMTS cell analysis.
11-2
Issue 03 (2010-06-30)
11.1 Basic Knowledge of Neighboring GSM/UMTS Cell Analysis

This section describes the basic knowledge of the neighboring GSM/UMTS cell analysis, such as the neighboring GSM/UMTS cell analysis function, application scenarios, and algorithms for neighboring cell analysis. The basic knowledge helps you perform the operations of neighboring GSM/UMTS cell analysis. 11.1.1 Neighboring GSM/UMTS Cell Analysis This section describes the neighboring GSM/UMTS cell analysis function. This function is used to analyze defined and undefined neighboring UMTS cells of GSM cells. By performing this task, you can check and handle the problem of redundant and missing neighboring cell configuration. Direct display of the information provided by this function can help you solve network quality problems that are caused by the redundant and missing neighboring cell configuration. 11.1.2 Algorithm for the Neighboring GSM/UMTS Cell Analysis This section describes the algorithm for the neighboring GSM/UMTS cell analysis, such as the algorithm used to check missing neighboring cells and redundant neighboring cells.
11.1.1 Neighboring GSM/UMTS Cell Analysis

This section describes the neighboring GSM/UMTS cell analysis function. This function is used to analyze defined and undefined neighboring UMTS cells of GSM cells. By performing this task, you can check and handle the problem of redundant and missing neighboring cell configuration. Direct display of the information provided by this function can help you solve network quality problems that are caused by the redundant and missing neighboring cell configuration.
Inter-RAT Neighboring Cell Analysis

After you set the conditions for checking the inter-RAT redundant and missing neighboring cell configurations, the Nastar analyzes the inter-RAT neighboring cells of a selected cell. The analysis results are displayed on a bar chart. In the bar chart, the defined neighboring UMTS cells, undefined neighboring UMTS cells, redundant neighboring UMTS cells, and missing neighboring UMTS cells are illustrated in different colors. In addition, the Nastar enables you to export the results of the inter-RAT neighboring cell analysis as files. In the window of the inter-RAT neighboring cell analysis results, after you add missing neighboring cells and delete the redundant neighboring cells, the Nastar generates the analysis result file, which provides the optimization suggestions. You can export the results of the inter-RAT neighboring cell analysis as a .csv or .xls file, which helps to optimize the neighboring cell relations on the network.

The network must be stable during the period when data for neighboring cell analysis is collected. Otherwise, the accuracy of the analysis cannot be guaranteed. Table 11-1 describes the network changes and their impacts.
Table 11-1 Network changes and their impacts Network Change Adding or deleting BTSs Antenna data change such as change of the azimuth, tilt angle, or height Changes of the transmit power and the related parameters such as the discontinuous transmission and power control Changes in handover relations and parameters Change of BSC topology and other NE topology Impact Affects the cell handover and network coverage. In this case, the analysis result cannot correctly show the current network status. Results in the changes in cell coverage and network interference.
Affects the statistical results during the period of collecting the data about neighboring relations and optimizing neighboring relations. The BSC is responsible for collecting statistical results. Thus, the measurement task cannot be normally performed if the network topology is changed. You are advised to keep the network topology unchanged during the data collection.
11.1.2 Algorithm for the Neighboring GSM/UMTS Cell Analysis

This section describes the algorithm for the neighboring GSM/UMTS cell analysis, such as the algorithm used to check missing neighboring cells and redundant neighboring cells. Based on the information reported by the MS such as the signal level of a cell, the Nastar calculates the total score and then sorts the defined and undefined neighboring UMTS cells. According to the sequence of neighboring UMTS cells and result analysis chart, users can analyze the neighboring cells depending on the actual network situation, and then provide suggestions on the missing neighboring UMTS cell configuration and redundant neighboring UMTS cells to be deleted. The algorithm for the neighboring GSM/UMTS cell analysis is as follows: 1. Calculate the integrated priority of all the neighboring UMTS cells of the test cell. The neighboring cells are sorted in descending order of integrated priority. The sequence numbers of neighboring cells are inversely proportional to integrated priorities. The formula for calculating the integrated priority is as follows: TH% = {(X1 Weight 1 + X2 Weight 2) X0 } 100% Table 11-2 describes the parameters involved in the formula.
11-4
Issue 03 (2010-06-30)
Table 11-2 Parameters in the calculation of integrated priority Parameter TH% X1 Full Name Integrated priority of neighboring cells Number of MRs of neighboring UMTS cells whose absolute level is higher than the threshold 1 Number of MRs of neighboring UMTS cells whose relative level is higher than the threshold 2 Number of MRs of the test cell whose receive level is lower than the threshold 0 Weight of absolute threshold MRs Description Provides a reference for arranging the sequence of neighboring UMTS cells. Indicates the total number of MRs of all the neighboring UMTS cells when the receive level of the test cell is lower than the threshold 0 and the receive level of the UMTS cell is higher than the threshold 1. Indicates the total number of MRs of all the neighboring UMTS cells when the receive level of the test cell is lower than the threshold 0 and the difference of the receive level between the neighboring UMTS cell and the test cell is higher than the threshold 2. Indicates the total number of MRs of the test cell when the receive level of the test cell is lower than the threshold 0. Indicates the weight of the number of MRs where the absolute level of all the neighboring UMTS cells is higher than the threshold 1 during the calculation of integrated priority of neighboring cells. Indicates the weight of the number of MRs where the relative level of all the neighboring UMTS cells is higher than the threshold 2 during the calculation of integrated priority of neighboring cells.
X2
X0
Weight 1
Weight 2
Weight of relative threshold MRs
2.
Determine the missing neighboring cells. When the sequence number of an undefined neighboring UMTS cell is smaller than or equal to Number of Configured Neighboring Cells that is set when creating a neighboring GSM/UMTS neighboring cell analysis task, the neighboring UMTS cell is regarded as a missing neighboring cell.
3.
Determine the redundant neighboring cells. When the sequence number of a defined neighboring UMTS cell is larger than Number of Configured Neighboring Cells that is set when creating a neighboring GSM/UMTS cell analysis task, the neighboring UMTS cell is regarded as a redundant neighboring cell.
11.2 Process of Neighboring GSM/UMTS Cell Analysis

This section describes the process of neighboring GSM/UMTS cell analysis. Figure 11-1 shows the process of neighboring GSM/UMTS cell analysis.
Figure 11-1 Process of neighboring GSM/UMTS cell analysis
Table 11-3 describes the items in the flowchart.
11-6
Issue 03 (2010-06-30)
Table 11-3 Process of neighboring GSM/UMTS cell analysis No. 1 Procedure Querying NE data information Create an endto-end task corresponding to a neighboring GSM/UMTS cell analysis task Create a performance data collecting task Creating a neighboring GSM/UMTS cell measurement task files importing task Creating a neighboring GSM/UMTS cell analysis task Querying neighboring GSM/UMTS cell analysis reports Exporting neighboring GSM/UMTS cell analysis reports Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the neighboring GSM/UMTS cell analysis is imported to the database. You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a neighboring GSM/UMTS cell analysis task. After the task is created, the Nastar issues the MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. Finally, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a performance data collecting task. After the task is created, the Nastar periodically obtains the required performance data from M2000 and saves the data as files on the Nastar server. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a neighboring GSM/UMTS cell measurement task files importing task. After the task is created, the Nastar periodically imports the neighboring GSM/UMTS cell measurement task files saved on the Nastar server to the database. You can create a neighboring GSM/UMTS cell analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required measurement data of neighboring GSM/UMTS cells from the Nastar database, and then generates an analysis report. You can view the analysis results of the neighboring GSM/ UMTS cell analysis tasks that are successfully performed, add missing neighboring cells, and delete redundant neighboring cells. You can export analysis result files in the Nastar performance analysis system.
Issue 03 (2010-06-30)
11-7
11.3 Managing Neighboring GSM/UMTS Cell Analysis Tasks

This section describes how to manage the neighboring GSM/UMTS cell analysis tasks. You can create, modify, delete, suspend, and resume neighboring GSM/UMTS cell analysis tasks. You can also view the status and execution progress of a task. 11.3.1 Creating GSM E2E Tasks This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 11.3.2 Creating a Neighboring GSM/UMTS Cell Analysis Task This section describes how to create a neighboring GSM/UMTS cell analysis task. In a neighboring GSM/UMTS cell analysis task, the Nastar performance analysis system analyzes the relevant data in the Nastar database periodically. By checking the analysis results, you can know the redundant and missing inter-RAT neighboring cells, and thus quickly locate and solve network problems. 11.3.3 Modifying Neighboring GSM/UMTS Cell Analysis Tasks This section describes how to modify a neighboring GSM/UMTS cell analysis task. You can modify the attributes of an existing neighboring GSM/UMTS cell analysis task according to the new requirement. 11.3.4 Querying Neighboring GSM/UMTS Cell Analysis Tasks This section describes how to check a neighboring GSM/UMTS cell analysis task. You can check the attributes of the neighboring GSM/UMTS cell analysis task, execution progress of the task, and the execution results.

Prerequisite
l l l
Context
TIP
11-8
Issue 03 (2010-06-30)
Procedure
l l l l
4.
Issue 03 (2010-06-30)
11-9
CAUTION
NOTE
7.
8.
Click Next to set Time (Minute), that is, the total duration of the measurement task execution. In the Cell Parameter Setting area, select the cell and frequency band to be tested. a. b. From the Frequency Segment drop-down list box, select the frequency band that the cell uses. From the object navigation tree, select the cell related to the task.
11-10
The system enables you to search for the objects in the navigation tree. You can rightclick any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. 4. In the Frequency Parameter Setting area, select the ARFCNs to be scanned. a. b. 5. From the Frequency Type drop-down list, select the required frequency type. When Frequency Type is set to User Defined in The Frequency Segment, you need to select ARFCNs from the ARFCN list. Selected ARFCNs are displayed in gray.
Click Finish. The added uplink frequency scan task is displayed in the task list. Set the basic information about the task. a. b. c. In the Task Name field, enter the name of the VIP analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM VIP Analysis Data Task.
Step 6 Perform the following operations to add a GSM VIP analysis task: 1.
2.
3.
Click Next. From the VIP group list, select one or multiple VIP groups and select Report Raw Data as required. If you select to report raw data, the original call record data is collected when the VIP KPI overview information is provided. Click Finish. The added VIP analysis task is displayed in the task list. Set the basic information about the task. a. b. c. In the Task Name field, enter the name of the GSM/UMTS neighboring cell data task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM/UMTS Neighboring Cell Data Task.
4.
2.
Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.
Issue 03 (2010-06-30)
You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. 3. Click Finish. The added GSM/UMTS neighboring cell data task is displayed in the task list. Set the basic information about the task. a. b. c. 2. In the Task Name field, enter the name of the cell performance analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Cell Performance Analysis Task.
3. 4.
----End
Postrequisite
NOTE
11.3.2 Creating a Neighboring GSM/UMTS Cell Analysis Task

This section describes how to create a neighboring GSM/UMTS cell analysis task. In a neighboring GSM/UMTS cell analysis task, the Nastar performance analysis system analyzes the relevant data in the Nastar database periodically. By checking the analysis results, you can
know the redundant and missing inter-RAT neighboring cells, and thus quickly locate and solve network problems.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the neighboring GSM/UMTS cell analysis task function. The E2E task, collection task, and data import task corresponding to the neighboring GSM/ UMTS cell analysis task are normal. The neighboring GSM/UMTS cell analysis task can be created successfully even if the prerequisites are not met. The execution of the neighboring GSM/UMTS cell analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l l
A neighboring GSM/UMTS cell analysis task can be performed for only once. A maximum of 50 tasks of this type can be created and the time range of the data in a task cannot exceed 7 days. Before you create an analysis task, check and ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name , Task Type , and Note . The value of Execution Type can only be Once Task . Step 3 Click Next . Step 4 Set Time Setting for Once Task Data . Step 5 Click Next .
Step 6 Select one or multiple objects in the object navigation tree on the Ne Selection tab page.
l

Step 7 Set Neighboring Cell Analysis Parameters , Possible Nerghboring Cell Parameters , and Result Show Parameters on the Parameter Setting tab page. Step 8 Click Complete . ----End
Postrequisite
l
Delete a task. You can delete a neighboring cell analysis task that is not required for saving the system resources.
NOTE
1.
Choose GSM/UMTS Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function , the task list on the right displays all the performance analysis tasks.
2. 3.
Select a task from the task list in the upper right pane, and then click In the displayed Confirm dialog box, click OK.
Suspend a task.
11-14
This section describes how to suspend a neighboring cell analysis task. To delay the task execution, you can suspend a neighboring cell analysis task that is in the idle state. After this operation, the state of the neighboring cell analysis task changes to suspended.
NOTE
The Nastar can manage only the neighboring cell analysis tasks that are not suspended.
1.
2.
Select a task from the task list in the upper-right pane, and then click This operation can be performed for only the tasks whose Status is Idle . If a task is not in the idle state, the button is unavailable.
Restoring a task This section describes how to resume a neighboring cell analysis task. You can resume a suspended neighboring cell analysis task to the idle state. Then, the Nastar can perform the resumed task..
NOTE
The Nastar can perform only the neighboring cell analysis tasks that are in the idle state.
1.
2.
Select a task from the task list in the upper-right pane, and then click This operation can be performed for only the tasks whose Status is Suspended . If a task is not in the suspended state, the button is unavailable.
11.3.3 Modifying Neighboring GSM/UMTS Cell Analysis Tasks

This section describes how to modify a neighboring GSM/UMTS cell analysis task. You can modify the attributes of an existing neighboring GSM/UMTS cell analysis task according to the new requirement.
Issue 03 (2010-06-30)
11-15
Prerequisite
l l
You have logged in to the Nastar client. A neighboring GSM/UMTS cell analysis task is created.
Context
Procedure
Step 1 Click the GSM/UMTS Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For description of the parameters, see 11.8.2 Parameters for Creating and Modifying Neighboring GSM/UMTS Cell Analysis Tasks. You are allowed to modify the following parameters: Note in the basic information, Data Time Scope and Task Start At in the time information, information in the object navigation tree, Neighboring Cell Analysis Parameters, Possible Nerghboring Cell Parameters, and Result Show Parameters.
11.3.4 Querying Neighboring GSM/UMTS Cell Analysis Tasks

This section describes how to check a neighboring GSM/UMTS cell analysis task. You can check the attributes of the neighboring GSM/UMTS cell analysis task, execution progress of the task, and the execution results.
Prerequisite
l l
You have logged in to the Nastar client. A neighboring GSM/UMTS cell analysis task is created.
Procedure
Step 1 Click the GSM/UMTS Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required:
If You Want to ...
Then ...
Query the attributes related to the Select a task from the task list in the upperneighboring GSM/UMTS cell analysis task right pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 11.3.3 Modifying Neighboring GSM/UMTS Cell Analysis Tasks. Check the execution progress of the running task Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column. Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
Check the task execution results
----End
Postrequisite
l
Issue 03 (2010-06-30)
11-17
11.4 Querying Neighboring GSM/UMTS Cell Analysis Reports

This section describes how to query neighboring GSM/UMTS cell analysis reports. With this function, you can query all the defined and undefined neighboring UMTS cells of a GSM cell under a BSC as required. In addition, you can calculate the integrated priority of neighboring cells according to the related algorithm and sort the neighboring cells, thus helping users locate redundant and missing neighboring cells in the inter-RAT neighboring cells.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the neighboring GSM/UMTS cell analysis task function. A neighboring GSM/UMTS cell analysis task is executed successfully.
Procedure
Step 1 Click the GSM/UMTS Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result record, or right-click a result record and then choose Analysis Result from the shortcut menu. The GSM/UMTS Neighboring Cell Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell from the test cell list in Area (2) in the GSM/UMTS Neighboring Cell Analysis Task window.
l
The neighboring UMTS cell list on the right in Area (4) displays all the defined and undefined neighboring UMTS cells of the selected cell. The Nastar determines the redundant neighboring cells, missing neighboring cells, and neighboring cells requiring no operations according to the neighboring cell analysis algorithms. It also provides the relevant operation suggestions. For details about the neighboring cell analysis algorithms, see 11.1.2 Algorithm for the Neighboring GSM/UMTS Cell Analysis. If User Modify is selected for a row in the neighboring UMTS cell list, the Nastar saves the modified list automatically. Thus, you can view the modified information the next time you open the analysis report. If no modification is made, the Nastar displays the list in the database the next time you open the analysis report. The file with the modification automatically saved is stored in the installation path of the client. This file is deleted automatically when the corresponding task is deleted. If the possible neighboring cell table of the neighboring cell analysis report is modified (see the description in 11.5 Querying Possible Neighboring GSM/UMTS Cell Analysis
11-18
Issue 03 (2010-06-30)
Reports), the information about the undefined neighboring cells in the neighboring UMTS cell list is replaced by the information about the most possible neighboring cell selected in the preceding possible neighboring cell analysis the next time the neighboring cell analysis report is opened. The following fields in the report are updated: UMTS Neighboring Cell Name, RNC ID, CI, and Distance (km). You can double-click the neighboring UMTS cell list to zoom in on the area, and then doubleclick the area again to restore the area to the original size.
l
----End
Postrequisite
l
11.5 Querying Possible Neighboring GSM/UMTS Cell Analysis Reports

This section describes how to query possible neighboring GSM/UMTS cell analysis reports. With this function, you can learn about all the possible neighboring UMTS cells of a GSM cell
quickly based on the measurement result of the missing neighboring cell configuration and the analysis of engineering parameters and configuration data, thus improving the neighboring relations on the network.
Prerequisite
l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the possible neighboring GSM/UMTS cell analysis task function. A possible neighboring GSM/UMTS cell analysis task is executed successfully.
Procedure
Step 1 Click the GSM/UMTS Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Right-click a result record, and then choose Possible Neighboring Cell Analysis Result. The GSM/UMTS Possible Neighboring Cell Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell from the possible neighboring cell overview table in the GSM/UMTS Possible Neighboring Cell Analysis Task window.
l
All the possible neighboring UMTS cells of the selected cell are displayed in the possible neighboring cell confirmation table on the right. To add a possible neighboring cell to a test cell, do as follows: 1. 2. above the possible neighboring cell confirmation table to open the GSM/ Click UMTS Possible Neighboring Cell Analysis Task dialog box. Select one or multiple cells from the Cell List navigation tree, and then click Confirm.
To export all information in the possible neighboring cell overview table, see 11.7 Exporting Possible Neighboring GSM/UMTS Cell Analysis Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. Right-click the query result list and then choose Save As... from the shortcut menu. After setting a file name and specifying the save path, click Save to save the query results to a .csv or .xls file. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.
11-20
You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
11.6 Exporting Neighboring GSM/UMTS Cell Analysis Reports

This section describes how to export neighboring GSM/UMTS cell analysis reports. You can export the neighboring GSM/UMTS cell analysis reports as .csv or .xls files to help improve the neighboring relations on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the neighboring GSM/UMTS cell analysis reports.
Procedure
l Perform the following operations as required: If You Want to ... Export the neighboring cell overview Then ... 1. Click in the GSM/UMTS Neighboring Cell Analysis Task window. The Save dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. The main information contained in the .csv or .xls files is task name, creator, start time of the result, end time of the result, and related information about the test cells.
Issue 03 (2010-06-30)
11-21
If You Want to ... Export the neighboring cell optimization result of a test cell
Then ... 1. Click in the GSM/UMTS Neighboring Cell Analysis Task window. The Save dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. The main information contained in the .csv or .xls files is task name, creator, start time of the result, end time of the result, BSC serving the test cell, number and name of the test cell, and defined neighboring UMTS cell and undefined neighboring UMTS cell information.
Export all the possible neighboring cell 1. Click in the GSM/UMTS analysis results Neighboring Cell Analysis Task window. The Save dialog box is displayed. If the analysis result data amount of all the neighboring cells is large, you need to wait for a while before the dialog box is displayed. 2. Specify a save path for the file. Then, click Save. You are only allowed to save all the neighboring cell analysis results as .xls files on the basis of BSC. The neighboring cell analysis results of each BSC correspond to one .xls file. The naming convention is task name_NE name_NCS.xls.
NOTE
l l l
Exporting neighboring cell overview refers to exporting the information about all the test cells involved in the selected analysis task. Exporting the neighboring cell optimization result of a test cell refers to exporting the information about the defined and undefined neighboring cells of a specified test cell. Exporting all the neighboring cell analysis results refers to exporting the information about the defined and undefined neighboring cells of all test cells.
----End
11-22
Issue 03 (2010-06-30)
11.7 Exporting Possible Neighboring GSM/UMTS Cell Analysis Reports

This section describes how to export possible neighboring GSM/UMTS cell analysis reports. You can export the possible neighboring cell analysis results as .csv or .xls files to help improve the neighboring relations on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the possible neighboring GSM/UMTS cell analysis reports.
Context
Procedure
Step 1 In the GSM/UMTS Possible Neighboring Cell Analysis Task window, click possible neighboring cell overview table to open the Save dialog box. Step 2 Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. ----End above the
11.8 Reference to the Neighboring GSM/UMTS Cell Analysis Interface

This section describes the interface for neighboring GSM/UMTS cell analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of neighboring GSM/UMTS cell analysis. 11.8.1 Parameters for Creating GSM E2E Tasks This section describes the parameters for creating GSM E2E tasks. You can refer to the description when creating a GSM E2E task. 11.8.2 Parameters for Creating and Modifying Neighboring GSM/UMTS Cell Analysis Tasks This section describes the parameters for creating and modifying neighboring GSM/UMTS cell analysis tasks. You can refer to the description when creating and modifying a neighboring GSM/ UMTS cell analysis task. 11.8.3 Parameters for Querying the Analysis Reports of Neighboring GSM/UMTS Cells This section describes the parameters for querying the analysis reports of neighboring GSM/ UMTS cells. You can refer to the description when querying the analysis reports of neighboring GSM/UMTS cells.
11.8.4 Parameters for Querying the Analysis Reports of Possible Neighboring GSM/UMTS Cells This section describes the parameters for querying the analysis reports of possible neighboring GSM/UMTS cells. You can refer to the description when querying the analysis reports of possible neighboring GSM/UMTS cells.


Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a neighboring cell measurement task. Indicates the name of the OSS related to the task. Select the GSM Neighbor Cell Data Task node. Indicates the time when the task starts to run. The start time must be later than the current time. By default, the start time is five minutes later than the current system time. Persist Time (Minute) Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 65535. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15. Measurement 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 15 minutes. For example, if this parameter is set to 2, the measurement time of each ARFCN is 215 minutes, that is, 30 minutes. Measurement step length 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 to the minimum rest step of the selected cell. Cell Object Indicates the cell related to the neighboring cell measurement task.
11-24
Issue 03 (2010-06-30)
Parameter Displays the frequency information.
Description Indicates the set of ARFCNs to be measured. The ARFCNs are classified by group. The number of ARFCNs of each group is determined by Measure Step.
NOTE
Step.
ASSThres
The value is an integer from 0 to 63. When the level of the neighboring cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one.
NCELLINTERFLE VELTHRES 1-7
You can set the thresholds of interference level for seven neighboring cells. The value is an integer from 0 to 127. When the difference between the levels of the neighboring cell and the serving cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one.
NOTE
l l l
Issue 03 (2010-06-30)
11-25

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Time (Minute) Description Indicates the name of a uplink frequency scanning task. Indicates the name of the OSS related to the task. Select the GSM Uplink Interference Analysis Data Task node. Indicates the total duration that a measurement task is performed. The value is an integer from 5 to 1440. Band Indicates the frequency band used by a cell. The M2000 supports the scanning of the following frequency bands:
l l l l l l
l

Parameter Basic information
11-26
Description Task Name Indicates the name of a VIP analysis data task.
Issue 03 (2010-06-30)
Parameter OSS Name E2E Task List Measurement information Start Time
Description Indicates the name of the OSS related to the task. Select the GSM VIP Analysis Task node. Indicates the time when the VIP analysis data task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the VIP analysis data task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Selected Indicates the NE object related to the VIP analysis data task. If you select this parameter, the content in the Report Raw Data field corresponding to the VIP group can be selected. Indicates the name of a VIP group. Indicates the number of members in the VIP group. Indicates that the raw call data is also collected during the collection of the KPI aggregation information of all VIP objects of the selected VIP groups, thus helping to analyze problems thoroughly. Indicates the description of the VIP group.
Description

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a GSM/UMTS neighboring cell data task. Indicates the name of the OSS related to the task. Select the GSM/UMTS Neighboring Cell Data Task node. Indicates the time when the GSM/UMTS neighboring cell data task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss.
Issue 03 (2010-06-30)
11-27
Parameter End Time
Description Indicates the time when the GSM/UMTS neighboring cell data task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Indicates the NE object related to the GSM/ UMTS neighboring cell data task.

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a cell performance analysis task Indicates the name of the OSS related to the task Select the GSM Cell Performance Data Task node. Indicates the time when the cell performance analysis task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the cell performance analysis task is stopped. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE object Service Type Exception Type Indicates the NE object related to the cell performance analysis task. Indicates service types involved during the exception determination, such as Voice Service. Indicates the exception types involved during the exception determination, such as Short service duration. Indicates the KPIs involved during the exception determination. Indicates the types of exception determination, such as >=.
KPI Determination rule
11-28
Issue 03 (2010-06-30)
Parameter Exception Value
Description Indicates the exception threshold involved during the exception determination, such as 30. The value is an integer from 0 to 65535.
11.8.2 Parameters for Creating and Modifying Neighboring GSM/ UMTS Cell Analysis Tasks
This section describes the parameters for creating and modifying neighboring GSM/UMTS cell analysis tasks. You can refer to the description when creating and modifying a neighboring GSM/ UMTS cell analysis task.
l l
l l
Task Type Execution Type Note
Choose GSM/UMTS Neighboring Cell Analysis Task from the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range:
l l
Time information
Data Time Scope
The start time must precede the end time. You can either enter the time value in this field, or click and select the date and time in the Date Selection dialog box. This parameter is valid for only one-time tasks.
Issue 03 (2010-06-30)
11-29
Parameter Task Start At
Description Indicates the time when the analysis task is executed. The time specified in this field must not precede the end time specified in the Data Time Scope field.
Object information
BSC Cell Group
If you select this option, the navigation tree displays all the BSCs of the entire network. If you select this option, the navigation tree displays all the cell groups of the entire network. Indicates the threshold of the neighboring cell sequence number. All the undefined neighboring cells whose sequence numbers are smaller than or equal to the value of this parameter are regarded as missing neighboring cells. All the defined neighboring cells whose sequence numbers are larger than the value of this parameter are regarded as redundant neighboring cells. This parameter can be set to any integer from 3 to 32. The default value is 26.
Number of Configured Neighboring Cells
Weight of absolute level MRs
Indicates the weight of the number of MRs where the absolute level of all the neighboring UMTS cells is higher than the threshold 1 during the calculation of integrated neighboring cell priority. This parameter can be set to any integer from 1 to 10. The default value is 5.
Weight of relative level MRs
Indicates the weight of the number of MRs where the relative level of all the neighboring UMTS cells is higher than the threshold 2 during the calculation of integrated neighboring cell priority. This parameter can be set to any integer from 1 to 10. The default value is 5.
Omni Gain
Indicates the omnidirectional gain of an antenna. This parameter can be set to any integer from 0 to 15. The default value is 11. Unit: dBi
Directive Gain
Indicates the directional gain of an antenna. This parameter can be set to any integer from 0 to 25. The default value is 17. Unit: dBi
Display Number of Undefined Neighboring Cells
Indicates that only the TopN undefined neighboring cells are displayed. N can be any integer from 20 to 50. The default value is 30.
11-30
Issue 03 (2010-06-30)
11.8.3 Parameters for Querying the Analysis Reports of Neighboring GSM/UMTS Cells
This section describes the parameters for querying the analysis reports of neighboring GSM/ UMTS cells. You can refer to the description when querying the analysis reports of neighboring GSM/UMTS cells.
Description of Parameters About a Test Cell

Parameter BSC Where Test Cell Is Located Test Cell Name Total Number of Measurement Reports Number of Redundant Neighboring Cells Percentage of Measurement Report on Redundant Neighboring Cells (%) Number of Not Configured Neighboring Cells Percentage of Measurement Report on Not Configured Neighboring Cells (%) LAC CI BCCH BSIC Service Type of Test Cell Test Cell ID Description Indicates the name of the BSC that a test cell belongs to, for example, BSC_1. Indicates the name of a test cell, for example, Cell_1. Indicates the total number of MRs received by a test cell.
Indicates the number of redundant neighboring UMTS cells of the current test cell. Indicates the sum of the integrated priority of the redundant neighboring UMTS cells of the current test cell in Area (4).
Indicates the number of missing neighboring UMTS cells of the current test cell. Indicates the sum of the integrated priority of the missing neighboring UMTS cells of the current test cell in Area (4).
Indicates the location area code of the current test cell. Indicates the identification code of the current test cell. Indicates the broadcast control channel of the current test cell. Indicates the base station identity code of the current test cell. Indicates the service type of the current test cell, such as indoor site and outdoor site. Learning the service type of the test cell prevents important neighboring cells from being mistakenly deleted. Indicates the ID of the current test cell.
Issue 03 (2010-06-30)
11-31
Description of Parameters About the Neighboring UMTS Cells

Parameter Neighboring UMTS Cell Name RNC ID CI ARFCN_DL P-SC Suggested Operation Description Indicates the name of a defined or undefined neighboring UMTS cell of the current test cell. Indicates the ID of the RNC that the neighboring UMTS cell belongs to. Indicates the cell identity of a neighboring UMTS cell. Indicates the downlink ARFCNs of a neighboring UMTS cell. Indicates the primary scrambling code of a neighboring UMTS cell. Indicates the operation suggestions that the Nastar provides. The options are Missing Neighboring Cell, Redundant Neighboring Cell, or NA. User Modify Indicates whether the user operations are recommended. If this option is selected, you are advised to perform modification according to Suggested Operation. Otherwise, no user operation is recommended. Integrated Priority TH (%) Indicates the integrated priority of the neighboring UMTS cell, which is calculated according to the following expression: Number of MRs related to the neighboring cell level that is higher than the relative level and absolute level/Total number of MRs of the test cell x 100% Indicates the sequence number of a neighboring UMTS cell of the current test cell. The sequence number is obtained after all the neighboring UMTS cells of the current test cell are sorted according to the integrated priority. Indicates the distance from the current test cell to a neighboring UMTS cell. Indicates the service type of a neighboring UMTS cell, such as indoor site and outdoor site. Learning the service type of the neighboring UMTS cell prevents important neighboring cells from being mistakenly deleted. Indicates the duration that a neighboring UMTS cell is measured. Indicates the number of MRs related to the information that the difference between the signal strength of the neighboring UMTS cell and the signal strength of the test cell is greater than the relative level threshold. Indicates the number of MRs related to the information that the signal strength of the neighboring UMTS cell is greater than the threshold of the absolute level.
Priority
Distance (km) Service Type of Neighboring Cell
In BA Time (min) Number of MRs Higher Than Absolute Threshold Number of MRs Higher Than Relative Threshold
11-32
Issue 03 (2010-06-30)
11.8.4 Parameters for Querying the Analysis Reports of Possible Neighboring GSM/UMTS Cells
This section describes the parameters for querying the analysis reports of possible neighboring GSM/UMTS cells. You can refer to the description when querying the analysis reports of possible neighboring GSM/UMTS cells.

Parameter BSC Where Test Cell Is Located Test Cell Name Test Cell CGI Test Cell BCCH Test Cell BSIC Neighboring Cell ARFCN_DL Neighboring Cell PSC RNC ID of the Selected Possible Neighboring Cell Neghboring Cell Name Neighboring Cell LAC Neighboring Cell CI Neighboring Distance Angle form Neighboring Cell Direction Predicted DL Signal Strength Get from config data Description Indicates the name of the BSC that a test cell belongs to, for example, BSC203. Indicates the name of the test serving cell, for example, Cell_1. Indicates the global ID of a test cell, for example, 286-01-33034-50712. Indicates the broadcast control channel of a test cell. Indicates the base station identity code of a test cell. Indicates the measured downlink ARFCNs of a neighboring UMTS cell. Indicates the measured primary scrambling code of a neighboring UMTS cell. Indicates the number of the RNC that the selected possible neighboring UMTS cell belongs to. Indicates the name of the selected possible neighboring UMTS cell. Indicates the location area code of the selected possible neighboring UMTS cell. Indicates the cell identity code of the selected possible neighboring UMTS cell. Indicates the distance from the test cell to the selected possible UMTS neighboring cell. Indicates the relative angle between the selected possible neighboring UMTS cell and the test cell. Indicates the signal strength of the selected possible UMTS neighboring cell based on the dimensioning. Indicates whether the selected possible neighboring UMTS cell is obtained from the configuration data.
Issue 03 (2010-06-30)
11-33
Parameter Neghboring Cell Loop Number Number of Possible Neighboring Cells in the Possible Neighboring Cell Pairs Percentage of Integrated Priority
Description Indicates the number of laps between the selected possible UMTS neighboring cell and the test cell, that is, the number of cells between the selected possible neighboring UMTS cell and the test cell. Indicates the number of possible neighboring cells in the possible neighboring UMTS cell pair.
Indicates the integrated priority of the neighboring UMTS cell, which is calculated according to the following expression: Number of MRs related to the neighboring UMTS cell level that is higher than the relative level and absolute level/Total number of MRs of the test cell x 100% Indicates the number of MRs related to the information that the difference between the signal strength of the neighboring UMTS cell and the signal strength of the test cell is greater than the relative level threshold. Indicates the number of MRs related to the information that the signal strength of the neighboring UMTS cell is greater than the threshold of the absolute level.
Number of MRs Higher Than Relative Threshold Number of MRs Higher Than Absolute Threshold
11-34
Issue 03 (2010-06-30)

Parameter Whether to Use Description Indicates whether to select the current possible neighboring UMTS cell 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 neighboring UMTS cell of the test cell. In addition, you need to replace the information about the selected possible neighboring cell in the possible neighboring cell confirmation table with the corresponding information in the possible neighboring cell overview table.
Name of Possible Neighboring Cell replaces Neghboring Cell Name. Possible Neighboring Cell BSC Name replaces Neghboring BSC. LAC replaces Neighboring Cell LAC. CI replaces Neighboring Cell CI. Distance of Possible Neighboring Cell(m) replaces Neighboring Distance. Relative Angle of Neighboring Cell() replaces Angle form Neighboring Cell Direction. Predicted Signal Strength of Neighboring Cell(dBm) replaces Predicted DL Signal Strength. Obtain From Configuration Data replaces Get from config data. Number of Possible Neighboring Cell Laps replaces Neghboring Cell Loop Number.

Neghboring Cell Name Neghboring BSC Neighboring Cell LAC Neighboring Cell CI Neighboring Distance Angle form Neighboring Cell Direction Predicted DL Signal Strength Get from config data Neghboring Cell Loop Number
Name of Possible Neighboring Cell
Indicates the cell name of a possible neighboring UMTS cell.
Issue 03 (2010-06-30)
11-35
Parameter LAC CI Distance of Possible Neighboring Cell(m) Relative Angle of Neighboring Cell() Predicted Signal Strength of Neighboring Cell (dBm) Obtain From Configuration Data Number of Possible Neighboring Cell Laps
Description Indicates the location area code of a possible neighboring UMTS cell. Indicates the cell identity of a possible neighboring UMTS cell. Indicates the distance from the test cell to a possible neighboring UMTS cell. Indicates the relative angle between the test cell and a possible neighboring UMTS cell. Indicates the signal strength of a possible neighboring UMTS cell based on the dimensioning.
Indicates whether the possible neighboring UMTS cell is obtained from the configuration data. Indicates the number of laps between the test cell and a possible neighboring UMTS cell, that is, the number of cells between the test cell and a possible neighboring UMTS cell.
11-36
Issue 03 (2010-06-30)
12 GSM Frequency Analysis
12
About This Chapter
GSM Frequency Analysis
GSM frequency analysis involves the following operations on GSM frequencies: managing analysis tasks, querying analysis reports, exporting analysis reports, and querying optimization reports. The system allows for analysis of MR-based interference matrix frequency interference matrix, which helps you adjust the frequencies. You can also create frequency optimization solutions based on the frequency interference matrix and identify the feasibility of a solution by analyzing the frequency optimization results. 12.1 Basic Knowledge of GSM Frequency Analysis This section describes the basic knowledge of the GSM frequency analysis, which covers the following aspects: frequency analysis functions, function application scenarios, frequency analysis algorithms, frequency optimization algorithms, and ARFCN spacing rules. The basic knowledge helps you analyze and optimize the GSM frequencies more efficiently. 12.2 Procedure for Using GSM Frequency Analysis This section describes the process of GSM frequency analysis. 12.3 Managing GSM Frequency Analysis Tasks This section describes how to manage the GSM frequency analysis tasks. You can create, modify, delete, suspend, and resume GSM frequency analysis tasks. You can also view the status and execution progress of a task. 12.4 Querying GSM Frequency Analysis Reports This section describes how to query the GSM frequency analysis reports. You can query the relevant frequency analysis reports as required. Through the information about the interference matrix and frequency interference matrix in the reports, you can know the cells and frequencies with strong interference. The GSM frequency reports can be classified into reports of measurement cells, reports of GSM cell interference matrix, and reports of GSM cell frequency interference matrix. 12.5 Querying the GSM Frequency Optimization Report The Nastar performance analysis system allows you to query GSM frequency optimization reports. You can select a frequency analysis task, select some cells in the interference matrix of this task, set the algorithm parameters for frequency optimization, and then identify the frequency interference when the measurement cell is configured as the current BCCH and TCH among the candidate ARFCNs. In this way, you can set a proper BCCH and proper TCHs for each measurement cell.
12.6 Exporting GSM Interference Analysis Reports This section describes how to export the reports of GSM interference analysis. You can export the reports of frequency analysis as CSV or XLS files. These files can be imported to the CME of Huawei to reduce the cell frequency interference on the network. 12.7 Exporting GSM Frequency Optimization Reports The Nastar performance analysis system allows you to export GSM frequency optimization reports. You can export the queried frequency optimization results to a CSV or an XLS file for future comparison and analysis. 12.8 Reference for the GSM Frequency Analysis GUI This section describes the interface for GSM frequency analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the GSM frequency analysis functions.
12-2
Issue 03 (2010-06-30)
12.1 Basic Knowledge of GSM Frequency Analysis

This section describes the basic knowledge of the GSM frequency analysis, which covers the following aspects: frequency analysis functions, function application scenarios, frequency analysis algorithms, frequency optimization algorithms, and ARFCN spacing rules. The basic knowledge helps you analyze and optimize the GSM frequencies more efficiently. 12.1.1 GSM Frequency Analysis Function This section describes the GSM frequency analysis function. By using this function, you can analyze the cell interference matrix and frequency interference matrix, check the interference between a cell and its neighboring cells, evaluate the results of the frequency planning, and analyze the strongly interfered cells and frequency. 12.1.2 Process of GSM Frequency Analysis This section describes the process of GSM frequency analysis, which helps you perform frequency analysis more efficiently. 12.1.3 Process of GSM Frequency Optimization This section describes the process of GSM frequency optimization, which helps you perform frequency optimization more efficiently. 12.1.4 Spacing Rules of GSM ARFCNs This section describes the spacing rules of GSM ARFCNs, which help you optimize the frequencies more efficiently.
12.1.1 GSM Frequency Analysis Function

This section describes the GSM frequency analysis function. By using this function, you can analyze the cell interference matrix and frequency interference matrix, check the interference between a cell and its neighboring cells, evaluate the results of the frequency planning, and analyze the strongly interfered cells and frequency.
Frequency Analysis
The Nastar performance analysis system provides the interference traffic of each neighboring cell of the measurement cell, and exports the interference matrix of each cell in a report. The output of the interference matrix is based on the real traffic of the network. The system can accurately calculate the ratio of the interference traffic to the cell traffic during the frequency adjustment. Before the frequency analysis, check whether a defined neighboring cell of the measurement cell is of co-channel and co-BSIC with other cells. If a defined neighboring cell or an undefined neighboring cell close to the measurement cell is of co-channel and co-BSIC with other cells, it affects the network stability and accuracy of the frequency analysis. In addition, the Nastar performance analysis system enables you to export the frequency analysis results as a CSV or XLS file.

The network must be stable during the period of collecting data for frequency analysis. Otherwise, the accuracy of the analysis cannot be guaranteed. Table 12-1 describes the network changes and their impacts.
Table 12-1 Network changes and their impacts Network Change Adding or deleting BTSs Antenna data changes such as the changes of the azimuth, tilt angle, and height Changes of the transmit power and the related parameters such as the discontinuous transmission and power control Frequency planning change. For example, a new frequency planning is added to the network Change of handover relations and parameters Change of the BSC topology or other NE topologies Impact Affects the cell handover and network coverage. In this case, the analysis result cannot correctly reflect the current network status. Results in the changes of the cell coverage and network interference.
The change of the configuration data affects the identification of defined cells and undefined cells. In this case, the analysis result cannot correctly reflect the current network status. You are advised to keep the network stable during the data collection period. Affects the statistical results during the period of collecting and optimizing the neighboring relation data. The BSC is responsible for collecting statistical results. Thus, the measurement task cannot be normally performed if the network topology is changed. You are advised to keep the network topology unchanged during the data collection period.
12.1.2 Process of GSM Frequency Analysis

This section describes the process of GSM frequency analysis, which helps you perform frequency analysis more efficiently. The mechanism of frequency analysis is as follows: The system identifies the interference between a measurement cell and its intra-frequency cells and cells on a neighboring frequency, estimates the result of frequency planning, analyzes the cells and ARFCNs with strong interference on the current network. For more information about the mechanism, see Figure 12-1.
12-4
Issue 03 (2010-06-30)
Figure 12-1 Flow chart for frequency analysis

Start
Pre-process data for frequency optimization Check the validity and name of an undefined neighboring cell
Check the name of an undefined neighboring cell Calculate the interference matrices of co-frequency cells
Calculate the ICDM matrices of a test cell
Calculate the frequency interference matrices of a test cell Calculate the matrix of interference from a configured frequency to neighboring cells
End
12.1.3 Process of GSM Frequency Optimization

This section describes the process of GSM frequency optimization, which helps you perform frequency optimization more efficiently. The mechanism for frequency optimization is as follows: The system identifies the frequency interference when a measurement cell in a frequency interference matrix is configured with the current BCCH and TCH among the candidate ARFCNs. Then, it assigns a proper BCCH and proper TCHs for each measurement cell. For more information about the mechanism, see Figure 12-2.
Issue 03 (2010-06-30)
12-5
Figure 12-2 Flow chart for frequency optimization

Start
Generate interference matrix through frequency analysis task
Obtain interference matrix of selected cell
Calculate interference of configured ARFCN
Calculate interference of candidate ARFCNs
Calculate interference over VIP cell
End
12.1.4 Spacing Rules of GSM ARFCNs

This section describes the spacing rules of GSM ARFCNs, which help you optimize the frequencies more efficiently. The spacing rules are as follows:
l
Spacing rules between BCCHs, TCHs, or between a BCCH and a TCH of co-site cells For example, you select three co-site cells: cell A, cell B, and cell C. The space between BCCHs of each cell is set to 2. If you select cell A as the measurement cell, and the BCCHs of cell B and cell C are respectively 16 and 20, the BCCH of cell A should not be 15, 16, 17, 19, 20, or 21. If these ARFCNs are present in the candidate BCCHs, the information about these ARFCNs are highlighted in pink.
Spacing rules between BCCHs, TCHs, or between a BCCH and a TCH of one cell Each cell has only one BCCH, and therefore no spacing rules are required between BCCHs of one cell. The space is 0 by default, that is, no restriction exists. For example, the space between TCHs of one cell is set to 2. If the TCHs of the selected measurement cell are 27, 51, and 61, the TCH of this cell should not be 26, 28, 50, 52, 60, or 62. If these ARFCNs are present in the candidate TCHs, the information about these ARFCNs are highlighted in red.
Spacing rules between BCCHs, TCHs, or between a BCCH and a TCH of a selected cell and its defined neighboring cells For example, the selected cell, namely, cell A, has cell B, cell C, and cell D as its defined neighboring cells. The BCCH space between cell A and its defined neighboring cells is set to 2. If the BCCHs of the neighboring cells are respectively 16, 19, and 27, the BCCH of
12-6
Issue 03 (2010-06-30)
cell A should not be 15, 16, 17, 18, 19, 20, 26, 27, or 28. If these ARFCNs are present in the candidate BCCHs, the information about these ARFCNs are highlighted in orange. The spacing rules between ARFCNs provide a highlighting function. Information about ARFCNs that meet the co-cell rules is highlighted in red, and the legend is . Information about ARFCNs that meet the co-site rules is highlighted in pink, and the legend is . Information about ARFCNs that meet the neighboring cell rules are highlighted in orange, and the legend is . The system arranges the highlighting of ARFCNs by priority in the following descending order: co-cell ARFCNs, co-site ARFCNs, and neighboring cell ARFCNs. If an ARFCN meets multiple conditions, the information about this ARFCN is highlighted in the color with a higher or the highest priority.
12.2 Procedure for Using GSM Frequency Analysis

This section describes the process of GSM frequency analysis. Figure 12-3 shows the general process of GSM frequency analysis. Figure 12-3 Process of GSM frequency analysis
Start
Set an E2E task
Set a frequency analysis task
Check the overview report of a test cell
Check the report of the test cell interference matrix
Check the report of the test cell frequency interference matrix
Export the frequency analysis report End
Issue 03 (2010-06-30)
12-7
Table 12-2 describes the process of GSM frequency analysis. Table 12-2 Process of GSM frequency analysis Seria l No. 1 Procedure Querying NE data information Create an endto-end task corresponding to a neighboring cell analysis task Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the frequency analysis is imported to the database. You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a neighboring cell analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE to start the measurement task for all objects.
NOTE Starting the measurement task for all objects needs to be performed only once. If this operation has been performed, you do not need to create an end-to-end task corresponding to a neighboring cell task again.
Create a performance data collecting task and a neighboring cell measurement task files collecting task Create a performance data importing task Create a neighboring cell measurement task files importing task Create a frequency analysis task
You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a performance data collecting task and a neighboring cell measurement task files collecting task. After the tasks are created, the Nastar periodically obtains the required performance data and neighboring cell measurement task files from M2000, and saves the data as files on the Nastar server. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a performance data importing task. After the task is created, the Nastar periodically imports the performance data files saved on the Nastar server to the database. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a neighboring cell measurement task files importing task. After the task is created, the Nastar periodically imports the neighboring cell measurement task files saved on the Nastar server to the database. You can create a frequency analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required performance data, neighboring cell measurement task files and configuration data from the Nastar database, and then generates an analysis report through the analysis.
12-8
Issue 03 (2010-06-30)
Seria l No. 6
Procedure
l
Description You can view the analysis results of the tasks that are successfully performed, identify the strongly interfered cells and frequency, and evaluate the frequency planning results.
Querying overview reports of measuremen t cells Querying reports of the cell interference matrix Querying reports of the cell frequency interference matrix
Export frequency analysis reports
You can export a frequency analysis report from the Nastar.
12.3 Managing GSM Frequency Analysis Tasks

This section describes how to manage the GSM frequency analysis tasks. You can create, modify, delete, suspend, and resume GSM frequency analysis tasks. You can also view the status and execution progress of a task. 12.3.1 Creating GSM E2E Tasks This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 12.3.2 Creating a GSM Frequency Analysis Task This section describes how to create a GSM frequency analysis task. By performing frequency analysis tasks, the Nastar performance analysis system analyzes the relevant data in the database at the preset time. By checking the analysis results, you can ascertain the network status and fast locate and solve the network faults. 12.3.3 Modifying a GSM Frequency Analysis Task You can modify the attributes of a GSM frequency analysis task to meet the new requirement. 12.3.4 Checking a GSM Frequency Analysis Task This section describes how to check a GSM frequency analysis task. You can check the attributes, execution progress, and execution results of a GSM frequency analysis task

This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the
MML command to the related NE. Then, the NE performs the measurement task and generates the result.
Prerequisite
l l l
Context
TIP
Procedure
l l
Begin Time indicates the start time of the measurement task. Persist Time (Minute) indicates the total duration of the measurement task execution.
12-10

l l
Period indicates the interval at which each group of ARFCNs is measured. Measure Step indicates the number of ARFCNs in a group.
4.
CAUTION
NOTE
7.
8.
Step 5 Perform the following operations to create a GSM uplink frequency scan task:
1.
Set the basic information about the task. a. b. c. In the Task Name field, enter the name of the uplink frequency scan task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Uplink Interference Analysis Data Task.
2. 3.
4.
5.
3.
4.
12-12
Issue 03 (2010-06-30)
3.
Click Finish. The added GSM/UMTS neighboring cell data task is displayed in the task list.
Step 8 Perform the following operations to add a GSM cell performance analysis task: 1. Set the basic information about the task. a. b. c. 2. In the Task Name field, enter the name of the cell performance analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Cell Performance Analysis Task.
3. 4.
----End
Postrequisite
To delete an unnecessary E2E task, perform the following operations: 1.

Issue 03 (2010-06-30)
Select a task from the E2E Task Management window, and then click Delete.
2.
In the displayed Confirm dialog box, click OK.

NOTE
12.3.2 Creating a GSM Frequency Analysis Task

This section describes how to create a GSM frequency analysis task. By performing frequency analysis tasks, the Nastar performance analysis system analyzes the relevant data in the database at the preset time. By checking the analysis results, you can ascertain the network status and fast locate and solve the network faults.
Prerequisite
l l
Context
l l
A frequency analysis task can be performed only once. The system supports a maximum of 50 tasks of this type. The time range of the data to be analyzed cannot exceed 7 days.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can be only Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects in the object navigation tree on the NE Object Selection tab page.
l

12-14
Step 7 Set Frequency Analysis Parameter on the Parameter Setting tab page. Step 8 Click Complete. ----End
Postrequisite
l
Deleting a task You can delete a frequency analysis task that is not required so that you can save system resources.
NOTE
1.
Choose GSM Frequency Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task To delay the task execution, you can suspend a frequency analysis task that is in the idle state. After this operation, the frequency analysis task is in the suspended state.
NOTE
The system can schedule only the frequency analysis tasks that are not suspended.
1.
2.
. button is
Resuming a task You can resume a suspended frequency analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the frequency analysis task that is in the idle state can be scheduled by the system.
1.
2.
Select a task from the task list in the upper-right pane, and then click
12.3.3 Modifying a GSM Frequency Analysis Task

You can modify the attributes of a GSM frequency analysis task to meet the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. A GSM frequency analysis task is created.
Context
Procedure
Step 1 Choose GSM Frequency Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the parameters, see 12.8.4 Parameters for Creating and Modifying GSM Frequency Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the navigation tree of objects, and the Frequency Analysis Parameter parameter.
12.3.4 Checking a GSM Frequency Analysis Task

This section describes how to check a GSM frequency analysis task. You can check the attributes, execution progress, and execution results of a GSM frequency analysis task
Prerequisite
l l
You have logged in to the Nastar client. A GSM frequency analysis task is created.
Procedure
Step 1 Choose GSM Frequency Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
Step 2 Perform the following operations as required: Purpose Checking the attributes of a frequency analysis task Operation Select a task from the task list in the upper-right pane. Double-click the task or click .
You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 12.3.3 Modifying a GSM Frequency Analysis Task. Checking the execution progress of the active task Select a task from the task list in the upper-right pane. Then, you can view the execution progress of the task in the Progress column. Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view all the analysis results of the selected task in the lower-right pane.
Checking the task execution results
----End
Postrequisite
l
Issue 03 (2010-06-30)
12-17
12.4 Querying GSM Frequency Analysis Reports

This section describes how to query the GSM frequency analysis reports. You can query the relevant frequency analysis reports as required. Through the information about the interference matrix and frequency interference matrix in the reports, you can know the cells and frequencies with strong interference. The GSM frequency reports can be classified into reports of measurement cells, reports of GSM cell interference matrix, and reports of GSM cell frequency interference matrix. 12.4.1 Querying the Interference Matrix Report of GSM Measurement Cells This section describes how to query the interference matrix report of the GSM measurement cells. You can query the information about the cells involved in a frequency analysis task. With this function, you can ascertain the information about the interference from co-channel or adjacent-channel cells to a measurement cell and the interference from a measurement cell to the co-channel or adjacent-channel cells. The Nastar automatically sorts the analyzed cells, determines the cells to be optimized, and uses the optimized cells as the basis for later frequency analysis. 12.4.2 Querying the Report of the GSM Cell Interference Matrix This section describes how to query the report of the GSM cell interference matrix. You can query the volume and proportion of the traffic that is affected by the interference from the measurement cell to a neighboring cell with a co-channel or adjacent-channel, and the volume and proportion of the traffic that is affected by the interference from a neighboring cell with a co-channel or adjacent-channel to the measurement cell. The analysis result of the interference matrix helps you learn about the information about the interference between cells and serves as a reference for frequency optimization. 12.4.3 Querying the Report of the GSM Cell Frequency Interference Matrix This section describes how to query the report of the GSM cell frequency interference matrix. You can query the traffic that is affected by the interference between a certain frequency of a measurement cell and the BCCH of its neighboring cell. When querying the interference matrix, you can query the traffic that is affected by the interference between a certain frequency of a measurement cell and the co-channel and adjacent channels of its neighboring cells.
12.4.1 Querying the Interference Matrix Report of GSM Measurement Cells

This section describes how to query the interference matrix report of the GSM measurement cells. You can query the information about the cells involved in a frequency analysis task. With this function, you can ascertain the information about the interference from co-channel or adjacent-channel cells to a measurement cell and the interference from a measurement cell to the co-channel or adjacent-channel cells. The Nastar automatically sorts the analyzed cells, determines the cells to be optimized, and uses the optimized cells as the basis for later frequency analysis.
Prerequisite
12-18
Issue 03 (2010-06-30)
Procedure
Step 1 Choose GSM Frequency Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose Frequency Analysis. The Frequency Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 View the list of measurement cells in the left pane in the displayed window. For details about the relevant parameters, see 12.8.5 Parameters for Querying the Overview Report of the GSM Test Cells. ----End
Postrequisite
l
12.4.2 Querying the Report of the GSM Cell Interference Matrix

This section describes how to query the report of the GSM cell interference matrix. You can query the volume and proportion of the traffic that is affected by the interference from the
measurement cell to a neighboring cell with a co-channel or adjacent-channel, and the volume and proportion of the traffic that is affected by the interference from a neighboring cell with a co-channel or adjacent-channel to the measurement cell. The analysis result of the interference matrix helps you learn about the information about the interference between cells and serves as a reference for frequency optimization.
Prerequisite
Procedure
Step 1 Choose GSM Frequency Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose Frequency Analysis. The Frequency Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a measurement cell from the measurement cell list in the left pane and click the Interference Matrix tab in the right pane. Then, view the information about the interface matrix. For details about the relevant parameters, see 12.8.6 Parameters for Querying the Report of GSM Cell Interference Matrix. ----End
Postrequisite
l
12.4.3 Querying the Report of the GSM Cell Frequency Interference Matrix
This section describes how to query the report of the GSM cell frequency interference matrix. You can query the traffic that is affected by the interference between a certain frequency of a measurement cell and the BCCH of its neighboring cell. When querying the interference matrix, you can query the traffic that is affected by the interference between a certain frequency of a measurement cell and the co-channel and adjacent channels of its neighboring cells.
Prerequisite
Context
The adjacent channels refer to the frequencies before and after a certain frequency of the measurement cell. For example, if a BCCH frequency of a measurement cell is 113, its adjacent channels are 112 and 114.
Procedure
Step 1 Choose GSM Frequency Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose Frequency Analysis. The Frequency Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a measurement cell from the measurement cell list in the left pane and click the Frequency Interference Matrix tab in the right pane. Then, view the information about the frequency interference matrix. For details about the relevant parameters, see 12.8.7 Parameters for Querying the Report of the GSM Cell Frequency Interference Matrix. ----End
Postrequisite
l
12.5 Querying the GSM Frequency Optimization Report

The Nastar performance analysis system allows you to query GSM frequency optimization reports. You can select a frequency analysis task, select some cells in the interference matrix of this task, set the algorithm parameters for frequency optimization, and then identify the frequency interference when the measurement cell is configured as the current BCCH and TCH among the candidate ARFCNs. In this way, you can set a proper BCCH and proper TCHs for each measurement cell.
Prerequisite
Procedure
Step 1 Choose GSM Frequency Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and then choose Frequency Optimization from the shortcut menu. The GSM Frequency Optimization dialog box is displayed.
l
This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. If the query of the GSM frequency optimization report is performed, the default query conditions in this dialog box are the same as the query conditions set in the last query. These default query conditions are saved in the \client\plugins\NastarPA\style\conf\FreqConf directory of the installation path on the client. Each frequency analysis task corresponds to one file.
Step 4 On the NE Object Selection tab page, select one or multiple cells. Step 5 On the Algorithm Parameter tab page, set the rules for spacing between ARFCNs, BCCH frequency range, TCH frequency range, VIP cell group, the ARFCNs used by the algorithm. Then, click OK.
l
In the ARFCN Spacing Rule Setting area, double-click each pane to set the ARFCN spacing rules. For the relevant rules, see 12.1.4 Spacing Rules of GSM ARFCNs. on the right of Set the BCCH ARFCN range, Set the TCH ARFCN range, or Click Set a VIP cell group to select a candidate ARFCN of the BCCH/TCH or select a VIP cell group. The system allows you to set duplicate ARFCNs serving as both BCCH ARFCNs and TCH ARFCNs. That is, the range of BCCH ARFCNs and TCH ARFCNs can be overlapped. If duplicate ARFCNs exist, the Nastar analyzes and optimize ARFCNs and does not filter out the duplicate ARFCNs. The system provides a highlighting function for spacing rules of ARFCNs. For details, see 12.1.4 Spacing Rules of GSM ARFCNs. You can perform frequency optimization based on the current frequency configuration on the existing network or based on the last modified and submitted frequency ARFCN configuration.
Step 6 Select a cell from area (1) in the GSM Frequency Optimization window.
l
For the rules of dividing areas, see 12.8.2 Interface Description: GSM Frequency Optimization. Area (3) displays all the configured and candidate BCCHs and TCHs of the measurement cell selected in area (1).
12-22
Based on the user-defined algorithm parameters, the system calculates and identifies the ARFCNs that meet the co-cell rules, co-site rules, and neighboring cell rules, respectively. This information is fundamental for frequency optimization.
l
Area (4) displays the interfered traffic, external interference traffic, latest total interference traffic, original interference traffic, and total interference traffic in legends of different colors.
Step 7 Optional: Perform either of the following operations on the BCCH or TCH tab page as required: Purpose Adding an ARFCN Operation 1. Select an unconfigured ARFCN, and then select the corresponding option in the Configured column. You can also click upper-left corner of the window. 2. Click for the settings to take effect. in the
Deleting an ARFCN 1. Select a configured ARFCN, and then clear the corresponding option in the Configured column. You can also click in the upper-left corner of the window. 2. Click for the settings to take effect.
After the submission, you can click and to view the interference on each ARFCN before and after the submission, respectively. Thus, you can analyze the change of interference on each ARFCN before and after the frequency optimization and identify the feasibility of this frequency optimization.
NOTE
If an ARFCN is already configured as the BCCH in the selected cell, according to Spacing Rules of ARFCNs, this ARFCN cannot be configured as the TCH even if it is within the range of candidate TCH ARFCNs. Otherwise, the Nastar displays an error message, indicating that the ARFCN is already configured. Each cell can be configured with only one BCCH. Therefore, you need to delete the configured ARFCN before adding a new one. If you have configured an ARFCN as a TCH of the measurement cell, the neighboring ARFCNs of this ARFCN should not be configured as TCHs of this cell. For the ARFCNs that violate the spacing rules, a dialog box is displayed during the ARFCN addition operation. Click Yes to proceed with the operation.
l l l
----End
Postrequisite
l
The system enables you to export the query results. Right-click the query result list and choose Save As. After setting the save path and filename, click Save. Then, the query results are saved as a CSV or XLS file. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Then, type the keywords, that is, the search conditions, in the dialog box. The system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive.
Issue 03 (2010-06-30)
12-23
You can select Up or Down in the Direction area to define the search area.
12.6 Exporting GSM Interference Analysis Reports

This section describes how to export the reports of GSM interference analysis. You can export the reports of frequency analysis as CSV or XLS files. These files can be imported to the CME of Huawei to reduce the cell frequency interference on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have checked the reports of GSM frequency analysis.
Procedure
l Perform the following operations as required: If you need to ... Export the frequency overview information Then ... 1. Click in the Frequency Analysis window. The Save As dialog box is displayed. 2. Set the name, type and save path of the file. Then, click Save. After being saved, a CSV or XLS file is automatically open so that you can view the file conveniently. Export the interference information about a specified cell 1. Click in the Frequency Analysis window. The Save As dialog box is displayed. 2. Set the name, type and save path of the file. Then, click Save. After being saved, a CSV or XLS file is automatically open so that you can view the file conveniently. Export the details about the interference 1. Click in the Frequency Analysis matrix on the entire network window. The Save As dialog box is displayed. 2. Set the name, type and save path of the file. Then, click Save. After being saved, a CSV or XLS file is automatically open so that you can view the file conveniently.
12-24
Issue 03 (2010-06-30)
If you need to ... Export the information about the possible neighboring cells of a measurement cell
Then ... 1. Click in the Frequency Analysis window. The Save As dialog box is displayed. 2. Set the name, type and save path of the file. Then, click Save. After being saved, a CSV or XLS file is automatically open so that you can view the file conveniently.
NOTE
l l
Exporting frequency overview results refers to exporting the information about all the measurement cells involved in the selected analysis task. Exporting the interference information about a specified cell refers to exporting the mutual interference information about a measurement cell and its neighboring cells, and the information about the frequency interference matrix involved in this measurement cell. Exporting the details about the interference matrixes on the entire network refers to exporting the information about frequency interference matrixes involved in all the measurement cells. Exporting the analysis results of possible neighboring cells refers to exporting the information about the possible neighboring cells of a measurement cell.
l l
----End
12.7 Exporting GSM Frequency Optimization Reports

The Nastar performance analysis system allows you to export GSM frequency optimization reports. You can export the queried frequency optimization results to a CSV or an XLS file for future comparison and analysis.
Prerequisite
l l
You have logged in to the Nastar performance analysis client. You have checked the GSM frequency optimization reports.
Procedure
Step 1 In the GSM Frequency Optimization window, click . The Save As dialog box is displayed.
Step 2 Set the filename, file type, and save path. Then, click Save. The saved CSV or XLS file can be open automatically so that you can view it conveniently. ----End
Issue 03 (2010-06-30)
12-25
12.8 Reference for the GSM Frequency Analysis GUI

This section describes the interface for GSM frequency analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the GSM frequency analysis functions. 12.8.1 Interface Description: GSM Frequency Analysis This section describes the interface for GSM frequency analysis. Before performing relevant operations, familiarize yourself with the rules for dividing areas on the interface. 12.8.2 Interface Description: GSM Frequency Optimization This section describes the interface for GSM frequency optimization. You can familiarize yourself with each area to facilitate the operations on this interface. 12.8.3 Parameters for Creating GSM E2E Tasks This section describes the parameters for creating GSM E2E tasks. You can refer to the description when creating a GSM E2E task. 12.8.4 Parameters for Creating and Modifying GSM Frequency Analysis 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. 12.8.5 Parameters for Querying the Overview Report of the GSM Test Cells This section describes the parameters related to querying the overview report of the GSM measurement cells. You can refer to the description when querying the overview report of the GSM measurement cells. 12.8.6 Parameters for Querying the Report of GSM Cell Interference Matrix This section describes the parameters for querying the report of the GSM cell interference matrix. You can refer to the description when querying the report of the GSM cell interference matrix. 12.8.7 Parameters for Querying the Report of the GSM Cell Frequency Interference Matrix This section describes the parameters for querying the report of the GSM cell frequency interference matrix. You can refer to the description when querying the report of the GSM cell frequency interference matrix. 12.8.8 Parameters for Querying GSM Frequency Optimization Reports This section describes the parameters for querying the reports of the GSM frequency optimization.
12.8.1 Interface Description: GSM Frequency Analysis

This section describes the interface for GSM frequency analysis. Before performing relevant operations, 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 about the measurement cells, list of information about interference matrix, and list of information about frequency interference matrix are contained, as shown in Figure 12-4 and Figure 12-5.
12-26
Issue 03 (2010-06-30)
Figure 12-4 Frequency analysis interface (1)
No. Name (1) Measurement Cell Overview Information
Description Displays the information about all taskrelated measurement cells. Displays the traffic interfered by the neighboring cells of the measurement cell selected in Area (1). Displays the traffic affected by the interference from the measurement cell selected in Area (1) to the defined and undefined neighboring cells.
(2)
Neighboring Cell-Measurement Cell Interference Matrix Detail
(3)
Measurement Cell-Neighboring Cell Interference Matrix Detail
Issue 03 (2010-06-30)
12-27
Figure 12-5 Frequency analysis interface (2)
No. Name (4) Frequency Interference Matrix
Description Displays the traffic affected by the interference between the measurement cell selected in Area (1) and its neighboring cells by frequencies.
(5)
BCCH Configured Frequency Cell List Displays the interfered traffic between the measurement cell and its neighboring cells on the same BCCH or between the measurement cell and its neighboring cells with the adjacent BCCH when the frequency selected in Area (4) is set to be the BCCH of the measurement cell. Button area Four buttons are provided to export the overview information about frequency analysis, the interference of specified cell, the interference matrix, and the possible neighboring cell analysis results.
(6)
12.8.2 Interface Description: GSM Frequency Optimization

This section describes the interface for GSM frequency optimization. You can familiarize yourself with each area to facilitate the operations on this interface. The frequency optimization results can be tabulated into general information, BCCH information, and TCH information, respectively. Figure 12-6 shows the interface.
Figure 12-6 Frequency optimization interface
SN Name (1) General information
Description Shows the information about all the measurement cells selected in the current task. Provides six buttons respectively for adding a frequency, deleting a frequency, returning to the previous operation results, switching to the next operation result, exporting the frequency optimization results, and submitting the operation.
(2) Button area
Issue 03 (2010-06-30)
12-29
SN Name (3) BCCH information and TCH information
Description
l
The BCCH table shows all the configured and candidate BCCHs of the measurement cell selected in area (1). The TCH table shows all the configured and candidate TCHs of the measurement cell selected in area (1).
At the top of the ARFCN, Total Interference Traffic, Interfered Traffic, External Interference Traffic, Interference Traffic to VIP Cells, Latest Total Interference Traffic, and Original Total Interference Traffic columns, set the ascending order or descending order. Area (4) displays the images in a new order. (4) Image area Shows the information about frequency interference in the selected cell in a combination of bar charts and line charts. Displays information about the co-cell, cosite, and neighboring cell frequencies in different colors. Displays the algorithm parameters set when frequency optimization is queried. Rules for spacing between frequencies, and VIP cell groups are contained in this area. By default, this area is hidden. You need to
(5) Legends of the highlighting function
(6) Algorithm parameter area
click on the right of the window to display this area.


Parameter Basic information Task Name OSS Name
12-30
Description Indicates the name of a neighboring cell measurement task. Indicates the name of the OSS related to the task.
Issue 03 (2010-06-30)
Parameter E2E Task List Measurement information Start Time
Description Select the GSM Neighbor Cell Data Task node. Indicates the time when the task starts to run. The start time must be later than the current time. By default, the start time is five minutes later than the current system time. Persist Time (Minute) Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 65535. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15. Measurement 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 15 minutes. For example, if this parameter is set to 2, the measurement time of each ARFCN is 215 minutes, that is, 30 minutes. Measurement step length 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 to the minimum rest step of the selected cell. Cell Object Displays the frequency information. Indicates the cell related to the neighboring cell measurement task. Indicates the set of ARFCNs to be measured. The ARFCNs are classified by group. The number of ARFCNs of each group is determined by Measure Step.
NOTE
Step.
Set the soft parameters.
If you select this option, the soft parameters that you set are valid for this measurement task.
Issue 03 (2010-06-30)
12-31
Parameter RSSThres
Description The value is an integer from 0 to 127. When the difference between the levels of the neighboring cell and the serving cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one. ASSThres The value is an integer from 0 to 63. When the level of the neighboring cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one. NCELLINTERFLE VELTHRES 1-7 You can set the thresholds of interference level for seven neighboring cells. The value is an integer from 0 to 127. When the difference between the levels of the neighboring cell and the serving cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one.
NOTE
l l l

12-32
Issue 03 (2010-06-30)
Parameter Band
l l l l l l
l

Issue 03 (2010-06-30)
12-33
Parameter End Time
Description

12-34
Issue 03 (2010-06-30)
Parameter NE Object

Issue 03 (2010-06-30)
12-35
12.8.4 Parameters for Creating and Modifying GSM Frequency Analysis 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.
Parameter Basic Information Task Name Description Indicates the name of a frequency analysis task. Value range:
l l
l l
You need to select GSM Frequency Analysis Task from the Task Type navigation tree. Such a task can be executed only once in a time segment. Indicates the description of the task. Value range:
l l
Time Information
Data Time Scope
The start time should precede the end time. You can either type the time value in this field, or click to select the date and time in the Date Selection dialog box. This parameter is valid for only one-time tasks.
Task Start At
Indicates the start time for executing analysis tasks. The parameter value must be later than the end time of Data Time Scope.
Object Information
BSC Cell Group
If you select this option, the navigation tree displays all the BSCs of the entire network. If you select this option, the navigation tree displays all the cell groups of the entire network. Indicates that only the TopN frequencies of undefined neighboring cells are displayed. N can be any integer from 20 to 50. The default value is 30.
Issue 03 (2010-06-30)
Frequency Parameter Analysis
Display Number of Undefined Neighboring Cells
12-36
Parameter Co-Channel Interference C/I
Description Indicates the threshold of co-channel interference. This parameter can be set to any integer from 6 to 15. The default value is 12. Unit: dB Adjacent-Channel Interference C/A Indicates the threshold of adjacent-channel interference. This parameter can be set to any integer from -12 to 0. The default value is -6. Unit: dB Omni Gain Indicates the omnidirectional gain of an antenna. This parameter can be set to any integer from 0 to 15. The default value is 11. Unit: dbi Directive Gain Indicates the directional gain of an antenna. This parameter can be set to any integer from 0 to 25. The default value is 17. Unit: dbi
12.8.5 Parameters for Querying the Overview Report of the GSM Test Cells
This section describes the parameters related to querying the overview report of the GSM measurement cells. You can refer to the description when querying the overview report of the GSM measurement cells.
Parameter BSC Name Test Cell Test Cell CGI BCCH BSIC Description Indicates the name of the BSC that the measurement cell belongs to, for example, BSC_1. Indicates the name of the measurement cell, for example, Cell_1. Indicates the measurement cell CGI. Indicates the broadcast control channel of a measurement cell. Indicates the base station identity code of a measurement cell.
Issue 03 (2010-06-30)
12-37
Parameter Number of CoBCCH Neighboring Cells (Co-BCCH defined neighbors and Co-BCCH defined neighbors of tested cell's defined cells.) Probable CoInterferenced Traffic by neighbor Probable AdjInterferenced Traffic by neighbor Probable CoInterferenced Traffic to neighbor Probable AdjInterferenced Traffic to neighbor Total Number of Measurement Reports on Test Cells Proximate CoChannel Neighboring Cell Distance (km)
Description Indicates the number of co-channel neighboring cells of a measurement cell, including the defined neighboring cells and undefined neighboring cells.
Indicates the number of MRs received by the measurement cell from the co-channel neighboring cells. Indicates the number of MRs received by the measurement cell from the adjacent-channel cells. Indicates the number of MRs received by the co-channel neighboring cells from the measurement cell. Indicates the number of MRs received by the adjacent-channel cells from the measurement cell. Indicates the total number of downlink MRs received by the measurement cell within the measurement period.
Indicates the distance from the measurement cell to the nearest cochannel neighboring cell.
12.8.6 Parameters for Querying the Report of GSM Cell Interference Matrix
This section describes the parameters for querying the report of the GSM cell interference matrix. You can refer to the description when querying the report of the GSM cell interference matrix.
Parameter related to the matrix of the interference from other cells to the measurement cell
Parameter Interference Cell Description Indicates the name of a cell that interferes the measurement cell.
12-38
Issue 03 (2010-06-30)
Parameter Interference Cell BCCH Frequency Interference Cell BSIC Neighboring Cell Property Overlapping Traffic Percentage of CoInterferenced Traffic by Neighbor(%)
Description Indicates the broadcast control channel of an interfering cell. Indicates the base station identity code of an interfering cell. Indicates the attributes of an interfering cell, such as Defined Neighboring Cell and Undefined Neighboring Cell. Indicates the number of MRs received by the measurement cell from the co-channel cells and adjacent-channel cells. If the BCCH of the measurement cell is set to be the same as that of a neighboring cell, the value of this parameter is calculated according to the formula: Value = Traffic affected by the interference from a cochannel neighboring cell to the measurement cell/Number of reports generated by the measurement cell during measurement period x 100% If the BCCH of the measurement cell is set to the frequency adjacent to the BCCH of a neighboring cell, the value of this parameter is calculated according to the formula: Value = Traffic affected by the interference from an adjacent-channel neighboring cell to the measurement cell/Number of reports generated by the measurement cell during measurement period x 100% Indicates the total traffic affected by the interference from a neighboring cell to the measurement cell when the BCCH of the test cell is the same as that of the neighboring cell. Indicates the total traffic affected by the interference from a neighboring cell to the measurement cell when the BCCH of the test cell is adjacent to the BCCH of the neighboring cell. Distance from the measurement cell to a neighboring cell.
Percentage of AdjInterferenced Traffic by Neighbor(%)
Probable CoInterferenced Traffic by Neighbor Probable AdjInterferenced Traffic by Neighbor Distance (km)
Parameter related to the matrix of the interference from the measurement cell to its neighboring cells
Parameter Interfered Cell Interfered Cell BCCH Interfered Cell BSIC Description Indicates the name of a cell interfered by the measurement cell Indicates the broadcast control channel of an interfered cell. Indicates the base station identity code of an interfered cell.
Issue 03 (2010-06-30)
12-39
Parameter Neighboring Cell Property Overlapping Traffic Percentage of CoInterferenced Traffic to Neighbor (%)
Description Indicates the attributes of an interfered cell, such as Defined Neighboring Cell and Undefined Neighboring Cell. Indicates the number of MRs received by the co-channel cells and adjacent-channel cells from the measurement cell. If the BCCH of the measurement cell is set to be the same as that of a neighboring cell, the value of this parameter is calculated according to the formula: Value = Traffic affected by the interference from the measurement cell to the co-channel neighboring cell/Number of reports generated by the measurement cell during measurement period x 100% If the BCCH of the measurement cell is set to the frequency adjacent to the BCCH of a neighboring cell, the value of this parameter is calculated according to the formula: Value = Traffic affected by the interference from the measurement cell to the adjacent-channel neighboring cell/Number of reports generated by the test cell during measurement period x 100% Indicates the total traffic affected by the interference from the measurement cell to a neighboring cell when the BCCH of the test cell is the same as that of the neighboring cell. Indicates the total traffic affected by the interference from the measurement cell to a neighboring cell when the BCCH of the test cell is adjacent to the BCCH of the neighboring cell. Distance from the measurement cell to an interfered cell.
Percentage of AdjInterferenced Traffic to Neighbor (%)
Probable CoInterferenced Traffic to Neighbor Probable AdjInterferenced Traffic to Neighbor Distance (km)
12.8.7 Parameters for Querying the Report of the GSM Cell Frequency Interference Matrix
This section describes the parameters for querying the report of the GSM cell frequency interference matrix. You can refer to the description when querying the report of the GSM cell frequency interference matrix.
Parameters Related to Frequency Interference Matrix

Parameter BCCH Frequency Traffic of Test Cell Caused by Neighboring Cell Interference Description Indicates the BCCHs of the defined and undefined neighboring cells of the measurement cell If the BCCH of the measurement cell is set to the value of BCCH Frequency, the value of this parameter is the total volume of the interfered traffic of the measurement cell. The interfered traffic is caused by the co-channel and adjacent-channel neighboring cells of the test cell.
12-40
Issue 03 (2010-06-30)
Parameter Traffic of Neighboring Cell Caused by Test Cell Interference Proximate CoChannel Neighboring Cell Distance (km)
Description If the BCCH of the measurement cell is set to the value of BCCH Frequency, the value of this parameter is the total volume of the interfered traffic of the co-channel and adjacent-channel neighboring cells. The interfered traffic is caused by the measurement cell. Indicates the distance from the measurement cell to the nearest cochannel cell when the BCCH of the measurement cell is configured to the value of BCCH Frequency.
Parameters Related to the Cells Whose BCCHs Specified by BCCH Frequency

Parameter Interference Cell BCCH Frequency Interference Cell BSIC Frequency Interference Cell ID. Interference Cell Name Neighboring Cell Property Overlapping Traffic Percentage of CoInterferenced Traffic by neighbor (%) Description Indicates the broadcast control channel of an interfering cell. Indicates the base station identity code of an interfering cell. Indicates the number of an interfering cell. Indicates the name of a cell that interferes the measurement cell. Indicates the attributes of an interfering cell, such as Defined Neighboring Cell and Undefined Neighboring Cell. Indicates the total number of reports sent from a co-channel cell to the measurement cell and reports sent from the measurement cell to the cochannel cell. If the BCCH of the measurement cell is the same as that of a neighboring cell, the value of this parameter is calculated according to the formula: Value = Traffic affected by the interference from the co-channel neighboring cell to the measurement cell/Number of reports generated by the measurement cell during measurement period x 100% If the BCCH of the measurement cell is set to the frequency adjacent to the BCCH of a neighboring cell, the value of this parameter is calculated according to the formula: Value = Traffic affected by the interference from the adjacent-channel neighboring cell to the measurement cell/Number of reports generated by the measurement cell during measurement period x 100% Indicates the total traffic affected by the interference from a neighboring cell to the measurement cell when the BCCH of the test cell is the same as that of the neighboring cell.
Percentage of AdjInterferenced Traffic by neighbor (%)
Probable CoInterferenced Traffic by neighbor
Issue 03 (2010-06-30)
12-41
Parameter Probable AdjInterferenced Traffic by neighbor Percentage of CoInterferenced Traffic to neighbor (%)
Description Indicates the total traffic affected by the interference from a neighboring cell to the measurement cell when the BCCH of the test cell is adjacent to the BCCH of the neighboring cell. If the BCCH of the measurement cell is set to be the same as that of a neighboring cell, the value of this parameter is calculated according to the formula: Value = Traffic affected by the interference from the measurement cell to the co-channel neighboring cell/Number of reports generated by the measurement cell during measurement period x 100% If the BCCH of the measurement cell is set to a BCCH adjacent to the BCCH of a neighboring cell, the value of this parameter is calculated according to the formula: Value = Traffic affected by the interference from the measurement cell to the adjacent-channel neighboring cell/Number of reports generated by the test cell during measurement period x 100% Indicates the total traffic affected by the interference from the measurement cell to a neighboring cell when the BCCH of the test cell is the same as that of the neighboring cell. Indicates the total traffic affected by the interference from the measurement cell to a neighboring cell when the BCCH of the test cell is adjacent to the BCCH of the neighboring cell. Indicates the distance from the measurement cell to a neighboring cell.
Percentage of AdjInterferenced Traffic to neighbor (%)
Probable CoInterferenced Traffic to neighbor Probable AdjInterferenced Traffic to neighbor Distance (km)
12.8.8 Parameters for Querying GSM Frequency Optimization Reports

This section describes the parameters for querying the reports of the GSM frequency optimization.
Parameter Description of the Current Measurement Cell

Parameter BSC Name Cell Name BCCH LAC CI TCH
12-42
Description Refers to the BSC to which the measurement cell belongs. For example, the BSC is named BSC_1. Refers to the name of the measurement cell. For example, the cell is named Cell_1. Refers to the broadcast control channel of the current test cell. Refers to the location code of the current measurement cell. Refers to the cell identity of the current measurement cell. Refers to the traffic channel of the current measurement cell.
Parameter Description of BCCH/TCH ARFCNs

Parameter Configured ARFCN Cell with the Strongest Interference Description Indicates whether the current ARFCN is configured as the BCCH ARFCN or a TCH ARCFN of the selected cell. Indicates the configured and candidate BCCH and TCH ARFCNs of the measurement cell. Indicates the name of the cell that has the strongest interference over the measurement cell. This parameter might be null in the following cases:
l
The system identifies the BCCH and BSIC values of the cell with the strongest interference but cannot locate the cell according to these values. The system fails to identify the BCCH or BSIC value of the cell with the strongest interference, and these values are displayed as 0, that is, the cell with the strongest interference is not within the interference matrix, and thus it cannot be measured.
Cell Measured or Not
Indicates whether the cell with the strongest interference over the measurement cell is within the interference matrix, that is, whether the cell with the strongest interference is measured. The value can be Yes or No.
l
Yes indicates that the cell with the strongest interference over the measurement cell is within the interference matrix, that is, the cell with the strongest interference is measured. In such a case, External Interference Traffic of this ARFCN is reliable. No indicates that the cell with the strongest interference over the measurement cell is not within the interference matrix, that is, the cell with the strongest interference is not measured. In such a case, External Interference Traffic of this ARFCN is unreliable.
Maximum Interference Traffic Total Interference Traffic Interfered Traffic
Indicates the maximum interference traffic received by the measurement cell when the BCCH/TCH of the measurement cell is configured as the current candidate ARFCN. Indicates the total interference traffic received from and caused to other cells when the BCCH/TCH of the measurement cell is configured as the current candidate ARFCN. Indicates the total interference traffic received from other cells when the BCCH/TCH of the measurement cell is configured as the current candidate ARFCN. Indicates the total interference traffic caused to other cells when the BCCH/TCH of the measurement cell is configured as the current candidate ARFCN.
External Interference Traffic
Issue 03 (2010-06-30)
12-43
Parameter Interference Traffic to VIP Cells Latest Total Interference Traffic Original Total Interference Traffic
Description Indicates the total interference traffic caused to other VIP cells when the BCCH/TCH of the measurement cell is configured as the current candidate ARFCN. Indicates the total interference traffic received from and caused to other cells when the BCCH/TCH of the measurement cell is configured as the current candidate ARFCN after the latest frequency optimization is performed. Indicates the total interference traffic received from and caused to other cells when the BCCH/TCH of the measurement cell is configured as the ARFCN of the existing network.
12-44
Issue 03 (2010-06-30)
13 GSM Uplink Interference Analysis
13
GSM Uplink Interference Analysis
About This Chapter

This section describes the GSM uplink interference analysis. The GSM uplink interference analysis involves the management and query of GSM uplink interference analysis tasks. The Nastar measures the uplink levels. By checking the analysis results, you can know the strength of the measured frequencies received in a certain cell and choose a proper frequency to be used. 13.1 Basic Knowledge of GSM Uplink Interference Analysis This section describes the GSM uplink interference analysis. The GSM uplink interference analysis function is used to analyze the diverse average interference strength and main average interference strength of uplink levels. In the network planning, this function enables the network planners to look for the frequency resources that are not interfered on the network. In the network optimization, this function enables the network planners to look for the frequency resources with better quality for the cells with interference sources according to the analysis of the measurement results. In the network monitoring, this function can be used to monitor the interference levels of the network. 13.2 Procedure for Using GSM Uplink Interference Analysis This section describes the process of GSM uplink interference analysis. 13.3 Managing GSM Uplink Interference Analysis Tasks This section describes how to manage the GSM uplink interference analysis tasks. You can create, modify, delete, suspend, and resume GSM uplink interference analysis tasks. You can also view the status and the execution progress of a task. 13.4 Querying a GSM Uplink Interference Analysis Report This section describes how to query a GSM uplink-interference analysis report. You can query the signal strength of the measured frequency received and choose the proper operating frequency based on the result. 13.5 Reference for the GSM Uplink Interference Analysis GUI This section describes the interface for GSM uplink interference analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of GSM uplink interference analysis.
Issue 03 (2010-06-30)
13-1
13.1 Basic Knowledge of GSM Uplink Interference Analysis

This section describes the GSM uplink interference analysis. The GSM uplink interference analysis function is used to analyze the diverse average interference strength and main average interference strength of uplink levels. In the network planning, this function enables the network planners to look for the frequency resources that are not interfered on the network. In the network optimization, this function enables the network planners to look for the frequency resources with better quality for the cells with interference sources according to the analysis of the measurement results. In the network monitoring, this function can be used to monitor the interference levels of the network. The uplink frequency analysis aims at testing uplink levels. The analysis results reflect the strength of the signals received by the measurement cell at the test frequencies. The engineers can select appropriate work frequencies according to the analysis results. The Huawei BTS can scan the received levels at uplink of all frequencies in the following frequency 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/1930 MHz to 1989 MHz), E-GSM extended frequency band (880 MHz to 890 MHz), and R-GSM extended frequency band (876 MHz to 880 MHz). That is, the Huawei BTS can scan the strength of the interference signals in the frequency bands ranging from 876 MHz to 915 MHz and from 1805 MHz to 1880 MHz. The principles of the frequency analysis for the BTS of the Huawei BTS3X series are as follows: In the case of not affecting normal calls, the uplink frequency analysis function is used to perform the cycling test by using the IDLE frame of a TCH within the measurement cell and scan the received levels at uplink of the specified frequencies (When the BSC allocates this channel, the TCH at the TRX where the BCCH is located is preferred). The TCH channel adopts the structure of 26 multiframes. Each TCH multiframe contains an IDLE frame. The period of the IDLE frame on the TCH channel is 26 multiframes x 0.577 (Burst length) x 8 (TDMA frame) = 120 ms. During the application, 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 are spent on measuring these 124 frequencies. After you set the conditions of uplink interference analysis, the Nastar performance analysis system starts to analyze the uplink interference for the selected cells. The analysis results are displayed in histogram mode or in line chart to show the diverse average interference strength and main average interference strength of each frequency at different time and in different colors.
13.2 Procedure for Using GSM Uplink Interference Analysis

This section describes the process of GSM uplink interference analysis. Figure 13-1 shows the general process of GSM uplink interference analysis.
13-2
Issue 03 (2010-06-30)
Figure 13-1 Process of GSM uplink interference analysis

Start
Set an E2E task
Set an uplink interference analysis task Query an uplink interference analysis report End
Table 13-1 describes the process of GSM uplink interference analysis. Table 13-1 Process of GSM uplink interference analysis Seria l No. 1 Procedure Querying NE data information Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the uplink interference analysis is imported to the database.
Issue 03 (2010-06-30)
13-3
Seria l No. 2
Procedure Create an endto-end task corresponding to an uplink frequency scanning task
Description You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to an uplink frequency scanning task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results.
NOTE If no end-to-end task corresponding to an uplink frequency scanning task is created, first you need to create an end-to-end task corresponding to an uplink frequency scanning task to enable the measurement of all the objects.
Create an uplink ARFCN scanning data collecting task
You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create an uplink ARFCN scanning data collecting task. After the task is created, the Nastar periodically obtains the required uplink ARFCN scanning data from M2000, and saves the data as files on the Nastar server. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create an uplink ARFCN scanning data importing task. After the task is created, the Nastar periodically imports the uplink ARFCN scanning data files saved on the Nastar server to the database. You can create an uplink interference analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required uplink ARFCN scanning data from the Nastar database, and then generates an analysis report through the analysis. You can browse the analysis result when the uplink interference analysis task is successfully performed. The system sorts interference signals on the BCCH and TCH frequencies in all cells and determines whether the uplink signal interference exists in some cells, thus providing references for you to select proper operating frequencies.
Create an uplink ARFCN scanning data importing task
Create an uplink interference analysis task
Query uplink interference analysis reports
13.3 Managing GSM Uplink Interference Analysis Tasks

This section describes how to manage the GSM uplink interference analysis tasks. You can create, modify, delete, suspend, and resume GSM uplink interference analysis tasks. You can also view the status and the execution progress of a task. 13.3.1 Creating GSM E2E Tasks
This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 13.3.2 Creating a GSM Uplink Interference Analysis Task This section describes how to create a GSM uplink-interference analysis task. By performing uplink-interference analysis tasks, the Nastar performance analysis system analyzes the uplinklevel data in the database at the preset time. By checking the analysis results, you can ascertain the signal strength of the measurement ARFCNs received in certain cells and choose a proper operating ARFCN. 13.3.3 Modifying a GSM Uplink Interference Analysis Task You can modify the attributes of a GSM uplink-interference analysis task to meet the new requirement. 13.3.4 Checking a GSM Uplink Interference Analysis Task This section describes how to check a GSM uplink-interference analysis task. You can check the attributes, execution progress, and execution results of a GSM uplink-interference analysis task.

Prerequisite
l l l
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Perform the following operations as required:
Issue 03 (2010-06-30)
13-5
If You Want to ... Add a GSM neighboring cell measurement task Add a GSM uplink frequency scan task Add a GSM VIP analysis task Add a GSM/UMTS neighboring cell data task Add a GSM cell performance data task
Then ... Perform Step 4. Perform Step 5. Perform Step 6. Perform Step 7. Perform Step 8.
l l l l
4.
CAUTION
It is recommended that the number of test cells under one BSC does not exceed 200. If the recommended value is exceeded, certain cells may fail to report complete data. The upper threshold is 400. 5. Optional: Click Frequency Analysis to traverse the three level neighboring cells of the selected cell. The Nastar then analyzes the BCCH frequencies of the traversed neighboring cells and highlights these BCCH frequencies in the frequency selection area in gray to provide reference for measurement frequency analysis. Traversing of the three level neighboring cells indicates that the Nastar searches for the neighboring cells of the selected cell (neighboring cell A), the neighboring cells of
13-6
neighboring cells A (neighboring cell B), and the neighboring cells of neighboring cells B (neighboring cell C). All traversed neighboring cells A, B, and C are neighboring cells obtained through the traversing of the three level neighboring cells. 6. Set the ARFCNs.
NOTE
7.
8.
Click Finish. The added neighboring cell measurement task is displayed in the task list. Set the basic information about the task. a. b. c. In the Task Name field, enter the name of the uplink frequency scan task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Uplink Interference Analysis Data Task.
Step 5 Perform the following operations to create a GSM uplink frequency scan task: 1.
2. 3.
4.
5.
Issue 03 (2010-06-30)
Click Finish.
The added uplink frequency scan task is displayed in the task list. Step 6 Perform the following operations to add a GSM VIP analysis task: 1. Set the basic information about the task. a. b. c. 2. In the Task Name field, enter the name of the VIP analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM VIP Analysis Data Task.
3.
4.
2.
3.
2.
Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list.
13-8
The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. 3. 4. Click Next and then set the exception value for each KPI in the exception value setting list. Click Finish. The added cell performance analysis task is displayed in the task list.
----End
Postrequisite
NOTE
13.3.2 Creating a GSM Uplink Interference Analysis Task

This section describes how to create a GSM uplink-interference analysis task. By performing uplink-interference analysis tasks, the Nastar performance analysis system analyzes the uplinklevel data in the database at the preset time. By checking the analysis results, you can ascertain the signal strength of the measurement ARFCNs received in certain cells and choose a proper operating ARFCN.
Prerequisite
l l
Context
l l
Issue 03 (2010-06-30)
Procedure
Step 1 Click in the Analysis Task Management window. The Analysis Task Management-New Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can be only Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects in the object navigation tree on the NE Object Selection tab page.
l

Step 7 Set Uplink Interference Analysis Parameter on the Parameter Setting tab page. Step 8 Click Complete. ----End
Postrequisite
l
Deleting a task You can delete an uplink-interference analysis task that is not required so that you can save system resources.
NOTE
1.
Choose GSM Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task To delay the task execution, you can suspend an uplink-interference analysis task that is in the Idle state. After this operation, the uplink-interference analysis task is in the suspended state.
NOTE
The system can schedule only the uplink-interference analysis tasks that are not suspended.
13-10
Issue 03 (2010-06-30)
1.
2.
. button is
Resuming a task You can resume a suspended uplink-interference analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the uplink-interference analysis task that is in the idle state can be scheduled by the system.
1.
2.
13.3.3 Modifying a GSM Uplink Interference Analysis Task

You can modify the attributes of a GSM uplink-interference analysis task to meet the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. A GSM uplink-interference analysis task is created.
Context
Procedure
Step 1 Choose GSM Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
. The

l
For details about the parameters, see 13.5.3 Parameters for Creating and Modifying GSM Uplink Interference Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the object navigation tree, and the Uplink Interference Analysis parameter.
13.3.4 Checking a GSM Uplink Interference Analysis Task

This section describes how to check a GSM uplink-interference analysis task. You can check the attributes, execution progress, and execution results of a GSM uplink-interference analysis task.
Prerequisite
l l
You have logged in to the Nastar client. A GSM uplink-interference analysis task is created.
Procedure
Step 1 Choose GSM Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: Purpose Checking the attributes of an uplinkinterference analysis task Operation Select a task from the task list in the upperright pane. Double-click the task or click You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 13.3.3 Modifying a GSM Uplink Interference Analysis Task. Checking the execution progress of the active task Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column. .
13-12
Issue 03 (2010-06-30)
----End
Postrequisite
l
13.4 Querying a GSM Uplink Interference Analysis Report

This section describes how to query a GSM uplink-interference analysis report. You can query the signal strength of the measured frequency received and choose the proper operating frequency based on the result.
Prerequisite
Procedure
Step 1 Choose GSM Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose Uplink Interference Analysis Task . The GSM Uplink Frequency Interference Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Optional: To view the counter chart corresponding to a frequency, select a frequency and choose Cell Uplink Interference Analysis from the navigation tree on the left. Alternatively, rightclick the frequency and choose Cell Uplink Interference Analysis.
l
The counter bar chart shows the interference strength of all the measured frequencies in the measurement cell at a certain time. The counter line chart shows the interference strength of a certain frequency in the selected cell during the measurement period. You can choose Cell Uplink Interference Overview from the navigation tree in the left pane to switch to the list of measured frequencies.
----End
Postrequisite
l
13-14
Issue 03 (2010-06-30)
13.5 Reference for the GSM Uplink Interference Analysis GUI

This section describes the interface for GSM uplink interference analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of GSM uplink interference analysis. 13.5.1 Interface Description: GSM Uplink Interference Analysis This section describes the interface for GSM uplink interference analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 13.5.2 Parameters for Creating GSM E2E Tasks This section describes the parameters for creating GSM E2E tasks. You can refer to the description when creating a GSM E2E task. 13.5.3 Parameters for Creating and Modifying GSM Uplink Interference Analysis Tasks This section describes the parameters for creating and modifying GSM uplink-interference analysis tasks. You can refer to the description when creating or modifying a GSM uplinkinterference analysis task. 13.5.4 Parameters for Querying the Uplink Interference Analysis Reports of GSM Cells This section describes the parameters for querying the uplink interference analysis reports of GSM cells. You can refer to the description when querying the uplink interference analysis reports of GSM cells.
13.5.1 Interface Description: GSM Uplink Interference Analysis

This section describes the interface for GSM uplink interference analysis. Before performing relevant 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, as shown in Figure 13-2 and Figure 13-3. Figure 13-2 Interface for the overview of the uplink interference of cells
Issue 03 (2010-06-30)
13-15
Figure 13-2 shows the signal strength of all the cell frequencies in a selected cell group or under a selected BSC. To view the counter chart corresponding to a frequency, select a frequency, and then click Cell Uplink Interference Analysis in the navigation tree in the left pane. Alternatively, right-click the frequency and choose Cell Uplink Interference Analysis. Figure 13-3 Interface for the uplink interference analysis of a cell
In Figure 13-3, the counter bar chart shows the interference strength of all the measured frequencies in the measurement cell at a certain time; the counter line chart shows the interference strength of a certain frequency in the selected cell during the measurement period. In the bar chart, each value on the vertical coordinate is the sum of 110 and the interference strength of the measured frequency, which ensures that the values on the vertical coordinate are positive. For details about the parameters on the interface, see 13.5.4 Parameters for Querying the Uplink Interference Analysis Reports of GSM Cells.


Parameter Basic information Task Name OSS Name E2E Task List
13-16
Description Indicates the name of a neighboring cell measurement task. Indicates the name of the OSS related to the task. Select the GSM Neighbor Cell Data Task node.
Issue 03 (2010-06-30)
Description Indicates the time when the task starts to run. The start time must be later than the current time. By default, the start time is five minutes later than the current system time. Persist Time (Minute) Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 65535. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15. Measurement 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 15 minutes. For example, if this parameter is set to 2, the measurement time of each ARFCN is 215 minutes, that is, 30 minutes. Measurement step length 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 to the minimum rest step of the selected cell. Cell Object Displays the frequency information. Indicates the cell related to the neighboring cell measurement task. Indicates the set of ARFCNs to be measured. The ARFCNs are classified by group. The number of ARFCNs of each group is determined by Measure Step.
NOTE
Step.
Issue 03 (2010-06-30)
13-17
Parameter ASSThres
Description The value is an integer from 0 to 63. When the level of the neighboring cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one. NCELLINTERFLE VELTHRES 1-7 You can set the thresholds of interference level for seven neighboring cells. The value is an integer from 0 to 127. When the difference between the levels of the neighboring cell and the serving cell in the MR is greater than this value, the relevant traffic statistical counter is incremented by one.
NOTE
l l l

13-18
Issue 03 (2010-06-30)
Parameter Band
l l l l l l
l

Issue 03 (2010-06-30)
13-19
Parameter End Time
Description

13-20
Issue 03 (2010-06-30)
Parameter NE Object

Issue 03 (2010-06-30)
13-21
13.5.3 Parameters for Creating and Modifying GSM Uplink Interference Analysis Tasks
This section describes the parameters for creating and modifying GSM uplink-interference analysis tasks. You can refer to the description when creating or modifying a GSM uplinkinterference analysis task.
Parameter Basic Information Task Name Description Indicates the name of an uplink-interference analysis task. Value range:
l l
l l
You need to select GSM Uplink Interference Analysis Task from the Task Type navigation tree. Such a task can be executed only once in a time segment. Indicates the description of the task. Value range:
l l
Time Information
Data Time Scope
Task Start At
Object Information
BSC Cell Group
If you select this option, the navigation tree displays all the BSCs of the entire network. If you select this option, the navigation tree displays all the cell groups of the entire network.
13-22
Issue 03 (2010-06-30)
Parameter Parameter Information Frequency band of the current cell is
Description Indicates the band of the current cell. The value of this parameter can be PGSM 900, EGSM 900, RGSM 900, DSC 1800, PCS 1900, GSM 450, GSM 480, and GSM 850. The default value is PGSM 900. Indicates the threshold of the average interference strength of the uplink diversity antenna. This parameter can be set to any integer from -100 to 0. The default value is -100. Unit: dBm Minimum Main Threshold Indicates the threshold of the average interference strength of the uplink main antenna. This parameter can be set to any integer from -100 to 0. The default value is -100. Unit: dBm Frequency Type Setting Arithmetic of Average Indicates an ARFCN type. The value can be BCCH or TCH. Indicates the method for calculating the average value. The value can be Signal Strength Average or Power Average. If the parameter is set to Signal Strength Average, the average value is calculated directly based on the signal strength. If the parameter is set to Power Average, the average value is calculated based on the power that is converted from the signal strength and then the average value is converted to a value in the unit of signal strength.
Minimum Diversity Threshold
13.5.4 Parameters for Querying the Uplink Interference Analysis Reports of GSM Cells
This section describes the parameters for querying the uplink interference analysis reports of GSM cells. You can refer to the description when querying the uplink interference analysis reports of GSM cells.
Parameters Related to the Uplink Interference of GSM Cells

Parameter BSC Sequence Number BSC Name
Issue 03 (2010-06-30)
Description Indicates the ID of the BSC that a measured TRX belongs to. Indicates the name of a BSC, for example, BSC_1.
Parameter Cell Name Frequency Type Diverse Average Interference Strength (dBm) Main Average Interference Strength (dBm)
Description Indicates the name of the cell that a measured TRX belongs to. Indicates the frequency of a measured TRX. Indicates the type of a measured TRX. The options are BCCH and TCH. Indicates the diverse average interference strength of a measured TRX. Indicates the main average interference strength of a measured TRX.
Parameters Related to the Uplink Interference Analysis of GSM Cells

Parameter Cell Name BSC Name Time Scope BCCH Frequency Frequency Hopping Mode Description Indicates the name of the cell that a measured TRX belongs to. Indicates the name of a BSC, for example, BSC_1. Indicates the time range in which an uplink interference analysis task is performed. Indicates a BCCH of the selected cell. Indicates the type of the frequency hopping. The options are No Frequency Hopping, Baseband Frequency Hopping, Radio Frequency Hopping, and BCCH Synthesized Baseband Frequency Hopping. Indicates all the TCH frequencies of the selected cell. Indicates the counter bar chart of the selected cell at a certain time. Indicates the data displayed in the bar chart. The options are Frequency, Diversity, and Main. Diversity indicates the diverse average interference strength, and Main indicates the main average interference strength. Frequency Indicates the trend of the strength of a frequency in the selected cell in a certain time segment. The trend is displayed on a line chart.
TCH List Time Point Sort Type
13-24
Issue 03 (2010-06-30)
14 GSM VIP Analysis
14
About This Chapter
GSM VIP Analysis
This section describes the GSM VIP analysis, including the management of VIP analysis tasks and the query and export of VIP analysis reports. By monitoring the KPIs related to the QoS of the VIP subscribers, the Nastar enables you to identify and solve the network problems that may cause VIP subscriber complaints. This helps provide good services to VIP subscribers and improve satisfaction of VIP subscribers. 14.1 Basic Knowledge of GSM VIP Analysis The GSM VIP analysis function enables you to routinely monitor the calls of the selected VIP subscribers on the network. Analyzing monitoring reports helps you learn the quality of service (QoS) of VIP subscribers. In addition, it helps network engineers actively analyze and locate possible network problems of VIP subscribers in advance, thus improving the satisfaction of VIP subscribers. 14.2 GSM VIP Analysis Process This section describes the GSM MR analysis process. 14.3 Managing GSM VIP Analysis Tasks This section describes how to manage GSM VIP analysis tasks. You can create, modify, delete, suspend, or restore GSM VIP analysis tasks. You can also view the status and execution progress of such tasks. 14.4 Querying GSM VIP Analysis Reports This section describes how to query GSM VIP analysis reports. By monitoring the number of service call reports, traffic, and KPIs of the selected VIP subscriber, you can learn about the service quality of the VIP subscriber and identify and solve the network problems that may cause VIP subscriber complaints. 14.5 Exporting GSM VIP Analysis Reports This section describes how to export GSM VIP analysis reports. You can export the queried VIP analysis results as .csv or .xls files as required. The exported VIP analysis results help you identify and solve the network problems that may cause VIP subscriber complaints. 14.6 Reference to the GSM VIP Analysis Interface This section describes the interface for GSM VIP analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of GSM VIP analysis.
14 GSM VIP Analysis
14.1 Basic Knowledge of GSM VIP Analysis

The GSM VIP analysis function enables you to routinely monitor the calls of the selected VIP subscribers on the network. Analyzing monitoring reports helps you learn the quality of service (QoS) of VIP subscribers. In addition, it helps network engineers actively analyze and locate possible network problems of VIP subscribers in advance, thus improving the satisfaction of VIP subscribers.
VIP Analysis
The Nastar obtains the information about IMSIs reported by UEs during calls and finally helps to solve the problems related to the subscriber-level network optimization through the aggregation and analysis of KPIs (including service-level KPIs in CS and PS domains and KPIs of active cells) based on the VIP group level and VIP subscriber level.
l
The aggregation and analysis of KPIs based on the VIP group level help network engineers efficiently and timely monitor the service usage of subscribers from important groups in a centralized manner. This effectively improves the operation efficiency and reduces the operation expenditure. In addition, this function helps operators identify problem VIP groups and the corresponding VIP subscribers in time, thus enabling operators to actively analyze and solve problems in advance to prevent losing important customer groups. The aggregation and analysis of KPIs based on the VIP subscriber level provide a detailed analysis of KPI trends related to subscriber experience and behavior. For example, analysis of variation trends of originated-call connection delay of voice services, analysis of variation trends of terminated-call connection delay of voice services, and analysis of variation trends based on service duration. The trend analysis based on different types helps network engineers quickly identify the worst and best QoS of VIP subscribers and QoS variation trends during a certain period and learn the relation between network problems and time.
In addition, the Nastar supports in-depth analysis for the important VIP subscribers whose raw data is collected in advance. When the KPIs of important VIP subscribers of a group deteriorate, but the network engineers cannot recur and locate the problem at the site, the Nastar helps to extract the detailed call records of these VIP subscribers within the specified period. By analyzing these reports, the network engineers quickly locate the key call report that results in the deterioration of KPIs, and then analyzes the information such as the network quality and signaling procedure before the link release and abnormal causes, thus locating problems. The aggregation and analysis of KPIs of active cells based on VIP groups and VIP subscribers help network engineers learn the main active areas of VIP subscribers on the network. Based on the network problems that occur in these active areas, the network engineers can quickly identify the key cells that need to be preferentially treated to solve these network problems. Thus, they can timely solve the problem of the deterioration of QoS of VIP subscribers caused by network problems. Used with the GIS, this function enables the Nastar to display active cells in geographic mode, thus improving the efficiency of problem analysis and location.
Limitation
The GSM VIP analysis function allows the NEs to report raw call data of important VIP subscribers to the Nastar. The amount of raw data is huge. Therefore, limitation is required to prevent the system from becoming overloaded in the case of concurrent operations by a large number of users. In such a case, for the analysis function based on the VIP group level, the Nastar
14 GSM VIP Analysis
supports the analysis of 100,000 subscribers (that is, the maximum number of subscribers in all the VIP groups that are selected for the analysis cannot exceed 100,000); for the analysis function based on the VIP subscriber level, the Nastar supports the analysis of 2,000 subscribers (that is, the maximum number of subscribers in all the VIP groups that are allowed to report data sources cannot exceed 2,000). In addition, the analysis function of KPIs in active cells of GSM VIP subscribers requires the display of geographic distribution of active cells. To ensure the display effect, you need to import correct engineering parameters.
14.2 GSM VIP Analysis Process

This section describes the GSM MR analysis process. Figure 14-1 shows the general process of GSM VIP analysis.
Issue 03 (2010-06-30)
14-3
14 GSM VIP Analysis
Figure 14-1 Process of GSM VIP analysis
14-4
Issue 03 (2010-06-30)
14 GSM VIP Analysis
Table 14-1 Process of GSM VIP analysis No. 1 Procedure Managing VIP groups Item In the Analysis Task Management window on the Nastar client, you can enter the VIP group management window to create the VIP groups and relevant subscribers required for the VIP analysis. After the creation, the VIP analysis function provides options based on the information about the created VIP subscribers or VIP groups. Thus, you can create an analysis task for a specified VIP subscriber. In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the VIP analysis is imported to the database. On the Nastar client, choose Maintenance > E2E Task Management. In the displayed E2E Task Management window, you can create an E2E task of VIP analysis. After the task is created, the Nastar issues MML commands to the M2000, and then the M2000 issues MML commands to NEs. Finally, the NEs execute the measurement task and generate results. After an E2E task is created, in the Task Management window, you can view the corresponding collection task that has been created by the system. You can perform a data import task only after the corresponding collection task is complete. On the Nastar client, choose Maintenance > Task Management. In the displayed Task Management window, you can create a data import task corresponding to the VIP analysis task so that the Nastar periodically imports the VIP analysis data saved as files on the Nastar server to the database. In the Analysis Task Management window on the Nastar client, you can create VIP analysis tasks. After obtaining the related analysis data from the database, the Nastar analyzes data and then outputs the analysis result. You can view the analysis results of the VIP analysis tasks that are executed successfully and also perform comprehensive analysis together with maps. In addition, you can export the result files through the one-key method in the analysis result query interface. 7 Exporting VIP analysis reports You can export analysis result files in the Nastar performance analysis system.
Querying NE data information Creating an E2E task for VIP analysis
Creating a task for importing VIP analysis data Creating a VIP analysis task
Querying VIP analysis reports
14.3 Managing GSM VIP Analysis Tasks

This section describes how to manage GSM VIP analysis tasks. You can create, modify, delete, suspend, or restore GSM VIP analysis tasks. You can also view the status and execution progress of such tasks.
Issue 03 (2010-06-30)
14-5
14 GSM VIP Analysis
14.3.1 Managing GSM VIP Groups This section describes how to manage the GSM VIP groups. You can create VIP groups as required and add certain VIP subscribers to a VIP group to monitor the service quality of these VIP subscribers simultaneously. In addition, you can modify the attributes of a VIP group, delete, or export a VIP group. 14.3.2 Creating GSM E2E Tasks This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 14.3.3 Creating GSM VIP Analysis Tasks This section describes how to create GSM VIP analysis tasks. In a GSM VIP analysis task, the Nastar obtains the IMSI reported by the mobile subscriber through the communications device, and then performs aggregation and analysis for the service call report quantity, traffic, and KPIs on the basis of VIP subscribers or VIP groups. This helps solve the subscriber level network optimization problem, thus providing better services for VIP subscribers and improving VIP subscriber satisfaction. 14.3.4 Modifying GSM VIP Analysis Tasks This section describes how to modify the attributes of the GSM VIP analysis tasks. You can modify the attributes of the GSM VIP analysis tasks as required. 14.3.5 Checking GSM VIP Analysis Tasks This section describes how to check GSM VIP analysis tasks. You can check the attributes, execution progress, and execution results of a GSM VIP analysis task as required.
14.3.1 Managing GSM VIP Groups

This section describes how to manage the GSM VIP groups. You can create VIP groups as required and add certain VIP subscribers to a VIP group to monitor the service quality of these VIP subscribers simultaneously. In addition, you can modify the attributes of a VIP group, delete, or export a VIP group.
Context
IMSI refers to the international mobile subscriber identity. The IMSI is a 15-digit string formed by numerals 0 to 9. The structure of the IMSI from the left to the right is MCC+MNC+MSIN. The MNC and the MSIN forms the NMSI. Where:
l l
MCC refers to the mobile country code of a mobile subscriber. MNC refers to the mobile network code, namely, the PLMN code of a mobile subscriber. PLMN refers to the public land mobile network. MSIN refers to the mobile subscriber identification number. NMSI refers to the national mobile subscriber identification. This identification can uniquely identify an MS in a country.
l l
The VIP group file to be imported must include the following fields: Group name, Priority, and Description, as shown in Table 14-2. The match sequence of columns is restricted and automatic matching of columns is not supported.
14-6
Issue 03 (2010-06-30)
14 GSM VIP Analysis
Table 14-2 VIP group file Group Name Group 1 Group 2 Level Important Low Description Second level director of ** Group Project manager of ** Group
The export of VIP group files in .csv and .xls formats are supported.
Procedure
Step 1 Choose Function List > System Function > VIP Group Management from the navigation tree in the Analysis Task Management window. The VIP Group Management dialog box is displayed. Step 2 Perform the following operations as required: If You Want to ... Create a VIP group by adding one Create a VIP group by importing one Step 3 To create a VIP group by adding one, do as follows: 1. 2. Click the GSM VIP Group Name tab. Then, click New to open the GSM VIP Group Management - Create VIP Group dialog box. Set Group Name, Priority, and Description. If the * character is present on the right of a parameter, it indicates that the setting of this parameter is mandatory. 3. Select one or multiple VIP subscribers from the Group Member list. You can add new VIP subscribers to this list as required or import VIP subscribers to this list, delete the existing VIP subscribers from the list, or export the VIP subscriber information in the list to .csv or .xls files.
l
Adding a VIP subscriber a. b. Click New below the Group Member list to open the VIP User Management dialog box. Set User Name, Phone Number, IMSI, and Description. If the * character is present on the right of a parameter, it indicates that the setting of this parameter is mandatory. c. Click Confirm. Click Import below the Group Member list to open the Open dialog box. Select an edited VIP subscriber file, and then click Open.
Importing a VIP subscriber a. b.
Issue 03 (2010-06-30)
14 GSM VIP Analysis
If a VIP subscriber file in .xls format is selected and the file contains multiple worksheets, a prompt is displayed. In this case, select the worksheet to be imported. c. After the import is complete, perform the operations as prompted. The number of new records, the number of updated records, and the number of failed records are displayed.

Click Close to complete the import operation. Click Export Fail Record to export the error information as a file so that you can learn the cause of the import failures.
Deleting a VIP subscriber a. b. Select one or multiple VIP subscribers from the Group Member list and then click Delete below the list. In the displayed Confirm dialog box, click Confirm. Click Export below the Group Member list. Set a file name and specify the save path and file type in the displayed Save dialog box, and then click Save.
Exporting the VIP subscriber information to .csv or .xls files a. b.
You can also select all records, find a record, or save a record through the shortcut menu prompted by right-clicking in the Group Member list. 4. Click Confirm.
Step 4 To create a VIP group by importing one, do as follows: 1. 2. Click Import on the GSM VIP Group Name tab page to open the Open dialog box. Select an edited VIP group file, and then click Open. If a VIP group file in .xls format is selected and the file contains multiple worksheets, a prompt is displayed. In this case, select the worksheet to be imported.
NOTE
In a VIP group file, if Priority and Description of the same VIP group in different rows are different, the Nastar displays Priority and Description in the last row of the VIP group in the Priority and Description column on the GSM VIP Group Name tab page. It is recommended that the description and priority information in different rows regarding a VIP group be the same when you define VIP group information. If the Priority column is empty, Medium is displayed by default.
3. 4.
Click Import. In the Confirm dialog box, click OK after checking the number of added records, updated records, and failed records. , , and indicate the VIP group that In the Import GSM VIP Group dialog box, is successfully imported, partially imported, and failed to be imported respectively.
5.

l
If the imported information is correct, only VIP groups that are marked by displayed. In this case, click Close. or
are
If abnormal records exist in the imported information, VIP groups that are marked by are displayed. In this case, perform the following operations: Click Export Fail Record to export the failed records as a file so that you can make modifications based on the error information to complete the current import task.
14-8
14 GSM VIP Analysis
Click Close to complete the current import task.
----End
Postrequisite
l
Modifying the attributes of a VIP group 1. Select a VIP group on the GSM VIP Group Name tab page and then click Modified to open the GSM VIP Group Management - Modify VIP Group dialog box. Modify the relevant parameters. For description of the parameters, see 14.6.1 Parameters for Creating and Modifying GSM VIP Subscribers/VIP Groups. 3. Click Confirm. If the VIP group is used by certain tasks, the modification does not affect the ongoing tasks. If the VIP group is used by a periodic task, the related information is updated in the next period after the modification.
2.
Viewing the information about members of a VIP group On the GSM VIP Group Name tab page, double-click a VIP group to view the detailed information about the members of the VIP group.
Deleting a VIP group 1. 2. Select a VIP group on the GSM VIP Group Name tab page, and then click Delete. In the displayed Confirm dialog box, click Confirm. If the VIP group is used by certain tasks, the modification does not affect the ongoing tasks. If the VIP group is used by a periodic task, the related information is updated in the next period after the modification.
Exporting the VIP group information to .csv or .xls files 1. 2. On the GSM VIP Group Name tab page, click Export. Set a file name and specify the save path and file type in the displayed Save dialog box, and then click Save.
You can also select all VIP groups, and find or save a VIP group through the shortcut menu prompted by right-clicking on the GSM VIP Group Name tab page.

Prerequisite
l l l
Issue 03 (2010-06-30)
14 GSM VIP Analysis
Context
TIP
Procedure
l l l l
4.
From the object navigation tree, select the cell related to the task. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive.
14-10
Issue 03 (2010-06-30)
14 GSM VIP Analysis
You can select Up or Down in the Direction area to determine the direction of the search.
CAUTION
NOTE
7.
8.
Step 5 Perform the following operations to create a GSM uplink frequency scan task: 1. Set the basic information about the task. a. b. c. 2. 3.
Issue 03 (2010-06-30)
In the Task Name field, enter the name of the uplink frequency scan task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Uplink Interference Analysis Data Task.
Click Next to set Time (Minute), that is, the total duration of the measurement task execution. In the Cell Parameter Setting area, select the cell and frequency band to be tested.
14 GSM VIP Analysis
a. b.
From the Frequency Segment drop-down list box, select the frequency band that the cell uses. From the object navigation tree, select the cell related to the task. The system enables you to search for the objects in the navigation tree. You can rightclick any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
4.
5.
3.
4.
Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list.
14-12
14 GSM VIP Analysis
The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. 3. Click Finish. The added GSM/UMTS neighboring cell data task is displayed in the task list. Step 8 Perform the following operations to add a GSM cell performance analysis task: 1. Set the basic information about the task. a. b. c. 2. In the Task Name field, enter the name of the cell performance analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM Cell Performance Analysis Task.
3. 4.
----End
Postrequisite
NOTE
14 GSM VIP Analysis
14.3.3 Creating GSM VIP Analysis Tasks

This section describes how to create GSM VIP analysis tasks. In a GSM VIP analysis task, the Nastar obtains the IMSI reported by the mobile subscriber through the communications device, and then performs aggregation and analysis for the service call report quantity, traffic, and KPIs on the basis of VIP subscribers or VIP groups. This helps solve the subscriber level network optimization problem, thus providing better services for VIP subscribers and improving VIP subscriber satisfaction.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the VIP analysis function. The E2E task, collection task, and data import task corresponding to the VIP analysis task are normal. The VIP analysis task can be created successfully even if the prerequisites are not met. The execution of the VIP analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l
A VIP analysis task can be performed once or periodically. The supported unit of the execution period of a periodical task is hour. A maximum of 50 tasks of this type can be created and the time range of the data in a task cannot exceed 7 days. Before you create an analysis task, check to ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, Execution Type, and Note. Step 3 Click Next. Step 4 Set Task Configuration and Time Setting for Cycle Task Data/Time Setting for Once Task Data. If Once Task is selected in the previous step, you need to set only Data Time Scope. Step 5 Click Next. Step 6 On the VIP Group Selection tab page, select one or multiple VIP groups and select Report Raw Data as required. If you select to report raw data, the original call record data is collected when the VIP KPI overview information is provided. Step 7 On the VIP KPI Threshold Setting tab page, set the threshold value of each KPI.

l
14 GSM VIP Analysis
In the analysis report of the corresponding task, if the KPI value of a corresponding subscriber does not reach the threshold value, it is considered that this is a problem KPI or deteriorating KPI. The threshold values of the KPIs related to success rate can be set to any percentage from 0 to 100%. The threshold values of the KPIs related to delay can be set to any number that is greater than zero. To apply the modified threshold value to subsequent VIP analysis tasks, click App. To restore the modified threshold value to the initial value, click Default.
Postrequisite
l
Deleting a task You can delete an unnecessary VIP analysis task to release system resources.
NOTE
1.
Click the GSM VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Select a task from the task list in the upper-right pane, and then click the In the displayed Confirm dialog box, click Confirm.
button.
Suspending a task To delay the task execution, you can suspend a VIP analysis task that is in the idle state. Then, the VIP analysis task becomes a suspended task.
NOTE
The system can schedule only the VIP analysis tasks that are not suspended.
1.
Click the GSM VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
Select a task from the task list in the upper-right pane, and then click the
button.
This operation can be performed for only the tasks whose Status is Idle. If a task is not in the idle state, the button is unavailable.
l
Restoring a task You can restore a suspended VIP analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the VIP analysis tasks that are in the idle state can be scheduled by the system.
1.
Click the GSM VIP Analysis Task node in the navigation tree in the Analysis Task Management window.
Issue 03 (2010-06-30)
14 GSM VIP Analysis
If you choose Subject Function, the task list on the right displays all the performance analysis tasks. 2. Select a task from the task list in the upper-right pane, and then click the button.
This operation can be performed for only the tasks whose Status is Suspended. If a task is not in the suspended state, the button is unavailable.
14.3.4 Modifying GSM VIP Analysis Tasks

This section describes how to modify the attributes of the GSM VIP analysis tasks. You can modify the attributes of the GSM VIP analysis tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the VIP analysis function. A GSM VIP analysis task is created.
Context
Procedure
Step 1 Click the GSM VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 14.6.3 Parameters for Creating and Modifying GSM VIP Analysis Tasks. For periodical tasks, you can modify the Note parameter in the basic information, the Begin Date, Cycle, Execution Times, and Time parameters in the time information, the VIP group information, and the VIP KPI information. For the tasks that can be performed only once, you can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the VIP group information, and the VIP KPI information.
14.3.5 Checking GSM VIP Analysis Tasks

This section describes how to check GSM VIP analysis tasks. You can check the attributes, execution progress, and execution results of a GSM VIP analysis task as required.
14 GSM VIP Analysis
Prerequisite
l l
You have logged in to the Nastar client. A GSM VIP analysis task is created.
Procedure
Step 1 Click the GSM VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Check the attributes of a GSM VIP analysis task Then ... Select a task from the task list in the upper-right pane. Double-click the task or click .
You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 14.3.4 Modifying GSM VIP Analysis Tasks. Check the execution progress of the active Select a task from the task list in the upper-right task pane. Then, you can view the execution progress of the task in the Progress column. Check the task execution results Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
In the drop-down list boxes above the task list, you can set the filter conditions to filter the tasks by the task status, task execution type, and task type. You can also type the keyword of a task name in the text box. Then, the system searches for the tasks by the keyword.
Issue 03 (2010-06-30)
14 GSM VIP Analysis
By clicking , you can restore the preset filtering conditions to the initial state, that is, all the task information is displayed.
l
14.4 Querying GSM VIP Analysis Reports

This section describes how to query GSM VIP analysis reports. By monitoring the number of service call reports, traffic, and KPIs of the selected VIP subscriber, you can learn about the service quality of the VIP subscriber and identify and solve the network problems that may cause VIP subscriber complaints.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the VIP analysis function. The E2E task, collection task, and data import task corresponding to the VIP analysis task are normal. The VIP analysis task is executed successfully.
Procedure
Step 1 Click the GSM VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. All the analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose GSM VIP Analysis Task from the shortcut menu. The GSM VIP Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select one VIP subscriber or VIP group from the VIP group overview table on the left of the GSM VIP Analysis Task window, and then view the details of the KPIs of each service and the change trend of these KPIs on the CS Service KPI and Active Cell tab pages on the right.
l
When a VIP group is selected as the analysis object, the KPI list area on the right does not display the change trend of the KPIs. Initially, Object above the VIP group overview table on the left is set to All. After you change the value to User, information box Please Choose Group is displayed for selection, namely, selection of the VIP group to be analyzed. In this case, the VIP group overview table displays the KPI overview information of all VIP subscribers in the specified group. In addition, the
14-18
14 GSM VIP Analysis
area below the KPI list on the right displays the change trend of a specific KPI of the selected VIP subscriber. You can double-click the change trend chart to zoom in on the chart, and then double-click the chart again to restore the chart to the original size.
l
The display options provided for different change trend charts are as follows:
In the change trend chart of a CS KPI, the options to display originated-call connection delay, terminated-call connection delay, and service duration are provided.
Select one VIP group or VIP subscriber from the VIP group overview table on the left of the window, and then click the Active Cell tab on the right of the window to view the analysis result and geographical display result of the active cell corresponding to the selected VIP group or VIP subscriber. The description of the geographical display of the active cell corresponding to the VIP group or VIP subscriber is as follows:
If the geographical display is started for the first time, the analysis result list of the active cell does not contain any record, and all the active cells involved in the selected VIP group or VIP subscriber are highlighted on the map. You can switch between different KPIs through the shortcut menu prompted when rightclicking on the map. When you switch to a specific KPI, all active cells that serve the selected VIP group or VIP subscriber and contain the KPI are highlighted on the map. These active cells are rendered in different colors according to the number of times that VIP subscribers present in each active cell. With the increase in the number of times that VIP subscribers present in an active cell, the darkness of the rendering color increases. The rendering configuration can be modified as required.
In addition, the KPI values of a selected VIP group or VIP subscriber in an active cell can be displayed in labels next to the active cell on the map.
For description of the parameters, see 14.6.4 Parameters for Querying GSM VIP Analysis Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 14.5 Exporting GSM VIP Analysis Reports. If certain KPIs of a VIP subscriber are abnormal according to the query result and thus further analysis is required, select the basic information of the VIP subscriber and then choose Start Further Analysis from the shortcut menu to start the complaint analysis support function for further analysis. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
Issue 03 (2010-06-30)
14-19
14 GSM VIP Analysis
14.5 Exporting GSM VIP Analysis Reports

This section describes how to export GSM VIP analysis reports. You can export the queried VIP analysis results as .csv or .xls files as required. The exported VIP analysis results help you identify and solve the network problems that may cause VIP subscriber complaints.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the GSM VIP analysis reports.
Procedure
Step 1 Click in the GSM VIP Analysis Task window. The Save As dialog box is displayed.
14.6 Reference to the GSM VIP Analysis Interface

This section describes the interface for GSM VIP analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of GSM VIP analysis. 14.6.1 Parameters for Creating and Modifying GSM VIP Subscribers/VIP Groups This section describes the parameters for creating and modifying GSM VIP subscribers and VIP groups. You can refer to the description when creating and modifying a GSM VIP subscriber and VIP group. 14.6.2 Parameters for Creating GSM E2E Tasks This section describes the parameters for creating GSM E2E tasks. You can refer to the description when creating a GSM E2E task. 14.6.3 Parameters for Creating and Modifying GSM VIP Analysis Tasks This section describes the parameters for creating and modifying GSM VIP analysis tasks. You can refer to the description when creating and modifying a GSM VIP analysis task. 14.6.4 Parameters for Querying GSM VIP Analysis Reports This section describes the parameters for querying GSM VIP analysis reports. You can refer to the description when querying a GSM VIP analysis report.
14.6.1 Parameters for Creating and Modifying GSM VIP Subscribers/VIP Groups
This section describes the parameters for creating and modifying GSM VIP subscribers and VIP groups. You can refer to the description when creating and modifying a GSM VIP subscriber and VIP group.
14 GSM VIP Analysis
Description of Parameters Related to VIP Subscribers

Parameter User Name Item Indicates the name of a VIP subscriber. The value range is as follows:
l l l l
A maximum of 128 characters Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' ` Not null Duplicated allowed (a VIP subscriber is allowed to use multiple SIM card) Case sensitive
Phone Number
Indicates the number of a UE used by a VIP subscriber. The value range is as follows:
l l
A combination of 0-digit to 20-digit numerals from 0 to 9 Duplicated allowed
IMSI
Indicates the International Mobile Subscriber Identity (IMSI) of a VIP subscriber. The value range is as follows:
l l
A combination of 15-digit numerals from 0 to 9 Unique and not null
Description
Indicates the description of the VIP subscriber. The value range is as follows:
l l
Description of Parameters Related to VIP Groups

Parameter Group Name Item Indicates the name of a VIP group. The value range is as follows:
l l l l
Priority
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.
Issue 03 (2010-06-30)
14-21
14 GSM VIP Analysis
Item Indicates the description of the VIP group. The value range is as follows:
l l
Group Member
Indicates the information about members in the VIP group.


Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a neighboring cell measurement task. Indicates the name of the OSS related to the task. Select the GSM Neighbor Cell Data Task node. Indicates the time when the task starts to run. The start time must be later than the current time. By default, the start time is five minutes later than the current system time. Persist Time (Minute) Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 65535. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15. Measurement 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 15 minutes. For example, if this parameter is set to 2, the measurement time of each ARFCN is 215 minutes, that is, 30 minutes.
14-22
Issue 03 (2010-06-30)
14 GSM VIP Analysis
Parameter Measurement step length
Description 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 to the minimum rest step of the selected cell. Cell Object Displays the frequency information. Indicates the cell related to the neighboring cell measurement task. Indicates the set of ARFCNs to be measured. The ARFCNs are classified by group. The number of ARFCNs of each group is determined by Measure Step.
NOTE
Step.
ASSThres
Issue 03 (2010-06-30)
14-23
14 GSM VIP Analysis

NOTE
l l l

l l l l l l
Cell Object
Indicates the name of a cell related to the uplink frequency scanning task.
14-24
Issue 03 (2010-06-30)
14 GSM VIP Analysis
Parameter Frequency Type
Description Indicates the types of the test ARFCNs. The options are as follows:
l

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a VIP analysis data task. Indicates the name of the OSS related to the task. Select the GSM VIP Analysis Task node. Indicates the time when the VIP analysis data task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the VIP analysis data task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Selected Indicates the NE object related to the VIP analysis data task. If you select this parameter, the content in the Report Raw Data field corresponding to the VIP group can be selected. Indicates the name of a VIP group. Indicates the number of members in the VIP group.
Group Name Number of Members
Issue 03 (2010-06-30)
14-25
14 GSM VIP Analysis
Parameter Report Raw Data
Description Indicates that the raw call data is also collected during the collection of the KPI aggregation information of all VIP objects of the selected VIP groups, thus helping to analyze problems thoroughly. Indicates the description of the VIP group.
Description

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a GSM/UMTS neighboring cell data task. Indicates the name of the OSS related to the task. Select the GSM/UMTS Neighboring Cell Data Task node. Indicates the time when the GSM/UMTS neighboring cell data task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the GSM/UMTS neighboring cell data task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Indicates the NE object related to the GSM/ UMTS neighboring cell data task.

Parameter Basic information Task Name OSS Name E2E Task List Description Indicates the name of a cell performance analysis task Indicates the name of the OSS related to the task Select the GSM Cell Performance Data Task node.
14-26
Issue 03 (2010-06-30)
14 GSM VIP Analysis
Description Indicates the time when the cell performance analysis task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the cell performance analysis task is stopped. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE object Service Type Exception Type Indicates the NE object related to the cell performance analysis task. Indicates service types involved during the exception determination, such as Voice Service. Indicates the exception types involved during the exception determination, such as Short service duration. Indicates the KPIs involved during the exception determination. Indicates the types of exception determination, such as >=. Indicates the exception threshold involved during the exception determination, such as 30. The value is an integer from 0 to 65535.
14.6.3 Parameters for Creating and Modifying GSM VIP Analysis Tasks
This section describes the parameters for creating and modifying GSM VIP analysis tasks. You can refer to the description when creating and modifying a GSM VIP analysis task.
Issue 03 (2010-06-30)
14-27
14 GSM VIP Analysis
Parameter Basic informati on Task Name Item Indicates the name of a VIP analysis task. The value range is as follows:
l l
A maximum of 60 characters Characters not allowed: ~ ! # $ % ^ * + = | \/,'` Unique and not null Case sensitive
l l
Task Type Task Execution Type
Choose GSM VIP Analysis Task from the navigation tree.

l
Remarks
Provides the description of the task. Value range: a maximum of 200 characters
Time informati on
Periodic task
Begin Date
Indicates time for starting a task. The start time must be later than the current server time. You can either enter the time value in this field, or click and select the date and time in the Date Selection dialog box.
Task Start At
Indicates the time when the analysis task is executed. The time specified in this field must not precede the latest end time specified in the Time Setting for Cycle Task Data field.
Cycle
l l
Unit: hour Value range: 1 to 9999
Execution Times
Indicates the number of times a periodic task is executed. If this parameter is set to 0, you can infer that the task is executed all the time. Value range: 0 to 9999. Default value: 0.
14-28
Issue 03 (2010-06-30)
14 GSM VIP Analysis
Parameter Time
Item Indicates the time range of the data to be analyzed.

l
One-Time Task
Data Time Scope
The start time must precede the end time. You can either enter the time value in this field, or click and select the date and time in the Date Selection dialog box.
Task Start At
Indicates the time when the analysis task is executed. The time specified in this field must not precede the end time specified in the Data Time Scope field.
Object informati on
Option
If you select this option, the content in the Report Raw Data field corresponding to the VIP group can be selected. Indicates the name of a VIP group. Indicates the number of members in the VIP group. Indicates that the raw call data is also collected during the collection of the KPI aggregation information of all VIP objects of the selected VIP groups, thus helping to analyze problem thoroughly. Indicates the description of the VIP group. The VIP analysis tasks involve the service type such as CS service KPIs. This field is read-only.
Description Type
KPI Name
Indicates the name of a KPI. This field is read-only.
Issue 03 (2010-06-30)
14-29
14 GSM VIP Analysis
Parameter KPI Threshold Value
Item Indicates the threshold value of a KPI. In the analysis report of the corresponding task, if the KPI value of a corresponding user does not reach the threshold value, it is considered that this is a problem KPI or deteriorated KPI. This parameter can be null. That is, no threshold value is provided.
14.6.4 Parameters for Querying GSM VIP Analysis Reports

This section describes the parameters for querying GSM VIP analysis reports. You can refer to the description when querying a GSM VIP analysis report.
Description of Parameters in the VIP Group Overview Table

Parameter Group Name (Number of Members)\User Name Item Indicates the name of the VIP group or VIP object. The number of members contained in the VIP group is added to the group name. You can select the group name or subscriber name from the dropdown list box to display the related information. Indicates the level of the VIP group or VIP object. Indicates the number of abnormal KPIs. Indicates international mobile subscriber identity of a VIP subscriber. Indicates the number of a UE used by a VIP subscriber.
Level Number of Abnormal KPIs IMSI MS Number
Description of Parameters Related to KPIs in CS Domain

Parameter Total Number of Reports Immediate Assignment Success Rate (%) Number of Immediate Assignment Failures Item Indicates the total number of MRs involved in the KPIs in CS domain. Indicates the success rate of UE accesses.
Indicates the number of access failures.
14-30
Issue 03 (2010-06-30)
14 GSM VIP Analysis
Parameter SDCCH Call Drop Rate (%) Number of SDCCH Call Drops TCH Assignment Success Rate (%) Number of TCH Assignment Failures TCH Call Drop Rate (%) Number of TCH Call Drops Call Setup Success Rate (%) Handover Success Rate (%) Number of Handover Failures Average OriginatedCall Connection Delay (s) Average Terminated-Call Connection Delay (s) Average Duration (s) UL One-Way Audio Rate (%) DL One-Way Audio Rate (%)
Item Indicates the call drop rate in the case that UEs access the network and the signaling is in the stable state. Indicates the number of abnormal call drops in the case that UEs access the network and the signaling is in the stable state. Indicates the success rate of TCH assignments after the network access. Indicates the number of TCH assignment failures after the network access. Indicates the call drop rate when the TCH assignment is complete after the network access. Indicates the number of call drops when the TCH assignment is complete after the network access. Indicates the success rate of call setups after the network access. Indicates the success rate of handovers during calls. Indicates the number of handover failures during calls. Indicates the average connection delay of originated-calls.
Indicates the average connection delay of terminated-calls.
Indicates the average duration of a successful call initiation. Indicates the proportion of one-way audio on the uplink. Indicates the proportion of one-way audio on the downlink.
Description of Parameters of KPIs in Active Cells

Parameter BSC Cell Name CGI Item Indicates the name of the BSC that an active cell belongs to. Indicates the name of an active cell. Indicates the global ID of an active cell.
Issue 03 (2010-06-30)
14-31
14 GSM VIP Analysis
Parameter Number of Signaling Accesses Number of Abnormal Signaling Accesses Number of Signaling Releases Number of Abnormal Signaling Releases Number of Source Cell Handovers Number of Target Cell Handovers Number of Target Cell Handover Failures
Item Indicates the number of signaling accesses of a VIP group or VIP object in an active cell. Indicates the number of abnormal signaling accesses of a VIP group or VIP object in an active cell. Indicates the number of signaling releases of a VIP group or VIP object in an active cell. Indicates the number of abnormal signaling releases of a VIP group or VIP object in an active cell. Indicates the number of source cell handovers of a VIP group or VIP object in an active cell. Indicates the number of target cell handovers of a VIP group or VIP object in an active cell. Indicates the number of target cell handover failures of a VIP group or VIP object in an active cell.
14-32
Issue 03 (2010-06-30)
15 GSM Complaint Analysis Support
15
GSM Complaint Analysis Support
About This Chapter

This section describes the GSM complaint analysis support, including the management of complaint analysis support tasks and the query and export of complaint analysis support reports. The Nastar can quickly locate all the call records that are related to the faulty cell involved in a complaint based on the known faulty cell and IMSI of the complaint subscriber. Through the analysis of causes of access failure, handover failure, and abnormal call drop, the Nastar assists in problem location and solution. This improves the efficiency of handling complaints and increases the subscriber satisfaction. 15.1 Basic Knowledge of GSM Complaint Analysis Support The GSM complaint analysis support function helps you to analyze the subscriber calls that are recorded before and after a complaint and to locate and rectify the fault. This improves the efficiency of handling complaints and increases user satisfaction. 15.2 GSM Complaint Analysis Support Process This section describes the GSM complaint analysis support process. 15.3 Managing GSM Complaint Analysis Support Tasks This section describes how to manage GSM complaint analysis support tasks. You can create, modify, delete, suspend, or restore GSM complaint analysis support tasks. You can also view the status and execution progress of such tasks. 15.4 Querying GSM Complaint Analysis Support Reports This section describes how to query GSM complaint analysis support reports. With this function, you can view the call records of subscribers and the details of each call record. The Nastar provides information about the UE capability, access and release, and service quality regarding each call record to assist you in determining the network location where the problem occurs and the possible causes. 15.5 Exporting GSM Complaint Analysis Support Reports This section describes how to export GSM complaint analysis support reports. You can export the queried complaint analysis support results as .csv or .xls files as required. The exported complaint analysis support results can then assist you in determining the network location where the problem occurs and the possible causes. 15.6 Reference to the GSM Complaint Analysis Support Interface
This section describes the interface for GSM complaint analysis support and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of GSM complaint analysis support.
15-2
Issue 03 (2010-06-30)
15.1 Basic Knowledge of GSM Complaint Analysis Support

The GSM complaint analysis support function helps you to analyze the subscriber calls that are recorded before and after a complaint and to locate and rectify the fault. This improves the efficiency of handling complaints and increases user satisfaction.
Complaint Analysis Support

The Nastar obtains the call history records (CHRs) from the network, and then filters, aggregates, and analyzes data based on a specified history period and detailed call records of subscribers in a specified area, thus assisting in problem location and solving. The complaint analysis support consists of the aggregation and analysis of cause types in call reports from complaint subscribers, aggregation and analysis of information about call reports from complaint subscribers, analysis of detailed information about call reports from complaint subscribers, analysis of procedure before the signaling release in call reports from complaint subscribers, and analysis of active cells in call reports from complaint subscribers.
l
The aggregation and analysis of cause types in call reports from complaint subscribers help network engineers filter and aggregate call reports based on abnormal causes. The cause types are classified into six types: normal, access failed, handover failed, QoS problem, call drop, and other exceptions. For detailed description of cause types, see Table 15-1. Table 15-1 Cause type and related description Cause Type Normal Access failed Item Indicates the call reports recording normal release. Indicates the call reports in which failure occurs in the phase of initial access, signaling stability, or TCH assignment, or before the call setup. Indicates the call reports in which the intra-BSC handover or inter-BSC handover fails. Indicates the call reports recording QoS problems during calls. Indicates the call reports recording call drops. Indicates the call reports recording other exceptions.
Handover failed QoS problem Call drop Other exceptions
The aggregation and analysis of call information of complaint subscribers provide the overview of information about all the filtered call records. The information includes the access time, access cell, release time, release cell, IMSI, IMEI, service duration, link setup type, and call status. This function helps network engineers quickly identify abnormal call records (for example, too-short-time call record) and preliminarily learn the situation of complaint subscribers. The analysis of detailed call records of complaint subscribers provides the detailed information about all the filtered call records. The information includes the subscriber
Issue 03 (2010-06-30)
information, access/release information, CS service information, PS service information, and handover information. This function helps network engineers learn the key events that occur during calls, service usage, and MRs before the signaling release, thus accurately and quickly assisting in problem location.
l
The analysis of procedures before the signaling release in call records of complaint subscribers provides the detailed procedures before the signaling release of all the filtered subscribers. This function helps network engineers locate problems based on the information before the signaling release. The analysis of active cells in call records of complaint subscribers enables network engineers to learn all the cells recorded in abnormal call records.
Limitation
The GSM complaint analysis support function requires the reporting of raw call data from complaint subscribers. The amount of raw data is huge. Therefore, limitation is required to prevent the system from becoming overloaded in the case of concurrent operations by a large number of users. In such a case, the maximum number of complaint subscribers allowed by the Nastar cannot exceed 2,000, and the selected complaint subscribers must be under the same OSS.
15.2 GSM Complaint Analysis Support Process

This section describes the GSM complaint analysis support process. Figure 15-1 shows the general process of GSM complaint analysis support. Figure 15-1 Process of GSM complaint analysis support
Start Set a complaint assistant analysis task Query a complaint assistant analysis report Export a complaint assistant analysis report End
15-4
Issue 03 (2010-06-30)
Table 15-2 Description of GSM complaint analysis support process No. 1 Procedure Creating a complaint analysis support task Querying complaint analysis support reports Item In the Analysis Task Management window on the Nastar client, you can create complaint analysis support tasks. After obtaining the related analysis data from the database, the Nastar analyzes the data and then outputs the analysis result. You can view the analysis results of the complaint analysis support tasks that are executed successfully and also perform comprehensive analysis together with maps. In addition, you can export the result files through the one-key method in the analysis result query interface. You can export analysis result files in the Nastar performance analysis system.
Exporting complaint analysis support reports
15.3 Managing GSM Complaint Analysis Support Tasks

This section describes how to manage GSM complaint analysis support tasks. You can create, modify, delete, suspend, or restore GSM complaint analysis support tasks. You can also view the status and execution progress of such tasks. 15.3.1 Creating GSM Complaint Analysis Support Tasks This section describes how to create a GSM complaint analysis support task. When receiving a subscriber complaint, you can create a GSM complaint analysis support task to search for the subscriber call records related to the complaints based on the cell and subscriber IMSI related to the complaint. This helps the analysis personnel in problem analysis and location. 15.3.2 Modifying GSM Complaint Analysis Support Tasks This section describes how to modify the attributes of the GSM complaint analysis support tasks. You can modify the attributes of the GSM complaint analysis support tasks as required. 15.3.3 Checking GSM Complaint Analysis Support Tasks This section describes how to check GSM complaint analysis support tasks. You can check the attributes, execution progress, and execution results of a GSM complaint analysis support task as required.
15.3.1 Creating GSM Complaint Analysis Support Tasks

This section describes how to create a GSM complaint analysis support task. When receiving a subscriber complaint, you can create a GSM complaint analysis support task to search for the subscriber call records related to the complaints based on the cell and subscriber IMSI related to the complaint. This helps the analysis personnel in problem analysis and location.
Prerequisite
l

Issue 03 (2010-06-30)

l l l
The ItmService process of the Nastar runs normally. You are authorized to perform the complaint analysis support. The related data tracing task is enabled on the NE.
Context
l l
Tasks of this type can be performed only once. The system supports a maximum of 50 tasks of this type. The time range of the data to be analyzed cannot exceed 7 days and the start time must be earlier than the current time. The IMSI file of the complaint subscriber to be imported contains only the IMSI column, as shown in Table 15-3. Table 15-3 Complaint subscriber IMSI file IMSI 460079053010239 460005396052916 460022068262211
Procedure
Step 1 Click in the Analysis Task Management window. The Analysis Task Management-New Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can only be Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 In the NE Filtering area, perform the following operations: 1. 2. 3. Select connect cell or release cell for the filtering. In the OSS Name drop-down list box, select the OSS name for the task. Click Select. In the displayed Cell Selection dialog box, select one or multiple cells. Adding a subscriber 1. 2.
l
Step 7 In the User Filtering area, perform the following operations:

l
Click Add. In the displayed New Task - Add User dialog box, enter the IMSI of the subscriber. Click Confirm. Click Importing(I). The Open dialog box is displayed. Select the edited IMSI file of a complaint subscriber, and then click Open.
Importing a subscriber 1. 2.
15-6
3.
If the imported information is correct and no duplicates of the records exist, click Confirm in the displayed dialog box. If the imported information is correct but certain duplicates of the records exist, the Confirm dialog box is displayed. In this case, click Yes to overwrite the existing records and import the additional records. After the import is complete, click Confirm in the displayed dialog box. You can also click No in the displayed Confirm dialog box to ignore the duplicate records and import the additional records.
If certain abnormal records exist in the information to be imported, the import of the current file is not allowed. In this case, the system displays the number of abnormal records.
Click Export Check Result to export the check result so that you can make modifications based on the error information to complete the current import task. You can click Cancel to terminate the current import task.
Postrequisite
l
Deleting a task You can delete an unnecessary complaint analysis support task to release system resources.
NOTE
1.
Click the GSM Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
button.
Suspending a task To delay the task execution, you can suspend a complaint analysis support task that is in the idle state. Then, the complaint analysis support task becomes a suspended task.
NOTE
The system can schedule only the complaint analysis support tasks that are not suspended.
1.
2.
button.
l
Restoring a task
Issue 03 (2010-06-30)
You can restore a suspended complaint analysis support task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the complaint analysis support tasks that are in the idle state can be scheduled by the system.
1.
2.
button.
15.3.2 Modifying GSM Complaint Analysis Support Tasks

This section describes how to modify the attributes of the GSM complaint analysis support tasks. You can modify the attributes of the GSM complaint analysis support tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the complaint analysis support. A GSM complaint analysis support task is created.
Context
Procedure
Step 1 Click the GSM Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 15.6.1 Parameters for Creating and Modifying GSM Complaint Analysis Support Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, and the filtering method.

15.3.3 Checking GSM Complaint Analysis Support Tasks

This section describes how to check GSM complaint analysis support tasks. You can check the attributes, execution progress, and execution results of a GSM complaint analysis support task as required.
Prerequisite
l l
You have logged in to the Nastar client. A GSM complaint analysis support task is created.
Procedure
Step 1 Click the GSM Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Then ...
Check the attributes of a GSM complaint Select a task from the task list in the upper-right analysis support task pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 15.3.2 Modifying GSM Complaint Analysis Support Tasks. Check the execution progress of the active Select a task from the task list in the upper-right task pane. Then, you can view the execution progress of the task in the Progress column. Check the task execution results Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
In the drop-down list boxes above the task list, you can set the filter conditions to filter the tasks by the task status, task execution type, and task type. You can also type the keyword of a task name in the text box. Then, the system searches for the tasks by the keyword. By clicking , you can restore the preset filtering conditions to the initial state, that is, all the task information is displayed.
15.4 Querying GSM Complaint Analysis Support Reports

This section describes how to query GSM complaint analysis support reports. With this function, you can view the call records of subscribers and the details of each call record. The Nastar provides information about the UE capability, access and release, and service quality regarding each call record to assist you in determining the network location where the problem occurs and the possible causes.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the complaint analysis support. The complaint analysis support task is executed successfully.
Procedure
Step 1 Click the GSM Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. The analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose GSM Complaint Analysis Support Task from the shortcut menu. The GSM Complaint Analysis Support Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a call record from the navigation tree of the call report cause type overview of complaint subscribers on the left of the GSM Complaint Analysis Support Task window, view the call report overview table and the detailed call report table on the right. You can also check the signaling record in the lower pane to learn the signaling information before the call release.

l
The navigation tree of the call report cause type overview of complaint subscribers provides two display modes, namely, Cause type-IMSI and IMSI-Cause type.
In Cause type-IMSI mode, all the call records are classified on the basis of cause types and the call records of each cause type is then classified on the basis of IMSIs. In IMSI-Cause type mode, all the call records are classified on the basis of IMSIs and the call records of each IMSI is then classified on the basis of cause types.
For detailed description of cause types, see 15.1 Basic Knowledge of GSM Complaint Analysis Support.
l
You can find a call record quickly from a great number of call reports by entering the IMSI or cause type in the Find area above the navigation tree of the call report cause type overview of complaint subscribers. In the call report overview table of a complaint subscriber, you can view the overview information of all the filtered call reports. The information includes access time, access cell, release time, release cell, IMSI, IMEI, service duration, and call status. In the detailed call report table of a complaint subscriber, you can view the details of all the filtered call reports. The details include information about the subscriber, call access, call release, and handover. In the table of the signaling flow before the call release associated with the complaint subscriber call report, you can view the detailed signaling flows before the call release of every filtered subscribers. For description of the parameters, see 15.6.2 Parameters for Querying GSM Complaint Analysis Support Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 15.5 Exporting GSM Complaint Analysis Support Reports. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
15.5 Exporting GSM Complaint Analysis Support Reports

This section describes how to export GSM complaint analysis support reports. You can export the queried complaint analysis support results as .csv or .xls files as required. The exported complaint analysis support results can then assist you in determining the network location where the problem occurs and the possible causes.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the GSM complaint analysis support reports.
Issue 03 (2010-06-30)
Procedure
Step 1 Click in the GSM Complaint Analysis Support Task window. The Save As dialog box is displayed. Step 2 Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. ----End
15.6 Reference to the GSM Complaint Analysis Support Interface

This section describes the interface for GSM complaint analysis support and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of GSM complaint analysis support. 15.6.1 Parameters for Creating and Modifying GSM Complaint Analysis Support Tasks This section describes the parameters for creating and modifying GSM complaint analysis support tasks. You can refer to this description when creating and modifying a GSM complaint analysis task. 15.6.2 Parameters for Querying GSM Complaint Analysis Support Reports This section describes the parameters for querying GSM complaint analysis support reports. You can refer to the description when querying a GSM complaint analysis support report.
15.6.1 Parameters for Creating and Modifying GSM Complaint Analysis Support Tasks
This section describes the parameters for creating and modifying GSM complaint analysis support tasks. You can refer to this description when creating and modifying a GSM complaint analysis task.
Parameter Basic information Task Name Item Indicates the name of a complaint analysis task. The value range is as follows:
l l
l l
Task Type
Choose GSM Complaint Analysis Support Task from the navigation tree.
15-12
Issue 03 (2010-06-30)
Parameter Run Type Remarks
Item Such a task can be executed only once in one time period. Provides the description of the task. Value range: a maximum of 200 characters
Time information
Data Time Scope
Task Start At
NE filtering information
NE Filtering OSS Name
You can select access cell or release cell to filter NEs. Indicates the name of an EMS. You can select IMSI to filter call records.
User filtering information
User Filtering
15.6.2 Parameters for Querying GSM Complaint Analysis Support Reports

This section describes the parameters for querying GSM complaint analysis support reports. You can refer to the description when querying a GSM complaint analysis support report.
Description of Parameters in the Call Report Overview Table

Parameter Access Time Access Cell Release Time Release Cell IMSI Item Indicates the time when the signaling accesses during a call. Indicates the name of the cell where signaling accesses. Indicates the time when the signaling is released during a call. Indicates the name of the cell where signaling is released. Indicates the identity number of the international mobile subscriber. IMSI is an abbreviation for International Mobile Subscriber Identity. IMEI Indicates the international mobile station equipment identity. IMEI is an abbreviation for International Mobile Equipment Identity.
Issue 03 (2010-06-30)
15-13
Parameter Called MSISDN Call Duration Service Duration Access Cause Call Setup Result Call Release Result
Item Indicates the phone number of the MTC (Mobile Terminating Call). Indicates the duration of a service call. Indicates the duration of a service, including the call duration and the signaling duration. Indicates the access cause of a service call. Indicates the call setup result of a service call. Indicates the call setup release of a service call.
Description of Parameters Related to Subscribers

Parameter PTMSI/TMSI IMSI IMEI Called MSISDN Item Indicates the temporary subscriber identifier that is allocated by the network in CS domain. Indicates the identity number of the international mobile subscriber. Indicates the international mobile station equipment identity. Indicates the phone number of the MTC (Mobile Terminating Call).
Description of Parameters Related to Call Access

Parameter Access Time Access TA Access Cell Access Carrier Access channel Access cause Call Setup Result Cause of abnormal call setup Subcause of abnormal call setup Item Indicates the time when the signaling accesses during a call. Indicates the TA value during the signaling access. Indicates the name of the cell where signaling accesses. Indicates the carrier number where signaling accesses. Indicates the channel number during signaling access. Indicates the cause in the signaling access request message. Indicates the call setup result of a service call. Indicates the cause of abnormal call setup in the service call. Indicates the detailed cause of abnormal call setup in the service call.
15-14
Issue 03 (2010-06-30)
Description of Parameters Related to Call Release

Parameter Release Time Release Cell Call Release Result Cause of abnormal call completion Subcause of abnormal call completion UL one-way audio during a call DL one-way audio during a call UL call crosstalk DL call crosstalk UL average call signal quality DL average call signal quality UL call VQI DL call VQI Item Indicates the time when the signaling is released during a call. Indicates the name of the cell where signaling is released. Indicates the call release result of a service call. Indicates the cause of abnormal call completion in the service call. Indicates the detailed cause of abnormal call completion in the service call. Indicates whether the uplink one-way audio occurs during a call. Indicates whether the downlink one-way audio occurs during a call. Indicates whether the uplink call crosstalk occurs during a call. Indicates whether the downlink call crosstalk occurs during a call. Indicates whether the uplink average call signal quality occurs during a call. Indicates whether the downlink average call signal quality occurs during a call. Indicates whether the uplink voice quality indicator occurs during a call. Indicates whether the downlink voice quality indicator occurs during a call.
Description of Parameters Related to Handover

Parameter Number of handover records Handover initiating time HO initiation cause Handover source cell Handover target cell Handover result Item Indicates the number of handovers during a call. Indicates the time when a handover is initiated. Indicates the cause of initiating a handover. Indicates the name of the source cell where the handover is initiated. Indicates the name of the target cell where the handover is performed. Indicates whether the handover is successful.
Issue 03 (2010-06-30)
15-15
15-16
Issue 03 (2010-06-30)
16 GSM Cell Performance Analysis
16
GSM Cell Performance Analysis
About This Chapter

This section describes the GSM cell performance analysis, including the management of cell performance analysis tasks and the query and export of cell performance analysis reports. By providing call data of abnormal users in problem cells, the Nastar assists you in analyzing the root cause of abnormal calls. This helps to provide better services and improve user satisfaction. 16.1 Basic Knowledge of GSM Cell Performance Analysis This section describes the basic knowledge of the GSM cell performance analysis function, which facilitates identification of problem cells and enables the Nastar to obtain the data of exceptional calls in problem cells. By analyzing and displaying the data of exceptional calls, the Nastar assists in identifying the causes of problem cells, thus facilitating in-depth problem analysis. 16.2 GSM Cell Performance Analysis Process This section describes the GSM cell performance analysis process. 16.3 Managing GSM Cell Performance Analysis Tasks This section describes how to manage GSM cell performance analysis tasks. You can create, modify, delete, suspend, or restore GSM cell performance analysis tasks. You can also view the status and execution progress of such tasks. 16.4 Querying GSM Cell Performance Analysis Reports This section describes how to query GSM cell performance analysis reports. The Nastar analyzes the call records of abnormal users in all problem cells under the selected NE and identifies the cause and top users. This helps to locate and solve the cell performance exceptions. 16.5 Exporting GSM Cell Performance Analysis Reports This section describes how to export GSM cell performance analysis reports. You can export the queried cell performance analysis results and save them as .xls files as required. The exported cell performance analysis results can then assist you in determining the problem cells on the network. 16.6 Reference to the GSM Cell Performance Analysis Interface This section describes the interface for GSM cell performance analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of GSM cell performance analysis.
16.1 Basic Knowledge of GSM Cell Performance Analysis

This section describes the basic knowledge of the GSM cell performance analysis function, which facilitates identification of problem cells and enables the Nastar to obtain the data of exceptional calls in problem cells. By analyzing and displaying the data of exceptional calls, the Nastar assists in identifying the causes of problem cells, thus facilitating in-depth problem analysis. Generally, the whole-to-partial analysis method is used during the network optimization or performance analysis. That is, the Nastar locates and analyzes network problems by monitoring 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 top problem cells. After that, the Nastar analyzes the top problem cells. At present, the minimum analysis unit of most performance data is a cell. The Nastar, however, provides detailed and in-depth analysis on problem cells. The functions provided by the Nastar are as follows:
l
The Nastar analyzes exceptional call records based on the BSC or NE groups and provides top causes of exceptional cells. This helps network engineers to identify the detailed causes of the exception, thus improving work efficiency. After the main causes of problem cells are identified, the Nastar provides you with an indepth understanding of top users with poor KPIs by providing the function of analyzing top exceptional users in cells. This function helps network engineers to locate a type of top users in problem cells. In this case, network engineers can solve the problems of top users, thus improving cell performance. If problem cells are unknown, the Nastar analyzes top problem cells based on the BSC, thus helping to identify the top problem cells.
The results of cell performance analysis can be exported as .xls files. In this case, users can optimize problem cells in the network according to the exported analysis results.
16.2 GSM Cell Performance Analysis Process

This section describes the GSM cell performance analysis process. Figure 16-1 shows the GSM cell performance analysis process.
16-2
Issue 03 (2010-06-30)
Figure 16-1 Process of GSM cell performance analysis
Issue 03 (2010-06-30)
16-3
Table 16-1 Description of the GSM cell performance analysis process No. 1 Procedure Querying NE data information Creating an end-to-end task for cell performance analysis Description In the Analysis Task Management window on the Nastar client, you can switch to the data query window to query whether the raw data required for the cell performance analysis is imported to the database. On the Nastar client, choose Maintenance > E2E Task Management. In the displayed E2E Task Management window, you can create an E2E task for cell performance analysis. After the task is created, the Nastar sends MML commands to the M2000, and then the M2000 sends MML commands to NEs. After that, the NEs execute the measurement task and generate results. After an E2E task is created, you can view the corresponding collection task that has been created by the system in the Task Management window. A data import task can be performed only after the corresponding collection task is complete. On the Nastar client, choose Maintenance > Task Management. In the displayed Task Management window, create a data import task corresponding to the cell performance analysis task so that the Nastar periodically imports the cell performance analysis data saved as files on the Nastar server to the database. In the Analysis Task Management window on the Nastar client, you can create cell performance analysis tasks. After obtaining the related analysis data from the database, the Nastar analyzes data and then generates the analysis result. You can view the analysis results of the tasks that are successfully performed. In addition, you can export the analysis result files through the one-key method in the analysis result query interface. You can export analysis result files in the Nastar.
Creating a task for importing data of cell performance analysis Creating a cell performance analysis task Querying cell performance analysis reports
Exporting cell performance analysis reports
16.3 Managing GSM Cell Performance Analysis Tasks

This section describes how to manage GSM cell performance analysis tasks. You can create, modify, delete, suspend, or restore GSM cell performance analysis tasks. You can also view the status and execution progress of such tasks. 16.3.1 Creating GSM E2E Tasks This section describes how to create GSM end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result.
16.3.2 Creating GSM Cell Performance Analysis Tasks This section describes how to create GSM cell performance analysis tasks. In a GSM cell performance analysis task, the Nastar analyzes the abnormal call records associated with all problem cells under the selected NE to identify the cause of the abnormal calls. This function helps operators locate and rectify network faults in key areas, thus improving the service quality and enhancing the user experience in the key areas. 16.3.3 Modifying GSM Cell Performance Analysis Tasks This section describes how to modify the attributes of the GSM cell performance analysis tasks. You can modify the attributes of the GSM cell performance analysis tasks as required. 16.3.4 Checking GSM Cell Performance Analysis Tasks This section describes how to check GSM cell performance analysis tasks. You can check the attributes, execution progress, and execution results of a GSM cell performance analysis task as required.

Prerequisite
l l l
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Perform the following operations as required: If You Want to ... Add a GSM neighboring cell measurement task Add a GSM uplink frequency scan task Then ... Perform Step 4. Perform Step 5.
Issue 03 (2010-06-30)
16-5
If You Want to ... Add a GSM VIP analysis task Add a GSM/UMTS neighboring cell data task Add a GSM cell performance data task
Then ... Perform Step 6. Perform Step 7. Perform Step 8.
l l l l
4.
CAUTION
It is recommended that the number of test cells under one BSC does not exceed 200. If the recommended value is exceeded, certain cells may fail to report complete data. The upper threshold is 400. 5. Optional: Click Frequency Analysis to traverse the three level neighboring cells of the selected cell. The Nastar then analyzes the BCCH frequencies of the traversed neighboring cells and highlights these BCCH frequencies in the frequency selection area in gray to provide reference for measurement frequency analysis. Traversing of the three level neighboring cells indicates that the Nastar searches for the neighboring cells of the selected cell (neighboring cell A), the neighboring cells of neighboring cells A (neighboring cell B), and the neighboring cells of neighboring cells B (neighboring cell C). All traversed neighboring cells A, B, and C are neighboring cells obtained through the traversing of the three level neighboring cells.
6.
Set the ARFCNs.

NOTE
7.
8.
4.
5.
Step 6 Perform the following operations to add a GSM VIP analysis task:
1.
Set the basic information about the task. a. b. c. In the Task Name field, enter the name of the VIP analysis task. In the OSS name drop-down list box, select the OSS name for the task. In E2E Task List, select GSM VIP Analysis Data Task.
2.
3.
4.
2.
3.
2.
Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type
16-8
the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. 3. 4. Click Next and then set the exception value for each KPI in the exception value setting list. Click Finish. The added cell performance analysis task is displayed in the task list. ----End
Postrequisite
NOTE
16.3.2 Creating GSM Cell Performance Analysis Tasks

This section describes how to create GSM cell performance analysis tasks. In a GSM cell performance analysis task, the Nastar analyzes the abnormal call records associated with all problem cells under the selected NE to identify the cause of the abnormal calls. This function helps operators locate and rectify network faults in key areas, thus improving the service quality and enhancing the user experience in the key areas.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the function of cell performance analysis. The E2E task, collection task, and data import task corresponding to the cell performance analysis task are normal. The cell performance analysis task can be created successfully even if the prerequisites are not met. The execution of the cell performance analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Issue 03 (2010-06-30)
16-9
Context
l l
Tasks of this type can be performed only once. A maximum of 50 tasks of this type can be created and the time range of the data in a task cannot exceed six days, that is, the start time and end time are both within three past days and three coming days. Before you create an analysis task, check to ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. Execution Type can only be set to Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects on the tab page.
l

Postrequisite
l
Deleting a task You can delete an unnecessary cell performance analysis task to release system resources.
NOTE
1.
Click the GSM Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
16-10
button.
Issue 03 (2010-06-30)

l
Suspending a task To delay the task execution, you can suspend a cell performance analysis task that is in the idle state. Then, the cell performance analysis task becomes a suspended task.
NOTE
The system can schedule only the cell performance analysis tasks that are not suspended.
1.
2.
button.
l
Restoring a task You can restore a suspended cell performance analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the cell performance analysis tasks that are in the idle state can be scheduled by the system.
1.
2.
button.
16.3.3 Modifying GSM Cell Performance Analysis Tasks

This section describes how to modify the attributes of the GSM cell performance analysis tasks. You can modify the attributes of the GSM cell performance analysis tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the function of cell performance analysis. A GSM cell performance analysis task is created.
Context
Procedure
Step 1 Click the GSM Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window.
If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 16.6.2 Parameters for Creating or Modifying GSM Cell Performance Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, and the information about the NE object selection.
16.3.4 Checking GSM Cell Performance Analysis Tasks

This section describes how to check GSM cell performance analysis tasks. You can check the attributes, execution progress, and execution results of a GSM cell performance analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A GSM cell performance analysis task is created.
Procedure
Step 1 Click the GSM Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Then ...
Check the attributes of a cell performance Select a task from the task list in the upperanalysis task right pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 16.3.3 Modifying GSM Cell Performance Analysis Tasks. Check the execution progress of the active Select a task from the task list in the uppertask right pane. Then, you can view the execution progress of the task in the Progress column.
16-12
Issue 03 (2010-06-30)
If You Want to ... Check the task execution results
Then ... Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
16.4 Querying GSM Cell Performance Analysis Reports

This section describes how to query GSM cell performance analysis reports. The Nastar analyzes the call records of abnormal users in all problem cells under the selected NE and identifies the cause and top users. This helps to locate and solve the cell performance exceptions.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the function of cell performance analysis. The cell performance analysis task is executed successfully.
Issue 03 (2010-06-30)
16-13
Procedure
Step 1 Click the GSM Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. The analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose Complaint Analysis from the shortcut menu. The GSM Cell Performance Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell node from the object navigation tree in the left pane of the window, and then you can view the KPI overview information of the selected cell and the ranking overview information of each KPI in the areas in the middle and on the right of the window.
l
The exception types of the cells are displayed in a table and a pie chart in the middle area, that is, Area (3) and Area (4).
The table lists the number of records of each exception type and the percentage of each exception type to all exceptions in the report. The cell performance exception is analyzed from two aspects, namely, objective network exception and subjective experience exception.
The objective network exception is classified into six types, namely, immediate assignment failure, SDCCH call drop, TCH assignment failure, TCH call drop, outgoing handover failure, and incoming handover failure. The subjective experience exception is classified into five types, namely, long connection delay for originated-call, long connection delay for terminated-call, short service duration, uplink one-way audio, and downlink one-way audio.
The pie chart displays the percentage of each service regarding each exception type.
In the area on the right, namely, Area (5) and Area (6), the top users identified by IMSIs, top cells, and top exceptions are illustrated in tables and pie charts. The tables and pie charts show the number of exception records and the percentage of each exception type.
You can set Quantity in Area (8) to determine the number of top users, top cells, and top exception causes. By default, top 10 users, cells, and exception causes are displayed. The default number can not be modified. Analyze Top exceptional cells is valuable in Area (8) only when the overview node or NE group node is selected in the object navigation tree in the left pane of the window.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 16.5 Exporting GSM Cell Performance Analysis Reports. To query chart properties, and save, print, and resize the chart in the chart area, perform the following operations:
16-14
The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
16.5 Exporting GSM Cell Performance Analysis Reports

This section describes how to export GSM cell performance analysis reports. You can export the queried cell performance analysis results and save them as .xls files as required. The exported cell performance analysis results can then assist you in determining the problem cells on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the GSM cell performance analysis reports.
Procedure
in the GSM Cell Performance Analysis Task window. The Save As dialog box is Step 1 Click displayed. Step 2 Set a file name and specify the save path and file type. Then, click Save. The saved .xls file is opened automatically so that you can view it conveniently. The exported results are displayed in different worksheets. The following information is included in an exported report: cell performance analysis overview, KPIs of the top 20 abnormal users, and KPIs associated with the top 20 causes. ----End
Issue 03 (2010-06-30)
16-15
16.6 Reference to the GSM Cell Performance Analysis Interface

This section describes the interface for GSM cell performance analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of GSM cell performance analysis. 16.6.1 Parameters for Creating GSM E2E Tasks This section describes the parameters for creating GSM E2E tasks. You can refer to the description when creating a GSM E2E task. 16.6.2 Parameters for Creating or Modifying GSM Cell Performance Analysis Tasks This section describes the parameters for creating or modifying GSM cell performance analysis tasks. You can refer to the description when creating or modifying a GSM cell performance analysis task. 16.6.3 Parameters for Querying the GSM Cell Performance Analysis Report This section describes the parameters for querying the GSM cell performance analysis report. You can refer to the description when querying the GSM cell performance analysis report.


Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a neighboring cell measurement task. Indicates the name of the OSS related to the task. Select the GSM Neighbor Cell Data Task node. Indicates the time when the task starts to run. The start time must be later than the current time. By default, the start time is five minutes later than the current system time. Persist Time (Minute) Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 65535. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15.
16-16
Issue 03 (2010-06-30)
Parameter Measurement period
Description 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 15 minutes. For example, if this parameter is set to 2, the measurement time of each ARFCN is 215 minutes, that is, 30 minutes. Measurement step length 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 to the minimum rest step of the selected cell. Cell Object Displays the frequency information. Indicates the cell related to the neighboring cell measurement task. Indicates the set of ARFCNs to be measured. The ARFCNs are classified by group. The number of ARFCNs of each group is determined by Measure Step.
NOTE
Step.
ASSThres
Issue 03 (2010-06-30)
16-17
NOTE
l l l

l l l l l l
Cell Object
Indicates the name of a cell related to the uplink frequency scanning task.
16-18
Issue 03 (2010-06-30)
Parameter Frequency Type
Description Indicates the types of the test ARFCNs. The options are as follows:
l

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a VIP analysis data task. Indicates the name of the OSS related to the task. Select the GSM VIP Analysis Task node. Indicates the time when the VIP analysis data task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the VIP analysis data task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Selected Indicates the NE object related to the VIP analysis data task. If you select this parameter, the content in the Report Raw Data field corresponding to the VIP group can be selected. Indicates the name of a VIP group. Indicates the number of members in the VIP group.
Group Name Number of Members
Issue 03 (2010-06-30)
16-19
Parameter Report Raw Data
Description Indicates that the raw call data is also collected during the collection of the KPI aggregation information of all VIP objects of the selected VIP groups, thus helping to analyze problems thoroughly. Indicates the description of the VIP group.
Description

Parameter Basic information Task Name OSS Name E2E Task List Measurement information Start Time Description Indicates the name of a GSM/UMTS neighboring cell data task. Indicates the name of the OSS related to the task. Select the GSM/UMTS Neighboring Cell Data Task node. Indicates the time when the GSM/UMTS neighboring cell data task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the GSM/UMTS neighboring cell data task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Indicates the NE object related to the GSM/ UMTS neighboring cell data task.

Parameter Basic information Task Name OSS Name E2E Task List Description Indicates the name of a cell performance analysis task Indicates the name of the OSS related to the task Select the GSM Cell Performance Data Task node.
16-20
Issue 03 (2010-06-30)
Description Indicates the time when the cell performance analysis task is executed. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the cell performance analysis task is stopped. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE object Service Type Exception Type Indicates the NE object related to the cell performance analysis task. Indicates service types involved during the exception determination, such as Voice Service. Indicates the exception types involved during the exception determination, such as Short service duration. Indicates the KPIs involved during the exception determination. Indicates the types of exception determination, such as >=. Indicates the exception threshold involved during the exception determination, such as 30. The value is an integer from 0 to 65535.
16.6.2 Parameters for Creating or Modifying GSM Cell Performance Analysis Tasks
This section describes the parameters for creating or modifying GSM cell performance analysis tasks. You can refer to the description when creating or modifying a GSM cell performance analysis task.
Issue 03 (2010-06-30)
16-21
Parameter Basic information Task Name Description Indicates the name of a cell performance analysis task. Value range:
l l
l l
Task Type Task Execution Type Remarks
Select GSM Cell Performance Analysis Task in the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range: a maximum of 200 characters
Time information
Data Time Scope
The start time must precede the end time. You can either enter the time value in this field or click and select the date and time in the Date Selection dialog box. This parameter is valid for only one-time tasks.
Task Start At
Object information
BSC Cell Group
If you select this option, the navigation tree displays all the BSCs on the entire network. If you select this option, the navigation tree displays all the cell groups on the entire network.
16.6.3 Parameters for Querying the GSM Cell Performance Analysis Report
This section describes the parameters for querying the GSM cell performance analysis report. You can refer to the description when querying the GSM cell performance analysis report.
16-22
Issue 03 (2010-06-30)
Description of parameters in the exception type overview table

Parameter Service Type Description Indicates types of cell exceptional services, such as Voice Service. Cell exceptional performance can be analyzed on the basis of objective network exceptions and subjective exceptions.
l
Objective network exceptions can be classified into the following types:

Immediate assignment failure SDCCH call drop TCH assignment failure TCH call drop Outgoing HO failure Originated-call connection delay long Terminated-call connection delay long Short service duration UL one-way audio DL one-way audio
Subjective exceptions can be classified into the following types:

Number of Reports Ratio(%)
Indicates the number of exceptional call records of an exception type. Indicates the proportion of an exception type.
Description of parameters in the exception type ranking table

Parameter Description Select rank modes, which consist of the following types:
l l l
Analyze Top exceptional causes Analyze Top exceptional subscribers Analyze Top exceptional cells
Quantity Ratio(%)
Set the number of displayed objects. Indicates the proportion of exception types, cells, and users.
Issue 03 (2010-06-30)
16-23
17 UMTS Centralized Task Management
17
UMTS Centralized Task Management
About This Chapter

The Nastar provides centralized management for the UMTS timing tasks. By setting UMTS timing tasks, you can collect data from the EMS periodically, save the data as a file in certain path on the Nastar system, and import the data from the file to the database periodically for future query and analysis. In addition, you can delete the data whose storage duration has expired from the database at the preset time to save system resources. By using the function of UMTS centralized task management, you can create, modify, delete, suspend, resume, or cancel a UMTS timing task. In addition, you can view information such as status and progress of a task. 17.1 Basic Knowledge of UMTS Centralized Task Management UMTS centralized task management involves the concepts such as types of timing tasks, parameters for task scheduling, and states of timing tasks. Learning the basic knowledge of the UMTS centralized task management helps you perform the operations related to the UMTS centralized task management. 17.2 Creating a UMTS User-Defined Timing Task The Nastar allows you to create UMTS timing tasks. Thus, you can create UMTS timing tasks by setting common parameters and extended parameters based on the requirements of network maintenance. 17.3 Modifying a UMTS User-Defined Timing Task The Nastar allows you to modify certain parameters of a UMTS user-defined timing task. If the execution of a UMTS user-defined timing task is complete, you cannot modify the task. 17.4 Modifying a UMTS Data Deletion Task This section describes how to modify a UMTS data deletion task. If data is periodically imported to the Nastar database, the database resources may be insufficient. By performing the UMTS data deletion task, the Nastar can delete the data whose storage duration has expired from the database at the preset time to save system resources. A UMTS data deletion task is a system timing task. You can modify only certain parameters of the task. To modify a UMTS data deletion task, you must be a user in the administrator group. If the execution of a UMTS data deletion task is complete, you cannot modify the task. 17.5 Modifying the Task of Backing Up Data This section describes how to modify certain information about the system-created task of backing up data.
17.6 Setting the Suspend or Resume Time of a Timing Task You can set an automatic suspend time or an automatic resume time for a timing task. In this situation, the Nastar automatically suspends the task or resumes the task. 17.7 Viewing Timing Tasks Through the Nastar function of viewing timing tasks, you can view the status of all timing tasks in a centralized manner. This helps you adjust the concerned timing tasks according to actual conditions. 17.8 Reference to the UMTS Centralized Task Management Interface This section describes the interface for the UMTS centralized task management and related information such as the parameters used in the centralized task management. This help you understand the functions of the UMTS centralized task management.
17-2
Issue 03 (2010-06-30)
17.1 Basic Knowledge of UMTS Centralized Task Management

UMTS centralized task management involves the concepts such as types of timing tasks, parameters for task scheduling, and states of timing tasks. Learning the basic knowledge of the UMTS centralized task management helps you perform the operations related to the UMTS centralized task management. 17.1.1 Types of Timing Tasks The Nastar divides timing tasks into different types according to execution periods and task features. 17.1.2 System Timing Tasks The system timing task is created during the installation or upgrade of the Nastar system. User dbuser is the Creator of the system timing task. 17.1.3 User Timing Task A user timing task is a customized task that is created to maintain a network. 17.1.4 Task Scheduling Parameters The task scheduling parameters are the parameters related to the task execution type, consisting of task start time, task execution period, and execution times. 17.1.5 States of a Timing Task A timing task has four states: idle, running, suspended, and finished. 17.1.6 Customizing the Interface for Managing Timing Tasks This section describes how to customize the interface for managing timing tasks. The system can display timing tasks of the specified function type in the navigation tree or display the timing tasks that meet the conditions in the task list.


Issue 03 (2010-06-30)
17-3

According to different task features, the Nastar divides the managed tasks into two types: system timing tasks and user timing tasks. Table 17-2 describes the meanings of each task type. Table 17-2 Tasks Divided According to Task Features Task Type System Timing Tasks Description System timing tasks are necessary for the Nastar system to run properly. For details, see 17.1.2 System Timing Tasks. User timing tasks are the user-defined tasks that are created to meet the requirement of network maintenance. For details, see 17.1.3 User Timing Task.
User Timing Tasks

NOTE
l l

l l

The task scheduling parameters are the parameters related to the task execution type, consisting of task start time, task execution period, and execution times. Table 17-3 describes the task scheduling parameters.
17-4
Issue 03 (2010-06-30)
Table 17-3 Description of the task description parameters Parameter Task Type Description According to different task execution periods, the Nastar divides the execution types of the managed timing tasks into two types: periodic execution and one-time execution. The execution type of the system timing tasks is periodic execution. The execution type of the other user timing tasks can be periodic execution or one-time execution. Indicates start time of periodic tasks and one-time tasks set during task creation, including date and time. The start time of tasks should be later than the current server time.
l
Task start time
Period
Run Times
l l l l

A timing task has four states: idle, running, suspended, and finished. The states of a timing task change with different operations. For details, see Figure 17-1.
Issue 03 (2010-06-30)
17-5
Figure 17-1 State transition of a timing task

l l l l l l

Prerequisite
Procedure
Step 1 Choose Maintenance > Task Management, the Task Management window is displayed.
Step 2 Perform different operations according to different customized requirement. Customized Requirement Operation
17.2 Creating a UMTS User-Defined Timing Task

The Nastar allows you to create UMTS timing tasks. Thus, you can create UMTS timing tasks by setting common parameters and extended parameters based on the requirements of network maintenance. 17.2.1 Creating a Task of Importing UMTS Uplink-Interference Data A task of importing UMTS uplink-interference data is performed to import data from the uplinkinterference data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS uplink-interference data. 17.2.2 Creating a Task of Importing UMTS Neighboring-Cell Analysis Data A task of importing UMTS neighboring-cell analysis data is performed to import data from the neighboring-cell analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS neighboring-cell analysis data. 17.2.3 Creating a Task of Importing UMTS/GSM Neighboring-Cell Analysis Data A task of importing UMTS/GSM neighboring-cell analysis data is performed to import data from the UMTS/GSM neighboring-cell analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS/ GSM neighboring-cell analysis data. 17.2.4 Creating a Task of Importing UMTS Configuration Data A task of importing UMTS configuration data is performed to import data from the configuration data file in the specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS configuration data. 17.2.5 Creating a Task of Importing UMTS Coverage Analysis Data
A task of importing UMTS coverage analysis data is performed to import data from the coverage analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS coverage analysis data. 17.2.6 Creating a Task of Importing UMTS VIP Analysis Data A task of importing UMTS VIP analysis data is performed to import data from the VIP data file in the specified directory on the server to the database at the preset time. 17.2.7 Creating a Task of Importing UMTS Pilot Pollution Analysis Data A task of importing UMTS pilot pollution analysis data is performed to import data from the pilot pollution analysis data file in the specified directory on the server to the database at the preset time. 17.2.8 Creating a Task of Importing UMTS Cell Performance Analysis Data A task of importing UMTS cell performance analysis data is performed to import data from the cell performance analysis data file in the specified directory on the server to the database at the preset time. 17.2.9 Creating a Task of Importing UMTS Engineering Parameters A task of importing UMTS engineering parameters is performed to import data from the engineering parameter file in the specified directory on the server to the database at the preset time.
17.2.1 Creating a Task of Importing UMTS Uplink-Interference Data

A task of importing UMTS uplink-interference data is performed to import data from the uplinkinterference data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS uplink-interference data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The UMTS uplink-interference data is collected to the Nastar server.
Context
l l
A task of importing UMTS uplink-interference data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
17-8
Issue 03 (2010-06-30)

TIP
You can choose Task Type > Import UMTS Data from the navigation tree and then double-click Import UMTS Uplink Interference Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import UMTS Uplink Interference Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. Select the task of importing uplink-interference data from Task Type.
Step 4 Click Next to set the execution time of the task and other related parameters. 1. Click
NOTE
You can also set the start time in the Start Time area.
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Suspending a task automatically

Issue 03 (2010-06-30)
Select a timing task to be suspended from the task list in the right pane. Right-click and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Suspend Time and set its value. Click OK. To set the time for automatically suspending a task, see 17.8.16 Parameters for Setting the Time of a Timing Task.
l
NOTE
1. 2.
NOTE
1. 2. 3.
l
17.2.2 Creating a Task of Importing UMTS Neighboring-Cell Analysis Data

A task of importing UMTS neighboring-cell analysis data is performed to import data from the neighboring-cell analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS neighboring-cell analysis data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The UMTS neighboring-cell analysis data is collected to the Nastar server.
Context
l l
A task of importing UMTS neighboring-cell analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
TIP
You can choose Task Type > Import UMTS Data from the navigation tree and then double-click Import UMTS Intra-Frequency Neighboring Cell Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import UMTS Intra-Frequency Neighboring Cell Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. Select the neighboring-cell analysis data import task from Task Type.
NOTE
2.
Postrequisite
l
Issue 03 (2010-06-30)
17-11

NOTE
l l l
1. 2. 3. 4.
l
NOTE
1. 2.
Canceling a task
17-12
You can cancel a running task. After a task is canceled, its state is changed from Running to Idle.
NOTE
1. 2. 3.
l
17.2.3 Creating a Task of Importing UMTS/GSM Neighboring-Cell Analysis Data

A task of importing UMTS/GSM neighboring-cell analysis data is performed to import data from the UMTS/GSM neighboring-cell analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS/ GSM neighboring-cell analysis data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The UMTS/GSM neighboring-cell analysis data is collected to the Nastar server.
Context
l
A task of importing UMTS/GSM neighboring-cell analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
TIP
You can choose Task Type > Import UMTS Data from the navigation tree and then double-click Import UMTS/GSM Neighboring Cell Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import UMTS/GSM Neighboring Cell Analysis Data by default.
Step 3 Set the basic information about the task.

1. 2.
Type the name of the task in Task Name. Select the UMTS/GSM neighboring-cell analysis data import task from Task Type.
Step 4 Click Next to set the execution time of the task and other related parameters. 1. Click . In the displayed Date/Time Selection dialog box, set the start time. You can also set the start time in the Start Time area.
NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Resuming a task
17-14
You can resume a suspended task to the idle state. Then, the task can be scheduled by the system.
NOTE
1. 2.
NOTE
1. 2. 3.
l
17.2.4 Creating a Task of Importing UMTS Configuration Data

A task of importing UMTS configuration data is performed to import data from the configuration data file in the specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS configuration data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The UMTS configuration data is collected to the Nastar server.
Issue 03 (2010-06-30)
For details of creating the performance data collection task, see 8.2.1 Creating a Data Collection Task.
Context
l l
A task of importing UMTS configuration data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
TIP
You can choose Task Type > Import UMTS Data from the navigation tree and then double-click Import UMTS CFG Data. The New Task dialog box is displayed. The Task Type parameter is set to Import UMTS CFG Data by default.
NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3.
17-16
Choose Task Type from the navigation tree in the left pane of the Task Management window. Select the timing task from the task list in the right pane. Click Delete.
4.
l
In the Confirm dialog box, click Yes. Then, the task is deleted from the task list.
NOTE
1. 2.
NOTE
1. 2.
Choose Task Type from the navigation tree in the right pane of the Task Management window. Select the running task from the task list in the right pane. Right-click and choose Cancel.
Issue 03 (2010-06-30)
3.
l
In the Confirm dialog box, click Yes. Then, the task state is changed from Running to Idle.
17.2.5 Creating a Task of Importing UMTS Coverage Analysis Data

A task of importing UMTS coverage analysis data is performed to import data from the coverage analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing UMTS coverage analysis data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The UMTS coverage analysis data is collected to the Nastar server.
Context
l l
A task of importing UMTS coverage analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
TIP
You can choose Task Type > Import UMTS Data from the navigation tree and then double-click Import UMTS Coverage Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import UMTS Coverage Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. Select the coverage analysis data import task from Task Type.
NOTE
2.
Step 5 Click Finish.

The new task is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
NOTE
1. 2.
Issue 03 (2010-06-30)
17-19
NOTE
1. 2. 3.
l
17.2.6 Creating a Task of Importing UMTS VIP Analysis Data

A task of importing UMTS VIP analysis data is performed to import data from the VIP data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to the UMTS VIP analysis is saved on the Nastar server.
Context
l l
The task of importing UMTS VIP analysis data is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month. For the tasks of one type, only one user-defined scheduled task of this type can be created.
Procedure

TIP
Choose Task Type > UMTS Data Import > Import UMTS VIP Analysis Data from the navigation tree. Double-click the node, the New Task dialog box is displayed. The Task Type parameter is set to Import UMTS VIP Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Enter the name of the scheduled task in Task Name. Select the VIP analysis data import task from Task Type.

NOTE
. In the displayed Date/Time Selection dialog box, set the start time of the task.
2.
Step 5 Click Finish. The new VIP analysis data import task is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Suspending a task automatically

Issue 03 (2010-06-30)
Select a timing task to be suspended from the task list in the right pane. Right-click and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Suspend Time and set its value. Click OK. To set the time for automatically suspending a task, see 17.8.16 Parameters for Setting the Time of a Timing Task.
l
NOTE
1. 2.
NOTE
1. 2. 3.
l
17.2.7 Creating a Task of Importing UMTS Pilot Pollution Analysis Data

A task of importing UMTS pilot pollution analysis data is performed to import data from the pilot pollution analysis data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to the UMTS pilot pollution analysis is saved on the Nastar server.
Context
l l
The task of importing UMTS pilot pollution is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month. For the tasks of one type, only one user-defined scheduled task of this type can be created.
Procedure
TIP
Choose Task Type > UMTS Data Import > Import UMTS Pilot Pollution Analysis Data from the navigation tree. Double-click the node, the New Task dialog box is displayed. The Task Type parameter is set to Import UMTS Pilot Pollution Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Enter the name of the scheduled task in Task Name. Select the pilot pollution analysis data import task from Task Type.
NOTE
2.
Step 5 Click Finish. The new pilot pollution analysis data import task is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
Issue 03 (2010-06-30)
17-23
1. 2. 3. 4.
l
NOTE
1. 2.
NOTE
17-24
Issue 03 (2010-06-30)
1. 2. 3.
l
17.2.8 Creating a Task of Importing UMTS Cell Performance Analysis Data

A task of importing UMTS cell performance analysis data is performed to import data from the cell performance analysis data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to the UMTS cell performance analysis is saved on the Nastar server.
Context
l
The task of importing UMTS cell performance analysis data is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month. For the tasks of one type, only one user-defined scheduled task of this type can be created.
Procedure
TIP
Choose Task Type > UMTS Data Import > Import UMTS Cell Performance Analysis Data from the navigation tree. Double-click the node, the New Task dialog box is displayed. The parameter Task Type is set to Import UMTS Cell Performance Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Enter the name of the scheduled task in Task Name. Select the cell performance analysis data import task from Task Type.
Issue 03 (2010-06-30)

NOTE
2.
Step 5 Click Finish. The new cell performance analysis data import task is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
NOTE
1.
Choose Task Type from the navigation tree in the right pane of the Task Management window.
17-26
2.
You can manually or automatically resume a task that is in the suspended state:
NOTE
1. 2. 3.
l
17.2.9 Creating a Task of Importing UMTS Engineering Parameters

A task of importing UMTS engineering parameters is performed to import data from the engineering parameter file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The UMTS engineering parameters are collected to the Nastar server.
Context
l l
A task of importing UMTS engineering parameters is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. The system allows you to create only one user-defined timing task of this type.
Issue 03 (2010-06-30)
Procedure
TIP
Choose Task Type > UMTS Data Import > UMTS Engineering Parameter Import from the navigation tree. Double-click the node, the New Task dialog box is displayed. The Task Type parameter is set to UMTS Engineering Parameter Import by default.
Step 3 Set the information about the task. 1. 2. Enter the name of timing task in Task Name. Select the task of importing performance data from Task Type.
Step 4 Click Next to set the time. 1. Click . In the displayed Date/Time Selection dialog box, set the start time. You can also set the start time by editing the Start Time area.
NOTE
2.
Postrequisite
l
Delete a task. You can delete created tasks to save the system resources.
NOTE
l l l
Each user can delete only the tasks that are created by him. If you are a user in the administrator group, you can delete all the user-defined tasks. System tasks cannot be deleted. Running tasks cannot be deleted.
1. 2. 3. 4.
l
Choose Task Type from the navigation tree in the left pane of the Task Management window. Select a periodic task from the task list in the right part of the window. Click Delete. In the Confirm dialog box, click Yes. Then the task is deleted from the task list.
Suspend a task. To delay the execution of a task, you can suspend a timing task that is in the idle state. 1. 2. Choose Task Type from the navigation tree in the left pane of the Task Management window. You can manually or automatically suspend a task that is in the idle state:
Suspend a task manually.

17-28
Select an existing timing tasks that are in the idle state from the task list in the right pane. Right-click the task and choose Suspend. In the Confirm dialog box, click Yes.
Suspend a task automatically. Select a timing task to be suspended from the task list in the right pane. Right-click the task and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Suspend Time and set its value. Click OK. To set the time for automatically suspending a task, see 17.8.16 Parameters for Setting the Time of a Timing Task.
Resume a task. You can restore a suspended task to wait for the dispatching. Then the status of the task is changed to idle.
NOTE
Only idle tasks can wait to be used.
1. 2.
Choose Task Type from the navigation tree in the left pane of the Task Management window. You can manually or automatically resume a task that is in the suspended state:
Resume a task manually. Select an existing timing tasks that are in the suspended state from the task list in the right pane. Right-click the task and choose Resume. In the Confirm dialog box, click Yes.
Resume a task automatically. Select a timing task to be resumed from the task list in the right pane. Right-click the task and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Resume Time and set its value. Click OK. To set the time for automatically resuming a task, see 17.8.16 Parameters for Setting the Time of a Timing Task.
Cancel a task. You can cancel a running task. The task status is changed to idle after being cancelled.
NOTE
1. 2. 3.
l
Choose Task Type from the navigation tree in the left pane of the Task Management window. Select an existing running task in the task list in the right pane. Right-click the task and choose Cancel. In the Confirm dialog box, click Yes. Then, the task state is changed from Running to Idle.
View a log. You can view the system log related to an import task. For details, see 5.3.1 Querying System Logs.
Issue 03 (2010-06-30)
17-29
17.3 Modifying a UMTS User-Defined Timing Task

The Nastar allows you to modify certain parameters of a UMTS user-defined timing task. If the execution of a UMTS user-defined timing task is complete, you cannot modify the task. 17.3.1 Modifying a Task of Importing UMTS Uplink Interference Data This section describes how to modify certain information about a task of importing UMTS uplink-interference data. 17.3.2 Modifying a Task of Importing UMTS Neighboring-Cell Analysis Data This section describes how to modify certain information about a task of importing UMTS neighboring-cell analysis data. 17.3.3 Modifying a Task of Importing UMTS/GSM Neighboring-Cell Analysis Data This section describes how to modify certain information about a task of importing UMTS/GSM neighboring-cell analysis data. 17.3.4 Modifying a Task of Importing UMTS Configuration Data This section describes how to modify certain information about a task of importing UMTS configuration data. 17.3.5 Modifying a Task of Importing UMTS Coverage Analysis Data This section describes how to modify certain information about a task of importing UMTS coverage analysis data. 17.3.6 Modifying a UMTS VIP Analysis Data Import Task This section describes how to modify certain information about a task of importing UMTS VIP analysis data. 17.3.7 Modifying a Task of Importing UMTS Pilot Pollution Analysis Data This section describes how to modify certain information about a task of importing UMTS pilot pollution analysis data. 17.3.8 Modifying a Task of Importing UMTS Cell Performance Analysis Data This section describes how to modify certain information about a task of importing UMTS cell performance analysis data. 17.3.9 Modifying a Task of Importing UMTS Engineering Parameters This section describes how to modify certain information about a task of importing UMTS engineering parameters.
17.3.1 Modifying a Task of Importing UMTS Uplink Interference Data

This section describes how to modify certain information about a task of importing UMTS uplink-interference data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS uplink-interference data is created.
17-30
Issue 03 (2010-06-30)
Context
l l
A task of importing UMTS uplink-interference data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import UMTS Data > Import UMTS Uplink Interference Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
17.3.2 Modifying a Task of Importing UMTS Neighboring-Cell Analysis Data

This section describes how to modify certain information about a task of importing UMTS neighboring-cell analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS neighboring-cell analysis data is created.
Context
l l
The task is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import UMTS Data > Import UMTS Intra-Frequency Neighboring Cell Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest task information in the task list.

NOTE
----End
17.3.3 Modifying a Task of Importing UMTS/GSM NeighboringCell Analysis Data

This section describes how to modify certain information about a task of importing UMTS/GSM neighboring-cell analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS/GSM neighboring-cell analysis data is created.
Context
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import UMTS Data > Import UMTS/GSM Neighboring Cell Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest task information in the task list.
NOTE
----End
17.3.4 Modifying a Task of Importing UMTS Configuration Data

This section describes how to modify certain information about a task of importing UMTS configuration data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS configuration data is created.
Context
l
The task is a user-defined timing task.

17-32

l
The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import UMTS Data > Import UMTS CFG Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest task information in the task list.
NOTE
----End
17.3.5 Modifying a Task of Importing UMTS Coverage Analysis Data

This section describes how to modify certain information about a task of importing UMTS coverage analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS coverage analysis data is created.
Context
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import UMTS Data > Import UMTS Coverage Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest task information in the task list.

NOTE
----End
17.3.6 Modifying a UMTS VIP Analysis Data Import Task

This section describes how to modify certain information about a task of importing UMTS VIP analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS VIP analysis data is created.
Context
l l
The task of importing UMTS VIP analysis data is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > UMTS Data Import > Import UMTS VIP Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can view the latest information in the task list.
NOTE
----End
17.3.7 Modifying a Task of Importing UMTS Pilot Pollution Analysis Data

This section describes how to modify certain information about a task of importing UMTS pilot pollution analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS pilot pollution analysis data is created.
Context
l
The task of importing UMTS pilot pollution is a user-defined scheduled task.

17-34

l
The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > UMTS Data Import > Import UMTS Pilot Pollution Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can view the latest information in the task list.
NOTE
----End
17.3.8 Modifying a Task of Importing UMTS Cell Performance Analysis Data

This section describes how to modify certain information about a task of importing UMTS cell performance analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS cell performance analysis data is created.
Context
l
The task of importing UMTS cell performance analysis data is a user-defined scheduled task. The task can only be executed periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > UMTS Data Import > Import UMTS Cell Performance Analysis Data from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can view the latest information in the task list.

NOTE
----End
17.3.9 Modifying a Task of Importing UMTS Engineering Parameters

This section describes how to modify certain information about a task of importing UMTS engineering parameters.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing UMTS engineering parameters is created.
Context
l l
A task of importing UMTS engineering parameters is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > UMTS Data Import > UMTS Engineering Parameter Import from the navigation tree on the left. Step 3 Double-click or click Attribute to view the Attribute dialog box. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can browse the newest task information in the task list.
NOTE
----End
17.4 Modifying a UMTS Data Deletion Task

This section describes how to modify a UMTS data deletion task. If data is periodically imported to the Nastar database, the database resources may be insufficient. By performing the UMTS data deletion task, the Nastar can delete the data whose storage duration has expired from the database at the preset time to save system resources. A UMTS data deletion task is a system timing task. You can modify only certain parameters of the task. To modify a UMTS data deletion task, you must be a user in the administrator group. If the execution of a UMTS data deletion task is complete, you cannot modify the task. 17.4.1 Modifying the Task of Deleting GSM History Data
This section describes how to modify certain information about the system-created task of deleting GSM history data. 17.4.2 Modifying a Task of Deleting UMTS Uplink Interference Data This section describes how to modify certain information about the system-created task of deleting UMTS uplink-interference data. 17.4.3 Modifying the Task of Deleting UMTS Neighboring-Cell Analysis Data This section describes how to modify certain information about the system-created task of deleting UMTS neighboring-cell analysis data. 17.4.4 Modifying the Task of Deleting UMTS/GSM Neighboring-Cell Analysis Data This section describes how to modify certain information about the system-created task of deleting UMTS/GSM neighboring-cell analysis data. 17.4.5 Modifying the Task of Deleting UMTS Configuration Data This section describes how to modify certain information about the system-created task of deleting UMTS configuration data. 17.4.6 Modifying the Task of Deleting UMTS Coverage Analysis Data This section describes how to modify certain information about the system-created task of deleting UMTS coverage analysis data. 17.4.7 Modifying a Task of Deleting UMTS VIP Analysis Data This section describes how to modify certain information about the system-created task of deleting UMTS VIP analysis data. 17.4.8 Modifying a Task of Deleting UMTS Pilot Pollution Analysis Data This section describes how to modify certain information about the system-created task of deleting UMTS pilot pollution analysis data. 17.4.9 Modifying a Task of Deleting UMTS Cell Performance Analysis Data This section describes how to modify certain information about the system-created task of deleting UMTS cell performance analysis data.

Prerequisite
l l
Context
l
Issue 03 (2010-06-30)
17-37
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Data Collection > Old Data Deletion from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages.
NOTE
NOTE
----End
17.4.2 Modifying a Task of Deleting UMTS Uplink Interference Data

This section describes how to modify certain information about the system-created task of deleting UMTS uplink-interference data.
Prerequisite
l l
Context
l
The task of deleting UMTS uplink-interference data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting uplink-interference data refers to deleting the uplink-interference data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete UMTS Data > Delete UMTS Uplink Interference Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.

NOTE
----End
17.4.3 Modifying the Task of Deleting UMTS Neighboring-Cell Analysis Data

This section describes how to modify certain information about the system-created task of deleting UMTS neighboring-cell analysis data.
Prerequisite
l l
Context
l
The task of deleting UMTS neighboring-cell analysis data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting neighboring-cell analysis data refers to deleting the neighboring-cell analysis data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete UMTS Data > UMTS Intra-Frequency Neighboring Cell Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
17.4.4 Modifying the Task of Deleting UMTS/GSM NeighboringCell Analysis Data

This section describes how to modify certain information about the system-created task of deleting UMTS/GSM neighboring-cell analysis data.
Prerequisite
l l
Issue 03 (2010-06-30)
Context
l
The task of deleting UMTS/GSM neighboring-cell analysis data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting UMTS/GSM neighboring-cell analysis data refers to deleting the UMTS/GSM neighboring-cell analysis data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete UMTS Data > UMTS/GSM Neighboring Cell Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
17.4.5 Modifying the Task of Deleting UMTS Configuration Data

This section describes how to modify certain information about the system-created task of deleting UMTS configuration data.
Prerequisite
l l
Context
l
The task of deleting UMTS configuration data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting configuration data refers to deleting the configuration data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete UMTS Data > UMTS CFG Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages.
NOTE
----End
17.4.6 Modifying the Task of Deleting UMTS Coverage Analysis Data

This section describes how to modify certain information about the system-created task of deleting UMTS coverage analysis data.
Prerequisite
l l
Context
l
The task of deleting UMTS coverage analysis data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting coverage analysis data refers to deleting the coverage analysis data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete UMTS Data > UMTS Coverage Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
17.4.7 Modifying a Task of Deleting UMTS VIP Analysis Data

This section describes how to modify certain information about the system-created task of deleting UMTS VIP analysis data.
Prerequisite
l

Issue 03 (2010-06-30)

l
The current user is a member of the user group Administrators.
Context
l
The task of deleting UMTS VIP analysis data is a system scheduled task. It can only be executed periodically. Only the parameters Start Time and Period of a UMTS VIP analysis data deletion task can be modified. Deleting the VIP analysis data is performed to delete the expired VIP analysis data on the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete UMTS Data > UMTS VIP Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can view the latest information in the task list.
NOTE
----End
17.4.8 Modifying a Task of Deleting UMTS Pilot Pollution Analysis Data

This section describes how to modify certain information about the system-created task of deleting UMTS pilot pollution analysis data.
Prerequisite
l l
Context
l
The task of deleting UMTS pilot pollution analysis data is a system scheduled task. It can only be executed periodically. Only the parameters Start Time and Period of a UMTS pilot pollution analysis data deletion task can be modified. Deleting the pilot pollution analysis data is performed to delete the expired pilot pollution analysis data on the NASTAR server.
Procedure
Step 2 Choose Task Type > Delete UMTS Data > UMTS Pilot Pollution Analysis Data Maintenance from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters and Extended Parameters tab pages. Step 5 Click OK. You can view the latest information in the task list.
NOTE
----End
17.4.9 Modifying a Task of Deleting UMTS Cell Performance Analysis Data

This section describes how to modify certain information about the system-created task of deleting UMTS cell performance analysis data.
Prerequisite
l l
Context
l
The task of deleting UMTS cell performance analysis data is a system scheduled task. It can only be executed periodically. Only the parameters Start Time and Period of a UMTS cell performance analysis data deletion task can be modified. Deleting the cell performance analysis data is performed to delete the expired cell performance analysis data on the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete UMTS Data > UMTS Cell Performance Analysis Data Maintenance from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can view the latest information in the task list.
NOTE
----End

Prerequisite
l l
Context
l l
The task of backing up data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time, Execution Period, Full Backup Time, Backup Mode, and Backup Path. Periodic backup refers to perform full backup on certain day within the period, and perform incremental backup at other time. The Nastar services are not disrupted when you back up data.
Procedure
NOTE
NOTE
----End

Prerequisite
l l
17-44
Context
l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the task type of which you plan to suspend/restore. Step 3 Select a task in the task list in the right pane. Right-click the task and select Suspend/Restore Step 4 In the Timing Suspend/Resume dialog box, select Suspend Time or Resume Time as required. Step 5 Set the suspend time or resume time. For details of setting an automatic suspend time or an automatic restore time, refer to 17.8.16 Parameters for Setting the Time of a Timing Task. ----End


Prerequisite
l l
Issue 03 (2010-06-30)
17-45
Context
l l
Procedure
l l
NOTE
l l
----End

Prerequisite
l l
Procedure

Prerequisite
l l
17-46
Context
l
Procedure
l
----End
17.8 Reference to the UMTS Centralized Task Management Interface

This section describes the interface for the UMTS centralized task management and related information such as the parameters used in the centralized task management. This help you understand the functions of the UMTS centralized task management. 17.8.1 Interface Description: Centralized Task Management This section describes the Task Management interface and relevant parameters, which helps you perform the related operations. 17.8.2 Parameter for Setting Task Filter Conditions This section describes the parameters in the Task Filter Setting dialog box. When you set filter conditions for a task list, you can refer to this section. 17.8.3 Parameter for Setting Common Parameters for Timing Tasks This section describes the parameters on the Common Parameters tab on property panels of all timing tasks. When you modify a timing task, you can refer to this section. 17.8.4 Parameter for Setting the Time of a Common Periodic Task This section describes the time parameters in the New Task dialog box. When you set the time of a periodic task, you can refer to this section. 17.8.5 Parameter for Setting the Time of a Common One-Time Task This section describes the time parameter in the New Task dialog box. When you modify the time of a one-time task, you can refer to this section. 17.8.6 Parameters for Modifying the Task of Deleting History Data This section describes the parameters related to the task of deleting history data. You can refer to the description when modifying the task of deleting history data. 17.8.7 Parameters for Modifying the Task of Deleting UMTS Uplink Interference Data This section describes the parameters related to the task of deleting UMTS uplink interference data. You can refer to the description when modifying the task of deleting UMTS uplink interference data. 17.8.8 Parameters for Modifying the Task of Deleting Neighboring UMTS Cell Analysis Data
This section describes the parameters related to the task of deleting neighboring UMTS cell analysis data. You can refer to the description when modifying the task of deleting neighboring UMTS cell analysis data. 17.8.9 Parameters for Modifying the Task of Deleting UMTS/GSM Neighboring-Cell Analysis Data This section describes the parameters related to the task of deleting UMTS/GSM neighboringcell analysis data. You can refer to the description when modifying the task of deleting UMTS/ GSM neighboring-cell analysis data. 17.8.10 Parameters for Modifying the Task of Deleting UMTS Configuration Data This section describes the parameters related to the task of deleting UMTS configuration data. You can refer to the description when modifying a task of deleting UMTS configuration data. 17.8.11 Parameters for Modifying the Task of Deleting UMTS Coverage Analysis Data This section describes the parameters related to the task of deleting UMTS coverage analysis data. You can refer to the description when modifying the task of deleting UMTS coverage analysis data. 17.8.12 Parameters for Modifying the Task of Deleting UMTS VIP Analysis Data This section describes the parameters related to the task of deleting UMTS VIP analysis data. You can refer to the description when modifying the task of deleting UMTS VIP analysis data. 17.8.13 Parameters for Modifying the Task of Deleting UMTS Pilot Pollution Analysis Data This section describes the parameters related to the task of deleting UMTS pilot pollution analysis data. You can refer to the description when modifying the task of deleting UMTS pilot pollution analysis data. 17.8.14 Parameters for Modifying the Task of Deleting UMTS Cell Performance Analysis Data This section describes the parameters related to the task of deleting UMTS cell performance analysis data. You can refer to the description when modifying the task of deleting UMTS cell performance analysis data. 17.8.15 Parameters for Modifying the Task of Backing Up Data This section describes the parameters related to the task of backing up data. You can refer to the description when modifying the task of backing up data. 17.8.16 Parameters for Setting the Time of a Timing Task This section describes the parameters of auto-suspend time and auto-resume time for timing tasks.

This section describes the Task Management interface and relevant parameters, which helps you perform the related operations. After you log in to the server, the Task Management interface is displayed, as shown in Figure 17-2. Table 17-4 describes each element displayed in Figure 17-2.
17-48
Issue 03 (2010-06-30)
Figure 17-2 Integrated Task Management interface
Table 17-4 Description of the Integrated Task Management interface No. (1) (2) Name Navigation tree Task result information panel Description You can precisely locate a timing task through the navigation tree. After a task is carried out, the task result is displayed. On the task result information panel, you can browse the result of the task last carried out. Only the result of the currently selected task is displayed on the task result information panel. If multiple tasks are selected in the task list, only the result of the firstly selected task is displayed. The buttons used for carrying out integrated task management are available on the button panel.
(3)
Button panel
Issue 03 (2010-06-30)
17-49
No. (4)
Name Task list
Description You can browse the timing tasks that exist on the server side and the detailed information. In the task list, different colors are used for indicate different states of tasks (gray: complete; orange: suspended; blue: active; white: idle). The selected color of the task is darker than the previous color of the task.

Parameters
Parameter User Name Current User Description Description: Indicates the user that operates the client. Other Users Description: Indicates other users except the current user. Catego ry User Task Description: Indicates the task created by users. System Task Description: Indicates the task created by OMC during the system installation or upgrade. State Idle Description: Indicates that the task waits for being performed by the system. Running Description: Indicates that the task is being performed by the system. Suspend Description: The task is not ready to be scheduled. Finished Description: Indicates that the task is completed by the system. Last Run Result Success Description: Indicates that the task is successfully carried out. Processing Description: Indicates that the task is being processed by the system.
Parameter Partly Success Failed
Description Description: Indicates that the task is partly successfully carried out. Description: Indicates that the task fails to carry out.
Miss Run Time
Unknown

Parameters
l
l l
Run Type
Once
Period
Issue 03 (2010-06-30)
17-51
Parameter Start Time
Description Description: This parameter sets the time for starting a task. The start time should be later than the time displayed on the server.
Value Range Value: If you have selected Run At Once, the Start Time parameter is invalid. The task is performed immediately after the related settings are complete. Value:
l
Period
Run Times
Value: 0-65535

Parameters
l
17-52
Issue 03 (2010-06-30)
Parameter Period Setting Period
Description Description: Interval of periodic tasks. The value consists of numerals and units.
Settings Value:
l
Run Times
Value: 0 - 65535

Parameters
l l

Parameter Config Data Range An integer from 1 to 100 Unit: day Performanc e Data An integer from 1 to 100 Unit: day Description Indicates the storage duration of the configuration data files in the relevant path on the Nastar server. The configuration data is limited to the GSM, CDMA, UMTS, and TD-SCDMA networks. Indicates the storage duration of the performance data files in the relevant path on the Nastar server. The performance data is limited to the GSM network, and the data related to all the analysis tasks of the CDMA, UMTS, and TD-SCDMA networks. Indicates the storage duration of the neighbor measurement task files in the relevant file path on the Nastar server. The neighbor measurement task files are limited to the GSM network. Frqlog Data An integer from 1 to 100 Unit: day Indicates the storage duration of the files containing the uplink ARFCN scanning data in the relevant file path on the Nastar server. The uplink ARFCN scanning data is limited to the GSM network.
17.8.7 Parameters for Modifying the Task of Deleting UMTS Uplink Interference Data
This section describes the parameters related to the task of deleting UMTS uplink interference data. You can refer to the description when modifying the task of deleting UMTS uplink interference data.
Parameter Data Reserve Days Value Range 7, 15, 30, 45, 60, 90, 180 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the uplink interference data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the uplink interference data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the uplink interference data saved before 2009-03-24 from the database.
17-54
Issue 03 (2010-06-30)
17.8.8 Parameters for Modifying the Task of Deleting Neighboring UMTS Cell Analysis Data
This section describes the parameters related to the task of deleting neighboring UMTS cell analysis data. You can refer to the description when modifying the task of deleting neighboring UMTS cell analysis data.
Parameter Data Reserve Days Value Range 7, 15, 30, 45, 60, 90, 180 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the neighboring cell analysis data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the neighboring cell analysis data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the neighboring cell analysis data saved before 2009-03-24 from the database.
17.8.9 Parameters for Modifying the Task of Deleting UMTS/GSM Neighboring-Cell Analysis Data
This section describes the parameters related to the task of deleting UMTS/GSM neighboringcell analysis data. You can refer to the description when modifying the task of deleting UMTS/ GSM neighboring-cell analysis data.
Parameter Data Reserve Days Value Range 7, 15, 30, 45, 60, 90, 180 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the UMTS/GSM neighboring-cell analysis data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the UMTS/GSM neighboring-cell analysis data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the UMTS/GSM neighboring-cell analysis data saved before 2009-03-24 from the database.
17.8.10 Parameters for Modifying the Task of Deleting UMTS Configuration Data
This section describes the parameters related to the task of deleting UMTS configuration data. You can refer to the description when modifying a task of deleting UMTS configuration data.
Parameter Data Reserve Days Value Range 7, 15, 30, 45, 60, 90, 180 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the configuration data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the configuration data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the configuration data saved before 2009-03-24 from the database.
17.8.11 Parameters for Modifying the Task of Deleting UMTS Coverage Analysis Data
This section describes the parameters related to the task of deleting UMTS coverage analysis data. You can refer to the description when modifying the task of deleting UMTS coverage analysis data.
Parameter Data Reserve Days Value Range 7, 15, 30, 45, 60, 90, 180 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the coverage analysis data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the coverage analysis data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the VIP analysis data saved before 2009-03-24 from the database.
17.8.12 Parameters for Modifying the Task of Deleting UMTS VIP Analysis Data
This section describes the parameters related to the task of deleting UMTS VIP analysis data. You can refer to the description when modifying the task of deleting UMTS VIP analysis data.
17-56
Issue 03 (2010-06-30)
Parameter Data Reserve Days Value Range 7, 15, 30, 45, 60, 90, 180 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the VIP analysis data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the VIP analysis data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the VIP analysis data saved before 2009-03-24 from the database.
17.8.13 Parameters for Modifying the Task of Deleting UMTS Pilot Pollution Analysis Data
This section describes the parameters related to the task of deleting UMTS pilot pollution analysis data. You can refer to the description when modifying the task of deleting UMTS pilot pollution analysis data.
Parameter Data Reserve Days Value Range 7, 15, 30, 45, 60, 90, 180 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the pilot pollution analysis data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the pilot pollution analysis data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the pilot pollution analysis data saved before 2009-03-24 from the database.
17.8.14 Parameters for Modifying the Task of Deleting UMTS Cell Performance Analysis Data
This section describes the parameters related to the task of deleting UMTS cell performance analysis data. You can refer to the description when modifying the task of deleting UMTS cell performance analysis data.
Issue 03 (2010-06-30)
17-57
Parameter Data Reserve Days Value Range 7, 15, 30 Unit: day Item Assume that N refers to the preset Data Reserve Days. All the cell performance analysis data that is saved N days before the time of saving the latest data is deleted from the database. For example, among all the cell performance analysis data in the database, if the time of saving the latest data is 2009-03-31, and Data Reserve Days is set to 7, the system deletes all the cell performance analysis data saved before 2009-03-24 from the database.

Parameter Full Backup Time Backup Mode Backup Path Range SUN, MON, TUE, WED, THU, FRI, SAT ALL, INC Description Indicates the date when data backup is performed.
Indicates the mode of the data backup. Indicates the save path of backup files. By default, the path is /export/home/backup.

This section describes the parameters of auto-suspend time and auto-resume time for timing tasks. Table 17-5 lists the parameters of auto-suspend time and auto-resume time for timing tasks.
17-58
Issue 03 (2010-06-30)
Table 17-5 Time parameters of a timing task Name Suspend Time Description Description: The system suspends an idle task and delay the time for performing this task. If the timing task is not in the idle state at the specified time, the suspension fails. Settings Setting method: You can set the value manually. Alternatively, you can click and select the time from the time select panel. The default time format is DD/ MM/YYYY HH:MM:SS.
l l l l l l
Resume Time
Issue 03 (2010-06-30)
17-59
18 UMTS Uplink Interference Analysis
18
UMTS Uplink Interference Analysis
About This Chapter

UMTS uplink-interference analysis involves managing uplink-interference analysis tasks and querying UMTS uplink-interference analysis reports. The system analyzes the received total wideband power (RTWP) data that is sent by the NodeB. It initially locates the interfered base station by using the interference ranking function. Then, you can analyze whether the values of the main and diversity antennas are correct based on the overall RTWP trend of the selected cell. In this way, you can determine the interference features. You can also determine whether the main and diversity antenna are connected contrarily by browsing the distribution chart of the differences between the RTWPs of the main and diversity antennas. 18.1 Basic Knowledge of UMTS Uplink-Interference Analysis The UMTS uplink-interference analysis function is performed to analyze the RTWP data reported by NodeBs. Based on uplink-interference analysis results, you can determine whether the carriers on the existing network are experiencing interference. You can also locate antenna feeder problems by analyzing the signal strength of the main and diversity antennas of the uplink. 18.2 Process of UMTS uplink interference Analysis This section describes the process of UMTS uplink interference analysis. 18.3 Managing UMTS Uplink Interference Analysis Tasks This section describes how to manage UMTS uplink-interference analysis tasks. You can create, modify, delete, suspend, and resume UMTS uplink-interference analysis tasks. You can also view the status and execution progress of a task. 18.4 Querying a UMTS Uplink Interference Analysis Report This section describes how to query the UMTS uplink-interference analysis report. You can query the RTWP data reported by the NodeB and initially locate the BTS that is interfered. Then, you can analyze whether the values of the main and diversity antennas are correct based on the overall RTWP trend of the selected cell. In this way, you can determine the interference features. You can also determine whether the main and diversity antenna are connected contrarily by browsing the distribution chart of the differences between the RTWPs of the main and diversity antennas. 18.5 Reference for the UMTS Uplink Interference Analysis GUI
Issue 03 (2010-06-30)
18-1
This section describes the interface for UMTS uplink-interference analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS uplink-interference analysis.
18-2
Issue 03 (2010-06-30)
18.1 Basic Knowledge of UMTS Uplink-Interference Analysis

The UMTS uplink-interference analysis function is performed to analyze the RTWP data reported by NodeBs. Based on uplink-interference analysis results, you can determine whether the carriers on the existing network are experiencing interference. You can also locate antenna feeder problems by analyzing the signal strength of the main and diversity antennas of the uplink. Uplink interference is a key factor that affects the QoS of networks with respect to the following aspects: conversation quality, call drop, handover, congestion, network coverage, and network capacity. If interference and load cannot be distinguished, load control cannot work properly. The uplink-interference analysis function is applicable to the RTWP data reported by NodeBs. Through the uplink-interference-ranking function, you can locate the NodeB experiencing interference initially. Then, by checking the overall RTWP trend of the selected cell, you can analyze whether the values of the main and diversity antennas are correct. In this way, you can determine the interference features. You can also determine whether the main and diversity antenna are connected contrarily by browsing the distribution chart of the differences between the RTWPs of the main and diversity antennas. After the conditions for uplink-interference analysis are set, the Nastar performs uplinkinterference analysis on the selected cells. The analysis results are displayed in a line chart. The chart displays the values of the main and diversity antennas of each cell at each time point in different colors and shows overall RTWP trend and detailed trend of the selected cell.
18.2 Process of UMTS uplink interference Analysis

This section describes the process of UMTS uplink interference analysis. Figure 18-1 shows the general process of UMTS uplink interference analysis.
Issue 03 (2010-06-30)
18-3
Figure 18-1 Workflow of uplink interference analysis

Start
Set an E2E task
Set an uplink interference analysis task Query an uplink interference analysis report End
Table 18-1 describes the items listed in Figure 18-1. Table 18-1 Description of the workflow of uplink interference analysis No. 1 Procedure Querying NE data information Create an endto-end task corresponding to an uplink interference analysis task Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the uplink interference analysis is imported to the database. You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to an uplink interference analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create an uplink interference data importing task. After the task is created, the Nastar periodically imports the uplink interference data files saved on the Nastar server to the database.
Create an uplink interference data importing task
18-4
Issue 03 (2010-06-30)
No. 4
Procedure Create an uplink interference analysis task
Description You can create an uplink interference analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required configuration data and RTWP data from the Nastar database, and then generates an analysis report through the analysis. You can view the analysis results of the uplink interference analysis task that is successfully performed and initially locate the BTS that experiences interference. You can analyze whether the values of the main and diversity antennas are correct based on the overall RTWP trend and detailed trend of the selected cell. In this way, you can determine the interference features. You can also determine whether the main and diversity antenna are connected contrarily by browsing the distribution chart of the differences between the RTWPs of the main and diversity antennas.
Query uplink interference analysis reports
18.3 Managing UMTS Uplink Interference Analysis Tasks

This section describes how to manage UMTS uplink-interference analysis tasks. You can create, modify, delete, suspend, and resume UMTS uplink-interference analysis tasks. You can also view the status and execution progress of a task. 18.3.1 Creating UMTS E2E Tasks This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 18.3.2 Creating a UMTS Uplink Interference Analysis Task This section describes how to create a UMTS uplink-interference analysis task. By performing UMTS uplink-interference analysis tasks, the Nastar performance analysis system analyzes the RTWP data of each NodeB in the database at the preset time. Based on the analysis result, you can learn about the signal strength of the main and diversity antennas and the trend of the signal strength related to the selected cell, which helps you to detect abnormal interference on the network. 18.3.3 Modifying a UMTS Uplink-Interference Analysis Task You can modify the attributes of a UMTS uplink-interference analysis task to meet the new requirement. 18.3.4 Checking a UMTS Uplink Interference Analysis Task This section describes how to check a UMTS uplink-interference analysis task. You can check the attributes, execution progress, and execution results of a UMTS uplink-interference analysis task.
18.3.1 Creating UMTS E2E Tasks

This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the
MML command to the related NE. Then, the NE performs the measurement task and generates the result.
Prerequisite
l l l
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Set the basic information about the task. 1. 2. 3. In the Task Name field, enter the name of the E2E task. In the OSS name drop-down list box, select the OSS name for the task. Select a task from E2E Task List. Table 18-2 describes the mapping between the E2E tasks and the analysis tasks. Table 18-2 Mapping between the E2E tasks and the analysis tasks E2E Task RTWP data task UMTS Neighboring cell data task UMTS Coverage data task UMTS VIP tracing task UMTS Pilot pollution task UMTS/GSM neighboring cell data task UMTS cell performance data task Analysis Task UMTS uplink interference analysis task UMTS co-frequency neighboring cell analysis task UMTS coverage analysis task UMTS VIP analysis task UMTS pilot pollution analysis task UMTS/GSM neighboring cell analysis task UMTS cell performance analysis task
Step 4 Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the
keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. Step 5 Optional: Click Next and then set the exception value for each KPI in the exception value setting list. You need to perform this step only when a UMTS cell performance analysis task is created. Step 6 Click Complete. The MML Preview dialog box is displayed, showing the MML commands related to the current theme analysis E2E task. The MML commands can be exported for future use. Step 7 Click OK. The added E2E task is displayed in the task list. ----End
Postrequisite
After an E2E task is created, you can view that the corresponding collection task has been created by the system in the Task Management window. You can perform a data import task only after the corresponding collection task is complete. To view the attributes of a created E2E task, perform the following operations: 1. 2. Select a task from the task list in the right pane of the E2E Task Management window, and then click Attribute. The Attribute dialog box is displayed. View the related parameters.
To delete an unnecessary E2E task, perform the following operations: 1. 2. Select a task from the E2E Task Management window, and then click Delete. Click OK in the displayed Confirm dialog box.
NOTE
18.3.2 Creating a UMTS Uplink Interference Analysis Task

This section describes how to create a UMTS uplink-interference analysis task. By performing UMTS uplink-interference analysis tasks, the Nastar performance analysis system analyzes the RTWP data of each NodeB in the database at the preset time. Based on the analysis result, you can learn about the signal strength of the main and diversity antennas and the trend of the signal strength related to the selected cell, which helps you to detect abnormal interference on the network.
Prerequisite
l l
Context
l l
Procedure
l
Choose RNC or Cell Group above the navigation tree to display the objects in the navigation tree as required. The system enables you to search for the objects in the navigation tree. You can click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Step 7 On the Parameter Setting tab page, set Display mode of the RTWP trend of a cell. Step 8 Click Complete. ----End
Postrequisite
l
Deleing a task You can delete an uplink-interference analysis task that is not required so that you can save system resources.
NOTE
1.
Choose UMTS Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window.
18-8
If you choose Subject Function, the task list on the right displays all the performance analysis tasks. 2. 3.
l
Suspending a task To delay the task execution, you can suspend an uplink-interference analysis task that is in the idle state. After this operation, the uplink-interference analysis task is in the suspended state.
NOTE
The system can schedule only the uplink-interference analysis tasks that are not suspended.
1.
Choose UMTS Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
Only the tasks whose Status is Idle can be suspended. Otherwise, the button is unavailable.
l
Resuming a task You can resume a suspended uplink-interference analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the uplink-interference analysis task that is in the idle state can be scheduled by the system.
1.
Choose UMTS Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
18.3.3 Modifying a UMTS Uplink-Interference Analysis Task

You can modify the attributes of a UMTS uplink-interference analysis task to meet the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS uplink-interference analysis task is created.
Context
Procedure
Step 1 Choose UMTS Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the relevant parameters, see 18.5.3 Parameters for Creating or Modifying a UMTS Uplink Interference Analysis Task. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the object navigation tree, and the Display Mode of the RTWP Trend of a Cell parameter.
18.3.4 Checking a UMTS Uplink Interference Analysis Task

This section describes how to check a UMTS uplink-interference analysis task. You can check the attributes, execution progress, and execution results of a UMTS uplink-interference analysis task.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS uplink-interference analysis task is created.
Procedure
Step 1 Choose UMTS Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: Purpose Checking the attributes of an uplinkinterference analysis task Operation Select a task from the task list in the upperright pane. Double-click the task or click .
For detailed operations, see 18.3.3 Modifying a UMTS Uplink-Interference Analysis Task.
18-10
Issue 03 (2010-06-30)
Purpose Checking the execution progress of the active task
Operation Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column. Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view all the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
18.4 Querying a UMTS Uplink Interference Analysis Report

This section describes how to query the UMTS uplink-interference analysis report. You can query the RTWP data reported by the NodeB and initially locate the BTS that is interfered. Then, you can analyze whether the values of the main and diversity antennas are correct based on the overall RTWP trend of the selected cell. In this way, you can determine the interference features. You can also determine whether the main and diversity antenna are connected contrarily by browsing the distribution chart of the differences between the RTWPs of the main and diversity antennas.
Prerequisite
Procedure
Step 1 Choose UMTS Uplink Interference Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose Uplink Interference Analysis Task. The UMTS Uplink Interference Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell from the left list. Then, you can view the overall RTWP trend and the difference of the main and diversity antennas of the selected cell on the right area.
l
In the area on the right,
the upper part displays the trend chart of the interference signal strength of the main and diversity antennas related to the selected cell during a time range. The chart at the lower part displays the distribution of the differences between the RTWPs of the main and diversity antennas of the selected cell. The difference between the RTWPs of the main and diversity antennas at each time point is calculated first. Then, the system calculates the percentage of a difference to the total number of differences.
You can zoom in or zoom out the chart by dragging it with the mouse.
l
The RTWP data displayed on the overall RTWP trend chart of the cell is not the original data. It is refreshed every minute.
----End
Postrequisite
l
Right-click the chart, and then choose Property from the shortcut menu. In the displayed Chart Property dialog box, set the coordinate axes of and basic information about the chart. Right-click the chart, and then choose Save as from the shortcut menu. In the displayed Save dialog box, set the save path and file name, and then click Save to save the queried chart as a file on the local PC. Right-click the chart, and then choose Print from the shortcut menu. In the displayed Page Setup dialog box, set print properties, and then click OK. If the chart is not clear due to an excessive number of dots, right-click the chart, and then choose Zoom In > ***, Zoom Out > ***, or Auto Range > *** to adjust the size of the chart.
18-12
Issue 03 (2010-06-30)
Here, *** indicates a submenu item. It can be Both Axes, Horizontal Axis, or Vertical Axis, which indicates that you can adjust both axes, the horizontal axis, or the vertical axis, respectively.
l
18.5 Reference for the UMTS Uplink Interference Analysis GUI

This section describes the interface for UMTS uplink-interference analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS uplink-interference analysis. 18.5.1 Interface for UMTS Uplink Interference Analysis This section describes the interface for UMTS uplink-interference analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 18.5.2 Parameters for Creating UMTS E2E Tasks This section describes the parameters for creating UMTS E2E tasks. You can refer to the description when creating a UMTS E2E task. 18.5.3 Parameters for Creating or Modifying a UMTS Uplink Interference Analysis Task This section describes the parameters for creating and modifying UMTS uplink-interference analysis tasks. You can refer to the description when creating or modifying a UMTS uplinkinterference analysis task. 18.5.4 Parameters for Querying the Uplink Interference Analysis Reports of UMTS Cells This section describes the parameters for querying the uplink-interference analysis reports of UMTS cells. You can refer to the description when querying the uplink-interference analysis reports of UMTS cells.
18.5.1 Interface for UMTS Uplink Interference Analysis

This section describes the interface for UMTS uplink-interference analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. The uplink-interference analysis result interface displays the trends of the RTWP data in a line chart, as shown in Figure 18-2.
Issue 03 (2010-06-30)
18-13
Figure 18-2 Interface for the uplink-interference analysis of a cell
No. Name (1) Cell information list
Description Displays the basic information about all the cells involved in an analysis task in a table. Displays the trends of the RTWPs of the main and diversity antennas of a selected cell in a time segment in a line chart. Displays the distribution of the difference between the RTWPs of the main and diversity antennas of the selected cell in column charts.
(2)
Overall RTWP trend chart of a cell
(3)
Distribution chart of the differences between the RTWPs of the main and diversity antennas
18.5.2 Parameters for Creating UMTS E2E Tasks

This section describes the parameters for creating UMTS E2E tasks. You can refer to the description when creating a UMTS E2E task.
Parameter Basic information
18-14
Description Task Name Indicates the name of an E2E task.
Issue 03 (2010-06-30)
Parameter OSS Name E2E Task List
Description Indicates the name of the OSS related to the task. Indicates the types of E2E tasks. You can select one of the following E2E tasks: RTWP data task, UMTS Neighboring cell data task, UMTS Coverage data task, UMTS VIP tracing task, UMTS Pilot pollution task, UMTS/GSM neighboring cell data task, or UMTS cell performance data task. Indicates the time when the E2E task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the E2E task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Indicates the NE related to the E2E task.
Measurement information
Start Time
Description of Special Parameters

The following table lists the parameters for setting the exception threshold during the creation of the UMTS cell performance analysis E2E task. Parameter Measurement information Service Type Exception Type KPI Determination rule Exception Value Description Indicates service types involved during the exception determination, such as Network level. Indicates the exception types involved during the exception determination, such as Call setup failure. Indicates the KPIs involved during the exception determination. Indicates the types of exception determination, such as >=. Indicates the exception threshold involved during the exception determination, such as 30 The value is an integer from 0 to 65535.
Issue 03 (2010-06-30)
18-15
18.5.3 Parameters for Creating or Modifying a UMTS Uplink Interference Analysis Task
This section describes the parameters for creating and modifying UMTS uplink-interference analysis tasks. You can refer to the description when creating or modifying a UMTS uplinkinterference analysis task.
Parameter Basic Information Task Name Description Indicates the name of an uplink-interference analysis task. Value range:
l l
l l
You need to select UMTS Uplink Interference Analysis Task from the Task Type navigation tree. Such a task can be executed only once in a time segment. Indicates the description of the task. Value range:
l l
Time Information
Data Time Scope
Task Start At
Object Information
RNC Cell Group
If you select this option, the navigation tree displays all the RNCs of the entire network. If you select this option, the navigation tree displays all the cell groups of the entire network.
18-16
Issue 03 (2010-06-30)
Parameter Parameter Information Display mode of the RTWP trend of a cell
Description Indicates the rules for summarizing RTWP data every minute when the system displays the overall trend of the RTWP data. The value can be Mean or Maximum. If the parameter is set to Mean, the average value is calculated based on the power that is converted from the signal strength of each time point during a minute and then the average value is converted to signal strength and used as the summary data of this minute. If the parameter is set to Maximum, the maximum value is calculated based on the signal strength of each time point during a minute and used as the summary data of this minute.
18.5.4 Parameters for Querying the Uplink Interference Analysis Reports of UMTS Cells
This section describes the parameters for querying the uplink-interference analysis reports of UMTS cells. You can refer to the description when querying the uplink-interference analysis reports of UMTS cells.
Parameter RNC ID Cell ID Cell Name P-SC Main Average Strength (dBm) Diversity Average Strength (dBm) Average Difference (Main-Diversity) (dB) Description Indicates the ID of an RNC. Indicates the ID of a cell. Indicates the name of a cell, for example, Cell_1. Indicates the primary scrambling code (p-SC) of a cell. Indicates the average value of the interference strength of main antennas. Indicates the average value of the interference strength of diversity antennas. Indicates the value calculated by dividing the sum of the differences between the RTWPs of the main and diversity antennas at each time point in the selected time range by the total number of time points.
Issue 03 (2010-06-30)
18-17
Parameter Standard Deviation (Main-Diversity)
Description Indicates the square root of the value calculated through the following steps: Firstly, calculate the average of the differences between the RTWPs of the main and diversity antennas at every time point in a selected time range. Secondly, substract the average from the differences between the RTWPs of the main and diversity antennas separately. Thirdly, divide the sum of the squares of the values obtained in the second step by the total number of time points.
18-18
Issue 03 (2010-06-30)
19 UMTS Co-Frequency Neighboring Cell Analysis
19
UMTS Co-Frequency Neighboring Cell Analysis
About This Chapter

This section describes the UMTS co-frequency neighboring cell analysis. The UMTS cofrequency neighboring cell analysis involves managing neighboring cell analysis tasks, querying UMTS neighboring cell analysis reports, and exporting UMTS neighboring cell analysis reports. With the configuration data and engineering parameters, the Nastar determines the missing neighboring cells, redundant neighboring cells, and the priorities that need to be adjusted of a measurement cell based on MRs and events reported by UEs. If this information exists, the system displays the information. This helps you to solve the problems relating to the network quality that are caused by redundant or missing neighboring cell configuration, or by incorrect priority. 19.1 Basic Knowledge of UMTS Co-Frequency Neighboring Cell Analysis This section describes the basic knowledge of the UMTS co-frequency neighboring cell analysis, such as the neighboring cell analysis functions, application scenarios, and algorithms for the neighboring cell analysis. The basic knowledge helps you perform the operations related to the UMTS co-frequency neighboring cell analysis. 19.2 Process of UMTS Co-Frequency Neighboring Cell Analysis This section describes the process of UMTS co-frequency neighboring cell analysis. 19.3 Managing UMTS Neighboring Cell Analysis Tasks This section describes how to manage UMTS neighboring cell analysis tasks. You can create, modify, delete, suspend, and resume UMTS neighboring cell analysis tasks. You can also view the status and execution progress of the tasks. 19.4 Querying a UMTS Co-Frequency Neighboring Cell Analysis Report The Nastar provides the function of querying UMTS co-frequency neighboring cell analysis reports. You can query the missing and redundant neighboring cells and the neighboring cell priorities that need to be adjusted of a best cell. Then, you can configure the missing neighboring cells, delete the redundant cells, and adjust the neighboring cell priorities based on the query results. 19.5 Exporting a UMTS Co-Frequency Neighboring Cell Analysis Report This section describes how to export a UMTS co-frequency neighboring cell analysis report. After querying the co-frequency neighboring cell analysis results, you can export the found
analysis results and save them in .csv files or .xls files. Based on the exported analysis results, you can configure neighboring relations on the network to optimize the neighboring relations between the cells on the network. 19.6 Reference for the UMTS Co-Frequency Neighboring Cell Analysis GUI This section describes the interface for UMTS co-frequency neighboring cell analysis and the relevant parameters. Before performing relevant operations, you can familiarize yourself with the functions of the UMTS co-frequency neighboring cell analysis.
19-2
Issue 03 (2010-06-30)
19.1 Basic Knowledge of UMTS Co-Frequency Neighboring Cell Analysis

This section describes the basic knowledge of the UMTS co-frequency neighboring cell analysis, such as the neighboring cell analysis functions, application scenarios, and algorithms for the neighboring cell analysis. The basic knowledge helps you perform the operations related to the UMTS co-frequency neighboring cell analysis. 19.1.1 UMTS Co-Frequency Neighboring Cell Analysis Function The MRs of UEs reflect the actual propagation status of radio signals. Based on the MRs and events reported by UEs, the Nastar can determine the missing neighboring cells, redundant neighboring cells, and the neighboring-cell priorities that need to be adjusted of a measurement cell. If this information exists, the system displays the information. This helps you to solve the problems relating to the network quality that are caused by redundant or missing neighboring cell configuration, or by incorrect priority. 19.1.2 UMTS Co-Frequency Neighboring Cell Analysis Algorithms This section describes the algorithms related to the analysis of UMTS co-frequency neighboring cells. The algorithms help determine the missing neighboring cells, redundant neighboring cells, and recommended priorities of neighboring cells.
19.1.1 UMTS Co-Frequency Neighboring Cell Analysis Function

The MRs of UEs reflect the actual propagation status of radio signals. Based on the MRs and events reported by UEs, the Nastar can determine the missing neighboring cells, redundant neighboring cells, and the neighboring-cell priorities that need to be adjusted of a measurement cell. If this information exists, the system displays the information. This helps you to solve the problems relating to the network quality that are caused by redundant or missing neighboring cell configuration, or by incorrect priority.

Correct neighboring relations ensure that UEs located at the service boundary of a cell can be timely switched to the neighboring cell that has optimal signals. In this case, the handover gain can be obtained and internal interference of the network can be reduced. Thus, QoS and performance of the network are enhanced. Using the configuration data and engineering parameters, the Nastar can analyze the neighboring cells of a selected cell on the basis of the MRs and events reported by a UE. Based on the measurement data, the Nastar can determine the missing and redundant neighboring cells and the neighboring cell priorities that need to be adjusted of the selected cell. In addition, the system can sequence the recommended priorities of the neighboring cells. By comparing the recommended priorities and the actually configured priorities, you can adjust the final priorities of the neighboring cells on the Nastar client. The Nastar displays results in a line or bar chart. It displays the neighboring cells of different types in different colors and the sequence of finally ascertained priorities. You can export the neighboring cell analysis results as a file in .csv or .xls format. Then, you can refer to this file when optimizing the neighboring relations. In measurement results, undefined neighboring cells are identified first by frequencies and primary scrambling codes (PSCs). On the network, cells that have the same frequency and same
PSC may exist around a best cell. You need to predict the signal strength based on the site location, antenna azimuth, and antenna gain of these cells and then determine the possible neighboring cells. In addition, you need to export the analysis report on the possible neighboring cells through the Nastar client.
Limitation and Impact

The accuracy of neighboring cell analysis results may be affected in the following cases:
l l
Engineering parameters are incorrect. The network is not stable during the data collection for neighboring cell analysis. For example, the air interface parameters or the network topology is not stable. Table 19-1 describes the network changes and their impacts.
Table 19-1 Network changes and their impacts Network Change Adding or deleting BTSs Antenna data changes such as the changes of the azimuth, tilt angle, and height Change of handover parameters Change of the RNC topology or other topologies Impact Affects the cell handover and network coverage. In this case, the analysis result cannot correctly reflect the current network status. Results in the changes of the cell coverage and network interference.
Affects the statistical results during the period of collecting and optimizing the neighboring relation data. Affects the execution of measurement tasks. The RNC is responsible for collecting statistical results. Thus, measurement tasks cannot be normally performed if the network topology is changed. You are advised to keep the network topology unchanged during the data collection.
NOTE
The Nastar can only be used for measuring and analyzing the UMTS co-frequency neighboring cells in the case of soft handover or softer handover.
19.1.2 UMTS Co-Frequency Neighboring Cell Analysis Algorithms

This section describes the algorithms related to the analysis of UMTS co-frequency neighboring cells. The algorithms help determine the missing neighboring cells, redundant neighboring cells, and recommended priorities of neighboring cells. The neighboring cell analysis algorithms are the basis for determining the missing neighboring cells, redundant neighboring cells, and recommended priorities of neighboring cells.
l
The algorithm for calculating the recommended priority of a neighboring cell is as follows: 1. Calculate the overall score of a neighboring cell. The overall score of a neighboring cell is determined together by the appearance times of the neighboring cell, the relative difference between the Ec/No of the neighboring
19-4
Issue 03 (2010-06-30)
cell and the Ec/No of the best cell, and the absolute difference between the Ec/No of the neighboring cell and the Ec/No of the best cell. 2. Sequence the total scores in descending order. The higher the total score is, the higher the recommended priority is. The recommended highest priority is 0.
l
The algorithm for determining a missing neighboring cell is as follows: In the case of an undefined neighboring cell, if the recommended priority of the neighboring cell is smaller than the recommended number of neighboring cells, you can infer that the neighboring cell is a missing neighboring cell.
The algorithm for determining a redundant neighboring cell is as follows: In the case of a defined neighboring cell, if the recommended priority of the neighboring cell is not smaller than the recommended number of neighboring cells, you can infer that the neighboring cell is a redundant neighboring cell.
19.2 Process of UMTS Co-Frequency Neighboring Cell Analysis

This section describes the process of UMTS co-frequency neighboring cell analysis. Figure 19-1 shows the general process of co-frequency neighboring cell analysis. Figure 19-1 Workflow of co-frequency neighboring cell analysis
Start
Set an E2E task
Set a co-frequency neighboring cell analysis task Query a co-frequency neighboring cell analysis report Export a co-frequency neighboring cell analysis report End
Issue 03 (2010-06-30)
19-5
Table 19-2 describes the items listed in Figure 19-1. Table 19-2 Description of the workflow of co-frequency neighboring cell analysis No. 1 Procedure Querying NE data information Create an endto-end task corresponding to a cofrequency neighboring cell analysis task Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the co-frequency neighboring cell analysis is imported to the database. You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a cofrequency neighboring cell analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a co-frequency neighboring cell analysis data importing task. After the task is created, the Nastar periodically imports the co-frequency neighboring cell analysis data files saved on the Nastar server to the database. You can create a co-frequency neighboring cell analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required measurement reports from the Nastar database, and then generates an analysis report through the analysis. You can view the analysis results of the co-frequency neighboring cell analysis task that is successfully performed, configure missing neighboring cells, delete redundant neighboring cells, and adjust neighboring cell priorities. You can export a complaint analysis support report from the Nastar.
Create a cofrequency neighboring cell analysis data importing task Create a cofrequency neighboring cell analysis task
Query cofrequency neighboring cell analysis reports Export cofrequency neighboring cell analysis reports
19.3 Managing UMTS Neighboring Cell Analysis Tasks

This section describes how to manage UMTS neighboring cell analysis tasks. You can create, modify, delete, suspend, and resume UMTS neighboring cell analysis tasks. You can also view the status and execution progress of the tasks. 19.3.1 Creating UMTS E2E Tasks
This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 19.3.2 Creating a UMTS Co-Frequency Neighboring Cell Analysis Task This section describes how to create a UMTS co-frequency neighboring cell analysis task. After a UMTS co-frequency neighboring cell analysis task is created, the Nastar, based on the configuration data and the engineering parameters, periodically analyzes the MRs that are reported by UEs and saved in the Nastar database to check for the redundant and missing neighboring cell configuration of a test carrier and to check for the priorities that need to be adjusted. By querying the results of an analysis task, you can learn about the overall status of the network and locate the network quality problems that are caused by redundant or missing neighboring cell configuration, or by incorrect priority. 19.3.3 Modifying a UMTS Co-Frequency Neighboring Cell Analysis Task This section describes how to modify the attributes of a UMTS co-frequency neighboring cell analysis task. You can modify the attributes of a UMTS co-frequency neighboring cell analysis task as required. 19.3.4 Checking a UMTS Co-Frequency Neighboring Cell Analysis Task This section describes how to check a UMTS co-frequency neighboring cell analysis task. You can check the attributes of the UMTS co-frequency neighboring cell analysis task, execution progress of the task, and the execution results.

This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result.
Prerequisite
l l l
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Set the basic information about the task.
1. 2. 3.
In the Task Name field, enter the name of the E2E task. In the OSS name drop-down list box, select the OSS name for the task. Select a task from E2E Task List. Table 19-3 describes the mapping between the E2E tasks and the analysis tasks. Table 19-3 Mapping between the E2E tasks and the analysis tasks E2E Task RTWP data task UMTS Neighboring cell data task UMTS Coverage data task UMTS VIP tracing task UMTS Pilot pollution task UMTS/GSM neighboring cell data task UMTS cell performance data task Analysis Task UMTS uplink interference analysis task UMTS co-frequency neighboring cell analysis task UMTS coverage analysis task UMTS VIP analysis task UMTS pilot pollution analysis task UMTS/GSM neighboring cell analysis task UMTS cell performance analysis task
Step 4 Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. Step 5 Optional: Click Next and then set the exception value for each KPI in the exception value setting list. You need to perform this step only when a UMTS cell performance analysis task is created. Step 6 Click Complete. The MML Preview dialog box is displayed, showing the MML commands related to the current theme analysis E2E task. The MML commands can be exported for future use. Step 7 Click OK. The added E2E task is displayed in the task list. ----End
Postrequisite
After an E2E task is created, you can view that the corresponding collection task has been created by the system in the Task Management window. You can perform a data import task only after the corresponding collection task is complete.
NOTE
19.3.2 Creating a UMTS Co-Frequency Neighboring Cell Analysis Task

This section describes how to create a UMTS co-frequency neighboring cell analysis task. After a UMTS co-frequency neighboring cell analysis task is created, the Nastar, based on the configuration data and the engineering parameters, periodically analyzes the MRs that are reported by UEs and saved in the Nastar database to check for the redundant and missing neighboring cell configuration of a test carrier and to check for the priorities that need to be adjusted. By querying the results of an analysis task, you can learn about the overall status of the network and locate the network quality problems that are caused by redundant or missing neighboring cell configuration, or by incorrect priority.
Prerequisite
l l
Context
l l
Tasks of this type can be performed only once. The system supports a maximum of 50 tasks of this type. The time range of the data to be analyzed must within 7 days.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can be only Once Task. Step 3 Click Next.
Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects in the object navigation tree on the NE Object Selection tab page.
l

Step 7 Set Number of Configured Neighboring Cells on the Parameter Setting tab page. Step 8 Click Complete. ----End
Postrequisite
l
Deleting a task This section describes how to delete a neighboring cell analysis task. You can delete the unnecessary neighboring cell analysis tasks to save system resources.
NOTE
The tasks in Running state cannot be deleted.
1.
Choose UMTS Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task This section describes how to suspend a neighboring cell analysis task. To delay the task execution, you can suspend a neighboring cell analysis task that is in idle state. After this operation, the neighboring cell analysis task is in suspended state.
NOTE
1.
2.
Select a task from the task list in the upper-right pane, and then click Only the tasks whose Status are Idle can be suspended. Otherwise, the unavailable.
. button
19-10
Issue 03 (2010-06-30)

l
NOTE
Only the neighboring cell analysis tasks that are in idle state can be scheduled by the system.
1.
2.
The task can be performed only when its Status is Suspend. If the task is not in suspended state, the button is unavailable.
19.3.3 Modifying a UMTS Co-Frequency Neighboring Cell Analysis Task

This section describes how to modify the attributes of a UMTS co-frequency neighboring cell analysis task. You can modify the attributes of a UMTS co-frequency neighboring cell analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS co-frequency neighboring cell analysis task is created.
Context
Procedure
Step 1 Choose UMTS Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the relevant parameters, see 19.6.3 Parameters for Creating and Modifying UMTS Co-Frequency Neighboring Cell Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the object navigation tree, and the Number of Configured Neighboring Cells parameter.

19.3.4 Checking a UMTS Co-Frequency Neighboring Cell Analysis Task

This section describes how to check a UMTS co-frequency neighboring cell analysis task. You can check the attributes of the UMTS co-frequency neighboring cell analysis task, execution progress of the task, and the execution results.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS co-frequency neighboring cell analysis task is created.
Procedure
Step 1 Choose UMTS Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required. Purpose Checking the attributes of a neighboring cell analysis task Operation Select a task from the task list in the upperright pane. Double-click the task or click .
You can check the attributes of the selected task or modify the relevant parameter settings. For detailed operations, see 19.3.3 Modifying a UMTS Co-Frequency Neighboring Cell Analysis Task. Checking the execution progress of the active task Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column.
19-12
Issue 03 (2010-06-30)
----End
Postrequisite
l
19.4 Querying a UMTS Co-Frequency Neighboring Cell Analysis Report

The Nastar provides the function of querying UMTS co-frequency neighboring cell analysis reports. You can query the missing and redundant neighboring cells and the neighboring cell priorities that need to be adjusted of a best cell. Then, you can configure the missing neighboring cells, delete the redundant cells, and adjust the neighboring cell priorities based on the query results.
Prerequisite
Issue 03 (2010-06-30)
19-13
Procedure
Step 1 Choose UMTS Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. All the analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result, or right-click a result and choose Neighboring Cell Analysis from the shortcut menu. The Neighboring Cell Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell from the list of best cells in Area (2) in the Neighboring Cell Analysis window.
l
For the rules of dividing areas, see 19.6.1 Interface Description: UMTS Co-Frequency Neighboring-Cell Analysis. The neighboring cell list in Area (4) displays all the neighboring cells of the selected cell. The Nastar determines the redundant neighboring cells, the missing neighboring cells, the neighboring cells whose priorities need to be adjusted, and the neighboring cells that require no operations based on the neighboring cell analysis algorithms. It also provides the relevant operation suggestions. For details about the neighboring cell analysis algorithms, see 19.1.2 UMTS Co-Frequency Neighboring Cell Analysis Algorithms. If a neighboring cell of the selected cell is unknown, the Nastar adds cellid:p-sc to identify the unknown neighboring cell. The system highlights the information about undefined neighboring cells in grey.
In the figure of Area (5), the normal neighboring cells, redundant neighboring cells, and missing neighboring cells of the selected cell are displayed in legends in different colors. You can select a parameter from the drop-down list box above Area (5). Then, the parameter values corresponding to each neighboring cell are displayed in a line chart. In the figure, the left axis represents the total scores, the right axis represents the value of the line chart, and the horizontal coordinate represents names of the neighboring cells. The neighboring cells are sequenced in descending order of the total scores from left to right.
Step 5 Select a neighboring cell whose priority needs to be adjusted in Area (4), and then click the up or down icon above the list to adjust the priority. ----End
Postrequisite
l
Right-click the chart, and then choose Property from the shortcut menu. In the displayed Chart Property dialog box, set the coordinate axes of and basic information about the chart.
19-14
Right-click the chart, and then choose Save as from the shortcut menu. In the displayed Save dialog box, set the save path and file name, and then click Save to save the queried chart as a file on the local PC. Right-click the chart, and then choose Print from the shortcut menu. In the displayed Page Setup dialog box, set print properties, and then click OK. If the chart is not clear due to an excessive number of dots, right-click the chart, and then choose Zoom In > ***, Zoom Out > ***, or Auto Range > *** to adjust the size of the chart. Here, *** indicates a submenu item. It can be Both Axes, Horizontal Axis, or Vertical Axis, which indicates that you can adjust both axes, the horizontal axis, or the vertical axis, respectively.
19.5 Exporting a UMTS Co-Frequency Neighboring Cell Analysis Report

This section describes how to export a UMTS co-frequency neighboring cell analysis report. After querying the co-frequency neighboring cell analysis results, you can export the found analysis results and save them in .csv files or .xls files. Based on the exported analysis results, you can configure neighboring relations on the network to optimize the neighboring relations between the cells on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried UMTS co-frequency neighboring cell analysis reports.
Procedure
l Perform the following operations as required.
Issue 03 (2010-06-30)
19-15
If ... You want to export the overview information about neighboring cells
Then ... 1. Click in the UMTS Intra-Frequency Neighboring Cell Analysis window. The Save dialog box is displayed. 2. Set the filename, file type, and save path, and then click Save. The saved .csv or .xls file is opened automatically so that you can view the information in it. The information in the .csv or .xls file consists of the task name, task creator, execution result, start time, end time, and best cell information.
You want to export all neighboring cell 1. Click in the UMTS Intra-Frequency optimization results Neighboring Cell Analysis window. The Save dialog box is displayed. If the analysis result data amount of all the neighboring cells is large, it takes some time for the dialog box to be displayed. 2. Set the save path, and then click Save. You are allowed to save only the analysis results of all neighboring cells as CSV files by RNC. The analysis result of the neighboring cells of each cell corresponds to one CSV file. The naming convention is task name_NE name_NCS.csv. Export the information about the 1. Click in the UMTS Intra-Frequency possible neighboring cells of a best cell Neighboring Cell Analysis window. The Save dialog box is displayed. 2. Set the name, type and save path of the file. Then, click Save. After being saved, a CSV or XLS file is automatically open so that you can view the file conveniently. The CSV or XLS file contains the following information: the task name, creator, start time and end time of the results, and possible neighboring cells of the best cell.
19-16
Issue 03 (2010-06-30)

NOTE
l l l
Exporting overview information about neighboring cells refers to exporting the information about all the best cells involved in the selected analysis task. Exporting all neighboring cell optimization results refers to exporting the information about the neighboring cells of each best cell. Exporting the analysis results of possible neighboring cells refers to exporting the information about the possible neighboring cells of a best cell.
----End
19.6 Reference for the UMTS Co-Frequency Neighboring Cell Analysis GUI
This section describes the interface for UMTS co-frequency neighboring cell analysis and the relevant parameters. Before performing relevant operations, you can familiarize yourself with the functions of the UMTS co-frequency neighboring cell analysis. 19.6.1 Interface Description: UMTS Co-Frequency Neighboring-Cell Analysis This section describes the interface for UMTS co-frequency neighboring-cell analysis. Before performing relevant operations, you can familiarize yourself with the functions of the areas on the interface. 19.6.2 Parameters for Creating UMTS E2E Tasks This section describes the parameters for creating UMTS E2E tasks. You can refer to the description when creating a UMTS E2E task. 19.6.3 Parameters for Creating and Modifying UMTS Co-Frequency Neighboring Cell Analysis Tasks This section describes the parameters for creating and modifying UMTS co-frequency neighboring cell analysis tasks. You can refer to the description when creating or modifying a UMTS co-frequency neighboring cell analysis task. 19.6.4 Parameters for Querying UMTS Co-Frequency Neighboring Cell Analysis Reports This section describes the parameters for querying UMTS co-frequency neighboring cell analysis reports. You can refer to the description when querying UMTS co-frequency neighboring cell analysis reports.
19.6.1 Interface Description: UMTS Co-Frequency NeighboringCell Analysis

This section describes the interface for UMTS co-frequency neighboring-cell analysis. Before performing relevant operations, you can familiarize yourself with the functions of the areas on the interface. The analysis results of co-frequency neighboring cells can be displayed in tables or in column charts, as shown in Figure 19-2.
Issue 03 (2010-06-30)
19-17
Figure 19-2 UMTS co-frequency neighboring-cell analysis interface
No. Name (1) Button area
Description Consists of three buttons that are used for exporting the overview information about neighboring cells, all neighboring cell optimization results, and all possible neighboring cells of a best cell.
(2)
Current best cell information list Displays the information related to the current best cell. Button area Consists of three buttons used for adjusting the priorities of neighboring cells and restoring default priority. Displays all the co-frequency neighboring cells of the cell selected in area (2).
(3)
(4)
Neighboring cell list
19-18
Issue 03 (2010-06-30)
No. Name (5) Image area
Description Displays the information about all the neighboring cells of the selected best cell in the combination of column charts and line charts.
NOTE If the name of a missing neighboring cell of the best cell is unknown, the neighboring cell is marked cellid:p-sc.

Parameter Basic information Task Name OSS Name E2E Task List Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task. Indicates the types of E2E tasks. You can select one of the following E2E tasks: RTWP data task, UMTS Neighboring cell data task, UMTS Coverage data task, UMTS VIP tracing task, UMTS Pilot pollution task, UMTS/GSM neighboring cell data task, or UMTS cell performance data task. Indicates the time when the E2E task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the E2E task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Indicates the NE related to the E2E task.
Start Time

The following table lists the parameters for setting the exception threshold during the creation of the UMTS cell performance analysis E2E task.
Issue 03 (2010-06-30)
19-19
Parameter Measurement information Service Type Exception Type KPI Determination rule Exception Value
Description Indicates service types involved during the exception determination, such as Network level. Indicates the exception types involved during the exception determination, such as Call setup failure. Indicates the KPIs involved during the exception determination. Indicates the types of exception determination, such as >=. Indicates the exception threshold involved during the exception determination, such as 30 The value is an integer from 0 to 65535.
19.6.3 Parameters for Creating and Modifying UMTS Co-Frequency Neighboring Cell Analysis Tasks
This section describes the parameters for creating and modifying UMTS co-frequency neighboring cell analysis tasks. You can refer to the description when creating or modifying a UMTS co-frequency neighboring cell analysis task.
Parameter Basic Information Task Name Description Indicates the name of a neighboring cell analysis task. Value range:
l l
l l
Task Type
Choose UMTS Intra-Frequency Neighboring Cell Analysis Task from the Task Type navigation tree. Such a task can be executed only once in a time segment.
Execution Type
19-20
Issue 03 (2010-06-30)
Parameter Note
Description Indicates the description of the task. Value range:

l l
Time Information
Data Time Scope
The start time must be earlier than the end time. You can either type the time in this field, or click to select the date and time in the Date Selection dialog box. This parameter is valid for only one-time tasks.
Task Start At
Indicates the time when the analysis task is executed. This start time must be equal to or later than the end time specified by Data Time Scope.
Object Information
RNC Cell Group
If you select this option, the navigation tree displays all the RNCs on the entire network. If you select this option, the navigation tree displays all the cell groups on the entire network. Indicates the number of neighboring cells that you are recommended to configure. N can be any integer ranging from 0 to 32. The default value is 30.
19.6.4 Parameters for Querying UMTS Co-Frequency Neighboring Cell Analysis Reports
This section describes the parameters for querying UMTS co-frequency neighboring cell analysis reports. You can refer to the description when querying UMTS co-frequency neighboring cell analysis reports.
NOTE
For details about the rules of dividing areas, see 19.6.1 Interface Description: UMTS Co-Frequency Neighboring-Cell Analysis.
Parameters related to the general information about a best cell

Parameter RNC ID Cell ID Description Indicates the ID of the RNC. Indicates the ID of the best cell.
Issue 03 (2010-06-30)
19-21
Parameter Cell Name P-SC Downlink ARFCN Number of Measurement Reports Average Ec/No (dB) RSCP (dBm) Number of the 1A1C Events Number of Missing Neighboring Cells Number of Redundant Neighboring Cells Number of Configured IntraFrequency Neighboring Cells
Description Indicates the name of the best cell, for example, Cell_1. Indicates the primary scrambling code (P-SC) of the best cell. Indicates the downlink absolute radio frequency channel number (ARFCN) of the best cell. Indicates the number of MRs received by the best cell.
Indicates the average Ec/No of the best cell. Indicates the average Received Signal Code Power (RSCP) of the best cell. Indicates the total number of 1A/1C events triggered by neighboring cells. Indicates the number of missing intra-frequency neighboring cells among the undefined neighboring cells of the best cell. Indicates the number of redundant intra-frequency neighboring cells among the defined neighboring cells of the best cell. Indicates the number of defined intra-frequency neighboring cells of the best cell.
Parameters related to the detailed information about neighboring cells

Parameter Neighboring RNC ID Neighboring Cell ID Neighboring Cell Name P-SC Neighboring Cell Type Description Indicates the number of the RNC that the neighboring cell belongs to. Indicates the ID of a neighboring cell. Indicates the name of a neighboring cell, for example, Cell_1. Indicates the P-SC of a neighboring cell. Indicates the type of a neighboring cell. The options are Defined Neighboring Cell (reserved), Defined Neighboring Cell (redundant), Undefined Neighboring Cell (missing), and Undefined Neighboring Cell (non-operation). Indicates the total score of each neighboring cell. The total score is calculated through the neighboring cell algorithm based on each measurement result.
Total Score
19-22
Issue 03 (2010-06-30)
Parameter Final Priority Recommended Priority Configured Priority Average RSCP of Neighboring Cells (dBm) Average ECNO of Neighboring Cells (dB) Average ECNO of Primary Cells (dB) Average RSCP of Primary Cells (dBm) MR Number of the Neighboring Cell in the Monitor Set/ Detective Set MR Number of the Neighboring Cell in the Active Set Number of the 1A/ 1C Events Number of the 1D Events Distance (km) Neighboring Cell Service Type
Description Indicates the final priority after the manual adjustment based on the recommended priority. Indicates the recommended priority of a neighboring cell based on the total score of the neighboring cell. The higher the total score, the higher is the recommended priority. Indicates the priority of an intra-frequency neighboring cell in the configuration data. Indicates the average RSCP of a neighboring cell in all the MRs that contain the information about this neighboring cell. Indicates the average Ec/No of a neighboring cell in all the MRs that contain the information about this neighboring cell. Indicates the average Ec/No of the best cell in all the MRs that contains the current neighboring cell. Indicates the average RSCP of the best cell in all the measurement reports that contains the current neighboring cell. Indicates the number of MRs that contain the current neighboring cell in the monitor set or detective set.
Indicates the number of MRs that contain the current neighboring cell in the active set. Indicates the number of 1A/1C events triggered by the current neighboring cell. Indicates the number of 1D events triggered by the current neighboring cell. Indicates the distance between the best cell and the current neighboring cell. Indicates the type of the neighboring cell. The options are indoor and outdoor. By knowing the types of neighboring cells, you can avoid deleting important neighboring cells.
Issue 03 (2010-06-30)
19-23
20 Neighboring UMTS/GSM Cell Analysis
20
Neighboring UMTS/GSM Cell Analysis
About This Chapter

This section describes the neighboring UMTS/GSM cell analysis. The neighboring UMTS/GSM cell analysis supports the management of neighboring UMTS/GSM cell analysis tasks, check of the neighboring UMTS/GSM cell analysis reports, and export of the neighboring UMTS/ GSM cell analysis reports. The Nastar supports the check of redundant and missing inter-RAT neighboring cells, and thus helps to solve the network quality problems caused by redundant and missing neighboring cell configuration. 20.1 Basic Knowledge of Neighboring UMTS/GSM Cell Analysis This section describes the basic knowledge of the neighboring UMTS/GSM cell analysis, such as the neighboring UMTS/GSM cell analysis function, application scenarios, and algorithms for neighboring cell analysis. The basic knowledge helps you perform the operations of neighboring UMTS/GSM cell analysis. 20.2 Process of Neighboring UMTS/GSM Cell Analysis This section describes the process of neighboring UMTS/GSM cell analysis. 20.3 Managing Neighboring UMTS/GSM Cell Analysis Tasks This section describes how to manage the neighboring UMTS/GSM cell analysis tasks. You can create, modify, delete, suspend, and resume neighboring UMTS/GSM cell analysis tasks. You can also view the status and execution progress of a task. 20.4 Querying Neighboring UMTS/GSM Cell Analysis Reports This section describes how to query neighboring UMTS/GSM cell analysis reports. With this function, you can query all the defined and undefined neighboring GSM cells of a UMTS cell under an RNC as required. In addition, you can calculate the total score of neighboring cells according to the related algorithm and sort the neighboring cells, thus helping users locate redundant and missing neighboring cells in the inter-RAT neighboring cells. 20.5 Querying Possible Neighboring UMTS/GSM Cell Analysis Reports This section describes how to query possible neighboring UMTS/GSM cell analysis reports. With this function, you can learn about all the possible neighboring GSM cells of a UMTS cell quickly based on the measurement result of the missing neighboring cell configuration and the analysis of engineering parameters and configuration data, thus improving the neighboring relations on the network. 20.6 Exporting Neighboring UMTS/GSM Cell Analysis Reports
This section describes how to export neighboring UMTS/GSM cell analysis reports. You can export the neighboring UMTS/GSM cell analysis reports as .csv or .xls files to help improve the neighboring relations on the network. 20.7 Exporting Possible Neighboring UMTS/GSM Cell Analysis Reports This section describes how to export possible neighboring UMTS/GSM cell analysis reports. You can export the possible neighboring cell analysis results as .csv or .xls files to help improve the neighboring relations on the network. 20.8 Reference to the Neighboring UMTS/GSM Cell Analysis Interface This section describes the interface for neighboring UMTS/GSM cell analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of neighboring UMTS/GSM cell analysis.
20-2
Issue 03 (2010-06-30)
20.1 Basic Knowledge of Neighboring UMTS/GSM Cell Analysis

This section describes the basic knowledge of the neighboring UMTS/GSM cell analysis, such as the neighboring UMTS/GSM cell analysis function, application scenarios, and algorithms for neighboring cell analysis. The basic knowledge helps you perform the operations of neighboring UMTS/GSM cell analysis. 20.1.1 Neighboring UMTS/GSM Cell Analysis This section describes the neighboring UMTS/GSM cell analysis function. This function is used to analyze defined and undefined neighboring GSM cells of UMTS cells. By performing this task, you can check and handle the problem of redundant and missing neighboring cell configuration. Direct display of the information provided by this function can help you solve network quality problems that are caused by the redundant and missing neighboring cell configuration. 20.1.2 Algorithm for the Neighboring UMTS/GSM Cell Analysis This section describes the algorithm for the neighboring UMTS/GSM cell analysis, such as the algorithm used to check missing neighboring cells and redundant neighboring cells.
20.1.1 Neighboring UMTS/GSM Cell Analysis

This section describes the neighboring UMTS/GSM cell analysis function. This function is used to analyze defined and undefined neighboring GSM cells of UMTS cells. By performing this task, you can check and handle the problem of redundant and missing neighboring cell configuration. Direct display of the information provided by this function can help you solve network quality problems that are caused by the redundant and missing neighboring cell configuration.
Inter-RAT Neighboring Cell Analysis

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

The network must be stable during the period when data for neighboring cell analysis is collected. Otherwise, the accuracy of the analysis cannot be guaranteed. Table 20-1 describes the network changes and their impacts.
Table 20-1 Network changes and their impacts Network Change Adding or deleting BTSs Antenna data change such as change of the azimuth, tilt angle, or height Changes in handover relations and parameters Change of RNC topology and other NE topology Impact Affects the cell handover and network coverage. In this case, the analysis result cannot correctly show the current network status. Results in the changes in cell coverage and network interference.
Affects the statistical results during the period of collecting the data about neighboring relations and optimizing neighboring relations. The RNC is responsible for collecting statistical results. Thus, the measurement task cannot be normally performed if the network topology is changed. You are advised to keep the network topology unchanged during the data collection.
20.1.2 Algorithm for the Neighboring UMTS/GSM Cell Analysis

This section describes the algorithm for the neighboring UMTS/GSM cell analysis, such as the algorithm used to check missing neighboring cells and redundant neighboring cells. Based on the information reported by the MS such as the signal level of a cell, the Nastar calculates the total score and then sorts the defined and undefined neighboring GSM cells. According to the sequence of neighboring GSM cells and result analysis chart, users can analyze the neighboring cells depending on the actual network situation, and then provide suggestions on the missing neighboring GSM cell configuration and redundant neighboring GSM cells to be deleted. The algorithm for the neighboring UMTS/GSM cell analysis is as follows: 1. Calculate the total score of all the neighboring GSM cells of the test cell. The sequence of neighboring GSM cells is arranged according to the strength of receive level. That is, the stronger the signal level is, the smaller the sequence number of the neighboring GSM cell and the higher the score is. The score is set during the creation of a neighboring UMTS/GSM cell analysis task. 2. Determine the missing neighboring cells. When the sequence number of an undefined neighboring GSM cell is smaller than or equal to Number of Configured Neighboring Cells that is set when creating a neighboring UMTS/GSM cell analysis task, the neighboring GSM cell is regarded as a missing neighboring cell. 3. Determine the redundant neighboring cells. When the sequence number of a defined neighboring GSM cell is larger than Number of Configured Neighboring Cells that is set when creating a neighboring UMTS/GSM cell analysis task, the neighboring GSM cell is regarded as a redundant neighboring cell.
20-4
Issue 03 (2010-06-30)
20.2 Process of Neighboring UMTS/GSM Cell Analysis

This section describes the process of neighboring UMTS/GSM cell analysis. Figure 20-1 shows the process of neighboring UMTS/GSM cell analysis. Figure 20-1 Process of neighboring UMTS/GSM cell analysis

Table 20-2 Process of neighboring UMTS/GSM cell analysis No. 1 Procedure Querying NE data information Create an endto-end task corresponding to a neighboring UMTS/GSM cell analysis task Creating a neighboring UMTS/GSM cell measurement task files importing task Creating a neighboring UMTS/GSM cell analysis task Querying neighboring UMTS/GSM cell analysis reports Exporting neighboring UMTS/GSM cell analysis reports Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the neighboring UMTS/GSM cell analysis is imported to the database. You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a neighboring UMTS/GSM cell analysis task. After the task is created, the Nastar issues the MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. Finally, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a neighboring UMTS/GSM cell measurement task files importing task. After the task is created, the Nastar periodically imports the neighboring UMTS/GSM cell measurement task files saved on the Nastar server to the database. You can create a neighboring UMTS/GSM cell analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required measurement data of neighboring UMTS/GSM cells from the Nastar database, and then generates an analysis report. You can view the analysis results of the neighboring UMTS/ GSM cell analysis tasks that are successfully performed, add missing neighboring cells, and delete redundant neighboring cells. You can export analysis result files in the Nastar performance analysis system.
20.3 Managing Neighboring UMTS/GSM Cell Analysis Tasks

This section describes how to manage the neighboring UMTS/GSM cell analysis tasks. You can create, modify, delete, suspend, and resume neighboring UMTS/GSM cell analysis tasks. You can also view the status and execution progress of a task.
20.3.1 Creating UMTS E2E Tasks This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 20.3.2 Creating a Neighboring UMTS/GSM Cell Analysis Task This section describes how to create a neighboring UMTS/GSM cell analysis task. In a neighboring UMTS/GSM cell analysis task, the Nastar performance analysis system analyzes the relevant data in the Nastar database periodically. By checking the analysis results, you can know the redundant and missing inter-RAT neighboring cells, and thus quickly locate and solve network problems. 20.3.3 Modifying Neighboring UMTS/GSM Cell Analysis Tasks This section describes how to modify a neighboring UMTS/GSM cell analysis task. You can modify the attributes of an existing neighboring UMTS/GSM cell analysis task according to the new requirement. 20.3.4 Querying Neighboring UMTS/GSM Cell Analysis Tasks This section describes how to check a neighboring UMTS/GSM cell analysis task. You can check the attributes of the neighboring UMTS/GSM cell analysis task, execution progress of the task, and the execution results.

Prerequisite
l l l
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Set the basic information about the task. 1.
Issue 03 (2010-06-30)
In the Task Name field, enter the name of the E2E task.
2. 3.
In the OSS name drop-down list box, select the OSS name for the task. Select a task from E2E Task List. Table 20-3 describes the mapping between the E2E tasks and the analysis tasks. Table 20-3 Mapping between the E2E tasks and the analysis tasks E2E Task RTWP data task UMTS Neighboring cell data task UMTS Coverage data task UMTS VIP tracing task UMTS Pilot pollution task UMTS/GSM neighboring cell data task UMTS cell performance data task Analysis Task UMTS uplink interference analysis task UMTS co-frequency neighboring cell analysis task UMTS coverage analysis task UMTS VIP analysis task UMTS pilot pollution analysis task UMTS/GSM neighboring cell analysis task UMTS cell performance analysis task
Postrequisite
After an E2E task is created, you can view that the corresponding collection task has been created by the system in the Task Management window. You can perform a data import task only after the corresponding collection task is complete. To view the attributes of a created E2E task, perform the following operations:
1. 2.
Select a task from the task list in the right pane of the E2E Task Management window, and then click Attribute. The Attribute dialog box is displayed. View the related parameters.
NOTE
20.3.2 Creating a Neighboring UMTS/GSM Cell Analysis Task

This section describes how to create a neighboring UMTS/GSM cell analysis task. In a neighboring UMTS/GSM cell analysis task, the Nastar performance analysis system analyzes the relevant data in the Nastar database periodically. By checking the analysis results, you can know the redundant and missing inter-RAT neighboring cells, and thus quickly locate and solve network problems.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the neighboring UMTS/GSM cell analysis task function. The E2E task, collection task, and data import task corresponding to the neighboring UMTS/GSM cell analysis task are normal. The neighboring UMTS/GSM cell analysis task can be created successfully even if the prerequisites are not met. The execution of the neighboring UMTS/GSM cell analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l l
A neighboring UMTS/GSM cell analysis task can be performed for only once. A maximum of 50 tasks of this type can be created and the time range of the data in a task cannot exceed 7 days. Before you create an analysis task, check and ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name
, Task Type , and Note . The value of Execution Type can only be Once Task . Step 3 Click Next . Step 4 Set Time Setting for Once Task Data . Step 5 Click Next . Step 6 Select one or multiple objects in the object navigation tree on the Ne Selection tab page.
l

Step 7 Set Neighboring Cell Analysis Parameters , Possible Nerghboring Cell Parameters , and Result Show Parameters on the Parameter Setting tab page. Step 8 Click Complete . ----End
Postrequisite
l
Delete a task.
20-10
You can delete a neighboring cell analysis task that is not required for saving the system resources.
NOTE
1.
Choose UMTS/GSM Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function , the task list on the right displays all the performance analysis tasks.
2. 3.
Select a task from the task list in the upper right pane, and then click In the displayed Confirm dialog box, click OK.
Suspend a task. This section describes how to suspend a neighboring cell analysis task. To delay the task execution, you can suspend a neighboring cell analysis task that is in the idle state. After this operation, the state of the neighboring cell analysis task changes to suspended.
NOTE
The Nastar can manage only the neighboring cell analysis tasks that are not suspended.
1.
Choose UMTS/GSM Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function , the task list on the right displays all the performance analysis tasks.
2.
Select a task from the task list in the upper-right pane, and then click This operation can be performed for only the tasks whose Status is Idle . If a task is not in the idle state, the button is unavailable.
Restoring a task This section describes how to resume a neighboring cell analysis task. You can resume a suspended neighboring cell analysis task to the idle state. Then, the Nastar can perform the resumed task..
NOTE
The Nastar can perform only the neighboring cell analysis tasks that are in the idle state.
1.
Choose UMTS/GSM Neighboring Cell Analysis Task from the navigation tree in the
Issue 03 (2010-06-30)
Analysis Task Management window. If you choose Subject Function , the task list on the right displays all the performance analysis tasks. 2. Select a task from the task list in the upper-right pane, and then click This operation can be performed for only the tasks whose Status is Suspended . If a task is not in the suspended state, the button is unavailable. .
20.3.3 Modifying Neighboring UMTS/GSM Cell Analysis Tasks

This section describes how to modify a neighboring UMTS/GSM cell analysis task. You can modify the attributes of an existing neighboring UMTS/GSM cell analysis task according to the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. A neighboring UMTS/GSM cell analysis task is created.
Context
Procedure
Step 1 Click the UMTS/GSM Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For description of the parameters, see 20.8.2 Parameters for Creating and Modifying Neighboring UMTS/GSM Cell Analysis Tasks. You are allowed to modify the following parameters: Note in the basic information, Data Time Scope and Task Start At in the time information, information in the object navigation tree, Neighboring Cell Analysis Parameters, Possible Nerghboring Cell Parameters, and Result Show Parameters.

20.3.4 Querying Neighboring UMTS/GSM Cell Analysis Tasks

This section describes how to check a neighboring UMTS/GSM cell analysis task. You can check the attributes of the neighboring UMTS/GSM cell analysis task, execution progress of the task, and the execution results.
Prerequisite
l l
You have logged in to the Nastar client. A neighboring UMTS/GSM cell analysis task is created.
Procedure
Step 1 Click the UMTS/GSM Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Then ...
Query the attributes related to the Select a task from the task list in the upperneighboring UMTS/GSM cell analysis task right pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 20.3.3 Modifying Neighboring UMTS/GSM Cell Analysis Tasks. Check the execution progress of the running task Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column. Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
Check the task execution results
----End
Postrequisite
l
20.4 Querying Neighboring UMTS/GSM Cell Analysis Reports

This section describes how to query neighboring UMTS/GSM cell analysis reports. With this function, you can query all the defined and undefined neighboring GSM cells of a UMTS cell under an RNC as required. In addition, you can calculate the total score of neighboring cells according to the related algorithm and sort the neighboring cells, thus helping users locate redundant and missing neighboring cells in the inter-RAT neighboring cells.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the neighboring UMTS/GSM cell analysis task function. A neighboring UMTS/GSM cell analysis task is executed successfully.
Procedure
Step 1 Click the UMTS/GSM Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result record, or right-click a result record and then choose Analysis Result from the shortcut menu. The UMTS/GSM Neighboring Cell Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell from the test cell list in Area (2) in the UMTS/GSM Neighboring Cell Analysis Task window.
l
The neighboring GSM cell list on the right in Area (4) displays all the defined and undefined neighboring GSM cells of the selected cell.
20-14
The Nastar determines the redundant neighboring cells, missing neighboring cells, and neighboring cells requiring no operations according to the neighboring cell analysis algorithms. It also provides the relevant operation suggestions. For details about the neighboring cell analysis algorithms, see 20.1.2 Algorithm for the Neighboring UMTS/GSM Cell Analysis. If User Modify is selected for a row in the neighboring GSM cell list, the Nastar saves the modified list automatically. Thus, you can view the modified information the next time you open the analysis report. If no modification is made, the Nastar displays the list in the database the next time you open the analysis report. The file with the modification automatically saved is stored in the installation path of the client. This file is deleted automatically when the corresponding task is deleted. If the possible neighboring cell table of the neighboring cell analysis report is modified (see the description in 20.5 Querying Possible Neighboring UMTS/GSM Cell Analysis Reports), the information about the undefined neighboring cells in the neighboring GSM cell list is replaced by the information about the most possible neighboring cell selected in the preceding possible neighboring cell analysis the next time the neighboring cell analysis report is opened. The following fields in the report are updated: GSM Neighboring Cell Name, LAC, CI, and Distance (km). You can double-click the neighboring GSM cell list to zoom in on the area, and then doubleclick the area again to restore the area to the original size.
l
----End
Postrequisite
l
Issue 03 (2010-06-30)
20-15

l
20.5 Querying Possible Neighboring UMTS/GSM Cell Analysis Reports

This section describes how to query possible neighboring UMTS/GSM cell analysis reports. With this function, you can learn about all the possible neighboring GSM cells of a UMTS cell quickly based on the measurement result of the missing neighboring cell configuration and the analysis of engineering parameters and configuration data, thus improving the neighboring relations on the network.
Prerequisite
l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the possible neighboring UMTS/GSM cell analysis task function. A possible neighboring UMTS/GSM cell analysis task is executed successfully.
Procedure
Step 1 Click the UMTS/GSM Neighboring Cell Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Right-click a result record, and then choose Possible Neighboring Cell Analysis Result. The UMTS/GSM Possible Neighboring Cell Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell from the possible neighboring cell overview table in the UMTS/GSM Possible Neighboring Cell Analysis Task window.
l
All the possible neighboring GSM cells of the selected cell are displayed in the possible neighboring cell confirmation table on the right. To add a possible neighboring cell to a test cell, do as follows: 1. 2. above the possible neighboring cell confirmation table to open the UMTS/ Click GSM Possible Neighboring Cell Analysis Task dialog box. Select one or multiple cells from the Cell List navigation tree, and then click Confirm.
20-16

l
To export all information in the possible neighboring cell overview table, see 20.7 Exporting Possible Neighboring UMTS/GSM Cell Analysis Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. Right-click the query result list and then choose Save As... from the shortcut menu. After setting a file name and specifying the save path, click Save to save the query results to a .csv or .xls file. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
20.6 Exporting Neighboring UMTS/GSM Cell Analysis Reports

This section describes how to export neighboring UMTS/GSM cell analysis reports. You can export the neighboring UMTS/GSM cell analysis reports as .csv or .xls files to help improve the neighboring relations on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the neighboring UMTS/GSM cell analysis reports.
Procedure
l Perform the following operations as required: If You Want to ... Export the neighboring cell overview Then ... 1. Click in the UMTS/GSM Neighboring Cell Analysis Task window. The Save dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. The main information contained in the .csv or .xls files is task name, creator, start time of the result, end time of the result, and related information about the test cells.
If You Want to ... Export the neighboring cell optimization result of a test cell
Then ... 1. Click in the UMTS/GSM Neighboring Cell Analysis Task window. The Save dialog box is displayed. 2. Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. The main information contained in the .csv or .xls files is task name, creator, start time of the result, end time of the result, RNC serving the test cell, number and name of the test cell, and defined neighboring GSM cell and undefined neighboring GSM cell information.
Export all the possible neighboring cell 1. Click in the UMTS/GSM analysis results Neighboring Cell Analysis Task window. The Save dialog box is displayed. If the analysis result data amount of all the neighboring cells is large, you need to wait for a while before the dialog box is displayed. 2. Specify a save path for the file. Then, click Save. You are only allowed to save all the neighboring cell analysis results as .xls files on the basis of RNC. The neighboring cell analysis results of each RNC correspond to one .xls file. The naming convention is task name_NE name_NCS.xls.
NOTE
l l l
Exporting neighboring cell overview refers to exporting the information about all the test cells involved in the selected analysis task. Exporting the neighboring cell optimization result of a test cell refers to exporting the information about the defined and undefined neighboring cells of a specified test cell. Exporting all the neighboring cell analysis results refers to exporting the information about the defined and undefined neighboring cells of all test cells.
----End
20-18
Issue 03 (2010-06-30)
20.7 Exporting Possible Neighboring UMTS/GSM Cell Analysis Reports

This section describes how to export possible neighboring UMTS/GSM cell analysis reports. You can export the possible neighboring cell analysis results as .csv or .xls files to help improve the neighboring relations on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the possible neighboring UMTS/GSM cell analysis reports.
Context
Procedure
Step 1 In the UMTS/GSM Possible Neighboring Cell Analysis Task window, click possible neighboring cell overview table to open the Save dialog box. Step 2 Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. ----End above the
20.8 Reference to the Neighboring UMTS/GSM Cell Analysis Interface

This section describes the interface for neighboring UMTS/GSM cell analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of neighboring UMTS/GSM cell analysis. 20.8.1 Parameters for Creating UMTS E2E Tasks This section describes the parameters for creating UMTS E2E tasks. You can refer to the description when creating a UMTS E2E task. 20.8.2 Parameters for Creating and Modifying Neighboring UMTS/GSM Cell Analysis Tasks This section describes the parameters for creating and modifying neighboring UMTS/GSM cell analysis tasks. You can refer to the description when creating and modifying a neighboring UMTS/GSM cell analysis task. 20.8.3 Parameters for Querying the Analysis Reports of Neighboring UMTS/GSM Cells This section describes the parameters for querying the analysis reports of neighboring UMTS/ GSM cells. You can refer to the description when querying the analysis reports of neighboring UMTS/GSM cells.
20.8.4 Parameters for Querying the Analysis Reports of Possible Neighboring UMTS/GSM Cells This section describes the parameters for querying the analysis reports of possible neighboring UMTS/GSM cells. You can refer to the description when querying the analysis reports of possible neighboring UMTS/GSM cells.

Start Time

The following table lists the parameters for setting the exception threshold during the creation of the UMTS cell performance analysis E2E task. Parameter Measurement information Service Type Exception Type Description Indicates service types involved during the exception determination, such as Network level. Indicates the exception types involved during the exception determination, such as Call setup failure.
20-20
Issue 03 (2010-06-30)
Parameter KPI Determination rule Exception Value
Description Indicates the KPIs involved during the exception determination. Indicates the types of exception determination, such as >=. Indicates the exception threshold involved during the exception determination, such as 30 The value is an integer from 0 to 65535.
20.8.2 Parameters for Creating and Modifying Neighboring UMTS/ GSM Cell Analysis Tasks
This section describes the parameters for creating and modifying neighboring UMTS/GSM cell analysis tasks. You can refer to the description when creating and modifying a neighboring UMTS/GSM cell analysis task.
l l
l l
Choose UMTS/GSM Neighboring Cell Analysis Task from the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range:
l l
Issue 03 (2010-06-30)
20-21
Parameter Time information Data Time Scope
Description The start time must precede the end time. You can either enter the time value in this field, or click and select the date and time in the Date Selection dialog box. This parameter is valid for only one-time tasks. Task Start At Indicates the time when the analysis task is executed. The time specified in this field must not precede the end time specified in the Data Time Scope field.
Object information
RNC Cell Group
If you select this option, the navigation tree displays all the RNCs of the entire network. If you select this option, the navigation tree displays all the cell groups of the entire network. Indicates the threshold of the neighboring cell sequence number. All the undefined neighboring cells whose sequence numbers are smaller than or equal to the value of this parameter are regarded as missing neighboring cells. All the defined neighboring cells whose sequence numbers are larger than the value of this parameter are regarded as redundant neighboring cells. This parameter can be set to any integer from 3 to 32. The default value is 26.
Omni Gain
Indicates the omnidirectional gain of an antenna. This parameter can be set to any integer from 0 to 15. The default value is 11. Unit: dBi
Directive Gain
Indicates the directional gain of an antenna. This parameter can be set to any integer from 0 to 25. The default value is 17. Unit: dBi
Score of Neighboring cells ranking No.1 to 8
Indicates the scores of the neighboring cell ranking No.1 to 8. This parameter can be set to any integer from 0 to 100. In addition, the neighboring cell with a small sequence number must obtain a higher score than that of the neighboring cell with a large sequence number.
20-22
Issue 03 (2010-06-30)
Parameter Display Number of Undefined Neighboring Cells
Description Indicates that only the TopN undefined neighboring cells are displayed. N can be any integer from 20 to 50. The default value is 30.
20.8.3 Parameters for Querying the Analysis Reports of Neighboring UMTS/GSM Cells
This section describes the parameters for querying the analysis reports of neighboring UMTS/ GSM cells. You can refer to the description when querying the analysis reports of neighboring UMTS/GSM cells.
Description of Parameters About a Test Cell

Parameter RNC ID Cell ID Cell Name P-SC ARFCN_DL Number of MRs Number of Redundant Neighboring Cells Number of Missing Neighboring Cells Number of Configured Neighboring GSM Cells Service Type of Test Cell Description Indicates the ID of the RNC that the dominant cell belongs to. Indicates the number of a dominant cell. Indicates the name of a dominant cell, for example, Cell_1. Indicates the primary scrambling code of a dominant cell. Indicates the downlink ARFCNs of a dominant cell. Indicates the total number of MRs received by each dominant cell. Indicates the number of redundant neighboring GSM cells of the current dominant cell. Indicates the number of missing neighboring GSM cells of the current dominant cell. Indicates the number of defined neighboring GSM cells of the dominant cell.
Indicates the service type of the current dominant cell, such as indoor site and outdoor site. Learning the service type of the dominant cell prevents important neighboring cells from being mistakenly deleted.
Issue 03 (2010-06-30)
20-23
Description of Parameters About the Neighboring GSM Cells

Parameter GSM Neighboring Cell Name BSC LAC CI BCCH BSIC Suggested Operation Description Indicates the name of a defined or undefined neighboring GSM cell of the current dominant cell. Indicates the name of the BSC that a neighboring GSM cell belongs to. Indicates the location area code of a neighboring GSM cell. Indicates the cell identity of a neighboring GSM cell. Indicates the broadcast control channel of a neighboring GSM cell. Indicates the base station identity code of a neighboring GSM cell. Indicates the operation suggestions that the Nastar provides. The options are Missing Neighboring Cell, Redundant Neighboring Cell, or N/A. User Modify Indicates whether the user operations are recommended. If this option is selected, you are advised to perform modification according to Suggested Operation. Otherwise, no user operation is recommended. Total Score Final Priority Suggested Priority Indicates the total score of each neighboring cell based on the measurement result according to the neighboring cell algorithm. Indicates the final sequence of priorities adjusted on the basis of suggested priority. Indicates the suggested priority provided on the basis of total score of neighboring cells. The higher the total score is, the higher the suggested priority is. Indicates the average receive signal strength of a neighboring GSM cell. Indicates the number of MRs of the current neighboring GSM cell.
Average Receive Signal Strength (dBm) Number of Measurement Reports Distance (km) Service Type of Neighboring Cell
Indicates the distance from the current dominant cell to a neighboring GSM cell. Indicates the service type of a neighboring GSM cell, such as indoor site and outdoor site. Learning the service type of the neighboring GSM cell prevents important neighboring cells from being mistakenly deleted. Indicates the number of times a cell ranking No.1 in the neighboring cell list.
Number of Times A Neighboring Cell Ranking No.1 in MRs
20-24
Issue 03 (2010-06-30)
Parameter Number of Times A Neighboring Cell Ranking No.2 in MRs Number of Times A Neighboring Cell Ranking No.3 in MRs Number of Times A Neighboring Cell Ranking No.4 in MRs Number of Times A Neighboring Cell Ranking No.5 in MRs Number of Times A Neighboring Cell Ranking No.6 in MRs Number of Times A Neighboring Cell Ranking No.7 in MRs Number of Times A Neighboring Cell Ranking No.8 in MRs Measurement Probability
Description Indicates the number of times a cell ranking No.2 in the neighboring cell list.
Indicates the number of times a cell ranking No.3 in the neighboring cell list.
Indicates the ratio of the number of undefined neighboring GSM cell measurements to the number of defined neighboring GSM cell measurements.
20.8.4 Parameters for Querying the Analysis Reports of Possible Neighboring UMTS/GSM Cells
This section describes the parameters for querying the analysis reports of possible neighboring UMTS/GSM cells. You can refer to the description when querying the analysis reports of possible neighboring UMTS/GSM cells.
Issue 03 (2010-06-30)
20-25

Parameter RNC ID Cell ID Cell Name ARFCN_DL P-SC Neighboring Cell BCCH Neighboring Cell BSIC BSC ID of the Selected Possible Neighboring Cell Possible Neighboring Cell Name Neighboring Cell CGI Neighboring Distance Angle form Neighboring Cell Direction Predicted DL Signal Strength Get from config data Neghboring Cell Loop Number Description Indicates the ID of the RNC that the dominant cell belongs to. Indicates the number of a dominant cell. Indicates the name of a dominant cell, for example, Cell_1. Indicates the downlink ARFCNs of a dominant cell. Indicates the primary scrambling code of a dominant cell. Indicates the broadcast control channel of a neighboring GSM cell. Indicates the base station identity code of a neighboring GSM cell. Indicates the name of the BSC that the selected possible neighboring GSM cell belongs to. Indicates the name of the selected possible neighboring GSM cell.
Indicates the global ID of the selected possible neighboring GSM cell. Indicates the distance from the dominant cell to the selected possible neighboring GSM cell. Indicates the relative angle between the selected possible neighboring GSM cell and the dominant cell. Indicates the signal strength of the selected possible neighboring GSM cell based on the dimensioning. Indicates whether the selected possible neighboring GSM cell is obtained from the configuration data. Indicates the number of laps between the selected possible neighboring GSM cell and the dominant cell, that is, the number of cells between the selected possible neighboring GSM cell and the dominant cell. Indicates the number of possible neighboring cells in the possible neighboring GSM cell pair.
Number of Possible Neighboring Cells in the Possible Neighboring Cell Pairs Number of Measurement Reports
20-26
Indicates the number of MRs of the current neighboring GSM cell.
Issue 03 (2010-06-30)
Parameter Total Score
Description Indicates the total score of each neighboring cell based on the measurement result according to the neighboring cell algorithm.
Issue 03 (2010-06-30)
20-27

Parameter Whether to Use Description Indicates whether to select the current possible neighboring UMTS cell 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 neighboring UMTS cell of the test cell. In addition, you need to replace the information about the selected possible neighboring cell in the possible neighboring cell confirmation table with the corresponding information in the possible neighboring cell overview table.
Name of Possible Neighboring Cell replaces Neghboring Cell Name Possible Neighboring Cell BSC Name replaces Neghboring BSC LAC replaces Neighboring Cell LAC CI replaces Neighboring Cell CI Distance of Possible Neighboring Cell(m) replaces Neighboring Distance Relative Angle of Neighboring Cell() replaces Angle form Neighboring Cell Direction Predicted Signal Strength of Neighboring Cell(dBm) replaces Predicted DL Signal Strength Obtain From Configuration Data replaces Get from config data Number of Possible Neighboring Cell Laps replaces Neghboring Cell Loop Number

Neghboring Cell Name Neghboring BSC Neighboring Cell LAC Neighboring Cell CI Neighboring Distance Angle form Neighboring Cell Direction Predicted DL Signal Strength Get from config data Neghboring Cell Loop Number
Name of Possible Neighboring Cell
Indicates the name of a possible neighboring GSM cell.
20-28
Issue 03 (2010-06-30)
Parameter Possible Neighboring Cell BSC Name LAC CI Distance of Possible Neighboring Cell(m) Relative Angle of Neighboring Cell() Predicted Signal Strength of Neighboring Cell (dBm) Obtain From Configuration Data Number of Possible Neighboring Cell Laps
Description Indicates the name of the BSC that a possible neighboring GSM cell belongs to. Indicates the location area code of a possible neighboring GSM cell. Indicates the cell identity of a possible neighboring GSM cell. Indicates the distance from the dominant cell to a possible neighboring GSM cell. Indicates the relative angle between the dominant cell and a possible neighboring GSM cell. Indicates the signal strength of a possible neighboring GSM cell based on the dimensioning.
Indicates whether the possible neighboring GSM cell is obtained from the configuration data. Indicates the number of laps between the dominant cell and a possible neighboring GSM cell, that is, the number of cells between the dominant cell and a possible neighboring GSM cell.
Issue 03 (2010-06-30)
20-29
21 UMTS Coverage Analysis
21
About This Chapter
UMTS Coverage Analysis
UMTS coverage analysis involves managing UMTS coverage analysis tasks, querying UMTS coverage analysis reports, and exporting UMTS coverage analysis reports. The Nastar analyzes the MRs sent by a UE and directly displays the information about coverage status, signal quality, and user distribution of the measurement cell through the GUI. It helps you to quickly locate the problems such as weak cell coverage, cross coverage, and poor QoS on the radio network. 21.1 Basic Knowledge of UMTS Coverage Analysis The UMTS coverage analysis function enables you to analyze the MR sent by a UE. The analysis results help you to check the coverage status of the measurement cell on the network and determine whether problems such as weak cell coverage, cross coverage, and poor QoS occur on the network. 21.2 Process of UMTS Coverage Analysis This section describes the process of UMTS coverage analysis. 21.3 Managing a UMTS Coverage Analysis Task This section describes how to manage UMTS coverage analysis tasks. You can create, modify, delete, suspend, and resume a UMTS coverage analysis task. You can also view the status and execution progress of such a task. 21.4 Querying a UMTS Coverage Analysis Report This section describes how to query a UTMS coverage analysis report. You can query the MRs sent by a UE in a time segment. The query results help you to check the coverage status of the measurement cell on the network and determine whether problems such as weak cell coverage, cross coverage, and poor QoS occur on the network. 21.5 Exporting a UMTS Coverage Analysis Report This section describes how to export a UMTS coverage analysis report. After querying coverage analysis results, you can export the found analysis results as .csv files. Based on the exported analysis results, you can determine the coverage of the measurement cells on the network. 21.6 Reference for the UMTS Coverage Analysis GUI This section describes the interface for UMTS coverage analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS coverage analysis.
21.1 Basic Knowledge of UMTS Coverage Analysis

The UMTS coverage analysis function enables you to analyze the MR sent by a UE. The analysis results help you to check the coverage status of the measurement cell on the network and determine whether problems such as weak cell coverage, cross coverage, and poor QoS occur on the network. The MR sent by an UE consists of downlink RSCP and Ec/No, and the TP when the UE is connected. After you specify the conditions for coverage analysis, the Nastar analyzes the coverage of the selected cell and then displays the analysis results in a two-dimensional chart, a threedimensional chart, and a table.
l
The two-dimensional chart displays the AMR, VP, BE, AMR+BE, and OTHER services. For each service, three counters, namely, RSCP_DL, Ec/No_DL, and TP counters. The three-dimensional chart displays the PS and CS services. For each service, three counters, namely, RSCP_DL, Ec/No_DL, and TP, are involved. The summary table displays the statistics on the counters that correspond to the services in the two-dimensional chart.
The analysis results can be exported as a .csv file. You can optimize the cell coverage based on the analysis results.
21.2 Process of UMTS Coverage Analysis

This section describes the process of UMTS coverage analysis. Figure 21-1 shows the general process of coverage analysis.
21-2
Issue 03 (2010-06-30)
Figure 21-1 Workflow of coverage analysis

Start
Set an E2E task
Set a coverage analysis task
Query a coverage analysis report
Export a coverage analysis report
End
Table 21-1 describes the items listed in Figure 21-1. Table 21-1 Description of the workflow of coverage analysis No. 1 Procedure Querying NE data information Create an endto-end task corresponding to a coverage analysis task Description In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the coverage analysis is imported to the database. You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a coverage analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a coverage analysis data importing task. After the task is created, the Nastar periodically imports the coverage analysis data files saved on the Nastar server to the database.
Create a coverage analysis data importing task
Issue 03 (2010-06-30)
21-3
No. 4
Procedure Create a coverage analysis task
Description You can create a coverage analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required measurement data and configuration data from the Nastar database, and then generates an analysis report through the analysis. You can view the analysis results of the coverage analysis task that is successfully performed, learn about the coverage of the selected measurement cell on the network, and determine whether the problems such as weak coverage, cross coverage, and poor QoS on the existing network. You can export a coverage analysis report from the Nastar.
Query coverage analysis reports
Export coverage analysis reports
21.3 Managing a UMTS Coverage Analysis Task

This section describes how to manage UMTS coverage analysis tasks. You can create, modify, delete, suspend, and resume a UMTS coverage analysis task. You can also view the status and execution progress of such a task. 21.3.1 Creating UMTS E2E Tasks This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 21.3.2 Creating a UMTS Coverage Analysis Task This section describes how to create a UMTS coverage analysis task. By creating UMTS coverage analysis tasks, you can enable the Nastar to periodically analyze the MRs sent by a UE. Based on the analysis results, you can learn about the coverage status of the measurement cell on the network and determine whether problems such as weak cell coverage, cross coverage, and poor QoS occur on the network. 21.3.3 Modifying a UMTS Coverage Analysis Task This section describes how to modify the attributes of a UMTS coverage analysis task. You can modify the attributes of a UMTS coverage analysis task as required. 21.3.4 Checking a UMTS Coverage Analysis Task This section describes how to check a UMTS coverage analysis task. You can check the attributes of the UMTS coverage analysis task, execution progress of the task, and the execution results.

Prerequisite
l l l
Context
TIP
Procedure
Step 4 Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.
You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. Step 5 Optional: Click Next and then set the exception value for each KPI in the exception value setting list. You need to perform this step only when a UMTS cell performance analysis task is created. Step 6 Click Complete. The MML Preview dialog box is displayed, showing the MML commands related to the current theme analysis E2E task. The MML commands can be exported for future use. Step 7 Click OK. The added E2E task is displayed in the task list. ----End
Postrequisite
NOTE
21.3.2 Creating a UMTS Coverage Analysis Task

This section describes how to create a UMTS coverage analysis task. By creating UMTS coverage analysis tasks, you can enable the Nastar to periodically analyze the MRs sent by a UE. Based on the analysis results, you can learn about the coverage status of the measurement cell on the network and determine whether problems such as weak cell coverage, cross coverage, and poor QoS occur on the network.
Prerequisite
l l
21-6
Context
l l
Procedure
Step 1 Click in the Analysis Task Management window. The Analysis Task Management-New Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can be only Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects in the object navigation tree on the NE Object Selection tab page.
l
Choose RNC or Cell Group above the navigation tree to display the objects in the navigation tree as required. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to define the search range.
Step 7 On the Parameter Setting tab page, set filtering conditions. By default, the system provides 12 filtering conditions. You can add or modify filtering conditions.
l
Adding a filtering condition Select a counter under a type of service. Set the formula related to the filtering condition, and then click Add. The two-dimensional chart supports the setting of the formula with either one counter or two counters. The three-dimensional chart supports the setting of the formula with only two counters.
Modifying a filtering condition In the area of the filtering conditions, select the target formula, and then modify the formula in the condition setting area. Then, click Apply.
Deleting a filtering condition In the area of the filtering conditions, select a target formula, and then click Delete.
Modifying or deleting the filtering condition of a task whose Status is Running or Complete is not allowed. Step 8 Click Complete. ----End
Postrequisite
l
Deleting a task You can delete a coverage analysis task that is not required so that you can save system resources.
NOTE
The tasks that are in the Running status cannot be deleted.
1.
Choose UMTS Coverage Analysis Task from the navigation tree in theAnalysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task To delay the task execution, you can suspend a coverage analysis task that is in the idle state. After this operation, the coverage analysis task is in the suspended state.
NOTE
The system can schedule only the coverage analysis tasks that are not suspended.
1.
2.
. button is
Resuming a task You can resume a suspended coverage analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the coverage analysis tasks that are in the idle state can be scheduled by the system.
1.
2.
21.3.3 Modifying a UMTS Coverage Analysis Task

This section describes how to modify the attributes of a UMTS coverage analysis task. You can modify the attributes of a UMTS coverage analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS coverage analysis task is created.
Context
Procedure
Step 1 Choose UMTS Coverage Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the relevant parameters, see 21.6.3 Parameters for Creating and Modifying UMTS Coverage Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the object navigation tree, and the filtering conditions of the analysis task.
21.3.4 Checking a UMTS Coverage Analysis Task

This section describes how to check a UMTS coverage analysis task. You can check the attributes of the UMTS coverage analysis task, execution progress of the task, and the execution results.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS coverage analysis task is created.
Procedure
Step 1 Choose UMTS Coverage Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required:
Issue 03 (2010-06-30)
21-9
Purpose Checking the attributes of a coverage analysis task
Operation Select a task from the task list in the upper-right pane. Double-click the task or click .
You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 21.3.3 Modifying a UMTS Coverage Analysis Task. Checking the execution progress of the active task Select a task from the task list in the upper-right pane. Then, you can view the execution progress of the task in the Progress column. Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view all the analysis results of the selected task in the lower-right pane.
----End
Postrequisite
l
21.4 Querying a UMTS Coverage Analysis Report

This section describes how to query a UTMS coverage analysis report. You can query the MRs sent by a UE in a time segment. The query results help you to check the coverage status of the
measurement cell on the network and determine whether problems such as weak cell coverage, cross coverage, and poor QoS occur on the network.
Prerequisite
Procedure
Step 1 Choose UMTS Coverage Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose Coverage Analysis from the shortcut menu. The UMTS Coverage Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell under RNC Overview Report or Cell Group Overview Report from the list on the left pane. View the two-dimensional chart, three-dimensional chart, and summary table on the right pane.
l
In the two-dimensional chart, the information about the AMR, VP, BE, AMR+BE, and Other services is displayed on five tab pages, respectively. Each tab page displays the RSCP, ECNO, and TP counters of the corresponding service in a column chart and a counter accumulation distribution line chart. The two-dimensional chart contains two vertical axes and one horizontal axis. The horizontal axis represents the value of each counter. The left vertical axis represents the percentage of the number of MRs of each counter to the total number of MRs. The right vertical axis represents the value in the line chart. The value of any counter on the horizontal axis is taken as the benchmark. The values (indicating the sum of the MR percentage of each counter) that are equal to or smaller than the benchmark value are displayed on the right vertical axis.
In the three-dimensional chart, each two of the three counters (RSCP, ECNO, and TP) are grouped for the PS and CS services. Therefore, you can find six tabs in the chart. The distribution of different counters is identified in different colors. After you type the value ranges of the counters corresponding to the horizontal and vertical axes in the formula area, the system automatically calculates the sum of the density of the counter distribution in this overlapped area.
The summary table displays the statistics on the counters that correspond to the services in the two-dimensional chart.
----End
Postrequisite
l
Issue 03 (2010-06-30)
21.5 Exporting a UMTS Coverage Analysis Report

This section describes how to export a UMTS coverage analysis report. After querying coverage analysis results, you can export the found analysis results as .csv files. Based on the exported analysis results, you can determine the coverage of the measurement cells on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried UMTS coverage analysis reports.
Context
Exporting the overview information about coverage analysis refers to exporting the general information about all the measurement cells involved in the selected analysis task.
Procedure
Step 1 Click in the UMTS Coverage Analysis window. The Save dialog box is displayed.
Step 2 Set the save path, and then click Save. The saved .csv file is opened automatically so that you can view the information in it. The information in the .csv file consists of the coverage information about a measurement cell. ----End
21-12
Issue 03 (2010-06-30)
21.6 Reference for the UMTS Coverage Analysis GUI

This section describes the interface for UMTS coverage analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS coverage analysis. 21.6.1 Interface for UMTS Coverage Analysis This section describes the interface for UMTS coverage analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 21.6.2 Parameters for Creating UMTS E2E Tasks This section describes the parameters for creating UMTS E2E tasks. You can refer to the description when creating a UMTS E2E task. 21.6.3 Parameters for Creating and Modifying UMTS Coverage Analysis Tasks This section describes the parameters for creating and modifying UMTS coverage analysis tasks. You can refer to the description when creating or modifying a UMTS coverage analysis task. 21.6.4 Parameters for Querying UMTS Coverage Analysis Reports This section describes the parameters for checking UMTS coverage analysis reports. You can refer to the description when querying a UMTS coverage analysis report.
21.6.1 Interface for UMTS Coverage Analysis

This section describes the interface for UMTS coverage analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. The analysis results of coverage analysis can be displayed in a two-dimensional chart, a threedimensional chart, and a summary table, as shown in Figure 21-2, Figure 21-3 and Figure 21-4. Figure 21-2 Interface for the coverage analysis (1)
Issue 03 (2010-06-30)
21-13
Description The buttons used for exporting the general information about all the measurement cells. You can precisely locate a cell object through the navigation tree. You can precisely locate a cell object through the search condition. The system filters counters according to the filtering formula that is set during the creation of analysis tasks and then displays the result counters.
(2)
Cell object navigation tree
(3)
Search panel
(4)
Filtering condition area
(5)
Two-dimensional chart area The information about the AMR, VP, BE, AMR+BE, and Other services is displayed on five tab pages, respectively. Each tab page displays the RSCP, ECNO, and TP counters of the corresponding service in a column chart and a counter accumulation distribution line chart.
Figure 21-3 Interface for the coverage analysis (2)
21-14
Issue 03 (2010-06-30)
No. Name (6)
Description
Three-dimensional chart area In the three-dimensional chart, each two of the three counters (RSCP, ECNO, and TP) are grouped for the PS and CS services. Therefore, you can find six tabs in the chart. Formula area After you type the values of the counters corresponding to the horizontal and vertical axes in area (6), the system automatically calculates the sum of the density of the counter distribution in this overlapped area.
(7)
Figure 21-4 Interface for the coverage analysis (3)
No. Name (8)
Description
Summary table area The summary table displays the statistics on the counters that correspond to the services in the two-dimensional chart.

Start Time

21-16
Issue 03 (2010-06-30)
21.6.3 Parameters for Creating and Modifying UMTS Coverage Analysis Tasks
This section describes the parameters for creating and modifying UMTS coverage analysis tasks. You can refer to the description when creating or modifying a UMTS coverage analysis task.
Parameter Basic Information Task Name Description Indicates the name of a coverage analysis task. Value range:
l l
l l
Choose UMTS Coverage Analysis Task from the navigation tree. Such a task can be executed only once in a time segment. Indicates the description of the task. Value range:
l l
Time Information
Data Time Scope
Task Start At
Indicates the time when the analysis task is executed. The time specified in this field should not precede the end time specified in the Data Time Scope field.
Object Information
RNC Cell Group
Issue 03 (2010-06-30)
21-17
21.6.4 Parameters for Querying UMTS Coverage Analysis Reports

This section describes the parameters for checking UMTS coverage analysis reports. You can refer to the description when querying a UMTS coverage analysis report.
Parameter Service Type Description Indicates the type of service. The coverage analysis involves the following types of services: AMR, VP, BE, AMR+BE, and OTHER. Indicates the total number of TP MRs of the selected cell, which is calculated based on the service type. Indicates the total number of RSCP MRs of the selected cell, which is calculated based on the service type. Indicates the total number of Ec/No MRs of the selected cell, which is calculated based on the service type. Indicates the average TP of the selected cell in the selected time segment, which is calculated based on the service type. Indicates the average RSCP of the selected cell in the selected time segment, which is calculated based on the service type. Indicates the average Ec/No of the selected cell in the selected time segment, which is calculated based on the service type.
Total Number of TP Measurement Reports Total Number of RSCP Measurement Reports Total Number of ECNO Measurement Reports Average TP Average RSCP(dBm) Average ECNO(dB)
21-18
Issue 03 (2010-06-30)
22 UMTS VIP Analysis
22
About This Chapter
UMTS VIP Analysis
This section describes the UMTS VIP analysis, including the management of VIP analysis tasks and the query and export of VIP analysis reports. By monitoring the KPIs related to the QoS of the VIP subscribers, the Nastar enables you to identify and solve the network problems that may cause VIP subscriber complaints. This helps provide good services to VIP subscribers and improve satisfaction of VIP subscribers. 22.1 Basic Knowledge of UMTS VIP Analysis The UMTS VIP analysis function enables you to routinely monitor the calls of the selected VIP subscribers on the network. Analyzing monitoring reports helps you learn the quality of service (QoS) of VIP subscribers. In addition, it helps network engineers actively analyze and locate possible network problems of VIP subscribers in advance, thus improving the satisfaction of VIP subscribers. 22.2 UMTS VIP Analysis Process This section describes the UMTS VIP analysis process. 22.3 Managing UMTS VIP Analysis Tasks This section describes how to manage UMTS VIP analysis tasks. You can create, modify, delete, suspend, or restore UMTS VIP analysis tasks. You can also view the status and execution progress of such tasks. 22.4 Querying UMTS VIP Analysis Reports This section describes how to query UMTS VIP analysis reports. By monitoring the number of service call reports, traffic, and KPIs of the selected VIP subscriber, you can learn about the service quality of the VIP subscriber and identify and solve the network problems that may cause VIP subscriber complaints. 22.5 Exporting UMTS VIP Analysis Reports This section describes how to export UMTS VIP analysis reports. You can export the queried VIP analysis results as .csv or .xls files as required. The exported VIP analysis results help you identify and solve the network problems that may cause VIP subscriber complaints. 22.6 Reference to the UMTS VIP Analysis Interface This section describes the interface for UMTS VIP analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS VIP analysis.
22.1 Basic Knowledge of UMTS VIP Analysis

The UMTS VIP analysis function enables you to routinely monitor the calls of the selected VIP subscribers on the network. Analyzing monitoring reports helps you learn the quality of service (QoS) of VIP subscribers. In addition, it helps network engineers actively analyze and locate possible network problems of VIP subscribers in advance, thus improving the satisfaction of VIP subscribers.
VIP Analysis
The Nastar obtains the information about IMSIs reported by UEs during calls and finally helps to solve the problems related to the subscriber-level network optimization through the aggregation and analysis of KPIs (including network-level KPIs, service-level KPIs in CS and PS domains, and KPIs of active cells) based on the VIP group level and VIP subscriber level.
l
The aggregation and analysis of KPIs based on the VIP group level help network engineers efficiently and timely monitor the service usage of subscribers from important groups in a centralized manner. This effectively improves the operation efficiency and reduces the operation expenditure. In addition, this function helps operators identify problem VIP groups and the corresponding VIP subscribers in time, thus enabling operators to actively analyze and solve problems in advance to prevent losing important customer groups. The aggregation and analysis of KPIs based on the VIP subscriber level provide a detailed analysis of KPI trends related to subscriber experience and behavior. For example, analysis of variation trends based on voice service setup delay, analysis of variation trends based on SQI distribution of voice service quality, analysis of variation trends based on data service average rate, analysis of variation trends based on uplink BLER distribution of data services, and analysis of variation trends based on service duration. The trend analysis based on different types helps network engineers quickly identify the worst and best QoS of VIP subscribers and QoS variation trends during a certain period and learn the relation between network problems and time.
In addition, the Nastar supports in-depth analysis for the important VIP subscribers whose raw data is collected in advance. When the KPIs of important VIP subscribers of a group deteriorate, but the network engineers cannot recur and locate the problem at the site, the Nastar helps to extract the detailed call records of these VIP subscribers within the specified period. By analyzing these reports, the network engineers quickly locate the key call report that results in the deterioration of KPIs, and then analyzes the information such as the network quality and signaling procedure before the link release and abnormal causes, thus locating problems. The aggregation and analysis of KPIs of active cells based on VIP groups and VIP subscribers help network engineers learn the main active areas of VIP subscribers on the network. Based on the network problems that occur in these active areas, the network engineers can quickly identify the key cells that need to be preferentially treated to solve these network problems. Thus, they can timely solve the problem of the deterioration of QoS of VIP subscribers caused by network problems. Used with the GIS, this function enables the Nastar to display active cells in geographic mode, thus improving the efficiency of problem analysis and location.
Limitation
The UMTS VIP analysis function allows the NEs to report raw call data of important VIP subscribers to the Nastar. The amount of raw data is huge. Therefore, limitation is required to prevent the system from becoming overloaded in the case of concurrent operations by a large
number of users. In such a case, for the analysis function based on the VIP group level, the Nastar supports the analysis of 100,000 subscribers (that is, the maximum number of subscribers in all the VIP groups that are selected for the analysis cannot exceed 100,000); for the analysis function based on the VIP subscriber level, the Nastar supports the analysis of 2,000 subscribers (that is, the maximum number of subscribers in all the VIP groups that are allowed to report data sources cannot exceed 2,000). In addition, the analysis function of KPIs in active cells of UMTS VIP subscribers requires the display of geographic distribution of active cells. To ensure the display effect, you need to import correct engineering parameters.
22.2 UMTS VIP Analysis Process

This section describes the UMTS VIP analysis process. Figure 22-1 shows the general process of UMTS VIP analysis.
Issue 03 (2010-06-30)
22-3
Figure 22-1 Process of UMTS VIP analysis
22-4
Issue 03 (2010-06-30)
Table 22-1 Process of UMTS VIP analysis No. 1 Procedure Managing VIP groups Item In the Analysis Task Management window on the Nastar client, you can enter the VIP group management window to create the VIP groups and relevant subscribers required for the VIP analysis. After the creation, the VIP analysis function provides options based on the information about the created VIP subscribers or VIP groups. Thus, you can create an analysis task for a specified VIP subscriber. In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the VIP analysis is imported to the database. On the Nastar client, choose Maintenance > E2E Task Management. In the displayed E2E Task Management window, you can create an E2E task of VIP analysis. After the task is created, the Nastar issues MML commands to the M2000, and then the M2000 issues MML commands to NEs. Finally, the NEs execute the measurement task and generate results. After an E2E task is created, in the Task Management window, you can view the corresponding collection task that has been created by the system. You can perform a data import task only after the corresponding collection task is complete. On the Nastar client, choose Maintenance > Task Management. In the displayed Task Management window, you can create a data import task corresponding to the VIP analysis task so that the Nastar periodically imports the VIP analysis data saved as files on the Nastar server to the database. In the Analysis Task Management window on the Nastar client, you can create VIP analysis tasks. After obtaining the related analysis data from the database, the Nastar analyzes data and then outputs the analysis result. You can view the analysis results of the VIP analysis tasks that are executed successfully and also perform comprehensive analysis together with maps. In addition, you can export the result files through the one-key method in the analysis result query interface. 7 Exporting VIP analysis reports You can export analysis result files in the Nastar performance analysis system.
Querying NE data information Creating an E2E task for VIP analysis
Creating a task for importing VIP analysis data Creating a VIP analysis task
Querying VIP analysis reports
22.3 Managing UMTS VIP Analysis Tasks

This section describes how to manage UMTS VIP analysis tasks. You can create, modify, delete, suspend, or restore UMTS VIP analysis tasks. You can also view the status and execution progress of such tasks.
Issue 03 (2010-06-30)
22-5
22.3.1 Managing UMTS VIP Groups This section describes how to manage the UMTS VIP groups. You can create VIP groups as required and add certain VIP subscribers to a VIP group to monitor the service quality of these VIP subscribers simultaneously. In addition, you can modify the attributes of a VIP group, delete, or export a VIP group. 22.3.2 Creating UMTS E2E Tasks This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 22.3.3 Creating UMTS VIP Analysis Tasks This section describes how to create UMTS VIP analysis tasks. In a UMTS VIP analysis task, the Nastar obtains the IMSI reported by the mobile subscriber through the communications device, and then performs aggregation and analysis for the service call report quantity, traffic, and KPIs on the basis of VIP subscribers or VIP groups. This helps solve the subscriber level network optimization problem, thus providing better services for VIP subscribers and improving VIP subscriber satisfaction. 22.3.4 Modifying UMTS VIP Analysis Tasks This section describes how to modify the attributes of the UMTS VIP analysis tasks. You can modify the attributes of the UMTS VIP analysis tasks as required. 22.3.5 Checking UMTS VIP Analysis Tasks This section describes how to check UMTS VIP analysis tasks. You can check the attributes, execution progress, and execution results of a UMTS VIP analysis task as required.
22.3.1 Managing UMTS VIP Groups

This section describes how to manage the UMTS VIP groups. You can create VIP groups as required and add certain VIP subscribers to a VIP group to monitor the service quality of these VIP subscribers simultaneously. In addition, you can modify the attributes of a VIP group, delete, or export a VIP group.
Context
IMSI refers to the international mobile subscriber identity. The IMSI is a 15-digit string formed by numerals 0 to 9. The structure of the IMSI from the left to the right is MCC+MNC+MSIN. The MNC and the MSIN forms the NMSI. Where:
l l
MCC refers to the mobile country code of a mobile subscriber. MNC refers to the mobile network code, namely, the PLMN code of a mobile subscriber. PLMN refers to the public land mobile network. MSIN refers to the mobile subscriber identification number. NMSI refers to the national mobile subscriber identification. This identification can uniquely identify an MS in a country.
l l
The VIP group file to be imported must include the following fields: Group name, Priority, and Description, as shown in Table 22-2. The match sequence of columns is restricted and automatic matching of columns is not supported.
22-6
Issue 03 (2010-06-30)
Table 22-2 VIP group file Group Name Group 1 Group 2 Level High Low Description Second level director of ** Group Project manager of ** Group
The export of VIP group files in .csv and .xls formats are supported.
Procedure
Step 1 Choose Function List > System Function > VIP Group Management from the navigation tree in the Analysis Task Management window. The VIP Group Management dialog box is displayed. Step 2 Perform the following operations as required: If You Want to ... Create a VIP group by adding one Create a VIP group by importing one Step 3 To create a VIP group by adding one, do as follows: 1. 2. Click the UMTS VIP Group Name tab. Then, click New to open the VIP Group Management - Create VIP Group dialog box. Set Group Name, Priority, and Description. If the * character is present on the right of a parameter, it indicates that the setting of this parameter is mandatory. 3. Select one or multiple VIP subscribers from the Group Member list. You can add new VIP subscribers to this list as required or import VIP subscribers to this list, delete the existing VIP subscribers from the list, or export the VIP subscriber information in the list to .csv or .xls files.
l
Adding a VIP subscriber a. b. Click New below the Group Member list to open the VIP User Management dialog box. Set User Name, Phone Number, IMSI, and Description. If the * character is present on the right of a parameter, it indicates that the setting of this parameter is mandatory. c. Click Confirm. Click Import below the Group Member list to open the Open dialog box. Select an edited VIP subscriber file, and then click Open.
Issue 03 (2010-06-30)
If a VIP subscriber file in .xls format is selected and the file contains multiple worksheets, a prompt is displayed. In this case, select the worksheet to be imported. c. After the import is complete, perform the operations as prompted. The number of new records, the number of updated records, and the number of failed records are displayed.

Step 4 To create a VIP group by importing one, do as follows: 1. 2. Click Import on the UMTS VIP Group Name tab page to open the Open dialog box. Select an edited VIP group file, and then click Open. If a VIP group file in .xls format is selected and the file contains multiple worksheets, a prompt is displayed. In this case, select the worksheet to be imported.
NOTE
In a VIP group file, if Priority and Description of the same VIP group in different rows are different, the Nastar displays Priority and Description in the last row of the VIP group in the Priority and Description column on the UMTS VIP Group Name tab page. It is recommended that the description and priority information in different rows regarding a VIP group be the same when you define VIP group information. If the Priority column is empty, Medium is displayed by default.
3. 4.
Click Import. In the displayed Confirm dialog box, click OK after checking the number of added records, updated records, and failed records. , and indicate the VIP group that In the Import UMTS VIP Group dialog box, is successfully imported, partially imported, and failed to be imported respectively.
5.

l
are
If abnormal records exist in the imported information, VIP groups that are marked by are displayed. In this case, perform the following operations: Click Export Fail Record to export the failed records as a file so that you can make modifications based on the error information to complete the current import task.
22-8
Click Close to complete the current import task.
----End
Postrequisite
l
Modifying the attributes of a VIP group 1. Select a VIP group on the UMTS VIP Group Name tab page and then click Modified to open the UMTS VIP user group management Modify VIP user group dialog box. Modify the relevant parameters. For description of the parameters, see 22.6.2 Parameters for Creating and Modifying UMTS VIP Subscribers/VIP Groups. 3. Click Confirm. If the VIP group is used by certain tasks, the modification does not affect the ongoing tasks. If the VIP group is used by a periodic task, the related information is updated in the next period after the modification.
2.
Viewing the information about members of a VIP group On the UMTS VIP Group Name tab page, double-click a VIP group to view the detailed information about the members of the VIP group.
Deleting a VIP group 1. 2. Select a VIP group on the UMTS VIP Group Name tab page, and then click Delete. In the displayed Confirm dialog box, click Confirm. If the VIP group is used by certain tasks, the modification does not affect the ongoing tasks. If the VIP group is used by a periodic task, the related information is updated in the next period after the modification.
Exporting the VIP group information to .csv or .xls files 1. 2. On the UMTS VIP Group Name tab page, click Export. Set a file name and specify the save path and file type in the displayed Save dialog box, and then click Save.
You can also select all VIP groups, and find or save a VIP group through the shortcut menu prompted by right-clicking on the UMTS VIP Group Name tab page.

Prerequisite
l l l
Issue 03 (2010-06-30)
Context
TIP
Procedure
Step 4 Click Next. Then, set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search. Step 5 Optional: Click Next and then set the exception value for each KPI in the exception value setting list.
You need to perform this step only when a UMTS cell performance analysis task is created. Step 6 Click Complete. The MML Preview dialog box is displayed, showing the MML commands related to the current theme analysis E2E task. The MML commands can be exported for future use. Step 7 Click OK. The added E2E task is displayed in the task list. ----End
Postrequisite
NOTE
22.3.3 Creating UMTS VIP Analysis Tasks

This section describes how to create UMTS VIP analysis tasks. In a UMTS VIP analysis task, the Nastar obtains the IMSI reported by the mobile subscriber through the communications device, and then performs aggregation and analysis for the service call report quantity, traffic, and KPIs on the basis of VIP subscribers or VIP groups. This helps solve the subscriber level network optimization problem, thus providing better services for VIP subscribers and improving VIP subscriber satisfaction.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the VIP analysis function. The E2E task, collection task, and data import task corresponding to the VIP analysis task are normal.
Issue 03 (2010-06-30)
The VIP analysis task can be created successfully even if the prerequisites are not met. The execution of the VIP analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l
A VIP analysis task can be performed once or periodically. The supported unit of the execution period of a periodical task is hour. A maximum of 50 tasks of this type can be created and the time range of the data in a task cannot exceed 7 days. Before you create an analysis task, check to ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, Execution Type, and Note. Step 3 Click Next. Step 4 Set Task Configuration and Time Setting for Cycle Task Data/Time Setting for Once Task Data. If Once Task is selected in the previous step, you need to set only Data Time Scope. Step 5 Click Next. Step 6 On the VIP Group Selection tab page, select one or multiple VIP groups and select Report Raw Data as required. If you select to report raw data, the original call record data is collected when the VIP KPI overview information is provided. Step 7 On the VIP KPI Threshold Setting tab page, set the threshold value of each KPI.
l
In the analysis report of the corresponding task, if the KPI value of a corresponding subscriber does not reach the threshold value, it is considered that this is a problem KPI or deteriorating KPI. The threshold values of the KPIs related to success rate can be set to any percentage from 0 to 100%. The threshold values of the KPIs related to delay can be set to any number that is greater than zero. To apply the modified threshold value to subsequent VIP analysis tasks, click App. To restore the modified threshold value to the initial value, click Default.
Postrequisite
l
22-12
Issue 03 (2010-06-30)

NOTE
1.
Click the UMTS VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Select a task from the task list in the upper-right pane, and then click In the displayed Confirm dialog box, click Confirm.
Suspending a task To delay the task execution, you can suspend a VIP analysis task that is in the idle state. Then, the VIP analysis task becomes a suspended task.
NOTE
The system can schedule only the VIP analysis tasks that are not suspended.
1.
2.
button.
l
Restoring a task You can restore a suspended VIP analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the VIP analysis tasks that are in the idle state can be scheduled by the system.
1.
2.
button.
22.3.4 Modifying UMTS VIP Analysis Tasks

This section describes how to modify the attributes of the UMTS VIP analysis tasks. You can modify the attributes of the UMTS VIP analysis tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the VIP analysis function. A UMTS VIP analysis task is created.
Issue 03 (2010-06-30)
Context
Procedure
Step 1 Click the UMTS VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 22.6.4 Parameters for Creating and Modifying UMTS VIP Analysis Tasks. For periodical tasks, you can modify the Note parameter in the basic information, the Begin Date, Cycle, Execution Times, and Time parameters in the time information, the VIP group information, and the VIP KPI information. For the tasks that can be performed only once, you can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the VIP group information, and the VIP KPI information.
22.3.5 Checking UMTS VIP Analysis Tasks

This section describes how to check UMTS VIP analysis tasks. You can check the attributes, execution progress, and execution results of a UMTS VIP analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS VIP analysis task is created.
Procedure
Step 1 Click the UMTS VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required:
22-14
Issue 03 (2010-06-30)
If You Want to ... Check the attributes of a UMTS VIP analysis task
Then ... Select a task from the task list in the upper-right pane. Double-click the task or click .
You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 22.3.4 Modifying UMTS VIP Analysis Tasks. Check the execution progress of the active Select a task from the task list in the upper-right task pane. Then, you can view the execution progress of the task in the Progress column. Check the task execution results Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
22.4 Querying UMTS VIP Analysis Reports

This section describes how to query UMTS VIP analysis reports. By monitoring the number of service call reports, traffic, and KPIs of the selected VIP subscriber, you can learn about the
service quality of the VIP subscriber and identify and solve the network problems that may cause VIP subscriber complaints.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the VIP analysis function. The E2E task, collection task, and data import task corresponding to the VIP analysis task are normal. The VIP analysis task is executed successfully.
Procedure
Step 1 Click the UMTS VIP Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. All the analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose UMTS VIP Analysis Task from the shortcut menu. The UMTS VIP Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select one VIP subscriber or VIP group from the VIP group overview table on the left of the UMTS VIP Analysis Task window, and then view the details of the KPIs of each service and the change trend of these KPIs on the Network Level KPI, CS Service KPI, PS Service KPI, and Active Cell tab pages on the right.
l
When a VIP group is selected as the analysis object, the KPI list area on the right does not display the change trend of the KPIs. Initially, Object above the VIP group overview table on the left is set to Group. After you change the value to User, information about Group is available for selection, namely, selection of the VIP group to be analyzed. In this case, the VIP group overview table displays the KPI overview information of all VIP subscribers in the specified group. In addition, the area below the KPI list on the right displays the change trend of a specific KPI of the selected VIP subscriber. You can double-click the change trend chart to zoom in on the chart, and then double-click the chart again to restore the chart to the original size.
The display options provided for different change trend charts are as follows:
In the change trend chart of a network level KPI, the options to display Business and NunBusiness are provided. In the change trend chart of a CS KPI, the options to display AMR service, VP service, and other services are provided. In the change trend chart of a PS KPI, the options to display PS service, HSDPA service, HSUPA service, and other services are provided.
Multiple KPI fields and services are involved in the change trend charts of AMR service quality distribution based on SQI, uplink BLER distribution, and RAB negotiated final rate
22-16
distribution. That is, 3 (1 x 3 = 3) curves are included in the AMR service quality distribution chart; 12 (2 x 6 = 12) curves are included in the uplink BLER distribution chart; and 2 (2 x 1 = 2) curves are included in the RAB negotiated final rate distribution chart.
l
Select one VIP group or VIP subscriber from the VIP group overview table on the left of the window, and then click the Active Cell tab on the right of the window to view the analysis result and geographical display result of the active cell corresponding to the selected VIP group or VIP subscriber. The description of the geographical display of the active cell corresponding to the VIP group or VIP subscriber is as follows:
If the geographical display is started for the first time, the analysis result list of the active cell does not contain any record, and all the active cells involved in the selected VIP group or VIP subscriber are highlighted on the map. You can switch between different KPIs through the shortcut menu prompted when rightclicking on the map. When you switch to a specific KPI, all active cells that serve the selected VIP group or VIP subscriber and contain the KPI are highlighted on the map. These active cells are rendered in different colors according to the number of times that VIP subscribers present in each active cell. With the increase in the number of times that VIP subscribers present in an active cell, the darkness of the rendering color increases. The rendering configuration can be modified as required.
In addition, the KPI values of a selected VIP group or VIP subscriber in an active cell can be displayed in labels next to the active cell on the map.
For description of the parameters, see 22.6.5 Parameters for Querying UMTS VIP Analysis Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 22.5 Exporting UMTS VIP Analysis Reports. If certain KPIs of a VIP subscriber are abnormal according to the query result and thus further analysis is required, select the basic information of the VIP subscriber and then choose Start Further Analysis from the shortcut menu to start the complaint analysis support function for further analysis. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
22.5 Exporting UMTS VIP Analysis Reports

This section describes how to export UMTS VIP analysis reports. You can export the queried VIP analysis results as .csv or .xls files as required. The exported VIP analysis results help you identify and solve the network problems that may cause VIP subscriber complaints.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the UMTS VIP analysis reports.
Procedure
Step 1 Click in the UMTS VIP Analysis Task window. The Save As dialog box is displayed.
22.6 Reference to the UMTS VIP Analysis Interface

This section describes the interface for UMTS VIP analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS VIP analysis. 22.6.1 Interface Description: UMTS VIP Analysis This section describes the interface for UMTS VIP analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 22.6.2 Parameters for Creating and Modifying UMTS VIP Subscribers/VIP Groups This section describes the parameters for creating and modifying UMTS VIP subscribers and VIP groups. You can refer to the description when creating and modifying a UMTS VIP subscriber and VIP group. 22.6.3 Parameters for Creating UMTS E2E Tasks This section describes the parameters for creating UMTS E2E tasks. You can refer to the description when creating a UMTS E2E task. 22.6.4 Parameters for Creating and Modifying UMTS VIP Analysis Tasks This section describes the parameters for creating and modifying UMTS VIP analysis tasks. You can refer to the description when creating and modifying a UMTS VIP analysis task. 22.6.5 Parameters for Querying UMTS VIP Analysis Reports This section describes the parameters for querying UMTS VIP analysis reports. You can refer to the description when querying a UMTS VIP analysis report.
22.6.1 Interface Description: UMTS VIP Analysis

This section describes the interface for UMTS VIP analysis. Before performing relevant operations, 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 22-2.
22-18
Issue 03 (2010-06-30)
Figure 22-2 VIP analysis interface
Description Provides the function of exporting the aggregation information about VIP groups. Displays the aggregation information about abnormal KPIs of all the VIP subscribers or VIP groups involved in the task in a table. Provides options for displaying the aggregation information about abnormal KPIs in Area (2) based on VIP subscribers or VIP groups.
l
(2)
VIP group overview table
(3)
Area for selecting object types
Aggregation based on VIP subscribers When you select this mode, the aggregation information about abnormal KPIs of all the VIP subscribers in a certain VIP group is displayed in Area (2).
Aggregation based on VIP groups When you select this mode, the aggregation information about abnormal KPIs of all the VIP subscribers in all VIP groups is displayed in Area (2).
Issue 03 (2010-06-30)
22-19
No. Name (4) Network-level KPI information table
Description Displays the network-level KPI values or aggregation values corresponding to the VIP subscribers or VIP groups selected in Area (2). Displays the variation trend of a certain KPI of a VIP subscriber selected in Area (2) when you select the aggregation of abnormal KPIs based on VIP subscribers in Area (3). Displays the service KPIs in CS domain, PS domain, and active cells of the VIP subscribers or VIP groups selected in Area (2) on three tab pages respectively.
(5)
Network-level KPI change chart
(6)
Service KPIs in CS domain/PS domain/ active cell information table
22.6.2 Parameters for Creating and Modifying UMTS VIP Subscribers/VIP Groups
This section describes the parameters for creating and modifying UMTS VIP subscribers and VIP groups. You can refer to the description when creating and modifying a UMTS VIP subscriber and VIP group.
Description of Parameters Related to VIP Subscribers

Parameter User Name Description Indicates the name of a VIP subscriber. Value range:
l l l l
A maximum of 128 characters Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' ` Not null Duplicated allowed (a VIP subscriber is allowed to use multiple SIM card) Case sensitive
Phone Number
Indicates the number of a UE used by a VIP subscriber. Value range:

l l
A combination of 0-digit to 20-digit numerals from 0 to 9 Duplicated allowed
22-20
Issue 03 (2010-06-30)
Parameter IMSI
Description Indicates the International Mobile Subscriber Identity (IMSI) of a VIP subscriber. Value range:
l l
A combination of 15-digit numerals from 0 to 9 Unique and not null
Description
Indicates the description of the VIP subscriber. Value range:

l l
Description of Parameters Related to VIP Groups

Parameter Group Name Description Indicates the name of a VIP group. Value range:
l l l l
Priority
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. Value range:

l l
Group Member
Indicates the information about members in the VIP group.

Issue 03 (2010-06-30)
22-21
Start Time

22-22
Issue 03 (2010-06-30)
22.6.4 Parameters for Creating and Modifying UMTS VIP Analysis Tasks
This section describes the parameters for creating and modifying UMTS VIP analysis tasks. You can refer to the description when creating and modifying a UMTS VIP analysis task.
Parameter Basic informati on Task Name Description Indicates the name of a VIP analysis task. Value range:
l l
A maximum of 60 characters Characters not allowed: ~ ! # $ % ^ * + = | \/,'` Unique and not null Case sensitive
l l
Task Type Task Execution Type
Choose UMTS VIP Analysis Task from the navigation tree.

l
Remarks
Provides the description of the task. Value range: a maximum of 200 characters
Time informati on
Periodic task
Begin Date
Indicates time for starting a task. The start time must be later than the current server time. You can either enter the time value in this field, or click and select the date and time in the Date Selection dialog box.
Task Start At
Indicates the time when the analysis task is executed. The time specified in this field must not precede the latest end time specified in the Time Setting for Cycle Task Data field.
Cycle
l l
Unit: hour Value range: 1 to 9999
Issue 03 (2010-06-30)
22-23
Description Indicates the number of times a periodic task is executed. If this parameter is set to 0, you can infer that the task is executed all the time. Value range: 0 to 9999. Default value: 0. Time Indicates the time range of the data to be analyzed.
l
One-Time Task
Data Time Scope
Task Start At
Object informati on
Option
If you select this option, the content in the Report Raw Data field corresponding to the VIP group can be selected. Indicates the name of a VIP group. Indicates the number of members in the VIP group. Indicates that the raw call data is also collected during the collection of the KPI aggregation information of all VIP objects of the selected VIP groups, thus helping to analyze problem thoroughly. Indicates the description of the VIP group.
Description
22-24
Issue 03 (2010-06-30)
Parameter Type
Description The service types involved in VIP analysis tasks are as follows: network-level KPI, AMR (CS domain), VP (CS domain), other (CS domain), PS (PS domain), HSDPA (PS domain), HSUPA (PS domain), and Other (PS domain). This field is read-only. KPI Name Indicates the name of a KPI. This field is read-only. KPI Threshold Value Indicates the threshold value of a KPI. In the analysis report of the task, if the KPI value of a corresponding user does not reach the threshold value, it is considered that this is a problem KPI or deteriorated KPI. This parameter can be null. That is, no threshold value is provided.
22.6.5 Parameters for Querying UMTS VIP Analysis Reports

This section describes the parameters for querying UMTS VIP analysis reports. You can refer to the description when querying a UMTS VIP analysis report.
Description of Parameters in the VIP Group Overview Table

Parameter Group Name (Number of Members)\User Name Description Indicates the name of the VIP group or VIP object. The number of members contained in the VIP group is added to the group name. You can select the group name or subscriber name from the dropdown list box to display the related information. Indicates the level of the VIP group or VIP object. Indicates the number of abnormal KPIs. Indicates international mobile subscriber identity of a VIP subscriber. Indicates the number of a UE used by a VIP subscriber.
Level Number of Abnormal KPIs IMSI MS Number
Issue 03 (2010-06-30)
22-25
Description of Parameters Related to Network-Level KPIs

Parameter Total Number of Reports RRC setup success rate (%) Number of RRC setup failures Average RRC access delay (s) SHO success rate (%) Number of SHO failures HHO success rate (%) Number of HHO failures Description Indicates the total number of MRs involved in the network-level KPIs. Indicates the success rate from subscriber access to RRC setup. RRC is an abbreviation for Radio Resource Control. Indicates the number of failures from the network access to the RRC setup. Indicates the average delay for RRC setup during the successful call initiation. Indicates the success rate of soft handovers (including softer handovers) during the successful service process. Indicates the number of soft handover failures during the successful service process. Indicates the success rate of hard handovers during the successful call process. Indicates the number of hard handovers during the successful call initiation.
Description of Parameters Related to KPIs in CS Domain

The CS domain contains the following types of services:
l l l
AMR (Adaptive Multi-Rate codec) VP (Virtual Path) Other Description Indicates the total number of MRs involved in the KPIs in CS domain. Indicates the success rate from the initiation of RAB request to the call setup. Indicates the success rate from the initiation of RAB request to the call completion. Indicates the call drop rate from the network access to the call initiation. Indicates the number of abnormal dropped calls from the network access to the call initiation. Indicates the success rate of RAB setups after the network access. RAB is an abbreviation for Radio Access Bearer.
Issue 03 (2010-06-30)
Parameter Total Number of Reports Call setup success rate (%) Call completion success rate (%) Call drop rate (%) Number of call drops RAB setup success rate (%)
22-26
Parameter Number of RAB setup failures Average RAB access delay (s) Average call connection delay (s) Average duration (s) Average ratio of Good SQI Average ratio of Accept SQI Average ratio of Bad SQI
Description Indicates the number of RAB setup failures after the network access. Indicates the average delay for RAB setup during the successful call initiation. Indicates the average delay for call connection during the successful call initiation. Indicates the average duration of a successful call initiation. Indicates the ratio of Good SQI of signal quality during a voice call. Indicates the ratio of Accept SQI of signal quality during a voice call. Indicates the ratio of Bad SQI of signal quality during a voice call.
Description of Parameters Related to KPIs in the PS Domain

The PS domain contains the following types of services:
l l l l
PS (Packet Switched) HSDPA (High Speed Downlink Packet Access) HSUPA (High Speed Uplink Packet Access) Other Description Indicates the total number of MRs involved in the KPIs in PS domain. Indicates the success rate from the initiation of RAB request to the call setup. Indicates the success rate from the initiation of RAB request to the call completion. Indicates the call drop rate from the network access to the call initiation. Indicates the number of abnormal dropped calls from the network access to the call initiation. Indicates the success rate of RAB setups after the network access. Indicates the number of RAB setup failures after the network access.
Parameter Total Number of Reports Call setup success rate (%) Call completion success rate (%) Call drop rate (%) Number of call drops RAB setup success rate (%) Number of RAB setup failures
Issue 03 (2010-06-30)
22-27
Parameter Average RAB access delay (s) Average call connection delay (s) Average duration (s) Ratio of level 1 UL BLER
Description Indicates the average delay for RAB setup during the successful call initiation. Indicates the average delay for call connection during the successful call initiation. Indicates the average duration of a successful call initiation. Indicates the proportion of the uplink BLER with the level of 1 during the successful call initiation. BLER is an abbreviation for Block Error Rate.
Ratio of level 2 UL BLER Ratio of level 3 UL BLER Ratio of level 4 UL BLER Ratio of level 5 UL BLER Ratio of level 6 UL BLER UL RAB average negotiated final rate DL RAB average negotiated final rate
Indicates the proportion of the uplink BLER with the level of 2 during the successful call initiation. Indicates the proportion of the uplink BLER with the level of 3 during the successful call initiation. Indicates the proportion of the uplink BLER with the level of 4 during the successful call initiation. Indicates the proportion of the uplink BLER with the level of 5 during the successful call initiation. Indicates the proportion of the uplink BLER with the level of 6 during the successful call initiation. Indicates the final negotiated rate of uplink RAB when a common PS service is initiated. Indicates the final negotiated rate of downlink RAB when a common PS service is initiated.
Description of Parameters of KPIs in Active Cells

Parameter RNC ID Cell ID Cell Name Number of signaling accesses Number of abnormal signaling accesses Number of signaling releases Description Indicates the ID of the RNC that the active cell belongs to. Indicates the number of an active cell. Indicates the name of an active cell. Indicates the number of signaling accesses of a VIP group or VIP object in an active cell. Indicates the number of abnormal signaling accesses of a VIP group or VIP object in an active cell. Indicates the number of signaling releases of a VIP group or VIP object in an active cell.
22-28
Issue 03 (2010-06-30)
Parameter Number of abnormal signaling releases Number of PS service accesses Number of CS service abnormal accesses Number of CS service best cell accesses Number of CS service exception best cell accesses
Description Indicates the number of abnormal signaling releases of a VIP group or VIP object in an active cell. Indicates the number of CS service accesses of a VIP group or VIP object in an active cell. Indicates the number of abnormal CS service accesses of a VIP group or VIP object in an active cell. Indicates the number of times that an active cell serves as the best cell before the CS service of a VIP group or VIP object is released. Indicates the number of times that an active cell serves as the best cell before the CS service of a VIP group or VIP object is abnormally released. Indicates the number of PS service accesses of a VIP group or VIP object in an active cell.
Number of PS service abnormal accesses Number of PS service best cell accesses Number of PS service exception best cell accesses
Indicates the number of abnormal PS service accesses of a VIP group or VIP object in an active cell. Indicates the number of times that an active cell serves as the best cell before the PS service of a VIP group or VIP object is released. Indicates the number of times that an active cell serves as the best cell before the PS service of a VIP group or VIP object is abnormally released.
Issue 03 (2010-06-30)
22-29
23 UMTS Complaint Analysis Support
23
UMTS Complaint Analysis Support
About This Chapter

This section describes the UMTS complaint analysis support, including the management of complaint analysis support tasks and the query and export of complaint analysis support reports. The Nastar can quickly locate all the call records that are related to the faulty cell involved in a complaint based on the known faulty cell and IMSI of the complaint subscriber. Through the analysis of causes of access failure, handover failure, and abnormal call drop, the Nastar assists in problem location and solution. This improves the efficiency of handling complaints and increases the subscriber satisfaction. 23.1 Basic Knowledge of UMTS Complaint Analysis Support The UMTS complaint analysis support function helps you analyze the subscriber calls that are recorded before and after a complaint and to locate and rectify the fault. This improves the efficiency of handling complaints and increases user satisfaction. 23.2 UMTS Complaint Analysis Support Process This section describes the UMTS complaint analysis support process. 23.3 Managing UMTS Complaint Analysis Support Tasks This section describes how to manage UMTS complaint analysis support tasks. You can create, modify, delete, suspend, or restore UMTS complaint analysis support tasks. You can also view the status and execution progress of such tasks. 23.4 Querying UMTS Complaint Analysis Support Reports This section describes how to query UMTS complaint analysis support reports. With this function, you can view the call records of subscribers and the details of each call record. The Nastar provides information about the UE capability, access and release, and service quality regarding each call record to assist you in determining the network location where the problem occurs and the possible causes. 23.5 Exporting UMTS Complaint Analysis Support Reports This section describes how to export UMTS complaint analysis support reports. You can export the queried complaint analysis support results as .csv or .xls files as required. The exported complaint analysis support results can then assist you in determining the network location where the problem occurs and the possible causes. 23.6 Reference to the UMTS Complaint Analysis Support Interface
This section describes the interface for UMTS complaint analysis support and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS complaint analysis support.
23-2
Issue 03 (2010-06-30)
23.1 Basic Knowledge of UMTS Complaint Analysis Support

The UMTS complaint analysis support function helps you analyze the subscriber calls that are recorded before and after a complaint and to locate and rectify the fault. This improves the efficiency of handling complaints and increases user satisfaction.
Complaint Analysis Support

The Nastar obtains the call history records (CHRs) from the network, and then filters, aggregates, and analyzes data based on a specified history period and detailed call records of subscribers in a specified area, thus assisting in problem location and solving. The complaint analysis support consists of the aggregation and analysis of cause types in call reports from complaint subscribers, aggregation and analysis of information about call reports from complaint subscribers, analysis of detailed information about call reports from complaint subscribers, analysis of procedure before the signaling release in call reports from complaint subscribers, and analysis of active cells in call reports from complaint subscribers.
l
The aggregation and analysis of cause types in call reports from complaint subscribers help network engineers filter and aggregate call reports based on abnormal causes. The cause types are classified into five types: normal, access failed, handover failed, call drop, and other exceptions. For detailed description of cause types, see Table 23-1. Table 23-1 Cause type and related description Cause Type Normal Item Indicates the call reports in which the RRC access/release, RAB block, and all the corresponding handover blocks are normal. Indicates the call reports in which the RRC access, CS service access, or PS service access fails. Indicates the call reports in which any of the soft handover, hard handover, or interRAT handover fails or the combination of the preceding handover failures exists. Corresponding Call Status
l l l l
RRC access normal RRC release normal CS service normal PS service normal
Access failed
l l l
RRC access failed CS service access failed PS service access failed Soft handover failed Hard handover failed Inter-RAT handover failed
Handover failed
l l l
Issue 03 (2010-06-30)
23-3
Cause Type Call drop
Item Indicates the call reports in which the CS call drops or PS call drops are recorded.
Corresponding Call Status

l l l l l
CS service call drop PS service call drop CS service call drop/PS service normal CS service normal/PS service call drop CS service call drop/PS service call drop
Other exceptions
Indicates the call reports recording other exceptions.
The aggregation and analysis of call information of complaint subscribers provide the overview of information about all the filtered call records. The information includes the access time, access cell, release time, release cell, IMSI, IMEI, service duration, link setup type, and call status. This function helps network engineers quickly identify abnormal call records (for example, too-short-time call record) and preliminarily learn the situation of complaint subscribers. The analysis of detailed call records of complaint subscribers provides the detailed information about all the filtered call records. The information includes the subscriber information, access/release information, CS service information, PS service information, and handover information. This function helps network engineers learn the key events that occur during calls, service usage, and MRs before the signaling release, thus accurately and quickly assisting in problem location. The analysis of procedures before the signaling release in call records of complaint subscribers provides the detailed procedures before the signaling release of all the filtered subscribers. This function helps network engineers locate problems based on the information before the signaling release. The analysis of active cells in call records of complaint subscribers enables network engineers to learn all the cells recorded in abnormal call records.
Limitation
The UMTS complaint analysis support function requires the reporting of raw call data from complaint subscribers. The amount of raw data is huge. Therefore, limitation is required to prevent the system from becoming overloaded in the case of concurrent operations by a large number of users. In such a case, the maximum number of complaint subscribers allowed by the Nastar cannot exceed 2,000, and the selected complaint subscribers must be under the same OSS.
23.2 UMTS Complaint Analysis Support Process

This section describes the UMTS complaint analysis support process. Figure 23-1 shows the general process of UMTS complaint analysis support.
23-4
Issue 03 (2010-06-30)
Figure 23-1 Process of UMTS complaint analysis support

Table 23-2 describes the items in the flowchart. Table 23-2 Description of UMTS complaint analysis support process No. 1 Procedure Creating a complaint analysis support task Querying complaint analysis support reports Item In the Analysis Task Management window on the Nastar client, you can create complaint analysis support tasks. After obtaining the related analysis data from the database, the Nastar analyzes the data and then outputs the analysis result. You can view the analysis results of the complaint analysis support tasks that are executed successfully and also perform comprehensive analysis together with maps. In addition, you can export the result files through the one-key method in the analysis result query interface. You can export analysis result files in the Nastar performance analysis system.
Exporting complaint analysis support reports
23.3 Managing UMTS Complaint Analysis Support Tasks

This section describes how to manage UMTS complaint analysis support tasks. You can create, modify, delete, suspend, or restore UMTS complaint analysis support tasks. You can also view the status and execution progress of such tasks. 23.3.1 Creating UMTS Complaint Analysis Support Tasks This section describes how to create a UMTS complaint analysis support task. When receiving a subscriber complaint, you can create a UMTS complaint analysis support task to search for
the subscriber call records related to the complaints based on the cell and subscriber IMSI related to the complaint. This helps the analysis personnel in problem analysis and location. 23.3.2 Modifying UMTS Complaint Analysis Support Tasks This section describes how to modify the attributes of the UMTS complaint analysis support tasks. You can modify the attributes of the UMTS complaint analysis support tasks as required. 23.3.3 Checking UMTS Complaint Analysis Support Tasks This section describes how to check UMTS complaint analysis support tasks. You can check the attributes, execution progress, and execution results of a UMTS complaint analysis support task as required.
23.3.1 Creating UMTS Complaint Analysis Support Tasks

This section describes how to create a UMTS complaint analysis support task. When receiving a subscriber complaint, you can create a UMTS complaint analysis support task to search for the subscriber call records related to the complaints based on the cell and subscriber IMSI related to the complaint. This helps the analysis personnel in problem analysis and location.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the complaint analysis support. The related data tracing task is enabled on the NE.
Context
l l
Tasks of this type can be performed only once. The system supports a maximum of 50 tasks of this type. The time range of the data to be analyzed cannot exceed 7 days and the start time must be earlier than the current time. The IMSI file of the complaint subscriber to be imported contains only the IMSI column, as shown in Table 23-3. Table 23-3 Complaint subscriber IMSI file IMSI 460079053010239 460005396052916 460022068262211
Procedure
Step 1 Click in the Analysis Task Management window. The Analysis Task Management-New Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can only be Once Task.
Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 In the NE Filtering area, perform the following operations: 1. 2. 3. Select connect cell or release cell for the filtering. In the OSS Name drop-down list box, select the OSS name for the task. Click Select. In the displayed Cell Selection dialog box, select one or multiple cells.
Step 7 In the User Filtering area, perform the following operations:

l
Adding a subscriber 1. 2. Click Add. In the displayed New Task - Add User dialog box, enter the IMSI of the subscriber. Click Confirm. Click Importing(I). The Open dialog box is displayed. Select the edited IMSI file of a complaint subscriber, and then click Open. Perform the operations as prompted.
Importing a subscriber 1. 2. 3.
If the imported information is correct and no duplicates of the records exist, click Confirm in the displayed dialog box. If the imported information is correct but certain duplicates of the records exist, the Confirm dialog box is displayed. In this case, click Yes to overwrite the existing records and import the additional records. After the import is complete, click Confirm in the displayed dialog box. You can also click No in the displayed Confirm dialog box to ignore the duplicate records and import the additional records.
If certain abnormal records exist in the information to be imported, the import of the current file is not allowed. In this case, the system displays the number of abnormal records.
Click Export Check Result to export the check result so that you can make modifications based on the error information to complete the current import task. You can click Cancel to terminate the current import task.
Postrequisite
l
Deleting a task You can delete an unnecessary complaint analysis support task to release system resources.
NOTE
1.
Click the UMTS Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window.
Issue 03 (2010-06-30)
If you choose Subject Function, the task list on the right displays all the performance analysis tasks. 2. 3.
l
Suspending a task To delay the task execution, you can suspend a complaint analysis support task that is in the idle state. Then, the complaint analysis support task becomes a suspended task.
NOTE
The system can schedule only the complaint analysis support tasks that are not suspended.
1.
Click the UMTS Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
button.
l
Restoring a task You can restore a suspended complaint analysis support task to the idle state. Then, the task can be scheduled by the system.
NOTE
1.
Click the UMTS Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
button.
23.3.2 Modifying UMTS Complaint Analysis Support Tasks

This section describes how to modify the attributes of the UMTS complaint analysis support tasks. You can modify the attributes of the UMTS complaint analysis support tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the complaint analysis support. A UMTS complaint analysis support task is created.
Context
Procedure
Step 1 Click the UMTS Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 23.6.1 Parameters for Creating and Modifying UMTS Complaint Analysis Support Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, and the filtering method.
23.3.3 Checking UMTS Complaint Analysis Support Tasks

This section describes how to check UMTS complaint analysis support tasks. You can check the attributes, execution progress, and execution results of a UMTS complaint analysis support task as required.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS complaint analysis support task is created.
Procedure
Step 1 Click the UMTS Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Then ...
Check the attributes of a UMTS complaint Select a task from the task list in the upper-right analysis support task pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 23.3.2 Modifying UMTS Complaint Analysis Support Tasks.
Issue 03 (2010-06-30)
23-9
If You Want to ...
Then ...
Check the execution progress of the active Select a task from the task list in the upper-right task pane. Then, you can view the execution progress of the task in the Progress column. Check the task execution results Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
23.4 Querying UMTS Complaint Analysis Support Reports

This section describes how to query UMTS complaint analysis support reports. With this function, you can view the call records of subscribers and the details of each call record. The Nastar provides information about the UE capability, access and release, and service quality regarding each call record to assist you in determining the network location where the problem occurs and the possible causes.
Prerequisite
l

23-10

l l l
The ItmService process of the Nastar runs normally. You are authorized to perform the complaint analysis support. The complaint analysis support task is executed successfully.
Procedure
Step 1 Click the UMTS Complaint Analysis Support Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. The analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose UMTS Complaint Analysis Support Task from the shortcut menu. The UMTS Complaint Analysis Support Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a call record from the navigation tree of the call report cause type overview of complaint subscribers on the left of the UMTS Complaint Analysis Support Task window, view the call report overview table and the detailed call report table on the right. You can also check the signaling record in the lower pane to learn the signaling information before the call release.
l
The navigation tree of the call report cause type overview of complaint subscribers provides two display modes, namely, Cause type-IMSI and IMSI-Cause type.
In Cause type-IMSI mode, all the call records are classified on the basis of cause types and the call records of each cause type is then classified on the basis of IMSIs. In IMSI-Cause type mode, all the call records are classified on the basis of IMSIs and the call records of each IMSI is then classified on the basis of cause types.
For detailed description of cause types, see 23.1 Basic Knowledge of UMTS Complaint Analysis Support.
l
You can find a call record quickly from a great number of call reports by entering the IMSI or cause type in the Find area above the navigation tree of the call report cause type overview of complaint subscribers. In the call report overview table of a complaint subscriber, you can view the overview information of all the filtered call reports. The information includes access time, access cell, release time, release cell, IMSI, IMEI, service duration, link establishment type, and call status. In the detailed call report table of a complaint subscriber, you can view the details of all the filtered call reports. The details include information about the subscriber, access, release, CS service, PS service, and handover. In the table of the signaling flow before the call release associated with the complaint subscriber call report, you can view the detailed signaling flows before the call release of every filtered subscribers. For description of the parameters, see 23.6.2 Parameters for Querying UMTS Complaint Analysis Support Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 23.5 Exporting UMTS Complaint Analysis Support Reports. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
23.5 Exporting UMTS Complaint Analysis Support Reports

This section describes how to export UMTS complaint analysis support reports. You can export the queried complaint analysis support results as .csv or .xls files as required. The exported complaint analysis support results can then assist you in determining the network location where the problem occurs and the possible causes.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the UMTS complaint analysis support reports.
Procedure
in the UMTS Complaint Analysis Support Task window. The Save As dialog box Step 1 Click is displayed. Step 2 Set a file name and specify the save path and file type. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. ----End
23.6 Reference to the UMTS Complaint Analysis Support Interface

This section describes the interface for UMTS complaint analysis support and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS complaint analysis support. 23.6.1 Parameters for Creating and Modifying UMTS Complaint Analysis Support Tasks This section describes the parameters for creating and modifying UMTS complaint analysis support tasks. You can refer to this description when creating and modifying a UMTS complaint analysis task. 23.6.2 Parameters for Querying UMTS Complaint Analysis Support Reports This section describes the parameters for querying UMTS complaint analysis support reports. You can refer to the description when querying a UMTS complaint analysis support report.
23.6.1 Parameters for Creating and Modifying UMTS Complaint Analysis Support Tasks
This section describes the parameters for creating and modifying UMTS complaint analysis support tasks. You can refer to this description when creating and modifying a UMTS complaint analysis task.
Parameter Basic information Task Name Description Indicates the name of a complaint analysis task. Value range:
l l
l l
Task Type Run Type Remarks
Choose UMTS Complaint Analysis Support Task from the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range: a maximum of 200 characters
Time information
Data Time Scope
Task Start At
NE filtering information
NE Filtering OSS Name
You can select access cell or release cell to filter NEs. Indicates the name of an EMS. You can select IMSI to filter call records.
User filtering information
User Filtering
Issue 03 (2010-06-30)
23-13
23.6.2 Parameters for Querying UMTS Complaint Analysis Support Reports

This section describes the parameters for querying UMTS complaint analysis support reports. You can refer to the description when querying a UMTS complaint analysis support report.

Parameter Access Time Cell for Access Release Time Cell for Release IMSI Description Indicates the time when the signaling accesses during a call. Indicates the name of the cell where signaling accesses. Indicates the time when the signaling is released during a call. Indicates the name of the cell where signaling is released. Indicates the identity number of the international mobile subscriber. IMSI is an abbreviation for International Mobile Subscriber Identity. IMEI Indicates the international mobile station equipment identity. IMEI is an abbreviation for International Mobile Equipment Identity. Service Duration Link Setup Type Indicates the duration of a service call. The types of link setup are classified into the following types:
l
Intra-system static incoming migration, that is, the radio link to the DRNC is already set up before the migration. Intra-system hard handover associated incoming migration, that is, the first radio link that is triggered by the migration request on the IU interface is set up. Intra-system CCH migration Inter-system incoming handover RRC normal setup (without DRD) RRC normal setup (with DRD)
l l l l
The results of the preceding four types are displayed as Migrated from another RNC, and the results of the later two types are displayed as Access from home RNC. Call Status Indicates the status of a call. For details, see Table 23-1.
Description of Parameters Related to Subscribers

Parameter TMSI/PTMSI Description Indicates the temporary subscriber identifier that is allocated by the network in CS domain or PS domain.
23-14
Parameter IMSI IMEI UE HS-DSCH capability UE EDCH capability
Description Indicates the identity number of the international mobile subscriber. Indicates the international mobile station equipment identity. Indicates the high-speed shared control channel capability of a UE. Indicates the enhanced dedicated channel capability of a UE.
Description of Parameters Related to Signaling Access/Release

Parameter Access Time Cell for Access RRC status during access Access cause Access delay Target DRD cell during access Access failure cause Measurement information during access Release Time Cell for Release IU release cause RRC abnormal release caus Measurement information during call release Description Indicates the time when the signaling accesses during a call. Indicates the name of the cell where signaling accesses. Indicates the RRC status during the signaling access. Indicates the cause in the RRC setup request message. Indicates the delay of the signaling access during a call. Indicates the target cell of a handover. Contains the information such as signaling failure cause, description of signaling failure, and error decoding of signaling failure. Indicates the information about the network environment measurement during the signaling access. Indicates the time when the signaling is released during a call. Indicates the ID of the cell where signaling is released. Indicates the cause of signaling release of a call. Indicates the cause of abnormal signaling release of a call. Indicates the information about the network environment measurement during the signaling release.
Description of Parameters Related to CS Services

CS refers to the circuit switched.
Issue 03 (2010-06-30)
23-15
Parameter RAB setup time
Description Indicates the setup duration of RAB service during a call. RAB is an abbreviation for Radio Access Bearer.
RAB request service type DL/UL RB rate during RAB setup DL/UL channel type for RB transmission during RAB setup RAB call drop indication Ratio of Good SQI Ratio of Accept SQI Ratio of Bad SQI Average SQI
Indicates the service type of the RAB. Indicates the uplink/downlink radio bearer rate during the RAB setup. RB is an abbreviation for Radio Bearer. Indicates the type of uplink/downlink radio bearer transmission channel during the RAB setup. Indicates the service indication of RAB call drops. Indicates the ratio of Good SQI of voice services during a call. Indicates the ratio of Accept SQI of voice services during a call. Indicates the ratio of Bad SQI of voice services during a call. Indicates the average SQI of voice services during a call. SQI is an abbreviation for Signal Quality Indicator.
Number of times UL service BLER falls into levels 1 to 6 Total number of UL blocks received within the five periods before link release Number of UL error blocks received within the five periods before link release RAB release time Best cell before the RAB release DL/UL rate during RAB release DL/UL channel type during RAB release RAB setup or release failure cause
Indicates the total number of BLERs within level 1 to level 6 in the uplink service. BLER is an abbreviation for Block Error Rate. Indicates the total number of blocks received in the uplink during the periods from 1 to 5 before the link release.
Indicates the total number of error blocks received in the uplink during the periods from 1 to 5 before the link release.
Indicates the RAB release time during a call. Indicates the name of the cell with the best signal quality before the RAB release. Indicates the uplink/downlink rate during the RAB release. Indicates the type of uplink/downlink transmission channel during the RAB release. Indicates the cause of RAB setup failure or release failure.
23-16
Issue 03 (2010-06-30)
Description of Parameters Related to PS Services

PS refers to the packet switched. Parameter RAB setup time RAB request service type DL/UL RB rate during RAB setup DL/UL channel type for RB transmission during RAB setup RAB call drop indication DL/UL RAB negotiated final rate Number of UL TRB RLC resets Number of DL TRB RLC resets HSDPA Ratio of 0 BO HSDPA PDCP UL data amount HSDPA PDCP DL data amount Number of times UL service BLER falls into levels 1 to 6 Total number of UL blocks received within the five periods before link release Number of UL error blocks received within the five periods before link release Description Indicates the setup duration of PS service during a call. Indicates the service type of the RAB. Indicates the uplink/downlink radio bearer rate during the RAB setup. Indicates the type of uplink/downlink radio bearer transmission channel during the RAB setup. Indicates the service indication of RAB call drops. Indicates the uplink/downlink final transmission rate during the data sending of RAB service. Indicates the number of uplink radio bearer resets after multiple RLC retransmissions fail in acknowledged mode. Indicates the number of downlink radio bearer resets after multiple RLC retransmissions fail in acknowledged mode. Indicates the proportion that the amount of transmission data is zero. HSDPA is an abbreviation for High Speed Downlink Packet Access. Indicates the amount of uplink data at the packet data convergence layer of the HSDPA service. Indicates the amount of downlink data at the packet data convergence layer of the HSDPA service. Indicates the total number of BLERs within level 1 to level 6 in the uplink service. Indicates the total number of blocks received in the uplink during the periods from 1 to 5 before the link release.
Indicates the total number of error blocks received in the uplink during the periods from 1 to 5 before the link release.
Issue 03 (2010-06-30)
23-17
Parameter RAB release time Best cell before the RAB release DL/UL rate during RAB release DL/UL channel type during RAB release RAB setup or release failure cause
Description Indicates the RAB release time during a call. Indicates the name of the best cell before the RAB release. Indicates the uplink/downlink rate during the RAB release. Indicates the type of uplink/downlink transmission channel during the RAB release. Indicates the cause of RAB setup failure or release failure.
Description of Parameters Related to Handover

Parameter SHO SHO initiating time Measurement information during SHO
l
Description Indicates the time when a soft handover request is initiated. Indicates the information about the network environment measurement during the soft handover.
cells in active set
IDs of cells in active set Ec/NO of cells in active set RSCP of cells in active set
cells in monitoring set
IDs of cells in monitoring set Ec/NO of cells in monitoring set RSCP of cells in monitoring set
23-18
Issue 03 (2010-06-30)
Parameter SHO target cell

l
Description ID of SHO target cell Link setup time Link removal time Operation type SHO type CRNC communication context Indicates the cause of the soft handover failure. Indicates the time when a hard handover request is initiated. Indicates the target cell of a hard handover.
l
Indicates the information about the target cell of the soft handover.
l l l l l
SHO failure cause HHO HHO initiating time HHO target cell Measurement information during HHO cells in active set
IDs of cells in active set CRNC communication context
Indicates the information about the network environment measurement during the hard handover.
l l
HHO target cell Ec/NO of the target cell RSCP of the target cell Indicates the cause of the hard handover failure. Indicates the time when an inter-RAT handover request is initiated. Indicates the target cell of the interRAT handover. Indicates the target system of the interRAT handover.
HHO failure cause InterRAT HO Inter-RAT HO initiation cause Inter-RAT HO target cell Inter-RAT HO target System
Issue 03 (2010-06-30)
23-19
24 UMTS Pilot Pollution Analysis
24
About This Chapter
UMTS Pilot Pollution Analysis
This section describes the UMTS pilot pollution analysis, including the management of pilot pollution analysis tasks and the query and export of pilot pollution analysis reports. Through the analysis of subscriber calls, the Nastar finds out the cells where pilot pollution exists, the cells that cause interference, and the interference strength. The Nastar also displays the analysis results on a map so that you can learn the detailed situation of pilot pollution. This reduces the DT time and improves the problem location accuracy. 24.1 Basic Knowledge of UMTS Pilot Pollution Analysis The UMTS pilot pollution analysis function enables you to analyze routine calls. Through the analysis of query reports, the Nastar identifies the cells where pilot pollution exists, the cells that cause interference, and the interference strength and displays the analysis results on a map. In this manner, you can directly learn the details about pilot pollution. 24.2 UMTS Pilot Pollution Analysis Process This section describes the UMTS pilot pollution analysis process. 24.3 Managing UMTS Pilot Pollution Analysis Tasks This section describes how to manage UMTS pilot pollution analysis tasks. You can create, modify, delete, suspend, or restore UMTS pilot pollution analysis tasks. You can also view the status and execution progress of such tasks. 24.4 Querying UMTS Pilot Pollution Analysis Reports This section describes how to query UMTS pilot pollution analysis reports. The Nastar analyzes the cells where pilot pollution exists, the cells that cause interference, and the interference strength by obtaining the subscriber call records. This helps solve the pilot pollution caused by factors such as cross coverage. 24.5 Exporting UMTS Pilot Pollution Analysis Reports This section describes how to export UMTS pilot pollution analysis reports. You can export the queried pilot pollution analysis results as .csv or .xls files as required. The exported pilot pollution analysis results can then assist you in determining the cells where the pilot pollution exists, the cells that causes interference, and the interference strength. 24.6 Reference to the UMTS Pilot Pollution Analysis Interface
Issue 03 (2010-06-30)
24-1
This section describes the interface for UMTS pilot pollution analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS pilot pollution analysis.
24-2
Issue 03 (2010-06-30)
24.1 Basic Knowledge of UMTS Pilot Pollution Analysis

The UMTS pilot pollution analysis function enables you to analyze routine calls. Through the analysis of query reports, the Nastar identifies the cells where pilot pollution exists, the cells that cause interference, and the interference strength and displays the analysis results on a map. In this manner, you can directly learn the details about pilot pollution. Pilot pollution refers to the situation that there are excessive signals with close strength in an area in a UMTS network. Generally, excessive radio signals form a cross coverage to the neighboring cells due to improper site layout or impacts of geographical locations. In this case, pilot pollution is produced. The pilot pollution affects network performance in the following aspects:
l
Reduced call connection ratio When there is pilot pollution, the UE constantly performs cell reselection because it cannot stably camp on a cell. During a call, the UE constantly changes serving cells, thus easily leading to call failure.
Increased call drop rate When there is pilot pollution, ping-pong hangovers occur frequently during a call because the pilot is not strong enough to be the dominant pilot. As a result, the call drop rate increases.
Reduced system capacity Pilot pollution causes strong interference. Hence, the receive sensitivity of the system is improved, and thus signals far away from the NodeB cannot be received. As a result, the system capacity is reduced.
High Block Error Rate (BLER) When there is pilot pollution, there is strong interference. Hence, the BLER is increased, leading to the deterioration of the voice quality and the decrease in the data transmission rate.
Severe pilot pollution may cause problems such as call drops, deteriorated voice quality, reduced system capacity, and network interference. Based on routine calls, the Nastar analyzes the pilot pollution, thus helping in locating polluted cells and polluter cells. Used with the GIS, this function enables the Nastar to display polluted cells and polluter cells in geographic mode, thus improving the efficiency of problem analysis and location.
24.2 UMTS Pilot Pollution Analysis Process

This section describes the UMTS pilot pollution analysis process. Figure 24-1 shows the general process of UMTS pilot pollution analysis.
Issue 03 (2010-06-30)
24-3
Figure 24-1 Process of UMTS pilot pollution analysis
Table 24-1 describes the items in the flowchart. Table 24-1 Description of UMTS pilot pollution analysis process No. 1 Procedure Querying NE data information Item In the Analysis Task Management window on the Nastar client, you can enter the data query window to query whether the raw data required for the pilot pollution analysis is imported to the database.
24-4
Issue 03 (2010-06-30)
No. 2
Procedure Creating an E2E task for the pilot pollution analysis
Item On the Nastar client, choose Maintenance > E2E Task Management. In the displayed E2E Task Management window, you can create an E2E task of pilot pollution analysis. After the task is created, the Nastar issues MML commands to the M2000, and then the M2000 issues MML commands to NEs. Finally, the NEs execute the measurement task and generate results. After an E2E task is created, in the Task Management window, you can view the corresponding collection task that has been created by the system. You can perform a data import task only after the corresponding collection task is complete. On the Nastar client, choose Maintenance > Task Management. In the displayed Task Management window, you can create a data import task corresponding to the pilot pollution analysis task so that the Nastar can periodically import the pilot pollution analysis data saved as files on the Nastar server to the database. In the Analysis Task Management window on the Nastar client, you can create pilot pollution analysis tasks. After obtaining the related analysis data from the database, the Nastar analyzes data and then outputs the analysis result. You can view the analysis results of the pilot pollution analysis tasks that are executed successfully and also perform comprehensive analysis together with maps. In addition, you can export the result files through the one-key method in the analysis result query interface.
Creating a task of importing pilot pollution analysis data
Creating a pilot pollution analysis task Querying pilot pollution analysis reports
Exporting pilot pollution analysis reports
You can export analysis result files in the Nastar performance analysis system.
24.3 Managing UMTS Pilot Pollution Analysis Tasks

This section describes how to manage UMTS pilot pollution analysis tasks. You can create, modify, delete, suspend, or restore UMTS pilot pollution analysis tasks. You can also view the status and execution progress of such tasks. 24.3.1 Creating UMTS E2E Tasks This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result. 24.3.2 Creating UMTS Pilot Pollution Analysis Tasks This section describes how to create UMTS pilot pollution analysis tasks. In a UMTS pilot pollution analysis task, the Nastar analyzes the cells where pilot pollution exists, the cells that cause interference, and the interference strength by obtaining the subscriber call records. This
helps solve the pilot pollution caused by factors such as cross coverage, thus reducing the DT time and improving the problem location accuracy. 24.3.3 Modifying UMTS Pilot Pollution Analysis Tasks This section describes how to modify the attributes of the UMTS pilot pollution analysis tasks. You can modify the attributes of the UMTS pilot pollution analysis tasks as required. 24.3.4 Checking UMTS Pilot Pollution Analysis Tasks This section describes how to check UMTS pilot pollution analysis tasks. You can check the attributes, execution progress, and execution results of a UMTS pilot pollution analysis task as required.

Prerequisite
l l l
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Set the basic information about the task. 1. 2. 3. In the Task Name field, enter the name of the E2E task. In the OSS name drop-down list box, select the OSS name for the task. Select a task from E2E Task List. Table 24-2 describes the mapping between the E2E tasks and the analysis tasks. Table 24-2 Mapping between the E2E tasks and the analysis tasks E2E Task RTWP data task
24-6
Analysis Task UMTS uplink interference analysis task

Issue 03 (2010-06-30)
E2E Task UMTS Neighboring cell data task UMTS Coverage data task UMTS VIP tracing task UMTS Pilot pollution task UMTS/GSM neighboring cell data task UMTS cell performance data task
Analysis Task UMTS co-frequency neighboring cell analysis task UMTS coverage analysis task UMTS VIP analysis task UMTS pilot pollution analysis task UMTS/GSM neighboring cell analysis task UMTS cell performance analysis task
Postrequisite

Issue 03 (2010-06-30)
2.
Click OK in the displayed Confirm dialog box.

NOTE
24.3.2 Creating UMTS Pilot Pollution Analysis Tasks

This section describes how to create UMTS pilot pollution analysis tasks. In a UMTS pilot pollution analysis task, the Nastar analyzes the cells where pilot pollution exists, the cells that cause interference, and the interference strength by obtaining the subscriber call records. This helps solve the pilot pollution caused by factors such as cross coverage, thus reducing the DT time and improving the problem location accuracy.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the pilot pollution analysis function. The E2E task, collection task, and data import task corresponding to the pilot pollution analysis task are normal. The pilot pollution analysis task can be created successfully even if the prerequisites are not met. The execution of the pilot pollution analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l l
Tasks of this type can be performed only once. A maximum of 50 tasks of this type can be created and the time range of the data in a task cannot exceed 7 days. Before you create an analysis task, check to ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can only be Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next.
Step 6 Select one or multiple objects in the object navigation tree on the tab page.
l
Select RNC or Cell Group above the navigation tree to display the objects in the navigation tree as required. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Postrequisite
l
Deleting a task You can delete an unnecessary pilot pollution analysis task to release system resources.
NOTE
1.
Click the UMTS Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task To delay the task execution, you can suspend a pilot pollution analysis task that is in the idle state. Then, the pilot pollution analysis task becomes a suspended task.
NOTE
The system can schedule only the pilot pollution analysis tasks that are not suspended.
1.
Click the UMTS Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
button.
l
Restoring a task You can restore a suspended pilot pollution analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the pilot pollution analysis tasks that are in the idle state can be scheduled by the system.
1.
Click the UMTS Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window.
Issue 03 (2010-06-30)
24.3.3 Modifying UMTS Pilot Pollution Analysis Tasks

This section describes how to modify the attributes of the UMTS pilot pollution analysis tasks. You can modify the attributes of the UMTS pilot pollution analysis tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the pilot pollution analysis function. A UMTS pilot pollution analysis task is created.
Context
Procedure
Step 1 Click the UMTS Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 24.6.3 Parameters for Creating and Modifying UMTS Pilot Pollution Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, and the information about the NE object selection.
24.3.4 Checking UMTS Pilot Pollution Analysis Tasks

This section describes how to check UMTS pilot pollution analysis tasks. You can check the attributes, execution progress, and execution results of a UMTS pilot pollution analysis task as required.
24-10
Issue 03 (2010-06-30)
Prerequisite
l l
You have logged in to the Nastar client. A UMTS pilot pollution analysis task is created.
Procedure
Step 1 Click the UMTS Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Check the attributes of a UMTS pilot pollution analysis task Then ... Select a task from the task list in the upper-right pane. Double-click the task or click .
You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 24.3.3 Modifying UMTS Pilot Pollution Analysis Tasks. Check the execution progress of the active Select a task from the task list in the upper-right task pane. Then, you can view the execution progress of the task in the Progress column. Check the task execution results Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
Issue 03 (2010-06-30)
l
24.4 Querying UMTS Pilot Pollution Analysis Reports

This section describes how to query UMTS pilot pollution analysis reports. The Nastar analyzes the cells where pilot pollution exists, the cells that cause interference, and the interference strength by obtaining the subscriber call records. This helps solve the pilot pollution caused by factors such as cross coverage.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the pilot pollution analysis function. The pilot pollution analysis task is executed successfully.
Procedure
Step 1 Click the UMTS Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. The analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose UMTS Pilot Pollution Analysis from the shortcut menu. The UMTS Pilot Pollution Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 In the UMTS Pilot Pollution Analysis window, view the overview information and details of the polluted cells and polluter cells.
l
Initially, the polluted cell overview table is displayed on the left and the polluter cell details table is displayed on the right of the UMTS Pilot Pollution Analysis window. You can click in the upper left corner to switch the display mode, namely, polluter cell overview table on the left and polluted cell details table on the right.
You can select a polluted cell from the polluted cell overview table on the left to view all the polluter cells of the selected cell in the polluter cell details table on the right. In the polluter cell details table, select a polluter cell, and then click in the upper left corner of the window to view the cells that are polluted by the selected polluter cell.
24-12
Issue 03 (2010-06-30)

l
For description of the parameters, see 24.6.4 Parameters for Querying UMTS Pilot Pollution Analysis Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 24.5 Exporting UMTS Pilot Pollution Analysis Reports. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
24.5 Exporting UMTS Pilot Pollution Analysis Reports

This section describes how to export UMTS pilot pollution analysis reports. You can export the queried pilot pollution analysis results as .csv or .xls files as required. The exported pilot pollution analysis results can then assist you in determining the cells where the pilot pollution exists, the cells that causes interference, and the interference strength.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the UMTS pilot pollution analysis reports.
Procedure
Step 1 Right-click the query result list in the UMTS Pilot Pollution Analysis window and then choose Save As... from the shortcut menu. The Save As dialog box is displayed. Step 2 Set a file name and specify the save path and file type. Then, click Save. ----End
24.6 Reference to the UMTS Pilot Pollution Analysis Interface

This section describes the interface for UMTS pilot pollution analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS pilot pollution analysis. 24.6.1 Interface Description: UMTS Pilot Pollution Analysis This section describes the interface for UMTS pilot pollution analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 24.6.2 Parameters for Creating UMTS E2E Tasks This section describes the parameters for creating UMTS E2E tasks. You can refer to the description when creating a UMTS E2E task.
24.6.3 Parameters for Creating and Modifying UMTS Pilot Pollution Analysis Tasks This section describes the parameters for creating and modifying UMTS pilot pollution analysis tasks. You can refer to this description when creating and modifying a UMTS pilot pollution analysis task. 24.6.4 Parameters for Querying UMTS Pilot Pollution Analysis Reports This section describes the parameters for querying UMTS pilot pollution analysis reports. You can refer to the description when querying a UMTS pilot pollution analysis report.
24.6.1 Interface Description: UMTS Pilot Pollution Analysis

This section describes the interface for UMTS pilot pollution analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. The pilot pollution analysis results are displayed in tables, which consist of a polluted cell overview table, a polluted cell details table, a polluter cell overview table, and a polluter cell details table, as shown in Figure 24-2. Figure 24-2 Pilot pollution analysis interface
24-14
Issue 03 (2010-06-30)
Description Provides the function of switching the information in Area (2) and (3). Initially, Area (2) displays the polluted cell overview table and Area (3) displays the polluter cell details table. After you click the switching button, Area (2) displays the polluter cell overview table and Area (3) displays the polluted cell details table.
(2)
Polluted cell overview table/polluter cell Displays the overview of all the polluted cells overview table or polluter cells involved in the task. Polluter cell details table/polluted cell details table You can select a polluted cell from the polluted cell overview table on the left to view all the polluter cells of the selected cell in the polluter cell details table on the right. In the polluter cell details table, select a polluter cell, and then click in the upper left corner of the window to view the cells that are polluted by the selected polluter cell.
(3)

Parameter Basic information Task Name OSS Name E2E Task List Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task. Indicates the types of E2E tasks. You can select one of the following E2E tasks: RTWP data task, UMTS Neighboring cell data task, UMTS Coverage data task, UMTS VIP tracing task, UMTS Pilot pollution task, UMTS/GSM neighboring cell data task, or UMTS cell performance data task. Indicates the time when the E2E task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss.
Start Time
Issue 03 (2010-06-30)
24-15
Parameter End Time
Description Indicates the time when the E2E task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Indicates the NE related to the E2E task.

24.6.3 Parameters for Creating and Modifying UMTS Pilot Pollution Analysis Tasks
This section describes the parameters for creating and modifying UMTS pilot pollution analysis tasks. You can refer to this description when creating and modifying a UMTS pilot pollution analysis task.
24-16
Issue 03 (2010-06-30)
Parameter Basic information Task Name Description Indicates the name of a pilot pollution analysis task. Value range:
l l
l l
Choose UMTS Pilot Pollution Analysis Task from the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range: a maximum of 200 characters
Time information
Data Time Scope
Task Start At
Object information
RNC Cell Group
24.6.4 Parameters for Querying UMTS Pilot Pollution Analysis Reports

This section describes the parameters for querying UMTS pilot pollution analysis reports. You can refer to the description when querying a UMTS pilot pollution analysis report.
Issue 03 (2010-06-30)
24-17
Description of Parameters in the Polluted Cell Overview Table

NOTE
With the pilot pollution analysis function, the Nastar analyzes the pilot pollution according to the signals of the serving cell and neighboring cells and primary scrambling codes (PSCs) of neighboring cells that are measured by UEs. During the analysis, the Naster determines the cell corresponding to the measured PSC of a neighboring cell based on the configuration data and engineering parameters. If any of the following conditions exists in the pilot pollution analysis result, it indicates that the cell corresponding to the PSC of a neighboring cell is not found in the search of three-layer neighboring cells of the serving cell.
l l l
RNC ID is 0. Cell ID is 0 or the PSC value is displayed. Cell Name is displayed as Unknown Cell.
Parameter RNC ID Cell ID Cell Name P-SC UARFCN_DL
Description Indicates the ID of the RNC that the polluted cell belongs to. Indicates the ID of the polluted cell. Indicates the name of the polluted cell. Indicates the primary scrambling code (P-SC) of the polluted cell. Indicates the Absolute Radio Frequency Channel Number (ARFCN) on the downlink of the UTRAN. UTRAN is an abbreviation for Universal Terrestrial Radio Access Network.
Number of MRs Average Ec/No(dB) Average RSCP (dBm) Total Number of Polluted Events Total Number of Pollution Neighboring Cells
Indicates the number of measurement reports (MRs) of the polluted cell. Indicates the average receive signal quality of pilot signals of the polluted cell. Indicates the average receive signal strength of pilot signals of the polluted cell. Indicates the total number of pollution events of the polluted cell. Indicates the total number of cells that bring pollution to the current cell.
Description of Parameters in the Polluter Cell Details Table

Parameter RNC ID Cell ID Description Indicates the ID of the RNC that the polluter cell belongs to. Indicates the ID of the polluter cell.
24-18
Issue 03 (2010-06-30)
Parameter Cell Name
Description Indicates the name of the polluter cell.

l
If the current polluter cell is a defined neighboring cell of the current polluted cell, the name of a defined neighboring cell is displayed in this field. If the current polluter cell is an undefined neighboring cell of the current polluted cell, the name of a possible neighboring cell is displayed in this field. If the system cannot find the detailed information about the cell corresponding to the P-SC of the polluted cell, Unknown is displayed in this field.
Average Ec/No(dB) Average RSCP(dBm) Number of Polluted Events Distance
Indicates the average receive signal quality of pilot signals of the polluter cell. Indicates the average receive signal strength of pilot signals of the polluter cell. Indicates the total number of pollution events that the current cell is polluted by the polluter cell. Indicates the distance between the polluted cell and the polluter cell.
Description of Parameters in the Polluter Cell Overview Table

Parameter RNC ID Cell ID Cell Name UARFCN_DL Average Ec/No(dB) Average RSCP (dBm) Total Number of Pollution Events Total Number of Polluted Neighboring Cells Description Indicates the ID of the RNC that the polluter cell belongs to. Indicates the ID of the polluter cell. Indicates the name of the polluter cell. Indicates the UTRAN ARFCN. Indicates the average receive signal quality of pilot signals of the polluter cell. Indicates the average receive signal strength of pilot signals of the polluter cell. Indicates the total number of pollution events that the polluter cell brings pollution to other cells. Indicates the total number of cells that is polluted by the current cell.
Issue 03 (2010-06-30)
24-19
Description of Parameters in the Polluted Cell Details Table

Parameter RNC ID Cell ID Cell Name Average Ec/No(dB) Average RSCP (dBm) Number of Pollution Events Distance Description Indicates the ID of the RNC that the polluted cell belongs to. Indicates the ID of the polluted cell. Indicates the name of the polluted cell. Indicates the average receive signal quality of pilot signals of the polluted cell. Indicates the average receive signal strength of pilot signals of the polluted cell. Indicates the total number of pollution events that the polluted cell is polluted by the current polluter cell. Indicates the distance between the polluted cell and the polluter cell.
24-20
Issue 03 (2010-06-30)
25 UMTS Cell Performance Analysis
25
UMTS Cell Performance Analysis
About This Chapter

This section describes the UMTS cell performance analysis, including the management of cell performance analysis tasks and the query and export of cell performance analysis reports. By providing call data of abnormal users in problem cells, the Nastar assists you in analyzing the root cause of abnormal calls. This helps to provide better services and improve user satisfaction. 25.1 Basic Knowledge of UMTS Cell Performance Analysis This section describes the basic knowledge of the UMTS cell performance analysis function, which facilitates identification of problem cells and enables the Nastar to obtain the data of exceptional calls in problem cells. By analyzing and displaying the data of exceptional calls, the Nastar assists in identifying the causes of problem cells, thus facilitating in-depth problem analysis. 25.2 UMTS Cell Performance Analysis Process This section describes the UMTS cell performance analysis process. 25.3 Managing UMTS Cell Performance Analysis Tasks This section describes how to manage UMTS cell performance analysis tasks. You can create, modify, delete, suspend, or restore UMTS cell performance analysis tasks. You can also view the status and execution progress of such tasks. 25.4 Querying UMTS Cell Performance Analysis Reports This section describes how to query UMTS cell performance analysis reports. The Nastar analyzes the call records of abnormal users in all problem cells under the selected NE and identifies the cause and top users. This helps to locate and solve the cell performance exceptions. 25.5 Exporting UMTS Cell Performance Analysis Reports This section describes how to export UMTS cell performance analysis reports. You can export the queried cell performance analysis results and save them as .xls files as required. The exported cell performance analysis results can then assist you in determining the problem cells on the network. 25.6 Reference to the UMTS Cell Performance Analysis Interface This section describes the interface for UMTS cell performance analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS cell performance analysis.
25.1 Basic Knowledge of UMTS Cell Performance Analysis

This section describes the basic knowledge of the UMTS cell performance analysis function, which facilitates identification of problem cells and enables the Nastar to obtain the data of exceptional calls in problem cells. By analyzing and displaying the data of exceptional calls, the Nastar assists in identifying the causes of problem cells, thus facilitating in-depth problem analysis.
Cell Performance Analysis

Generally, the whole-to-partial analysis method is used during the network optimization or performance analysis. That is, the Nastar locates and analyzes network problems by monitoring KPIs, and then analyzes the KPIs of the entire network or a specific RNC. Then, the Nastar analyzes cells of a faulty RNC to identify the top problem cells. After that, the Nastar analyzes the top problem cells. At present, the minimum analysis unit of most performance data is a cell. The Nastar, however, provides detailed and in-depth analysis on problem cells. The functions provided by the Nastar are as follows:
l
The Nastar analyzes exceptional call records based on the RNC or NE groups and provides top causes of exceptional cells. This helps network engineers to identify the detailed causes of the exception, thus improving work efficiency. After the main causes of problem cells are identified, the Nastar provides you with an indepth understanding of top users with poor KPIs by providing the function of analyzing top exceptional users in cells. This function helps network engineers to locate a type of top users in problem cells. In this case, network engineers can solve the problems of top users, thus improving cell performance. If problem cells are unknown, the Nastar analyzes top problem cells based on the RNC, thus helping to identify the top problem cells.
The results of cell performance analysis can be exported as .xls files. In this case, users can optimize problem cells in the network according to the exported analysis results.
Exception Types
Cell exceptional performance can be analyzed on the basis of objective network exceptions and subjective experience exceptions. For details, see Table 25-1. Table 25-1 Exception Types and Functions Service Type Network level Exception Type Objective network exception Non-service RRC setup failure Service RRC setup failure SHO failure Function Indicates exceptional conditions during the RRC setup process. Indicates exceptional conditions during the RRC setup process. Indicates exceptional conditions during soft handoffs.
Issue 03 (2010-06-30)
25-2
Service Type
Exception Type HHO failure Subjective experience exception Non-service RRC long access delay Service RRC long access delay
Function Indicates exceptional conditions during hard handovers. Indicates exceptional conditions when delay is very long during the access of the RRC. Indicates exceptional conditions when delay is very long during the access of the RRC. Indicates exceptional conditions during the call setup process. Indicates exceptional conditions during the call completion process. Indicates exceptional conditions if service call drops occur. Indicates exceptional conditions if the RAB fails to be set up. Indicates exceptional conditions if call connection delay occurs. Indicates exceptional conditions during the RAB setup process. Indicates exceptional conditions if extra-short call duration occurs. Indicates exceptional conditions if service quality is poor. Indicates exceptional conditions during the call setup process. Indicates exceptional conditions during the call completion process. Indicates exceptional conditions if service call drops occur. Indicates exceptional conditions if the RAB fails to be set up. Indicates exceptional conditions if call connection delay occurs. Indicates exceptional conditions during the RAB setup process.
CS AMR service
Objective network exception
Call setup failure Call completion failure Call drop RAB setup failure
Subjective experience exception
Long call connection delay Long RAB setup delay Short service duration High ratio of bad SQI
CS VP service CS other service
Call setup failure Call completion failure Call drop RAB setup failure
Long call connection delay Long RAB setup delay
Issue 03 (2010-06-30)
25-3
Service Type
Exception Type Short service duration
Function Indicates exceptional conditions if extra-short call duration occurs. Indicates exceptional conditions during the call setup process. Reflecting exceptional conditions during the call completion process Indicates exceptional conditions if service call drops occur. Indicates exceptional conditions if the RAB fails to be set up. Indicates exceptional conditions if call connection delay occurs. Indicates exceptional conditions during the RAB setup process. Indicates exceptional conditions if extra-short call duration occurs. Indicates exceptional conditions during the increase of the rate of the DCCC. Indicates exceptional conditions during the decrease of the rate of the DCCC. Indicates exceptional conditions if the transmission rate of uplink services is low. Indicates exceptional conditions if the transmission rate of downlink services is low. Indicates exceptional conditions during the call setup process. Indicates exceptional conditions during the call completion process. Indicates exceptional conditions if service call drops occur. Indicates exceptional conditions if the RAB fails to be set up.
PS PS service
PS call setup failure PS call completion failure PS call drop PS RAB setup failure
PS long call connection delay PS long RAB connection delay PS short service duration PS DCCC rate increase failure PS DCCC rate decrease failure Low PS UL RAB negotiated final rate Low PS DL RAB negotiated final rate
PS HSDPA service
HSDPA call setup failure HSDPA call completion failure HSDPA call drop HSDPA RAB setup failure
25-4
Issue 03 (2010-06-30)
Service Type
Exception Type Subjective experience exception HSDPA long call connection delay HSDPA long RAB setup delay HSDPA short service duration HSDPA DCCC rate increase failure HSDPA DCCC rate decrease failure Low HSDPA DL average rate
Function Indicates exceptional conditions if call connection delay occurs. Indicates exceptional conditions during the RAB setup process. Indicates exceptional conditions if extra-short call duration occurs. Indicates exceptional conditions during the increase of the rate of the DCCC. Indicates exceptional conditions during the decrease of the rate of the DCCC. Indicates exceptional conditions if the transmission rate of downlink services is low. Indicates exceptional conditions during the call setup process. Indicates exceptional conditions during the call completion process. Indicates exceptional conditions if service call drops occur. Indicates exceptional conditions if the RAB fails to be set up. Indicates exceptional conditions if call connection delay occurs. Indicates exceptional conditions during the RAB setup process. Indicates exceptional conditions if extra-short call duration occurs. Indicates exceptional conditions during the increase of the rate of the DCCC. Indicates exceptional conditions during the decrease of the rate of the DCCC. Indicates exceptional conditions if the transmission rate of downlink services is low.
PS HSUPA service
HSUPA call setup failure HSUPA call completion failure HSUPA call drop HSUPA RAB setup failure
HSUPA long call connection delay HSUPA long RAB setup delay HSUPA short service duration HSUPA DCCC rate increase failure HSUPA DCCC rate decrease failure Poor PS PS UL BLER level
Issue 03 (2010-06-30)
25-5
Service Type PS other service
Exception Type Objective network exception Other call setup failure Other call completion failure Other call drop Other RAB setup failure Subjective experience exception Other long call connection delay Other long RAB setup delay Other short service duration Other DCCC rate increase failure Other DCCC rate decrease failure
Function Indicates exceptional conditions during the call setup process. Indicates exceptional conditions during the call completion process. Indicates exceptional conditions if service call drops occur. Indicates exceptional conditions if the RAB fails to be set up. Indicates exceptional conditions if call connection delay occurs. Indicates exceptional conditions during the RAB setup process. Indicates exceptional conditions if extra-short call duraiton occurs. Indicates exceptional conditions during the increase of the rate of the DCCC. Indicates exceptional conditions during the decrease of the rate of the DCCC.
25.2 UMTS Cell Performance Analysis Process

This section describes the UMTS cell performance analysis process. Figure 25-1 shows the UMTS cell performance analysis process.
25-6
Issue 03 (2010-06-30)
Figure 25-1 Process of UMTS cell performance analysis
Issue 03 (2010-06-30)
25-7
Table 25-2 Description of the UMTS cell performance analysis process No. 1 Procedure Querying NE data information Creating an end-to-end task for cell performance analysis Description In the Analysis Task Management window on the Nastar client, you can switch to the data query window to query whether the raw data required for the cell performance analysis is imported to the database. On the Nastar client, choose Maintenance > E2E Task Management. In the displayed E2E Task Management window, you can create an E2E task for cell performance analysis. After the task is created, the Nastar sends MML commands to the M2000, and then the M2000 sends MML commands to NEs. After that, the NEs execute the measurement task and generate results. After an E2E task is created, you can view the corresponding collection task that has been created by the system in the Task Management window. A data import task can be performed only after the corresponding collection task is complete. On the Nastar client, choose Maintenance > Task Management. In the displayed Task Management window, create a data import task corresponding to the cell performance analysis task so that the Nastar periodically imports the cell performance analysis data saved as files on the Nastar server to the database. In the Analysis Task Management window on the Nastar client, you can create cell performance analysis tasks. After obtaining the related analysis data from the database, the Nastar analyzes data and then generates the analysis result. You can view the analysis results of the tasks that are successfully performed. In addition, you can export the result files through the one-key method in the analysis result query interface. You can export analysis result files in the Nastar.
Creating a task for importing data of cell performance analysis Creating cell performance analysis task Querying cell performance analysis reports
Exporting cell performance analysis reports
25.3 Managing UMTS Cell Performance Analysis Tasks

This section describes how to manage UMTS cell performance analysis tasks. You can create, modify, delete, suspend, or restore UMTS cell performance analysis tasks. You can also view the status and execution progress of such tasks. 25.3.1 Creating UMTS E2E Tasks This section describes how to create UMTS end-to-end (E2E) tasks. After you set an E2E task on the Nastar, the Nastar issues an MML command to the M2000 and then the M2000 sends the MML command to the related NE. Then, the NE performs the measurement task and generates the result.
25.3.2 Creating UMTS Cell Performance Analysis Tasks This section describes how to create UMTS cell performance analysis tasks. In a UMTS cell performance analysis task, the Nastar analyzes the abnormal call records associated with all problem cells under the selected NE to identify the cause of the abnormal calls. This function helps operators locate and rectify network faults in key areas, thus improving the service quality and enhancing the user experience in the key areas. 25.3.3 Modifying UMTS Cell Performance Analysis Tasks This section describes how to modify the attributes of the UMTS cell performance analysis tasks. You can modify the attributes of the UMTS cell performance analysis tasks as required. 25.3.4 Checking UMTS Cell Performance Analysis Tasks This section describes how to check UMTS cell performance analysis tasks. You can check the attributes, execution progress, and execution results of a UMTS cell performance analysis task as required.

Prerequisite
l l l
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task. The New Task dialog box is displayed. Step 3 Set the basic information about the task. 1. 2. 3. In the Task Name field, enter the name of the E2E task. In the OSS name drop-down list box, select the OSS name for the task. Select a task from E2E Task List. Table 25-3 describes the mapping between the E2E tasks and the analysis tasks.
Issue 03 (2010-06-30)
25-9
Table 25-3 Mapping between the E2E tasks and the analysis tasks E2E Task RTWP data task UMTS Neighboring cell data task UMTS Coverage data task UMTS VIP tracing task UMTS Pilot pollution task UMTS/GSM neighboring cell data task UMTS cell performance data task Analysis Task UMTS uplink interference analysis task UMTS co-frequency neighboring cell analysis task UMTS coverage analysis task UMTS VIP analysis task UMTS pilot pollution analysis task UMTS/GSM neighboring cell analysis task UMTS cell performance analysis task
Postrequisite
To delete an unnecessary E2E task, perform the following operations:

1. 2.
Select a task from the E2E Task Management window, and then click Delete. Click OK in the displayed Confirm dialog box.
NOTE
25.3.2 Creating UMTS Cell Performance Analysis Tasks

This section describes how to create UMTS cell performance analysis tasks. In a UMTS cell performance analysis task, the Nastar analyzes the abnormal call records associated with all problem cells under the selected NE to identify the cause of the abnormal calls. This function helps operators locate and rectify network faults in key areas, thus improving the service quality and enhancing the user experience in the key areas.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the function of cell performance analysis. The E2E task, collection task, and data import task corresponding to the cell performance analysis task are normal. The cell performance analysis task can be created successfully even if the prerequisites are not met. The execution of the cell performance analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l l
Tasks of this type can be performed only once. A maximum of 50 tasks of this type can be created and the time range of the data in a task cannot exceed six days, that is, the start time and end time are both within three past days and three coming days. Before you create an analysis task, check to ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. Execution Type can only be set to Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data.
Step 5 Click Next. Step 6 Select one or multiple objects on the tab page.
l

Postrequisite
l
NOTE
1.
Click the UMTS Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
button.
NOTE
1.
2.
button.
l
NOTE
25-12
Issue 03 (2010-06-30)
1.
2.
button.
25.3.3 Modifying UMTS Cell Performance Analysis Tasks

This section describes how to modify the attributes of the UMTS cell performance analysis tasks. You can modify the attributes of the UMTS cell performance analysis tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the function of cell performance analysis. A UMTS cell performance analysis task is created.
Context
Procedure
Step 1 Click the UMTS Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 25.6.2 Parameters for Creating or Modifying UMTS Cell Performance Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, and the information about the NE object selection.
25.3.4 Checking UMTS Cell Performance Analysis Tasks

This section describes how to check UMTS cell performance analysis tasks. You can check the attributes, execution progress, and execution results of a UMTS cell performance analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A UMTS cell performance analysis task is created.
Procedure
Step 1 Click the UMTS Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Then ...
Check the attributes of a cell performance Select a task from the task list in the upperanalysis task right pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 25.3.3 Modifying UMTS Cell Performance Analysis Tasks. Check the execution progress of the active Select a task from the task list in the uppertask right pane. Then, you can view the execution progress of the task in the Progress column. Check the task execution results Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
25-14
l
25.4 Querying UMTS Cell Performance Analysis Reports

This section describes how to query UMTS cell performance analysis reports. The Nastar analyzes the call records of abnormal users in all problem cells under the selected NE and identifies the cause and top users. This helps to locate and solve the cell performance exceptions.
Prerequisite
l l l l
Procedure
Step 1 Click the UMTS Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. The analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose Complaint Analysis from the shortcut menu. The UMTS Cell Performance Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a cell node from the object navigation tree in the left pane of the window, and then you can view the KPI overview information of the selected cell and the ranking overview information of each KPI in the areas in the middle and on the right of the window.
l
The table lists the number of records of each exception type and the percentage of each exception type to all exceptions in the report. The cell performance exception is analyzed from two aspects, namely, objective network exception and subjective experience exception. For details, see 25.1 Basic Knowledge of UMTS Cell Performance Analysis.
Issue 03 (2010-06-30)
25-15

l
In the area on the right, namely, Area (5) and Area (6), the top users identified by IMSIs, top cells, and top exceptions are illustrated in tables and pie charts. The tables and pie charts show the number of exception records and the percentage of each exception type.
You can set Quantity in Area (8) to determine the number of top users, top cells, and top exception causes. By default, top 10 users, cells, and exception causes are displayed. The default number can not be modified. Analyze Top exceptional cells is valuable in Area (8) only when the overview node or NE group node is selected in the object navigation tree in the left pane of the window.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 25.5 Exporting UMTS Cell Performance Analysis Reports. To query chart properties, and save, print, and resize the chart in the chart area, perform the following operations:
25.5 Exporting UMTS Cell Performance Analysis Reports

This section describes how to export UMTS cell performance analysis reports. You can export the queried cell performance analysis results and save them as .xls files as required. The exported cell performance analysis results can then assist you in determining the problem cells on the network.
25-16
Issue 03 (2010-06-30)
Prerequisite
l l
You have logged in to the Nastar client. You have queried the UMTS cell performance analysis reports.
Procedure
in the UMTS Cell Performance Analysis Task window. The Save As dialog box is Step 1 Click displayed. Step 2 Set a file name and specify the save path and file type. Then, click Save. The saved .xls file is opened automatically so that you can view it conveniently. The exported results are displayed in different worksheets. The following information is included in an exported report: cell performance analysis overview, KPIs of the top 20 abnormal users, and KPIs associated with the top 20 causes. ----End
25.6 Reference to the UMTS Cell Performance Analysis Interface

This section describes the interface for UMTS cell performance analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of UMTS cell performance analysis. 25.6.1 Parameters for Creating UMTS E2E Tasks This section describes the parameters for creating UMTS E2E tasks. You can refer to the description when creating a UMTS E2E task. 25.6.2 Parameters for Creating or Modifying UMTS Cell Performance Analysis Tasks This section describes the parameters for creating or modifying UMTS cell performance analysis tasks. You can refer to the description when creating or modifying a UMTS cell performance analysis task. 25.6.3 Parameters for Querying the UMTS Cell Performance Analysis Report This section describes the parameters for querying the UMTS cell performance analysis report. You can refer to the description when querying the UMTS cell performance analysis report.

Parameter Basic information Task Name OSS Name Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task.
25-17
Issue 03 (2010-06-30)
Parameter E2E Task List
Description Indicates the types of E2E tasks. You can select one of the following E2E tasks: RTWP data task, UMTS Neighboring cell data task, UMTS Coverage data task, UMTS VIP tracing task, UMTS Pilot pollution task, UMTS/GSM neighboring cell data task, or UMTS cell performance data task. Indicates the time when the E2E task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the E2E task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must precede the end time. NE Object Indicates the NE related to the E2E task.
Start Time

25-18
Issue 03 (2010-06-30)
25.6.2 Parameters for Creating or Modifying UMTS Cell Performance Analysis Tasks
This section describes the parameters for creating or modifying UMTS cell performance analysis tasks. You can refer to the description when creating or modifying a UMTS cell performance analysis task.
Parameter Basic information Task Name Description Indicates the name of a cell performance analysis task. Value range:
l l
l l
Task Type Task Execution Type Remarks
Select UMTS Cell Performance Analysis Task in the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range: a maximum of 200 characters
Time information
Data Time Scope
Task Start At
Object information
RNC Cell Group
If you select this option, the navigation tree displays all the RNCs on the entire network. If you select this option, the navigation tree displays all the cell groups on the entire network.
Issue 03 (2010-06-30)
25-19
25.6.3 Parameters for Querying the UMTS Cell Performance Analysis Report
This section describes the parameters for querying the UMTS cell performance analysis report. You can refer to the description when querying the UMTS cell performance analysis report.

Parameter Service Type Description Indicates types of cell exceptional services, such as Network level. Cell exceptional performance can be analyzed on the basis of objective network exceptions and subjective exceptions. For details, see 25.1 Basic Knowledge of UMTS Cell Performance Analysis. Number of Reports Ratio(%) Indicates the number of exceptional call records of an exception type. Indicates the proportion of an exception type.

Parameter Description Select rank modes, which consist of the following types:
l l l
Analyze Top exceptional causes Analyze Top exceptional subscribers Analyze Top exceptional cells
Quantity Ratio(%)
Set the number of displayed objects. Indicates the proportion of exception types, cells, and users.
25-20
Issue 03 (2010-06-30)
26 CDMA Centralized Task Management
26
CDMA Centralized Task Management
About This Chapter

The Nastar provides centralized management for the CDMA timing tasks. By setting CDMA timing tasks, you can collect data from the EMS periodically, save the data as a file in certain path on the Nastar system, and import the data from the file to the database periodically for future reference. In addition, you can delete the data whose storage duration has expired from the database at the preset time to save resource space of the system. By using the function of CDMA centralized task management, you can create, modify, delete, suspend, resume, or cancel a CDMA timing task. In addition, you can view information such as status and progress of a task. 26.1 Basic Knowledge of CDMA Centralized Task Management CDMA centralized task management involves the concepts such as types of timing tasks, parameters for task scheduling, and states of timing tasks. Learning the basic knowledge of the CDMA centralized task management helps you perform the operations related to the CDMA centralized task management. 26.2 Creating a CDMA User-Defined Timing Task The Nastar allows you to create CDMA timing tasks. Thus, you can create CDMA timing tasks by setting common parameters and extended parameters based on the requirements of network maintenance. 26.3 Modifying a CDMA User-Defined Timing Task The Nastar allows you to modify certain parameters of a CDMA user-defined timing task. If the execution of a CDMA user-defined timing task is complete, you cannot modify the task. 26.4 Modifying a CDMA Data Deletion Task This section describes how to modify a CDMA data deletion task. If data is periodically imported to the Nastar database, the database resources may be insufficient. By performing the CDMA data deletion task, the Nastar can delete the data whose storage duration has expired from the database at the preset time to save system resources. A CDMA data deletion task is a system timing task. You can modify only certain parameters of the task. To modify a CDMA data deletion task, you must be a user in the administrator group. If the execution of a CDMA data deletion task is complete, you cannot modify the task. 26.5 Modifying the Task of Backing Up Data This section describes how to modify certain information about the system-created task of backing up data.
26.6 Setting the Suspend or Resume Time of a Timing Task You can set an automatic suspend time or an automatic resume time for a timing task. In this situation, the Nastar automatically suspends the task or resumes the task. 26.7 Viewing Timing Tasks Through the Nastar function of viewing timing tasks, you can view the status of all timing tasks in a centralized manner. This helps you adjust the concerned timing tasks according to actual conditions. 26.8 Reference to the CDMA Centralized Task Management Interface This section describes the interface for the CDMA centralized task management and related information such as the parameters used in the centralized task management. This help you understand the functions of the CDMA centralized task management.
26-2
Issue 03 (2010-06-30)
26.1 Basic Knowledge of CDMA Centralized Task Management

CDMA centralized task management involves the concepts such as types of timing tasks, parameters for task scheduling, and states of timing tasks. Learning the basic knowledge of the CDMA centralized task management helps you perform the operations related to the CDMA centralized task management. 26.1.1 Types of Timing Tasks The Nastar divides timing tasks into different types according to execution periods and task features. 26.1.2 System Timing Tasks The system timing task is created during the installation or upgrade of the Nastar system. User dbuser is the Creator of the system timing task. 26.1.3 User Timing Task A user timing task is a customized task that is created to maintain a network. 26.1.4 Task Scheduling Parameters The task scheduling parameters are the parameters related to the task execution type, consisting of task start time, task execution period, and execution times. 26.1.5 States of a Timing Task A timing task has four states: idle, running, suspended, and finished. 26.1.6 Customizing the Interface for Managing Timing Tasks This section describes how to customize the interface for managing timing tasks. The system can display timing tasks of the specified function type in the navigation tree or display the timing tasks that meet the conditions in the task list.


Issue 03 (2010-06-30)
26-3

According to different task features, the Nastar divides the managed tasks into two types: system timing tasks and user timing tasks. Table 26-2 describes the meanings of each task type. Table 26-2 Tasks Divided According to Task Features Task Type System Timing Tasks Description System timing tasks are necessary for the Nastar system to run properly. For details, see 26.1.2 System Timing Tasks. User timing tasks are the user-defined tasks that are created to meet the requirement of network maintenance. For details, see 26.1.3 User Timing Task.
User Timing Tasks

NOTE
l l

l l

The task scheduling parameters are the parameters related to the task execution type, consisting of task start time, task execution period, and execution times. Table 26-3 describes the task scheduling parameters.
26-4
Issue 03 (2010-06-30)
Table 26-3 Description of the task description parameters Parameter Task Type Description According to different task execution periods, the Nastar divides the execution types of the managed timing tasks into two types: periodic execution and one-time execution. The execution type of the system timing tasks is periodic execution. The execution type of the other user timing tasks can be periodic execution or one-time execution. Indicates start time of periodic tasks and one-time tasks set during task creation, including date and time. The start time of tasks should be later than the current server time.
l
Task start time
Period
Run Times
l l l l

A timing task has four states: idle, running, suspended, and finished. The states of a timing task change with different operations. For details, see Figure 26-1.
Issue 03 (2010-06-30)
26-5
Figure 26-1 State transition of a timing task

l l l l l l

Prerequisite
Procedure
Step 1 Choose Maintenance > Task Management, the Task Management window is displayed.
Step 2 Perform different operations according to different customized requirement. Customized Requirement Operation
26.2 Creating a CDMA User-Defined Timing Task

The Nastar allows you to create CDMA timing tasks. Thus, you can create CDMA timing tasks by setting common parameters and extended parameters based on the requirements of network maintenance. 26.2.1 Creating a Task of Importing CDMA VIP KPI Analysis Data A task of importing CDMA VIP KPI analysis data is performed to import data from the VIP KPI analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA VIP KPI analysis data. 26.2.2 Creating a Task of Importing CDMA Uplink-Interference-Ranking Analysis Data A task of importing CDMA uplink-interference-ranking analysis data is performed to import data from the uplink-interference-ranking analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA uplink-interference-ranking analysis data. 26.2.3 Creating a Task of Importing the CDMA Uplink-Interference-Spectrum Analysis Data A task of importing the CDMA uplink-interference-spectrum analysis data is performed to import data from the uplink-interference-spectrum analysis data file in a specified directory on the server to the database. This section describes how to create a task of importing the CDMA uplink-interference-spectrum analysis data. 26.2.4 Creating a Task of Importing CDMA Neighboring-Cell Analysis Data A task of importing CDMA neighboring-cell analysis data is performed to import data from the neighboring-cell analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA neighboring-cell analysis data. 26.2.5 Creating a Task of Importing CDMA Pilot Pollution Analysis Data
This section describes how to import a task of importing CDMA pilot pollution analysis data. A task of importing CDMA pilot pollution analysis data is performed to import data from the pilot pollution analysis data file in the specified directory on the server to the database at the preset time. 26.2.6 Creating a Task of Importing CDMA Coverage Analysis Data This section describes how to create a task of importing CDMA coverage analysis data. A task of importing CDMA coverage analysis data is performed to import data from the coverage analysis data file in a specified directory on the server to the database at the preset time. 26.2.7 Creating a Task of Importing CDMA Cell Performance Analysis Data This section describes how to create a task of importing CDMA cell performance analysis data. A task of importing CDMA cell performance analysis data is performed to import data from the cell performance analysis data file in a specified directory on the server to the database at the preset time. 26.2.9 Creating a Task of Importing CDMA Configuration Data A task of importing CDMA configuration data is performed to import data from the configuration data file in the specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA configuration data.
26.2.1 Creating a Task of Importing CDMA VIP KPI Analysis Data

A task of importing CDMA VIP KPI analysis data is performed to import data from the VIP KPI analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA VIP KPI analysis data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to CDMA VIP KPI analysis is collected to the Nastar server.
Context
l l
A task of importing CDMA VIP KPI analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
TIP
You can choose Task Type > Import CDMA Data from the navigation tree and then double-click Import CDMA VIP KPI Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import CDMA VIP KPI Analysis Data by default.
Step 3 Set the basic information about the task. 1.

26-8
Type the name of the task in Task Name.

2.
Select the VIP KPI analysis data import task from Task Type.
NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Issue 03 (2010-06-30)
26-9

NOTE
1. 2.
NOTE
1. 2. 3.
l
26.2.2 Creating a Task of Importing CDMA Uplink-InterferenceRanking Analysis Data

A task of importing CDMA uplink-interference-ranking analysis data is performed to import data from the uplink-interference-ranking analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA uplink-interference-ranking analysis data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The CDMA uplink-interference-ranking analysis data is collected to the Nastar server.
26-10
Context
l
A task of importing the CDMA uplink-interference-ranking analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
TIP
You can choose Task Type > Import CDMA Data from the navigation tree and then double-click Import CDMA Uplink Interference Analysis - TopN Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import CDMA Uplink Interference Analysis - TopN Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. From Task Type, select the task of importing uplink-interference-ranking analysis data.
NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
Issue 03 (2010-06-30)
Choose Task Type from the navigation tree in the left pane of the Task Management window. Select the timing task from the task list in the right pane. Click Delete. In the Confirm dialog box, click Yes.
Then, the task is deleted from the task list.

l
NOTE
1. 2.
NOTE
1. 2. 3.
26-12
Choose Task Type from the navigation tree in the right pane of the Task Management window. Select the running task from the task list in the right pane. Right-click and choose Cancel. In the Confirm dialog box, click Yes.
Then, the task state is changed from Running to Idle.

l
26.2.3 Creating a Task of Importing the CDMA UplinkInterference-Spectrum Analysis Data

A task of importing the CDMA uplink-interference-spectrum analysis data is performed to import data from the uplink-interference-spectrum analysis data file in a specified directory on the server to the database. This section describes how to create a task of importing the CDMA uplink-interference-spectrum analysis data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The CDMA uplink-interference-spectrum analysis data is collected to the Nastar server.
Context
l
A task of importing the CDMA uplink-interference-spectrum analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
TIP
You can choose Task Type > Import CDMA Data from the navigation tree and then double-click Import CDMA Uplink Interference Analysis - Spectrum Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import CDMA Uplink Interference Analysis - Spectrum Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. From Task Type, select the task of importing the uplink-interference-spectrum analysis data.
NOTE
Issue 03 (2010-06-30)
26-13
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
NOTE
1. 2.

26-14
Select the timing task that is in the suspended state from the task list in the right pane. Right-click and choose Resume. In the Confirm dialog box, click Yes.
NOTE
1. 2. 3.
l
26.2.4 Creating a Task of Importing CDMA Neighboring-Cell Analysis Data

A task of importing CDMA neighboring-cell analysis data is performed to import data from the neighboring-cell analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA neighboring-cell analysis data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to CDMA neighboring-cell analysis is collected to the Nastar server.
Context
l l
A task of importing CDMA neighboring-cell analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Issue 03 (2010-06-30)
Procedure
TIP
You can choose Task Type > Import CDMA Data from the navigation tree and then double-click Import CDMA Intra-Frequency Neighboring Cell Analysis Data (1X) or Import CDMA Intra-Frequency Neighboring Cell Analysis Data (DO). The New Task dialog box is displayed. The Task Type parameter is set to Import CDMA Intra-Frequency Neighboring Cell Analysis Data (1X) or Import CDMA Intra-Frequency Neighboring Cell Analysis Data (DO) by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. Select the neighboring-cell analysis data import task from Task Type.
NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
26-16
NOTE
1. 2.
NOTE
1. 2. 3.
l
Issue 03 (2010-06-30)
26-17
26.2.5 Creating a Task of Importing CDMA Pilot Pollution Analysis Data

This section describes how to import a task of importing CDMA pilot pollution analysis data. A task of importing CDMA pilot pollution analysis data is performed to import data from the pilot pollution analysis data file in the specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to the CDMA pilot pollution analysis is saved on the Nastar server.
Context
l l
The task of importing CDMA pilot pollution analysis data is a user-defined scheduled task. This type of task can be executed only periodically. The unit of the task execution period can be Hour, Day, Week, or Month. You can create only one user-defined scheduled task of the same type.
Procedure
TIP
Choose Task Type > Import CDMA Data > Import CDMA Pilot Pollution Analysis Data(1X) or Task Type > Import CDMA Data > Import CDMA Pilot Pollution Analysis Data(DO) from the navigation tree. Double-click the node. The New Task dialog box is displayed. Task Type is set to Import CDMA Pilot Pollution Analysis Data(1X) or Import CDMA Pilot Pollution Analysis Data(DO) by default.
Step 3 Set the basic information about the task. 1. 2. In the Task Name field, enter the name of the scheduled task. Select the cell performance analysis data import task from Task Type.
Step 4 Click Next to set the execution time of the task. 1. Click
NOTE
. In the displayed Date/Time Selection dialog box, select the start time.
Note that Start Time must be later than the current server time.
2.
Step 5 Click Finish. The new pilot pollution analysis data import task is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
NOTE
1. 2.
Resuming a task automatically Select a timing task to be resumed from the task list in the right pane. Right-click and choose Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Resume Time and set its value. Click OK.
Issue 03 (2010-06-30)
26-19
To set the time for automatically resuming a task, see 26.8.8 Parameters for Setting the Time of a Timing Task.
l
NOTE
1. 2. 3.
l
26.2.6 Creating a Task of Importing CDMA Coverage Analysis Data

This section describes how to create a task of importing CDMA coverage analysis data. A task of importing CDMA coverage analysis data is performed to import data from the coverage analysis data file in a specified directory on the server to the database at the preset time.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The CDMA coverage analysis data is collected to the Nastar server.
Context
l l
The CDMA coverage analysis data import task is a type of user-defined scheduled task. This type of task can be executed only periodically. The unit of the task execution period can be Hour, Day, Week, or Month. You can create only one user-defined scheduled task of the same type.
Procedure
TIP
Choose Task Type > Import CDMA Data > Import CDMA Coverage Analysis Data(1X) or Task Type > Import CDMA Data > Import CDMA Coverage Analysis Data(DO) from the navigation tree. Double-click the node. The New Task dialog box is displayed. Task Type is set to Import CDMA Coverage Analysis Data(1X) or Import CDMA Coverage Analysis Data(DO) by default.
26-20
Issue 03 (2010-06-30)
Step 4 Click Next to set the execution time of the task. 1. Click
NOTE
. In the displayed Date/Time Selection dialog box, select the start time.
2.
Step 5 Click Finish. The added task of importing coverage analysis data is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Issue 03 (2010-06-30)
26-21

l
NOTE
1. 2.
NOTE
1. 2. 3.
l
26.2.7 Creating a Task of Importing CDMA Cell Performance Analysis Data

This section describes how to create a task of importing CDMA cell performance analysis data. A task of importing CDMA cell performance analysis data is performed to import data from the cell performance analysis data file in a specified directory on the server to the database at the preset time.
Prerequisite
l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally.
26-22

l l
The NastarDataImportService process of the Nastar runs normally. The CDMA cell performance analysis data is collected to the Nastar server.
Context
l
The CDMA cell performance analysis data import task is a type of user-defined scheduled task. This type of task can be executed only periodically. The unit of the task execution period can be Hour, Day, Week, or Month. You can create only one user-defined scheduled task of the same type.
Procedure
TIP
Choose Task Type > Import CDMA Data > Import CDMA Cell Performance Analysis Data from the navigation tree. Double-click the node. The New Task dialog box is displayed. Task Type is set to Import CDMA Cell Performance Analysis Data by default.
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. You can also set the start time in the Start Time area.
NOTE
2.
Step 5 Click Finish. The added task of importing cell performance analysis data is displayed in the task list. ----End
Postrequisite
l
NOTE
l l l
1. 2.
Issue 03 (2010-06-30)
Choose Task Type from the navigation tree in the left pane of the Task Management window. Select the timing task from the task list in the right pane.
3. 4.
l
Click Delete. In the Confirm dialog box, click Yes. Then, the task is deleted from the task list.
NOTE
1. 2.
NOTE
1.
Choose Task Type from the navigation tree in the right pane of the Task Management window.
26-24
2. 3.
l
Select the running task from the task list in the right pane. Right-click and choose Cancel. In the Confirm dialog box, click Yes. Then, the task state is changed from Running to Idle.
26.2.8 Creating a Task of Importing CDMA VIP KPI Analysis Data

A task of importing CDMA VIP KPI analysis data is performed to import data from the VIP KPI analysis data file in a specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA VIP KPI analysis data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The data related to CDMA VIP KPI analysis is collected to the Nastar server.
Context
l l
A task of importing CDMA VIP KPI analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Procedure
TIP
You can choose Task Type > Import CDMA Data from the navigation tree and then double-click Import CDMA VIP KPI Analysis Data. The New Task dialog box is displayed. The Task Type parameter is set to Import CDMA VIP KPI Analysis Data by default.
Step 3 Set the basic information about the task. 1. 2. Type the name of the task in Task Name. Select the VIP KPI analysis data import task from Task Type.
NOTE
2.
Issue 03 (2010-06-30)

Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
NOTE
1. 2.

26-26
Select the timing task that is in the suspended state from the task list in the right pane. Right-click and choose Resume. In the Confirm dialog box, click Yes.
NOTE
1. 2. 3.
l
26.2.9 Creating a Task of Importing CDMA Configuration Data

A task of importing CDMA configuration data is performed to import data from the configuration data file in the specified directory on the server to the database at a preset time. This section describes how to create a task of importing CDMA configuration data.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. The NastarDataImportService process of the Nastar runs normally. The CDMA configuration data is collected to the Nastar server. For details of creating the performance data collection task, see 8.2.1 Creating a Data Collection Task.
Context
l l
A task of importing CDMA configuration data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month. For the user-defined timing tasks of the same type, the system can create only one.
Issue 03 (2010-06-30)
Procedure
TIP
You can choose Task Type > Import CDMA Data from the navigation tree and then double-click Import CDMA CFG Data. The New Task dialog box is displayed. The Task Type parameter is set to Import CDMA CFG Data by default.
NOTE
2.
Postrequisite
l
NOTE
l l l
1. 2. 3. 4.
l
Suspending a task manually

26-28
Select the timing task that is in the idle state from the task list in the right pane. Right-click and choose Suspend. In the Confirm dialog box, click Yes.
NOTE
1. 2.
NOTE
1. 2. 3.
l
26.3 Modifying a CDMA User-Defined Timing Task

The Nastar allows you to modify certain parameters of a CDMA user-defined timing task. If the execution of a CDMA user-defined timing task is complete, you cannot modify the task.
26.3.1 Modifying a Task of Importing CDMA VIP KPI Analysis Data This section describes how to modify certain information about a task of importing CDMA VIP KPI analysis data. 26.3.2 Modifying a Task of Importing CDMA Uplink-Interference-Ranking Analysis Data This section describes how to modify certain information about a task of importing CDMA uplink-interference-ranking analysis data. 26.3.3 Modifying a Task of Importing CDMA Uplink-Interference-Spectrum Analysis Data This section describes how to modify certain information about a task of importing CDMA uplink-interference-spectrum analysis data. 26.3.4 Modifying a Task of Importing CDMA Neighboring Cell Analysis Data This section describes how to modify certain information about a task of importing CDMA neighboring cell analysis data. 26.3.5 Modifying a Task of Importing CDMA Pilot Pollution Analysis Data This section describes how to modify certain information about a created task of importing CDMA pilot pollution analysis data. 26.3.6 Modifying a Task of Importing CDMA Coverage Analysis Data This section describes how to modify certain information in a created task of importing CDMA coverage analysis data. 26.3.7 Modifying a Task of Importing CDMA Cell Performance Analysis Data This section describes how to modify certain information in a created task of importing CDMA cell performance analysis data. 26.3.8 Modifying a Task of Deleting CDMA VIP KPI Analysis Data This section describes how to modify certain information about the system-created task of deleting CDMA VIP KPI analysis data. 26.3.9 Modifying a Task of Importing CDMA Configuration Data This section describes how to modify certain information about a task of importing CDMA configuration data.
26.3.1 Modifying a Task of Importing CDMA VIP KPI Analysis Data

This section describes how to modify certain information about a task of importing CDMA VIP KPI analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing CDMA VIP KPI analysis data is created.
Context
l l
26-30
Issue 03 (2010-06-30)
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import CDMA Data > Import CDMA VIP KPI Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest task information in the task list.
NOTE
----End
26.3.2 Modifying a Task of Importing CDMA Uplink-InterferenceRanking Analysis Data

This section describes how to modify certain information about a task of importing CDMA uplink-interference-ranking analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing CDMA uplink-interference-ranking analysis data is created.
Context
l
A task of importing the CDMA uplink-interference-ranking analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import CDMA Data > Import CDMA Uplink Interference Analysis - TopN Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
26.3.3 Modifying a Task of Importing CDMA Uplink-InterferenceSpectrum Analysis Data

This section describes how to modify certain information about a task of importing CDMA uplink-interference-spectrum analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing CDMA uplink-interference-spectrum analysis data is created.
Context
l
A task of importing the CDMA uplink-interference-spectrum analysis data is a user-defined timing task. The task can be executed only periodically. The options of the execution period are Hour, Day, Week, and Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import CDMA Data > Import CDMA Uplink Interference Analysis - Spectrum Analysis Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
26.3.4 Modifying a Task of Importing CDMA Neighboring Cell Analysis Data

This section describes how to modify certain information about a task of importing CDMA neighboring cell analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing CDMA neighboring cell analysis data is created.
Context
l l
26-32
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import CDMA Data > Import CDMA Intra-Frequency Neighboring Cell Analysis Data (1X) or Task Type > Import CDMA Data > Import CDMA IntraFrequency Neighboring Cell Analysis Data (DO) from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest task information in the task list.
NOTE
----End
26.3.5 Modifying a Task of Importing CDMA Pilot Pollution Analysis Data

This section describes how to modify certain information about a created task of importing CDMA pilot pollution analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing CDMA pilot pollution analysis data is created.
Context
l l
The task of importing CDMA pilot pollution analysis data is a user-defined scheduled task. This type of task can be executed only periodically. The unit of the task execution period can be Hour, Day, Week, or Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import CDMA Data > Import CDMA Pilot Pollution Analysis Data (1x) or Task Type > Import CDMA Data > Import CDMA Pilot Pollution Analysis Data (DO) from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. The latest task information is displayed in the task list.
NOTE
----End
26.3.6 Modifying a Task of Importing CDMA Coverage Analysis Data

This section describes how to modify certain information in a created task of importing CDMA coverage analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing CDMA coverage analysis data is created.
Context
l l
The CDMA coverage analysis data import task is a type of user-defined scheduled task. This type of task can be executed only periodically. The unit of the task execution period can be Hour, Day, Week, or Month.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import CDMA Data > Import CDMA Coverage Analysis Data(1x) or Task Type > Import CDMA Data > Import CDMA Coverage Analysis Data(DO) from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. The latest task information is displayed in the task list.
NOTE
----End
26.3.7 Modifying a Task of Importing CDMA Cell Performance Analysis Data

This section describes how to modify certain information in a created task of importing CDMA cell performance analysis data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing CDMA cell performance analysis data is created.
Context
l
The CDMA cell performance analysis data import task is a type of user-defined scheduled task.
26-34

l
This type of task can be executed only periodically. The unit of the task execution period can be Hour, Day, Week, or Month
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import CDMA Data > Import CDMA Cell Performance Analysis Data from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. The latest task information is displayed in the task list.
NOTE
----End
26.3.8 Modifying a Task of Deleting CDMA VIP KPI Analysis Data

This section describes how to modify certain information about the system-created task of deleting CDMA VIP KPI analysis data.
Prerequisite
l l
Context
l
The task of deleting CDMA VIP KPI analysis data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting VIP KPI analysis data refers to deleting the VIP KPI analysis data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete CDMA Data > CDMA VIP KPI Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.

NOTE
----End
26.3.9 Modifying a Task of Importing CDMA Configuration Data

This section describes how to modify certain information about a task of importing CDMA configuration data.
Prerequisite
l l
You have logged in to the Nastar client. A task of importing CDMA configuration data is created.
Context
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Import CDMA Data > Import CDMA CFG Data from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest task information in the task list.
NOTE
----End
26.4 Modifying a CDMA Data Deletion Task

This section describes how to modify a CDMA data deletion task. If data is periodically imported to the Nastar database, the database resources may be insufficient. By performing the CDMA data deletion task, the Nastar can delete the data whose storage duration has expired from the database at the preset time to save system resources. A CDMA data deletion task is a system timing task. You can modify only certain parameters of the task. To modify a CDMA data deletion task, you must be a user in the administrator group. If the execution of a CDMA data deletion task is complete, you cannot modify the task. 26.4.1 Modifying the Task of Deleting GSM History Data This section describes how to modify certain information about the system-created task of deleting GSM history data.
26.4.2 Modifying a Task of Deleting CDMA VIP KPI Analysis Data This section describes how to modify certain information about the system-created task of deleting CDMA VIP KPI analysis data. 26.4.3 Modifying a Task of Deleting CDMA Uplink-Interference-Ranking Analysis Data This section describes how to modify certain information about the system-created task of deleting CDMA uplink-interference-ranking analysis data. 26.4.4 Modifying a Task of Deleting CDMA Uplink-Interference-Spectrum Analysis Data This section describes how to modify certain information about the system-created task of deleting CDMA uplink-interference-spectrum analysis data. 26.4.5 Modifying a Task of Deleting CDMA Neighboring Cell Analysis Data This section describes how to modify certain information about the system-created task of deleting CDMA neighboring cell analysis data. 26.4.6 Modifying a Task of Deleting CDMA Pilot Pollution Analysis Data This section describes how to modify certain information in a system-created task of deleting CDMA pilot pollution analysis data. 26.4.7 Modifying a Task of Deleting CDMA Coverage Analysis Data This section describes how to modify certain information in a system-created task of deleting CDMA coverage analysis data. 26.4.8 Modifying a Task of Deleting CDMA Cell Performance Analysis Data This section describes how to modify certain information in a system-created task of deleting CDMA cell performance analysis data. 26.4.10 Modifying a Task of Deleting CDMA Configuration Data This section describes how to modify certain information about the system-created task of deleting CDMA configuration data.

Prerequisite
l l
Context
l
Procedure
Step 2 Choose Task Type > Data Collection > Old Data Deletion from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters and Extended Parameters tab pages.
NOTE
NOTE
----End

Prerequisite
l l
Context
l
l l
Procedure
NOTE
----End
26.4.3 Modifying a Task of Deleting CDMA Uplink-InterferenceRanking Analysis Data

This section describes how to modify certain information about the system-created task of deleting CDMA uplink-interference-ranking analysis data.
Prerequisite
l l
Context
l
The task of deleting CDMA uplink-interference-ranking analysis data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting uplink-interference-ranking analysis data refers to deleting the uplinkinterference-ranking analysis data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete CDMA Data > CDMA Uplink Interference Analysis - TopN Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
26.4.4 Modifying a Task of Deleting CDMA Uplink-InterferenceSpectrum Analysis Data

This section describes how to modify certain information about the system-created task of deleting CDMA uplink-interference-spectrum analysis data.
Prerequisite
l l
Context
l
The task of deleting CDMA uplink-interference-spectrum analysis data is a system timing task. It can be executed only periodically.
Issue 03 (2010-06-30)

l l
You can modify the following parameters of the task: Start Time and Period. Deleting uplink-interference-spectrum analysis data refers to deleting the uplinkinterference-spectrum analysis data collected to the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete CDMA Data > CDMA Uplink Interference Analysis - Spectrum Analysis Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End
26.4.5 Modifying a Task of Deleting CDMA Neighboring Cell Analysis Data

This section describes how to modify certain information about the system-created task of deleting CDMA neighboring cell analysis data.
Prerequisite
l l
Context
l
The task of deleting CDMA neighboring cell analysis data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting neighboring cell analysis data refers to deleting the neighboring cell analysis data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete CDMA Data > CDMA Intra-Frequency Neighboring Cell Analysis Data (1X) Maintenance or Task Type > Delete CDMA Data > CDMA IntraFrequency Neighboring Cell Analysis Data (DO) Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page.
NOTE
----End
26.4.6 Modifying a Task of Deleting CDMA Pilot Pollution Analysis Data

This section describes how to modify certain information in a system-created task of deleting CDMA pilot pollution analysis data.
Prerequisite
l l
You have logged in to the Nastar client. You are a member of the Administrators group.
Context
l
The task of deleting CDMA pilot pollution analysis data is a system scheduled task. It can only be executed periodically. Only the parameters Start Time and Period of a CDMA pilot pollution analysis data deletion task can be modified. Deleting the pilot pollution analysis data is performed to delete the expired pilot pollution analysis data on the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete CDMA Data > CDMA Pilot Pollution Analysis Data Maintenance from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. The latest task information is displayed in the task list.
NOTE
----End
26.4.7 Modifying a Task of Deleting CDMA Coverage Analysis Data

This section describes how to modify certain information in a system-created task of deleting CDMA coverage analysis data.
Prerequisite
l l
Context
l
The task of deleting CDMA coverage analysis data is a system scheduled task. It can only be executed periodically. Parameters that can be modified for a CDMA coverage analysis data deletion task are Start Time and Period. Deleting coverage analysis data refers to deleting the expired coverage analysis data collected to the NASTAR server.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete CDMA Data > CDMA Coverage Analysis Data Maintenance from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. The latest task information is displayed in the task list.
NOTE
----End
26.4.8 Modifying a Task of Deleting CDMA Cell Performance Analysis Data

This section describes how to modify certain information in a system-created task of deleting CDMA cell performance analysis data.
Prerequisite
l l
Context
l
The task of deleting CDMA cell performance analysis data is a system scheduled task. It can only be executed periodically. Parameters that can be modified for a CDMA cell performance analysis data deletion task are Start Time and Period. Deleting the cell performance analysis data is performed to delete the expired cell performance analysis data on the NASTAR server.
26-42
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete CDMA Data > CDMA Cell Performance Analysis Data Maintenance from the navigation tree in the left pane. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes on the Common Parameters tab page. Step 5 Click OK. The latest task information is displayed in the task list.
NOTE
----End

Prerequisite
l l
Context
l
l l
Procedure
NOTE
----End
26.4.10 Modifying a Task of Deleting CDMA Configuration Data

This section describes how to modify certain information about the system-created task of deleting CDMA configuration data.
Prerequisite
l l
Context
l
The task of deleting CDMA configuration data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time and Period. Deleting configuration data refers to deleting the configuration data collected to the NASTAR server.
l l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Choose Task Type > Delete CDMA Data > CDMA CFG Data Maintenance from the navigation tree on the left. Step 3 Double-click the task or click Attribute. The Attribute dialog box is displayed. Step 4 Set relevant attributes again on the Common Parameters tab page. Step 5 Click OK. You can browse the latest information about the task in the task list.
NOTE
----End

Prerequisite
l l
Context
l l
The task of backing up data is a system timing task. It can be executed only periodically. You can modify the following parameters of the task: Start Time, Execution Period, Full Backup Time, Backup Mode, and Backup Path.
26-44

l
Periodic backup refers to perform full backup on certain day within the period, and perform incremental backup at other time. The Nastar services are not disrupted when you back up data.
Procedure
NOTE
NOTE
----End

Prerequisite
l l
Context
l
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 In the navigation tree, select the task type of which you plan to suspend/restore. Step 3 Select a task in the task list in the right pane. Right-click the task and select Suspend/Restore Step 4 In the Timing Suspend/Resume dialog box, select Suspend Time or Resume Time as required.
Step 5 Set the suspend time or resume time. For details of setting an automatic suspend time or an automatic restore time, refer to 26.8.8 Parameters for Setting the Time of a Timing Task. ----End


Prerequisite
l l
Context
l l
Procedure
l l

NOTE
l l
----End

Prerequisite
l l
Procedure

Prerequisite
l l
Context
l
Procedure
l
----End
26.8 Reference to the CDMA Centralized Task Management Interface

This section describes the interface for the CDMA centralized task management and related information such as the parameters used in the centralized task management. This help you understand the functions of the CDMA centralized task management. 26.8.1 Interface Description: Centralized Task Management This section describes the Task Management interface and relevant parameters, which helps you perform the related operations. 26.8.2 Parameter for Setting Task Filter Conditions This section describes the parameters in the Task Filter Setting dialog box. When you set filter conditions for a task list, you can refer to this section. 26.8.3 Parameter for Setting Common Parameters for Timing Tasks This section describes the parameters on the Common Parameters tab on property panels of all timing tasks. When you modify a timing task, you can refer to this section. 26.8.4 Parameter for Setting the Time of a Common Periodic Task This section describes the time parameters in the New Task dialog box. When you set the time of a periodic task, you can refer to this section. 26.8.5 Parameter for Setting the Time of a Common One-Time Task This section describes the time parameter in the New Task dialog box. When you modify the time of a one-time task, you can refer to this section. 26.8.6 Parameters for Modifying the Task of Deleting History Data This section describes the parameters related to the task of deleting history data. You can refer to the description when modifying the task of deleting history data. 26.8.7 Parameters for Modifying the Task of Backing Up Data This section describes the parameters related to the task of backing up data. You can refer to the description when modifying the task of backing up data. 26.8.8 Parameters for Setting the Time of a Timing Task This section describes the parameters of auto-suspend time and auto-resume time for timing tasks.

This section describes the Task Management interface and relevant parameters, which helps you perform the related operations. After you log in to the server, the Task Management interface is displayed, as shown in Figure 26-2. Table 26-4 describes each element displayed in Figure 26-2.
26-48
Issue 03 (2010-06-30)
Figure 26-2 Integrated Task Management interface
Table 26-4 Description of the Integrated Task Management interface No. (1) (2) Name Navigation tree Task result information panel Description You can precisely locate a timing task through the navigation tree. After a task is carried out, the task result is displayed. On the task result information panel, you can browse the result of the task last carried out. Only the result of the currently selected task is displayed on the task result information panel. If multiple tasks are selected in the task list, only the result of the firstly selected task is displayed. The buttons used for carrying out integrated task management are available on the button panel.
(3)
Button panel
Issue 03 (2010-06-30)
26-49
No. (4)
Name Task list
Description You can browse the timing tasks that exist on the server side and the detailed information. In the task list, different colors are used for indicate different states of tasks (gray: complete; orange: suspended; blue: active; white: idle). The selected color of the task is darker than the previous color of the task.

Parameters
Parameter User Name Current User Description Description: Indicates the user that operates the client. Other Users Description: Indicates other users except the current user. Catego ry User Task Description: Indicates the task created by users. System Task Description: Indicates the task created by OMC during the system installation or upgrade. State Idle Description: Indicates that the task waits for being performed by the system. Running Description: Indicates that the task is being performed by the system. Suspend Description: The task is not ready to be scheduled. Finished Description: Indicates that the task is completed by the system. Last Run Result Success Description: Indicates that the task is successfully carried out. Processing Description: Indicates that the task is being processed by the system.
Parameter Partly Success Failed
Description Description: Indicates that the task is partly successfully carried out. Description: Indicates that the task fails to carry out.
Miss Run Time
Unknown

Parameters
l
l l
Run Type
Once
Period
Issue 03 (2010-06-30)
26-51
Parameter Start Time
Description Description: This parameter sets the time for starting a task. The start time should be later than the time displayed on the server.
Value Range Value: If you have selected Run At Once, the Start Time parameter is invalid. The task is performed immediately after the related settings are complete. Value:
l
Period
Run Times
Value: 0-65535

Parameters
l
26-52
Issue 03 (2010-06-30)
Parameter Period Setting Period
Description Description: Interval of periodic tasks. The value consists of numerals and units.
Settings Value:
l
Run Times
Value: 0 - 65535

Parameters
l l

Parameter Config Data Range An integer from 1 to 100 Unit: day Performanc e Data An integer from 1 to 100 Unit: day Description Indicates the storage duration of the configuration data files in the relevant path on the Nastar server. The configuration data is limited to the GSM, CDMA, UMTS, and TD-SCDMA networks. Indicates the storage duration of the performance data files in the relevant path on the Nastar server. The performance data is limited to the GSM network, and the data related to all the analysis tasks of the CDMA, UMTS, and TD-SCDMA networks. Indicates the storage duration of the neighbor measurement task files in the relevant file path on the Nastar server. The neighbor measurement task files are limited to the GSM network. Frqlog Data An integer from 1 to 100 Unit: day Indicates the storage duration of the files containing the uplink ARFCN scanning data in the relevant file path on the Nastar server. The uplink ARFCN scanning data is limited to the GSM network.

Parameter Full Backup Time Backup Mode Backup Path Range SUN, MON, TUE, WED, THU, FRI, SAT ALL, INC Description Indicates the date when data backup is performed.
Indicates the mode of the data backup. Indicates the save path of backup files. By default, the path is /export/home/backup.

This section describes the parameters of auto-suspend time and auto-resume time for timing tasks.
Table 26-5 lists the parameters of auto-suspend time and auto-resume time for timing tasks. Table 26-5 Time parameters of a timing task Name Suspend Time Description Description: The system suspends an idle task and delay the time for performing this task. If the timing task is not in the idle state at the specified time, the suspension fails. Settings Setting method: You can set the value manually. Alternatively, you can click and select the time from the time select panel. The default time format is DD/ MM/YYYY HH:MM:SS.
l l l l l l
Resume Time
Issue 03 (2010-06-30)
26-55
27 CDMA Uplink Interference Analysis
27
CDMA Uplink Interference Analysis
About This Chapter

CDMA uplink interference analysis consists of uplink-interference-ranking analysis and uplinkinterference-spectrum analysis. By using the uplink-interference-ranking analysis function, you can know the overall interference status of the selected carrier. This helps you to check whether any external interference exists on the network. If a carrier has external interference, you can enable the Nastar to display the relevant spectrum data in a chart by using the uplink-interferencespectrum analysis function. Thus, you can check the interference features. 27.1 Basic Knowledge of CDMA Uplink-Interference Analysis The CDMA uplink-interference analysis function is performed to analyze the uplink level measurement data reported by BTSs. The analysis is classified into two types: uplinkinterference-ranking analysis and uplink-interference-spectrum analysis. Based on uplinkinterference-ranking analysis results, you can determine whether the carriers on a network are experiencing external interference. The distribution chart of the difference between the RSSIs of the main and diversity antennas of the uplink can help you to locate antenna feeder problems. If any carrier is experiencing external interference, the network optimization engineers can perform the uplink-interference-spectrum analysis function to analyze the spectrum and period of the external interference. As a result, interference problems can be located quickly. 27.2 Process of CDMA Uplink Interference Analysis This section describes the process of CDMA uplink interference analysis. 27.3 Managing CDMA Uplink Interference Analysis Tasks This section describes how to manage CDMA uplink interference analysis tasks. You can create, modify, delete, suspend, and resume CDMA uplink interference analysis tasks. You can also view the status and execution progress of a task. 27.4 Querying the CDMA Uplink-Interference-Ranking Analysis Report This section describes how to query the CDMA uplink-interference-ranking analysis report. By querying the CDMA uplink-interference-ranking analysis report, you can analyze the uplinklevel measurement data reported by the BTS during a time segment, obtain the RSSIs of the main and diversity antennas and the number of concurrent users of the selected carriers during a time range, and learn about the trends of the RSSIs and the number of concurrent users. The Nastar ranks the selected carriers according to the query result and then helps you to determine whether any external interference exists on the network. 27.5 Querying the CDMA Uplink-Interference-Spectrum Analysis Report
This section describes how to query the CDMA uplink-interference-spectrum analysis task. By querying the CDMA uplink-interference-spectrum analysis task, you can analyze the scanning data (reported by the BTS) about 10 MHz or 20 MHz bands and enables the Nastar to display the distribution and trend of the spectrum data in charts. Then, you can analyze the spectral and periodical features of the external interference to quickly locate interference-related problems. 27.6 Reference for the CDMA Uplink Interference Analysis GUI This section describes the interface for CDMA uplink-interference analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA uplink-interference analysis.
27-2
Issue 03 (2010-06-30)
27.1 Basic Knowledge of CDMA Uplink-Interference Analysis

The CDMA uplink-interference analysis function is performed to analyze the uplink level measurement data reported by BTSs. The analysis is classified into two types: uplinkinterference-ranking analysis and uplink-interference-spectrum analysis. Based on uplinkinterference-ranking analysis results, you can determine whether the carriers on a network are experiencing external interference. The distribution chart of the difference between the RSSIs of the main and diversity antennas of the uplink can help you to locate antenna feeder problems. If any carrier is experiencing external interference, the network optimization engineers can perform the uplink-interference-spectrum analysis function to analyze the spectrum and period of the external interference. As a result, interference problems can be located quickly. Uplink interference is a key factor that affects the QoS of networks with respect to the following aspects: conversation quality, call drop, handover, congestion, network coverage, and network capacity. If interference and load cannot be distinguished, load control cannot work properly. After the conditions for uplink-interference-ranking analysis are set, the Nastar performs uplinkinterference-ranking analysis on the selected carriers. The analysis results are displayed in a line chart. The chart displays the values and trends of the RSSIs of the main and diversity antennas and the number of subscribers of each carrier in different colors. After the conditions for uplink-interference-spectrum analysis are set, the Nastar performs uplink-interference-spectrum analysis on the selected carriers. The analysis results are displayed in a column chart or a line chart. In the chart, the average interference strength of all the frequency sampling points of each carrier in a time segment is displayed in a color. In addition, the values and trends of the RSSIs of the main and diversity antennas of each sampling frequency point at each time point within a selected time segment are displayed in different colors.
27.2 Process of CDMA Uplink Interference Analysis

This section describes the process of CDMA uplink interference analysis. Figure 27-1 shows the process of CDMA uplink interference analysis.
Issue 03 (2010-06-30)
27-3
Figure 27-1 Workflow of uplink interference analysis

Start
Set an E2E task
Set an uplinkinterference-ranking analysis task Querying a uplinkinterference-ranking analysis report
Whether external interference exists Yes Set an uplinkinterference-spectrum analysis task Query an uplinkinterference-spectrum analysis report End
No
Table 27-1 describes the items listed in Figure 27-1.
27-4
Issue 03 (2010-06-30)
Table 27-1 Description of the workflow of uplink interference analysis No. 1 Procedure Create an endto-end task corresponding to an uplink interference analysis task Description You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to an uplink interference analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create an uplink-interference-ranking analysis data importing task. After the task is created, the Nastar periodically imports the uplink-interference-ranking analysis data files saved on the Nastar server to the database.
NOTE If you need to analyze the uplink interference spectrum, you must create a task for importing the data of uplink interference spectrum in the Task Management window. After the task is created, the Nastar periodically imports the files of the uplink interference spectrum data saved on the Nastar server to the database.
Create an uplinkinterferenceranking analysis data importing task
Create an uplinkinterferenceranking analysis task
You can create an uplink-interference-ranking analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required uplink spectrum scanning log, uplink RSSI measurement data, and configuration data from the Nastar database, and then generates an analysis report through the analysis. You can view the analysis results of the uplink-interferenceranking analysis task that is successfully performed. In addition, you can query the RSSIs of the main and diversity antennas of the selected test carrier on the network, the number of subscribers, and the trend of subscribers. The Nastar ranks the selected carriers according to the query result and thus helps you to determine whether any external interference exists on the network. You can create an uplink-interference-spectrum analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required uplink spectrum scanning log, uplink RSSI measurement data, and configuration data from the Nastar database, and then generates an analysis report through the analysis.
Querying a uplinkinterferenceranking analysis report
Create an uplinkinterferencespectrum analysis task
Issue 03 (2010-06-30)
27-5
No. 6
Procedure Query an uplinkinterferencespectrum analysis report
Description You can view the analysis results of the uplink-interferencespectrum analysis task that is successfully performed. The Nastar analyzes the scanning data about 10 MHz or 20 MHz bands in the database at a preset time and displays the distribution and trend of the spectrum data in charts. Based on the information, you can analyze the spectral and periodical features of the external interference to quickly locate interference-related problems.
27.3 Managing CDMA Uplink Interference Analysis Tasks

This section describes how to manage CDMA uplink interference analysis tasks. You can create, modify, delete, suspend, and resume CDMA uplink interference analysis tasks. You can also view the status and execution progress of a task. 27.3.1 Creating a CDMA E2E Task This section describes how to create an end-to-end (E2E) task. After you set an E2E task in the Nastar, the Nastar issues MML commands to the M2000. The M2000 then sends these MML commands to the corresponding NEs. Finally, the NEs perform the measurement tasks and generate results. 27.3.2 Creating a CDMA Uplink-Interference-Ranking Analysis Task This section describes how to create a CDMA uplink-interference-ranking analysis task. By performing CDMA uplink-interference-ranking analysis tasks, the Nastar performance analysis system analyzes the uplink-level measurement data reported by the BTS in the database at the preset time. By querying the analysis results of a selected carrier, you can learn about the corresponding RSSIs of the main and diversity antennas and the number of concurrent users during a time range, and you can also learn about the trends of the RSSIs and the number of concurrent users. Then, you can determine whether any external interference exists on the network. 27.3.3 Creating a CDMA Uplink-Interference-Spectrum Analysis Task This section describes how to create a CDMA uplink-interference-spectrum analysis task. By performing uplink-interference-spectrum analysis tasks, the Nastar performance analysis system analyzes the scanning data about 10 MHz or 20 MHz bands in the database at the preset time and displays the distribution and trend of the spectrum data in charts. Then, you can analyze the spectral and periodical features of the external interference to quickly locate interference-related problems. 27.3.4 Modifying a CDMA Uplink-Interference-Ranking Analysis Task You can modify the attributes of a CDMA uplink-interference-ranking analysis task to meet the new requirement. 27.3.5 Modifying a CDMA Uplink-Interference-Spectrum Analysis Task You can modify the attributes of a CDMA uplink-interference-spectrum analysis task to meet the new requirement. 27.3.6 Checking a CDMA Uplink-Interference-Ranking Analysis Task This section describes how to check a CDMA uplink-interference-ranking analysis task. You can check the attributes, execution progress, and execution results of a CDMA uplinkinterference-ranking analysis task.
27.3.7 Checking a CDMA Uplink-Interference-Spectrum Analysis Task This section describes how to check a CDMA uplink-interference-spectrum analysis task. You can check the attributes, execution progress, and execution results of a CDMA uplinkinterference-spectrum analysis task.
27.3.1 Creating a CDMA E2E Task

This section describes how to create an end-to-end (E2E) task. After you set an E2E task in the Nastar, the Nastar issues MML commands to the M2000. The M2000 then sends these MML commands to the corresponding NEs. Finally, the NEs perform the measurement tasks and generate results.
Prerequisite
l l l
You have logged in to the Nastar client. The OSS and NEs related to analysis tasks are created. The configuration data related to the analysis tasks is imported to the Nastar database.
Context
TIP
Procedure
Step 1 Choose Maintenance > E2E Task Management. The E2E Task Management window is displayed. Step 2 Click New Task.... The New Task dialog box is displayed. Step 3 Set the basic information about the task. 1. 2. In Task Name, type the name of the E2E task. From the OSS Name drop-down list box, select the OSS that is related to the E2E task. You can also click
l
to type the name of the OSS that is related to the E2E task.
If the OSS list does not contain the created OSS, click Add to create an OSS. OSS Name indicates the name of the OSS to be created. Port indicates the number of the port on the FTP server where the file to be collected is saved. User Name indicates the user name used for logging in to the M2000 server. Password indicates the password used for logging in to the M2000 server. FTP User indicates the user name used for logging in to the FTP server. FTP Password indicates the password used for logging in to the FTP server.
To modify the information about a created OSS, select the OSS, and then click Modify. To delete an unnecessary OSS, select the OSS, and then click Delete.
Issue 03 (2010-06-30)
3.
In E2E Task List, select a task. Table 27-2 describes the mapping between E2E tasks and analysis tasks. Table 27-2 Mapping between E2E tasks and analysis tasks E2E Tasks VIP subscriber monitoring task Interference data task Spectrum data task 1x neighboring cell data task DO neighboring cell data task Complaint analysis data task Analysis tasks CDMA VIP analysis task CDMA uplink-interference-ranking analysis task CDMA uplink-interference-spectrum analysis task CDMA co-frequency neighboring cell analysis task CDMA co-frequency neighboring cell analysis task CDMA complaint assistant analysis task
Step 4 Click Next to set Begin Time and End Time, and select one or multiple NEs from the NE list. The system enables you to search for the objects in the navigation tree. You can right-click in the navigation area and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the objects that meet the search condition. You can select Case sensitive to ensure that the typed keywords are case sensitive. You can select Up or Down in the Direction area to define the search area. Step 5 Click Complete. The MML Preview dialog box is displayed, showing the MML commands related to the current theme analysis E2E task. The MML commands can be exported for future use. Step 6 Click OK. The new E2E task is displayed in the task list. ----End
Postrequisite

27-8
2.
Click OK in the displayed Confirm dialog box.

NOTE
27.3.2 Creating a CDMA Uplink-Interference-Ranking Analysis Task

This section describes how to create a CDMA uplink-interference-ranking analysis task. By performing CDMA uplink-interference-ranking analysis tasks, the Nastar performance analysis system analyzes the uplink-level measurement data reported by the BTS in the database at the preset time. By querying the analysis results of a selected carrier, you can learn about the corresponding RSSIs of the main and diversity antennas and the number of concurrent users during a time range, and you can also learn about the trends of the RSSIs and the number of concurrent users. Then, you can determine whether any external interference exists on the network.
Prerequisite
l l
Context
l l
Procedure
l
Choose BSC or Carrier Group above the navigation tree to display the objects in the navigation tree as required. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type
Issue 03 (2010-06-30)
the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Step 7 Set Filtering Conditions of Datasource for TopN Analysis on the Parameter Setting tab page. You can flexibly set the main interference threshold and the diversity interference threshold. That is, you can set either of the thresholds or set both thresholds. Step 8 Click Complete. ----End
Postrequisite
l
Deleting a task You can delete an uplink-interference-ranking analysis task that is not required so that you can save system resources.
NOTE
1.
Choose CDMA Uplink Interference Analysis - TopN Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task To delay the task execution, you can suspend an uplink-interference-ranking analysis task that is in the idle state. After this operation, the uplink-interference-ranking analysis task is in the suspended state.
NOTE
Only the uplink-interference-ranking analysis tasks that are not suspended can be scheduled by the system.
1.
2.
. button is
Resuming a task You can resume a suspended uplink-interference-ranking analysis task to the idle state. Then, the task can be scheduled by the system.
27-10
Issue 03 (2010-06-30)

NOTE
Only the uplink-interference-ranking analysis task that is in the idle state can be scheduled by the system.
1.
2.
27.3.3 Creating a CDMA Uplink-Interference-Spectrum Analysis Task

This section describes how to create a CDMA uplink-interference-spectrum analysis task. By performing uplink-interference-spectrum analysis tasks, the Nastar performance analysis system analyzes the scanning data about 10 MHz or 20 MHz bands in the database at the preset time and displays the distribution and trend of the spectrum data in charts. Then, you can analyze the spectral and periodical features of the external interference to quickly locate interference-related problems.
Prerequisite
l l
Context
l l
Procedure
l
Choose BSC or Carrier Group above the navigation tree to display the objects in the navigation tree as required.
Issue 03 (2010-06-30)

l
The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Postrequisite
l
Deleting a task You can delete an uplink-interference-spectrum analysis task that is not required so that you can save system resources.
NOTE
1.
Choose CDMA Uplink Interference Analysis - Spectrum Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task To delay the task execution, you can suspend an uplink-interference-spectrum analysis task that is in the idle state. After this operation, the uplink-interference-spectrum analysis task is in the suspended state.
NOTE
The system can schedule only the uplink-interference-spectrum analysis tasks that are not suspended.
1.
Choose CDMA Uplink Interference Analysis - Spectrum Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
. button is
Resuming a task You can resume a suspended uplink-interference-spectrum analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the uplink-interference-spectrum analysis task that is in the idle state can be scheduled by the system.
1.
Choose CDMA Uplink Interference Analysis - Spectrum Analysis Task from the navigation tree in the Analysis Task Management window.
27-12
If you choose Subject Function, the task list on the right displays all the performance analysis tasks. 2. Select a task from the task list in the upper-right pane, and then click .
27.3.4 Modifying a CDMA Uplink-Interference-Ranking Analysis Task

You can modify the attributes of a CDMA uplink-interference-ranking analysis task to meet the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA uplink-interference-ranking analysis task is created.
Context
Procedure
Step 1 Choose CDMA Uplink Interference Analysis - TopN Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the relevant parameters, see 27.6.4 Parameters for Creating and Modifying CDMA Uplink-Interference-Ranking Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the object navigation tree, and the Filtering Conditions of Datasource for TopN Analysis parameter.
27.3.5 Modifying a CDMA Uplink-Interference-Spectrum Analysis Task

You can modify the attributes of a CDMA uplink-interference-spectrum analysis task to meet the new requirement.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA uplink-interference-spectrum analysis task is created.
Context
Procedure
Step 1 Click the CDMA Uplink Interference Analysis Task node from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the relevant parameters, see 27.6.4 Parameters for Creating and Modifying CDMA Uplink-Interference-Ranking Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, and the information about the object navigation tree.
27.3.6 Checking a CDMA Uplink-Interference-Ranking Analysis Task

This section describes how to check a CDMA uplink-interference-ranking analysis task. You can check the attributes, execution progress, and execution results of a CDMA uplinkinterference-ranking analysis task.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA uplink-interference-ranking analysis task is created.
Procedure
Step 1 Choose CDMA Uplink Interference Analysis - TopN Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required:
If you need to ... Checking the attributes of an uplinkinterference-ranking analysis task
Then ... Select a task from the task list in the upperright pane. Double-click the task or click .
You can view the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 27.3.4 Modifying a CDMA Uplink-Interference-Ranking Analysis Task. Check the execution progress of a task. Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column. Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view all the analysis results of a selected task in the lower-right pane.
Check the task execution results.
----End
Postrequisite
l
Issue 03 (2010-06-30)
27-15
27.3.7 Checking a CDMA Uplink-Interference-Spectrum Analysis Task

This section describes how to check a CDMA uplink-interference-spectrum analysis task. You can check the attributes, execution progress, and execution results of a CDMA uplinkinterference-spectrum analysis task.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA uplink-interference-spectrum analysis task is created.
Procedure
Step 1 Choose CDMA Uplink Interference Analysis - Spectrum Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: Purpose Checking the attributes of an uplinkinterference-spectrum analysis task Operation Select a task from the task list in the upperright pane. Double-click the task or click You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 27.3.5 Modifying a CDMA Uplink-InterferenceSpectrum Analysis Task. Checking the execution progress of the active task Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column. .
27-16
Issue 03 (2010-06-30)
----End
Postrequisite
l
27.4 Querying the CDMA Uplink-Interference-Ranking Analysis Report

This section describes how to query the CDMA uplink-interference-ranking analysis report. By querying the CDMA uplink-interference-ranking analysis report, you can analyze the uplinklevel measurement data reported by the BTS during a time segment, obtain the RSSIs of the main and diversity antennas and the number of concurrent users of the selected carriers during a time range, and learn about the trends of the RSSIs and the number of concurrent users. The Nastar ranks the selected carriers according to the query result and then helps you to determine whether any external interference exists on the network.
Prerequisite
Procedure
Step 1 Choose CDMA Uplink Interference Analysis - TopN Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose CDMA Uplink Interference Analysis - TopN Analysis Task. The CDMA Uplink Interference Analysis - TopN Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a test carrier from the list on the left of the window. Then, you can view the RSSIs of the main and diversity antennas of the selected carrier, the number of concurrent users, the trends of the RSSIs and the number of concurrent users, and the distribution chart of the differences between the RSSIs of the main and diversity antennas in the area on the right.
l
The left area displays the minimum average values of the RSSIs. By default, the minimum average values are in a sequence of descending order. You can adjust the sequence as required. In the area on the right:
The chart at the upper part displays the RSSIs of the main and diversity antennas of the selected carrier during the measurement period, the number of concurrent users, and the trends of the RSSIs and the number of concurrent users. The chart at the lower part displays the distribution of the differences between the RSSIs of the main and diversity antennas of the selected carrier. The difference between the RSSIs of the main and diversity antennas at each time point is calculated first. Then, the system calculates the percentage of a difference to the total number of differences.
You can zoom in or zoom out the trend chart by dragging it with the mouse. ----End
Postrequisite
l
Right-click the chart, and then choose Property from the shortcut menu. In the displayed Chart Property dialog box, set the coordinate axes of and basic information about the chart. Right-click the chart, and then choose Save as from the shortcut menu. In the displayed Save dialog box, set the save path and file name, and then click Save to save the queried chart as a file on the local PC. Right-click the chart, and then choose Print from the shortcut menu. In the displayed Page Setup dialog box, set print properties, and then click OK.
27-18
If the chart is not clear due to an excessive number of dots, right-click the chart, and then choose Zoom In > ***, Zoom Out > ***, or Auto Range > *** to adjust the size of the chart. Here, *** indicates a submenu item. It can be Both Axes, Horizontal Axis, or Vertical Axis, which indicates that you can adjust both axes, the horizontal axis, or the vertical axis, respectively.
27.5 Querying the CDMA Uplink-Interference-Spectrum Analysis Report

This section describes how to query the CDMA uplink-interference-spectrum analysis task. By querying the CDMA uplink-interference-spectrum analysis task, you can analyze the scanning data (reported by the BTS) about 10 MHz or 20 MHz bands and enables the Nastar to display the distribution and trend of the spectrum data in charts. Then, you can analyze the spectral and periodical features of the external interference to quickly locate interference-related problems.
Prerequisite
Procedure
Step 1 Choose CDMA Uplink Interference Analysis - Spectrum Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of the selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose CDMA Uplink Interference Analysis - Spectrum Analysis Task. The CDMA Uplink Interference Analysis - Spectrum Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a carrier from the list on the left. Then, view the distribution chart of the spectrum scanning data and the frequency-interference time sequence chart of the selected carrier in the area on the right. In the area on the right, the chart above, by default, displays the average signal strength of the main and diversity antennas of all the frequency sampling points of a selected carrier in a certain time segment. Select a time point from the drop-down list box in the upper-right part the chart. Then, you can view the signal strength of the main and diversity antennas of all the frequency sampling points at the selected time. From the drop-down list box in the lower-right part of the distribution chart, select a frequency sampling point. Then, the chart below displays the values
of the signal interference strength of the main and diversity antennas of the selected frequency sampling point in a certain time segment, and the trends of the values. You can zoom in or zoom out the distribution chart and sequence chart by dragging them using the mouse. ----End
Postrequisite
l
27.6 Reference for the CDMA Uplink Interference Analysis GUI

This section describes the interface for CDMA uplink-interference analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA uplink-interference analysis. 27.6.1 Interface Description: CDMA Uplink-Interference-Ranking Analysis This section describes the interface for CDMA uplink-interference-ranking analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 27.6.2 Interface Description: CDMA Uplink-Interference-Spectrum Analysis
This section describes the interface for CDMA uplink-interference-spectrum analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 27.6.3 Parameters of CDMA E2E Tasks This section describes the parameters of CDMA E2E tasks. You can refer to the description when creating or modifying a CDMA E2E task. 27.6.4 Parameters for Creating and Modifying CDMA Uplink-Interference-Ranking Analysis Tasks This section describes the parameters for creating and modifying CDMA uplink-interferenceranking analysis tasks. You can refer to the description when creating or modifying a CDMA uplink-interference-ranking analysis task. 27.6.5 Parameters for Creating and Modifying CDMA Uplink-Interference-Spectrum Analysis Tasks This section describes the parameters for creating and modifying CDMA uplink-interferencespectrum analysis tasks. You can refer to the description when creating or modifying a CDMA uplink-interference-spectrum analysis task. 27.6.6 Parameters for Querying the Uplink-Interference-Ranking Analysis Reports of CDMA Cells This section describes the parameters for querying the uplink-interference-ranking analysis reports of CDMA cells. You can refer to the description when querying the uplink-interferenceranking analysis reports of CDMA cells. 27.6.7 Parameters for Querying the Uplink-Interference-Spectrum Analysis Reports of CDMA Cells This section describes the parameters for querying the uplink-interference-spectrum analysis reports of CDMA cells. You can refer to the description when querying the uplink-interferencespectrum analysis reports of CDMA cells.
27.6.1 Interface Description: CDMA Uplink-Interference-Ranking Analysis

This section describes the interface for CDMA uplink-interference-ranking analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. The analysis results of the uplink-interference-ranking can be displayed in tables or in line charts, as shown in Figure 27-2.
Issue 03 (2010-06-30)
27-21
Figure 27-2 Interface for the uplink-interference-ranking analysis
No. Name (1) Current test carrier information list
Description Displays the basic information about all the carriers involved in an analysis task in a table. Displays the RSSIs of the main and diversity antennas of the selected carrier during the measurement period, the number of concurrent users, and the trends of the RSSIs and the number of concurrent users in charts. Displays the distribution of the differences between the RSSIs of the main and diversity antennas of the selected carrier in column charts.
(2)
Detailed information about the RSSIs of the main and diversity antennas and the number of users
(3)
Distribution chart of the differences between the RSSIs of the main and diversity antennas
27.6.2 Interface Description: CDMA Uplink-Interference-Spectrum Analysis

This section describes the interface for CDMA uplink-interference-spectrum analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface.
The analysis results of the uplink-interference-spectrum can be displayed in line charts, as shown in Figure 27-3. Figure 27-3 Interface for the uplink-interference-spectrum analysis
In Figure 27-3, the chart above, by default, displays the average signal strength of the main and diversity antennas of all the frequency sampling points of a selected carrier in a certain time segment. Select a time point from the drop-down list box in the upper-right part the chart. Then, you can view the signal strength of the main and diversity antennas of all the frequency sampling points at the selected time. From the drop-down list box in the lower-right part of the distribution chart, select a frequency sampling point. Then, the chart below displays the values of the signal interference strength of the main and diversity antennas of the selected frequency sampling point in a certain time segment, and the trends of the values.
27.6.3 Parameters of CDMA E2E Tasks

This section describes the parameters of CDMA E2E tasks. You can refer to the description when creating or modifying a CDMA E2E task.
Parameter Basic Information Task Name OSS Name Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task.
Issue 03 (2010-06-30)
27-23
Description Indicates the types of E2E tasks. You can select one of the following E2E tasks: VIP subscriber monitoring task, interference data task, spectrum data task, 1x neighboring cell data task, DO neighboring cell data task, or complaint analysis data task. Indicates the time when the task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must be earlier than the end time. NE Object Indicates the NE related to the E2E task.
Measurement Information
Begin Time
27.6.4 Parameters for Creating and Modifying CDMA UplinkInterference-Ranking Analysis Tasks
This section describes the parameters for creating and modifying CDMA uplink-interferenceranking analysis tasks. You can refer to the description when creating or modifying a CDMA uplink-interference-ranking analysis task.
Parameter Basic Information Task Name Description Indicates the name of an uplink-interferenceranking analysis task. Value range:
l l
l l
Task Type
You need to select CDMA Uplink Interference Analysis - TopN Analysis Task from the Task Type navigation tree. Such a task can be executed only once in a time segment.
Execution Type
27-24
Issue 03 (2010-06-30)
Parameter Note

l l
Time Information
Data Time Scope
Task Start At
Object Information
BSC Carrier Group
If you select this option, the navigation tree displays all the BSCs of the entire network. If you select this option, the navigation tree displays all the carrier groups of the entire network. Indicates the minimum interference strength threshold of the uplink main and diversity antennas. This parameter can be set to any integer from -120 to 0. The default value is -90. Unit: dBm
Filtering Conditions of Datasource for TopN Analysis
27.6.5 Parameters for Creating and Modifying CDMA UplinkInterference-Spectrum Analysis Tasks
This section describes the parameters for creating and modifying CDMA uplink-interferencespectrum analysis tasks. You can refer to the description when creating or modifying a CDMA uplink-interference-spectrum analysis task.
Issue 03 (2010-06-30)
27-25
Parameter Basic Information Task Name Description Indicates the name of an uplink-interferencespectrum analysis task. Value range:
l l
l l
Task Type
You need to select CDMA Uplink Interference Analysis - Spectrum Analysis Task from the Task Type navigation tree. Such a task can be executed only once in a time segment. Indicates the description of the task. Value range:
l l
Execution Type Note
Time Information
Data Time Scope
Task Start At
Object Information
BSC Carrier Group
If you select this option, the navigation tree displays all the BSCs of the entire network. If you select this option, the navigation tree displays all the carrier groups of the entire network.
27.6.6 Parameters for Querying the Uplink-Interference-Ranking Analysis Reports of CDMA Cells
This section describes the parameters for querying the uplink-interference-ranking analysis reports of CDMA cells. You can refer to the description when querying the uplink-interferenceranking analysis reports of CDMA cells.
Parameter Carrier Name Average RSSI of Main (dBm) Average RSSI of Diversity (dBm) Maximum Number of User Legs Minimum RSSI Average of the Main and Diversity (dBm) Average Difference (Main-Diversity) (dB) Standard Deviation (Main-Diversity) Description Indicates the name of the test carrier, for example, Carrier_1. Indicates the average RSSI of the main antennas of the carriers in a selected time segment. Indicates the average RSSI of the diversity antennas of the carriers in a selected time segment. Indicates the maximum number of subscriber-occupied traffic channels of each carrier in a selected time segment. Indicates the average value of the minimum RSSI of the main antenna and of the diversity antenna of each carrier in a selected time segment. Indicates the value calculated by dividing the sum of the differences between the RTWPs of the main and diversity antennas at each time point in the selected time range by the total number of time points. Indicates the square root of the value calculated by dividing the sum of the square of the difference between the RTWPs of the main and diversity antennas at each time point in the selected time range by the total number of time points.
27.6.7 Parameters for Querying the Uplink-Interference-Spectrum Analysis Reports of CDMA Cells
This section describes the parameters for querying the uplink-interference-spectrum analysis reports of CDMA cells. You can refer to the description when querying the uplink-interferencespectrum analysis reports of CDMA cells.
Parameter Central frequency BSCName Site name Description Indicates the frequency of the selected carrier. Indicates the name of the BSC that a carrier belongs to, for example, BSC_1. Indicates the name of the BTS that a carrier belongs to. The naming rule is BTS name - BTS ID. CellName Indicates the name of the cell that a carrier belongs to. The naming rule is cell name - cell ID. Sector Name Indicates the name of the sector that a carrier belongs to. The naming rule is sector name - sector ID.
Parameter Band Center Frequency Bandwidth Spectrum RBW Time Span
Description Indicates the band of a carrier. Indicate the frequency of the selected carrier. Indicates the frequency range corresponding to a spectrum. Indicates the resolution bandwidth. Indicates the time segment of the data selected for the analysis task.
27-28
Issue 03 (2010-06-30)
28 CDMA Co-Frequency Neighboring Cell Analysis
28
CDMA Co-Frequency Neighboring Cell Analysis
About This Chapter

This section describes the CDMA co-frequency neighboring cell analysis. The CDMA cofrequency neighboring cell analysis function enables you to manage neighboring cell analysis tasks, check CDMA neighboring cell analysis reports, and export the CDMA neighboring cell analysis reports. Based on the configuration data and the engineering parameters, the Nastar analyzes the Pilot Strength Measurement Message (PSMM)/Route Update message (RU) reported by UEs on the network to check for the redundant and missing neighboring cell configuration of a measurement cell and the priorities that need to be adjusted. If this information exists, the system displays the information. This helps you to solve the problems relating to the network quality that are caused by redundant or missing neighboring cell configuration, or by incorrect priority. 28.1 Basic Knowledge of CDMA Neighboring Cell Analysis This section describes the basic knowledge of the CDMA neighboring cell analysis, such as the neighboring cell analysis functions, application scenarios, and algorithms for the neighboring cell analysis. The basic knowledge helps you perform the operations related to the CDMA neighboring cell analysis. 28.2 Process of CDMA Co-Frequency Neighboring-Cell Analysis This section describes the process of CDMA co-frequency neighboring-cell analysis. 28.3 Managing CDMA Neighboring Cell Analysis Tasks This section describes how to manage CDMA neighboring cell analysis tasks. You can create, modify, delete, suspend, and resume CDMA neighboring cell analysis tasks. You can also view the status and execution progress of the tasks. 28.4 Query a CDMA Co-Frequency Neighboring Cell Analysis Report The Nastar provides the function of querying CDMA co-frequency neighboring cell analysis reports. You can query the missing and redundant neighboring cells and the neighboring cell priorities that need to be adjusted of a test carrier. Then, you can configure the missing neighboring cells, delete the redundant cells, and adjust the neighboring cell priorities based on the query results. 28.5 Exporting a CDMA Co-Frequency Neighboring Cell Analysis Report
This section describes how to export a CDMA co-frequency neighboring cell analysis report. After querying the co-frequency neighboring cell analysis results, you can export the found analysis results and save them in .csv files or .xls files or export the found analysis results as MML scripts. Based on the exported analysis results or generated MML scripts, you can configure neighboring relations on the network to optimize the neighboring relations between the carriers on the network. 28.6 Reference for the CDMA Neighboring Cell Analysis GUI This section describes the interface for CDMA neighboring cell analysis and the relevant parameters. Before performing relevant operations, you can familiarize yourself with the functions of the CDMA neighboring cell analysis.
28-2
Issue 03 (2010-06-30)
28.1 Basic Knowledge of CDMA Neighboring Cell Analysis

This section describes the basic knowledge of the CDMA neighboring cell analysis, such as the neighboring cell analysis functions, application scenarios, and algorithms for the neighboring cell analysis. The basic knowledge helps you perform the operations related to the CDMA neighboring cell analysis. 28.1.1 CDMA Co-Frequency Neighboring Cell Analysis Functions The MRs of MSs reflect the actual propagation status of radio signals. By using the CDMA cofrequency neighboring cell analysis functions, the Nastar can summarize and analyze the PSMM/ RU messages reported by MSs on the network to check for the redundant and missing neighboring cell configuration of a test carrier and to check for the priorities that need to be adjusted. If this information exists, the system displays the information. This helps you to solve the problems relating to the network quality that are caused by redundant or missing neighboring cell configuration, or by incorrect priority. 28.1.2 CDMA Neighboring Cell Analysis Algorithms This section describes the algorithms related to the analysis of CDMA co-frequency neighboring cells. The algorithms help determine the missing neighboring cells, redundant neighboring cells, and recommended priorities of neighboring cells.
28.1.1 CDMA Co-Frequency Neighboring Cell Analysis Functions

The MRs of MSs reflect the actual propagation status of radio signals. By using the CDMA cofrequency neighboring cell analysis functions, the Nastar can summarize and analyze the PSMM/ RU messages reported by MSs on the network to check for the redundant and missing neighboring cell configuration of a test carrier and to check for the priorities that need to be adjusted. If this information exists, the system displays the information. This helps you to solve the problems relating to the network quality that are caused by redundant or missing neighboring cell configuration, or by incorrect priority.

When an overlapped coverage area with strong signals exists between sectors, handovers may occur between the sectors. In this case, you need to configure neighboring relations. Correct neighboring relations ensure that MSs located at the service boundary of a cell can be switched in time to the neighboring cell that has optimal signals. In this case, handover gains can be obtained and the transmit power of the terminals on the network can be reduced. Thus, QoS and performance of the network are enhanced. Using the configuration data and engineering parameters, the Nastar can analyze the neighboring cells of a selected carrier on the basis of the PSMM/RU messages reported by a MS. By collecting weighted statistics based on handover relations, the Nastar can determine the redundant and missing neighboring cell configuration of a test carrier and the priorities that need to be adjusted. In addition, the Nastar can sequence the recommended priorities of the neighboring cells. By comparing the recommended priorities and the actually configured priorities, you can adjust the final priorities of the neighboring cells on the Nastar client. The Nastar displays results in line or bar chart. It displays both the neighboring cells of different types and the sequence of finally ascertained priorities in different colors. The results of neighboring cell analysis can be exported as a file in .csv or .xls format or be used to generate a script that can be directly used for the network. You can configure neighboring
relations based on the exported file or the generated script to optimize the neighboring relations of the carrier on the network. In measurement results, undefined neighboring cells are identified first by frequencies and pseudo number (PN). On the network, cells that have the same frequency and same PN may exist around a best cell. You need to predict the signal strength based on the site location, antenna azimuth, and antenna gain of these cells and then determine the possible neighboring cells. In addition, you need to export the analysis report on the possible neighboring cells through the Nastar client.
Limitation and Impact

The PSMM message may fail to meet the requirements due to improper PN planning of the existing network, incorrect site configuration and installation, or impacts of geographical locations. Thus, the accuracy of neighboring cell optimization results is affected. In this case, you need to manually confirm or adjust the optimization results (especially at the BSC boundary area or the area where different network modes are adopted) based on the results of neighboring cell analysis. Here, network modes can be GSM, CDMA, and WCDMA. The accuracy of neighboring cell analysis results may be affected in the following cases:
l l
Engineering parameters are incorrect. The air interface parameters during data collection for neighboring cell analysis are not stable. PN-related problems occur. For example, the reuse distance of a same or near PN is excessively short, neighboring cells of the same PN are incorrectly configured, or the PN Oneway/Twoway problem occurs. Neighboring cell data of less than three days (seven days are recommended) is collected.
NOTE
The Nastar can only be used for measuring and analyzing the CDMA co-frequency neighboring cells in the case of soft handover or softer handover.
28.1.2 CDMA Neighboring Cell Analysis Algorithms

This section describes the algorithms related to the analysis of CDMA co-frequency neighboring cells. The algorithms help determine the missing neighboring cells, redundant neighboring cells, and recommended priorities of neighboring cells. The neighboring cell analysis algorithms are the basis for determining the missing neighboring cells, redundant neighboring cells, and recommended priorities of neighboring cells.
l
The algorithm for calculating the recommended priority of a neighboring cell is as follows: 1. Calculate the weighted value of the neighboring cell. The overall score of a neighboring cell is determined together by the appearance times of the neighboring cell, the relative difference between the Ec/Io of the neighboring cell and the Ec/Io of the measurement cell, and the absolute difference between the Ec/Io of the neighboring cell and the Ec/Io of the measurement cell. 2. Sequence the weighted values in descending order. The higher the weighted value is, the higher the priority is. The recommended highest priority is 0. 3. Determine whether the priority of the neighboring cell needs to be adjusted.
28-4
Handovers occur in the neighboring cell. In addition, the neighboring cell is configured in the BAM. When Abs (Recommended priority - Configured priority) 4, you can infer that the priority of the neighboring cell needs to be adjusted.
l
The algorithm for determining a missing neighboring cell is as follows: Handovers occur in the neighboring cell. In addition, the neighboring cell is not configured in the BAM. If the recommended priority of the neighboring cell is smaller than the recommended number of neighboring cells, you can infer that the neighboring cell is a missing neighboring cell.
The algorithm for determining a redundant neighboring cell is as follows: No handover occurs in the neighboring cell. In addition, the neighboring cell is configured in the BAM. If the recommended priority of the neighboring cell is not smaller than the recommended number of neighboring cells, you can infer that the neighboring cell is a redundant neighboring cell.
28.2 Process of CDMA Co-Frequency Neighboring-Cell Analysis

This section describes the process of CDMA co-frequency neighboring-cell analysis. Figure 28-1 shows the process of co-frequency neighboring-cell analysis. Figure 28-1 Workflow of co-frequency neighboring-cell analysis
Start
Set an E2E task
Set a co-frequency neighboring cell analysis task Query a co-frequency neighboring cell analysis report Export a co-frequency neighboring cell analysis report End

Table 28-1 Description of the workflow of co-frequency neighboring-cell analysis No. 1 Procedure Create an endto-end task corresponding to a cofrequency neighboring cell analysis task Description You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a cofrequency neighboring cell analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a co-frequency neighboring cell analysis data importing task. After the task is created, the Nastar periodically imports the co-frequency neighboring cell analysis data files saved on the Nastar server to the database. You can create a co-frequency neighboring cell analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required measurement reports from the Nastar database, and then generates an analysis report through the analysis. You can view the analysis results of the co-frequency neighboring-cell analysis task that is successfully performed, configure missing neighboring cells, delete redundant neighboring cells, and adjust neighboring cell priorities. You can export a co-frequency neighboring-cell analysis report from the Nastar.
Create a cofrequency neighboring cell analysis data importing task Create a cofrequency neighboring cell analysis task
Query a cofrequency neighboring cell analysis report Export a cofrequency neighboring cell analysis report
28.3 Managing CDMA Neighboring Cell Analysis Tasks

This section describes how to manage CDMA neighboring cell analysis tasks. You can create, modify, delete, suspend, and resume CDMA neighboring cell analysis tasks. You can also view the status and execution progress of the tasks. 28.3.1 Creating a CDMA E2E Task This section describes how to create an end-to-end (E2E) task. After you set an E2E task in the Nastar, the Nastar issues MML commands to the M2000. The M2000 then sends these MML commands to the corresponding NEs. Finally, the NEs perform the measurement tasks and generate results. 28.3.2 Creating a CDMA Co-Frequency Neighboring Cell Analysis Task This section describes how to create a CDMA co-frequency neighboring cell analysis task. After a CDMA co-frequency neighboring cell analysis task is created, the Nastar, based on the
configuration data and the engineering parameters, periodically analyzes the PSMMs/RUs reported by UEs on the network to check for the redundant and missing neighboring cell configuration of a test carrier and to check for the priorities that need to be adjusted. By querying the results of an analysis task, you can learn about the overall status of the network and locate the network quality problems that are caused by redundant or missing neighboring cell configuration, or by incorrect priority. 28.3.3 Modifying a CDMA Co-Frequency Neighboring Cell Analysis Task This section describes how to modify the attributes of a CDMA co-frequency neighboring cell analysis task. You can modify the attributes of a CDMA neighboring cell analysis task as required. 28.3.4 Checking a CDMA Co-Frequency Neighboring Cell Analysis Task This section describes how to check a CDMA co-frequency neighboring cell analysis task. You can check the attributes, execution progress, and execution results of a CDMA co-frequency neighboring cell analysis task as required.

Prerequisite
l l l
Context
TIP
Procedure
l
If the OSS list does not contain the created OSS, click Add to create an OSS. OSS Name indicates the name of the OSS to be created.
Issue 03 (2010-06-30)
Port indicates the number of the port on the FTP server where the file to be collected is saved. User Name indicates the user name used for logging in to the M2000 server. Password indicates the password used for logging in to the M2000 server. FTP User indicates the user name used for logging in to the FTP server. FTP Password indicates the password used for logging in to the FTP server.
3.
28-8
Issue 03 (2010-06-30)
Postrequisite
NOTE
28.3.2 Creating a CDMA Co-Frequency Neighboring Cell Analysis Task

This section describes how to create a CDMA co-frequency neighboring cell analysis task. After a CDMA co-frequency neighboring cell analysis task is created, the Nastar, based on the configuration data and the engineering parameters, periodically analyzes the PSMMs/RUs reported by UEs on the network to check for the redundant and missing neighboring cell configuration of a test carrier and to check for the priorities that need to be adjusted. By querying the results of an analysis task, you can learn about the overall status of the network and locate the network quality problems that are caused by redundant or missing neighboring cell configuration, or by incorrect priority.
Prerequisite
l l
Context
l l
Tasks of this type can be performed only once. The system supports a maximum of 50 tasks of this type. The time range of the data to be analyzed must be within seven days.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed.
Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can be only Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects in the object navigation tree on the NE Object Selection tab page.
l
Choose BSC or Carrier Group above the navigation tree to display the objects in the navigation tree as required. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Step 7 Set Recommended Number of Neighboring Cells on the Parameter Setting tab page. Step 8 Click Complete. ----End
Postrequisite
l
Deleting a task This section describes how to delete a neighboring cell analysis task. You can delete the unnecessary neighboring cell analysis tasks to save system resources.
NOTE
The tasks in Running state cannot be deleted.
1.
Choose CDMA Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task This section describes how to suspend a neighboring cell analysis task. To delay the task execution, you can suspend a neighboring cell analysis task that is in idle state. After this operation, the neighboring cell analysis task is in suspended state.
NOTE
1.
28-10
Issue 03 (2010-06-30)
2.
. button is
NOTE
Only the neighboring cell analysis tasks that are in idle state can be scheduled by the system.
1.
2.
The task can be performed only when its Status is Suspend. If the task is not in suspended state, the button is unavailable.
28.3.3 Modifying a CDMA Co-Frequency Neighboring Cell Analysis Task

This section describes how to modify the attributes of a CDMA co-frequency neighboring cell analysis task. You can modify the attributes of a CDMA neighboring cell analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA co-frequency neighboring cell analysis task is created.
Context
Procedure
Step 1 Choose CDMA Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the relevant parameters, see 28.6.3 Parameters for Creating and Modifying CDMA Co-Frequency Neighboring Cell Analysis Tasks.
Issue 03 (2010-06-30)

l
You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the object navigation tree, and the Recommended Number of Neighboring Cells parameter.
28.3.4 Checking a CDMA Co-Frequency Neighboring Cell Analysis Task

This section describes how to check a CDMA co-frequency neighboring cell analysis task. You can check the attributes, execution progress, and execution results of a CDMA co-frequency neighboring cell analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA co-frequency neighboring cell analysis task is created.
Procedure
Step 1 Choose CDMA Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If you need to ... Check the attributes of a neighboring cell analysis task. Then ... Select a task from the task list in the upperright pane. Double-click the task or click .
You can view the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 28.3.3 Modifying a CDMA Co-Frequency Neighboring Cell Analysis Task. Check the execution progress of a task. Select a task from the task list in the upperright pane. Then, you can view the execution progress of the task in the Progress column.
28-12
Issue 03 (2010-06-30)
If you need to ... Check the task execution results.
Then ... Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view all the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
28.4 Query a CDMA Co-Frequency Neighboring Cell Analysis Report

The Nastar provides the function of querying CDMA co-frequency neighboring cell analysis reports. You can query the missing and redundant neighboring cells and the neighboring cell priorities that need to be adjusted of a test carrier. Then, you can configure the missing neighboring cells, delete the redundant cells, and adjust the neighboring cell priorities based on the query results.
Prerequisite
Issue 03 (2010-06-30)
28-13
Procedure
Step 1 Choose CDMA Intra-Frequency Neighboring Cell Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. You can view all the analysis results of a selected task in the lower-right pane. Step 3 Double-click a result, or right-click a result and choose CDMA Intra-Frequency Neighboring Cell Analysis from the shortcut menu. The CDMA Intra-Frequency Neighboring Cell Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select a carrier from the list of test carriers in Area (2) in the CDMA Intra-Frequency Neighboring Cell Analysis window.
l
For details about the rules for dividing areas, see 28.6.1 Interface Description: CDMA CoFrequency Neighboring Cell Analysis. The neighboring cell list in Area (4) displays all the neighboring cells of the selected carrier. Based on the neighboring cell analysis algorithms, the Nastar determines the redundant neighboring cells, the missing neighboring cells, the neighboring cells whose priorities need to be adjusted, and the neighboring cells that require no operations. It also provides the relevant operation suggestions. For details about the neighboring cell analysis algorithms, see 28.1.2 CDMA Neighboring Cell Analysis Algorithms.
If a neighboring cell of the selected carrier is unknown, the Nastar calculates the possible location of the neighboring cell and adds Unknow PN to the corresponding name of the selected carrier in Area (4) to identify the unknown neighboring cell. The figure in Area (5), displays the normal neighboring cells, redundant neighboring cells, missing neighboring cells, and the neighboring cells whose priorities need to be adjusted of the selected carrier in legends in different colors. You can select a parameter from the dropdown list box above Area (5). Then, the parameter values corresponding to each neighboring cell are displayed in a line chart. In the figure, the left axis represents the weighted values of the neighboring cells, the right axis represents the value of the line chart, and the horizontal coordinate represents the names of the neighboring cells. In the figure, the neighboring cells are sequenced in descending order of the weighted values from left to right.
Step 5 Select a neighboring cell whose priority needs to be adjusted in Area (4), and then click the up or down icon above the list to adjust the priority. The adjustment result is saved as a .dat file in the local installation directory.
l
above the list. A dialog box for adding new neighboring cells is displayed. Select Click a carrier and set its priority. Then, click OK. The selected carrier is added to the neighboring cell list according to the preset priority.
28-14
Issue 03 (2010-06-30)
After you adjust the priority of a neighboring cell, you can click above the list to restore the original priority and then the corresponding .dat file is deleted from the local installation directory accordingly.
----End
Postrequisite
l
28.5 Exporting a CDMA Co-Frequency Neighboring Cell Analysis Report

This section describes how to export a CDMA co-frequency neighboring cell analysis report. After querying the co-frequency neighboring cell analysis results, you can export the found analysis results and save them in .csv files or .xls files or export the found analysis results as MML scripts. Based on the exported analysis results or generated MML scripts, you can configure neighboring relations on the network to optimize the neighboring relations between the carriers on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried CDMA co-frequency neighboring cell analysis reports.
Issue 03 (2010-06-30)
Procedure
l Perform the following operations as required. If ... You want to export the general information about a test carrier Then ... 1. Click in the CDMA Intra-Frequency Neighboring Cell Analysis window. The Save dialog box is displayed. 2. Set the filename, file type, and save path, and then click Save. The saved .csv or .xls file is opened automatically so that you can view the information in it. The information in the .csv or .xls file consists of the task name, task creator, execution result, start time, end time, and test carrier information. You want to export the neighboring cell optimization results of a test carrier
l
Exporting the results as a .csv file or an .xls file 1. Click in the CDMA Intra-Frequency Neighboring Cell Analysis window. The Save dialog box is displayed. 2. Set the filename, file type, and save path. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view the information in it. The information in the .csv or .xls file consists of the task name, task creator, execution result, start time, end time, and test carrier information.
Exporting the results as MML scripts in the CDMA Intra-Frequency 1. Click Neighboring Cell Analysis window. Choose Export Optimized Script. The Export Script - Export Optimized Script dialog box is displayed. 2. Set the save path of the scripts and the neighboring-cell analysis results to be exported, and then click OK. The system saves the neighboring-cell analysis results as MML scripts.
28-16
Issue 03 (2010-06-30)
If ...
Then ...
You want to export the manually 1. Click in the CDMA Intra-Frequency adjusted neighboring cell Neighboring Cell Analysis window. Choose optimization results of a test carrier Export Manually Adjusted Script. The Export Script - Export Manually Adjusted Script dialog box is displayed. 2. Set the save path of the scripts and script objects, and then click OK. The system saves the neighboring-cell analysis results as MML scripts. You want to export all neighboring cell analysis results 1. Click in the CDMA Intra-Frequency Neighboring Cell Analysis window. The Save dialog box is displayed. If the data amount of the analysis results of all the neighboring cells is large, you need to wait for a while for the dialog box to appear. 2. Set the filename and save path, and then click Save. You are allowed to save all the neighboringcell analysis results only as .xls files by test carrier. The analysis results of each test carrier corresponds to one .xls file. The file is named task name_test carrier name_NbrInfo.xls. Export the information about the possible neighboring cells of a best cell 1. Click in the CDMA Intra-Frequency Neighboring Cell Analysis window. The Save dialog box is displayed. 2. Set the name, type and save path of the file. Then, click Save. After being saved, a CSV or XLS file is automatically open so that you can view the file conveniently. The CSV or XLS file contains the following information: the task name, creator, start time and end time of the results, and possible neighboring cells of the test carrier.
Issue 03 (2010-06-30)
28-17

NOTE
l l l
Exporting the general information about a test carrier refers to exporting the information about all the test carriers involved in the selected analysis task. Exporting the neighboring cell optimization results of a test carrier refers to exporting the information about the neighboring cells of a specified test carrier. Exporting the manually adjusted neighboring cell optimization results of a test carrier refers to exporting the neighboring cell optimization results that are manually adjusted from all the neighboring cell analysis results of a specified test carrier. Exporting all neighboring cell analysis results refers to exporting the information about all the test carriers and the information about the neighboring cells of the test carriers. Exporting the analysis results of possible neighboring cells refers to exporting the information about the possible neighboring cells of a test carrier.
l l
----End
28.6 Reference for the CDMA Neighboring Cell Analysis GUI

This section describes the interface for CDMA neighboring cell analysis and the relevant parameters. Before performing relevant operations, you can familiarize yourself with the functions of the CDMA neighboring cell analysis. 28.6.1 Interface Description: CDMA Co-Frequency Neighboring Cell Analysis This section describes the interface for CDMA co-frequency neighboring cell analysis. Before performing relevant operations, familiarize yourself with the rules for dividing areas on the interface. 28.6.2 Parameters of CDMA E2E Tasks This section describes the parameters of CDMA E2E tasks. You can refer to the description when creating or modifying a CDMA E2E task. 28.6.3 Parameters for Creating and Modifying CDMA Co-Frequency Neighboring Cell Analysis Tasks This section describes the parameters for creating and modifying CDMA co-frequency neighboring cell analysis tasks. You can refer to the description when creating or modifying a CDMA co-frequency neighboring cell analysis task. 28.6.4 Parameters for Querying CDMA Co-Frequency Neighboring Cell Analysis Reports This section describes the parameters for querying CDMA co-frequency neighboring cell analysis reports. You can refer to the description when querying CDMA co-frequency neighboring cell analysis reports.
28.6.1 Interface Description: CDMA Co-Frequency Neighboring Cell Analysis

This section describes the interface for CDMA co-frequency neighboring cell analysis. Before performing relevant operations, familiarize yourself with the rules for dividing areas on the interface. The analysis results of co-frequency neighboring cells can be displayed in tables or in line charts, as shown in Figure 28-2.
Figure 28-2 Interface for the co-frequency neighboring cell analysis
Description Consists of five buttons that are used for exporting overview data of measured carrier, neighboring cell analysis data, all neighboring analysis data, neighboring cell script and analysis results of possible neighboring cells.
(2)
Current test carrier information list Displays the information related to the current test carrier. Button area Consists of three buttons used for adjusting the priorities of neighboring cells and saving adjustment results. Displays all the co-frequency neighboring cells of the carrier selected in area (2).
(3)
(4)
Neighboring cell list
Issue 03 (2010-06-30)
28-19
No. Name (5) Image area
Description Displays the information about all the neighboring cells of the selected test carrier in the combination of line charts.
NOTE If a neighboring cell of the selected carrier is unknown, the Nastar calculates the possible location of the neighboring cell and adds Unknow PN to the corresponding name of the selected carrier in Area (2) to identify the unknown neighboring cell.

Parameter Basic Information Task Name OSS Name E2E Task List Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task. Indicates the types of E2E tasks. You can select one of the following E2E tasks: VIP subscriber monitoring task, interference data task, spectrum data task, 1x neighboring cell data task, DO neighboring cell data task, or complaint analysis data task. Indicates the time when the task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must be earlier than the end time. NE Object Indicates the NE related to the E2E task.
Begin Time
28.6.3 Parameters for Creating and Modifying CDMA CoFrequency Neighboring Cell Analysis Tasks
This section describes the parameters for creating and modifying CDMA co-frequency neighboring cell analysis tasks. You can refer to the description when creating or modifying a CDMA co-frequency neighboring cell analysis task.
Parameter Basic Information Task Name Description Indicates the name of a neighboring cell analysis task. Value range:
l l
l l
Task Type
Choose CDMA Intra-Frequency Neighboring Cell Analysis Task from the Task Type navigation tree. Such a task can be executed only once in a time segment. Indicates the description of the task. Value range:
l l
Execution Type Note
Time Information
Data Time Scope
The start time must be earlier than the end time. You can either type the time in this field, or click to select the date and time in the Date Selection dialog box. This parameter is valid for only one-time tasks.
Task Start At
Indicates the time when the analysis task is executed. This start time must be equal to or later than the end time specified by Data Time Scope.
Object Information
BSC Carrier Group
If you select this option, the navigation tree displays all the BSCs on the entire network. If you select this option, the navigation tree displays all the carrier groups on the entire network. Indicates the number of neighboring cells that you are recommended to configure. This parameter can be any integer ranging from 1 to 40. The default value is 20.
Recommended Number of Neighboring Cells
Issue 03 (2010-06-30)
28-21
28.6.4 Parameters for Querying CDMA Co-Frequency Neighboring Cell Analysis Reports
This section describes the parameters for querying CDMA co-frequency neighboring cell analysis reports. You can refer to the description when querying CDMA co-frequency neighboring cell analysis reports.
Parameters related to the general information about a test carrier

Parameter MSC Where Test Carrier Is Located BSC Where Test Carrier Is Located Test Carrier Name Number of Missing Neighboring Cells Number of Redundant Neighboring Cells Number of Neighboring Cells Whose Priorities Are Adjusted Description Indicates the name of the MSC that the test carrier belongs to. Indicates the name of the BSC that the test carrier belongs to, for example, BSC_1. Indicates the name of the test carrier, for example, Carrier_1. Indicates the number of missing intra-frequency neighboring cells among the undefined neighboring cells of the test carrier. Indicates the number of redundant intra-frequency neighboring cells among the defined neighboring cells of the test carrier. Indicates the number of neighboring cells that are specified as Adjusted Priority in the detailed neighboring cell list of the test carrier.

Parameter Neighboring Cell Name Weighted Value Handoff Count Suggestion by Tool Recommended Priority Configured Priority Description Indicates the name of a neighboring cell. Indicates the weighted value calculated through the neighboring cell weighted algorithm. Indicates the number of handovers of a neighboring cell. Lists the recommended operations on a neighboring cell and displays whether the neighboring cell is defined. Indicates the recommended priority of a neighboring cell based on the weighted value of the neighboring cell. The higher the weighted value, the higher is the recommended priority. Indicates the priority of an intra-frequency neighboring cell in the configuration data.
28-22
Issue 03 (2010-06-30)
Parameter Adjusted Priority Average EcIo Distance (km) MSC ID BTS ID Cell ID Sector ID ARFCN Band
Description Indicates the final priority after the manual adjustment based on the recommended priority. Indicates the average Ec/Io of a neighboring cell in all the MRs that contain the information about this neighboring cell. Indicates the distance between the test carrier and the current neighboring cell. Indicates the ID of the MSC that a neighboring cell belongs to. Indicates the ID of the BTS that a neighboring cell belongs to. Indicates the ID of a neighboring cell. Indicates the ID of the sector that a neighboring cell belongs to. Indicates the ARFCN of a neighboring cell. Indicates the band of a neighboring cell. The value 0 represents 800 MHz, the value 1 represents 1900 MHz, and the value 5 represents 450 MHz.
Issue 03 (2010-06-30)
28-23
29 CDMA Complaint Analysis Support
29
CDMA Complaint Analysis Support
About This Chapter

CDMA complaint analysis support involves managing complaint analysis support tasks and querying CDMA complaint analysis support reports. After receiving a subscriber complaint, the Nastar quickly locates the relevant calls, which are recorded before and after the complaint, of the subscriber. By querying the call records, the Nastar helps you analyze the possible cause, locate and solve the problem, and thus improve the efficiency of handling complaints. 29.1 Basic Knowledge of CDMA Complaint Analysis Support The CDMA complaint analysis support function helps you to analyze the subscriber calls that are recorded before and after a complaint and to locate and rectify the fault. This improves the efficiency of handling complaint and increases user satisfaction. 29.2 Process of CDMA Complaint Analysis Support This section describes the process of CDMA complaint analysis support. 29.3 Managing CDMA Complaint Analysis Support Tasks This section describes how to manage CDMA complaint analysis support tasks. You can create, modify, delete, suspend, and resume CDMA complaint analysis support tasks. You can also view the status and execution progress of such tasks. 29.4 Querying a Complaint Analysis Support Report This section describes how to query a complaint analysis support report. After receiving a complaint, the system quickly finds the CHRs related to the complaint. You can query the CHRs to analyze the possible causes of the complaint, locates and solves the problem quickly. This facilitates the complaint handling. 29.5 Reference for the CDMA Complaint Analysis Support GUI This section describes the interface for CDMA complaint analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA complaint analysis support.
Issue 03 (2010-06-30)
29-1
29.1 Basic Knowledge of CDMA Complaint Analysis Support

The CDMA complaint analysis support function helps you to analyze the subscriber calls that are recorded before and after a complaint and to locate and rectify the fault. This improves the efficiency of handling complaint and increases user satisfaction. You can group the call history record (CHR) counters based on the requirements on services so that you can perform analyses based on different service requirements. The compliant assistant analysis function can quickly locate the relevant CHRs before and after a complaint or locate all the CHRs that are related to a faulty cell based on the International Mobile Subscriber Identity (IMSI), the number of the MS, or the Equipment Serial Number (ESN). The Nastar provides the information about the key event of each call, call path, and MR that is sent before the call is released. By analyzing the information, the Nastar helps you to locate and rectify faults. This improves the efficiency of handling complaint and increases user satisfaction.
29.2 Process of CDMA Complaint Analysis Support

This section describes the process of CDMA complaint analysis support. Figure 29-1 shows the process of complaint analysis support. Figure 29-1 Workflow of complaint analysis support
29-2
Issue 03 (2010-06-30)
Table 29-1 Description of the workflow of complaint analysis support No. 1 Procedure Create a complaint analysis support task Query a complaint analysis support report Description You can create a complaint analysis support task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required subscriber calls from the Nastar database, and then generates an analysis report through the analysis. After the Nastar receives a complaint, you can query the corresponding complaint analysis support report to quickly find the call history records (CHRs) related to the complaint. Then, you can analyze the CHRs to find the possible causes of the complaint, locate the problem, and solve the problem quickly. This facilitates the complaint handling. You can export a complaint analysis support report from the Nastar.
Export a complaint analysis support report
29.3 Managing CDMA Complaint Analysis Support Tasks

This section describes how to manage CDMA complaint analysis support tasks. You can create, modify, delete, suspend, and resume CDMA complaint analysis support tasks. You can also view the status and execution progress of such tasks. 29.3.1 Creating CDMA Complaint Analysis Support Tasks By creating CDMA complaint analysis support tasks, you can enable the Nastar to quickly locate the relevant calls, which are recorded before and after a complaint, of the subscriber after receiving the complaint. By querying the call records, the Nastar helps you analyze the possible cause and thus locate and solve the problem. 29.3.2 Modifying CDMA Complaint Analysis Support Tasks This section describes how to modify the attributes of a CDMA complaint assistant analysis task. You can modify the attributes of a CDMA complaint assistant analysis task as required. 29.3.3 Checking CDMA Complaint Analysis Support Tasks This section describes how to check CDMA complaint analysis support tasks. You can check the attributes, the execution progress, and the execution result of a CDMA complaint analysis support task.
29.3.1 Creating CDMA Complaint Analysis Support Tasks

By creating CDMA complaint analysis support tasks, you can enable the Nastar to quickly locate the relevant calls, which are recorded before and after a complaint, of the subscriber after receiving the complaint. By querying the call records, the Nastar helps you analyze the possible cause and thus locate and solve the problem.
Issue 03 (2010-06-30)
29-3
Prerequisite
l l
You have logged in to the Nastar client. The relevant trace tasks are already opened on NEs.
Context
l l
Tasks of this type can be performed only once. The system supports a maximum of 50 tasks of this type. The time range of the data to be analyzed cannot exceed seven days. The task for importing the CDMA complaint analysis data is created by the system. You need not create the task.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can be only Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Set OSS name and BSC name. Step 7 Click Next. Step 8 On the Filter by VIP tab page, perform the following operations: 1. Select Start Filtering by User. The filtering condition can be Subscriber, IMSI, ESN, MEID, or any combination of these four options. Click Select from VIPs or VIP groups, select one or more VIP subscribers or subscriber groups, and then click OK. The Nastar filters the subscriber IDs based on the selected filtering condition and displays the results on the right area. Select Start Filtering by NE. The filtering condition can be Accessed Carriers or Released Carriers. Select one or more carriers from the navigation tree.
2.
Step 9 On the Filter by NE tab page, perform the following operations: 1. 2.
Step 10 Select one or more counter sets on the Select Counters to Be Queried tab page. Step 11 Click Complete. ----End
Postrequisite
l
Deleting a task
29-4
You can delete a complaint analysis support task that is not required so that you can save system resources.
NOTE
The tasks that are in the Running status cannot be deleted.
1.
Choose CDMA Complaint Analysis Support Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
Suspending a task To delay the task execution, you can suspend a complaint analysis support task that is in the idle state. After this operation, the complaint analysis support task is in the suspended state.
NOTE
The system can schedule only the complaint assistant analysis tasks that are not suspended.
1.
2.
. button is
Resuming a task You can resume a suspended complaint analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
1.
2.
29.3.2 Modifying CDMA Complaint Analysis Support Tasks

This section describes how to modify the attributes of a CDMA complaint assistant analysis task. You can modify the attributes of a CDMA complaint assistant analysis task as required.
Issue 03 (2010-06-30)
29-5
Prerequisite
l l
You have logged in to the Nastar client. A CDMA complaint analysis support task is created.
Context
Procedure
Step 1 Choose CDMA Complaint Assistant Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameter settings.
l
. The
For details about the relevant parameters, see 29.5.2 Parameters for Creating and Modifying CDMA Complaint Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the filtering conditions, and the output counter sets.
29.3.3 Checking CDMA Complaint Analysis Support Tasks

This section describes how to check CDMA complaint analysis support tasks. You can check the attributes, the execution progress, and the execution result of a CDMA complaint analysis support task.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA complaint analysis support task is created.
Procedure
Step 1 Choose CDMA Complaint Analysis Support Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required:
Purpose
Operation
Check the attributes of a CDMA complaint Select a task from the task list in the upper-right analysis support task. pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 29.3.2 Modifying CDMA Complaint Analysis Support Tasks. Checking the execution progress of the active task Select a task from the task list in the upper-right pane. Then, you can view the execution progress of the task in the Progress column. Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view all the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
29.4 Querying a Complaint Analysis Support Report

This section describes how to query a complaint analysis support report. After receiving a complaint, the system quickly finds the CHRs related to the complaint. You can query the CHRs
to analyze the possible causes of the complaint, locates and solves the problem quickly. This facilitates the complaint handling.
Prerequisite
Procedure
Step 1 Choose CDMA Complaint Assistant Analysis Task from the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. All the analysis results of the selected task are displayed in the lower-right pane. Step 3 Double-click or right-click an analysis result, and then choose CDMA Complaint Analysis Support from the shortcut menu. The CDMA Complaint Assistant Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 In the CDMA Complaint Analysis Support window, click the 1X item or DO item tab to view the counter information related to the analysis task.
l l
The 1X item tab page displays all the 1x counter information involved in the analysis task. The DO item tab page displays all the DO connection level counter information and DO streaming level counter information involved in the analysis task.
----End
Postrequisite
l
The system enables you to export query results. Right-click the query result list, and then choose Save As from the shortcut menu. After setting the save path and filename, click Save. Then, the query results are saved as a .csv or an .xls file. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Then, type the keywords, that is, the search conditions, in the dialog box. The system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the typed keywords are case sensitive. You can select Up or Down in the Direction area to define the search area.
29.5 Reference for the CDMA Complaint Analysis Support GUI

This section describes the interface for CDMA complaint analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA complaint analysis support. 29.5.1 Interface for CDMA Complaint Analysis Support
This describes the interface for CDMA complaint assistant analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. 29.5.2 Parameters for Creating and Modifying CDMA Complaint Analysis Tasks This section describes the parameters for creating and modifying CDMA complaint analysis support tasks. You can refer to the description when creating or modifying a CDMA complaint analysis support task. 29.5.3 Parameters for Querying a CDMA Complaint Analysis Support Report This section describes the parameters for querying a CDMA complaint analysis support report. You can refer to the description when a CDMA complaint analysis support report.
29.5.1 Interface for CDMA Complaint Analysis Support

This describes the interface for CDMA complaint assistant analysis. Before performing relevant operations, familiarize yourself with the functions of the areas on the interface. The complaint analysis support result interface displays in the 1X item and DO item tabs, as shown in Figure 29-2 and Figure 29-3. Figure 29-2 Interface for the complaint analysis support (1)
The 1X item tab page displays all the 1x counter information involved in the analysis task.
Issue 03 (2010-06-30)
29-9
Figure 29-3 Interface for the complaint analysis support (2)
The DO item tab page displays all the DO connection level counter information and DO streaming level counter information involved in the analysis task.
29.5.2 Parameters for Creating and Modifying CDMA Complaint Analysis Tasks
This section describes the parameters for creating and modifying CDMA complaint analysis support tasks. You can refer to the description when creating or modifying a CDMA complaint analysis support task.
Parameter Basic Information Task Name Description Indicates the name of a complaint analysis support task. Value range:
l l
l l
Choose CDMA Complaint Analysis Support Task from the navigation tree. Such a task can be executed only once in a time segment.
Issue 03 (2010-06-30)
29-10
Parameter Note

l l
Time Information
Data Time Scope
Task Start At
Indicates the time when the analysis task is executed. The time specified in this field should not precede the end time specified in the Data Time Scope field.
Filtering Information by User
Start Filtering by User Filtering Condition Setting Select from VIPs or VIP groups
If you select this option, the Nastar filters the calls based on the selected filtering condition. The filtering condition can be Subscriber, IMSI, ESN, MEID, or any combination of these four options. If you select this option, the Nastar filters the required MS numbers from the selected VIP subscribers. If you select this option, the Nastar filters the NEs based on the selected filtering condition. The filtering condition can be Accessed Carriers, Released Carriers, or a combination of the two options. You can select a set of counters to be exported based on the service requirement.
Filtering Information by NE
Start Filtering by NE Filtering Condition Setting Select Counters to Be Queried
Counter Information
29.5.3 Parameters for Querying a CDMA Complaint Analysis Support Report

This section describes the parameters for querying a CDMA complaint analysis support report. You can refer to the description when a CDMA complaint analysis support report.
Issue 03 (2010-06-30)
29-11
Parameters related to the general information about a test carrier

Parameter MSC Where Test Carrier Is Located BSC Where Test Carrier Is Located Test Carrier Name Number of Missing Neighboring Cells Number of Redundant Neighboring Cells Number of Neighboring Cells Whose Priorities Are Adjusted Description Indicates the number of the MSC that the test carrier belongs to. Indicates the name of the BSC that the test carrier belongs to, for example, BSC_1. Indicates the name of the test carrier, for example, Carrier_1. Indicates the number of missing co-channel neighboring cells among the undefined neighboring cells of the test carrier. Indicates the number of redundant co-channel neighboring cells among the defined neighboring cells of the test carrier. Indicates the number of neighboring cells that are specified as Priority Adjusting in the detailed neighboring cell list of the test carrier.

Parameter Neighboring Cell Name Weighted Value Handoff Count Suggestion by Tool Recommended Priority Configured Priority Final Priority Average EcIo Description Indicates the name of a neighboring cell. Indicates the weighted value calculated through the neighboring-cell weighted algorithm. Indicates the number of handovers of a neighboring cell. Lists the recommended operations on a neighboring cell and displays whether the neighboring cell is defined. Indicates the recommended priority of a neighboring cell based on the weighted value of the neighboring cell. The higher the weighted value, the higher is the recommended priority. Indicates the priority of an co-channel neighboring cell in the configuration data. Indicates the final priority after the manual adjustment based on the recommended priority. Indicates the average Ec/Io of a neighboring cell in all the MRs that contain the information about this neighboring cell. Unit: dBm Distance (m) Indicates the distance between the carrier and the current neighboring cell.
29-12
Parameter MSC ID BTS ID Cell ID Sector ID Frequency Point Band
Description Indicates the number of the MSC that a neighboring cell belongs to. Indicates the number of the BTS that a neighboring cell belongs to. Indicates the ID of a neighboring cell. Indicates the ID of the sector that a neighboring cell belongs to. Indicates the frequency of a neighboring cell. Indicates the band of a neighboring cell. The value 0 represents 800 MHz, the value 1 represents 1900 MHz, and the value 5 represents 450 MHz.
Issue 03 (2010-06-30)
29-13
30 CDMA Pilot Pollution Analysis
30
CDMA Pilot Pollution Analysis
About This Chapter

This section describes the CDMA pilot pollution analysis, including the management of pilot pollution analysis tasks and the query and export of pilot pollution analysis reports. Through the analysis of subscriber calls, the Nastar identifies the carriers where pilot pollution exists, the carriers that cause interference, and the interference strength. The Nastar also displays the analysis results on a map so that you can learn the detailed situation of pilot pollution. This reduces the DT time and improves the problem location accuracy. 30.1 Basic Knowledge of CDMA Pilot Pollution Analysis The CDMA pilot pollution analysis function enables you to analyze routine calls. Through the analysis of query reports, the Nastar identifies the carriers where pilot pollution exists, the carriers that cause interference, and the interference strength and displays the analysis results on a map. In this manner, you can directly learn the details about pilot pollution. 30.2 CDMA Pilot Pollution Analysis Process This section describes the CDMA pilot pollution analysis process. 30.3 Managing CDMA Pilot Pollution Analysis Tasks This section describes how to manage CDMA pilot pollution analysis tasks. You can create, modify, delete, suspend, and restore CDMA pilot pollution analysis tasks. You can also view the status and execution progress of such tasks. 30.4 Querying CDMA Pilot Pollution Analysis Reports This section describes how to query CDMA pilot pollution analysis reports. The Nastar analyzes the carriers where pilot pollution exists, the carriers that cause interference, and the interference strength by obtaining the subscriber call records. This helps to solve the pilot pollution caused by factors such as cross coverage. 30.5 Exporting CDMA Pilot Pollution Analysis Reports This section describes how to export CDMA pilot pollution analysis reports. You can export the queried pilot pollution analysis results as .xls files as required. The exported pilot pollution analysis results can then assist you in determining the carriers where the pilot pollution exists, the carriers that cause interference, and the interference strength. 30.6 Reference for the CDMA Pilot Pollution Analysis
Issue 03 (2010-06-30)
30-1
This section describes the interface for CDMA pilot pollution analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA pilot pollution analysis.
30-2
Issue 03 (2010-06-30)
30.1 Basic Knowledge of CDMA Pilot Pollution Analysis

The CDMA pilot pollution analysis function enables you to analyze routine calls. Through the analysis of query reports, the Nastar identifies the carriers where pilot pollution exists, the carriers that cause interference, and the interference strength and displays the analysis results on a map. In this manner, you can directly learn the details about pilot pollution. Pilot pollution refers to the situation that there are excessive signals with close strength in an area in a CDMA network. Generally, excessive radio signals form a cross coverage to the neighboring carriers due to improper site layout or impacts of geographical locations. In this case, pilot pollution is produced. The pilot pollution affects network performance in the following aspects:
l
Reduced call connection ratio When pilot pollution exists, the MS constantly performs cell reselection because it cannot stably camp on a carrier. During a call, the MS frequently changes serving carriers, thus easily leading to call failure.
Increased call drop rate When pilot pollution exists, ping-pong hangovers occur frequently during a call because the pilot is not strong enough to be the dominant pilot. As a result, the call drop rate increases.
Reduced system capacity Pilot pollution causes strong interference. Hence, the receive sensitivity of the system is improved, and thus signals far away from the BTS cannot be received. As a result, the system capacity is reduced.
High Block Error Rate (BLER) When there is pilot pollution, there is strong interference. Hence, the BLER is increased, leading to the deterioration of the voice quality and the decrease in the data transmission rate.
Severe pilot pollution may cause problems such as call drops, deteriorated voice quality, reduced system capacity, and network interference. Based on routine calls, the Nastar analyzes the pilot pollution, thus helping in locating polluted carriers and polluter carriers. Used with the GIS, this function enables the Nastar to geographically display polluted carriers and polluter carriers, thus improving the efficiency of problem analysis and location. The results of pilot pollution analysis can be exported as .xls files. In this case, users can optimize problem carriers in the network according to the exported analysis results.
30.2 CDMA Pilot Pollution Analysis Process

This section describes the CDMA pilot pollution analysis process. Figure 30-1 shows the CDMA pilot pollution analysis process.
Issue 03 (2010-06-30)
30-3
Figure 30-1 Process of CDMA pilot pollution analysis
Table 30-1 describes the items in the flowchart. Table 30-1 Description of CDMA pilot pollution analysis process No. 1 Procedure Querying NE data information Description In the Analysis Task Management window on the Nastar client, you can switch to the data query window to query whether the raw data required for the pilot pollution analysis is imported to the database.
30-4
Issue 03 (2010-06-30)
No. 2
Procedure Creating an E2E task for the pilot pollution analysis
Description On the Nastar client, choose Maintenance > E2E Task Management. In the displayed E2E Task Management window, you can create an E2E task of pilot pollution analysis. After the task is created, the Nastar issues MML commands to the M2000, and then the M2000 issues MML commands to NEs. Finally, the NEs execute the measurement task and generate results. After an E2E task is created, you can view the corresponding collection task that has been created by the system in the Task Management window. A data import task can be performed only after the corresponding collection task is complete. On the Nastar client, choose Maintenance > Task Management. In the displayed Task Management window, you can create a data import task corresponding to the pilot pollution analysis task so that the Nastar can periodically import the pilot pollution analysis data saved as files on the Nastar server to the database. In the Analysis Task Management window on the Nastar client, you can create pilot pollution analysis tasks. After obtaining the related analysis data from the database, the Nastar analyzes data and then generates the analysis result. You can view the analysis results of the pilot pollution analysis tasks that are executed successfully and also perform comprehensive analysis together with maps. In addition, you can export the result files through the one-key method in the analysis result query interface.
Creating a task of importing pilot pollution analysis data
Creating a pilot pollution analysis task Querying pilot pollution analysis reports
Exporting pilot pollution analysis reports
You can export analysis result files in the Nastar.
30.3 Managing CDMA Pilot Pollution Analysis Tasks

This section describes how to manage CDMA pilot pollution analysis tasks. You can create, modify, delete, suspend, and restore CDMA pilot pollution analysis tasks. You can also view the status and execution progress of such tasks. 30.3.1 Creating a CDMA E2E Task This section describes how to create an end-to-end (E2E) task. After you set an E2E task in the Nastar, the Nastar issues MML commands to the M2000. The M2000 then sends these MML commands to the corresponding NEs. Finally, the NEs perform the measurement tasks and generate results. 30.3.2 Creating CDMA Pilot Pollution Analysis Tasks This section describes how to create CDMA pilot pollution analysis tasks. In a CDMA pilot pollution analysis task, the Nastar analyzes the carriers where pilot pollution exists, the carriers that cause interference, and the interference strength by obtaining the subscriber call records.
This helps to solve the pilot pollution problems caused by factors such as cross coverage, thus reducing the DT time and improving the problem location accuracy. 30.3.3 Modifying CDMA Pilot Pollution Analysis Tasks This section describes how to modify the attributes of the created CDMA pilot pollution analysis tasks. You can modify the attributes of the created CDMA pilot pollution analysis tasks as required. 30.3.4 Checking CDMA Pilot Pollution Analysis Tasks This section describes how to check CDMA pilot pollution analysis tasks. You can check the attributes, execution progress, and execution results of a CDMA pilot pollution analysis task as required.

Prerequisite
l l l
Context
TIP
Procedure
l
If the OSS list does not contain the created OSS, click Add to create an OSS. OSS Name indicates the name of the OSS to be created. Port indicates the number of the port on the FTP server where the file to be collected is saved. User Name indicates the user name used for logging in to the M2000 server.
30-6

l
Password indicates the password used for logging in to the M2000 server. FTP User indicates the user name used for logging in to the FTP server. FTP Password indicates the password used for logging in to the FTP server.
3.
Postrequisite
After an E2E task is created, you can view that the corresponding collection task has been created by the system in the Task Management window. You can perform a data import task only after the corresponding collection task is complete.
NOTE
30.3.2 Creating CDMA Pilot Pollution Analysis Tasks

This section describes how to create CDMA pilot pollution analysis tasks. In a CDMA pilot pollution analysis task, the Nastar analyzes the carriers where pilot pollution exists, the carriers that cause interference, and the interference strength by obtaining the subscriber call records. This helps to solve the pilot pollution problems caused by factors such as cross coverage, thus reducing the DT time and improving the problem location accuracy.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the pilot pollution analysis function. The E2E task, collection task, and data import task corresponding to the pilot pollution analysis task are normal. The VIP analysis task can be created successfully even if the prerequisites are not met. The execution of the VIP analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l l
Tasks of this type can be performed only once. A maximum of 50 tasks of this type can be created and the time range of the data in a task cannot exceed seven days. Before you create an analysis task, check to ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed.
Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can only be Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects in the object navigation tree on the tab page.
l
Choose BSC or Carrier Group above the navigation tree to display the objects in the navigation tree as required. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Postrequisite
l
Deleting a task You can delete an unnecessary pilot pollution analysis task to release system resources.
NOTE
1.
Click the CDMA Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
button.
Suspending a task To delay the task execution, you can suspend a pilot pollution analysis task that is in the idle state. Then, the pilot pollution analysis task becomes a suspended task.
NOTE
The system can schedule only the pilot pollution analysis tasks that are not suspended.
1.
2.
button.

l
Restoring a task You can restore a suspended pilot pollution analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the pilot pollution analysis tasks that are in the idle state can be scheduled by the system.
1.
2.
button.
30.3.3 Modifying CDMA Pilot Pollution Analysis Tasks

This section describes how to modify the attributes of the created CDMA pilot pollution analysis tasks. You can modify the attributes of the created CDMA pilot pollution analysis tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the pilot pollution analysis function. A CDMA pilot pollution analysis task is created.
Context
Procedure
Step 1 Click the CDMA Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 30.6.2 Parameters for Creating and Modifying CDMA Pilot Pollution Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, and the information about the NE object selection.

30.3.4 Checking CDMA Pilot Pollution Analysis Tasks

This section describes how to check CDMA pilot pollution analysis tasks. You can check the attributes, execution progress, and execution results of a CDMA pilot pollution analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA pilot pollution analysis task is created.
Procedure
Step 1 Click the CDMA Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Check the attributes of a CDMA pilot pollution analysis task Then ... Select a task from the task list in the upper-right pane. Double-click the task or click .
You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 30.3.3 Modifying CDMA Pilot Pollution Analysis Tasks. Check the execution progress of the active Select a task from the task list in the upper-right task pane. Then, you can view the execution progress of the task in the Progress column. Check the task execution results Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
30.4 Querying CDMA Pilot Pollution Analysis Reports

This section describes how to query CDMA pilot pollution analysis reports. The Nastar analyzes the carriers where pilot pollution exists, the carriers that cause interference, and the interference strength by obtaining the subscriber call records. This helps to solve the pilot pollution caused by factors such as cross coverage.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the pilot pollution analysis function. The pilot pollution analysis task is executed successfully.
Procedure
Step 1 Click the CDMA Pilot Pollution Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. The analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose Analysis Result from the shortcut menu. The CDMA Pilot Pollution Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 View the overview and details on polluted carriers and polluter carriers in the CDMA Pilot Pollution Analysis Task window.
l
Initially, the polluted carrier overview table is displayed on the left and the polluter carrier details table is displayed on the right of the CDMA Pilot Pollution Analysis Task window. in the upper left corner of the window to switch the display mode, namely, You can click polluter carrier overview table on the left and polluted carrier details table on the right.
30-12
Issue 03 (2010-06-30)

l
You can select a polluted carrier on the left to view all the polluter cells of the selected carrier on the right. In the polluter carrier details table, select a polluter carrier, and then click in the upper left corner of the window to view the carriers that are polluted by the selected polluter carrier.
For description of the parameters, see 30.6.3 Parameters for Querying CDMA Pilot Pollution Analysis Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 30.5 Exporting CDMA Pilot Pollution Analysis Reports. The system enables you to search for the query results. You can click any line of the query result list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you typed are case sensitive. You can select Up or Down in the Direction area to determine the direction of the search.
30.5 Exporting CDMA Pilot Pollution Analysis Reports

This section describes how to export CDMA pilot pollution analysis reports. You can export the queried pilot pollution analysis results as .xls files as required. The exported pilot pollution analysis results can then assist you in determining the carriers where the pilot pollution exists, the carriers that cause interference, and the interference strength.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the CDMA pilot pollution analysis reports.
Procedure
l Export the pilot pollution analysis report by using the shortcut icon. Initially, the polluted cell overview table is displayed on the left and the polluter cell details table is displayed on the right of the CDMA Pilot Pollution Analysis Task window. You to switch the display mode, that is, polluter cell overview table on the left and can click polluted cell details table on the right.
Issue 03 (2010-06-30)
30-13
If You Want to ... Export polluted carrier overview table - polluter carrier details table
Then ... 1. Click in the CDMA Pilot Pollution Analysis Task window. The Save dialog box is displayed. 2. Set the name and save path of the file. Then, click Save. The saved .xls file is opened automatically so that you can view it conveniently. The main information contained in the .xls file is task name, creator, start time of the result, end time of the result, and polluted carrier overview table - polluter carrier details table.
Export polluter carrier overview table - polluted carrier details table.
1. In the CDMA Pilot Pollution Analysis Task window, click to switch the display mode of the information on the left and that on the right. 2. Click . The Save dialog box is displayed.
3. Set the name and save path of the file. Then, click Save. The saved .xls file is opened automatically so that you can view it conveniently. The main information contained in the .xls file is task name, creator, start time of the result, end time of the result, and polluter carrier overview table - polluted carrier details table. l Export the list by using the shortcut menu. 1. 2. Right-click the query result list in the CDMA Pilot Pollution Analysis Task window and then choose Save As... from the shortcut menu. The Save dialog box is displayed. Set a file name and specify the save path and file type. Then, click Save. You are only allowed to save all the pilot pollution analysis results as .xls files on the basis of BSC. The pilot pollution analysis results of each BSC correspond to one .xls file. The naming convention is task name_BSC name_pollution.xls. ----End
30.6 Reference for the CDMA Pilot Pollution Analysis

This section describes the interface for CDMA pilot pollution analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA pilot pollution analysis.
30.6.1 Parameters of CDMA E2E Tasks This section describes the parameters of CDMA E2E tasks. You can refer to the description when creating or modifying a CDMA E2E task. 30.6.2 Parameters for Creating and Modifying CDMA Pilot Pollution Analysis Tasks This section describes the parameters for creating and modifying CDMA pilot pollution analysis tasks. You can refer to this description when creating and modifying a CDMA pilot pollution analysis task. 30.6.3 Parameters for Querying CDMA Pilot Pollution Analysis Reports This section describes the parameters for querying CDMA pilot pollution analysis reports. You can refer to the description when querying a CDMA pilot pollution analysis report.

Parameter Basic Information Task Name OSS Name E2E Task List Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task. Indicates the types of E2E tasks. You can select one of the following E2E tasks: VIP subscriber monitoring task, interference data task, spectrum data task, 1x neighboring cell data task, DO neighboring cell data task, or complaint analysis data task. Indicates the time when the task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must be earlier than the end time. NE Object Indicates the NE related to the E2E task.
Begin Time
30.6.2 Parameters for Creating and Modifying CDMA Pilot Pollution Analysis Tasks
This section describes the parameters for creating and modifying CDMA pilot pollution analysis tasks. You can refer to this description when creating and modifying a CDMA pilot pollution analysis task.
Parameter Basic information Task Name Description Indicates the name of a pilot pollution analysis task. The value range is as follows:
l l
l l
Choose CDMA Pilot Pollution Analysis Task from the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range: a maximum of 200 characters
Time information
Data Time Scope
Task Start At
Object information
BSC Carrier Group
If you select this option, the navigation tree displays all the BSCs on the entire network. If you select this option, the navigation tree displays all the carrier groups on the entire network.
30.6.3 Parameters for Querying CDMA Pilot Pollution Analysis Reports

This section describes the parameters for querying CDMA pilot pollution analysis reports. You can refer to the description when querying a CDMA pilot pollution analysis report.
30-16
Issue 03 (2010-06-30)
Description of parameters in the polluted carrier overview table

Parameter MSC ID Description Indicates the ID of the MSC that the polluted carrier belongs to. The value of this parameter is empty if the polluted carrier is of the EV-DO type. BSC Name Carrier Name PN Average Ec/Io(dB) NUMBEROFMRS Total Number of Polluted Events Total Number of Pollution Neighboring Cells Indicates the name of the BSC that the polluted carrier belongs to. Indicates the name of the polluted carrier. Indicates the Pseudo Number (PN) of the polluted carrier. Indicates the average Ec/Io of the dominant carrier. Indicates the number of MRs of the dominant carrier. Indicates the total number of events that the dominant carrier is polluted. Indicates the total number of neighboring cells that cause the pollution.
Description of parameters in the polluter carrier details table

Parameter MSC ID of Polluter Carrier Description Indicates the ID of the MSC that the polluter carrier belongs to. The value of this parameter is empty if the polluter carrier is of the EV-DO type. Indicates the name of the BSC that the polluter carrier belongs to. Indicates the name of the polluter carrier. For a defined neighboring cell, the value of this parameter is the name of the defined neighboring cell. For an undefined neighboring cell, the value of this parameter is the name of a possible neighboring cell. If the name of a possible neighboring cell fails to be identified by PN, the value of this parameter is Unknown. Indicates the average Ec/Io of the polluter carrier. Indicates the total number of events that the dominant carrier is polluted by the pilot of the neighboring cell. Indicates the distance from the dominant carrier to the neighboring cell.
BSC Name of Polluter Carrier Polluter Carrier Name
Average Ec/Io(dB) Total Number of Pollution Events Distance(km)
Issue 03 (2010-06-30)
30-17
Description of parameters in the polluter carrier overview table

Parameter MSC ID Description Indicates the ID of the MSC that the polluter carrier belongs to. The value of this parameter is empty if the polluter carrier is of the EV-DO type. BSC Name Carrier Name PN Average Ec/Io(dB) Total Number of Pollution Events Total Number of Polluted Neighboring Cells Indicates the name of the BSC that the polluter carrier belongs to. Indicates the name of the polluter carrier. Indicates the Pseudo Number (PN) of the polluter carrier. Indicates the average Ec/Io of the dominant carrier. Indicates the total number of events that the dominant carrier is polluted. Indicates the total number of polluted neighboring cells.
Description of parameters in the polluted carrier details table

Parameter MSC ID of Polluted Carrier Description Indicates the ID of the MSC that the polluted carrier belongs to. The value of this parameter is empty if the polluted carrier is of the EV-DO type. Indicates the name of the BSC that the polluted carrier belongs to. Indicates the name of the polluted carrier. Indicates the average Ec/Io of the polluted carrier. Indicates the total number of events that the dominant carrier is polluted by the pilot of the neighboring cell. Indicates the distance from the dominant carrier to the neighboring cell.
BSC Name of Polluted Carrier Polluted Carrier Name Average Ec/Io(dB) Total Number of Pollution Events Distance(km)
30-18
Issue 03 (2010-06-30)
31 CDMA Coverage Analysis
31
About This Chapter
CDMA Coverage Analysis
This section describes the CDMA coverage analysis, including the management of CDMA coverage analysis tasks and the query and export of CDMA coverage analysis reports. The Nastar analyzes the MRs sent by MSs and displays the coverage status, signal quality, and user distribution of the test carrier directly on the GUI. In this way, the Nastar helps to quickly locate carrier problems such as poor coverage, cross coverage, poor QoS, and unbalanced uplink and downlink on the radio network. 31.1 Basic Knowledge of CDMA Coverage Analysis This section describes the CDMA coverage analysis. The Nastar analyzes MRs reported by MSs in the CDMA coverage analysis function. The analysis results helps you learn the coverage of test carriers in the network, thus determining the carrier problems such as poor coverage, cross coverage, and poor QoS on the existing network. 31.2 CDMA Coverage Analysis Process This section describes the CDMA coverage analysis process. 31.3 Managing CDMA Coverage Analysis Tasks This section describes how to manage CDMA coverage analysis tasks. You can create, modify, delete, suspend, and restore CDMA coverage analysis tasks. You can also view the status and execution progress of such tasks. 31.4 Querying CDMA Coverage Analysis Reports This section describes how to query CDMA coverage analysis reports. The Nastar analyzes the MRs sent by UEs to display the coverage status of the test carrier. In this way, the Nastar helps to quickly locate carrier problems such as poor coverage, cross coverage, poor QoS, and unbalanced uplink and downlink on the radio network. 31.5 Exporting CDMA Coverage Analysis Reports This section describes how to export CDMA coverage analysis reports. You can export the queried coverage analysis results and save them as .xls files as required. The exported coverage analysis results help you learn about the coverage status of the test carriers on the network. 31.6 Reference for the CDMA Coverage Analysis Interface
Issue 03 (2010-06-30)
31-1
This section describes the interface for CDMA coverage analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA coverage analysis.
31-2
Issue 03 (2010-06-30)
31.1 Basic Knowledge of CDMA Coverage Analysis

This section describes the CDMA coverage analysis. The Nastar analyzes MRs reported by MSs in the CDMA coverage analysis function. The analysis results helps you learn the coverage of test carriers in the network, thus determining the carrier problems such as poor coverage, cross coverage, and poor QoS on the existing network.
CDMA Coverage Analysis

With the coverage analysis function, the Nastar collects data of the specific data sources base on the cell level to measure the coverage-related KPIs and the cells or carriers that have the pilot pollution and displays the coverage situation in professional manner. This analysis helps network engineers evaluate the quality of network coverage and thus quickly locate and solve network coverage problems. The MRs reported by MSs contain the KPIs of 1X and EV-DO services. After you specify the conditions for coverage analysis, the Nastar analyzes the coverage of the selected carrier and then displays the analysis results in a two-dimensional chart, a threedimensional chart, and a table.
l
In the two-dimensional chart, the KPIs of 1X and EV-DO services are available.
The KPIs of 1X services are forward Ec/Io, RX (MS receive power), RTD (distance), forward FER, and reverse FER. The KPIs of EV-DO services are forward Ec/Io, RTD (distance), and reverse PER. The KPI pairs of 1X services are RTD/forward Ec/Io, RTD/reverse FER, RTD/forward FER, RTD/RX (MS receive power), RX (MS receive power)/forward Ec/Io, and RX (MS receive power)/forward FER. The KPI pairs of EV-DO services are RTD/forward Ec/Io and RTD (distance)/reverse PER.
In the three-dimensional chart, the KPIs of 1X and EV-DO services are available.
In the overview table, the statistics of all service KPIs in the two-dimensional chart are displayed.
The results of coverage analysis can be exported as .xls files. In this case, users can optimize problem cells in the network according to the exported analysis results.
Common Scenario and Solution

Coverage problems may affect the quality of the network. Table 31-1 describes the common scenarios and solutions of coverage analysis during network optimization.
Issue 03 (2010-06-30)
31-3
Table 31-1 Common scenario and solution Common Scenario Dead zone Description Dead zone is the coverage area where the pilot signal level is lower than the minimum access threshold of MSs, such as basin, back of the hillside, elevator shaft, tunnel, underground garage, basement, and interior of high buildings. Coverage hole is the coverage area where the pilot signal level is lower than the minimum requirement of the whole coverage service but are higher than the minimum access threshold of MSs. Solution
l l l l l
Deploy a new BTS. Expand the coverage area. Use RRU and repeater. Adopt Pico. Adopt the indoor distributed coverage system. Deploy a micro BTS or repeater. Use the antenna with a high gain and increase the antenna height or decrease the mechanical antenna downtilt. Optimize the power configuration of the whole coverage service in the scenario where the large capacity is not required. Adjust the downtilt and azimuth of the antenna. Avoid the situation where the antenna transmits signals by directly facing the road. Utilize the shielding effect caused by surrounding buildings. Adjust the pilot power and narrow the coverage area of the BTS.
Coverage hole
l l
Cross coverage
Cross coverage is produced when the coverage areas of certain BTSs exceed the planned range. In this case, incontinuous dominant areas that meet the requirements of the whole coverage service are formed in the coverage areas of other BTSs.
Unbalanced uplink and downlink Pilot pollution
This situation occurs when the uplink coverage or downlink coverage is limited within the target coverage area. Pilot pollution occurs when multiple pilot signals exist in a cell but no pilot is strong enough to be the dominant pilot.
Adjust the antenna layout and related parameters. Reduce the pilot power. Combine sectors of the BTS or delete redundant sectors without affecting the capacity.
l l
31.2 CDMA Coverage Analysis Process

This section describes the CDMA coverage analysis process.
Figure 31-1 shows the CDMA coverage analysis process. Figure 31-1 Process of CDMA coverage analysis
Start
Set an E2E task
Set a coverage analysis task
Query a coverage analysis report
Export a coverage analysis report
End
Table 31-2 describes the items in the flowchart. Table 31-2 Description of the CDMA coverage analysis process No. 1 Procedure Querying NE data information Creating an end-to-end task for coverage analysis Description In the Analysis Task Management window on the Nastar client, you can switch to the data query window to query whether the raw data required for the coverage analysis is imported to the database. You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a coverage analysis task. After the task is created, the Nastar issues MML commands to the M2000, and then the M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results.
Issue 03 (2010-06-30)
31-5
No. 3
Procedure Creating a coverage data import task
Description You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a task for importing the coverage data. After the task is created, the Nastar periodically imports the coverage data files saved on the Nastar server to the database. In the Analysis Task Management window on the Nastar client, you can create coverage analysis tasks. After obtaining the related analysis data from the database, the Nastar analyzes data and then generates the analysis result. You can view the analysis result of an executed coverage analysis task. The analysis result helps you learn the coverage of the selected test carrier, thus determining the carrier problems such as poor coverage, cross coverage, poor QoS, and unbalanced uplink and downlink on the existing network. You can export analysis result files in the Nastar.
Creating a coverage analysis task Querying a coverage analysis report
Exporting CDMA coverage analysis reports
31.3 Managing CDMA Coverage Analysis Tasks

This section describes how to manage CDMA coverage analysis tasks. You can create, modify, delete, suspend, and restore CDMA coverage analysis tasks. You can also view the status and execution progress of such tasks. 31.3.1 Creating a CDMA E2E Task This section describes how to create an end-to-end (E2E) task. After you set an E2E task in the Nastar, the Nastar issues MML commands to the M2000. The M2000 then sends these MML commands to the corresponding NEs. Finally, the NEs perform the measurement tasks and generate results. 31.3.2 Creating CDMA Coverage Analysis Tasks This section describes how to create CDMA coverage analysis tasks. In a CDMA coverage analysis task, the Nastar periodically analyzes the MRs sent by an MS in the Nastar database. Based on the analysis results, you can learn about the coverage status of the test carrier and determine whether carrier problems such as poor coverage, cross coverage, poor QoS, and unbalanced uplink and downlink occur on the existing network. 31.3.3 Modifying CDMA Coverage Analysis Tasks This section describes how to modify the attributes of the created CDMA coverage analysis tasks. You can modify the attributes of the created CDMA coverage analysis tasks as required. 31.3.4 Checking CDMA Coverage Analysis Tasks This section describes how to check CDMA coverage analysis tasks. You can check the attributes, execution progress, and execution results of a CDMA coverage analysis task as required.
31-6
Issue 03 (2010-06-30)

Prerequisite
l l l
Context
TIP
Procedure
l
3.
In E2E Task List, select a task. Table 31-3 describes the mapping between E2E tasks and analysis tasks.
Issue 03 (2010-06-30)
31-7
Table 31-3 Mapping between E2E tasks and analysis tasks E2E Tasks VIP subscriber monitoring task Interference data task Spectrum data task 1x neighboring cell data task DO neighboring cell data task Complaint analysis data task Analysis tasks CDMA VIP analysis task CDMA uplink-interference-ranking analysis task CDMA uplink-interference-spectrum analysis task CDMA co-frequency neighboring cell analysis task CDMA co-frequency neighboring cell analysis task CDMA complaint assistant analysis task
Postrequisite
NOTE
31-8
Issue 03 (2010-06-30)
31.3.2 Creating CDMA Coverage Analysis Tasks

This section describes how to create CDMA coverage analysis tasks. In a CDMA coverage analysis task, the Nastar periodically analyzes the MRs sent by an MS in the Nastar database. Based on the analysis results, you can learn about the coverage status of the test carrier and determine whether carrier problems such as poor coverage, cross coverage, poor QoS, and unbalanced uplink and downlink occur on the existing network.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the coverage analysis function. The E2E task, collection task, and data import task corresponding to the coverage analysis task are normal. The VIP analysis task can be created successfully even if the prerequisites are not met. The execution of the VIP analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l l
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. The value of Execution Type can only be Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects in the object navigation tree on the tab page.
l
Choose BSC or Carrier Group above the navigation tree to display the objects in the navigation tree as required. The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to display the Find dialog box. Type
Issue 03 (2010-06-30)
the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Step 7 Set filtering conditions on the Condition Selection tab page. With the filtering conditions, users can find out the carriers that meet the specified conditions, thus determining the analysis range. By default, 16 filtering conditions are provided. Users can add filtering conditions or modify the existing filtering conditions.
l
Add a filtering condition. Select a KPI of a service, and then set the filtering condition formula. Then, click Add. The two-dimensional chart supports the setting of formulas with either one counter or two counters. The three-dimensional chart supports only the setting of formulas with two counters.
Modify a filtering condition. Select a formula in the filtering condition display area, and then modify the formula in the filtering condition setting area. Then, click Apply.
Delete a filtering condition. Select a formula in the filtering condition display area, and then click Delete.
Filtering conditions of the tasks whose Status is Running or Complete cannot be modified or deleted. Step 8 Click Complete. ----End
Postrequisite
l
Deleting a task You can delete an unnecessary coverage analysis task to release system resources.
NOTE
1.
Click the CDMA Coverage Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
button.
Suspending a task To delay the task execution, you can suspend a coverage analysis task that is in the idle state. Then, the coverage analysis task becomes a suspended task.
NOTE
The system can schedule only the coverage analysis tasks that are not suspended.
1.
Click the CDMA Coverage Analysis Task node in the navigation tree in the Analysis Task Management window.
31-10
l
Restoring a task You can restore a suspended coverage analysis task to the idle state. Then, the task can be scheduled by the system.
NOTE
Only the coverage analysis tasks that are in the idle state can be scheduled by the system.
1.
Click the CDMA Coverage Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2.
button.
31.3.3 Modifying CDMA Coverage Analysis Tasks

This section describes how to modify the attributes of the created CDMA coverage analysis tasks. You can modify the attributes of the created CDMA coverage analysis tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the coverage analysis function. A CDMA coverage analysis task is created.
Context
Procedure
Step 1 Click the CDMA Coverage Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 31.6.2 Parameters for Creating and Modifying CDMA Coverage Analysis Tasks.
Issue 03 (2010-06-30)

l
You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about the object navigation tree, and the filtering conditions of a coverage analysis task.
31.3.4 Checking CDMA Coverage Analysis Tasks

This section describes how to check CDMA coverage analysis tasks. You can check the attributes, execution progress, and execution results of a CDMA coverage analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA coverage analysis task is created.
Procedure
Step 1 Click the CDMA Coverage Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Then ...
Check the attributes of a coverage analysis Select a task from the task list in the upper-right task pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 31.3.3 Modifying CDMA Coverage Analysis Tasks. Check the execution progress of the active Select a task from the task list in the upper-right task pane. Then, you can view the execution progress of the task in the Progress column.
31-12
Issue 03 (2010-06-30)
Then ... Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
31.4 Querying CDMA Coverage Analysis Reports

This section describes how to query CDMA coverage analysis reports. The Nastar analyzes the MRs sent by UEs to display the coverage status of the test carrier. In this way, the Nastar helps to quickly locate carrier problems such as poor coverage, cross coverage, poor QoS, and unbalanced uplink and downlink on the radio network.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the coverage analysis function. The coverage analysis task is executed successfully.
Issue 03 (2010-06-30)
31-13
Procedure
Step 1 Click the CDMA Coverage Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. The analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose Analysis Result from the shortcut menu. The CDMA Coverage Analysis Task window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Optional: In the filtering condition setting area in the lower left corner of the CDMA Coverage Analysis Task window, select a filtering condition so that the object navigation tree displays only the carriers that meet the filtering condition. You can also type the keyword of an object name in the search box above the object navigation tree, and then click so that the carriers that meet the condition are displayed.
Step 5 Select a carrier under 1X Analysis or EVDO Analysis in the object navigation tree in the left pane of the window, and then you can view the two-dimensional chart, three-dimensional chart, and KPI overview table of the selected carrier in the area on the right of the window.
l
The two-dimensional charts of bar chart and KPI accumulative distribution chart display the 1X KPI information and EV-DO KPI information about the selected carrier. The two-dimensional chart displays the KPI information with two y axes. The x axis displays the KPI values. The left y axis displays the percentage of the reports of each KPI value to the total reports. The right y axis displays the values of the line chart. Each value of the line chart is the sum of the report percentages corresponding to all the KPI values lower than the current KPI value.
The three-dimensional chart displays the KPI distribution by pairing 1X KPIs and EV-DO KPIs of the selected carrier. Different colors are used to differentiate the KPI distribution density. After you specify the value ranges of the two KPIs corresponding to the x axis and y axis in the formula setting area, the Nastar calculates the density sum of KPI distribution in the value range intersection.
The overview table displays the statistics of all KPIs in the two-dimensional chart.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 31.5 Exporting CDMA Coverage Analysis Reports. To query the chart attributes, save the chart, print the chart, or adjust the chart size in the chart area, do as follows:
Right-click the chart and then choose Property from the shortcut menu. In the displayed Chart Property dialog box, set the coordinate axes and basic information about the chart.
31-14
Right-click the chart and then choose Save as from the shortcut menu. In the displayed Save dialog box, set the save path and file name. Then, click Save to save the queried chart in files on the local PC. Right-click the chart and then choose Print from the shortcut menu. In the displayed Page Setup dialog box, set the print attributes and then click OK. If the chart cannot be viewed properly because of excessive data points, you can rightclick the chart and then choose Zoom In > ***, Zoom Out > ***, or Auto Range > *** to adjust the chart size. *** represents the level 2 menu name, including Both Axes, Horizontal Axis, and Vertical Axis. You can adjust the chart size in both the x axis and the y axis or either axis.
31.5 Exporting CDMA Coverage Analysis Reports

This section describes how to export CDMA coverage analysis reports. You can export the queried coverage analysis results and save them as .xls files as required. The exported coverage analysis results help you learn about the coverage status of the test carriers on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the CDMA coverage analysis reports.
Context
Exporting coverage analysis overview refers to exporting the overview table of all the test carriers involved in the selected coverage analysis task.
Procedure
l Export the overview table by using the shortcut icon. 1. 2. in the CDMA Coverage Analysis Task window. The Save dialog box is Click displayed. Specify a save path. Then, click Save. The main information contained in the .xls file is the coverage information about all the test carriers that meet the current filtering conditions. Click the Counter Overview Data tab in the right pane of the CDMA Coverage Analysis Task window. Right-click on the overview table, and then choose Save As... from the shortcut menu. Specify a save path and file name. Then, click Save. The main information contained in the .xls file is the coverage information about all the test carriers that meet the current filtering conditions. In the .xls file, the
Export the overview table by using the shortcut menu. 1.
2.
Issue 03 (2010-06-30)
information about 1X carriers and EV-DO carriers are displayed on the 1X Carrier and EVDO Carrier worksheets respectively. ----End
31.6 Reference for the CDMA Coverage Analysis Interface

This section describes the interface for CDMA coverage analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA coverage analysis. 31.6.1 Parameters of CDMA E2E Tasks This section describes the parameters of CDMA E2E tasks. You can refer to the description when creating or modifying a CDMA E2E task. 31.6.2 Parameters for Creating and Modifying CDMA Coverage Analysis Tasks This section describes the parameters for creating and modifying CDMA coverage analysis tasks. You can refer to the description when creating and modifying a CDMA coverage analysis task. 31.6.3 Parameters for Querying CDMA Coverage Analysis Reports This section describes the parameters for querying CDMA coverage analysis reports. You can refer to the description when querying a CDMA coverage analysis report.

Parameter Basic Information Task Name OSS Name E2E Task List Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task. Indicates the types of E2E tasks. You can select one of the following E2E tasks: VIP subscriber monitoring task, interference data task, spectrum data task, 1x neighboring cell data task, DO neighboring cell data task, or complaint analysis data task. Indicates the time when the task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must be earlier than the end time.
Begin Time
31-16
Issue 03 (2010-06-30)
Parameter NE Object
Description Indicates the NE related to the E2E task.
31.6.2 Parameters for Creating and Modifying CDMA Coverage Analysis Tasks
This section describes the parameters for creating and modifying CDMA coverage analysis tasks. You can refer to the description when creating and modifying a CDMA coverage analysis task.
Parameter Basic information Task Name Description Indicates the name of a coverage analysis task. The value range is as follows:
l l
l l
Select CDMA Coverage Analysis Task in the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range:
l l
Time information
Data Time Scope
Task Start At
Issue 03 (2010-06-30)
31-17
Parameter Object information BSC Carrier Group
Description If you select this option, the navigation tree displays all the BSCs on the entire network. If you select this option, the navigation tree displays all the carrier groups on the entire network.
31.6.3 Parameters for Querying CDMA Coverage Analysis Reports

This section describes the parameters for querying CDMA coverage analysis reports. You can refer to the description when querying a CDMA coverage analysis report.
Description of parameters related to KPIs of 1X services

Parameter Total Number of FWDECIO Measurement Reports Total Number of RTD Measurement Reports Total Number of FWDFER Measurement Reports Total Number of REVFER Measurement Reports Total Number of RxPwr Measurement Reports Average FWDEcIo (dB) Average RTD(m) Average FWDFER(%) Average REVFER(%) Average RXPWR (dBm) Description Indicates the total number of MRs that contain the forward Ec/Io information of the selected carrier measured by service type. Indicates the total number of MRs that contain the RTD information of the selected carrier measured by service type. Indicates the total number of MRs that contain the forward FER information of the selected carrier measured by service type. Indicates the total number of MRs that contain the reverse FER information of the selected carrier measured by service type. Indicates the total number of MRs that contain the RX (MS receive power) information of the selected carrier measured by service type. Indicates the average forward Ec/Io of the selected carrier measured by service type within the specified time range. Indicates the average RTD of the selected carrier measured by service type within the specified time range. Indicates the average forward FER of the selected carrier measured by service type within the specified time range. Indicates the average reverse FER of the selected carrier measured by service type within the specified time range. Indicates the average RX (MS receive power) of the selected carrier measured by service type within the specified time range.
31-18
Issue 03 (2010-06-30)
Description of parameters related to KPIs of EV-DO services

Parameter Total Number of FWDECIO Measurement Reports Total Number of RTD Measurement Reports Total Number of REVFER Measurement Reports Average FWDEcIo (dB) Average RTD(m) Average REVFER(%) Description Indicates the total number of MRs that contain the forward Ec/Io information of the selected carrier measured by service type. Indicates the total number of MRs that contain the RTD information of the selected carrier measured by service type. Indicates the total number of MRs that contain the reverse PER information of the selected carrier measured by service type. Indicates the average forward Ec/Io of the selected carrier measured by service type within the specified time range. Indicates the average RTD of the selected carrier measured by service type within the specified time range. Indicates the average reverse PER of the selected carrier measured by service type within the specified time range.
Issue 03 (2010-06-30)
31-19
32 CDMA Cell Performance Analysis
32
CDMA Cell Performance Analysis
About This Chapter

This section describes the CDMA cell performance analysis, including the management of cell performance analysis tasks and the query and export of cell performance analysis reports. By providing call data of abnormal users in problem cells, the Nastar assists you in analyzing the root cause of abnormal calls. This helps to provide better services and improve user satisfaction. 32.1 Basic Knowledge of CDMA Cell Performance Analysis This section describes the basic knowledge of the CDMA cell performance analysis function, which facilitates identification of problem carriers and enables the Nastar to obtain the data of abnormal calls of problem carriers. By analyzing and displaying the data of exceptional calls, the Nastar assists in identifying the causes of problem carriers, thus facilitating in-depth problem analysis. 32.2 CDMA Cell Performance Analysis Process This section describes the CDMA cell performance analysis process. 32.3 Managing CDMA Cell Performance Analysis Tasks This section describes how to manage CDMA cell performance analysis tasks. You can create, modify, delete, suspend, and restore CDMA cell performance analysis tasks. You can also view the status and execution progress of such tasks. 32.4 Querying CDMA Cell Performance Analysis Reports This section describes how to query CDMA cell performance analysis reports. The Nastar analyzes the abnormal call records of subscribers in all problem carriers under the selected NE and identifies the cause and top subscribers. This helps to locate and solve the carrier performance exceptions. 32.5 Exporting CDMA Cell Performance Analysis Reports This section describes how to export CDMA cell performance analysis reports. You can export the queried cell performance analysis results and save them as .xls files as required. The exported cell performance analysis results can then assist you in determining the problem cells on the network. 32.6 Reference for the CDMA Cell Performance Analysis Interface
Issue 03 (2010-06-30)
32-1
This section describes the interface for CDMA cell performance analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA cell performance analysis.
32-2
Issue 03 (2010-06-30)
32.1 Basic Knowledge of CDMA Cell Performance Analysis

This section describes the basic knowledge of the CDMA cell performance analysis function, which facilitates identification of problem carriers and enables the Nastar to obtain the data of abnormal calls of problem carriers. By analyzing and displaying the data of exceptional calls, the Nastar assists in identifying the causes of problem carriers, thus facilitating in-depth problem analysis. Generally, the whole-to-partial analysis method is used during network optimization or performance analysis. The Nastar monitors the KPIs to analyze and locate network problems. After analyzing the KPIs of the entire network or a BSC, the Nastar analyzes the carriers of the faulty BSC to identify top problem carriers. Finally, the Nastar analyzes the top problem carriers in depth. At present, the minimum analysis unit of most performance data is a carrier. The Nastar, however, provides detailed and in-depth analysis on problem carriers. The Nastar provides the following functions:
l
Providing the cause of abnormal carriers by analyzing abnormal call records based on NEs or NE groups Further analyzing top users whose network KPI values do not meet the requirements Identifying and analyzing top problem carriers
l l
The results of cell performance analysis can be exported as .xls files. In this case, users can optimize problem carriers in the network according to the exported analysis results.
32.2 CDMA Cell Performance Analysis Process

This section describes the CDMA cell performance analysis process. Figure 32-1 shows the CDMA cell performance analysis process.
Issue 03 (2010-06-30)
32-3
Figure 32-1 Process of CDMA cell performance analysis
32-4
Issue 03 (2010-06-30)
Table 32-1 Description of the CDMA cell performance analysis process No. 1 Procedure Querying NE data information Creating an end-to-end task for cell performance analysis Description In the Analysis Task Management window on the Nastar client, you can switch to the data query window to query whether the raw data required for the cell performance analysis is imported to the database. On the Nastar client, choose Maintenance > E2E Task Management. In the displayed E2E Task Management window, you can create an E2E task for cell performance analysis. After the task is created, the Nastar sends MML commands to the M2000, and then the M2000 sends MML commands to NEs. After that, the NEs execute the measurement task and generate results. After an E2E task is created, you can view the corresponding collection task that has been created by the system in the Task Management window. A data import task can be performed only after the corresponding collection task is complete. On the Nastar client, choose Maintenance > Task Management. In the displayed Task Management window, create a data import task corresponding to the cell performance analysis task so that the Nastar periodically imports the cell performance analysis data saved as files on the Nastar server to the database. In the Analysis Task Management window on the Nastar client, you can create cell performance analysis tasks. After obtaining the related analysis data from the database, the Nastar analyzes data and then generates the analysis result. You can view the analysis results of the tasks that are successfully performed. In addition, you can export the result files through the one-key method in the analysis result query interface. You can export analysis result files in the Nastar.
Creating a task for importing data of cell performance analysis Creating a task for analyzing cell performance Querying a report of cell performance analysis Exporting a report of cell performance analysis
32.3 Managing CDMA Cell Performance Analysis Tasks

This section describes how to manage CDMA cell performance analysis tasks. You can create, modify, delete, suspend, and restore CDMA cell performance analysis tasks. You can also view the status and execution progress of such tasks. 32.3.1 Creating a CDMA E2E Task This section describes how to create an end-to-end (E2E) task. After you set an E2E task in the Nastar, the Nastar issues MML commands to the M2000. The M2000 then sends these MML
commands to the corresponding NEs. Finally, the NEs perform the measurement tasks and generate results. 32.3.2 Creating CDMA Cell Performance Analysis Tasks This section describes how to create CDMA cell performance analysis tasks. In a CDMA cell performance analysis task, the Nastar analyzes the abnormal call records associated with all problem carriers under the selected NE to identify the cause of the abnormal calls. This function helps operators locate and rectify network faults in key areas, thus improving the QoS and enhancing the user experience in the key areas. 32.3.3 Modifying CDMA Cell Performance Analysis Tasks This section describes how to modify the attributes of the created CDMA cell performance analysis tasks. You can modify the attributes of the created CDMA cell performance analysis tasks as required. 32.3.4 Checking CDMA Cell Performance Analysis Tasks This section describes how to check CDMA cell performance analysis tasks. You can check the attributes, execution progress, and execution results of a CDMA cell performance analysis task as required.

Prerequisite
l l l
Context
TIP
Procedure
32-6
Issue 03 (2010-06-30)

l
If the OSS list does not contain the created OSS, click Add to create an OSS.

OSS Name indicates the name of the OSS to be created. Port indicates the number of the port on the FTP server where the file to be collected is saved. User Name indicates the user name used for logging in to the M2000 server. Password indicates the password used for logging in to the M2000 server. FTP User indicates the user name used for logging in to the FTP server. FTP Password indicates the password used for logging in to the FTP server.
3.
Postrequisite
NOTE
32.3.2 Creating CDMA Cell Performance Analysis Tasks

This section describes how to create CDMA cell performance analysis tasks. In a CDMA cell performance analysis task, the Nastar analyzes the abnormal call records associated with all problem carriers under the selected NE to identify the cause of the abnormal calls. This function helps operators locate and rectify network faults in key areas, thus improving the QoS and enhancing the user experience in the key areas.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the function of cell performance analysis. The E2E task, collection task, and data import task corresponding to the cell performance analysis task are normal. The VIP analysis task can be created successfully even if the prerequisites are not met. The execution of the VIP analysis task, however, will always fail when the data to be analyzed is not imported to the database.
Context
l l
32-8
Procedure
Step 1 Click in the Analysis Task Management window. The Analysis Task Management-New Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, and Note. Execution Type can only be set to Once Task. Step 3 Click Next. Step 4 Set Time Setting for Once Task Data. Step 5 Click Next. Step 6 Select one or multiple objects on the tab page.
l
Select BSC or Carrier Group above the navigation tree to display the objects in the navigation tree as required. If the objects are selected by NE, a maximum of 500 carriers can be selected. If the objects are selected by carrier group, a maximum of 25 carrier groups can be select, and the total number of carriers in all carrier groups cannot exceed 500.
The system enables you to search for the objects in the navigation tree. You can right-click any point of the navigation tree and then press Ctrl+F to open the Find dialog box. Type the keywords, that is, the search condition, in the dialog box. Then, the system searches for the query result that meets the search condition.

Postrequisite
l
NOTE
1.
Click the CDMA Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks.
2. 3.
l
button.
NOTE
Issue 03 (2010-06-30)
32-9
1.
2.
button.
l
NOTE
1.
2.
button.
32.3.3 Modifying CDMA Cell Performance Analysis Tasks

This section describes how to modify the attributes of the created CDMA cell performance analysis tasks. You can modify the attributes of the created CDMA cell performance analysis tasks as required.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the function of cell performance analysis. A CDMA cell performance analysis task is created.
Context
Procedure
Step 1 Click the CDMA Cell Performance Analysis Task node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed.
32-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
. The
Issue 03 (2010-06-30)
Step 3 Modify the relevant parameters.

l
For description of the parameters, see 32.6.2 Parameters for Creating and Modifying CDMA Cell Performance Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, and the information about the NE object selection.
32.3.4 Checking CDMA Cell Performance Analysis Tasks

This section describes how to check CDMA cell performance analysis tasks. You can check the attributes, execution progress, and execution results of a CDMA cell performance analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA cell performance analysis task is created.
Procedure
Step 1 Click the CDMA Cell Performance Analysis node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Then ...
Check the attributes of a cell performance Select a task from the task list in the upperanalysis task right pane. Double-click the task or click . You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 32.3.3 Modifying CDMA Cell Performance Analysis Tasks. Check the execution progress of the active Select a task from the task list in the uppertask right pane. Then, you can view the execution progress of the task in the Progress column.
Issue 03 (2010-06-30)
32-11
Then ... Select a task from the task list in the upperright pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
32.4 Querying CDMA Cell Performance Analysis Reports

This section describes how to query CDMA cell performance analysis reports. The Nastar analyzes the abnormal call records of subscribers in all problem carriers under the selected NE and identifies the cause and top subscribers. This helps to locate and solve the carrier performance exceptions.
Prerequisite
l l l l
32-12
Issue 03 (2010-06-30)
Procedure
Step 1 Click the CDMA Cell Performance Analysis node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. The analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose Analysis Result from the shortcut menu. The CDMA Cell Performance Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Optional: In the drop-down list in the upper left corner of the CDMA Cell Performance Analysis window, select 1X carrier or EV-DO carrier so that the object navigation tree displays only the selected type of carriers under the BSC node or the carrier group node. Step 5 Select a carrier node from the object navigation tree in the left pane of the window, and then you can view the KPI overview information of the selected carrier and the ranking overview information of each KPI in the areas in the middle and on the right of the window.
l
The table lists the number of records of each exception type and the percentage of each exception type to all exceptions in the report.
The 1X carrier exception is classified into six types, namely, voice service access failure, voice service call drop, data service access failure, data service call drop, access failure of other services, and call drop of other services.
NOTE
The access failure of other services and call drop of other services are not illustrated in pie charts.
The EV-DO carrier exception is classified into two types, namely, access failure and call drop.
In the area on the right, namely, Area (4) and Area (5), the top subscribers identified by IMSIs, top cells, and top exception causes are illustrated in tables and pie charts. The tables and pie charts show the number of exception records and the percentage of each exception type.
You can set Display Num in Area (4) to determine the number of top subscribers, top cells, and top exception causes. By default, top 10 users, cells, and exception causes are displayed. If Display is set to TOP User or TOP Exception Reason, Display Num cannot be empty and its maximum value is 50. If Display is set to TOP Cell, setting of Display Num is optional. If Display Num is not set, all carriers are displayed.
TOP Cell is displayed in the Display drop-down list box in Area (4) only when the overview node or NE/NE group node is selected in the object navigation tree in the left pane of the window.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 32.5 Exporting CDMA Cell Performance Analysis Reports. To query the chart attributes, save the chart, print the chart, or adjust the chart size in the chart area, do as follows:
Right-click the chart and then choose Property from the shortcut menu. In the displayed Chart Property dialog box, set the coordinate axes and basic information about the chart. Right-click the chart and then choose Save as from the shortcut menu. In the displayed Save dialog box, set the save path and file name. Then, click Save to save the queried chart in files on the local PC. Right-click the chart and then choose Print from the shortcut menu. In the displayed Page Setup dialog box, set the print attributes and then click OK. If the chart cannot be viewed properly because of excessive data points, you can rightclick the chart and then choose Zoom In > ***, Zoom Out > ***, or Auto Range > *** to adjust the chart size. *** represents the level 2 menu name, including Both Axes, Horizontal Axis, and Vertical Axis. You can adjust the chart size in both the x axis and the y axis or either axis.
32.5 Exporting CDMA Cell Performance Analysis Reports

This section describes how to export CDMA cell performance analysis reports. You can export the queried cell performance analysis results and save them as .xls files as required. The exported cell performance analysis results can then assist you in determining the problem cells on the network.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the CDMA cell performance analysis reports.
Procedure
in the CDMA Cell Performance Analysis window. The CDMA Cell Performance Step 1 Click Analysis dialog box is displayed. Step 2 Set a file name and specify the save path and file type. Then, click Save. The saved .xls file is opened automatically so that you can view it conveniently. The Nastar exports two types of cell performance analysis report:

l
Cell performance analysis report for 1X carriers: This type of report is named by Specified file name1X. Cell performance analysis report for EV-DO carriers: This type of report is named by Specified file nameDO.
----End
32.6 Reference for the CDMA Cell Performance Analysis Interface

This section describes the interface for CDMA cell performance analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA cell performance analysis. 32.6.1 Parameters of CDMA E2E Tasks This section describes the parameters of CDMA E2E tasks. You can refer to the description when creating or modifying a CDMA E2E task. 32.6.2 Parameters for Creating and Modifying CDMA Cell Performance Analysis Tasks This section describes the parameters for creating and modifying CDMA cell performance analysis tasks. You can refer to the description when creating and modifying a CDMA cell performance analysis task. 32.6.3 Parameters for Querying CDMA Cell Performance Analysis Reports This section describes the parameters for querying CDMA cell performance analysis reports. You can refer to the description when querying a CDMA cell performance analysis report.

Parameter Basic Information Task Name OSS Name E2E Task List Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task. Indicates the types of E2E tasks. You can select one of the following E2E tasks: VIP subscriber monitoring task, interference data task, spectrum data task, 1x neighboring cell data task, DO neighboring cell data task, or complaint analysis data task. Indicates the time when the task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss.
Begin Time
Issue 03 (2010-06-30)
32-15
Parameter End Time
Description Indicates the time when the task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must be earlier than the end time. NE Object Indicates the NE related to the E2E task.
32.6.2 Parameters for Creating and Modifying CDMA Cell Performance Analysis Tasks
This section describes the parameters for creating and modifying CDMA cell performance analysis tasks. You can refer to the description when creating and modifying a CDMA cell performance analysis task.
Parameter Basic information Task Name Description Indicates the name of a cell performance analysis task. The value range is as follows:
l l
l l
Select CDMA Cell Performance Analysis Task in the navigation tree. Such a task can be executed only once in one time period. Provides the description of the task. Value range: a maximum of 200 characters
Time information
Data Time Scope
32-16
Issue 03 (2010-06-30)
Parameter Task Start At
Description Indicates the time when the analysis task is executed. The time specified in this field must not precede the end time specified in the Data Time Scope field.
Object information
BSC Carrier Group
If you select this option, the navigation tree displays all the BSCs on the entire network. If you select this option, the navigation tree displays all the carrier groups on the entire network.
32.6.3 Parameters for Querying CDMA Cell Performance Analysis Reports

This section describes the parameters for querying CDMA cell performance analysis reports. You can refer to the description when querying a CDMA cell performance analysis report.

Parameter Exception Type Description The carrier exceptions of 1X services are classified into the following types:
l l l l l l
CS service access failure CS service call drop PS service access failure PS service call drop Other service access failure Other service call drop
The carrier exceptions of EV-DO services are classified into the following types:
l l
Access failure Call drop
Exception Record Count Percent(%)
Indicates the number of exceptional call records of an exception type. Indicates the proportion of an exception type.
Description of parameters in the exception type overview pie chart

The Nastar supports further analysis on the exceptions of various services and displays the exception types in a pie chart.
Parameter Normal release Resource scarcity fail Motion Device fail Manual force release Wireless link fail Device link fail Calling release early Other fail
Description Indicates the call reports that record normal release. Indicates the call reports that record the failed release due to insufficient network resources. For example, the radio resources are unavailable, or the forward power is insufficient. Indicates the call reports that record the failed release due to the MS fault. For example, the MS is powered off, or the MS does not support channels of certain types. Indicates the call reports that record the failed release due to manual operation on the maintenance console or commissioning console. Indicates the call reports that record the failed release due to the radio link fault in the network. For example, the radio interface of the BSC is faulty, or a service request expires. Indicates the call reports that record the failed release due to the device link fault in the network. For example, a hardware device is faulty. Indicates the call reports that record the early release due to the network disconnection or connection rejection. Indicates the call reports that record other exceptions.

Parameter Display Description Select ranking modes, which consist of the following types:
l l l
TOP Cell TOP User(by IMSI) TOP Exception Reason
Display Num Exception Record Count
Sets the number of displayed objects. Indicates the number of exceptional call records of an exception type, a cell, or a subscriber.
32-18
Issue 03 (2010-06-30)
33 CDMA VIP Analysis
33
About This Chapter
CDMA VIP Analysis
This section describes the CDMA VIP analysis, including the management of VIP analysis tasks and the query and export of VIP analysis reports. By monitoring the KPIs relevant to the QoS of the VIP, the Nastar enables you to identify and solve the network problems that may cause VIP complaints, thus improving QoS and subscriber satisfaction. 33.1 Basic Knowledge of CDMA VIP Analysis The CDMA VIP analysis function enables you to routinely monitor the calls of the selected VIPs on a CDMA network. By analyzing the monitoring reports, you can learn the quality of service (QoS) of these VIPs. If there are any potential network problems, you can identify and solve the problems in advance, thus improving subscriber satisfaction. 33.2 Process of CDMA VIP Analysis This section describes the process of CDMA VIP analysis. 33.3 Managing CDMA VIP Analysis Tasks This section describes how to manage CDMA VIP analysis tasks. You can create, modify, delete, suspend, and resume CDMA VIP analysis tasks. You can also view the status and execution progress of such tasks. 33.4 Querying CDMA VIP Analysis Reports This section describes how to query CDMA VIP analysis reports. By monitoring the number of service call reports, traffic, and KPIs of the selected VIP, you can learn about the QoS of the VIP and identify and solve the network problems that may cause VIP complaints. 33.5 Exporting CDMA VIP Analysis Reports This section describes how to export CDMA VIP analysis reports. You can export the queried VIP analysis results as .csv or .xls files as required. The exported VIP analysis results help you identify and solve the network problems that may cause VIP complaints. 33.6 Reference for the CDMA VIP Analysis GUI This section describes the interface for CDMA VIP analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA VIP analysis.
Issue 03 (2010-06-30)
33-1
33.1 Basic Knowledge of CDMA VIP Analysis

The CDMA VIP analysis function enables you to routinely monitor the calls of the selected VIPs on a CDMA network. By analyzing the monitoring reports, you can learn the quality of service (QoS) of these VIPs. If there are any potential network problems, you can identify and solve the problems in advance, thus improving subscriber satisfaction.
VIP Analysis
The Nastar collects and analyzes the KPIs (including KPIs relevant to the CS services in a 1X network, KPIs relevant to the PS services in a 1X network, KPIs relevant to the services in an EV-DO network, and KPIs relevant to an active cell) by VIP groups or VIPs according to the IMSIs obtained from MSs during calls. Then, network optimization is performed on the basis of the analysis result.
l
The collection and analysis of KPIs by VIP groups enable you to monitor the service conditions of the VIPs in a centralized manner, thus improving operation efficiency and reducing operation expenditure. If you identify any problem in a VIP group and the corresponding VIPs, you can analyze and solve the problem in advance to avoid losing the VIPs. The collection and analysis of KPIs by VIPs enable you to learn about the trends of the KPIs relevant to the experience and behaviors of VIPs, for example, the trends of the delay in setting up the CS services, the distribution of the CS services in radio environments, the average rate of the PS services, the FER distribution of the PS services, the service duration, and the EV-DO data rate. In this manner, you can quickly identify the VIPs with the worst and best QoS during a certain period and learn about the time when network problems occur.
The Nastar also provides an in-depth analysis for the VIPs whose raw data is collected in advance. If you detect that the KPIs of some VIPs in a group deteriorate but cannot identify the problem at the site, the Nastar helps you retrieve the detailed call records of these VIPs within a specified period. By analyzing these call records, you can quickly locate the call record pertaining to the deteriorated KPIs and then analyze the information such as the network quality before the link release and the causes of KPI deterioration to identify the problem. The collection and analysis of KPIs relevant to active cells by VIP groups and VIPs enables you to learn about the main active cells of the VIPs on the network. Based on the network problems that occur in these active cells, the network engineers can quickly identify the key cells that need to be preferentially handled to solve these network problems. In this manner, you can solve the problem of the QoS deterioration caused by network problems in time. This function in combination with the GIS enables the Nastar to display active cells in geographic mode, thus improving the efficiency in analyzing and identifying problems.
Limitation
Although the CDMA VIP analysis function allows the reporting of the raw data of the VIPs, the volume of the raw data must be limited because the system may be overloaded when the raw data of a larger number of VIPs is reported. In the case of the analysis by VIP groups, the Nastar allows the analysis of 30,000 VIPs (that is, the maximum number of VIPs in all the VIP groups that are selected for the analysis cannot exceed 30,000). In the case of the analysis by VIPs, the Nastar allows the analysis of 2,000 VIPs (that is, the maximum number of VIPs in all the VIP groups that are allowed to report raw data cannot exceed 2,000).
In the analysis of the KPIs relevant to the active cell of the VIPs, the geographical distribution of active cells needs to be displayed. This requires you to import correct engineering parameters.
33.2 Process of CDMA VIP Analysis

This section describes the process of CDMA VIP analysis. Figure 33-1 shows the process of VIP analysis. Figure 33-1 Workflow of VIP analysis

Table 33-1 Description of the workflow of VIP analysis No. 1 Procedure Create an endto-end task corresponding to a VIP analysis task Description You can choose Maintenance > E2E Task Management on the Nastar client to open the E2E Task Management window, and then create an end-to-end task corresponding to a VIP analysis task. After the task is created, the Nastar issues MML commands to M2000, and then M2000 issues the received MML commands to the corresponding NE. At last, the NE that receives the MML commands performs the measurement task and generates measurement results. You can choose Maintenance > Task Management on the Nastar client to open the Task Management window, and then create a VIP analysis data importing task. After the task is created, the Nastar periodically imports the VIP analysis data files saved on the Nastar server to the database. You can create a VIP analysis task in the Analysis Task Management window of the main interface on the Nastar client. After the task is created, the Nastar periodically obtains the required call records from the Nastar database, and then generates an analysis report through the analysis. You can view the analysis results of the VIP analysis task that is successfully performed. The Nastar monitors the KPI reports related to the voice service and data service of VIP subscribers daily. This helps you to learn about the quality of service (QoS) of VIP subscribers. In addition, you can locate and solve the network problems, which may incur complaints, beforehand. You can export a VIP analysis report from the Nastar.
Create a VIP analysis data importing task
Create a VIP analysis task
Query a VIP analysis report
Export a VIP analysis report
33.3 Managing CDMA VIP Analysis Tasks

This section describes how to manage CDMA VIP analysis tasks. You can create, modify, delete, suspend, and resume CDMA VIP analysis tasks. You can also view the status and execution progress of such tasks. 33.3.1 Managing CDMA VIP Groups This section describes how to manage the CDMA VIP groups. You can create VIP groups as required and add certain VIP subscribers to a VIP group to monitor the service quality of these VIP subscribers simultaneously. In addition, you can modify the attributes of a VIP group, delete, or export a VIP group. 33.3.2 Creating a CDMA E2E Task This section describes how to create an end-to-end (E2E) task. After you set an E2E task in the Nastar, the Nastar issues MML commands to the M2000. The M2000 then sends these MML commands to the corresponding NEs. Finally, the NEs perform the measurement tasks and generate results. 33.3.3 Creating a CDMA VIP Analysis Task
This section describes how to create a CDMA VIP analysis task. In a CDMA VIP analysis task, the Nastar collects and analyzes the number of service call reports, traffic volume, and KPIs by VIP groups or VIPs according to the IMSIs obtained from the MSs. In this manner, the Nastar helps to optimize the network, thus improving the QoS and subscriber satisfaction. 33.3.4 Modifying a CDMA VIP Analysis Task This section describes how to modify the attributes of a created CDMA VIP analysis task to meet new analysis requirements. 33.3.5 Viewing a CDMA VIP Analysis Task This section describes how to check CDMA VIP analysis tasks. You can check the attributes, execution progress, and execution results of a CDMA VIP analysis task as required.
33.3.1 Managing CDMA VIP Groups

This section describes how to manage the CDMA VIP groups. You can create VIP groups as required and add certain VIP subscribers to a VIP group to monitor the service quality of these VIP subscribers simultaneously. In addition, you can modify the attributes of a VIP group, delete, or export a VIP group.
Prerequisite
l l
You have logged in to the Nastar client. You have the rights to create VIP subscribers and VIP groups.
Procedure
Step 1 Choose Function List > System Function > VIP Group Management from the navigation tree in the Analysis Task Management window. The VIP Group Management dialog box is displayed. Step 2 Perform the following operations as required: If You Want to ... Create a VIP group by adding one Create a VIP group by importing one Step 3 To create a VIP group by adding one, do as follows: 1. 2. Click the CDMA VIP Group Name tab. Then, click New to open the VIP Group Management - Create VIP Group dialog box. Set Group Name, Priority, and Description. If the * character is present on the right of a parameter, it indicates that the setting of this parameter is mandatory. 3. Select one or multiple VIP subscribers from the Group Member list. You can add new VIP subscribers to this list as required or import VIP subscribers to this list, delete the existing VIP subscribers from the list, or export the VIP subscriber information in the list to .csv or .xls files.
l
Adding a VIP subscriber

Issue 03 (2010-06-30)
a. b.
Click New below the Group Member list to open the VIP User Management dialog box. Set User Name, Phone Number, IMSI, IMSI, ESN, and Description. If the * character is present on the right of a parameter, it indicates that the setting of this parameter is mandatory.
c.
l
Click Confirm. Click Import below the Group Member list to open the Open dialog box. Select an edited VIP subscriber file, and then click Open. If a VIP subscriber file in .xls format is selected and the file contains multiple worksheets, a prompt is displayed. In this case, select the worksheet to be imported.
c.
After the import is complete, perform the operations as prompted. The number of new records, the number of updated records, and the number of failed records are displayed.

Step 4 To create a VIP group by importing one, do as follows: 1. 2. Click Import on the CDMA VIP Group Name tab page to open the Open dialog box. Select an edited VIP group file, and then click Open. If a VIP group file in .xls format is selected and the file contains multiple worksheets, a prompt is displayed. In this case, select the worksheet to be imported.
NOTE
In a VIP group file, if Priority and Description of the same VIP group in different rows are different, the Nastar displays Priority and Description in the last row of the VIP group in the Priority and Description column on the CDMA VIP Group Name tab page. It is recommended that the description and priority information in different rows regarding a VIP group be the same when you define VIP group information. If the Priority column is empty, Medium is displayed by default.
3. 4.
Click Import. In the Confirm dialog box, click Confirm after checking the number of added records, updated records, and failed records.
33-6
In the Import CDMA VIP group dialog box, , , and indicate the VIP group that is successfully imported, partially imported, and failed to be imported respectively. 5. Perform the operations as prompted.
l l
are
If abnormal records exist in the imported information, VIP groups that are marked by are displayed. In this case, perform the following operations: Click Export Fail Record to export the failed records as a file so that you can make modifications based on the error information to complete the current import task. Click Close to complete the current import task.
----End
Postrequisite
l
Modifying the attributes of a VIP group 1. Select a VIP group on the CDMA VIP Group Name tab page and then click Modified to open the CDMA VIP user group management - Modify VIP user group dialog box. Modify the relevant parameters. For description of the parameters, see 33.6.1 Parameters for Creating and Modifying CDMA VIP Subscribers and VIP Groups. 3. Click Confirm. If the VIP group is used by certain tasks, the modification does not affect the ongoing tasks. If the VIP group is used by a periodic task, the related information is updated in the next period after the modification.
2.
Viewing the information about members of a VIP group On the CDMA VIP Group Name tab page, double-click a VIP group to view the detailed information about the members of the VIP group.
Deleting a VIP group 1. 2. Select a VIP group on the CDMA VIP Group Name tab page, and then click Delete. In the displayed Confirm dialog box, click Confirm. If the VIP group is used by certain tasks, the modification does not affect the ongoing tasks. If the VIP group is used by a periodic task, the related information is updated in the next period after the modification.
Exporting the VIP group information to .csv or .xls files 1. 2. On the CDMA VIP Group Name tab page, click Export. Set a file name and specify the save path and file type in the displayed Save dialog box, and then click Save.
You can also select all VIP groups, and find or save a VIP group through the shortcut menu prompted by right-clicking on the CDMA VIP Group Name tab page.

This section describes how to create an end-to-end (E2E) task. After you set an E2E task in the Nastar, the Nastar issues MML commands to the M2000. The M2000 then sends these MML
commands to the corresponding NEs. Finally, the NEs perform the measurement tasks and generate results.
Prerequisite
l l l
Context
TIP
Procedure
l
3.
In E2E Task List, select a task. Table 33-2 describes the mapping between E2E tasks and analysis tasks. Table 33-2 Mapping between E2E tasks and analysis tasks E2E Tasks VIP subscriber monitoring task Analysis tasks CDMA VIP analysis task
Issue 03 (2010-06-30)
33-8
E2E Tasks Interference data task Spectrum data task 1x neighboring cell data task DO neighboring cell data task Complaint analysis data task
Analysis tasks CDMA uplink-interference-ranking analysis task CDMA uplink-interference-spectrum analysis task CDMA co-frequency neighboring cell analysis task CDMA co-frequency neighboring cell analysis task CDMA complaint assistant analysis task
Postrequisite
NOTE
The attributes of a created E2E task cannot be modified. If you want to change certain parameter values, you need to delete the original task and then create another one.
To update the task list, click Refresh in the lower-right corner of the E2E Task Management window.
33.3.3 Creating a CDMA VIP Analysis Task

This section describes how to create a CDMA VIP analysis task. In a CDMA VIP analysis task, the Nastar collects and analyzes the number of service call reports, traffic volume, and KPIs by VIP groups or VIPs according to the IMSIs obtained from the MSs. In this manner, the Nastar helps to optimize the network, thus improving the QoS and subscriber satisfaction.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the VIP analysis function. The E2E task, collection task, and data import task corresponding to the VIP analysis task are normal. The VIP analysis task can be created successfully even if the prerequisites are not met. The execution of the VIP analysis task, however, will always fail because the data to be analyzed is not imported to the database.
Context
l
A VIP analysis task can be performed once or periodically. A periodic task is performed by hours. 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. Before you create an analysis task, ensure that the data related to the analysis task is imported to the database so that the analysis task can be executed normally. For details, see 2.14 Querying NE Data.
Procedure
in the Analysis Task Management window. The Analysis Task Management-New Step 1 Click Task dialog box is displayed. Step 2 Set the basic task information such as Task Name, Task Type, Execution Type, and Note. Step 3 Click Next. Step 4 Set Task Configuration and Time Setting for Cycle Task Data/Time Setting for Once Task Data. If Once Task is selected in the previous step, you need to set only Data Time Scope. Step 5 Click Next. Step 6 On the VIP Group Selection tab page, select one or multiple VIP groups and select Report Raw Data as required. If you select Report Raw Data, the raw call records are collected when the VIP KPI overview information is provided. Step 7 On the VIP KPI Threshold Setting tab page, set the threshold of each KPI.

l
In the analysis report of the corresponding task, if the KPI value of a subscriber does not reach the threshold, it is considered that the KPI is problematic. The values of the KPIs related to the success rate can range from 0 to 100%. The values of the KPIs related to delay can be set to any number that is greater than zero. To apply the modified threshold to subsequent VIP analysis tasks, click App. To restore the modified threshold to the initial value, click Default.
Postrequisite
l
NOTE
1.
Click the CDMA VIP Analysis node in the navigation tree in the Analysis Task Management window. If you choose the Subject Function node, all the performance analysis tasks are displayed in the task list on the right.
2. 3.
l
button.
Suspending a task To delay the task execution, you can suspend a VIP analysis task that is in the idle state. Then, the VIP analysis task becomes suspended.
NOTE
Only the VIP analysis tasks that are not suspended can be executed.
1.
2.
button.
l
Restoring a task You can restore a suspended VIP analysis task to the idle state for execution.
NOTE
Only the VIP analysis tasks that are in the idle state can be executed.
1.
2.
Issue 03 (2010-06-30)
button.
33-11
33.3.4 Modifying a CDMA VIP Analysis Task

This section describes how to modify the attributes of a created CDMA VIP analysis task to meet new analysis requirements.
Prerequisite
l l l
You have logged in to the Nastar client. You are authorized to perform the VIP analysis function. A CDMA VIP analysis task is created.
Context
Procedure
Step 1 Click the CDMA VIP Analysis node in the navigation tree in the Analysis Task Management window. If you choose the Subject Function node, all the performance analysis tasks are displayed in the task list on the right. Step 2 Select a task from the task list in the upper-right pane. Double-click the task or click Analysis Task Management-Modify Task Information dialog box is displayed. Step 3 Modify the relevant parameters.
l
. The
For description of the parameters, see 33.6.3 Parameters for Creating and Modifying CDMA VIP Analysis Tasks. You can modify the Note parameter in the basic information, the Data Time Scope and Task Start At parameters in the time information, the information about VIP groups, and the information about VIP KPIs.
33.3.5 Viewing a CDMA VIP Analysis Task

This section describes how to check CDMA VIP analysis tasks. You can check the attributes, execution progress, and execution results of a CDMA VIP analysis task as required.
Prerequisite
l l
You have logged in to the Nastar client. A CDMA VIP analysis task is created.
33-12
Issue 03 (2010-06-30)
Procedure
Step 1 Click the CDMA VIP Analysis node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, the task list on the right displays all the performance analysis tasks. Step 2 Perform the following operations as required: If You Want to ... Check the attributes of a CDMA VIP analysis task Then ... Select a task from the task list in the upper-right pane. Double-click the task or click .
You can check the attributes of the selected task and modify the relevant parameter settings. For detailed operations, see 33.3.4 Modifying a CDMA VIP Analysis Task. Check the execution progress of the active Select a task from the task list in the upper-right task pane. Then, you can view the execution progress of the task in the Progress column. Check the task execution results Select a task from the task list in the upper-right pane. Then, you can view the results of the previous execution of the selected task in the Last Running Result column. You can view the analysis results of a selected task in the lower-right pane.
----End
Postrequisite
l
The system enables you to search for task information. You can click any line in the task information list and then press Ctrl+F to display the Find dialog box. Type the keywords, that is, the search conditions, in the dialog box. Then, the system searches for the task information that meets the search condition.
Issue 03 (2010-06-30)
33.4 Querying CDMA VIP Analysis Reports

This section describes how to query CDMA VIP analysis reports. By monitoring the number of service call reports, traffic, and KPIs of the selected VIP, you can learn about the QoS of the VIP and identify and solve the network problems that may cause VIP complaints.
Prerequisite
l l l l
You have logged in to the Nastar client. The ItmService process of the Nastar runs normally. You are authorized to perform the VIP analysis. The E2E task, collection task, and data import task corresponding to the VIP analysis task are normal. The VIP analysis task is executed successfully.
Procedure
Step 1 Click the CDMA VIP Analysis node in the navigation tree in the Analysis Task Management window. If you choose Subject Function, all the performance analysis tasks are displayed in the task list on the right. Step 2 Select a task from the task list in the upper right pane. All the analysis results of the selected task are displayed in the lower right pane. Step 3 Double-click a result record, or right-click a result record and then choose CDMA VIP Analysis from the shortcut menu. The CDMA VIP Analysis window is displayed. This operation can be performed only when Result Status of a task is Complete. Otherwise, the shortcut menu is unavailable. Step 4 Select one VIP or VIP group from the VIP group overview table on the left of the CDMA VIP Analysis window, and then view the details of the KPIs of each service and the trend of these KPIs on the 1X-CS KPI, 1X-PS KPI, EVDO KPI, 1X Active Cell and EV-DO Active Cell tab pages on the right.
l
When a VIP group is selected as the analysis object, the trend of the KPIs is not displayed in the KPI list area on the right. Initially, Object above the VIP group overview table on the left is set to Group. After you change the value to User, you need to select a Group, namely, the VIP group to be analyzed. In this case, the KPIs of all VIPs in the specified group are displayed in the VIP group overview table. In addition, the trend of a specific KPI of the selected VIP is displayed in the area below the KPI list on the right. You can double-click the trend chart to zoom in on the chart, and then double-click the chart again to restore the chart to the original size.
The trend charts are classified into the following types:
1X-CS KPI trend chart, which shows the trend of some KPIs of the CS services in a 1X network
33-14
1X-PS KPI trend chart, which shows the trend of some KPIs of the PS services in a 1X network EV-DO KPI trend chart, which shows the trend of some KPIs of the EV-DO services
Select one VIP group or VIP from the VIP group overview table on the left of the window, and then click the Active Cell tab on the right of the window to view the analysis result and geographical display result of the active cell corresponding to the selected VIP group or VIP. The description of the geographical display of the active cell corresponding to the VIP group or VIP is as follows:
If the geographical display is started for the first time, no record is contained in the analysis result list of the active cell, and all the active cells of the selected VIP group or VIP are highlighted on the map.
For description of the parameters, see 33.6.4 Parameters for Querying CDMA VIP Analysis Reports.
----End
Postrequisite
l
The Nastar supports the export of the query results. For details, see 33.5 Exporting CDMA VIP Analysis Reports. If certain KPIs of a VIP are abnormal according to the query result and thus further analysis is required, select the basic information of the VIP and then choose Start Further Analysis from the shortcut menu to start the complaint assistant support function for further analysis. The system enables you to search for the query results. You can click any line in the query result list, and then press Ctrl+F. In the displayed Find dialog box, type the keywords, that is, the search condition. Then, the system searches for the query result that meets the search condition. You can select Case sensitive to ensure that the keywords you type are case sensitive. You can select Up or Down in the Direction area to determine the search direction.
33.5 Exporting CDMA VIP Analysis Reports

This section describes how to export CDMA VIP analysis reports. You can export the queried VIP analysis results as .csv or .xls files as required. The exported VIP analysis results help you identify and solve the network problems that may cause VIP complaints.
Prerequisite
l l
You have logged in to the Nastar client. You have queried the CDMA VIP analysis reports.
Procedure
Step 1 Click in the CDMA VIP Analysis window. The Save dialog box is displayed.
Step 2 Specify the file name, file type, and save path. Then, click Save. The saved .csv or .xls file is opened automatically so that you can view it conveniently. ----End
33.6 Reference for the CDMA VIP Analysis GUI

This section describes the interface for CDMA VIP analysis and the relevant parameters. Before performing relevant operations, familiarize yourself with the functions of CDMA VIP analysis. 33.6.1 Parameters for Creating and Modifying CDMA VIP Subscribers and VIP Groups This section describes the parameters of VIP subscribers and groups. You can refer to the parameter description when creating or modifying a VIP subscriber or VIP group. 33.6.2 Parameters of CDMA E2E Tasks This section describes the parameters of CDMA E2E tasks. You can refer to the description when creating or modifying a CDMA E2E task. 33.6.3 Parameters for Creating and Modifying CDMA VIP Analysis Tasks This section describes the parameters for creating and modifying the tasks of analyzing the QoS of CDMA VIP subscribers. You can refer to the description when creating or modifying a CDMA VIP analysis task. 33.6.4 Parameters for Querying CDMA VIP Analysis Reports This section describes the parameters for querying CDMA VIP analysis reports. You can refer to the parameter description when querying a CDMA VIP analysis report.
33.6.1 Parameters for Creating and Modifying CDMA VIP Subscribers and VIP Groups
This section describes the parameters of VIP subscribers and groups. You can refer to the parameter description when creating or modifying a VIP subscriber or VIP group.
Description of the parameters of VIP subscribers

Parameter User Name Description Indicates the name of a VIP subscriber. Value range:
l l l l
A maximum of 128 characters Any character except for ~ ! # $ % ^ * + = | \ / , ' ` Unique and not null Case sensitive
Phone Number IMSI ESN MEID
Indicates the mobile number of a VIP subscriber. Indicates the International Mobile Subscriber Identity (IMSI) of the VIP subscriber. Indicates the Equipment Serial Number (ESN) of the VIP subscriber. Indicates the Mobile Equipment Identifier (MEID) of the VIP subscriber.
33-16
Issue 03 (2010-06-30)
Description Indicates the description of the VIP subscriber. Value range:

l l
A maximum of 512 characters Any character except for ~ ! # $ % ^ * + = | \ / , ' `
Description of the parameters of VIP groups

Parameter Group Name Description Indicates the name of a VIP group. Value range:
l l l l
A maximum of 128 characters Any character except for ~ ! # $ % ^ * + = | \ / , ' ` Unique and not null Case sensitive
Priority
Indicates the priority of a VIP group, such as Very Important, Important, Medium, Low, and Very Low. Select a parameter value from the drop-down list box.
Description
Indicates the description of the VIP group. Value range:

l l
A maximum of 512 characters Any character except for ~ ! # $ % ^ * + = | \ / , ' `
Group Member
Indicates all the VIP subscribers of the VIP group.

Parameter Basic Information Task Name OSS Name Description Indicates the name of an E2E task. Indicates the name of the OSS related to the task.
Issue 03 (2010-06-30)
33-17
Description Indicates the types of E2E tasks. You can select one of the following E2E tasks: VIP subscriber monitoring task, interference data task, spectrum data task, 1x neighboring cell data task, DO neighboring cell data task, or complaint analysis data task. Indicates the time when the task starts to run. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. End Time Indicates the time when the task stops running. The format is the same as that in the district setting, for example, YYYY-MM-DD hh:mm:ss. The start time must be earlier than the end time. NE Object Indicates the NE related to the E2E task.
Begin Time
33.6.3 Parameters for Creating and Modifying CDMA VIP Analysis Tasks
This section describes the parameters for creating and modifying the tasks of analyzing the QoS of CDMA VIP subscribers. You can refer to the description when creating or modifying a CDMA VIP analysis task.
Parameter Basic Information Task Name Description Indicates the name of a VIP analysis task. Value range:
l l
l l
Choose CDMA VIP Analysis Task from the navigation tree.

l
Once task: The system executes the created tasks only once at the specified time. Period task: The system executes the created tasks at the preset time.
33-18
Issue 03 (2010-06-30)
Parameter Note

l l
Time Information
Begin Date
Indicates time for starting a task. The start time should be later than the current server time. You can either type the time value in this field, or click to select the date and time in the Date Selection dialog box. This parameter is valid for only periodic tasks.
Cycle
l l
Unit: day. Interval: 1 to 30.
This parameter is valid for only periodic tasks. Execution Times Indicates the times that a periodic task is executed. If this parameter is set to 0, you can infer that the task is executed all the time. Value range: 0 to 9999. This parameter is valid for only periodic tasks. Data Time Scope The start time should precede the end time. You can either type the time value in this field, or click to select the date and time in the Date Selection dialog box. This parameter is valid for only one-time tasks. Task Start At Indicates the time when the analysis task is executed. The time specified in this field should not precede the end time specified in the Data Time Scope field. Time
l
All day: The task is executed every day during the selected time range. Specify: The task is executed during the specified time segment every day during the selected time range. The time segment cannot overlap. The start time of the next time segment must be later than or the same as the end time of the current time segment.
Issue 03 (2010-06-30)
33-19
Parameter Object Information VIPs VIP Groups
Description If you select this option, the navigation tree displays all the VIP subscribers of the entire network. If you select this option, the navigation tree displays all the VIP groups of the entire network.
33.6.4 Parameters for Querying CDMA VIP Analysis Reports

This section describes the parameters for querying CDMA VIP analysis reports. You can refer to the parameter description when querying a CDMA VIP analysis report.
Description of the parameters related to 1X-CS KPIs

Parameter Call attempt times Call drop times Call drop rate(%) Number of unsuccessful CS call setups Call setup failure rate (%) Duration of CS call setup(s) Average originatedcall access duration (s) Average terminatedcall access duration (s) Occupancy percentage of calls in pilot strength (0,-3) (s) Occupancy percentage of calls in pilot strength (-3,-6) (s) Description Number of CS call attempts Number of CS call drops CS call drop rate Number of successful CS call setups
CS call setup failure rate CS call duration Unit: millisecond Average duration of CS originating-call access. Unit: millisecond
Average duration of CS originated-call access. Unit: millisecond
Total duration of the CS calls with the pilot strength ranging from 0 dBm to -3 dBm. Unit: second
Total duration of the CS calls with the pilot strength ranging from -3 dBm to -6 dBm. Unit: second
33-20
Issue 03 (2010-06-30)
Parameter Occupancy percentage of calls in pilot strength (-6,-9) (s) Occupancy percentage of calls in pilot strength (-9,-15)(s) Occupancy percentage of calls in pilot strength (-15,-32)(s) Bad radio environment rate(%) Average FER on forward TCH(%) Average FER on reverse TCH(%) SHO frequency(%) Number of suspected one-way audio occurrences
Description Total duration of the CS calls with the pilot strength ranging from -6 dBm to -9 dBm. Unit: second
Proportion of bad CS radio environments Average CS forward FER Average CS reverse FER Soft handoff frequency during the CS services Number of suspected one-way audio occurrences during the CS services
Description of the parameters related to 1X-PS KPIs

Parameter Call attempt times Call drop times Call drop rate(%) Number of unsuccessful CS call setups Call setup failure rate (%) Duration of CS call setup(s) Average originatedcall access duration (s)
Issue 03 (2010-06-30)
Description Number of PS call attempts Number of PS call drops PS call drop rate Number of successful PS call setups
PS call setup failure rate PS call duration Unit: millisecond Average duration of PS originating-call access. Unit: millisecond
33-21
Parameter Average terminatedcall access duration (s) Occupancy percentage of calls in pilot strength (0,-3) (s) Occupancy percentage of calls in pilot strength (-3,-6) (s) Occupancy percentage of calls in pilot strength (-6,-9) (s) Occupancy percentage of calls in pilot strength (-9,-15)(s) Occupancy percentage of calls in pilot strength (-15,-32)(s) Bad radio environment rate(%) Total forward data throughput[byte] Total reverse data throughput[byte] Average forward rate [Kbps] Average reverse rate [Kbps] Average FER on forward TCH(%) Average FER on reverse TCH(%) Average FER on forward SCH(%) Average FER on reverse SCH(%)
33-22
Description Average duration of PS originated-call access. Unit: millisecond
Total duration of the PS calls with the pilot strength ranging from 0 dBm to -3 dBm. Unit: second
Total duration of the PS calls with the pilot strength ranging from -3 dBm to -6 dBm. Unit: second
Proportion of bad PS radio environments Total PS forward data traffic. Unit: byte Total PS reverse data traffic. Unit: byte Average PS forward data rate. Unit: kbit/s Average reverse data rate during the PS services. Unit: kbit/s Average FER of the forward TCHs during the PS services Average FER of the reverse TCHs during the PS services Average FER of the forward SCHs during the PS services Average FER of the reverse SCHs during the PS services
Issue 03 (2010-06-30)
Parameter SHO frequency(%)
Description Soft handoff frequency during the PS services
Description of parameters related to EV-DO KPIs

Parameter Access setup times Access setup failure rate(%) Call drop times Call drop rate(%) Unsuccessful access authentication rate (%) Paging success rate (%) Duration of CS call setup(s) Access connection setup average duration(s) Occupancy percentage of calls in pilot strength (0,-2) (s) Occupancy percentage of calls in pilot strength (-2,-4.5)(s) Occupancy percentage of calls in pilot strength (-4.5,-7)(s) Occupancy percentage of calls in pilot strength(-7,-10) (s) Description Requests for setting up EV-DO services EV-DO call setup failure rate EV-DO call drops EV-DO call drop rate EV-DO access authentication failure rate
EV-DO paging success rate EV-DO call duration Unit: millisecond Average duration for setting up the EV-DO services Unit: millisecond
Total duration of the EV-DO calls with the pilot strength ranging from 0 dBm to -2 dBm. Unit: second
Total duration of the EV-DO calls with the pilot strength ranging from -2 dBm to -4.5 dBm. Unit: second
Total duration of the EV-DO calls with the pilot strength ranging from -4.5 dBm to -7 dBm. Unit: second
Total duration of the EV-DO calls with the pilot strength ranging from -7 dBm to -10 dBm. Unit: second
Issue 03 (2010-06-30)
33-23
Parameter Occupancy percentage of calls in pilot strength (-10,-32)(s) Bad radio environment rate(%) Total forward data throughput[byte] Total reverse data throughput[byte] Average forward rate during connection [Kbps] Average reverse rate during connection [Kbps] RLP forward retransmission rate (%) RLP reverse retransmission rate (%) Reverse FER(%) Virtual SHO frequency(%) Virtual SHO intermittence rate(%)
Description Total duration of the EV-DO calls with the pilot strength ranging from -10 dBm to -32 dBm. Unit: second
Proportion of bad EV-DO radio environments Total forward data traffic during the EV-DO services. Unit: byte Total reverse data traffic during the EV-DO services. Unit: byte Average forward data rate during the EV-DO services. Unit: kbit/s
Average reverse data rate during the EV-DO services. Unit: kbit/s
RLP forward retransmission rate during the EV-DO services
RLP forward retransmission rate during the EV-DO services
Average R-FER during the EV-DO services Virtual soft handoff frequency during the EV-DO services Virtual soft handoff interruption frequency during the EV-DO services
Description of parameters of 1X KPIs in active cells

Parameter BSC Name Carrier name Number of voice service accesses Number of voice service abnormal accesses Description ID of the BSC to which the active cell belongs Name of an active carrier Number of CS access attempts of a VIP group or VIP under an active carrier Number of abnormal access of a VIP group or VIP under an active carrier to perform the CS services
33-24
Issue 03 (2010-06-30)
Parameter Number of voice service normal accesses Number of voice service call drops Number of data service accesses Number of data service abnormal accesses Number of data service normal accesses Number of data service call drops
Description Number of normal access of a VIP group or VIP under an active carrier to perform the CS services Number of call drops of a VIP group or VIP under an active carrier during the CS services Number of access attempts of a VIP group or VIP under an active carrier to perform the PS services Number of abnormal access of a VIP group or VIP under an active carrier to perform the PS services Number of normal access of a VIP group or VIP under an active carrier to perform the PS services Number of call drops of a VIP group or VIP under an active carrier to perform the PS services
Description of parameters of EV-DO KPIs in active cells

Parameter BSC Name Carrier name Number of accesses Number of abnormal accesses Number of normal accesses Number of call drops Description ID of the BSC to which the active cell belongs Name of an active carrier Number of access of a VIP group or VIP under an active carrier Number of abnormal access of a VIP group or VIP under an active carrier Number of normal access of a VIP group or VIP under an active carrier Number of call drops of a VIP group or VIP under an active carrier
Issue 03 (2010-06-30)
33-25

Nastar Operator Guide - (V600R008 - 03)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nastar Operator Guide - (V600R008 - 03)

Uploaded by

Copyright:

Available Formats

Nastar V600R008

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

About This Document

Changes in Issue 03 (2010-06-30)

Changes in Issue 02 (2010-05-30)

Changes in Issue 01 (2010-04-20)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.