0% found this document useful (0 votes)

568 views4,310 pages

Nastar Network Optimization User Guide (V600R014C00 - 05) (PDF) - EN PDF

Uploaded by

m.alnabhani9097

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

568 views4,310 pages

Nastar Network Optimization User Guide (V600R014C00 - 05) (PDF) - EN PDF

Uploaded by

m.alnabhani9097

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

Nastar

V600R014C00

Network Optimization User Guide

Issue 05
Date 2015-02-14

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.

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

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com
Email: support@huawei.com

Issue 05 (2015-02-14) Huawei Proprietary and Confidential i

About This Document

Purpose
The Nastar provides a complete solution for wireless network performance analysis. It applies
to GSM/GPRS/EDGE, UMTS/HSUPA/HSDPA, LTE TDD/LTE FDD, and PS Core networks.
This solution can further analyze and locate wireless network problems and supports user
experience-based performance optimization and location-based network evaluation.

Product Version
The products described in this guide are as follows:

Product Name Product Version

Nastar V600R014C00

Intended Audience
This document is intended for network optimization engineers.

Change History
05 (2015-02-14)
This is the fifth official release of V600R014. Compared with issue 04 (2014-11-30) of
V600R014, this issue includes the following changes.

Change Document Description

Type

Modified 7 System Synchronized the new iMAP platform.

Management

Procedure Types Added PDN connectivity Procedure
(Root Cause
Analysis for PS
Core Performance
Problems)

Issue 01 (2014-07-15)
This is the first release. Compared with issue 05 (2014-01-20) of V600R011C00, this issue
incorporates the changes listed in the following table.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential iii

Content Change Description

OSS Information Management l The eNodeB group management function

is added for you to manage eNodeBs and
select NEs.
l This function allows you to migrate NEs
between OSSs.

Nastar System Monitoring This function allows you to monitor the SAU
processing performance, including the
processing capability and the amount of data
being processed.

LTE VIP The function of detecting CSFB and VoLTE

problems is added.

GSM/UMTS/LTE/PS PS Core Complaint The function of detecting CSFB problems is

Analysis Support added.

PS Core Performance Root Cause Analysis l The procedure analysis function

supported by this feature allows you to
collect statistics on and analyze KPIs by
APN.
l This feature allows you to analyze KPI
trends based on the result of a periodic
analysis task.
l This feature allows you to execute an
analysis task based on a 5-minute period.

Organization
1 Nastar Overview
Nastar provides a complete solution for wireless network performance analysis. It is applicable
to GSM/GPRS/EDGE, UMTS/HSUPA/HSDPA, LTE TDD/LTE FDD, and PS Core networks.
This solution can deeply analyze and locate wireless network problems and supports user
experience-based performance optimization and location-based network evaluation.
2 Nastar Quick Start
This chapter describes the basic ideas and operations for network optimization and describes the
Nastar operation processes by using examples. Only basic Nastar operations are described in
this section. It is especially useful to new users. It is recommended that you read this section
when using the Nastar the first time. If you are familiar with Nastar basic operations, refer to
chapters named in *** Network Optimization format to perform theme analysis.
3 GSM Network Optimization
This section describes how to perform GSM network optimization on the Nastar. Through this
function, you can perform various theme analysis functions on the Nastar, such as MR analysis,
frequency analysis, neighboring cell analysis, GSM/UMTS neighboring cell analysis, VIP

Issue 05 (2015-02-14) Huawei Proprietary and Confidential iv

analysis, complaint analysis support, terminal analysis, and network geographic observation. It
is especially useful to users who are familiar with the Nastar basic operations. It is recommended
that you read this section when using the Nastar for the GSM network optimization. If you use
the Nastar in the first time, refer to Nastar Quick Start chapters.

4 UMTS Network Optimization

The Nastar provides network optimization function. The network optimization function helps
you perform various UMTS theme analyses on the Nastar, including coverage analysis, intra-
frequency analysis, inter-frequency analysis, UMTS/GSM neighboring cell analysis, VIP
analysis, complaint analysis support, terminal analysis, and network geographic analysis. These
analysis functions help to quickly locate network problems. It is especially useful to users who
are familiar with the Nastar basic operations. It is recommended that you read this section when
using the Nastar for the UMTS network optimization. If you use the Nastar in the first time, refer
to Nastar Quick Start chapters.

5 LTE Network Optimization

This section describes how to perform LTE network optimization on the Nastar. Through this
function, you can perform various theme analysis functions on the Nastar, such as coverage
analysis, VIP analysis, complaint analysis support, network geographic observation. This helps
to quickly locate network problems. It is especially useful to users who are familiar with the
Nastar basic operations. It is recommended that you read this section when using the Nastar for
the LTE network optimization. If you use the Nastar in the first time, refer to Nastar Quick
Start chapters.

6 PS Core Network Optimization

This section describes how to perform PS Core network optimization on the Nastar. Through
this function, you can perform various theme analysis functions on the Nastar, such as terminal
analysis, VIP analysis, root cause analysis for PS Core performance problems, and complaint
analysis support. It is especially useful to users who are familiar with the Nastar basic operations.
It is recommended that you read this section when using the Nastar for the PS Core network
optimization. If you use the Nastar in the first time, refer to Nastar Quick Start chapters.

7 System Management

The system management includes the following parts, such as security management, log
management, task management, and monitoring the Nastar system. You can manage the
Nastar and monitor the running status of the Nastar through the functions.

Conventions
Symbol Conventions

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

Symbol Description

Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential v

Symbol Description

Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury.

Indicates a potentially hazardous situation which, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.

Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.

General Conventions

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

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in

Courier New.

Command Conventions

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

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential vi

Convention Description

{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.

GUI Conventions

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

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"

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

Keyboard Operations

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

Format Description

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

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

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

Mouse Operations

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

Action Description

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

Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential vii

Action Description

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

Issue 05 (2015-02-14) Huawei Proprietary and Confidential viii

Contents

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

1 Nastar Overview............................................................................................................................1
1.1 Position in Networking...................................................................................................................................................2
1.2 Analysis Data Sources....................................................................................................................................................4
1.2.1 Data Sources for Nastar GSM Analysis......................................................................................................................4
1.2.2 Data Sources for Nastar UMTS Analysis....................................................................................................................6
1.2.3 Data Sources for Nastar LTE Analysis........................................................................................................................9
1.2.4 Data Sources for Nastar PS Core Analysis................................................................................................................13
1.3 Product Functions.........................................................................................................................................................15
1.4 Technical Specifications...............................................................................................................................................18
1.5 Basic Concept/Glossary................................................................................................................................................21
1.6 Guide to the Document.................................................................................................................................................24

2 Nastar Quick Start.......................................................................................................................25

2.1 Nastar Operation Process..............................................................................................................................................27
2.2 Login In to the Nastar...................................................................................................................................................29
2.2.1 Logging In to the Nastar Client.................................................................................................................................29
2.2.2 Interface Description: Nastar Client..........................................................................................................................31
2.2.3 Interface Description: Geographic Observation Results...........................................................................................32
2.3 Configuring OSS and NE Information.........................................................................................................................44
2.3.1 Configuration Procedures..........................................................................................................................................44
2.3.2 Preparations for OSS and NE Information Configuration.........................................................................................46
2.3.3 Configuring eSAU Information.................................................................................................................................51
2.3.4 Configuring OSS Information...................................................................................................................................55
2.3.5 Configuring NE Information on the RAN Side.........................................................................................................63
2.3.6 Configuring NE Information on the CN Side............................................................................................................73
2.3.7 Setting the Vendor Type of EPCs (MMEs)...............................................................................................................78
2.3.8 Configuring Relationships Between HSSs and eNodeBs (Optional)........................................................................79
2.4 Configuring the Anonymous Policy.............................................................................................................................80
2.4.1 Setting the NE Data Anonymization Protection Policy.............................................................................................80
2.4.2 Setting the Nastar Non-Anonymization Data Analysis Switch.................................................................................81
2.5 Preparing Basic Data....................................................................................................................................................84
2.5.1 Introduction to Basic Data.........................................................................................................................................84

Issue 05 (2015-02-14) Huawei Proprietary and Confidential ix

2.5.2 Checking the Integrity of Configuration Data...........................................................................................................89

2.5.3 Preparing Engineering Parameters............................................................................................................................90
2.5.4 Preparing the Map File (Optional)...........................................................................................................................106
2.5.5 Managing NE Groups..............................................................................................................................................110
2.5.6 Managing VIP Groups or VIP Users (VIP Analysis)..............................................................................................115
2.5.7 Managing Terminal Information (Terminal Analysis)............................................................................................126
2.5.8 Managing PS Core Knowledge Bases (Optional)...................................................................................................132
2.5.9 Setting a Mailbox and Address List for Sending Analysis Reports (Optional).......................................................134
2.5.10 Setting Location Parameters for Geographic Observation (Optional)..................................................................136
2.5.11 PS Core Cell Information Management................................................................................................................138
2.6 Subscribing to Analysis Data.....................................................................................................................................142
2.6.1 Basics of Data Subscription.....................................................................................................................................142
2.6.2 Basic Subscription of Analysis Data.......................................................................................................................145
2.6.3 Application Subscription of Analysis Data.............................................................................................................150
2.6.4 Appendix: List of Data Subscription Function of All the Analysis Function.........................................................154
2.7 Checking the Integrity of Analysis Data....................................................................................................................164
2.8 Creating an Analysis Task..........................................................................................................................................166
2.9 Querying Analysis Results.........................................................................................................................................171
2.10 Viewing Geographic Analysis Results (Optional)...................................................................................................173
2.11 Exporting Analysis Reports......................................................................................................................................173
2.12 FAQs.........................................................................................................................................................................174
2.12.1 What Do I Do When the Interface for Analysis Task Management Is Blank After I Log In to the Nastar Client?
..........................................................................................................................................................................................175
2.12.2 What Can I Do If the Subscription Is Longer Than Expected?.............................................................................175
2.12.3 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption
Key....................................................................................................................................................................................176
2.12.4 Supporting Historical Data Analysis on a Changed NE........................................................................................178
2.12.5 Nastar Fails to Identify Information in Non-Specified Languages.......................................................................178
2.12.6 Why Cannot the Nastar Client Be Displayed Again?............................................................................................179
2.12.7 What Do I Do if the System Displays Login U2000/M2000 Failed When a Nastar Basic Data Subscription
Task Fails?........................................................................................................................................................................179
2.12.8 Failed NE Version Upgrade Causes Failures in Subscribing To Basic Data for Some Themes...........................181
2.12.9 Data Subscription Failures in Some Themes Due to the Reconstruction of Existing RNCs into RNC In Pools
..........................................................................................................................................................................................182
2.12.10 How Do I Resolve the Problem that the Analysis Results of All Themes for the Cells Under the Newly Created
Site Are Empty When No Basic Subscription Is Issued Again After the Newly Created Site Is Activated?..................183
2.12.11 What Should I Do When the Percentage Counters in the Cell Performance Analysis and the PS Core Performance
Problem Cause Analysis Exceed 100%?..........................................................................................................................184
2.12.12 What Do I Do When NE Names in the NE Tree Are Different from Those in the NE Details Area?...............184
2.12.13 What Do I Do When the Nastar Client Does Not Respond to the Querying of a Created Task?.......................185

3 GSM Network Optimization..................................................................................................186

3.1 GSM MR Analysis.....................................................................................................................................................188

Issue 05 (2015-02-14) Huawei Proprietary and Confidential x

3.1.1 Basics of GSM MR Analysis...................................................................................................................................188

3.1.2 Preparations for GSM MR Analysis........................................................................................................................195
3.1.3 Process of GSM MR Analysis.................................................................................................................................195
3.1.4 Reference for GSM MR Analysis Interface............................................................................................................204
3.1.5 Reference for GSM MR Analysis Parameters.........................................................................................................211
3.2 GSM Frequency Analysis...........................................................................................................................................262
3.2.1 Basics of GSM Frequency Analysis........................................................................................................................262
3.2.2 Preparations for GSM Frequency Analysis.............................................................................................................271
3.2.3 Process of GSM Frequency Analysis......................................................................................................................272
3.2.4 Reference for GSM Frequency Analysis Interface..................................................................................................284
3.2.5 Reference for GSM Frequency Analysis Parameters..............................................................................................292
3.3 GSM Neighboring Cell Analysis................................................................................................................................323
3.3.1 Basics of GSM Neighboring Cell Analysis.............................................................................................................323
3.3.2 Preparations for GSM Neighboring Cell Analysis..................................................................................................329
3.3.3 Process of GSM Neighboring Cell Analysis...........................................................................................................331
3.3.4 Reference for GSM Neighboring Cell Analysis Interface.......................................................................................342
3.3.5 Reference for GSM Neighboring Cell Analysis Parameters...................................................................................350
3.4 GSM/UMTS Neighboring Cell Analysis...................................................................................................................389
3.4.1 Basics of GSM/UMTS Neighboring Cell Analysis.................................................................................................390
3.4.2 Preparations for GSM/UMTS Neighboring Cell Analysis......................................................................................395
3.4.3 Process of GSM/UMTS Neighboring Cell Analysis...............................................................................................397
3.4.4 Reference for GSM/UMTS Neighboring Cell Analysis Interface..........................................................................405
3.4.5 Reference for GSM/UMTS Neighboring Cell Analysis Parameters.......................................................................410
3.5 GSM Uplink Interference Analysis............................................................................................................................426
3.5.1 Basics of GSM Uplink Interference Analysis.........................................................................................................426
3.5.2 Preparations for GSM Uplink Interference Analysis...............................................................................................432
3.5.3 Process of GSM Uplink Interference Analysis........................................................................................................433
3.5.4 Interface Description: GSM Uplink Interference Analysis.....................................................................................440
3.5.5 Parameters for Viewing GSM Uplink Interference Analysis Results.....................................................................442
3.6 GSM Terminal Analysis.............................................................................................................................................446
3.6.1 Basics of GSM Terminal Analysis..........................................................................................................................446
3.6.2 Preparations for GSM Terminal Analysis...............................................................................................................451
3.6.3 Process of GSM Terminal Analysis........................................................................................................................453
3.6.4 Interface Description: GSM Terminal Analysis......................................................................................................463
3.6.5 Parameters for Viewing GSM Terminal Analysis Results......................................................................................470
3.7 GSM Cell Performance Analysis...............................................................................................................................497
3.7.1 Basics of GSM Cell Performance Analysis.............................................................................................................498
3.7.2 Preparations for GSM Cell Performance Analysis..................................................................................................502
3.7.3 Process of GSM Cell Performance Analysis...........................................................................................................503
3.7.4 Interface Description: GSM Cell Performance Analysis.........................................................................................515
3.7.5 Parameters for Viewing GSM Cell Performance Analysis Results........................................................................517

Issue 05 (2015-02-14) Huawei Proprietary and Confidential xi

3.8 GSM Network Geographic Observation....................................................................................................................542

3.8.1 Basics of GSM Network Geographic Observation..................................................................................................542
3.8.2 Preparations for GSM Network Geographic Observation.......................................................................................547
3.8.3 Process of GSM Network Geographic Observation................................................................................................549
3.8.4 Interface Description: GSM Network Geographic Observation.............................................................................562
3.9 VIP Analysis...............................................................................................................................................................566
3.9.1 Basics of VIP Analysis............................................................................................................................................566
3.9.2 Preparations for VIP Analysis.................................................................................................................................580
3.9.3 Process of VIP Analysis..........................................................................................................................................588
3.9.4 Reference for VIP Analysis Interface......................................................................................................................611
3.9.5 Reference for VIP Analysis Parameters (GSM)......................................................................................................625
3.9.6 Reference for VIP Analysis Parameters (UMTS)...................................................................................................671
3.9.7 Reference for VIP Analysis Parameters (LTE).......................................................................................................748
3.9.8 Reference for VIP Analysis Parameters (PS Core).................................................................................................778
3.9.9 FAQ: How Do I Set the LTE All-Signaling Switch to On?....................................................................................818
3.10 Complaint Analysis Support.....................................................................................................................................819
3.10.1 Basics of Complaint Analysis Support..................................................................................................................820
3.10.2 Preparations for Complaint Analysis Support.......................................................................................................827
3.10.3 Process of Complaint Analysis Support................................................................................................................837
3.10.4 Reference for Complaint Analysis Support Interface............................................................................................854
3.10.5 Reference for Complaint Analysis Support Parameters (GSM)............................................................................890
3.10.6 Reference for Complaint Analysis Support Parameters (UMTS).........................................................................962
3.10.7 Reference for Complaint Analysis Support Parameters (LTE)...........................................................................1047
3.10.8 Reference for Complaint Analysis Support Parameters (PS Core).....................................................................1098
3.10.9 Reference for Complaint Analysis Support Parameters (Combined Analysis)...................................................1203
3.10.10 Appendix: Exception Cause Classification / Key Signaling.............................................................................1212

4 UMTS Network Optimization..............................................................................................1272

4.1 UMTS Coverage Analysis........................................................................................................................................1275
4.1.1 Basics of UMTS Coverage Analysis.....................................................................................................................1275
4.1.2 Preparations for UMTS Coverage Analysis..........................................................................................................1279
4.1.3 Process of UMTS Coverage Analysis...................................................................................................................1279
4.1.4 Interface Description: UMTS Coverage Analysis.................................................................................................1286
4.1.5 Parameters for Viewing UMTS Coverage Analysis Results.................................................................................1290
4.2 UMTS Intra-Frequency Neighboring Cell Analysis................................................................................................1292
4.2.1 Basics of UMTS Intra-Frequency Neighboring Cell Analysis..............................................................................1292
4.2.2 Preparations for UMTS Intra-Frequency Neighboring Cell Analysis...................................................................1297
4.2.3 Process of UMTS Intra-Frequency Neighboring Cell Analysis............................................................................1299
4.2.4 Interface Description: UMTS Intra-Frequency Neighboring Cell Analysis..........................................................1305
4.2.5 Parameters for Viewing UMTS Intra-frequency Neighboring Cell Analysis Results..........................................1309
4.3 UMTS/GSM Neighboring Cell Analysis.................................................................................................................1319
4.3.1 Basics of UMTS/GSM Neighboring Cell Analysis...............................................................................................1319

Issue 05 (2015-02-14) Huawei Proprietary and Confidential xii

4.3.2 Preparations for UMTS/GSM Neighboring Cell Analysis....................................................................................1324

4.3.3 Process of UMTS/GSM Neighboring Cell Analysis.............................................................................................1325
4.3.4 Reference for UMTS/GSM Neighboring Cell Analysis Interface........................................................................1333
4.3.5 Reference for UMTS/GSM Neighboring Cell Analysis Parameters.....................................................................1339
4.4 UMTS Inter-Frequency Neighboring Cell Analysis................................................................................................1357
4.4.1 Basics of UMTS Inter-Frequency Neighboring Cell Analysis..............................................................................1357
4.4.2 Preparations for UMTS Inter-Frequency Neighboring Cell Analysis...................................................................1362
4.4.3 Process of UMTS Inter-Frequency Neighboring Cell Analysis............................................................................1363
4.4.4 Interface Description: UMTS Inter-Frequency Neighboring Cell Analysis..........................................................1371
4.4.5 Parameters for Viewing UMTS Inter-frequency Neighboring Cell Analysis Results..........................................1375
4.5 UMTS Pilot Pollution Analysis................................................................................................................................1385
4.5.1 Basics of UMTS Pilot Pollution Analysis.............................................................................................................1385
4.5.2 Preparations for UMTS Pilot Pollution Analysis..................................................................................................1390
4.5.3 Process of UMTS Pilot Pollution Analysis...........................................................................................................1391
4.5.4 Interface Description: UMTS Pilot Pollution Analysis.........................................................................................1397
4.5.5 Parameters for Viewing UMTS Pilot Pollution Analysis Results.........................................................................1402
4.6 UMTS Uplink Interference Analysis........................................................................................................................1413
4.6.1 Basics of UMTS Uplink Interference Analysis.....................................................................................................1413
4.6.2 Preparations for UMTS Uplink Interference Analysis..........................................................................................1416
4.6.3 Process of UMTS Uplink Interference Analysis...................................................................................................1417
4.6.4 Interface Description: UMTS Uplink Interference Analysis.................................................................................1423
4.6.5 Parameters for Viewing UMTS Uplink Interference Analysis Results.................................................................1424
4.7 UMTS Terminal Analysis........................................................................................................................................1426
4.7.1 Basics of UMTS Terminal Analysis......................................................................................................................1427
4.7.2 Preparations for UMTS Terminal Analysis...........................................................................................................1427
4.7.3 Process of UMTS Terminal Analysis....................................................................................................................1429
4.7.4 Interface Description: UMTS Terminal Analysis..................................................................................................1444
4.7.5 Parameters for Viewing UMTS Terminal Analysis Results.................................................................................1451
4.8 UMTS Cell Performance Analysis...........................................................................................................................1500
4.8.1 Basics of UMTS Cell Performance Analysis........................................................................................................1501
4.8.2 Preparations for UMTS Cell Performance Analysis.............................................................................................1505
4.8.3 Process of UMTS Cell Performance Analysis......................................................................................................1506
4.8.4 Interface Description: UMTS Cell Performance Analysis....................................................................................1527
4.8.5 Parameters for Viewing UMTS Cell Performance Analysis Results....................................................................1529
4.8.6 FAQ: What Do I Do When NE Objects Are Missing from the Analysis Results?...............................................1548
4.9 UMTS Network Geographic Observation................................................................................................................1549
4.9.1 Basics of UMTS Network Geographic Observation.............................................................................................1549
4.9.2 Preparations for UMTS Network Geographic Observation..................................................................................1554
4.9.3 Process of UMTS Network Geographic Observation...........................................................................................1556
4.9.4 Interface Description: UMTS Network Geographic Observation.........................................................................1567
4.9.5 Parameters for Viewing UMTS Network Geographic Observation Results.........................................................1571

Issue 05 (2015-02-14) Huawei Proprietary and Confidential xiii

4.10 VIP Analysis...........................................................................................................................................................1577

4.10.1 Basics of VIP Analysis........................................................................................................................................1577
4.10.2 Preparations for VIP Analysis.............................................................................................................................1591
4.10.3 Process of VIP Analysis......................................................................................................................................1599
4.10.4 Reference for VIP Analysis Interface..................................................................................................................1622
4.10.5 Reference for VIP Analysis Parameters (UMTS)...............................................................................................1636
4.10.6 Reference for VIP Analysis Parameters (GSM)..................................................................................................1713
4.10.7 Reference for VIP Analysis Parameters (LTE)...................................................................................................1759
4.10.8 Reference for VIP Analysis Parameters (PS Core).............................................................................................1789
4.10.9 FAQ: How Do I Set the LTE All-Signaling Switch to On?................................................................................1829
4.11 Complaint Analysis Support...................................................................................................................................1830
4.11.1 Basics of Complaint Analysis Support................................................................................................................1831
4.11.2 Preparations for Complaint Analysis Support.....................................................................................................1838
4.11.3 Process of Complaint Analysis Support..............................................................................................................1848
4.11.4 Reference for Complaint Analysis Support Interface..........................................................................................1865
4.11.5 Reference for Complaint Analysis Support Parameters (UMTS).......................................................................1901
4.11.6 Reference for Complaint Analysis Support Parameters (GSM)..........................................................................1986
4.11.7 Reference for Complaint Analysis Support Parameters (LTE)...........................................................................2058
4.11.8 Reference for Complaint Analysis Support Parameters (PS Core).....................................................................2108
4.11.9 Reference for Complaint Analysis Support Parameters (Combined Analysis)...................................................2213
4.11.10 Appendix: Exception Cause Classification / Key Signaling.............................................................................2222

5 LTE Network Optimization...................................................................................................2282

5.1 LTE Coverage Analysis............................................................................................................................................2284
5.1.1 Basics of LTE Coverage Analysis.........................................................................................................................2284
5.1.2 Preparations for LTE Coverage Analysis..............................................................................................................2288
5.1.3 Process of LTE Coverage Analysis.......................................................................................................................2289
5.1.4 Interface Description: LTE Coverage Analysis.....................................................................................................2301
5.1.5 Parameters for Viewing LTE Coverage Analysis Results.....................................................................................2306
5.2 LTE Cell Performance Analysis...............................................................................................................................2308
5.2.1 Basics of LTE Cell Performance Analysis............................................................................................................2308
5.2.2 Preparations for LTE Cell Performance Analysis.................................................................................................2313
5.2.3 Process of LTE Cell Performance Analysis..........................................................................................................2315
5.2.4 Interface Description: LTE Cell Performance Analysis........................................................................................2326
5.2.5 Parameters for Viewing LTE Cell Performance Analysis Results........................................................................2328
5.3 LTE Terminal Analysis............................................................................................................................................2341
5.3.1 Basics of LTE Terminal Analysis.........................................................................................................................2341
5.3.2 Preparations for LTE Terminal Analysis...............................................................................................................2346
5.3.3 Process of LTE Terminal Analysis........................................................................................................................2348
5.3.4 Interface Description: LTE Terminal Analysis.....................................................................................................2359
5.3.5 Parameters for Viewing LTE Terminal Analysis Results.....................................................................................2364
5.4 LTE Network Geographic Observation....................................................................................................................2405

Issue 05 (2015-02-14) Huawei Proprietary and Confidential xiv

5.4.1 Basics of LTE Network Geographic Observation.................................................................................................2405

5.4.2 Preparations for LTE Network Geographic Observation......................................................................................2411
5.4.3 Process of LTE Network Geographic Observation...............................................................................................2414
5.4.4 Interface Description: LTE Network Geographic Observation.............................................................................2427
5.4.5 Parameters for Viewing LTE Network Geographic Observation Results.............................................................2432
5.5 VIP Analysis.............................................................................................................................................................2437
5.5.1 Basics of VIP Analysis..........................................................................................................................................2437
5.5.2 Preparations for VIP Analysis...............................................................................................................................2451
5.5.3 Process of VIP Analysis........................................................................................................................................2459
5.5.4 Reference for VIP Analysis Interface....................................................................................................................2482
5.5.5 Reference for VIP Analysis Parameters (LTE).....................................................................................................2496
5.5.6 Reference for VIP Analysis Parameters (GSM)....................................................................................................2525
5.5.7 Reference for VIP Analysis Parameters (UMTS).................................................................................................2571
5.5.8 Reference for VIP Analysis Parameters (PS Core)...............................................................................................2648
5.5.9 FAQ: How Do I Set the LTE All-Signaling Switch to On?..................................................................................2688
5.6 Complaint Analysis Support.....................................................................................................................................2689
5.6.1 Basics of Complaint Analysis Support..................................................................................................................2690
5.6.2 Preparations for Complaint Analysis Support.......................................................................................................2697
5.6.3 Process of Complaint Analysis Support................................................................................................................2707
5.6.4 Reference for Complaint Analysis Support Interface............................................................................................2724
5.6.5 Reference for Complaint Analysis Support Parameters (LTE).............................................................................2760
5.6.6 Reference for Complaint Analysis Support Parameters (GSM)............................................................................2811
5.6.7 Reference for Complaint Analysis Support Parameters (UMTS).........................................................................2883
5.6.8 Reference for Complaint Analysis Support Parameters (PS Core).......................................................................2968
5.6.9 Reference for Complaint Analysis Support Parameters (Combined Analysis).....................................................3073
5.6.10 Appendix: Exception Cause Classification / Key Signaling...............................................................................3082
5.6.11 FAQ: Why Are CHRs Related to RRC Connection Setup Failures Not Displayed in LTE Complaint Analysis
Support Results?.............................................................................................................................................................3141

6 PS Core Network Optimization............................................................................................3143

6.1 PS Core Terminal Analysis......................................................................................................................................3145
6.1.1 Basics of PS Core Terminal Analysis....................................................................................................................3145
6.1.2 Preparations for PS Core Terminal Analysis.........................................................................................................3150
6.1.3 Process of PS Core Terminal Analysis..................................................................................................................3151
6.1.4 Interface Description: PS Core Terminal Analysis...............................................................................................3158
6.1.5 Parameters for PS Terminal Core Analysis...........................................................................................................3163
6.2 Root Cause Analysis for PS Core Performance Problems.......................................................................................3179
6.2.1 Basics of Root Cause Analysis for PS Core Performance Problems....................................................................3180
6.2.2 Preparations for Root Cause Analysis for PS Core Performance Problems..........................................................3185
6.2.3 Process of Root Cause Analysis for PS Core Performance Problems...................................................................3186
6.2.4 Interface Summary for Results of Root Cause Analysis on PS Core Performance Problems..............................3196
6.2.5 Parameters for Root Cause Analysis for PS Core Performance Problems............................................................3205

Issue 05 (2015-02-14) Huawei Proprietary and Confidential xv

6.2.6 Appendix: Procedure Types (Root Cause Analysis for PS Core Performance Problems)....................................3215
6.3 VIP Analysis.............................................................................................................................................................3267
6.3.1 Basics of VIP Analysis..........................................................................................................................................3268
6.3.2 Preparations for VIP Analysis...............................................................................................................................3281
6.3.3 Process of VIP Analysis........................................................................................................................................3289
6.3.4 Reference for VIP Analysis Interface....................................................................................................................3312
6.3.5 Reference for VIP Analysis Parameters (PS Core)...............................................................................................3326
6.3.6 Reference for VIP Analysis Parameters (GSM)....................................................................................................3366
6.3.7 Reference for VIP Analysis Parameters (UMTS).................................................................................................3412
6.3.8 Reference for VIP Analysis Parameters (LTE).....................................................................................................3489
6.3.9 FAQ: How Do I Set the LTE All-Signaling Switch to On?..................................................................................3519
6.4 Complaint Analysis Support.....................................................................................................................................3520
6.4.1 Basics of Complaint Analysis Support..................................................................................................................3521
6.4.2 Preparations for Complaint Analysis Support.......................................................................................................3528
6.4.3 Process of Complaint Analysis Support................................................................................................................3538
6.4.4 Reference for Complaint Analysis Support Interface............................................................................................3555
6.4.5 Reference for Complaint Analysis Support Parameters (PS Core).......................................................................3591
6.4.6 Reference for Complaint Analysis Support Parameters (GSM)............................................................................3696
6.4.7 Reference for Complaint Analysis Support Parameters (UMTS).........................................................................3767
6.4.8 Reference for Complaint Analysis Support Parameters (LTE).............................................................................3852
6.4.9 Reference for Complaint Analysis Support Parameters (Combined Analysis).....................................................3862
6.4.10 Appendix: Exception Cause Classification / Key Signaling...............................................................................3862

7 System Management...............................................................................................................3922
7.1 Common Client Settings...........................................................................................................................................3924
7.1.1 Logging In to or Exiting the Nastar Client............................................................................................................3924
7.1.2 Setting the Level of Logs Recorded by the Client.................................................................................................3927
7.1.3 Changing the Password of the Current User.........................................................................................................3928
7.1.4 Getting to Know the Client GUI............................................................................................................................3928
7.1.5 Customizing the Client GUI Effect.......................................................................................................................3945
7.1.6 Locking the Client.................................................................................................................................................3951
7.1.7 Unlocking the Client..............................................................................................................................................3952
7.1.8 Broadcast Messages...............................................................................................................................................3953
7.1.9 Setting the Alert upon Network Disconnections...................................................................................................3955
7.1.10 Managing the Nastar License..............................................................................................................................3955
7.1.11 Selecting More Secure Network Protocols..........................................................................................................3961
7.1.12 Querying the System Time..................................................................................................................................3961
7.1.13 GUI Reference.....................................................................................................................................................3961
7.1.14 FAQs about the Client Operations.......................................................................................................................3982
7.2 Security Management...............................................................................................................................................3991
7.2.1 Getting to Know the Concepts of Nastar Security................................................................................................3991
7.2.2 Managing User Rights...........................................................................................................................................3995

Issue 05 (2015-02-14) Huawei Proprietary and Confidential xvi

7.2.3 Security Policy Management.................................................................................................................................4044

7.2.4 Managing Passwords and Locking Clients............................................................................................................4054
7.2.5 Setting Nastar Data Transmission Security...........................................................................................................4059
7.2.6 Monitoring Nastar Users.......................................................................................................................................4063
7.2.7 GUIs and Parameters for Security Management...................................................................................................4065
7.2.8 Appendix...............................................................................................................................................................4124
7.2.9 FAQs About Authorization...................................................................................................................................4126
7.3 Digital Certificate Management...............................................................................................................................4128
7.3.1 Getting to Know Digital Certificates.....................................................................................................................4128
7.3.2 Configuring Digital Certificates............................................................................................................................4130
7.3.3 Updating Digital Certificates.................................................................................................................................4139
7.3.4 Obtaining the Certificate Revocation List.............................................................................................................4139
7.3.5 Reference of the Certificate Authentication Management GUI............................................................................4140
7.4 Log Management......................................................................................................................................................4150
7.4.1 Getting to Know Log Management.......................................................................................................................4150
7.4.2 Managing Nastar Operation Logs..........................................................................................................................4155
7.4.3 Managing Nastar System Logs..............................................................................................................................4160
7.4.4 Managing Nastar Security Logs............................................................................................................................4166
7.4.5 Setting Nastar Log Templates...............................................................................................................................4171
7.4.6 Setting Nastar Log Forwarding.............................................................................................................................4173
7.4.7 Managing Log Data...............................................................................................................................................4179
7.4.8 Reference of the Log Management GUI...............................................................................................................4183
7.5 Monitoring the Nastar Server...................................................................................................................................4215
7.5.1 Setting the Monitoring Parameters........................................................................................................................4215
7.5.2 Setting the Monitoring Parameters of the xSAU...................................................................................................4219
7.5.3 Monitoring the Status of the Nastar Server...........................................................................................................4220
7.5.4 Monitoring the Status of the xSAU.......................................................................................................................4225
7.5.5 Distributing xSAU System Monitoring Results....................................................................................................4228
7.5.6 Monitoring the System's Network Connections....................................................................................................4229
7.5.7 Interface Reference for System Monitoring..........................................................................................................4230
7.6 Integrated Task Management...................................................................................................................................4259
7.6.1 Getting to Know Integrated Task Management.....................................................................................................4259
7.6.2 Customizing the Interface for Managing Scheduled Tasks...................................................................................4264
7.6.3 Creating User Scheduled Tasks.............................................................................................................................4264
7.6.4 Managing Scheduled Tasks...................................................................................................................................4266
7.6.5 Viewing Scheduled Tasks.....................................................................................................................................4270
7.6.6 GUIs and Parameters for Integrated Task Management........................................................................................4271
7.7 Managing Adapter Packages....................................................................................................................................4284
7.7.1 Delivering an Adapter Package.............................................................................................................................4285
7.7.2 Rolling Back an Adapter Package.........................................................................................................................4286
7.7.3 Viewing Log Information About Adapter Packages.............................................................................................4287

Issue 05 (2015-02-14) Huawei Proprietary and Confidential xvii

7.8 Managing Analysis Data..........................................................................................................................................4288

7.8.1 Checking the Integrity of Analysis Data...............................................................................................................4288
7.8.2 Periodically Deleting Analysis Data......................................................................................................................4290

Issue 05 (2015-02-14) Huawei Proprietary and Confidential xviii

1 Nastar Overview

About This Chapter

Nastar provides a complete solution for wireless network performance analysis. It is applicable
to GSM/GPRS/EDGE, UMTS/HSUPA/HSDPA, LTE TDD/LTE FDD, and PS Core networks.
This solution can deeply analyze and locate wireless network problems and supports user
experience-based performance optimization and location-based network evaluation.

1.1 Position in Networking

The Nastar system consists of multiple physical entities such as the Nastar server, eSAU, SAU,
RAN SAU, LTE SAU, and PS SAU. Each physical entity is deployed in specific position of the
network.

1.2 Analysis Data Sources

This section introduces the data sources used by each analysis function of the Nastar.

1.3 Product Functions

This section lists the analysis functions provided by the Nastar for the GSM, UMTS, LTE, and
PS Core networks.

1.4 Technical Specifications

Nastar performance specifications vary based on the network scale, network model, and traffic
model of a user. This section describes technical specifications supported by the Nastar based
on default network and traffic models.

1.5 Basic Concept/Glossary

This section describes the basic concepts used in this document.

1.6 Guide to the Document

This section describes the intended audience, task type, and objective of each type of scenarios.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1

1.1 Position in Networking

The Nastar system consists of multiple physical entities such as the Nastar server, eSAU, SAU,
RAN SAU, LTE SAU, and PS SAU. Each physical entity is deployed in specific position of the
network.

Figure 1-1 shows the position of the Nastar system on the network.

Figure 1-1 Position of the Nastar system on the network

The communication between different units on the network is based on the TCP/IP protocol.
The Nastar server, eSAU, LTE SAU, and U2000/M2000 must be in the same local area network
(LAN), and their IP addresses must be on the same network segment.

Table 1-1 describes the function of each unit.

Table 1-1 Description of the functional units

System Functional Description

Unit

Radio GBSS Refers to the functional entity of the radio access network
access (RAN) in GSM. The GBSS consists of the BTS and BSC.
network It provides CS and PS data on the GSM RAN side for the
(RAN) Nastar system.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 2

System Functional Description

Unit

UTRAN Refers to the functional entity of the RAN in UMTS. The

UTRAN consists of the NodeB and RNC. It provides CS
and PS data on the UMTS RAN side for the Nastar system.

E-UTRAN Refers to the functional entity of the RAN in LTE. The E-

UTRAN consists of the eNodeB. It provides data on the E-
UTRAN side for the Nastar system to analyze.

Core Serving GPRS The SGSN is a functional unit at the CN. It provides PS
Network support node data on the CN side for the Nastar system.
(CN) (SGSN)

Gateway GPRS The GPRS is a functional unit at the CN. It provides PS data
support node on the CN side for the Nastar system.
(GGSN/SAE-
GW)

Mobility The MME provides data on the LTE RAN side for the
management Nastar system to analyze.
entity (MME)

Network U2000/M2000 A uniform management platform of Huawei mobile

manageme networks. It manages the mobile NEs manufactured by
nt system Huawei. It provides performance data, configuration data,
and alarm data for the Nastar system.

Trace Server The data collection server on the LTE network is used to
collect the LTE analysis data.
For details about Trace Server, see U2000/M2000 Trace
Server User Guide on U2000/M2000 Product
Documentation.

Nastar SAU The service aware unit (SAU) is an optional component of

system the Nastar system. It is installed in the controller of the
GSM, UMTS network as an SAUa, SAUc, or ESAUa
board. The SAU preprocesses the raw data from NEs of the
GSM, UMTS network and generates the data required by
Nastar to analyze.
NOTE
The meaning of data preprocessing is as follows: The Nastar filters
and parses raw data by predefined rules to obtain the preprocessed
data.

RAN SAU The RAN SAU is a service aware unit. When the SAU
board supports the data forwarding function, you can
deploy the RAN SAU software on the RH2288 server,
obtain raw data forwarded by the SAU board, pre-process
the data, and generate analysis data that meets the Nastar
requirements.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 3

System Functional Description

Unit

LTE SAU The SAU for LTE is an optional component of the Nastar
system. It is deployed at the OSS for LTE as an ATAE
server or HP PC server. The LTE SAU preprocesses the
raw data from the eNodeB and generates the data required
by Nastar to analyze.

PS SAU The PS SAU of the CN is an optional component of the

Nastar system. It is deployed in the CN equipment room as
an ATAE server or HP PC server. The PS SAU collects and
preprocesses the signaling plane data on the CN side and
generates the data required by the Nastar to analyze.

evolved service The eSAU is a mandatory component of the Nastar system

aware unit for data aggregation. It is deployed at the OSS as an ATAE
(eSAU) server or HP PC server. The eSAU aggregates data
preprocessed by the SAU or LTE SAU in multiple
dimensions and exports the aggregated MR/CHR data to
the Nastar server.

Nastar server The Nastar server is a mandatory component of the Nastar

system. It is deployed at the OSS as an ATAE server or HP
PC server. The Nastar server analyzes data and generates
analysis results for users to view on the Nastar client.

1.2 Analysis Data Sources

This section introduces the data sources used by each analysis function of the Nastar.

1.2.1 Data Sources for Nastar GSM Analysis

The Nastar uses three types of data for GSM analysis: GSM configuration data, GSM engineering
parameters, and data related to Nastar analysis.

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

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 4

Figure 1-2 Data sources for Nastar GSM analysis

Table 1-2 describes the data sources for Nastar analysis.

Table 1-2 Data sources for Nastar GSM analysis

Analysis Data Source Function

GSM configuration data The data contains basic information on network

optimization and helps the Nastar correctly
retrieve cell data from data sources.

GSM engineering parameters The parameters provide basic information on

network optimization, including longitudes and
latitudes of sites and azimuths and tilt angles of
antennas.
The parameters are used for the geographic
observation of analysis results. The parameters are
essential for the geographic observation function,
but optional for other functions.

Data related GSM performance data The data is obtained from the U2000/M2000 and
to Nastar used for GSM MR analysis, GSM frequency
analysis analysis, neighboring GSM cell analysis, and
GSM/UMTS neighboring cell analysis.
GSM/UMTS neighboring cell measurement data
is sourced from the GSM performance data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 5

Analysis Data Source Function

Neighboring GSM cell The data is obtained from the U2000/M2000 and
measurement data used for GSM frequency analysis and neighboring
cell analysis.

GSM uplink interference The data is obtained from the U2000/M2000 and
data used for GSM uplink interference analysis.

GSM MR GSM The data is obtained from an SAU and used for
data geographic GSM geographic observation.
observatio
n data

GSM The data is obtained from an SAU and used for

complaint GSM complaint analysis support, optional.
analysis
support
data

GSM GSM The data is obtained from an SAU and used for
CHR data geographic GSM geographic observation.
observatio
n data

GSM The data is obtained from an SAU and used for

terminal GSM terminal analysis.
analysis
data

GSM The data is obtained from an SAU and used for

complaint GSM complaint analysis support.
analysis
support
data

GSM VIP The data is obtained from an SAU and used for
analysis GSM VIP analysis.
data

GSM cell The data is obtained from an SAU and used for
performanc GSM cell performance analysis.
e analysis
data

1.2.2 Data Sources for Nastar UMTS Analysis

The Nastar uses three types of data during UMTS analysis: UMTS configuration data, UMTS
engineering parameters, and data related to Nastar analysis.

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

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 6

Figure 1-3 Data sources for Nastar UMTS analysis

Table 1-3 describes the data sources for Nastar analysis.

Table 1-3 Data sources for Nastar UMTS analysis

Analysis Data Source Function

UMTS configuration data The data contains basic information on network

optimization and helps the Nastar correctly
retrieve cell data from data sources.

UMTS Engineering Parameters The parameters provide basic information on

network optimization, including longitudes and
latitudes of sites and azimuths and tilt angles of
antennas.
The parameters are used for the geographic
observation of analysis results. The parameters
are essential for the geographic observation
function, but optional for other functions.

Data related MR data UMTS The data is obtained from an SAU and used for
to Nastar coverage UMTS coverage analysis.
analysis data

UMTS The data is obtained from an SAU and used for

pilot UMTS pilot pollution analysis.
pollution
analysis
data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 7

Analysis Data Source Function

UMTS The data is obtained from an SAU and used for

intra- UMTS intra-frequency neighboring cell analysis.
frequency
neighborin
g cell
analysis
data

UMTS The data is obtained from an SAU and used for

inter- UMTS inter-frequency neighboring cell analysis.
frequency
neighborin
g cell
analysis
data

UMTS/ The data is obtained from an SAU and used for

GSM UMTS/GSM neighboring cell analysis.
neighborin
g cell
measureme
nt data

UMTS The data is obtained from an SAU and used for

geographic UMTS geographic observation.
observatio
n data

UMTS The data is obtained from an SAU and used for

terminal UMTS terminal analysis.
analysis
data

Received UMTS The data is obtained from the U2000/M2000 and

total uplink used for UMTS uplink interference analysis.
wideband interferenc
power e analysis
(RTWP) data
data

CHR data UMTS The data is obtained from an SAU and used for
geographic UMTS geographic observation.
observatio
n data

UMTS The data is obtained from an SAU and used for

terminal UMTS terminal analysis.
analysis
data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 8

Analysis Data Source Function

UMTS The data is obtained from an SAU and used for

complaint UMTS complaint analysis support.
analysis
support
data

UMTS VIP The data is obtained from an SAU and used for
analysis UMTS VIP analysis.
data

UMTS cell The data is obtained from an SAU and used for
performan UMTS cell performance analysis.
ce analysis
data

1.2.3 Data Sources for Nastar LTE Analysis

Before performing analysis on an LTE network, the Nastar needs to obtain data about the LTE
network. Such data includes LTE configuration data, LTE engineering parameters, and data
related to Nastar analysis.
l Nastar-based LTE Data Sources
l 3GPP-based LTE Data Sources
l Mapping between Nastar- and 3GPP-based LTE data sources

Nastar-based LTE Data Sources

Figure 1-4 shows the sources for Nastar analysis data on an LTE network.

Figure 1-4 Sources for Nastar analysis data (LTE)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 9

Table 1-4 describes the sources for Nastar analysis data on an LTE network.

Table 1-4 Sources for Nastar analysis data (LTE)

Data Source Function

LTE configuration data The data contains basic information on network

optimization and helps the Nastar correctly
retrieve cell data from data sources.

LTE engineering parameters The parameters provide basic information on

Data related eNodeB LTE The data is used for LTE coverage analysis. It is
to Nastar CHR data: coverage uploaded to the LTE SAU through the Trace
analysis The data is analysis Server.
also data
referred to
as cell LTE The data is used for LTE network geographic
trace data. network observation. It is uploaded to the LTE SAU
geographic through the Trace Server.
observatio
n data

LTE The data is used for LTE terminal analysis. It is

terminal uploaded to the LTE SAU through the Trace
analysis Server.
data

LTE The data is used for LTE complaint analysis

complaint support. It is uploaded to the LTE SAU through
analysis the Trace Server.
support
data

LTE VIP The data is used for LTE VIP analysis. It is

analysis uploaded to the LTE SAU through the Trace
data Server.

LTE cell The data is used for LTE cell performance

performanc analysis. It is uploaded to the LTE SAU through
e analysis the Trace Server.
data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 10

Data Source Function

eNodeB LTE VIP The data is used for LTE VIP analysis. It contains
single- analysis all-signaling information for the analysis of
subscriber data important VIP subscribers and is uploaded to the
all- LTE SAU through the Trace Server.
signaling
data

MME LTE The data is used for LTE terminal analysis. It

CHR data terminal contains information such as IMSI and IMEI for
analysis LTE terminal analysis and is directly collected by
data the LTE SAU.

LTE The data is used for LTE complaint analysis

complaint support. It contains information such as IMSI and
analysis IMEI for LTE terminal analysis and is directly
support collected by the LTE SAU.
data

LTE VIP The data is used for LTE VIP analysis. It contains
analysis information such as IMSI and IMEI for LTE VIP
data analysis and is directly collected by the LTE SAU.

LTE cell The data is used for LTE cell performance

performanc analysis. It contains information such as IMSI and
e analysis IMEI for LTE cell performance analysis and is
data directly collected by the LTE SAU.

3GPP-based LTE Data Sources

According to 3GPP TR 32.423 "Telecommunication management; Subscriber and equipment
trace; Trace data definition and management", trace data is used for the routine maintenance and
optimization of LTE networks.

Application Scenarios

According to the 3GPP specifications, trace data can be used in the following scenarios:
l Multi-vendor UE validation
l Subscriber complaint
l Malfunctioning UE
l Checking radio coverage
l Testing a new feature
l Fine-tuning and optimization of algorithms/procedures
l Analyzing drop calls in E-UTRAN
l Periodical sampling of network performance

Trace Objects

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 11

According to the 3GPP specifications, trace objects are classified into single-subscriber trace
objects and device trace objects.
l Single-subscriber trace: NEs are notified of the information "IMSI+TR" of the mobile
subscribers to be traced, and then trace the call-related signaling information of these
subscribers.
l Device trace: NEs are notified of the information "Cell ID+TR" or "MME ID+TR" of the
devices to be traced, and then trace the call-related signaling information of all mobile
subscribers served by these devices.

Trace Content

According to the 3GPP specifications, trace content is managed by the following trace levels:
maximum, medium, and minimum.
l Maximum: All signaling information generated during each call process of a subscriber is
traced and the related raw code streams are recorded as ASN.1 codes.
l Medium: Only the key signaling information generated during each call process of a
subscriber is traced and the related key information elements (IEs) are recorded.
l Minimum: Signaling information generated during each call process of a subscriber is
sampled and the related key IEs are recorded.
NOTE
The minimum trace level records only a little signaling information, and therefore is not recommended.

Mapping between Nastar- and 3GPP-based LTE data sources

Nastar-based 3GPP-based LTE Data Sources Trace Capability
LTE Data
Sources

eNodeB CHR Cell trace data at the medium level N/A

data: The data Trace objects: devices
is also referred
to as cell trace Trace level: medium
data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 12

Nastar-based 3GPP-based LTE Data Sources Trace Capability

LTE Data
Sources

eNodeB single- Single-subscriber trace data at the l eRAN3.X (BTS3900

subscriber maximum level V100R005C00/
trace data Trace objects: single subscribers V100R005C01): ≤ 20 UEs/
eNodeBs
Trace level: maximum
l eRAN6.0 (BTS3900
V100R008C00): ≤ 40 UEs/
eNodeBs
l eRAN7.0 (BTS3900
V100R009C00): ≤ 40 UEs/
eNodeBs
l eRAN8.0 (BTS3900
V100R010C00): ≤ 40 UEs/
eNodeBs
NOTE
NEs in eRAN3.X support such data,
whereas the Nastar supports such data
only from NEs in eRAN6.0 or a later
version onwards.

MME CHR Regardless of the trace levels and N/A

data objects, identity information (such as
IMSI and IMEI) about subscribers or
terminals must be collected from the
CN side if the Nastar performs
analysis from the subscriber or
terminal dimension. That is, many
LTE RAN analysis themes provided
by the Nastar depend on the MME
CHR data collected from the CN
side.

NOTE

Cell trace and single-subscriber trace are not in any binding relationship, and therefore can be enabled
simultaneously. However, an eNodeB will start flow control when its CPU load exceeds 80%, which causes
data loss and consequently affects the analysis accuracy of the Nastar.

1.2.4 Data Sources for Nastar PS Core Analysis

Before performing analysis on a PS core network, the Nastar must obtain data for the analysis.

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

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 13

Figure 1-5 Data sources for Nastar PS core analysis

Table 1-5 describes the data sources for Nastar analysis.

Table 1-5 Data sources for Nastar PS core analysis

Analysis Data Source Function

SGSN/MME PS core The data is obtained from a PS SAU and used for PS core
CHR data terminal terminal analysis.
analysis data

PS core The data is obtained from a PS SAU and used for PS core
complaint complaint analysis support.
analysis
support

PS core VIP The data is obtained from a PS SAU and used for PS core
analysis data VIP analysis.

Data for root The data is obtained from a PS SAU and used for root cause
cause analysis analysis of PS core performance problems.
of PS core
performance
problems

GGSN/SAE- PS core The data is obtained from a PS SAU and used for PS core
GW CHR complaint complaint analysis support.
data analysis
support

PS core VIP The data is obtained from a PS SAU and used for PS core
analysis data VIP analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 14

Analysis Data Source Function

Data for root The data is obtained from a PS SAU and used for root cause
cause analysis analysis of PS core performance problems.
of PS core
performance
problems

1.3 Product Functions

This section lists the analysis functions provided by the Nastar for the GSM, UMTS, LTE, and
PS Core networks.

Scenario Function Description Networ

Basic Coverage The information about the radio links involved in a GSM/
network analysis, subscriber's call in the test cell is included in the MR. UMTS/
optimizati also called The information pertains to the coverage, quality, LTE
on MR analysis and distribution of subscribers of the carrier and cell. TDD/
on the GSM Coverage analysis can help network maintenance LTE
network engineers analyze and locate a large number of FDD
network problems, such as weak cell coverage, cross
coverage, poor service quality, imbalance between
uplink and downlink.

Neighborin This function is performed to analyze neighboring GSM/

g cell cells based on the MRs of the actual calls of all the UMTS
analysis 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 service quality problems caused by
redundant or missing neighboring cell configuration.
In addition to intra-RAT neighboring cell analysis,
such as neighboring GSM cell analysis, UMTS intra-
frequency neighboring cell analysis, and UMTS
inter-frequency neighboring cell analysis, the Nastar
supports the inter-RAT neighboring cell analysis,
such as the neighboring cell analysis between the
GSM network and the UMTS network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 15

Scenario Function Description Networ

Uplink This function is performed to analyze whether the GSM/

interference values of the main and diversity Received Signal UMTS
analysis Strength Indicators (RSSIs) of the transmit and
receive channels of a BTS are normal. Based on the
analysis and display in the time domain, it helps
Nastar operators analyze reverse interference signal
sources, and therefore initially locate the BTS that is
being interfered with and the cause of the
interference. On the GSM and UMTS networks, this
function can be performed to analyze and identify
interference in the frequency domain and help Nastar
operators select the frequencies experiencing light
interference.

Frequency This function is performed to evaluate the impact of GSM

analysis 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 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 service quality is improved. Based on the
interference traffic sequence of the available
ARFCNs in an expanded cell, this function can also
be used to find out the optimal frequencies to be
added to the expanded cell. This is a basis for
preparing a frequency plan for the network.

Pilot The network systems based on the code division UMTS

pollution multiple access (CDMA) technology are self-
analysis interfered systems, in which interference seriously
affects the performance and capacity of the systems.
In addition, 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, therefore
reducing DTs and improving the accuracy of
locating problems. Through the pilot pollution
analysis function, the Nastar analyzes the cells where
there is pilot pollution, the cells that cause
interference, and the interference strength. It then
displays the analysis results on a map.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 16

Scenario Function Description Networ

Network Network Through the geographic display and statistical GSM/

analysis geographic analysis of network coverage, network traffic, and UMTS/
observation network KPIs, the Nastar helps operators to detect LTE
network problems, therefore reducing drive test TDD/
costs. LTE
FDD

Cell Through the cell performance analysis, the Nastar GSM/

performanc obtains the data of abnormal calls in problematic UMTS/
e analysis cells, displays the data in comprehensive LTE
presentation modes, analyzes the causes of abnormal TDD/
calls, and therefore helps network OM personnel LTE
locate cell problems. FDD

Root cause The root cause analysis function enables the Nastar PS Core
analysis for to collect statistics about signaling procedures on the
performanc CN and to perform further analysis of possible causes
e problems for procedure exceptions. This helps network
optimization engineers locate network problems and
improve O&M efficiency.

User Complaint Whenever mobile subscribers encounter network- GSM/

assurance analysis related problems, they lodge a complaint with the UMTS/
support operators. After receiving the complaint, the LTE
operator can perform this function to obtain the user TDD/
call event records pertaining to the mobile user LTE
concerned. Then, the operator can analyze the cause FDD/PS
of the problem and then locate and solve the problem. Core
This helps to improve the efficiency of handling
complaints, therefore improving user satisfaction.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 17

Scenario Function Description Networ

VIP This function is performed to filter the call records GSM/

analysis of VIP subscribers from the user call event records UMTS/
of the entire network and obtain the KPIs of the voice LTE
and data services of VIP subscribers. The KPIs TDD/
include call drop rate, call setup duration, and LTE
forward and reverse data rate. By monitoring the FDD/PS
service quality of VIP subscribers daily, the Nastar Core
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, based on the user call event records of
the VIP subscribers, the Nastar can identify the
regions and cells where the call activities of VIP
subscribers are frequent. These cells are considered
VIP cells. Mobile operators can ensure the
performance of these cells to guarantee the service
quality of VIP subscribers.

Terminal Terminal Users can collect statistics of KPIs such as call drop GSM/
analysis analysis rate, access success rate, and handover success rate UMTS/
based on terminal models from the user call event LTE
record data of the entire network. The Nastar can TDD/
compare the performance data of the terminals and LTE
provide useful reference information for network FDD/PS
operation and troubleshooting. Core

1.4 Technical Specifications

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 18

Technical Specifications

NOTICE
l The service specifications of the Nastar depend on the network model and traffic model in
addition to the network scale. You need to calculate the service specifications again if the
onsite network model and traffic model are not the same as those supported by the Nastar by
default.
l This section describes the service specifications of the Nastar for a single analysis task. When
multiple analysis tasks are executed concurrently, the service specifications of the Nastar
will be decreased.
l If GSM/UMTS dual-mode base stations are deployed on the live network, the hardware
configuration must be calculated separately for GSM and UMTS.

For details about the performance specifications supported by each Nastar feature, see ***
Network Optimization > Feature Name > Basics of Feature Name > Technical
Specifications for Feature Name.

Appendix: Default Performance Calculation Models

Default Network Model

Parameter Default Value

GSM UMTS LTE

Average 4 - -
number of
TRXs in a
cell

Average 200 BSCs 1500 RNCs 3 eNodeBs

number of
cells under a
controller

Average 32 32 32
number of
neighboring
cells of a
cell

Average cell 500 meters 500 meters 500 meters

coverage
radius

Number of 100,000 100,000 100,000

network-
level IMEI-
TAC entries

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 19

Parameter Default Value

GSM UMTS LTE

Average 100 100 100

number of
IMEI-TAC
entries of a
cell per day

Total 2,500,000 8,000,000 2,000,000

number of
network-
level
subscribers

Default Traffic Model

Parameter Default Value

GSM UMTS LTE

Average 6 10 10
number of
BHCA per
subscriber

Average 20mErl 20mErl -

traffic per
subscriber
in busy
hours

Busy-hour 0.4 0.4 0.6

percentage
coefficient

Percentage 0.5 0.5 0.5

of active
subscribers
in busy
hours

Average 2 2 -
number of
CS services
per
subscriber
in busy
hours

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 20

Parameter Default Value

GSM UMTS LTE

Average 4 8 10
number of
PS services
per
subscriber
in busy
hours

Average 3 6 6
number of
active cells
per
subscriber
in busy
hours

Average 9 18 18
number of
active cells
per
subscriber
per day

Percentage 0.3 0.3 0.1

of abnormal
calls

1.5 Basic Concept/Glossary

This section describes the basic concepts used in this document.

Nastar System
The Nastar system consists of multiple physical entities such as the Nastar server, eSAU, SAU,
RAN SAU, LTE SAU, and PS SAU.

Basic Data
Basic data includes configuration data, engineering parameters, map files, and other data such
as NE group information, terminal information, VIP information, complaining subscriber
information, feature matrix, and mailbox information.

Analysis Data
Analysis data includes the MR data, CHR data, and GSM performance data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 21

MR Data
MR data file: It is generated in the unit of measurement objects based on the measurement that
is triggered periodically or by specific events. It records network environment features such as
serving cell RSCP, serving cell Ec/No, DL BLER, neighboring cell RSCP and neighboring cell
Ec/No for a certain place at a certain time during a call.

The MR data is recorded in the unit of measurement objects for a certain place at a certain time.
Therefore, a large amount of collected MR data can effectively show the network traffic
distribution, signal coverage, and other network indicators. In this way, the Nastar can perform
network performance analysis from the network perspective.

MR data is generated by base station controllers, and is saved on OMU boards in binary format.
SAU boards then download the MR data from the OMU boards and save the data.

CHR Data
CHR data file: It records key information such as access and release time, access and release
cell, and access and release cause in the unit of calls.

The CHR data is recorded in the unit of calls. Therefore, the CHR data effectively shows the
subscriber behavior on the network and enable the Nastar to perform network performance
analysis from the subscriber perspective.

CHR data is generated by base station controllers, and is saved on OMU boards in binary format.
SAU boards then download the CHR data from the OMU boards and save the data. UMTS event-
based CHRs are saved directly on SAU boards after they are generated. The Nastar cannot obtain
UMTS event-based CHRs if SAU boards are not installed.

Basic subscription
Basic data subscription is used to turn on the NE data switches on the live network so that NEs
can generate raw data and to enable the data preprocessing functions of the SAU and eSAU so
that the raw data generated by NEs can be preprocessed to the analysis data that meets the Nastar
requirements.

Application subscription
Application data subscription is used to deliver specific rule files to NEs so that NEs can generate
raw data that meets requirements.

OSS
OSS refers to the Operating Support System. On the GSM, UMTS, LTE or PS Core network,
the U2000/M2000 is used.

IMSI
IMSI refers to the international mobile subscriber identity. An IMSI is a 15-digit string consisting
of digits 0 to 9. The structure of the IMSI from left to right is MCC+MNC+MSIN. MNC and
MSIN form the NMSI.

l MCC refers to the mobile country code of a mobile subscriber.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 22

l MNC refers to the mobile network code, that is, the PLMN code of a mobile subscriber.
PLMN refers to the public land mobile network.
l MSIN refers to the mobile subscriber identification number.
l NMSI refers to the national mobile subscriber identification and uniquely identifies an MS
in a country.

Huawei provides a dedicated solution to secure IMSI information. When the anonymous policy
is enabled on the network where the Nastar is deployed, first encrypt IMSIs using the anonymous
policy tool. The Nastar analyzes services based on the encrypted IMSIs.

IMEI-TAC
International Mobile Equipment Identity (IMEI) uniquely identifies an MS.

An IMEI consists of 15 digits ranging from 0 to 9 and is composed of the following four parts:
l Type approval code (TAC): consists of six digits and is used to identify an MS type.
l Final assembly code (FAC): consists of two digits and is used to identify a vendor.
l Serial Number (SNR): consists of six digits and is used to uniquely identify an MS when
the TAC and FAC of two MSs are the same.
l SSP: a spare bit, which consists of only one digit and is reserved for use.

In an IMEI, the first eight digits that are composed of TAC and FAC uniquely identify an MS
type, and the later digits from 9 to 15 uniquely identify an MS of a certain type.

The Nastar analyzes only MSs of a certain type identified by the first eight digits that are
composed of TAC and FAC. In the Nastar window, IMEI-TAC refers to these eight digits.

Peer Number
Peer number refers to the phone number of the peer end during a call, such as the fixed-line
phone number or mobile number. For example, if the calling party is being analyzed, the peer
end number is the phone number of the called party.

Huawei provides a dedicated solution to secure MSISDN information. When the anonymous
policy is enabled on the network where the Nastar is deployed, first encrypt MSISDNs using
the anonymous policy tool. The Nastar analyzes services based on the encrypted MSISDNs.

Layers
Layers are classified into site layers, service layers and map layers.
l Map layers are generated when the map files are imported, such as street map layer and
river map layer.
l Site layers are generated when the engineering parameter files are imported, such as base
station layer.
l Service layers refer to the layers with counters or grids in the network geographical
observation function.

Equivalent NE
Equivalent NE is a term introduced to calculate the network scale for the Nastar.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 23

BHCA
BHCA refers to busy hour call attempts, that is, the number of calls within one busiest hour.

The formula for calculating BHCA is as follows: BHCA = A x W1 + B x W2 + C x W3.

This counter can reflect influences on the performance of the Nastar and SAU of a user's network
in different traffic models. This helps to check whether the Nastar and SAU can process data
for a specific network scale and traffic model. Traffic model changes cause BHCA changes.
Users need to expand the capacity if the processing capability of the Nastar fails to meet BHCA
requirements.

1.6 Guide to the Document

This section describes the intended audience, task type, and objective of each type of scenarios.

l This document provides instructions for the task types in yellow background. Click a
specific region and it is linked to the desired section.
l In the scenario "User of services", beginners are advised to perform operations by following
the links while professional engineers can perform operations by referring to specific
sections under "XXX Network Optimization" of the document.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 24

2 Nastar Quick Start

About This Chapter

This chapter describes the basic ideas and operations for network optimization and describes the
Nastar operation processes by using examples. Only basic Nastar operations are described in
this section. It is especially useful to new users. It is recommended that you read this section
when using the Nastar the first time. If you are familiar with Nastar basic operations, refer to
chapters named in *** Network Optimization format to perform theme analysis.

2.1 Nastar Operation Process

This section describes the operation process for network optimization by using Nastar and each
involved procedure.

2.2 Login In to the Nastar

This section describes how to log in to the Nastar client, and how to log out the current user add
exit the Nastar client.

2.3 Configuring OSS and NE Information

This section describes how to configure OSS and NE information on the Nastar client. The Nastar
collects radio access network (RAN) and core network (CN) data from entities such as the
U2000/M2000, eSAU, LTE SAU, SAU, and PS SAU. Therefore, you need to configure OSS
and NE information so that these entities can identify and communicate with each other. In this
manner, data can be obtained successfully. The information to be configured includes IP address,
user name, password, and FTP information.

2.4 Configuring the Anonymous Policy

2.5 Preparing Basic Data

This section describes how to collect basic data including configuration data, engineering
parameters, and map information before analyzing data.

2.6 Subscribing to Analysis Data

This section describes how to enable data source switches by using the data source subscription
function before performing various theme analysis functions. After required data source switches
are enabled, the Nastar can collect required data from network elements (NEs). This function is
the prerequisite for all Nastar theme analysis functions.

2.7 Checking the Integrity of Analysis Data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 25

This section describes how to check the integrity of analysis data. You need to check the integrity
of analysis data to ensure that the Nastar can analyze the data normally.

2.8 Creating an Analysis Task

This section describes how to create an analysis task. After the analysis task is created, the Nastar
retrieves the performance data of the selected NE from the database, analyzes it, and generates
an analysis report.

2.9 Querying Analysis Results

The section describes how to query the analysis results. After the analysis task is finished, you
can locate and solve the network problems through viewing the results.

2.10 Viewing Geographic Analysis Results (Optional)

This section describes how to view geographic analysis results. If analysis tasks support
geographic display, you can directly analyze counter analysis results by viewing the geographic
analysis results after an analysis task is executed successfully.

2.11 Exporting Analysis Reports

This section describes how to export the analysis reports as files.

2.12 FAQs
This section describes the problems and solutions to the FAQs when using the Nastar, and also
provides methods for common operations.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 26

2.1 Nastar Operation Process

This section describes the operation process for network optimization by using Nastar and each
involved procedure.

The operations performed on the Nastar are divided into the following three phases:
1. Preparation phase: In this phase, users must input the OSS, eSAU, SAU, LTE SAU, PS
SAU and NE information so that the Nastar system can communicate with these entities
normally, and users must have successfully collected the basic data, such as configuration
data and engineering parameters. It is recommended by the administrator of Nastar client.
2. Data acquisition phase: In this phase, users have subscribed to data for analysis. The purpose
is to ensure that the Nastar system can successfully collect the data required for analysis.
After data subscription is completed, users need to check whether the data for analysis is
available. It is recommended by the administrator of Nastar client.
3. Analysis phase: In this phase, users create an analysis task based on the obtained data for
analysis and basic data and view the analysis result on the client. It is recommended by the
network optimization engineers.

Figure 2-1 shows the flowchart. For details, see Table 2-1.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 27

Figure 2-1 Nastar operation process

Table 2-1 Operation procedures for network optimization by using Nastar

No. Procedure Description

(1) Start 2.2 Login In This section describes how to log in to the Nastar client,
to the Nastar and how to log out the current user add exit the Nastar
client.

(2) Prepar Configuring Users must configure OSS and NE information before the
ation OSS and NE Nastar can collect data. The OSS, eSAU, SAU, LTE SAU,
phase Information PS SAU, and NE in the Nastar system can successfully
identify and communicate with each other only after users
have configured their information on the Nastar client. In
this manner, data can be obtained successfully.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 28

No. Procedure Description

(3) Preparing Before obtaining the data for analysis, users must collect
Basic Data some basic data for analysis such as the configuration data,
engineering parameters, and map information.

(4) Data Subscribing Before starting a theme analysis, users must turn on the
acquisi to Analysis data switch of a required NE by using the data subscription
tion Data function. Once the data switch of the NE is turned on, the
phase Nastar can successfully collect the required data from the
NE for analysis.

(5) Check the Check that the Nastar has imported the data for analysis
Integrity of into the database. The purpose is to ensure that an analysis
Analysis task can be processed normally.
Data

(6) Analys Creating an After an analysis task is created, the Nastar retrieves the
is Analysis performance data of the desired NE from the database for
phase Task analysis.

(7) View the After the analysis is complete, users can view the analysis
Analysis result. The analysis result can be used as a basis for
Result network optimization.

(8) Exporting You can export the analysis results into Excel files.
Analysis
Reports

2.2 Login In to the Nastar

This section describes how to log in to the Nastar client, and how to log out the current user add
exit the Nastar client.

2.2.1 Logging In to the Nastar Client

The Nastar adopts the client\server mode. You can perform operations on the client only after
you successfully connect to the server through the client.

Prerequisites
l Before login, ensure that the Nastar client and server are connected normally, and the server
works properly.
l The screen resolution of the PC must be 1440*900 or higher to ensure that information can
be properly displayed on the Nastar client.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 29

Context
l The default port number of the server is 31037. Do not change it in normal conditions.
Otherwise, you cannot log in to the Nastar client.
l The Nastar server provides the default user account admin. The admin user has all operation
rights, and the password is Changeme_123 by default. When you attempt to log in to the
Nastar client as the admin user for the first time, the login is successful only after you
change the password.
l You can log in to the server in Secure Sockets Layer (SSL) mode or common mode. In
SSL mode, the data is encrypted when being transmitted between the client and the server.
In common mode, the data is not encrypted during transmission.
l By default, if you do not log in to the Nastar client for more than 60 days, your account
automatically turns to the suspend state except that you are an admin user.
l If you never use your new account to log in to the Nastar client, the Nastar does not disable
or delete the new account.
l The user with the rights of the security administrator group can click the hibernated account
in the security navigation tree on the Nastar client, and then set Suspend account to No
on the Details tab to enable this account.
l It is not recommended to run the clients of two different versions on the same PC.

Procedure
Step 1 Start the Nastar client.

Step 2 In the Login dialog box, perform the following operations to select a server where you want to
log in:

l If the server list does not exist:

1. Click on the right of Server drop-down list.

2. In the Server List dialog box, click Add.
3. In the Add Server Information dialog box, set the Name, Server Name (or IP
Address), Port and Mode.
NOTE

If the Nastar client accesses the Nastar server by using the IP address of the firewall where the
network address translation (NAT) is performed, type the IP address converted by the NAT.
4. Click OK to go back to the Server List dialog box.
In the Server List dialog box, the server that you set is selected by default.
5. In the Server List dialog box, click OK.
l If servers are listed in the Server drop-down list:
Select a server from the Server drop-down list.

Step 3 In the Login dialog box, enter the user name and password.

Step 4 Click Login.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 30

NOTE

l If the user name and the password are correct, the Loading dialog box is displayed, indicating the
loading progress.
l If the user name or password is incorrect, the Information dialog box prompts a login failure.
l If the password is to expire, the system prompts you to change the password before the expiration date.
l If the license is to expire, the system notifies you of the expiration date.
l If you use a temporary license, you are prompted to apply for an official license.

----End

Follow-up Procedure
l Exiting the Nastar client
1. Choose File > Exit.
2. In the Confirm dialog box, click OK.
l Logging out the user account
1. Choose File > Log Out.
2. In the Confirm dialog box,click OK.
NOTE

After logout, the Login dialog box is displayed. You can enter the proper information in the
dialog box to log in to the Nastar client again.

2.2.2 Interface Description: Nastar Client

This section describes the contents and functions of the Nastar client. The Nastar GUI is
displayed after logging in to the Nastar client. You can refer to the description for better
operations on the Nastar client.

The Figure 2-2 shows the client GUI.

For details of the areas in the interface, see 7.1.4 Getting to Know the Client GUI.

Figure 2-2 Client GUI

1: Menu bar 2: Toolbar 3: Navigation tree 4: Output pane

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 31

5: Window bar 6: Task list pane 7: Task result pane 8: Status bar

2.2.3 Interface Description: Geographic Observation Results

This section describes the Geographic Observation window and the function of each area in
the window. Using engineering parameters and map files, the Geographic Observation window
can display the results of various analysis tasks.

Navigation Path
l In the Nastar main window, click . The Geographic Observation window is displayed.
In this window, you can check the geographic distribution of sites on the network, or check
analysis results of added themes.

l In the theme analysis result window, click . The Geographic Observation window is
displayed. In this window, you can add counters related to a theme to the layer navigation
tree for analysis.

NOTE

l Before you perform a geographic observation analysis, check that engineering parameters have been
imported into the Nastar. For detailed operations, see Importing Engineering Parameters.
l When you close the window, the Nastar hides the window and does not delete the analysis results.

When you click again, the analysis results are displayed again.
l If the Geographic Observation window of a theme (excluding network geographic observation
themes) is open, the Nastar deletes related counters from the layer navigation tree when you close the
theme analysis result window.
l There is no analysis result window for network geographic observation themes. The results of such
themes are displayed in the Geographic Observation window.

Window
Figure 2-3 shows the Geographic Observation window.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 32

Figure 2-3 Geographic Observation window

N Item Description
o
.

1 Toolbar Provides icons for you to perform operations. For detailed operations, see
Buttons on the toolbar.

2 Layer Site Before performing a geographic observation analysis, you have

navigati Layer
to click to load site layers. Currently, the Nastar allows you
on tree node
to load site layers based on outdoor and indoor sites. After site
layers are loaded, you can select a site for analysis under the Site
Layer node in the navigation tree. Then, area 3 geographically
displays the site information.
NOTE
l You can adjust the site legend by performing the following operations:
Right-click a radio access technology (RAT) under Site Layer and
choose Sector Display Settings or Site Display Settings from the
shortcut menu. In the displayed dialog box, you can change the type,
size, shape, and color of the legend.
l If you need to delete all sites in a network system, click Remove
through the layer management function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 33

N Item Description
o
.

Polygon By drawing a polygon, you can further analyze only desired areas.
Areas All created polygons are displayed under the Polygon Areas
node node.
You can perform the following operations to manage polygons:

l Drawing a polygon: You can click to draw a polygon.

After you draw a polygon, the name of the polygon is displayed
under the Polygon Areas node. You are allowed to draw a
maximum of 30 polygons. For details about how to draw a
polygon, see drawing a polygon.
l Deleting a polygon: You can right-click a polygon and choose
Delete from the shortcut menu to delete the polygon.
l Checking the area of a polygon: You can right-click a polygon
and check its area in the displayed shortcut menu.
l Showing a polygon in the center: You can right-click a polygon
and choose Center Display from the shortcut menu. Then, the
polygon is displayed in the center. With this function, the
Nastar can quickly display a selected polygon in the
Geographic Observation window.

l Saving cells as an NE group: You can click to save the

cells in a polygon as an NE group. These cells can be used
directly during theme analysis and are highlighted in the
Geographic Observation window.
Further polygon analysis includes the following functions:
l Statistical analysis: enables you to analyze multiple counters
simultaneously based on a polygon and displays the analysis
results in a list.
To enable this function, perform the following operations:
1. Right-click a polygon and choose Statistical Analysis
from the shortcut menu.
2. In the displayed dialog box, select an analysis task,
dimension, and counters, and click OK.
3. In the displayed Statistical Analysis Result dialog box,
view the counter analysis results of the polygon.
NOTE
Currently, the themes that support the statistical analysis function are
network geographic observation, and terminal geographic
observation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 34

N Item Description
o
.

Theme Displays counter sets for analysis. If you select multiple counters,
the Nastar displays the analysis results of the last selected counter.
Nodes of different levels are described as follows:
l level-1 nodes: analysis features, such as GSM network
geographic observation, and GSM terminal analysis.
l Level-2 nodes: names of analysis tasks, which are specified by
users when they create tasks.
l Level-3 nodes: analysis dimensions, such as network
geographic observation, all services, traffic analysis, and
capability analysis.
l Level-4 nodes: counters for analysis, which are automatically
loaded and generated by the Nastar.
You can right-click a counter and perform operations as required:
l Choose Display Settings to adjust the legend for displaying
grids or cells in different colors, set frequencies, site types, or
NEs to query, or set other geographic observation parameters
such as confidence level.
l Choose Center Display for the CME to quickly display the
area covered by the selected counter in the Geographic
Observation window.
NOTE
l If a counter in the left pane is gray, no counter data is available.
l Shortcut menus and parameters supported by counters vary according
to themes. You can log in to the Nastar client to view details.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 35

N Item Description
o
.

3 Chart The display effects of themes are different:

area l After you select counters for network geographic observation, this area
displays information about grids, sites, and sectors in different colors.

shows grids.
l After you select counters for other themes, this area displays only site and
sector information. Sectors are colored based on the levels of the current

counter values, as shown in . For coloring description, see the

legend.
You can perform the following operations on the chart area of grids:
l Showing the lines between grids and related cells: After you select a grid,
the Nastar displays the top 5 cells related to the grid using grid-site
connection lines at the layers, and the analysis results in areas 4 and 5 are
correlated.
NOTE
The lines connecting the top cells in grids are not affected by the function of filtering
site layers by frequency or frequency band. If the filtering function is enabled, the
Nastar displays only the filtered sites. However, no matter whether the filtering
function is enabled or disabled, the Nastar displays all the top cells in grids and the
lines connecting these top cells.
l Showing grids related to cell coverage: Right-click a cell and choose Cell
Coverage Grids > KPI from the shortcut menu. The Nastar displays all
the grids covered by the cell using black outlines based on KPIs.

4 Grid Displays contribution values of the top 5 cells related to a selected grid under
details a counter. In addition:
area l If you have selected multiple counters for analysis, these counters are
displayed on different tab pages. If you switch to another tab page, the grid-
cell connection lines displayed in the chart area are updated according to
the current counter.

l You can click on the table header to sort the table and click to filter
the table content.
l You can right-click in the table and choose Save As from the shortcut menu
to save the grid details to a local PC.
l After you select a record in the table, the grid-site connection line between
the cell and grid is highlighted.
l You can right-click a record in the table and choose Distance and Angle
from the shortcut menu to measure the distance from the grid to the cell
and the angle between the grid-cell connection line and the cell azimuth.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 36

N Item Description
o
.

5 Legend This area is not displayed by default. If you want to view the legend details
details about an analysis theme, click in the button area.
area
The Nastar provides three methods for you to set legends:

l Click in area 1. In the displayed Layer Management dialog box, click

Display to set the counter legend.
l Right-click a counter in area 2 and choose Display from the shortcut menu.
In the displayed dialog box, set the counter legend.
l Right-click in area 3 and choose Layer Management from the shortcut
menu. In the displayed Layer Management dialog box, click Display to
set the counter legend.
NOTE
l If no counter needs to be analyzed in a geographic observation theme, such as GSM
neighboring cell analysis, the counter legend cannot be set.
l You can back up and restore the configured counter legends by using the file sharing
function. The counter legend information is saved in \NastarClient\client\plugins
\com.huawei.galaxy.geography.ui\style\config\style.

6 Informa This area does not display any information when it is opened for the first time.
tion You can select desired objects to view related information:
area l Grid: displays the value of the selected counter in this grid.
l Site: displays information related to the site.
l Cell: displays details about the cell, including engineers parameters,
longitude, and latitude.

Buttons on the toolbar

Button Functio Operation
n
Descrip
tion

Imports For detailed operations, see Importing Map Files.

a map
file.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 37

Button Functio Operation

n
Descrip
tion

Loads Site information is displayed in the Geographic Observation

site window. Before you load site information, ensure that engineering
informat parameters have been imported into the Nastar. For detailed
ion. operations, see Importing Engineering Parameters.

1. Click on the toolbar. The Choose Geographic Sites dialog

box is displayed.
2. Choose a RAT from the drop-down list box.
3. Select the site whose information you want to load from the area
at the bottom.
4. Click OK.
After the site information has been loaded, the Geographic
Observation window displays the site icon.

Manages
Click on the toolbar. In the displayed Layer Management
layers.
dialog box, set the layer information.
NOTE
Layers are classified into site layers, service layers and map layers. You can
set attributes at site layers and service layers, such as legends. Attributes
cannot be set at map layers. You can remove all layers or move them upwards
or downwards.
l If multiple layers are available, you can select a layer and click
Up (U) or Down (D) on the right of the layer list to adjust the
overlap sequence of layers. You can also determine whether to
show or hide a layer and set the transparency of the layer to be
displayed in the Properties area below the map layer list.
l You can click Add on the right of the map layer list to add a
layer file.
Layer files are in .tab format.
l After selecting a layer, you can click Properties on the lower
right of the layer list to set the legends and cell objects to be
displayed at the layers.

Shows or Click on the toolbar to open the legend and view the counter
hides a value range mapped to each color.
legend.
You can also reset the legend in the Layer Management dialog
box.

Moves a
Click on the toolbar, move the pointer to the map and drag the
map.
map to the required direction.

Selects
Click on the toolbar and click an object on the map to select it.
objects.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 38

Button Functio Operation

n
Descrip
tion

Measure
1. Click on the toolbar.
s the
distance. 2. Click a point on the map and use it as the start point for
measuring the distance.
Then, the start point is fixed. Hold down the mouse, and then
move it. When the pointer moves away from the start point, the
Nastar displays a solid black connection line between the start
point and the pointer. On the status bar in the right pane of the
network geographic observation window, the distance between
two points is displayed in the Distance(km) area in real time.
3. Double-click or right-click the map to complete the distance
measurement.

Zooms
or Click on the toolbar to zoom in the map or click to zoom
in or out
out the map.
a map.
NOTE
You can scroll the mouse wheel forward or backward to zoom in or out the
map.

Views
the Click on the toolbar. The Nastar displays all the objects in the
panoram Geographic Observation window.
ic scene
of a map.

Refreshe
You can click on the menu bar to re-execute operations that are
s a map.
not responded to and to refresh maps.

Saves a
1. Click on the toolbar. The Save dialog box is displayed.
map.
2. Set the file name and type.
You can export the display effect of overlapped layers in the
map window as an image in .png, .gif, .jpg or .tab Reformat.
3. Click Save.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 39

Button Functio Operation

n
Descrip
tion

Draws a You can draw a polygon for hot spots to filter multiple cells or grids.
polygon.
1. Click on the toolbar.
2. Add points to the polygon one by one in the Geographic
Observation window.
NOTE
l The maximum number of grids within a polygon area is 1000. If the
number of grids exceeds the threshold, draw the polygon area again.
l The lines of a polygon must not intersect. Otherwise, certain selected
areas may be missed out.
l Draw a polygon area with an appropriate size as required. If you
select a large area with many grids, a long wait time is required.
3. After the last point is added, double-click or right-click in the
window to exit the polygon drawing. In addition, the Label
dialog box is displayed.
4. Set the name of the polygon.
5. Click OK. The polygon drawing is complete.
The Geographic Observation window displays the polygon
and its name. In addition, the polygon name is added to the
Polygon Areas node in the navigation tree in the left pane.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 40

Button Functio Operation

n
Descrip
tion

Filters You can optimize only cells by filtering cells based on specified
cells. RATs, engineering parameters, and optimization areas.

1. Click to draw the area where you want to filter cells.

For detailed operations, see the content in the last row.
2. Set filter criteria.

a. Click on the toolbar. The Search dialog box is displayed.

b. Select a RAT in Network Technology.
c. Select the area you want to filter in Region.
d. Set engineering parameters in the lower left corner of the
dialog box.
The Nastar supports filtering of all engineering parameters.
Generally, you can set one or two parameters as the filter
criteria. The logical operator between the two parameters can
be set to And or Or.
3. Click Search. The Nastar starts to filter cells.
The filtering results are displayed in the Search Result area.
4. Select or clear Search Result to determine whether to filter cells
again.
5. The Nastar geographically displays filtered cells.
Click Geographic(D). The cells selected in the Search Result
area are highlighted in the Geographic Observation window.
6. Save the filtered cells as an NE group.
a. Click Save As NE Group. The Save As NE group dialog
box is displayed.
b. Set NE Group Name and add remarks.
c. Click OK.
Cells selected in the Search Result area are saved as an NE
group. You can double-click System Function > NE Group
Management in the Analysis Task Management window
and then view information about the NE group in the
displayed window.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 41

Button Functio Operation

n
Descrip
tion

Searches
1. Click on the toolbar or use the shortcut key Ctrl+F. The
for cells.
Find dialog box is displayed.
2. Type keywords in Cell Name.
3. Select a RAT in Select the network.
4. Click Find Next. Then, the Nastar searches for cells whose
names contain the keywords.
l Keywords are case insensitive.
l The Nastar highlights searched cells in the center of the
window.

Displays Select two to four counters in the layer navigation tree and click
multiple
on the toolbar. The Nastar displays the layers mapped to the
windows
selected counters in multiple panes concurrently. These panes are
.
zoomed in, zoomed out, and moved together. When you click
again, the large window is displayed.
NOTE
l The Nastar displays the analysis results of only two to four counters in
concurrent panes.

Exports
1. Click on the toolbar. The Export Data dialog box is
grid data.
displayed.
2. In Path, set the file name and save path. In Type, set the file
type.
3. In Subject, select the theme whose grid data you want to save.
4. On the Item tab page, select counters whose data you want to
export.
5. On the Range tab page, select the data range for export.
l By NE: The Nastar allows you to export data by BSC, RNC,
or cell group.
l By Polygon: The Nastar allows you to export grids in the
polygon selected in the Geographic Observation window.
6. Click Export.
You can view the export progress in the displayed Exported
File List dialog box. After the export is complete, you can click
on the right of the progress bar to view file information.
NOTE
The maximum number of grids within a polygon area is 1000. If the number
of grids exceeds the threshold, draw the polygon area again.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 42

Button Functio Operation

n
Descrip
tion

Exports
1. Click on the toolbar. The Export Data dialog box is
Google
displayed.
Earth
data. 2. In Path, set the file name and save path. In Type, set the file
type.
3. In Subject, select the theme whose data you want to save.
4. On the Item tab page, select the analysis counters you want to
export.
5. On the Scenario tab page, select the analysis scenario files to
be imported.
l If Export Engineering Parameter is selected, Google Earth
data that contains engineering parameters will be exported.
l If Import Scenario is selected, scenario files to be imported
will be converted into Google Earth data.
Scenario files are mainly used to quickly pinpoint desired
geographic locations on Google Earth maps. The Nastar
allows you to import only CSV scenario files. In a scenario
file, the first column contains address names, the second
column is empty or contains any values, the third column
contains address types, the fourth column contains latitudes,
and the fifth column contains longitudes. In addition, column
header information cannot be included.
6. Click Export.
You can view the export progress in the displayed Exported
File List dialog box.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 43

Button Functio Operation

n
Descrip
tion

Imports The Nastar allows users to import vector points of specified

points. longitudes and latitudes, and can display the vector points in the
GIS. For example, if users want to quickly and clearly locate certain
key locations in an area, they can import the longitudes and latitudes
of these locations into the GIS so that the Nastar can display these
locations on maps in specified shapes and colors.
1. Click on the toolbar. The Open dialog box is displayed.
2. Select the vector point data file that you want to import.
l Vector point data files must be in CSV, XLS, or XLSX
format.
l Vector point data files must contain a longitude column and
a latitude column to indicate longitudes and latitudes.
NOTE
Column names in vector point data files are not case sensitive.
3. Click Open.
4. The Nastar loads the data and displays it in the GIS in the form
of vector point. In addition, a node named based on the file name
is added under the Point Layer node in the navigation tree.
5. Right-click the node and choose Display Settings, Center
Display, or Delete from the shortcut menu to perform operations
as required.

2.3 Configuring OSS and NE Information

2.3.1 Configuration Procedures

The OSS information management function enables the Nastar to collect information from
objects such as the U2000/M2000, eSAU, and NEs.

To ensure that the Nastar can properly communicate with each object, configure the OSS and
NEs shown in Figure 2-4 on the Nastar client.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 44

Figure 2-4 Configuration procedures

Table 2-2 Configuration procedures

Configur No. Step Description

ation
Scenario

Preparatio 1 2.3.2 Preparations This section describes how to obtain the required
ns for OSS for OSS and NE information about OSS and NEs. Read this
and NE Information section before configuring information about
Informatio Configuration OSS and NEs.
n
Configurat
ion

Configuri a.1 Configuring In this step, configure the IP address, port

ng eSAU information number, and FTP information of the server
informatio running the eSAU software.
n about

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 45

Configur No. Step Description

ation
Scenario

NEs on the a.2 Configuring OSS In this step, configure the IP address, software
radio information version, networking mode, and FTP information
access of the OSS server.
network
(RAN) a.3 Selecting RAN In this step, select the RAN NEs managed by an
side NEs managed by OSS, such as BSC, RNC, and eNodeB.
an OSS

a.4 Setting SAU or In this step, configure the SAU or LTE SAU
LTE SAU information before you use the analysis function
information. of the SAU or LTE SAU board.

Configuri b.1 Configuring In this step, configure the IP address, port

ng eSAU information number, and FTP information of the server
informatio running the eSAU software.
n about
NEs on the b.2 Configuring OSS In this step, configure the IP address, software
core information version, networking mode, and FTP information
network of the OSS server.
(CN) side b.3 Selecting CN NEs In this step, select the CN NEs managed by an
managed by an OSS, such as serving GPRS support node
OSS (SGSN).

b.4 Setting PS SAU In this step, configure the PS SAU information

information. before you use the analysis function of the CN
network.

2.3.2 Preparations for OSS and NE Information Configuration

This section describes how to obtain the required information about OSS and NEs. Read this
section before configuring information about OSS and NEs.

Before configuring information about OSS and NEs, obtain information listed in Table 2-3.

Table 2-3 Pre-configuration checklist

Scenario Required Information

Configuring eSAU Information about the server running the eSAU software, including:
information l IP address of the server
l User name, password, and port number for the FTP service of the
server

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 46

Scenario Required Information

Configuring OSS Information about the OSS system within the analysis area,
information including:
l Version number and networking scheme
l User name, password, and port number for the FTP service of the
OSS system. If the OSS system contains slave servers, obtain the
preceding information about the slave servers.
l Number of the port for communicating with the OSS system.
Retain the default setting when you configure information about
NEs.
l User name and password for logging in to the OSS client. For
details about how to apply for this user account, see Applying for
an OSS User Account.
l If an access control list (ACL) is configured on the U2000/
M2000, add the IP address of the Nastar to the Security > System
ACL of the U2000/M2000 to ensure that the Nastar can access
the U2000/M2000.

Configuring Information about the SAU, including:

information about l IP address and port information of the SAU board for the GSM
NEs on the RAN side or UMTS network.
NOTE
(Required for NEs that have been configured with the RAN SAU server,
which is RH2288 server) You have obtained RAN SAU information and
mapping between the RAN SAU and NEs.
l IP address and port information of the server running the LTE
SAU for the LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 47

Scenario Required Information

Configuring Information about the serving GPRS support node (SGSN/MME)

information about within the analysis area, including:
NEs on the CN side l IP address of the PS SAU server for SGSN/MME
l User name, password, and port number for the FTP service of the
PS SAU server for SGSN/MME
Obtain information about the GGSN/SAE-GW within the analysis
area:
l View the control plane equipment number.
1. Log in to the UGW LMT.
2. Run the display chr device-number command in the OM
view.
l View the user plane equipment number.
1. Log in to the UGW LMT.
2. Run the display service-report server-info command in the
OM view.
l View the time zone and daylight saving time (DST) of the NE.
1. Log in to the UGW LMT.
2. Run the display clock command in any view.

Applying for an OSS User Account

1. Create the user name.
Request OSS engineers to create a user account for the Nastar. Require user to change
password on next login in the basic user information must be deselected to ensure that the
Nastar can log in to the OSS client.
2. Assign operation permissions to the user account.
To ensure normal running of the Nastar, the user account for the Nastar must have the
operation permissions described in Table 2-4.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 48

Table 2-4 Operation permissions

Operation
GUI-based
Permissio Purpose OSS Version
Navigation Path
n

Security > Security Used for invoking the

Management > CORBA interface of the
Operation Rights > DccTool and for creating,
Nastar
Network deleting, and modifying
Collection M2000
Management Nastar-related collection
Task V200R012CXXS
Application > tasks in the following
Manageme PCXXX
Operation > Data themes: GSM uplink
nt
Collection interference analysis and
Management under UMTS uplink interference
a user or user group analysis.

OSS Tool Security > Security Used for using the DccTool
Collection Management > to create data collection tasks
Task Operation Rights > through the centralized task
Manageme Network management function of the
U2000/M2000
nt Management U2000 in the following
V200R013C00 or
Application > themes: GSM uplink
later
Operation > Data interference analysis and
Collection UMTS uplink interference
Management under analysis.
a user or user group

Send MML Security > Security Used for issuing MML

to NE Management > commands to NEs through
Operation Rights > the DccTool in all themes.
Network
U2000/M2000
Management
V200R012C00 or
Application >
later
Operation > Data
Collection
Management under
a user or user group

Query OSS Security > Security Used for invoking the

Basic Info Management > CORBA interface of the
Operation Rights > DccTool to obtain the basic
Network U2000 information (for
U2000/M2000
Management example, the FTP, version,
V200R012C00 or
Application > and DccTool version) in all
later
Operation > Data themes.
Collection
Management under
a user or user group

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 49

Operation
GUI-based
Permissio Purpose OSS Version
Navigation Path
n

Collect NE Security > Security Used for setting performance

PM Data Management > counters and objects for NEs
Operation Rights > and exporting the
Network performance results of NEs
Management (for example, NodeBs) that
U2000/M2000
Application > do not support file interfaces
V200R012C00 or
Operation > Data in the following themes:
later
Collection GSM neighboring cell
Management under analysis, GSM frequency
a user or user group analysis, GSM MR analysis,
and GSM/UMTS
neighboring cell analysis.

Collect NE Security > Security Used for collecting NE

Signal Data Management > signaling data through the
Operation Rights > DccTool in all LTE themes.
Network
U2000/M2000
Management
V200R012C00 or
Application >
later
Operation > Data
Collection
Management under
a user or user group

RAN Pool Security > Security Used for modifying RNC

Manageme Management > pools and BSC pools in all
nt Operation Rights > themes.
Network
Management U2000/M2000
Application > V200R013C00 or
Operation > later
System Operation
> Configuration
Management under
a user or user group

RAN Pool Security > Security Used for querying RNC

Manageme Management > pools and BSC pools in all
nt Browser Operation Rights > themes.
Network
Management U2000/M2000
Application > V200R013C00 or
Operation > later
System Operation
> Configuration
Management under
a user or user group

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 50

Operation
GUI-based
Permissio Purpose OSS Version
Navigation Path
n

Task Security > Security Used for viewing tasks in the

Manageme Management > window for centralized task
nt Operation Rights > management in all themes.
Network
Management
U2000/M2000
Application >
V200R013C00 or
Operation >
later
System
Maintenance >
Task Management
under a user or user
group

3. Bind NEs and command groups

l In RAN16.0 or later, you need to bind NEs and to-be-issued command groups to the
user account.
l The GUI-based navigation path on the OSS is as follows: Security > Security
Management > Bound NE under a user or user group.
l U2000 V200R014C00 or later is supported.

NEs to Be Bound to the User Command Groups to Be Bound to the

Account User Account

BSC6900 GSM, BSC6900 UMTS,

BSC6900 GU, BSC6910 GSM,
G_0, G_1, G_2, G_3 and G_21
BSC6910 UMTS, BSC6910 GU and
BTS3900

2.3.3 Configuring eSAU Information

This section describes how to configure eSAU information. The eSAU aggregates analysis data
preprocessed by the xSAU and exports the data to the Nastar server. You can configure OSS
and NE information only after you have configured information about the eSAU.

Prerequisites
You have obtained relevant information includes the server running the eSAU software.
Information includes the IP address, user name and password for FTP service, and ports.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 51

Context

NOTICE
The Nastar, eSAU, and xSAU communicate with each other based on security protocols (SSL/
SSH protocols) by default to ensure data confidentiality and integrity. The common plaintext
data transfer mode does not provide high security. Before changing the network communication
mode from the security mode to the common mode, you need to obtain a written authorization
from the customer. (A standard authorization must contain the following information: product
or item name, purpose, content, range, time restriction, and other conventions.)
Communication modes among Nastar components (including the Nastar, eSAU, and xSAU)
must be consistent, and the communication modes of external components (such as the U2000/
M2000 and NEs) must also be consistent with the Nastar communication mode. When the
communication mode of one of the Nastar components is switched, those of others also need to
be switched.

Procedure
Step 1 Choose Maintenance > OSS Information Management.

If... Then...

You configure the eSAU information The eSAU modification window will be
firstly, displayed. Please perform Step 2.

You modify the configured eSAU 1. Click eSAU in the navigation tree in the OSS
information, Information Management window.
2. Click Modify.
3. Perform Step 2.

Step 2 In the upper area of the right pane, set basic eSAU server information so that the system can
identify the server, as shown in Figure 2-5.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 52

Figure 2-5 OSS Information Management window

Table 2-5 describes basic eSAU server information.

Table 2-5 Basic eSAU server information

Parameter Description

IP Address IP address of the server running eSAU.

Port Number of the port for logging in to the server. The default port number is
30010.

SSL Port Number of the port for logging in to the server by the security mode. The
default port number is 30110.

Step 3 In the lower area of the right pane, set FTP information so that the system can collect data from
the eSAU server using FTP.

Table 2-6 describes eSAU FTP information.

Table 2-6 eSAU FTP information

Parameter Description

IP Address IP address of the server running eSAU.

Port FTP port of the server. The default port number is 22.

User Name Name of the user for connecting to the FTP service. The default user is
ftpuser.
NOTE
You are advised to use the preset FTP user account of the Nastar. If you use any other
user account, the Nastar may run improperly.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 53

Parameter Description

Password Password of the user for connecting to the FTP service.

Protocol l SFTP: encrypted FTP transfer, which requires the support from the FTP
server. By default, the secure transmission mode (SFTP) is selected.
l FTP: non-encrypted and common FTP mode.
NOTE
The FTP protocol has security risks. You are advised to use security protocols, such
as SFTP and FTPS.If you need to use the insecure transmission mode (FTP), contact
Huawei engineers.

Step 4 Optional: In the Key Info area, set the authentication key information of the Nastar and eSAU.
Table 2-7 describes key-related parameters.
NOTE

To improve the system security, you need to change the initial authentication key as quickly as possible. In
routine maintenance, you need to change the passwords periodically (at an interval of 3 or 6 months) to avoid
security risks, such as violent password cracking.
If you modify the authentication key of the esau and Nastar, you should also modify the authentication key of
the xSAU, otherwise, the xSAU will fail to access the Nastar. See Changing the Authentication Key of the
xSAU in the corresponding Nastar Administrators Guide to modify the xSAU authentication key.

Table 2-7 Key-related parameters

Parameter Description

Allow modifying the key Allows you to modify key information after this parameter is
selected.

Old key Indicates that you need to enter the existing key before
modification.
NOTE
l The default authentication key is ei*b+@b#6Nh(tS1j.
l The new cipher key must contain 16 characters and all types of the
following characters:
l At least one digit
l At least one lowercase letter
l At least one uppercase letter
l At least a special character, such as space and the following
symbols: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ | [ { } ] ; : " , < . > / ?
The special character space cannot be placed at the end of the
cypher key.

New key Indicates that you need to enter the new key after modification.

Confirm key Indicates that you need to re-enter the new key.

Validity period Indicates the validity period of the key. The system displays
information prompting you to change the key after the validity
period elapses.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 54

Step 5 Click OK.

----End

Follow-up Procedure
When information about the OSS and NEs accessed by the Nastar is changed and the Nastar
database has been synchronized with EAMInfo data, you can click Refresh in the lower area of
the navigation tree in the OSS Information Management window to update OSS and NE
information displayed on the Nastar client.
NOTE
The Nastar synchronizes its database with EAMInfo data once every hour. Therefore, after NE information
is changed, you need to wait one hour before you update NE information by clicking Refresh.

2.3.4 Configuring OSS Information

This section describes how to configure OSS information while creating an OSS. After creating
an OSS, the protocols for the interfaces between the Nastar and OSS are initialized. Then, the
Nastar can access OSS devices and collect data from the OSS.

Prerequisites
l You have configured eSAU information.
l You have applied for and obtained the user name and password for logging in to the U2000/
M2000 client. For details about the user rights and requirements, see 2.3.2 Preparations
for OSS and NE Information Configuration.
l You have obtained U2000/M2000 system information, such as the IP address and the
network mode. For details, see Table 2-8, Table 2-9 and Table 2-11 in the Procedure
section.

Context

NOTICE
The Nastar and OSS communicate with each other based on security protocols (SSL/SSH
protocols) by default to ensure data confidentiality and integrity. The common plaintext data
transfer mode does not provide high security. Before changing the network communication mode
from the security mode to the common mode, you need to obtain a written authorization from
the customer. (A standard authorization must contain the following information: product or item
name, purpose, content, range, time restriction, and other conventions.)
Communication modes among Nastar components (including the Nastar, eSAU, and xSAU)
must be consistent, and the communication modes of external components (such as the U2000/
M2000 and NEs) must also be consistent with the Nastar communication mode. When the
communication mode of one of the Nastar components is switched, those of others also need to
be switched.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 55

Procedure
Step 1 Choose Maintenance > OSS Information Management.

Step 2 Click NE Management in the navigation tree in the OSS Information Management window,
as shown in Figure 2-6.

Figure 2-6 NE Management navigation tree

Step 3 Click Create OSS in the lower-right of the window. The window shown in Figure 2-7 is
displayed.

Figure 2-7 OSS information

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 56

Step 4 Set basic OSS information by referring to Table 2-8.

Table 2-8 Basic OSS information

Param Description Mandator

eter y/
Optional

Name A user-defined OSS server name, which must be unique. Mandatory

Type Type of the data collection interface between the U2000/M2000 Mandatory
and the Nastar.
NOTE
l The data collection specifications supported by the OSS might vary from
one OSS version to another. Therefore, when creating an OSS, you need
to set Type to an appropriate value according to the data collection
specifications supported by the OSS.
l For details about the OSS versions supported by the Nastar, see GENEX
Nastar V600RXXXCXX Release Notes.

Networ Networking mode of the U2000/M2000, which includes: Mandatory

k Mode l Single High Availability(HA)
l Remote High Availability(RHA)
l Multi-server load sharing system (SLS)/ATAE Cluster
The default value is Single High Availability(HA).

Server IP address of the U2000/M2000 server. Mandatory

IP l If the U2000/M2000 adopts the HA, RHA, or SLS system, type
the IP address of the master server.
l If you have configured northbound and southbound IP addresses
for the U2000/M2000 servers, type the northbound IP address
of the U2000/M2000 master server.
l If the IP address of the U2000/M2000 master server has been
translated using an NAT device during the communication
between the Nastar server and the U2000/M2000 master server,
you need to type the translated IP address of the U2000/
M2000 master server. In addition, you need to configure the
mapping between the IP address and logical host name of the
U2000/M2000 master server on the Nastar server. For detailed
operations, see Configuring the Mapping Between the IP
Address and Host Name of the Active U2000/M2000 Server on
the Nastar on the Commissioning Guide.

Port Port number used for logging in to the U2000/M2000 server. Mandatory
Generally, the port number is 10511.

User Name of the user for logging in to the U2000/M2000 client. Mandatory
Name

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 57

Param Description Mandator

eter y/
Optional

Passwor Password of the user for logging in to the U2000/M2000 client. Mandatory
d NOTE
If the number of times that users enter incorrect user names or passwords
exceeds the limitation, the system locks the account automatically. In this
case, contact the U2000/M2000 administrator.

Internal IP address for the communication between the U2000/M2000 and Optional
IP the OM network.
NOTE
If the U2000/M2000 is already equipped with southbound and northbound
IP addresses, enter the southbound IP address of the master U2000/M2000
server. This parameter must be set.

SSL Set the U2000/M2000 and the Nastar mode of communication for Mandatory
Availab SSL. By default, the secure communication mode (SSL) is selected.
le NOTE
l The eSAU supports only one communication mode at a time. Therefore,
the communication modes of multiple U2000/M2000 systems must be
the same. Otherwise, basic data subscription fails.
l If the communication mode of the U2000/M2000 is Both or SSL, you
must select the SSL communication mode and enable the SSL port when
adding the U2000/M2000 on the Nastar. Otherwise, adding the U2000/
M2000 on the Nastar fails.

Descrip Description information. Optional

tion

Step 5 Set OSS FTP information by referring to Table 2-9.

Table 2-9 OSS FTP information

Param Description Mandatory/

eter Optional

User Name of the user for connecting to the FTP service on the U2000/ Mandatory
Name M2000.
NOTE
You are advised to use the FTP user account of the U2000/M2000. If you
use any other user account, the Nastar may fail to obtain data from the
U2000/M2000.

Passwo Password of the user for connecting to the FTP service. Mandatory
rd

Port FTP port of the server. The default port number is 22. Mandatory

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 58

Param Description Mandatory/

eter Optional

Mode Transfer mode of the FTP server, consisting of Passive and Mandatory
Active.
l Passive mode: The client sends a connection request to the FTP
port of the server. The server receives the request and sets up
a command link. Before transmitting data, the server sends a
message to the client using the PASV command on the link.
The message indicates that the FTP port on the server is
enabled and the server can be connected. Then, the client sends
a connection request to the server to set up a link for
transmitting data.
l Active mode: The client sends a connection request to the FTP
port of the server. The server receives the request and sets up
a command link. Before transmitting data, the client sends a
message to the server using the PORT command on the link.
The message indicates that the port on the client is enabled and
the client can be connected. In response to the client, the server
sends a connection request through port 20 to establish a link
for transmitting data.

Protoco l SFTP: encrypted FTP transfer, which requires the support from Mandatory
l the FTP server. You must select this protocol if the operating
system of the U2000/M2000 server connected to the Nastar has
been hardened.
NOTE
l If the U2000/M2000 is deployed on a SUN server and its version
is V200R011 or later, the operating system is hardened upon
factory delivery. If the U2000/M2000 version is earlier than
V200R011, you need to check whether the operating system is
hardened based on the description in U2000/M2000
Commissioning Guide.
l If the U2000/M2000 is deployed in an ATAE cluster system, the
operating system is hardened upon factory delivery.
l If the U2000/M2000 is deployed on an IBM server, the operating
system is hardened upon factory delivery.
l FTP: non-encrypted and common FTP mode.
NOTE
The FTP protocol has security risks. You are advised to use security
protocols, such as SFTP and FTPS.

Step 6 Optional: If Type is U2000/M2000 V200R012 or a later version, and you have set U2000/
M2000 to Multi-server load sharing system (SLS)/ATAE Cluster, you need to perform the
following operations to set slave servers:
NOTE
When the U2000/M2000 V200R012 or a later version adopts the SLS system, the data required by the
system is distributed on different servers because the amount of network data is large. When creating an
OSS, you must create a master server before setting the slave servers.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 59

1. In the Slave Server Information area, click Add to open the Add Slave Server dialog
box.
2. Set information about slave servers by referring to Table 2-10.

Table 2-10 Slave server FTP information

Param Description Mandato

eter ry/
Optional

Server IP address of the slave server. Mandator

IP y

NAT Configure the slave server IP address that has been translated Optional
IP using NAT.
If the IP address of the U2000/M2000 master server has been
translated using an NAT device during the communication
between the Nastar server and the U2000/M2000 master server,
you need to set NAT IP.

FTP Name of the user for connecting to the FTP service on the slave Mandator
User server. The default user name is ftpuser. y
Name NOTE
You are advised to use the FTP user account of the U2000/M2000. If you
use any other user account, the Nastar may fail to obtain data from the
U2000/M2000.

FTP Password of the user for connecting to the FTP service. Mandator
Passw y
ord

Port FTP port of the server. The default port number is 22. Mandator
y

Mode Transfer mode of the FTP server, consisting of Passive and Mandator
Active. y
l Passive mode: The client sends a connection request to the
FTP port of the server. The server receives the request and
sets up a command link. Before transmitting data, the server
sends a message to the client using the PASV command on
the link. The message indicates that the FTP port on the server
is enabled and the server can be connected. Then, the client
sends a connection request to the server to set up a link for
transmitting data.
l Active mode: The client sends a connection request to the
FTP port of the server. The server receives the request and
sets up a command link. Before transmitting data, the client
sends a message to the server using the PORT command on
the link. The message indicates that the port on the client is
enabled and the client can be connected. In response to the
client, the server sends a connection request through port 20
to establish a link for transmitting data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 60

Param Description Mandato

eter ry/
Optional

Protoc l SFTP: encrypted FTP transfer, which requires the support Mandator
ol from the FTP server.You must select this protocol if the y
operating system of the U2000/M2000 server connected to
the Nastar has been hardened.
NOTE
l If the U2000/M2000 is deployed on a SUN server and its version
is V200R011 or later, the operating system is hardened upon
factory delivery. If the U2000/M2000 version is earlier than
V200R011, you need to check whether the operating system is
hardened based on the description in U2000/M2000
Commissioning Guide.
l If the U2000/M2000 is deployed in an ATAE cluster system, the
operating system is hardened upon factory delivery.
l If the U2000/M2000 is deployed on an IBM server, the operating
system is hardened upon factory delivery.
l FTP: non-encrypted and common FTP mode.
NOTE
The FTP protocol has security risks. You are advised to use security
protocols, such as SFTP and FTPS.

3. Click OK.
4. Repeat the preceding operations to set parameters of all slave servers.

Step 7 Optional: Configure the Trace Server information by referring to Table 2-11. Only performing
the LTE network analysis, you need set the Trace Server information.
NOTE
When you configure Trace Server information, Version is set to the Trace Server version that the system
automatically obtains from the Trace Server.

Table 2-11 Trace Server FTP information

Param Description Mandatory/

eter optional

Server IP address of the Trace Server. Mandatory

FTP Name of the user for connecting to the FTP service on the Trace Mandatory
User Server.
Name The user for connecting to the FTP service on the Trace Server is
ftpuser.

FTP Password of the user for connecting to the FTP service. Mandatory
Passwo
rd

Port FTP port of the server. The default port number is 22. Mandatory

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 61

Param Description Mandatory/

eter optional

Protoco l SFTP: encrypted FTP transfer, which requires the support from Mandatory
l the FTP server. You must select this protocol if the operating
system of the Trace Server connected to the Nastar has been
hardened.
NOTE
l If the Trace Server is deployed on a SUN server and the U2000/
M2000 version is V200R013 or later, the operating system is
hardened upon factory delivery. If the U2000/M2000 version is
earlier than V200R013, you need to check whether the operating
system is hardened based on the description in U2000/M2000
Trace Server User Guide.
l If the Trace Server is deployed in an ATAE cluster system, the
operating system is hardened upon factory delivery.
l FTP: non-encrypted and common FTP mode.
NOTE
The FTP protocol has security risks. You are advised to use security
protocols, such as SFTP and FTPS.

Step 8 Click OK.

----End

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 62

NOTE
The Nastar synchronizes its database with EAMInfo data once every hour. Therefore, after NE
information is changed, you need to wait one hour before you update NE information by clicking
Refresh.
l Modify OSS information.
1. In the navigation tree, select a node to be modified and click Modify.
2. Modify OSS information.
3. Click OK.
l Delete an existing OSS.
1. Click NE Management in the navigation tree in the OSS Information
Management window.
2. Select an OSS information to be deleted and click Delete OSS.
If the OSS contains collection tasks, the system prompts you to delete the collection
tasks. You can delete the OSS only after all the collection tasks in this OSS are deleted.
3. In the displayed dialog box, click OK.

2.3.5 Configuring NE Information on the RAN Side

Before analyzing RAN data, you need to configure NE information on the RAN side, which
includes information about NEs and related SAUs/LTE SAUs.

Selecting RAN NEs Managed by an OSS

This section describes how to select the RAN NEs managed by an OSS so that the Nastar can
collect the data of these NEs.

Prerequisites
You have created an OSS.

Procedure
Step 1 Choose Maintenance > OSS Information Management.

Step 2 Choose an OSS from the navigation tree in the OSS Information Management window.

Step 3 Click the RAN NE List tab in the right pane, as shown in Figure 2-8.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 63

Figure 2-8 NE List tab page

Step 4 Click Select NE. The Select NE dialog box is displayed.

Step 5 Select NEs managed by the selected OSS.
The NEs to be selected are in the left pane, and the selected NEs are in the right pane.

l Click , , , or to select NEs. You can click a single-arrow

icon to move an NE at a time, or a double-arrow icon to move all NEs.
l You can also select multiple NEs while holding down Ctrl.
l When an NE changes (for example, its name is changed) and reconnects to the Nastar, you
must configure the NE mapping relationship before and after the change. For detailed
operations, see 2.12.4 Supporting Historical Data Analysis on a Changed NE.

NOTICE
l The Nastar does not support NEs whose names contain ampersand (&), comma (,), or single
quotation mark ('). If NE names contain any of the previous characters, data analysis will
fail.
l If an NE is not added to the right pane, the data of this NE cannot be collected to the Nastar
server.

Step 6 Optional: Add LTE NEs to an eNodeB management group.

1. Click eNodeB Management Group Settings. The eNodeB Management Group
Settings dialog box is displayed.
2. Select the eNodeB Management Group and the NEs to be added to the group.
The NEs to be selected are in the left pane, and the selected NEs are in the right pane.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 64

l Click , , , or to select NEs. You can click a single-

arrow icon to move an NE at a time, or a double-arrow icon to move all NEs.
l You can also hold down Ctrl to select multiple NEs.
3. Click OK.
NOTE
You can also add an NE to an eNodeB management group in the following way: In the List of selected

NEs of the Select NE dialog box, click following a selected LTE NE in the eNodeB Management
Group column.

Step 7 Click OK.

----End

Follow-up Procedure
l When information about the OSS and NEs accessed by the Nastar is changed and the
Nastar database has been synchronized with EAMInfo data, you can click Refresh in the
lower area of the navigation tree in the OSS Information Management window to update
OSS and NE information displayed on the Nastar client.
NOTE
The Nastar synchronizes its database with EAMInfo data once every hour. Therefore, after NE
information is changed, you need to wait one hour before you update NE information by clicking
Refresh.
l Synchronize basic NE information.
After NE information is changed, you need to update NE version information manually.
This ensures that the Nastar performs analysis based on the latest NE information.
1. In the navigation tree of the OSS Information Management window, select the OSS
you want to modify.
2. On the RAN NE List tab page, click Sync NE Basic Info. The Nastar then
automatically obtains EAMInfo data from the OSS and updates NE information
displayed on the client.
NOTE
If two NEs change their names on the M2000, the Nastar cannot synchronize information about the two
NEs from the M2000.
l Migrate NEs managed by an OSS system.
When an OSS system is upgraded or the network is adjusted onsite, some NEs need to be
migrated from the OSS system to the other OSS system. In this situation, the Nastar needs
to modify the saved mapping between the OSS system and NEs. With the NE migration
function, user operations and data subscription wait time can be reduced.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 65

NOTICE
l Basic subscription and application subscription need to be re-enabled for LTE NEs.
l Application data subscription needs to be re-enabled for the GSM MR Analysis, GSM
Neighboring Cell Analysis, GSM/UMTS Neighboring Cell Analysis, GSM Uplink
Interference Analysis, UMTS Uplink Interference Analysis, and functions.

1. In the navigation tree of the OSS Information Management window, choose an OSS
you want to modify.
2. On the RAN NE List tab page, click NE Migration. The NE Migration dialog box
is displayed.
3. In the Original OSS area, select the OSS from which you want to migrate NEs.
4. In the Destination OSS area, select the OSS to which you want to migrate NEs.
5. Select NEs you want to migrate.
The NEs to be selected are in the left pane, and the selected NEs are in the right pane.
An NE exists in only the left or right pane.
– You can search for NEs to be migrated using the Find function.
– You can also click Batch Select NEs to import the information list of NEs to be
migrated, thereby completing batch NE migration.
NOTE
The NE information list can be an XLS, XLSX, or CSV file and must contain the
NEName column.
– You can also click Auto-Analyze to analyze the OSS configuration data, thereby
determining whether NEs managed by the selected OSS system have been
migrated and whether NEs need to be migrated to a new OSS system.

– Click , , , or to select NEs. You can click a

single-arrow icon to select one or more NEs, or a double-arrow icon to select all
NEs.
– You can also hold down Ctrl to select multiple NEs.
6. Click OK.
l Modify NEs managed by an OSS.
1. Select an OSS node to be modified in the navigation tree of the OSS Information
Management window.
2. On the RAN NE List tab page, click Select NE to reselect NEs managed by the OSS.
3. Click OK.
l Modify the description of the NEs managed by the OSS.
1. Select an OSS node to be modified in the navigation tree of the OSS Information
Management window.
2. Select an NE row on the RAN NE List tab page.
3. Click Modify Description to add description for the NE.
4. Click OK.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 66

Configuring SAU or LTE SAU Information

This section describes how to configure the SAU information. On the GSM or UMTS network,
if you want to use the analysis function depending on the SAU board, you must configure the
SAU information. On the LTE network, you must configure the LTE SAU information.

Prerequisites
l You have selected an NE.
l You have obtained related SAU information.
– (Required for NEs that have been configured with the RAN SAU server, which is
RH2288 server) You have obtained RAN SAU information and mapping between the
RAN SAU and NEs.
– If the SAU version does not correspond to the Nastar version, the Nastar cannot obtain
related data for geographic observation. The SAU version must correspond to the Nastar
version.

Context
l On the GSM network, the data used for GSM MR analysis, GSM neighboring cell analysis,
GSM frequency analysis, GSM/UMTS neighboring cell analysis, and GSM uplink
interference analysis is the GSM performance data or uplink interference data which is
collected from the U2000/M2000, and therefore the SAU board is not required. The data
used in all the other analysis functions, however, is collected from NEs through the SAU
board, and therefore you must configure the SAU information.
l On the UMTS network, the data used for UMTS uplink interference analysis is the received
total wideband power (RTWP) data which is collected from the U2000/M2000, and
therefore the SAU board is not required. The data used in all the other analysis functions,
however, is collected from NEs through the SAU board, and therefore you must configure
the SAU information.
l On the LTE network, the data used in all analysis functions is collected from NEs through
the LTE SAU, and therefore you must configure the LTE SAU information.
l For a newly added NE, after setting the SAU, you must turn on the anonymization switch
again. For detailed operations, see 2.4.2 Setting the Nastar Non-Anonymization Data
Analysis Switch.

Procedure
Step 1 Choose Maintenance > OSS Information Management.

Step 2 In the navigation tree in the left pane of the OSS Information Management window, select an
OSS node.

Step 3 Click the RAN NE List tab in the right pane, as shown in Figure 2-9.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 67

Figure 2-9 NE list tab page

Step 4 Set SAU parameters.

If... Then...

The selected NE belongs to the GSM or You must perform this step to set the IP address and
UMTS network and the SAU board port number of the SAU. Otherwise, the analysis
has been installed functions such as the VIP analysis and complaint
analysis of the SAU are unavailable to the NE.
NOTICE
For NEs that have been configured with the RAN SAU
server (RH2288 server), the IP address and port number
need to be set to those of the RAN SAU (RH2288 server)
instead of those of the SAU board.

The NE belongs to the GSM or UMTS No information needs to be configured.

network but the SAU board has not
been installed

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 68

If... Then...

The NE belongs to the LTE network You must perform this step to set the IP address and
port number of the server that installing the LTE
SAU software.
NOTE
l Before you set the IP address of LTE SAU, stop the
subscription first.
l Perform the following method to set the IP address:
l If the LTE SAU is deployed by using the
standalone deployment scheme, you need to set
the IP address to the IP address of the server that
runs the LTE SAU software.
l If the LTE SAU is deployed by using the
distributed deployment scheme, you need to set
the IP address to the IP address of the master
server that runs the LTE SAU services.

1. Select an NE row.
2. Click Modify SAU > Configure SAU to configure the SAU or LTE SAU information.
3. Set the IP address and port number of the SAU.
The default port is 30020, the default port of security mode is 30120.
4. Click OK.
NOTE

In the RNC In Pool scenario, for all the physical RNCs belonging to the same RNC In Pool, must configure
the SAU information before performing basic subscription.

Step 5 Optional: View details about the selected NE.

1. View details about the selected NE on the RAN NE List tab page, including the NE type,
NE FDN, and NE version.
2. View the SAU information about the NE.
3. Optional: If you are required to collect configuration data immediately, select one or more
NEs and click Immediately Collect Configuration Data.

By default, the start time for collecting configuration data is the start time of the data
collection service, and the period is 6 hour. For example, the start time of the data collection
service is 6:00, so the next execution time is 12:00. The start time of the data collection
service is the same as the start time of the system service.

After clicking Immediately Collect Configuration Data, the system will immediately
collects configuration data in the OSS instead of collecting the data until the default time.
If the system is executing another collection task, the task that you trigger manually will
be automatically executed after the running task is complete.

----End

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 69

Follow-up Procedure
l Delete the SAU configuration information: Select a record of SAU configuration
information, click Modify SAU > Delete SAU and then click OK.
In the RNC In Pool scenario, when deleting the SAU information of a physical RNC, stop
the subscription of the logical RNC of the pool formed by the physical RNC.
l View information about the collection and import of configuration data in the Log Info
area. Table 2-12 lists the parameters.

Table 2-12 Log parameters

Parameter Description

Time Time when a task is complete.

Function Log type such as configuration data collect and import.

Severity Level of the log, including Minor and Major. You are advised to
focus on the Major level log information.

Operation User User that executes a task. The default user is system.

NE Name Names of NEs involved in a task.

l For the GSM and UMTS networks, logs are recorded on the
base station controller basis, and a controller records one log
entry.
l For the LTE network, logs are recorded on the eNodeB basis,
and an eNodeB records one log entry.

Subject Type Data type, such as configuration data.

Operation Name Task type, such as data collection, data import, or basic NE
information update.

Operation Result Operation result. The value can be Succeed or Failure.

Details Detailed information about the operation result, for example, the
path of analysis data on the Nastar server after data collection or
the reason why operation fails.

– Select Function, Severity, Condition, and type the keyword. Click Filter to filter the
log information.
– It displays the latest 100 log information by default in the Logs area. Click Show All,
the Log Manager window is opened. You can view all of the log information generated
within seven days.
– Click Show All, the Log Manager window is opened. Right-click the log list and choose
Save As from the shortcut menu to save the log information.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 70

Configuring LTE eNodeB Management Group (Optional)

This section describes how to add a newly accessed eNodeB to a specified eNodeB management
group.

Prerequisites
l You have completed LTE NE configurations. For detailed operations, see Selecting RAN
NEs Managed by an OSS.
l You are authorized for LTE eNodeB management group operations.

Context
The OSS information management function enables users to add a newly accessed eNodeB to
a specific eNodeB management group. If an SAU, configuration data collection and import, and
data subscription delivery have been set for the eNodeB management group, the following
operations need to be performed:
l The Nastar system automatically sets an SAU for the newly accessed eNodeB.
l The Nastar system automatically collects and imports configuration data for the newly
accessed eNodeB.
l The Nastar system automatically sets user rights for the newly accessed eNodeB.
l The Nastar periodically scans the newly accessed eNodeB, and users need to issue basic
subscription and application subscription tasks.
NOTE
An eNodeB can belong to only an eNodeB management group or does not belong to any eNodeB
management group.

Procedure
Step 1 Choose Maintenance > OSS Information Management.

Step 2 In the navigation tree of the OSS Information Management window, select an OSS node.

Step 3 Click the LTE eNodeB Management Group tab in the right pane.

Step 4 Click New to open the New eNodeB Management Group dialog box.

Step 5 Set a name for eNodeB Management Group and select the NEs to be manged by the OSS.

The NEs to be selected are in the left pane, and the selected NEs are in the right pane.

l Click , , , or to select NEs. You can click a single-arrow

icon to move an NE at a time, or a double-arrow icon to move all NEs.
l You can also select multiple NEs while holding down Ctrl.
l Alternatively, you can click Batch Select NEs. In the displayed Open dialog box, select the
NE information file you want to import. The file can be in CSV, XLS, or XLSX format and
must contain an NEName column.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 71

NOTICE
The Nastar does not support the NEs whose names contain ampersand, (&), comma (,), or single
quotation mark ('). If NE names contain any of the previous characters, data analysis will fail.

Step 6 Click OK.

----End

Follow-up Procedure
l Modify the NEs managed by the eNodeB management group.
1. In the navigation tree of the OSS Information Management window, choose an OSS.
2. On the LTE eNodeB Management Group tab page, select the eNodeB management
group, click Edit, and rename the eNodeB management group and select NEs.
3. Click OK.
NOTE
If you need to add an eNodeB to an eNodeB management group, adjust the rights of such eNodeBs
based on the following principles:
If the rights of an eNodeB before being added to the eNodeB management group are higher than the
rights of the eNodeB management group, the rights of an eNodeB are used. If the rights of an eNodeB
before being added to the eNodeB management group are lower than the rights of the eNodeB
management group, the rights of the eNodeB management group are used.
l View the automatic operation rights list of the eNodeB management group and NEs.
1. In the navigation tree of the OSS Information Management window, choose an OSS.
2. On the LTE eNodeB Management Group tab page, select the eNodeB management
group and click Query Auto Operation List.
l Delete the NEs managed by the eNodeB management group.
1. In the navigation tree of the OSS Information Management window, choose an OSS.
2. On the LTE eNodeB Management Group tab page, select the eNodeB management
group and click Delete.
3. In the displayed Confirm dialog box, click Yes.
NOTE
If an eNodeB is deleted from an eNodeB management group, its rights remain unchanged.

Querying RNC In Pool Information (Optional)

This section describes how to query information about a logical RNC based on the mapping
between the logical RNC and its physical RNCs. It helps you further locate problems if the RNCs
that connect to the Nastar are RNCs in an RNC pool and you fail to perform a theme analysis
because the logical RNC malfunctions.

Prerequisites
You have deployed an OSS system.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 72

Context
If the U2000/M2000 is in V200R013C00 or a later version, the Nastar supports RNC pooling,
and you can:
l Directly select and add a logical RNC. However, after you add a logical RNC, only the
physical RNCs instead of the logical RNC are displayed on the RAN NE List tab page.
l Configure SAU information by physical RNC.
l Perform theme analysis by logical RNC. The analysis results are also displayed by logical
RNC.

Procedure
Step 1 Choose Maintenance > OSS Information Management.

Step 2 In the navigation tree of the OSS Information Management window, select an OSS node.

Step 3 In the right pane, click the RNC In Pool tab, as shown in Figure 2-10.

Figure 2-10 RNC In Pool tab page

----End

2.3.6 Configuring NE Information on the CN Side

Before analyzing CN data, you need to configure NE information on the CN side, which includes
information about SGSNs and related PS SAUs.

Selecting CN NEs Managed by an OSS

This section describes how to select core network (CN) NEs managed by an OSS system so that
the Nastar can collect the data of these NEs. Only the SGSN/MME and GGSN/SAE-GW are
supported currently.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 73

Prerequisites
You have created an OSS system.

Procedure
Step 1 Choose Maintenance > OSS Information Management.

Step 2 In the navigation tree in the left pane of the OSS Information Management window, select an
OSS node.

Step 3 Click the PS Core NE List tab in the right pane, as shown in Figure 2-11.

Figure 2-11 NE list tab page

Step 4 Click Select NE. The Select NE dialog box is displayed.

Step 5 Select NEs managed by the selected OSS system.

The NEs to be selected are in the left pane, and the selected NEs are in the right pane. An NE
exists only in the left or right pane.

l Click , , , or to select NEs. You can click a single-arrow

icon to select an NE or multiple NEs at a time, or a double-arrow icon to select all NEs.
l You can also hold down Ctrl to select multiple NEs.
l If an NE is changed (for example, the name is changed), configure its matching relationship
before and after the change. For detailed operations, see 2.12.4 Supporting Historical Data
Analysis on a Changed NE.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 74

NOTICE
l The Nastar does not support NEs whose names contain ampersand (&), comma (,), or single
quotation mark ('). If NE names contain any of the preceding characters, data analysis fails.
l If an NE is not added to the right pane, the data of this NE cannot be collected to the Nastar
server.

Step 6 Click next to the selected NE in the right pane. Set the NE equipment number, time zone,
and daylight saving time (DST).
The GGSN/SAE-GW and SGSN/MME do not support MML commands. Therefore, you have
to manually set the information on the Nastar after querying related NE equipment number, time
zone, and DST information on the LMT.
l GGSN/SAE-GW: You have to set the control plane equipment number, user plane equipment
number, and DST. For details about how to obtain the information, see 2.3.2 Preparations
for OSS and NE Information Configuration.
l SGSN/MME: You have to set the time zone and DST. For details about how to obtain the
information, see 2.3.2 Preparations for OSS and NE Information Configuration.

Step 7 Click OK.

----End

Follow-up Procedure
l When information about the OSS and NEs accessed by the Nastar is changed and the
Nastar database has been synchronized with EAMInfo data, you can click Refresh in the
lower area of the navigation tree in the OSS Information Management window to update
OSS and NE information displayed on the Nastar client.
NOTE
The Nastar synchronizes its database with EAMInfo data once every hour. Therefore, after NE
information is changed, you need to wait one hour before you update NE information by clicking
Refresh.
l Synchronize basic NE information.
After NE information is changed, you need to update NE version information manually.
This ensures that the Nastar performs analysis based on the latest NE information.
1. In the navigation tree of the OSS Information Management window, select the OSS
you want to modify.
2. On the PS Core NE List tab page, click Sync NE Basic Info. The Nastar then
automatically obtains EAMInfo data from the OSS and updates NE information
displayed on the client.
NOTE
If two NEs change their names on the M2000, the Nastar cannot synchronize information about the two
NEs from the M2000.
l Migrate NEs managed by an OSS system.
When an OSS system is upgraded or the network is adjusted onsite, some NEs need to be
migrated from the OSS system to the other OSS system. In this situation, the Nastar needs

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 75

to modify the saved mapping between the OSS system and NEs. With the NE migration
function, user operations and data subscription wait time can be reduced.
1. In the navigation tree of the OSS Information Management window, choose an OSS
you want to modify.
2. On the PS Core NE List tab page, click NE Migration. The NE Migration dialog
box is displayed.
3. In the Original OSS area, select the OSS from which you want to migrate NEs.
4. In the Destination OSS area, select the OSS to which you want to migrate NEs.
5. Select NEs you want to migrate.
The NEs to be selected are in the left pane, and the selected NEs are in the right pane.
An NE exists in only the left or right pane.
– You can search for NEs to be migrated using the Find function.
– You can also click Batch Select NEs to import the information list of NEs to be
migrated, thereby completing batch NE migration.
NOTE
The NE information list can be an XLS, XLSX, or CSV file and must contain the
NEName column.
– You can also click Auto-Analyze to analyze the OSS configuration data, thereby
determining whether NEs managed by the selected OSS system have been
migrated and whether NEs need to be migrated to a new OSS system.

– Click , , , or to select NEs. You can click a

single-arrow icon to select one or more NEs, or a double-arrow icon to select all
NEs.
– You can also hold down Ctrl to select multiple NEs.
6. Click OK.
l Modify NEs managed by an OSS system.
1. In the navigation tree of the OSS Information Management window, choose an OSS
you want to modify.
2. On the PS Core NE List tab page, click Select NE to select NEs managed by the OSS
system again.
3. Click OK.
l Modify the description of the NEs managed by the OSS system.
1. In the navigation tree of the OSS Information Management window, select an OSS
node you want to modify.
2. On the PS Core NE List tab page, select an NE row.
3. Click Modify Description to add description for the NE.
4. Click OK.

Configuring PS SAU Information

This section describes how to configure PS SAU information. After you configure PS SAU
information, the Nastar can collect data from the CN.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 76

Prerequisites
l You have selected NEs.
l You have obtained relevant PS SAU information.
l Before you set the IP address of LTE SAU, stop the subscription first.

Procedure
Step 1 Choose Maintenance > OSS Information Management.

Step 2 In the navigation tree in the left pane of the OSS Information Management window, select an
OSS node.

Step 3 Click the PS Core NE List tab in the right pane, as shown in Figure 2-12.

Figure 2-12 NE list tab page

Step 4 Set the PS SAU information.

1. Select an NE row.
2. Click Modify SAU > Configure SAU to configure the PS SAU information.
3. Configure the IP address and port of the SAU.

Table 2-13 SAU information

Parameter Description

SAU IP IP address of the PS SAU server for SGSN/MME or GGSN/SAE-

GW.

SAU Port Port number of the PS SAU server for SGSN/MME or GGSN/SAE-
GW. The default port number is 30030 and the default SSL port
SSL Port number is 30130.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 77

Parameter Description

PS SAU ID(EVU) ID of the CHR server when USN9810 V900R013C00 or later is

used and the USN9810 is equipped with an EVU board. This ID,
which is allocated by the USN9810 to the Nastar, corresponds to
the configuration parameter SVRNUM on the USN9810. The value
of this parameter, which is used to obtain USN CHR data, is unique
in the Nastar system. This parameter is optional.
Data needs to be re-subscribed to after the value of this parameter
is changed.

4. Click OK.

Step 5 Set the time zone information.

1. Select an NE row.
2. Click NE Information Setting.
3. Set Time Zone.
4. Select DST Available. It does not need to be set.

After selecting DST Available, set the start time and end time of DST.
5. Click OK.

Step 6 Optional: Set NE descriptive information.

1. Select an NE.
2. Click Modify Description.
3. Set Description.
4. Click OK.

Step 7 Optional: View details about the selected NE on the PS Core NE List tab page, including the
NE type, NE FDN, NE version, and PS SAU information about the NE.

----End

2.3.7 Setting the Vendor Type of EPCs (MMEs)

The Nastar can access Huawei and third-party EPCs (MMEs) to collect and combine MME call
history records (CHRs) and eNodeB CHRs, thereby obtaining IMSI and IMEI information used
for LTE network optimization analysis (such as complaint analysis support, VIP analysis, cell
performance analysis, and terminal analysis).

Prerequisites
l You have loaded the basic LTE license file.
l You have disabled the basic subscription and application subscription of LTE complaint
analysis support, LTE VIP analysis, LTE cell performance analysis, and LTE terminal
analysis.
l You have confirmed the vendor type of the EPCs (MMEs) to be accessed by the Nastar.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 78

Procedure
Step 1 Choose Maintenance > EPC(MME) Vendor Setting.
NOTE
If the Information window is displayed, click OK.

Step 2 In the EPC (MME) Vendor Settings dialog box, set EPC (MME) Vendor.
l HUAWEI: indicates that the Nastar accesses only Huawei MMEs.
l Other vendor: indicates that the Nastar accesses only third-party MMEs.
l HUAWEI + Other vendor: indicates that the Nastar accesses Huawei and third-party MMEs
at the same time.
l Non-interconnection: indicates that the Nastar does not access MMEs and obtains the TMSI
information from eNodeBs. It applies when the network optimization is based on the TMSI
rather than IMSI.
NOTE

When EPC (MME) Vendor is set to Non-interconnection, the Nastar supports LTE complaint analysis
and cell performance analysis, but not VIP query and analysis.

Step 3 Click OK.

Step 4 Re-deliver the basic subscription and application subscription of LTE complaint analysis
support, LTE VIP analysis, LTE cell performance analysis, and LTE terminal analysis to obtain
analysis data.

----End

2.3.8 Configuring Relationships Between HSSs and eNodeBs

(Optional)
This section describes how to manually configure the relationships between home subscriber
servers (HSSs) and eNodeBs before using the LTE all-signaling analysis function. The Nastar
delivers LTE all-signaling subscription tasks to eNodeBs through HSSs.

Prerequisites
l You have obtained information about the eNodeBs to which the Nastar will deliver LTE
all-signaling subscription tasks.
l You have confirmed the HSSs serving involved eNodeBs.
l You have obtained information about the OSS (U2000/M2000) that manages each HSS.
l The HSS version is V900R008C01 or later, the TS version is V200R013C01CP2201 or
later, and the U2000/M2000 version is V200R013C00SPC200 or later.

Procedure
Step 1 Set information about the OSS that manages each HSS.

For detailed operations, see 2.3.4 Configuring OSS Information.

Step 2 Add an HSS.

1. Choose Maintenance > OSS Information Management.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 79

2. In the navigation tree of the OSS Information Management window, select the OSS node
that manages the HSS.
3. Click the PS Core NE List tab in the right pane.
4. Click Select NE.
5. Select the HSS.
The HSS is moved from the left area to the right area.
6. Click OK.

Step 3 Configure the relationships between an HSS and eNodeBs.

1. Click the HSS/eNodeB tab in the right pane.
2. Click Adjust HSS/eNodeB Relationship.
3. In the displayed Adjust HSS/eNodeB Relationship dialog box, set HSS Name to HSS
and select the eNodeBs that the HSS serves in the NE List window.
4. Click OK.

----End

2.4 Configuring the Anonymous Policy

2.4.1 Setting the NE Data Anonymization Protection Policy

Huawei wireless NEs accessed by the Nastar support the personal data anonymization policy.
They use the HMAC-SHA256 algorithm to perform unidirectional Hash computation of user
identifiers contained in records (such as CHRs, MRs, xDRs, and UFDRs) and replace the original
user identifiers with the computation results. After user identifiers are anonymized, natural
persons cannot identified in such records, providing a good protection mechanism for personal
data and minimizing impacts on original OM services. You can enable or disable the
anonymization policy on the U2000. In addition, you can change the key for the anonymization
algorithm on the U2000, To ensure data security, you are advised to periodically change the
anonymization key.

Context

NOTICE
Enable the personal data anonymization policy based on laws and regulations of countries
concerned and operators' personal data protection requirements.

l The U2000 centrally controls the anonymization switch and encryption key for all managed
NEs. The encryption key is managed only by operators. Engineers on the NE side cannot
independently configure or query the encryption key.
l Users can centrally turn on or turn off the anonymization switch on the U2000. By default,
this switch is turned off before factory delivery. Engineers on the NE side can query the
status of the anonymization switch but cannot the switch status.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 80

l The Nastar can obtain the key fingerprint (the SHA256 value), query the status of the
anonymization switch on the U2000, and check whether the keys on multiple U2000 are
consistent. However, the Nastar does not obtain the key for the HMAC-SHA256 algorithm.
l The U2000 provides a default key. A key can be updated onsite as required and must be
securely and permanently stored. A key cannot be configured or queried on NEs. Users are
advised to manually update the key.

Procedure
Step 1 For details about how to configure the anonymization policy and key on the U2000, see
Operation and Maintenance > Fault Management > FARS > Anonymous Policy
Management > Configuring the Anonymous Policy and Anonymity Key in iManager U2000
MBB Network Management System Product Documentation.

You can obtain iManager U2000 MBB Network Management System Product Documentation
by choosing Support > Product Support > Wireless Network > SingleOSS > M2000 >
M2000-Common > iManager U2000-M at http://support.huawei.com.

----End

2.4.2 Setting the Nastar Non-Anonymization Data Analysis Switch

This section describes how to set the Nastar non-anonymization data analysis switch. By setting
the non-anonymization data analysis switch, users can determine whether to perform Nastar
analysis tasks by using non-anonymized personal data.

Prerequisites
l You have applied for the license for non-anonymized data analysis.
l You have configured OSS and NE information. For detailed operations, see 2.3.5
Configuring NE Information on the RAN Side.
l Check that you have the operation rights to manage Anonymity Key Management.

Context
l Only user admin or users in the administrators group have the rights to manage
Anonymity Key Management.
l When the non-anonymization data analysis switch is set to OFF, Nastar analysis tasks are
performed using anonymized personal data. Nastar analysis tasks are performed using
anonymized personal data.
l If the status of the data anonymization switch is different among multiple U2000 systems
that access the Nastar system, you might fail to create an analysis task for analyzing data
of multiple U2000 systems. If this occurs, you can turn on the non-anonymization data
analysis switch; alternatively, you can contact U2000 engineers to turn on or off the U2000
data anonymization switch.
l You need to reset the non-anonymization data analysis switch after you change or add OSS
and NE configuration.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 81

Procedure
Step 1 On the Nastar client, check the anonymization data analysis switch status of the U2000 and the
current key hash value.

Option Description

The OSS anonymization switch is turned on. User identifiers in the data files collected and
stored by the Nastar are anonymized. User
identifiers in the database and displayed on the
Nastar client are anonymized. To ensure that
Nastar feature can be used properly, contact
operators to obtain anonymized personal data
for analysis.

Operators need to contact Huawei technical

support engineers to obtain the anonymization
tool from the following address and then
scramble data in the same way as NEs do
through the HMAC-SHA256 algorithm:
Support > Software > Global Service >
Managing Customer Experience Service-
SmartCare > Network Optimization
Service > GENEX Mobile Manager >
HMACUtil

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 82

Option Description

The OSS anonymization switch is turned By default, the non-anonymization data

off. analysis switch is turned off on the Nastar,
That is, Nastar analysis tasks are performed
using anonymized personal data. The SAU
does not automatically process CHR-related
theme data. As a result, the VIP analysis,
complaint analysis support, terminal
inventory analysis, and terminal geographic
observation themes cannot report data
properly, and the in-depth analysis cannot be
performed based on the cell performance
analysis results.

Comply with laws and regulations of

countries concerned and operators' personal
data protection requirements. If operators
allows the Nastar to use plaintext user
identifiers and have applied for the license for
non-anonymized data analysis, perform the
following operations to turn on the non-
anonymized data analysis switch:
1. Choose Security > Anonymity Key
Management.
2. In the displayed Anonymity Key
Management window, click Non–
Anonymization Data Analysis Switch.
The status of the non-anonymization data
analysis switch is displayed in State.
3. In the displayed Non–Anonymization
Data Analysis Switch dialog box, select
ON.
4. Click OK. The setting is complete.

1. Choose Security > Anonymity Key Management.

2. In the left pane of the Anonymity Key Management window, Current Key Info is
displayed for the U2000. You can view the status of the data anonymization switch and the
current key hash value in State and Current Key Hash Value.

Table 2-14 describes the State of the data anonymization switch:

Table 2-14 Switch status description

Status Description

ON The data anonymization switch of the

U2000 is turned on.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 83

Status Description

OFF The data anonymization switch of the

U2000 is turned off, and therefore the
current cipher key hash value is null.

Abnormal The Nastar might fail to set up a connection

with the U2000 or the U2000 does not
support the data anonymization switch.
Therefore, the current cipher key hash
value is null.

3. In the Anonymity Key Management window, you can click Check Now to manually
check the current cipher key hash value of the U2000 and click Refresh to manually refresh
the historical cipher key information.
Historical Key Info is displayed in the right pane of the Anonymity Key Management.
You can select Show modified records or Show all records to view the historical cipher
key information about the U2000.
NOTE

l By selecting Show modified records, you can view the change history of the non-anonymization
data analysis switch for an U2000, including the change history of Cipher Key Hash Value or
State.
l If the Nastar task analysis duration includes the time when the U2000 cipher key hash value
changes, errors might occur in the task analysis result.
l The Nastar system automatically checks the data anonymization switch of the U2000 every 30
minutes. You can select Show all records to view all historical cipher key information.

----End

2.5 Preparing Basic Data

This section describes how to collect basic data including configuration data, engineering
parameters, and map information before analyzing data.

2.5.1 Introduction to Basic Data

This section describes the basic data used for Nastar analysis, including configuration data,
engineering parameters, map files, and other data (NE group information, terminal information,
VIP information, complaining subscriber information, mailbox information, and so on).

Table 2-15 describes basic data related to the Nastar.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 84

Table 2-15 Basic data

Da M Description
ta an
Ty dat
pe or
y
or
Op
tio
nal

Co Ma Function: Configuration data contains the basic information for network

nfi nda optimization, which is used for the Nastar to correctly retrieve data of each cell
gur tor from data sources.
ati y Acquisition means: The Nastar automatically retrieves the configuration data
on from a specific path of the U2000/M2000 or OMC after users have configured
dat the OSS information on the Nastar.
a
Data format: The data format is related to NE versions. Files in .dat, MML,
and .xml.gz formats are supported for GSM, files in MML and .xml.gz formats
are supported for UMTS, and files in .xml.gz format are supported for LTE.

En Op Function: Engineering parameters, which contain basic information for network

gin tio optimization such as the longitude and latitude of a site, antenna azimuth, and tilt
eer nal angle, help Nastar to achieve accurate geographic display.
ing Acquisition means: Contact the onsite administrator.
par
am Data format: Engineering parameter files in .xls, .xlsx, or .csv format are
ete available.
rs

Ma Op Function: Electronic maps help Nastar to achieve accurate geographic display

p tio for desired regions.
file nal Acquisition means: Contact the onsite administrator.
s
Data format: Map files in .wor, .tab, or .sxwu format are available. If the PC is
connected to the Internet, you can view analysis results on the Google Earth.
NOTE
Users can convert the map files in wor or tab format to those in sxwu format by using the
map conversion function provided by Nastar.

NE Op Function: Users can group NEs to facilitate analysis on site. You must create NE
gro tio groups during LTE analysis (excluding complaint analysis) and can create NE
up nal groups for other radio access technologies (RATs) as required.
inf Acquisition means: Users can create NE groups on their own needs or by
or selecting NEs of specific regions in the GIS window.
ma
tio Data format: NE group information files in .xls, .xlsx, or .csv format can be
n imported and exported.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 85

Da M Description
ta an
Ty dat
pe or
y
or
Op
tio
nal

Ter Op Function: The terminal information, such as the model, radio access technology
mi tio (RAT), and vendor, is used during terminal analysis.
nal nal Acquisition means: Contact the onsite administrator.
inf
or Data format: Terminal information files in .xls, .xlsx, or .csv format can be
ma imported and exported.
tio
n

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 86

Da M Description
ta an
Ty dat
pe or
y
or
Op
tio
nal

VI Op Function: The VIP information, such as a NOTE

P tio specific VIP and its IMSI, is used during The Nastar provides sufficient
protection for service data used by this
inf nal VIP analysis.
function, such as IMSI and IMEI
or Acquisition means: Contact the onsite information, to ensure personal data
ma administrator. security. For details about the service
tio data and protection policies,
n Data format: VIP files in .csv format can seeDescriptions > Nastar Security
be imported and exported. Description > Application Security >
Protecting Private Subscriber Data.
Co Op Function: The complaining subscriber
The Nastar provides an anonymization
mp tio information, such as the complainer, its mechanism for processing personal
lai nal IMSI/MSISDN, peer MSISDN of the data, such as the IMSI, IMEI,
nin complainer, or time and location MSISDN, and IMEISV. After this
g information about the complaint, is used mechanism is used, the Nastar no
sub during complaint analysis. longer allows you to enter the plaintext
IMSI and MSISDN. In this situation,
scr Acquisition means: Contact the onsite you need to contact telecom operators
ibe administrator. to obtain the encrypted IMSI. The
r Nastar does not support the encrypted
inf Data format: The IMSI, MSISDN, or peer MSISDN. Telecom operators can
or MSISDN in .xls, .xlsx, or .csv format can contact the Huawei technical support
ma be imported. You can also export existing engineers to visit http://
tio subscriber information to files support.huawei.com and choose
in .xls, .xlsx, or .csv format. Support > Software > Global
n Service > Managing Customer
Experience Service-SmartCare >
Network Optimization Service >
GENEX Mobile Manager >
HMACUtil.
You have checked whether the
subscriber identity anonymization
switch or the encryption key is
changed. If the subscriber identity
anonymization switch or the
encryption key is changed, see 2.12.3
Troubleshooting Problems Caused
by Change of the Subscriber Identity
Anonymization Switch or the
Encryption Key.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 87

Da M Description
ta an
Ty dat
pe or
y
or
Op
tio
nal

Ma Op Function: The mailbox information, such as the mailboxes of the sender and
ilb tio recipient, is used during automatic analysis report sending. It is currently used
ox nal only for VIP analysis and the PS Core root cause analysis.
inf Acquisition means: Contact the onsite administrator.
or
ma Data format: Address books in .xls, .xlsx, or .csv format can be imported and
tio exported.
n

Kn Op Function: PS Core knowledge bases manage information such as failure cause

ow tio values, failure cause description, and related solutions to exceptions that occur
led nal during theme analysis. This helps you quickly check the maintenance experience
ge when exceptions occur.
bas Acquisition means: The system already exists this information by default. If you
es need to upgrade, contact the Huawei engineers.
Data format: Files in .xls, .xlsx, or .csv format can be imported and exported.

Lo Op Function: You can minimize the distortion of geographic observation data by

cat tio properly setting parameters based on the areas on the sphere.
ion nal Acquisition means: By default, the system uses the first engineering parameter
par record. You need to set the parameters only if the default engineering parameters
am do not meet requirements. If you need to modify, set it.
ete
rs Data format: None.

Da Op Function: The data service servers information is used during VIP analysis for
ta tio analyzing the servers.
ser nal Acquisition means: Contact the onsite administrator.
vic
e Data format: Files in .xls, .xlsx, or .csv format can be imported and exported.
ser
ver
s
inf
or
ma
tio
n

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 88

Da M Description
ta an
Ty dat
pe or
y
or
Op
tio
nal

Cu Op Function: The Custom Data Source provides cell information for PS Core
sto tio performance root cause analysis and enables the Nastar to display cell information
m nal for TopN cell and procedure delay analysis.
Da Acquisition means: Contact the onsite administrator. If you need to modify, set
ta it.
So
urc Data format: Files in .xlsx format can be imported.
e

2.5.2 Checking the Integrity of Configuration Data

In situations where the OSS and NE information is configured, the Nastar automatically collects
configuration data. You can check whether the configuration data has been collected and
imported to the database.

Prerequisites
l You have configured the OSS information through the OSS information management
function.
l You are authorized to query configuration data.

Context
The collecting and importing principles of the Nastar system are as follows:
l Collecting:
The Nastar automatically collects configuration data after the OSS and NE information
have been configured. By default, the start time for collecting configuration data is the start
time of the data collection service, and the period is 6 hour. For example, the start time of
the data collection service is 6:00, so the next execution time is 12:00. The start time of the
data collection service is the same as the start time of the system service.
After clicking Immediately Collect Configuration Data on the RAN NE List tab page
of OSS information management function, the system will immediately collects
configuration data in the OSS instead of collecting the data until the default time. If the
system is executing another collection task, the task that you trigger manually will be
automatically executed after the running task is complete.
l Importing: When detecting the configuration data, the system will import it to the database
automatically.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 89

Procedure
Step 1 Choose Maintenance > Data Maintenance Management. The Data Maintenance
Management window is displayed.
Step 2 In the Data Maintenance Management window, set Data Type > System Type > ***
Configuration Data on the left navigation tree.
Step 3 Set Select Condition on the Query Data tab page.
1. Set Query type.
You can query the configuration data of day-level.
2. Set a time segment only after you select Is time limit required. If no time limit is required
for the query, you need not set this parameter.
3. Select the NE object to be queried in the NE object navigation tree.
Step 4 Click Query.
In the right pane, check whether the configuration data has been imported into the Nastar
database.
l In the result list, NEs with data are listed as well as the start time and end time. The start time
and end time indicate when services are performed, not the time when the configuration data
is imported.
l On the NE Name tab page, day-level detailed data about each NE with data is displayed on
a separate tab page.
On the tab page, green grids indicate that data is available, and white grids indicate that data
is not available.
If you fail to query configuration data provided that the OSS is configured and the configuration
result is normal, contact Huawei technical support engineers.

----End

Follow-up Procedure
You can right-click in the right pane and choose Save As from the shortcut menu to save the
current query results as a .csv, .xls, or .xlsx file.

2.5.3 Preparing Engineering Parameters

This section describes how to obtain the engineering parameter file, and import it to the database.
After importing, you are advised to check whether the existing engineering parameter data is
consistent with the configuration data.

Importing Engineering Parameters

This section describes how to import engineering parameters. You can import engineering
parameters into the Nastar database to provide a reference for certain algorithms related to
performance analysis.

Prerequisites
You have obtained the engineering parameter file, and the file format and engineering parameter
fields contained in the file meet the Nastar requirement.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 90

Context
l The engineering parameter template files in .csv, .xls, and .xlsx formats can be imported.
Nastar imports and exports .csv files most efficiently. You are advised to use engineering
parameter files in .csv format.
NOTE
If an .xls engineering parameter file contains more than 27,000 records, this file cannot be imported.
Therefore, you are advised to convert an .xls file to the .csv format before importing it.
l The system supports a maximum number of cells contained in the engineering parameter
file as follows:
– 60,000 (the Nastar hardware configuration is matched with the 400 equal NEs network
size.)
– 120,000 (the Nastar hardware configuration is matched with the 800 equal NEs network
size.)
l When engineering parameters of NEs that are not accessed by the Nastar system are
imported in the engineering parameter window, only user admin has the rights to view and
operate engineering parameters of all RATs, whereas other users has only the rights to view
and operate GSM engineering parameters.
l The requirement of the engineering parameter file is referred to Appendix: Engineering
Parameter Templates.

Procedure
Step 1 Double-click System Function > Engineering Parameter Management from the navigation
tree in the Analysis Task Management window.
NOTE

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

Step 2 In the Engineering Parameter Management window, click the *** engineering
parameters tab and then click Import.
In the name of the tab, *** refers to the network system such as GSM, UMTS, or LTE.

Step 3 In the displayed Open dialog box, select an engineering parameter file, and then click Open.
If an engineering parameter file in .xls or .xlsx format is selected and the file contains multiple
sheets, the system displays a message, prompting you to select the sheet to be imported.

Step 4 Configure the column headers.

l At the header of each column, right-click and choose the title of the current column.
When you move the pointer to the column header of a column, a pop-up message is displayed,
showing the information about this column, for example, Column No./Configured column
title/Column title in the engineering parameter file.
l Right-click the header of a column and view the field configuration information in the
shortcut menu.
The column headers marked with the * character must be configured. Otherwise, the import
operation is not allowed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 91

l If you need to modify an incorrectly configured column header, right-click the column
header, clear the check box next to the original header, and then reconfigure the header.
l The engineering parameters must meet the following restrictions in different network
systems. For details, see Table 2-16. Otherwise, the engineering parameter file cannot be
imported into the database.
For details of the mandatory parameters and the range, see Appendix: Engineering
Parameter Templates.

Table 2-16 Restrictions on engineering parameters

Network System Restriction

GSM l The mandatory parameters must be configured, and the

values of the mandatory parameters must not be empty.
l The values of the parameters must be in the specified
range.
l The value of MCC+MNC+LAC+CI of a cell must be
unique.

UMTS l The mandatory parameters must be configured, and the

values of the mandatory parameters must not be empty.
l The values of the parameters must be in the specified
range.
l The value of RNC ID+CELL ID of a cell must be unique.

LTE l The mandatory parameters must be configured, and the

values of the mandatory parameters must not be empty.
l The values of the parameters must be in the specified
range.
l The value of eNodeB ID+CELL ID of a cell must be
unique.

Step 5 Click OK.

Step 6 In the OK dialog box, check the number of added records, updated records, and failed records.
Then, click OK.
NOTE

l You can learn the synchronization status by viewing the progress bar. If the progress bar is green, the
synchronization is successful. If the progress bar is red, the synchronization fails.
l During engineering parameter import, the Nastar checks the synchronization status of all NEs. If
synchronization fails for an NE, the Nastar displays that the synchronization fails. In such case, if you
want to query whether synchronization succeeds for the current NE, perform Step 8.

Step 7 Perform the operations as prompted.

If... Then...

The imported engineering parameter data is Click Close.

correct

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 92

If... Then...

The imported engineering parameter data is The data that fails to be imported is
abnormal. highlighted in red. In this case, perform either
of the following operations:
l Click Export Failed Records.
The system exports the error records to a
file. You can modify error data and then
complete the import operation.
l Click Close to complete the import
operation.

Step 8 View the synchronization status of the SAU to check whether the engineering parameters have
been synchronized to the SAU.

1. In the lower right area, click Close to return to the Engineering Parameters
Management window.
2. Click View Dispatching Status.

NOTE
On an LTE network, after LTE engineering parameters are imported, the system delivers the LTE
engineering parameters to all SAUs mounted on the LTE network.

----End

Follow-up Procedure
l Exporting engineering parameters.
After engineering parameter data is imported, you can export all engineering parameter
data from the database and save the data as a .csv, .xls, or .xlsx file for easy query and
management. To export engineering parameter data, do as follows:

1. In the Engineering Parameter Management window, click the *** engineering

parameters tab and select the engineering parameters to be exported from the
engineering parameter list. Then click Export.
In the name of the tab, *** refers to the network system such as GSM, UMTS, or LTE.
2. Set a file name and specify the save path and file type in the displayed Save dialog
box, and then click Save.
l Deleting engineering parameters
. Select the engineering parameters to be deleted from the engineering parameter list, and
then click Delete.

Checking Engineering Parameters and Configuration Data

This section describes how to check engineering parameters and configuration data. Through
this function, you can check whether the existing engineering parameter data is consistent with
the configuration data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 93

Prerequisites
l Configuration data is imported. For details, see 2.5.2 Checking the Integrity of
Configuration Data.
l Engineering parameter data is imported. For details, see Importing Engineering
Parameters.

Procedure
Step 1 Double-click System Function > Engineering Parameter Management from the navigation
tree in the Analysis Task Management window.
NOTE

Step 2 In the Engineering parameter management window, click the *** engineering
parameters tab.
In the name of the tab page, *** indicates the network system such as GSM, UMTS, or LTE.

Step 3 Check engineering parameters.

1. Click Check Configuration. The Nastar displays the check results.
NOTE
If you delete an NE in the OSS Information Management window, the configuration data of deleted
NE is save for a time period based on the time set in Storage Period. Therefore, if you immediately
check the consistency between engineering parameter data and configuration data, the check result
is different from the actual situation. When the save time of the configuration data reaches the
specified time, this phenomenon does not occurs.
l Number of cells with configuration and engineering parameters: indicates the number
of cells that are configured with both engineering parameters and configuration data.
l Number of cells with configuration but without engineering parameters: indicates the
number of cells that are configured with configuration data but are not configured with
engineering parameters.
l Number of cells with engineering parameters but without configuration: indicates the
number of cells that are configured with engineering parameters but are not configured
with configuration data.
l Number of external cells with configuration but without engineering parameter:
indicates the number of external neighboring cells that are configured with configuration
data but are not configured with engineering parameters.
2. Click Export Checking Results.
3. Select the saving path, saving name, and saving format of the check results in the Save
dialog box.

The check results in .csv, .xls, or .xlsx format can be exported.

Check results are saved in a folder, the folder includes the following files:
l Engineering Parameters and Configuration Shared: This sheet records the information
about cells that are configured with both engineering parameters and configuration data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 94

l Proprietary Engineering Parameter: This sheet records the information of cells that are
configured with only engineering parameters.
l Proprietary Configuration: This sheet records the information of cells that are
configured with only configuration data.
l External Neighboring Cell with No engineering parameter: This sheet records the
information of external neighboring cells that are configured with only configuration
data.

Step 4 Optional: Click Update from Configuration to synchronize engineering parameter data with
configuration data.
After engineering parameter data is imported into the database, the Nastar updates some
engineering parameters based on the latest configuration data according to some fields.

Table 2-17 describes the parameters are updated.

Table 2-17 Update description between configuration data and engineering parameters

Network Fields Parameters to be updated

GSM CGI (MNC + MCC + LAC + CI) BCC, NCC, BCCH, CELLNAME,
and TCH.

UMTS RNCID + CELLID CELLNAME, PSC, and

UARFCNDOWNLINK.

LTE ENODEBID + CELLID CELLNAME,

UARFCNDOWNLINK, and
PHYCELLID.

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

----End

Appendix: Engineering Parameter Templates

Only the engineering parameter files that meet template requirements can be imported into the
Nastar database. The section describes the parameters and templates of Nastar engineering
parameters on the GSM, UMTS, and LTE networks.

l For details about GSM engineering parameters, see GSM Engineering Parameters.
l For details about UMTS engineering parameters, see UMTS Engineering Parameters.
l For details about LTE engineering parameters, see LTE Engineering Parameters.

GSM Engineering Parameters

Table 2-18 describes GSM engineering parameters supported by the Nastar.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 95

Table 2-18 GSM engineering parameters

Parameter Description Value Range Optional/

Mandatory

BSCName Indicates the name of a l String Mandatory

BSC. l Value range:
[0,64]

SiteName Indicates the name of a l String Optional

site. l Value range:
[0,64]

CellName Indicates the name of a l String Mandatory

cell. l Value range:
[0,64]

MCC Indicates the mobile l Integer Mandatory

country code. l Value range:
[000,999]

MNC Indicates the mobile l Integer Mandatory

network code. l Value range:
[000,999]

LAC Indicates the location l Integer Mandatory

area code of a cell. l Value range:
[0,65535]

CI Indicates the cell identity. l Integer Mandatory

l Value range:
[0,65535]

BCCH Indicates the broadcast l Integer Mandatory

control channel. l Value range:
[0,1024]

BCC Indicates the base station l Integer Mandatory

color code. l Value range: [0,7]

NCC Indicates the network l Integer Mandatory

color code. l Value range: [0,7]

Longitude Indicates the longitude Value range: Mandatory

where a cell is located. [-180.000000,180.00
0000]

Latitude Indicates the latitude Value range: Mandatory

where a cell is located. [-90.000000,90.0000
00]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 96

Parameter Description Value Range Optional/

Mandatory

Azimuth Indicates the azimuth of Value range: Mandatory

an antenna. [0.00,360.00]

Outdoor Indicates whether a cell is l No: indoor cell Optional

an outdoor cell. l Yes: outdoor cell NOTE
l It is mandatory for
the network
geographic
observation
function.
l When preparing an
engineering
parameter template,
comply with the
following rules.
Otherwise, the
check will fail
during the import of
engineering
parameter
templates.
If this parameter is
not used, delete this
column.
If this parameter is
used, ensure that the
values in this
column are not
empty.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 97

Parameter Description Value Range Optional/

Mandatory

Sectorization Indicates whether a cell is l Omni: Optional

a directional cell. omnidirectional NOTE
cell l It is mandatory for
l Sectorize: the network
directional cell geographic
observation
function.
l When preparing an
engineering
parameter template,
comply with the
following rules.
Otherwise, the
check will fail
during the import of
engineering
parameter
templates.
If this parameter is
not used, delete this
column.
If this parameter is
used, ensure that the
values in this
column are not
empty.

TCH Indicates the traffic l Value range: Optional

channel. [0,255]
l TCH ARFCNs
must be separated
by semicolon.

AntHeight Indicates the antenna l Integer Optional

height. l Value range:
[0,65535]

MechTilt Indicates the antenna l Integer Optional

mechanical tilt. l Value range:
[-90.0,90.0]

ElecTilt Indicates the antenna l Integer Optional

electrical tilt. l Value range:
[-90.0,90.0]

AntVendor Indicates the antenna l String Optional

vendor. l Value range:
[0,32]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 98

Parameter Description Value Range Optional/

Mandatory

AntType Indicates the antenna l String Optional

type. l Value range:
[0,32]

SiteType Indicates the site type. l String Optional

l Value range:
[0,32]

PrimaryAnt Indicates whether an l No: diversity Optional

antenna is the main antenna
antenna. l Yes: main antenna
NOTE
l If a cell has only one
engineering parameter
record and the
parameter value is
empty or NO, the
system sets the
parameter value to
YES by default.
l If a cell has multiple
engineering parameter
records and the
parameters value are
empty or NO, the
system determines that
the first record is
related to the main
antenna and sets the
parameter value to
YES by default.

Template: GSM Engineering Parameters Template

UMTS Engineering Parameters

Table 2-19 describes UMTS engineering parameters supported by the Nastar.

Table 2-19 UMTS engineering parameters

Parameter Description Value Range Optional/

Mandatory

RNCID Indicates the ID of an RNC. l Integer Mandatory

l Value range:
[0,65535]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 99

Parameter Description Value Range Optional/

Mandatory

NodeBID Indicates the ID of a NodeB. l Integer Mandatory

l Value range:
[0,65535]

NodeBName Indicates the name of a l String Mandatory

NodeB. l Value range:
[0,64]

CellID Indicates the ID of a cell. l Integer Mandatory

l Value range:
[0,65535]

CellName Indicates the name of a cell. l String Mandatory

l Value range:
[0,64]

LAC Indicates the location area l Integer Optional

code of a cell. l Value range:
[0,65535]

RAC Indicates the routing area code l Integer Optional

of a cell. l Value range:
[0,65535]

UARFCNDo Indicates the downlink l Integer Mandatory

wnlink UARFCN of a cell. l Value range:
[0,65535]

UARFCNUpl Indicates the uplink UARFCN l Integer Optional

ink of a cell. l Value range:
[0,65535]

PSC Indicates the primary l Integer Mandatory

scrambling code of a cell. l Value range:
[0,511]

Longitude Indicates the longitude where Value range: Mandatory

a cell is located. [-180.000000,180.0
00000]

Latitude Indicates the latitude where a Value range: Mandatory

cell is located. [-90.000000,90.000
000]

Azimuth Indicates the azimuth of an Value range: Mandatory

antenna. [0,360]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 100

Parameter Description Value Range Optional/

Mandatory

Outdoor Indicates whether a cell is an l No: indoor cell Optional

outdoor cell. l Yes: outdoor NOTE
cell l It is mandatory
for the network
geographic
observation
function.
l When preparing
an engineering
parameter
template, comply
with the
following rules.
Otherwise, the
check will fail
during the import
of engineering
parameter
templates.
If this parameter
is not used, delete
this column.
If this parameter
is used, ensure
that the values in
this column are
not empty.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 101

Parameter Description Value Range Optional/

Mandatory

Sectorization Indicates whether a cell is a l Omni: Optional

directional cell. omnidirectional NOTE
cell l It is mandatory
l Sectorize: for the network
directional cell geographic
observation
function.
l When preparing
an engineering
parameter
template, comply
with the
following rules.
Otherwise, the
check will fail
during the import
of engineering
parameter
templates.
If this parameter
is not used, delete
this column.
If this parameter
is used, ensure
that the values in
this column are
not empty.

SAC Indicates the service area code l Integer Optional

of a cell. l Value range:
[0,65535]

AntHeight Indicates the antenna height. l Integer Optional

l Value range:
[0,65535]

MechTilt Indicates the antenna l Integer Optional

mechanical tilt. l Value range:
[-90.0,90.0]

ElecTilt Indicates the antenna l Integer Optional

electrical tilt. l Value range:
[-90.0,90.0]

AntType Indicates the antenna type. l String Optional

l Value range:
[0,32]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 102

Parameter Description Value Range Optional/

Mandatory

AntVendor Indicates the antenna vendor. l String Optional

l Value range:
[0,32]

SiteType Indicates the site type. l String Optional

l Value range:
[0,32]

Template: UMTS Engineering Parameters Template

LTE Engineering Parameters

Table 2-20 describes LTE engineering parameters supported by the Nastar.

Table 2-20 LTE engineering parameters

Parameter Description Value Range Optional/

Mandatory

eNodeBName Indicates the name of an l String Mandatory

eNodeB. l Value range:
[0,64]

SiteName Indicates the name of a site. l String Optional

l Value range:
[0,64]

CellName Indicates the name of a cell. l String Mandatory

l Value range:
[0,64]

eNodeBID Indicates the ID of an l Integer Mandatory

eNodeB. l Value range:
[0,1048575]

SectorID Indicates the ID of a sector. l Integer Optional

l Value range:
[0,16]

LocalCellID Indicates the ID of a local cell. l Integer Optional

l Value range:
[0,32]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 103

Parameter Description Value Range Optional/

Mandatory

CellID Indicates the ID of a cell. l Integer Mandatory

l Value range:
[0,65535]

PhyCellID Indicates the ID of a physical l Integer Mandatory

cell. l Value range:
[0,503]

TAC Indicates the tracking area l Integer Optional

code of a cell. l Value range:
[0,65535]

Longitude Indicates the longitude where Value range: Mandatory

a cell is located. [-180.000000,180.0
00000]

Latitude Indicates the latitude where a Value range: Mandatory

cell is located. [-90.000000,90.000
000]

Azimuth Indicates the azimuth of an Value range: Mandatory

antenna. [0,360]

AntHeight Indicates the antenna height. l Integer Optional

l Value range:
[0,65535]

MechTilt Indicates the antenna l Integer Optional

mechanical tilt. l Value range:
[-90.0,90.0]

ElecTilt Indicates the antenna l Integer Optional

electrical tilt. l Value range:
[-90.0,90.0]

AntVendor Indicates the antenna vendor. l String Optional

l Value range:
[0,32]

AntType Indicates the antenna type. l String Optional

l Value range:
[0,32]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 104

Parameter Description Value Range Optional/

Mandatory

Outdoor Indicates whether a cell is an l No: indoor cell Optional

outdoor cell. l Yes: outdoor cell NOTE
l It is mandatory
for the network
geographic
observation
function.
l When preparing
an engineering
parameter
template,
comply with the
following rules.
Otherwise, the
check will fail
during the import
of engineering
parameter
templates.
If this parameter
is not used,
delete this
column.
If this parameter
is used, ensure
that the values in
this column are
not empty.

ULEARFCN Indicates the uplink ARFCN l Integer Optional

of the UTRAN. l Value range:
[0,65535]

DLEARFCN Indicates the downlink l Integer Mandatory

ARFCN of the UTRAN. l Value range:
[0,65535]

OnAir Indicates whether a cell is l String Optional

enabled. l Value range:
YES, NO.

SiteType Indicates the site type. l String Optional

l Value range:
[0,32]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 105

Parameter Description Value Range Optional/

Mandatory

Sectorization Indicates whether a cell is a l Omni: Optional

directional cell. omnidirectional NOTE
cell l It is mandatory
l Sectorize: for the network
directional cell geographic
observation
function.
l When preparing
an engineering
parameter
template,
comply with the
following rules.
Otherwise, the
check will fail
during the import
of engineering
parameter
templates.
If this parameter
is not used,
delete this
column.
If this parameter
is used, ensure
that the values in
this column are
not empty.

Template: LTE Engineering Parameters Template

2.5.4 Preparing the Map File (Optional)

On Nastar, you can import a digital map as a WOR, TAB, or SXWU file directly to view analysis
results or view analysis results by using Google Earth.

Context
Nastar provides two modes for viewing analysis results on a map, as shown in Figure 2-13.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 106

Figure 2-13 Displaying analysis results on a map

Connecting to Google Earth

This section describes how to view analysis results by using the Google Earth. The Nastar can
quickly display BTS and performance analysis results (for example, VIP analysis results) on the
Google Earth. The three-dimensional map enables you to easily view the network performance
analysis results and reduces the workload of field survey.

Prerequisites
l The PC is connected to the Internet.
l The Google Earth is installed in the PC.

Context
The principles for displaying the Nastar data on the Google Earth are as follows:
l After the engineering parameters are read, the geographic data is displayed on the scale of
2,600 meters at heights and with the last cell in the engineering parameter list being in the
center by default.
l 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.
NOTE

The description of operations related to the Google Earth is not provided in this document.

Procedure
Step 1 Choose Tools > Google Earth. 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.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 107

If... Then...

The EarthViewWindow window displays sites It indicates that the system succeeds in
and cells, and the specified area is located. automatically reading the Nastar
engineering parameters.

The EarthViewWindow window displays the It indicates that the system fails to
home page of the Google Earth 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 Tools > Google Earth again.

Step 2 Enable the Google Earth to display the Nastar data synchronously.
After you click a cell in the analysis results, the Google Earth regards the selected cell as a center,
and then displays the geographic data on the scale of 2,600 meters at heights.
Step 3 View the cell information.
After you click a cell, the Google Earth displays the engineering parameter information about
the cell in a message box.
You can click the cell again to cancel the display of the message box.

----End

Converting the Map File Format

This section describes how to convert WOR or TAB map files to SXWU map files to improve
the efficiency of importing map files.

Prerequisites
A map file in .wor or .tab format is available on the PC.
NOTE

l Before importing a TAB map file, you must verify that a DAT or DBF file that has the same file name as
the TAB map file exists in the directory for saving map files. If such file does not exist, converting file
format fails.
l Before importing a WOR map file, you must verify that the TAB map files that form the WOR map file
exist in the directory for saving map files. If such files do not exist, converting file format fails.

Context
It takes a long time to import a WOR or TAB map file. If users on multiple clients attempt to
import the same map file, the work efficiency is low.
To solve this problem, the Nastar allows users to convert a WOR or TAB map file to an SXWU
map file and import the file because the Nastar can quickly identify and import SXWU map files
and allows multiple users to share the SXWU map files. This greatly improves the efficiency of
importing map files. It is recommended that the map files be converted by one person, and then
be shared to others.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 108

Procedure
Step 1 Choose Tools > Convert Map on the menu bar.

Step 2 In the displayed Parameter Config dialog box, set the conversion parameters.
l Maps Path: selects a WOR or TAB map file.
l Save Path: sets the save path after format conversion.
l Save Name: sets the file name after format conversion.

Step 3 Click OK.

The Nastar starts importing the map file. If the size of the map file is large, the format conversion
speed is low.

The file after format conversion is saved in a folder, which contains multiple files. In the folder,
the File Name.sxwu file is used to import map data.

----End

Importing Map Files

This section describes how to import WOR, TAB, or SXWU map files to help you view
performance analysis results directly on maps.

Prerequisites
A WOR, TAB, or SXWU map file is available on the PC.
NOTE

Context

NOTICE
l When performing operations in the GIS window, you are advised not to import or load map
files repeatedly. This is to prevent any unknown impact.
l If you import WOR or TAB map files whose total size exceeds 200 MB, the import speed is
low and the system running speed is decreased after the import because the map files contain
a large amount of vector information. You are advised to import only several key TAB map
files required for service analysis. Alternatively, you can convert WOR or TAB map files
into SXWU map files before you import the files, thereby improving the import speed. For
details, see Converting the Map File Format.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 109

Procedure

Step 1 Click on the toolbar. The Geographic Observation window is displayed.

Step 2 Click on the toolbar. The Open the map dialog box is displayed.
Step 3 Select a wor, tab, or sxwu map file.
Step 4 Click Open.

----End

2.5.5 Managing NE Groups

This section describes how to group NEs into an NE group, and provides guidance for you to
directly select an NE group and perform performance analysis after creating an analysis task.

Prerequisites
You have configured the information about the OSS and NEs. For detailed operations, see 2.3
Configuring OSS and NE Information.

Context
l The system supports a maximum of 100 NE groups.
l You can create an NE group by using one of the following methods:
– Creating an NE group by directly selecting NEs.
– Creating an NE group by importing an NE group file. The Nastar allows you to import
and export NE group files in .csv, .xls, and .xlsx formats.
According to the different network, the fields must be contained in the NE group files
is different.
An NE group file of the GSM network to be imported must contain the following fields:
NE Group Name, BSC Name, Cell Name, LAC, CI, Creator, Creation Time, and
Note, as shown in Table 2-21. The sequence for matching each column must be the
same as that in the following example.

Table 2-21 Examples of NE group files

NE BSC Cell LAC CI Creator Creatio Note

Grou Nam Nam n Time
p e e
Nam
e

Group A a 12121 21212 C 2014010 NA

1 1

Group B b 21212 12121 D 2014010 NA

2 1

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 110

An NE group file of the UMTS network to be imported must contain the following
fields: NE Group Name, RNC Name, Cell Name, LAC, SAC, Creator, Creation
Time, and Note.
An NE group file of the LTE network to be imported must contain the following fields:
NE Group Name, Cell ID, Cell Name, eNodeB ID, eNodeB Name, Creator,
Creation Time and Note.
– Creating an NE group by marking an area on the map. Mark an area on the map, and
group the NEs within the area into an NE group.
Before using this function, you must ensure that you have imported the engineering
parameters and the configuration data, and that the site names and cell names in the
engineering parameters are the same as those in the configuration data.

Procedure
l Creating an NE group by directly selecting NEs.
1. In the navigation tree of the Analysis Task Management window, double-click the
System Function > NE Group Management node. The NE Group Management
window is displayed.
NOTE

You can also click System Function > NE Group Management and then right-click Open
to open the NE Group Management window.
2. Select the *** NE Group tab, and click New. The New NE Group dialog box is
displayed.
In the name of the *** NE Group tab, *** indicates a network system such as GSM,
UMTS, LTE FDD, and LTE TDD.
3. Set relevant parameters.
– The Nastar supports the function of searching for objects in the object navigation
tree. You can click anywhere in the navigation tree and then press Ctrl+F to search
for and locate objects.
– Table 2-22 describes the parameter settings.

Table 2-22 Description of NE group parameters

Parameter Description

Group Name Name of an NE group, for example, Cell_1.

Value range:
l A maximum of 128 characters
l Characters not allowed: ` ~ ! @ # $ % ^ & * ( ) + { }
[]\/|;':,.?<>"
l This parameter must be unique and cannot be null.
l This parameter is case sensitive.

Element List Select required NEs.

Note Description of an NE group.

Value range:A maximum of 250 characters.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 111

4. Click OK.
l Creating an NE group by importing an NE group file.
1. Select the *** NE Group tab, and click Import.
In the name of the *** NE Group tab, *** indicates a network system such as GSM,
UMTS, LTE FDD and LTE TDD.
2. In the displayed Open dialog box, select a complete NE group file, and click Open.
If an .xls or .xlsx NE group file is selected and the file contains multiple worksheets,
the system displays information providing guidance for you to select the worksheet
to be imported.
NOTE

In the complete NE group file, if multiple lines of inconsistent remarks exist in an NE group,
the system displays the last line of remarks under Note in the NE Group Management window.
You are advised to keep the remarks in each line for an NE group consistent when defining
information for this NE group.
3. The Import NE Group dialog box displays the NE group file to be imported. Click
Import.

For some networks, you can select the matching type between the parameters of the
NE group file and the configuration data. For example, in the GSM network, you can
select Match LAC and CI or Match Cell Name to import the NE group file on the
Import button area.

The Message window displays the number of NE groups that have been successfully
imported and the number of NE groups that fail to be imported.
4. Click OK.
l Creating an NE group by marking an area on the map.
Before using this function, you must ensure that you have imported the engineering
parameters and the configuration data, and that the site names and cell names in the
engineering parameters are the same as those in the configuration data.

No. Procedure Step

1 Opening
On the toolbar of the main window, click . The Geographic
the map
Observation window is displayed.
window

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 112

No. Procedure Step

2 Drawing a
1. Click on the toolbar.
polygon to
define the 2. Add points to the polygon one by one in the Geographic
area to be Observation window.
filtered NOTE
l The maximum number of grids within a polygon area is 1000. If
the number of grids exceeds the threshold, draw the polygon area
again.
l The lines of a polygon must not intersect. Otherwise, certain
selected areas may be missed out.
l Draw a polygon area with an appropriate size as required. If you
select a large area with many grids, a long wait time is required.
3. After the last point is added, double-click or right-click in the
window to exit the polygon drawing. In addition, the Label
dialog box is displayed.
4. Set the name of the polygon.
5. Click OK. The polygon drawing is complete.
The Geographic Observation window displays the polygon
and its name. In addition, the polygon name is added to the
Polygon Areas node in the navigation tree in the left pane.

3 Setting
1. Click on the toolbar. The Search dialog box is displayed.
filtering
criteria to 2. Select a RAT in Network Technology.
filter the 3. Select the area you want to filter in Region.
cells in the 4. Set engineering parameters in the lower left corner of the dialog
defined box.
area and The Nastar supports filtering of all engineering parameters.
with the Generally, you can set one or two parameters as the filter
specified criteria. The logical operator between the two parameters can
network be set to And or Or.
system and
engineerin
g parameter
fields

4 Saving the 1. Click Save As NE Group. The Save As NE group dialog box
filtered is displayed.
cells as an 2. Set NE Group Name and add remarks.
NE group
3. Click OK.
Cells selected in the Search Result area are saved as an NE
group. You can double-click System Function > NE Group
Management in the Analysis Task Management window and
then view information about the NE group in the displayed
window.

----End

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 113

Follow-up Procedure
In the NE Group Management window, select the *** NE Group tab, and then select an NE
group to view, modify, delete, or export this NE group.
In the name of the *** NE Group tab, *** indicates a network system such as GSM, UMTS,
and LTE.

If... Then...

You need to view and modify 1. Click Modify/View.

the property of an NE group 2. View the information about the NEs of the NE group.
If you need to modify certain parameters, perform 3
through 4.
3. Reset certain parameters.
You are allowed to modify the NE information and the
remarks but not the NE group name.
For details about the parameters, see Table 2-22.
4. Click OK.
NOTE
l If the NE group is being used by another ongoing task, the current
modification does not affect this ongoing task. If the NE group is
being used by another periodic task, the modified information will
be updated in the next task period.
l You can double-click an NE group record to view the attributes
of this NE group.
l If you need to modify the NE group information in batches, you
can export the original NE group information, make
modifications, and then import the modified NE group
information.

You need to delete an NE 1. Click Delete.

group 2. In the displayed dialog box, click Yes.
NOTE
l If the NE group is being used by another ongoing task, the
current modification does not affect this ongoing task. If the
NE group is being used by another periodic task, the modified
information will be updated in the next task period.
l When the NE group deletion operations are performed on
multiple clients, the Nastar server responds to the client where
the NE group deletion is first performed. The NE group
deletion operations for other clients are performed in
sequence after the message indicating an ongoing deletion in
the lower right corner disappears.

You need to export an NE 1. Click Export.

Group 2. In the displayed Save dialog box, set the name, type, and
save path of the NE group file to be exported, and click
Save.
The system then exports all the NE group information on
this tab page.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 114

2.5.6 Managing VIP Groups or VIP Users (VIP Analysis)

This section describes how to group multiple VIP users into a VIP group for guarantee
management. You need to create VIP users and VIP groups before subscribing to VIP analysis
data.

Basics of VIP Group and VIP User

This section describes the relationship between VIP groups and VIP users, and the technical s

Relationship
Figure 2-14 shows the relationship between VIP groups and VIP users.

Figure 2-14 Relationship between VIP groups and VIP users

The description is as follows:

l VIP users is the basic object for the Nastar user analysis. VIP users fall into two classes:
important and common. Multiple VIP users can be contained to a VIP group for batch
analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 115

l A VIP group can be configured with multiple VIP users. A VIP user can be configured in
multiple VIP groups.
l When adding users to a VIP group, you can add existing VIP users in batches. If the existing
VIP users cannot meet requirements, create VIP users.
l When setting the homing VIP group of a VIP user, you can set the homing VIP group of
the VIP user to an existing VIP group. If the existing VIP groups cannot meet requirements,
create a VIP group.

Technical Specifications
Table 2-23 describes the technical specifications of the VIP group and the VIP user.

Table 2-23 Technical specifications for VIP group management 1

Item Task Management Capacity

Number of allowed VIP <= 1,000

groups

Number of allowed VIP <= 30,000

subscribers where the number of important VIP subscribers is less than or
equal to 500.

Number of VIP groups to <= 30

which one VIP subscriber
can belong

NOTE

VIP subscribers move across networks of different types. Therefore, the technical specifications for VIP
management have nothing to do with network types. No matter how many types of networks there are, the
Nastar supports a maximum of 30,000 VIP subscribers and a maximum of 1,000 VIP groups.

The number of important VIP subscribers that support signaling tracing analysis on the radio
access network (RAN) side depends on the capability of the NE. Therefore, the value of
supported numbers varies with NE version. For details, see Table 2-24.

Table 2-24 Technical specifications for VIP group management 2

Network Earliest NE Version Number of Important VIP Subscribers

Type Supported That Support Signaling Tracing Analysis

GSM l CS domain: GBSS11.0 <= 500/BSC

(BSC6900
V900R011C00)
l PS domain: GBSS14.0
(BSC6900
V900R014C00)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 116

Network Earliest NE Version Number of Important VIP Subscribers

Type Supported That Support Signaling Tracing Analysis

UMTS RAN13.0 (BSC6900 <= 100/RNC

V900R013C00)

RAN16.0 (BSC6900 <= 500/RNC

V900R016C00)

LTE eRAN6.0 (LTE3900 <= 500/HSS

V100R008C00)

Multi-RAT - <= 500/NE

networks

Managing VIP Groups

This section describes how to group multiple VIP users into a VIP group for guarantee
management. You need to create VIP groups and then add VIP users to the VIP groups. A VIP
group contains at least one VIP user.

Prerequisites
l You are authorized to manage VIP groups.
l You have obtained VIP user information, including the MS number, IMSI, and user class.

Context
You can create a VIP group using either of the following methods:
l Create a VIP group directly
l Create a VIP group by importing a file. The Nastar allows you to import and export VIP
group files in CSV, XLS, or XLSX format.
The VIP group file to be imported must include the following fields as shown in Table
2-25. The column sequence must be the same as that in the following example, which is
the same as that on the Nastar.

Table 2-25 Sample VIP group file

No. Group Name Number of Description

Members

1 Group 1 50 Secondary department

director of ** Group

2 Group 2 100 Project manager of ** Group

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 117

Procedure
Step 1 Double-click System Function > VIP Group Management in the navigation tree on the left
of the Analysis Task Management window.
NOTE

You can also choose System Function > VIP Group Management from the navigation tree in the Analysis
Task Management window and right-click Open. The VIP Group Management window is displayed.

Step 2 Click the VIP Group tab.

Step 3 Create a VIP group.

If you need to... Then...

Create a VIP group directly 1. Click New. The Create VIP Group dialog box
is displayed.
2. Set Group Name and Description.
If the asterisk (*) is present on the right of a
parameter, the setting of this parameter is
mandatory.
3. Click OK.
The new VIP group is displayed on the VIP
Group tab page.

Create VIP groups by importing a file 1. Click Import. The Open dialog box is
displayed.
2. Select a VIP group file.
The Nastar allows you to import and export VIP
group files in CSV, XLS, or XLSX format. For
details about the requirements of a VIP group
file, see Table 2-25.
3. Click Open.
If a selected XLS or XLSX file contains multiple
sheets, the system displays information
prompting you to select the sheet to be imported.
The imported VIP groups are displayed on the
VIP Group tab page.

Step 4 Add VIP users to VIP groups.

1. On the VIP Group tab page, select a VIP group, and click Modify/View.
2. Click Select in Members.
3. Select one or multiple VIP users from the existing VIP user list, and click OK.
If the required VIP user is unavailable in the existing VIP user list, click New or Import
to create a VIP user. For detailed parameter descriptions, see Managing VIP
Subscribers.
4. Click OK.

----End

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 118

Follow-up Procedure
On the VIP Group tab page, select a VIP group, and then perform operations as required.
NOTE

If the VIP group is used by other tasks, the modification does not affect the ongoing tasks. If the VIP group
is used by a periodic task, the related information is updated in the next period after the modification.

If you need to... Then...

Search VIP groups On the VIP Group tab page, right-click the VIP group
list and choose Search from the shortcut menu. Enter
a keyword to quickly locate a VIP group.

Modify a VIP group Click Modify/View. In the displayed Modify/View

VIP Group dialog box, change the values of VIP group
parameters.
The VIP group name cannot be changed. You can
change the values of Members and Description.
Change the value of Members.
l Click Select to add an existing VIP user to the VIP
group.
l Click New to create a VIP user and then add it to
the VIP group.
l Click Delete to delete a VIP user that has been
added to the VIP group.
NOTICE
l Issue the subscription task again after the VIP group is
updated so that the VIP subscription function is not
affected.
l If an existing VIP user not involved in data subscription
is added to a VIP group for which data subscription has
been performed, a message will be displayed indicating
that you need to perform the subscription again.
l If you attempt to delete a VIP user from a VIP group
involved in data subscription, a message will be displayed
indicating that you have to cancel the subscription before
the deletion.
l A VIP user can be analyzed only after the VIP user is
grouped into VIP groups. Therefore, if the VIP user you
want to delete belongs only to the current VIP group, you
will not be allowed to delete the VIP user.

Export a VIP group Click Export.

Delete a VIP group Click Delete.

NOTE
l A VIP group in use cannot be deleted.
l If a VIP user belongs only to the current VIP group, the
Nastar will also delete the VIP user information when
deleting the VIP group.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 119

If you need to... Then...

View a VIP group Double-click a VIP group to view the detailed

information.

Save a VIP group On the VIP Group tab page, right-click the VIP group
list, and choose Save As from the shortcut menu.

Managing VIP Subscribers

This section describes how to manage VIP subscribers by specifying VIP subscriber information
and grouping VIP subscribers into VIP groups. You need to create VIP subscribers and then add
them to VIP groups. A VIP subscriber must belong to at least one VIP group.

Prerequisites
l You are authorized to manage VIP groups. The entered subscriber information by using
the VIP subscriber management function contains real personal information, such as the
MSISDN and IMSI. Therefore, user rights of this function must be properly managed to
protect real subscriber information from being leaked.
l You have obtained VIP subscriber information, including the MSISDN, IMSI, and
subscriber class.
NOTE

The Nastar provides sufficient protection for service data used by this function, such as IMSI and
IMEI information, to ensure personal data security. For details about the service data and protection
policies, seeDescriptions > Nastar Security Description > Application Security > Protecting
Private Subscriber Data.
The Nastar provides an anonymization mechanism for processing personal data, such as the IMSI,
IMEI, MSISDN, and IMEISV. After this mechanism is used, the Nastar no longer allows you to enter
the plaintext IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain
the encrypted IMSI. The Nastar does not support the encrypted MSISDN. Telecom operators can
contact the Huawei technical support engineers to visit http://support.huawei.com and choose
Support > Software > Global Service > Managing Customer Experience Service-SmartCare >
Network Optimization Service > GENEX Mobile Manager > HMACUtil.
You have checked whether the subscriber identity anonymization switch or the encryption key is
changed. If the subscriber identity anonymization switch or the encryption key is changed, see 2.12.3
Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization
Switch or the Encryption Key.

Context
You can create a VIP subscriber using either of the following methods:
l Create a VIP subscriber directly.
l Create VIP subscribers by importing a file. The Nastar allows you to import and export
VIP subscriber files in CSV, XLS, or XLSX format.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 120

NOTE

.csv files can be opened by using Microsoft Excel or Notepad. If you use Microsoft Excel to view or
edit a .csv file, you need to preset cells in the file to the text format, thereby preventing information
in the IMSI column from being displayed as non-text characters. You are advised to use Notepad to
open a .csv file, which prevents the preceding problem occurring in files that are opened by using
Microsoft Excel.
The VIP subscriber file you want to import must include the following fields as shown in
Table 2-26. The column sequence must be the same as that in the following example, which
is the same as that on the Nastar.

Table 2-26 Sample VIP subscriber file

No. Alia Phone CC IMSI Class VIP Descri

s Numbe Group ption
r

1 a1 135 86 123*** Importan A,B User a

**** **124 t

2 b2 130 86 123*** Commo A User b

**** **125 n

3 c3 131 86 123*** Commo A,B,C User c

**** **126 n

Procedure
Step 1 Double-click System Function > VIP Group Management in the navigation tree on the left
side of the Analysis Task Management window.
NOTE

You can also choose System Function > VIP Group Management from the navigation tree in the Analysis
Task Management window and right-click Open. The VIP Group Management window is displayed.

Step 2 Click the VIP User tab.

Step 3 Create VIP subscribers and add them to VIP groups.

Class VIP subscribers fall into two classes:

l Important: important VIP subscribers, supporting all types of analysis
including aggregation analysis, in-depth record analysis, and all-
signaling analysis.
A maximum of 500 important subscribers are supported.
l Common: common VIP subscribers, supporting only aggregation
analysis and in-depth record analysis.
A maximum of 30,000 common subscribers are supported.
Function: The class is used to control the subscribers to view different types
of analysis results.

Description Descriptive information of a VIP subscriber.

Value range:The name contains a maximum of 250 characters.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 124

Parameter Description

VIP Group Click Select to choose one or more existing VIP group. Click OK.
If the required VIP group is unavailable in the existing VIP group list, click
New or Import to create a VIP group. For detailed parameter descriptions,
see Managing VIP Groups.
NOTE
One VIP subscriber can belong to a maximum of 30 VIP groups.

----End

Follow-up Procedure
On the VIP User tab page, select a VIP subscriber, and then perform operations as required.
NOTE

l If the VIP subscriber is used by other tasks, the modification does not affect the ongoing tasks. If the
VIP subscriber is used by a periodic task, the related information is updated in the next period after
the modification.
l If a newly created VIP subscriber is added to a VIP group for which data subscription has been
performed, a message will be displayed indicating that you need to perform the subscription again.

If you need to... Then...

Search for a VIP On the VIP User tab page, right-click the VIP subscriber list and
subscriber choose Search from the shortcut menu. Enter a keyword to quickly
find a VIP subscriber.

Modify a VIP 1. Select a VIP subscriber, and click Modify/View. The Modify/
subscriber View VIP User window is displayed.
2. Set one or multiple fields among User Name, Phone Number,
CC, Class, Description, and VIP Group.
NOTE
The IMSI of a VIP subscriber cannot be modified.
3. Click OK.

Add or delete the VIP 1. Click Modify/View.

group to which a VIP 2. In the Modify/View VIP User dialog box, click the buttons to
subscriber belongs add or delete the VIP group where a VIP subscriber belongs.

Import VIP Click Import.

subscribers If a selected XLS or XLSX file contains multiple sheets, the system
displays information prompting you to select the sheet to be
imported.

Export VIP Click Export.

subscribers The Nastar allows you to import and export VIP subscriber files in
CSV, XLS, or XLSX format.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 125

If you need to... Then...

Delete VIP 1. Select a VIP subscriber record or press Ctrl to select multiple
subscribers VIP subscriber records and click Delete.
2. In the displayed dialog box, click Yes.

Save VIP subscribers On the VIP User tab page, right-click the VIP subscriber list, and
choose Save As from the shortcut menu.

2.5.7 Managing Terminal Information (Terminal Analysis)

This section describes how to create terminal types to establish terminal management records
for terminal analysis in the future.

Prerequisites
l You are authorized to manage terminal information.
l You have obtained the terminal information.

Context
l The system supports a maximum number of terminal types: 100,000.
l You can create a terminal type using either of the following methods:
– Create a terminal type directly.
– Create a terminal type by importing a file. Terminal type files in .csv, .xls, and .xlsx
formats can be imported and exported.
NOTE

l You can open a file in .csv format by using Microsoft Excel or the notepad. If you use Microsoft
Excel to view or edit a file in .csv format, the international mobile equipment identity (IMEI)
might be displayed abnormally. If you use the notepad to view or edit a file in .csv format, however,
information in the file can be displayed normally. Therefore, you are advised to open a file in .csv
format by using the notepad.
l When you edit the records exported in a .csv file before importing the records into the terminal
type file, if the information in a table cell contains commas, add a pair of quotation marks (") to
include the information.
The terminal type file to be imported must include the following fields: IMEI-TAC,
Vendor, and Terminal Model. The sample of terminal type file is shown in Table
2-28.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 126

Table 2-28 Sample terminal type file

IMEI- Vendo Termi Chip Termi Data Termi Suppo

TAC r nal Model nal Transf nal rt Wi-
Model Type er Techn Fi
ology

123XX Huawei U8800 msm72 Cell GPRS/ WCDM Support

XXX 30 phone EDGE/ A
HSDPA

123XX Huawei U8660 msm76 Cell GPRS/ WCDM Support

XXX 27 phone EDGE/ A
HSDPA

l If the default terminal attributes cannot meet your requirement when you create terminal
types, you can define terminal attributes. Terminal type management supports a maximum
of 12 user-defined terminal attributes, including those directly created and those created
by importing files. You can create a terminal attribute using either of the following methods:
– Create a terminal attribute directly.
– Create a terminal attribute by importing a file. Terminal attribute files in .csv, .xls, .xlsx
or .tac format can be imported and exported.

NOTICE
Terminal attribute files in .tac format are Huawei proprietary files. Such files cannot be
exported after being imported, whereas other files can. For details, contact Huawei
technical support.

– Table 2-29 shows a sample terminal attribute file.

Table 2-29 Sample terminal attribute file

Attribute Name Attribute Value

Terminal Type Feature Phone

Terminal Type Data Card

Terminal Technology GSM

Terminal Technology GSM/WCDMA

Procedure
Step 1 Double-click System Function > Terminal Type Management in the navigation tree on the
left of the Analysis Task Management window.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 127

NOTE

You can also choose System Function > Terminal Type Management from the navigation tree in the
Analysis Task Management window and right-click Open. The Terminal Type Management window
is displayed.

Step 2 Create a terminal type.

If you need to... Then...

Create a terminal type directly Perform Step 3.

Create a terminal type by manually importing a terminal type file Perform Step 4.

Step 3 Create a terminal type directly.

1. Click New in the lower right corner. The Terminal Type Management-New dialog box
is displayed.
2. Set parameters listed in Table 2-30.
If the asterisk (*) is present on the right of a parameter, the setting of this parameter is
mandatory.

Table 2-30 Terminal type parameters

Parameter Description Optional/

Mandatory

IMEI-TAC Indicates the first eight digits of the International Mobile Mandatory
Equipment Identity (IMEI) that identifies the type of a
terminal.

Vendor Indicates the vendor of a terminal. Mandatory

Terminal Indicates the model of a terminal. Mandatory

Model

Chip Model Indicates the chip model. Optional

Terminal Indicates the technology the terminal supports. The Optional

Technology default technologies include GSM, WCDMA, TD-
SCDMA, GSM/WCDMA, GSM/TD-SCDMA, and
LTE.
If the default terminal attributes cannot meet the
statistical requirements, define terminal attributes. For
details, see Step 5. The default terminal attributes and
their values cannot be deleted, but values can be added
to the default terminal attributes.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 128

Parameter Description Optional/

Mandatory

Data Indicates the PS transfer mode the terminal supports. Optional

Transfer The default PS transmission modes include GPRS/
EDGE, GPRS/EDGE/HSDPA, and GPRS/EDGE/
HSPA.
If the default terminal attributes cannot meet the
statistical requirements, define terminal attributes. For
details, see Step 5. The default terminal attributes and
their values cannot be deleted, but values can be added
to the default terminal attributes.

Terminal Indicates the type of a terminal. The default terminal Optional

Type types include Feature Phone, Smartphone, Data
Card, Wireless Landline, Family Gateway.
If the default terminal attributes cannot meet the
statistical requirements, define terminal attributes. For
details, see Step 5. The default terminal attributes and
their values cannot be deleted, but values can be added
to the default terminal attributes.

Support Wi- Indicates that whether the terminal supports Wi-Fi. Optional
Fi

3. Click OK.

Step 4 Create a terminal type by manually importing a terminal type file.

1. Click Import in the lower right corner. The Open dialog box is displayed.
2. Select an edited terminal type file, and then click Open.
l If a terminal type file in .xls or .xlsx format is selected and the file contains multiple
worksheets, a prompt is displayed for you to select the desired worksheet.
l After the import is finished, the system will prompt the number of records should be
imported, and the actual number of records imported.

Step 5 Optional: Define a terminal attribute or add attribute values to an existing terminal attribute.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 129

If you need to... Then...

Define a terminal attribute l Create a terminal attribute directly.

1. In the Terminal Type Management window, right-
click the table header and choose Customize Column
from the shortcut menu. The Customize Column dialog
box is displayed.
2. Click Add in the Attribute area to set the new terminal
attribute name. Click OK.
3. Select the new terminal attribute in the Attribute area,
click Add in the Value area, and set the new terminal
attribute value. Click OK.
l Create a terminal attribute by importing a file.
1. In the Terminal Type Management window, right-
click the table header and choose Customize Column
from the shortcut menu. The Customize Column dialog
box is displayed.
2. Click Import. The Open dialog box is displayed.
3. Select an edited terminal attribute file, and click Open.
4. Perform the operations as prompted. Click OK.

Add a value to an existing 1. In the Terminal Type Management window, right-click

terminal attribute the table header and choose Customize Column from the
shortcut menu. The Customize Column dialog box is
displayed.
2. Select an existing terminal attribute in the Attribute area.
3. Click Add in the Value area to set the new terminal attribute
value.
4. Click OK.

----End

Follow-up Procedure
Perform operations in the Terminal Type Management window as required.

If you need to... Then...

Modify a terminal Only user-defined terminal attributes can be modified.

attribute and its 1. In the Terminal Type Management window, right-click the table
value header and choose Customize Column from the shortcut menu. The
Customize Column dialog box is displayed.
2. Select a terminal attribute in the Attribute area, click Edit, and
modify the terminal attribute name.
3. Select a terminal attribute in the Attribute area, choose a value in
the Value area, and click Edit to modify the terminal attribute value.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 130

If you need to... Then...

Delete a terminal Only user-defined terminal attributes can be deleted.

attribute and its 1. In the Terminal Type Management window, right-click the table
value header and choose Customize Column from the shortcut menu. The
Customize Column dialog box is displayed.
2. Select a terminal attribute in the Attribute area, choose a value in
the Value area, and click Delete to delete the value of a terminal
attribute.
3. Select one or multiple user-defined terminal attributes in the
Attribute area, and click Delete to delete a terminal attribute.
After you delete a terminal attribute, its value is deleted
automatically.

Export a terminal 1. In the Terminal Type Management window, right-click the table
attribute and its header and choose Customize Column from the shortcut menu. The
value Customize Column dialog box is displayed.
2. Click Export.
3. Set the file name and specify the save path and file type. Then, click
Save.
NOTE
An attribute whose value is empty is not displayed in the exported attribute file.

Modify terminal 1. In the Terminal Type Management window, select a terminal type,
type information and click Modify/View. The Terminal Type Management-
Modify/View dialog box is displayed.
2. Modify the relevant parameters.
The IMEI-TAC cannot be changed. The Vendor and Terminal
Model cannot be empty.
3. Click OK.
If a terminal type is used by certain tasks, the modification does not
affect the ongoing tasks. If a terminal type is used by a periodic task,
the related information is updated in the next period after the
modification.

Delete terminal 1. In the Terminal Type Management window, select one or multiple
types terminal types, and click Delete.
2. In the displayed dialog box, click Yes.
If a terminal type is used by certain tasks, the modification does not
affect the ongoing tasks. If a terminal type is used by a periodic task,
the related information is updated in the next period after the
modification.

Filter the terminal 1. In the Terminal Type Management window, set the filter condition
information and the filter context.
2. Click Filter.
The system will filter out the terminal information that meet the filter
condition and the filter context.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 131

If you need to... Then...

Export the 1. In the Terminal Type Management window, select one or multiple
terminal type terminal types, and click Export.
information and 2. Set the file name and specify the save path and file type. Then, click
save the Save.
information in
a .csv, .xls, or .xlsx
file

2.5.8 Managing PS Core Knowledge Bases (Optional)

This section describes how to manage PS Core knowledge bases. PS Core knowledge bases
manage information such as failure cause values, failure cause description, and related solutions
to exceptions that occur during theme analysis. This helps you quickly check the maintenance
experience when exceptions occur.

Prerequisites
You are authorized to manage PS Core knowledge bases.

Context
l PS Core knowledge bases include the SGSN/MME knowledge base and GGSN/SAE-GW
knowledge base. Each of the knowledge bases supports a maximum of 10,000 records.
l The knowledge bases are provided by default. You can use information in the knowledge
bases as a reference. Knowledge bases apply to any NE versions. However, you are advised
to use knowledge bases with USN9810V900R011C01 SPC100 and UGW9811
V900R009C01 and later versions.
l The following themes support association with PS Core knowledge bases: root cause
analysis for PS Core performance problems, PS Core VIP analysis, and PS Core complaint
analysis support.

Procedure
Step 1 In the navigation tree in the left pane of the Analysis Task Management window, double-click
System > PS Core Knowledge Base Management.

Step 2 In the displayed PS Core Knowledge Base Management window, check existing records.
You can select a record and click Modify/View to check the record details. For parameters
recorded in the knowledge bases, see Table 2-31.

Step 3 Optional: If an existing record in a knowledge base does not meet requirements, you can modify
it or create new ones.

If you need to... Then...

Modify an existing record Select the record and click Modify/View to modify its attributes.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 132

If you need to... Then...

Create new records l To create a single record, click New. In the displayed Create
Knowledge Base dialog box, set related parameters. For
parameters recorded in the knowledge bases, see Table
2-31.
l To import records in batches, click Import and select a file
you want to import. The Nastar does not allow you to import
a record with the same cause value as an existing record in
the knowledge bases.
NOTE
Comply with the following rules when you edit the records exported
in a csv file and then import the records into the knowledge databases:
l If the information in a table cell contains commas (,) or line feeds,
add a pair of quotation marks (") to include the information.
l If the information in a table cell is included in a pair of quotation
marks ("), add one more pair of quotation marks (") to include
the information.

Table 2-31 Parameters recorded in the knowledge bases

Parameter Description Optional/

Mandatory

Cause Hexadecimal value, which is the unique identifier of a Mandatory

record.
l Cause value range for SGSN/MME: 0x0 to 0xFFFF
l Cause value range for GGSN/SAE-GW: 0x0 to
0xFFFFFFFF

Failure cause Description of a failure cause. Mandatory

description

Solution Solutions to failures. You can solve problems by Mandatory

referring to this description.

Note Remarks. Knowledge bases apply to any NE versions. Optional

If there are differences between failure cause
description and solutions, you are advised to add
remarks.

----End

Follow-up Procedure
If you need to... Then...

Delete a record Select one or more records and click Delete.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 133

If you need to... Then...

Export records in Click Export and set the name of the file you want to import. The
batches Nastar then exports all existing records.

Restore default Click Resume. The Nastar restores the default knowledge base
settings information during initial Nastar installation.

2.5.9 Setting a Mailbox and Address List for Sending Analysis

Reports (Optional)
After a mailbox and address list for sending analysis reports are set, the Nastar can send the
generated analysis reports to the specified mailboxes through the mailbox. The function is only
be used for the VIP analysis and the PS Core root cause analysis.

Prerequisites
l You have obtained the mailbox information, including the server address, mail address,
user name, and password.
l You have obtained the addressee information.

Context
A maximum of 1000 records are allowed in the contact list.

The Nastar allows you to create an address list using either of the following methods:
l Adding information to the address list directly.
l Adding information to the address list by importing a file.
An address list file in .csv, .xls, or .xlsx format to be imported must contain the following
fields: User Name, Email, and Remark, as shown in Table 2-32. The match sequence of
columns is specified and automatic matching of columns is not supported.

Table 2-32 Example of the address list

User Name Email Remark

a1 a12121212@huawei.com ** CEO

b2 b90909090@yahoo.com ** PM

NOTE

The mailbox name must meet the following requirements:

l You can enter any digits, English characters, underscores (_), hyphens (-) or dot (.) preceding the at
sign (@) but cannot leave it empty.
l You can enter any digits, English characters, underscores (_) and hyphens (-) between the at sign
(@) and dot (.).
l You can enter any number or English character following the dot (.).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 134

Procedure
l Do as follows to set the mailbox for sending analysis reports:
1. Choose Maintenance > Email Settings. The Email Settings window is displayed.
2. Set the parameters for the mailbox in Table 2-33.

Table 2-33 Parameters for setting the mailbox for sending analysis reports

Parameter Description

SMTP Host Name or Address of the sending email server.

Address The address can be either an IP address or a domain
name, for example, 10.0.0.1 or mail.yourdomain.com.
An ATAE cluster system cannot directly parse a
domain name. Therefore, you must specify the IP
address of the email server here if the Nastar is deployed
in an ATAE cluster system.

Send Email Address Email address of the sender.

Max attachment size Maximum size of the files attached to the email.
(MB) Usually, the size of attachments is smaller than 8 MB.
Value range is 1 MB to 1000 MB.
If the actual attachment is larger than the configured
threshold, the analysis report will be divided to multiple
files based on the attachment threshold, and the files
will be sent in multiple mails.

Authentication required Indicates that the authentication is required when you

log in to the email server.
If you select this option, you need to set User Name
and Password. If you do not select this option, the User
Name and Password are unavailable.
NOTE
If the authentication is not required by the email server for
sending analysis reports, you do not need to select Is it
required to authenticate and the Nastar client directly sends
emails. If the authentication is required by the email server for
sending analysis reports, select Is it required to
authenticate and enter the user name and password to send
analysis reports.

User Name User name used to log in to the email sending server.

Password Password used to log in to the email sending server.

3. Click OK.
l Do as follows to set the address list for sending analysis reports:
1. Choose Maintenance > Auto-Distribution User Management. The Auto-
Distribution User Management window is displayed.
2. Click New. The New User window is displayed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 135

You can click Import to add users.

3. Set the parameters for the mailbox in Table 2-34.

Table 2-34 Parameter for setting the addressee

Parameter Description

User Name User name of the addressee.

Email Email address of the addressee.

Remarks Description of the User to be sent.

4. Click OK.

----End

2.5.10 Setting Location Parameters for Geographic Observation

(Optional)
The results of geographic locations are the longitudes and latitudes on a spherical coordinate
system. The system projects all or part of the sphere to a plane in order to display the location
results on a grid map. The sphere is distorted after the projection, and therefore the generated
grid map or geographic observation data is distorted. You can minimize the distortion of
geographic observation data by properly setting parameters based on the areas on the sphere.
By default, the system uses the first engineering parameter record. You need to set the parameters
only if the default engineering parameters do not meet requirements.

Prerequisites
You are authorized to manage the location parameters.

Context
l The current location parameters only allow you to set and query grid origins. You can
minimize the distortion of geographic observation data displayed on a grid map in the GIS
by properly setting the origin (by default, the system uses the first site information record
in the engineering parameters as the origin).
l The system maintains only the origin parameters that you have set during the last month
and deletes all the other historical origin parameter settings. If the origin parameters are
not set over one month, the system displays and maintains the latest origin parameter
settings until you set new origin parameters.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 136

NOTICE
l If the live network spans many latitudes and longitudes, you are advised to specify the
location, which is indicated by a proper latitude and longitude, as the origin for grid-based
geographic observation during the initial Nastar deployment.
l If the engineering parameters of the live network need to be updated frequently (due to
operations such as site deployment and reparenting), you are advised to specify the location,
which is indicated by a proper latitude and longitude as the origin for grid-based geographic
observation.

Procedure
Step 1 In the navigation tree of the Analysis Task Management window, double-click System
Function > Geo-Location Parameter Management.

Step 2 In the displayed Geo-Location Parameter Management window, view the existing origin
records.
The system performs analysis based on the latest origin record. For detailed historical origin
parameters, see Table 2-35.

Table 2-35 Historical origin parameters

Parameter Description

No. Number of the historical origin.

Delivered On Time when the origin was delivered.

Origin Mode for delivering the origin, including:

Delivery Mode l Use the first engineering parameter: uses the longitude and latitude
in the first engineering parameter record as an origin.
l Use the fixed origin: uses the longitude and latitude that you have
entered manually as a fixed origin.

Origin Longitude and latitude in the coordinate system.

NOTE
You need to select a proper latitude and longitude within the range of the live network
to specify the origin. Otherwise, grid-based geographic observation results may
deform or even no grid-based geographic observation results will be generated.

Step 3 Set the origin if the existing origin records do not meet requirements.
1. In the Geo-Location Parameter Management window, select a record.
2. Click Parameter Settings.
3. Change the grid origin.
4. Click OK to make the change take effect immediately.

----End

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 137

Follow-up Procedure
View logs in the Log Info area. For detailed log parameters, see Table 2-36.

Table 2-36 Log parameters

Parameter Description

Delivered On Time when the task was delivered.

Severity Level of the log. The value of this parameter

can be Minor or Major. Usually, you only
need to pay attention to logs of the Major
level.

NE Name Name of the NE involved in the task.

Operation Result Result of the operation. The value of this

parameter can be Success or Fail.

Details Details about the operation result.

l Set Function, Severity, and Condition, enter keywords, and then click Filter to filter out
desired logs.
l By default, the Log Info area displays the latest 100 log records. You can click Show
All to view all the logs generated during the last seven days in the Log Manager window.
l Click Show All, right-click in the log list displayed in the Log Manager window, and then
choose Save As from the shortcut menu to save logs.

2.5.11 PS Core Cell Information Management

This section describes how to use the PS Core cell information management function provided
by the Nastar client to provide cell information required for displaying information about the
TopN cells. The PS Core cell information management function allows you to configure, modify,
import, and export information about GSM and UMTS cells and to query cell information in
various analysis themes.

Prerequisites
You have obtained the data source files for cell information management and have checked that
the files and the parameters in the files meet the Nastar's requirements if you want to use the
import function.

Checking the License and User Rights

l The logged-in user is authorized to view and operate the PS Core cell information
management function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 138

Opening the Window

l In the navigation tree of the Analysis Task Management window, choose System
Function > PS Core Cell Information Management.

Main Window

Figure 2-15 PS Core Cell Information Management Interface

1: Window that displays cell information in a list 2: Button area

Table 2-37 Interface functions

No. Item Description

(1) Window that displays cell Displays information about

information in a list all cells in a list.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 139

No. Item Description

(2) Button area Provides buttons for various

functions:
l Import: You can click
this button to import cell
information.
Set the file name, file
type, and save path, and
save in CSV, XLS, or
XLSX format.
l Export: You can click
this button to export cell
information.
Set the file name, file
type, and save path, and
save in CSV, XLS, or
XLSX format.
l New: You can click this
button to set cell
parameters and create cell
information.
l View: You can click this
button to view parameter
information about a GSM
or UMTS cell.
l Delete: You can click this
button to delete
information about one or
more unnecessary cells.
l Export Template: You
can click this button to
export a cell information
template.
Set the file name, file
type, and save path, and
save in CSV, XLS, or
XLSX format.
For details about parameter
definition specifications, see
Specifications of data
source parameters for cell
information management.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 140

Specifications of Data Source Parameters for Cell Information Management

l The Nastar supports the data source files for cell information management in XLS, XLSX,
or CSV format.
l The following table describes the parameters contained in the data source files for cell
information management. Such files are required for PS Core performance root cause
analysis and various GSM and UMTS analysis themes.

Table 2-38 Specifications of data source parameters for cell information management

Parameter Value Range Description Mandatory or

Optional

MCC [000,999] Country code of a Mandatory

NOTE specified mobile
Each MCC is subscriber
centrally processed
into a 3-digit
number on the CN.
During cell
information import
or creation, 0s are
added at the
beginning of an
MCC if the length of
the MCC is less than
3.

LAC [0X0,0XFFFF] Location area code of Mandatory

a specified cell

CI [0X0,0XFFFF] Identity of a specified Mandatory (the value

cell of this parameter is set
to SAC on a UMTS
network)

Description 200 characters Descriptive Optional

information of a
specified cell

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 141

NOTE
Each RAT supports a maximum of 100,000 cells.
l An example of the cell information template (containing cell information) supported by the
Nastar is as follows:

MCC MNC LAC CI Description

Number(3) Number(3) Number(6) Number(6) string(200)

46 1 1 11 cell name: test

name, bsc
name: rnc1, bsc
ip:10.1.1.1

NOTICE
l The names of fields in the first line cannot be changed.
l The formats of fields in the second line cannot be changed.
l The fields in the third line are cell information examples for your reference.

2.6 Subscribing to Analysis Data

2.6.1 Basics of Data Subscription

This section describes the purposes and application scenarios of the Nastar data subscription
function. Data subscription of Nastar is classified into basic subscription and application
subscription.

Function Description
l Basic data subscription is used to turn on the data switches of NEs on the live network so
that NEs can generate raw data.
l Application data subscription is used to deliver specific rule files to NEs so that NEs can
generate raw data that meets the analysis requirements. It also enables the data
preprocessing functions of the SAU and eSAU so that the raw data generated by NEs can
be preprocessed and the analysis data meets the Nastar analysis requirements.

About the conditions and purposes of applying basic subscription and application subscription
for different themes, refer to 2.6.4 Appendix: List of Data Subscription Function of All the
Analysis Function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 142

Scenarios
The analysis data subscription is a function with a high security level. In normal cases, this
operation is performed by the following roles:
l Administrator: has the permission to query and set the subscription status of all NEs and
VIP group users.
l Common user: has the permission to query the subscription status of only specified NEs
and VIP group users.
NOTE

You can choose Security > Security Management in the main window of the Nastar and set the rights of
users in the displayed window. By allocating the permissions for managing subscriber data subscription
and for viewing and operating NE and VIP groups, you can control the permissions of users to subscribing
to data related to different NEs and VIP groups.

Figure 2-16 shows the application scenarios for the two roles to use the analysis data subscription
function.

Figure 2-16 Application scenarios of the data subscription function

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 143

Table 2-39 Scenario description of the data subscription function

User Applica Description Example

tion
Scenari
o

Admin Initial If the administrator uses the Managed network: networks A

istrator configura Nastar for the first time, the and B.
tion administrator needs to collect Involved theme: VIP analysis.
information about the NEs on the
managed network and the Nastar The administrator selects all the
functions to be used. Then, the cells on networks A and B, and
administrator turns on the data sets the data switch status of all
switches of NEs for each analysis cells for the VIP analysis to ON in
theme in batches. batches by using the basic
subscription function. The
administrator can also set the VIP
objects and NE objects by using
the application subscription
function.

Routine The administrator can obtain -

maintena information for routine
nce maintenance in the following
ways:
l The administrator periodically
updates the data subscription
status on the live network. If a
data switch that should be
turned on is in the OFF state,
the administrator needs to
enable the data subscription
function again and turns on the
data switch.
l A common user queries the
data switch status on the live
network and finds that the
certain data switch status does
not meet analysis
requirements. In this case, the
administrator enables the data
subscription function again
and turns on these data
switches.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 144

User Applica Description Example

tion
Scenari
o

Comm Routine Before creating an analysis task, a A common user in network A

on Query common user needs to check finds that the data switch of cell a
users whether the data subscription for the VIP analysis is in the
status on the live network meets OFF state, which does not meet
analysis requirements. If the data analysis requirements. Therefore,
subscription status does not meet the common user submits an
analysis requirements, the application to the administrator
common user needs to submit an for turning on this switch.
application to the administrator After receiving the application,
for turning on certain switches. the administrator sets the data
switch status of cell a for the VIP
analysis to ON.

2.6.2 Basic Subscription of Analysis Data

This section describes how to turn on the data switches in batches for selected NEs in an analysis
task. Then, the Nastar system can collect required analysis data. You are advised to perform
these operations as the administrator.

Prerequisites
l You have the permissions to manage analysis data subscription. Permissions on data
subscription management include the permission on data subscription tasks, permission on
analysis tasks (such as VIP analysis tasks), and permission on operation objects (such as
NEs, NE groups, VIP subscribers, and VIP groups). Data subscription tasks cannot be
successfully issued if you are granted only the permission on data subscription tasks.
l The OSS and NEs involved in an analysis task have been created, and the SAU of each NE
has been configured. For detailed operations, see 2.3 Configuring OSS and NE
Information.
l Configuration data has been imported. For details, see 2.5.2 Checking the Integrity of
Configuration Data.

Context
The administrator needs to obtain the NE information and Nastar analysis theme information on
the network before basic subscription of analysis data. Then, the administrator can turn on the
data switches of the selected NEs for corresponding analysis themes in batches based on the
obtained information.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 145

NOTE

l If the NE information (for example, NE FDN) is changed, you need to issue the basic data subscription
command again.
l If NE information is changed, you can click Refresh in the Data Subscription Management window
to update NE information displayed on the client. This ensures that subscription tasks can be
successfully delivered to NEs whose information has been changed.

Procedure Diagram

Procedure
Step 1 Choose Maintenance > Data Subscription Management. The Data Subscription
Management window is displayed.

Step 2 Click a tab for an RAT in the Data Subscription Management window.

Step 3 In the NE object navigation tree, select the required NEs.

On the Basic Subscription Settings tab page, data switch status of the selected NEs is displayed.
During the initial setting, all data switches are in the OFF or Unknown state.

Step 4 Optional: For the LTE network, you can import and export an Excel file on the data subscription
management page to view the subscription status of some NEs as required. The detailed
procedure is as follows:
1. Click Import under the NE tree and select an Excel file.
NOTE

Values in the eNodeBID and eNodeBName columns in the imported file cannot be empty.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 146

2. View the subscription status of imported NEs in Table 2-40.

Table 2-40 Imported NEs status

If... Then...

The import is successful. The NEs in the left NE tree that match those
in the Excel file are selected, and the right
list is synchronously displayed.

The import fails. The If you export failed eNodeB? dialog

box is displayed. In such case, you can
click Yes to export the information about
the NEs that do not match the left NE tree.

NOTE

If you need to export only some records, select them in the right list, right-click, choose Save As from the
shortcut menu, and click Save. Then, you can view the records in your local PC.

Step 5 Choose the Basic Subscription Settings tab page.

Step 6 Click Set. The Basic Subscription Settings dialog box is displayed.

Step 7 Set the data switch status of each analysis theme to ON.

Basic subscription of analysis data has the following states:

l ON: turn on the data switches of the selected NEs for corresponding analysis themes.
l OFF: turn off the data switches of the selected NEs for corresponding analysis themes. This
operation is not recommended.
l No Modification: The data switch status has not ever been changed by using the Nastar. This
is the default state.
NOTE

Certain analysis themes use data of the same type. For example, complaint analysis, VIP analysis, and cell
performance analysis use the CHR data. If you change the status of the data switch for a type of data in
one analysis theme, the status of the data switch for this type of data in all other analysis themes changes
accordingly. For example, the status of the data switch for CHR data in both VIP analysis and cell
performance analysis is changed to ON if you change the status of the data switch for CHR data in complaint
analysis support to ON.

Step 8 Optional: Click to set the advanced parameters of subscription.

The advanced parameter settings will affect the content of the data generated by the NE. For
example, set the advanced parameters of VIP Analysis Data (CHR-PS) in the GSM network.
l Set the thresholds about *** Threshold parameter. After subscribing successfully, the CHR
data will be generated by the NEs in accordance with the configured thresholds.
l For details about all the advanced parameters, refer to the NE product documentation. For
details about all the signaling message, refer to the 3GPP.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 147

NOTE

l If the icon following a data type is grey, you do not need to set advanced parameters for this type of
data or the advanced parameter setting function is unsupported.
l If data subscription is enabled, you can set the check box status corresponding to a parameter as required.
The check box status includes:

l : indicates that the delivery of this parameter is enabled. When subscription data is delivered, the NE
delivers the corresponding data or turns on the corresponding switch.
l : indicates that the delivery of this parameter is disabled. When subscription data is delivered, the NE
does not deliver the corresponding data or turns off the corresponding switch.

l : indicates that data is not delivered.

l If data subscription is disabled, the related data subscription functions are all unavailable, and the preceding
options are invalid.

Step 9 Click Confirm.

The Nastar starts to deliver commands to the NEs to turn on their data switches. The operation
information is displayed in the Log Info area.

----End

Follow-up Procedure
l After required data is subscribed to, click Export to export data subscription results in
batches. The data subscription results are used to identify NEs whose data subscription is
abnormal and to select NEs whose data you want to subscribe to in batches by using the
import function.
l After the basic subscription, right-click the subscription status table and choose Refresh
from the shortcut menu to view the switch status for the data sources on the live network.
Table 2-41 describes the switch status of various data source switches.

Table 2-41 Data switch status

Icon Status Description

ON The data switch of an NE for an analysis theme

on the live network is in the ON state, meeting
analysis requirements of the Nastar.

OFF The data switch of an NE for an analysis theme

on the live network is in the OFF state, not
meeting analysis requirements of the Nastar.

Partly Succeeded Indicates that only some cells served by an NE

have successfully reported analysis data based
on which the Nastar can perform analysis.

Processing The Nastar is starting, closing, or querying the

data switch of an NE for an analysis theme on
the live network, the status is Processing.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 148

Icon Status Description

Unknown The data switch of an NE for an analysis theme

on the live network is in the Unknown state.
The Nastar cannot detect the data switch status.
The possible causes are as follows:
l The communication between the Nastar
and the U2000/M2000 is abnormal.
l The communication between the U2000/
M2000 and NEs is abnormal.
l NEs are not in normal running status. For
example, NEs are being upgraded or have
been shut down.
l In the RNC in Pool scenario, the Nastar
performs operations on all the physical
RNCs of a logical RNC when you turn on
or turn off a data source switch or query the
state of data source switch.
– When you turn on or turn off a data
source switch, the values of Action
Result for all physical RNCs are
Succeed in the Log Info area.
– If you query the state of a data source
switch when no cells are configured for
a non-master physical RNC, the state of
the data source switch queried on the
non-master physical RNC is OFF.
However, the state of the data source
switch queried on the master physical
RNC is ON. As a result, the Nastar
displays only the Unknown.

NonSupport Users cannot query the data switch status of an

NE on the live network by using the Nastar
system. For example, if an NE is of the base
station controller (BSC) level but a data switch
on the live network is of the cell level, the data
switch status of the NE is displayed as
NonSupport.

l View information about the subscription in the Log Info area. Table 2-42 lists the
parameters.

Table 2-42 Log parameters

Parameter Description

Date/Time Time when a task is complete.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 149

Parameter Description

Level Level of the log, including Minor and Major. You are advised to
focus on the Major level log information.

Action Type Action type, including open and close.

Action Result Action result. The value can be Succeed or Failure.

OSS Name The name of OSS which the subscribed NEs belong to.

NE Name The name of the subscribed NEs.

Switch Name Switch type.

Details Detailed information about the operation result.

– Select Function, Severity, Condition, and type the keyword. Click Filter to filter the
log information.
– It displays the latest 100 log information by default in the Log Info area. Click Show
All, the Log Manager window is opened. You can view all of the log information
generated within seven days.
– Click Show All, the Log Manager window is opened. Right-click the log list and choose
Save As from the shortcut menu to save the log information.

2.6.3 Application Subscription of Analysis Data

This section describes the application subscription of analysis data. For certain analysis themes,
basic subscription of analysis data only turns on data switches of NEs, which cannot meet the
special requirements of the Nastar. By using the application subscription function, the Nastar
can deliver special rule files to NEs to obtain required analysis data and enable data preprocessing
functions of the SAU and eSAU.

Prerequisites
l You have the permissions to manage analysis data subscription.
l The OSS and NEs involved in an analysis task have been created, and the SAU of each NE
has been configured. For detailed operations, see 2.3 Configuring OSS and NE
Information.
l You have imported the configuration data. For detailed operations, see 2.5.2 Checking the
Integrity of Configuration Data.
l You have performed basic subscription of analysis data. For detailed operations, see 2.6.2
Basic Subscription of Analysis Data.
l You have created a VIP group before subscribing to VIP analysis data. For detailed
operations, see Managing VIP Groups.
l You have imported the engineering parameters before subscribing to network geographic
observation data. For detailed operations, see Importing Engineering Parameters.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 150

Context
NOTE
If the NE FDN changes, you need to issue the application data subscription command again.

Application subscription is not required for certain analysis themes. To learn the data you must
subscribe to for the analysis themes, see 2.6.4 Appendix: List of Data Subscription Function
of All the Analysis Function.

Procedure Diagram

Procedure
Step 1 Choose Maintenance > Data Subscription Management. The Data Subscription
Management window is displayed.

Step 2 Click a tab for an RAT in the Data Subscription Management window.

Step 3 In the NE object navigation tree, select the required NEs.

On the *** Analysis tab page, application subscription status of the selected NEs is displayed.
During the initial setting, all application subscription status is OFF or Unknown.

1. Click Import under the NE tree and select an Excel file.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 151

NOTE

Values in the eNodeBID and eNodeBName columns in the imported file cannot be empty.
2. View the subscription status of imported NEs in Table 2-43.

Table 2-43 Imported NEs status

If... Then...

The import is successful. The NEs in the left NE tree that match those
in the Excel file are selected, and the right
list is synchronously displayed.

The import fails. The If you export failed eNodeB? dialog

box is displayed. In such case, you can
click Yes to export the information about
the NEs that do not match the left NE tree.

NOTE

If you need to export only some records, select them in the right list, right-click, choose Save As from the
shortcut menu, and click Save. Then, you can view the records in your local PC.

Step 5 Choose the *** Analysis tab page.

Step 6 Click ON. The *** Analysis Parameter Setting dialog box is displayed.

Step 7 Set application subscription parameters.

The application subscription GUI varies based on analysis theme. For details about the
application subscription parameters of each analysis theme, see *** Network Optimization >
*** Analysis > Process of *** Analysis in the Online Help.

Step 8 Click Confirm.

The Nastar starts to deliver rule files to the NEs. The operation information is displayed in the
Log Info area.

----End

Follow-up Procedure
l After required data is subscribed to, click Export to export data subscription results in
batches. The data subscription results are used to identify NEs whose data subscription is
abnormal and to select NEs whose data you want to subscribe to in batches by using the
import function.
l After the application subscription of analysis data, right-click the subscription status table
and choose Refresh from the shortcut menu to view the switch status for the data sources
on the live network. Table 2-44 describes the switch status of various data source switches.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 152

Table 2-44 Application subscription status

Icon Status Description

ON The Nastar has delivered rule files to NEs to

obtain analysis data.

OFF The Nastar does not deliver rule files to NEs.

Partly Succeeded Indicates that only some cells served by an NE

have successfully reported analysis data based
on which the Nastar can perform analysis.

Processing The Nastar is delivering or canceling

delivering the rule files to NEs, the status is
Processing.

Unknown The status of delivering rule files to an NE is

unknown. The Nastar cannot detect the rule file
delivery status. The possible causes are as
follows:
l The network is faulty, or NEs are
disconnected.
l The actual data switch status of an NE is
different from the delivered data switch
status.

NonSupport The Nastar cannot subscribe to the analysis

data of an NE. For example, if an NE is of the
BSC level but the data switch on the live
network is of the cell level, the data switch
status of the NE is displayed as NonSupport.

l View information about the subscription in the Log Info area. Table 2-45 lists the
parameters.

Table 2-45 Log parameters

Parameter Description

Date/Time Time when a task is complete.

Level Level of the log, including Minor and Major. You are advised to
focus on the Major level log information.

Action Type Action type, including open and close.

Action Result Action result. The value can be Succeed or Failure.

OSS Name The name of OSS which the subscribed NEs belong to.

NE Name The name of the subscribed NEs.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 153

Parameter Description

Switch Name Switch type.

Details Detailed information about the operation result.

2.6.4 Appendix: List of Data Subscription Function of All the

Analysis Function
Basic subscription is required for almost all analysis themes. Application subscription is required
for only a few analysis themes. This chapter lists the conditions and purposes of applying basic
subscription and application subscription for different themes.

l GSM
l UMTS
l LTE TDD
l LTE FDD
l PS Core

GSM

Table 2-46 Data subscription for different themes (GSM)

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

GSM Performanc Basic Basic subscription: -

MR e data subscription:
Analysis No

Application Application subscription: Obtain NE performance

subscription: data from the U2000/M2000.
Yes

GSM Performanc Basic Basic subscription: -

Neighbo e data and subscription:
neighboring No

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 154

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

ring Cell cell Application Application subscription: Set neighboring cell

Analysis measureme subscription: measurement parameters of NEs so that the Nastar
nt data Yes can obtain performance data that meets the
analysis requirements.

GSM Performanc Basic Basic subscription: -

Frequen e data and subscription:
cy neighboring No
Analysis cell
measureme Application Application subscription: Set neighboring cell
nt data subscription: measurement parameters of NEs so that the Nastar
Yes can obtain performance data that meets the
analysis requirements.

GSM/ Performanc Basic Basic subscription: -

UMTS e data subscription:
Neighbo No
ring Cell
Analysis Application Application subscription: Set neighboring cell
subscription: measurement parameters of NEs so that the Nastar
Yes can obtain performance data that meets the
analysis requirements.

GSM Scanned Basic Basic subscription: -

Uplink uplink subscription:
Interfere frequency No
nce data
Analysis Application Application subscription: Set frequency
subscription: measurement parameters of NEs so that the Nastar
Yes can obtain scanned uplink frequency data that
meets the analysis requirements.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 155

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

GSM CHR data, Basic Basic subscription:

Complai MR data subscription: l GSM complaint analysis support data (MR-
nt Yes CS), optional: Turn on the MR switch. The
Analysis information in the MR data can replace the
Support original measurement report information in
the CHR data, so that measurement report
information more comprehensively and the
voice quality analysis more accurately.
l GSM complaint analysis support data (CHR-
CS): Turn on the CHR switch for the CS
service and enable MSs to report international
mobile subscriber identities (IMSIs).
l GSM complaint analysis support data (CHR-
PS): Turn on the CHR switch for the PS
service.

Application Application subscription: -

subscription:
No

GSM CHR data Basic Basic subscription:

VIP subscription: l GSM VIP analysis data (CHR-CS): Turn on
Analysis Yes the CHR switch for the CS service and enable
MSs to report IMSIs.
l GSM VIP analysis data (CHR-PS): Turn on
the CHR switch for the PS service.

Application Application subscription: Set VIP objects and NE

subscription: objects.
Yes

GSM CHR data Basic Basic subscription:

Cell subscription: l GSM cell performance analysis data (CHR-
Perform Yes CS): Turn on the CHR switch for the CS
ance service and enable MSs to report IMSIs.
Analysis
l GSM cell performance analysis data (CHR-
PS): Turn on the CHR switch for the PS
service.

Application Application subscription: Set the exception

subscription: thresholds of KPIs.
Yes

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 156

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

GSM CHR data Basic Basic subscription:

Termina subscription: l GSM terminal analysis data (CHR-CS): Turn
l Yes on the CHR switch for the CS service and
Analysis enable MSs to report IMSIs.
l GSM CHR terminal analysis (CHR-PS): Turn
on the CHR switch for the PS service.

Application Application subscription: Set the exception

subscription: thresholds of KPIs.
Yes

GSM MR data Basic Basic subscription:

Network and CHR subscription: l Network geographic observation data (MR-
Geograp data Yes CS): Turn on the BSC- or BTS-level MR
hic measurement switch.
Observa
tion l Network geographic observation data (CHR-
CS): Turn on the CHR switch for the CS
service and enable MSs to report IMSIs.
l Network geographic observation data (CHR-
PS): Turn on the CHR switch for the PS
service.

Application Application subscription: Set filter criteria of

subscription: KPIs.
Yes

UMTS

Table 2-47 Data subscription for different themes (UMTS)

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

UMTS MR data Basic Basic subscription: Turn on the RNC-level MR

Coverag subscription: measurement switch.
e Yes
Analysis

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 157

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

Application Application subscription: Turn on the threshold

subscription: switch.
Yes

UMTS MR data Basic Basic subscription: Turn on the RNC-level MR

Intra- subscription: measurement switch.
Frequen Yes
cy
Neighbo Application Application subscription: Turn on the threshold
ring Cell subscription: switch.
Analysis No

UMTS MR data Basic Basic subscription: Turn on the RNC-level MR

Inter- subscription: measurement switch.
Frequen Yes
cy
Neighbo Application Application subscription: Set frequency
ring Cell subscription: measurement parameters.
Analysis Yes

UMTS/ MR data Basic Basic subscription: Turn on the RNC-level MR

GSM subscription: measurement switch.
Neighbo Yes
ring Cell
Analysis Application Application subscription: Set frequency
subscription: measurement parameters.
Yes

UMTS MR data Basic Basic subscription: Turn on the RNC-level MR

Pilot subscription: measurement switch.
Pollutio Yes
n
Analysis Application Application subscription: Set the exception
subscription: thresholds of KPIs.
Yes

UMTS RTWP data Basic Basic subscription: -

Uplink subscription:
Interfere No
nce
Analysis Application Application subscription: Set the exception
subscription: thresholds of KPIs.
Yes

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 158

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

UMTS CHR data, Basic Basic subscription:

Complai MR data subscription: l UMTS complaint analysis support data (MR),
nt Yes optional: Turn on the MR switch. The
Analysis information in the MR data can replace the
Support original measurement report information in
the CHR data, so that measurement report
information more comprehensively and the
voice quality analysis more accurately.
l UMTS complaint analysis support data
(CHR): Turn on the CHR switch and enable
UEs to report IMSIs.

Application Application subscription: -

subscription:
No

UMTS CHR data Basic Basic subscription: Turn on the CHR switch and
VIP subscription: enable UEs to report IMSIs.
Analysis Yes

Application Application subscription: Set VIP objects and NE

subscription: objects.
Yes

UMTS MR data Basic Basic subscription:

Termina and CHR subscription: l UMTS terminal analysis data (MR): Turn on
l data Yes the RNC-level MR measurement switch.
Analysis
l UMTS terminal analysis data (CHR): Turn on
the CHR switch and enable UEs to report
IMSIs.

Application Application subscription: Set the exception

subscription: thresholds of KPIs.
Yes

UMTS CHR data Basic Basic subscription: Turn on the CHR switch and
Cell subscription: enable UEs to report IMSIs.
Perform Yes
ance
Analysis Application Application subscription: Set the exception
subscription: thresholds of KPIs.
Yes

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 159

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

UMTS MR data Basic Basic subscription:

Network and CHR subscription: l Network geographic observation data (MR):
Geograp data Yes Turn on the RNC-level MR measurement
hic switch.
Observa
tion l Network geographic observation data (CHR):
Turn on the CHR switch and enable UEs to
report IMSIs.

Application Application subscription: Set the exception

subscription: thresholds of KPIs.
Yes

LTE TDD

Table 2-48 Data subscription for different themes (LTE TDD)

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

TDD CHR data subscription: measurement switch.
Coverag Yes
e
Analysis Application Application subscription: Turn on the threshold
subscription: switch.
Yes

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

TDD CHR data subscription: measurement switch.
Complai MME CHR Yes
nt data
Analysis Application Application subscription: -
Support subscription:
No

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

TDD CHR data subscription: measurement switch.
VIP MME CHR Yes
Analysis data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 160

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

Application Application subscription: Set VIP objects and NE

subscription: objects.
Yes

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

TDD CHR data subscription: measurement switch.
Termina MME CHR Yes
l data
Analysis Application Application subscription: Set the exception
subscription: thresholds of KPIs.
Yes

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

TDD CHR data subscription: measurement switch.
Cell MME CHR Yes
Perform data
ance Application Application subscription: Set the exception
Analysis subscription: thresholds of KPIs.
Yes

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

TDD CHR data subscription: measurement switch.
Network Yes
Geograp
hic Application Application subscription: Set the exception
Observa subscription: thresholds of KPIs.
tion Yes

NOTE

The generation and transmission of the MME CHR data is not triggered by the Nastar subscription
command. The MME CHR data will be uploaded to the LTE SAU through Huawei internal protocols in
real time after the CHR data reporting values are configured and the CHR data transmission switch is
enabled.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 161

LTE FDD

Table 2-49 Data subscription for different themes (LTE FDD)

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

FDD CHR data subscription: measurement switch.
Coverag Yes
e
Analysis Application Application subscription: Turn on the threshold
subscription: switch.
Yes

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

FDD CHR data subscription: measurement switch.
Complai MME CHR Yes
nt data
Analysis Application Application subscription: -
Support subscription:
No

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

FDD CHR data subscription: measurement switch.
VIP MME CHR Yes
Analysis data
Application Application subscription: Set VIP objects and NE
subscription: objects.
Yes

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

FDD CHR data subscription: measurement switch.
Termina MME CHR Yes
l data
Analysis Application Application subscription: Set the exception
subscription: thresholds of KPIs.
Yes

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

FDD CHR data subscription: measurement switch.
Cell MME CHR Yes
Perform data
ance Application Application subscription: Set the exception
Analysis subscription: thresholds of KPIs.
Yes

LTE eNodeB Basic Basic subscription: Turn on the eNodeB CHR

FDD CHR data subscription: measurement switch.
Network Yes
Geograp

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 162

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

hic Application Application subscription: Set the exception

Observa subscription: thresholds of KPIs.
tion Yes

NOTE

PS Core

Table 2-50 Data subscription for different themes (PS Core)

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

PS Core CHR data Basic Basic subscription: Set the SGSN/MME CHR
Termina subscription: reporting value.
l Yes
Analysis
Application Application subscription: Deliver the
subscription: preprocessing task.
Yes

PS Core CHR data Basic Basic subscription: Set the SGSN/MME CHR
Perform subscription: reporting value.
ance Yes
Root
Cause Application Application subscription: Deliver the
Analysis subscription: preprocessing task.
Yes

PS Core CHR data Basic Basic subscription: Set the SGSN/MME CHR
VIP subscription: reporting value.
Analysis Yes

Application Application subscription: Set VIP objects and NE

subscription: objects.
Yes

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 163

Theme Required Whether Purpose

Data Data
Subscriptio
n Is
Required

PS Core CHR data Basic Basic subscription: Set the SGSN/MME CHR
Complai subscription: reporting value.
nt Yes
Analysis
Support Application Application subscription: -
subscription:
No

2.7 Checking the Integrity of Analysis Data

This section describes how to check the integrity of analysis data. You need to check the integrity
of analysis data to ensure that the Nastar can analyze the data normally.

Prerequisites
l You have subscribed to analysis data.
l You are authorized to query analysis data.

Procedure Diagram

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 164

Procedure
Step 1 Choose Maintenance > Data Maintenance Management. The Data Maintenance
Management window is displayed.

Step 2 In the navigation tree of Data Maintenance Management window, choose Data Type >
Analysis sort > *** Data.

For the analysis theme of the different analysis sort, you need to query the data of the different
type. *** indicates the name of analysis theme to be analyzed, for example, Data Type >
Network Analysis > GSM Cell Performance Analysis Data.

Step 3 Set Select Condition on the Query Data tab page.

1. Set Query type.
The Nastar gathers analysis data according to the different time levels.
2. Specify a time period only after you select Is time limit required.
NOTE

l If no time limit is required for the query, you do not need to set this parameter.
l If the local time zone settings of the client and the server are different, the start and end time
limits for queried results are different from the specified start and end time limits. Change the
local time zone settings of the client and the server to ensure that the local time zone settings of
the client and the server are the same by following the instructions provided in Nastar
Administrator Guide.
3. Select specific nodes from the NE object navigation tree.
4. Optional: Select the VIP group to be queried from the VIP group navigation tree.
This step is only used for querying the *** VIP analysis data. *** refers to the network
system.

Step 4 Click Query in the bottom left corner of the window.

You can check and ensure that the configuration data is imported into the database.

l NEs with data, as well as the start time and end time of NE data, are listed in a table. The
start time and end time indicate the time period during which a service is used instead of the
time period during which the data is imported into the database.
l Each NE Name tab page displays detailed data with selected query type of an NE with data.
For example, after setting Query Type to Hour, you can query the detailed data information
of per hour of each day within the time range. After setting Query Type to Day, you can
query the detailed data information of per day of each month within the time range.
On the tab page, green grids indicate that data is available and white grids indicate that data
is unavailable.

If the analysis data is subscribed, and the result is normal, but no relevant data is displayed,
contact Huawei technical support.

----End

Follow-up Procedure
You can right-click in the right pane and choose Save As from the shortcut menu to save the
current query results as a .csv, .xls, or .xlsx file.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 165

2.8 Creating an Analysis Task

Prerequisites
l The analysis data and configuration data have been imported to the Nastar database. For
detailed operations, see 2.7 Checking the Integrity of Analysis Data.
l The number of tasks of each type does not exceed the maximum value.
The number of tasks of each type is limited. If the number of tasks exceeds the maximum
value, new tasks cannot be created.
In the navigation tree in the left of the Analysis Task Management window, select a theme
function. In the lower part of the analysis task list, the number of the created analysis tasks
for the selected theme and the permitted number of analysis tasks are displayed.

Context
l The network scale that the Nastar supports for one analysis task is limited. For details, see
the specification-related section of each theme. When you create an analysis task beyond
specifications, the task may fail due to uncontrollable risks of task execution time and
required disk space. If unnecessary, you are not advised to create a task beyond
specifications.
l When the free database and storage space on the Nastar or eSAU is less than 100 GB, the
system will display a message during analysis task creation, indicating that the disk space
is insufficient. If you create an analysis task when the free space is insufficient, the task
may fail due to insufficient space. You can release disk space by deleting outdated analysis
tasks or historical analysis data. For details about how to delete historical analysis data, see
7.8.2 Periodically Deleting Analysis Data.
l This section describes the common steps for creating an analysis task. The parameter
settings vary from one theme to another. For details about how to set the parameters, see
the section under *** Network Optimization in this document. *** represents a certain
network type.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 166

Procedure Diagram

Procedure

Step 1 In the Analysis Task Management window, click . The New Task dialog box is displayed.
NOTE
You can also open the window in either of the following ways:
l In the navigation tree in the left of the Analysis Task Management window, double-click the analysis
node for a theme. The New Task dialog box is displayed.
l In the navigation tree in the left of the Analysis Task Management window, select the analysis node
for a theme and right-click New. The New Task dialog box is displayed.

Step 2 Set the basic information for a task including Task Name, Task Type, and Remarks.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 167

NOTICE
l Task Name must be unique and cannot be null.
l Task Name must be named in Chinese or English. Otherwise, the function of distributing
analysis results by emails is unavailable.

Step 3 Click Next.

Step 4 Set the task properties.

The task properties vary from one theme function to another. For details about the parameters,
see the sections for each theme.

Step 5 Click Next.

Step 6 Set the execution time for the task.

l If only One-time is available for Task Type in the window, the task supports only one-time
analysis.
l If only Periodic is available for Execution Type in the window, the task supports only
periodic analysis.
l If both One-time and Periodic are available for Execution Type, the task supports one-time
analysis and periodic analysis.

For details about parameters, see Table 2-51.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 168

Table 2-51 Parameters for task execution time

Execution Type Parameter Description

One-time The system executes the task once at a specified period. Set the data
time range and the start time for executing the task as follows:
l Time Range: Indicates that when a task is performed, only the
data generated within the time range is analyzed. The start time
should precede the end time.
: Indicates the time range of the analysis of the selected task.
For details about the time range of the analysis for each task, see
the sections for different themes.
NOTE
If the time exceeds the maximum value, creating the new task fails.
l Delayed: Indicates that if this parameter is not selected, the system
executes the task immediately. If it is selected, the system will
execute the task at the time of the Execution Delay.
l Execution Delay: Indicates the specified execution time of the
task.
l XXX Analysis Data tab page: Indicates the status of the required
data for analysis task in the Nastar database. The blue area
indicates the theme data within an hour; the yellow area indicates
the configuration data within an hour; the green area indicates that
both the theme data and configuration data exist.
The data within the time period can be analyzed successfully only
when both the configuration data and theme data exist within a
time period.
NOTE
Select the desired time range of the analysis on the tab page. The selected
time range is associated with Time Range.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 169

Execution Type Parameter Description

Periodic The system executes the task periodically. Set the start time for
executing the task, period, and times of the task as follows:
l Start Time: Indicates the date for starting a task.
– If the start time is later than the current server time, after the
date is set, the Nastar will execute the task at 00:00 of the next
day by default.
– If the start time is earlier than the current server time, after the
date is set, the Nastar will execute the task immediately.
l Execution Delay: Indicates the time of task execution delay. The
unit is hour.
The parameter must be used with Start Time. After this parameter
is set, the Nastar will execute the task certain hours later than 00:00
of the specified day in Start Time. For example, if Start Time is
set to 12/16/2009 and Execution Delay is set to 3, the Nastar will
execute the task at 03:00 on December 17, 2009.
l Period: Indicates the interval between periodic tasks.
l Number of execution times: Indicates the execution times of a
periodic task. Value range: 0–9999. The value 0 indicates that the
execution times are countless.
l Part of the analysis tasks support only busy-hour analysis.

NOTE
When the time is in the DST period, the DST check box is automatically selected, and users are not allowed to
set the DST. When the time is not in the DST period, the DST check box is automatically deselected, and users
are not allowed to set the DST. When the time in the time is in the DST overlapping period, the DST check box
is automatically selected, and users are allowed to set the DST.

Step 7 Click Finish.

The newly created analysis task is displayed in the task list.

----End

Follow-up Procedure
In the task list of the Analysis Task Management window, select an analysis task and then
perform operations as required.
NOTE
In the navigation tree in the left of the Analysis Task Management window, choose Theme Function >
Theme classification > ***Analysis to quickly find the *** analysis task.
Here, *** indicates the name of a specific analysis task.

If you need to... Then...

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

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 170

If you need to... Then...

Delete a Task
Select one or more tasks and click , or right-click Delete.
Tasks in Running state cannot be deleted.

Suspend a task
Select a periodic task in Waiting state and click , or right-click
Suspended.

Restore a suspended
Select a periodic task in Suspended state and click , or right-click
task
Resume.

Set the task result Click . In the displayed Task Management Parameter
expiration period. Settings dialog box, set Task result expiration period.
Tasks whose results have not been viewed before the specified task
result expiration period will expire after the period elapses. You can
click Expired to view the results of expired tasks. You can also delete
expired tasks as required.
Unit: day

Set the task execution Click . In the displayed Task Management Parameter
time threshold. Settings dialog box, set Task Execute Time Threshold.
The Nastar estimates the execution time of each new task. If the
estimated execution time is greater than the threshold, this task is
regarded as a major task. If the estimated execution time is equal to
or less than the threshold, this task is regarded as a minor task.
The Nastar supports a maximum of five concurrent tasks by default.
If the five concurrent tasks do not include any minor task, the Nastar
supports one more minor task in addition to the five concurrent tasks.
For example, if you create a minor task when there are already five
major tasks running concurrently, the Nastar also executes this minor
task concurrently.
If you create a minor task when there are already five tasks, including
some minor tasks, running concurrently, the Nastar executes this
minor task after the five tasks are completed.
Unit: minute

2.9 Querying Analysis Results

The section describes how to query the analysis results. After the analysis task is finished, you
can locate and solve the network problems through viewing the results.

Prerequisites
The progress bar of the analysis task reaches 100%.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 171

Procedure Diagram

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

Step 2 Select a task from the task list in the upper right pane.
All the analysis results of the selected task are displayed in the lower right pane.

Step 3 Select an analysis result from the result list on the lower right of the Analysis Task
Management window.
If a theme analysis task is executed more than 30 days, only result records of the latest 30 days
are displayed in the analysis result list. For example, the start time of a created MR analysis task
is September 1, 2012. If the task is executed more than 30 days (if the task execution period is
12 hours, the task is executed more than 60 times), the result record on September 1, 2012 will
be deleted and the result records of 30 days from September 2, 2012 to October 1, 2012 are
reserved when the task is executed on October 1, 2012.

Step 4 Double click or right-click the analysis result, and then choose View Analysis Result. The
analysis results window is displayed.
NOTE

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

Step 5 Query the results in the displayed window.

For details, see the *** Network Optimization chapter. *** refers to the network system such
as GSM, UMTS, or LTE.

----End

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 172

2.10 Viewing Geographic Analysis Results (Optional)

Prerequisites
Engineering parameters have been imported. For detailed operations, see Importing
Engineering Parameters.

Context
Currently, geographic display applies to the following analysis results:
l GSM neighboring cell analysis, GSM/UMTS neighboring cell analysis, GSM VIP analysis,
GSM network geographic observation, GSM terminal analysis, GSM complaint analysis
support.
l UMTS intra-frequency neighboring cell analysis, UMTS/GSM neighboring cell analysis,
UMTS inter-frequency neighboring cell analysis, UMTS VIP analysis, UMTS pilot
pollution analysis, UMTS network geographic observation, UMTS terminal analysis,
UMTS complaint analysis support.
l LTE VIP analysis, LTE complaint analysis support, and LTE network geographic
observation

Procedure
Step 1 Navigate to the result window of theme analysis tasks.
For detailed operations, see 2.9 Querying Analysis Results.

Step 2 Optional: In the displayed task analysis result window, click . The Geographic
Observation window is displayed.
This step is not required for geographic observation themes. Instead, when you query the task
results for such themes, the Geographic Observation window is directly displayed.

Step 3 Click and select sites you want to load.

Step 4 In the layer navigation tree in the Geographic Observation window, select sites and counters
you want to analyze.
If you select multiple counters, the Nastar displays the analysis results of the last selected counter.
For details about the Geographic Observation window, see 2.2.3 Interface Description:
Geographic Observation Results.

----End

2.11 Exporting Analysis Reports

This section describes how to export the analysis reports as files.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 173

Prerequisites
The analysis results interface is opened.

Context
VIP analysis results can be exported in .csv format, and the analysis results of other themes can
be exported in .csv, .xls, or .xlsx format.

NOTE

For the file in .csv format, you can open it by using Microsoft Excel or the notepad. If you use Microsoft Excel
to view or edit a file in .csv format, the information such as the time might be displayed abnormally. If you use
the notepad to view or edit a file in .csv format, however, information in the file can be displayed normally.
Therefore, you are advised to open a file in .csv format by using the notepad.

Procedure
Step 1 Click the export button in the left upper pane of the analysis window. The Save dialog box is
displayed.
NOTE

l The same VIP analysis result might be required to be exported to analysis reports of different types.
For details, see the interface description on the chapters according to the themes.
l For the VIP analysis, a dialog box that provides personal data disclaimer will be displayed before the
Save dialog box is displayed, reminding you of the illegality if you possess the personal data. You can
click OK to close the dialog box or select Do not display again so that the dialog box will not be
displayed again.

Step 2 Set the file name and specify the save path and file type. Then, click Save.
The progress of an export task is displayed in the Exported File List dialog box. You can perform
other operations during the execution of the export task.
l Only one export task can be executed at a time on one client. If more than one export task
are created, other tasks are in the waiting state and can be executed only after the running
task is executed completely or canceled.

l You can click on the right side of the progress bar to cancel an export task in the waiting
or running state so that the task is terminated and deleted from the task list. You can click
on the right side of the progress bar to delete an export task in the finished state so that
the task is deleted from the task list.

l You can click on the right side of the progress bar to view detailed information about an
export task in the finished state.

----End

2.12 FAQs
This section describes the problems and solutions to the FAQs when using the Nastar, and also
provides methods for common operations.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 174

2.12.1 What Do I Do When the Interface for Analysis Task

Management Is Blank After I Log In to the Nastar Client?

Symptom
After the Nastar client was started on a PC running the Windows operating system, the
communication between the Nastar client and server was abnormal when I attempted to log in
to the Nastar client, and consequently logging in to the client failed. After the communication
between the client and server was restored, I successfully logged in to the Nastar client but the
interface for analysis task management was blank.

Handling Procedure
Method 1

Do not perform any operation in the Are you sure you want to log out of the
terminal? dialog box displayed after the communication between the Nastar client and server
becomes abnormal. Wait until the Nastar client and server are automatically reconnected and
the Nastar client is automatically started. Then, wait approximately 5 minutes before you perform
any operation. Otherwise, some functions may fail to run properly.

Method Two

Click Yes in the Are you sure you want to log out of the terminal? dialog
box displayed after the communication between the Nastar client and server becomes abnormal.
Check that the PC running the client software can properly communicate with external networks.
Then, log in to the Nastar client again.

If the problem persists, contact Huawei technical support engineers.

2.12.2 What Can I Do If the Subscription Is Longer Than Expected?

This section describes how to resolve the problem that the Nastar window stays in the
Processing state for a long time during the data subscription on the Nastar client.

Symptom
The Nastar window stays in the Processing state for a long time during the data subscription on
the Nastar client. That is, the subscription status icon is .

Cause
l The eSAU service restarts or experience an exception.
The eSAU service is stopped or experiences an exception, causing communication
interruption between the Nastar and eSAU. After the eSAU service restarts, it does not send
the subscription success message before the restart to the Nastar. As a result, the
subscription status is Processing.
l Other causes.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 175

Solution
1. Check the log and locate the faulty node (such as eSAU).
2. Restart the eSAU service. Then, check the status of the eSAU service to ensure that the
eSAU service is functioning properly.
3. Execute the subscription task again. For details, see 2.6 Subscribing to Analysis Data.

If... Then...

The subscription switch status is . The problem is resolved.

Contact Huawei technical support.

The subscription switch status is .

2.12.3 Troubleshooting Problems Caused by Change of the

Subscriber Identity Anonymization Switch or the Encryption Key
This section describes how the change of the subscriber identity anonymization switch or the
encryption key affects the execution of VIP and complaint analysis tasks. The identity
information of a subscriber includes the subscriber's international mobile subscriber identity
(IMSI), mobile station international ISDN number (MSISDN), and international mobile
equipment identity (IMEI). This section also provides measures for you to mitigate the impact.

Prerequisites
You have the operation authority as user Administrator to change VIP subscriber identity
information.

Scenario Description
Usually, the Nastar analyzes plaintext subscriber identity information, such as the IMSI,
MSISDN, and IMEI. If a privacy and security policy for subscriber identity anonymization is
implemented on the network that houses the Nastar system, all subscriber identity information,
including the IMSI, MSISDN, and IMEI, is anonymized. In this case, the Nastar obtains and
analyzes the anonymized subscriber identity information.

If the privacy and security policy for subscriber identity anonymization on the network is
changed, the performance of the VIP and complaint analysis functions provided by the Nastar
is affected. Following describes the scenarios in which the privacy and security policy for
subscriber identity anonymization is changed:
l Scenario 1: A user implements the privacy and security policy for subscriber identity
anonymization on the network that has no privacy and security policy for subscriber identity
anonymization.
l Scenario 2: A user has implemented the privacy and security policy for subscriber identity
anonymization, but the encryption key for anonymizing subscriber identity information is
changed.
l Scenario 3: A user stops the privacy and security policy for subscriber identity
anonymization on the network.

Following describes the impacts of the preceding changes on the Nastar:

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 176

l When the subscriber identity anonymization switch on the network side is turned on or off,
or when the encryption key on the network side is changed, the encryption key stored in
theNastar system is different from the encryption key stored on the network side, and the
Nastar system cannot properly obtain or analyze information. For example, when the
encryption key is changed, the subscriber IMSI stored in the Nastar system is different from
the subscriber IMSI stored on the network side, and one VIP subscriber is mapped to
multiple anonymized subscriber IMSIs. This produces inaccurate results for VIP and
complaint analysis tasks.
l The impacts of the preceding changes on the analysis service performance of the Nastar
system are the same.

Troubleshooting Methods
Perform the following procedures based on how the change of the privacy and security policy
for subscriber identity anonymization impacts the results of VIP and complaint analysis tasks.

No. Procedure Description

1 Obtain new subscriber identity l In scenario 1, contact the operator to obtain

information, such as the IMSI, the anonymized subscriber identity
MSISDN, and IMEI information.
l In scenario 2, contact the operator to obtain
the subscriber identity information
encrypted by using the new encryption key.
l In scenario 3, contact the operator to obtain
the plaintext subscriber identity
information.

2 Change original VIP subscriber This procedure is applicable only to VIP

identity information analysis. Change the original VIP subscriber
identity information to the new VIP subscriber
identity information by using the Managing
VIP Groups function. For detailed operations,
see 2.5.6 Managing VIP Groups or VIP Users
(VIP Analysis).

3 Re-subscribe to analysis data for This procedure is applicable only to VIP

performing VIP analysis analysis. For detailed operations, see 2.6.3
Application Subscription of Analysis Data.

4 Suspend or delete existing VIP and For detailed operations, see the Follow-up
complaint analysis tasks Procedure in 2.8 Creating an Analysis Task.

5 Re-create VIP and complaint For detailed operations, see 2.8 Creating an
analysis tasks Analysis Task.
NOTE
When performing a complaint analysis task, you need
to import the new identity information of the
complaining subscriber into this task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 177

2.12.4 Supporting Historical Data Analysis on a Changed NE

This section describes how to configure the matching relationship of an NE before and after
change to ensure that the Nastar can analyze the historical data of the changed NE.

Scenario Description
The Nastar has configured the information about an NE and performed related analysis on this
NE. If this NE is changed, the Nastar cannot identify the matching relationship of this NE before
and after change. As a result, the Nastar cannot analyze the historical data of this NE.

Following describes the scenarios in which the NE is changed:

l The NE is renamed
For example, an NE abc is renamed def on the U2000/M2000, or an NE abc is deleted from
and then reconnected to the U2000/M2000 with the name of def.
l The NE is deleted from and then reconnected to the U2000/M2000
For example, an NE abc is deleted from the U2000/M2000 and then reconnected to the
U2000/M2000 with the same name (abc).
l The NE is managed by another U2000/M2000 system
For example, an NE is moved from U2000/M2000 A to U2000/M2000 B and managed by
U2000/M2000 B.

Solution
To ensure that the Nastar can analyze the historical data of the changed NE, you need to perform
the following steps to configure the matching relationship of this NE before and after change
(taking the RAN NEs as an example) :

1. Choose Maintenance > OSS Information Management.

2. In the navigation tree in the OSS Information Management window, select the OSS node
where the changed NE is located.
3. On the RAN NE List tab page in the right pane, click Select NE. The Select NE dialog
box is displayed.
4. Select the changed NE in the NE List area and then add it to the List of Selected NEs area.
5. In the Matched NE column in the List of Selected NEs area, select this NE and click
. The Select Matched NE dialog box is displayed.
6. Select the NE name before change and click OK.
7. Click OK.

2.12.5 Nastar Fails to Identify Information in Non-Specified

Languages
If the information that a user inputs into the Nastar system contains characters of a non-specified
language, the system displays an error message. The specified languages for the Nastar include
simplified Chinese and English.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 178

Symptom
If the information that a user inputs into the Nastar by using a PC contains characters of a non-
specified language, the system displays an error message.
If you name a new task using traditional Chinese characters, the system displays an error message
indicating that the characters are invalid; if the file name and save path for importing a results
file contain traditional Chinese characters, the system displays an error message indicating that
importing the results file fails.

Cause
The Nastar can identify only simplified Chinese characters and English characters.

Solution
It is recommended that a user enter only simplified Chinese characters and English characters
when the user is inputting information into the Nastar by using a PC.

2.12.6 Why Cannot the Nastar Client Be Displayed Again?

This section describes why the Nastar client cannot be displayed again after users click a result
record on the Nastar client, switch to another tool when they wait for the Nastar to display the
result, and then switch back to the Nastar client.

Symptom
Users click a result record on the Nastar client, switch to another tool when they wait for the
Nastar to display the result, and then switch back to the Nastar client. However, the Nastar client
cannot be displayed again.

Cause
The Nastar client occupies too much memory or the computer that runs the Nastar client does
not provide sufficient resources, and consequently users cannot switch from one window to
another. In fact, this problem occurs during the running of many Windows applications.

Solution
Log off or close the Nastar client, and then log in to the Nastar client again.

2.12.7 What Do I Do if the System Displays Login U2000/M2000

Failed When a Nastar Basic Data Subscription Task Fails?
After a user changes SSL Available in the OSS Information Management window on the
Nastar client, the basic data subscription task fails.

Symptom
After a user changes SSL Available in the OSS Information Management window on the
Nastar client, the basic data subscription task fails and the system displays Login U2000/
M2000 Failed. However, the U2000/M2000 still runs properly.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 179

Cause
A user needs to log in to the eSAU server and execute the setTaoService.sh script to set
communication mode after changing the communication mode between the Nastar and the
U2000/M2000 on the Nastar client.

Solution
1. Log in to the eSAU server as user ossuser.
NOTE

For an ATAE cluster system, log in to the active and standby eSAU node as user ossuser, perform
the following in the active and standby node.
2. Run the following command to switch to user root.
~> su - root
Password:Password of root
3. Run the following commands to stop eSAU services:
# cd /opt/esau
# . ./svc_profile.sh
# esau_stop
If the command output contains Stopping the system succeeded!, eSAU
services have stopped. Otherwise, run the esau_kill command to forcibly stop eSAU
services.
4. Run the following commands to set the communication mode:
# cd /opt/esau
# . ./svc_profile.sh
# cd /opt/esau/script/admin/
# sh setTaoService.sh
5. When the system displays information similar to the following, type y:
In the following displayed information, XXXX indicates disable or enable.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 180

You are about to XXXX SSL TAO configuration

Configurating TAO service will interrupt existing TAO connections
Do you want to continue? [y/n]

When the system displays the following information, setting the communication mode
succeeds:
Succeed to configurate TAO service

6. Run the following command to restart eSAU services:

# esau_start

2.12.8 Failed NE Version Upgrade Causes Failures in Subscribing

To Basic Data for Some Themes
This section describes the solution to the problem that after the NE version is upgraded, the
Nastar fails to obtain the basic data for some themes when it executes basic data subscription
tasks.

Symptom
When the Nastar executes basic data subscription tasks, it fails to obtain the basic data for some
themes, and logs show Execute MML Failed.

Cause
After the NE version is upgraded, new NE configuration data is not imported into the Nastar.
MML commands that the Nastar issues for subscribing to basic data still contain old NE version
information. Consequently the Nastar fails to obtain the basic data for some themes.

Solution
To ensure that the Nastar can properly obtain data in the preceding scenario, perform the
following operations:
1. Export NE configuration data through the U2000/M2000.
l By default, the U2000/M2000 periodically exports NE configuration data. Generally,
the period is one day.
l If you need to export NE configuration data immediately, you can do it manually. For
detailed operations, see Preparing for Obtaining Data (Common) in section Product
Documentation > Installation and Commissioning > System Installation and
Commissioning > Nastar Commissioning Guide (DL580) > Commissioning the
Function of Obtaining Data > Preparing for Obtaining Data.
2. Collect NE configuration data on the Nastar client again.
l By default, the Nastar automatically collects configuration data. The start time for
collecting configuration data is the start time of the data collection service and the period
is 6 hour by default. For example, if the start time of the data collection service is 6:00,
the next execution time is 12:00. The start time of the data collection service is the same
as the start time of the system service.
l If you need to collect configuration data immediately, and do not want to wait until the
default time for collecting configuration data, click Immediately Collect
Configuration Data on the RAN NE List tab page through the OSS information
management function. If the Nastar is executing another data collection task, the task

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 181

that you manually trigger will be automatically executed after the running task is
complete.
3. Import configuration data.
When the Nastar detects the collected configuration data, it automatically imports the data
to its database.
4. Execute failed basic data subscription tasks again.
a. Turn off the switch for the basic data that the Nastar fails to collect.
b. Turn on the switch for the basic data that you want to subscribe to again.
5. Execute failed application data subscription tasks for the related themes.
a. Turn off the switch for the application data that the Nastar fails to obtain.
b. Turn on the switch for the application data that you want to subscribe to again.

2.12.9 Data Subscription Failures in Some Themes Due to the

Reconstruction of Existing RNCs into RNC In Pools
This section provides a solution to the problem that after existing RNCs are reconstructed into
RNC In Pools, the Nastar fails to obtain basic and application data in some themes.

Symptom
When the Nastar executes basic and application data subscription tasks, it fails to obtain data in
some themes, and logs show Execute MML Failed.

Cause
After existing RNCs are reconstructed into RNC In Pools, new configuration data is not imported
into the Nastar and logical RNCs (main physical RNCs) are not updated to the NE list.
Consequently, the Nastar fails to obtain data in some themes.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 182

the next execution time is 12:00. The start time of the data collection service is the same
as the start time of the system service.
l If you need to collect configuration data immediately, and do not want to wait until the
default time for collecting configuration data, click Immediately Collect
Configuration Data on the RAN NE List tab page through the OSS information
management function. If the Nastar is executing another data collection task, the task
that you manually trigger will be automatically executed after the running task is
complete.
3. Import configuration data.
When the Nastar detects the collected configuration data, it automatically imports the data
to its database.
4. Optional: Import engineering parameters again for the network geographic observation
theme.
5. Execute failed basic data subscription tasks again.

a. Turn off the switch for the basic data that the Nastar fails to collect.
b. Turn on the switch for the basic data that you want to subscribe to again.
6. Execute failed application data subscription tasks for the related themes.

a. Turn off the switch for the application data that the Nastar fails to obtain.
b. Turn on the switch for the application data that you want to subscribe to again.

2.12.10 How Do I Resolve the Problem that the Analysis Results of

All Themes for the Cells Under the Newly Created Site Are Empty
When No Basic Subscription Is Issued Again After the Newly
Created Site Is Activated?

Symptom
If no basic subscription is issued again, the analysis results of each theme for the cells under the
newly created site on the Nastar are empty.

For example, after the newly created UMTS site is activated, if no basic subscription is issued
to the RNC where the site is located again, for the cells under the site, the UMTS coverage
analysis results and the cell performance analysis results are empty, and the number of
measurement reports in the intra-frequency neighboring cell analysis results is 0.

Cause
For the newly created site and its managed cells, the Nastar, as the upper-layer application
software, cannot automatically enable the data source subscription of the site.

Solution
After the newly created site is activated, issue basic subscription to the NE where the site is
located again.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 183

2.12.11 What Should I Do When the Percentage Counters in the Cell

Performance Analysis and the PS Core Performance Problem Cause
Analysis Exceed 100%?
This section describes how to resolve the problem that the percentage counters in the cell
performance analysis and the Root Cause Analysis for PS Core Performance Problems exceed
100%.

Symptom
l For the cell performance analysis, if users select the data analysis time period that contains
the future time when creating an analysis task and collect statistics on an exception type
by BottomN Users or BottomN Terminal Models , the total exception percentage exceeds
100%.
l For the PS Core performance problem cause analysis, if users select the data analysis time
period that contains the future time when creating an analysis task and analyze the objects
corresponding to a cause value, the total exception percentage exceeds 100%.

Cause
For the cell performance analysis and the PS core performance problem cause analysis, the
number of exceptions in terms of different dimensions are obtained by phase.

1. Obtain the number of exceptions in terms of the problem category.

2. Obtain the number of exceptions in terms of the problem object. The problem objects are
as follows:
l For the cell performance analysis: BottomN Users and BottomN Terminal Models
l For the PS Core performance problem cause analysis: TopN Old RAI, TopN
Slot,TopN old SGSN/MME IP and so on.

The preceding analysis data can be obtained from the eSAU. When the data amount is great and
the execution of the analysis task is slow, delay occurs between 1 and 2. If the data is imported
to the eSAU database during the delay period, the data amount in 2 is greater than that in 1. As
a result, the percentage obtained by dividing the data obtained in 2 by the data obtained in 1 is
greater than 100%.

Solution
When creating an analysis task, the selected data analysis time period cannot contain the future
time. That is, you can select only the existing time period for data analysis.

2.12.12 What Do I Do When NE Names in the NE Tree Are Different

from Those in the NE Details Area?
This section describes how to solve the problem causing inconsistencies between NE names in
the NE tree and those in the NE details area on the Nastar client.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 184

Symptom
NE names in the NE tree are different from those in the NE details area when you query analysis
data in the window for data maintenance and management on the Nastar client.

Cause
1. The data sources are different.
NE names in the NE tree are obtained from configuration data, whereas NE names in the
NE details area are obtained from the EAMInfo file.
2. The source data collection periods are different.
Configuration data and the EAMInfo file are obtained from the OSS. By default, the OSS
generates configuration data once every day and generates the EAMInfo file once every
two hours, and the Nastar obtains the configuration data and EAMInfo file from the OSS
once every six hours. After NE names are changed, NE names in the EAMInfo file may
have been updated while those in the configuration data may remain unchanged. As a result,
NE names in the NE tree and those in the NE details area become different.

Solution
Request the OSS administrator to manually trigger the immediate generation of configuration
data. Then, trigger the immediate collection of configuration data on the Nastar client manually,
thereby ensuring that the configuration data is consistent with data in the EAMInfo file.

2.12.13 What Do I Do When the Nastar Client Does Not Respond to

the Querying of a Created Task?

Symptom
The Nastar client does not respond to the querying of a created task.

Cause
Though the Nastar keeps being connected to the server, the server has been restarted for multiple
times. As a result, the webservice service for connecting the client to the server has changed,
causing the loss of some functions.

Solution
Log in to the Nastar client again.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 185

3 GSM Network Optimization

About This Chapter

This section describes how to perform GSM network optimization on the Nastar. Through this
function, you can perform various theme analysis functions on the Nastar, such as MR analysis,
frequency analysis, neighboring cell analysis, GSM/UMTS neighboring cell analysis, VIP
analysis, complaint analysis support, terminal analysis, and network geographic observation. It
is especially useful to users who are familiar with the Nastar basic operations. It is recommended
that you read this section when using the Nastar for the GSM network optimization. If you use
the Nastar in the first time, refer to Nastar Quick Start chapters.
3.1 GSM MR Analysis
The GSM MR analysis function in the Nastar analyzes uplink/downlink level, uplink/downlink
quality, timing advance (TA) distribution and link balance information of test cells. Through the
function, the Nastar directly displays radio link information on wireless network problems for
quickly locating problems.
3.2 GSM Frequency Analysis
The Nastar provides the interference matrix analysis function and frequency interference matrix
analysis function based on Measurement Reports (MRs) to assist users in adjusting the frequency
setting. In addition, users can plan a frequency optimization scheme based on frequency
interference matrix and judge the usability of the scheme based on frequency optimization
results. You are advised to perform neighboring cell analysis before starting frequency analysis.
This helps to improve the accuracy of neighboring cell identification and enable the Nastar to
generate a correct interference model.
3.3 GSM Neighboring Cell Analysis
On Nastar, you can identify redundant or missing neighboring GSM cells of a test cell and
incorrect priority settings by summarizing and analyzing the MRs and events sent by MSs,
configuration data, and engineering parameter data. This helps you resolve network quality
problems due to redundant neighboring GSM cells, missing neighboring GSM cells, or incorrect
priorities.
3.4 GSM/UMTS Neighboring Cell Analysis
On Nastar, you can check whether any neighboring UMTS cell of a GSM cell is missing or
redundant by summarizing and analyzing the MRs and events sent by MSs, configuration data,
and engineering parameter data. This helps you resolve network quality problems due to
redundant or missing neighboring UMTS cells.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 186

3.5 GSM Uplink Interference Analysis

The Nastar analyzes uplink levels of cells and displays signal strength of measurement ARFCNs
of certain cells in the analysis results. This provides reference for you to select appropriate
ARFCNs.

3.6 GSM Terminal Analysis

The GSM terminal analysis function enables the Nastar to analyze KPIs based on the CHR data
of terminal users. This function helps operators identify the terminals with poor performance in
the GSM network, therefore encouraging terminal manufacturers to improve the terminals with
poor performance and guide subscribers to purchase terminals with good performance. In this
case, subscribers can obtain stable services, and the subscriber satisfaction can be improved.
This function can be used to quickly locate and resolve problems. Normally there is no way to
avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used
during the troubleshooting. However, this function provides an anonymous data processing
method. You are obligated to take considerable measures, in compliance with the laws of the
countries concerned and the user privacy policies of your company, to ensure that the personal
data of users is fully protected.

3.7 GSM Cell Performance Analysis

The Nastar analyzes the call data of subscribers in abnormal cells to detect the root cause of
abnormal calls. This helps provide better services and improve subscriber satisfaction.This
function can be used to quickly locate and resolve problems. Normally there is no way to avoid
that some user data such as International Mobile Subscriber Identity (IMSI) will be used during
the troubleshooting. However, this function provides an anonymous data processing method.
You are obligated to take considerable measures, in compliance with the laws of the countries
concerned and the user privacy policies of your company, to ensure that the personal data of
users is fully protected.

3.8 GSM Network Geographic Observation

The Nastar displays the relevant information on the map based on the data collected for the entire
network to show the network coverage and distribution of traffic and abnormal events in an
intuitive and comprehensive manner.

3.9 VIP Analysis

By monitoring the indicators related to the quality of service of VIP subscribers, the Nastar helps
you identify and solve the network problems that may cause VIP complaints so that the service
quality of VIP subscribers is ensured and the satisfaction of VIP subscribers is improved.This
function can be used to quickly locate and resolve problems. Normally there is no way to avoid
that some user data such as International Mobile Subscriber Identity (IMSI) will be used during
the troubleshooting. However, this function provides an anonymous data processing method.
You are obligated to take considerable measures, in compliance with the laws of the countries
concerned and the user privacy policies of your company, to ensure that the personal data of
users is fully protected.

3.10 Complaint Analysis Support

After receiving a subscriber complaint, the Nastar can quickly searches for all call records of
the complaint subscriber in a problem cell based on the known problem cell and the key
information of the complaint subscriber. Through the analysis of causes of exceptions such as
access failure, handover failure, and abnormal call drop, the Nastar helps you locate and solve
complaint problems.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 187

3.1 GSM MR Analysis

The GSM MR analysis function in the Nastar analyzes uplink/downlink level, uplink/downlink
quality, timing advance (TA) distribution and link balance information of test cells. Through the
function, the Nastar directly displays radio link information on wireless network problems for
quickly locating problems.

3.1.1 Basics of GSM MR Analysis

This section describes the basic knowledge of GSM MR analysis, including the function,
technical specifications and feature restrictions. The basic knowledge helps you perform
operations related to GSM MR analysis. You must read this section before starting the analysis.

NOTE
For details about the service data types, definition, collection sources, application scenarios, and protection
measures, see Descriptions > Nastar Security Description > Application Security > Protecting Private
Subscriber Data in the Nastar Product Documentation.

Functions of GSM MR Analysis

This section describes the GSM MR analysis function. The GSM MR includes the following
information about test cells: 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 solve many network
problems.

Function Description
MR overview analysis

The MR overview analysis results provide the following information: an overview of the radio
network performance, the distribution of TopN TRXs and problematic TRXs of each BSC or
cell group, and the TopN TRXs for which the value of each radio link counter is the lowest. This
function also offers analysis results and suggestions.

Users can view the daily overview analysis report to learn information about the problematic
TRXs of each BSC, each cell group, and the entire network, and check the causes of the problems.
Users can also check whether other problematic TRXs exist in the cell where a TopN TRX is
located and analyze these TRXs.

The analysis results can be displayed in tables or bar charts to provide the radio link quality,
level, traffic distance distribution, and link balance. Analysis of the problems and suggestions
are provided to help you quickly analyze and locate the quality problems that occur on the
wireless network.

MR query

During network performance analysis and optimization, when problematic cells (such as a cell
whose call drop rate is high or number of handover failures is large) are found, you can query
the information about these cells and radio link information about the TRXs in the cells through
the Nastar.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 188

You can set cell objects before the query. The MR information about these cells is displayed in
the result window. The Nastar allows further query of TRXs. The comparison and query of
different TRXs in cells enable you to locate more complicated network problems effectively.

The query results are displayed in tables or bar charts to provide the radio link quality and user
distribution of each TRX.

MR comparison analysis

After network upgrade and optimization, you can compare the quality and coverage of the
network, BSC, cell group, or cell before and after antenna adjustment and parameter
modifications. You can evaluate the results of network optimization.

The analysis results are displayed in tables or bar charts.

Function Principles
The data source of GSM MR analysis is the performance data on the U2000/M2000.

Figure 3-1 shows the principles for collecting, importing, and analyzing data on the Nastar. For
detailed operations, see Table 3-1.
NOTE
Before you use the Nastar to collect and import performance data, check that the data export function has been
enabled on the U2000/M2000.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 189

Figure 3-1 Principles for analysis

Table 3-1 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

1. Issue an Nas eSA To deliver performance indicator requirements to the

Subscri applicat tar U U2000/M2000 so that the U2000/M2000 filters out the
be to ion data Ser performance data that meets the Nastar's requirements.
applicat subscrip ver After a user enables the application data subscription
ion data tion function on the Nastar client, the Nastar issues an
comma application data subscription command to the eSAU.
nd

Collect eS U20 To deliver a data-processing request to the U2000/

perform AU 00/ M2000, requesting the U2000/M2000 to filter out the
ance M20 performance data that meets the Nastar's requirements.
data 00

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 190

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Upload U2 eSA To upload the performance data that meets the Nastar's
perform 000 U requirements to the eSAU.
ance /
data M2
000

2. Issue a Nas eSA To issue a data query command to the eSAU. After a user
Check data tar U enables the data maintenance function on the Nastar
the query Ser client, the Nastar checks whether the analysis data is
integrit comma ver ready on the eSAU.
y of nd
analysi
s data Return eS Nast To return data integrity check results to the Nastar server
data AU ar and display the results on the Nastar client.
query Serv
results er

3. Issue a Nas eSA To issue a task execution request to the eSAU. After a
Create task tar U user creates an analysis task on the Nastar client, the
and executio Ser Nastar server issues a task execution command to the
execute n ver eSAU, requesting the eSAU to aggregate data.
an comma
analysi nd
s task
Upload eS Nast To aggregate the data reported by SAUs, generate data
data AU ar analysis results, and upload the data analysis results to
analysis Serv the Nastar server.
results er

4. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

TopN Counters for GSM MR Analysis

This section describes TopN KPIs related to the performance analysis. The KPIs include uplink
receive quality, downlink receive quality, uplink receive level, downlink receive level, TA
distribution, and link balance.

Received Signal Quality

The quality of received signals is divided into seven classes from 1 to 7 according to the bit error
rate. Each class corresponds to different bit error rates. Higher class indicates poorer quality of

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 191

received signals. Class 1 indicates the minimum bit error rate and the best quality of received
signals. Class 7 indicates the maximum bit error rate and the poorest quality of received signals.

Table 3-2 describes the relation between the quality classes of received signals and the bit error
rate.

Table 3-2 Relation between the quality classes of the received signals and bit error rate

Quality Bit Error Rate (%)

Class of
Received
Signals

1 [0.2, 0.4)

2 [0.4, 0.8)

3 [0.8, 1.6)

4 [1.6, 3.2)

5 [3.2, 6.4)

6 [6.4, 12.8)

7 ≥ 12.8

Received Level
The received signal level is divided into seven classes according to level values. Each class
corresponds to different ranges of received levels. Higher class indicates poorer quality of
received signals. Class 1 indicates the lowest received level and class 7 indicates the highest
received level.

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

Table 3-3 Relation between the received levels and the seven classes

Class of Received Level (dBm)

Received
Level

1 (-100, -95]

2 (-95, -90]

3 (-90, -85]

4 (-85, -80]

5 (-80, -75]

6 (-75, -70]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 192

Class of Received Level (dBm)

Received
Level

7 > -70

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

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 divided into 11
classes from 1 to 11. Table 3-4 describes the relations between classes and values of the Uplink
and Downlink Balance Level counter.

Table 3-4 Description of link balance classes

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

Downlink
Balance
Class

1 ≤ -15

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

3 -10, -9, -8

4 -7, -6, -5

5 -4, -3, -2

6 -1, 0, 1

7 2, 3, 4

8 5, 6, 7

9 8, 9, 10

10 11, 12, 13, 14

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 193

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

Downlink
Balance
Class

11 ≥ 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 class 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 class 11, the uplink
loss is excessively high or the uplink transmit power is excessively low. According to the
statistical result, you can locate the faults that may occur on the transmit and receive channels,
such as the TRX or antenna feeder.

Technical Specifications for GSM MR Analysis

This section describes the technical specifications, including the analysis ability and the range
of analysis time.

NOTE
The network scale specification for one analysis task is for reference only and is not restricted by the Nastar
software. If the network scale for one analysis task onsite exceeds this specification, however, the number
of supported analysis tasks and the duration of one analysis task will be changed.

Item Service Specifications

Execution type One-time task or periodic task

Network scale for one analysis task <= 10,000 cells

Number of allowed analysis tasks l <= 50 one-time tasks

l <= 10 periodic tasks

Time range for data in one analysis 7 days

task

Duration of one analysis task <= 5 minutes

Default duration for storing 15 days

analysis data

Maximum duration for storing 15 days

analysis data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 194

3.1.2 Preparations for GSM MR Analysis

Before starting a GSM MR analysis, check the user rights and the matching environment, and
prepare relevant data to ensure that the GSM MR analysis task is performed normally. You must
read this section before starting the analysis.

Checking the License and User Rights

l Check that you have applied for a valid license for GSM MR analysis.
l Check that you have the operation rights to subscribe to the MR analysis data upon login.
Users are advised to contact the administrator to turn on the data subscription switch
because the data subscription function has a high security requirement.
l Check that you have the operation rights to create a GSM MR analysis task upon login,
and the operation rights to operate the analyzed NEs.

Preparing Basic Data

Configuration Data

The configuration data of the NE controlling the test cell and neighboring cells is used to correctly
analyze the information about the test cell and neighboring cells and collect the analysis data of
these cells from the network during the analysis process.

If the OSS information has been already configured, the Nastar automatically and periodically
collects and imports the configuration data after the OSS and NE information is configured. You
can also manually collect the configuration data before the specified time period starts. After
the configuration data is imported, you can choose Maintenance > Data Maintenance
Management to check whether the configuration data is available in the Nastar database. For
detailed information about collecting, importing, and checking, see 2.5.2 Checking the
Integrity of Configuration Data.

After the configuration data has been successfully imported, you are advised to check the validity
of the configuration data. The purpose is to avoid expiration of configuration data due to network
adjustment. Expired configuration data may cause incorrect cell information in the analysis
result. For detailed operations, see Checking Engineering Parameters and Configuration
Data.

Checking the Matching Environment

Check that the matching U2000/M2000 version is V200R012C00 (or later), and the NE version
is BSC6900 V900R014C00 (or later) or BSC6910 V100R014C00 (or later).

3.1.3 Process of GSM MR Analysis

This section describes procedures of GSM MR analysis, and steps of each procedure.

l Prerequisite
l Procedure
l Subscription Task Parameters
l Analysis Task Parameters

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 195

Prerequisite
GSM configuration data has been imported into the Nastar Database. For details, see 3.1.2
Preparations for GSM MR Analysis.

Procedure
Figure 3-2 shows the analysis process.

Figure 3-2 Analysis process

View the Entry: Choose a task, whose status is Complete

GSM Cell and which lies in the Task Result area, from the
MR upper right area of the Analysis Task
analysis Management window.
result Procedure:
1. Right-click an analysis result of the task, and
choose MR Query from the shortcut menu.
2. Choose a cell as the object. Click OK.
3. View a GSM MR analysis result in the displayed
GSM MR Query Results window.
For details about analysis results, see Interface
Description: GSM MR Query.

Compare Entry: Choose a neighboring cell analysis task

GSM MR whose status is Complete and whose execution
analysis type is Period from the upper right area of the
results Analysis Task Management window. In the lower
right Task Result area, choose an analysis result of
the task.
Procedure:
1. Select the two results of a periodic task. Right-
click an analysis result of the task, and choose
Comparison Analysis from the shortcut menu.
2. Choose a cell as the object. Click OK.
3. View GSM MR analysis results in the displayed
GSM MR Comparison Analysis window.
For details about analysis results, see Interface
Description: GSM MR Comparison
Analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 199

No. Procedur Description Reference for

e Detailed
Operations

(5) Export a Entry: Click the icon on the toolbar in the upper 2.11 Exporting
GSM MR left part of each MR analysis results window. Analysis Reports
overview Procedure:
analysis
report 1. Click the export icon on the toolbar.
For the description of export icon, see Interface
Description: GSM MR Overview Analysis.
2. Set the export path and export format.
3. Click Save.

Subscription Task Parameters

Application Subscription

Parameter Description

Uplink Quality >= X MRs of If the proportion of MRs in which the uplink quality equals to
(%) >= Y MRs >= Z or is larger than X in all MRs exceeds Y and, at the same time,
the number of all MRs equals to or is larger than Z, 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 is the threshold. It can be any integer from 1 to 100. The
default value is 10.
Z is the threshold. It can be any integer from 1 to 9999. The
default value is 200.

Downlink Quality >= X MRs If the proportion of MRs in which the downlink quality equals
of (%) >= Y MRs >= Z to or is larger than X in all MRs exceeds Y and, at the same
time, the number of all MRs equals to or is larger than Z, 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 is the threshold. It can be any integer from 1 to 100. The
default value is 10.
Z is the threshold. It can be any integer from 1 to 9999. The
default value is 200.

Uplink Level <= X MRs of If the proportion of MRs in which the uplink level equals to
dBm(%) >= Y MRs >= Z or is smaller than X in all MRs exceeds Y and, at the same time,
the number of all MRs equals to or is larger than Z, 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 is the threshold. It can be any integer from 1 to 100. The
default value is 70.
Z is the threshold. It can be any integer from 1 to 9999. The
default value is 200.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 201

Parameter Description

Downlink Level <= X MRs If the proportion of MRs in which the downlink level equals
of dBm(%) >= Y MRs >= Z to or is smaller than X in all MRs exceeds Y and, at the same
time, the number of all MRs equals to or is larger than Z, 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 is the threshold. It can be any integer from 1 to 100. The
default value is 40.
Z is the threshold. It can be any integer from 1 to 9999. The
default value is 200.

TA >= X MRs of (%) >= Y If the proportion of MRs in which TA equals to or is larger
MRs >= Z than X in all MRs exceeds Y and, at the same time, the number
of all MRs equals to or is larger than Z, the TRX is problematic.
X is a TA value and can be set to any integer from 1 to 64. The
default value is 6.
Y is the threshold. It can be any integer from 1 to 100. The
default value is 50.
Z is the threshold. It can be any integer from 1 to 9999. The
default value is 200.

Downlink Level - Uplink If the proportion of MRs in which difference between

Level <= X MRs of dB(%) downlink level and uplink level equals to or is smaller than
>= Y and MRs >= Z X in all MRs exceeds Y and, at the same time, the number of
all MRs equals to or is larger than Z, the TRX is problematic.
X indicates the level difference. It can be -15, -10, -6, -3, or
-1. The default value is -15.
Y is the threshold. It can be any integer from 1 to 100. The
default value is 40.
Z is the threshold. It can be any integer from 1 to 9999. The
default value is 200.

Downlink Level - Uplink If the proportion of MRs in which difference between

Level >= X MRs of dB(%) downlink level and uplink level equals to or is greater than X
>= Y and MRs >= Z in all MRs exceeds Y and, at the same time, the number of all
MRs equals to or is larger than Z, the TRX is problematic.
X indicates the level difference. It can be 1, 3, 6, 10, or 15. The
default value is 15.
Y is the threshold. It can be any integer from 1 to 100. The
default value is 40.
Z is the threshold. It can be any integer from 1 to 9999. The
default value is 200.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 202

Parameter Description

TopN = X MRs >= Z Use a radio link counter to query the information about X
problematic TRXs whose performance is the poorest on the
entire network. Make sure that the number of all MRs is
greater than or equal to Z.
X is the number of TopN counters. It can be any integer from
1 to 99. The default value is 99.
Z is the threshold. It can be any integer from 1 to 9999. The
default value is 200.

Time information of one-time task

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

Delay If you do not select this parameter, the system executes the task
immediately.
If you select this parameter, the system executes the task at the time
specified in Execute on.

Execute on Time when a task is executed.

Time information of periodic task

Param Description Note

eter

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 203

Param Description Note

eter

Delay Time delayed for executing a task. NOTE

by Value range: 0 to 24. Unit: hour. l If the start time of a periodic task is
(hours) later than the current server time, the
NOTE Nastar automatically executes the task
If DST starts before a task is executed, the at the start time.
execution delay will be automatically Example: If the current server time is
updated to ensure that the task can be 01/01/2013 14:00:00, Start time is
executed at the specified time. For example, 01/02/2013, Period is 1 Day, and Delay
if you set Start time at 01:00 on a day, and by (hours) is 3, the Nastar automatically
the value of Delay by (hours) for the task executes the task at 01/03/2013
was set to 3 hours, the task was scheduled to 03:00:00.
be executed at 04:00. However, DST started
l If the start time of a periodic task is
before 02:00 on that day, and 02:00 was
earlier than the current server time, the
changed to 03:00. As a result, the value of
Nastar immediately executes the task.
Delay by (hours) for the task was
Example: The current server time is
automatically updated to 4 hours so that the
01/02/2013 14:00:00, Start time is
task was executed at 05:00 (equal to 04:00
01/01/2013, Period is 1 Day, and Delay
before DST started).
by (hours) is 3, the Nastar immediately
executes the task.
Whole If you select this parameter, it works the
day same as All Busy Time under Busy
hours.
You are not allowed set this parameter.

Busy If you select this parameter, the system

hours analyzes the data generated within
several periods of a day. You can select
a maximum of four periods. Several
continuous time points can be selected
in each period.
l All Busy: defines a whole day as
busy time.
l All Not Busy: defines no busy time.
l Invert Selection: defines inverted
time as the busy time.

3.1.4 Reference for GSM MR Analysis Interface

The interfaces for the GSM MR analysis results include GSM MR overview analysis interface,
GSM MR query interface and GSM MR comparison analysis interface. Before performing
relevant operations, familiarize yourself with the functions of the areas on interfaces.

Interface Description: GSM MR Overview Analysis

This section describes the interface for GSM MR overview analysis. Before performing relevant
operations, familiarize yourself with the functions of the areas on the interface.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 204

Opening the Window

You can enter GSM MR overview analysis window in two methods.

l Select an executed GSM MR analysis task, and double-click a result of the task in the Task
Result area.
l Select an executed GSM MR analysis task, right-click a result of the task in the Task
Result area, and choose View Analysis Result from the shortcut menu.

Main Window
The GSM MR overview analysis results can be displayed in a combination of tables and bar
charts. The query list of MR overview report, TRX list, counter bar chart, and task information
list are contained, as shown in Figure 3-3.

Figure 3-3 GSM MR overview analysis interface

N Name Description
o.

1 Button area Portals for two functions are provided:

l : Export MR analysis results of all the cells.

Set the file name, file type, and save path, and save in .csv, .xls,
or .xlsx format.

l : Export MR analysis results of all the TRXs.

Set the file name, file type, and save path, and save in .csv, .xls,
or .xlsx format.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 205

N Name Description
o.

2 Navigation Users can accurately locate the objects of an MR report on the

tree of GSM navigation tree. The Nastar provides TRX overview analysis of three
MR overview latitudes: BSC/Cell Group, TopN, and Filter Condition.
report NOTE
When users create an analysis task, in the Select NE Object tab page, select
BSC to analyze by BSC, or select Cell Group to analyze by cell group.
l BSC overview:
– Choose the BSC Overview Report node to display the number
of TopN TRXs, the number of problematic TRXs, and average
values of radio link counters of all the NEs.
– Choose a counter node under an NE node to display the
information about TopN TRXs of the NE to be analyzed, which
meet conditions of this counter.
l Cell group overview:
– Choose the Cell Group Overview Report node to display the
number of TopN TRXs, the number of problematic TRXs and
average values of radio link counters of all the cell groups.
– Choose a counter node under the cell group node to display the
information about TopN TRXs of a cell group to be analyzed,
which meet conditions of this counter.
l TopN overview:
Choose a counter node under the TopN node to display the
information of TopN TRXs with the poorest performance on the
entire network.
l Filter condition overview:
Choose a counter node under the Filter condition node to display
the information about all problematic TRXs on the entire network,
which meet conditions of this counter.
Users configure all filter conditions when they create analysis tasks.
If the number of problematic TRXs for all the counters on the navigation
tree is greater than that in the previous period, an UP arrow is displayed
next to the corresponding counter and the number of newly-added
problematic TRXs is displayed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 206

N Name Description
o.

3 Area for Display the information about TopN TRXs or problematic TRXs
TopN TRXs complying with a counter on the navigation tree in a table.
or The Nastar provides the function of highlighting MR overview reports
problematic in colors. If the number of TopN TRXs or problematic TRXs for a radio
TRXs link counter is greater than that in the previous period, display and
highlight the information about newly-added TopN TRXs in yellow.
The Nastar provides the functions of filtering and sorting. Click the
column header and choose a filtering item from the drop-down box
to display the table in a filtered way; click the column header to
display the table in the descending order.
For details, see 3.1.5 Reference for GSM MR Analysis Parameters.

4 Area for Display different results for different analysis latitudes:

TRXs l Choose BSC Overview Report or Cell Group Overview Report
to display average values of radio link counters for each BSC or cell
group.
l If you choose a counter node, the following information about the
cell where the selected TRX is located in Area 3 is displayed:
average values of all TRXs' radio link counters, average values of
all frequency bands' radio link counters, and average values of each
TRX's radio link counters.
The Nastar provides the function of highlighting MR overview
reports in colors. If a TRX meets any filter condition, it is regarded
as a problematic TRX and the Nastar highlights it in red.
The Nastar provides the functions of filtering and sorting. Click the
column header and choose a filtering item from the drop-down box
to display the table in a filtered way; click the column header to
display the table in the descending order.
For details, see 3.1.5 Reference for GSM MR Analysis Parameters.

5 Area for Display the selected information in Area 3 and Area 4 in bar charts.
counter l The X-axis coordinate indicates counter values and the Y-axis
charts coordinate indicates percentage values.
l Double-click a bar chart to zoom in and then double-click the chart
again to restore it to the normal size.
Right-click a chart and then choose an option from the shortcut
menu to perform the corresponding operation, such as modifying
the attributes of the chart, resizing, saving, and printing.

6 Task l The upper part displays basic information of the task.

information l The middle part displays related information about the cell where a
list selected TRX is located.
l The lower part displays all filter conditions a selected TRX meets.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 207

Interface Description: GSM MR Query

This section describes the interface for GSM MR query results. Before performing relevant
operations, familiarize yourself with the functions of the areas on the interface.

Opening the Window

You can enter GSM MR query result window by performing the following operations:
1. Select a finished GSM MR analysis task, right-click a result of the task in the Task
Result area, and choose MR Query from the shortcut menu.
2. Select one or multiple cells to be viewed in the displayed window.
3. Click OK and open the GSM MR Query Results window.

Main Window
The GSM MR query results can be displayed in a combination of tables and bar charts. The cell
list, TRX list, counter bar chart, and task information list are contained, as shown in Figure
3-4.

Figure 3-4 GSM MR query result interface

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 208

No. Name Description

1 Cell list Display average values of radio link counters for each cell
in tables.
The Nastar provides the functions of filtering and sorting.
Click the column header and choose a filtering item
from the drop-down box to display the table in a filtered
way; click the column header to display the table in the
descending order.
For details, see Parameters for Viewing MR Analysis
Results of GSM Cells.

2 Area for TRXs Display average values of radio link counters for all TRXs
of a cell in Area 1 in tables.
The system supports the function of highlighting MR
results in colors. If a TRX is faulty, this TRX is
highlighted in red.
For details, see Parameters for Viewing MR Analysis
Results of GSM Cells.

3 Area for counter Display the selected information in Area 1 and Area 2 in
charts bar charts.
l The X-axis coordinate indicates counter values and the
Y-axis coordinate indicates percentage values.
l Double-click a bar chart to zoom in and then double-
click the chart again to restore it to the normal size.
Right-click a chart and then choose an option from the
shortcut menu to perform the corresponding operation,
such as modifying the attributes of the chart, resizing,
saving, and printing.

4 Task information Display basic information of this task, and related

list information about the cell corresponding to the selected
TRX in Area 2.
For details, see Parameters for Viewing MR Analysis
Results of GSM Cells.

Interface Description: GSM MR Comparison Analysis

This section describes the interface for GSM MR comparison analysis. Before performing
relevant operations, familiarize yourself with the functions of the areas on the interface.

Opening the Window

1. Select a finished GSM MR analysis task, right-click two results of the task in the Task
Result area, and choose Comparison Analysis from the shortcut menu.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 209

NOTE

The premise of displaying the comparison analysis result is that the finished GSM MR analysis task
is a periodic task.
2. Select one or multiple cells to be viewed in the displayed window. Click OK to enter the
GSM MR Comparison Analysis window.
3. Perform operations as configured.

If... Then...

Select NE Object for the current 1. Select Cell, BSC or All from the upper area
GSM MR analysis task is set to BSC in the navigation tree.
2. Select one or multiple objects from the
navigation tree.
3. Click OK.

Select NE Object for the current 1. Select All, NE Group or Cell from the upper
GSM MR analysis task is set to Cell area in the navigation tree.
Group 2. Select one or multiple objects from the
navigation tree.
3. Click OK.

Main Window
The GSM MR analysis results can be displayed in a combination of tables and bar charts. The
counter information and counter charts are contained, as shown in Figure 3-5.

Figure 3-5 GSM MR comparison report interface

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 210

No. Name Description

1 Area for counter Displays the differences of radio link counters of each object
overview within two periods in tables. Area 1 and Area 2 are displayed
information in a synchronized manner.
The Nastar displays the compared counter values that indicate
performance trends 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.
For details, see Parameters for Comparing GSM MR
Analysis Results.

2 Area for counter Displays the counter comparison information about a selected
charts object of Area 1 in bar charts.
l Display detailed time periods before and after the analysis
in the upper right part of charts.
l Double-click a bar chart in Area 2 to zoom in and then
double-click the chart again to restore it to the normal size.
Right-click a chart and then choose an option from the
shortcut menu to perform the corresponding operation, such
as modifying the attributes of the chart, resizing, saving, and
printing.

3.1.5 Reference for GSM MR Analysis Parameters

This section describes the parameters for viewing GSM MR analysis results, including Viewing
GBSC Reports, Viewing the GSM Cell Group Reports, Viewing the GSM TopN TRX Reports,
Viewing the GSM MR Filter Condition Analysis Reports, Viewing the MR Analysis Results of
GSM Cells, Comparing GSM MR Analysis Results.

Parameters for Viewing GBSC Reports

This section describes the parameters related to querying the GBSC reports. You can refer to
these parameters when querying the GBSC reports.

Parameters for Querying TRXs on the Entire Network (1)

Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 211

Parameter Range Unit Description Supported NE

Version

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

TRX Count for [0,+∞) N/A Indicates the BSC6900

Average Uplink number of V900R014C00
Receive Quality TRXs with the (or later) or
average BSC6910
received signal V100R014C00
quality values of (or later)
the BTSs
exceeding the
threshold.

TRX Count for [0,+∞) N/A Indicates the BSC6900

Average number of V900R014C00
Downlink TRXs with the (or later) or
Receive Quality average BSC6910
received signal V100R014C00
quality values of (or later)
the MSs
exceeding the
threshold.

TRX Count for [0,+∞) dBm Indicates the BSC6900

Average Uplink number of V900R014C00
Receive Level TRXs with the (or later) or
average BSC6910
received levels V100R014C00
of the BTSs (or later)
exceeding the
threshold.

TRX Count for [0,+∞) dBm Indicates the BSC6900

Average number of V900R014C00
Downlink TRXs with the (or later) or
Receive Level average BSC6910
received levels V100R014C00
of the MSs (or later)
exceeding the
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 212

Parameter Range Unit Description Supported NE

Version

TRX Count for [0,+∞) N/A Indicates the BSC6900

Average TA number of V900R014C00
Distribution TRXs with the (or later) or
values of BSC6910
Average TA V100R014C00
Distribution (or later)
exceeding the
threshold.

TRX Count for [0,+∞) N/A Indicates the BSC6900

Link Balance number of V900R014C00
TRXs with the (or later) or
values of Link BSC6910
Balance V100R014C00
exceeding the (or later)
threshold.

TRX Count for [0,+∞) N/A Indicates the BSC6900

Uplink Quality number of the V900R014C00
>= X AND MR TRXs for which (or later) or
(%) >= Y% the proportion BSC6910
of the MRs in V100R014C00
which the uplink (or later)
quality is larger
than or equal to
X in all MRs
exceeds Y.
NOTE:
X and Y are the
thresholds
specified when
you create an
analysis task.

TRX Count for [0,+∞) N/A Indicates the BSC6900

Downlink number of the V900R014C00
Quality >= X TRXs for which (or later) or
AND MR(%) the proportion BSC6910
>= Y% of the MRs in V100R014C00
which the (or later)
downlink
quality is larger
than or equal to
X in all MRs
exceeds Y.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 213

Parameter Range Unit Description Supported NE

Version

TRX Count for [0,+∞) N/A Indicates the BSC6900

Uplink Level number of the V900R014C00
Grade <= X TRXs for which (or later) or
dBm AND MR the proportion BSC6910
(%) >= Y% of the MRs in V100R014C00
which the uplink (or later)
level grade is
smaller than or
equal to X in all
MRs exceeds Y.

TRX Count for [0,+∞) N/A Indicates the BSC6900

Downlink Level number of the V900R014C00
Grade <= X TRXs for which (or later) or
dBm AND MR the proportion BSC6910
(%) >= Y% of the MRs in V100R014C00
which the (or later)
downlink level
grade is smaller
than or equal to
X in all MRs
exceeds Y.

TRX Count for [0,+∞) N/A Indicates the BSC6900

TA >= X AND number of the V900R014C00
MR(%) >= Y% TRXs for which (or later) or
the proportion BSC6910
of the MRs in V100R014C00
which the TA is (or later)
larger than or
equal to X in all
MRs exceeds Y.

TRX Count for [0,+∞) N/A Indicates the BSC6900

Link Balance number of the V900R014C00
<= X dB AND TRXs for which (or later) or
MR(%) >= Y% the proportion BSC6910
of the MRs in V100R014C00
which the link (or later)
balance is
smaller than or
equal to X in all
MRs exceeds Y.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 214

Parameter Range Unit Description Supported NE

Version

TRX Count for [0,+∞) N/A Indicates the BSC6900

Link Balance number of the V900R014C00
>= X dB AND TRXs for which (or later) or
MR(%) >= Y% the proportion BSC6910
of the MRs in V100R014C00
which the link (or later)
balance is larger
than or equal to
X in all MRs
exceeds Y.

Parameters for Querying TRXs on the Entire Network (2)

Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality value of the V900R014C00
average (or later) or
received signal BSC6910
quality (full V100R014C00
rate) of the BTS. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 215

Parameter Range Unit Description Supported NE

Version

Average [0,7] N/A Indicates the BSC6900

Downlink value of the V900R014C00
Receive Quality average (or later) or
received signal BSC6910
quality (full V100R014C00
rate) of the MS. (or later)

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received level (or later) or
(full rate) of the BSC6910
BTS. V100R014C00
(or later)

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received level (or later) or
(full rate) of the BSC6910
MS. V100R014C00
(or later)

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 216

Parameters for Querying TRXs in a GBSC(1)

Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 217

Parameter Range Unit Description Supported NE

Version

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTSs V100R014C00
corresponding (or later)
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MSs V100R014C00
corresponding (or later)
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received levels (or later) or
of the BTSs BSC6910
corresponding V100R014C00
to the TopN (or later)
TRXs or
problematic
TRXs
controlled by
the BSC.

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received levels (or later) or
of the MSs BSC6910
corresponding V100R014C00
to the TopN (or later)
TRXs or
problematic
TRXs
controlled by
the BSC.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 218

Parameter Range Unit Description Supported NE

Version

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 219

Parameters for Querying TRXs in a GBSC(2)

Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Frequency Band GSM900 N/A Indicates the BSC6900

GSM1800 frequency band V900R014C00
assigned to (or later) or
BSC. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 220

Parameter Range Unit Description Supported NE

Version

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTSs V100R014C00
corresponding (or later)
to all TRXs.

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MSs V100R014C00
corresponding (or later)
to all TRXs.

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received levels (or later) or
of the BTSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received levels (or later) or
of the MSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 221

Parameter Range Unit Description Supported NE

Version

Parameters related to the basic information

Parameter Range Unit Description Supported NE
Version

Task Name 1 to 64 N/A Indicates the BSC6900

characters name of the V900R014C00
queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Start Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar starts (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

End Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar stops (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 222

Parameter Range Unit Description Supported NE

Version

Creator N/A N/A Indicates the BSC6900

creator's name V900R014C00
of the queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Parameters for Viewing 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.

Parameters Related to Querying TopN TRXs(1)

Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 223

Parameter Range Unit Description Supported NE

Version

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTSs V100R014C00
corresponding (or later)
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.

Average [0,7] N/A Indicates the BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 224

Parameter Range Unit Description Supported NE

Version

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received levels (or later) or
of the BTSs BSC6910
corresponding V100R014C00
to the TopN (or later)
TRXs or
problematic
TRXs
controlled by
the BSC.

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received levels (or later) or
of the MSs BSC6910
corresponding V100R014C00
to the TopN (or later)
TRXs or
problematic
TRXs
controlled by
the BSC.

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 225

Parameter Range Unit Description Supported NE

Version

Link Balance N/A dB Indicates the dB BSC6900

Parameters Related to Querying TopN TRXs(2)

Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 226

Parameter Range Unit Description Supported NE

Version

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Frequency Band GSM900 N/A Indicates the BSC6900

GSM1800 frequency band V900R014C00
assigned to (or later) or
BSC. BSC6910
V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 227

Parameter Range Unit Description Supported NE

Version

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTSs V100R014C00
corresponding (or later)
to all TRXs.

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MSs V100R014C00
corresponding (or later)
to all TRXs.

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received levels (or later) or
of the MSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 228

Parameter Range Unit Description Supported NE

Version

Link Balance N/A dB Indicates the dB BSC6900

Parameters related to the basic information

Parameter Range Unit Description Supported NE
Version

Task Name 1 to 64 N/A Indicates the BSC6900

characters name of the V900R014C00
queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Start Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar starts (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

End Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar stops (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 229

Parameter Range Unit Description Supported NE

Version

Task Creator N/A N/A Indicates the BSC6900

creator's name V900R014C00
of the queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Parameters for Viewing 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.

Parameters Related to Querying the TRXs on the Entire Network (1)

Parameter Range Unit Description Supported NE
Version

Cell Group ID N/A N/A Indicates the ID BSC6900

of a cell group. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Cell Group 1 to 128 N/A Indicates the BSC6900

Name characters name of a cell V900R014C00
group, for (or later) or
example, BSC6910
CELL_1. V100R014C00
(or later)

TRX Count for [0,+∞) N/A Indicates the BSC6900

Average Uplink number of TopN V900R014C00
Receive Quality TRXs with the (or later) or
average quality BSC6910
values of the V100R014C00
received signals (or later)
of the BTSs
exceeding the
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 230

Parameter Range Unit Description Supported NE

Version

TRX Count for [0,+∞) N/A Indicates the BSC6900

Average number of TopN V900R014C00
Downlink TRXs with the (or later) or
Receive Quality average quality BSC6910
values of the V100R014C00
received signals (or later)
of the MSs
exceeding the
threshold.

TRX Count for [0,+∞) dBm Indicates the BSC6900

Average Uplink number of TopN V900R014C00
Receive Level TRXs with the (or later) or
average BSC6910
received levels V100R014C00
of the BTSs (or later)
exceeding the
threshold.

TRX Count for [0,+∞) dBm Indicates the BSC6900

Average number of TopN V900R014C00
Downlink TRXs with the (or later) or
Receive Level average BSC6910
received levels V100R014C00
of the MSs (or later)
exceeding the
threshold.

TRX Count for [0,64) N/A Indicates the BSC6900

Average TA number of TopN V900R014C00
Distribution TRXs with the (or later) or
values of BSC6910
Average TA V100R014C00
Distribution (or later)
exceeding the
threshold.

TRX Count for [0,+∞) N/A Indicates the BSC6900

Link Balance number of TopN V900R014C00
TRXs with the (or later) or
values of Link BSC6910
Balance V100R014C00
exceeding the (or later)
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 231

Parameter Range Unit Description Supported NE

Version

TRX Count for [0,+∞) N/A Indicates the BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 232

Parameter Range Unit Description Supported NE

Version

TRX Count for [0,+∞) N/A Indicates the BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 233

Parameters Related to Querying the TRXs on the Entire Network (2)

Parameter Range Unit Description Supported NE
Version

Cell Group ID N/A N/A Indicates the ID BSC6900

of a cell group. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Cell Group 1 to 128 N/A Indicates the BSC6900

Name characters name of a cell V900R014C00
group, for (or later) or
example, BSC6910
CELL_1. V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality value of the V900R014C00
average (or later) or
received signal BSC6910
quality (full V100R014C00
rate) of the BTS. (or later)

Average [0,7] N/A Indicates the BSC6900

Downlink value of the V900R014C00
Receive Quality average (or later) or
received signal BSC6910
quality (full V100R014C00
rate) of the MS. (or later)

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received level (or later) or
(full rate) of the BSC6910
BTS. V100R014C00
(or later)

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received level (or later) or
(full rate) of the BSC6910
MS. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 234

Parameter Range Unit Description Supported NE

Version

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Link Balance N/A dB Indicates the dB BSC6900

Parameters Related to Querying TRXs in a Cell Group (1)

Parameter Range Unit Description Supported NE
Version

Cell Group ID N/A N/A Indicates the ID BSC6900

of a cell group. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Cell Group 1 to 128 N/A Indicates the BSC6900

Name characters name of a cell V900R014C00
group, for (or later) or
example, BSC6910
CELL_1. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 235

Parameter Range Unit Description Supported NE

Version

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name [1,64] N/A Indicates the BSC6900

name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTS V100R014C00
corresponding (or later)
to a TopN TRX
or problematic
TRX in the cell
group.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 236

Parameter Range Unit Description Supported NE

Version

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MS V100R014C00
corresponding (or later)
to a TopN TRX
or problematic
TRX in the cell
group.

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received level (or later) or
value of the BTS BSC6910
corresponding V100R014C00
to a TopN TRX (or later)
or problematic
TRX in the cell
group.

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received level (or later) or
value of the MS BSC6910
corresponding V100R014C00
to a TopN TRX (or later)
or problematic
TRX in the cell
group.

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
is used by the BSC6910
MS to advance V100R014C00
its timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 237

Parameter Range Unit Description Supported NE

Version

Parameters Related to Querying TRXs in a Cell Group (2)

Parameter Range Unit Description Supported NE
Version

Cell Group ID N/A N/A Indicates the ID BSC6900

of a cell group. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 238

Parameter Range Unit Description Supported NE

Version

Cell Group 1 to 128 N/A Indicates the BSC6900

Name characters name of a cell V900R014C00
group, for (or later) or
example, BSC6910
CELL_1. V100R014C00
(or later)

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name [1,64] N/A Indicates the BSC6900

name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Frequency Band GSM900 N/A Indicates the BSC6900

GSM1800 frequency band V900R014C00
assigned to (or later) or
BSC. BSC6910
V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 239

Parameter Range Unit Description Supported NE

Version

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTSs V100R014C00
corresponding (or later)
to all TRXs.

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MSs V100R014C00
corresponding (or later)
to all TRXs.

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received levels (or later) or
of the BTSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received levels (or later) or
of the MSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 240

Parameter Range Unit Description Supported NE

Version

Link Balance N/A dB Indicates the dB BSC6900

Parameters related to the basic information

Parameter Range Unit Description Supported NE
Version

Task Name 1 to 64 N/A Indicates the BSC6900

characters name of the V900R014C00
queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Start Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar starts (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

End Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar stops (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 241

Parameter Range Unit Description Supported NE

Version

Task Creator N/A N/A Indicates the BSC6900

creator's name V900R014C00
of the queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Parameters for Viewing GSM MR Filter Condition Analysis Reports

This section describes the parameters for querying the reports of the GSM MR filter condition
analysis. You can refer to the description when querying the GSM MR filter condition analysis
reports.

Parameters Related to Querying Problematic TRXs Involved in Filter Condition

Analysis (1)
Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 242

Parameter Range Unit Description Supported NE

Version

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTS V100R014C00
corresponding (or later)
to the
problematic
TRX.

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MS V100R014C00
corresponding (or later)
to the
problematic
TRX.

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received level of (or later) or
the BTS BSC6910
corresponding V100R014C00
to the (or later)
problematic
TRX.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 243

Parameter Range Unit Description Supported NE

Version

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received level of (or later) or
the MS BSC6910
corresponding V100R014C00
to the (or later)
problematic
TRX.

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
is used by the BSC6910
MS to advance V100R014C00
its timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 244

Parameters Related to Querying Problematic TRXs Involved in Filter Condition

Analysis (2)
Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 245

Parameter Range Unit Description Supported NE

Version

Frequency Band GSM900 N/A Indicates the BSC6900

GSM1800 frequency band V900R014C00
assigned to (or later) or
BSC. BSC6910
V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTSs V100R014C00
corresponding (or later)
to all TRXs.

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MSs V100R014C00
corresponding (or later)
to all TRXs.

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received levels (or later) or
of the BTSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received levels (or later) or
of the MSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 246

Parameter Range Unit Description Supported NE

Version

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Link Balance N/A dB Indicates the dB BSC6900

Parameters related to the basic information

Parameter Range Unit Description Supported NE
Version

Task Name 1 to 64 N/A Indicates the BSC6900

characters name of the V900R014C00
queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 247

Parameter Range Unit Description Supported NE

Version

Start Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar starts (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

End Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar stops (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

Task Creator N/A N/A Indicates the BSC6900

creator's name V900R014C00
of the queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Parameters for Viewing MR Analysis Results of GSM Cells

This section describes the parameters for viewing 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.

Parameters Related to Querying TopN TRXs and Problematic TRXs in the MR

Analysis Results (1)
Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 248

Parameter Range Unit Description Supported NE

Version

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTSs V100R014C00
corresponding (or later)
to all TRXs.

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MSs V100R014C00
corresponding (or later)
to all TRXs.

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received levels (or later) or
of the BTSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received levels (or later) or
of the MSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 249

Parameter Range Unit Description Supported NE

Version

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Link Balance N/A dB Indicates the dB BSC6900

Parameters Related to Querying TopN TRXs and Problematic TRXs in the MR

Analysis Results (2)
Parameter Range Unit Description Supported NE
Version

BSC ID 1 to 64 N/A Indicates the ID BSC6900

characters of a BSC. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 250

Parameter Range Unit Description Supported NE

Version

BSC Name 1 to 64 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

TRX ID [0,8191] N/A Index of a TRX, BSC6900

uniquely V900R014C00
identifying a (or later) or
TRX in a BSC. BSC6910
V100R014C00
(or later)

TRX No. [0,125] N/A Number of a BSC6900

TRX in a BTS. V900R014C00
The number of a (or later) or
TRX is unique BSC6910
in a BTS. V100R014C00
(or later)

Frequency Band GSM900 N/A Indicates the BSC6900

GSM1800 frequency band V900R014C00
assigned to (or later) or
BSC. BSC6910
V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports transferred over (or later) or
the channel. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 251

Parameter Range Unit Description Supported NE

Version

Average Uplink [0,7] N/A Indicates the BSC6900

Receive Quality average quality V900R014C00
of received (or later) or
signals of the BSC6910
BTSs V100R014C00
corresponding (or later)
to all TRXs.

Average [0,7] N/A Indicates the BSC6900

Downlink average quality V900R014C00
Receive Quality of received (or later) or
signals of the BSC6910
MSs V100R014C00
corresponding (or later)
to all TRXs.

Average Uplink [-110,-40] dBm Indicates the BSC6900

Receive Level average V900R014C00
received levels (or later) or
of the BTSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average [-110,-40] dBm Indicates the BSC6900

Downlink average V900R014C00
Receive Level received levels (or later) or
of the MSs BSC6910
corresponding V100R014C00
to all TRXs. (or later)

Average TA [0,64) N/A Indicates the BSC6900

Distribution weighted V900R014C00
average TA that (or later) or
the MS uses to BSC6910
advance its V100R014C00
timings of (or later)
transmissions to
the BTS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 252

Parameter Range Unit Description Supported NE

Version

Link Balance N/A dB Indicates the dB BSC6900

Parameters Related to the Basic Information (1)

Parameter Range Unit Description Supported NE
Version

Task Name 1 to 64 N/A Indicates the BSC6900

characters name of the V900R014C00
queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Start Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar starts (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

End Time N/A N/A Indicates the BSC6900

time that the V900R014C00
Nastar stops (or later) or
generating a BSC6910
task report. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 253

Parameter Range Unit Description Supported NE

Version

Creator N/A N/A Indicates the BSC6900

creator's name V900R014C00
of the queried (or later) or
performance BSC6910
analysis task. V100R014C00
(or later)

Parameters Related to the Basic Information (2)

Parameter Range Unit Description Supported NE
Version

Cell ID [0,2047] N/A Indicates the BSC6900

number of the V900R014C00
cell that the (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that the TRX (or later) or
belongs to. BSC6910
V100R014C00
(or later)

LAC [1,65533], N/A Indicates the BSC6900

[65535] location area V900R014C00
code of the cell (or later) or
where the BSC6910
selected TRX is V100R014C00
located. (or later)

CI [0,65535] N/A Indicates the ID BSC6900

of the cell where V900R014C00
the selected (or later) or
TRX is located. BSC6910
V100R014C00
(or later)

BCCH [0,1023] N/A Indicates the BSC6900

frequency V900R014C00
transmitted on (or later) or
the BCCH. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 254

Parameter Range Unit Description Supported NE

Version

BCC [0,7] N/A Indicates the BSC6900

color code of a V900R014C00
base station. (or later) or
BSC6910
V100R014C00
(or later)

NCC [0,7] N/A Indicates the BSC6900

network color V900R014C00
code. (or later) or
BSC6910
V100R014C00
(or later)

Cell Layer [1,4] N/A Indicates the BSC6900

layer where the V900R014C00
cell is located. (or later) or
BSC6910
V100R014C00
(or later)

Cell Priority [1,3] N/A Indicates the BSC6900

cell priority. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Supporting Half Yes, No N/A Indicates BSC6900

Rate whether half V900R014C00
rate is (or later) or
supported. BSC6910
V100R014C00
(or later)

Frequency N/A N/A Indicates the BSC6900

Hopping Type type of the V900R014C00
frequency (or later) or
hopping, such as BSC6910
the RF hopping V100R014C00
and baseband (or later)
frequency
hopping.

Supporting Yes, No N/A Indicates BSC6900

GPRS whether the V900R014C00
GPRS service is (or later) or
supported. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 255

Parameter Range Unit Description Supported NE

Version

Supporting Yes, No N/A Indicates BSC6900

EDGE whether the V900R014C00
EDGE service is (or later) or
supported. BSC6910
V100R014C00
(or later)

Cell Type Normal Cell, N/A Indicates the BSC6900

Concentric cell type. V900R014C00
Circle Cell, (or later) or
Enhanced Dual BSC6910
Frequency V100R014C00
Network Cell (or later)

Base Station N/A N/A Indicates the BSC6900

Type BTS type. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

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 Description
Parameter Range Unit Description Supported NE
Version

Object Name 1 to 64 N/A Names of the BSC6900

characters objects to which V900R014C00
two MR results (or later) or
to be compared BSC6910
belong. V100R014C00
(or later)

First Total [0,+∞) Number Indicates the BSC6900

Number of number of MRs V900R014C00
Measurement in the previous (or later) or
Reports period. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 256

Parameter Range Unit Description Supported NE

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 260

Parameter Range Unit Description Supported NE

Version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 261

Parameter Range Unit Description Supported NE

Version

Link Balance N/A dB Indicates the BSC6900

Difference difference V900R014C00
between the (or later) or
value of First BSC6910
Link Balance V100R014C00
and the value of (or later)
Second Link
Balance.

3.2 GSM Frequency Analysis

The Nastar provides the interference matrix analysis function and frequency interference matrix
analysis function based on Measurement Reports (MRs) to assist users in adjusting the frequency
setting. In addition, users can plan a frequency optimization scheme based on frequency
interference matrix and judge the usability of the scheme based on frequency optimization
results. You are advised to perform neighboring cell analysis before starting frequency analysis.
This helps to improve the accuracy of neighboring cell identification and enable the Nastar to
generate a correct interference model.

3.2.1 Basics of GSM Frequency Analysis

This section describes the basics of GSM frequency analysis, including the function, technical
specification and feature restriction description. The basic knowledge helps you perform GSM
frequency analysis and optimization.

Functions of GSM Frequency Analysis

The GSM frequency analysis function helps you to analyze interference matrices for test cells
and frequencies. GSM frequency analysis can generate interference matrices of analyzed cells,
which can be exported for ARFCN analysis on other tools. You can optimize the frequencies of
poor quality cells one by one based on the frequency configuration plan implemented on the live
network.

Function Description
Frequency analysis
The Nastar provides the interference traffic of each neighboring cell of a test cell and provides
the interference matrix of each cell in a report.
The mechanism of GSM frequency analysis is as follows: The Nastar identifies the interference
between a test cell and its co-channel or adjacent-channel cells, evaluates the frequency planning
results, and analyzes the cells and ARFCNs with strong interference on the current network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 262

The generated interference matrices are based on the traffic volume of the network. In this
manner, the Nastar can accurately calculate the ratio of the interference traffic to the cell traffic
during frequency adjustment.

Before performing frequency analysis, check whether any defined neighboring cell of the test
cell shares the same ARFCN and the same BSIC with other neighboring cells. If a defined
neighboring cell or an undefined neighboring cell close to the test cell shares the same ARFCN
and the same BSIC with other neighboring cells, the network stability and accuracy of frequency
analysis are affected.

GSM frequency analysis results can be exported as .csv, .xls, or .xlsx files. In addition, the GSM
interference matrix data can be exported as .txt files and imported into the Cellopt software for
re-planning network frequencies.

NOTE
To obtain the Cellopt software, log in to http://www.actix.com/, and purchase a liscence for the software.
Frequency optimization

The Nastar enables you to view GSM frequency optimization results. You can perform automatic
frequency optimization, or set parameters to perform frequency optimization manually.
l Automatic frequency optimization: In this mode, the Nastar automatically selects ARFCNs
to be optimized. This improves the efficiency of frequency optimization and reduces user
operations.
l Manual frequency optimization: You select some cells in the interference matrix related to
a frequency analysis task and set algorithm parameters related to frequency optimization.
The Nastar analyzes the frequency interference of the BCCH ARFCNs and TCH ARFCNs
selected from the candidate ARFCNs of a test cell and selects appropriate BCCH ARFCNs
and TCH ARFCNs for test cells.

Function Principles
The data source for GSM frequency analysis is the performance data and neighboring cell
measurement data collected from the U2000/M2000.

Figure 3-6 shows the principles for collecting, importing, and analyzing data on the Nastar. For
detailed operations, see Table 3-6.
NOTE
Before you use the Nastar to collect and import performance data, check that the data export function has been
enabled on the U2000/M2000.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 263

Figure 3-6 Principles for analysis

Table 3-6 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

1. Issue an Nas eSA To request the U2000/M2000 to filter out the

Subscri applicat tar U performance data and neighboring cell measurement
be to ion data Ser data that meets the Nastar's requirements. After a user
applicat subscrip ver enables the application data subscription function on the
ion data tion Nastar client, the Nastar issues an application data
comma subscription command to the eSAU.
nd

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 264

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Collect eS U20 To deliver a data-processing request to the U2000/

perform AU 00/ M2000, requesting the U2000/M2000 to filter out the
ance M20 performance data and neighboring cell measurement
data and 00 data that meets the Nastar's requirements.
neighbo
ring cell
measure
ment
data

Upload U2 eSA To upload the performance data and neighboring cell

perform 000 U measurement data that meets the Nastar's requirements
ance / to the eSAU.
data and M2
neighbo 000
ring cell
measure
ment
data

4. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 265

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

Requirements for the Network

The network must be stable while the Nastar is collecting data for GSM frequency analysis.
Otherwise, frequency analysis may be inaccurate.Table 3-7 describes network changes and their
impacts.

Table 3-7 Network changes and their respective impacts

Network Change Impacts

Adding or deleting BTSs Affects network coverage and normal handovers between cells.
As a result, the analysis results cannot accurately reflect the
current state of network.

Adjusting the antenna The cell coverage and network interference may change.
data, such as the azimuth,
tilt, and height of an
antenna

Adjusting the transmit The cell coverage and network interference may change.
power or other power-
related parameters, such
as discontinuous
transmission or power
control.

Adjusting frequency Adjustment of configuration data affects the identification of

planning, for example, defined and undefined neighboring GSM cells. As a result, the
adding new frequencies analysis results cannot reflect the actual state of network. You are
advised to keep the configuration data of the network stable
during data collection.

Adjusting handover Statistical results are affected if you change the handover
relationship and parameters and handover relationship during neighbor
handover parameters relationship data collection and optimization.

Adjusting the BSC As the BSC is responsible for collecting statistical results, the
topology or other measurement task cannot be successfully executed if the network
network topology topology is adjusted. Therefore, you are not advised to adjust the
network topology during data collection.

GSM ARFCN Spacing Rules

This section describes the spacing rules for GSM absolute radio frequency channel numbers
(ARFCNs), which facilitates frequency optimization.

Table 3-8 shows the spacing rules for GSM ARFCNs.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 266

NOTE

l The ARFCNs that violate co-site spacing rules are highlighted in pink with the legend . The

ARFCNs that violate co-cell spacing rules are highlighted in red with the legend . The ARFCNs
that violate neighboring cell spacing rules are highlighted in orange with the legend .
l The ARFCNs are highlighted by their class priorities in the following descending order: co-cell ARFCNs,
co-site ARFCNs, and neighboring cell ARFCNs. If an ARFCN violates multiple spacing rules, this ARFCN
is highlighted in the color based on its highest class priority.
l Assume that the ARFCN spacing is set to N.

l For and , the range of ARFCNs that violate spacing rules is [Current
ARFCN - N + 1, Current ARFCN + N - 1].

l For , the range of ARFCNs that violate spacing rules is [Current ARFCN - N + 1, current
ARFCN) and (Current ARFCN, Current ARFCN + N - 1].
l If N is 0, ARFCN spacing rules are not limited.

Table 3-8 Description of GSM ARFCN spacing rules

Cla Sub Description Example

ss class

Co- Betw If a BCCH ARFCN of Scenario: Three co-site cells are Cell A, Cell B, and
site een a cell violates an Cell C. The BCCH ARFCN spacing is set to 2.
BCC ARFCN spacing rule CellB_BCCH=16 and CellC_BCCH=20.
H for a BCCH ARFCN of Purpose: To set BCCH ARFCNs for Cell A.
ARF the selected co-site cell,
CNs this BCCH ARFCN is Result: According to the ARFCN spacing rule,
highlighted in pink in CellA_BCCH must not be set to 15, 16, 17, 19, 20,
BCCH. or 21. If these ARFCNs are present in the candidate
BCCH ARFCNs of Cell A, these ARFCNs are
highlighted in pink, indicating that these ARFCNs
violate the BCCH ARFCN spacing rule for co-site
cells. These ARFCNs are not recommended.

Betw If a TCH ARFCN of a Scenario: Three co-site cells are Cell A, Cell B, and
een cell violates an ARFCN Cell C. The TCH ARFCN spacing rules is set to 2.
TCH spacing rule for a TCH CellB_TCH=8, 21, and CellC_TCH=4, 13.
ARF ARFCN of the selected Purpose: To set TCH ARFCNs for Cell A.
CNs co-site cell, this TCH
ARFCN is highlighted Result: According to the ARFCN spacing rule,
in pink in TCH. CellA_TCH must not be set to 3, 4, 5, 7, 8, 9, 12, 13,
14, 20, 21, or 22. If these ARFCNs are present in the
candidate TCH ARFCNs of Cell A, these ARFCNs
are highlighted in pink, indicating that these
ARFCNs violate the TCH ARFCN spacing rule for
co-site cells. These ARFCNs are not recommended.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 267

Cla Sub Description Example

ss class

Betw l If a TCH frequency Scenario: Three co-site cells are Cell A, Cell B, and
een is displayed in pink Cell C. The spacing rules between BCCH ARFCNs
BCC in TCH if it is not and TCH ARFCNs is set to 2. CellB_BCCH=16,
H properly isolated CellC_BCCH=20, CellB_TCH=8, 21, and
ARF from the BCCH CellC_TCH=4, 13.
CNs frequency of a co- Purpose: To set a BCCH ARFCN and TCH
and site cell of the ARFCNs for Cell A.
TCH selected cell.
ARF Result: According to the ARFCN spacing rule,
l If a BCCH ARFCN CellA_TCH must not be set to 15, 16, 17, 19, 20, or
CNs violates a spacing 21; CellA_BCCH must not be set to 3, 4, 5, 7, 8, 9,
rule between BCCH 12, 13, 14, 20, 21, or 22. If these ARFCNs are
ARFCNs and TCH present in the candidate TCH ARFCNs and
ARFCNs for a TCH candidate BCCH ARFCNs of Cell A, these
ARFCN of the ARFCNs are highlighted in pink, indicating that
selected co-site cell, these ARFCNs violate the spacing rule between
this BCCH ARFCN BCCH ARFCNs and TCH ARFCNs for co-site
is highlighted in cells. These ARFCNs are not recommended.
pink in BCCH.

Co- Betw Each cell has only one -

cell een BCCH ARFCN.
BCC Therefore, no spacing
H rule is required for
ARF BCCH ARFCN of one
CNs cell. The default
spacing is 0, which
means no limitation on
ARFCNs.

Betw If a TCH ARFCN Scenario: The selected cell is Cell A. The co-cell
een violates an ARFCN TCH ARFCN spacing rules is set to 2.
TCH spacing rule for a TCH CellA_TCH=27, 51, 61.
ARF ARFCN of the selected Purpose: To set new TCH ARFCNs for Cell A.
CNs cell, this TCH ARFCN
is highlighted in red in Result: According to the ARFCN spacing rule,
TCH. CellA_TCH must not be set to 26, 28, 50, 52, 60, or
62. If these ARFCNs are present in the candidate
TCH ARFCNs of Cell A, these ARFCNs are
highlighted in red, indicating that these ARFCNs
violate the co-cell TCH ARFCN spacing rule. These
ARFCNs are not recommended.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 268

Cla Sub Description Example

ss class

Betw l If a TCH frequency Scenario: The selected cell is Cell A. The spacing
een is displayed in red in rules between the BCCH ARFCN and TCH
BCC TCH if it is not ARFCNs of one cell is set to 2. CellA_BCCH=15
H properly isolated and CellA_TCH=27, 51, 61.
ARF from the BCCH Purpose: To set a BCCH ARFCN and TCH
CNs frequency of the ARFCNs for Cell A.
and selected cell.
TCH Result: According to the ARFCN spacing rule,
l If a BCCH CellA_TCH must not be set to 14 or 16.
ARF frequency is
CNs CellA_BCCH must not be set to 26, 28, 50, 52, 60,
displayed in red in or 62. If these ARFCNs are present in the candidate
BCCH if it is not TCH ARFCNs and candidate BCCH ARFCNs of
properly isolated Cell A, these ARFCNs are highlighted in red,
from the TCH indicating that these ARFCNs violate the spacing
frequencies of the rule between the BCCH ARFCN and TCH ARFCNs
selected cell. for one cell. These ARFCNs are not recommended.

Nei Betw If a BCCH ARFCN Scenario: The serving cell is Cell A, and its defined
ghb een violates an ARFCN neighboring cells are Cell B, Cell C, and Cell D. The
orin BCC spacing rule for the spacing for BCCH ARFCNs between the serving
g H BCCH ARFCN of a cell and its neighboring cells is set to 2.
cell ARF defined neighboring CellB_BCCH=16, CellC_BCCH=19, and
CNs cell of the selected cell, CellD_BCCH=27.
this BCCH ARFCN is Purpose: To set BCCH ARFCNs for Cell A.
highlighted in orange in
BCCH. Result: According to the ARFCN spacing rule,
CellA_BCCH must not be set to 15, 16, 17, 18, 19,
20, 26, 27, or 28. If these ARFCNs are present in the
candidate BCCH ARFCNs of Cell A, these
ARFCNs are highlighted in orange, indicating that
these ARFCNs violate spacing rules for BCCH
ARFCNs between the serving cell and its
neighboring cells. These ARFCNs are not
recommended.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 269

Cla Sub Description Example

ss class

Betw If a TCH frequency is Scenario: The serving cell is Cell A, and its defined
een displayed in orange in neighboring cells are Cell B, Cell C, and Cell D. The
TCH TCH if it is not spacing for BCCH ARFCNs between the serving
ARF properly isolated from cell and its neighboring cells is set to 2.
CNs the TCH frequencies of CellB_TCH=16, 19, CellC_TCH=27, 45, and
a defined neighboring CellD_TCH=87, 102.
cell of the selected cell. Purpose: To set TCH ARFCNs for Cell A.
Result: According to the ARFCN spacing rule,
CellA_TCH must not be set to 15, 16, 17, 18, 19, 20,
26, 27, 28, 44, 45, 46, 86, 87, 88, 101, 102, or 103.
If these ARFCNs are present in the candidate TCH
ARFCNs of Cell A, these ARFCNs are highlighted
in orange, indicating that these ARFCNs violate the
spacing rule for TCH ARFCNs between the serving
cell and its neighboring cells. These ARFCNs are
not recommended.

Betw l If a TCH ARFCN Scenario: The serving cell is Cell A, and its defined
een violates a spacing neighboring cells are Cell B, Cell C, and Cell D. The
BCC rule between BCCH ARFCN spacing between the serving cell and its
H ARFCNs and TCH neighboring cells is set to 2. CellB_BCCH=16,
ARF ARFCNs for the CellC_BCCH=19, CellD_BCCH=27,
CNs BCCH ARFCN of a CellB_TCH=16, 19, CellC_TCH=27, 45, and
and defined CellD_TCH=87, 102.
TCH neighboring cell of Purpose: To set a BCCH ARFCN and TCH
ARF the selected cell, ARFCNs for Cell A.
CNs this TCH ARFCN is
highlighted in Result: According to the ARFCN spacing rule,
orange in TCH. CellA_BCCH must not be set to 15, 16, 17, 18, 19,
20, 26, 27, 28, 44, 45, 46, 86, 87, 88, 101, 102, or
l If a BCCH ARFCN 103. CellA_TCH must not be set to 15, 16, 17, 18,
violates a spacing 19, 20, 26, 27, or 28. If these ARFCNs are present
rule between BCCH in the candidate TCH ARFCNs and candidate
ARFCNs and TCH BCCH ARFCNs of Cell A, these ARFCNs are
ARFCNs for a TCH highlighted in orange, indicating that these ARFCNs
ARFCN of a violate spacing rules between BCCH ARFCNs and
defined TCH ARFCNs for the serving cell and its
neighboring cell of neighboring cells. These ARFCNs are not
the selected cell, recommended.
this BCCH ARFCN
is highlighted in
orange in BCCH.

Technical Specifications for GSM Frequency Analysis

This section describes the technical specifications, including the analysis ability and the range
of analysis time.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 270

Item Service Specifications

Execution type One-time task

Network scale for one <= 10,000 cells

analysis task

Number of allowed <= 50

analysis tasks

Time range for data in 7 days

one analysis task

Duration of one analysis <= 30 minutes

task

Default duration for 15 days

storing analysis data

Maximum duration for 15 days

storing analysis data

3.2.2 Preparations for GSM Frequency Analysis

Before starting a GSM frequency analysis task, you need to check the user rights and the
matching environment, and prepare relevant data to ensure that the GSM frequency analysis task
is performed normally. You must read this section before starting the analysis.

Checking the License and User Rights

l Check that you have applied for a valid license for GSM frequency analysis.
l Check that you have the operation rights to subscribe to GSM frequency analysis data upon
login.
You are advised to contact the administrator to turn on the data switch because the analysis
data subscription function has a high security requirement.
l Check that you have the operation rights to create a GSM frequency analysis task upon
login, and the operation rights to operate the analyzed NEs.

Preparing Basic Data

Configuration Data
The configuration data of the NE controlling the test cell allows users to correctly obtain the
performance data of test cells from the network and analyze the cell information in MRs and the
information about the following cells: cells to which subscribers have gained access, cells from
which subscribers have been released, and cells to which subscribers will be handed over.
If the OSS information has been already configured, the Nastar automatically and periodically
collects and imports the configuration data after the OSS and NE information is configured. You

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 271

can also manually collect the configuration data before the specified time period starts. After
the configuration data is imported, you can choose Maintenance > Data Maintenance
Management to check whether the configuration data is available in the Nastar database. For
detailed information about collecting, importing, and checking, see 2.5.2 Checking the
Integrity of Configuration Data.

Engineering parameters

The engineering parameters for a specific area include the longitude and latitude of the cell and
the azimuth of the antenna. You can use the information to quickly identify serving cell and
neighboring cell information during theme analysis.

In the navigation tree of the Analysis Task Management window, choose System Function >
Engineering Parameter Management. Then double-click Engineering Parameter
Management to check whether engineering parameters have been imported. If the parameters
are unavailable, you must import the engineering parameter template. The Nastar can import the
engineering parameter files in .csv, .xls, and .xlsx format, but engineering parameter fields must
be set correctly. For details about the fields and templates supported by the Nastar, see
Appendix: Engineering Parameter Templates.

After the engineering parameters are successfully imported, you are advised to check whether
the engineering parameters are consistent with the configuration data and whether the
engineering parameters are correct. For example, if the cell identification information in the
engineering parameters is not consistent with the configuration data, the TOP cell will be
repeated in the network geographic observation function.

Checking the Matching Environment

l Check that the matching U2000/M2000 version is V200R012C00 (or later), and the NE
version is BSC6900 V900R014C00 (or later) or BSC6910 V100R014C00 (or later).
l Ensure that the U2000/M2000 has the license for obtaining neighboring cell measurement
data. For detailed operations, see Commissioning the Function of Obtaining the Data >
Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Checking the
License on the U2000/M2000/GBSC in the Nastar Commissioning Guide.

3.2.3 Process of GSM Frequency Analysis

This section describes the process of GSM frequency analysis, and steps of each procedure.

l Prerequisite
l Procedure
l Subscription Task Parameters
l Analysis Task Parameters

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 272

Prerequisite
GSM configuration data and GSM engineering parameters have been imported into the Nastar
Database. For details, see 3.2.2 Preparations for GSM Frequency Analysis.

Procedure
Figure 3-7 shows the analysis process.

Figure 3-7 Analysis process

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 273

Table 3-9 Description of GSM frequency analysis procedures

N Procedure Description Reference for

o. Detailed
Operations

(1 Check the Navigation path: Choose Maintenance > Data 2.7 Checking the
) integrity of Maintenance Management Integrity of
GSM Procedure: Analysis Data
frequency
analysis 1. Set Data Type to GSM Frequency Analysis
data Data.
2. Set the query time segment.
3. Select the NE to be queried.
4. Click Query.
The query results are displayed in the right pane
of the window.
l If analysis data exists, perform (3) to create
an analysis task.
l If analysis data does not exist, request the
administrator to subscribe to the data by
performing (2).
NOTE
The data subscription function has high security
requirements. You are advised to contact the
administrator with subscription rights to perform
the subscription operation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 274

N Procedure Description Reference for

o. Detailed
Operations

(2 Subscribe NOTE 2.6 Subscribing to

) to GSM When a neighboring cell measurement task is being Analysis Data
performed, the BA2 table does not automatically update.
frequency
Ensure frequency stability of measured cells and their
analysis neighboring cells. Otherwise, errors may occur during
data cell handover and measurement data may not be accurate.
(applicatio
Navigation path: Choose Maintenance > Data
n)
Subscription Management
Procedure:
1. In the Data Subscription Management
window, click the GSM tab.
2. Select one or multiple NEs in the navigation
tree.
3. On the Neighboring Cell/Frequency
Analysis tab page, click ON.
4. In the Neighboring Cell/Frequency Analysis
Parameter Setting window, set the analysis
period. Click Next.
5. Set the parameters for the neighboring cell
measurement data task.
6. Click Complete.
The actual end time of an application
subscription task is approximately one hour later
than the end time provided in the task list. This
is because the system reserves one extra hour for
data collection to ensure the integrity of
collected data.
For details about the parameters, see
Subscription Task Parameters.
NOTE
Subject to the restriction of the NE data subscription
switch, the GSM/UMTS neighboring cell analysis and the
GSM neighboring cell analysis cannot be performed
concurrently.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 275

N Procedure Description Reference for

o. Detailed
Operations

Check the Navigation path: Choose Maintenance > Data 2.7 Checking the
integrity of Maintenance Management Integrity of
GSM Procedure: Analysis Data
frequency
analysis 1. Set Data Type to GSM Frequency Analysis
data Data.
2. Set the query time segment.
3. Select the NE to be queried.
4. Click Query.
The query results are displayed in the right pane
of the window.
l If analysis data exists, perform (3) to create
an analysis task.
l If the analysis data does not exist, contact
Huawei technical support.

(3 Create a Navigation path: Choose Theme Function > 2.8 Creating an

) GSM Basic Network Optimization > GSM Frequency Analysis Task
frequency Analysis Task from the navigation tree of the
analysis Analysis Task Management window.
task Procedure:
1. Double-click GSM Frequency Analysis Task.
2. Set the task name and task remarks. Click
Next.
3. Select the NE to be analyzed on the Select NE
Object tab.
4. Set frequency analysis parameters on the
Parameters Setting tab. Click Next.
For details, see Analysis Task Parameters.
5. Choose an analysis time range. After you set the
time range, the Nastar obtains the analysis data
generated within this time range.
6. Click Finish.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 276

N Procedure Description Reference for

o. Detailed
Operations

(4 View the Navigation path: In the upper right area of the 2.9 Querying
) GSM Analysis Task Management window, select an Analysis Results
frequency analysis task in the Finished state. In the lower right
analysis of the Task Result area, select a result record of the
result task.
Procedure:
1. Double-click an analysis result of the task.
2. View the GSM frequency analysis result in the
displayed GSM Frequency Analysis Task
window.
For details about analysis results, see Interface
Description: GSM Frequency Analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 277

N Procedure Description Reference for

o. Detailed
Operations

(5 View the Navigation path: Choose a frequency analysis task

) GSM whose status is Finished from the upper right area
frequency of the Analysis Task Management window. In the
optimizatio lower right Task Result area, choose an analysis
n result result of the task.
Procedure:
1. Right-click an analysis result of the task, and
choose Frequency Optimization from the
shortcut menu.
2. Configure the parameters related to frequency
optimization algorithm on the Algorithm
Parameters tab.
a. In the ARFCN Spacing Rule Setting area,
double-click each cell to set detailed ARFCN
spacing rules. For details, see GSM ARFCN
Spacing Rules.

b. Click to the right of BCCH ARFCN

Range Setting, TCH ARFCN Range
Setting, or VIP Cell Group Setting, and
choose a candidate ARFCN of the BCCH/
TCH and a VIP cell group.
The Nastar supports frequency analysis and
optimization in the case that identical
candidate ARFCNs of BCCHs and TCHs are
configured during the setting of BCCH
ARFCN and TCH ARFCN ranges. The
identical candidate ARFCNs are not
automatically filtered out.
The Nastar can highlight ARFCNs
according to ARFCN spacing rules. For
details, see GSM ARFCN Spacing Rules.
c. Choose an ARFCN in Last Modified
Frequency configuration.
l Original: indicates that the current
ARFCN configuration on the network is
used for frequency optimization.
l Last Modified: indicates that the
ARFCN configuration modified last time
is used for frequency optimization.
3. Click OK.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 278

N Procedure Description Reference for

o. Detailed
Operations

(6 Export the Navigation path: Click the icon on the toolbar in 2.11 Exporting
) GSM the upper left part of each analysis results window. Analysis Reports
frequency Procedure:
analysis
report 1. Click the export icon on the toolbar.
For the description of export icon, see Interface
Description: GSM Frequency Analysis.
2. Set the export path and export format.
3. Click Save.

(7 Export the Navigation path: Click the icon on the toolbar in

) GSM the upper left part of each analysis results window.
frequency Procedure:
optimizatio 1. Click the export icon on the toolbar.
n report For the description of export icon, see Interface
Description: GSM Frequency Optimization.
2. Set the export path and export format.
3. Click Save.

Subscription Task Parameters

Application Subscription

Parameter Description

Task Name Indicates the name of a created analysis task.

Duration Indicates the total duration which a measurement

task is performed.
The value is an integer from 1 to 1410.Unit: minute.
The duration time must be later than the time
calculated by (Measurement period ×15) × ([Total
number of test ARFCNs ÷ measurement step + 1]) +
15.

Measurement Interval between the ARFCNs of each group. The

period interval is 1 by default and cannot be changed.
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 2×15 minutes,
that is, 30 minutes.

Analysis Task Parameters

Basic task information

Parameter Description

Task Name Name of an analysis task.

Task Type Type of an analysis task to be created.

Remarks Description of the task.

Value range: The name contains a maximum of 200 characters.

NE information

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 282

Parameter Description

Select NE(s) NEs or cell groups to be selected for analysis.

Parameter information

Parameter Description

Number of Displays the TopN undefined neighboring cells.

undefined N can be any integer from 20 to 999. The default value is 30.
neighboring cells

Co-channel Indicates the threshold of co-channel interference.

interference C/I This parameter can be set to any integer from 6 to 15. The default value
is 12.
Unit: dB

Adjacent-channel Indicates the threshold of adjacent-channel interference.

interference C/A This parameter can be set to any integer from -12 to 0. The default value
is -6.
Unit: dB

Max. distance for Indicates the distance of the search for cells with the same BCCH
checking for co- ARFCN and BSIC as the test cell.
BCCH co-BSIC This parameter can be set to any flowing point number from 0.0 to 20.0.
neighboring cell The default value is 5.0.
(km)
Unit: km

Typical site Indicates the distance between typical base stations. The Nastar
distance calculates a threshold according to the distance, and filters analysis
results.
The parameter can be set to any value from 0.1 to 35.0. The default
value is 0.5.
Unit: km

Time information of one-time task

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 283

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

Delay If you do not select this parameter, the system executes the task
immediately.
If you select this parameter, the system executes the task at the time
specified in Execute on.

Busy hours If you do not select this parameter, the system analyzes the data generated
within all periods of day within the Date.
If you select this parameter, the system analyzes only the data generated
within certain periods of a day. You can select a maximum of four periods.
Several continuous time points can be selected in each period.

Execute on Time when a task is executed.

3.2.4 Reference for GSM Frequency Analysis Interface

The interfaces of the GSM frequency analysis include GSM frequency analysis interface and
GSM frequency optimization interface. Before performing relevant operations, familiarize
yourself with the functions of the areas on interfaces.

Interface Description: GSM Frequency Analysis

This section describes the interface for GSM frequency analysis. Before performing relevant
operations, familiarize yourself with the functions of the areas on the interface.

Opening the Window

You can enter GSM frequency analysis window in two methods.
l Select an executed GSM frequency analysis task, and double-click a result of the task in
the Task Result area.
l Select a finished GSM frequency analysis task, right-click a result of the task in the Task
Result area, and choose View Analysis Result from the shortcut menu.

Main Window
The GSM frequency analysis results can be displayed in tables. The overview information about
test cells, information about interference matrix, and information about frequency interference
matrix are contained, as shown in Figure 3-8 and Figure 3-9.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 284

Figure 3-8 Frequency analysis interface 1

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 285

N Name Description
o.

1 Button Portals for five functions are provided:

area
l : Exporting frequency analysis overview information is to export the
information about all the test cells involved in the selected analysis task.

l : Exporting the interference information about a specific test cell is

to export the mutual interference information between the test cell and its
neighboring cells and the frequency interference matrix of the test cell.

l : Exporting the information about interference matrices is to export

the information about frequency interference matrices involved in all the
test cells.
– Select Text File (txt) from File Type to export the .txt file of a
specified template of the Cellopt software. The exported result can be
imported into the Cellopt software for frequency re-planning on the
entire network.
– If serving cell base station (BS) name (Column 4) and interference cell
BS name (Column 7) are left empty in the exported document, this
means that the Nastar cannot retrieve related information in
engineering parameters and configuration data. You need to check the
integrity of engineering parameters and configuration data.

l : Exporting the check results of the interference matrix is to export

the interference matrix check results summarized by BSC and cell for all
BSCs and cells and the time check report result.

l : Exporting analysis results of possible neighboring cells is to export

the information about possible neighboring cells of all test cells.

l : Exporting interference comparison analysis reports is to export

interference comparison information about Overview Compare, BSC
Compare, and Cell Compare of objects, which are involved in two
different analysis tasks.
The steps are as follows:
1. Click the icon. In the Select Two Task to Compare dialog box, select
two task names from the drop-down list.
2. Click OK to display the Interference Compare Result window.
In the list of results, right-click Save As to save the current query
results.
All exported analysis results are saved in .csv, .xls, or .xlsx format and
exported analysis results of interference matrices also are saved in .txt format.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 286

N Name Description
o.

2 Test Cell Displays the information about all task-related test cells, the interference of
Overvie a test cell caused by co-channel or adjacent-channel neighboring cells and
w the interference of co-channel or adjacent-channel neighboring cells caused
Informat by a test cell.
ion The Nastar automatically sorts cells by interference and picks out targeted
cells, providing a basis of frequency analysis for test cells.

3 Neighbo Displays the matrix detail affected by the interference from neighboring cells
ring of the test cell selected in Area 2 to the test cell. It provides the basis for
Cell- frequency optimization.
Test Cell For details, see Parameters for Viewing GSM Frequency Analysis
Interfere Results.
nce
Matrix
Details

4 Test Displays matrix details of the interference from the test cell selected in Area
Cell- 2 to all the defined and undefined neighboring cells. It provides the basis for
Neighbo frequency optimization.
ring Cell For details, see Parameters for Viewing GSM Frequency Analysis
Interfere Results.
nce
Matrix
Details

Figure 3-9 Frequency analysis interface 2

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 287

N Name Description
o.

5 Frequency Displays the interference traffic between the test cell selected in the left
Interference list and its neighboring cells with BCCH configuration by frequencies.
Matrix For details, see Parameters for Viewing GSM Frequency Analysis
Results.

6 BCCH Displays the interfered traffic between the test cell and its co-channel or
Configured adjacent-channel neighboring cells when a frequency in Area 5 is selected
Frequency as the BCCH frequency of the test cell.
Cell List For details, see Parameters for Viewing GSM Frequency Analysis
Results.

Interface Description: GSM Frequency Optimization

This section describes the interface for GSM frequency optimization. Before performing relevant
operations, familiarize yourself with the functions of the areas on the interface.

Opening the Window

You can enter GSM frequency optimization interface by performing the following operations:
1. Select a finished GSM frequency analysis task, right-click a result of the task in the Task
Result area, and choose Frequency Optimization from the shortcut menu.
2. Set the parameters related to frequency optimization on the Algorithm Parameters tab
page, and then click OK.
NOTE

If users have queried the GSM frequency optimization report, the default settings of query conditions in
the displayed dialog box are the same as the settings of the last time. The default settings of query conditions
are saved in the \client\client\plugins\NastarPA\style\conf\FreqConf directory. The query conditions
of each frequency analysis task are saved in a file.

Main Window
The GSM frequency optimization results can be displayed in a combination of tables and charts.
The overview information about test cells, BCCH information, TCH information, bar chart of
frequency interference, and algorithm parameters are included, as shown in Figure 3-10.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 288

Figure 3-10 GSM frequency optimization interface

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 289

No. Name Description

1 Button area Portals for 10 functions are provided:

l : Add unconfigured BCCH or TCH ARFCNs.

The function of this button is to select the check box in the
Configured column for an unconfigured ARFCN.
– If an ARFCN is configured as the BCCH ARFCN for the
selected test cell, according to spacing rules of ARFCNs, this
ARFCN cannot be configured as the TCH ARFCN 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.
– If you have configured an ARFCN as a TCH ARFCN of the test
cell, the neighboring ARFCNs of this ARFCN should not be
configured as TCH ARFCNs of this cell.
– If you add an ARFCN that violates spacing rules of ARFCNs, a
dialog box is displayed. In this case, users need to click Yes to
add the ARFCN.
– You can press + to add an unconfigured TCH ARFCN.

l : Delete configured BCCH or TCH ARFCNs.

The function of this button is to deselect the check box in the
Configured column for a configured ARFCN.
You can press - or Delete to delete a configured TCH ARFCN.

l : Submit an operation request.

After users click or delete ARFCNs, click this button and perform
the submit operation to make the settings take effect.
You can press F9 to submit the TCH ARFCN modification
operation to make the settings take effect.

l : return to the previous operation result; : switch to the

next operation result.
After the submit operation, users can click these two icons to
navigate through the interfaces for displaying the interference of the
ARFCNs before and after the submit operation. This helps users
analyze the variation of the interference of the ARFCNs before and
after frequency optimization, determining the feasibility of
performing frequency optimization.

l : Export a frequency optimization result.

Set the file name, file type, and save path in the dialog box of
exporting a result.

l : Analyze spectrum usage.

View the usage of current BCCH and TCH ARFCNs to improve the
spectrum usage.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 290

No. Name Description

l : View interference comparison results before and after

frequency optimization.
The Nastar provides comparison results of three levels, including
Overview Compare, BSC Compare, and Cell Compare.
Right-click in the result list and choose Save As to save the current
result.

l : Provide the function of automatic frequency optimization.

1. Click the icon. In the displayed Optimize Parameters tab page,
configure Phase Optimize Range, ARFCN Type, and
Optimize Loop Count.
2. Click OK. Display the progress of automatic ARFCN selection
in the upper right progress bar of the interface.

You can click the button to stop automatic ARFCN

selection.

2 Test cell Shows the information about all the test cells involved in the current
overview task.
information

3 BCCH and Displays the BCCH and TCH frequency information about the selected
TCH test cell in area 2.
information l The BCCH table describes all the configured and candidate BCCH
ARFCNs of the test cell selected in Area 2.
l The TCH table describes all the configured and candidate TCH
ARFCNs of the test cell selected in Area 2.
Based on configured algorithm parameters, the Nastar calculates and
determines the ARFCNs that meet co-cell configuration rules,
ARFCNs that meet co-site configuration rules, and ARFCNs that meet
neighboring cell configuration rules, providing basic information for
frequency optimization.
The system allows you to resort the table by performing the following
operations: After you click on a column, the system to display the
table in reverse order. After you set the ascending or descending order
for the ARFCN, Maximum Interference Traffic, Interfered
Traffic, External Interference Traffic, and Interference Traffic to
VIP Cells columns, the system displays the image based on the new
rule in area 4.
For details, see Parameters for Viewing GSM Frequency
Optimization Results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 291

No. Name Description

4 Image area Shows the frequency interference information about the selected test
cell of Area 2 in a combination of bar charts and line charts.
l The X-axis coordinate is ARFCN, the left y axis is the bar chart
value, the right y axis is the line chart value, and the lower part is
the bar chart legend.
l Current indicates the information about ARFCNs of the current
serving cells; Adjacent indicates the information about ARFCNs
of neighboring cells.

5 Legends of Displays information about ARFCNs that violate the co-cell, co-site,
the or neighboring cell frequencies rules in different colors.
highlightin For details of spacing rules of ARFCNs, see GSM ARFCN Spacing
g function Rules.

6 Algorithm Displays the algorithm parameters set when frequency optimization is

parameter queried. Rules for spacing between ARFCNs and VIP cell groups are
area contained in this area.

3.2.5 Reference for GSM Frequency Analysis Parameters

This section describes the parameters for viewing GSM frequency analysis results. You can refer
to the description when viewing GSM frequency analysis results.

Parameters for Viewing GSM Frequency Analysis Results

This section describes the parameters for querying GSM Frequency Analysis results, You can
refer to the description when querying GSM Frequency Analysis results.

Overview Report of the GSM Test Cells

Parameter Range Unit Description Supported NE
Version

BSC Name 1 to 32 N/A Indicates the BSC6900

characters name of the V900R014C00
BSC that a test (or later) or
cell belongs to, BSC6910
for example, V100R014C00
BSC_1. (or later)

Test Cell 1 to 64 N/A Indicates the BSC6900

characters name of a test V900R014C00
cell, for (or later) or
example, BSC6910
Cell_1. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 292

Parameter Range Unit Description Supported NE

Version

Test Cell CGI MCC-MNC- N/A Indicates the BSC6900

LAC-CI global ID of a V900R014C00
test cell. (or later) or
MCC[000,999] BSC6910
V100R014C00
MNC[00,99] (or later)
LAC[1,65533],
[65535]
CI[0,65535]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 293

Parameter Range Unit Description Supported NE

Version

BCCH [0,1023] N/A Indicates the BSC6900

broadcast V900R014C00
control channel (or later) or
for a test cell. BSC6910
1 to 124: belong V100R014C00
to P-GSM 900; (or later)

0 to 124, 975 to
1023: belong to
E-GSM900;
0 to 124, 955 to
1023: belong to
R-GSM900;
512 to 885:
belong to
DCS1800;
512 to 810:
belong to
PCS1900;
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
GSM1800
layer.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 294

Parameter Range Unit Description Supported NE

Version

BSIC [0,77] N/A Indicates the BSC6900

base station V900R014C00
identity code of (or later) or
a test cell. BSC6910
Consists of the V100R014C00
following parts: (or later)

NCC[0,7]
BCC[0,7]
BSIC=NCC*10
+BCC

Number of Co- [0,+∞) Number Total number of BSC6900

BCCH co-BCCH V900R014C00
Neighboring neighboring (or later) or
Cells (Co- cells = Number BSC6910
BCCH defined of co-BCCH V100R014C00
neighbors and neighboring (or later)
Co-BCCH cells for the test
defined cell + Number
neighbors of of co-BCCH
tested cell's neighboring
defined cells.) cells for the
neighboring
cells

Probable [0,+∞) N/A Indicates the BSC6900

Overlapped number of MRs V900R014C00
Traffic received by the (or later) or
Interfered by test cell from the BSC6910
Co-BCCH neighboring V100R014C00
Neighboring cells that share (or later)
Cell the same BCCH
ARFCN with
the test cell.

Overlapped [0,+∞) N/A Indicates the BSC6900

Traffic number of MRs V900R014C00
Interfered by received by the (or later) or
Adjacent- test cell from the BSC6910
BCCH neighboring V100R014C00
Neighboring cells that have (or later)
Cell neighboring
ARFCNs of the
BCCH ARFCN
of the test cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 295

Parameter Range Unit Description Supported NE

Version

Probable [0,+∞) N/A Indicates the BSC6900

Overlapped number of MRs V900R014C00
Traffic received by the (or later) or
Interfered on neighboring BSC6910
Co-BCCH cells that share V100R014C00
Neighboring the same BCCH (or later)
Cell ARFCN with
the test cell.

Overlapped [0,+∞) N/A Indicates the BSC6900

Traffic number of MRs V900R014C00
Interfered on received by the (or later) or
Adjacent- neighboring BSC6910
BCCH cells that have V100R014C00
Neighboring neighboring (or later)
Cell ARFCNs of the
BCCH ARFCN
of the test cell.

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement total number of V900R014C00
Reports on Test downlink MRs (or later) or
Cell received by the BSC6910
test cell within V100R014C00
the (or later)
measurement
period.

Proximate Co- [0,+∞) km Indicates the BSC6900

Channel distance from V900R014C00
Neighboring the test cell to (or later) or
Cell Distance the nearest intra- BSC6910
frequency V100R014C00
neighboring (or later)
cell.

Interference Matrix Details (Neighboring Cell to Test Cell)

Parameter Range Unit Description Supported NE
Version

Interference 1 to 64 N/A Indicates the BSC6900

Cell characters name of a cell V900R014C00
that causes (or later) or
interference to BSC6910
the test cell. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 296

Parameter Range Unit Description Supported NE

Version

Interference [0,1023] N/A Indicates the BSC6900

Cell BCCH broadcast V900R014C00
control channel (or later) or
for an BSC6910
interfering cell. V100R014C00
1 to 124: belong (or later)
to P-GSM 900;
0 to 124, 975 to
1023: belong to
E-GSM900;
0 to 124, 955 to
1023: belong to
R-GSM900;
512 to 885:
belong to
DCS1800;
512 to 810:
belong to
PCS1900;
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
GSM1800
layer.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 297

Parameter Range Unit Description Supported NE

Version

Interference [0,77] N/A Indicates the BSC6900

Cell BSIC base station V900R014C00
identity code of (or later) or
an interfering BSC6910
cell. V100R014C00
Consists of the (or later)
following parts:
NCC[0,7]
BCC[0,7]
BSIC=NCC*10
+BCC

Neighboring Defined N/A Indicates the BSC6900

Cell Property neighboring attributes of an V900R014C00
cell, Undefined interfering cell. (or later) or
neighboring cell BSC6910
V100R014C00
(or later)

Overlapped [0,+∞) N/A Indicates the BSC6900

Traffic number of MRs V900R014C00
received by the (or later) or
test cell from the BSC6910
intra-frequency V100R014C00
neighboring (or later)
cells and
adjacent-
channel
neighboring
cells.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 298

Parameter Range Unit Description Supported NE

Version

Percentage of [0.00,100.00] % If the BCCH BSC6900

Overlapped ARFCN of the V900R014C00
Traffic test cell is set to (or later) or
Interfered by be the same as BSC6910
Co-Channel that of a V100R014C00
Neighboring neighboring (or later)
Cell on Test Cell cell, the value of
this parameter is
calculated
according to the
following
formula:
Percentage of
Co-Interference
Traffic by
Neighbor(%) =
Traffic affected
by the
interference
from a co-
channel
neighboring cell
to the test cell/
Number of
reports
generated by the
test cell during
the
measurement
period x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 299

Parameter Range Unit Description Supported NE

Version

Percentage of [0.00,100.00] % If the BCCH of BSC6900

Overlapped the test cell is set V900R014C00
Traffic to the frequency (or later) or
Interfered by adjacent to the BSC6910
Adjacent- BCCH of a V100R014C00
Channel neighboring (or later)
Neighboring cell, the value of
Cell on Test Cell this parameter is
calculated
according to the
formula:
Percentage of
Overlapped
Traffic
Interfered by
Co-Channel
Neighboring
Cell on Test Cell
(%) = Traffic
affected by the
interference
from an
adjacent-
channel
neighboring cell
to the test cell/
Number of
reports
generated by the
test cell during
measurement
period x 100%

Probable [0,+∞) N/A Indicates the BSC6900

Overlapped total traffic V900R014C00
Traffic affected by the (or later) or
Interfered by interference BSC6910
Co-BCCH from a V100R014C00
Neighboring neighboring cell (or later)
Cell to the test cell
when the BCCH
ARFCN of the
test cell is the
same as that of
the neighboring
cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 300

Parameter Range Unit Description Supported NE

Version

Overlapped [0,+∞) N/A Indicates the BSC6900

Traffic total traffic V900R014C00
Interfered by affected by the (or later) or
Adjacent- interference BSC6910
BCCH from a V100R014C00
Neighboring neighboring cell (or later)
Cell to the test cell
when the BCCH
ARFCN of the
test cell is a
neighboring
ARFCN for the
BCCH ARFCN
of the
neighboring
cell.

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the test cell to a (or later) or
neighboring BSC6910
cell. V100R014C00
(or later)

Interference Matrix Details (Test Cell to Neighboring Cell)

Parameter Range Unit Description Supported NE
Version

Interfered Cell 1 to 64 N/A Indicates the BSC6900

characters name of a cell V900R014C00
interfered by the (or later) or
test cell BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 301

Parameter Range Unit Description Supported NE

Version

Interfered Cell [0,1023] N/A Indicates the BSC6900

BCCH broadcast V900R014C00
control channel (or later) or
for an interfered BSC6910
cell. V100R014C00
1 to 124: belong (or later)
to P-GSM 900;
0 to 124, 975 to
1023: belong to
E-GSM900;
0 to 124, 955 to
1023: belong to
R-GSM900;
512 to 885:
belong to
DCS1800;
512 to 810:
belong to
PCS1900;
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
GSM1800
layer.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 302

Parameter Range Unit Description Supported NE

Version

Interfered Cell [0,77] N/A Indicates the BSC6900

BSIC base station V900R014C00
identity code of (or later) or
an interfered BSC6910
cell. V100R014C00
Consists of the (or later)
following parts:
NCC[0,7]
BCC[0,7]
BSIC=NCC*10
+BCC

Neighboring Defined N/A Indicates the BSC6900

Cell Property neighboring attributes of an V900R014C00
cell, Undefined interfered cell, (or later) or
neighboring cell such as Defined BSC6910
Neighboring V100R014C00
Cell and (or later)
Undefined
Neighboring
Cell.

Overlapped [0,+∞) N/A Indicates the BSC6900

Traffic number of MRs V900R014C00
received by the (or later) or
intra-frequency BSC6910
neighboring V100R014C00
cells and (or later)
adjacent-
channel
neighboring
cells from the
test cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 303

Parameter Range Unit Description Supported NE

Version

Percentage of [0,+∞) % If the BCCH BSC6900

Overlapped ARFCN of the V900R014C00
Traffic test cell is set to (or later) or
Interfered by be the same as BSC6910
Test Cell on Co- that of a V100R014C00
Channel neighboring (or later)
Neighboring cell, the value of
Cell this parameter is
calculated
according to the
formula:
Percentage of
Co-Interference
Traffic to
Neighbor(%) =
Traffic affected
by the
interference
from the test cell
to the co-
channel
neighboring
cell/Number of
reports
generated by the
test cell during
measurement
period x 100%
(Normalization
is used here. As
a result, the
value may be
greater than
100% for
serving cells
with small
traffic).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 304

Parameter Range Unit Description Supported NE

Version

Percentage of [0,+∞) % If the BCCH BSC6900

Overlapped ARFCN of the V900R014C00
Traffic test cell is set to (or later) or
Interfered by the frequency BSC6910
Test Cell on adjacent to the V100R014C00
Adjacent- BCCH of a (or later)
Channel neighboring
Neighboring cell, the value of
Cell this parameter is
calculated
according to the
formula:
Percentage of
Adj-
Interference
Traffic to
Neighbor(%) =
Traffic affected
by the
interference
from the test cell
to the adjacent-
channel
neighboring
cell/Number of
reports
generated by the
test cell during
measurement
period x 100%
(Normalization
is used here. As
a result, the
value may be
greater than
100% for
serving cells
with small
traffic).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 305

Parameter Range Unit Description Supported NE

Version

Probable [0,+∞) N/A Indicates the BSC6900

Overlapped total traffic V900R014C00
Traffic affected by the (or later) or
Interfered on interference BSC6910
Co-BCCH from the test cell V100R014C00
Neighboring to a neighboring (or later)
Cell cell when the
BCCH ARFCN
of the test cell is
the same as that
of the
neighboring
cell.

Overlapped [0,+∞) N/A Indicates the BSC6900

Traffic total traffic V900R014C00
Interfered on affected by the (or later) or
Adjacent- interference BSC6910
BCCH from the test cell V100R014C00
Neighboring to a neighboring (or later)
Cell cell when the
BCCH ARFCN
of the test cell is
a neighboring
ARFCN for the
BCCH ARFCN
of the
neighboring
cell.

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the test cell to an (or later) or
interfered cell. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 306

Frequency Interference Matrix

Parameter Range Unit Description Supported NE
Version

BCCH [0,1023] N/A Indicates the BSC6900

BCCH V900R014C00
ARFCNs of the (or later) or
defined and BSC6910
undefined V100R014C00
neighboring (or later)
cells of the test
cell.
1 to 124: belong
to P-GSM 900;
0 to 124, 975 to
1023: belong to
E-GSM900;
0 to 124, 955 to
1023: belong to
R-GSM900;
512 to 885:
belong to
DCS1800;
512 to 810:
belong to
PCS1900;
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 307

Parameter Range Unit Description Supported NE

Version

GSM1800
layer.

Traffic of Test [0,+∞) N/A If this ARFCN BSC6900

Cell Caused by of the test cell is V900R014C00
Neighboring set to the BCCH (or later) or
Cell ARFCN, the BSC6910
Interference value of this V100R014C00
parameter is the (or later)
total volume of
the interfered
traffic of the test
cell. The
interfered traffic
is caused by the
co-channel and
adjacent-
channel
neighboring
cells for the test
cell.

Traffic of [0,+∞) N/A If this ARFCN BSC6900

Neighboring of the test cell is V900R014C00
Cell Caused by set to the BCCH (or later) or
Test Cell ARFCN, the BSC6910
Interference value of this V100R014C00
parameter is the (or later)
total volume of
the interfered
traffic of the co-
channel and
adjacent-
channel
neighboring
cells. The
interfered traffic
is caused by the
test cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 308

Parameter Range Unit Description Supported NE

Version

Proximate Co- [0,+∞) km If this ARFCN BSC6900

Channel of the test cell is V900R014C00
Neighboring set to the BCCH (or later) or
Cell Distance ARFCN, the BSC6910
value of this V100R014C00
parameter is the (or later)
distance from
the test cell to
the nearest intra-
frequency
neighboring
cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 309

Cell List with BCCH Configured As This ARFCN

Parameter Range Unit Description Supported NE
Version

Interference [0,1023] N/A Indicates the BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 310

Parameter Range Unit Description Supported NE

Version

Interference [0,77] N/A Indicates the BSC6900

Cell BSIC base station V900R014C00
identity code of (or later) or
an interfering BSC6910
cell. V100R014C00
Consists of the (or later)
following parts:
NCC[0,7]
BCC[0,7]
BSIC=NCC*10
+BCC

Interference [0 to 2047] N/A Indicates the BSC6900

Cell ID. number of an V900R014C00
interfering cell. (or later) or
BSC6910
V100R014C00
(or later)

Interference 1 to 64 N/A Indicates the BSC6900

Cell Name characters name of a cell V900R014C00
that causes (or later) or
interference to BSC6910
the test cell. V100R014C00
(or later)

Neighboring Defined N/A Indicates the BSC6900

Cell Property neighboring attributes of an V900R014C00
cell, Undefined interfering cell, (or later) or
neighboring cell such as Defined BSC6910
Neighboring V100R014C00
Cell and (or later)
Undefined
Neighboring
Cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 311

Parameter Range Unit Description Supported NE

Version

Percentage of [0.00,100.00] % If the BCCH BSC6900

Overlapped ARFCN of the V900R014C00
Traffic test cell is the (or later) or
Interfered by same as that of a BSC6910
Co-Channel neighboring V100R014C00
Neighboring cell, the value of (or later)
Cell on Test Cell this parameter is
calculated
according to the
formula: Value
= Traffic
affected by the
interference
from the co-
channel
neighboring cell
to the test cell/
Number of
reports
generated by the
test cell during
the
measurement
period x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 312

Parameter Range Unit Description Supported NE

Version

Percentage of [0.00,100.00] % If the BCCH BSC6900

Overlapped ARFCN of the V900R014C00
Traffic test cell is set to (or later) or
Interfered by a neighboring BSC6910
Adjacent- ARFCN for the V100R014C00
Channel BCCH ARFCN (or later)
Neighboring of a neighboring
Cell on Test Cell 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 test cell/
Number of
reports
generated by the
test cell during
the
measurement
period x 100%

Probable [0,+∞) N/A Indicates the BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 313

Parameter Range Unit Description Supported NE

Version

Overlapped [0,+∞) N/A Indicates the BSC6900

Percentage of [0.00,100.00] % If the BCCH of BSC6900

Overlapped the test cell is set V900R014C00
Traffic to be the same as (or later) or
Interfered by that of a BSC6910
Test Cell on Co- neighboring V100R014C00
Channel cell, the value of (or later)
Neighboring this parameter is
Cell calculated
according to the
formula: Value
= Traffic
affected by the
interference
from the test cell
to the co-
channel
neighboring
cell/Number of
reports
generated by the
test cell during
the
measurement
period x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 314

Parameter Range Unit Description Supported NE

Version

Percentage of [0.00,100.00] % If the BCCH BSC6900

Overlapped ARFCN of the V900R014C00
Traffic test cell is set to (or later) or
Interfered by a neighboring BSC6910
Test Cell on ARFCN for the V100R014C00
Adjacent- BCCH ARFCN (or later)
Channel of a neighboring
Neighboring cell, the value of
Cell this parameter is
calculated
according to the
formula: Value
= Traffic
affected by the
interference
from the test cell
to the adjacent-
channel
neighboring
cell/Number of
reports
generated by the
test cell during
the
measurement
period x 100%

Probable [0,+∞) N/A Indicates the BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 315

Parameter Range Unit Description Supported NE

Version

Overlapped [0,+∞) N/A Indicates the BSC6900

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the test cell to a (or later) or
neighboring BSC6910
cell. V100R014C00
(or later)

Parameters for Viewing GSM Frequency Optimization Results

This section describes the parameters for viewing GSM Frequency Optimization results, You
can refer to the description when querying GSM Frequency Optimization results.

Current Measurement Cell

Parameter Range Unit Description Supported NE
Version

BSC Name 1 to 32 N/A Indicates the BSC6900

characters name of the V900R014C00
BSC that a test (or later) or
cell belongs to, BSC6910
for example, V100R014C00
BSC_1. (or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of a test V900R014C00
cell, for (or later) or
example, BSC6910
Cell_1. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 316

Parameter Range Unit Description Supported NE

Version

BCCH [0,1023] N/A Indicates the BSC6900

broadcast V900R014C00
control channel (or later) or
for a test cell. BSC6910
1 to 124: belong V100R014C00
to P-GSM 900; (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 317

Parameter Range Unit Description Supported NE

Version

LAC [1,65533], N/A Indicates the BSC6900

[65535] location area V900R014C00
code of the (or later) or
selected test BSC6910
cell. V100R014C00
(or later)

CI [0,65535] N/A Indicates the BSC6900

identification V900R014C00
code of the (or later) or
selected test BSC6910
cell. V100R014C00
(or later)

TCH N/A N/A Indicates traffic BSC6900

channels for the V900R014C00
selected test (or later) or
cell. BSC6910
V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates total BSC6900

Measurement number of MRs V900R014C00
Reports on Test on the test cell. (or later) or
Cell BSC6910
V100R014C00
(or later)

BCCH/TCH ARFCNs
Parameter Range Unit Description Supported NE
Version

Configured Yes, No N/A Indicates BSC6900

whether the V900R014C00
current ARFCN (or later) or
is configured as BSC6910
the BCCH V100R014C00
ARFCN or a (or later)
TCH ARCFN of
the selected test
cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 318

Parameter Range Unit Description Supported NE

Version

ARFCN N/A N/A Indicates the BSC6900

configured and V900R014C00
candidate (or later) or
BCCH BSC6910
ARFCNs and V100R014C00
TCH ARFCNs (or later)
of the test cell.

Cell with the N/A N/A Indicates the BSC6900

Strongest name of the cell V900R014C00
Interference that has the (or later) or
strongest BSC6910
interference V100R014C00
over the test cell. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 319

Parameter Range Unit Description Supported NE

Version

Cell Measured Yes, No N/A Indicates BSC6900

whether the cell V900R014C00
with the (or later) or
strongest BSC6910
interference V100R014C00
over the test cell (or later)
is within the
interference
matrix, that is,
whether the cell
with the
strongest
interference is
measured.
The value can be
Yes or No.
Yes indicates
that the cell with
the strongest
interference
over the test 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 test cell
is not within the
interference
matrix, that is,
the cell with the
strongest
interference is
not measured. In
such a case,

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 320

Parameter Range Unit Description Supported NE

Version

External
Interference
Traffic of this
ARFCN is
unreliable.

Maximum [0,+∞) N/A Indicates the BSC6900

Interfered maximum V900R014C00
Traffic interference (or later) or
traffic received BSC6910
by the test cell V100R014C00
when the BCCH (or later)
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN.

Total Interfered [0,+∞) N/A Indicates the BSC6900

Traffic total V900R014C00
interference (or later) or
traffic received BSC6910
from and caused V100R014C00
to other cells (or later)
when the BCCH
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN.

Interfered [0,+∞) N/A Indicates the BSC6900

Traffic total V900R014C00
interference (or later) or
traffic received BSC6910
from other cells V100R014C00
when the (or later)
BCCH/TCH of
the test cell is
configured as
the current
candidate
ARFCN.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 321

Parameter Range Unit Description Supported NE

Version

External [0,+∞) N/A Indicates the BSC6900

Interfered total V900R014C00
Traffic interference (or later) or
traffic caused to BSC6910
other cells when V100R014C00
the BCCH (or later)
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN.

Interfered [0,+∞) N/A Indicates the BSC6900

Traffic to VIP total V900R014C00
Cells interference (or later) or
traffic caused to BSC6910
other VIP cells V100R014C00
when the BCCH (or later)
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN.

Latest Total [0,+∞) N/A Indicates the BSC6900

Interfered total V900R014C00
Traffic interference (or later) or
traffic received BSC6910
from and caused V100R014C00
to other cells (or later)
when the BCCH
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN after
the latest
frequency
optimization is
performed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 322

Parameter Range Unit Description Supported NE

Version

Original Total [0,+∞) N/A Indicates the BSC6900

3.3 GSM Neighboring Cell Analysis

On Nastar, you can identify redundant or missing neighboring GSM cells of a test cell and
incorrect priority settings by summarizing and analyzing the MRs and events sent by MSs,
configuration data, and engineering parameter data. This helps you resolve network quality
problems due to redundant neighboring GSM cells, missing neighboring GSM cells, or incorrect
priorities.

3.3.1 Basics of GSM Neighboring Cell Analysis

This section describes the basics of GSM neighboring cell analysis in terms of function, authority
policies, technical specifications, and restrictions. You can refer to this section when you analyze
neighboring GSM cells.

Functions of GSM Neighboring Cell Analysis

This section describes the GSM neighboring cell analysis function. Using this function, you can
identify redundant neighboring GSM cells, missing neighboring GSM cells, and coverage
overlap by summarizing and analyzing the measurement reports (MRs) and events reported by
MSs on Nastar. This helps you resolve network quality problems due to redundant neighboring
GSM cells, missing neighboring GSM cells, and coverage overlap.

Function Description
GSM neighboring cell analysis is based on the MRs of the ARFCNs in the BA2 list reported by
MSs. The ARFCNs in the BA2 list include the BCCH ARFCNs of defined neighboring GSM

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 323

cells and undefined neighboring GSM cells. Figure 3-11 shows the process of measuring the
ARFCNs in the BA2 list.

Figure 3-11 Process of measuring the ARFCNs in the BA2 list

Run the data subscription function on Nastar, and send the BCCH ARFCNs of undefined
neighboring GSM cells to an NE. The NE sends the ARFCN information through system
messages to MSs in the serving cell. Before you perform the analysis, check whether the BCCHs
of any defined or undefined neighboring GSM cells share one BCCH ARFCN and BSIC. If the
BCCHs of two defined or undefined neighboring GSM cells share one BCCH ARFCN and BSIC,
the stability of the network and the accuracy of GSM neighboring cell analysis will be affected.

During calls, the MSs in the serving cell test the ARFCNs in the BA2 list, and send MRs to the
BSC. The BSC collects statistics on the MRs by cell-neighboring cell pair, including the BCCHs
and BSICs of defined and undefined neighboring GSM cells, how many times the absolute level
of the serving cell exceeds the preset threshold, how many times the relative level of the serving
cell exceeds the preset threshold, and quantity of MRs.

Nastar analyzes neighboring GSM cells based on the statistical results provided by the BSC, and
generates analysis results. Based on the analysis results, you can add missing neighboring GSM
cells and delete redundant neighboring GSM cells. Then, set Nastar to generate the result files
of GSM neighboring cell analysis, which serve as the suggestions on GSM network optimization.

The results of GSM neighboring cell analysis can be exported as .csv, .xls, or .xlsx files.

Nastar can display the results of GSM neighboring cell analysis and possible neighboring cell
analysis on a map and highlights the serving cell, missing neighboring GSM cells, redundant
neighboring GSM cells, and defined and undefined neighboring GSM cells in different colors.
This helps you query neighboring relationships.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 324

Function Algorithm
Based on the MRs sent by MSs, Nastar scores and arranges the defined and undefined
neighboring GSM cells in sequence. You can analyze the neighboring GSM cells based on the
sequence and result map in combination with the actual network situations, and provide
suggestions on adding missing neighboring GSM cells and deleting redundant neighboring GSM
cells.

The algorithm for analyzing neighboring GSM cells is as follows:

1. Calculate the overall priority of each neighboring GSM cell of the serving cell.
The priority of each neighboring cell is calculated based on the number of handovers
between every two neighboring cells and based on the MR-based overall priorities of
neighboring cells. Then, all neighboring cells are sorted by priority in descending order. A
higher overall priority indicates a higher ranking (priority).
2. Identify missing neighboring GSM cells.
When the priority of an undefined neighboring GSM cell is equal to or smaller than the
value of Neighboring Cell Rank No.1 (which is set when the neighboring GSM analysis
task is created), the neighboring GSM cell is considered as a missing neighboring GSM
cell.
3. Identify redundant neighboring GSM cells.
Undefined neighboring cells are inserted into the re-sorted list of defined neighboring cells,
and rank following the neighboring cells that have been re-sorted by their overall priories.
An undefined neighboring cell is identified as a redundant neighboring cell if its ranking
exceeds Constraint of Neighboring Cell Table Length or Constraint of BA2 Table
Length. All thresholds are set when the neighboring GSM cell analysis task is created.

Function Principles
GSM neighboring cell analysis is based on the performance data and neighboring cell
measurement file data on U2000/M2000.

Figure 3-12 shows the principles for collecting, importing, and analyzing data on the Nastar.
For detailed operations, see Table 3-10.
NOTE
Before you use the Nastar to collect and import performance data, check that the data export function has been
enabled on the U2000/M2000.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 325

Figure 3-12 Principles for analysis

Table 3-10 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

1. Issue an Nas eSA To request the U2000/M2000 to filter out the

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 326

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Collect eS U20 To deliver a data-processing request to the U2000/

Upload U2 eSA To upload the performance data and neighboring cell

perform 000 U measurement data that meets the Nastar's requirements
ance / to the eSAU.
data and M2
neighbo 000
ring cell
measure
ment
data

4. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 327

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

Network Requirements
During raw data collection, the network must be stable. Otherwise, the accuracy of GSM
neighboring cell analysis will be affected. Table 3-11 lists the network changes and their
respective impacts.

Table 3-11 Network changes and their respective impacts

Network Change Impacts

Adding or deleting BTSs Affects network coverage and normal handovers between cells.
As a result, the analysis results cannot accurately reflect the
current state of network.

Adjusting the antenna The cell coverage and network interference may change.
data, such as the azimuth,
tilt, and height of an
antenna

Adjusting the transmit The cell coverage and network interference may change.
power or other power-
related parameters, such
as discontinuous
transmission or power
control.

Adjusting frequency Adjustment of configuration data affects the identification of

Technical Specifications for GSM Neighboring Cell Analysis

This section describes the technical specifications, including the analysis ability and the range
of analysis time.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 328

Item Service Specifications

Execution type One-time task

Network scale for one <= 10,000 cells

analysis task

Number of allowed <= 50

analysis tasks

Time range for data in 7 days

one analysis task

Duration of one analysis <= 10 minutes

task

Default duration for 15 days

storing analysis data

Maximum duration for 15 days

storing analysis data

3.3.2 Preparations for GSM Neighboring Cell Analysis

To ensure the normal execution of a GSM neighboring cell analysis task, check your user
authority and network environment, and prepare the required raw data before starting the task.

Checking License and User Authority

l Ensure that a valid license for the GSM neighboring cell analysis function has been
obtained.
l Ensure that you have the operation rights to subscribe to GSM neighboring cell analysis
data upon login.
You are advised to contact the administrator to turn on the data switch because the analysis
data subscription function has a high security requirement.
l Ensure that your user account is authorized to create GSM neighboring cell analysis tasks,
and the operation rights to operate the analyzed NEs.

Preparing Basic Data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 329

Engineering parameter data

The engineering parameters for a specific area include the cell longitude and latitude and the
antenna azimuth. The information is used for the effective identification of neighboring cell
information and geographic display of analysis results during theme analysis.

Map file (optional)

The map file for a specific area displays the analysis result geographically. You do not need to
prepare the map file if you do not want to view the analysis result on the map.

You can import the map files in wor, tab, or sxwu format to the Nastar. If the PC is connected
to the Internet, you can view analysis results on the Google Earth. For details, see 2.5.4
Preparing the Map File (Optional).

Checking Network Environment

l Check that the matching U2000/M2000 version is V200R012C00 (or later), and the NE
version is BSC6900 V900R014C00 (or later) or BSC6910 V100R014C00 (or later).
l Ensure that the U2000/M2000 has the license for obtaining neighboring cell measurement
data and the BSC has the license for using the function 2G/3G neighboring cell auto-
optimization. For detailed operations, see Commissioning the Function of Obtaining

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 330

the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) >
Checking the License on the U2000/M2000/GBSC in Nastar Commissioning Guide.

3.3.3 Process of GSM Neighboring Cell Analysis

This section describes the process of GSM neighboring cell analysis, and steps of each procedure.

l Prerequisites
l Procedure
l Subscription Task Parameters
l Analysis Task Parameters

Prerequisites
GSM configuration data and GSM engineering parameters have been imported into the Nastar
database. For details, see 3.3.2 Preparations for GSM Neighboring Cell Analysis.

Procedure
Figure 3-13 shows the analysis process.

Figure 3-13 Analysis process

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 331

Table 3-12 Process of GSM neighboring cell analysis

No. Step Description Details

(1) Check Navigation path: Choose Maintenance > Data 2.7

GSM Maintenance Management Checking
Neighbo Procedure: the Integrity
ring Cell of Analysis
analysis 1. Choose Data Type > Basic Network Optimization Data
data > GSM Neighboring Cell Analysis Data.
2. Specify the query period.
3. Select one or multiple NEs.
4. Click Query.
The query results are displayed in the right pane of the
window.
l If analysis data exists, perform (3) to create an
analysis task.
l If analysis data does not exist, request the
administrator to subscribe to the data by
performing (2).
NOTE
The data subscription function has high security
requirements. You are advised to contact the
administrator with subscription rights to perform the
subscription operation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 332

No. Step Description Details

(2) Subscrib NOTE 2.6

e to the When a neighboring cell measurement task is being performed, Subscribing
the BA2 table does not automatically update. Ensure frequency
GSM to Analysis
stability of measured cells and their neighboring cells.
neighbor Otherwise, errors may occur during cell handover and Data
ing cell measurement data may not be accurate.
analysis
Navigation path: Choose Maintenance > Data
data
Subscription Management
(applicat
ion) Procedure:
1. In the Data Subscription Management window,
click the GSM tab.
2. Select one or multiple NEs in the navigation tree.
3. On the Neighboring Cell/Frequency Analysis tab
page, click ON.
4. In the Neighboring Cell/Frequency Analysis
Parameter Setting window, set the analysis period.
Click Next.
5. Set the parameters for the neighboring cell
measurement data task.
6. Click Complete.
The actual end time of an application subscription task
is approximately one hour later than the end time
provided in the task list. This is because the system
reserves one extra hour for data collection to ensure
the integrity of collected data.
For details about the parameters, see Subscription
Task Parameters.
NOTE
Subject to the restriction of the NE data subscription switch, the
GSM/UMTS neighboring cell analysis and the GSM
neighboring cell analysis cannot be performed concurrently.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 333

No. Step Description Details

Check Navigation path: Choose Maintenance > Data 2.7

(3) Create a Navigation path: In the Analysis Task Management 2.8 Creating
GSM window, choose Theme Function > Basic Network an Analysis
neighbor Optimization > GSM Neighboring Cell Analysis Task
ing cell Task from the navigation tree.
analysis Procedure:
task
1. Double-click GSM Neighboring Cell Analysis
Task.
2. Set the task name and remarks. Click Next.
3. Select NEs and cell groups on the Select NE(s) tab
page.
4. On the Parameter Settings tab page, set parameters.
Click Next.
5. Specify the analysis period. Nastar obtains the data of
the analysis period.
6. Click Finish.
For details about the parameters, see Analysis Task
Parameters.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 334

No. Step Description Details

(4) View Function: By viewing the check result of neighboring 2.9

GSM GSM cells, you can learn the redundant or missing Querying
neighbor configuration of the neighboring cells. This helps you Analysis
ing cell configure missing neighboring cells and delete redundant Results
analysis neighboring cells.
results Navigation path: In the upper right area of the Analysis
Task Management window, select an analysis task in the
Finished state. In the lower right of the Task Result area,
select a result record of the task.
Procedure:
1. Double-click the result of the task.
2. In the GSM Neighboring Cell Analysis dialog box,
view the GSM neighboring cell analysis results.
For details about the dialog box, see Interface
Description: GSM Neighboring Cell Analysis.

(5) View Function: By viewing the analysis results of possible

GSM neighboring GSM cells, you can quickly learn all possible
possible neighboring GSM cells and optimize neighbor
neighbor relationships based on the results.
ing cell Navigation path: In the Analysis Task Management
analysis window, select an inter-RAT neighboring cell analysis
results task whose state is Finished, and select the result of the
task in the Task Result area.
Procedure:
1. Double-click the result of the task.
2. In the GSM Possible Neighboring Cell Analysis
dialog box, view the GSM possible neighboring cell
analysis results.
For details about the dialog box, see Interface
Description: Possible GSM Neighboring Cell
Analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 335

No. Step Description Details

(6) View Function: This function allows you to check whether the
GSM selected cell has co-BCCH and co-BSIC neighboring
Co- cells within all the cells having neighbor relationships
BCCH with the selected cell or within the cells that are physically
and Co- adjacent to the selected cell. Then, you can determine
BSIC whether to modify the BCCH or BSIC frequency
Neighbo information about the selected cell based on the check
ring Cell result.
Analysis Navigation path: In the Analysis Task Management
Results window, select an inter-RAT neighboring cell analysis
task whose state is Finished, and select the result of the
task in the Task Result area.
Procedure:
1. Double-click the result of the task.
2. In the Co-BCCH and Co-BSIC Check Result dialog
box, view the GSM possible neighboring cell analysis
results.
For details about the dialog box, see Interface
Description: GSM Intra-Frequency Co-BSIC Cell
Analysis.

(7) GSM Function: This function allows you to check whether the
Intra- selected cell has co-BCCH cells within all the
Frequen neighboring cells of the selected cell. Then, you can
cy determine whether to modify the BCCH frequency
Neighbo information about the selected cell based on the check
ring Cell result.
Analysis Navigation path: In the Analysis Task Management
Results window, select an inter-RAT neighboring cell analysis
task whose state is Finished, and select the result of the
task in the Task Result area.
Procedure:
1. Double-click the result of the task.
2. In the Neighboring Cells Co-BCCH Analysis
Result dialog box, view the GSM possible
neighboring cell analysis results.
For details about the dialog box, see Interface
Description: GSM Intra-Frequency Neighboring
Cell Analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 336

No. Step Description Details

(8) Export Navigation path: Click the icon on the toolbar in the 2.11
Neighbo upper left part of each analysis results window. Exporting
ring Cell Procedure: Analysis
Analysis Reports
reports 1. Click Interface Description: GSM Neighboring
Cell Analysis in the toolbar.
2. Set the save path and format of the analysis report.
3. Click Finish.

Subscription Task Parameters

Application Subscription

Advance Counter period The U2000/M2000 collects performance data based

Parameters on various counter periods. The Nastar collects
Settings performance data based on two counter periods: 30
minutes and 60 minutes.
Value range: 30 and 60. Unit: minute.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 339

Parameter Description

Duration Indicates the total duration which a measurement

Measurement Interval between the ARFCNs of each group. The

Analysis Task Parameters

Basic task information

Parameter Description

Task Name Name of an analysis task.

Task Type Type of an analysis task to be created.

Remarks Description of the task.

Value range: The name contains a maximum of 200 characters.

NE information

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 340

Parameter Description

Select NE(s) NEs or cell groups to be selected for analysis.

Parameter Setting Information

Parameter Description

Missing Neighboring Indicates the lower threshold of the neighboring cell

Neighboring cell ranking sequence. All the undefined neighboring cells whose
Cell number sequence numbers are smaller than or equal to the value of
Parameters this parameter are regarded as missing neighboring cells.
This parameter can be set to any integer from 1 to 32. The
default value is 10.

Redundant BA2 table Indicates the limitation on the number of test ARFCNs of
Neighboring length limit neighboring cells.
Cell This parameter can be set to any integer from 1 to 32. The
Parameters default value is 20.

Neighboring Indicates the limitation on the number of neighboring cells.

cell table This parameter can be set to any integer from 1 to 64. The
length limit default value is 50.
This parameter and BA2 table length limit are used to
determine whether a neighboring cell is redundant. A
neighboring cell is regarded as redundant if it does not meet
either of the two conditions.

Result Display the Indicates that only the TopN undefined neighboring cells are
Display number of displayed.
Parameters undefined N can be any integer from 20 to 50. The default value is 30.
neighboring
cells

Other Super- Specifies the threshold for the distance to a super-far

Parameter distance neighboring cell.
Settings threshold The value of this parameter ranges from 0 to 50000 (unit:
meter). The default value of this parameter is 5000.

Time information of one-time task

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 341

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

Delay If you do not select this parameter, the system executes the task
immediately.
If you select this parameter, the system executes the task at the time
specified in Execute on.

Execute on Time when a task is executed.

3.3.4 Reference for GSM Neighboring Cell Analysis Interface

This chapter describes the interfaces for GSM neighboring cell analysis, possible GSM
neighboring cell analysis, GSM intra-frequency co-BSIC cell analysis, and GSM intra-frequency
neighboring cell analysis. Familiarize yourself with the functions of each area in these interfaces
before you perform the related operations.

Interface Description: GSM Neighboring Cell Analysis

This section describes the interface for GSM neighboring cell analysis. Before you perform the
related operations, familiarize yourself with the functions of each area in this interface.

Opening the Window

Two modes are provided for navigating to the interface:
l Select an executed GSM neighboring cell analysis task, and double-click a result of the
task in the Task Result area.
l Select an executed GSM neighboring cell analysis task, right-click a result of the task in
the Task Result area, and choose View Analysis Result from the shortcut menu.

Main Window
In the main window, the GSM neighboring cell analysis results are displayed in charts and lists,
such as the list of test cells, list of neighboring GSM cells, bar chart, and line chart, as shown in
Figure 3-14.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 342

Figure 3-14 Interface for GSM neighboring cell analysis

No Area Description
.

1 List of test Lists the information about each test cell. You can press Ctrl+F to search
cells in the list, or right-click in the list and choose Save As from the shortcut
menu to save the list.
The Nastar provides the functions of filtering and sorting. Click the
column header and choose a filtering item from the drop-down box to
display the table in a filtered way; click the column header to display
the table in the descending order.

2 List of Lists all defined neighboring GSM cells of all test cells in the list of test
defined cells.
neighborin l Select the User Modify check box of a defined neighboring GSM
g GSM cell. The system automatically saves the modification and reads the
cells modified data when you open the analysis report next time.
If no operation is performed, the system reads the list information
from the database when you open the analysis report next time. The
modified information is saved as a file in the installation path of the
Nastar client. The file will be automatically deleted when the analysis
task is deleted.
l You can double-click in the area to zoom in the list and double-click
again to zoom out the list.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 343

No Area Description
.

3 List of Lists all undefined neighboring GSM cells of all test cells in the list of
undefined test cells.
neighborin The operations in this area are the same as those in area 2.
g GSM
cells

4 Chart area Shows the information about all neighboring GSM cells of all test cells
in a bar+line chart.
l The neighboring GSM cells of a selected test cell can be arranged in
sequence by their overall priorities. The percentages of the top 32
neighboring GSM cells are displayed in a bar chart.
l You can select a parameter from the drop-down list on the upper right
to display the statistical results of the parameter for the top 32
neighboring GSM cells in a line chart.
l The rules on displaying cell names on the X-axis are as follows:
– Generally, only cell names are displayed on the X-axis.
– If the names of two or more cells are the same, the BCCHs and
BSICs of the cells are displayed along with the cell names on the
X-axis.
– If a cell cannot be located, the BCCH and BSIC of the cell is
displayed on the X-axis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 344

No Area Description
.

5 Button area Four buttons are provided in this area:

l is used to export the summary of neighboring GSM cell analysis

results.
Using this button, you can export the information about all test cells
involved in the analysis task, including the task name, creator, start
time and end time of result information, and details about each test
cell.

l is used to export the optimization results of the neighboring

GSM cells of a test cell.
Using this button, you can export the information about the defined
and undefined neighboring GSM cells of a test cell, including the
task name, creator, start time and end time of result information,
BSC, ID, and name of the test cell, and details about each defined
and undefined neighboring GSM cell.

l is used to export the analysis results of possible neighboring

GSM cells. The system saves the information about the possible
neighboring cells of all test cells as files of specified formats by BSC.
Each file contains the information about the possible neighboring
cells of the test cells served by one BSC.

l is used to export all neighboring GSM cell analysis results.

Using this button, you can export the information about the defined
and undefined neighboring GSM cells of all test cells. To export the
analysis results, do as follows:
1. Click a button to open the Save dialog box.
If the a large quantity of neighboring GSM cell analysis results
exist, the dialog box may take a long period of time to display.
2. Set the save path of the result files, and click Save.
The system saves all neighboring cell analysis results by BSC as
a file in the specified format. Each file maps the neighboring cell
analysis result of one BSC.

Map Interface
After you click on the upper left of the Nastar client, the map interface (Geographic
Observation) is displayed. The Figure 3-15 shows this interface.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 345

Figure 3-15 Map interface for GSM GSM neighboring cell analysis results

No. Name Description

1 Button area Displays all the buttons for performing basic operations on the map
interface. For the meanings of these buttons, see 2.2.3 Interface
Description: Geographic Observation Results.

2 Navigation Site Layer: When an RAT is selected, site information of the selected
tree RAT is displayed in area 3.
l Site Layer: displays site information. You can set the display
effect through the shortcut menu. The site information is
displayed on the condition that the engineering parameters have
been imported to the Nastar database and site information have
been loaded in map window.
NOTE
If you need to delete all sites in a network system, click Remove through
the layer management function.
l If you clear this RAT, site information of this RAT is not displayed
in area 3.

3 Geographic After you select a cell in the neighboring cell analysis results, the map
display area interface uses different colors to display neighboring cells of this cell.
The geographic information area below displays information about
the longitude and latitude of the point where the cursor is placed and
about the distance between two points.

4 Legend area This area is not displayed by default. It is displayed only after you
click in the button area.

5 Information Displays information such as names and engineering parameters of

area the selected cell. If no engineering parameter has been imported for
this cell, a message is displayed in this area.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 346

Interface Description: Possible GSM Neighboring Cell Analysis

This section describes the interface for possible GSM neighboring cell analysis. Before
performing the related operations, familiarize yourself with the functions of each area in this
interface.

Opening the Window

You can perform the following operations to open the GSM Possible Neighboring Analysis
window:

Select an executed GSM neighboring cell analysis task, right-click a result of the task in the
Task Result area, and choose GSM Possible Neighboring Analysis from the shortcut menu.

Main Window
In the main window, the analysis results of possible neighboring GSM cells are displayed in
charts and lists, including the summary of possible neighboring cell analysis results and the
confirmation list of possible neighboring GSM cells, as shown in Figure 3-16.

Figure 3-16 Window for analyzing possible neighboring GSM cells

No Area Description
.

1 Button
area is used to export the summary of possible neighboring GSM cell
analysis results, that is, all information about the possible neighboring
GSM cells in area 2.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 347

No Area Description
.

2 Summary Lists the summary of the possible neighboring GSM cells of all cells
of possible involved in the analysis task.
neighborin The Nastar provides the functions of filtering and sorting. Click the
g GSM column header and choose a filtering item from the drop-down box to
cell
analysis display the table in a filtered way; click the column header to display
results the table in the descending order. You can also press Ctrl+F to search in
the area.

3 Confirmati Lists all the possible neighboring GSM cells of selected cells in area 2.
on list of
possible l Button area: is used to add possible neighboring GSM cells for
neighborin the serving cell. The procedure is as follows:
g GSM Select a cell in area 2, and click this button. The GSM Possible
cells Neighboring Cell Analysis dialog box is displayed. Select one or
multiple possible neighboring GSM cells from the navigation tree, and
click OK. One or multiple lines containing the information about
possible neighboring GSM cells are added to the list of possible
neighboring GSM cells.
l List of possible neighboring GSM cells: In the list of possible
neighboring GSM cells, select the Whether to Use check box of a
possible neighboring GSM cell. The possible neighboring GSM cell
is set as the best possible neighboring GSM cell of the serving cell in
the left area. The information about the corresponding parameters
(such as Neighboring Cell CGI, Neighboring BSC, and
Neighboring Cell Name) in the summary of possible neighboring
GSM cell analysis results is replaced with the information about this
possible neighboring GSM cell.
If the check box of Whether to Use is cleared, the information about
the preceding parameters will not be displayed in the left area.
For details about the parameters, see Parameters for Viewing GSM
Possible Neighboring Cell Analysis Results.

Interface Description: GSM Intra-Frequency Co-BSIC Cell Analysis

This section describes the interface for GSM intra-frequency co-BSIC GSM cell analysis. You
can determine whether to modify the BCCH ARFCN or BSIC of a test cell based on analysis
results in this interface.

Opening the Window

You can open the GSM intra-frequency co-BSIC cell analysis window in the following mode:

Select an executed GSM neighboring cell analysis task, right-click a result of the task in the
Task Result area, and choose Co-BCCH & Co-BSIC Checking from the shortcut menu.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 348

Main Window
Nastar shows the list of intra-frequency co-BSIC GSM cells in the main window, as shown in
Figure 3-17.

Figure 3-17 GSM Intra-frequency co-BSIC cell analysis Interface

Figure 3-17 lists the analysis results of the intra-frequency co-BSIC GSM cells of all cells
involved in the analysis task. You can press Ctrl+F to search in the area.

The Nastar provides the functions of filtering and sorting. Click the column header and choose
a filtering item from the drop-down box to display the table in a filtered way; click the column
header to display the table in the descending order.

Based on the analysis results, you can check whether any neighboring GSM cells of the test cell
share the same BCCH ARFCN and BSIC with the test cell. Based on the check results, you can
determine whether to modify the BCCH ARFCN or BSIC of the selected cell.

Interface Description: GSM Intra-Frequency Neighboring Cell Analysis

This section describes the interface for GSM intra-frequency neighboring cell analysis. You can
refer to this section when you determine whether to modify the BCCH ARFCN of a test cell.

Opening the Window

You can open the GSM intra-frequency neighboring cell analysis window in the following mode:

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 349

Select an executed GSM neighboring cell analysis task, right-click a result of the task in the
Task Result area, and choose Neighboring Cells Co-BCCH Analysis from the shortcut menu.

Main Window
The system shows the list of analysis results of intra-frequency neighboring GSM cells in the
main window, as shown in Figure 3-18.

Figure 3-18 GSM intra-frequency neighboring cell analysis Interface

Figure 3-18 lists the analysis results of the intra-frequency neighboring GSM cells of all cells
involved in the analysis task. You can press Ctrl+F to search in the area.

Based on the analysis results, you can check whether any neighboring GSM cells of the test cell
share the same BCCH ARFCN with the test cell. Based on the check results, you can decide
whether to modify the BCCH ARFCN of the selected cell.

3.3.5 Reference for GSM Neighboring Cell Analysis Parameters

This chapter describes the parameters for GSM neighboring cell analysis, possible GSM
neighboring cell analysis, GSM intra-frequency co-BSIC cell analysis, and GSM intra-frequency
neighboring cell analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 350

Parameters for Viewing GSM Neighboring Cell Analysis Results

This section describes the parameters for querying GSM neighboring cell analysis results, You
can refer to the description when querying GSM Neighboring Cell Analysis results.

Information About a Test Cell

Parameter Range Unit Description Supported NE
Version

BSC Where 1 to 32 N/A Indicates the BSC6900

Test Cell Is characters name of the V900R014C00
Located BSC that a test (or later) or
cell belongs to, BSC6910
for example, V100R014C00
BSC_1. (or later)

Test Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of a test V900R014C00
cell, for (or later) or
example, BSC6910
Cell_1. V100R014C00
(or later)

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement total number of V900R014C00
Reports MRs received (or later) or
by a test cell. BSC6910
V100R014C00
(or later)

Configured [0,64] Number Indicates the BSC6900

Neighboring number of V900R014C00
Cells neighboring (or later) or
cells defined for BSC6910
a specified cell. V100R014C00
(or later)

Number of [0,+∞) Number Indicates the BSC6900

Redundant number of V900R014C00
Neighboring redundant (or later) or
Cells neighboring BSC6910
cells for the V100R014C00
selected test (or later)
cell.

Number of Not [0,+∞) Number Indicates the BSC6900

Configured number of V900R014C00
Neighboring missing (or later) or
Cells neighboring BSC6910
cells for the V100R014C00
selected test (or later)
cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 351

Parameter Range Unit Description Supported NE

Version

Percentage of [0.00,100.00] % Indicates the BSC6900

Measurement sum of the V900R014C00
Report on Not integrated (or later) or
Configured priority BSC6910
Neighboring percentages of V100R014C00
Cells all missing (or later)
neighboring
cells for the
selected test
cell.

LAC [1,65533], N/A Indicates the BSC6900

[65535] location area V900R014C00
code of the (or later) or
selected test BSC6910
cell. V100R014C00
LAC is a part of (or later)
CGI and
uniquely
identifies a
GSM cell.

CI [0,65535] N/A Indicates the BSC6900

identification V900R014C00
code of the (or later) or
selected test BSC6910
cell. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 352

Parameter Range Unit Description Supported NE

Version

BCCH [0,1023] N/A Indicates the BSC6900

broadcast V900R014C00
control channel (or later) or
for the selected BSC6910
test cell. V100R014C00
1 to 124: belong (or later)
to P-GSM 900.
0 to 124, 975 to
1023: belong to
E-GSM 900.
0 to 124, 955 to
1023: belong to
R-GSM 900.
512 to 885:
belong to DCS
1800.
512 to 810:
belong to PCS
1900.
259 to 293:
belong to GSM
450.
306 to 340:
belong to GSM
480.
128 to 251:
belong to GSM
850.
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 353

Parameter Range Unit Description Supported NE

Version

BSIC [0,77] N/A Indicates the BSC6900

base station V900R014C00
identity code of (or later) or
the selected test BSC6910
cell. V100R014C00
BSIC=NCC*10 (or later)
+BCC, NCC
[0,7], BCC
[0,7].

Test Cell ID [0 to 2047] N/A Indicates the ID BSC6900

of the selected V900R014C00
test cell. (or later) or
BSC6910
V100R014C00
(or later)

Defined Neighboring Cell

Parameter Range Unit Description Supported NE
Version

Defined 1 to 64 N/A Indicates the BSC6900

Neighboring characters name of a V900R014C00
Cell Name defined (or later) or
neighboring cell BSC6910
for the selected V100R014C00
test cell. (or later)

CGI MCC-MNC- N/A Indicates the BSC6900

LAC-CI global ID of a V900R014C00
neighboring (or later) or
cell. BSC6910
MCC [000,999] V100R014C00
(or later)
MNC [00,99]
LAC [0,65535]
CI [0,65535]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 354

Parameter Range Unit Description Supported NE

Version

Neighboring [0,1023] N/A Indicates the BSC6900

Cell BCCH broadcast V900R014C00
control channel (or later) or
for a BSC6910
neighboring V100R014C00
cell. (or later)
1 to 124: belong
to P-GSM 900.
0 to 124, 975 to
1023: belong to
E-GSM 900.
0 to 124, 955 to
1023: belong to
R-GSM 900.
512 to 885:
belong to DCS
1800.
512 to 810:
belong to PCS
1900.
259 to 293:
belong to GSM
450.
306 to 340:
belong to GSM
480.
128 to 251:
belong to GSM
850.
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 355

Parameter Range Unit Description Supported NE

Version

Neighboring [0,77] N/A Indicates the BSC6900

Cell BSIC base station V900R014C00
identity code of (or later) or
the selected test BSC6910
cell. V100R014C00
BSIC=NCC*10 (or later)
+BCC, NCC
[0,7], BCC
[0,7].

Service Type of Indoor, Outdoor N/A Indicates the BSC6900

Neighboring or null service type V900R014C00
Cell provided by a (or later) or
GSM BSC6910
neighboring V100R014C00
cell, including (or later)
indoor site,
outdoor site and
unknow service
type. Learning
about the
service type
provided by a
GSM
neighboring cell
helps prevent
important
neighboring
cells from being
deleted.

Suggested "Defined N/A Indicates the BSC6900

Operation Neighboring operation V900R014C00
Cell suggestions on a (or later) or
(Reserved)" or neighboring BSC6910
"Defined cell. V100R014C00
Neighboring (or later)
Cell
(Redundant)"

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 356

Parameter Range Unit Description Supported NE

Version

One-Way/Two- "One-Way", N/A Field for BSC6900

Way "Two-Way", identifying a V900R014C00
"Unknown" unidirectional (or later) or
or bidirectional BSC6910
neighbor V100R014C00
relationship (or later)
based on
configuration
data.

User Modify N/A N/A Field for BSC6900

identifying data V900R014C00
that users can (or later) or
modify. Each of BSC6910
such data V100R014C00
records contains (or later)
this field after
being exported.
Users can
change this field
as required.

Number of [0,+∞) Number Indicates the BSC6900

Handover number of V900R014C00
Requests handover (or later) or
requests from BSC6910
the current V100R014C00
serving cell to (or later)
another cell.

Number of [0,+∞) Number Indicates the BSC6900

Handover number of V900R014C00
Failure handover (or later) or
failures among BSC6910
all handover V100R014C00
requests from (or later)
the current
serving cell to
another cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 357

Parameter Range Unit Description Supported NE

Version

Handover [0.00,100.00] % Indicates the BSC6900

Success Rate handover V900R014C00
success rate (or later) or
from the current BSC6910
serving cell to V100R014C00
another cell. (or later)
Outgoing cell
handover
success rate =
Number of
successful
outgoing cell
handovers/
Number of
outgoing cell
handover
requests x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 358

Parameter Range Unit Description Supported NE

Version

Relative [0.00,100.00] % Indicates the BSC6900

Percentage proportion of V900R014C00
the total (or later) or
handover BSC6910
attempts from V100R014C00
the current (or later)
serving cell to a
neighboring cell
to the total
handover
attempts from
the current
serving cell to
any neighboring
cells.
Relative
percentage =
Total number of
handover
attempts from
the current
serving cell to a
neighboring
cell/Total
number of
handover
attempts from
the current
serving cell to
any neighboring
cells x 100%

Version

Neighboring [0,1023] N/A Indicates the BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 364

Parameter Range Unit Description Supported NE

Version

Neighboring [0,77] N/A Indicates the BSC6900

Cell BSIC base station V900R014C00
identity code of (or later) or
the selected test BSC6910
cell. V100R014C00
BSIC=NCC*10 (or later)
+BCC, NCC
[0,7], BCC
[0,7].

Service Type of Indoor, Outdoor N/A Indicates the BSC6900

Neighboring or null service type V900R014C00
Cell provided by a (or later) or
GSM BSC6910
neighboring V100R014C00
cell, including (or later)
indoor site,
outdoor site and
unknow service
type . Learning
about the
service type
provided by a
GSM
neighboring cell
helps prevent
important
neighboring
cells from being
deleted.

Suggested "Undefined N/A Indicates the BSC6900

Operation Neighboring operation V900R014C00
Cell (Missing)" suggestions on a (or later) or
or "Undefined neighboring BSC6910
Neighboring cell. V100R014C00
Cell (Non- (or later)
Operation)"

One-Way/Two- "One-Way", N/A Field for BSC6900

Way "Unknown", "-" identifying V900R014C00
neighbor (or later) or
relationship BSC6910
based on V100R014C00
configuration (or later)
data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 365

Parameter Range Unit Description Supported NE

Version

User Modify N/A N/A Field for BSC6900

Percentage of [0.00,100.00] % Indicates the BSC6900

Integrated integrated V900R014C00
Priority priority of a (or later) or
neighboring BSC6910
cell, that is, the V100R014C00
percentage of (or later)
total number of
MRs related to
the test cell to
the number of
MRs related to
the neighboring
cell level higher
than the relative
level and the
absolute level.

Priority [0,+∞) N/A Indicates the BSC6900

sequence V900R014C00
number of a (or later) or
neighboring cell BSC6910
among all V100R014C00
neighboring (or later)
cells for the
selected test cell
according to its
integrated
priority.

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the selected test (or later) or
cell to a BSC6910
neighboring V100R014C00
cell. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 366

Parameter Range Unit Description Supported NE

Version

Super-Distance Yes, No or null N/A Indicates that BSC6900

the distance V900R014C00
between a (or later) or
specified cell BSC6910
and its V100R014C00
neighboring cell (or later)
exceeds a
predefined
threshold.

In BA Time [0,+∞) minute Indicates the BSC6900

duration for V900R014C00
measuring a (or later) or
neighboring BSC6910
cell. V100R014C00
(or later)

Number of [0,+∞) Number Indicates the BSC6900

Neighboring number of MRs V900R014C00
Cell related to a (or later) or
Measurement neighboring BSC6910
Reports cell. V100R014C00
(or later)

Total [0,+∞) Number Indicates the BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 367

Parameter Range Unit Description Supported NE

Version

Source Cell N/A dBm Indicates the BSC6900

Signal Strength average signal V900R014C00
strength of the (or later) or
selected test BSC6910
cell. V100R014C00
(or later)

Neighboring N/A dBm Indicates the BSC6900

Cell Signal average signal V900R014C00
Strength strength of a (or later) or
neighboring BSC6910
cell. V100R014C00
(or later)

Mean S-N N/A dB Indicates the BSC6900

Difference average V900R014C00
difference (or later) or
between the BSC6910
signal strength V100R014C00
of the selected (or later)
test cell and the
signal strength
of a neighboring
cell.

Relative TH [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports containing (or later) or
information that BSC6910
the difference V100R014C00
between the (or later)
signal strength
of a neighboring
cell and the
signal strength
of the test cell is
greater than the
relative level
threshold.

Absolute TH [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports containing the (or later) or
signal strength BSC6910
of neighboring V100R014C00
cells greater (or later)
than the
absolute level
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 368

Parameters for Viewing GSM Possible Neighboring Cell Analysis Results

This section describes the parameters for viewing GSM Possible Neighboring Cell Analysis
results, You can refer to the description when viewing GSM Possible Neighboring Cell Analysis
results.

Possible Neighboring Cell Overview Table

Parameter Range Unit Description Supported NE
Version

BSC Where 1 to 32 N/A Indicates the BSC6900

Test Cell Is characters name of the V900R014C00
Located BSC that a test (or later) or
cell belongs to, BSC6910
for example, V100R014C00
ERM3H201. (or later)

Test Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the test V900R014C00
serving cell, for (or later) or
example, BSC6910
Cell_1. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 369

Parameter Range Unit Description Supported NE

Version

Test Cell BCCH [0,1023] N/A Indicates the BSC6900

broadcast V900R014C00
control channel (or later) or
for a test BSC6910
neighboring V100R014C00
cell. (or later)
1 to 124: belong
to P-GSM 900.
0 to 124, 975 to
1023: belong to
E-GSM 900.
0 to 124, 955 to
1023: belong to
R-GSM 900.
512 to 885:
belong to
DCS1800
512 to 810:
belong to
PCS1900.
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 370

Parameter Range Unit Description Supported NE

Version

Test Cell BSIC [0,77] N/A Indicates the BSC6900

base station V900R014C00
identity code of (or later) or
a test cell. BSC6910
BSIC=NCC*10 V100R014C00
+BCC, NCC (or later)
[0,7], BCC
[0,7].

Test Cell CGI MCC-MNC- N/A Indicates the BSC6900

LAC-CI global ID of a V900R014C00
test cell, for (or later) or
example, BSC6910
286-01-33034-5 V100R014C00
0712. (or later)
MCC[000,999]
MNC[00,99]
LAC[0,65535]
CI[0,65535]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 371

Parameter Range Unit Description Supported NE

Version

Neighboring [0,1023] N/A Indicates the BSC6900

Cell BCCH broadcast V900R014C00
control channel (or later) or
for a test BSC6910
neighboring V100R014C00
cell. (or later)
1 to 124: belong
to P-GSM 900.
0 to 124, 975 to
1023: belong to
E-GSM 900.
0 to 124, 955 to
1023: belong to
R-GSM 900.
512 to 885:
belong to
DCS1800
512 to 810:
belong to
PCS1900.
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 372

Parameter Range Unit Description Supported NE

Version

Neighboring [0,77] N/A Indicates the BSC6900

Cell BSIC base station V900R014C00
identity code of (or later) or
a test BSC6910
neighboring V100R014C00
cell. (or later)
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].

Neighboring MCC-MNC- N/A Indicates the BSC6900

Cell CGI LAC-CI global ID of the V900R014C00
selected (or later) or
possible BSC6910
neighboring V100R014C00
cell. (or later)
MCC[000,999]
MNC[00,99]
LAC[0,65535]
CI[0,65535]

BSC of Selected 1 to 32 N/A Indicates the BSC6900

Neighboring characters name of the V900R014C00
Cell BSC that the (or later) or
selected BSC6910
possible V100R014C00
neighboring cell (or later)
belongs to.

Neighboring 1 to 64 N/A Indicates the BSC6900

Cell Name characters name of the V900R014C00
selected (or later) or
possible BSC6910
neighboring V100R014C00
cell. (or later)

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the test cell to (or later) or
the selected BSC6910
possible V100R014C00
neighboring (or later)
cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 373

Parameter Range Unit Description Supported NE

Version

Number of 2,3,9 N/A Indicates the BSC6900

Possible number of laps V900R014C00
Neighboring between the (or later) or
Cell Laps selected BSC6910
possible V100R014C00
neighboring cell (or later)
and the test cell,
that is, the
number of cells
between the
selected
possible
neighboring cell
and the test cell.

Angle of [0,360] ° Indicates the BSC6900

Neighboring relative angle V900R014C00
Cell Direction between the (or later) or
selected BSC6910
possible V100R014C00
neighboring cell (or later)
and the test cell.

Predicted Signal N/A dBm Indicates the BSC6900

Strength of signal strength V900R014C00
Neighboring of the selected (or later) or
Cell possible BSC6910
neighboring cell V100R014C00
based on the (or later)
dimensioning.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 374

Parameter Range Unit Description Supported NE

Version

Get from Config Yes, No N/A Indicates BSC6900

Data whether the V900R014C00
selected (or later) or
possible BSC6910
neighboring cell V100R014C00
is obtained from (or later)
the
configuration
data. Yes
indicates that
possible
neighboring
cells are
obtained from
the
configuration
data. No
indicates that
possible
neighboring
cells are not
obtained from
the
configuration
data.

Number of [0,+∞) Number Indicates the BSC6900

Possible number of V900R014C00
Neighboring possible (or later) or
Cells neighboring BSC6910
cells. V100R014C00
(or later)

Percentage of [0.00,100.00] % Indicates the BSC6900

Integrated percentage of V900R014C00
Priority integrated (or later) or
priority. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 375

Parameter Range Unit Description Supported NE

Version

Priority [0,+∞) N/A Indicates the BSC6900

sequence V900R014C00
number of a (or later) or
possible BSC6910
neighboring cell V100R014C00
among all (or later)
possible
neighboring
cells for the
selected test cell
according to its
integrated
priority.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 376

Possible Neighboring Cell Confirmation Table

Parameter Range Unit Description Supported NE
Version

Whether to Use N/A N/A Indicates BSC6900

whether to V900R014C00
select the (or later) or
current possible BSC6910
neighboring cell V100R014C00
as the most (or later)
possible
neighboring cell
for the test cell.
If the parameter
is selected, the
current possible
neighboring cell
serves as the
most possible
neighboring cell
for the test cell.
In addition, you
must replace
information
about the
selected
possible
neighboring cell
in the possible
neighboring cell
confirmation
table with
information in
the possible
neighboring cell
overview table.
Possible
Neighboring
Cell CGI
replaces
Neighboring
Cell CGI.
Possible
Neighboring
Cell BSC Name
replaces
Neighboring
BSC.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 377

Parameter Range Unit Description Supported NE

Version

Name of
Possible
Neighboring
Cell replaces
Neighboring
Cell Name.
Distance of
Possible
Neighboring
Cell(km)
replaces
Neighboring
Distance(km).
Number of
Possible
Neighboring
Cell Laps
replaces
Neighboring
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

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 378

Parameter Range Unit Description Supported NE

Version

determined. In
addition, the
system clears all
the information
in the following
fields in the
possible
neighboring cell
overview table:
Neighboring
Cell CGI
Neighboring
Cell Name
Neighboring
Distance(km)
Neighboring
Cell Loop
Number
Angle form
Neighboring
Cell Direction
Predicted DL
Signal Strength
Get from config
data

Possible MCC-MNC- N/A Indicates the BSC6900

Neighboring LAC-CI global ID of a V900R014C00
Cell CGI possible (or later) or
neighboring BSC6910
cell. V100R014C00
MCC[000,999] (or later)

MNC[00,99]
LAC[0,65535]
CI[0,65535]

BSC of Possible 1 to 32 N/A Indicates the BSC6900

Neighboring characters name of the V900R014C00
Cell BSC that a (or later) or
possible BSC6910
neighboring cell V100R014C00
belongs to. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 379

Parameter Range Unit Description Supported NE

Version

Name of 1 to 64 N/A Indicates the BSC6900

Possible characters name of a V900R014C00
Neighboring possible (or later) or
Cell neighboring BSC6910
cell. V100R014C00
(or later)

Distance of [0,+∞) km Indicates the BSC6900

Possible distance from V900R014C00
Neighboring the test cell to a (or later) or
Cell possible BSC6910
neighboring V100R014C00
cell. (or later)

Number of 2,3,9 N/A Indicates the BSC6900

Possible number of laps V900R014C00
Neighboring between the test (or later) or
Cell Laps cell and a BSC6910
possible V100R014C00
neighboring (or later)
cell, that is, the
number of cells
between the test
cell and a
possible
neighboring
cell.

Relative Angle [0,360] ° Indicates the BSC6900

of Possible relative angle V900R014C00
Neighboring between the test (or later) or
Cell cell and a BSC6910
possible V100R014C00
neighboring (or later)
cell.

Predicted Signal N/A dBm Indicates the BSC6900

Strength of signal strength V900R014C00
Possible of a possible (or later) or
Neighboring neighboring cell BSC6910
Cell based on the V100R014C00
dimensioning. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 380

Parameter Range Unit Description Supported NE

Version

Get from Config Yes, No N/A Indicates BSC6900

Data whether V900R014C00
possible (or later) or
neighboring BSC6910
cells are V100R014C00
obtained from (or later)
the
configuration
data. Yes
indicates that
possible
neighboring
cells are
obtained from
the
configuration
data. No
indicates that
possible
neighboring
cells are not
obtained from
the
configuration
data.

Parameters for Viewing GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis
Results
This section describes the parameters for querying GSM Co-BCCH and Co-BSIC Neighboring
Cell Analysis results, You can refer to the description when querying GSM Co-BCCH and Co-
BSIC Neighboring Cell Analysis results.

Parameter
Parameter Range Unit Description Supported NE
Version

BSC Where 1 to 32 N/A Indicates the BSC6900

Test Cell Is characters name of the V900R014C00
Located BSC that a test (or later) or
cell belongs to, BSC6910
for example, V100R014C00
BSC_1. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 381

Parameter Range Unit Description Supported NE

Version

Test Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of a test V900R014C00
cell, for (or later) or
example, BSC6910
Cell_1. V100R014C00
(or later)

Test Cell CGI MCC-MNC- N/A Indicates the BSC6900

LAC-CI global ID of a V900R014C00
neighboring cell (or later) or
for the selected BSC6910
test cell. V100R014C00
MCC[000,999] (or later)

MNC[00,99]
LAC[0,65535]
CI[0,65535]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 382

Parameter Range Unit Description Supported NE

Version

Test Cell BCCH [0,1023] N/A Indicates the BSC6900

broadcast V900R014C00
control channel (or later) or
for a test cell. BSC6910
1 to 124: belong V100R014C00
to P-GSM 900. (or later)

0 to 124, 975 to
1023: belong to
E-GSM 900.
0 to 124, 955 to
1023: belong to
R-GSM 900.
512 to 885:
belong to
DCS1800
512 to 810:
belong to
PCS1900.
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 383

Parameter Range Unit Description Supported NE

Version

Test Cell BSIC [0,77] N/A Indicates the BSC6900

base station V900R014C00
identity code of (or later) or
a test cell. BSC6910
BSIC=NCC*10 V100R014C00
+BCC, NCC (or later)
[0,7], BCC
[0,7].

Neighboring 1 to 64 N/A Indicates the BSC6900

Cell Name characters name of a V900R014C00
neighboring cell (or later) or
for the selected BSC6910
test cell. V100R014C00
(or later)

Neighboring MCC-MNC- N/A Indicates the BSC6900

Cell CGI LAC-CI global ID of a V900R014C00
neighboring cell (or later) or
for the selected BSC6910
test cell. V100R014C00
MCC[000,999] (or later)

MNC[00,99]
LAC[0,65535]
CI[0,65535]

Angle of [0°,360°] Degree Indicates the BSC6900

Neighboring antenna azimuth V900R014C00
Cell Direction of the selected (or later) or
test cell. BSC6910
V100R014C00
(or later)

Distance [0,+∞) km Indicates the BSC6900

distance V900R014C00
between the test (or later) or
cell and a BSC6910
neighboring V100R014C00
cell. (or later)

Number of [0,+∞) Number Indicates the BSC6900

Handover number of V900R014C00
Requests handover (or later) or
requests from BSC6910
the current V100R014C00
serving cell to (or later)
another cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 384

Parameters for Viewing GSM Intra-frequency Neighboring Cell Analysis Results

This section describes the parameters for querying GSM Intra-frequency Neighboring Cell
Analysis results, You can refer to the description when querying GSM Intra-frequency
Neighboring Cell Analysis results.

Parameter
Parameter Range Unit Description Supported NE
Version

BSC Where 1 to 32 N/A Indicates the BSC6900

Test Cell Is characters name of the V900R014C00
Located BSC that a test (or later) or
cell belongs to, BSC6910
for example, V100R014C00
BSC_1. (or later)

Test Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of a test V900R014C00
cell, for (or later) or
example, BSC6910
Cell_1. V100R014C00
(or later)

Test Cell CGI MCC-MNC- N/A Indicates the BSC6900

LAC-CI global ID of a V900R014C00
neighboring cell (or later) or
for the selected BSC6910
test cell. V100R014C00
MCC[000,999] (or later)

MNC[00,99]
LAC[0,65535]
CI[0,65535]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 385

Parameter Range Unit Description Supported NE

Version

Test Cell BCCH [0,1023] N/A Indicates the BSC6900

broadcast V900R014C00
control channel (or later) or
for a test cell. BSC6910
1 to 124: belong V100R014C00
to P-GSM 900. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 386

Parameter Range Unit Description Supported NE

Version

Test Cell BSIC [0,77] N/A Indicates the BSC6900

base station V900R014C00
identity code of (or later) or
a test cell. BSC6910
BSIC=NCC*10 V100R014C00
+BCC, NCC (or later)
[0,7], BCC
[0,7].

Neighboring 1 to 64 N/A Indicates the BSC6900

Cell Name characters name of a V900R014C00
neighboring cell (or later) or
for the selected BSC6910
test cell. V100R014C00
(or later)

BSC Where 1 to 32 N/A Indicates the BSC6900

Neighboring characters name of the V900R014C00
Cell Is Located BSC that a (or later) or
neighboring cell BSC6910
for the selected V100R014C00
test cell belongs (or later)
to.

Neighboring MCC-MNC- N/A Indicates the BSC6900

Cell CGI LAC-CI global ID of a V900R014C00
neighboring cell (or later) or
for the selected BSC6910
test cell. V100R014C00
MCC[000,999] (or later)

MNC[00,99]
LAC[0,65535]
CI[0,65535]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 387

Parameter Range Unit Description Supported NE

Version

Neighboring [0,1023] N/A Indicates the BSC6900

Cell BCCH broadcast V900R014C00
control channel (or later) or
for a BSC6910
neighboring cell V100R014C00
for the selected (or later)
test cell.
1 to 124: belong
to P-GSM 900.
0 to 124, 975 to
1023: belong to
E-GSM 900.
0 to 124, 955 to
1023: belong to
R-GSM 900.
512 to 885:
belong to
DCS1800
512 to 810:
belong to
PCS1900.
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
Regulation: P-
GSM, E-GSM,
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 388

Parameter Range Unit Description Supported NE

Version

Neighboring [0,77] N/A Indicates the BSC6900

Cell BSIC base station V900R014C00
identity code of (or later) or
a neighboring BSC6910
cell for the V100R014C00
selected test (or later)
cell.
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the selected test (or later) or
cell to a BSC6910
neighboring V100R014C00
cell. (or later)

Number Of [0,+∞) Number Indicates the BSC6900

Handover number of V900R014C00
Requests handover (or later) or
requests from BSC6910
the current V100R014C00
serving cell to (or later)
another cell.

Priority [0,+∞) N/A Indicates the BSC6900

3.4 GSM/UMTS Neighboring Cell Analysis

On Nastar, you can check whether any neighboring UMTS cell of a GSM cell is missing or
redundant by summarizing and analyzing the MRs and events sent by MSs, configuration data,

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 389

and engineering parameter data. This helps you resolve network quality problems due to
redundant or missing neighboring UMTS cells.

3.4.1 Basics of GSM/UMTS Neighboring Cell Analysis

This section describes the basics of GSM/UMTS neighboring cell analysis in terms of function,
authority policies, technical specifications, and restrictions. You can refer to this section when
you analyze GSM/UMTS neighboring cells. You must read this section before starting the
analysis.

Functions of GSM/UMTS Neighboring Cell Analysis

This section describes the GSM/UMTS neighboring cell analysis function. Through this
function, the Nastar summarizes the measurement reports (MRs) and events reported by
terminals and analyzes inter-RAT neighboring cells to check for the redundant and missing
neighboring cell configurations and cross coverage. This helps to improve the network quality.

Function Description
After you set the conditions for checking the redundant or missing neighboring cell
configurations, the Nastar performs inter-RAT neighboring cell analysis for the selected cell.
The analysis results are displayed in a bar chart. In the bar chart, the defined UMTS neighboring
cells, undefined UMTS neighboring cells, redundant UMTS neighboring cells, and missing
UMTS neighboring cells are illustrated in different colors.
The Nastar can export analysis results of inter-RAT neighboring cells to a file. In the inter-RAT
neighboring cell analysis result window, you can export the result file of inter-RAT neighboring
cell analysis after adding the missing neighboring cells and deleting the redundant neighboring
cells. The result file provides the related optimization suggestions.
The GSM/UMTS neighboring cell analysis results can be exported to a .csv, .xls, or .xlsx file.

Function Algorithm
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 measurement reports (MRs) reported by UEs, the Nastar calculates the overall
score and then ranks the defined and undefined UMTS neighboring cells. According to the
ranking of UMTS neighboring cells and result analysis charts, you can enable the Nastar to
analyze the neighboring cells depending on the actual network situation, and then provide
suggestions on missing UMTS neighboring cells to be added and redundant UMTS neighboring
cells to be deleted.
The algorithms for GSM/UMTS neighboring cell analysis are as follows:
1. Calculate the integrated priority of all the UMTS neighboring cells of a serving cell.
In terms of multiple factors such as UMTS neighboring cells MRs, measurement time, and
serving cell MRs, the GSM/UMTS neighboring cell analysis provides scores and integrated

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 390

priorities based on the Nastar algorithms. The higher the integrated priority is, and the
smaller the sequence number is.
2. Determine missing neighboring cells.
When the sequence number of an undefined UMTS neighboring cell is smaller than or
equal to the value of Neighboring Cell Count Setting that is set when a GSM/UMTS
neighboring cell analysis task is created, the UMTS neighboring cell is regarded as a
missing neighboring cell.
3. Determine redundant neighboring cells.
When the sequence number of a defined UMTS neighboring cell is greater than the value
of Neighboring Cell Count Setting that is set when a GSM/UMTS neighboring cell
analysis task is created, the UMTS neighboring cell is regarded as a redundant neighboring
cell.

Function Principles
Data required by GSM/UMTS neighboring cell analysis comes from the performance data on
the U2000/M2000.

Figure 3-19 shows the principles for collecting, importing, and analyzing data on the Nastar.
For detailed operations, see Table 3-13.
NOTE
Before you use the Nastar to collect and import performance data, check that the data export function has been
enabled on the U2000/M2000.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 391

Figure 3-19 Principles for analysis

Table 3-13 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

1. Issue an Nas eSA To deliver performance indicator requirements to the

Collect eS U20 To deliver a data-processing request to the U2000/

perform AU 00/ M2000, requesting the U2000/M2000 to filter out the
ance M20 performance data that meets the Nastar's requirements.
data 00

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 392

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Upload U2 eSA To upload the performance data that meets the Nastar's
perform 000 U requirements to the eSAU.
ance /
data M2
000

4. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

Requirements for the Network

The network must be stable during the period of collecting data for GSM/UMTS neighboring
cell analysis. Otherwise, the analysis results are inaccurate. Table 3-14 describes network
changes and their impacts.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 393

Table 3-14 Network changes and their respective impacts

Network Change Impacts

Adding or deleting BTSs Affects network coverage and normal handovers between cells.
As a result, the analysis results cannot accurately reflect the
current state of network.

Adjusting the antenna The cell coverage and network interference may change.
data, such as the azimuth,
tilt, and height of an
antenna

Adjusting the transmit The cell coverage and network interference may change.
power or other power-
related parameters, such
as discontinuous
transmission or power
control.

Adjusting frequency Adjustment of configuration data affects the identification of

Technical Specifications for GSM/UMTS Neighboring Cell Analysis

This section describes the technical specifications, including the analysis ability and the range
of analysis time.

Item Service Specifications

Execution type One-time task

Network scale for one <= 10,000 cells

analysis task

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 394

Item Service Specifications

Number of allowed <= 50

analysis tasks

Time range for data in 14 days

one analysis task

Duration of one analysis <= 5 minutes

task

Default duration for 15 days

storing analysis data

Maximum duration for 15 days

storing analysis data

3.4.2 Preparations for GSM/UMTS Neighboring Cell Analysis

To ensure the normal execution of a GSM/UMTS neighboring cell analysis task, check your
user authority and network environment, and prepare the required raw data before starting the
task. You must read this section before starting the analysis.

Checking License and User Authority

l Ensure that a valid license for the GSM/UMTS neighboring cell analysis function has been
obtained.
l Ensure that you have the operation rights to subscribe to GSM/UMTS neighboring cell
analysis data upon login.
You are advised to contact the administrator to turn on the data switch because the analysis
data subscription function has a high security requirement.
l Ensure that your user account is authorized to create GSM/UMTS neighboring cell analysis
tasks, and the operation rights to operate the analyzed NEs.

Preparing Basic Data

Configuration Data
The configuration data of the NE controlling the test cell and neighboring cells is used to correctly
analyze the information about the test cell and neighboring cells and collect the analysis data of
these cells from the network during the analysis process.
If the OSS information has been already configured, the Nastar automatically and periodically
collects and imports the configuration data after the OSS and NE information is configured. You
can also manually collect the configuration data before the specified time period starts. After
the configuration data is imported, you can choose Maintenance > Data Maintenance
Management to check whether the configuration data is available in the Nastar database. For
detailed information about collecting, importing, and checking, see 2.5.2 Checking the
Integrity of Configuration Data.
After the configuration data has been successfully imported, you are advised to check the validity
of the configuration data. The purpose is to avoid expiration of configuration data due to network

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 395

adjustment. Expired configuration data may cause incorrect cell information in the analysis
result. For detailed operations, see Checking Engineering Parameters and Configuration
Data.

Engineering parameter data

Map file (optional)

The map file for a specific area displays the analysis result geographically. You do not need to
prepare the map file if you do not want to view the analysis result on the map.

Checking Network Environment

l Check that the matching U2000/M2000 version is V200R012C00 (or later), and the NE
version is BSC6900 V900R014C00 (or later) or BSC6910 V100R014C00 (or later).
l Before collecting GSM performance data, ensure that the performance data export function
has been enabled on the U2000/M2000. For detailed operations, see Commissioning the
Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for
Obtaining Data(GSM) > Enabling the GSM Performance Data Export Function on
the U2000/M2000 (U2000/M2000 R011 or earlier) in the Nastar Commissioning
Guide.
l Ensure that the U2000/M2000 has the license for obtaining neighboring cell measurement
data and the BSC has the license for using the function 2G/3G neighboring cell auto-
optimization. For detailed operations, see Commissioning the Function of Obtaining
the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) >
Checking the License on the U2000/M2000/GBSC in Nastar Commissioning Guide.
l Check that the BSC (BSC6900 V900R014 or earlier version) has been turned on the switch
whether to allow a 3G to 2G handover. For detailed operations, see Commissioning the
Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for
Obtaining Data(GSM) > Turning On the Switch Whether to Allow a 3G to 2G
Handover (GSM/UMTS Neighboring Cell Analysis) in Nastar Commissioning Guide.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 396

3.4.3 Process of GSM/UMTS Neighboring Cell Analysis

This section describes procedures of GSM/UMTS neighboring cell analysis, and steps of each
procedure.

l Prerequisite
l Procedure
l Subscription Task Parameters
l Analysis Task Parameters

Prerequisite
GSM configuration data and GSM engineering parameters have been imported to the Nastar
database. For details, see 3.4.2 Preparations for GSM/UMTS Neighboring Cell Analysis.

Procedure
Figure 3-20 shows the analysis process.

Figure 3-20 Analysis process

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 397

Table 3-15 Description of GSM/UMTS neighboring cell analysis procedures

N Procedure Description Reference for

o. Detailed
Operations

(1 Check the Navigation path: Choose Maintenance > Data 2.7 Checking the
) integrity of Maintenance Management Integrity of
GSM/UMTS Procedure: Analysis Data
neighboring
cell analysis 1. Set Data Type to GSM/UMTS
data Neighboring Cell analysis data.
2. Set the query time segment.
3. Select the NE to be queried.
4. Click Query.
The query results are displayed in the right
pane of the window.
l If analysis data exists, perform (3) to
create an analysis task.
l If analysis data does not exist, request the
administrator to subscribe to the data by
performing (2).
NOTE
The data subscription function has high
security requirements. You are advised to
contact the administrator with subscription
rights to perform the subscription operation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 398

N Procedure Description Reference for

o. Detailed
Operations

(2 Subscribe to Navigation path: Choose Maintenance > Data 2.6 Subscribing to

) GSM/UMTS Subscription Management Analysis Data
neighboring Procedure:
cell analysis
data 1. In the Data Subscription Management
(application) window, click the GSM tab.
2. Choose the NE to be configured in the
navigation tree.
3. Click ON on the GSM/UMTS Neighboring
Cell Analysis tab.
4. On the Basic Parameter Settings tab, set
basic parameters for GSM/UMTS
neighboring cell analysis.
5. On the Advanced Parameter Settings tab,
set advanced parameters for GSM/UMTS
neighboring cell analysis.
6. Click Next.
7. In Result of setting window, add the
ARFCN and scrambling code of a cell.
8. Click Complete.
For details about parameters, see Subscription
Task Parameters.
NOTE
Subject to the restriction of the NE data subscription
switch, the GSM/UMTS neighboring cell analysis
and the GSM neighboring cell analysis cannot be
performed concurrently.

Check the Navigation path: Choose Maintenance > Data 2.7 Checking the
integrity of Maintenance Management Integrity of
GSM/UMTS Procedure: Analysis Data
neighboring
cell analysis 1. Set Data Type to GSM/UMTS
data Neighboring Cell analysis data.
2. Set the query time segment.
3. Select the NE to be queried.
4. Click Query.
The query results are displayed in the right
pane of the window.
l If analysis data exists, perform (3) to
create an analysis task.
l If the analysis data does not exist, contact
Huawei technical support.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 399

N Procedure Description Reference for

o. Detailed
Operations

(3 Create a GSM/ Navigation path: Choose Theme Function > 2.8 Creating an
) UMTS Basic Network Optimization > GSM/UMTS Analysis Task
neighboring Neighboring Cell Analysis from the navigation
cell analysis tree of the Analysis Task Management
task window.
Procedure:
1. Double-click GSM/UMTS Neighboring
Cell Analysis.
2. Set the task name and task remarks. Click
Next.
3. Select the NE to be analyzed on the Select
NE(s) tab.
4. Configure parameters on the Parameter
Settings tab. Click Next.
For details about parameters, see Analysis
Task Parameters.
5. Choose an analysis time segment. After you
set the time range, the Nastar obtains the
analysis data generated within this time
range.
6. Click Finish.

(4 View GSM/ Navigation path: In the upper right area of the 2.9 Querying
) UMTS Analysis Task Management window, select an Analysis Results
neighboring analysis task in the Finished state. In the lower
cell analysis right of the Task Result area, select a result
results record of the task.
Procedure:
1. Double-click an analysis result of the task.
2. View the analysis result in the displayed
GSM/UMTS Neighboring Cell Analysis
window.
For details about analysis results, see
Interface Description: GSM/UMTS
Neighboring Cell Analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 400

N Procedure Description Reference for

o. Detailed
Operations

(5 View possible Navigation path: Choose a neighboring cell

) GSM/UMTS analysis task whose status is Finished from the
neighboring upper right area of the Analysis Task
cell analysis Management window. In the lower right Task
results Result area, choose an analysis result of the
task.
Procedure:
1. Right-click an analysis result of the task, and
choose GSM/UMTS Possible Neighboring
Analysis from the shortcut menu.
2. View the GSM/UMTS possible neighboring
cell analysis result in the displayed GSM/
UMTS Possible Neighboring Cell
Analysis.
For details about analysis results, see
Interface Description: GSM/UMTS
Possible Neighboring Cell Analysis.

(6 Export GSM/ Navigation path: Click the icon on the toolbar 2.11 Exporting
) UMTS in the upper left part of each analysis results Analysis Reports
neighboring window.
cell analysis Procedure:
reports
1. Click the export icon on the toolbar.
For the description of export icon, see
Interface Description: GSM/UMTS
Neighboring Cell Analysis.
2. Set the export path and export format.
3. Click Finish.

(7 Export GSM/ Navigation path: Click the icon on the toolbar

) UMTS in the upper left part of each analysis results
Possible window.
Neighboring Procedure:
Cell Analysis
Reports 1. Click the export icon on the toolbar.
For the description of export icon, see
Interface Description: GSM/UMTS
Possible Neighboring Cell Analysis.
2. Set the export path and export format.
3. Click Save.

Subscription Task Parameters

Application Subscription

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 401

Parameter Description

Measure Task Start Time Time when the task starts to run.
The start time must be later than the current time.
By default, the start time is the previous full hour
of the current system time.

Measure Extra l If this parameter is selected, the Nastar delivers

Neighboring Cells an analysis task to SAUs and delivers data
source switches to the eSAU or NEs when users
deliver an application data subscription task.
l If this parameter is not selected, the Nastar
delivers an analysis task only to SAUs when
users deliver an application data subscription
task. In addition, measurement task parameters
and certain advanced parameters are
unavailable.
l This parameter is selected by default.

Measurement step Number of frequencies in a frequency group.

The value of this parameter is an integer ranging
from 1 to 31.
The measurement step must be less than or equal to
the minimum rest step of the selected cell.

Period Interval between two periodic measurement tasks.

This parameter is set to one day by default and
cannot be changed by users.

Repeat times Number of times that a periodic task is performed.

The value 0 indicates that there is no limitation on
the number of times that a periodic task is
performed.

NE Object NE objects related to GSM/UMTS neighboring cell

analysis data subscription.

Advanced Duration Indicates the total duration which a measurement

Parameter task is performed.
Settings
Counter period The U2000/M2000 collects performance data
based on various counter periods. The Nastar
collects performance data based on two counter
periods: 30 minutes and 60 minutes.
Value range: 30 and 60. Unit: minute.

Measurement Interval between the ARFCNs of each group. The

period interval is 15 minutes by default and cannot be
changed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 402

Parameter Description

Result of setting Query allows users to fill the configured ARFCNs and
Configuration scrambling code in Test ARFCN and Scrambling
Code.

Auto-Analyze The system automatically analyzes the ARFCNs

and scrambling codes of neighboring cells.
Following describes the analysis process:
l First phase: queries inter-RAT neighboring
cells.
l Second phase: queries inter-RAT neighboring
cells of intra-RAT neighboring cells.
l Third phase: queries inter-RAT neighboring
cells of intra-RAT neighboring cells of intra-
RAT neighboring cells.

Batch Configure allows users to set the ARFCNs and scrambling

codes for cells in batches.

Adjust cell allows users to modify the ARFCNs and

scrambling codes of a selected cell.

Export Result allows users to export the settings of ARFCNs and

scrambling codes.

Analysis Task Parameters

Basic task information

Parameter Description

Task Name Name of an analysis task.

Task Type Type of an analysis task to be created.

Remarks Description of the task.

Value range: The name contains a maximum of 200 characters.

NE information

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 403

Parameter Description

Select NE(s) NEs or cell groups to be selected for analysis.

Parameter information

Parameter Description

Neighboring Neighboring Threshold of the neighboring cell sequence number. All the
Cell Analysis Cell Count undefined neighboring cells whose sequence numbers are
Parameters Setting 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.

Result Show Number of Indicates that only the TopN undefined neighboring cells are
Parameters undefined displayed.
neighboring N can be any integer from 20 to 50. The default value is 30.
cells to be
displayed

Other Super- Specifies the threshold for the distance to a super-far

Parameter distance neighboring cell.
Settings threshold The value of this parameter ranges from 0 to 50000 (unit:
meter). The default value of this parameter is 5000.

Time information of one-time task

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

Delay If you do not select this parameter, the system executes the task
immediately.
If you select this parameter, the system executes the task at the time
specified in Execute on.

Execute on Time when a task is executed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 404

3.4.4 Reference for GSM/UMTS Neighboring Cell Analysis

Interface
This section describes the interfaces for GSM/UMTS neighboring cell analysis and possible
GSM/UMTS neighboring cell analysis. Familiarize yourself with the functions of each area in
these interfaces before you perform the related operations.

Interface Description: GSM/UMTS Neighboring Cell Analysis

This section describes the interface for GSM/UMTS neighboring cell analysis. Before you
perform the related operations, familiarize yourself with the functions of each area in this
interface.

Opening the Window

You can open the GSM/UMTS neighboring cell analysis window in two modes:
l Select an executed GSM/UMTS neighboring cell analysis task, and double-click a result
of the task in the Task Result area.
l Select an executed GSM/UMTS neighboring cell analysis task, right-click a result of the
task in the Task Result area, and choose View Analysis Result from the shortcut menu.

Main Window
In the main window, the system shows the analysis results of neighboring UMTS cells in lists
and charts, including the list of test cells, list of neighboring cells, bar chart, and line chart, as
shown in Figure 3-21.

Figure 3-21 GSM/UMTS neighboring cell analysis Interface

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 405

No. Area Description

1 Button area Three buttons are provided:

l is used to export the summary of neighboring UMTS cell

analysis results. Using this button, you can export the information
about all test cells involved in the analysis task, including the task
name, creator, start time and end time of result information, and
details about each test cell.

l is used to export the neighboring UMTS cell analysis results

of a specified test cell. Using this button, you can export the
information about all inter-RAT neighboring cells of a specified
test cell, including the task name, creator, start time and end time
of result information, BSC, ID, and name of the test cell, and
details about the defined and undefined neighboring UMTS cells
of the test cell.

l is used to export all analysis results of neighboring UMTS

cells of all test cells.
After you click the icon, the Save dialog box is displayed. After
you set the name, format, and save path for the file, the system
saves all neighboring cell analysis results by BSC as a file in the
specified format. Each file maps the neighboring cell analysis
result of one BSC.

2 List of test Lists the information about each test cell.

cells

3 List of Lists all neighboring UMTS cells of selected test cells in area 1.
neighboring In this area, you can perform the following operations;
UMTS cells
l If the User Modify check box of a neighboring UMTS cell is
selected, the system automatically saves the modified information
and displays the modified information when you open the analysis
report next time.
If no operation is performed, the system reads the list information
from the database when you open the analysis report next time.
The modified information is saved as a file in the installation path
of the Nastar client. The file will be automatically deleted when
the task is deleted.
l You can double-click in any part of the list to zoom in and double-
click again to zoom out the list.
l The Nastar provides the functions of filtering and sorting. Click
the column header and choose a filtering item from the drop-
down box to display the table in a filtered way; click the column
header to display the table in the descending order.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 406

No. Area Description

4 Chart area In this area, the information about all neighboring UMTS cells of the
selected cells is displayed in a bar+line chart.
l The system arranges the neighboring UMTS cells in sequence by
their overall priorities and displays the percentages of the top 32
neighboring UMTS cells in a bar chart.
l You can select a parameter from the drop-down list on the upper
right to display the statistical results of the parameter for the top
32 neighboring UMTS cells in a line chart.

Map Interface
After you click on the upper left of the Nastar client, the map interface (Geographic
Observation) is displayed. The Figure 3-22 shows this interface.

Figure 3-22 Map interface for GSM/UMTS neighboring cell analysis results

No. Name Description

1 Button area Displays all the buttons for performing basic operations on the map
interface. For the meanings of these buttons, see 2.2.3 Interface
Description: Geographic Observation Results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 407

No. Name Description

4 Legend area This area is not displayed by default. It is displayed only after you
click in the button area.

5 Information Displays information such as names and engineering parameters of

area the selected cell. If no engineering parameter has been imported for
this cell, a message is displayed in this area.

Interface Description: GSM/UMTS Possible Neighboring Cell Analysis

This section describes the interface for GSM/UMTS possible neighboring cell analysis. Before
you perform the related operations, familiarize yourself with the functions of each area in this
interface.

Opening the Window

You can open the GSM/UMTS possible neighboring cell analysis window in the following
mode:

Select an executed GSM/UMTS neighboring cell analysis task, right-click a result of the task in
the Task Result area, and choose GSM/UMTS Possible Neighboring Analysis from the
shortcut menu.

Main Window
In the main window, the system shows the analysis results of possible neighboring UMTS cells
in charts and lists, including the summary of possible neighboring UMTS cell analysis results
and the confirmation list of possible neighboring UMTS cells, as shown in Figure 3-23.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 408

Figure 3-23 GSM/UMTS Neighboring cell analysis Interface

No. Area Description

1 Button area
is used to export the summary of possible neighboring UMTS cell
analysis results, which are all information about the possible
neighboring UMTS cells in area 2.

2 Summary Lists the summary of the possible neighboring UMTS cells of all cells
of possible involved in the analysis task.
neighborin The Nastar provides the functions of filtering and sorting. Click the
g UMTS column header and choose a filtering item from the drop-down box
cell
analysis to display the table in a filtered way; click the column header to
results display the table in the descending order. You can also press Ctrl+F to
search in the area.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 409

No. Area Description

3 Confirmati Lists all the possible neighboring UMTS cells of selected cells in area
on list of 2.
possible
neighborin l Button area: is used to add possible neighboring UMTS cells
g UMTS for a serving cell. The procedure is as follows:
cells Select a cell in area 2, and click this button. The GSM/UMTS
Possible Neighboring Cell Analysis dialog box is displayed. Select
one or multiple possible neighboring UMTS cells from the
navigation tree, and click OK. One or multiple lines containing the
information about possible neighboring UMTS cells are added to
the list below.
l List of possible neighboring UMTS cells: In the list of possible
neighboring UMTS cells, select the Whether to Use check box of
a possible neighboring UMTS cell. The possible neighboring UMTS
cell is set as the best possible neighboring UMTS cell of the serving
cell in the left area. The information about the corresponding
parameters (such as RNC ID of the Selected Possible Neighboring
Cell and Name of the Selected Possible Neighboring Cell) in the
summary of possible neighboring UMTS cell analysis results is
replaced with the information about this possible neighboring
UMTS cell.
If the check box of Whether to Use is unselected, the information
about the preceding parameters will not be displayed in the left area.
For details about the parameters, see Parameters for Viewing GSM
Possible Neighboring Cell Analysis Results.

3.4.5 Reference for GSM/UMTS Neighboring Cell Analysis

Parameters
This section describes the parameters for GSM/UMTS neighboring cell analysis and possible
GSM/UMTS neighboring cell analysis.

Parameters for Viewing GSM/UMTS Neighboring Cell Analysis Results

This section describes the parameters for querying the analysis reports of GSM/UMTS
neighboring cells. You can refer to the description when querying the analysis reports of GSM/
UMTS neighboring cells.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 410

Parameters About a Test Cell

Parameter Range Unit Description Supported NE
Version

BSC Where 1 to 32 N/A Indicates the BSC6900

Test Cell Is characters name of the V900R014C00
Located BSC that a test (or later) or
cell belongs to, BSC6910
for example, V100R014C00
BSC_1. (or later)

Test Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of a test V900R014C00
cell, for (or later) or
example, BSC6910
Cell_1. V100R014C00
(or later)

FDD REP ECNO N/A Indicates the BSC6900

QUANT RSCP signal receiving V900R014C00
indicator of the (or later) or
UMTS BSC6910
neighboring cell V100R014C00
reported in the (or later)
FDD cell test
report, for
example, ECNO
or RSCP.

Total Number of [0,+∞) Number Indicates the BSC6900

Measurement total number of V900R014C00
Reports Measurement (or later) or
Reports BSC6910
received by a V100R014C00
test cell. (or later)

Configured [0,64] Number Indicates the BSC6900

Neighboring number of V900R014C00
Cells neighboring (or later) or
cells defined for BSC6910
a specified cell. V100R014C00
(or later)

Number of [0,+∞) Number Indicates the BSC6900

Redundant number of V900R014C00
Neighboring redundant (or later) or
Cells neighboring BSC6910
UMTS cells of V100R014C00
the current test (or later)
cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 411

Parameter Range Unit Description Supported NE

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 414

Parameter Range Unit Description Supported NE

Version

User Modify N/A N/A Field for BSC6900

Total Score [0,+∞) N/A Indicates the BSC6900

total score of V900R014C00
each (or later) or
neighboring cell BSC6910
based on the V100R014C00
measurement (or later)
result according
to the
neighboring cell
algorithm.

Integrated [0,+∞) N/A Indicates the BSC6900

Priority integrated V900R014C00
priority of the (or later) or
neighboring BSC6910
UMTS cell. V100R014C00
(or later)

Service Type of Indoor, Outdoor N/A Indicates the BSC6900

Neighboring or null service type of a V900R014C00
Cell neighboring (or later) or
UMTS cell, BSC6910
such as indoor V100R014C00
site, outdoor site (or later)
and unknow
service type.
Learning the
service type of
the neighboring
UMTS cell
prevents
important
neighboring
cells from being
mistakenly
deleted.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 415

Parameter Range Unit Description Supported NE

Version

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the current test (or later) or
cell to a BSC6910
neighboring V100R014C00
UMTS cell. (or later)

Super-Distance Yes, No or null N/A Indicates that BSC6900

the distance V900R014C00
between a (or later) or
specified cell BSC6910
and its V100R014C00
neighboring cell (or later)
exceeds a
predefined
threshold.

Test Duration in [0,+∞) minute Indicates the BSC6900

BA List duration that a V900R014C00
neighboring (or later) or
UMTS cell is BSC6910
measured. V100R014C00
(or later)

UMTS (-∞,0] dB Indicates the BSC6900

Neighboring average RSCP/ V900R014C00
Cell RSCP ECNO of (or later) or
(dBm)/ECNO UMTS BSC6910
(dB) neighboring V100R014C00
cells. Test FDD (or later)
REP QUANT to
decide whether
the data reported
by UMTS
neighboring cell
is the RSCP or
the ECNO.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 416

Parameter Range Unit Description Supported NE

Version

Source Cell (-∞,0] dBm Indicates the BSC6900

Signal Strength average signal V900R014C00
strength of the (or later) or
selected test BSC6910
cell. V100R014C00
(or later)

Number of [0,+∞) Number Indicates the BSC6900

Measurement number of MRs V900R014C00
Reports with including the (or later) or
UMTS Cell UMTS BSC6910
neighboring V100R014C00
cell. (or later)

Number of [0,+∞) Number Indicates the BSC6900

Measurement number of times V900R014C00
Reports with a UMTS cell (or later) or
UMTS Cell ranking No.1 in BSC6910
Ranking First the neighboring V100R014C00
cell list of MR. (or later)

Request [0,+∞) Number Indicates the BSC6900

Number of number of V900R014C00
Handover handover (or later) or
requests from BSC6910
the current V100R014C00
serving cell to (or later)
another cell.

Failure Number [0,+∞) Number Indicates the BSC6900

of Handover number of V900R014C00
handover (or later) or
failures among BSC6910
all handover V100R014C00
requests from (or later)
the current
serving cell to
another cell.

Parameters for Viewing GSM/UMTS Possible Neighboring Cell Analysis Results

This section describes the parameters for querying the analysis reports of GSM/UMTS possible
neighboring cells. You can refer to the description when querying the analysis reports of GSM/
UMTS possible neighboring cells.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 417

Possible Neighboring Cell Overview Table

Parameter Range Unit Description Supported NE
Version

Test Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of a V900R014C00
dominant cell, (or later) or
for example, BSC6910
Cell_1. V100R014C00
(or later)

FDD REP ECNO N/A Indicates the BSC6900

QUANT RSCP signal receiving V900R014C00
indicator of the (or later) or
UMTS BSC6910
neighboring cell V100R014C00
reported in the (or later)
FDD cell test
report, for
example, ECNO
or RSCP.

Test Cell CGI MCC-MNC- N/A Indicates the BSC6900

LAC-CI global ID of a V900R014C00
test cell, for (or later) or
example, BSC6910
286-01-33034-5 V100R014C00
0712. (or later)

Test Cell BCCH [0,1023] N/A Indicates the BSC6900

broadcast V900R014C00
control channel (or later) or
of a test cell. BSC6910
V100R014C00
(or later)

Test Cell BSIC [0,77] N/A Indicates the BSC6900

base station V900R014C00
identity code of (or later) or
a test cell. BSC6910
V100R014C00
(or later)

Neighboring N/A N/A Indicates the BSC6900

Cell DownLink measured V900R014C00
ARFCN downlink (or later) or
ARFCNs of a BSC6910
neighboring V100R014C00
UMTS cell. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 418

Parameter Range Unit Description Supported NE

Version

Neighboring [0,511] N/A Indicates the BSC6900

Cell P-SC measured V900R014C00
primary (or later) or
scrambling code BSC6910
of a neighboring V100R014C00
UMTS cell. (or later)

RNC ID of the [0,+∞) N/A Indicates the BSC6900

Selected number of the V900R014C00
Possible RNC that the (or later) or
Neighboring selected BSC6910
Cell possible V100R014C00
neighboring (or later)
UMTS cell
belongs to.

Name of the 1 to 64 N/A Indicates the BSC6900

Selected characters name of the V900R014C00
Possible selected (or later) or
Neighboring possible BSC6910
Cell neighboring V100R014C00
UMTS cell. (or later)

Neighboring [0,65535] N/A Indicates the BSC6900

Cell CI cell identity V900R014C00
code of the (or later) or
selected BSC6910
possible V100R014C00
neighboring (or later)
UMTS cell.

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the test cell to (or later) or
the selected BSC6910
possible UMTS V100R014C00
neighboring (or later)
cell.

Relative Angle [0,360] (°) Indicates the BSC6900

of Possible relative angle V900R014C00
Neighboring between the (or later) or
Cell selected BSC6910
possible V100R014C00
neighboring (or later)
UMTS cell and
the test cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 419

Parameter Range Unit Description Supported NE

Version

Predicted Signal N/A dBm Indicates the BSC6900

Strength signal strength V900R014C00
of the selected (or later) or
possible UMTS BSC6910
neighboring cell V100R014C00
based on the (or later)
dimensioning.

Get from Config Yes,No N/A Indicates BSC6900

Data whether the V900R014C00
selected (or later) or
possible BSC6910
neighboring V100R014C00
UMTS cell is (or later)
obtained from
the
configuration
data.

Number of 2,3,9 N/A Indicates the BSC6900

Neighboring number of laps V900R014C00
Cell Laps between the (or later) or
selected BSC6910
possible UMTS V100R014C00
neighboring cell (or later)
and the test cell,
that is, the
number of cells
between the
selected
possible
neighboring
UMTS cell and
the test cell.

Number of [0,+∞) N/A Indicates the BSC6900

Possible number of V900R014C00
Neighboring possible (or later) or
Cells neighboring BSC6910
cells in the V100R014C00
possible (or later)
neighboring
UMTS cell pair.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 420

Parameter Range Unit Description Supported NE

Version

Integrated N/A N/A Indicates the BSC6900

Priority integrated V900R014C00
priority of the (or later) or
neighboring BSC6910
UMTS cell. V100R014C00
(or later)

UMTS N/A dB Indicates the BSC6900

Source Cell N/A dBm Indicates the BSC6900

Signal Strength average signal V900R014C00
strength of the (or later) or
selected test BSC6910
cell. V100R014C00
(or later)

Number of [0,+∞) Number Indicates the BSC6900

Neighboring number of MRs V900R014C00
Cell of a UMTS (or later) or
Measurement neighboring BSC6910
Reports cell. V100R014C00
(or later)

Number of [0,+∞) Number Indicates the BSC6900

Times A number of times V900R014C00
Neighboring a UMTS cell (or later) or
Cell Ranking ranking No.1 in BSC6910
No.1 in the neighboring V100R014C00
Measurement cell list of MR. (or later)
Reports

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 421

Possible Neighboring Cell Confirmation Table

Parameter Range Unit Description Supported NE
Version

Whether to Use N/A N/A Indicates BSC6900

whether to V900R014C00
select the (or later) or
current possible BSC6910
neighboring V100R014C00
UMTS cell as (or later)
the most
possible
neighboring cell
of the test cell.
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 the
Selected
Possible
Neighboring
Cell replaces
Neighboring
Cell Name.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 422

Parameter Range Unit Description Supported NE

Version

RNC ID of the
Selected
Possible
Neighboring
Cell replaces
Neighboring
RNC.
CI replaces
Neighboring
Cell CI.
Distance(km)
replaces
Distance(km).
Relative Angle
of Possible
Neighboring
Cell(°) replaces
Relative Angle
of Neighboring
Cell(°).
Predicted Signal
Strength (dBm)
replaces
Predicted Signal
Strength (dBm).
Get from Config
Data replaces
Get from Config
Data.
Number of
Neighboring
Cell Laps
replaces
Number of
Neighboring
Cell Laps.
If this parameter
is not selected, it
indicates that
the most
possible
neighboring cell
is not
determined. In
addition, the
system clears all

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 423

Parameter Range Unit Description Supported NE

Version

the information
in the following
fields in the
possible
neighboring cell
overview table:
Name of the
Selected
Possible
Neighboring
Cell
RNC ID of the
Selected
Possible
Neighboring
Cell
Neighboring
Cell CI
Number of
Neighboring
Cell Laps
Relative Angel
of Neighboring
Cell (°)
Predicted Signal
Strength (dBm)
Get from Config
Data
Number of
Neighboring
Cell Laps

Name of 1 to 64 N/A Indicates the BSC6900

Possible characters cell name of a V900R014C00
Neighboring possible (or later) or
Cell neighboring BSC6910
UMTS cell. V100R014C00
(or later)

RNC ID [0,+∞) N/A Indicates the ID BSC6900

of the RNC that V900R014C00
a possible (or later) or
neighboring BSC6910
UMTS cell V100R014C00
belongs to. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 424

Parameter Range Unit Description Supported NE

Version

CI [0,65535] N/A Indicates the BSC6900

cell identity of a V900R014C00
possible (or later) or
neighboring BSC6910
UMTS cell. V100R014C00
(or later)

Distance [0,+∞) km Indicates the BSC6900

distance from V900R014C00
the test cell to a (or later) or
possible BSC6910
neighboring V100R014C00
UMTS cell. (or later)

Relative Angle [0,360] (°) Indicates the BSC6900

of Possible relative angle V900R014C00
Neighboring between the test (or later) or
Cell cell and a BSC6910
possible V100R014C00
neighboring (or later)
UMTS cell.

Predicted Signal N/A dBm Indicates the BSC6900

Strength signal strength V900R014C00
of a possible (or later) or
neighboring BSC6910
UMTS cell V100R014C00
based on the (or later)
dimensioning.

Get from Config Yes,No N/A Indicates BSC6900

Data whether the V900R014C00
possible (or later) or
neighboring BSC6910
UMTS cell is V100R014C00
obtained from (or later)
the
configuration
data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 425

Parameter Range Unit Description Supported NE

Version

Number of 2,3,9 Number Indicates the BSC6900

Neighboring number of laps V900R014C00
Cell Laps between the test (or later) or
cell and a BSC6910
possible V100R014C00
neighboring (or later)
UMTS cell, that
is, the number of
cells between
the test cell and
a possible
neighboring
UMTS cell.

3.5 GSM Uplink Interference Analysis

The Nastar analyzes uplink levels of cells and displays signal strength of measurement ARFCNs
of certain cells in the analysis results. This provides reference for you to select appropriate
ARFCNs.

3.5.1 Basics of GSM Uplink Interference Analysis

This section describes the basics of GSM uplink interference analysis, including the function,
technical specifications, and feature restrictions. Read this section before performing GSM
uplink interference analysis.
NOTE
For details about the service data types, definition, collection sources, application scenarios, and protection
measures, see Descriptions > Nastar Security Description > Application Security > Protecting Private
Subscriber Data in the Nastar Product Documentation.

Functions of GSM Uplink Interference Analysis

The Nastar provides the GSM uplink interference analysis function to analyze the average uplink
interference strength of the diversity and main antennas. During network planning, this function
can be used to find frequency resources that are not interfered on the network. During network
optimization, this function can be used to analyze measurement results to find frequency
resources with higher quality for source cells that generate interference. During network
assurance, this function can be used to evaluate the interference level of the network.

Function Description
The Nastar analyzes the uplink levels of a cell to display the received signal strength of the
measurement ARFCNs in this cell. This provides reference for you to select appropriate
ARFCNs.
Huawei BTSs can scan the uplink receive levels of all frequencies at P-GSM (1–124), E-GSM
(0, 975–1023), R-GSM (955–974), DCS1800 (512–885), PCS1900 (512–810),

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 426

GSM850_BAND (128–251) or FB_BAND_TGSM810 (350–425). That is, Huawei BTSs can

scan the interfering signal strength at any of the preceding frequencies.

Huawei BTS3X series BTSs perform uplink interference analysis based on the following
principles: Without affecting normal calls, the BTSs use the IDLE frame of a TCH within the
measurement cell to repeatedly scan the uplink receive levels of specified ARFCNs. When the
BSC allocates TCHs, the BTSs prefer the IDLE frame of the TCH at the TRX where the BCCH
is located. Therefore, the BTSs can scan only the ARFCNs that are in the same frequency band
as the ARFCN of the measurement cell.

The TCH adopts the structure of 26 multiframes. Each TCH multiframe contains an IDLE frame.
The period of the IDLE frame on the TCH is 26 multiframes x 0.577 (Burst length) x 8 (TDMA
frame) = 120 ms. Each ARFCN is measured 10 times and about one minute is required for
measuring 50 ARFCNs. An uplink interference analysis task records a maximum of 124
ARFCNs. Therefore, about three minutes are required for measuring these ARFCNs.

After you create an uplink interference analysis task, the Nastar will perform uplink interference
analysis on the selected cells. The analysis results can be displayed in bar charts or line charts
that use different colors to show the average main and diversity interference strength for each
ARFCN at each time point.

Function Principles
The Nastar uses the scanned uplink frequency data on the U2000/M2000 for GSM uplink
interference analysis.

Figure 3-24 shows the principles for collecting, importing, and analyzing data by using the
Nastar on a newtork where NEs such as BSC6900s (excluding eGBTSs) are deployed. For
detailed operations, see Table 3-16.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 427

Figure 3-24 Principles for analysis

Table 3-16 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

1. Issue an Nas U20 To request the U2000/M2000 to filter out the scanned
Subscri applicat tar 00/ uplink frequency data that meets the Nastar's
be to ion data Ser M20 requirements. After a user enables the application data
applicat subscrip ver 00 subscription function on the Nastar client, the Nastar
ion data tion issues an application data subscription command to the
comma eSAU.
nd

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 428

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Upload U2 Nast The Nastar periodically scans the directories on the

scanned 000 ar U2000/M2000 for saving reported data. By doing this,
uplink / Serv the Nastar can obtain data from the U2000/M2000
frequen M2 er immediately once data is reported.
cy data 000

2. Issue - Nast To issue a data query command to the Nastar server.

Check data ar After a user enables the data maintenance function on
the query Serv the Nastar client, the Nastar checks whether the analysis
integrit comma er data is ready on the Nastar server. To return data integrity
y of nds and check results to the Nastar client and display the results
analysi return on the Nastar client.
s data data
query
results

3. Issue - Nast To issue a task execution request to the Nastar server.

Create task ar After a user creates an analysis task on the Nastar client,
and executio Serv the Nastar client issues a task execution command to the
execute n er Nastar server, requesting the Nastar server to aggregate
an comma data. To aggregate the data reported by SAUs, generate
analysi nds and data analysis results, and upload the data analysis results
s task upload to the Nastar client.
data
analysis
results

4. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

Figure 3-25 shows the principles for collecting, importing, and analyzing data by using the
Nastar on a network where eGSM BTSs are deployed. For detailed operations, see Table
3-17.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 429

Figure 3-25 Principles for analysis

Table 3-17 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

1. Issue an Nas eSA To request the U2000/M2000 to filter out the scanned
Subscri applicat tar U uplink frequency data that meets the Nastar's
be to ion data Ser requirements. After a user enables the application data
applicat subscrip ver subscription function on the Nastar client, the Nastar
ion data tion issues an application data subscription command to the
comma eSAU.
nd

Collect eS U20 The eSAU delivers data processing requests to NEs

scanned AU 00/ through the U2000/M2000, requesting the NEs to report
uplink M20 scanned uplink frequency data to the U2000/M2000.
frequen 00
cy data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 430

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Upload U2 Nast The eSAU periodically scans the directories on the

scanned 000 ar U2000/M2000 for saving reported data. By doing this,
uplink / Serv the eSAU can notify the Nastar of obtaining data from
frequen M2 er the U2000/M2000 once data is reported.
cy data 000

2. Issue - Nast To issue a data query command to the Nastar server.

3. Issue - Nast To issue a task execution request to the Nastar server.

4. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

Technical Specifications for GSM Uplink Interference Analysis

This section describes the technical specifications.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 431

Item Service Specifications

Execution type One-time task

Network scale for one analysis task <= 1000 cells

Number of allowed analysis tasks <= 50

Time range for data in one analysis 7 days

task

Duration of one analysis task <= 135 minutes

Default duration for storing 15 days

analysis data

Maximum duration for storing 15 days

analysis data

3.5.2 Preparations for GSM Uplink Interference Analysis

Before starting a GSM uplink interference analysis task, you must check the operation rights
and the matching environment and prepare relevant data. Read this section before performing
GSM uplink interference analysis.

Checking the License and User Rights

l Check that you have applied the license for GSM uplink interference analysis and the
license is valid.
l Check that the login user has the rights to subscribe to the source data for GSM uplink
interference analysis, create GSM uplink interference analysis tasks, and perform
operations on the NEs involved in these tasks.

Preparing Basic Data

Configuration Data
The configuration data of NEs related to the measurement cells is used to obtain the scanned
uplink frequency data of cells from the network. The configuration data is also used to analyze
cell information in MRs and information about the following cells: cells to which subscribers
have gained access, cells from which subscribers have been released, and cells to which
subscribers are handed over.
If the OSS information has been already configured, the Nastar automatically and periodically
collects and imports the configuration data after the OSS and NE information is configured. You
can also manually collect the configuration data before the specified time period starts. After
the configuration data is imported, you can choose Maintenance > Data Maintenance
Management to check whether the configuration data is available in the Nastar database. For
detailed information about collecting, importing, and checking, see 2.5.2 Checking the
Integrity of Configuration Data.
After the configuration data has been successfully imported, you are advised to check the validity
of the configuration data. The purpose is to avoid expiration of configuration data due to network

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 432

adjustment. Expired configuration data may cause incorrect cell information in the analysis
result. For detailed operations, see Checking Engineering Parameters and Configuration
Data.

Checking the Matching Environment

l Check that the OSS version used with the Nastar is U2000/M2000 V200ROO9SPC261 or
U2000/M2000 V200R010SPC231 or later and the NE version is BSC6000
V900R008C12SPC25 or BSC6900 V900R011C00SPH721 or later.
l Check that the U2000/M2000 has the license for obtaining the scanned uplink frequency
data. For detailed operations, see section Commissioning the Function of Obtaining the
Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) >
Checking the License on the M2000/GBSC License(GSM) in Nastar System
Commissioning Guide.

3.5.3 Process of GSM Uplink Interference Analysis

This section describes the GSM uplink interference analysis process.

l Prerequisites
l Procedure
l Subscription Task Parameters
l Analysis Task Parameters

Prerequisites
GSM configuration data has been imported into the Nastar database. For detailed operations,
see 3.5.2 Preparations for GSM Uplink Interference Analysis.

Procedure
Figure 3-26 shows the analysis process.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 433

Figure 3-26 Analysis process

Subscription Task Parameters

Application Subscription

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 437

Parameter Description

Task Name Indicates the name of a created analysis task.

Value range:
l The name contains a maximum of 60 characters.
l Characters not allowed: ` ~ ! @ # $ % ^ & * ( ) + { } [ ] \ / | ; ' : , . ? <
>"
l Do not use special characters entered by pressing Tab or Enter.
l The name is unique and case-sensitive. It cannot be left empty.

Start Time Start time of a measurement task.

The start time must be later than the current time. By default, the start time
is five minutes later than the current system time.

Cycle Interval between executing a measurement task. The default value is one
day and cannot be changed.
NOTE
Data generated within a total of 30 minutes is lost for every 20-hour (or shorter)
period due to data collection and system delays.

Execute Times Number of times for executing a measurement task. If this parameter is
set to 0, the task is executed without the limit of times.

Time(Minute) Total duration that a measurement task is performed.

The value is an integer from 5 to 1410.
NOTE
When a single BSC serves 2048 cells according to its full configuration, the duration
of a single subscription cannot exceed 6 x 60 minutes due to subscription capability
restrictions on a single BSC.

NE Type The supported NE types.

Frequency Frequency band used by a cell.

Segment The following frequency bands are supported:
l P-GSM (1 to 124)
l E-GSM (0, 975 to 1023)
l R-GSM (955 to 974)
l DCS1800 (512 to 885)
l PCS1900 (512 to 810)
l GSM850_BAND (128 to 251)
l FB_BAND_TGSM810 (350 to 425)

Cell Object Cells involved in a GSM uplink interference analysis task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 438

Parameter Description

Frequency Type Type of the measurement ARFCNs. The options are as follows:
l All Frequency in The Frequency Segment
All ARFCNs in the selected frequency band.
l All Configuration in the Selected Cells
All ARFCNs in the selected cell.
l User Defined in The Frequency Segment
ARFCNs you select manually. The selected ARFCNs are displayed in
yellow.

Analysis Task Parameters

Basic task information

Parameter Description

Task Name Name of an analysis task.

Task Type Type of an analysis task to be created.

Remarks Description of the task.

Value range: The name contains a maximum of 200 characters.

NE information

Parameter Description

Select NE(s) NEs or cell groups to be selected for analysis.

Parameter description

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 439

Parameter Description

Minimum Threshold of the average uplink interference strength of the diversity

Diversity antenna.
Threshold The value is an integer from -115 to 0. The default value is -115.
Unit: dBm

Minimum Main Threshold of the average uplink interference strength of the main antenna.
Threshold The value is an integer from -115 to 0. The default value is -115.
Unit: dBm

Frequency Type Type of an ARFCN.

The value can be BCCH or TCH.

Average Algorithm for calculating the average value.

Calculation The value can be Signal Strength or Power. If the parameter is set to
Algorithm Signal Strength, the average value is calculated directly based on the
signal strength. If the parameter is set to Power, 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.

Time information of one-time task

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

Delay If you do not select this parameter, the system executes the task
immediately.
If you select this parameter, the system executes the task at the time
specified in Execute on.

Execute on Time when a task is executed.

3.5.4 Interface Description: GSM Uplink Interference Analysis

This section describes the interface that displays the results of GSM uplink interference analysis.
Before performing relevant operations, familiarize yourself with the functions of the areas on
this interface.

Portal
Use either of the following methods to open the interface that displays GSM uplink interference
analysis results:

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 440

l Select an executed GSM uplink interference analysis task and double-click a result record
in the Task Result area.
l Select an executed GSM uplink interference analysis task, right-click a result record in the
Task Result area, and choose View Analysis Result from the shortcut menu.

Main Interface
The uplink interference analysis results are displayed in one table and two charts: table of
measurement cells, bar chart of interference strength, and line chart of interference strength.
Figure 3-27 shows the interface.

Figure 3-27 Interface for GSM uplink interference analysis results

N Name Description
o.

1 Cell Displays the interference strength of all measurement cells involved in an

informati analysis task.
on table Right-click on the table and choose Save As from the shortcut menu. After
you set the file name, file type and save path, the Nastar will save the
analysis results in this table as a file.

2 Informati Displays the basic information about the selected cell, including the cell
on area name, BCCH frequency, frequency hopping mode, time range, location
group number, BSC name, and TCH list.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 441

N Name Description
o.

3 Bar chart Displays the interference strength of all ARFCNs in the selected cell at a
of certain time point.
interferen l The horizontal coordinate lists ARFCNs sequentially from left to right
ce after you can set Sort Type.
strength
– When you set Sort Type to Frequency, the bar chart displays the
main and diversity interference strength of ARFCNs from left to
right according to ARFCN values.
– When you set Sort Type to Main, the bar chart displays the main
and diversity interference strength of ARFCNs from left to right
according to the main interference strength.
– When you set Sort Type to Diversity, the bar chart displays the main
and diversity interference strength of ARFCNs from left to right
according to the diversity interference strength.
l The vertical coordinate represents the interference strength. To ensure
that the interference strength values are positive, the values displayed
on the vertical coordinate are the results of the actual interference
strength values plus 110.
l In the bar chart area, you can right-click the chart and choose an option
from the shortcut menu to modify the attributes, resize, save, or print
the chart.

4 Line Displays the interference strength of a certain ARFCN in the selected cell
chart of within a specified time period. You can select the ARFCN from the
interferen Frequency drop-down list.
ce l The horizontal coordinate represents the time period.
strength
l The vertical coordinate represents the interference strength of the
ARFCN.

3.5.5 Parameters for Viewing GSM Uplink Interference Analysis

Results
This section describes the parameters for viewing GSM uplink interference analysis results. You
can refer to the description when viewing GSM uplink interference analysis results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 442

Measurement Cell Overview Information

Parameter Range Unit Description Supported NE
Version

BSC Name 1 to 32 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Cell ID [0,65535] N/A Indicates the ID BSC6900

of a cell. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that a measured (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Location Group 0 to 35 or null N/A Number of the BSC6900

Number location group V900R014C00
under the BTS. (or later) or
It is unique for BSC6910
each BTS. V100R014C00
(or later)

Frequency [0,1023] N/A Indicates the BSC6900

frequency of a V900R014C00
measured TRX. (or later) or
BSC6910
V100R014C00
(or later)

Type BCCH, TCH N/A Indicates the BSC6900

type of a V900R014C00
measured TRX. (or later) or
The options are BSC6910
BCCH and V100R014C00
TCH. (or later)

Main Average [-120,-47] dBm Indicates the BSC6900

Interference average main V900R014C00
Strength interference (or later) or
strength of a BSC6910
measured TRX. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 443

Parameter Range Unit Description Supported NE

Version

Diverse [-120,-47] dBm Indicates the BSC6900

Average average V900R014C00
Interference diversity (or later) or
Strength interference BSC6910
strength of a V100R014C00
measured TRX. (or later)

Parameters
Parameter Range Unit Description Supported NE
Version

Cell Name 1 to 64 N/A Indicates the BSC6900

characters name of the cell V900R014C00
that a measured (or later) or
TRX belongs to. BSC6910
V100R014C00
(or later)

Location Group 0 to 35 or null N/A Number of the BSC6900

Number location group V900R014C00
under the BTS. (or later) or
It is unique for BSC6910
each BTS. V100R014C00
(or later)

BSC Name 1 to 32 N/A Indicates the BSC6900

characters name of a BSC, V900R014C00
for example, (or later) or
BSC_1. BSC6910
V100R014C00
(or later)

Time Range N/A N/A Indicates the BSC6900

time range in V900R014C00
which an uplink (or later) or
interference BSC6910
analysis task is V100R014C00
performed. (or later)

BCCH N/A N/A Indicates a BSC6900

Frequency BCCH ARFCN V900R014C00
of the selected (or later) or
cell. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 444

Parameter Range Unit Description Supported NE

Version

Frequency No Frequency N/A Indicates the BSC6900

Hopping Mode Hopping, type of the V900R014C00
Baseband frequency (or later) or
Frequency hopping. BSC6910
Hopping, RF V100R014C00
Frequency (or later)
Hopping,
BCCH-
involved
baseband
Frequency
Hopping

TCH List N/A N/A Indicates all BSC6900

TCH ARFCNs V900R014C00
of the selected (or later) or
cell. BSC6910
V100R014C00
(or later)

Time Point N/A N/A Indicates the BSC6900

counter bar V900R014C00
chart of the (or later) or
selected cell at a BSC6910
certain time. V100R014C00
(or later)

Sort Type Frequency, N/A Indicates the BSC6900

Diversity, Main data sequence V900R014C00
mode in the bar (or later) or
chart. BSC6910
Diversity V100R014C00
indicates the (or later)
average
diversity
interference
strength. Main
indicates the
average main
interference
strength.

Date N/A day Time period for BSC6900

the analysis V900R014C00
results of a (or later) or
selected cell. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 445

Parameter Range Unit Description Supported NE

Version

Frequency [0,1023] N/A Indicates the BSC6900

trend of the V900R014C00
strength of a (or later) or
frequency in the BSC6910
selected cell in a V100R014C00
certain time (or later)
segment. The
trend is
displayed on a
line chart.

3.6 GSM Terminal Analysis

3.6.1 Basics of GSM Terminal Analysis

This section describes the basics of GSM terminal analysis, including the terminal analysis
function, technical specification, and feature restriction. The basic knowledge helps you perform
the operations related to GSM terminal analysis. Read this section before performing GSM
terminal analysis.

Functions of GSM Terminal Analysis

This section describes the basic knowledge of GSM terminal inventory analysis. The GSM
terminal inventory analysis function enables the Nastar to analyze the performance of various
types of terminals and subscriber behavior from the perspective of terminals based on CHR data
on the live network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 446

Function Description
Call records of subscribers can reflect the access performance, service retainability, and intra-
RAT handover performance of terminals. KPIs related to delay, service quality, and traffic can
reflect the terminal capability.

GSM terminal analysis includes terminal inventory analysisand terminal geographic

observation. Terminal inventory analysis includes terminal penetration analysis, terminal
capability analysis, and terminal performance analysis.:
l Terminal Infiltrate Rate Analysis. The Nastar displays the distribution of terminals on the
live network by different dimensions such as vendor or terminal model to guide the follow-
up network building and marketing strategies.
l Terminal capability analysis. The Nastar evaluates the proportion of each terminal type
supporting specific terminal capabilities in the GSM network to provide data support for
professional network services or consultations. For example, the proportion of terminals
that support the EGPRS is small in the network, you can set the number of GPRS-dedicated
channels to improve the user experience of the GPRS subscribers.
l Terminal performance analysis. The Nastar provides the terminal-level and cell-level data
aggregation function based on KPIs. Based on aggregation results of terminal-level KPIs
and cell-level KPIs, you can determine whether poor terminal performance is caused by a
terminal defect or is affected by special cells (for example, neighboring GSM cells of
UMTS cells).
l Terminal geographic observation. The Nastar supports the display of terminal distribution
using the Geographic Information System (GIS) and supports the geographic display from
the two dimensions of terminal flow consumption and terminal support ability, which helps
network optimization engineers to analyze problems and improve the efficiency of locating
problems.

Function Principles
The data source for terminal analysis is the CHR data on the NE side.

Figure 3-28 shows the principles for collecting, importing, and analyzing data on the Nastar.
For detailed operations, see Table 3-19.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 447

Figure 3-28 Principles for analysis

Table 3-19 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

1. Issue a Nas eSA To turn on the data source switch on the NE side. After
Subscri basic tar U a user enables the basic data subscription function on the
be to data Ser Nastar client, the Nastar issues a basic data subscription
basic subscrip ver command to the eSAU.
data tion
comma
nd

Issue an eS U20 To issue an MML command to the U2000/M2000.

MML AU 00/
comma M20
nd 00

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 448

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Forward U2 BSC/ To forward the MML command to the NE through the

the 000 RNC U2000/M2000, requesting the NE to generate raw data.
MML /
comma M2
nd 000

Upload BS SAU To upload the raw data to the SAU.

raw data C/
RN
C

2. Issue an Nas eSA To deliver a data-preprocessing request to the eSAU.

Subscri applicat tar U After a user enables the application data subscription
be to ion data Ser function on the Nastar client, the Nastar issues a data-
applicat subscrip ver processing command to the eSAU.
ion data tion
comma
nd

Deliver eS SAU To deliver a data-preprocessing request to the SAU,

a data- AU requesting the SAU to start the data-preprocessing task.
preproc
essing
task
(direct)

Upload SA eSA To upload preprocessed data to the eSAU.

preproc U U
essed
data
(direct)

3. Issue a Nas eSA To enable the data maintenance function. After a user
Check data tar U enables the data maintenance function on the Nastar
the query Ser client, the Nastar checks whether the analysis data is
integrit comma ver ready on the eSAU.
y of nd
analysi
s data Return eS Nast To return data integrity check results to the Nastar server
data AU ar and display the results on the Nastar client.
query Serv
results er

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 449

User Proced So Dest Purpose

Operat ure urc inati
ion e on

analysi Upload eS Nast To aggregate the data reported by SAUs, generate data
s task data AU ar analysis results, and upload the data analysis results to
analysis Serv the Nastar server.
results er

5. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

Technical Specifications for GSM Terminal Analysis

This section describes the technical specifications, including the analysis ability and the range
of analysis time.

Item Service Specifications

Execution type One-time task

Network scale for one l <= 10,000 cells (for terminal inventory analysis)
analysis task l <= 10,000 cells (for terminal geographic observation)

Number of allowed <= 50

analysis tasks

Time range for data in 7 days

one analysis task

Duration of one analysis l Terminal inventory analysis: <= 90 minutes

task l Terminal geographic observation: <= 80 minutes

Default duration for 15 days

storing analysis data

Maximum duration for 15 days

storing analysis data

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 450

3.6.2 Preparations for GSM Terminal Analysis

Before running a GSM terminal analysis task, check and prepare the basic information to ensure
that the terminal analysis task can be performed successfully. Read this section before
performing GSM terminal analysis.

Verifying the License and User Rights

l Ensure that the License for GSM terminal analysis is applied and the License is valid.
– The license for GSM terminal inventory analysis is required for viewing the functions
of GSM terminal penetration analysis, GSM terminal ability analysis, and GSM
terminal performance analysis.
– The license for GSM terminal geographic display is required for viewing the function
of GSM terminal geographic display.
l If a user wants to view only the task results, only the rights to view terminal analysis results
needs to be granted. If the user wants to perform further operations on tasks, the following
rights must be granted:
– Right to subscribe to the source data for terminal analysis.
The source data subscription function has high security requirements. You are advised
to contact the administrator to turn on the data source switch.
– Right to perform operations on the NEs to be analyzed.
– Right to perform operations on terminal analysis tasks.
– You need to obtain right to perform GSM terminal inventory analysis if you want
to perform GSM terminal penetration analysis, GSM terminal capability analysis,
and GSM terminal performance analysis.
– You need to obtain right in order to perform GSM terminal geographic observation.

Preparing Basic Data

Terminal information

Terminal information indicates the IMEI-TAC, vendor, terminal model, chip model, terminal
type, terminal technology, and data transfer information. The system can display other
information about a terminal based on the IMEI-TAC detected by the live network to help users
to perform well-targeted terminal analysis.

In the navigation tree of the Analysis Task Management window, choose System Function >
Terminal Type Management. Then double-click Terminal Type Management. Import or edit
the terminal information as required. For details, see 2.5.7 Managing Terminal Information
(Terminal Analysis).

Configuration Data

The configuration data of the NEs for the area corresponding to the terminal is used to extract
the cell performance analysis data from the network and analyze the access cell, release cell,
handover cell, and the cell information in the relevant measurement result during the terminal
analysis process.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 451

the configuration data is imported, you can choose Maintenance > Data Maintenance
Management to check whether the configuration data is available in the Nastar database. For
detailed information about collecting, importing, and checking, see 2.5.2 Checking the
Integrity of Configuration Data.

NOTE

You are advised to perform terminal analysis with the granularity of a day to ensure the validity and
timeliness of the configuration data.
Engineering Parameters (Optional)

Map files (Optional)

The map file for a specific area displays the analysis result geographically. You do not need to
prepare the map file if you do not want to view the analysis result on the map.

Checking the Analysis Environment

l GSM RAN CS analysis: Check that the matching U2000/M2000 version is V200R012C00
(or later), and the NE version is BSC6900 V900R014C00 (or later) or BSC6910
V100R014C00 (or later).
l GSM RAN PS analysis: Check that the matching U2000/M2000 version is V200R012C00
(or later), and the NE version is BSC6900 V900R014C00 (or later), and BSC6910
V100R014C00 (or later).
l Check that the user identity information (IMSI and IMEI) reporting switch has been turned
on. For detailed operations, see Commissioning the Function of Obtaining the Data >
Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On
the User Identity Information Reporting Switch (GSM) in Nastar Commissioning
Guide.
l If you want to analyze the terminal geographic observation function, check that the PS
network control mode is set. For detailed operations, see Commissioning the Function of
Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data
(GSM) > Setting the PS Network Control Mode in Nastar Commissioning Guide.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 452

3.6.3 Process of GSM Terminal Analysis

This section describes the GSM terminal analysis process and the brief procedure of each
process.

This section includes the following information:

l Prerequisites
l Process
l Subscription Task Parameters
l Analysis Task Parameters

Prerequisites
The GSM configuration data and GSM engineering parameters have been imported to the Nastar
database. The terminal types has been configured on the Nastar. For details, see 3.6.2
Preparations for GSM Terminal Analysis.

Process
Figure 3-29 shows the analysis process.

Figure 3-29 Analysis process

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 453

Table 3-20 Description of the terminal analysis process

No. Procedure Description Reference

(1) Check Navigation path: Choose Maintenance > Data 2.7 Checking
whether Maintenance Management the Integrity of
analysis Procedure: Analysis Data
data is
integrated? 1. Set Data Type to GSM Terminal Inventory
Analysis Dataor GSM Terminal Geographic
Observation Data.
NOTE
l Only GSM Terminal Inventory Analysis Data
is required to analyze terminal penetration rate,
capability, and performance.
l Only GSM Terminal Geographic Observation
Data is required to observe terminals
geographically.
2. Set the query time period.
3. Select the NEs to be queried.
4. Click Query.
The query results are displayed in the right pane
of the window.
l If analysis data exists, perform (3) to create
an analysis task.
l If analysis data does not exist, request the
administrator to subscribe to the data by
performing (2).
NOTE
The data subscription function has high security
requirements. You are advised to contact the
administrator with subscription rights to perform
the subscription operation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 454

No. Procedure Description Reference

(2) Subscribe Navigation path: Choose Maintenance > Data 2.6.2 Basic
to analysis Subscription Management Subscription of
data Procedure: Analysis Data
(basic).
1. In the Data Subscription Management
window, click the GSM tab.
2. Select the NEs to be configured from the left
navigation tree.
3. On the Basic Subscription Settings tab page,
click Set.
4. In the Basic Subscription Settings dialog box,
set the switch of Terminal Analysis Data
(CHR-CS), Terminal Analysis Data(CHR-
PS) to ON.
5. Click Confirm.
Verify that the data switch is successfully turned
on by viewing information displayed in the Log
Info area.

Subscribe Navigation path: Choose Maintenance > Data

to analysis Subscription Management
data Procedure:
(applicatio
n). 1. In the Data Subscription Management
window, click the GSM tab.
2. Select the NEs to be configured from the left
navigation tree.
3. On the Terminal Analysis tab page, click ON.
4. In the Terminal Analysis Parameter Settings
dialog box, set the threshold value for
exceptions. For details about parameters, see
Subscription Task Parameters.
5. Click Confirm.
Verify that data subscription is successfully
turned on by viewing information displayed in
the Log Info area.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 455

No. Procedure Description Reference

Check Navigation path: Choose Maintenance > Data 2.7 Checking

whether Maintenance Management the Integrity of
analysis Procedure: Analysis Data
data is
integrated? 1. Set Data Type to GSM Terminal Inventory
Analysis Dataor GSM Terminal Geographic
Observation Data.
NOTE
l Only GSM Terminal Inventory Analysis Data
is required to analyze terminal penetration rate,
capability, and performance.
l Only GSM Terminal Geographic Observation
Data is required to observe terminals
geographically.
2. Set the query time period.
3. Select the NEs to be queried.
4. Click Query.
The query results are displayed in the right pane
of the window.
l If analysis data exists, perform (3) to create
an analysis task.
l If the analysis data does not exist, contact
Huawei technical support.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 456

No. Procedure Description Reference

(3) Create an Navigation path: In the left navigation tree of the 2.8 Creating an
analysis Analysis Task Management window, choose Analysis Task
task. Theme Function > Terminal Analysis > GSM
Terminal Analysis.
Procedure:
1. Double-click the GSM Terminal Analysis
node.
2. Set the task name and task remarks. Click Next.
3. On the Select NE(s) tab page, select the NEs to
be analyzed. You can select NEs by BSC or Cell
Group.
4. Optional: On the Geographic Terminal
Objects tab page, select terminals for analysis.
You can select a maximum of 10 terminals. The
Nastar automatically analyzes traffic of selected
terminals in each raster.
5. Optional: On the Geographic Terminal
Abilities tab page, select terminal capabilities
for analysis. The Nastar calculates numbers and
percentages of terminals supporting the
capabilities in each raster.
6. Optional: On the Grid Resolution Settings tab
page, select the Grid Resolution for displaying
terminal geographic observation results.
7. Click Next.
8. Select the analysis time period. The Nastar
obtains the relevant analysis data in the time
period.
9. Click Finish.
For details about parameters, see Analysis Task
Parameters.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 457

No. Procedure Description Reference

Parameter Description

Overlong Call Indicates the threshold for an extra long call setup duration when a
Setup Duration terminal initiates a call. The call setup duration indicates the average
Threshold duration from the Channel Request message to the Alerting message.
(MOC) Value range: [0.00,255.00], unit: s.

Overlong Call Indicates the threshold for an extra long call setup duration when a
Setup Duration terminal terminates a call. The call setup duration indicates the average
Threshold duration from the Channel Request message to the Alerting message.
(MTC) Value range: [0.00,255.00], unit: s.

Uplink VQI Indicates the threshold for uplink Voice Quality Indicator (VQI)
Abnormal exceptions of the voice service.
Threshold The VQI is the Mean Opinion Score (MOS) and reflects the voice quality
during a call.
Value range: [0.0,5.0] The larger the value is, the better the voice quality
is.

Uplink HQI Indicates the threshold for uplink High Quality Indicator (HQI) exceptions
Abnormal of the voice service.
Threshold The HQI reflects the voice quality in a call. The HQI is classified into
eight levels from 0 to 7. Levels 0 indicates the best quality.
In the CHR of BSC6900 V900R011 and later versions: HQI = Number of
the measurement reports with the reception quality of level 0 to level 3/
Number of the measurement reports with the reception quality of level 0
to level 7 x 100%
In the CHR of BSC6000 V900R008 version: HQI = Number of the
measurement reports with the reception quality of level 0 to level 5/
Number of the measurement reports with the reception quality of level 0
to level 7 x 100%
Value range: [0.0,100.0], unit: %.

Downlink HQI Indicates the threshold for downlink HQI exceptions of the voice service.
Abnormal The HQI reflects the voice quality in a call and is classified into eight
Threshold levels from 0 to 7. Levels 0 indicates the best quality.
In the CHR of BSC6900 V900R011 and later versions: HQI = Number of
the measurement reports with the reception quality of level 0 to level 3/
Number of the measurement reports with the reception quality of level 0
to level 7 x 100%
Value range: [0.0,100.0], unit: %.

Analysis Task Parameters

Basic task information

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 461

Parameter Description

Task Name Name of an analysis task.

Task Type Type of an analysis task to be created.

Remarks Description of the task.

Value range: The name contains a maximum of 200 characters.

NE information

Parameter Description

Select NE(s) NEs or cell groups to be selected for analysis.

Parameter information

Parameter Description

Grid Resolution Set the Grid Resolution for displaying terminal geographic observation
Settings results.
By default, this parameter is set to 50, and the size of displayed grids is
50m*50m. If you set this parameter to 100, the size of displayed grids is
100m*100m.

Geographic Selects terminal capabilities. After you select terminal capabilities, the
Terminal Nastar geographically displays the selected terminal capabilities.
Abilities If the parameters are not set, the Nastar does not geographically display
the terminal capabilities.

Geographic Selects terminal objects. After you select terminal objects, the Nastar
Terminal geographically displays the traffic of the selected terminal objects. You
Objects can select a maximum of ten terminal objects.
If the parameters are not set, the Nastar does not geographically display
the traffic of terminals.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 462

Time information of one-time task

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

Delay If you do not select this parameter, the system executes the task
immediately.
If you select this parameter, the system executes the task at the time
specified in Execute on.

Execute on Time when a task is executed.

3.6.4 Interface Description: GSM Terminal Analysis

This section describes the interface that displays the results of GSM terminal analysis. It also
describes the functions of each area on the interface to help you perform related operations.

Navigation Path
Use either of the following methods to open the interface that displays GSM terminal analysis
results:
l Select a GSM terminal analysis task in the Complete state and double-click a result record
in the Task Result area.
l Select a GSM terminal analysis task in the Complete state, right-click a result record of
the task in the Task Result area, and choose View Analysis Result from the shortcut menu.

Interface
Figure 3-30 shows the GSM terminal analysis result interface.

Figure 3-30 Interface for GSM terminal analysis results

No. Item Description

1 Icon area
is used to display terminal analysis results on maps. For
detailed operations, see Terminal Analysis Results Displayed
Through Geographic Observation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 463

No. Item Description

2 Analysis result Analysis results are displayed on tab pages.

tab page l The Market Share tab page is used to analyze the
occupation of terminals on the live network from different
dimensions. For detailed operations, see Interface
Description: Terminal Penetration Analysis.
l The Capability tab page is used to analyze the proportion
of each terminal capability supported by the terminals on the
live network. For detailed operations, see Interface
Description: Terminal Capability Analysis.
l The Performance tab page is used to analyze the
performance indicator of each type of terminal and analyze
the performance indicator of a type of terminal in each cell.
For detailed operations, see Interface Description:
Terminal Performance Analysis.

Interface Description: Terminal Penetration Analysis

The terminal-penetration analysis result shows the occupation of terminals on the live network
from different dimensions in the form of a chart and a table. Figure 3-31 shows the tab page.

Figure 3-31 Terminal penetration evaluation

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 464

No. Item Description

1 Icons and
analysis l is used to export terminal penetration analysis results
options into files of specified formats from different dimensions.
Analysis results of the same dimension are saved in one file.
l Dimension is used to specify analysis options.
l TOPN is used to specify the number of TopN analysis
objects.

2 Statistics chart The occupation of TopN terminals on the live network from a
certain analysis dimension is displayed in a pie chart. The pie
chart is displayed together with the table below the chart.

3 Statistics table The number and occupation of TopN terminals on the live
network from a certain analysis dimension are displayed in a
table. You can save the table by right-clicking the table and
choosing Save As from the shortcut menu.

Interface Description: Terminal Capability Analysis

The terminal capability analysis result shows the occupation of different capabilities supported
by the terminals in a histogram and a table. Figure 3-32 shows the tab page.

Figure 3-32 Terminal capability evaluation

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 465

No. Item Description

1 Icon area
is used to specify the file name and save path. After the
file name and save path are specified, the Nastar exports the
capability analysis results for all terminals into files of specified
formats.

2 NE object Selects all objects to be analyzed.

navigation tree Allows users to select objects for analysis from three
dimensions: whole network, a single BSC, or a single cell.

3 Terminal Selects the terminal capability to be analyzed. If you select one

capability list or more terminal capabilities, the capability analysis results are
displayed in both the chart area and table area on the right.

4 Chart area The proportion of the terminals that support a certain terminal
capability in an NE object and the proportion of the terminals
that do not support a certain terminal capability in an NE object
are displayed in a histogram. The histogram is mapped to the
table on the right.
The analysis results of a maximum of two types of terminal
capabilities can be displayed at the same time. You can view the
analysis results of other terminal capabilities by using the scroll
bar.

5 Table area The number and occupation of the terminals that support a
certain terminal capability in an NE object are displayed in a
table. You can save the table by right-clicking the table and
choosing Save As from the shortcut menu.
For detailed parameters, see 3.6.5 Parameters for Viewing
GSM Terminal Analysis Results.

Interface Description: Terminal Performance Analysis

The terminal performance analysis table shows the terminal performance indicator, and the
performance indicator of a certain type of terminal in each cell. Figure 3-33 shows the tab page.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 466

Figure 3-33 Terminal performance evaluation

No. Item Description

1 Analysis l The Aggregation Type drop-down list is used to select an

indicator aggravation dimension.
navigation tree l The Terminal Properties node is used to select a terminal
attribute. All attributes are selected by default. If you
deselect a node, the indicator information is not displayed in
area 2. If you select a node again, the indicator information
is displayed in area 2 again.
NOTE
When you select the aggravation objects, the node information is
displayed only when you select IMEI-TAC.
l The KPI Evaluation node is used to select the KPIs to be
analyzed. The KPIs are also displayed in the area on the right.

2 Aggregation Displays the KPI value of the aggregation analysis performed

table of the on the terminals based on the selected dimension.
terminal l You can select a KPI in the Sequence Column drop-down
performance list, and the system sorts the table in area 2 again based on
indicators the selected KPI.
l You can select Descending or Ascending from the Order
drop-down list. Then, the system sorts the table in area 2
based on the selected KPI.
l You can set TOPN to specify the number of the TopN
objects that you want to analyze.
l You can right-click in the table in area 2 and choose Save
all as from the shortcut menu. The system then saves the
displayed TopN results and all the other results that are not
displayed to your local computer.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 467

No. Item Description

3 Aggregation Displays the performance indicator value of a certain type of

table of the cell- NEs in area 2 in each cell.
level terminal l You can select a KPI in the Sequence Column drop-down
performance list, and the system sorts the table in area 3 again based on
indicators the selected KPI.
l You can select Descending or Ascending from the Order
drop-down list. Then, the system sorts the table in area 3
based on the selected KPI.
l You can set TOPN to specify the number of the TopN
objects that you want to analyze.
l You can click displayalldata to display all analysis results
in area 3.
You can save the table by right-clicking the table and choosing
Save As from the shortcut menu.
l You can right-click in the table in area 3 and choose Save
all as from the shortcut menu. The system saves all displayed
analysis results to your local computer.
l You can right-click in the table in area 3 and choose Selected
Save As,The system saves selected analysis results to your
local computer.
For detailed parameters, see 3.6.5 Parameters for Viewing
GSM Terminal Analysis Results.

Terminal Analysis Results Displayed Through Geographic Observation

In the icon area for displaying terminal analysis results, click . The Geographic
Observation window is displayed, as shown in Figure 3-34.

Figure 3-34 Terminal analysis results displayed through geographic observation

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 468

N Item Description
o.

1 Icon area Provides icons for you to perform operations.

2 Navigati Contains the KPIs to be analyzed:

on tree l Site Layer: displays site information. You can set the display effect
through the shortcut menu. The site information is displayed on the
condition that the engineering parameters have been imported to the
Nastar database and site information have been loaded in map window.
NOTE
If you need to delete all sites in a network system, click Remove through the layer
management function.
l Polygon Areas; enables you to analyze only a selected polygon in the
map interface.
– When the following functions are supported, the maximum number
of grids within a polygon area is 1000. If the number of grids exceeds
the threshold, draw the polygon area again.
– You can save the cells in a polygon as a cell group. The cell group
definition function does not support the polygon drawn upon the
previous client login. After logging in to the client, draw the
polygon again.
– You can analyze multiple KPIs simultaneously based on a
polygon.
– When implementing the following functions, polygon area raster size
is limited to 100 000, if you need to configure the grid number over
100,000, please contact Huawei technical engineers to assess the
impact after the operation.
– The data in grids within a polygon area can be exported. You can
export data of multiple counters based on the area.
l Themes: enables you to select a set of KPIs to be analyzed. The Nastar
displays the analysis results of the selected KPI on overlapped grid maps.
However, only the analysis results of the last selected KPI are visible.
– You can use the Center Display function available in the shortcut
menu to quickly and accurately locate grids.
– You can use the display function available in the shortcut menu to
reset the grid display effect or the criteria for filtering the KPIs that
you want to view in grids.
The display setting functions of different indicators are not exactly
the same, all the functions are described as follows:
– Illustration tab page: enables you to set the grid legend.
NOTE
You can back up and restore the configured counter legends by using the
file sharing function. The counter legend information is saved in
\NastarClient\client\client\plugins\com.huawei.galaxy.geography.ui
\style\config\style.
– Select Counters tab page: allows you to select the KPIs that you
want to view on the map.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 469

N Item Description
o.

3 Geograp l Displays the analysis results of selected KPIs on grid maps using distinct
hic colors by default. However, only the analysis results of the last selected
observati KPI are visible.
on area
l Displays analysis results in multiple windows. If you click , the
Nastar divides the current window into multiple small windows with
each small window displaying the analysis results of one KPI. The small
windows are zoomed in, zoomed out, and moved simultaneously. If you
click the icon again, the Nastar displays the original window.

4 Raster This area is empty for terminal analysis.

details
area

5 Legend By default, the Nastar does not display this area. If you want to view the
area legend details about an analysis theme, click the icon in the button area.
The Nastar distinguishes between directional and omnidirectional cells
using different legends. You can change the legend for directional cells. The
legend for omnidirectional cells is set the Nastar by default, and therefore
you cannot change it.

6 Informati The interface displays no information when it is opened. If you select a grid,
on area the values of selected KPIs in this gird are displayed. If you select a site,
information about the site is displayed. If you select a cell, information about
the cell such as engineering parameters and longitude and latitude
coordinates is displayed.

3.6.5 Parameters for Viewing GSM Terminal Analysis Results

This section describes the parameters for querying GSM terminal analysis results. You can refer
to the description when querying GSM terminal inventory analysis results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 470

Basic Terminal Information

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Mo [ N Indicates the terminal model, for N/A

del 1 / example, iPhone4.
, A
2
5
6
]

IME E N Indicates the combination of the type N/A

I- i / approval code (TAC) and the final
TA g A assembly code (FAC) in an
C h International Mobile Equipment
t Identity (IMEI). An IMEI consists of
d 15 digits and uniquely identifies a
i terminal in the world. In an IMEI, the
g TAC refers to the first six digits, and
it the FAC refers to the seventh and
s eighth digits. The combination of
TAC and FAC uniquely identifies a
terminal.

Ven [ N Indicates the terminal vendor, for N/A

dor 1 / example, Nokia and Apple.
, A
2
5
6
]

Typ N N Indicates the terminal type, for N/A

e / / example, common terminal,
A A intelligent terminal, and data card.

Chi [ N Indicates the terminal chip model. N/A

p 0 /
Mo , A
del 2
5
6
]

Tec N N Indicates the RAT that the terminal N/A

hnol / / supports, for example, GSM and
ogy A A WCDMA.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 471

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Dat N N Indicates the data transfer mode that N/A

a / / the terminal uses, for example,
Tra A A HSDPA and HSUPA.
nsfe
r

Ter [ N Indicates the number of terminals of N/A

min 1 u this type within the statistical range.
als , m If the statistics are collected based on
+ b IMEI-TAC, this parameter indicates
∞ e the number of terminals with the
) r same IMEI-TAC and different
IMEIs.

Ter [ % Proportion of terminals of a specified N/A

min 0 type in all terminals.
al ,
Rati 1
o 0
0
]

Terminal Capability Analysis Summary

Par R U Description Supported NE Version
am a n
eter n i
g t
e

EG N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or

PRS / / numbers and percentages of BSC6910 V100R014C00 (or later)
A A terminals that support EGPRS, that
do not support EGPRS, and whose
capability is unknown under a cell,
BSC, or the entire network.

180 N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or
0 / / numbers and percentages of BSC6910 V100R014C00 (or later)
ban A A terminals that support GSM-1800,
d that do not support GSM-1800, and
whose capability is unknown under a
cell, BSC, or the entire network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 472

Par R U Description Supported NE Version

am a n
eter n i
g t
e

GS N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or

ME / / numbers and percentages of BSC6910 V100R014C00 (or later)
ban A A terminals that support E-GSM-900,
d that do not support E-GSM-900, and
whose capability is unknown under a
cell, BSC, or the entire network.

G/U N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or
dual / / numbers and percentages of BSC6910 V100R014C00 (or later)
mod A A terminals that support GSM/UMTS
es dual-mode, that do not support GSM/
UMTS dual-mode, and whose
capability is unknown under a cell,
BSC, or the entire network.

G/ N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or

TD / / numbers and percentages of BSC6910 V100R014C00 (or later)
dual A A terminals that support GSM/TD-
mod SCDMA dual-mode, that do not
es support GSM/TD-SCDMA dual-
mode, and whose capability is
unknown under a cell, BSC, or the
entire network.

FD N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or

D- / / numbers and percentages of BSC6910 V100R014C00 (or later)
LTE A A terminals that support FDD-LTE, that
do not support FDD-LTE, and whose
capability is unknown under a cell,
BSC, or the entire network.

TD N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or

D- / / numbers and percentages of BSC6910 V100R014C00 (or later)
LTE A A terminals that support TDD-LTE,
that do not support TDD-LTE, and
whose capability is unknown under a
cell, BSC, or the entire network.

DT N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or

M / / numbers and percentages of BSC6910 V100R014C00 (or later)
A A terminals that support DTM, that do
not support DTM, and whose
capability is unknown under a cell,
BSC, or the entire network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 473

Par R U Description Supported NE Version

am a n
eter n i
g t
e

8PS N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or
K / / numbers and percentages of BSC6910 V100R014C00 (or later)
mod A A terminals that support the 8PSK
ulati modulation mode, that do not support
on the 8PSK modulation mode, and
whose capability is unknown under a
cell, BSC, or the entire network.

Upli N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or
nk / / numbers and percentages of BSC6910 V100R014C00 (or later)
exp A A terminals that support uplink
ansi expansion, that do not support uplink
on expansion, and whose capability is
unknown under a cell, BSC, or the
entire network.

PS N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or

han / / numbers and percentages of BSC6910 V100R014C00 (or later)
dov A A terminals that support PS handovers,
er that do not support PS handovers, and
whose capability is unknown under a
cell, BSC, or the entire network.

U90 N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or
0 / / numbers and percentages of BSC6910 V100R014C00 (or later)
A A terminals that support U900, that do
not support U900, and whose
capability is unknown under a cell,
BSC, or the entire network.

VA N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or

MO / / numbers and percentages of BSC6910 V100R014C00 (or later)
S A A terminals that support VAMOS, that
do not support VAMOS, and whose
capability is unknown under a cell,
BSC, or the entire network.

Wi- N N Used to collect statistics about the BSC6900 V900R014C00 (or later) or
Fi / / numbers and percentages of BSC6910 V100R014C00 (or later)
A A terminals that support Wi-Fi, that do
not support Wi-Fi, and whose
capability is unknown under a cell,
BSC, or the entire network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 474

Performance Analysis Summary-Accessibility Evaluation

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Call [ N Indicates the number of originated BSC6900 V900R014C00 (or later) or

Setu 0 u call and terminated call setup BSC6910 V100R014C00 (or later)
p , m requests initiated by a terminal, that
Req + b is, the number of voice service call
uest ∞ e setup requests (Channel request
s ) r signaling) initiated by the terminal in
the case that IMEIs are correctly
identified.

Call [ N Indicates the number of abnormal BSC6900 V900R014C00 (or later) or

Setu 0 u originated call and terminated call BSC6910 V100R014C00 (or later)
p , m setups.
Exc + b If a terminal receives a Connect
epti ∞ e Acknowledge message or a
ons ) r Disconnect message and the call is
terminated by the peer terminal, the
call is set up successfully.
If a terminal receives a Clear
command message and the call is
properly released by the network,
local terminal, or peer terminal, the
call is set up successfully.
If an inter-BSC handover occurs
during the call setup process and the
call fails to be set up in the destination
BSC, the Nastar records that the call
is released abnormally.

Rati [ % Indicates the proportion of abnormal BSC6900 V900R014C00 (or later) or

o of 0 originated call and terminated call BSC6910 V100R014C00 (or later)
Call , setups.
Setu 1 Proportion of abnormal call setups =
p 0 Number of abnormal call setups/
Exc 0 Number of call setup requests x 100%
epti ]
ons

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 475

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Call [ N Indicates the number of originated BSC6900 V900R014C00 (or later) or

Rati [ % Indicates the proportion of abnormal BSC6900 V900R014C00 (or later) or

o of 0 call releases after the terminal uses BSC6910 V100R014C00 (or later)
Abn , the voice service to access the
orm 1 network.
al 0 Proportion of abnormal call releases
Call 0 = Number of abnormal call releases/
Rele ] Number of call release requests
ases
The number of call release requests
refers to the times the terminal sends
a Disconnect message.

Sho [ N Indicates the number of measurement BSC6900 V900R014C00 (or later) or

rt 0 u reports (MRs) on the originated calls BSC6910 V100R014C00 (or later)
Call , m with the duration that is less than the
s + b specified threshold. The call duration
(M ∞ e is from the time when the terminal
OC) ) r receives a Connect Acknowledge
message to the time when the
terminal sends a Disconnect message.
The Nastar does not analyze the
CHRs on calls involved in inter-BSC
handovers because the entire duration
of the calls cannot be obtained.

Rati [ % Indicates the proportion of MRs on BSC6900 V900R014C00 (or later) or

o of 0 the originated calls with the duration BSC6910 V100R014C00 (or later)
Sho , that is less than the specified
rt 1 threshold to all MRs.
Call 0 Proportion of originated short calls =
s 0 Number of originated short calls/
(M ] Number of MRs with valid originated
OC) call duration

Sho [ N Indicates the number of MRs on the BSC6900 V900R014C00 (or later) or
rt 0 u terminated calls with the duration that BSC6910 V100R014C00 (or later)
Call , m is less than the specified threshold.
s + b The call duration is from the time
(MT ∞ e when the terminal receives a Connect
C) ) r Acknowledge message to the time
when the terminal sends a Disconnect
message. The Nastar does not analyze
the CHRs on calls involved in inter-
BSC handovers because the entire
duration of the calls cannot be
obtained.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 479

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Rati [ % Indicates the proportion of MRs on BSC6900 V900R014C00 (or later) or

o of 0 the terminated calls with the duration BSC6910 V100R014C00 (or later)
Sho , that is less than the specified
rt 1 threshold to all MRs.
Call 0 Proportion of terminated short calls =
s 0 Number of terminated short calls/
(MT ] Number of MRs with valid
C) terminated call duration

Abn [ s Proportion of abnormal voice service BSC6900 V900R014C00 (or later) or

orm 0 releases = Total traffic/Number of BSC6910 V100R014C00 (or later)
al , abnormal voice service releases
Traf + The total traffic refers to the duration
fic ∞ from the time when the terminal
Rele ) receives a Connect Acknowledge to
ase the time when the terminal sends a
Rati Disconnect message.
o

Performance Analysis Summary-Handover Evaluation

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Intr [ N Indicates the number of intra-RAT BSC6900 V900R014C00 (or later) or

a- 0 u handover requests initiated by the BSC6910 V100R014C00 (or later)
Syst , m terminal.
em + b
Han ∞ e
dov ) r
er
Req
uest
s

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 480

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Intr [ N Indicates the number of abnormal BSC6900 V900R014C00 (or later) or

a- 0 u intra-RAT handovers. BSC6910 V100R014C00 (or later)
Syst , m
em + b
Abn ∞ e
orm ) r
al
Han
dov
ers

Rati [ % Indicates the proportion of abnormal BSC6900 V900R014C00 (or later) or

o of 0 intra-RAT handovers. BSC6910 V100R014C00 (or later)
Intr , Proportion of abnormal intra-RAT
a- 1 handovers = Number of abnormal
Syst 0 intra-RAT handovers/Number of
em 0 intra-RAT handover requests x 100%
Abn ]
orm
al
Han
dov
ers

Abn [ N Indicates the number of abnormal call BSC6900 V900R014C00 (or later) or
orm 0 u releases during the intra-RAT BSC6910 V100R014C00 (or later)
al , m handover.
Rele + b
ases ∞ e
Duri ) r
ng
Intr
a-
Syst
em
Han
dov
er

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 481

Performance Analysis Summary-System Handover Evaluation

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Inte [ N Indicates the number of terminal BSC6900 V900R014C00 (or later) or

r- 0 u requests for the handover from a cell BSC6910 V100R014C00 (or later)
RA , m on a GSM network to a cell on
T + b another network.
Out ∞ e
goin ) r
g
Han
dov
er
Req
uest
s

Abn [ N Indicates the number of abnormal BSC6900 V900R014C00 (or later) or

orm 0 u terminal handovers from a cell on a BSC6910 V100R014C00 (or later)
al , m GSM network to a cell on another
Inte + b network.
r- ∞ e
RA ) r
T
Out
goin
g
Han
dov
ers

Rati [ % Indicates the proportion of abnormal BSC6900 V900R014C00 (or later) or

o of 0 terminal handovers from a cell on a BSC6910 V100R014C00 (or later)
Abn , GSM network to a cell on another
orm 1 network.
al 0 Proportion of abnormal outgoing
Inte 0 inter-RAT handovers = Number of
r- ] abnormal outgoing inter-RAT
RA handovers/Number of outgoing inter-
T RAT handover requests x 100%
Out
goin
g
Han
dov
ers

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 482

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Abn [ N Indicates the number of abnormal call BSC6900 V900R014C00 (or later) or
orm 0 u releases during the handover of the BSC6910 V100R014C00 (or later)
al , m terminal from a cell on a GSM
Rele + b network to a cell on another network.
ases ∞ e
Duri ) r
ng
Inte
r-
RA
T
Out
goin
g
Han
dov
er

Inte [ N Indicates the number of terminal BSC6900 V900R014C00 (or later) or

r- 0 u requests for the handover from a cell BSC6910 V100R014C00 (or later)
RA , m on another network to a cell on a
T + b GSM network.
Inco ∞ e
min ) r
g
Han
dov
er
Req
uest
s

Abn [ N Indicates the number of abnormal BSC6900 V900R014C00 (or later) or

orm 0 u terminal handovers from a cell on BSC6910 V100R014C00 (or later)
al , m another network to a cell on a GSM
Inte + b network.
r- ∞ e
RA ) r
T
Inco
min
g
Han
dov
ers

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 483

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Rati [ % Indicates the proportion of abnormal BSC6900 V900R014C00 (or later) or

o of 0 terminal handovers from a cell on BSC6910 V100R014C00 (or later)
Abn , another network to a cell on a GSM
orm 1 network.
al 0 Proportion of abnormal incoming
Inte 0 inter-RAT handovers = Number of
r- ] abnormal incoming inter-RAT
RA handovers/Number of incoming
T inter-RAT handover requests x 100%
Inco
min
g
Han
dov
ers

Inte [ N Indicates the number of MRs with BSC6900 V900R014C00 (or later) or
r- 0 u valid incoming inter-RAT handover BSC6910 V100R014C00 (or later)
RA , m delays. The Nastar cannot collect
T + b statistics on the delays of failed
Inco ∞ e incoming inter-RAT handovers.
min ) r Incoming inter-RAT handover delay
g = Handover completion time -
Han Handover request time
dov
er
Del
ay
Rep
orts

Inte [ s Indicates the average delay for the BSC6900 V900R014C00 (or later) or
r- 0 handover from a cell on another BSC6910 V100R014C00 (or later)
RA , network to a cell on a GSM network.
T + Average delay for incoming inter-
Inco ∞ RAT handover = Delay of all
min ) successful incoming inter-RAT
g handovers/Number of MRs with
Han valid incoming inter-RAT handover
dov delays
er
Ave
rage
Del
ay

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 484

Performance Analysis Summary-Delay Evaluation

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Call [ N Indicates the number of MRs with BSC6900 V900R014C00 (or later) or
Setu 0 u valid interval between the time when BSC6910 V100R014C00 (or later)
p , m the terminal sends a Channel Request
Del + b message to originate a call and the
ay ∞ e time when the terminal receives an
Rep ) r Alerting message. The Nastar does
orts not collect statistics on the delay for
(M calls involved in inter-BSC
OC) handovers.

Call [ s Indicates the average interval BSC6900 V900R014C00 (or later) or

Setu 0 between the time when the terminal BSC6910 V100R014C00 (or later)
p , sends a Channel Request message to
Ave + originate a call and the time when the
rage ∞ terminal receives an Alerting
Del ) message.
ay
(M
OC)

Rati [ % Indicates the proportion of MRs in BSC6900 V900R014C00 (or later) or

o of 0 which the originated call setup delay BSC6910 V100R014C00 (or later)
Call , is greater than the specified threshold.
Setu 1 Proportion of long delay for
p 0 originated call setup = Number of
Ove 0 MRs in which the originated call
rlon ] setup delay is greater than the
g specified threshold/Number of MRs
Del with originated call setup delay x
ays 100%
(M
OC)

Call [ N Indicates the number of MRs with BSC6900 V900R014C00 (or later) or
Setu 0 u valid interval between the time when BSC6910 V100R014C00 (or later)
p , m the terminal sends a Channel Request
Del + b message to terminate a call and the
ay ∞ e time when the terminal receives an
Rep ) r Alerting message. The Nastar does
orts not collect statistics on the delay for
(MT calls involved in inter-BSC
C) handovers.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 485

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Call [ s Indicates the average interval BSC6900 V900R014C00 (or later) or

Setu 0 between the time when the terminal BSC6910 V100R014C00 (or later)
p , sends a Channel Request message to
Ave + terminate a call and the time when the
rage ∞ terminal receives an Alerting
Del ) message.
ay
(MT
C)

Rati [ % Indicates the proportion of MRs in BSC6900 V900R014C00 (or later) or

o of 0 which the terminated call setup delay BSC6910 V100R014C00 (or later)
Call , is greater than the specified threshold.
Setu 1 Proportion of long delay for
p 0 terminated call setup = Number of
Ove 0 MRs in which the terminated call
rlon ] setup delay is greater than the
g specified threshold/Number of MRs
Del with terminated call setup delay x
ays 100%
(MT
C)

Performance Analysis Summary-Quality Evaluation

Upli [ % Indicates the proportion of calls with no audio on both BSC6900

nk 0 the uplink and the downlink. V900R014C00 (or
and , Proportion of calls with no audio on both the uplink later) or BSC6910
Do 1 and the downlink = Number of calls with downlink V100R014C00 (or
wnli 0 one-way audio and uplink one-way audio/Total later)
nk 0 number of successful calls x 100%
No- ]
Aud
io
Rati
o

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 491

Performance Analysis Summary-Multi-Mode

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Voi [ N Indicates the number of MRs with BSC6900 V900R014C00 (or later) or
ce 0 u valid voice service duration. BSC6910 V100R014C00 (or later)
Serv , m The voice service duration is the TCH
ice + b occupation duration from the time
Dur ∞ e when the TCH is assigned to the time
atio ) r when the TCH is released.
n
Rep
orts

Voi [ s Indicates the average duration of the BSC6900 V900R014C00 (or later) or
ce 0 voice service. The voice service BSC6910 V100R014C00 (or later)
Serv , duration in the MR is from the time
ice + when the TCH is assigned to the time
Ave ∞ when the TCH is released.
rage ) Average voice service duration =
Dur TCH occupation duration/Number of
atio MRs with voice service duration
n

Utra [ N Indicates the number of MRs with BSC6900 V900R014C00 (or later) or
nFD 0 u valid voice service duration of BSC6910 V100R014C00 (or later)
D- , m terminals that support UTRAN FDD.
Sup + b The voice service duration is the TCH
port ∞ e occupation duration from the time
ed ) r when the TCH is assigned to the time
Ter when the TCH is released.
min
al
Voi
ce
Serv
ice
Dur
atio
n
Rep
orts

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 492

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Utra [ s Indicates the average voice service BSC6900 V900R014C00 (or later) or
nFD 0 duration for terminals that support BSC6910 V100R014C00 (or later)
D- , UTRAN FDD. The voice service
Sup + duration in the MR is from the time
port ∞ when the TCH is assigned to the time
ed ) when the TCH is released.
Ter Average voice service duration =
min TCH occupation duration/Number of
al MRs with voice service duration
Voi
ce
Serv
ice
Ave
rage
Dur
atio
n

Utra [ N Indicates the number of MRs with BSC6900 V900R014C00 (or later) or
nTD 0 u valid voice service duration of BSC6910 V100R014C00 (or later)
D- , m terminals that support UTRAN TDD.
Sup + b The voice service duration is the TCH
port ∞ e occupation duration from the time
ed ) r when the TCH is assigned to the time
Ter when the TCH is released.
min
al
Voi
ce
Serv
ice
Dur
atio
n
Rep
orts

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 493

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Utra [ s Indicates the average voice service BSC6900 V900R014C00 (or later) or
nTD 0 duration for terminals that support BSC6910 V100R014C00 (or later)
D- , UTRAN TDD. The voice service
Sup + duration in the MR is from the time
port ∞ when the TCH is assigned to the time
ed ) when the TCH is released.
Ter Average voice service duration =
min TCH occupation duration/Number of
al MRs with voice service duration
Voi
ce
Serv
ice
Ave
rage
Dur
atio
n

Cell Information Overview

Par Range U Description Supported NE Version
am n
eter i
t

Ro [1,50000) N Indicates the number of a row in BSC6900 V900R014C00 (or

w / the summary table. later) or BSC6910
No A V100R014C00 (or later)

BS 1 to 64 N Indicates the name of the BSC BSC6900 V900R014C00 (or

C character / where the terminal is located. later) or BSC6910
Na s A V100R014C00 (or later)
me

Cell [0,7999] N Indicates the ID of the cell where BSC6900 V900R014C00 (or
ID / the terminal is located. later) or BSC6910
A V100R014C00 (or later)

Cell 1 to 64 N Indicates the name of the cell BSC6900 V900R014C00 (or

Na character / where the terminal is located. later) or BSC6910
me s A V100R014C00 (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 494

Par Range U Description Supported NE Version

am n
eter i
t

CGI MCC- N Indicates the global identity of BSC6900 V900R014C00 (or

MNC- / the cell where the terminal is later) or BSC6910
LAC-CI A located. V100R014C00 (or later)
MCC
[000,999]
MNC
[00,99]
LAC
[0,65535]
CI
[0,65535]

Ter [0,+∞) N Indicates the number of terminals BSC6900 V900R014C00 (or

min / of a specified type in each cell. later) or BSC6910
als A V100R014C00 (or later)

NOTE

For details about other parameters, see Performance Analysis Summary-Accessibility Evaluation,
Performance Analysis Summary- Retainability, Performance Analysis Summary-Handover
Evaluation, Performance Analysis Summary-System Handover Evaluation, Performance Analysis
Summary-Delay Evaluation, Performance Analysis Summary-Quality Evaluation and Performance
Analysis Summary-Multi-Mode.

Terminal Geographic Display-Traffic Analysis

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Tota [ K The grid map is rendered according BSC6900 V900R014C00 (or later) or
l 0 B to the total traffic of terminals in the BSC6910 V100R014C00 (or later)
Traf , grids.
fic +
∞
)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 495

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Upli [ K The grid map is rendered according BSC6900 V900R014C00 (or later) or
nk 0 B to the uplink traffic of terminals in the BSC6910 V100R014C00 (or later)
Traf , grids.
fic +
∞
)

Do [ K The grid map is rendered according BSC6900 V900R014C00 (or later) or

wnli 0 B to the downlink traffic of terminals in BSC6910 V100R014C00 (or later)
nk , the grids.
Traf +
fic ∞
)

Terminal Geographic Display-Capability Analysis

Par R U Description Supported NE Version
am a n
eter n i
g t
e

EG N N The grid map is rendered according BSC6900 V900R014C00 (or later) or

PRS / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
A A support the EGPRS frequency band
in the total number of terminals in the
grids.

180 N N The grid map is rendered according BSC6900 V900R014C00 (or later) or
0 / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
ban A A support the GSM 1800 frequency
d band in the total number of terminals
in the grids.

GS N N The grid map is rendered according BSC6900 V900R014C00 (or later) or

ME / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
ban A A support the E-GSM frequency band
d in the total number of terminals in the
grids.

FD N N The grid map is rendered according BSC6900 V900R014C00 (or later) or

D- / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
LTE A A support FDD-LTE in the total
number of terminals in the grids.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 496

Par R U Description Supported NE Version

am a n
eter n i
g t
e

TD N N The grid map is rendered according BSC6900 V900R014C00 (or later) or

D- / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
LTE A A support TDD-LTE in the total
number of terminals in the grids.

DT N N The grid map is rendered according BSC6900 V900R014C00 (or later) or

M / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
A A support DTM in the total number of
terminals in the grids.

8PS N N The grid map is rendered according BSC6900 V900R014C00 (or later) or
K / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
mod A A support 8PSK modulation in the total
ulati number of terminals in the grids.
on

Upli N N The grid map is rendered according BSC6900 V900R014C00 (or later) or
nk / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
exp A A support uplink expansion in the total
ansi number of terminals in the grids.
on

PS N N The grid map is rendered according BSC6900 V900R014C00 (or later) or

han / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
dov A A support PS handover in the total
er number of terminals in the grids.

Wi- N N The grid map is rendered according BSC6900 V900R014C00 (or later) or
Fi / / to the percentage of terminals that BSC6910 V100R014C00 (or later)
A A support Wi-Fi in the total number of
terminals in the grids.

3.7 GSM Cell Performance Analysis

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 497

3.7.1 Basics of GSM Cell Performance Analysis

This section describes the functions, technical specifications, and feature limitations of GSM
cell performance analysis. Read this section before performing a GSM cell performance analysis.

Functions of GSM Cell Performance Analysis

This section describes the functions of GSM cell performance analysis. These functions help
engineers quickly identify problematic cells and obtain the data about the abnormal calls in the
problematic cells. In this way, the engineers can better analyze the causes of cell exceptions and
then locate these cell exceptions.

Function Description
Generally, engineers prefer a whole-to-partial method to optimize the network and analyze the
network performance. With this method, engineers can analyze and detect network problems by
evaluating performance indicators,and then analyze the KPIs of the entire network or a specific
BSC. If the analysis results indicate that a BSC is faulty, the engineers analyze the cells under
the faulty BSC to find which cells are problematic and then further analyze these problematic
bottom cells. During the preceding process of cell performance analysis, the Nastar provides the
following functions:
l The Nastar analyzes the abnormal call records and the causes of exceptions in the bottom
cells based on BSCs or NE groups. This helps engineers better identify the detailed causes
of certain exceptions and solve the problems accordingly.
l After identifying the key exceptions in the problematic cells, the Nastar analyzes the bottom
subscribers and bottom terminals with exceptions in the problematic cells. This helps
engineers collect more information about the bottom subscribers and terminal models that
indicate low KPI values. In this way, the function helps engineers quickly identify certain
types of bottom subscriber and bottom terminal with exceptions in the problematic cells,
thereby enabling the engineers to improve cell performance by eliminating the exceptions
that occur on the bottom subscribers and bottom terminals.
l When problematic cells are not identified, the Nastar analyzes the exceptions in a large
number of problematic bottom cells under a specific BSC to help engineers identify the
bottom cells with the most exceptions.
l Besides identifying the problematic cells and the causes of certain exceptions, the Nastar
focuses on the further analyses of problematic cells. The Nastar performs further analyses
on abnormal call records based on different analysis needs and scopes. The further analyses
cover selected causes of certain types of exception, and bottom cells, bottom subscribers
or bottom terminals under the causes of certain exceptions. After the further analysis
function is enabled, the Nastar leads engineers to the complaint analysis results, helping
them obtain the information about subscribers' calls and locate problems.

Engineers can export the results of cell performance analysis as .csv, .xls, or .xlsx files, and then
solve the problems in the cells based on the exported results to optimize cell performance.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 498

NOTE

Under the Nastar, the statistical results of cell performance analysis are different from those of cell
performance data.
l The statistical results provided by the Nastar are based on subscriber perception. The traffic
measurement results, however, are based on the performance data about network devices. The two
types of result are collected by different dimensions, and therefore indicate certain differences.
l The Nastar focuses on the further analyses of problematic cells. The U2000/M2000 and the PRS,
however, focus on the identification of problematic cells by collecting statistics from the network
dimension.

Function Principles
The Nastar uses the CHR data from NEs for cell performance analysis.

Figure 3-35 shows the principles for collecting, importing, and analyzing data on the Nastar.
For detailed operations, see Table 3-21.

Figure 3-35 Principles for analysis

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 499

Table 3-21 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Issue an eS U20 To issue an MML command to the U2000/M2000.

MML AU 00/
comma M20
nd 00

Forward U2 BSC/ To forward the MML command to the NE through the

the 000 RNC U2000/M2000, requesting the NE to generate raw data.
MML /
comma M2
nd 000

Upload BS SAU To upload the raw data to the SAU.

raw data C/
RN
C

2. Issue an Nas eSA To deliver a data-preprocessing request to the eSAU.

Deliver eS SAU To deliver a data-preprocessing request to the SAU,

a data- AU requesting the SAU to start the data-preprocessing task.
preproc
essing
task
(direct)

Upload SA eSA To upload preprocessed data to the eSAU.

preproc U U
essed
data
(direct)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 500

User Proced So Dest Purpose

Operat ure urc inati
ion e on

4. Issue a Nas eSA To deliver a task execution request to the eSAU. After a
Create task tar U user creates an analysis task on the Nastar client, the
and executio Ser Nastar server issues a task execution command to the
execute n ver eSAU, requesting the eSAU to aggregate data.
an comma
analysi nd
s task
Upload eS Nast To aggregate the data reported by SAUs, generate data
data AU ar analysis results, and upload the data analysis results to
analysis Serv the Nastar server.
results er

5. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

Technical Specifications for GSM Cell Performance Analysis

This section describes the technical specifications for GSM cell performance analysis, including
the analysis capability and the analysis time range.

Item Service Specifications

Execution type One-time task

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 501

Item Service Specifications

Network scale for one analysis <= 2048 cells

task

Number of allowed analysis tasks <= 50

Time range for data in one 7 days

analysis task

Duration of one analysis task <= 100 minutes

Default duration for storing 7 days

analysis data

Maximum duration for storing 15 days

analysis data

3.7.2 Preparations for GSM Cell Performance Analysis

Before starting a GSM cell performance analysis task, you must check the user rights and version
mapping and prepare relevant data. Read this section before performing a GSM cell performance
analysis.

Checking the License and User Rights

l You have applied for a valid license for GSM cell performance analysis.
l The login user is authorized to subscribe to the source data for GSM cell performance
analysis.
The source data subscription function has high security requirements. You are advised to
contact the administrator to turn on the data source switch.
l The login user is authorized to execute GSM cell performance analysis tasks and analyze
related NEs.

Preparing Basic Data

Configuration Data

This is the configuration data of the NEs related to a cell. The configuration data enables users
to correctly obtain the CHR data of subscribers from the network. It also enables users to analyze
the cell information in MRs and the information about the following cells: cells to which
subscribers have gained access, cells from which subscribers have been released, and cells to
which subscribers will be handed over.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 502

NOTE
To ensure the validity of the configuration data, you are advised to perform GSM cell performance analyses
on a per day basis.

Checking Version Mapping

3.7.3 Process of GSM Cell Performance Analysis

This section describes the process of GSM cell performance analysis.

This section includes the following information:

l Prerequisites
l Process
l Subscription Task Parameters
l Analysis Task Parameters

Prerequisites
GSM configuration data and GSM engineering parameters have been imported into the Nastar
database. For detailed operations, see 3.7.2 Preparations for GSM Cell Performance
Analysis.

Process
Figure 3-36 shows the analysis process.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 503

Figure 3-36 Analysis process

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 504

Table 3-22 Description of the GSM cell performance analysis process

(3) Create Navigation path: Choose Theme Function > Network l For
an Analysis > GSM Cell Performance Analysis in the detailed
analysi navigation tree of the Analysis Task Management operations
s task window. , see 2.8
Steps: Creating
an
1. Double-click GSM Cell Performance Analysis. Analysis
2. Set the task name and remarks. Then, click Next. Task
3. On the Select NE(s) tab page, select the NEs to be l For
analyzed and click Next. detailed
4. Specify the time period. After the task is executed, the descriptio
Nastar obtains the analysis results for the specified time n of the
period. parameter
s, see
5. Click Finish.
Analysis
Task
Paramete
rs.

(4) View Navigation path: In the upper right area of the Analysis l For
analysi Task Management window, select an analysis task in the detailed
s Finished state. In the lower right of the Task Result area, operations
results select a result record of the task. , see 2.9
Steps: Querying
Analysis
1. Right-click the result record and choose View Analysis Results
Result from the shortcut menu.
l For
2. In the displayed GSM Cell Performance Analysis detailed
window, view the analysis results matching the record. descriptio
View Navigation path: In the window for showing analysis n of the
in- window
results, click the icon, or right-click a cell in the for
depth
navigation tree and choose In-depth analysis from the showing
analysi
shortcut menu. analysis
s
results Steps: results,
see 3.7.4
1. In the window for showing analysis results, click the
Interface
icon, or right-click a cell in the navigation tree and Descripti
choose In-depth analysis from the shortcut menu. on: GSM
2. View the analysis results in the displayed Further Cell
Analysis window. Performa
nce
NOTE
When you perform in-depth analysis on an existing cell Analysis.
performance analysis task after NE names are changed, NE
names on GUIs before the in-depth analysis is remain
unchanged, whereas NE names on GUIs after the in-depth
analysis will be updated.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 507

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 510

Slow Downl Slow download speed indicating a slow download speed: Download
Dow oad Speed (Kbit/s) = Number of bytes transmitted by using downlink
nload Speed PDU/Duration for data transmission by using downlink PDU.
Spee
d Trans Slow download speed indicating a slow download speed, judge
missio whether the download problem is caused by the transmission
n resource.
Resour
ce
Satisfa
ction
Rate of
Downli
nk
Averag
e
Single-
Slot
Throug
hput

Um Slow download speed indicating a slow download speed, judge

Quality whether the download problem is caused by the Um interface.
Non-
Satisfa
ction of
Downli
nk
Averag
e
Single-
Slot
Throug
hput

Slow Upload Slow upload speed indicating a slow upload speed: Upload Speed
Uplo Speed (Kbit/s) = Number of bytes transmitted by using uplink PDU/
ad Duration for data transmission by using uplink PDU.
Spee
d

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 513

Parameter Description

Trans Slow upload speed indicating a slow upload speed, judge whether
missio the upload problem is caused by the transmission resource.
n
Resour
ce
Satisfa
ction
Rate of
Uplink
Averag
e
Single-
Slot
Throug
hput

Analysis Task Parameters

On the aggregated analysis result interface, click , or right-click an NE and choose

Further Analysis from the shortcut menu.

Interface
The aggregated cell performance analysis results are displayed in tables, including the table of
exception types, table of exception causes, and table of bottom N subscribers, terminals, or cells.
Figure 3-37 shows the analysis result interface.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 515

Figure 3-37 Interface for cell performance analysis results

No. Name Description

1 Button area
Click to export analysis reports of all cells under each exception
cause.

2 NE l Upper part: Type a cell name in the Search area to quickly locate
navigation a cell.
tree l Lower part: Display all NEs involved in this task in a navigation
tree. The right pane is displayed after you choose an NE from the
navigation tree. (N) after each node indicates the number of times
related to the exception causes.

3 Table of Displays the number of reports and ratio under each exception type
exception for the selected BSC or cell under each service type. This area is
types displayed accordingly with Area 4.
Click the column header to resort this table. Right-click on the
table and choose Save As from the shortcut menu to export this table.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 516

No. Name Description

4 Table of Displays the number of reports and ratio under each exception cause
exception of an exception type for the selected BSC or cell. This area is
causes displayed accordingly with Area 5.
l The first row displays the total number of reports under all
exception causes, which is also the number of reports under the
selected exception type. Starting from the second row, each row
displays the number and ratio of reports under each exception
cause.

l Select an exception cause and click the icon to open the in-
depth analysis interface where you can view all abnormal call
records caused by this exception cause.

5 Table of Displays the number of reports related to bottom N users(N<=50),

bottom N terminal models(N<=50), or cells(N<=50) under an exception cause
users, for the selected BSC or cell.
terminal l After you select a BSC in Area 2, this table displays the number
models, or and ratio of reports caused by bottom N subscribers, terminals,
cells and cells.
l After you select a cell in Area 2, this table displays the number
and ratio of reports caused by bottom N subscribers and terminals.

l Select a subscriber, a terminal, or a cell and click the icon to

open the in-depth analysis interface where you can view all
abnormal call records under this subscriber, terminal, or cell.

NOTE

Click the icon to open the in-depth analysis interface where you can analyze abnormal call records
based on problematic cells. For details about the interfaces, see Interface Description: GSM Complaint
Analysis Support. The deep analysis results do not support the all signalling analysis of users.
If the cell coverage analysis covers an exceedingly large scale of the network, the in-depth analysis takes
a long period of time, during which you are not allowed to perform any other operations. You can estimate
the left time required based on the displayed in-depth analysis progress. If the left time required is
exceedingly long and most of the required results have been obtained, you can click Abort to stop the in-
depth analysis. All in-depth analysis results generated before the in-depth analysis is stopped will be
properly displayed.

3.7.5 Parameters for Viewing GSM Cell Performance Analysis

Results
This section describes the parameters for GSM cell performance analysis results. You can refer
to the description when viewing GSM cell performance analysis results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 517

Summary of Exception Types

Par Ra Un Description Supported NE Version
am nge it
ete
r

Ser Voi N/ Service type of a cell exception. BSC6900 V900R014C00 (or later)
vice ce A or BSC6910 V100R014C00 (or
Typ Ser later)
e vice
Sho
rt
Me
ssa
ge
Dat
a
Ser
vice

Exc N/ N/ Classified analysis of exceptions BSC6900 V900R014C00 (or later)

epti A A under a specific exception type. or BSC6910 V100R014C00 (or
on For detailed description of the later)
Typ exception types, see the following.
e

Exc [0, Nu Number of abnormal times under a BSC6900 V900R014C00 (or later)
epti +∞ mb specific exception type. or BSC6910 V100R014C00 (or
on ) er later)
Occ
urre
nce
Tim
es

Rati [0.0 % Proportion of the abnormal times BSC6900 V900R014C00 (or later)
o 0,1 under a specific exception type in or BSC6910 V100R014C00 (or
(%) 00. all the abnormal call records. later)
00]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 518

Description of Exception Types-Voice Service

Par Ra Un Description Supported NE
am nge it Version
ete
r

Call N/ N/ Failed call setup due to certain exceptions BSC6900

Set A A when a terminal receives a Disconnect V900R014C00 (or later)
up message after sending a Channel Request or BSC6910
Fail message. V100R014C00 (or later)
ure

Ab N/ N/ After sending a Channel Request message, a BSC6900

nor A A terminal receives an Alerting message, but V900R014C00 (or later)
mal fails to receive a Connect Acknowledge or BSC6910
Rel message due to certain exceptions. V100R014C00 (or later)
eas
e
Bef
ore
Call
Co
mpl
etio
n

Ab N/ N/ Abnormal call release after a terminal gains BSC6900

nor A A access to the network. V900R014C00 (or later)
mal After a successful call setup, any of the or BSC6910
Call following indicates an abnormal call release: V100R014C00 (or later)
Rel
eas 1. The terminal receives a Disconnect
e message that carries an abnormal cause
(indicating that this is a non-Normal
message).
2. The BSC receives a Clear command
message from the MSC due to an
abnormal call release triggered by the
network or the terminal (or the peer-end
terminal).
3. Call drops occur due to inter-BSC
handovers.
4. Call drops occur due to intra-BSC
handovers.
5. The BSC releases channel resources
abnormally.
6. The MSC releases channel resources
abnormally.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 519

Par Ra Un Description Supported NE

am nge it Version
ete
r

Ser N/ N/ Any of the following exceptions that might BSC6900

vice A A occur after a terminal gains access to the V900R014C00 (or later)
Qua network and successfully sends a Setup or BSC6910
lity message: V100R014C00 (or later)
Pro Poor Um-interface quality
ble
m Uplink one-way audio
Downlink one-way audio
No audio
Uplink crosstalk
Downlink crosstalk
You can set the exception threshold for poor
Um-interface quality by using the source data
subscription function.

Del N/ N/ Any of the following delay problems that BSC6900

ay A A might occur after a terminal gains access to V900R014C00 (or later)
Pro the network: or BSC6910
ble Long call access delay (mobile-originated) V100R014C00 (or later)
m
Long call access delay (mobile-terminated)
Long call completion delay (alerting)
(mobile-originated)
Long call completion delay (alerting)
(mobile-terminated)
You can set the exception thresholds by using
the source data subscription function.

Sho N/ N/ Short call that occurs when a terminal BSC6900

rt A A attempts to access the network and initiate a V900R014C00 (or later)
Call call. or BSC6910
Pro A short call occurs when a subscriber's actual V100R014C00 (or later)
ble call duration is below a specified short-call
m threshold (Call duration = Timestamp of the
Disconnect message – Timestamp of the
Connect Acknowledge message).
You can set the short-call threshold by using
the source data subscription function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 520

Par Ra Un Description Supported NE

am nge it Version
ete
r

Acc N/ N/ Number of abnormal TA values and RACH BSC6900

ess A A levels when a terminal attempts to access the V900R014C00 (or later)
Cov network. or BSC6910
era You can set the exception threshold by using V100R014C00 (or later)
ge the source data subscription function.
Pro
ble
m

Inc N/ N/ Number of failed incoming hard handovers BSC6900

omi A A when a subscriber is using a specific service. V900R014C00 (or later)
ng Statistics on incoming hard handovers are or BSC6910
Har collected based on the target cell. V100R014C00 (or later)
d
Han
dov
er
Fail
ure

Out N/ N/ Number of failed outgoing hard handovers BSC6900

goi A A when a subscriber is using a specific service. V900R014C00 (or later)
ng Statistics on outgoing hard handovers are or BSC6910
Har collected based on the source cell. V100R014C00 (or later)
d
Han
dov
er
Fail
ure

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 521

Par Ra Un Description Supported NE

am nge it Version
ete
r

Inte N/ N/ Number of failed outgoing inter-RAT BSC6900

r- A A handovers from the current GSM network V900R014C00 (or later)
Sys (and the failures occur on the GSM network) or BSC6910
tem when a subscriber is using a specific service. V100R014C00 (or later)
Out
goi
ng
Han
dov
er
Fail
ure
(Int
ra-
Sys
tem
)

Inte N/ N/ Number of failed call setups after a BSC6900

r- A A subscriber is handed over from a non-GSM V900R014C00 (or later)
Sys network to a GSM network. or BSC6910
tem V100R014C00 (or later)
Inc
omi
ng
Han
dov
er
Fail
ure
(Int
ra-
Sys
tem
)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 522

Description of Exception Types-SMS

Par Ra Un Description Supported NE Version
am nge it
ete
r

SM N/ N/ Number of times that a mobile- BSC6900 V900R014C00 (or later)

S A A originated subscriber attempts to or BSC6910 V100R014C00 (or
Req access the network to use SMS later)
uest service fails.
Fail
ure
(M
OC
)

SM N/ N/ Number of times that a mobile- BSC6900 V900R014C00 (or later)

S A A terminated subscriber attempts to or BSC6910 V100R014C00 (or
Req access the network to use SMS later)
uest service fails.
Fail
ure
(M
TC)

Description of Exception Types-Data Service

Par Ra Un Description Supported NE Version
am nge it
ete
r

Acc N/ N/ Number of access fails when a BSC6900 V900R014C00 (or later)

ess A A subscriber is using a data service. or BSC6910 V100R014C00 (or
Fail Any of the following indicates a later)
ure access fail:
No Service Interaction Response
Attach Failure
PDP Active Failure
AUC Failure

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 523

Par Ra Un Description Supported NE Version

am nge it
ete
r

Ser N/ N/ Number of service interruptions BSC6900 V900R014C00 (or later)

vice A A when a subscriber is using a data or BSC6910 V100R014C00 (or
Inte service. later)
rrup Any of the following indicates a
tion service interruption:
Last Service Interrupted Due to
Routing Area Update
Abnormal Interruption on Cell
Reselection
Service Interruptions Due to
FLUSH LL
Service Interruptions Due to TBF
Abnormal

Ab N/ N/ Any of the following service- BSC6900 V900R014C00 (or later)

nor A A interaction delay problems that or BSC6910 V100R014C00 (or
mal might occur when a subscriber is later)
Ser using a data service.
vice Service interaction response times
Inte out.
ract
ion The average duration for making a
Del service interaction response is
ay long.
You can set the exception
thresholds by using the source data
subscription function.

Lo N/ N/ Any of the following download BSC6900 V900R014C00 (or later)

w A A rate problems that might occur or BSC6910 V100R014C00 (or
Do when a subscriber is using a data later)
wnl service:
oad Low download rate
Spe
ed You can set the exception
thresholds by using the source data
subscription function.

Lo N/ N/ Any of the following Upload rate BSC6900 V900R014C00 (or later)

w A A problems that might occur when a or BSC6910 V100R014C00 (or
Upl subscriber is using a data service: later)
oad Low upload rate
Spe
ed You can set the exception
thresholds by using the source data
subscription function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 524

Par Ra Un Description Supported NE Version

am nge it
ete
r

TB N/ N/ Displayed when any of the BSC6900 V900R014C00 (or later)

F A A following conditions is met: or BSC6910 V100R014C00 (or
Ab Condition 1: The number of times later)
nor that the downlink TBF
mal establishment fails is greater than
0.
Condition 2: The number of times
that the downlink TBF is
abnormally released is greater than
0.
Condition 3: The number of times
that the uplink TBF establishment
fails is greater than 0.
Condition 4: The number of times
that the uplink TBF is abnormally
released is greater than 0.

Data About Exception Causes

Par Ra Un Description Supported NE Version
am nge it
ete
r

Han N/ N/ Provides detailed algorithms that BSC6900 V900R014C00 (or later)

dov A A trigger handovers upon outgoing or BSC6910 V100R014C00 (or
er hard handover and outgoing inter- later)
Tri RAT handover (within the system)
gge failures. The handover trigger
r algorithm is displayed only when
Alg exceptions occur on location group
orit handovers.
hm

Exc N/ N/ Cause of exceptions under a BSC6900 V900R014C00 (or later)

epti A A specific exception type. or BSC6910 V100R014C00 (or
ona later)
l
Cau
se

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 525

Par Ra Un Description Supported NE Version

am nge it
ete
r

Exc [0, Nu Number of times that a specific BSC6900 V900R014C00 (or later)
epti +∞ mb cause of certain exceptions is or BSC6910 V100R014C00 (or
on ) er reported. later)
Occ
urre
nce
Tim
es

Rati [0.0 % Proportion of a cause against the BSC6900 V900R014C00 (or later)
o 0,1 number of exceptions under the or BSC6910 V100R014C00 (or
(%) 00. same exception type. later)
00]

Description of Exception Causes

Par Ra Un Description Supported NE Version
am nge it
ete
r

Um N/ N/ Exceptions caused by poor Um- BSC6900 V900R014C00 (or later)

Inte A A interface quality or terminal fault. or BSC6910 V100R014C00 (or
rfac later)
e
Qua
lity
Pro
ble
m/
MS
Fau
lt

Sys N/ N/ Exceptions caused by system BSC6900 V900R014C00 (or later)

tem A A resource congestion. or BSC6910 V100R014C00 (or
Res later)
our
ce
Con
gest
ion

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 526

Par Ra Un Description Supported NE Version

am nge it
ete
r

Tra N/ N/ Exceptions caused by transmission BSC6900 V900R014C00 (or later)

nsm A A fault. or BSC6910 V100R014C00 (or
issi later)
on
Fau
lt

CN N/ N/ Exceptions caused by CN fault. BSC6900 V900R014C00 (or later)

Fau A A or BSC6910 V100R014C00 (or
lt later)

Oth N/ N/ Exceptions caused by other faults BSC6900 V900R014C00 (or later)

er A A except poor Um-interface quality, or BSC6910 V100R014C00 (or
Cau terminal fault, system resource later)
ses congestion, transmission fault, and
CN fault.

Call N/ N/ Call drops caused by failed BSC6900 V900R014C00 (or later)

Dro A A handovers after a terminal gains or BSC6910 V100R014C00 (or
p access to the network and sends a later)
Due Setup message.
to
HO
Fail
ure

Call N/ N/ Call drops caused by poor Um- BSC6900 V900R014C00 (or later)
Dro A A interface quality after a terminal or BSC6910 V100R014C00 (or
p gains access to the network and later)
Due sends a Setup message.
to
Um
Inte
rfac
e
Pro
ble
ms

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 527

Par Ra Un Description Supported NE Version

am nge it
ete
r

Call N/ N/ Call drops caused by transmission BSC6900 V900R014C00 (or later)

Dro A A faults after a terminal gains access or BSC6910 V100R014C00 (or
p to the network and sends a Setup later)
Due message.
to
Tra
nsm
issi
on
Fau
lt

Call N/ N/ Call drops caused by CN faults BSC6900 V900R014C00 (or later)

Dro A A after a terminal gains access to the or BSC6910 V100R014C00 (or
p network and sends a Setup later)
Due message.
to
CN
Fau
lt

Pee N/ N/ Call drops caused by call drops of BSC6900 V900R014C00 (or later)
r A A the peer-end terminal after a or BSC6910 V100R014C00 (or
Call terminal gains access to the later)
Dro network and sends a Setup
p message.

Call N/ N/ Call drops caused by other faults BSC6900 V900R014C00 (or later)
Dro A A except failed handover, poor Um- or BSC6910 V100R014C00 (or
p interface quality, transmission later)
Due fault, CN fault, and peer-end
to terminal fault after a terminal gains
Oth access to the network and sends a
er Setup message.
Cau
ses

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 528

Par Ra Un Description Supported NE Version

am nge it
ete
r

Poo N/ N/ Poor Um-interface quality caused BSC6900 V900R014C00 (or later)

r A A by the following KPIs after the or BSC6910 V100R014C00 (or
Qua subscriber gains access to the later)
lity network and sends a Set Up
of message (Call Setup Success).
Um Uplink VQI
Inte
rfac Uplink HQI
e Downlink HQI
You can set the exception
thresholds for the KPIs by using the
source data subscription function.
For description of the KPIs, refer to
the description of source data
subscription.

UL N/ N/ Uplink one-way audio event that BSC6900 V900R014C00 (or later)

One A A occurs after a terminal gains access or BSC6910 V100R014C00 (or
- to the network and sends a Setup later)
Wa message.
y The one-way audio test can only
Au detect one-way audio events
dio related to the channels within the
BSS (BTS<->TC) instead of those
related on the Um and A interfaces.
Principles for detecting uplink one-
way audio are as follows: The DSP
in the TC of the BSC performs
periodic statistics on the bad frame
rate based on uplink TRAU frames.
When the bad frame rate reaches a
specified threshold, the BSS
determines that a primary uplink
one-way audio event occurs, and
starts the mechanism for further
confirming the occurrence of
uplink one-way audio. During this
process, the BSC sends a message
to the BTS demanding that the BTS
send a test TRAU frame to the TC.
If the TC fails to receive a test
TRAU frame from the BTS within
a specified time period, one-way
audio occurs on the uplink voice
channel.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 529

Par Ra Un Description Supported NE Version

am nge it
ete
r

DL N/ N/ Downlink one-way audio event BSC6900 V900R014C00 (or later)

One A A that occurs after a terminal gains or BSC6910 V100R014C00 (or
- access to the network and sends a later)
Wa Setup message.
y The one-way audio test can only
Au detect one-way audio events
dio related to the channels within the
BSS (BTS<->TC) instead of those
related on the Um and A interfaces.
Principles for detecting downlink
one-way audio are as follows: The
DSP in the DTRU of the BTS
performs periodic statistics on the
bad frame rate based on downlink
TRAU frames. When the bad frame
rate reaches a specified threshold,
the BSS determines that a primary
downlink one-way audio event
occurs, and starts the mechanism
for further confirming the
occurrence of downlink one-way
audio. During this process, the
BSC sends a message to the TC
demanding that the TC send a test
TRAU frame to the BTS. If the
BTS fails to receive a test TRAU
frame from the TC within a
specified time period, one-way
audio occurs on the downlink voice
channel.

Mut N/ N/ No-audio event that occurs after a BSC6900 V900R014C00 (or later)
e A A terminal gains access to the or BSC6910 V100R014C00 (or
Call network and sends a Setup later)
message.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 530

Par Ra Un Description Supported NE Version

am nge it
ete
r

UL N/ N/ Uplink crosstalk event that occurs BSC6900 V900R014C00 (or later)

Cro A A after a terminal gains access to the or BSC6910 V100R014C00 (or
ssta network and sends a Setup later)
lk message.
The crosstalk test can only detect
crosstalk events related to the
channels within the BSS (BTS<-
>TC) instead of those related on the
Um and A interfaces.
Principles for detecting uplink
crosstalk are as follows: The DSP
of the BTS inserts the unique
identifier of a call into the free bit
of each TRAU frame on the uplink
voice channel. The DSP of the TC
decodes all the unique call
identifiers and checks their
consistency. If inconsistency is
detected among the unique call
identifiers within the test period,
uplink crosstalk occurs.

DL N/ N/ Downlink crosstalk event that BSC6900 V900R014C00 (or later)

Cro A A occurs after a terminal gains access or BSC6910 V100R014C00 (or
ssta to the network and sends a Setup later)
lk message.
The crosstalk test can only detect
crosstalk events related to the
channels within the BSS (BTS<-
>TC) instead of those related on the
Um and A interfaces.
Principles for detecting downlink
crosstalk are as follows: The DSP
of the TC inserts the unique
identifier of a call into the free bit
of each TRAU frame on the
downlink voice channel. The DSP
of the BTS decodes all the unique
call identifiers and checks their
consistency. If inconsistency is
detected among the unique call
identifiers within the test period,
downlink crosstalk occurs.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 531

Par Ra Un Description Supported NE Version

am nge it
ete
r

Ove N/ N/ Long delay for a mobile-originated BSC6900 V900R014C00 (or later)

rlon A A terminal to gain access to the or BSC6910 V100R014C00 (or
g network. later)
Acc Call access delay (mobile-
ess originated) (s) – The access
Del duration for mobile-originated call
ay spans from the time when the
(M terminal sends a Channel Request
OC message to the time when the
) terminal sends an Assignment
Complete message.
You can set the threshold for long
call access delay (mobile-
originated) by using the source data
subscription function.

Ove N/ N/ Long delay for a mobile- BSC6900 V900R014C00 (or later)

rlon A A terminated terminal to gain access or BSC6910 V100R014C00 (or
g to the network. later)
Acc Call access delay (mobile-
ess terminated) (s) – The access
Del duration for mobile-terminated call
ay spans from the time when the
(M terminal sends a Channel Request
TC) message to the time when the
terminal sends an Assignment
Complete message.
You can set the threshold for long
call access delay (mobile-
terminated) by using the source
data subscription function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 532

Par Ra Un Description Supported NE Version

am nge it
ete
r

Ove N/ N/ Long duration spanning from the BSC6900 V900R014C00 (or later)
rlon A A time when a mobile-originated or BSC6910 V100R014C00 (or
g subscriber initiates a call to the later)
Call time when the subscriber hears the
Co alerting.
mpl Call completion delay (Altering)
etio (mobile-originated) (s) is the
n duration spanning from the time
Del when the mobile-originated
ay subscriber initiates a call (namely,
(Alt when the subscriber's terminal
erin sends a Channel Request message)
g) to the time when the subscriber
(M hears the alerting (namely, when
OC the terminal receives the Alerting
) message).
You can set the threshold for long
call completion delay (mobile-
originated) by using the source data
subscription function.

Ove N/ N/ Long duration spanning from the BSC6900 V900R014C00 (or later)
rlon A A time when a mobile-terminated or BSC6910 V100R014C00 (or
g subscriber initiates a call to the later)
Call time when the subscriber hears the
Co alerting.
mpl Call completion delay (Altering)
etio (mobile-terminated) (s) is the
n duration spanning from the time
Del when the mobile-terminated
ay subscriber initiates a call (namely,
(Alt when the subscriber's terminal
erin sends a Channel Request message)
g) to the time when the subscriber
(M hears the alerting (namely, when
TC) the terminal receives the Alerting
message).
You can set the threshold for long
call completion delay (mobile-
terminated) by using the source
data subscription function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 533

Par Ra Un Description Supported NE Version

am nge it
ete
r

Sho N/ N/ Exception where a call lasts shortly BSC6900 V900R014C00 (or later)
rt A A after a mobile-originated or BSC6910 V100R014C00 (or
Call subscriber gains access to the later)
(M network and successfully initiates
OC the call. This might be caused by
) one-way audio or crosstalk. A short
call occurs when the subscriber's
actual call duration is below a
specified short-call threshold (Call
duration = Timestamp of the
Disconnect message – Timestamp
of the Connect Acknowledge
message).
You can set the short-call threshold
by using the source data
subscription function.

Sho N/ N/ Exception where a call lasts shortly BSC6900 V900R014C00 (or later)
rt A A after a mobile-terminated or BSC6910 V100R014C00 (or
Call subscriber gains access to the later)
(M network and successfully initiates
TC) the call. This might be caused by
one-way audio, crosstalk, or
disturbance call. A short call occurs
when the subscriber's actual call
duration is below a specified short-
call threshold (Call duration =
Timestamp of the Disconnect
message – Timestamp of the
Connect Acknowledge message).
You can set the short-call threshold
by using the source data
subscription function.

Ab N/ N/ Abnormal value of the TA when a BSC6900 V900R014C00 (or later)

nor A A terminal sends a Channel Request or BSC6910 V100R014C00 (or
mal message. later)
TA You can set the exception threshold
on by using the source data
Acc subscription function.
ess

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 534

Par Ra Un Description Supported NE Version

am nge it
ete
r

Ab N/ N/ Abnormal RACH level when a BSC6900 V900R014C00 (or later)

nor A A terminal sends a Channel Request or BSC6910 V100R014C00 (or
mal message. later)
RA You can set the exception threshold
CH by using the source data
Lev subscription function.
el
on
Acc
ess

No N/ N/ Exception where no response to BSC6900 V900R014C00 (or later)

Ser A A service interaction is made when a or BSC6910 V100R014C00 (or
vice subscriber is using a data service. later)
Inte No response to service interaction
ract is made when the number of times
ion that the uplink PDU carries data but
Res the downlink PDU does not is
pon above threshold 1 for determining
se that no response to service
interaction is made, and the value
of A is above threshold 2 for
determining that no response to
service interaction is made (A =
Number of times that the uplink
PDU carries data but the downlink
PDU does not/[Number of times
that the uplink PDU carries data but
the downlink PDU does not +
Number of times that an interval is
available between the data
transmission by using the uplink
and downlink PDU, respectively]).
Thresholds 1 and 2 for determining
that no response to service
interaction is made are customized
algorithm parameters.

Att N/ N/ Attach failure that occurs when a BSC6900 V900R014C00 (or later)
ach A A subscriber is using a data service. or BSC6910 V100R014C00 (or
Fail Number of Attach Request later)
ure messages – Number of Attach
Accept messages > 0

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 535

Par Ra Un Description Supported NE Version

am nge it
ete
r

PD N/ N/ PDP activation failure that occurs BSC6900 V900R014C00 (or later)

P A A when a subscriber is using a data or BSC6910 V100R014C00 (or
Act service. later)
ive Number of PDP Active Request
Fail messages – Number of PDP Active
ure Accept messages > 0

AU N/ N/ AUC failure that occurs when a BSC6900 V900R014C00 (or later)

C A A subscriber is using a data service. or BSC6910 V100R014C00 (or
Fail Number of Authentication and later)
ure ciphering req messages – Number
of Authentication and ciphering
resp messages > 0

Las N/ N/ Last service interruption caused by BSC6900 V900R014C00 (or later)

t A A routing area update. or BSC6910 V100R014C00 (or
Ser later)
vice
Inte
rrup
ted
Due
to
Rou
ting
Are
a
Up
date

Ab N/ N/ Exception that occurs when access BSC6900 V900R014C00 (or later)

nor A A and reselection information area or or BSC6910 V100R014C00 (or
mal FLUSHLL exists. later)
Inte
rrup
tion
on
Cell
Res
elec
tion

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 536

Par Ra Un Description Supported NE Version

am nge it
ete
r

Ser N/ N/ Exception that occurs when RAN BSC6900 V900R014C00 (or later)
vice A A exception information shows that or BSC6910 V100R014C00 (or
Inte the number of abnormal downlink later)
rrup interruptions on the RAN side is
tion greater than 0 and that the cause of
s clearing the downlink LLC PDU
Due buffer is
to PDU_REMOVE_FLUSH.
FL
US
H
LL

Ser N/ N/ Exception that occurs when RAN BSC6900 V900R014C00 (or later)
vice A A exception information shows that or BSC6910 V100R014C00 (or
Inte the total number of abnormal later)
rrup uplink and downlink interruptions
tion on the RAN side is greater than 0
s (the interruptions occur because
Due the PDU is cleared due to timed-out
to PDU removal and due to TBF
TB exceptions.
F
Ab
nor
mal

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 537

Par Ra Un Description Supported NE Version

am nge it
ete
r

Ser N/ N/ Long duration for making a service BSC6900 V900R014C00 (or later)
vice A A interaction response when a or BSC6910 V100R014C00 (or
Inte subscriber is using a data service. later)
ract The duration for making a service
ion interaction response is long if any
Res of the following exceeds its
pon specified threshold:
se
Tim 1. Duration for the downlink PDU
eou to transmit data.
t 2. Duration for the uplink PDU to
receive data.
3. Interval between the data
transmission by using the
downlink PDU and the data
reception by using the uplink
PDU.
Specific devices are equipped to
directly detect whether the
preceding duration or interval
exceeds its specified threshold.

Ove N/ N/ Long average duration for making BSC6900 V900R014C00 (or later)
rlon A A a service interaction response when or BSC6910 V100R014C00 (or
g a subscriber is using a data service. later)
Ave Average duration for making a
rag service interaction response =
e Duration for data transmission by
Dur using the downlink PDU +
atio Duration for data reception by
n on using the uplink PDU + Interval
Ser between the data transmission by
vice using the downlink PDU and the
Inte data reception by using the uplink
ract PDU
ion
Res You can set the threshold by using
pon the source data subscription
se function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 538

Par Ra Un Description Supported NE Version

am nge it
ete
r

Lo N/ N/ Low download rate when a BSC6900 V900R014C00 (or later)

w A A subscriber is using a data service. or BSC6910 V100R014C00 (or
Do Download rate (kbit/s) = Number later)
wnl of bytes transmitted by using the
oad downlink PDU/Duration for the
Spe downlink PDU to complete
ed transmitting the bytes
You can set the threshold by using
the source data subscription
function.

Lo N/ N/ Low upload rate when a subscriber BSC6900 V900R014C00 (or later)

w A A is using a data service. or BSC6910 V100R014C00 (or
Upl Upload rate (kbit/s) = Number of later)
oad bytes transmitted by using the
Spe uplink PDU/Duration for the
ed uplink PDU to complete
transmitting the bytes
You can set the threshold by using
the source data subscription
function.

TB N/ N/ Displayed when any of the BSC6900 V900R014C00 (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 539

Analysis of Bottom Subscribers

Par Ra Un Description Supported NE Version
am nge it
ete
r

Use N/ N/ Unique identifier that the system BSC6900 V900R014C00 (or later)
r A A assigns to each bottom subscriber or BSC6910 V100R014C00 (or
Na troubled with exceptions. later)
me

Exc [0, Nu Number of the exceptions that BSC6900 V900R014C00 (or later)
epti +∞ mb trouble a subscriber under the or BSC6910 V100R014C00 (or
on ) er cause of a certain type of exception. later)
Occ
urre
nce
Tim
es

Rati [0.0 % Proportion of the exceptions that BSC6900 V900R014C00 (or later)
o 0,1 trouble a subscriber in all the or BSC6910 V100R014C00 (or
(%) 00. exceptions. later)
00]

Analysis of Bottom Terminal Models

Par Ra Un Description Supported NE Version
am nge it
ete
r

IM 000 N/ Type identifier of a bottom BSC6900 V900R014C00 (or later)

EI- 000 A terminal troubled with exceptions. or BSC6910 V100R014C00 (or
TA 00- later)
C 999
999
99

Ter N/ N/ Terminal model that is obtained by BSC6900 V900R014C00 (or later)

min A A using the terminal type or BSC6910 V100R014C00 (or
al management function based on later)
Mo IMEI-TAC.
del

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 540

Par Ra Un Description Supported NE Version

am nge it
ete
r

Exc [0, Nu Number of the exceptions that BSC6900 V900R014C00 (or later)
epti +∞ mb trouble a certain type of terminal or BSC6910 V100R014C00 (or
on ] er under the cause of a certain type of later)
Occ exception.
urre
nce
Tim
es

Rati [0.0 % Proportion of the exceptions that BSC6900 V900R014C00 (or later)
o 0,1 trouble a terminal in all the or BSC6910 V100R014C00 (or
(%) 00. exceptions. later)
00]

Analysis of Bottom Cells

Par Ra Un Description Supported NE Version
am nge it
ete
r

Cell N/ N/ The identity of a bottom BSC6900 V900R014C00 (or later)

Ide A A problematic cell is in the following or BSC6910 V100R014C00 (or
ntit format: LAC: CI. later)
y

Cell 1 to N/ Name of a bottom cell in which BSC6900 V900R014C00 (or later)

Na 64 A exceptions occur. or BSC6910 V100R014C00 (or
me cha later)
ract
ers

Exc [0, Nu Number of the exceptions that BSC6900 V900R014C00 (or later)
epti +∞ mb occur in a cell under the cause of a or BSC6910 V100R014C00 (or
on ] er certain type of exception. later)
Occ
urre
nce
Tim
es

Rati [0.0 % Proportion of the exceptions that BSC6900 V900R014C00 (or later)
o 0,1 occur in a cell in all the exceptions. or BSC6910 V100R014C00 (or
(%) 00. later)
00]

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 541

3.8 GSM Network Geographic Observation

3.8.1 Basics of GSM Network Geographic Observation

This section describes the basics of GSM network geographic observation, including the
function, technical specifications and feature restrictions. The basic knowledge helps users
perform operations related to GSM network geographic observation. You must read this section
before starting the analysis.

GSM Network Geographic Observation

Network geographic observation uses radio link measurement reports (MRs) of subscribers on
the live network to locate exceptions. This function combines data based on the call times in call
history records (CHRs) and MRs to achieve location positioning and then displays the
distribution of coverage, traffic, and exceptions of wireless networks on the geographic
information system (GIS) at the grid level. This helps network optimization engineers evaluate
network performance, identify hot spots, and quickly locate problematic areas in a
straightforward way.

Function Description
Network geographic observation displays the distribution of network coverage, traffic, and
exceptions based on data collected from the live network. It replaces traditional drive tests (DTs)
and addresses the problem that DTs fail to cover all areas, thereby providing telecom operators
with cost-effective network evaluation and problem identification means.

GSM network geographic observation supports network coverage geographic observation,

network traffic geographic observation, and network event geographic observation:
l Network coverage geographic observation supports the geographic rendering for the
following indicators: serving cell, UL coverage strength, DL coverage strength, UL poor
coverage and low quality, DL poor coverage and low quality, UL interference area, DL
interference area, LAC stability, areas without dominant cells, and locating confidence
level.
Functions:
– It displays the coverage of each serving cell on the live network and helps telecom
operators identify problematic areas, such as those with a poor coverage.
– It supports locating confidence indicators for engineers to evaluate the geographic
locating results. The system classifies all MR locating results into five levels A, B, C,
D, and E, calculates the proportion of MRs at each level to the total number of MRs in

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 542

each grid, and then renders the proportion results by grid. If an area has a high confidence
level, its KPIs or traffic is more reliable.
l Network traffic geographic observation supports the geographic rendering for the following
indicators: voice service traffic distribution and bad-quality traffic distribution.
Function: It displays the traffic distribution of each area on the live network on a map and
helps telecom operators identify traffic hot spots.
l Network event geographic observation supports the geographic rendering for the following
indicators: number of call drops (number of CS call drops), number of handover failures,
number of UL/DL PS access failures, and number of UL/DL PS call drops.
Function: It displays the locations where exceptions (including call access failures, call
drops, and handover failures) occur and the frequency for each type of exceptions in each
area on grid maps, helping telecom operators identify problematic areas where call drops
and handover failures occur frequently.

NOTE

For the Nastar geographic feature, the geographic location accuracy can be improved using the A-GPS
technology. To enable A-GPS data reporting, contact NE management/maintenance engineers to manually
enable the function on NEs. After the geographic feature is used, manually disable A-GPS data reporting
on NEs.

Application Scenarios
l Network optimization: By providing grid-level analysis on network coverage, traffic, and
events at this stage, the system helps identify problems such as weak coverage, intra-system
interference and improper network structure and then locates problematic cells through
associated grid-cell analysis. This helps to greatly reduce DTs. After the addressed
problems are solved, the system allows network optimization engineers to evaluate the
network quality before and after the optimization.
l Network planning or tuning: By geographically displaying traffic distribution at this stage,
the system helps identify hot spots and determine key network development and coverage
guarantee areas for telecom operators.
l Routine network assurance and maintenance: By geographically displaying network events
at this stage, the system helps network optimization engineers identify areas where
exceptions such as call drops and handover failures occur and provides guidance for
troubleshooting.
Traditional network guarantee and routine problem locating use network performance KPIs
to identify and analyze cell-level call drops and handover failures. Exceptions occurred in
certain coverage areas of a cell might be ignored because users see only the average KPI
values and, if telecom operators fail to pay attention to such exceptions, complaints will
arise. By geographically displaying exceptions such as call drops and handover failures on
the live network, the system helps network optimization engineers quickly identify areas
where exceptions occur frequently. Then, in conjunction with functions such as cell
performance analysis and the GIS, the engineers can further locate radio frequency (RF)
causes so as to improve user experience of the entire network.

Function Principles
The data source of network geographic observation is the CHR and MR data on the NE side.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 543

Figure 3-38 shows the principles for collecting, importing, and analyzing data on the Nastar.
For detailed operations, see Table 3-23.

Figure 3-38 Principles for analysis

Table 3-23 Description of analysis

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Issue an eS U20 To issue an MML command to the U2000/M2000.

MML AU 00/
comma M20
nd 00

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 544

User Proced So Dest Purpose

Operat ure urc inati
ion e on

Forward U2 BSC/ To forward the MML command to the NE through the

the 000 RNC U2000/M2000, requesting the NE to generate raw data.
MML /
comma M2
nd 000

Upload BS SAU To upload the raw data to the SAU.

raw data C/
RN
C

2. Issue an Nas eSA To deliver a data-preprocessing request to the eSAU.

Deliver eS SAU To deliver a data-preprocessing request to the SAU,

a data- AU requesting the SAU to start the data-preprocessing task.
preproc
essing
task
(direct)

Upload SA eSA To upload preprocessed data to the eSAU.

preproc U U
essed
data
(direct)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 545

User Proced So Dest Purpose

Operat ure urc inati
ion e on

analysi Upload eS Nast To aggregate the data reported by SAUs, generate data
s task data AU ar analysis results, and upload the data analysis results to
analysis Serv the Nastar server.
results er

5. View Display - Nast To display analysis results on the Nastar client.

analysi analysis ar
s results results Serv
er

NOTE

The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of
MML Commands Delivered by Subscription Function.

Technical Specifications for GSM Network Geographic Observation

This section describes the technical specifications, including the analysis ability and the range
of analysis time.

Item Service Specifications

Execution type One-time or periodic task

Network scale for one l <= 6000 cells (when the Nastar hardware supports a
analysis task management capacity of 400 equivalent NEs for the live
network)
l <= 12,000 cells (when the Nastar hardware supports a
management capacity of 800 equivalent NEs for the live
network)
l <= 18,000 cells (when the Nastar hardware supports a
management capacity of 1200 equivalent NEs for the live
network)

Number of allowed l <= 50 one-time tasks

analysis tasks l <= 10 periodic tasks

Time range for data in 7 days

one analysis task

Duration of one analysis <= 60 minutes

task

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 546

Item Service Specifications

Default duration for 15 days

storing analysis data

Maximum duration for 15 days

storing analysis data

3.8.2 Preparations for GSM Network Geographic Observation

Before starting a GSM network geographic observation, you check the user rights and the
matching environment, and prepare relevant data to ensure that the GSM network geographic
observation task is performed normally. You must read this section before starting the analysis.

Checking the License and User Rights

l Check that you have applied for a valid license for GSM network geographic observation.
l Check that you have the operation rights to subscribe to GSM network geographic
observation data upon login.
You are advised to contact the administrator to turn on the data switch because the analysis
data subscription function has a high security requirement.
l Check that you have the operation rights to create GSM network geographic observation
tasks upon login, and the operation rights to operate the analyzed NEs.

Preparing Basic Data

Before analyzing, prepare the following basic data described in Table 3-24 for performing the
task successfully.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 547

Table 3-24 Required basic data of network geographic observation

Data Function Operation

Type

Config The configuration data of If the OSS information has been already configured, the
uratio the NE controlling the Nastar automatically and periodically collects and
n Data test cell and neighboring imports the configuration data after the OSS and NE
(Mand cells is used to correctly information is configured. You can also manually
atory) analyze the information collect the configuration data before the specified time
about the test cell and period starts. After the configuration data is imported,
neighboring cells and you can choose Maintenance > Data Maintenance
collect the analysis data Management to check whether the configuration data
of these cells from the is available in the Nastar database. For detailed
network during the information about collecting, importing, and checking,
analysis process. see 2.5.2 Checking the Integrity of Configuration
Data.
After the configuration data has been successfully
imported, you are advised to check the validity of the
configuration data. The purpose is to avoid expiration
of configuration data due to network adjustment.
Expired configuration data may cause incorrect cell
information in the analysis result. For detailed
operations, see Checking Engineering Parameters
and Configuration Data.

Engin The engineering In the navigation tree of the Analysis Task

eering parameters for a specific Management window, choose System Function >
Param area include the cell Engineering Parameter Management. Then double-
eters longitude and latitude click Engineering Parameter Management to check
(Mand and the antenna azimuth. whether engineering parameters have been imported. If
atory) The information is used the parameters are unavailable, you must import the
for the effective engineering parameter template. The Nastar can import
identification of the engineering parameter files in .csv, .xls, and .xlsx
neighboring cell format, but engineering parameter fields must be set
information and correctly. For details about the fields and templates
geographic display of supported by the Nastar, see Appendix: Engineering
analysis results during Parameter Templates.
theme analysis. After the engineering parameters are successfully
imported, you are advised to check whether the
engineering parameters are consistent with the
configuration data and whether the engineering
parameters are correct. For example, if the cell
identification information in the engineering
parameters is not consistent with the configuration data,
the TOP cell will be repeated in the network geographic
observation function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 548

Data Function Operation

Type

Map The map file for a You can import the map files in wor, tab, or sxwu
File specific area displays the format to the Nastar. If the PC is connected to the
(Optio analysis result Internet, you can view analysis results on the Google
nal) geographically. You do Earth. For details, see 2.5.4 Preparing the Map File
not need to prepare the (Optional).
map file if you do not
want to view the analysis
result on the map.

Checking the Matching Environment

l Check that the matching U2000/M2000 version is V200R012C00 (or later), and the NE
version is BSC6900 V900R014C00 (or later) or BSC6910 V100R014C00 (or later).
l If you want to analyze the PS network geographic observation function, check that the PS
network control mode is set. For detailed operations, see Commissioning the Function of
Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data
(GSM) > Setting the PS Network Control Mode in Nastar Commissioning Guide.

3.8.3 Process of GSM Network Geographic Observation

This section describes the process of GSM network geographic observation and each procedure
in the process.

This section includes the following information:

l Prerequisites
l Process
l Subscription Task Parameters
l Analysis Task Parameters

Prerequisites
You have finished the preparation of network geographic observation, such as checking the
operation rights, preparing the basic data, and so on. For details, see 3.8.2 Preparations for
GSM Network Geographic Observation.

Process
Figure 3-39 shows the analysis process.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 549

Figure 3-39 Analysis process

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 550

Table 3-25 Description of the network geographic observation process

(3) Create Navigation path: Choose Theme Function > Network l For
an Analysis > GSM Network Geographic Observation in details,
analysis the navigation tree of the Analysis Task Management see 2.8
task window. Creating
Procedure: an
Analysis
1. Double-click GSM Network Geographic Task.
observation.
l For details
2. Specify the task name and remarks. Then, click Next. about the
3. On the Grid Resolution Settings tab page, select the parameter
Grid Resolution for displaying terminal geographic s, see
observation results. Analysis
4. On the Select NE(s) tab page, select the NEs to be Task
analyzed. Then, click Next. Paramete
rs.
5. Specify the time period. After the task is executed, the
Nastar obtains the observation results for the specified
time period.
6. Click Finish.

(4) View Navigation path: In the upper right area of the Analysis l For
analysis Task Management window, select an analysis task in the details,
results Finished state. In the lower right of the Task Result area, see 2.9
select a result record of the task. Querying
Procedure: Analysis
Results.
1. Right-click the result record and choose Network
Geographic Observation from the shortcut menu. l For details
on the
2. In the Geographic Observation window, view the descriptio
observation results matching the record. n of the
window
for
showing
analysis
results,
see 3.8.4
Interface
Descripti
on: GSM
Network
Geograp
hic
Observat
ion.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 553

No. Proced Description Reference

ure

(5) Export Navigation path: Click the icon on the button area in the l For
analysis upper left part of the Geographic observation window. details,
results Procedure: see 2.11
Exportin
1. Click the export icon on the button area. g
2. Set the export format and path of a file, and the export Analysis
counter and range of data. Reports.
3. Click Save. l For details
on the
descriptio
n of the
window
for
showing
analysis
results,
see 3.8.4
Interface
Descripti
on: GSM
Network
Geograp
hic
Observat
ion.

Subscription Task Parameters

Basic Subscription

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 554

Parameter Description

Network Switch for enabling or disabling the reporting of CS CHR data. You can
Geographic retain the default state of the switch.
Observation
Data (CHR- You can click to set the following advanced parameters:
CS) l Service: specifies the service types for which CS CHR data is to be
reported. The service types include call, short message service (SMS),
and location update (LU). You can select all or none of the service types
or retain the existing settings.
l Error: specifies the types of information contained in reported CS CHR
data. If you select All, all CS CHR data containing normal and abnormal
service procedures is reported.
l Event Block: specifies that GSM does not support event blocks.
l All Signaling: specifies the types of all signaling messages contained in
reported CS CHR data. For details, see the SET GCSCHRCTRL
command in the related NE product documentation. You can select all or
none of the types or retain the existing settings.
l HQI Threshold: specifies the method of calculating the HQI threshold
during CS CHR tracing. For details, see the SET BSCEXSOFTPARA
command in the related NE product documentation. You can set this
parameter to a value ranging from 0 to 6 or retain the existing settings.
NOTE
HQI Threshold applies only to BSC6900 V900R015C00 (and later versions) and
BSC6910 V100R015C00 (and later versions).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 555

Parameter Description

Network Switch for enabling or disabling the reporting of PS CHR data. You can retain
Geographic the default state of the switch.
Observation
Data (CHR- You can click to set the following advanced parameters:
PS) l Event Block: specifies that GSM does not support event blocks.
l Service Type Information Report Switch: specifies whether to report
information about the service types contained in PS CHRs. For details,
see the SET GPSCHRCTRL command in the related NE product
documentation.
l Judge Delay-Related Services: For details, see the SET
GPSCHRCTRL command in the related NE product documentation.
l Overlong DL PDU Sending Delay Threshold for Delay-Related Services:
For details, see the SET GPSCHRCTRL command in the related NE
product documentation.
l Overlong UL PDU Receiving Delay Threshold for Delay-Related
Services: For details, see the SET GPSCHRCTRL command in the
related NE product documentation.
l Abnormal UL/DL PDU Interval Threshold for Delay-Related Services:
For details, see the SET GPSCHRCTRL command in the related NE
product documentation.
l UL PDU Response Waiting Threshold for Delay-Related Services: For
details, see the SET GPSCHRCTRL command in the related NE product
documentation.
l Overlong DL PDU Sending Delay Threshold for Rate-Related Services:
For details, see the SET GPSCHRCTRL command in the related NE
product documentation.
l Overlong UL PDU Receiving Delay Threshold: For details, see the SET
GPSCHRCTRL command in the related NE product documentation.

Network Switch for enabling or disabling the reporting of CS MR data. You can retain
Geographic the default state of the switch.
Observation
Data (MR- You can click to set the following advanced parameters:
CS) l Collection Switch: For details, see the SET GMRCTRL command in
the related NE product documentation.
l Original Sampling Rate: For details, see the SET GMRCTRL command
in the related NE product documentation.
l Preprocessed Sampling Rate: For details, see the SET GMRCTRL
command in the related NE product documentation.
l MRLOG Neighboring Cell Format: For details, see the SET
GMRCTRL command in the related NE product documentation.

Application Subscription

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 556

Parameter Description Value Range

Traffic Down Indicates the threshold for poor quality traffic. X: an integer
Link RxQual The Nastar obtains the data that shows a downlink between 0 and 7. The
>= X receive quality greater than or equal to X. default value is 6.

X indicates the level of downlink receive quality.

Down Link Indicates the threshold for poor downlink coverage X: an integer
RxQual >= X and low quality. between 0 and 7. The
and Down Link The Nastar obtains the data that shows a downlink default value is 6.
RxLev (dBm) receive quality greater than or equal to X and a Y: -110.0~0.0. The
<= Y receive level smaller than or equal to Y. default value is
X indicates the level of downlink quality. -90.0.

Y indicates the downlink level.

Up Link Indicates the threshold of poor uplink coverage and X: an integer

RxQual >= X low quality. between 0 and 7. The
and Up Link The Nastar obtains the data that shows an uplink default value is 6.
RxLev (dBm) receive quality greater than or equal to X and an Y: -110.0~0.0. The
<= Y uplink receive level smaller than or equal to Y. default value is
X indicates the level of uplink quality. -95.0.

Y indicates the uplink level.

Absolute Indicates non-dominant cells. X: an integer from 1

Down Link If the absolute value of the downlink receive level to 20. The default
RxLev difference between a serving cell and its value is 5.
between Main neighboring cell is smaller than X, the serving cell Y: an integer from 1
cell and is regarded as an area without a dominant cell. to 6. The default
Neighboring value is 2.
Cell (dB) < X The Nastar obtains the number of neighboring cells,
which meet conditions of non-dominant cells. The
Satisfy Cell number of neighboring cells is greater than or equal
Count >= Y to Y.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 557

Parameter Description Value Range

X < Up Link Defines the uplink interference threshold. l X and Y: an

RxLev(dBm) The Nastar obtains the data that shows an uplink integer from
<= Y and Up receive level ranging from X to Y and an uplink -110.0 to 0.0 and
Link RxQual receive quality greater than or equal to P, the data by default they
>= P or that shows an uplink receive level ranging from M are -90.0 and
M < Up Link to N and an uplink receive quality greater than or -85.0.
RxLev(dBm) equal to Q, or the data that shows an uplink receive P: an integer
<= N and Up level greater than Z and an uplink receive quality from 0 to 7 and
Link RxQual greater than or equal to R. by default it is 7.
>= Q or l M and N: an
Up Link integer from
RxLev(dBm) > -110.0 to 0.0 and
Z and Up Link by default they
RxQual >= R are -85.0 and
-80.0.
Q: an integer
from 0 to 7 and
by default it is 6.
l Z: an integer
from -110.0 to
0.0 and by
default it is
-80.0.
R: an integer
from 0 to 7 and
by default it is 5.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 558

Parameter Description Value Range

X < Down Link Defines the downlink interference threshold. l X and Y: an

RxLev(dBm) The Nastar obtains the data that shows a downlink integer from
<= Y and Down receive level ranging from X to Y and a downlink -110.0 to 0.0 and
Link RxQual receive quality greater than or equal to P, the data by default they
>= P or that shows a downlink receive level ranging from are -90.0 and
M < Down M to N and a downlink receive quality greater than -85.0.
Link Rxlex or equal to Q, or the data that shows a downlink P: an integer
(dBm) <= N receive level greater than Z and a downlink receive from 0 to 7 and
and Down Link quality greater than or equal to R. by default it is 7.
ReQual >= Q l M and N: an
or integer from
Down Link -110.0 to 0.0 and
RxLev(dBm) > by default they
Z and Down are -85.0 and
Link RxQual -80.0.
>= R Q: an integer
from 0 to 7 and
by default it is 6.
l Z: an integer
from -110.0 to
0.0 and by
default it is
-80.0.
R: an integer
from 0 to 7 and
by default it is 5.

Analysis Task Parameters

Basic task information

Parameter Description

Task Name Name of an analysis task.

Task Type Type of an analysis task to be created.

Remarks Description of the task.

Value range: The name contains a maximum of 200 characters.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 559

NE information

Parameter Description

Select NE(s) NEs or cell groups to be selected for analysis.

Parameter information

Parameter Description

Time information of one-time task

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

Delay If you do not select this parameter, the system executes the task
immediately.
If you select this parameter, the system executes the task at the time
specified in Execute on.

Execute on Time when a task is executed.

Time information of periodic task

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 560

Param Description Note

eter

Start Date for starting a task. Start Time of a periodic task = Next
time time point + Delay by (hours)
Time period of a periodic task: [Start
Period Interval between periodic tasks.
Time of a periodic task - Period, Start
Value range: 1 to 7 Days. Time of a periodic task]
Repeat Number of times that a periodic task is The Next time point is related to Start
times executed. If you set this parameter to 0, time and Period. If you set Period to N
the task is executed all the time. Day, the Next time point is 00 hours:00
minutes:00 seconds of the (N + 1) day
Value range: 0 to 9999
starting from Start time.
Delay Time delayed for executing a task. NOTE
by Value range: 0 to 24. Unit: hour. l If the start time of a periodic task is
(hours) later than the current server time, the
NOTE Nastar automatically executes the task
If DST starts before a task is executed, the at the start time.
execution delay will be automatically Example: If the current server time is
updated to ensure that the task can be 01/01/2013 14:00:00, Start time is
executed at the specified time. For example, 01/02/2013, Period is 1 Day, and Delay
if you set Start time at 01:00 on a day, and by (hours) is 3, the Nastar automatically
the value of Delay by (hours) for the task executes the task at 01/03/2013
was set to 3 hours, the task was scheduled to 03:00:00.
be executed at 04:00. However, DST started
l If the start time of a periodic task is
before 02:00 on that day, and 02:00 was
earlier than the current server time, the
changed to 03:00. As a result, the value of
Nastar immediately executes the task.
Delay by (hours) for the task was
Example: The current server time is
automatically updated to 4 hours so that the
01/02/2013 14:00:00, Start time is
task was executed at 05:00 (equal to 04:00
01/01/2013, Period is 1 Day, and Delay
before DST started).
by (hours) is 3, the Nastar immediately
Whole If you select this parameter, it works the executes the task.
day same as All Busy Time under Busy
hours.
You are not allowed to set this
parameter.

Busy If you set this parameter, the system

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 561

3.8.4 Interface Description: GSM Network Geographic Observation

This section describes the interface that displays GSM network geographic observation results.

Navigation Path
Use either of the following methods to open the interface that displays GSM network geographic
observation results:
l Select a finished GSM network geographic observation task and double-click a result record
in the Task Result area.
l Select a finished GSM network geographic observation task, right-click a result record in
the Task Result area, and choose Geographic Observation from the shortcut menu.

Interface
Figure 3-40 shows the interface that displays network geographic observation results on grid
maps.

Figure 3-40 Interface for GSM network geographic observation results

NOTE

results. That is, only the results of selected NEs can be displayed
in the map window.
– Confidence Level tab page: enables you to set the percentage
of MRs featured with a specified confidence level in all MRs in
a grid. After the percentage is set, statistical results are displayed
in this grid only when the percentage of MRs featured with a
specified confidence level in all MRs is higher than the value
of the configured percentage. Otherwise, no statistical results
are displayed in this grid.
– Parameter tab page: enables you to specify the displayed
parameter. That is, only the results met the parameter value can
be displayed in the map window.
– You can set the proportion of poor-quality traffic on the
Parameter tab page to obtain the analysis results of Poor-Quality
Traffic Distribution(G).

3 Geographi l Displays the analysis results of selected KPIs on grid maps using
c distinct colors by default. However, only the analysis results of the last
observatio selected KPI are visible.
n area – You can select a grid to view the lines connecting the grid and the
Top 5 cells related to the grid.
NOTE
The lines connecting the top cells in grids are not affected by the function
of filtering site layers by frequency or frequency band. If the filtering
function is enabled, the Nastar displays only the filtered sites. However, no
matter whether the filtering function is enabled or disabled, the Nastar
displays all the top cells in grids and the lines connecting these top cells.
– You can right-click a cell and use the shortcut menu to view all
grids covered by the cell.

l Displays analysis results in multiple windows. If you click , the

Nastar divides the current window into multiple small windows with
each small window displaying the analysis results of one KPI. The
small windows are zoomed in, zoomed out, and moved
simultaneously. If you click the icon again, the Nastar displays the
original window.

4 Grid Displays selected KPIs on different tab pages. Each tab page shows the
Details contribution values of the Top 5 cells related to a selected grid under this
area KPI. If you switch to another tab page, the grid-cell connecting lines
displayed in area 3 are updated according to the current KPI.
NOTE
If the contribution value of a cell for this KPI is 0%, this cell is not displayed in the
list of top 5 cells.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 565

N Item Description
o.

5 Legend By default, the Nastar does not display this area. If you want to view the
details area legend details about an analysis theme, click the icon in the button area.
The Nastar distinguishes between directional and omnidirectional cells
using different legends. You can change the legend for directional cells.
The legend for omnidirectional cells is set the Nastar by default, and
therefore you cannot change it.

6 Informatio The interface displays no information when it is opened. If you select a

n area grid, the values of selected KPIs in this gird are displayed. If you select a
site, information about the site is displayed. If you select a cell,
information about the cell such as engineering parameters and longitude
and latitude coordinates is displayed.

3.9 VIP Analysis

3.9.1 Basics of VIP Analysis

This section describes the basics of VIP analysis, including the function and technical
specification. The basic knowledge helps you perform VIP analysis. You are recommended to
read this section before performing VIP analysis.

Functions of VIP Analysis

VIP analysis depends on IMSIs reported by UEs during calls. It enables the Nastar to periodically
collect statistics on and analyze the wireless service experience of VIP subscribers or VIP groups.
VIP groups are key group subscribers or the cluster subscribers with the same characteristics.
By analyzing data, you can learn information, such as the quality of services experienced by
VIP subscribers, the radio environment where exceptions occurred, and the service process of
the control plane. VIP analysis helps quickly detect and identify possible network problems
experienced by VIP subscribers in time, improve operation efficiency, and reduce operation
expenditure. It also helps you ensure the user experience of VIP subscribers, improve VIP
subscriber satisfaction, and avoid losing VIP subscribers.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 566

Function Scenarios
l During network assurance, you can evaluate the KPIs of VIP subscribers to learn the service
usage of these VIP subscribers in time. You can also analyze the KPI trends of VIP
subscribers based on trend analysis to monitor the KPI information of these VIP subscribers.
l During network optimization, if the deteriorating KPI of a VIP subscriber cannot be
identified or located onsite, you can perform VIP in-depth analysis to obtain the detailed
call records of the VIP subscriber. Then, you can rapidly obtain problem identification and
analysis results to analyze the problem. This function also allows you to use the VIP KPI
evaluation function to verify that the problem is solved.
l During network optimization, if the control plane of a VIP subscriber is normal but the
service quality is unsatisfactory during calls or if the identification of complicated
exceptions requires analysis of the whole signaling procedure, you can perform VIP all-
signaling analysis on a few VIP subscribers.

Function Description
VIP Report Analysis (GSM/UMTS/LTE/PS Core)

The Nastar periodically collects statistics on and analyzes various user assurance KPIs of VIP
subscribers and VIP groups, and generates different types of service assurance reports.
l Generates KPI reports on the network, CS services, and PS services on the RAN side, and
collects statistics on and analyzes the success rate and delay of each key procedure on the
CN side. This helps you quickly learn the service usage of VIP subscribers or VIP groups.
l Generates KPI reports on the active cells on the RAN side. This helps you quickly detect
the areas where VIP subscribers or VIP groups often appear and locate major problems
occurred in these areas. You can then solve the problem of service quality deterioration
experienced by VIP subscribers in time if the problem is caused by a cell.
l Generates KPI reports on the active servers for PS services. This helps you quickly locate
the servers that VIP subscribers or VIP groups often visit and solve the problem of service
quality deterioration caused by server problems in time. This function is available only for
GSM.

VIP In-depth Analysis (GSM/UMTS/LTE/PS Core)

This function allows you to retrieve and analyze the call history information of a VIP subscriber
if the KPIs of the VIP subscriber deteriorates but the problem cannot be located or identified
onsite.
l Allows you to quickly locate the key call history information which results in the
deterioration of the KPIs and demarcate exceptions based on analysis.
l Allows you to analyze and demarcate the causes of identified exceptions based on
information, such as the cause of abnormal release, measurement report collected before
radio link release, mobility, and key signaling procedures during each call.

VIP Trend Analysis (GSM/UMTS/LTE/PS Core)

In the traditional method, you need to first save and manually process periodic analysis results
and then analyze the trends of specific KPIs, which result in low work efficiency. By contrast,
this function improves the work efficiency.

The application scenarios of this function are described as follows:

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 567

l Engineers can learn about VIP subscribers' service preferences by analyzing the trend of
their service usage.
l You can learn whether user assurance problems of VIP subscribers have been solved by
analyzing the trend of their service exceptions, such as call completion delay, and number
of short calls.
l You can learn poor user assurance caused by minor but persistent exceptions within a short
period of time by comparing and analyzing data collected based on different periods.

VIP Active Cells Displayed on the GIS (GSM/UMTS/LTE)

Combined with the GIS, the VIP analysis function can geographically display and render active
cells by group. If you select an active cell in the table, the active cell is also selected on the GIS.
In this way, you can quickly locate a cell and improve the efficiency of locating and analyzing
a problem.

VIP All-Signaling Analysis (GSM/UMTS/LTE)

If a VIP subscriber's control plane is normal but service quality problems occur during a call or
if complicated exceptions require analysis on complete signaling procedures, this function helps
you solve such problems. For details, see Table 3-26.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 568

Table 3-26 Description of VIP all-signaling analysis

Net Number of Supported Required NE Function

wor Supported VIP Signaling Range Version Display Mode
k All-Signaling
Subscribers

GS <= 500/BSC l All-signaling If you want to view For VIP

M VIP subscribers analysis on CS the all signaling subscribers of
are managed as services: A information on CS Important level
Important VIP interface domain, check that who subscribe to
subscribers by (3GPP-48.008) the matching all-signaling data, a
using the VIP signaling, Abis BSC6900 version complete signaling
group interface is V900R011C00 procedure will be
management (3GPP-48.058) or later. If you want displayed in the in-
function. signaling, and to view the all depth analysis
Um interface signaling function, and you
(3GPP-44.018/ information on PS can double-click a
44.060) domain, check that signaling record
signaling. the matching and then analyze
l All-signaling BSC6900 version detailed signaling
analysis on PS is V900R014C00 contents in the
services: Gb or later. displayed window.
interface
(3GPP-48.016/
48.018/24.008)
signaling, Um
interface
(3GPP-44.018/
44.060)
signaling. For a
detailed
signaling list,
see Key
Signaling (PS
Domain).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 569

Net Number of Supported Required NE Function

wor Supported VIP Signaling Range Version Display Mode
k All-Signaling
Subscribers

UM l <= 100/RNC Iu interface (3GPP If you want to view For VIP

TS (BSC6900 TS 25.413) the all signaling subscribers of
V900R013C0 signaling, Iur information, check Important level
0 or later interface (3GPP TS that the matching who subscribe to
version) 25.423) signaling, BSC6900 version all-signaling data, a
l <= 500/RNC Iub interface is V900R013C00 complete signaling
(BSC6900 (3GPP TS 25.433) or later. procedure will be
V900R016C0 signaling, Uu displayed in the
0 or later interface (3GPP TS deep analysis
version) 25.331) signaling. function, you can
double-click a
VIP subscribers signaling record
are managed as and then analyze
Important VIP detailed signaling
subscribers by contents in the
using the VIP displayed window.
group
management
function.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 570

Net Number of Supported Required NE Function

wor Supported VIP Signaling Range Version Display Mode
k All-Signaling
Subscribers

LTE <= 500/HSS Signaling LTE3900 The in-depth

VIP subscribers messages on the V100R008C00 or analysis function
are managed as S1-MME interface later; U2000/ displays signaling
Important VIP (3GPP M2000 procedures in
subscribers by specifications - V200R013C00SP charts and allows
using the VIP 36.423), X2 C230 or later; you to double-click
group interface (3GPP HSS9860 a signaling
management specifications - V900R008C01 or message and
function. 36.413), and Uu later. analyze details
interface (3GPP Note: You can about the signaling
specifications - analyze the key message in the
36.331). signaling displayed window.
Note: This function procedures of
allows you to common
analyze the subscribers other
signaling than the 500
procedures, Important VIP
including RRC subscribers only in
connection setup LTE3900
and release, eRAB V100R005C00SP
setup and release, C370 or later.
context setup and
release, and
handover, of
common
subscribers other
than the 500
Important VIP
subscribers. For
details, see Key
Signaling. For
3GPP
specifications, see
TS
36.331/36.413/36.
423.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 571

Net Number of Supported Required NE Function

wor Supported VIP Signaling Range Version Display Mode
k All-Signaling
Subscribers

Mult <= 500 of all the - - -

i- RATs on the
RAT entire network.
netw VIP subscribers
orks are managed as
Important VIP
subscribers by
using the VIP
group
management
function.

Principles of VIP Analysis

This section describes the data source and the function principles of the VIP analysis.

Data Source
The Nastar uses the CHR data for the VIP analysis both on the RAN side and the PS Core side.
You can choose the following scenes to analysis: CHR only on the RAN side, CHR only on the
PS Core side, CHR both on the RAN side and the PS Core side.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 572

NOTE

l On the LTE network, the CHR data includes the eNodeB CHR data and the MME CHR data. The MME
CHR data provides the IMSI and IMEI information. For the all signaling analysis, the data source is the
eNodeB single-subscriber all-signaling data.
l The Nastar provides sufficient protection for service data used by this function, such as IMSI and IMEI
information, to ensure personal data security. For details about the service data and protection policies,
seeDescriptions > Nastar Security Description > Application Security > Protecting Private
Subscriber Data.
The Nastar provides an anonymization mechanism for processing personal data, such as the IMSI, IMEI,
MSISDN, and IMEISV. After this mechanism is used, the Nastar no longer allows you to enter the plaintext
IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain the encrypted IMSI.
The Nastar does not support the encrypted MSISDN. Telecom operators can contact the Huawei technical
support engineers to visit http://support.huawei.com and choose Support > Software > Global
Service > Managing Customer Experience Service-SmartCare > Network Optimization Service >
GENEX Mobile Manager > HMACUtil.
l You have checked whether the subscriber identity anonymization switch or the encryption key is changed.
If the subscriber identity anonymization switch or the encryption key is changed, see 2.12.3
Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or
the Encryption Key.
l On the PS Core network, the CHR data includes the SGSN/MME CHR data and the GGSN/SAE-GW
CHR data.
l The CHR flow control function has been available since BSC6900 V900R016C00 and BSC6910
V100R016C00. When the SPU CPU load on an UMTS RNC exceeds a predefined threshold, the RNC
restricts the output of CHR event blocks, which affects the correctness of counters in Nastar analysis
results. For details about the CHR flow control policies, see the related NE product documentation.

Function Principles
Figure 3-41 shows the principles for collecting, importing, and analyzing data on the Nastar.
For detailed operations, see Table 3-27.

NOTE

This section describes how the function is implemented when the Nastar is deployed using the direct networking
scheme.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 573

Figure 3-41 Principle for analysis function

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 574

Table 3-27 Description of VIP analysis

User Scen Proce Sour Dest Purpose

Oper e dure ce inati
ation on

1. GSM Issue a Nast eSA To turn on the data source switch on the NE side.
Subscr / basic ar U After a user enables the basic data subscription
ibe to UMT data Serv function (GSM VIP analysis or UMTS VIP
basic S subscri er analysis) on the Nastar client, the Nastar issues
data netw ption a basic data subscription command to the eSAU.
ork comma
nd
(GSM/
UMTS
)

Issue eSA U200 To issue an MML command to the U2000/

an U 0/ M2000.
MML M20
comma 00
nd

Forwar U20 BSC/ To forward the MML command to the NE

d the 00/ RNC through the U2000/M2000, requesting the NE to
MML M20 generate raw data.
comma 00
nd

Upload BSC/ SAU To upload the raw data to the SAU.

raw RNC
data

PS Issue a Nast eSA To turn on the data source switch on the NE side.
Core basic ar U After a user enables the basic data subscription
netw data Serv function (PS Core VIP analysis) on the Nastar
ork subscri er client, the Nastar issues a basic data subscription
ption command to the eSAU.
comma
nd

Issue eSA U200 To issue an MML command to the U2000/

an U 0/ M2000.
MML M20
comma 00
nd

Forwar U20 SGS To forward the MML command to the NE,

d the 00/ N/ requesting the NE to generate raw data.
MML M20 MM
comma 00 E
nd

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 575

User Scen Proce Sour Dest Purpose

Oper e dure ce inati
ation on

Upload SGS PS To upload the raw data to the PS SAU.

raw N/ SAU NOTE
data MM The generation and transmission of the GGSN/SAE-
E/ GW CHR data is not triggered by the Nastar
GGS subscription command. The GGSN/SAE-GW CHR
data will be uploaded to the PS SAU through Huawei
N/
internal protocols in real time after the CHR data
SAE switch is enabled.
-GW

LTE Issue a Nast eSA To turn on the data source switch on the NE side.
netw basic ar U After a user enables the basic data subscription
ork data Serv function (LTE VIP analysis) on the Nastar client,
subscri er the Nastar issues a basic data subscription
ption command to the eSAU.
comma
nd

Issue a eSA U200 To issue a subscription command to the U2000/

subscri U 0/ M2000.
ption M20
comma 00
nd

Forwar U20 eNod l For VIP summary/in-depth/trend analysis:

d the 00/ eB The U2000/M2000 issues a subscription
subscri M20 command to the eNodeB, requesting the
ption 00 eNodeB to generate eNodeB CHRs.
comma l For VIP all-signaling analysis: The U2000/
nd M2000 issues a subscription command to the
HSS, and the HSS then requests the eNodeB
to generate all-signaling trace data for single
subscribers through the MME.

Upload eNod Trace l To upload the raw data (eNodeB CHR and
raw eB/ Serve eNodeB single-subscriber all-signaling data)
data MM r/ from the eNodeB to the Trace Server.
E LTE l To upload the raw data (MME CHR) from the
SAU MME to the LTE SAU directly.
NOTE
The generation and transmission of the MME
CHR data is not triggered by the Nastar
subscription command. The MME CHR data will
be uploaded to the LTE SAU through Huawei
internal protocols in real time after the CHR data
reporting values are configured and the CHR data
transmission switch is enabled.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 576

User Scen Proce Sour Dest Purpose

Oper e dure ce inati
ation on

2. GSM Issue Nast eSA To deliver a data-preprocessing request to the

Subscr / an ar U eSAU. After a user enables the application data
ibe to UMT applica Serv subscription function (GSM VIP analysis or
applic S tion er UMTS VIP analysis) on the Nastar client, the
ation netw data Nastar issues a data-processing command to the
data ork subscri eSAU.
ption
comma
nd

Deliver eSA SAU To deliver a data-preprocessing request to the

a data- U SAU, requesting the SAU to start the data-
prepro preprocessing task.
cessing
task
(direct)

Upload SAU eSA To upload preprocessed data to the eSAU.

prepro U
cessed
data
(direct)

PS Issue Nast eSA To deliver a data-preprocessing request to the

Core an ar U eSAU. After a user enables the application data
netw applica Serv subscription function (PS Core VIP analysis) on
ork tion er the Nastar client, the Nastar issues a data-
data processing command to the eSAU.
subscri
ption
comma
nd

Deliver eSA PS To deliver a data-preprocessing request to the PS

a data- U SAU SAU, requesting the PS SAU to start the data-
prepro preprocessing task.
cessing
task
(direct)

Upload PS eSA To upload preprocessed data to the eSAU.

prepro SAU U
cessed
data
(direct)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 577

User Scen Proce Sour Dest Purpose

Oper e dure ce inati
ation on

LTE Issue Nast eSA To deliver a data-preprocessing request to the

netw an ar U eSAU. After a user enables the application data
ork applica Serv subscription function (LTE VIP analysis) on the
tion er Nastar client, the Nastar issues a data-processing
data command to the eSAU.
subscri
ption
comma
nd

Deliver eSA LTE To deliver a data-preprocessing task to the LTE

a U SAU SAU, requesting the LTE SAU to start the data-
prepro preprocessing task.
cessing
task
(direct)

Upload LTE eSA To upload preprocessed data to the eSAU after

prepro SAU U obtaining the data from LTE SAU to Trace
cessed Server, and preprocessing .
data
(direct)

3. - Issue a Nast eSA To enable the data maintenance function. After

Check data ar U a user enables the data maintenance function on
the query Serv the Nastar client, the Nastar checks whether the
integri comma er analysis data is ready on the eSAU.
ty of nd
analys
is data Return eSA Nasta To return data integrity check results to the
data U r Nastar server and display the results on the
query Serve Nastar client.
results r

4. - Issue a Nast eSA To deliver a task execution request to the eSAU.

Create task ar U After a user creates an analysis task on the Nastar
and executi Serv client, the Nastar server issues a task execution
execut on er command to the eSAU, requesting the eSAU to
e an comma aggregate data.
analys nd
is task
Upload eSA Nasta To aggregate the data reported by SAUs,
data U r generate data analysis results, and upload the
analysi Serve data analysis results to the Nastar server.
s r
results

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 578

User Scen Proce Sour Dest Purpose

Oper e dure ce inati
ation on

5.Vie - Displa - Nasta To display analysis results on the Nastar client.

w y r
analys analysi Serve
is s r
results results

Technical Specifications for VIP Analysis

This section describes the technical specifications, including the analysis ability and the range
of analysis time.

Item Service Specifications

Execution type One-time or periodic task

Network scale for one ≤ Maximum management capacity of the Nastar

analysis task

Number of subscribers ≤ 30,000 VIP subscribers (when aggregation analysis and in-
allowed in one analysis depth analysis are supported)
task GSM or LTE VIP analysis supports the all-signaling analysis of
a maximum of 500 important VIP subscribers. UMTS VIP
analysis supports the all-signaling analysis of a maximum of 100
important VIP subscribers when BSC6900 V600R013C00 or later
is used, and supports the all-signaling analysis of a maximum of
500 important VIP subscribers when BSC6900 V600R016C00 or
later is used. PS Core VIP analysis does not support all-signaling
analysis.

Number of allowed l ≤ 300 one-time tasks (for all RATs)

analysis tasks l ≤ 60 periodic tasks (for all RATs)
NOTE
The Nastar provides basic licenses for the following six RATs: GSM,
UMTS, LTE FDD, LTE TDD, and PS Core. The number of supported
one-time VIP analysis tasks and that of supported periodic VIP analysis
tasks are added accumulatively along with the loading of these basic
licenses. The basic license for each RAT supports 50 one-time VIP
analysis tasks and 10 periodic VIP analysis tasks.

Time range for data in l 7 days (one-time task)

one analysis task l 30 days (periodic task)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 579

Item Service Specifications

Duration of one analysis l GSM: ≤ 75 minutes

task l UMTS: ≤ 90 minutes
l LTE: ≤10 minutes
l PS Core: ≤ 15 minutes

Default duration for l GSM: 30 days

storing analysis data l UMTS: 30 days
l LTE: 30 days
l PS Core: 30 days

Maximum duration for l GSM: 30 days

storing analysis data l UMTS: 30 days
l LTE: 30 days
l PS Core: 30 days

3.9.2 Preparations for VIP Analysis

Before running a VIP analysis task, you must check and prepare the basic information to ensure
that the VIP analysis task can be performed successfully. You must read this section before
performing VIP analysis.

Before running a VIP analysis task, you must check and prepare the following information:
l Checking the License Information and User Rights
l Preparing Basic Data
l Checking the Data Source Environment

Checking the License Information and User Rights

Check that you have loaded a valid license for VIP analysis to the Nastar system, and the login
users have had the related rights. For details, see Table 3-28.

Before analyzing, prepare the following basic data described in Table 3-29 for performing the
task successfully.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 583

Table 3-29 Required basic data of VIP analysis

Data Function Operation

Type

Config The configuration data of If the OSS information has been already configured, the
uratio the NE controlling the Nastar automatically and periodically collects and
n Data analysis cell allows the imports the configuration data after the OSS and NE
(Mand Nastar to correctly obtain information is configured. You can also manually
atory) detailed call data from the collect the configuration data before the specified time
network and analyze cell period starts. After the configuration data is imported,
information in MR you can choose Maintenance > Data Maintenance
reports and information Management to check whether the configuration data
about the following cells: is available in the Nastar database. For detailed
cells to which subscribers information about collecting, importing, and checking,
have gained access, cells see 2.5.2 Checking the Integrity of Configuration
which subscribers have Data.
released, and cells to After the configuration data has been successfully
which subscribers have imported, you are advised to check the validity of the
handed over. configuration data. The purpose is to avoid expiration
NOTE of configuration data due to network adjustment.
If you only perform the PS Expired configuration data may cause incorrect cell
Core VIP analysis, you do
information in the analysis result. For detailed
not need the configuration
data. operations, see Checking Engineering Parameters
and Configuration Data.

VIP VIP information includes For details, see 2.5.6 Managing VIP Groups or VIP
Infor VIP user and IMSI Users (VIP Analysis).
matio information. Before NOTE
n subscribing to VIP The Nastar provides sufficient protection for service data used
(Mand analysis data, create a by this function, such as IMSI and IMEI information, to ensure
atory) VIP group so that you can personal data security. For details about the service data and
protection policies, seeDescriptions > Nastar Security
perform analysis on and
Description > Application Security > Protecting Private
ensure the service quality Subscriber Data.
of multiple VIP users in
The Nastar provides an anonymization mechanism for
the VIP group. processing personal data, such as the IMSI, IMEI, MSISDN,
and IMEISV. After this mechanism is used, the Nastar no
longer allows you to enter the plaintext IMSI and MSISDN.
In this situation, you need to contact telecom operators to
obtain the encrypted IMSI. The Nastar does not support the
encrypted MSISDN. Telecom operators can contact the
Huawei technical support engineers to visit http://
support.huawei.com and choose Support > Software >
Global Service > Managing Customer Experience Service-
SmartCare > Network Optimization Service > GENEX
Mobile Manager > HMACUtil.
You have checked whether the subscriber identity
anonymization switch or the encryption key is changed. If the
subscriber identity anonymization switch or the encryption
key is changed, see 2.12.3 Troubleshooting Problems
Caused by Change of the Subscriber Identity
Anonymization Switch or the Encryption Key.

This section describes the process of VIP analysis and each procedure in the process.

This section includes the following information:

l Prerequisites
l Procedure
l Subscription Task Parameters
l Analysis Task Parameters

Prerequisites
You have finished the preparation of VIP analysis, such as checking the operation rights,
preparing the basic data, and so on. For details, see 3.9.2 Preparations for VIP Analysis.

Procedure
Figure 3-42 shows the analysis process.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 588

Figure 3-42 Analysis process

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 589

Table 3-31 Description of VIP analysis procedures

No. Procedur Description Reference

Check Navigation path: Choose Maintenance > Data 2.7

whether Maintenance Management Checking
analysis Procedure: the
data is Integrity
integrated 1. Choose Data Type > User Assurance > *** VIP of Analysis
Analysis Data. Data
*** indicates the network type.
2. (Optional) Specify a period for querying data
integrity.
3. Select the NEs and VIP groups for which the data
integrity needs to be queried.
4. Click Query.
The query results are displayed in the right pane of
the window.
l If analysis data exists, perform (3) to create an
analysis task.
l If the analysis data does not exist, contact Huawei
technical support.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 593

No. Procedur Description Reference

e for
Detailed
Operatio
ns

(3) Create an Navigation path: Choose Theme Function > User l For
analysis Assurance > VIP Analysis in the navigation tree of the details,
task Analysis Task Management window. see 2.8
Procedure: Creatin
g an
1. Double-click the VIP Analysis node. Analysi
2. Set the task name and task remarks. Click Next. s Task.
3. On the Analysis Type tab page, set the net type and l For
the data types. details
4. On the Select NE(s) tab page, select a NE. about
the
5. On the VIP Group tab page, select the VIP groups
paramet
to be analyzed.
ers, see
6. On the Result Threshold tab page, set the abnormal Analysi
threshold of each KPI. s Task
7. On the Process Threshold tab page, set the abnormal Param
threshold of each KPI. Click Next. eters.
8. Choose the task type, and set the analysis time l For
segment. The Nastar will obtain the relevant analysis details
data in the time period. Click Next. about
NOTE Sendin
To obtain accurate subscriber information, you are advised g
to set Execute on to 1 hour. Analysi
9. Optional: On the Sending Analysis Reports s
Setting tab page, set the values of multiple Report
parameters for automatically sending an analysis s
report through email. Setting,
see
10.Click Finish. 2.5.9
Setting
a
Mailbo
x and
Addres
s List
for
Sendin
g
Analysi
s
Report
s
(Optio
nal)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 594

(5) Export Navigation path: Click the icon on the toolbar in the l For
analysis upper left part of each analysis results window. details,
reports Procedure: see 2.11
Exporti
1. Click the export icon on the button area. ng
2. Specify the export path and export content. Analysi
3. Click Save. s
Report
s.
l For
details
on the
descript
ion of
the
window
for
showin
g
analysis
results,
see
Interfa
ce
Descrip
tion:
VIP
Analysi
s/In-
Depth
Analysi
s/
Geogra
phic
Display
.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 597

LTE Periodic MR Period Setting Parameters

Parameter Description

Periodic MR Specify the measurement report period for periodic events. The value of this
Period parameter can be 1024(ms), 2048(ms), 5120(ms), 10240(ms), 1(min), or
6(min). The default value is 5120(ms).

Number of Specify the number of sampled subscribers in periodic MRs. A larger

Sampled Users number of sampled subscribers indicates a higher service support capability.
The value of this parameter ranges from 0 to 400. 0 indicates that all
subscribers are sampled. The default value of this parameter is 0.
l In versions earlier than LTE3900 V100R008C00SPC260, the value of
this parameter is set to 10, which cannot be changed.
l In LTE3900 V100R008C00SPC260 and later versions, the default value
of this parameter on the eNodeB side is 10, which can be changed. The
value of this parameter cannot be changed through the Nastar. To change
the value of this parameter, you need to manually issue the MOD
ENBRSVDPARA command to change the value of reserved parameter
16 on the eNodeB side.
l In LTE3900 V100R009C00 and later versions, the default value of this
parameter on the eNodeB side is 10, which can be changed through the
Nastar.

Number of Specify the number of MRs times in periodic.

Times MRs l The value of this parameter can be 16, Unbounded.
Are Reported
l The default value is 16.

Subscription Task Parameters

Basic Subscription

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 598

Netwo Parameter Description

GSM VIP Switch for enabling or disabling the reporting of CS CHR data. You
Analysis can retain the default state of the switch.
Data (CHR-
CS) You can click to set the following advanced parameters:
l Service: specifies the service types for which CS CHR data is
to be reported. The service types include call, short message
service (SMS), and location update (LU). You can select all or
none of the service types or retain the existing settings.
l Error: specifies the types of information contained in reported
CS CHR data. If you select All, all CS CHR data containing
normal and abnormal service procedures is reported.
l Event Block: specifies that GSM does not support event blocks.
l All Signaling: specifies the types of all signaling messages
contained in reported CS CHR data. For details, see the SET
GCSCHRCTRL command in the related NE product
documentation. You can select all or none of the types or retain
the existing settings.
l HQI Threshold: specifies the method of calculating the HQI
threshold during CS CHR tracing. For details, see the SET
BSCEXSOFTPARA command in the related NE product
documentation. You can set this parameter to a value ranging
from 0 to 6 or retain the existing settings.
NOTE
HQI Threshold applies only to BSC6900 V900R015C00 (and later
versions) and BSC6910 V100R015C00 (and later versions).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 599

Netwo Parameter Description

PS Core VIP Switch for enabling or disabling the reporting of SGSN/MME CHR
Analysis data. You can retain the default state of the switch.
Data
(SGSN/ You can click to set the following advanced parameters:
MME- l Error Type: specifies the types of reported information. If you
CHR) select All, all normal and abnormal service procedures are
reported through CHR data.
l GERAN Procedure Type: specifies the types of reported
GERAN signaling messages. For details, see the SET
CHRCFG command in the related NE product documentation.
You can select all or none of the types or retain the existing
settings.
l UTRAN Procedure Type: specifies the types of reported
UTRAN signaling messages. For details, see the SET
CHRCFG command in the related NE product documentation.
You can select all or none of the types or retain the existing
settings.
l ERAN Procedure Type: specifies the types of reported ERAN
signaling messages. For details, see the SET CHRCFG
command in the related NE product documentation. You can
select all or none of the types or retain the existing settings.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 603

Application Subscription

Netwo Level Parameter Description

GSM Group VIP Group VIP groups, CS NEs, and PS NEs to be analyzed.
Level GSM CS NE
List
GSM PS NE
List

UTMS Group Open VIP VIP functions to be analyzed.

Level Speciality

VIP Group VIP groups and NEs to be analyzed.

NE List

LTE Group VIP Group VIP groups and NEs to be analyzed.

FDD/ Level NE List
LTE
TDD User Level eNodeB eNodeB interfaces to be analyzed.
Interface
Select

IMSI International mobile subscriber identify (IMSI)

information of VIP subscribers.

Select Whether a specified VIP subscriber is selected.

Trace Reference number for tracing a specified VIP

Reference No. subscriber, which is issued by the HSS.

VIP Group VIP group to which a specified VIP subscriber

belongs.

HSS Name Name of the HSS serving a specified VIP

subscriber, to which a VIP data subscription task is
to be delivered.

PS Group VIP Group VIP groups and NEs to be analyzed.

Core Level NE List

Analysis Task Parameters

Basic task information

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 604

Parameter Description

Task Name Name of an analysis task.

Value range:
l The name contains a maximum of 60 characters.
l The name is not allowed to contain any of the following characters: `
~!@#$%^&*()+{}[]\/|;':,.?<>"
l Do not use special characters entered by pressing Tab or Enter.
l The name is unique and case-sensitive and cannot be empty.
l Task Name must be named in Chinese or English. Otherwise, the
function of distributing analysis results by emails is unavailable.

Task Type Type of an analysis task to be created.

Remarks Description of the task.

Value range: The name contains a maximum of 200 characters.

Parameter information

Parameter Description

Analysis Type Analysis Set the analysis type:

Scene l Only support the data on the RAN side
l Only support the data on the PS Core side, that is on
CN side
l Support the data both on the RAN side and PS Core
side

Access Set the RAT for an NE. The system supports the following
Network RATs: GSM, UMTS, LTE FDD, LTE TDD.
Type

Data Type 1 Both access methods can be chosen.

Set the data type on the RAN side.
l RAN CS Data Access: Analyzes the CS service based
on the CS-related data on the RAN side. The LTE
network does not involve this parameter.
l RAN CS Data Access: Analyzes the PS service based
on the PS-related data on the RAN side.
Both access methods can be chosen.
NOTE
If you set the analysis scene to PS Core, you do not need to set
the data type, because it only supports the PS data on the PS Core.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 605

Parameter Description

Data Type 2 The system supports the following data on the CS domain
and the PS domain:
Control Plane: analyze the service based on the control
plane data on the RAN side and the CN side.

Select NEs RAN NE Click Select to select an NE.

VIP Group Select Select the VIP groups to be analyzed in the check box.
NOTE
To ensure the Nastar analysis performance, you are advised to
select the VIP groups that the total number of members of the
selected VIP groups is not more than 2000 when you create an
VIP analysis task.

Group Name Indicates the name of a VIP group.

Members Indicates the number of members in the VIP group.

Description Indicates the description of a VIP group.

Updated Indicates the last time the VIP group information is

Date updated.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 606

Parameter Description

Result Network Indicates the RAT of a VIP group. NOTE

Threshold Use the result
Domain Indicates the domain of an NE. counter of
Domains include signaling plane-CS, Short Calls
(Calling
signaling plane-PS, signaling plane-
Party) in VIP
integration. analysis results
as an example
Service Type l When only analyzing the RAN data, to describe the
or Flow Type the parameter is displayed as Service differences
Type that indicates the service type between the
or Service/ of the KPIs, such as NET, Call, and result
Flow Type so on. threshold and
the process
l When only analyzing the PS Core threshold.
data, the parameter is displayed as Result
Flow Type that indicates the flow threshold:
type of the KPIs, such as SGSN Engineers can
procedure, MME procedure, and so set the result
threshold of
on. the Short
l When analyzing the RAN data and Calls (Calling
PS Core data, the parameter is Party) counter
and detect VIP
displayed as Service/Flow Type that
subscribers
indicates the service type or flow that have more
type of the KPIs. short calls.
Process
Indicator Indicates the name of a KPI indicator.
threshold:
Name The indicators are displayed on the Engineers need
analysis result window. to set the
process
Criterion Indicates the relationship between the threshold for
KPI value and KPI abnormal threshold. defining a
short call based
Threshold Indicates the abnormal threshold of a on the
KPI. preceding
analysis result
In the analysis report of the counter. For
corresponding task, if the KPI value of example, If the
a subscriber reaches the threshold, this Service
KPI is considered as a problematic KPI Duration
or deteriorating KPI. The abnormal (Calling
KPIs will be colored yellow in the Party) of one
call is shorter
analysis results. than the Short
Click the unit and enter the KPI Call
abnormal threshold. This parameter can Threshold
be empty. That is, no threshold value is (Calling
Party), the call
provided. is called a short
call (calling
Process Network Indicates the RAT of a VIP group.
party).
Threshold

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 607

Parameter Description

Domain Indicates the domain of an NE.

Domains include signaling plane-CS,
signaling plane-PS, signaling plane-
integration.

Service Type l When only analyzing the RAN data,

or Flow Type the parameter is displayed as Service
Type that indicates the service type
or Service/ of the KPIs, such as NET, Call, and
Flow Type so on.
l When only analyzing the PS Core
data, the parameter is displayed as
Flow Type that indicates the flow
type of the KPIs, such as SGSN
procedure, MME procedure, and so
on.
l When analyzing the RAN data and
PS Core data, the parameter is
displayed as Service/Flow Type that
indicates the service type or flow
type of the KPIs.

Indicator Indicates the name of a KPI process

Name threshold. The threshold is based on the
process of obtaining the final values of
KPI indicators.

Criterion Indicates the relationship between the

KPI value and KPI abnormal threshold.

Threshold Indicates the abnormal threshold of a

KPI.
In the analysis report of the
corresponding task, if the KPI value of
a subscriber reaches the threshold, this
KPI is considered as a problematic KPI
or deteriorating KPI.
Click the unit and enter the KPI
abnormal threshold. This parameter can
be empty. That is, no threshold value is
provided.

Time information of one-time task

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 608

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

Delay If you do not select this parameter, the system executes the task
immediately.
If you select this parameter, the system executes the task at the time
specified in Execute on.

Execute on Time when a task is executed.

Time information of periodic task

Param Description Note

eter

Start Date for starting the task. Start Time of a periodic task = Next time
time point + Delay by (hours)
Time period of a periodic task: [Start Time of
Period Interval between periodic tasks.
a periodic task - Period, Start Time of a
Value range: 30 Minutes, 1 to periodic task]
24 Hours, 1 to 7 Days, and 1
The Next time point is related to Start time and
Week.
Period.
Repeat Number of times that a periodic l If you set Period to 30 Minutes, the Next
times task is executed. If you set this time point is 00 seconds of the next 30
parameter to 0, the task is minutes starting from the current server time
executed all the time. (minute-level). For example, if the current
Value range: 0 to 9999 server time is 01:10, the Next time point is
31:00 starting from Start time.
l If you set Period to N Hour, the Next time
point is 00 minutes:00 seconds of the next N
hour(s) starting from the current server time
(hour-level). For example, if the current
server time is 14:01:10, the period is 3
Hours, and the Next time point is 17:00:00
starting from Start time.
l If you set Period to N Day, the Next time
point is 00 hours:00 minutes:00 seconds of
the (N + 1) day starting from Start time.
l If you set Period to N Week, the Next time
point is 00 hours:00 minutes:00 seconds of
the (7*N + 1) day starting from Start time.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 609

Param Description Note

eter

Delay Time delayed for executing a NOTE

by task. l If the start time of a periodic task is later than
(hours) the current server time, the Nastar automatically
Value range: 0 to 24. Unit: hour. executes the task at the start time.
NOTE Example: If the current server time is 01/01/2013
If DST starts before a task is 14:00:00, Start time is 01/02/2013, Period is 1
executed, the execution delay will Day, and Delay by (hours) is 3, the Nastar
be automatically updated to ensure automatically executes the task at 01/03/2013
that the task can be executed at the 03:00:00.
specified time. For example, if you l If the start time of a periodic task is earlier than
set Start time at 01:00 on a day, the current server time, the Nastar immediately
and the value of Delay by executes the task.
(hours) for the task was set to 3 Example: The current server time is 01/02/2013
hours, the task was scheduled to be 14:00:00, Start time is 01/01/2013, Period is 1
executed at 04:00. However, DST Day, and Delay by (hours) is 3, the Nastar
started before 02:00 on that day, immediately executes the task.
and 02:00 was changed to 03:00.
As a result, the value of Delay by
(hours) for the task was
automatically updated to 4 hours
so that the task was executed at
05:00 (equal to 04:00 before DST
started).

Whole If this parameter is set, it works

day the same as All Busy Time
under Busy hours.
You are not allowed to set this
parameter.

Busy If you select this parameter, the

hours system analyzes the data
generated within several
periods of a day. You can select
a maximum of four periods.
Several continuous time points
can be selected in each period.
l All Busy: defines a whole
day as busy time.
l All Not Busy: defines no
busy time.
l Invert Selection: defines
inverted time as the busy
time.

Parameters about sending the analysis report

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 610

Parameter Description

Sendin Automatically After you select this option, the system delivers the exported VIP
g send analysis analysis result file to the mailboxes of the specified users.
Analysi reports via
s emails
Reports
Setting Target email Indicates the recipient's mailbox. Click Select. In the displayed
Email dialog box, set user mailboxes.

Email subject Indicates the title of an email.

Users are not allowed to change the value of this parameter.

Email Indicates the type of the report being sent.

contents l Result Type: Exception, Only delivers analysis results with
abnormal indicators. All, Delivers analysis results with all
indicators.
l Service Type: Only delivers analysis results with selected
service type, such as RAN PS.
l Report Type: Only delivers analysis results with selected
report type, such as user level analysis results, in-depth
analysis result.

Attachment Displays the threshold of an attachment. The threshold cannot be

modified. It only can be configured in the Maintenance > Email
Settings function.
l If the actual attachment is not larger than the configured
threshold, you can obtain the analysis report by the email
directly.
l If the actual attachment is larger than the configured threshold,
the analysis report will be divided to multiple files based on
the attachment threshold, and the files will be sent in multiple
mails.

3.9.4 Reference for VIP Analysis Interface

The section describes the relevant interface description of the VIP summary analysis results,
VIP deep analysis results, VIP trend analysis results, and VIP geographic observation results.

Interface Description: VIP Analysis/In-Depth Analysis/Geographic Display

This section describes the interface for VIP analysis. Before performing relevant operations,
familiarize yourself with the functions of each area on the interface.

NOTE

l VIP analysis and in-depth analysis are supported by the GSM, UMTS, LTE, and PS Core network.
l VIP geographic display is supported by the GSM, UMTS, and LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 611

Opening the Window

l Open the interface that displays the results of VIP analysis (use either of the following
methods):
– Select an executed VIP analysis task, and double-click a successful analysis result of
the task in the Task Result area.
– Select an executed VIP analysis task, and double-click a successful analysis result of
the task in the Task Result area.Right-click a successful analysis result of a task and
choose View Analysis Result from the shortcut menu.
l Open the interface that displays the results of VIP analysis (in-depth):
On the User Level Results tab page of VIP analysis result interface,

– If the table displays the counter overview information by group, click in the front

of each row, or click the counter value underlined in red (for example, ) directly.
The tab page for the counter overview information by user is displayed. You can view
the counter value for each user in the group.

– In such a case, click in the front of each row, or click the counter value underlined

in red (for example, ) directly. In-depth analysis of selected counters is started. For
details, see 3.10.4 Reference for Complaint Analysis Support Interface.
l Open the geographic display interface:

On the button area of VIP analysis result interface, click .

Main Window
Figure 3-43 shows the VIP analysis results window.

Figure 3-43 VIP analysis interface (example for a GSM network)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 612

No. Parameter Description

1 Button area The buttons provide navigation paths to the following three functions.

l : Exports VIP analysis summary reports.

1. Click , a dialog box that provides personal data disclaimer will

be displayed, reminding you of the illegality if you possess the
personal data. Click OK.
2. On the displayed dialog box, set the result (Exception or ALL),
service type, and report type. Click Next.
3. Set the report save path and the folder name, click Save to export
the analysis reports.
All the exported reports are contained in a folder named VIP
Analysis_Name of analysis task_YYYYMMDDHHMMSS by
default.
VIP analysis reports are named following the format of Number
Report type_Report categories 1 + Report categories 2 +
Number_Service type.csv. Report categories 1 indicates the
analysis object, such as the group and user of the user-level
analysis. Report categories 2 indicates the analysis result
categories, such as counter overview information table (KPI) and
active cell information table (cell) of the user-level analysis. For
example, 01 User Level Results_groupKPI00_RAN NET.csv
indicates the counter overview information table of the user-level
analysis, according the analysis object is group, and the service
type is RAN NET.

l : Displays the VIP analysis results geographically.

For details, see Geographic Display Interface.

l : Starts VIP trend analysis. Only periodical tasks support trend

analysis. For details, see Interface Description: VIP Trend
Analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 613

No. Parameter Description

2 Analysis Displays analysis results on different tab pages as follows:

result tab l On the User Level Results tab page, you can analyze counter value
page change, active cells, and active servers of specified VIP subscribers
or VIP groups. The system supports in-depth analysis from counter
to detailed records. For details, see User-Level Analysis Tab Page.
l On the Network Level Results: Active Cell tab page, you can analyze
all VIP subscribers' activities of a specified BSC/RNC/eNodeB or
cell. For details, see Network-Level Analysis Tab Page-Active
Cell.
l On the Network Level Results: Active Server tab page, you can
analyze all VIP subscribers' activities of a specified server or
application. It is only supported by the GSM network. For details, see
Network-Level Analysis Tab Page-Active Server of GSM
Network.

User-Level Analysis Tab Page

The VIP analysis results are displayed in charts and tables, as shown in Figure 3-44.

Figure 3-44 VIP analysis interface - user-level analysis (example for a GSM network)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 614

No. Parameter Description

(1) Analysis Set the display mode of counter summary results by VIP subscriber or
object VIP group. Select a VIP analysis object.
selection area l Group

Refers to one or certain selected VIP groups. Counter summary

results of all selected VIP groups are displayed in area 4.
l User
Refers to VIP subscribers in one or certain VIP groups. Counter
summary results of all selected VIP subscribers are displayed in area
4.
NOTE
The content contained in the parenthesis after the VIP group name is the number
of VIP users. You can sort ascending or descending through the menu by right-
clicking.

(2) Service type Select a service type to be viewed.

selection area
NOTE
l The RAN-CS and RAN-PS types cannot be chosen at the same time.
l The supported service type is referred to Reference for VIP Analysis
Parameters (***). *** indicates the network.

(3) Counter set Contains a counter set to be analyzed.

selection area
l The Nastar defines the default counter sets by analysis scenario.
l You can define the counter sets:
1. Right-click a service type (such as RAN-CS), and choose User-
Defined KPI from the shortcut menu.
2. On the User-Defined KPI dialog box, configure the counter set
name, and choose the counters contained in the counter set.
3. Click OK, the new counter set will be displayed under the
service type node.
Right-click the counter set, you can modify or delete it.
NOTE
The supported counter sets are referred to Reference for VIP Analysis
Parameters (***). *** indicates the network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 615

No. Parameter Description

(4) Counter Lists all counter values in different applications for the selected NE
overview object based on the selected counter set.
information
table l The color yellow indicates the abnormal counter that exceeds the
configured threshold. The underlined in red indicates the counter
can be analyzed deeply.
l If the table displays the counter overview information by group,
click in the front of each row, or click the counter value

underlined in red (for example, ) directly. The tab page for the
counter overview information by user is displayed. You can view
the counter value for each user in the group.

l In such a case, click in the front of each row, or click the counter

value underlined in red (for example, ) directly. In-depth

analysis of selected counters is started. For details, see 3.10.4
Reference for Complaint Analysis Support Interface.
NOTE
For combined CHRs, the voice quality problem counters (excluding average
counters) are measured based on the sub-CHRs in OR relationship during VIP
analysis, and the exception cause value for the voice quality problem in the
summary table of in-depth analysis is measured based on the sub-CHRs in AND
relationship. As a result, the VIP analysis results may be inconsistent with the
in-depth analysis results. However, the problem analysis is not affected. For
detailed analysis, see in-depth analysis results.

(5) Active cell Displays active cells of a selected VIP user object.
information
table

(6) Active server Displays active servers of a selected VIP user object. It is only
information supported by the GSM network.
table

Network-Level Analysis Tab Page-Active Cell

The VIP analysis results are displayed in tables. Figure 3-45 shows the interface.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 616

Figure 3-45 VIP analysis interface - active cells (example for a GSM network)

No. Parameter Description

(1) Analysis Set the counter summary results to being displayed by BSC/RNC/
object eNodeB or cell. Select an NE analysis object.
selection area l BSC/RNC/eNodeB

Refers to one or certain selected BSC/RNC/eNodeBs. Counter

summary results of all selected BSC/RNC/eNodeBs are displayed
in area 4.
l Cell
Refers that when you select one or certain BSC/RNC/eNodeBs,
counter summary results of all selected cells under the selected
BSC/RNC/eNodeBs are displayed in area 4.

(2) Service type Select a service type to be viewed.

selection area
NOTE
The RAN-CS and RAN-PS types cannot be chosen at the same time.

(3) Counter set Contains a counter set to be analyzed.

selection area
The Nastar defines a default counter set by analysis scenario.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 617

No. Parameter Description

(4) Counter Lists all counter values in different applications for the selected NE
overview object based on the selected counter set.
information
table

(5) Active VIP Displays VIP subscribers for selected NE objects.

subscriber
information
table

Network-Level Analysis Tab Page-Active Server of GSM Network

The network-level VIP analysis results are displayed in tables. Figure 3-46 shows the interface.

Figure 3-46 VIP analysis interface - active servers

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 618

No. Parameter Description

(1) Analysis object Set the counter summary results to being displayed by server
selection area or port. Select a server to be analyzed.
l Server
Refers to one or certain selected servers. Counter summary
results of all selected servers are displayed in area 4.
NOTE
The value of this parameter is displayed in the following format:
Server IP : Server Name. You need to set Server IP and Server
Name by using the data service server management function when
you create a data service server. If Server IP and Server Name are
not set, no information is displayed following the colon in Server
IP:Server Name.
l Port
Refers that when you select one or certain servers, counter
summary results of all selected ports under the selected
servers are displayed in area 4.

(2) Service type Select a service type to be viewed.

selection area
NOTE
Only the RAN-PS service is supported.

(3) Counter set Contains a counter set to be analyzed.

selection area
The Nastar defines a default counter set by analysis scenario.

(4) Counter overview Lists all counter values in different applications for the selected
information table analysis object based on the selected counter set.

(5) Active VIP Displays VIP subscribers for selected server objects.
subscriber
information table

Geographic Display Interface

Click . The map window (the Geographic Observation window) is displayed as shown in
Figure 3-47.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 619

Figure 3-47 Geographic display interface (example for a LTE network)

No. Feature Description

(1) Button area Navigation path for basic operations in the Geographic Observation
window. For details about the icons, see 2.2.3 Interface
Description: Geographic Observation Results.

(2) Navigation l Site Layer: displays site information. You can set the display
tree in the effect through the shortcut menu. The site information is
Geographic displayed on the condition that the engineering parameters have
Observation been imported to the Nastar database and site information have
window been loaded in map window.
NOTE
If you need to delete all sites in a network system, click Remove through
the layer management function.
l VIP Analysis: Node for the VIP analysis theme.
– A level-2 node under the node indicates a task name. A
level-3 node under the node indicates a KPI, such as active
cell KPI.
– If multiple VIP analysis result windows are open, only one
of the windows can be displayed on the Geographic
Observation window simultaneously.
– If an analysis result window is closed, the node for the
window in the navigation tree is deleted accordingly. In
addition, the rendered layer of the corresponding theme is
deleted.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 620

No. Feature Description

(3) Geographic Analysis results are displayed as icons in different colors.

observation
area

(4) Grid detail This area is empty for VIP analysis.

area

(5) Legend area This area is not displayed by default. It is displayed only after you
click the icon in the button area. After you click the icon, this
area displays the legend information about the icons in area 3.

(6) Information l In the geographic observation area, select an icon of a cell and
area the details about this cell is displayed in the information area.
l If the engineering parameters of a cell are not imported, the
system displays a message in this area.

Interface Description: VIP Trend Analysis

This section describes the interface for VIP trend analysis. Before performing relevant
operations, familiarize yourself with the functions of each area on the interface.

NOTE

VIP trend analysis is supported by the GSM, UMTS, LTE, and PS Core network.

Opening the Window

You can enter VIP analysis interface in two modes.
l Select an executed VIP periodical analysis task. Right-click a successful analysis result of
the task in the Task Result area, and choose Trend Analysis from the shortcut menu.
l Select an executed VIP periodical analysis task. Right-click a successful analysis result of
the task in the Task Result area, double-click a successful analysis result. A window is

displayed. On the toolbar, click to start the trend analysis.

Main Window
The function analyzes the trend of periodical analysis results. Based on the analysis results,
network optimization engineers can sum up the changes of KPIs, locate and analyze main
problems during VIP KPI assurance and optimization. Figure 3-48 shows the VIP trend analysis
results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 621

Figure 3-48 VIP analysis interface (example for a GSM network)

No. Parameter Description

1 Button area Provides buttons for exporting VIP trend analysis information.

1. Click .
2. After checking the disclaimer, set users for export in the Select
User dialog box. Click Next.
3. Set counters for export. Click Next.
4. Specify a save path.
Engineers can only specify the save path and folder name for exported
reports. The file name is fixed. The default naming convention is VIP
Trend Analysis_Analysis Task Name_YYYYMMDDHHMMSS.
Information about one subscriber is exported to one file.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 622

No. Parameter Description

2 Area for Selects a VIP user whose trend analysis is to be analyzed.

setting
NOTE
filtering
criteria The display format of the user is IMSI of the user:User alias or MSISDN of the
user(MSISDN):User alias.

The options of the user selection are as follows:

l Method one: Select the VIP subscribers and VIP group objects in
current periodical VIP tasks.
No configuration is needed.
l Method two: Select a VIP subscriber object that meets the filtering
criteria.
Analyze VIP subscribers in a selected VIP group that meet filtering
criteria, not all subscribers.

Use the following example to explain method two.

1. Click behind the Filter Subscribers text box.

2. Click Add. The Add Filter Criterion dialog box is displayed.
3. Set Criterion Name.
4. On the Object tab page, click Object.
5. In the Select Counter dialog box, select the needed option to be
configured. Click OK.
For example, select Access Requests (Intra-RAT) and Abnormal
Releases (Intra-RAT)
6. On the Object tab page, select a counter option and set its value range.
For example, set Access Requests (Intra-RAT) to more than 10. Set
Abnormal Releases (Intra-RAT) to more than two.
7. In the lower pane of the Object tab page, set the relationships between
counter options to Or or And.
For example, set the relationship between Access Requests (Intra-
RAT) > 10 and Abnormal Releases (Intra-RAT) > 2 to And.
8. On the Period tab page, set the time range that meets the counter filter
criteria.
For example, select N continuous periods, and set N to 3.
9. Click OK.
NOTE
This filter criteria setting applies only to the current task. After the task is closed,
the filter criteria setting restores to the default value.

3 Service Select the service type whose trend analysis is to be viewed. Only one
type service type can be selected each time.
selection
area

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 623

No. Parameter Description

4 Counter Select the counter type whose trend analysis is to be viewed. One or more
type counter types can be selected.
selection
area

5 Trend Displays the trend analysis charts of multiple counters for a selected
analysis subscriber during a time segment.
chart l Displays user objects, period dimension, and time range information
in the upper part of the tab page.
l Displays the counter name at the top of each chart.
l Displays time information for a maximum of 20 periods on the
horizontal coordinate. The time granularity is set to week.
NOTE
You can choose to view or hide horizontal coordinates by selecting or
deselecting Display Horizontal Coordinate. The horizontal coordinates in all
trend analysis charts are the same. Therefore, you can view more analysis
results in the same window if you hide the horizontal coordinates.
l Displays the actual counter value range on the vertical coordinate.
l Displays the detailed time and counter value if you click a point on
the trend chart.
l You can right-click a chart to maximize and minimize the window,
save data.
l You can right-click a data point in a trend analysis chart and choose
Drill Down Results from the shortcut menu to switch to the interface
that displays the results of the VIP analysis task corresponding to this
data point and to view detailed analysis results. For details about the
interface description, see Interface Description: VIP Analysis/In-
Depth Analysis/Geographic Display.
l For a data point showing an abnormal counter (such as a failure-
related analysis counter), you can right-click this data point in the
trend analysis chart and choose In-depth Analysis from the shortcut
menu to switch to the interface that displays the results of the
complaint analysis support task corresponding to this data point and
to view detailed CDR information about this counter. For details about
the interface description, see 3.10.4 Reference for Complaint
Analysis Support Interface.

6 Trend Displays detailed counter information during each period for the selected
analysis users. The counter information in this table is displayed synchronously
table with the change of the trend chart.

Parameters in the table are start time, counter 1, counter 2, ..., and counter
N.
NOTE
The system displays only the analysis results of the latest 20 periods by default.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 624

No. Parameter Description

7 Area for The trend analysis modes are as follows:

setting l Auto Refresh Mode: In this mode, The trend data is displayed based
trend on a periodical VIP analysis task. The trend chart refreshes itself
analysis automatically upon a VIP analysis task for one period is completed.
mode
l Specified Period Mode: In this mode, the displayed trend data is
displayed based on the period specified by a VIP analysis task. When
a VIP analysis task for one period is completed, the trend chart does
not refresh itself and only displays the trend for the specified period.

3.9.5 Reference for VIP Analysis Parameters (GSM)

This section describes the parameters for GSM VIP analysis.

Parameters for Viewing GSM VIP Analysis - Common Results

This section describes the parameters for querying GSM VIP analysis common results. You can
refer to the description when querying GSM VIP analysis common results.

Common
Paramet Ran Unit Description Supported
er ge NE
Version

Deep N/A N/A When the dimension is Group, this parameter is BSC6900
Analysis used to switch from the analysis results of a VIP V900R014
group to the analysis results of the VIP C00 (or
subscribers in this group. later) or
When the dimension is User, this parameter is BSC6910
used to switch from the analysis results of V100R014
counters to the analysis results of calls. C00 (or
later)

Group N/A N/A Name of a VIP group. BSC6900

Name V900R014
C00 (or
later) or
BSC6910
V100R014
C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 625

Paramet Ran Unit Description Supported

er ge NE
Version

User ID N/A N/A ID of a VIP subscriber. Query the ID of a VIP BSC6900

subscriber using VIP group management. V900R014
C00 (or
later) or
BSC6910
V100R014
C00 (or
later)

Alias N/A N/A Name of a VIP alias. Query the alias of a VIP BSC6900
subscriber using VIP group management. V900R014
C00 (or
later) or
BSC6910
V100R014
C00 (or
later)

IMSI N/A N/A IMSI information of a subscriber. BSC6900

Note: Only when you have the "User Identity" V900R014
right, you can view the IMSI information. C00 (or
later) or
BSC6910
V100R014
C00 (or
later)

IMEI- 0000 N/A International mobile equipment identity-type BSC6900

TAC 0000 allocation code (IMEI-TAC) of the terminal V900R014
- used by a VIP subscriber. C00 (or
9999 later) or
9999 BSC6910
V100R014
C00 (or
later)

Terminal N/A N/A Model of the terminal used by a VIP subscriber. BSC6900
Model Obtain the terminal type in the Terminal Type V900R014
Management window based on the IMEI-TAC C00 (or
of the terminal used by the VIP subscriber. later) or
BSC6910
V100R014
C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 626

Paramet Ran Unit Description Supported

er ge NE
Version

Service N/A N/A Service type for a following counter. BSC6900

Type V900R014
C00 (or
later) or
BSC6910
V100R014
C00 (or
later)

Number [0, Numb Number of abnormal counters in all counter sets BSC6900
of +∞) er determined based on the result thresholds set V900R014
Abnormal when engineers create a task. C00 (or
KPIs later) or
BSC6910
V100R014
C00 (or
later)

Total [0, Numb Indicates the number of records generated for all BSC6900
Reports +∞) er service types during the network access of a V900R014
subscriber. C00 (or
later) or
BSC6910
V100R014
C00 (or
later)

Parameters for Viewing GSM VIP Analysis - RAN CS Results

This section describes the parameters for querying GSM VIP Analysis - RAN CS results. You
can refer to the description when querying GSM VIP analysis - RAN CS results.

RAN-CS/NET/Accessibility Evaluation
Para Ran Unit Description Supported NE
meter ge Version

Acces [0, Number Number of access requests that a VIP BSC6900

s +∞) subscriber initiates to access the network V900R014C00 (or
Reque from a cell in the current system. later) or BSC6910
sts V100R014C00 (or
(Intra- later)
RAT)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 627

Para Ran Unit Description Supported NE

meter ge Version

Acces [0, Number Number of access failures that a VIP BSC6900

s +∞) subscriber experiences during the process V900R014C00 (or
Failur of accessing the network from a cell in the later) or BSC6910
es current system. V100R014C00 (or
(Intra- later)
RAT)

Acces [0, Number Number of access requests that a VIP BSC6900

s +∞) subscriber initiates to access the network V900R014C00 (or
Reque from a cell in another system. later) or BSC6910
sts V100R014C00 (or
(Inter- later)
RAT)

Acces [0, Number Number of access failures that a VIP BSC6900

s +∞) subscriber experiences during the process V900R014C00 (or
Failur of accessing the network from a cell in later) or BSC6910
es another system. V100R014C00 (or
(Inter- later)
RAT)

Avera [0,63 N/A Average TA value when a VIP subscriber BSC6900

ge TA ] initiates channel setup requests for V900R014C00 (or
on accessing the network. later) or BSC6910
Acces V100R014C00 (or
s later)

Abnor [0, Number Number of times that the TA value is BSC6900

mal +∞) abnormal when a VIP subscriber initiates V900R014C00 (or
TAs channel setup requests for accessing the later) or BSC6910
on network. V100R014C00 (or
Acces Set the exception threshold when you later)
s create a task.

Ratio [0.00, % Proportion of abnormal TA values when BSC6900

of 100.0 a VIP subscriber initiates channel setup V900R014C00 (or
Abnor 0] requests for accessing the network. later) or BSC6910
mal Proportion of abnormal TA values = V100R014C00 (or
TAs Number of abnormal TA values/Number later)
on of all TA values x 100%.
Acces
s

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 628

Para Ran Unit Description Supported NE

meter ge Version

Avera [-110 dBm Average RACH level when a VIP BSC6900

ge ,-47] subscriber initiates channel setup V900R014C00 (or
RAC requests for accessing the network. later) or BSC6910
H V100R014C00 (or
Level later)
on
Acces
s

Abnor [0, Number Number of times that the RACH level is BSC6900
mal +∞) abnormal when a VIP subscriber initiates V900R014C00 (or
RAC channel setup requests for accessing the later) or BSC6910
H network. V100R014C00 (or
Levels Set the exception threshold when you later)
on create a task.
Acces
s

Ratio [0.00, % Proportion of abnormal RACH levels BSC6900

of 100.0 when a VIP subscriber initiates channel V900R014C00 (or
Abnor 0] setup requests for accessing the network. later) or BSC6910
mal Proportion of abnormal RACH levels = V100R014C00 (or
RAC Number of abnormal RACH levels/ later)
H Number of all RACH levels x 100%.
Levels
on
Acces
s

RAN-CS/NET/Retainability Evaluation
Para Rang Unit Description Supported
mete e NE Version
r

Relea [0, Numb Number of times that a VIP subscriber releases BSC6900
ses +∞) er all services in the current system. V900R014C
(Intra Number of releases (intra-RAT) = Access 00 (or later)
- requests (intra-RAT) – Access failures (intra- or BSC6910
RAT) RAT) V100R014C
00 (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 629

Para Rang Unit Description Supported

mete e NE Version
r

Abno [0, Numb Number of times that a VIP subscriber BSC6900

rmal +∞) er abnormally releases all services in the current V900R014C
Relea system. The Nastar supports only the Call service. 00 (or later)
ses or BSC6910
(Intra V100R014C
- 00 (or later)
RAT)

Relea [0, Numb Number of times that a VIP subscriber releases BSC6900
ses +∞) er all services in another system. V900R014C
(Inter Number of releases (inter-RAT) = Access 00 (or later)
- requests (inter-RAT) – Access failures (inter- or BSC6910
RAT) RAT) V100R014C
00 (or later)

Abno [0, Numb Number of times that a VIP subscriber BSC6900

rmal +∞) er abnormally releases all services successfully V900R014C
Relea accessed from another system. 00 (or later)
ses This parameter is also referred to as the number or BSC6910
(Inter of times that the service is successfully handed V100R014C
- over from another system and proceeds but the 00 (or later)
RAT) call is abnormally released.

RAN-CS/NET/Mobility Evaluation
Paramet Range Unit Description Supported NE
er Version

Hard [0,+∞) Num Number of hard handover requests that BSC6900

Handover ber a VIP subscriber initiates. V900R014C00 (or
Requests later) or BSC6910
V100R014C00 (or
later)

Hard [0,+∞) Num Number of hard handover failures that BSC6900

Handover ber a VIP subscriber experiences. V900R014C00 (or
Failures later) or BSC6910
V100R014C00 (or
later)

Hard [0,+∞) Num Number of times that a VIP subscriber BSC6900

Handover ber successfully initiates a hard handover. V900R014C00 (or
Success later) or BSC6910
Times V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 630

Paramet Range Unit Description Supported NE

er Version

Inter- [0,+∞) Num Number of times that an outgoing BSC6900

RAT ber inter-RAT handover from a GSM V900R014C00 (or
Outgoing network is triggered during a service. later) or BSC6910
Handover The BSC records the value of the V100R014C00 (or
Requests parameter after it successfully sends later)
the command.

Inter- [0,+∞) Num Number of times that an outgoing BSC6900

RAT ber inter-RAT handover from a GSM V900R014C00 (or
Outgoing network is triggered during a service later) or BSC6910
Handover but the handover fails and the VIP V100R014C00 (or
Failures subscriber then is handed back over to later)
(Normal the GSM network.
Release)

Inter- [0,+∞) Num Number of times that call drops occur BSC6900
RAT ber during an outgoing inter-RAT V900R014C00 (or
Outgoing handover from a GSM network during later) or BSC6910
Handover a service. V100R014C00 (or
Failures later)
(Abnorm
al
Release)

Inter- [0,+∞) Num Number of times that a handover from BSC6900

RAT ber a non-GSM cell to a GSM cell is V900R014C00 (or
Incoming triggered during a service. later) or BSC6910
Handover V100R014C00 (or
Requests later)

Inter- [0,+∞) Num Number of times that a handover from BSC6900

RAT ber a non-GSM cell to a GSM cell fails V900R014C00 (or
Incoming during a service. later) or BSC6910
Handover V100R014C00 (or
Failures later)

RAN-CS/Call/Accessibility Evaluation
Param Ran Unit Description Supported NE
eter ge Version

Total [0, Numb Number of call setup requests that a VIP BSC6900
Call +∞) er subscriber initiates to access the network V900R014C00 (or
Setup and initiate a call. later) or BSC6910
Reques That is, the number of Channel Request V100R014C00 (or
ts messages from a VIP subscriber after the later)
BSC obtains the IMSI correctly.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 631

Param Ran Unit Description Supported NE

eter ge Version

Call [0, Numb Number of call setup failures that a VIP BSC6900
Setup +∞) er subscriber experiences during the process V900R014C00 (or
Failure of accessing the network and initiating a later) or BSC6910
s call. V100R014C00 (or
The call setup process spans from the later)
Channel Request message to the Altering
message.

Abnor [0, Numb Number of times that the call is abnormally BSC6900
mal +∞) er released before being set up when a VIP V900R014C00 (or
Release subscriber accesses the network and later) or BSC6910
Before initiates a call. V100R014C00 (or
Call The process before call setup spans from later)
Compl the Channel Request message to the
etion Connect Acknowledge message.

Call [0, Numb Number of successful call setups when a BSC6900

Setup +∞) er VIP subscriber accesses the network and V900R014C00 (or
Succes initiates a call. later) or BSC6910
s Times The call setup process spans from the V100R014C00 (or
Channel Request message to the Alerting later)
message.

Call [0, Numb Number of successful call completions BSC6900

Compl +∞) er (Alerting) when a VIP subscriber accesses V900R014C00 (or
etion the network and initiates a call. later) or BSC6910
(Alerti The call completion (Alerting) process V100R014C00 (or
ng) spans from the Channel Request message later)
to the Altering message.

Call [0, Numb Number of successful call completions BSC6900

Compl +∞) er (Connect Ack) after a subscriber accesses V900R014C00 (or
etion the network and initiates a call. later) or BSC6910
(Conne The call completion process (Connect Ack) V100R014C00 (or
ct Ack) spans from the Channel Request message later)
to the Connect Acknowledge message.

Call [0.00 % Call completion ratio (Alerting) when a BSC6900

Compl , VIP subscriber accesses the network and V900R014C00 (or
etion 100. initiates a call. later) or BSC6910
Succes 00] Call completion ratio (Alerting) = Number V100R014C00 (or
s Ratio of successful call completions (Alerting)/ later)
(Alerti Number of call setup requests x 100%
ng)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 632

Param Ran Unit Description Supported NE

eter ge Version

Call [0.00 % Call completion ratio (Connect Ack) when BSC6900

Compl , a VIP subscriber accesses the network and V900R014C00 (or
etion 100. initiates a call. later) or BSC6910
Succes 00] Call completion ratio (Connect Ack) = V100R014C00 (or
s Ratio Number of successful call completions/ later)
(Conne Number of call setup requests x 100%
ct Ack)

RAN-CS/Call/Retainability Evaluation
Parame Rang Unit Description Supported NE
ter e Version

Call [0, Num Number of successful call setups when a BSC6900

Setup +∞) ber VIP subscriber accesses the network and V900R014C00 (or
Success initiates a call. later) or BSC6910
Times The call setup process spans from the V100R014C00 (or
Channel Request message to the later)
Alerting message.

Call [0, Num Same as the related counter in RAN/CS/ BSC6900

Complet +∞) ber Call/Accessibility Evaluation. V900R014C00 (or
ion later) or BSC6910
(Connec V100R014C00 (or
t Ack) later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 633

Parame Rang Unit Description Supported NE

ter e Version

Abnorm [0, Num Number of times that the call is BSC6900

al Call +∞) ber abnormally released when a VIP V900R014C00 (or
Releases subscriber accesses the network and later) or BSC6910
initiates a call. V100R014C00 (or
After a successful call setup, any of the later)
following indicates an abnormal call
release:
1. The Disconnect message is called an
abnormal one.
2. The BSS receives the Clear Command
message from the MSC and the
abnormal call release is caused by the
network or the calling (or called) VIP
subscriber.
3. An outgoing inter-BSC handover
fails.
4. An intra-BSC handover fails.
5. The BSC releases the channel
resources abnormally.
6. The MSC releases the channel
resources abnormally.

Abnorm [0.00, % Abnormal call release ratio when a VIP BSC6900

al Call 100.00 subscriber accesses the network and V900R014C00 (or
Ratio ] initiates a call. later) or BSC6910
Abnormal call release ratio = Number of V100R014C00 (or
abnormal call releases/Number of later)
successful call completions (Connect
Ack) x 100%

RAN-CS/Call/Service Evaluation for Delay

Parame Ran Unit Description Supported NE
ter ge Version

Access [0, Numbe Number of times that the access delay BSC6900
Delays +∞) r is overlong upon successful call V900R014C00 (or
(MOC) initiation (mobile-originated call). later) or BSC6910
Access delay = Time when the V100R014C00 (or
Assignment Complete message is later)
generated – Time when the Channel
Request message is generated

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 634

Parame Ran Unit Description Supported NE

ter ge Version

Average [0, Second Average access delay upon successful BSC6900

Access +∞) call initiation (mobile-originated call). V900R014C00 (or
Delay Average access delay = Sum of access later) or BSC6910
(MOC) delays/Number of access delays V100R014C00 (or
later)

Overlon [0, Numbe Number of times that the access delay BSC6900
g Access +∞) r is overlong upon successful call V900R014C00 (or
Delays initiation (mobile-originated call). later) or BSC6910
(MOC) Set the exception threshold when you V100R014C00 (or
create a task. later)

Ratio of [0.00 % Proportion of overlong access delays BSC6900

Overlon , upon successful call initiation (mobile- V900R014C00 (or
g Access 100.0 originated call). later) or BSC6910
Delays 0] Proportion of overlong access delays = V100R014C00 (or
(MOC) Number of overlong access delays/ later)
Number of access delays x 100%

Access [0, Numbe Number of times that the access delay BSC6900
Delays +∞) r is overlong upon successful call V900R014C00 (or
(MTC) initiation (mobile-terminated call). later) or BSC6910
Access delay = Time when the V100R014C00 (or
Assignment Complete message is later)
generated – Time when the Channel
Request message is generated

Average [0, Second Average access delay upon successful BSC6900

Ratio of [0.00 % Proportion of overlong call completion BSC6900

Overlon , (Connect Ack) delays upon successful V900R014C00 (or
g Call 100.0 call initiation (mobile-terminated call). later) or BSC6910
Complet 0] Proportion of overlong call completion V100R014C00 (or
ion delays = Number of overlong call later)
Delays completion delays/Number of call
(Connec completion delays x 100%
t Ack)
(MTC)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 638

Parame Ran Unit Description Supported NE

ter ge Version

Average [0, Second Average duration of successful calls for BSC6900

Call +∞) the mobile-originated party. V900R014C00 (or
Duration This parameter indicates the average later) or BSC6910
(MOC) call duration. V100R014C00 (or
later)
Duration of a call = Time when the
DisConnect message is generated –
Time when the Connect Acknowledge
message is generated
Note: For an inter-BSC combined
CHR, the value of this counter is
regarded invalid if this CHR is
incomplete.

Short [0, Numbe Number of short calls for the mobile- BSC6900
Calls +∞) r originated party during a successful V900R014C00 (or
(MOC) call. later) or BSC6910
This parameter indicates the VIP V100R014C00 (or
subscriber's call-terminating actions later)
caused by exceptions, such as one-way
audio, crosstalk, and disturbance call,
based on a predefined short call
threshold.
A short call occurs when the actual call
duration (namely, the Service Duration)
of the VIP subscriber is shorter than the
short call threshold (namely, the
Service Duration predefined when the
task is created).

Ratio of [0.00 % Average duration of successful calls for BSC6900

Short , the mobile-originated party. V900R014C00 (or
Calls 100.0 This parameter indicates the average later) or BSC6910
(MOC) 0] call duration. V100R014C00 (or
later)
Duration of a call = Time when the
DisConnect message is generated –
Time when the Connect Acknowledge
message is generated

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 639

Parame Ran Unit Description Supported NE

ter ge Version

Average [0, Second Average duration of successful calls for BSC6900

Call +∞) the mobile-terminated party. V900R014C00 (or
Duration This parameter indicates the average later) or BSC6910
(MTC) call duration. V100R014C00 (or
later)
Duration of a call = Time when the
DisConnect message is generated –
Time when the Connect Acknowledge
message is generated
Note: For an inter-BSC combined
CHR, the value of this counter is
regarded invalid if this CHR is
incomplete.

Short [0, Numbe Number of short calls for the mobile- BSC6900
Calls +∞) r terminated party during a successful V900R014C00 (or
(MTC) call. later) or BSC6910
This parameter indicates the VIP V100R014C00 (or
subscriber's call-terminating actions later)
caused by exceptions, such as one-way
audio, crosstalk, and disturbance call,
based on a predefined short call
threshold.
A short call occurs when the actual call
duration (namely, the Service Duration)
of the VIP subscriber is shorter than the
short call threshold (namely, the
Service Duration predefined when the
task is created).

Ratio of [0.00 % Proportion of short calls for the mobile- BSC6900

Short , terminated party during a successful V900R014C00 (or
Calls 100.0 call. later) or BSC6910
(MTC) 0] Proportion of short calls = Number of V100R014C00 (or
short calls/Number of calls with valid later)
call durations x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 640

RAN-CS/Call/Service Evaluation for Call

Parame Ran Unit Description Supported NE
ter ge Version

Call [0, Num Number of successful call setups when BSC6900

Setup +∞) ber a VIP subscriber accesses the network V900R014C00 (or
Success and initiates a call. later) or BSC6910
Times The call setup process spans from the V100R014C00 (or
Channel Request message to the later)
Alerting message.

Call [0, Num Same as the related counter in RAN/ BSC6900

Complet +∞) ber CS/Call/Accessibility Evaluation. V900R014C00 (or
ion later) or BSC6910
(Connec V100R014C00 (or
t Ack) later)

Downlin [0, Num Number of times that one-way audio BSC6900

k One- +∞) ber occurs in the downlink during calls. V900R014C00 (or
way The one-way audio test can only detect later) or BSC6910
Audio the one-way audio exceptions related V100R014C00 (or
Times to the channels within the BSS (BTS<- later)
>TC) instead of those related to the
Um and A interfaces.
Principle for detecting one-way audio
occurs in the downlink: The DSP in the
DTRU of the BTS performs periodic
statistics on the bad frame rate based
on downlink TRAU frames. When the
bad frame rate reaches the predefined
threshold, the BSS determines that
primary one-way audio occurs in the
downlink and starts the mechanism for
confirming the occurrence of primary
one-way audio in the downlink.
During this process, the BSC sends a
message to the TC demanding that the
TC send a test TRAU frame to the
BTS. If the BTS fails to receive the test
TRAU frame from the TC within a
specified time period, one-way audio
occurs on the downlink voice channel.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 641

Parame Ran Unit Description Supported NE

ter ge Version

Downlin [0.00 % Proportion of successful call setups BSC6900

k One- , where one-way audio occurs in the V900R014C00 (or
way 100. downlink in all successful call setups. later) or BSC6910
Audio 00] Proportion of successful call setups V100R014C00 (or
Ratio where one-way audio occurs in the later)
downlink in all successful call setups
= Number of times that one-way audio
occurs in the downlink/Number of
successful call setups (Connect Ack) x
100%

Uplink [0, Num Number of times that one-way audio BSC6900

One- +∞) ber occurs in the uplink during calls. V900R014C00 (or
way The one-way audio test can only detect later) or BSC6910
Audio the one-way audio exceptions related V100R014C00 (or
Times to the channels within the BSS (BTS<- later)
>TC) instead of those related to the
Um and A interfaces.
Principle for detecting one-way audio
in the uplink: The DSP in the TC of the
BSC performs periodic statistics on
the bad frame rate based on uplink
TRAU frames. When the bad frame
rate reaches the predefined threshold,
the BSS determines that primary one-
way audio occurs in the uplink and
starts the mechanism for confirming
the occurrence of primary one-way
audio in the uplink. During this
process, the BSC sends a message to
the BTS demanding that the BTS send
a test TRAU frame to the TC. If the TC
fails to receive the test TRAU frame
from the BTS within a specified time
period, one-way audio occurs on the
uplink voice channel.

Uplink [0.00 % Proportion of successful call setups BSC6900

One- , where one-way audio occurs in the V900R014C00 (or
way 100. uplink in all successful call setups. later) or BSC6910
Audio 00] Proportion of successful call setups V100R014C00 (or
Ratio where one-way audio occurs in the later)
uplink in all successful call setups =
Number of times that one-way audio
occurs in the uplink/Number of
successful call setups (Connect Ack) x
100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 642

Parame Ran Unit Description Supported NE

ter ge Version

Downlin [0, Num Number of times that no audio occurs BSC6900

k/Uplink +∞) ber in both the uplink and downlink during V900R014C00 (or
No- calls. later) or BSC6910
Audio V100R014C00 (or
Times later)

Downlin [0.00 % Proportion of successful call setups BSC6900

k/Uplink , where one-way audio occurs in both V900R014C00 (or
No 100. the uplink and downlink in all later) or BSC6910
Audio 00] successful call setups. V100R014C00 (or
Ratio Proportion of successful call setups later)
where one-way audio occurs in both
the uplink and downlink in all
successful call setups = Number of
successful call setups where one-way
audio occurs in both the uplink and
downlink/Number of successful call
setups (Connect Ack) x 100%

Downlin [0, Num Number of times that crosstalk occurs BSC6900

k +∞) ber in the downlink during calls. V900R014C00 (or
Crosstal The crosstalk test can only detect the later) or BSC6910
k Times crosstalk exceptions related to the V100R014C00 (or
channels within the BSS (BTS<->TC) later)
instead of those related to the Um and
A interfaces.
Principle for detecting downlink
crosstalk: The DSP of the TC inserts
the unique identifier of a call into the
free bits of downlink speech TRAU
frames. The DSP on the BTS side
decodes the unique call identifier and
checks its consistency. If
inconsistency is detected within the
test period, crosstalk occurs in the
downlink.

Downlin [0.00 % Proportion of successful call setups BSC6900

k , where crosstalk occurs in the V900R014C00 (or
Crosstal 100. downlink in all successful call setups. later) or BSC6910
k Ratio 00] Proportion of successful call setups V100R014C00 (or
where crosstalk occurs in the later)
downlink in all successful call setups
= Number of successful call setups
where crosstalk occurs in the
downlink/Number of successful call
setups (Connect Ack) x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 643

Parame Ran Unit Description Supported NE

ter ge Version

Uplink [0, Num Number of times that crosstalk occurs BSC6900

Crosstal +∞) ber in the uplink during calls. V900R014C00 (or
k Times The crosstalk test can only detect the later) or BSC6910
crosstalk exceptions related to the V100R014C00 (or
channels within the BSS (BTS<->TC) later)
instead of those related to the Um and
A interfaces.
Principle for detecting uplink
crosstalk: The DSP of the BTS inserts
the unique identifier of a call into the
free bits of uplink speech TRAU
frames. The DSP of the TC decodes
the unique call identifier and checks its
consistency. If inconsistency is
detected within the test period,
crosstalk occurs in the uplink.

Uplink [0.00 % Proportion of successful call setups BSC6900

Crosstal , where crosstalk occurs in the uplink in V900R014C00 (or
k Ratio 100. all successful call setups. later) or BSC6910
00] Proportion of successful call setups V100R014C00 (or
where crosstalk occurs in the uplink in later)
all successful call setups = Number of
successful call setups where crosstalk
occurs in the uplink/Number of
successful call setups (Connect Ack) x
100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 644

Parame Ran Unit Description Supported NE

ter ge Version

Average [0.00 % Average value of downlink HQIs after BSC6900

Downlin , the call setup is successful. V900R014C00 (or
k HQI 100. HQI indicates the voice quality of a later) or BSC6910
00] call and is measured on a 0-to-7 scale. V100R014C00 (or
Level 0 indicates the best quality. later)

In CHRs of the BSC6900 V900R011

or any later version:
HQI = Number of measurement
reports indicating a voice quality of
levels 0 to 3/Number of measurement
reports indicating a voice quality of
levels 0 to 7 x 100%
In CHRs of the BSC6000 V900R008
version:
HQI = Number of measurement
reports indicating a voice quality of
levels 0 to 5/Number of measurement
reports indicating a voice quality of
levels 0 to 7 x 100%

Poor [0, Num Number of times that the uplink HQI BSC6900
Downlin +∞) ber is poor after the call setup is V900R014C00 (or
k HQI successful. later) or BSC6910
Times Set the exception threshold when you V100R014C00 (or
create a task. later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 645

Parame Ran Unit Description Supported NE

ter ge Version

Average [0.00 % Average value of uplink high quality BSC6900

Uplink , indicators (HQIs) after the call setup is V900R014C00 (or
HQI 100. successful. later) or BSC6910
00] HQI indicates the voice quality of a V100R014C00 (or
call and is measured on a 0-to-7 scale. later)
Level 0 indicates the best quality.
In CHRs of the BSC6900 V900R011
or any later version:
HQI = Number of measurement
reports indicating a voice quality of
levels 0 to 3/Number of measurement
reports indicating a voice quality of
levels 0 to 7 x 100%
In CHRs of the BSC6000 V900R008
version:
HQI = Number of measurement
reports indicating a voice quality of
levels 0 to 5/Number of measurement
reports indicating a voice quality of
levels 0 to 7 x 100%

Poor [0, Num Number of times that the uplink HQI BSC6900
Uplink +∞) ber is poor after the call setup is V900R014C00 (or
HQI successful. later) or BSC6910
Times Set the exception threshold when you V100R014C00 (or
a create task. later)

Average [1.00 N/A Average value of uplink voice quality BSC6900

Uplink , indicators (VQIs) during calls. V900R014C00 (or
VQI 5.00] VQI is the Mean Opinion Score later) or BSC6910
(MOS) and indicates the voice quality V100R014C00 (or
of a call. The value of the voice quality later)
ranges from 1 to 5. The larger the value
is, the better the voice quality is.
Average value for the uplink VQIs of
successful call setups = Aggregated
value of uplink VQIs/Number of
uplink VQI tests

Poor [0, Num Number of times that the uplink VQI BSC6900
Uplink +∞) ber is poor during calls. V900R014C00 (or
VQI Set the exception threshold when you later) or BSC6910
Times create a task. V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 646

Parame Ran Unit Description Supported NE

ter ge Version

Average [0.00 N/A Average value of downlink voice BSC6900

Downlin , quality indicators (VQIs) during calls. V900R014C00 (or
k VQI 5.00] VQI is the Mean Opinion Score later) or BSC6910
(MOS) and indicates the voice quality V100R014C00 (or
of a call. The value of the voice quality later)
ranges from 0 to 5. The larger the value
is, the better the voice quality is.
Average value for the downlink VQIs
of successful call setups = Aggregated
value of downlink VQIs/Number of
downlink VQI tests

Poor [0, Num Number of times that the downlink BSC6900

Downlin +∞) ber VQI is poor during calls. V900R014C00 (or
k VQI Set the exception threshold when you later) or BSC6910
Times create a task. V100R014C00 (or
later)

Average [0, Num Average downlink level during calls. BSC6900

Downlin +∞) ber V900R014C00 (or
k Level later) or BSC6910
V100R014C00 (or
later)

Average [0, Num Average uplink level during calls. BSC6900

Uplink +∞) ber V900R014C00 (or
Level later) or BSC6910
V100R014C00 (or
later)

Average [0,7] N/A Average downlink quality during BSC6900

Downlin calls. V900R014C00 (or
k later) or BSC6910
Quality V100R014C00 (or
later)

Average [0,7] N/A Average uplink quality during calls. BSC6900

Uplink V900R014C00 (or
Quality later) or BSC6910
V100R014C00 (or
later)

Downlin [0, Num Number of times that noise occurs in BSC6900

k Noise +∞) ber the downlink during calls, which is V900R014C00 (or
Occurre detected by the BSC. later) or BSC6910
nce V100R014C00 (or
Times later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 647

Parame Ran Unit Description Supported NE

ter ge Version

Downlin [0.00 % Proportion of successful call setups BSC6900

k Noise , where noise occurs in the downlink in V900R014C00 (or
Ratio 100. all successful call setups. later) or BSC6910
00] Proportion of successful call setups V100R014C00 (or
where noise occurs in the downlink in later)
all successful call setups = Number of
successful call setups where noise
occurs in the downlink/Number of
successful call setups (Connect Ack) x
100%

Uplink [0, Num Number of times that noise occurs in BSC6900

Noise +∞) ber the uplink during calls, which is V900R014C00 (or
Occurre detected by the BSC. later) or BSC6910
nce V100R014C00 (or
Times later)

Uplink [0.00 % Proportion of successful call setups BSC6900

Noise , where noise occurs in the uplink in all V900R014C00 (or
Ratio 100. successful call setups. later) or BSC6910
00] Proportion of successful call setups V100R014C00 (or
where noise occurs in the uplink in all later)
successful call setups = Number of
successful call setups where noise
occurs in the uplink/Number of
successful call setups (Connect Ack) x
100%

RAN-CS/SMS/Accessibility Evaluation
Param Range Unit Description Supported NE
eter Version

Call [0,+∞) Num Number of setup requests that the BSC6900

Setup ber mobile-originated party initiates to use V900R014C00 (or
Reques the SMS service. later) or BSC6910
ts V100R014C00 (or
(MOC) later)

Call [0,+∞) Num Number of call setup failures that the BSC6900
Setup ber mobile-originated party experiences V900R014C00 (or
Failure during the process of attempting to use later) or BSC6910
s the SMS service. V100R014C00 (or
(MOC) later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 648

Param Range Unit Description Supported NE

eter Version

Call [0.00,1 % Proportion of successful setup requests BSC6900

Setup 00.00] that mobile-originated party initiates to V900R014C00 (or
Succes use the SMS service. later) or BSC6910
s Ratio V100R014C00 (or
(MOC) later)

Call [0,+∞) Num Number of setup requests that the BSC6900

Setup ber mobile-terminated party initiates to use V900R014C00 (or
Reques the SMS service. later) or BSC6910
ts V100R014C00 (or
(MTC) later)

Call [0,+∞) Num Number of call setup failures that the BSC6900
Setup ber mobile-terminated party experiences V900R014C00 (or
Failure during the process of attempting to use later) or BSC6910
s the SMS service. V100R014C00 (or
(MTC) later)

Call [0.00,1 % Proportion of successful call setup BSC6900

Setup 00.00] requests that the mobile-terminated V900R014C00 (or
Succes party initiates to use the SMS service. later) or BSC6910
s Ratio V100R014C00 (or
(MTC) later)

Parameters for Viewing GSM VIP Analysis - RAN PS Results

This section describes the parameters for querying GSM VIP Analysis - RAN PS results. You
can refer to the description when querying GSM VIP analysis - RAN PS results.

RAN-PS/PS/General Evaluation
Parame Ran Unit Description Supported NE
ter ge Version

Access [0, Numb See Access Failures in RAN-PS/PS/ BSC6900

Failures +∞) er Accessibility Evaluation. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Total [0, Numb Indicates the number of the BSC6900

Reports +∞) er measurement reports that the access V900R014C00 (or
of failure count exceeds 0. later) or BSC6910
Access V100R014C00 (or
Failure later)
Count >
0

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 649

Parame Ran Unit Description Supported NE

ter ge Version

Abnorm [0,10 % Indicates the proportion of the total BSC6900

al 0] measurement reports that the access V900R014C00 (or
Proporti failure count exceeds 0. later) or BSC6910
on of V100R014C00 (or
Access later)
Failure
Count >
0

Service [0, Numb See Service Interruptions in RAN- BSC6900

Interrupt +∞) er PS/PS/Retainability Evaluation. V900R014C00 (or
ions later) or BSC6910
V100R014C00 (or
later)

Total [0, Numb Indicates the number of the BSC6900

Reports +∞) er measurement reports that the service V900R014C00 (or
of interruption count exceeds 0. later) or BSC6910
Service V100R014C00 (or
Interrupt later)
ion
Count >
0

Abnorm [0,10 % Indicates the proportion of the total BSC6900

al 0] measurement reports that the service V900R014C00 (or
Proporti interruption count exceeds 0. later) or BSC6910
on of V100R014C00 (or
Service later)
Interrupt
ion
Count >
0

Abnorm [0, Numb See Abnormal Service Interaction BSC6900

al +∞) er Delays in RAN-PS/PS/Service V900R014C00 (or
Service Evaluation for Delay. later) or BSC6910
Interacti V100R014C00 (or
on later)
Delays

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 650

Parame Ran Unit Description Supported NE

ter ge Version

Total [0, Numb Indicates the number of the BSC6900

Reports +∞) er measurement reports that the V900R014C00 (or
of abnormal service interaction latency later) or BSC6910
Abnorm count exceeds 0. V100R014C00 (or
al later)
Service
Interacti
on
Latency
Count >
0

Abnorm [0,10 % Indicates the proportion of the total BSC6900

al 0] measurement reports that the V900R014C00 (or
Proporti abnormal service interaction latency later) or BSC6910
on of count exceeds 0. V100R014C00 (or
Abnorm later)
al
Service
Interacti
on
Latency
Count >
0

Downloa [0, Numb See Downloads at Low Rate in BSC6900

ds at +∞) er RAN-PS/PS/Service Evaluation for V900R014C00 (or
Low Rate. later) or BSC6910
Rate V100R014C00 (or
later)

Abnorm [0,10 % Indicates the proportion of the total BSC6900

al 0] measurement reports that the V900R014C00 (or
Proporti download rate is low. later) or BSC6910
on at V100R014C00 (or
Low later)
Downloa
d Ratio

Uploads [0, Numb See Uploads at Low Rate in RAN- BSC6900

at Low +∞) er PS/PS/Service Evaluation for Rate. V900R014C00 (or
Rate later) or BSC6910
V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 651

Parame Ran Unit Description Supported NE

ter ge Version

Abnorm [0,10 % Indicates the proportion of the total BSC6900

al 0] measurement reports that the upload V900R014C00 (or
Proporti rate is low. later) or BSC6910
on at V100R014C00 (or
Low later)
Upload
Ratio

RAN-PS/PS/Accessibility Evaluation
Parame Rang Unit Description Supported NE
ter e Version

Cell +∞) d during the process for a VIP subscriber to V900R014C00 (or
Reselect use a data service. later) or BSC6910
ion This parameter is also referred to as the V100R014C00 (or
Interval average interval between cell later)
reselections.

Overlon [0, Numb Number of times that the cell reselection BSC6900
g Cell +∞) er interval is overlong during the process for V900R014C00 (or
Reselect a VIP subscriber to use a data service. later) or BSC6910
ion If the time interval is above the threshold V100R014C00 (or
Interval for overlong cell reselection, the cell later)
Times reselection interval is overlong.
Set the threshold when you create a task.

Service [0, Numb Number of service interruptions that a BSC6900

Interrupt +∞) er VIP subscriber experiences during the V900R014C00 (or
ions Due process of using a data service due to later) or BSC6910
to routing area update. V100R014C00 (or
Routing later)
Area
Update

Interrupt [0, Numb Number of service interruptions that a BSC6900

ions Due +∞) er VIP subscriber experiences during the V900R014C00 (or
to process of using a data service due to later) or BSC6910
FLUSH- FLUSH-LL. V100R014C00 (or
LL later)

Interrupt [0, Numb Number of service interruptions that a BSC6900

ions Due +∞) er VIP subscriber experiences during the V900R014C00 (or
to TBF process of using a data service due to later) or BSC6910
TBF. V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 655

RAN-PS/PS/Service Evaluation for Delay

Parame Rang Unit Description Supported
ter e NE Version

Abnorm [0, Numb Number of times that the service interaction BSC6900
al +∞) er delay is abnormal during the process for a VIP V900R014C0
Service subscriber to use a data service. 0 (or later) or
Interacti If Number of Service Interaction Timeouts is BSC6910
on not equal to 0, Number of Abnormal Service V100R014C0
Delays Interaction Delays is equal to Number of 0 (or later)
Service Interaction Timeouts.
If Number of Service Interaction Timeouts is
equal to 0, Number of Abnormal Service
Interaction Delays is equal to Number of
Service Interactions with Long Delay.

Service [0, Numb Number of times that the response to service BSC6900
Interacti +∞) er interaction times out during the process for a V900R014C0
on VIP subscriber to use a data service. 0 (or later) or
Timeout Number of Service Interaction Timeout BSC6910
s Times = Number of Timeout Times on V100R014C0
sending PDUs at Downlink + Number of 0 (or later)
Timeout Times on sending PDUs at Uplink +
Number of Interval Timeouts for data
transmission between the uplink and
downlink PDUs.

Average [0, Secon Average duration of the response to service BSC6900

Delay on +∞) d interaction during the process for a VIP V900R014C0
Service subscriber to use a data service. 0 (or later) or
Interacti Average duration of the response to service BSC6910
on interaction = (Average duration of data V100R014C0
transmission by using the downlink PDU + 0 (or later)
Average duration of data reception by using
the uplink PDU + Average duration of data
transmission between the uplink and
downlink PDUs) / number of valid values.

Service [0, Numb Number of times that the average duration of BSC6900
Interacti +∞) er the response to service interaction is overlong V900R014C0
ons with during the process for a subscriber to use a 0 (or later) or
Long data service. BSC6910
Delay If the average duration of the response to V100R014C0
service interaction is above the upper 0 (or later)
threshold for the average duration of the
response to service interaction,
the average duration of the response to service
interaction is overlong.
Set the threshold when you create a task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 656

RAN-PS/PS/Service Evaluation for Rate

Parame Rang Unit Description Supported
ter e NE Version

Average [0.00, kbit/s Average download rate during the process for BSC6900
Downlo +∞) a subscriber to use a data service. V900R014C0
ad Rate Download rate = Number of bytes transmitted 0 (or later) or
by using the downlink PDU/Duration of data BSC6910
transmission by using the downlink PDU V100R014C0
0 (or later)

Downlo [0, Numb Number of times that the download rate is low BSC6900
ads at +∞) er during the process for a subscriber to use a V900R014C0
Low data service. 0 (or later) or
Rate A download rate is low if it is lower than the BSC6910
threshold for low download rate. V100R014C0
0 (or later)
Set the threshold when you create a task.

Abnorm [0,10 % Indicates the proportion of the total BSC6900

al 0] measurement reports that the download rate is V900R014C0
Proporti low. 0 (or later) or
on at BSC6910
Low V100R014C0
Downlo 0 (or later)
ad Ratio

Downlin [0, Numb Number of times that downlink TCP disorder BSC6900
k TCP +∞) er occurs during the process for a subscriber to V900R014C0
Out-of- use a data service. 0 (or later) or
Orders BSC6910
V100R014C0
0 (or later)

Average [0.00, kbit/s Average upload rate during the process for a BSC6900
Upload +∞) subscriber to use a data service. V900R014C0
Rate Upload rate = Number of bytes transmitted by 0 (or later) or
using the uplink PDU/Duration of data BSC6910
transmission by using the uplink PDU V100R014C0
0 (or later)

Uploads [0, Numb Number of times that the upload rate is low BSC6900
at Low +∞) er during the process for a subscriber to use a V900R014C0
Rate data service. 0 (or later) or
An upload rate is low if it is lower than the BSC6910
threshold for low upload rate. V100R014C0
0 (or later)
Set the threshold is when you create a task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 657

Parame Rang Unit Description Supported

ter e NE Version

Abnorm [0,10 % Indicates the proportion of the total BSC6900

al 0] measurement reports that the upload rate is V900R014C0
Proporti low. 0 (or later) or
on at BSC6910
Low V100R014C0
Upload 0 (or later)
Ratio

RAN-PS/PS/Traffic Model Analysis

Parame Rang Unit Description Supported
ter e NE Version

Average [0.00, kbit/s See Average Download Rate in RAN-PS/PS/ BSC6900

Downlo +∞) Service Evaluation for Rate. V900R014C0
ad Rate 0 (or later) or
BSC6910
V100R014C0
0 (or later)

Average [0.00, kbit/s See Average Upload Rate in RAN-PS/PS/ BSC6900

Upload +∞) Service Evaluation for Rate. V900R014C0
Rate 0 (or later) or
BSC6910
V100R014C0
0 (or later)

Total [0, KB Total downlink traffic during the process for BSC6900
Traffic +∞) a subscriber to use a data service. V900R014C0
Downlin Total downlink traffic = Delay-Sensitive 0 (or later) or
k Information/Total Number of the Bytes BSC6910
Transmitted by Using the Downlink PDU V100R014C0
0 (or later)
+ Rate-Sensitive Information/Statistics on
Downlink Rate-Sensitive Service/Number of
the Bytes Transmitted by Using the Downlink
PDU
+ Rate-Sensitive Information/Statistics on
Uplink Rate-Sensitive Service/Number of the
Bytes Transmitted by Using the Downlink
PDU

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 658

Parame Rang Unit Description Supported

ter e NE Version

Total [0, KB Total uplink traffic during the process for a BSC6900
Traffic +∞) subscriber to use a data service. V900R014C0
Uplink Total uplink traffic = Delay-Sensitive 0 (or later) or
Information/Total Number of the Bytes BSC6910
Transmitted by Using the Uplink PDU V100R014C0
0 (or later)
+ Rate-Sensitive Information/Statistics on
Uplink Rate-Sensitive Service/Number of the
Bytes Transmitted by Using the Uplink PDU
+ Rate-Sensitive Information/Statistics on
Downlink Rate-Sensitive Service/Number of
the Bytes Transmitted by Using the Uplink
PDU

Uplink [0, Numb Number of access requests on the RACH BSC6900

Signalin +∞) er (uplink CCCH) during the process for a V900R014C0
g Access subscriber to use a data service. 0 (or later) or
Times BSC6910
V100R014C0
0 (or later)

Average [0, Numb Average number of channels occupied by the BSC6900

Occupie +∞) er downlink during the process for a subscriber V900R014C0
d to use a data service. 0 (or later) or
Downlin BSC6910
k V100R014C0
Channel 0 (or later)
s

Average [0, Numb Average number of channels occupied by the BSC6900

Occupie +∞) er uplink during the process for a subscriber to V900R014C0
d Uplink use a data service. 0 (or later) or
Channel BSC6910
s V100R014C0
0 (or later)

Parameters for Viewing GSM VIP Analysis - Active Cell Results

This section describes the parameters for querying GSM VIP analysis - active cell results. You
can refer to the description when querying GSM VIP analysis - active cell results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 659

Common
Para Range Unit Description Supported NE
met Version
er

BSC 1 to 64 N/A Name of the BSC to which an active cell BSC6900

Nam charact belongs. V900R014C00 (or
e ers Note: when name information cannot be later) or BSC6910
obtained because configuration V100R014C00 (or
information has been deleted or cell later)
information has not been activated,
Undefined is displayed.

Cell [0,2047 N/A ID of an active cell. BSC6900

ID ] V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Cell 1 to 64 N/A Name of an active cell. BSC6900

Nam charact Note: when name information cannot be V900R014C00 (or
e ers obtained because configuration later) or BSC6910
information has been deleted or cell V100R014C00 (or
information has not been activated, later)
Undefined is displayed.

CGI MCC- N/A Cell global identification (CGI) of an BSC6900

MNC- active cell. V900R014C00 (or
LAC- later) or BSC6910
CI V100R014C00 (or
MCC later)
[000,99
9]
MNC
[00,99]
LAC
[0,6553
5]
CI
[0,6553
5]

Gro 1 to 128 N/A Name of a VIP group. BSC6900

up charact V900R014C00 (or
Nam ers later) or BSC6910
e V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 660

Para Range Unit Description Supported NE

met Version
er

User [0,2047 N/A ID of a VIP subscriber. Query the ID of BSC6900

ID ] a VIP subscriber using VIP group V900R014C00 (or
management. later) or BSC6910
V100R014C00 (or
later)

Alia 1 to 64 N/A Name of a VIP alias. Query the alias of a BSC6900

s charact VIP subscriber using VIP group V900R014C00 (or
ers management. later) or BSC6910
V100R014C00 (or
later)

IMS N/A N/A IMSI information of a subscriber. BSC6900

I Note: Only when you have the "User V900R014C00 (or
Identity" right, you can view the IMSI later) or BSC6910
information. V100R014C00 (or
later)

IME N/A N/A International mobile equipment identity- BSC6900

I- type allocation code (IMEI-TAC) of the V900R014C00 (or
TAC terminal used by a VIP subscriber. later) or BSC6910
V100R014C00 (or
later)

Ter N/A N/A Type of the terminal used by a VIP BSC6900

mina subscriber. Obtain the terminal type in V900R014C00 (or
l the Terminal Type Management window later) or BSC6910
Mod based on the IMEI-TAC of the terminal V100R014C00 (or
el used by the VIP subscriber. later)

Serv N/A N/A Service type for a following counter. BSC6900

ice V900R014C00 (or
Typ later) or BSC6910
e V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 661

RAN-CS/NET/Accessibility Evaluation
Par R Uni Description Supported NE
am a t Version
eter n
g
e

Acc [ Nu Number of access requests that a VIP group or VIP BSC6900

ess 0 mbe subscriber initiates during the process of using a call V900R014C00
Req , r or SMS service in an active cell. (or later) or
uest + BSC6910
s ∞ V100R014C00
) (or later)

Acc [ Nu Number of access failures that a VIP group or VIP BSC6900

ess 0 mbe subscriber experiences during the process of using a V900R014C00
Fail , r call or SMS service in an active cell. (or later) or
ures + BSC6910
∞ V100R014C00
) (or later)

Abn [ Nu Number of abnormal TA values that a VIP group or BSC6900

orm 0 mbe VIP subscriber experiences during the process of V900R014C00
al , r attempting to access the network in an active cell. (or later) or
TAs + BSC6910
on ∞ V100R014C00
Acc ) (or later)
ess

Abn [ Nu Number of abnormal RACH levels that a VIP group BSC6900

orm 0 mbe or VIP subscriber experiences during the process of V900R014C00
al , r attempting the network in an active cell. (or later) or
RA + BSC6910
CH ∞ V100R014C00
Lev ) (or later)
els
on
Acc
ess

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 662

RAN-CS/NET/Retainability Evaluation
Par R U Description Supported NE
am a n Version
eter n i
g t
e

Rele [ N Number of times that a VIP group or VIP subscriber BSC6900

ases 0 u releases the Call service in an active cell. V900R014C00 (or
, m later) or BSC6910
+ b V100R014C00 (or
∞ e later)
) r

Abn [ N Number of times that a VIP group or VIP subscriber BSC6900

orm 0 u abnormally releases the Call service in an active cell. V900R014C00 (or
al , m later) or BSC6910
Rele + b V100R014C00 (or
ases ∞ e later)
) r

RAN-CS/NET/Mobility Evaluation
Par R U Description Supported NE
am a n Version
eter n i
g t
e

Inte [ N Number of incoming inter-RAT handover requests that BSC6900

r- 0 u a VIP group or VIP subscriber initiates in an active cell. V900R014C00 (or
RA , m later) or BSC6910
T + b V100R014C00 (or
Inco ∞ e later)
min ) r
g
Han
dov
er
Req
uest
s

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 663

Par R U Description Supported NE

am a n Version
eter n i
g t
e

Inte [ N Number of incoming inter-RAT handover failures that BSC6900

r- 0 u a VIP group or VIP subscriber experiences in an active V900R014C00 (or
RA , m cell. later) or BSC6910
T + b V100R014C00 (or
Inco ∞ e later)
min ) r
g
Han
dov
er
Fail
ures

RAN-CS/Call/Accessibility Evaluation
Par R U Description Supported NE
am a n Version
eter n i
g t
e

Tota [ N Number of call setup requests that a VIP group or VIP BSC6900
l 0 u subscriber initiates in an active cell. V900R014C00
Call , m (or later) or
Setu + b BSC6910
p ∞ e V100R014C00
Req ) r (or later)
uest
s

Call [ N Number of call setup failures that a VIP group or VIP BSC6900
Setu 0 u subscriber experiences in an active cell. V900R014C00
p , m (or later) or
Fail + b BSC6910
ures ∞ e V100R014C00
) r (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 664

Par R U Description Supported NE

am a n Version
eter n i
g t
e

Abn [ N Number of call releases that a VIP group or VIP BSC6900

orm 0 u subscriber experiences before call completion in an V900R014C00
al , m active cell. (or later) or
Rele + b BSC6910
ase ∞ e V100R014C00
Bef ) r (or later)
ore
Call
Co
mpl
etio
n

RAN-CS/Call/Retainability Evaluation
Par R U Description Supported NE
am a n Version
eter n i
g t
e

Abn [ N Number of abnormal call releases that a VIP group or BSC6900

orm 0 u VIP subscriber experiences in an active cell. V900R014C00
al , m (or later) or
Call + b BSC6910
Rele ∞ e V100R014C00
ases ) r (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 665

RAN-CS/SMS/Accessibility Evaluation
Par R U Description Supported NE
am a n Version
eter n i
g t
e

Call [ N Number of call setup requests that a VIP group or VIP BSC6900
Setu 0 u subscriber initiates in an active cell as the mobile- V900R014C00
p , m originated party. (or later) or
Req + b BSC6910
uest ∞ e V100R014C00
s ) r (or later)
(M
OC)

Call [ N Number of call setup failures that a VIP group or VIP BSC6900
Setu 0 u subscriber experiences in an active cell as the mobile- V900R014C00
p , m originated party. (or later) or
Fail + b BSC6910
ures ∞ e V100R014C00
(M ) r (or later)
OC)

Call [ N Number of call setup requests that a VIP group or VIP BSC6900
Setu 0 u subscriber initiates in an active cell as the mobile- V900R014C00
p , m terminated party. (or later) or
Req + b BSC6910
uest ∞ e V100R014C00
s ) r (or later)
(MT
C)

Call [ N Number of call setup failures that a VIP group or VIP BSC6900
Setu 0 u subscriber experiences in an active cell as the mobile- V900R014C00
p , m terminated party. (or later) or
Fail + b BSC6910
ures ∞ e V100R014C00
(MT ) r (or later)
C)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 666

RAN-PS/PS/Accessibility Evaluation
Par R U Description Supported NE
am a n Version
eter n i
g t
e

Atta [ N Number of Attach Request messages that a VIP group or BSC6900

ch 0 u VIP subscriber sends in an active cell. V900R014C00
Req , m (or later) or
uest + b BSC6910
s ∞ e V100R014C00
) r (or later)

PD [ N Number of PDP Active Request messages that a VIP BSC6900

P 0 u group or VIP subscriber sends in an active cell. V900R014C00
Acti , m (or later) or
ve + b BSC6910
Req ∞ e V100R014C00
uest ) r (or later)
s

No [ N Number of exceptions where no response to service BSC6900

Serv 0 u interaction is made when a VIP group or VIP subscriber V900R014C00
ice , m is using a service in an active cell. (or later) or
Inte + b BSC6910
racti ∞ e V100R014C00
on ) r (or later)
Res
pon
ses

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 667

RAN-PS/PS/Retainability Evaluation
Par R U Description Supported NE
am a n Version
eter n i
g t
e

Inte [ N Number of service interruptions that a VIP group or VIP BSC6900

rrup 0 u subscriber experiences due to cell reselection in an active V900R014C00
tion , m cell. (or later) or
s + b BSC6910
Due ∞ e V100R014C00
to ) r (or later)
Cell
Res
elec
tion

Ove [ N Number of times that the cell reselection interval is BSC6900

rlon 0 u overlong when a VIP group or VIP subscriber is using a V900R014C00
g , m service in an active cell. (or later) or
Cell + b BSC6910
Res ∞ e V100R014C00
elec ) r (or later)
tion
Inte
rval
Tim
es

Serv [ N Number of service interruptions that a VIP group or VIP BSC6900

ice 0 u subscriber experiences due to routing area update in an V900R014C00
Inte , m active cell. (or later) or
rrup + b BSC6910
tion ∞ e V100R014C00
s ) r (or later)
Due
to
Rou
ting
Are
a
Upd
ate

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 668

RAN-PS/PS/Service Quality Evaluation for Delay

Par R U Description Supported NE
am a n Version
eter n i
g t
e

Serv [ N Number of times that the duration of the response to BSC6900

ice 0 u service interaction is overlong when a VIP group or VIP V900R014C00
Inte , m subscriber is using a service in an active cell. (or later) or
racti + b BSC6910
on ∞ e V100R014C00
Tim ) r (or later)
eout
s

Serv [ N Number of times that the delay of the response to service BSC6900
ice 0 u interaction is overlong when a VIP group or VIP V900R014C00
Inte , m subscriber is using a service in an active cell. (or later) or
racti + b BSC6910
ons ∞ e V100R014C00
with ) r (or later)
Lon
g
Del
ay

Parameters for Viewing GSM VIP Analysis - Active Server Results

This section describes the parameters for querying GSM VIP analysis - active Server results.
You can refer to the description when querying GSM VIP analysis - active server results.

Common
Paramet Rang Unit Description Supported NE Version
er e

Server IP N/A N/A IP address of an active server. BSC6900 V900R014C00

(or later) or BSC6910
V100R014C00 (or later)

Server N/A N/A Name of an active server. Obtain BSC6900 V900R014C00

Name the name of an active server by (or later) or BSC6910
choosing System Function > V100R014C00 (or later)
Data Service Server
Management in the navigation
tree of the Nastar client based on
the IP address of the server.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 669

Paramet Rang Unit Description Supported NE Version

er e

Server N/A N/A Port number of an active server. BSC6900 V900R014C00

Port (or later) or BSC6910
V100R014C00 (or later)

Service N/A N/A Name of an active service. BSC6900 V900R014C00

Name Obtain the name of an active (or later) or BSC6910
service by choosing System V100R014C00 (or later)
Function > Data Service Server
Management in the navigation
tree of the Nastar client based on
the Server IP and Server Port
values of the service.

Total [0, Num Number of reports generated BSC6900 V900R014C00

Reports +∞) ber when a user accesses the server. (or later) or BSC6910
V100R014C00 (or later)

RAN-PS/PS/General Evaluation
Paramet Rang Unit Description Supported NE Version
er e

Server- [0, Num Server-Related Service BSC6900 V900R014C00

Related +∞) ber Abnormalities = No Service (or later) or BSC6910
Service Interaction Responses + Service V100R014C00 (or later)
Abnorma Interaction Timeouts + Service
lities Interaction with Long Delay +
Downlink TCP Out-of-Orders

RAN-PS/PS/Accessibility Evaluation
Paramet Rang Unit Description Supported NE Version
er e

No [0, Num Number of times that no BSC6900 V900R014C00 (or

Service +∞) ber response to service interaction later) or BSC6910
Interactio is made when a VIP group or V100R014C00 (or later)
n VIP subscriber is using a
Response service in an active cell.
s

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 670

RAN-PS/PS/Service Evaluation for Delay

Paramet Rang Unit Description Supported NE
er e Version

Service [0, Num Number of times that the response BSC6900

Interactio +∞) ber to service interaction times out V900R014C00 (or
n when a VIP group or VIP subscriber later) or BSC6910
Timeouts is using a service in an active cell. V100R014C00 (or
later)

Service [0, Num Number of times that the duration of BSC6900

Interactio +∞) ber the response to service interaction is V900R014C00 (or
n with overlong when a VIP group or VIP later) or BSC6910
Long subscriber is using a service in an V100R014C00 (or
Delay active cell. later)

RAN-PS/PS/Service Evaluation for Rate

Paramet Range Unit Description Supported NE Version
er

Downlin [0,+∞) Num Number of times that BSC6900 V900R014C00 (or

k TCP ber downlink TCP disorder later) or BSC6910
Out-of- occurs when a VIP group or V100R014C00 (or later)
Orders VIP subscriber is using a
service in an active cell.

3.9.6 Reference for VIP Analysis Parameters (UMTS)

This section describes the parameters for UMTS VIP analysis.

Parameters for Viewing UMTS VIP Analysis - Common Results

This section describes the parameters for querying UMTS VIP analysis-common results, You
can refer to the description when querying UMTS VIP analysis-common results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 671

Common
Param Rang Unit Description Supported NE Version
eter e

Deep N/A N/A ·When the dimension is Group, BSC6900 V900R014C00 (or
Analysi this parameter is used to switch later) or BSC6910
s from the analysis results of a V100R014C00 (or later)
VIP group to the analysis
results of VIP subscribers in
this group.
·When the dimension is User,
this parameter is used to switch
from the analysis results of
counters to the analysis results
of calls.

Group N/A N/A Name of a VIP group. BSC6900 V900R014C00 (or

Name later) or BSC6910
V100R014C00 (or later)

User ID N/A N/A ID of a VIP subscriber. Query BSC6900 V900R014C00 (or

the ID of a VIP subscriber later) or BSC6910
using VIP group management. V100R014C00 (or later)

Alias N/A N/A Name of a VIP alias. Query the BSC6900 V900R014C00 (or
alias of a VIP subscriber using later) or BSC6910
VIP group management. V100R014C00 (or later)

IMSI N/A N/A IMSI information of a BSC6900 V900R014C00 (or

subscriber. later) or BSC6910
Note: Only when you have the V100R014C00 (or later)
"User Identity" right, you can
view the IMSI information.

IMEI- N/A N/A Type approval code (TAC) in BSC6900 V900R014C00 (or
TAC international mobile later) or BSC6910
equipment identity (IMEI) of V100R014C00 (or later)
the UE used by a VIP
subscriber.

Termin N/A N/A Type of the UE used by a VIP BSC6900 V900R014C00 (or
al subscriber. Query the UE type later) or BSC6910
Model of a VIP subscriber using V100R014C00 (or later)
terminal type management
based on the IMEI-TAC of the
VIP subscriber.

Service N/A N/A Service type for a counter. BSC6900 V900R014C00 (or
Type later) or BSC6910
V100R014C00 (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 672

Param Rang Unit Description Supported NE Version

eter e

Numbe [0, Num Number of abnormal counters BSC6900 V900R014C00 (or

r of +∞) ber in all counter sets determined later) or BSC6910
Abnor based on the result thresholds V100R014C00 (or later)
mal set when engineers create a
KPIs task.

Total [0, Num Indicates the number of BSC6900 V900R014C00 (or

Reports +∞) ber records generated for all later) or BSC6910
service types during the V100R014C00 (or later)
network access of a subscriber.

Parameters for Viewing UMTS VIP Analysis - Network Level Results

This section describes the parameters for querying UMTS VIP analysis - Network Level results,
You can refer to the description when querying UMTS VIP analysis - network level results.

RAN-NET/Accessibility Evaluation
Parameter Range Unit Description Supported NE
Version

Access [0,+∞) Numbe Number of access requests that a BSC6900

Requests(Intra- r VIP subscriber initiates from a V900R014C00
RAT) cell in the current system. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 673

Parameter Range Unit Description Supported NE

Version

Access Failures [0,+∞) Numbe Number of access failures that a BSC6900

(Intra-RAT) r VIP subscriber experiences from V900R014C00
a cell in the current system. (or later) or
Number of failed access requests BSC6910
(intra-RAT) = Number of failed V100R014C00
service requests initiated by a (or later)
specified UE that has gained
access to a system of the current
RAT
= Number of RRC connection
setup failures (service) +
(Number of RAB setup failures
for AMR + Number of RAB
setup failures for VP + Number
of RAB setup failures for PS R99
+ Number of RAB setup failures
for HSDPA + Number of RAB
setup failures for HSUPA +
Number of RAB setup failures
for HSPA – Number of times that
the first RAB setup after an
incoming intra-RAT handover
fails)

Access [0,+∞) Numbe Number of access requests that a BSC6900

Requests(Inter- r VIP subscriber initiates from a V900R014C00
RAT) cell in another system. (or later) or
BSC6910
V100R014C00
(or later)

Access Failures [0,+∞) Numbe Number of access failures that a BSC6900

(Inter-RAT) r VIP subscriber experiences from V900R014C00
a cell in another system. (or later) or
Number of failed access requests BSC6910
(inter-RAT) = Number of failed V100R014C00
service requests initiated by a (or later)
specified UE that has gained
access to a system of another
RAT
= Number of incoming inter-
RAT handover failures that this
UE experiences on the entire
network + Number of times that
the first RAB setup after an
incoming inter-RAT handover
fails

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 674

Parameter Range Unit Description Supported NE

Version

Average TP on [0,3069 N/A Average TP value when a VIP BSC6900

Access ] subscriber gains access to the V900R014C00
network. (or later) or
BSC6910
V100R014C00
(or later)

Abnormal TPs [0,+∞) Numbe Number of times that theTP BSC6900

on Access r value is abnormal upon network V900R014C00
access. (or later) or
Set the exception threshold when BSC6910
you create a task. V100R014C00
(or later)
Remark: If the active set contains
multiple cells during access,
only the counters for the first cell
in this active set are analyzed.

Proportion of [0.00,10 % Proportion of abnormal TP BSC6900

Abnormal TPs 0.00] values that a VIP subscriber V900R014C00
on Access experiences upon network (or later) or
access. BSC6910
Proportion of abnormal TP V100R014C00
values = Number of abnormal TP (or later)
values/Number of TP values x
100%

Average RSCP [-116,-2 dBm Average RSCP value when a BSC6900

on Access 5] VIP subscriber gains access to V900R014C00
the network. (or later) or
BSC6910
V100R014C00
(or later)

Abnormal [0,+∞) Numbe Number of times that the RSCP BSC6900

RSCPs on r value is abnormal upon network V900R014C00
Access access. (or later) or
Set the exception threshold when BSC6910
you create a task. V100R014C00
(or later)
Remark: If the active set contains
multiple cells during access,
only the counters for the first cell
in this active set are analyzed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 675

Parameter Range Unit Description Supported NE

Version

Proportion of [0.00,10 % Proportion of abnormal RSCP BSC6900

Abnormal 0.00] values that a VIP subscriber V900R014C00
RSCPs on experiences upon network (or later) or
Access access. BSC6910
Proportion of abnormal RSCP V100R014C00
values = Number of abnormal (or later)
RSCP values/Number of RSCP
values x 100%

Average Ec/No [-24,0] dB Average Ec/No value when a BSC6900

on Access VIP subscriber gains access to V900R014C00
the network. (or later) or
BSC6910
V100R014C00
(or later)

Abnormal Ec/ [0,+∞) Numbe Number of times that the Ec/No BSC6900
Nos on Access r value is abnormal upon network V900R014C00
access. (or later) or
Set the exception threshold when BSC6910
you create a task. V100R014C00
(or later)
Remark: If the active set contains
multiple cells during access,
only the counters for the first cell
in this active set are analyzed.

Proportion of [0.00,10 % Proportion of abnormal Ec/No BSC6900

Abnormal Ec/ 0.00] values that a VIP subscriber V900R014C00
Nos on Access experiences upon network (or later) or
access. BSC6910
Proportion of abnormal Ec/No V100R014C00
values = Number of abnormal (or later)
Ec/No values/Number of Ec/No
values x 100%

RRC Setup [0,+∞) Numbe Number of non-service RRC BSC6900

Requests(Non- r connection setup requests V900R014C00
Service) initiated by a VIP subscriber. (or later) or
RRC is short for radio resource BSC6910
control. V100R014C00
(or later)
The non-service RRC
connection setup process spans
from the time when the non-
service RRC connection setup
request is initiated to the time
when the non-service RRC
connection setup is complete.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 676

Parameter Range Unit Description Supported NE

Version

RRC Setup [0,+∞) Numbe Number of non-service RRC BSC6900

Failures(Non- r connection setup failures after V900R014C00
Service) network access. (or later) or
BSC6910
V100R014C00
(or later)

RRC Setup [0.00,10 % Success ratio of non-service BSC6900

Success Ratio 0.00] RRC connection setups after V900R014C00
(Non-Service) network access. (or later) or
BSC6910
V100R014C00
(or later)

RRC Setup [0,+∞) Numbe Number of service RRC BSC6900

Requests r connection setup requests after V900R014C00
(Service) network access. (or later) or
BSC6910
V100R014C00
(or later)

RRC Setup [0,+∞) Numbe Number of service RRC BSC6900

Failures r connection setup failures after V900R014C00
(Service) network access. (or later) or
BSC6910
V100R014C00
(or later)

RRC Setup [0.00,10 % Success ratio of service RRC BSC6900

Success Ratio 0.00] connection setups after network V900R014C00
(Service) access. (or later) or
BSC6910
V100R014C00
(or later)

RRC Setup [0,+∞) Numbe Number of CS RRC connection BSC6900

Failures r setup failures after network V900R014C00
(Service-CS) access. (or later) or
BSC6910
V100R014C00
(or later)

RRC Setup [0.00,10 % Success ratio of CS RRC BSC6900

Success Ratio 0.00] connection setups after network V900R014C00
(Service-CS) access. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 677

Parameter Range Unit Description Supported NE

Version

RRC Setup [0,+∞) Numbe Number of PS RRC connection BSC6900

Failures r setup failures after network V900R014C00
(Service-PS) access. (or later) or
BSC6910
V100R014C00
(or later)

RRC Setup [0.00,10 % Success ratio of PS RRC BSC6900

Success Ratio 0.00] connection setups after network V900R014C00
(Service-PS) access. (or later) or
BSC6910
V100R014C00
(or later)

RAN-NET/E2E Evaluation(CS Domain)

Parameter Range Unit Description Supported NE
Version

Call Setup [0,+∞) Numbe Number of call setup requests BSC6900

Requests r that a VIP subscriber initiates to V900R014C00
(MOC) use the CS service as the mobile- (or later) or
originated party. BSC6910
V100R014C00
(or later)

Call Setup [0,+∞) Numbe Number of call setup failures BSC6900

Failures(MOC) r that a VIP subscriber V900R014C00
experiences during the process (or later) or
of using the CS service as the BSC6910
mobile-originated party. V100R014C00
(or later)

Call Setup [0.00,10 % Success ratio of call setup BSC6900

Success Ratio 0.00] requests that a VIP subscriber V900R014C00
(MOC) initiates to use the CS service as (or later) or
the mobile-originated party. BSC6910
V100R014C00
(or later)

Call Setup [0,+∞) Numbe Number of call setup requests BSC6900

Requests(MTC) r that a VIP subscriber initiates to V900R014C00
use the CS service as the mobile- (or later) or
terminated party. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 678

Parameter Range Unit Description Supported NE

Version

Call Setup [0,+∞) Numbe Number of call setup failures BSC6900

Failures(MTC) r that a VIP subscriber V900R014C00
experiences during the process (or later) or
of using the CS service as the BSC6910
mobile-terminated party. V100R014C00
(or later)

Call Setup [0.00,10 % Success ratio of call setup BSC6900

Success Ratio 0.00] requests that a VIP subscriber V900R014C00
(MTC) initiates to use the CS service as (or later) or
the mobile-terminated party. BSC6910
V100R014C00
(or later)

Call Connection [0,+∞) Numbe Number of call connection BSC6900

Acknowledgme r acknowledgment (alerting) V900R014C00
nt Success successes of a VIP subscriber (or later) or
Times(Alerting) who accesses the network and BSC6910
(MOC) uses the CS service as the V100R014C00
mobile-originated party. (or later)
The alerting process spans from
the RRC connection setup
request to the Alerting message.
Note: This parameter is
collected based only on the first
RAB after the RRC connection
setup is complete.

Call Connection [0.00,10 % Ratio of call connection BSC6900

Acknowledgme 0.00] acknowledgment (alerting) V900R014C00
nt Success Ratio successes of a VIP subscriber (or later) or
(Alerting) who accesses the network and BSC6910
(MOC) uses the CS service as the V100R014C00
mobile-originated party. (or later)

Call Connection [0,+∞) Numbe Number of successful call BSC6900

Acknowledgme r connection acknowledgments V900R014C00
nt Success (alerting) that a VIP subscriber (or later) or
Times(Alerting) experiences during the process BSC6910
(MTC) of using the CS service as the V100R014C00
mobile-terminated party. (or later)

Call Connection [0.00,10 % Success ratio of call connection BSC6900

Acknowledgme 0.00] acknowledgments (alerting) V900R014C00
nt Success Ratio that a VIP subscriber (or later) or
(Alerting) experiences during the process BSC6910
(MTC) of using the CS service as the V100R014C00
mobile-terminated party. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 679

Parameter Range Unit Description Supported NE

Version

Call Connection [0,+∞) Numbe Number of successful call BSC6900

Acknowledgme r connection acknowledgments V900R014C00
nt Success (Connect Ack) that a VIP (or later) or
Times(Connect subscriber experiences during BSC6910
Ack)(MOC) the process of using the CS V100R014C00
service as the mobile-originated (or later)
party.
The connection
acknowledgment (Connect
Ack) process spans from the
RRC connection setup request
to the Connect Ack message.
Note: This parameter is
collected based only on the first
RAB after the RRC connection
setup is complete.

Call Connection [0.00,10 % Success ratio of call connection BSC6900

Acknowledgme 0.00] acknowledgments (Connect V900R014C00
nt Success Ratio Ack) that a VIP subscriber (or later) or
(Connect Ack) experiences during the process BSC6910
(MOC) of using the CS service as the V100R014C00
mobile-originated party. (or later)

Call Connection [0,+∞) Numbe Number of successful call BSC6900

Acknowledgme r connection acknowledgments V900R014C00
nt Success (Connect Ack) that a VIP (or later) or
Times(Connect subscriber experiences during BSC6910
Ack)(MTC) the process of using the CS V100R014C00
service as the mobile-terminated (or later)
party.

Call Connection [0.00,10 % Success ratio of call connection BSC6900

Acknowledgme 0.00] acknowledgments (Connect V900R014C00
nt Success Ratio Ack) that a VIP subscriber (or later) or
(Connect Ack) experiences during the process BSC6910
(MTC) of using the CS service as the V100R014C00
mobile-terminated party. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 680

Parameter Range Unit Description Supported NE

Version

Call Success [0,+∞) Numbe Number of calls that a VIP BSC6900

Times(MOC) r subscriber successfully initiates V900R014C00
to use the CS service as the (or later) or
mobile-originated party. BSC6910
The call success process spans V100R014C00
from the RRC connection setup (or later)
request to the Disconnect
message.
Note: This parameter is
collected based only on the first
RAB after the RRC connection
setup is complete.

Call Success [0.00,10 % Success ratio of calls that a VIP BSC6900

Ratio(MOC) 0.00] subscriber successfully initiates V900R014C00
to use the CS service as the (or later) or
mobile-originated party. BSC6910
V100R014C00
(or later)

Call Success [0,+∞) Numbe Number of calls that a VIP BSC6900

Times(MTC) r subscriber successfully initiates V900R014C00
to use the CS service as the (or later) or
mobile-terminated party. BSC6910
V100R014C00
(or later)

Call Success [0.00,10 % Success ratio of calls that a VIP BSC6900

Ratio(MTC) 0.00] subscriber successfully initiates V900R014C00
to use the CS service as the (or later) or
mobile-terminated party. BSC6910
V100R014C00
(or later)

RAN-NET/E2E Evaluation(PS Domain)

Parameter Range Unit Description Supported NE
Version

Call Setup [0,+∞) Number Number of call setup requests BSC6900

Requests(PS) that a VIP subscriber initiates to V900R014C00
access the network and use the (or later) or
PS service. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 681

Parameter Range Unit Description Supported NE

Version

Call Setup [0,+∞) Number Number of call setup failures BSC6900

Failures(PS) that a VIP subscriber V900R014C00
experiences during the process (or later) or
of attempting to access the BSC6910
network and use the PS service. V100R014C00
(or later)

Call Setup [0.00,10 % Success ratio of call setup BSC6900

Success Ratio 0.00] requests that a VIP subscriber V900R014C00
(PS) initiates to access the network (or later) or
and use the PS service. BSC6910
V100R014C00
(or later)

Call Success [0,+∞) Number Number of calls that a VIP BSC6900

Times(PS) subscriber successfully initiates V900R014C00
to use the PS service. (or later) or
The call success process spans BSC6910
from the RRC connection setup V100R014C00
request to the Disconnect (or later)
message.
Note: This parameter is
collected based only on the first
RAB after the RRC connection
setup is complete.

Call Success [0.00,10 % Success ratio of calls that a VIP BSC6900

Ratio(PS) 0.00] subscriber successfully initiates V900R014C00
to use the PS service. (or later) or
BSC6910
V100R014C00
(or later)

RAN-NET/PDP Evaluation-PS
Parameter Range Unit Description Supported NE
Version

PDP Activation [0,+∞) Number Number of PDP activation BSC6900

Requests requests that a VIP subscriber V900R014C00
initiates to access the network (or later) or
and use the PS service. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 682

Parameter Range Unit Description Supported NE

Version

PDP Activation [0,+∞) Number Number of PDP activation BSC6900

Failures failures that a VIP subscriber V900R014C00
experiences during the process (or later) or
of attempting to access the BSC6910
network and use the PS service. V100R014C00
(or later)

PDP Activation [0.00,10 % Success ratio of PDP activation BSC6900

Success Ratio 0.00] requests that a VIP subscriber V900R014C00
initiates to access the network (or later) or
and use the PS service. BSC6910
V100R014C00
(or later)

RAN-NET/Retainability Evaluation
Parameter Range Unit Description Supported NE
Version

Release Times [0,+∞) Number Number of times that a VIP BSC6900

(Intra-RAT) subscriber releases all services in V900R014C00
the current system. (or later) or
Releases(Intra-RAT) = Access BSC6910
Requests(Intra-RAT) - Access V100R014C00
Failures(Intra-RAT) (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 683

Parameter Range Unit Description Supported NE

Version

Abnormal [0,+∞) Number Number of times that a VIP BSC6900

Release Times subscriber abnormally releases V900R014C00
(Intra-RAT) all services in the current system. (or later) or
Abnormal Release Times(Intra- BSC6910
RAT) = Number of AMR RAB V100R014C00
abnormal releases (or later)

+ Number of VP RAB abnormal

releases
+ Number of PS R99 RAB
abnormal releases
+ Number of HSDPA RAB
abnormal releases
+ Number of HSUPA abnormal
releases
+ Number of HSPA abnormal
releases
– Number of the first RAB
abnormal releases after inter-
RAT incoming handover occurs.

Release Times [0,+∞) Number Number of times that a VIP BSC6900

(Inter-RAT) subscriber releases all services in V900R014C00
another system. (or later) or
Releases(Inter-RAT) = Access BSC6910
Requests(Inter-RAT) – Access V100R014C00
Failures(Inter-RAT) (or later)

Abnormal [0,+∞) Number Number of times that a VIP BSC6900

Release Times subscriber abnormally releases V900R014C00
(Inter-RAT) all services in another system. (or later) or
Abnormal Release Times(Inter- BSC6910
RAT) = Number of times that the V100R014C00
first RAB after an incoming (or later)
inter-RAT handover is
abnormally released.

RRC Release [0,+∞) Number Number of times that a VIP BSC6900

Times subscriber releases all RRC V900R014C00
connections during the process (or later) or
of using a service. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 684

Parameter Range Unit Description Supported NE

Version

Abnormal RRC [0,+∞) Number Number of times that a VIP BSC6900

Release Times subscriber abnormally releases V900R014C00
all RRC connections during the (or later) or
process of using a service. BSC6910
V100R014C00
(or later)

RAN-NET/Delay Evaluation
Parameter Range Unit Description Supported NE
Version

RRC Setup [0,+∞) Number Number of successful non- BSC6900

Success Times service RRC connection setups V900R014C00
(Non-Service) upon successful call initiation. (or later) or
Number of successful RRC BSC6910
connection setups (non-service) V100R014C00
= Number of RRC connection (or later)
setup requests (non-service) –
Number of RRC connection
setup failures (non-service) =
Number of valid RRC
connection setup delays (non-
service)

Average RRC N/A Second Average delay for non-service BSC6900

Setup Delay RRC connection setup upon V900R014C00
(Non-Service) successful call initiation. (or later) or
RRC connection setup delay = BSC6910
Time when the RRC CONN V100R014C00
SETUP CMP message is (or later)
generated – Time when the RRC
CONN REQ message is
generated.

Overlong RRC [0,+∞) Number Number of overlong delays for BSC6900

Setup Delay non-service RRC connection V900R014C00
Times(Non- setup upon successful call (or later) or
Service) initiation. BSC6910
Set the overlong delay threshold V100R014C00
when you create a task. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 685

Parameter Range Unit Description Supported NE

Version

Proportion of [0.00,1 % Proportion of delays for non- BSC6900

Overlong RRC 00.00] service RRC connection setup in V900R014C00
Setup Delay all overlong delays upon (or later) or
(Non-Service) successful call initiation. BSC6910
V100R014C00
(or later)

RRC Setup [0,+∞) Number Number of successful service BSC6900

Success Times RRC connection setups upon V900R014C00
(Service) successful call initiation. (or later) or
Number of service RRC BSC6910
connection setups = Number of V100R014C00
service RRC connection setup (or later)
requests – Number of service
RRC connection setup failures =
Number of valid delays for
service RRC connection setup.

Average RRC [0,+∞) Second Average delay for service RRC BSC6900
Setup Delay connection setup upon V900R014C00
(Service) successful call initiation. (or later) or
RRC connection setup delay = BSC6910
Time when the RRC CONN V100R014C00
SETUP CMP message is (or later)
generated – Time when the RRC
CONN REQ message is
generated.

Overlong RRC [0,+∞) Number Number of overlong delays for BSC6900

Setup Delay service RRC connection setup V900R014C00
Times(Service) upon successful call initiation. (or later) or
Set the overlong delay threshold BSC6910
when you create a task. V100R014C00
(or later)

Proportion of [0.00,1 % Proportion of overlong delays BSC6900

Overlong RRC 00.00] for service RRC connection V900R014C00
Setup Delay setup in all overlong delays upon (or later) or
(Service) successful call initiation. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 686

RAN-NET/Mobility Evaluation
Parameter Range Unit Description Supported
NE Version

Soft Handover [0,+∞) Number Number of soft handover BSC6900

Requests requests that a VIP subscriber V900R014C00
initiates during the process of (or later) or
using a service. BSC6910
V100R014C00
(or later)

Soft Handover [0,+∞) Number Number of soft handover failures BSC6900

Failures that a VIP subscriber experiences V900R014C00
during the process of using a (or later) or
service. BSC6910
V100R014C00
(or later)

Soft Handover [0.00,1 % Success ratio of soft handovers BSC6900

Success Ratio 00.00] (including softer handovers) that V900R014C00
a VIP subscriber initiates during (or later) or
the process of using a service. BSC6910
V100R014C00
(or later)

Hard Handover [0,+∞) Number Number of hard handover BSC6900

Requests requests that a VIP subscriber V900R014C00
initiates during the process of (or later) or
using a service. BSC6910
V100R014C00
(or later)

Hard Handover [0,+∞) Number Number of hard handover BSC6900

Failures failures that a VIP subscriber V900R014C00
experiences during the process of (or later) or
using a service. BSC6910
V100R014C00
(or later)

Hard Handover [0.00,1 % Success ratio of hard handovers BSC6900

Success Ratio 00.00] that a VIP subscriber initiates V900R014C00
during the process of using a (or later) or
service. BSC6910
V100R014C00
(or later)

Average Soft [0,+∞) Second Average soft handover delay BSC6900

Handover Delay during the process for a VIP V900R014C00
subscriber to use a service. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 687

Parameter Range Unit Description Supported

NE Version

Average Hard [0,+∞) Second Average hard handover delay BSC6900

Handover Delay during the process for a VIP V900R014C00
subscriber to use a service. (or later) or
BSC6910
V100R014C00
(or later)

Inter-RAT [0,+∞) Number Number of outgoing handover BSC6900

Outgoing requests (from a UMTS network V900R014C00
Handover to another network) initiated by a (or later) or
Requests UE. BSC6910
V100R014C00
(or later)

Inter-RAT [0,+∞) Number Number of outgoing handover BSC6900

Outgoing requests (from a UMTS network V900R014C00
Handover to a GSM network) initiated by a (or later) or
Requests VIP subscriber. BSC6910
(UMTS to V100R014C00
GSM) (or later)

Inter-RAT [0,+∞) Number Number of outgoing handover BSC6900

Outgoing requests (from a UMTS network V900R014C00
Handover to an LTE network) initiated by a (or later) or
Requests VIP subscriber. BSC6910
(UMTS to LTE) V100R014C00
(or later)

Inter-RAT [0,+∞) Number Number of outgoing handover BSC6900

Outgoing failures (from a UMTS network V900R014C00
Handover to another network) experienced (or later) or
Failures by a VIP subscriber. BSC6910
V100R014C00
(or later)

Inter-RAT [0,+∞) Number Number of outgoing handover BSC6900

Outgoing failures (from a UMTS network V900R014C00
Handover to a GSM network) experienced (or later) or
Failures(UMTS by a VIP subscriber. BSC6910
to GSM) V100R014C00
(or later)

Inter-RAT [0,+∞) Number Number of outgoing handover BSC6900

Outgoing failures (from one UMTS V900R014C00
Handover network to another LTE (or later) or
Failures(UMTS network) experienced by a UE. BSC6910
to LTE) V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 688

Parameter Range Unit Description Supported

NE Version

Inter-RAT [0,+∞) Number Number of inter-RAT handover BSC6900

Incoming requests (from another network V900R014C00
Handover to a UMTS network) initiated by (or later) or
Requests a VIP subscriber. BSC6910
V100R014C00
(or later)

Inter-RAT [0,+∞) Number Number of inter-RAT handover BSC6900

Incoming requests (from a GSM network to V900R015C00
Handover a UMTS network) initiated by a (or later) or
Requests(GSM VIP subscriber. BSC6910
to UMTS) V100R015C00
(or later)

Inter-RAT [0,+∞) Number Number of inter-RAT handover BSC6900

Incoming requests (from an LTE network V900R015C00
Handover to a UMTS network) initiated by (or later) or
Requests(LTE a VIP subscriber. BSC6910
to UMTS) V100R015C00
(or later)

Inter-RAT [0,+∞) Number Number of inter-RAT handover BSC6900

Incoming failures (from another network to V900R014C00
Handover a UMTS network) experienced (or later) or
Failures by a VIP subscriber. BSC6910
V100R014C00
(or later)

Inter-RAT [0,+∞) Number Number of inter-RAT handover BSC6900

Incoming failures (from a GSM network to V900R015C00
Handover a UMTS network) experienced (or later) or
Failures(GSM by a VIP subscriber. BSC6910
to UMTS) V100R015C00
(or later)

Inter-RAT [0,+∞) Number Number of inter-RAT handover BSC6900

Incoming failures (from an LTE network to V900R015C00
Handover a UMTS network) experienced (or later) or
Failures(LTE to by a VIP subscriber. BSC6910
UMTS) V100R015C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 689

Parameter Range Unit Description Supported

NE Version

Average Inter- [0,+∞) Second Average delay for outgoing inter- BSC6900
RAT Outgoing RAT handover recorded by the V900R014C00
Handover Delay current system. (or later) or
Outgoing inter-RAT handover BSC6910
delay = Time when the IU V100R014C00
RELEASE COMMAND (or later)
message is generated – Time
when the RELOCATION
REQUIRED message is
generated.

Average Inter- [0,+∞) Second Average delay for UMTS-to- BSC6900

RAT Outgoing GSM handover recorded by the V900R014C00
Handover Delay current system. (or later) or
(UMTS to BSC6910
GSM) V100R014C00
(or later)

Average Inter- [0,+∞) Second Average delay for UMTS-to- BSC6900

RAT Outgoing LTE handover recorded by the V900R014C00
Handover Delay current system. (or later) or
(UMTS to LTE) BSC6910
V100R014C00
(or later)

Average Inter- [0,+∞) Second Average delay for incoming BSC6900

RAT Incoming inter-RAT handover recorded by V900R014C00
Handover Delay the current system. (or later) or
Incoming inter-RAT handover BSC6910
delay = Time when the UTRAN V100R014C00
MOBILITY INFORMATION (or later)
CONFIRM message is generated
– Time when the RELOCATION
REQUIRED message is
generated.

Average Inter- [0,+∞) Second Average delay for GSM-to- BSC6900

RAT Incoming UMTS handover recorded by the V900R015C00
Handover Delay current system. (or later) or
(GSM to BSC6910
UMTS) V100R015C00
(or later)

Average Inter- [0,+∞) Second Average delay for LTE-to- BSC6900

RAT Incoming UMTS handover recorded by the V900R015C00
Handover Delay current system. (or later) or
(LTE to UMTS) BSC6910
V100R015C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 690

Parameter Range Unit Description Supported

NE Version

Inter-RAT Cell [0,+∞) Number Number of cell reselections BSC6900

Reselection recorded by the current system. V900R014C00
Times (or later) or
BSC6910
V100R014C00
(or later)

Parameters for Viewing UMTS VIP Analysis - RAN CS Results

This section describes the parameters for querying UMTS VIP analysis - RAN CS results. You
can refer to the description when querying UMTS VIP analysis - RAN CS results.

RAN-CS/AMR/Accessibility Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Number of RAB setup requests BSC6900

Requests initiated by a VIP subscriber. V900R014C00
RAB is short for radio access (or later) or
bearer. BSC6910
V100R014C00
(or later)

RAB Setup [0,+∞) Number Number of RAB setup failures BSC6900

Failures experienced by a VIP V900R014C00
subscriber. (or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0,+∞) Number Number of times that a VIP BSC6900

Success Times subscriber successfully initiates V900R014C00
an RAB setup request. (or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0.00,10 % RAB setup success ratio after BSC6900

Success Ratio 0.00] network access. V900R014C00
RAB setup success ratio (%) = (or later) or
Number of successful RAB BSC6910
setups/Number of RAB setup V100R014C00
requests x 100%. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 691

Parameter Range Unit Description Supported NE

Version

Call Connection [0,+∞) Number Number of times that a VIP BSC6900

Acknowledgme subscriber hears the alerting V900R014C00
nt Success upon successful call initiation. (or later) or
Times(Alerting) BSC6910
V100R014C00
(or later)

Call Connection [0,+∞) Number Number of times that a VIP BSC6900

Acknowledgme subscriber hears the peer ends' V900R014C00
nt Success voice upon successful call (or later) or
Times(Connect initiation. BSC6910
Ack) V100R014C00
(or later)

Abnormal [0,+∞) Number Number of times that a call is BSC6900

Release Times abnormally released between V900R014C00
Before the time when a subscriber (or later) or
Connection hears the alerting and the time BSC6910
Acknowledge when the subscriber hears the V100R014C00
voice of the peer-end subscriber (or later)
during a successful call.

RAN-CS/AMR/Retainability Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number See RAB Setup Success Times BSC6900
Success Times in RAN-CS/VP/Accessibility V900R014C00
Evaluation (or later) or
BSC6910
V100R014C00
(or later)

Abnormal RAB [0,+∞) Number Number of times that the RAB BSC6900
Release Times is abnormally released after a V900R014C00
VIP subscriber gains access to (or later) or
the network and successfully BSC6910
initiates a call. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 692

Parameter Range Unit Description Supported NE

Version

Abnormal RAB [0.00,10 % Abnormal RAB release ratio BSC6900

Release Ratio 0.00] after a VIP subscriber gains V900R014C00
access to the network and (or later) or
successfully initiates a call. BSC6910
Abnormal RAB release ratio V100R014C00
(%) = Number of abnormal (or later)
RAB releases/Number of
successful call setups x 100%.

RAN-CS/AMR/Delay Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Number of successful RAB BSC6900

Success Times setups during call initiation, that V900R014C00
is, number of RAB setup delays. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 693

Parameter Range Unit Description Supported NE

Version

Average RAB [0,+∞) Second Average RAB setup delay BSC6900

Setup Delay during the process for a VIP V900R014C00
subscriber to initiate a call. (or later) or
·Average RAB setup delay (s) = BSC6910
Sum of RAB setup delays/ V100R014C00
Number of RAB setup delays. (or later)

·RAB setup delay = RAB setup

request connection
acknowledge time – RAB setup
request time.
·Statistical point for RAB setup
request connection
acknowledge time: When the
RAB assignment procedure is
successful, namely, when the
SRNC sends a Radio Access
Bearer Assignment Response
message to the CN after it
receives an RAB setup
connection acknowledge
message.
·Statistical point for RAB setup
request time: When the UTRAN
receives a Radio Access Bearer
Assignment Request message
from the CN.

Overlong RAB [0,+∞) Number Number of times that the RAB BSC6900
Setup Delay setup delay is overlong during V900R014C00
Times the process for a VIP subscriber (or later) or
to initiate a call. BSC6910
Set the exception threshold V100R014C00
when you create a task. (or later)

Proportion of [0.00,10 % Proportion of RAB setup delays BSC6900

Overlong RAB 0.00] in all overlong delays. V900R014C00
Setup Delay Proportion of RAB setup delays (or later) or
(%) = Number of overlong RAB BSC6910
setup delays/Number of RAB V100R014C00
setup delays x 100% = Number (or later)
of overlong RAB setup delays/
Number of successful RAB
setups x 100%.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 694

Parameter Range Unit Description Supported NE

Version

Call Setup [0,+∞) Number Number of times that the call BSC6900
Delay Times setup delay of the mobile- V900R014C00
(MOC) originated party upon successful (or later) or
call initiation is overlong. BSC6910
V100R014C00
(or later)

Average Call [0,+∞) Second Average call setup delay of the BSC6900
Setup Delay mobile-originated party upon V900R014C00
(MOC) successful call initiation. (or later) or
BSC6910
V100R014C00
(or later)

Overlong Call [0,+∞) Number Number of times that the call BSC6900
Setup Delay setup delay of the mobile- V900R014C00
Times(MOC) originated party upon successful (or later) or
call initiation is overlong. BSC6910
Set the exception threshold V100R014C00
when you create a task. (or later)

Proportion of [0.00,10 % Proportion of overlong call BSC6900

Overlong Call 0.00] setup delays of the mobile- V900R014C00
Setup Delay originated party upon successful (or later) or
(MOC) call initiation. BSC6910
Proportion of overlong call V100R014C00
setup delays (mobile- (or later)
originated) (%) = Number of
overlong call setup delays
(mobile-originated)/Number of
call setup delays (mobile-
originated) x 100% = Number of
overlong call setup delays
(mobile-originated)/Number of
successful RRC connection
setups x 100%.

Call Setup [0,+∞) Number Number of times that the call BSC6900
Delay Times setup delay of the mobile- V900R014C00
(MTC) terminated party upon (or later) or
successful call initiation is BSC6910
overlong. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 695

Parameter Range Unit Description Supported NE

Version

Average Call [0,+∞) Second Average call setup delay of the BSC6900
Setup Delay mobile-terminated party upon V900R014C00
(MTC) successful call initiation. (or later) or
BSC6910
V100R014C00
(or later)

Overlong Call [0,+∞) Number Number of times that the call BSC6900
Setup Delay setup delay of the mobile- V900R014C00
Times(MTC) terminated party upon (or later) or
successful call initiation is BSC6910
overlong. V100R014C00
Set the exception threshold (or later)
when you create a task.

Proportion of [0.00,10 % Proportion of overlong call BSC6900

Overlong Call 0.00] setup delays of the mobile- V900R014C00
Setup Delay terminated party upon (or later) or
(MTC) successful call initiation. BSC6910
Proportion of overlong call V100R014C00
setup delays (mobile- (or later)
terminated) (%) = Number of
overlong call setup delays
(mobile-terminated)/Number of
call setup delays (mobile-
terminated) x 100% = Number
of overlong call setup delays
(mobile-terminated)/Number of
successful RRC connection
setups x 100%.

Call Connection [0,+∞) Number Number of times that the BSC6900

Acknowledgme mobile-originated party hears V900R014C00
nt Success the alerting upon successful call (or later) or
Times(Alerting) initiation. BSC6910
(MOC) V100R014C00
(or later)

Average Call [0,+∞) Second Average alerting delay of the BSC6900

Connection mobile-originated party upon V900R014C00
Acknowledgme successful call initiation. (or later) or
nt Delay BSC6910
(Alerting) V100R014C00
(MOC) (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 696

Parameter Range Unit Description Supported NE

Version

Overlong Call [0,+∞) Number Number of times that the BSC6900

Connection alerting delay of the mobile- V900R014C00
Acknowledgme originated party upon successful (or later) or
nt Delay Times call initiation is overlong. BSC6910
(Alerting) Set the exception threshold V100R014C00
(MOC) when you create a task. (or later)

Proportion of [0.00,10 % Proportion of overlong alerting BSC6900

Overlong Call 0.00] delays experienced by the V900R014C00
Connection mobile-originated party upon (or later) or
Acknowledgme successful call initiation. BSC6910
nt Delay V100R014C00
(Alerting) (or later)
(MOC)

Call Connection [0,+∞) Number Number of call connection BSC6900

Acknowledgme acknowledgment (Connect V900R014C00
nt Success Ack) delays experienced by the (or later) or
Times(Connect mobile-originated party upon BSC6910
Ack)(MOC) successful call initiation. V100R014C00
(or later)

Average Call [0,+∞) Second Average call connection BSC6900

Connection acknowledgment (Connect V900R014C00
Acknowledgme Ack) delay of the mobile- (or later) or
nt Delay originated party upon successful BSC6910
(Connect Ack) call initiation. V100R014C00
(MOC) (or later)

Overlong Call [0,+∞) Number Number of times that the call BSC6900
Connection connection acknowledgment V900R014C00
Acknowledgme (Connect Ack) delay of the (or later) or
nt Delay Times mobile-originated party upon BSC6910
(Connect Ack) successful call initiation is V100R014C00
(MOC) overlong. (or later)
Set the exception threshold
when you create a task.

Proportion of [0.00,10 % Proportion of overlong call BSC6900

Overlong Call 0.00] connection acknowledgment V900R014C00
Connection (Connect Ack) delays (or later) or
Acknowledgme experienced by the mobile- BSC6910
nt Delay originated party upon successful V100R014C00
(Connect Ack) call initiation. (or later)
(MOC)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 697

Parameter Range Unit Description Supported NE

Version

Call Connection [0,+∞) Number Number of times that the BSC6900

Acknowledgme mobile-terminated party hears V900R014C00
nt Success the alerting upon successful call (or later) or
Times(Alerting) initiation. BSC6910
(MTC) V100R014C00
(or later)

Average Call [0,+∞) Second Average call connection BSC6900

Connection acknowledgment (alerting) V900R014C00
Acknowledgme delay of the mobile-terminated (or later) or
nt Delay party upon successful call BSC6910
(Alerting) initiation. V100R014C00
(MTC) (or later)

Overlong Call [0,+∞) Number Number of times that the call BSC6900
Connection connection acknowledgment V900R014C00
Acknowledgme (alerting) delay of the mobile- (or later) or
nt Delay Times terminated party upon BSC6910
(Alerting) successful call initiation is V100R014C00
(MTC) overlong. (or later)
Set the exception threshold
when you create a task.

Proportion of [0.00,10 % Proportion of overlong call BSC6900

Overlong Call 0.00] connection acknowledgment V900R014C00
Connection (alerting) delays experienced by (or later) or
Acknowledgme the mobile-terminated party BSC6910
nt Delay upon successful call initiation. V100R014C00
(Alerting) (or later)
(MTC)

Call Connection [0,+∞) Number Number of successful call BSC6900

Acknowledgme connection acknowledgments V900R014C00
nt Success (Connect Ack) experienced by (or later) or
Times(Connect the mobile-terminated party BSC6910
Ack)(MTC) upon successful call initiation. V100R014C00
(or later)

Average Call [0,+∞) Second Average call connection BSC6900

Connection acknowledgment (Connect V900R014C00
Acknowledgme Ack) delay of the mobile- (or later) or
nt Delay terminated party upon BSC6910
(Connect Ack) successful call initiation. V100R014C00
(MTC) (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 698

Parameter Range Unit Description Supported NE

Version

Overlong Call [0,+∞) Number Number of times that the call BSC6900
Connection connection acknowledgment V900R014C00
Acknowledgme (Connect Ack) delay of the (or later) or
nt Delay Times mobile-terminated party upon BSC6910
(Connect Ack) successful call initiation is V100R014C00
(MTC) overlong. (or later)
Set the exception threshold
when you create a task.

Proportion of [0.00,10 % Proportion of call connection BSC6900

Overlong Call 0.00] acknowledgment (Connect V900R014C00
Connection Ack) delays experienced by the (or later) or
Acknowledgme mobile-terminated party upon BSC6910
nt Delay successful call initiation. V100R014C00
(Connect Ack) (or later)
(MTC)

Average RAB [0,+∞) Second Average RAB duration upon BSC6900

Service successful call initiation. V900R014C00
Duration Average RAB duration (s) = (or later) or
Total RAB duration/Number of BSC6910
RAB durations V100R014C00
(or later)
- RAB duration = RAB release
complete time - RAB request
complete time
- Statistical point of RAB release
complete time: Time when the
SRNC receives the IU
RELEASE COMMAND or
RAB ASSIGNMENT
REQUEST message
- Statistical point of RAB
request complete time: Time
when the RAB assignment is
complete, namely, the time
when the SRNC responds the
CN with a Radio Access Bearer
Assignment Response message
after receiving the RAB Setup
Complete message

Overshort RAB [0,+∞) Number Number of times that the RAB BSC6900
Service duration is below the threshold V900R014C00
Duration Times for short RAB duration upon (or later) or
successful call initiation. BSC6910
Set the exception threshold V100R014C00
when you create a task. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 699

Parameter Range Unit Description Supported NE

Version

Average Service [0,+∞) Second Average call duration of calls BSC6900

Duration(MOC) initiated by a VIP subscriber. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Number of [0,+∞) Number Number of short calls upon BSC6900

Short Calls successful call initiation. V900R014C00
(MOC) The mechanism for calculating (or later) or
the number of short calls adds BSC6910
the condition that short calls are V100R014C00
initiated by the mobile- (or later)
originated party.

Proportion of [0.00,10 % Proportion of short calls upon BSC6900

Short Calls 0.00] successful call initiation. V900R014C00
(MOC) The mechanism for calculating (or later) or
the proportion of short calls adds BSC6910
the condition that short calls are V100R014C00
initiated by the mobile- (or later)
originated party.

Average Service [0,+∞) Second Average call duration of calls BSC6900

Duration(MTC) initiated by a VIP subscriber. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Number of [0,+∞) Number Number of short calls upon BSC6900

Short Calls successful call initiation. V900R014C00
(MTC) The mechanism for calculating (or later) or
the number of short calls adds BSC6910
the condition that short calls are V100R014C00
initiated by the mobile- (or later)
terminated.

Proportion of [0.00,10 % Proportion of short calls upon BSC6900

Short Calls 0.00] successful call initiation. V900R014C00
(MTC) The mechanism for calculating (or later) or
the proportion of short calls adds BSC6910
the condition that short calls are V100R014C00
initiated by the mobile- (or later)
terminated.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 700

RAN-CS/AMR/Quality Evaluation
Parameter Range Unit Description Supported
NE Version

Call Setup [0,+∞) Number Number of times that a VIP BSC6900

Success Times subscriber successfully initiates V900R014C00
a call setup request. (or later) or
BSC6910
V100R014C00
(or later)

Downlink One- [0,+∞) Number Number of calls with downlink BSC6900

Way Audio one-way audio problems. V900R014C00
Times Downlink one-way audio (or later) or
problems are detected by the BSC6910
RNC. V100R014C00
(or later)

Proportion of [0.00,10 % Proportion of Downlink One- BSC6900

Downlink One- 0.00] Way Audio = Downlink One- V900R014C00
Way Audio Way Audio Times/RAB Setup (or later) or
Successes x 100% BSC6910
V100R014C00
(or later)

Uplink One- [0,+∞) Number Number of calls with uplink BSC6900

Way Audio one-way audio problems. V900R014C00
Times Uplink one-way audio problems (or later) or
are detected by the RNC. BSC6910
V100R014C00
(or later)

Proportion of [0.00,10 % Proportion of Uplink One-Way BSC6900

Uplink One- 0.00] Audio = Uplink One-Way V900R014C00
Way Audio Audio Times/RAB Setup (or later) or
Successes x 100% BSC6910
V100R014C00
(or later)

Noise Times [0,+∞) Number Number of calls with static BSC6900

problems. V900R014C00
Static problems are detected by (or later) or
the RNC. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 701

Parameter Range Unit Description Supported

NE Version

Noise [0.00,10 % Proportion of calls with static BSC6900

Proportion 0.00] problems. V900R014C00
·Proportion of calls with static (or later) or
problems (%) = Number of calls BSC6910
with static problems/Number of V100R014C00
connected calls (Connect Ack) x (or later)
100%.

SQI Reports [0,+∞) Number Number of signal quality BSC6900

indicator (SQI) reports V900R014C00
generated during a call. (or later) or
1. Signal quality indicator (SQI) BSC6910
indicates signal quality on the V100R014C00
uplink to show voice quality (or later)
during a call. The SQI statistics
are collected by the RNC. When
the statistical period is less than
9.6 seconds, the value of SQI is
0. The value range is [0,500]. A
larger value indicates better
signal quality.
2. The RNC collects statistics on
the average SQI value and
divides signal quality into
different levels according to SQI
values:
·RAN14.0: Excellent (SQI<=
(400,500]), Good (SQI<=
(300,400]), Accept (SQI<=
(200,300]), Poor (SQI<=
(100,200]), Bad (SQI<=
[0,100]).
·RAN13.0 and earlier: Good
(SQI <= (300,500]), Accept
(SQI <= (200,300]), Bad (SQI
<=(0,200]).
You can modify the segment
intervals of levels by running the
SET USQICOUNT command
on the RNC.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 702

Parameter Range Unit Description Supported

NE Version

Average SQI [0,+∞) N/A Average SQI value in the SQI BSC6900
reports generated during a call. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Abnormal SQIs [0,+∞) Number Number of abnormal SQI values BSC6900

in the SQI reports. V900R014C00
·A SQI value is abnormal if the (or later) or
SQI value of a call is below the BSC6910
SQI exception threshold. V100R014C00
(or later)
Set the exception threshold
when you create a task.

Proportion of [0.00,10 % Proportion of calls with BSC6900

Abnormal SQIs 0.00] abnormal SQI values. V900R014C00
·Proportion of calls with (or later) or
abnormal SQI values (%) = BSC6910
Number of calls with abnormal V100R014C00
SQI values/Number of (or later)
connected calls (Connect Ack) x
100%.

Proportion of [0.00,10 % Proportion of calls whose SQI is BSC6900

Voice Quality 0.00] Excellent during successful V900R014C00
with SQI as voice service initiation. (or later) or
Excellent This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)

Proportion of [0.00,10 % Proportion of calls whose SQI is BSC6900

Voice Quality 0.00] Good during successful voice V900R014C00
with SQI as service initiation. (or later) or
Good This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)

Proportion of [0.00,10 % Proportion of calls whose SQI is BSC6900

Voice Quality 0.00] Accept during successful voice V900R014C00
with SQI as service initiation. (or later) or
Accept This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 703

Parameter Range Unit Description Supported

NE Version

Proportion of [0.00,10 % Proportion of calls whose SQI is BSC6900

Voice Quality 0.00] Poor during successful voice V900R014C00
with SQI as service initiation. (or later) or
Poor This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)

Proportion of [0.00,10 % Proportion of calls whose SQI is BSC6900

Voice Quality 0.00] Bad during successful voice V900R014C00
with SQI as Bad service initiation. (or later) or
This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)

Proportion of [0.00,10 % Proportion of level 1 uplink BSC6900

Level 1 Uplink 0.00] BLER values upon successful V900R014C00
BLER call initiation. (or later) or
BLER is short for block error BSC6910
ratio. V100R014C00
(or later)
This parameter is applicable
only to the AMR service.
Standard for level 1: 0–0.78%.

Proportion of [0.00,10 % Proportion of level 2 uplink BSC6900

Level 2 Uplink 0.00] BLER values upon successful V900R014C00
BLER call initiation. (or later) or
This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)
Standard for level 2: 0.78%–
1.56%.

Proportion of [0.00,10 % Proportion of level 3 uplink BSC6900

Level 3 Uplink 0.00] BLER values upon successful V900R014C00
BLER call initiation. (or later) or
This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)
Standard for level 3: 1.56%–
3.12%

Proportion of [0.00,10 % Proportion of level 4 uplink BSC6900

Level 4 Uplink 0.00] BLER values upon successful V900R014C00
BLER call initiation. (or later) or
This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)
Standard for level 4: 3.12%–
6.24%.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 704

Parameter Range Unit Description Supported

NE Version

Proportion of [0.00,10 % Proportion of level 5 uplink BSC6900

Level 5 Uplink 0.00] BLER values upon successful V900R014C00
BLER call initiation. (or later) or
This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)
Standard for level 5: 6.24%–
12.48%.

Proportion of [0.00,10 % Proportion of level 6 uplink BSC6900

Level 6 Uplink 0.00] BLER values upon successful V900R014C00
BLER call initiation. (or later) or
This parameter is applicable BSC6910
only to the AMR service. V100R014C00
(or later)
Standard for level 6: above
12.48%.

RAN-CS/VP/Accessibility Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Same as the related counter in BSC6900

Requests "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0,+∞) Number Same as the related counter in BSC6900

Failures "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0,+∞) Number Same as the related counter in BSC6900

Success Times "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 705

Parameter Range Unit Description Supported NE

Version

RAB Setup [0.00,10 % Same as the related counter in BSC6900

Success Ratio 0.00] "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Call Connection [0,+∞) Number Same as the related counter in BSC6900

Acknowledgme "RAN-CS/AMR". V900R014C00
nt Success (or later) or
Times(Alerting) BSC6910
V100R014C00
(or later)

Call Connection [0,+∞) Number Same as the related counter in BSC6900

Acknowledgme "RAN-CS/AMR". V900R014C00
nt Success (or later) or
Times(Connect BSC6910
Ack) V100R014C00
(or later)

Abnormal [0,+∞) Number Same as the related counter in BSC6900

Release Times "RAN-CS/AMR". V900R014C00
Before (or later) or
Connection BSC6910
Acknowledgme V100R014C00
nt (or later)

RAN-CS/VP/Retainability Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Same as the related counter in BSC6900

Success Times "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Abnormal RAB [0,+∞) Number Same as the related counter in BSC6900

Release Times "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 706

Parameter Range Unit Description Supported NE

Version

Abnormal RAB [0.00,10 % Same as the related counter in BSC6900

Release Ratio 0.00] "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAN-CS/VP/Delay Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Same as the related counter in BSC6900

Success Times "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Average RAB [0,+∞) Second Same as the related counter in BSC6900

Setup Delay "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Overlong RAB [0,+∞) Number Same as the related counter in BSC6900

Setup Delay "RAN-CS/AMR". V900R014C00
Times (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00,10 % Same as the related counter in BSC6900

Overlong RAB 0.00] "RAN-CS/AMR". V900R014C00
Setup Delay (or later) or
BSC6910
V100R014C00
(or later)

Call Setup [0,+∞) Number Same as the related counter in BSC6900

Delay Times "RAN-CS/AMR". V900R014C00
(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 707

Parameter Range Unit Description Supported NE

Version

Average Call [0,+∞) Second Same as the related counter in BSC6900

Setup Delay "RAN-CS/AMR". V900R014C00
(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Overlong Call [0,+∞) Number Same as the related counter in BSC6900

Setup Delay "RAN-CS/AMR". V900R014C00
Times(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00,10 % Same as the related counter in BSC6900

Overlong Call 0.00] "RAN-CS/AMR". V900R014C00
Setup Delay (or later) or
(MOC) BSC6910
V100R014C00
(or later)

Call Setup [0,+∞) Number Same as the related counter in BSC6900

Delay Times "RAN-CS/AMR". V900R014C00
(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Average Call [0,+∞) Second Same as the related counter in BSC6900

Setup Delay "RAN-CS/AMR". V900R014C00
(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Overlong Call [0,+∞) Number Same as the related counter in BSC6900

Setup Delay "RAN-CS/AMR". V900R014C00
Times(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00,10 % Same as the related counter in BSC6900

Overlong Call 0.00] "RAN-CS/AMR". V900R014C00
Setup Delay (or later) or
(MTC) BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 708

Parameter Range Unit Description Supported NE

Version

Call Connection [0,+∞) Number Same as the related counter in BSC6900

Acknowledgme "RAN-CS/AMR". V900R014C00
nt Success (or later) or
Times(Alerting) BSC6910
(MOC) V100R014C00
(or later)

Average Call [0,+∞) Second Same as the related counter in BSC6900

Connection "RAN-CS/AMR". V900R014C00
Acknowledgme (or later) or
nt Delay BSC6910
(Alerting) V100R014C00
(MOC) (or later)

Overlong Call [0,+∞) Number Same as the related counter in BSC6900

Connection "RAN-CS/AMR". V900R014C00
Acknowledgme (or later) or
nt Delay Times BSC6910
(Alerting) V100R014C00
(MOC) (or later)

Proportion of [0.00,10 % Same as the related counter in BSC6900

Overlong Call 0.00] "RAN-CS/AMR". V900R014C00
Connection (or later) or
Acknowledgme BSC6910
nt Delay V100R014C00
(Alerting) (or later)
(MOC)

Call Connection [0,+∞) Number Same as the related counter in BSC6900

Acknowledgme "RAN-CS/AMR". V900R014C00
nt Success (or later) or
Times(Connect BSC6910
Ack)(MOC) V100R014C00
(or later)

Average Call [0,+∞) Second Same as the related counter in BSC6900

Connection "RAN-CS/AMR". V900R014C00
Acknowledgme (or later) or
nt Delay BSC6910
(Connect Ack) V100R014C00
(MOC) (or later)

Overlong Call [0,+∞) Number Same as the related counter in BSC6900

Connection "RAN-CS/AMR". V900R014C00
Acknowledgme (or later) or
nt Delay Times BSC6910
(Connect Ack) V100R014C00
(MOC) (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 709

Parameter Range Unit Description Supported NE

Version

Proportion of [0.00,10 % Same as the related counter in BSC6900

Overlong Call 0.00] "RAN-CS/AMR". V900R014C00
Connection (or later) or
Acknowledgme BSC6910
nt Delay V100R014C00
(Connect Ack) (or later)
(MOC)

Call Connection [0,+∞) Number Same as the related counter in BSC6900

Acknowledgme "RAN-CS/AMR". V900R014C00
nt Success (or later) or
Times(Alerting) BSC6910
(MTC) V100R014C00
(or later)

Average Call [0,+∞) Second Same as the related counter in BSC6900

Connection "RAN-CS/AMR". V900R014C00
Acknowledgme (or later) or
nt Delay BSC6910
(Alerting) V100R014C00
(MTC) (or later)

Overlong Call [0,+∞) Number Same as the related counter in BSC6900

Connection "RAN-CS/AMR". V900R014C00
Acknowledgme (or later) or
nt Delay Times BSC6910
(Alerting) V100R014C00
(MTC) (or later)

Proportion of [0.00,10 % Same as the related counter in BSC6900

Overlong Call 0.00] "RAN-CS/AMR". V900R014C00
Connection (or later) or
Acknowledgme BSC6910
nt Delay V100R014C00
(Alerting) (or later)
(MTC)

Call Connection [0,+∞) Number Same as the related counter in BSC6900

Acknowledgme "RAN-CS/AMR". V900R014C00
nt Success (or later) or
Times(Connect BSC6910
Ack)(MTC) V100R014C00
(or later)

Average Call [0,+∞) Second Same as the related counter in BSC6900

Connection "RAN-CS/AMR". V900R014C00
Acknowledgme (or later) or
nt Delay BSC6910
(Connect Ack) V100R014C00
(MTC) (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 710

Parameter Range Unit Description Supported NE

Version

Overlong Call [0,+∞) Number Same as the related counter in BSC6900

Connection "RAN-CS/AMR". V900R014C00
Acknowledgme (or later) or
nt Delay Times BSC6910
(Connect Ack) V100R014C00
(MTC) (or later)

Proportion of [0.00,10 % Same as the related counter in BSC6900

Overlong Call 0.00] "RAN-CS/AMR". V900R014C00
Connection (or later) or
Acknowledgme BSC6910
nt Delay V100R014C00
(Connect Ack) (or later)
(MTC)

Average RAB [0,+∞) Second Same as the related counter in BSC6900

Service "RAN-CS/AMR". V900R014C00
Duration (or later) or
BSC6910
V100R014C00
(or later)

Overshort RAB [0,+∞) Number Same as the related counter in BSC6900

Service "RAN-CS/AMR". V900R014C00
Duration Times (or later) or
BSC6910
V100R014C00
(or later)

Average Service [0,+∞) Second Same as the related counter in BSC6900

Duration(MOC) "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Number of [0,+∞) Number Same as the related counter in BSC6900

Short Calls "RAN-CS/AMR". V900R014C00
(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00,10 % Same as the related counter in BSC6900

Short Calls 0.00] "RAN-CS/AMR". V900R014C00
(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 711

Parameter Range Unit Description Supported NE

Version

Average Service [0,+∞) Second Same as the related counter in BSC6900

Duration(MTC) "RAN-CS/AMR". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Number of [0,+∞) Number Same as the related counter in BSC6900

Short Calls "RAN-CS/AMR". V900R014C00
(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00,10 % Same as the related counter in BSC6900

Short Calls 0.00] "RAN-CS/AMR". V900R014C00
(MTC) (or later) or
BSC6910
V100R014C00
(or later)

RAN-CS/SMS/Accessibility Evaluation
Parameter Range Unit Description Supported
NE Version

Setup Requests [0,+∞) Number Number of SMS service setup BSC6900

(MOC) requests initiated by the mobile- V900R014C00
terminated party. (or later) or
BSC6910
V100R014C00
(or later)

Setup Failures [0,+∞) Number Number of failed SMS service BSC6900

(MOC) setups initiated by the mobile- V900R014C00
originated party. (or later) or
BSC6910
V100R014C00
(or later)

Setup Success [0.00,10 % Number of successful SMS BSC6900

Ratio (MOC) 0.00] service setups initiated by the V900R014C00
mobile-originated party. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 712

Parameter Range Unit Description Supported

NE Version

Setup Requests [0,+∞) Number Number of SMS service setup BSC6900

(MTC) requests initiated by the mobile- V900R014C00
terminated party. (or later) or
BSC6910
V100R014C00
(or later)

Setup Failures [0,+∞) Number Number of failed SMS service BSC6900

(MTC) setups initiated by the mobile- V900R014C00
terminated party. (or later) or
BSC6910
V100R014C00
(or later)

Setup Success [0.00,10 % Number of successful SMS BSC6900

Ratio (MTC) 0.00] service setups initiated by the V900R014C00
mobile-terminated party. (or later) or
BSC6910
V100R014C00
(or later)

Parameters for Viewing UMTS VIP Analysis - RAN PS Results

This section describes the parameters for querying UMTS VIP analysis - RAN PS results. You
can refer to the description when querying UMTS VIP analysis - RAN PS results.

NOTE

UMTS PS service types include PS-ALL, R99, HSDPA, HSUPA, and HSPA. PS-ALL covers all R99, HSDPA,
HSUPA, and HSPA services, which means that PS-ALL-related counters are calculated with all UMTS PS
services taken into account.

RAN-PS/PS R99/Accessibility Evaluation

Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Numb Number of RAB setup requests BSC6900

Requests er initiated by a VIP subscriber after V900R014C00
network access. (or later) or
RAB is short for radio access BSC6910
bearer. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 713

Parameter Range Unit Description Supported NE

Version

RAB Setup [0,+∞) Numb Number of RAB setup failures BSC6900

Failures er experienced by a VIP subscriber V900R014C00
after network access. (or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0,+∞) Numb Number of successful RAB setups BSC6900

Success Times er experienced by a VIP subscriber V900R014C00
after network access. (or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0.00,1 % RAB setup success ratio BSC6900

Success Ratio 00.00] experienced by a VIP subscriber V900R014C00
after network access. (or later) or
RAB setup success ratio = Number BSC6910
of successful RAB setups/Number V100R014C00
of RAB setup requests x 100%. (or later)

RAN-PS/PS R99/Retainability Evaluation

Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Numb See RAB Setup Success Times in BSC6900
Success Times er RAN-PS/PS R99/Accessibility V900R014C00
Evaluation. (or later) or
BSC6910
V100R014C00
(or later)

Abnormal RAB [0,+∞) Numb Number of times that a VIP BSC6900

Release Times er subscriber abnormally releases an V900R014C00
RAB after network access and (or later) or
successful service initiation. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 714

Parameter Range Unit Description Supported NE

Version

Abnormal RAB [0.00,1 % Proportion of abnormal RAB BSC6900

Release Ratio 00.00] releases experienced by a VIP V900R014C00
subscriber after network access (or later) or
and successful service initiation. BSC6910
Proportion of abnormal RAB V100R014C00
releases = Number of abnormal (or later)
RAB releases/Number of
successful call setups x 100%.

RAN-PS/PS R99/Delay Evaluation

Parameter Range Unit Description Supported NE
Version

RAB Setup [0, Numb Number of successful RAB setups BSC6900

Success Times +∞) er during call initiation, that is, V900R014C00
number of RAB setup delays. (or later) or
BSC6910
V100R014C00
(or later)

Average RAB [0, Secon Average RAB setup delay during BSC6900
Setup Delay +∞) d call initiation. V900R014C00
·Average RAB setup delay = Sum (or later) or
of RAB setup delays/Number of BSC6910
RAB setup delays. V100R014C00
(or later)
·RAB setup delay = RAB request
connection acknowledge time –
RAB setup request time.
·Statistical point for RAB request
connection acknowledge time:
When the RAB assignment
procedure is successful, namely,
when the SRNC sends a Radio
Access Bearer Assignment
Response message to the CN after
it receives an RAB setup
connection acknowledge message.
·Statistical point for RAB setup
request time: When the UTRAN
receives a Radio Access Bearer
Assignment Request message
from the CN.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 715

Parameter Range Unit Description Supported NE

Version

Overlong RAB [0, Numb Number of times that the RAB BSC6900
Setup Delay +∞) er setup delay during call initiation is V900R014C00
Times overlong (or later) or
Set the overlong delay threshold BSC6910
when you create a task. V100R014C00
(or later)

Proportion of [0.00,1 % Proportion of times that the RAB BSC6900

Overlong RAB 00.00] setup delay during call initiation is V900R014C00
Setup Delay overlong. (or later) or
Proportion of overlong RAB setup BSC6910
delays = Number of overlong RAB V100R014C00
setup delays/Number of RAB (or later)
setup delays x 100% = Number of
overlong RAB setup delays/
Number of successful RAB setups
x 100%.

Call Setup [0, Numb Number of times that the call setup BSC6900
Delay Times +∞) er delay of the mobile-originated V900R014C00
(MOC) party upon successful call (or later) or
initiation is overlong. BSC6910
V100R014C00
(or later)

Average Call [0, Secon Average call delay of the mobile- BSC6900
Setup Delay +∞) d originated party upon successful V900R014C00
(MOC) call initiation. (or later) or
BSC6910
V100R014C00
(or later)

Overlong RAB [0, Numb Number of times that the call setup BSC6900
Setup Delay +∞) er delay of the mobile-originated V900R014C00
Times(MOC) party upon successful call (or later) or
initiation is overlong. BSC6910
Set the overlong delay threshold V100R014C00
when you create a task. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 716

Parameter Range Unit Description Supported NE

Version

Proportion of [0.00,1 % Proportion of overlong call setup BSC6900

Overlong Call 00.00] delays of the mobile-originated V900R014C00
Setup Delay party upon successful call (or later) or
(MOC) initiation. BSC6910
·Proportion of overlong call setup V100R014C00
delays (mobile-originated) = (or later)
Number of overlong call setup
delays (mobile-originated)/
Number of call setup delays
(mobile-originated) x 100% =
Number of overlong call setup
delays (mobile-originated)/
Number of successful RRC
connection setups x 100%.

Call Setup [0, Numb Number of times that the call setup BSC6900
Delay Times +∞) er delay of the mobile-terminated V900R014C00
(MTC) upon successful call initiation is (or later) or
abnormal. BSC6910
V100R014C00
(or later)

Average Call [0, Secon Average call setup delay of the BSC6900
Setup Delay +∞) d mobile-terminated upon V900R014C00
(MTC) successful call initiation. (or later) or
·Average call setup delay =Sum of BSC6910
call setup delays/Number of call V100R014C00
setup delays. (or later)

·Call setup delay = RAB request

connection acknowledge time –
Signaling access time.
·Statistical point for RAB request
connection acknowledge time:
When the RAB assignment
procedure is successful, namely,
when the SRNC sends a Radio
Access Bearer Assignment
Response message to the CN after
it receives an RAB setup
connection acknowledge message.
·Statistical point for signaling
access time: When an RRC
SETUP REQ or RELOC REQ
message is received or when an
incoming inter-RAT handover
request is initiated.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 717

Parameter Range Unit Description Supported NE

Version

Overlong Call [0, Numb Number of times that the call setup BSC6900
Setup Delay +∞) er delay of the mobile-terminated V900R014C00
Times(MTC) party upon successful call (or later) or
initiation is overlong. BSC6910
Set the overlong delay threshold V100R014C00
when you create a task. (or later)

Proportion of [0.00,1 % Proportion of overlong call setup BSC6900

Overlong Call 00.00] delays experienced by the mobile- V900R014C00
Setup Delay terminated party upon successful (or later) or
(MTC) call initiation. BSC6910
Proportion of overlong call setup V100R014C00
delays = Number of overlong call (or later)
setup delays/Number of call setup
delays x 100% = Number of
overlong call setup delays/Number
of successful RRC connection
setups x 100%.

Average RAB [0, Secon Average RAB duration upon BSC6900

Service +∞) d successful call initiation. V900R014C00
Duration ·Average RAB duration = RAB (or later) or
duration/Number of RAB BSC6910
durations. V100R014C00
(or later)
·RAB duration = RAB release time
– RAB request connection
acknowledge time.
·Statistical point for RAB release
time: When a UE is released; when
the IU REL CMD message is
received (which indicates a normal
release); or when the RB REL
SUCC message is received.
·Statistical point for RAB request
connection acknowledge time:
When the RAB assignment
procedure is successful, after
receiving an RAB setup
connection acknowledge message,
the SRNC sends a Radio Access
Bearer Assignment Response
message to the CN.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 718

RAN-PS/PS R99/Rate Evaluation

Parameter Rang Unit Description Supported NE
e Version

Final Average [0.00, kbit/s Final negotiated rate of downlink BSC6900

Negotiated +∞) RAB when a VIP subscriber V900R014C00
Downlink RAB initiates a common PS service. (or later) or
Rate Average final negotiated rate of BSC6910
downlink RAB = Final negotiated V100R014C00
rate of downlink RAB/Number of (or later)
times for collecting the final
negotiated rate of downlink RAB.

Final Average [0.00, kbit/s Final negotiated rate of uplink BSC6900

Negotiated +∞) RAB when a VIP subscriber V900R014C00
Uplink RAB initiates a common PS service. (or later) or
Rate Average final negotiated rate of BSC6910
uplink RAB = Final negotiated V100R014C00
rate of uplink RAB/Number of (or later)
times for collecting the final
negotiated rate of uplink RAB.

Downlink [0, KB Downlink traffic volume of all BSC6900

Traffic Volume +∞) common PS services. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Average [0, Second Average downlink transmission BSC6900

Downlink +∞) duration for all common PS V900R014C00
Transmission services. (or later) or
Duration BSC6910
V100R014C00
(or later)

Average [0.00, kbit/s Average downlink throughput for BSC6900

Downlink +∞) all common PS services. V900R014C00
Throughput Average downlink throughput = (or later) or
Downlink traffic volume/ BSC6910
Downlink data transmission V100R014C00
duration. (or later)

Low Average [0, Numbe Number of times that among all BSC6900
Downlink +∞) r common PS services, the average V900R014C00
Throughput downlink throughput for one RAB (or later) or
Times setup is below a threshold for low BSC6910
average downlink throughput. V100R014C00
Set the exception threshold when (or later)
you create a task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 719

Parameter Rang Unit Description Supported NE

e Version

Uplink Traffic [0, KB Uplink traffic volume for all BSC6900

Volume +∞) common PS services. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Average Uplink [0, Second Average uplink transmission BSC6900

Transmission +∞) duration for all common PS V900R014C00
Duration services. (or later) or
BSC6910
V100R014C00
(or later)

Average Uplink [0.00, kbit/s Average uplink throughput rate for BSC6900
Throughput +∞) all common PS services. V900R014C00
Average uplink throughput = Total (or later) or
uplink traffic volume/Total uplink BSC6910
transmission duration V100R014C00
(or later)

Low Average [0, Numbe Number of times that among all BSC6900
Uplink +∞) r common PS services, the average V900R014C00
Throughput uplink throughput for one RAB (or later) or
Times setup is below a threshold for low BSC6910
average uplink throughput. V100R014C00
Set the exception threshold when (or later)
you create a task.

RAN-PS/PS R99/Quality Evaluation

Parameter Rang Unit Description Supported NE
e Version

Proportion of [0.00, % Proportion of level 1 uplink BLER BSC6900

Level 1 Uplink 100.00 values upon successful call V900R014C00
BLER ] initiation. (or later) or
This parameter is applicable only BSC6910
to the PS service. V100R014C00
(or later)
Standard for level 1: 0 =< X
=< 0.39%.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 720

Parameter Rang Unit Description Supported NE

e Version

Proportion of [0.00, % Proportion of level 2 uplink BLER BSC6900

Level 2 Uplink 100.00 values upon successful call V900R014C00
BLER ] initiation. (or later) or
This parameter is applicable only BSC6910
to the PS service. V100R014C00
(or later)
Standard for level 2: 0.39% < X
=< 0.78%.

Proportion of [0.00, % Proportion of level 3 uplink BLER BSC6900

Level 3 Uplink 100.00 values upon successful call V900R014C00
BLER ] initiation. (or later) or
This parameter is applicable only BSC6910
to the PS service. V100R014C00
(or later)
Standard for level 3: 0.78% < X
=< 3.12%.

Proportion of [0.00, % Proportion of level 4 uplink BLER BSC6900

Level 4 Uplink 100.00 values upon successful call V900R014C00
BLER ] initiation. (or later) or
This parameter is applicable only BSC6910
to the PS service. V100R014C00
(or later)
Standard for level 4: 3.12% < X
=< 6.24%.

Proportion of [0.00, % Proportion of level 5 uplink BLER BSC6900

Level 5 Uplink 100.00 values upon successful call V900R014C00
BLER ] initiation. (or later) or
This parameter is applicable only BSC6910
to the PS service. V100R014C00
(or later)
Standard for level 5: 6.24% < X
=< 12.48%.

Proportion of [0.00, % Proportion of level 6 uplink BLER BSC6900

Level 6 Uplink 100.00 values upon successful call V900R014C00
BLER ] initiation. (or later) or
This parameter is applicable only BSC6910
to the PS service. V100R014C00
(or later)
Standard for level 6: 12.48% <
X.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 721

RAN-PS/HSDPA/Accessibility Evaluation
Parameter Rang Unit Description Supported NE
e Version

RAB Setup [0, Numbe Same as the related counter in BSC6900

Requests +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0, Numbe Same as the related counter in BSC6900

Failures +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0, Numbe Same as the related counter in BSC6900

Success Times +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0.00,1 % Same as the related counter in BSC6900

Success Ratio 00.00] "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAN-PS/HSDPA/Retainability Evaluation
Parameter Rang Unit Description Supported NE
e Version

RAB Setup [0, Numbe Same as the related counter in BSC6900

Success Times +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Abnormal RAB [0, Numbe Same as the related counter in BSC6900

Release Times +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 722

Parameter Rang Unit Description Supported NE

e Version

Abnormal RAB [0.00, % Same as the related counter in BSC6900

Release Ratio 100.00 "RAN-PS/PS R99". V900R014C00
] (or later) or
BSC6910
V100R014C00
(or later)

RAN-PS/HSDPA/Delay Evaluation
Parameter Rang Unit Description Supported NE
e Version

RAB Setup [0, Numbe Same as the related counter in BSC6900

Success Times +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Average RAB [0, Second Same as the related counter in BSC6900

Setup Delay +∞) "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Overlong RAB [0, Numbe Same as the related counter in BSC6900

Setup Delay +∞) r "RAN-PS/PS R99". V900R014C00
Times (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00, % Same as the related counter in BSC6900

Overlong RAB 100.00 "RAN-PS/PS R99". V900R014C00
Setup Delay ] (or later) or
BSC6910
V100R014C00
(or later)

Call Setup [0, Numbe Same as the related counter in BSC6900

Delay Times +∞) r "RAN-PS/PS R99". V900R014C00
(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 723

Parameter Rang Unit Description Supported NE

e Version

Average Call [0, Second Same as the related counter in BSC6900

Setup Delay +∞) "RAN-PS/PS R99". V900R014C00
(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Overlong Call [0, Numbe Same as the related counter in BSC6900

Setup Delay +∞) r "RAN-PS/PS R99". V900R014C00
Times(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00, % Same as the related counter in BSC6900

Overlong Call 100.00 "RAN-PS/PS R99". V900R014C00
Setup Delay ] (or later) or
(MOC) BSC6910
V100R014C00
(or later)

Call Setup [0, Numbe Same as the related counter in BSC6900

Delay Times +∞) r "RAN-PS/PS R99". V900R014C00
(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Average Call [0, Second Same as the related counter in BSC6900

Setup Delay +∞) "RAN-PS/PS R99". V900R014C00
(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Overlong Call [0, Numbe Same as the related counter in BSC6900

Setup Delay +∞) r "RAN-PS/PS R99". V900R014C00
Times(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00, % Same as the related counter in BSC6900

Overlong Call 100.00 "RAN-PS/PS R99". V900R014C00
Setup Delay ] (or later) or
(MTC) BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 724

Parameter Rang Unit Description Supported NE

e Version

Average RAB [0, Second Same as the related counter in BSC6900

Service +∞) "RAN-PS/PS R99". V900R014C00
Duration (or later) or
BSC6910
V100R014C00
(or later)

RAN-PS/HSDPA/Rate Evaluation
Parameter Rang Unit Description Supported NE
e Version

Downlink [0, KB Same as the related counter in BSC6900

Traffic Volume +∞) "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Average [0, Second Same as the related counter in BSC6900

Downlink +∞) "RAN-PS/PS R99". V900R014C00
Transmission (or later) or
Duration BSC6910
V100R014C00
(or later)

Average [0.00, kbit/s Same as the related counter in BSC6900

Downlink +∞) "RAN-PS/PS R99". V900R014C00
Throughput (or later) or
BSC6910
V100R014C00
(or later)

Low Average [0, Numbe Same as the related counter in BSC6900

Downlink +∞) r "RAN-PS/PS R99". V900R014C00
Throughput (or later) or
Times BSC6910
V100R014C00
(or later)

Average [0.00, kbit/s Average downlink rate for all BSC6900

HSDPA +∞) HSDPA services. V900R014C00
Downlink Rate (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 725

Parameter Rang Unit Description Supported NE

e Version

Low Average [0, Numbe Number of times that the average BSC6900
HSDPA +∞) r downlink rate for all HSDPA V900R014C00
Downlink Rate services is low. (or later) or
Times Set the threshold for low average BSC6910
rate when you create a task. V100R014C00
(or later)

Average [0.00, kbit/s Average downlink rate for all BSC6900

HSDPA +∞) HSDPA services when service V900R014C00
Downlink Rate resources are sufficient. (or later) or
with Sufficient BSC6910
Resources V100R014C00
(or later)

Times of Low [0, Numbe Number of times that the average BSC6900
Average +∞) r downlink rate for all HSDPA V900R014C00
HSDPA services is low when service (or later) or
Downlink Rate resources are sufficient. BSC6910
with Sufficient Set the threshold for low average V100R014C00
Resources rate when you create a task. (or later)

Average [0.00, kbit/s Average downlink rate for all BSC6900

HSDPA +∞) HSDPA services when service V900R014C00
Downlink Rate resources are insufficient. (or later) or
with BSC6910
Insufficient V100R014C00
Resources (or later)

Times of Low [0, Numbe Number of times that the average BSC6900
Average +∞) r downlink rate for all HSDPA V900R014C00
HSDPA services is low when service (or later) or
Downlink Rate resources are insufficient. BSC6910
with Set the threshold for low average V100R014C00
Insufficient rate when you create a task. (or later)
Resources

RAN-PS/HSUPA/Accessibility Evaluation
Parameter Rang Unit Description Supported NE
e Version

RAB Setup [0, Numbe Same as the related counter in BSC6900

Requests +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 726

Parameter Rang Unit Description Supported NE

e Version

RAB Setup [0, Numbe Same as the related counter in BSC6900

Failures +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0, Numbe Same as the related counter in BSC6900

Success Times +∞) r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAB Setup [0.00,1 % Same as the related counter in BSC6900

Success Ratio 00.00] "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RAN-PS/HSUPA/Retainability Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Numbe Same as the related counter in BSC6900

Success Times r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Abnormal RAB [0,+∞) Numbe Same as the related counter in BSC6900

Release Times r "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Abnormal RAB [0.00,1 % Same as the related counter in BSC6900

Release Ratio 00.00] "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 727

RAN-PS/HSUPA/Delay Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Numb Same as the related counter in BSC6900

Success Times er "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Average RAB [0,+∞) Secon Same as the related counter in BSC6900

Setup Delay d "RAN-PS/PS R99". V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Overlong RAB [0,+∞) Numb Same as the related counter in BSC6900

Setup Delay er "RAN-PS/PS R99". V900R014C00
Times (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00,1 % Same as the related counter in BSC6900

Overlong RAB 00.00] "RAN-PS/PS R99". V900R014C00
Setup Delay (or later) or
BSC6910
V100R014C00
(or later)

Call Setup [0,+∞) Numb Same as the related counter in BSC6900

Delay Times er "RAN-PS/PS R99". V900R014C00
(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Average Call [0,+∞) Secon Same as the related counter in BSC6900

Setup Delay d "RAN-PS/PS R99". V900R014C00
(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Overlong Call [0,+∞) Numb Same as the related counter in BSC6900

Setup Delay er "RAN-PS/PS R99". V900R014C00
Times(MOC) (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 728

Parameter Range Unit Description Supported NE

Version

Proportion of [0.00,1 % Same as the related counter in BSC6900

Overlong Call 00.00] "RAN-PS/PS R99". V900R014C00
Setup Delay (or later) or
(MOC) BSC6910
V100R014C00
(or later)

Call Setup [0,+∞) Numb Same as the related counter in BSC6900

Delay Times er "RAN-PS/PS R99". V900R014C00
(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Average Call [0,+∞) Secon Same as the related counter in BSC6900

Setup Delay d "RAN-PS/PS R99". V900R014C00
(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Overlong Call [0,+∞) Numb Same as the related counter in BSC6900

Setup Delay er "RAN-PS/PS R99". V900R014C00
Times(MTC) (or later) or
BSC6910
V100R014C00
(or later)

Proportion of [0.00,1 % Same as the related counter in BSC6900

Overlong Call 00.00] "RAN-PS/PS R99". V900R014C00
Setup Delay (or later) or
BSC6910
V100R014C00
(or later)

Average RAB [0,+∞) Secon Same as the related counter in BSC6900

Service d "RAN-PS/PS R99". V900R014C00
Duration (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 729

RAN-PS/HSUPA/Rate Evaluation
Parameter Range Unit Description Supported NE
Version

Uplink Traffic [0,+∞) KB Same as the BSC6900

Volume related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Average Uplink [0,+∞) Second Same as the BSC6900

Transmission related counter V900R014C00
Duration in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Average Uplink [0.00,+∞) kbit/s Same as the BSC6900

Throughput related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Low Average [0,+∞) Number Same as the BSC6900

Uplink related counter V900R014C00
Throughput in "RAN-PS/PS (or later) or
Times R99". BSC6910
V100R014C00
(or later)

RAN-PS/HSPA/Accessibility Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Same as the BSC6900

Requests related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

RAB Setup [0,+∞) Number Same as the BSC6900

Failures related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 730

Parameter Range Unit Description Supported NE

Version

RAB Setup [0,+∞) Number Same as the BSC6900

Success Times related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

RAB Setup [0.00,100.00] % Same as the BSC6900

Success Ratio related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

RAN-PS/HSPA/Retainability Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Same as the BSC6900

Success Times related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Abnormal RAB [0,+∞) Number Same as the BSC6900

Release Times related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Abnormal RAB [0.00,100.00] % Same as the BSC6900

Release Ratio related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 731

RAN-PS/HSPA/Delay Evaluation
Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Same as the BSC6900

Success Times related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Average RAB [0,+∞) Second Same as the BSC6900

Setup Delay related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Overlong RAB [0,+∞) Number Same as the BSC6900

Setup Delay related counter V900R014C00
Times in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Proportion of [0.00,100.00] % Same as the BSC6900

Overlong RAB related counter V900R014C00
Setup Delay in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Call Setup [0,+∞) Number Same as the BSC6900

Delay Times related counter V900R014C00
(MOC) in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Average Call [0,+∞) Second Same as the BSC6900

Setup Delay related counter V900R014C00
(MOC) in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Overlong Call [0,+∞) Number Same as the BSC6900

Setup Delay related counter V900R014C00
Times(MOC) in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 732

Parameter Range Unit Description Supported NE

Version

Proportion of [0.00,100.00] % Same as the BSC6900

Overlong Call related counter V900R014C00
Setup Delay in "RAN-PS/PS (or later) or
(MOC) R99". BSC6910
V100R014C00
(or later)

Call Setup [0,+∞) Number Same as the BSC6900

Delay Times related counter V900R014C00
(MTC) in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Average Call [0,+∞) Second Same as the BSC6900

Setup Delay related counter V900R014C00
(MTC) in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Overlong Call [0,+∞) Number Same as the BSC6900

Setup Delay related counter V900R014C00
Times(MTC) in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Proportion of [0.00,100.00] % Same as the BSC6900

Overlong Call related counter V900R014C00
Setup Delay in "RAN-PS/PS (or later) or
(MTC) R99". BSC6910
V100R014C00
(or later)

Average RAB [0,+∞) Second Same as the BSC6900

Service related counter V900R014C00
Duration in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 733

RAN-PS/HSPA/Rate Evaluation
Parameter Range Unit Description Supported NE
Version

Downlink [0,+∞) KB Same as the BSC6900

Traffic Volume related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Average [0,+∞) Second Same as the BSC6900

Downlink related counter V900R014C00
Transmission in "RAN-PS/PS (or later) or
Duration R99". BSC6910
V100R014C00
(or later)

Average [0.00,+∞) kbit/s Same as the BSC6900

Downlink related counter V900R014C00
Throughput in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Low Average [0,+∞) Number Same as the BSC6900

Downlink related counter V900R014C00
Throughput in "RAN-PS/PS (or later) or
Times R99". BSC6910
V100R014C00
(or later)

Uplink Traffic [0,+∞) KB Same as the BSC6900

Volume related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Average Uplink [0,+∞) Second Same as the BSC6900

Transmission related counter V900R014C00
Duration in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Average Uplink [0.00,+∞) kbit/s Same as the BSC6900

Throughput related counter V900R014C00
in "RAN-PS/PS (or later) or
R99". BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 734

Parameter Range Unit Description Supported NE

Version

Low Average [0,+∞) Number Same as the BSC6900

Uplink related counter V900R014C00
Throughput in "RAN-PS/PS (or later) or
Times R99". BSC6910
V100R014C00
(or later)

Parameters for Viewing UMTS VIP Analysis - Multi Service Results

This section describes the parameters for querying UMTS VIP Analysis - Multi Service results,
You can refer to the description when querying umts vip analysis - multi service results.

RAN INTEGRATED/MULTI-RAB/Accessibility Evaluation

Par Ra U Description Supported NE Version
am ng n
eter e i
t

Mul [0, N Number of RAB setup requests BSC6900 V900R014C00 (or later)
ti- + u where multiple RABs are accessed or BSC6910 V100R014C00 (or
RA ∞) m during a call. later)
B b
Setu e
p r
Req
uest
s

Mul [0, N Number of RAB setup failures BSC6900 V900R014C00 (or later)
ti- + u where multiple RABs are accessed or BSC6910 V100R014C00 (or
RA ∞) m during a call. later)
B b
Setu e
p r
Fail
ures

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 735

Par Ra U Description Supported NE Version

am ng n
eter e i
t

Mul [0. % Setup success ratio for accessing BSC6900 V900R014C00 (or later)
ti- 00, multiple RABs during a call. or BSC6910 V100R014C00 (or
RA 10 later)
B 0.0
Setu 0]
p
Suc
cess
Rati
o

RAN INTEGRATED/MULTI-RAB/Retainability Evaluation-With CS

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Mul [ N Number of RAB releases where BSC6900 V900R014C00 (or later) or

ti- 0 u multiple CS RABs that contain at BSC6910 V100R014C00 (or later)
RA , m least one CS RAB are released during
B + b a call.
Rele ∞ e
ase ) r
Tim
es

Abn [ N Number of abnormal RAB releases BSC6900 V900R014C00 (or later) or

orm 0 u where multiple CS RABs that contain BSC6910 V100R014C00 (or later)
al , m at least one CS RAB are released at a
Mul + b time during a call.
ti- ∞ e
RA ) r
B
Rele
ase
Tim
es

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 736

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Abn [ % Abnormal RAB release ratio for BSC6900 V900R014C00 (or later) or
orm 0 releasing multiple RABs that contain BSC6910 V100R014C00 (or later)
al . at least one CS RAB at a time during
Mul 0 a call.
ti- 0
RA ,
B 1
Rele 0
ase 0
Rati .
o 0
0
]

RAN INTEGRATED/MULTI-RAB/Retainability Evaluation-Only PS

Par R U Description Supported NE Version
am a n
eter n i
g t
e

Mul [ N Number of RAB releases where BSC6900 V900R014C00 (or later) or

ti- 0 u multiple RABs that contain only PS BSC6910 V100R014C00 (or later)
RA , m RABs are released during a call.
B + b
Rele ∞ e
ase ) r
Tim
es

Abn [ N Number of abnormal RAB releases BSC6900 V900R014C00 (or later) or

orm 0 u where multiple RABs that contain BSC6910 V100R014C00 (or later)
al , m only PS RABs are released during a
Mul + b call.
ti- ∞ e
RA ) r
B
Rele
ase
Tim
es

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 737

Par R U Description Supported NE Version

am a n
eter n i
g t
e

Abn [ % Abnormal RAB release ratio for BSC6900 V900R014C00 (or later) or
orm 0 releasing multiple RABs that contain BSC6910 V100R014C00 (or later)
al . only PS RABs during a call.
Mul 0
ti- 0
RA ,
B 1
Rele 0
ase 0
Rati .
o 0
0
]

Parameters for Viewing UMTS VIP Analysis - Active Cell Results

This section describes the parameters for querying UMTS VIP Analysis - Active Cell results.
You can refer to the description when querying umts vip analysis - active cell results.

Active Cell/Common
Paramete Range Unit Description Supported NE
r Version

RNC ID [0,4095] N/A ID of the RNC to which BSC6900

an active cell belongs. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

RNC N/A N/A Name of the RNC to BSC6900

Name which an active cell V900R014C00 (or
belongs. later) or BSC6910
Note: when name V100R014C00 (or
information cannot be later)
obtained because
configuration
information has been
deleted or cell
information has not
been activated,
Undefined is displayed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 738

Paramete Range Unit Description Supported NE

r Version

Cell ID [0,65535] N/A ID of an active cell. BSC6900

V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Cell Name 1 to 64 N/A Name of an active cell. BSC6900

characters Note: when name V900R014C00 (or
information cannot be later) or BSC6910
obtained because V100R014C00 (or
configuration later)
information has been
deleted or cell
information has not
been activated,
Undefined is displayed.

Service N/A N/A Service type for a BSC6900

Type counter. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Active Cell/RAN NET/NET/Accessibility

Parameter Range Unit Description Supported NE
Version

RRC Setup [0,+∞) Number Number of non- BSC6900

Requests(Non- service setup V900R014C00 (or
Service) requests that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber initiates later)
in an active cell.

Abnormal TPs [0,+∞) Number Number of times BSC6900

on Access that the TP value is V900R014C00 (or
abnormal when a later) or BSC6910
VIP group or VIP V100R014C00 (or
subscriber gains later)
access to the
network in an
active cell.
Set the exception
threshold when
you create a task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 739

Parameter Range Unit Description Supported NE

Version

Abnormal Ec/ [0,+∞) Number Number of times BSC6900

Nos on Access that the Ec/No V900R014C00 (or
value is abnormal later) or BSC6910
when a VIP group V100R014C00 (or
or VIP subscriber later)
gains access to the
network in an
active cell.
Set the exception
threshold when
you create a task.

Abnormal [0,+∞) Number Number of times BSC6900

RSCPs on that the RSCP V900R014C00 (or
Access value is abnormal later) or BSC6910
when a VIP group V100R014C00 (or
or VIP subscriber later)
gains access to the
network in an
active cell.
Set the exception
threshold when
you create a task.

RRC Setup [0,+∞) Number Number of non- BSC6900

Requests(Non- service setup V900R014C00 (or
Service) requests that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber initiates later)
in an active cell.

RRC Setup [0,+∞) Number Number of service BSC6900

Requests setup requests that V900R014C00 (or
(Service) a VIP group or VIP later) or BSC6910
subscriber initiates V100R014C00 (or
in an active cell. later)

RRC Setup [0,+∞) Number Number of service BSC6900

Failures setup failures that V900R014C00 (or
(Service) a VIP group or VIP later) or BSC6910
subscriber V100R014C00 (or
experiences in an later)
active cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 740

Active Cell/RAN NET/NET/Retainability

Parameter Range Unit Description Supported NE
Version

RRC Release [0,+∞) Number Number of times BSC6900

Times that the RRC V900R014C00 (or
connection setup later) or BSC6910
for a VIP group or V100R014C00 (or
VIP subscriber is later)
released in an
active cell.

Abnormal RRC [0,+∞) Number Number of times BSC6900

Release Times that the RRC V900R014C00 (or
connection setup later) or BSC6910
for a VIP group or V100R014C00 (or
VIP subscriber is later)
abnormally
released in an
active cell.

Active Cell/RAN CS/AMR/Accessibility

Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Numbe Number of CS BSC6900

Requests r service setup V900R014C00 (or
requests that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber initiates later)
in an active cell.

RAB Setup [0,+∞) Numbe Number of CS BSC6900

Failures r service setup failures V900R014C00 (or
that a VIP group or later) or BSC6910
VIP subscriber V100R014C00 (or
experiences in an later)
active cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 741

Active Cell/RAN CS/AMR/Retainability

Parameter Range Unit Description Supported NE
Version

Best Cell Times [0,+∞) Numb Number of times that BSC6900

Before RAB er an active cell serves V900R014C00 (or
Release as the best cell before later) or BSC6910
the CS service of a V100R014C00 (or
VIP group or VIP later)
subscriber is
released.

Best Cell Times [0,+∞) Numb Number of times that BSC6900

Before er an active cell serves V900R014C00 (or
Abnormal RAB as the best cell before later) or BSC6910
Release the CS service of a V100R014C00 (or
VIP group or VIP later)
subscriber is
abnormally released.

Active Cell/RAN CS/VP/Accessibility

Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Number of CS BSC6900

Requests service setup V900R014C00 (or
requests that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber initiates later)
in an active cell.

RAB Setup [0,+∞) Number Number of CS BSC6900

Failures service setup V900R014C00 (or
failures that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber later)
experiences in an
active cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 742

Active Cell/RAN CS/VP/Retainability

Parameter Range Unit Description Supported NE
Version

Best Cell Times [0,+∞) Number Number of times BSC6900

Before RAB that an active cell V900R014C00 (or
Release serves as the best later) or BSC6910
cell before the CS V100R014C00 (or
service of a VIP later)
group or VIP
subscriber is
released.

Best Cell Times [0,+∞) Number Number of times BSC6900

Before that an active cell V900R014C00 (or
Abnormal RAB serves as the best later) or BSC6910
Release cell before the CS V100R014C00 (or
service of a VIP later)
group or VIP
subscriber is
abnormally
released.

Active Cell/RAN CS/SMS/Accessibility

Parameter Range Unit Description Supported NE
Version

SMS Requests [0,+∞) Number Number of SMS BSC6900

(MOC) requests that a VIP V900R014C00 (or
group or VIP later) or BSC6910
subscriber sends in V100R014C00 (or
an active cell. later)

SMS Request [0,+∞) Number Number of SMS BSC6900

Failures(MOC) requests that a VIP V900R014C00 (or
group or VIP later) or BSC6910
subscriber fails to V100R014C00 (or
send in an active later)
cell.

SMS Requests [0,+∞) Number Number of SMS BSC6900

(MTC) requests that a VIP V900R014C00 (or
group or VIP later) or BSC6910
subscriber receives V100R014C00 (or
in an active cell. later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 743

Parameter Range Unit Description Supported NE

Version

SMS Request [0,+∞) Number Number of SMS BSC6900

Failures(MTC) requests that a VIP V900R014C00 (or
group or VIP later) or BSC6910
subscriber fails to V100R014C00 (or
receive in an active later)
cell.

Active Cell/RAN PS/R99/Accessibility

Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Number of PS BSC6900

Requests service setup V900R014C00 (or
requests that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber initiates later)
in an active cell.

RAB Setup [0,+∞) Number Number of PS BSC6900

Failures service setup V900R014C00 (or
failures that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber later)
experiences in an
active cell.

Active Cell/RAN PS/R99/Retainability

Parameter Range Unit Description Supported NE
Version

Best Cell Times [0,+∞) Numbe Number of times that BSC6900

Before RAB r an active cell serves V900R014C00 (or
Release as the best cell later) or BSC6910
before the PS service V100R014C00 (or
of a VIP group or later)
VIP subscriber is
released.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 744

Parameter Range Unit Description Supported NE

Version

Best Cell Times [0,+∞) Numbe Number of times that BSC6900

Before RAB r an active cell serves V900R014C00 (or
Abnormal RAB as the best cell later) or BSC6910
Release before the PS service V100R014C00 (or
of a VIP group or later)
VIP subscriber is
abnormally released.

Active Cell/RAN PS/HSDPA/Accessibility

Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Number of PS BSC6900

Requests service setup V900R014C00
requests that a (or later) or
VIP group or VIP BSC6910
subscriber V100R014C00
initiates in an (or later)
active cell.

RAB Setup [0,+∞) Number Number of PS BSC6900

Failures service setup V900R014C00
failures that a VIP (or later) or
group or VIP BSC6910
subscriber V100R014C00
experiences in an (or later)
active cell.

Active Cell/RAN PS/HSDPA/Retainability

Parameter Range Unit Description Supported NE
Version

Best Cell Times [0,+∞) Numbe Number of times that BSC6900

Before RAB r an active cell serves V900R014C00 (or
Release as the best cell before later) or BSC6910
the PS service of a V100R014C00 (or
VIP group or VIP later)
subscriber is
released.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 745

Parameter Range Unit Description Supported NE

Version

Best Cell Times [0,+∞) Numbe Number of times that BSC6900

Before r an active cell serves V900R014C00 (or
Abnormal RAB as the best cell before later) or BSC6910
Release the PS service of a V100R014C00 (or
VIP group or VIP later)
subscriber is
abnormally released.

Active Cell/RAN PS/HSUPA/Accessibility

Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Number of PS BSC6900

Requests service setup V900R014C00 (or
requests that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber initiates later)
in an active cell.

RAB Setup [0,+∞) Number Number of PS BSC6900

Failures service setup V900R014C00 (or
failures that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber later)
experiences in an
active cell.

Active Cell/RAN PS/HSUPA/Retainability

Parameter Range Unit Description Supported NE
Version

Best Cell Times [0,+∞) Number Number of times BSC6900

Before RAB that an active cell V900R014C00 (or
Release serves as the best later) or BSC6910
cell before the PS V100R014C00 (or
service of a VIP later)
group or VIP
subscriber is
released.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 746

Parameter Range Unit Description Supported NE

Version

Best Cell Times [0,+∞) Number Number of times BSC6900

Before that an active cell V900R014C00 (or
Abnormal RAB serves as the best later) or BSC6910
Release cell before the PS V100R014C00 (or
service of a VIP later)
group or VIP
subscriber is
abnormally
released.

Active Cell/RAN PS/HSPA/Accessibility

Parameter Range Unit Description Supported NE
Version

RAB Setup [0,+∞) Number Number of PS BSC6900

Requests service setup V900R014C00 (or
requests that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber initiates later)
in an active cell.

RAB Setup [0,+∞) Number Number of PS BSC6900

Failures service setup V900R014C00 (or
failures that a VIP later) or BSC6910
group or VIP V100R014C00 (or
subscriber later)
experiences in an
active cell.

Active Cell/RAN PS/HSPA/Retainability

Parameter Range Unit Description Supported NE
Version

Best Cell Times [0,+∞) Number Number of times BSC6900

Before RAB that an active cell V900R014C00 (or
Release serves as the best later) or BSC6910
cell before the PS V100R014C00 (or
service of a VIP later)
group or VIP
subscriber is
released.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 747

Parameter Range Unit Description Supported NE

Version

Best Cell Times [0,+∞) Number Number of times BSC6900

3.9.7 Reference for VIP Analysis Parameters (LTE)

This section describes the parameters for querying LTE VIP analysis results. You can refer to
the description when querying LTE VIP analysis results.

Parameters for Viewing LTE VIP Analysis-Common Results

This section describes the parameters for querying LTE VIP analysis-common results. You can
refer to the description when querying results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 748

Common
Parameter Range Unit Description Supported NE
Version

Deep Analysis N/A N/A ·When the LTE3900

dimension is V100R005C00
Group, this or later version
parameter is
used to switch
from the
analysis results
of a VIP group
to the analysis
results of VIP
subscribers in
this group.
·When the
dimension is
User, this
parameter is
used to switch
from the
analysis results
of counters to
the analysis
results of calls.

Group Name N/A N/A Name of a VIP LTE3900

group. V100R005C00
or later version

User ID [1,+∞) N/A Identity of a VIP LTE3900

subscriber. V100R005C00
·User ID, which or later version
is created by the
system when
creating a VIP
User in the VIP
Group
Management.

Alias N/A N/A Alias of a VIP LTE3900

subscriber. V100R005C00
Query the name or later version
of a VIP
subscriber using
VIP group
management
based on the
IMSI of the VIP
subscriber.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 749

Parameter Range Unit Description Supported NE

Version

IMSI N/A N/A IMSI LTE3900

information of a V100R005C00
subscriber. or later version
Note: Only
when you have
the "User
Identity" right,
you can view the
IMSI
information.

IMEI-TAC 00000000-9999 N/A First eight digits LTE3900

9999 in the IMEI of a V100R005C00
UE. or later version
IMEI is
international
mobile
equipment
identity for short
and TAC is type
approval code
for short.

Terminal Model N/A N/A Type of the UE LTE3900

used by a VIP V100R005C00
subscriber. or later version
Query the UE
type of a VIP
subscriber using
terminal type
management
based on the
IMEI-TAC of
the VIP
subscriber.

Service Type N/A N/A Service type for LTE3900

a counter. V100R005C00
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 750

Parameter Range Unit Description Supported NE

Version

Number of [0,+∞) Number Number of LTE3900

Abnormal KPIs abnormal V100R005C00
counters in all or later version
counter sets
determined
based on the
result thresholds
set when
engineers create
a task.

Total Reports [0,+∞) Number Indicates the LTE3900

number of V100R005C00
records or later version
generated for all
service types
during the
network access
of a subscriber.

Parameters for Viewing LTE VIP Analysis-RAN NET Results

This section describes the parameters for querying LTE VIP analysis-RAN NET results. You
can refer to the description when querying results.

Accessibility
Parameter Range Unit Description Supported NE
Version

RRC Setup [0,+∞) Number Number of non- LTE3900

Requests (Non- service RRC V100R005C00
Service) setup requests or later version
initiated by a
UE.

RRC Setup [0,+∞) Number Number of LTE3900

Requests service RRC V100R005C00
(Service) setup requests or later version
initiated by a
UE.

RRC Re- [0,+∞) Number Number of RRC LTE3900

establishment reestablishment V100R008C00
Requests requests or later version
initiated by a
UE.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 751

Parameter Range Unit Description Supported NE

Outgoing successful inter- V100R008C00
Handover RAT outgoing or later version
SRVCC handovers to
Success Ratio inter-RAT
(with Data outgoing
Transmission) handover
requests
initiated by a UE
through
SRVCC during
data
transmission.

Parameters for Viewing LTE VIP Analysis-RAN PS Results

This section describes the parameters for querying LTE VIP analysis-RAN PS results. You can
refer to the description when querying results.

All/GBR/GBR-CQI 1 to 4-Accessibility
Parameter Range Unit Description Supported NE
Version

E-RAB Setup [0,+∞) Number Number of E- LTE3900

Requests RAB (short for V100R005C00
Evolved Radio or later version
Access Bearer)
setup requests
initiated by a
UE.

E-RAB Setup [0,+∞) Number Number of LTE3900

Failures failed E-RAB V100R005C00
setups after a or later version
UE initiates E-
RAB setup
requests.

E-RAB Setup [0,+∞) Number Number of LTE3900

Success Times successful E- V100R005C00
RAB setups or later version
after a UE
initiates E-RAB
setup requests.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 757

Transmission data V100R005C00
Duration transmission or later version
duration of PS
services.

Average Uplink [0,+∞) kbit/s Average uplink LTE3900

Throughput throughput of V100R005C00
PS services. or later version
Average uplink
throughput =
Total uplink
throughput/
Total uplink
data
transmission
duration

Low Average [0,+∞) Number Number of LTE3900

Uplink times when the V100R005C00
Throughput average uplink or later version
Times throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
uplink
throughput of
PS services.
The exception
threshold is set
by engineers
during task
creation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 765

All/NonGBR/NonGBR-QCI 5 to 9-Accessibility
Parameter Range Unit Description Supported NE
Version

E-RAB Setup [0,+∞) Number Number of E- LTE3900

Requests RAB setup V100R005C00
requests or later version
initiated by a
UE.

E-RAB Setup [0,+∞) Number Number of LTE3900

Failures failed E-RAB V100R005C00
setups after a or later version
UE initiates E-
RAB setup
requests.

E-RAB Setup [0,+∞) Number Number of LTE3900

Success Times successful E- V100R005C00
RAB setups or later version
after a UE
initiates E-RAB
setup requests.

E-RAB Setup [0,100] % Ratio of LTE3900

Success Ratio successful E- V100R005C00
RAB setups to or later version
E-RAB setup
requests
initiated by a
UE.

All/NonGBR/NonGBR-QCI 5 to 9-Retainability
Parameter Range Unit Description Supported NE
Version

E-RAB Setup [0,+∞) Number Number of LTE3900

Success Times successful E- V100R005C00
RAB setups or later version
after a UE
initiates E-RAB
setup requests.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 766

Parameter Range Unit Description Supported NE

Version

Abnormal E- [0,+∞) Number Number of LTE3900

RAB Release abnormal E- V100R005C00
Times RAB releases or later version
due to E-RAB
exceptions
among
successful E-
RAB setups.

Abnormal E- [0,100] % Ratio of LTE3900

RAB Release abnormal E- V100R005C00
Ratio RAB releases or later version
due to E-RAB
exceptions to
successful E-
RAB setups.

Abnormal E- [0,+∞) Number Number of LTE3900

RAB Release abnormal E- V100R005C01
Times (with RAB releases or later version
Data with data
Transmission) transmission
due to E-RAB
exceptions
among
successful E-
RAB setups.

Abnormal E- [0,100] % Ratio of LTE3900

RAB Release abnormal E- V100R005C01
Ratio(with Data RAB releases or later version
Transmission) with data
transmission
due to E-RAB
exceptions to
successful E-
RAB setups.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 767

All/NonGBR/NonGBR-QCI 5 to 9-Service Evaluation for Delay

Parameter Range Unit Description Supported NE
Version

E-RAB Setup [0,+∞) Number Number of LTE3900

Success Times successful E- V100R005C00
RAB setups or later version
after a UE
initiates E-RAB
setup requests.

Average E- [0,+∞) Second Average E- LTE3900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 768

Parameter Range Unit Description Supported NE

Version

Long E-RAB [0,+∞) Number This parameter LTE3900

Setup Delay indicates the V100R005C00
Times number of times or later version
when the E-
RAB setup
delay is greater
than the long E-
RAB setup
delay threshold.
The threshold is
set during
analysis task
creation.

Proportion of [0,100] % Ratio of long E- LTE3900

long E-RAB RAB setup V100R005C00
Setup Delay delay to the or later version
number of E-
RAB setup
delay reports.

Average E- [0,+∞) Second Average E- LTE3900

RAB Duration RAB V100R005C00
occupation or later version
duration
recorded in a
report.

All/NonGBR/NonGBR-QCI 5 to 9-Service Evaluation for Rate

Parameter Range Unit Description Supported NE
Version

Downlink [0,+∞) MB Total downlink LTE3900

Traffic Volume throughput of V100R005C00
PS services. or later version

Average [0,+∞) Second Average LTE3900

Downlink downlink data V100R005C00
Transmission transmission or later version
Duration duration of PS
services.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 769

Parameter Range Unit Description Supported NE

Version

Average [0,+∞) kbit/s Average LTE3900

Downlink downlink V100R005C00
Throughput throughput of or later version
PS services.
Average
downlink
throughput =
Total downlink
throughput/
Total downlink
data
transmission
duration

Low Average [0,+∞) Number Number of LTE3900

Uplink Traffic [0,+∞) MB Total uplink LTE3900

Volume throughput of V100R005C00
PS services. or later version

Average Uplink [0,+∞) Second Average uplink LTE3900

Transmission data V100R005C00
Duration transmission or later version
duration of PS
services.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 770

Parameter Range Unit Description Supported NE

Version

Average Uplink [0,+∞) kbit/s Average uplink LTE3900

Throughput throughput of V100R005C00
PS services. or later version
Average uplink
throughput =
Total uplink
throughput/
Total uplink
data
transmission
duration

Low Average [0,+∞) Number Number of LTE3900

Parameters for Viewing LTE VIP Analysis-Active Cell Results

This section describes the parameters for querying LTE VIP analysis-active cell results. You
can refer to the description when querying results.

Common
Parameter Range Unit Description Supported NE
Version

eNodeB ID N/A N/A ID of an eNodeB. LTE3900

V100R005C00
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 771

Parameter Range Unit Description Supported NE

Version

eNodeB Name 1 to 64 N/A Name of an eNodeB. LTE3900

charact Note: when name information V100R005C00
ers cannot be obtained because or later version
configuration information has
been deleted or cell information
has not been activated,
Undefined is displayed.

Cell ID N/A N/A ID of a cell. LTE3900

V100R005C00
or later version

Cell Name 1 to 64 N/A Name of a cell. LTE3900

RAN NET-Accessibility
Parameter Range Unit Description Supported NE
Version

RRC Setup [0,+∞) Number Number of non- LTE3900

Requests (Non- service RRC V100R005C00
Service) setup requests or later version
initiated by a
VIP group or
VIP subscriber
in an active cell.

RRC Setup [0,+∞) Number Number of LTE3900

Requests service RRC V100R005C00
(Service) setup requests or later version
initiated by a
VIP group or
VIP subscriber
in an active cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 772

Parameter Range Unit Description Supported NE

Version

RRC Re- [0,+∞) Number Number of RRC LTE3900

establishment reestablishment V100R008C00
Requests requests or later version
initiated by a
VIP group or
VIP subscriber
in an active cell.

RRC Re- [0,+∞) Number Number of LTE3900

establishment failed RRC V100R008C00
Failures reestablishment or later version
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.

RAN NET-Mobility
Parameter Range Unit Description Supported NE
Version

Intra-RAT [0,+∞) Number Number of LTE3900

Outgoing intra-RAT V100R005C00
Handover outgoing or later version
Requests handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.

Intra-RAT [0,+∞) Number Number of LTE3900

Outgoing failed intra- V100R005C00
Handover RAT outgoing or later version
Failures handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 773

Parameter Range Unit Description Supported NE

Version

Intra-RAT [0,+∞) Number Number of LTE3900

Incoming failed intra- V100R005C00
Handover RAT incoming or later version
Failures handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.

Intra-RAT [0,+∞) Number Number of LTE3900

Outgoing failed intra- V100R005C01
Handover RAT outgoing or later version
Failures (with handover
Data requests
Transmission) initiated by a
VIP group or
VIP subscriber
in an active cell
during data
transmission.

Inter-RAT [0,+∞) Number Number of LTE3900

Outgoing inter-RAT V100R005C00
Handover outgoing or later version
Requests handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.

Inter-RAT [0,+∞) Number Number of LTE3900

Outgoing failed inter- V100R005C00
Handover RAT outgoing or later version
Failures handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 774

Parameter Range Unit Description Supported NE

E-RAB Setup [0,+∞) Number Number of LTE3900

Failures failed E-RAB V100R005C00
setups initiated or later version
by a VIP group
or VIP
subscriber in an
active cell.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 777

RAN PS-All/GBR (Including QCI 1 to 4)/NonGBR (Including QCI 5 to 9)-

Retainability
Parameter Range Unit Description Supported NE
Version

Abnormal E- [0,+∞) Number Number of LTE3900

RAB Release abnormal E- V100R005C00
Times RAB releases of or later version
a VIP group or
VIP subscriber
in an active cell.

Abnormal E- [0,+∞) Number Number of LTE3900

RAB Release abnormal E- V100R005C01
Times (with RAB releases of or later version
Data a VIP group or
Transmission) VIP subscriber
in an active cell
during data
transmission.

3.9.8 Reference for VIP Analysis Parameters (PS Core)

This section describes the parameters for querying PS Core VIP analysis results. You can refer
to the description when querying PS Core VIP analysis results.

Parameters for Viewing PS Core VIP Analysis - Data Results

This section describes the parameters for querying PS Core VIP analysis data results. You can
refer to the description when querying PS Core VIP analysis data results.

Common
Parameter Rang Unit Description Supported NE
e Version

Deep N/A N/A ·When the dimension is Group, this USN9810

Analysis parameter is used to switch from the V900R011C01 or
analysis results of a VIP group to later version
those of the VIP subscribers in this
group.
·When the dimension is User, this
parameter is used to switch from the
analysis results of counters to those
of the calls.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 778

Parameter Rang Unit Description Supported NE

e Version

Group N/A N/A Name of a VIP group. USN9810

Name V900R011C01 or
later version

IMSI N/A N/A IMSI information of a subscriber. USN9810

Note: Only when you have the V900R011C01 or
"User Identity" right, you can view later version
the IMSI information.

MSISDN N/A N/A MSISDN information of a USN9810

subscriber. V900R011C01 or
Note: Only when you have the later version
"User Identity" right, you can view
the MSISDN information.

IMEI-TAC N/A N/A International mobile equipment USN9810

identity-type allocation code V900R011C01 or
(IMEI-TAC) of the terminal used later version
by a VIP subscriber.

User ID N/A N/A ID of a VIP subscriber. USN9810

V900R011C01 or
later version

Alias N/A N/A Alias of a VIP subscriber. You can USN9810

obtain the user name in the VIP V900R011C01 or
Group Management window based later version
on the IMSI of the VIP subscriber.

Terminal N/A N/A Type of the terminal used by a VIP USN9810

Model subscriber. You can obtain the V900R011C01 or
terminal type in the Terminal Type later version
Management window based on the
IMEI-TAC of the terminal used by
the VIP subscriber.

Total [0, Numb Indicates the number of records USN9810

Reports +∞) er generated for all service types V900R011C01 or
during the network access of a later version
subscriber.

Service N/A N/A Service type for a following USN9810

Type counter. V900R011C01 or
later version

Number of [0, Numb Number of abnormal counters in all USN9810

Abnormal +∞) er counter sets determined based on V900R011C01 or
KPIs the result thresholds set when later version
engineers create a task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 779

SGSN/Accessability/Attach
Parameter Range Unit Description Supported
NE Version

SGSN-Attach [0,+∞) Numb Number of attach process requests USN9810

Requests er by a VIP subscriber on the GSM V900R011C01
and UMTS networks. or later version
Attach processes include:
GPRS attach
Combined attach

SGSN-Attach [0,+∞) Numb Number of attach process failures USN9810

Failures er by a VIP subscriber on the GSM V900R011C01
and UMTS networks. or later version

SGSN-Attach [0.00,10 % Attach process success ratio by a USN9810

Success Ratio 0.00] VIP subscriber on the GSM and V900R011C01
UMTS networks. or later version
Attach success ratio = (1 - Number
of attach failures/Number of attach
requests) x 100%

SGSN-Average [0,+∞) ms Average delay of an attach process USN9810

Attach Delay by a VIP subscriber on the GSM V900R011C01
and UMTS networks. or later version

SGSN- [0,+∞) Numb Number of delays that exceed the USN9810

Overlong er exception threshold of an attach V900R011C01
Attach Delays process by a VIP subscriber on the or later version
GSM and UMTS networks.

SGSN/Accessability/Service Req
Parameter Range Unit Description Supported
NE Version

SGSN-Service [0,+∞) Number Number of service req process USN9810

Req Requests requests by a VIP subscriber on V900R011C0
the GSM and UMTS network. 1 or later
The service req process version
includes:
Service Request

SGSN-Service [0,+∞) Number Number of service req process USN9810

Req Failures failures by a VIP subscriber on V900R011C0
the GSM and UMTS network. 1 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 780

Parameter Range Unit Description Supported

NE Version

SGSN-Service [0.00,100. % Service req process success USN9810

Req Success 00] ratio by a VIP subscriber on the V900R011C0
Ratio GSM and UMTS networks. 1 or later
Service req success ratio = (1 - version
Number of service req failures/
Number of service req
requests) x 100%

SGSN-Average [0,+∞) ms Average delay of a service req USN9810

Service Req process by a VIP subscriber on V900R011C0
Delay the GSM and UMTS networks. 1 or later
version

SGSN- [0,+∞) Number Number of delays that exceed USN9810

Overlong the exception threshold of a V900R011C0
Service Req service req process by a VIP 1 or later
Delays subscriber on the GSM and version
UMTS networks.

SGSN/Accessability/Paging
Parameter Range Unit Description Supported
NE Version

SGSN-Paging [0,+∞) Number Number of paging process USN9810

Requests requests by a VIP subscriber on V900R011C01
the GSM and UMTS networks. or later version
The paging process includes
Paging.

SGSN-Paging [0,+∞) Number Number of paging process USN9810

Failures failures by a VIP subscriber on V900R011C01
the GSM and UMTS networks. or later version

SGSN-Paging [0.00,100. % Paging process success ratio by USN9810

Success Ratio 00] a VIP subscriber on the GSM V900R011C01
and UMTS networks. or later version
Paging success ratio = (1 -
Number of paging failures/
Number of paging requests) x
100%

SGSN-Average [0,+∞) ms Average delay of a paging USN9810

Paging Delay process by a VIP subscriber on V900R011C01
the GSM and UMTS networks. or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 781

Parameter Range Unit Description Supported

NE Version

SGSN- [0,+∞) Number Number of delays that exceed USN9810

Overlong the exception threshold of a V900R011C01
Paging Delays paging process by a VIP or later version
subscriber on the GSM and
UMTS networks.

SGSN/Accessability/PDP Act
Parameter Range Unit Description Supported
NE Version

PDP Act [0,+∞) Numb Number of PDP act process USN9810

Requests er requests by a VIP subscriber on the V900R011C0
GSM and UMTS networks. 1 or later
PDP act processes include: version

MS Init PDP Act

CN Init PDP Act

PDP Act [0,+∞) Numb Number of PDP act process USN9810

Failures er failures by a VIP subscriber on the V900R011C0
GSM and UMTS networks. 1 or later
version

PDP Act [0.00,100. % PDP act process success ratio by a USN9810

Success Ratio 00] VIP subscriber on the GSM and V900R011C0
UMTS networks. 1 or later
PDP act success ratio = (1 - version
Number of PDP act failures/
Number of PDP act requests) x
100%

Average PDP [0,+∞) ms Average delay of a PDP act USN9810

Act Delay process by a VIP subscriber on the V900R011C0
GSM and UMTS networks. 1 or later
version

Overlong PDP [0,+∞) Numb Number of delays that exceed the USN9810
Act Delays er exception threshold of a PDP act V900R011C0
process by a VIP subscriber on the 1 or later
GSM and UMTS networks. version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 782

SGSN/Accessability/PDP Sec Act

Parameter Range Unit Description Supported
NE Version

PDP Sec Act [0,+∞) Numbe Number of PDP sec act process USN9810
Requests r requests by a VIP subscriber on V900R011C0
the GSM and UMTS networks. 1 or later
The PDP sec act process version
includes:
MS Init PDP Sec Act
CN Init PDP Sec Act

PDP Sec Act [0,+∞) Numbe Number of PDP sec act process USN9810
Failures r failures by a VIP subscriber on V900R011C0
the GSM and UMTS networks. 1 or later
version

PDP Sec Act [0.00,100.0 % PDP sec act process success USN9810
Success Ratio 0] ratio by a VIP subscriber on the V900R011C0
GSM and UMTS networks. 1 or later
PDP sec act success ratio = (1 - version
Number of PDP sec act failures/
Number of PDP sec act
requests) x 100%

Average PDP [0,+∞) ms Average delay of a PDP sec act USN9810

Sec Act Delay process by a VIP subscriber on V900R011C0
the GSM and UMTS networks. 1 or later
version

Overlong PDP [0,+∞) Numbe Number of delays that exceed USN9810

Sec Act Delays r the exception threshold of a PDP V900R011C0
sec act process by a VIP 1 or later
subscriber on the GSM and version
UMTS networks.

SGSN/Accessability/RAB Assignment
Parameter Range Unit Description Supported
NE Version

RAB [0,+∞) Numbe Number of RAB Assignment USN9810

Assignment r requests of a VIP subscriber on V900R012C0
Requests the GSM/UMTS network 0 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 783

Parameter Range Unit Description Supported

NE Version

RAB [0,+∞) Numbe Number of RAB assignment USN9810

Assignment r failures of a VIP subscriber on V900R012C0
Failures the GSM/UMTS network 0 or later
version

RAB [0.00,100.0 % RAB assignment success ratio USN9810

Assignment 0] of a VIP subscriber on the GSM/ V900R012C0
Success Ratio UMTS network 0 or later
RAB assignment success ratio = version
(1 - Number of RAB assignment
failures/Number of RAB
Assignment requests) x 100%

Average RAB [0,+∞) ms Average RAB assignment delay USN9810

Assignment of a VIP subscriber on the GSM/ V900R012C0
Delay UMTS network 0 or later
version

Overlong RAB [0,+∞) Numbe Number of times that the RAB USN9810
Assignment r assignment delay of a VIP V900R012C0
Delays subscriber exceeds the 0 or later
predefined exception threshold version
on the GSM/UMTS network

SGSN/Accessability/PDN GW Dedicated Bearer Act

Parameter Range Unit Description Supported
NE Version

PDN GW [0,+∞) Numbe Number of PDN GW USN9810

Dedicated r Dedicated Bearer Act requests V900R012C00
Bearer Act of a VIP subscriber on the or later version
Requests GSM/UMTS network
A PDN GW Dedicated Bearer
Act request indicates a PDN
GW dedicated bearer
activation.

PDN GW [0,+∞) Numbe Number of PDN GW dedicated USN9810

Dedicated r bearer activation failures of a V900R012C00
Bearer Act VIP subscriber on the GSM/ or later version
Failures UMTS network

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 784

Parameter Range Unit Description Supported

NE Version

PDN GW [0.00,100. % PDN GW dedicated bearer USN9810

Dedicated 00] activation success ratio of a VIP V900R012C00
Bearer Act subscriber on the GSM/UMTS or later version
Success Ratio network
PDN GW dedicated bearer
activation success ratio = (1 -
Number of PDN GW dedicated
bearer activation failures/
Number of PDN GW
Dedicated Bearer Act requests)
x 100%

Average PDN [0,+∞) ms Average PDN GW dedicated USN9810

GW Dedicated bearer activation delay of a VIP V900R012C00
Bearer Act subscriber on the GSM/UMTS or later version
Delay network

Overlong PDN [0,+∞) Numbe Number of times that the PDN USN9810
GW Dedicated r GW dedicated bearer activation V900R012C00
Bearer Act delay of a VIP subscriber or later version
Delays exceeds the predefined
exception threshold on the
GSM/UMTS network

SGSN/Mobility/RAU
Parameter Range Unit Description Supported NE
Version

Intra SGSN [0,+∞) Number Number of intra SGSN RAU USN9810

RAU Requests process requests by a VIP V900R011C01
subscriber on the GSM and or later version
UMTS networks.
Intra SGSN RAU processes
include:
Intra RAU
Intra combined RAU
Periodic RAU
Periodic combined RAU

Intra SGSN [0,+∞) Number Number of intra SGSN RAU USN9810

RAU Failures process failures by a VIP V900R011C01
subscriber on the GSM and or later version
UMTS networks.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 785

Parameter Range Unit Description Supported NE

Version

Intra SGSN [0.00,100. % Intra SGSN RAU process USN9810

RAU Success 00] success ratio by a VIP V900R011C01
Ratio subscriber on the GSM and or later version
UMTS networks.
Intra SGSN RAU success
ratio = (1 - Number of intra
SGSN RAU failures/
Number of intra SGSN RAU
requests) x 100%

Average Intra [0,+∞) ms Average delay of an intra USN9810

SGSN RAU SGSN RAU process by a V900R011C01
Delay VIP subscriber on the GSM or later version
and UMTS networks.

Overlong Intra [0,+∞) Number Number of delays that USN9810

SGSN RAU exceed the exception V900R011C01
Delays threshold of an intra SGSN or later version
RAU process by a VIP
subscriber on the GSM and
UMTS networks.

Inter SGSN [0,+∞) Number Number of inter SGSN RAU USN9810

RAU Requests process requests by a VIP V900R011C01
subscriber on the GSM and or later version
UMTS networks.
Inter SGSN RAU processes
include:
Inter RAU
Inter combined RAU

Inter SGSN [0,+∞) Number Number of inter SGSN RAU USN9810

RAU Failures process failures by a VIP V900R011C01
subscriber on the GSM and or later version
UMTS networks.

Inter SGSN [0.00,100. % Inter SGSN RAU process USN9810

RAU Success 00] success ratio by a VIP V900R011C01
Ratio subscriber on the GSM and or later version
UMTS networks.
Inter SGSN RAU process
success ratio by a VIP
subscriber on the GSM and
UMTS networks.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 786

Parameter Range Unit Description Supported NE

Version

Average Inter [0,+∞) ms Average delay of an inter USN9810

SGSN RAU SGSN RAU process by a V900R011C01
Delay VIP subscriber on the GSM or later version
and UMTS networks.

Overlong Inter [0,+∞) Number Number of delays that USN9810

SGSN RAU exceed the exception V900R011C01
Delays threshold of an inter SGSN or later version
RAU process by a VIP
subscriber on the GSM and
UMTS networks.

RAU (others) [0.00,100. % Number of other RAU USN9810

Requests 00] processes by a VIP V900R011C01
subscriber on the GSM and or later version
UMTS networks

RAU (others) [0,+∞) ms Number of other RAU USN9810

Failures process failures by a VIP V900R011C01
subscriber on the GSM and or later version
UMTS networks.

RAU (others) [0.00,100. % Other RAU process success USN9810

Success Ratio 00] ratio by a VIP subscriber on V900R011C01
the GSM and UMTS or later version
networks.
RAU (others) success ratio =
(1 - Number of RAU (others)
failures/Number of RAU
(others) requests) x 100%

SGSN/Mobility/Relocation
Parameter Rang Unit Description Supported NE
e Version

Relocation [0, Number Number of relocation process USN9810

Requests +∞) requests by a VIP subscriber on V900R011C01 or
the GSM and UMTS networks. later version
Relocation processes include:
Intra SRNS relocation
Inter SRNS relocation

Relocation [0, Number Number of relocation process USN9810

Failures +∞) failures by a VIP subscriber on V900R011C01 or
the GSM and UMTS networks. later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 787

Parameter Rang Unit Description Supported NE

e Version

Relocation [0.00,1 % Relocation process success ratio USN9810

Success Ratio 00.00] by a VIP subscriber on the GSM V900R011C01 or
and UMTS networks. later version
Relocation success ratio = (1 -
Number of relocation failures/
Number of relocation requests)
x 100%

Average [0, ms Average delay of a relocation USN9810

Relocation +∞) process by a VIP subscriber on V900R011C01 or
Delay the GSM and UMTS networks. later version

Overlong [0, Number Number of delays that exceed USN9810

Relocation +∞) the exception threshold of a V900R011C01 or
Delays relocation process by a VIP later version
subscriber on the GSM and
UMTS networks.

SGSN/Mobility/System Change
Parameter Range Unit Description Supported NE
Version

System Change [0,+∞) Numb Number of system change USN9810

Requests er process requests by a VIP V900R011C01 or
subscriber on the GSM and later version
UMTS networks.
System change processes
include:
3G to 2G system change
2G to 3G system change

System Change [0,+∞) Numb Number of system change USN9810

Failures er process failures by a VIP V900R011C01 or
subscriber on the GSM and later version
UMTS networks.

System Change [0.00,100 % System change process USN9810

Success Ratio .00] success ratio by a VIP V900R011C01 or
subscriber on the GSM and later version
UMTS networks.
System change success ratio =
(1 - Number of system change
failures/Number of system
change requests) x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 788

Parameter Range Unit Description Supported NE

Version

Average System [0,+∞) ms Average delay of a system USN9810

Change Delay change process by a VIP V900R011C01 or
subscriber on the GSM and later version
UMTS networks.

Overlong [0,+∞) Numb Number of delays that exceed USN9810

System Change er the exception threshold of a V900R011C01 or
Delays system change process by a later version
VIP subscriber on the GSM
and UMTS networks.

SGSN/PDP Modification/PDP Mod

Parameter Range Unit Description Supported NE
Version

PDP Mod [0,+∞) Number Number of PDP mod USN9810

Requests process requests by a VIP V900R011C01 or
subscriber on the GSM later version
and UMTS networks.
PDP mod processes
include:
MS Init PDP Mod
CN Init PDP Mod

PDP Mod [0,+∞) Number Number of PDP mod USN9810

Failures process failures by a VIP V900R011C01 or
subscriber on the GSM later version
and UMTS networks.

PDP Mod [0.00,100. % PDP mod process success USN9810

Success Ratio 00] ratio by a VIP subscriber V900R011C01 or
on the GSM and UMTS later version
networks.
PDP mod success ratio =
(1 - Number of PDP mod
failures/Number of PDP
mod requests) x 100%

Average PDP [0,+∞) ms Average delay of a PDP USN9810

Mod Delay mod process by a VIP V900R011C01 or
subscriber on the GSM later version
and UMTS networks.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 789

Parameter Range Unit Description Supported NE

Version

Overlong PDP [0,+∞) Number Number of delays that USN9810

Mod Delays exceed the exception V900R011C01 or
threshold of a PDP mod later version
process by a VIP
subscriber on the GSM
and UMTS networks.

SGSN/Modification/PDN GW Initiated Bearer Mod

Parameter Range Unit Description Supported NE
Version

PDN GW [0,+∞) Number Number of PDN GW USN9810

Initiated Bearer Initiated Bearer Mod V900R012C00 or
Mod Requests requests of a VIP later version
subscriber on the GSM/
UMTS network
A PDN GW Initiated
Bearer Mod request
indicates a PDN GW
initiated bearer
modification.

PDN GW [0,+∞) Number Number of PDN GW USN9810

Initiated Bearer initiated bearer V900R012C00 or
Mod Failures modification failures of a later version
VIP subscriber on the
GSM/UMTS network

PDN GW [0.00,100. % PDN GW initiated bearer USN9810

Initiated Bearer 00] modification success V900R012C00 or
Mod Success ratio of a VIP subscriber later version
Ratio on the GSM/UMTS
network
PDN GW initiated bearer
modification success
ratio = (1 - Number of
PDN GW initiated bearer
modification failures/
Number of PDN GW
Initiated Bearer Mod
requests) x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 790

Parameter Range Unit Description Supported NE

Version

Average PDN [0,+∞) ms Average PDN GW USN9810

GW Initiated initiated bearer V900R012C00 or
Bearer Mod modification delay of a later version
Delay VIP subscriber on the
GSM/UMTS network

Overlong PDN [0,+∞) Number Number of times that the USN9810

GW Initiated PDN GW initiated bearer V900R012C00 or
Bearer Mod modification delay of a later version
Delays VIP subscriber exceeds
the predefined exception
threshold on the GSM/
UMTS network

MME/Accessability/Attach
Parameter Range Unit Description Supported NE
Version

MME-Attach [0,+∞) Numbe Number of attach process USN9810

Requests r requests by a VIP subscriber V900R011C01 or
on the LTE network. later version
The attach process includes:
Attach
Combined Attach

MME-Attach [0,+∞) Numbe Number of attach process USN9810

Failures r failures by a VIP subscriber V900R011C01 or
on the LTE network. later version

MME-Attach [0.00,100.0 % Attach process success ratio USN9810

Success Ratio 0] by a VIP subscriber on the V900R011C01 or
LTE network. later version
Attach success ratio = (1 -
Number of attach failures/
Number of attach requests) x
100%

MME-Average [0,+∞) ms Average delay of an attach USN9810

Attach Delay process by a VIP subscriber V900R011C01 or
on the LTE network. later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 791

Parameter Range Unit Description Supported NE

Version

MME-Overlong [0,+∞) Numbe Number of delays that USN9810

Attach Delays r exceed the exception V900R011C01 or
threshold of an attach later version
process by a VIP subscriber
on the LTE network.

MME/Accessability/Service Req
Parameter Range Unit Description Supported NE
Version

MME-Service [0,+∞) Numbe Number of service req USN9810

Req Requests r process requests by a VIP V900R011C01 or
subscriber on the LTE later version
network.
The service req process
includes:
Service Request

MME-Service [0,+∞) Numbe Number of service req USN9810

Req Failures r process failures by a VIP V900R011C01 or
subscriber on the LTE later version
network.

MME-Service [0.00,100. % Service req process success USN9810

Req Success 00] ratio by a VIP subscriber on V900R011C01 or
Ratio the LTE network. later version
Service req success ratio =
(1 - Number of service req
failures/Number of service
req requests) x 100%

MME-Average [0,+∞) ms Average delay of a service USN9810

Service Req req process by a VIP V900R011C01 or
Delay subscriber on the LTE later version
network.

MME-Overlong [0,+∞) Numbe Number of delays that USN9810

Service Req r exceed the exception V900R011C01 or
Delays threshold of a service req later version
process by a VIP subscriber
on the LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 792

MME/Accessability/Default Bearer Act

Parameter Range Unit Description Supported NE
Version

Default Bearer [0,+∞) Numb Number of Default Bearer USN9810

Act Requests er Act process requests by a VIP V900R013C00 or
subscriber on the LTE later version
network.
The default bearer act
processes include:
Default bearer activation in
attach

Default Bearer [0,+∞) Numb Number of Default Bearer USN9810

Act Failures er Act process failures by a VIP V900R013C00 or
subscriber on the LTE later version
network.

Default Bearer [0.00,100. % Default Bearer Act process USN9810

Act Success 00] success ratio by a VIP V900R013C00 or
Ratio subscriber on the LTE later version
network.
Default Bearer Act success
ratio = (1 - Number of Default
Bearer Act failures/Number
of Default Bearer Act
requests) x 100%

Default Bearer [0,+∞) ms Average delay of a Default USN9810

Act Delay Bearer Act process by a VIP V900R013C00 or
subscriber on the LTE later version
network.

Overlong [0,+∞) Numb Number of delays that exceed USN9810

Default Bearer er the exception threshold of a V900R013C00 or
Act Delays Default Bearer Act process later version
by a VIP subscriber on the
LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 793

MME/Accessability/Paging
Parameter Range Unit Description Supported NE
Version

MME-Paging [0,+∞) Numb Number of paging process USN9810

Requests er requests by a VIP subscriber V900R011C01 or
on the LTE network. later version
The paging process includes:
Paging.

MME-Paging [0,+∞) Numb Number of paging process USN9810

Failures er failures by a VIP subscriber V900R011C01 or
on the LTE network. later version

MME-Paging [0.00,100. % Paging process success ratio USN9810

Success Ratio 00] by a VIP subscriber on the V900R011C01 or
LTE network. later version
Paging success ratio = (1 -
Number of paging failures/
Number of paging requests) x
100%

MME-Average [0,+∞) ms Average delay of a paging USN9810

Paging Delay process by a VIP subscriber V900R011C01 or
on the LTE network. later version

MME-Overlong [0,+∞) Numb Number of delays that exceed USN9810

Paging Delays er the exception threshold of a V900R011C01 or
paging process by a VIP later version
subscriber on the LTE
network.

MME/Accessability/Dedicated Bearer Act

Parameter Range Unit Description Supported NE
Version

Dedicated [0,+∞) Numbe Number of dedicated bearer USN9810

Bearer Act r act process requests by a VIP V900R011C01 or
Requests subscriber on the LTE later version
network.
The dedicated bearer act
process includes:
Dedicated bearer activation
procedure

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 794

Parameter Range Unit Description Supported NE

Version

Dedicated [0,+∞) Numbe Number of dedicated bearer USN9810

Bearer Act r act process failures by a VIP V900R011C01 or
Failures subscriber on the LTE later version
network.

Dedicated [0.00,100. % Success ratio of a dedicated USN9810

Bearer Act 00] bearer act process by a VIP V900R011C01 or
Success Ratio subscriber on the LTE later version
network.
Dedicated bearer act success
ratio = (1 - Number of
dedicated bearer act failures/
Number of dedicated bearer
act requests) x 100%

Average [0,+∞) ms Average delay of a dedicated USN9810

Dedicated bearer act process by a VIP V900R011C01 or
Bearer Act subscriber on the LTE later version
Delay network.

Overlong [0,+∞) Numbe Number of delays that USN9810

Dedicated r exceed the exception V900R011C01 or
Bearer Act threshold of a dedicated later version
Delays bearer act process by a VIP
subscriber on the LTE
network.

MME/Accessability/PDN Connectivity
Parameter Range Unit Description Supported NE
Version

PDN [0,+∞) Number Number of PDN USN9810

Connectivity Connectivity process V900R011C01 or
Requests requests by a VIP later version
subscriber on the LTE
network.
The PDN Connectivity
process includes:
UE requested PDN
connectivity

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 795

Parameter Range Unit Description Supported NE

Version

PDN [0,+∞) Number Number of PDN USN9810

Connectivity connectivity process V900R011C01 or
Failures failures by a VIP later version
subscriber on the LTE
network.

PDN [0.00,100. % PDN Connectivity process USN9810

Connectivity 00] success ratio by a VIP V900R011C01 or
Success Ratio subscriber on the LTE later version
network.
PDN Connectivity success
ratio = (1 - Number of
PDN Connectivity
failures/Number of PDN
Connectivity requests) x
100%

Average PDN [0,+∞) ms Average delay of a PDN USN9810

Connectivity Connectivity process by a V900R011C01 or
Delay VIP subscriber on the LTE later version
network.

Overlong PDN [0,+∞) Number Number of delays that USN9810

Connectivity exceed the exception V900R011C01 or
Delays threshold of a PDN later version
Connectivity process by a
VIP subscriber on the LTE
network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 796

MME/Mobility/TAU
Parameter Range Unit Description Supported NE
Version

Intra TAU [0,+∞) Numbe Number of intra TAU process USN9810

Requests r requests by a VIP subscriber V900R011C01 or
on the LTE network. later version
Intra TAU processes include:
Intra USN Intra E-UTRAN
TAU
Intra USN GERAN to E-
UTRAN Inter RAT TAU
Intra USN UTRAN to E-
UTRAN Inter RAT TAU
Intra USN E-UTRAN to
GERAN Inter RAT RAU
Intra USN E-UTRAN to
UTRAN Inter RAT RAU
Intra USN Intra E-UTRAN
Combined TAU
Intra USN GERAN to E-
UTRAN Inter RAT
Combined TAU
Intra USN UTRAN to E-
UTRAN Inter RAT
Combined TAU

Intra TAU [0,+∞) Numbe Number of intra TAU process USN9810

Failures r failures by a VIP subscriber V900R011C01 or
on the LTE network. later version

Intra TAU [0.00,100. % Intra TAU process success USN9810

Success Ratio 00] ratio by a VIP subscriber on V900R011C01 or
the LTE network. later version
Intra TAU success ratio = (1 -
Number of intra TAU
failures/Number of intra TAU
requests) x 100%

Average Intra [0,+∞) ms Average delay of an intra USN9810

TAU Delay TAU process by a VIP V900R011C01 or
subscriber on the LTE later version
network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 797

Parameter Range Unit Description Supported NE

Version

Overlong Intra [0,+∞) Numbe Number of delays that exceed USN9810

TAU Delays r the exception threshold of an V900R011C01 or
intra TAU process by a VIP later version
subscriber on the LTE
network.

Inter TAU [0,+∞) Numbe Number of inter TAU process USN9810

Requests r requests by a VIP subscriber V900R011C01 or
on the LTE network. later version
Inter TAU processes include:
Inter USN Intra E-UTRAN
TAU
Inter USN GERAN/UTRAN
to E-UTRAN TAU
Inter USN E-UTRAN to
GERAN/UTRAN Inter RAT
RAU
Inter USN Intra E-UTRAN
Combined TAU
Inter USN GERAN/UTRAN
to E-UTRAN Combined
TAU

Inter TAU [0,+∞) Numbe Number of inter TAU process USN9810

Failures r failures by a VIP subscriber V900R011C01 or
on the LTE network. later version

Inter TAU [0.00,100. % Inter TAU process success USN9810

Success Ratio 00] ratio by a VIP subscriber on V900R011C01 or
the LTE network. later version
Inter TAU success ratio = (1 -
Number of inter TAU
failures/Number of inter TAU
requests) x 100%

Average Inter [0,+∞) ms Average delay of an inter USN9810

TAU Delay TAU process by a VIP V900R011C01 or
subscriber on the LTE later version
network.

Overlong Inter [0,+∞) Numbe Number of delays that exceed USN9810

TAU Delays r the exception threshold of an V900R011C01 or
inter TAU process by a VIP later version
subscriber on the LTE
network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 798

MME/Mobility/Handover
Parameter Range Unit Description Supported NE
Version

Intra E-UTRAN [0,+∞) Numbe Number of intra E-UTRAN USN9810

Handover r handover process requests by V900R011C01 or
Requests a VIP subscriber on the LTE later version
network.
Intra E-UTRAN handover
processes include:
X2 Handover
Intra MME S1 Handover
Inter MME S1 Handover

Intra E-UTRAN [0,+∞) Numbe Number of intra E-UTRAN USN9810

Handover r handover process failures by V900R011C01 or
Failures a VIP subscriber on the LTE later version
network.

Intra E-UTRAN [0.00,100. % Success ratio of an intra E- USN9810

Handover 00] UTRAN handover process V900R011C01 or
Success Ratio by a VIP subscriber on the later version
LTE network.
Intra E-UTRAN handover
success ratio = (1 - Number
of intra E-UTRAN handover
failures/Number of intra E-
UTRAN handover requests)
x 100%

Average Intra [0,+∞) ms Average delay of an intra E- USN9810

E-UTRAN UTRAN handover process V900R011C01 or
Handover Delay by a VIP subscriber on the later version
LTE network.

Overlong Intra [0,+∞) Numbe Number of delays that exceed USN9810

E-UTRAN r the exception threshold of an V900R011C01 or
Handover intra E-UTRAN handover later version
Delays process by a VIP subscriber
on the LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 799

Parameter Range Unit Description Supported NE

Version

Inter RAT [0,+∞) Numbe Number of inter RAT USN9810

Handover r handover process requests by V900R011C01 or
Requests a VIP subscriber on the LTE later version
network.
Inter RAT handover
processes include:
Intra USN UTRAN Iu mode
to E-UTRAN Inter RAT
handover
Inter USN UTRAN Iu mode
to E-UTRAN Inter RAT
handover
Intra USN E-UTRAN to
UTRAN Iu mode Inter RAT
handover
Inter USN E-UTRAN to
UTRAN Iu mode Inter RAT
handover

Inter RAT [0,+∞) Numbe Number of inter RAT USN9810

Handover r handover process failures by V900R011C01 or
Failures a VIP subscriber on the LTE later version
network.

Inter RAT [0.00,100. % Success ratio of an inter RAT USN9810

Handover 00] handover process by a VIP V900R011C01 or
Success Ratio subscriber on the LTE later version
network.
Inter RAT handover success
ratio = (1 - Number of inter
RAT handover failures/
Number of inter RAT
handover requests) x 100%

Average Inter [0,+∞) ms Average delay of an inter USN9810

RAT Handover RAT handover process by a V900R011C01 or
Delay VIP subscriber on the LTE later version
network.

Overlong Inter [0,+∞) Numbe Number of delays that exceed USN9810

RAT Handover r the exception threshold of an V900R011C01 or
Delays inter RAT handover process later version
by a VIP subscriber on the
LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 800

MME/Bearer Modification/UE Requested Bearer Resource Allocation

Parameter Range Unit Description Supported NE
Version

UE Requested [0,+∞) Number Number of UE requested USN9810

Bearer bearer resource allocation V900R013C00 or
Resource process requests by a VIP later version
Allocation subscriber on the LTE
Requests network.
The UE requested bearer
resource allocation process
includes:
UE requested bearer
resource allocation

UE Requested [0,+∞) Number Number of UE requested USN9810

Bearer bearer resource allocation V900R013C00 or
Resource process failures by a VIP later version
Allocation subscriber on the LTE
Failures network.

UE Requested [0.00,100 % Success ratio of a UE USN9810

Bearer .00] requested bearer resource V900R013C00 or
Resource allocation process by a VIP later version
Allocation subscriber on the LTE
Success Ratio network.
UE requested bearer
resource allocation success
ratio = (1 - Number of UE
requested bearer resource
allocation failures/Number
of UE requested bearer
resource allocation
requests) x 100%

UE Requested [0,+∞) ms Average delay of a UE USN9810

Bearer requested bearer resource V900R013C00 or
Resource allocation process by a VIP later version
Allocation subscriber on the LTE
Delay network.

Overlong UE [0,+∞) Number Number of delays that USN9810

Requested exceed the exception V900R013C00 or
Bearer threshold of a UE requested later version
Resource bearer resource allocation
Allocation process by a VIP subscriber
Delays on the LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 801

MME/Bearer Modification/Bearer Mod

Parameter Range Unit Description Supported NE
Version

Bearer Mod [0,+∞) Numb Number of bearer mod process USN9810

Requests er requests by a VIP subscriber on V900R011C01
the LTE network. or later version
Bearer mod processes include:
PDN GW initiated bearer
modification with bearer QoS
update
HSS Initiated Subscribed QoS
Modification
PDN GW initiated bearer
modification without bearer
QoS update

Bearer Mod [0,+∞) Numb Number of bearer mod process USN9810

Failures er failures by a VIP subscriber on V900R011C01
the LTE network. or later version

Bearer Mod [0.00,100 % Bearer mod process success USN9810

Success Ratio .00] ratio by a VIP subscriber on the V900R011C01
LTE network. or later version
Bearer mod success ratio = (1 -
Number of bearer mod failures/
Number of bearer mod
requests) x 100%

Average Bearer [0,+∞) ms Average delay of a bearer mod USN9810

Mod Delay process by a VIP subscriber on V900R011C01
the LTE network. or later version

Overlong [0,+∞) Numb Number of delays that exceed USN9810

Bearer Mod er the exception threshold of a V900R011C01
Delays bearer mod process by a VIP or later version
subscriber on the LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 802

MME/Bearer Modification/Bearer Resource Mod

Parameter Range Unit Description Supported NE
Version

Bearer [0,+∞) Number Number of bearer resource USN9810

Resource Mod mod process requests by a V900R011C01 or
Requests VIP subscriber on the LTE later version
network.
The bearer resource mod
process includes:
UE requested bearer
resource modification

Bearer [0,+∞) Number Number of bearer resource USN9810

Resource Mod mod process failures by a V900R011C01 or
Failures VIP subscriber on the LTE later version
network.

Bearer [0.00,100 % Success ratio of a bearer USN9810

Resource Mod .00] resource mod process by a V900R011C01 or
Success Ratio VIP subscriber on the LTE later version
network.
Bearer resource mod
success ratio = (1 - Number
of bearer resource mod
failures/Number of bearer
resource mod requests) x
100%

Bearer [0,+∞) ms Average delay of a bearer USN9810

Resource Mod resource mod process by a V900R011C01 or
Delay VIP subscriber on the LTE later version
network.

Overlong [0,+∞) Number Number of delays that USN9810

Bearer exceed the exception V900R011C01 or
Resource Mod threshold of a bearer later version
Delays resource mod process by a
VIP subscriber on the LTE
network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 803

GGSN/Accessability/Create PDP
Parameter Range Unit Description Supported NE
Version

Create PDP [0,+∞) Numb Number of Create PDP UGW9810

Requests er procedures of a VIP V900R011C01 or
subscriber on the GSM/ later version
UMTS network.

Create PDP [0,+∞) Numb Number of Create PDP UGW9810

Failures er failures of a VIP subscriber on V900R011C01 or
the GSM/UMTS network. later version

Create PDP [0.00,100 % Success ratio of the Create UGW9810

Success Ratio .00] PDP procedures of a VIP V900R011C01 or
subscriber on the GSM/ later version
UMTS network.
Create PDP Success Ratio =
(1 - Number of Create PDP
failures/Number of Create
PDP requests) x 100%

GGSN/PDP Update/Update PDP

Parameter Range Unit Description Supported NE
Version

Update PDP [0,+∞) Numb Number of Update PDP UGW9810

Requests er procedures of a VIP subscriber V900R011C01 or
on the GSM/UMTS network. later version

Update PDP [0,+∞) Numb Number of Update PDP UGW9810

Failures er failures of a VIP subscriber on V900R011C01 or
the GSM/UMTS network. later version

Update PDP [0.00,100. % Success ratio of the Update UGW9810

Success Ratio 00] PDP procedures of a VIP V900R011C01 or
subscriber on the GSM/UMTS later version
network.
Update PDP Success Ratio =
(1 - Number of Update PDP
failures/Number of Update
PDP requests) x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 804

SAE-GW/Accessability/Create Session
Parameter Range Unit Description Supported NE
Version

Create Session [0,+∞) Numbe Number of Create Session UGW9810

Requests r procedures of a VIP V900R011C01 or
subscriber on the LTE later version
network.

Create Session [0,+∞) Numbe Number of Create Session UGW9810

Failures r failures of a VIP subscriber V900R011C01 or
on the LTE network. later version

Create Session [0.00,100. % Success ratio of the Create UGW9810

Success Ratio 00] Session procedures of a VIP V900R011C01 or
subscriber on the LTE later version
network.
Create Session Success Ratio
= (1 - Number of Create
Session failures/Number of
Create Session requests) x
100%

SAE-GW/Accessability/Create Bearer
Parameter Range Unit Description Supported NE
Version

Create Bearer [0,+∞) Number Number of Create Bearer UGW9810

Requests procedures of a VIP V900R011C01 or
subscriber on the LTE later version
network.

Create Bearer [0,+∞) Number Number of Create Bearer UGW9810

Failures failures of a VIP subscriber V900R011C01 or
on the LTE network. later version

Create Bearer [0.00,100. % Success ratio of the Create UGW9810

Success Ratio 00] Bearer procedures of a VIP V900R011C01 or
subscriber on the LTE later version
network.
Create Bearer Success
Ratio = (1 - Number of
Create Bearer failures/
Number of Create Bearer
requests) x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 805

SAE-GW/Accessability/Create Indirect Data Forwarding

Parameter Range Unit Description Supported NE
Version

Create Indirect [0,+∞) Number Number of Create UGW9810

Data Indirect Data V900R011C01 or
Forwarding Forwarding later version
Requests procedures of a VIP
subscriber on the LTE
network.

Create Indirect [0,+∞) Number Number of Create UGW9810

Data Indirect Data V900R011C01 or
Forwarding Forwarding failures later version
Failures of a VIP subscriber on
the LTE network.

Create Indirect [0.00,100.00] % Success ratio of the UGW9810

Data Create Indirect Data V900R011C01 or
Forwarding Forwarding later version
Success Ratio procedures of a VIP
subscriber on the LTE
network.
Create Indirect Data
Forwarding Success
Ratio = (1 - Number
of Create Indirect
Data Forwarding
failures/Number of
Create Indirect Data
Forwarding requests)
x 100%

SAE-GW/Bearer Modification/Modify Bearer

Parameter Range Unit Description Supported NE
Version

Modify Bearer [0,+∞) Numb Number of Modify UGW9810

Requests er Bearer procedures of a V900R011C01 or
VIP subscriber on the later version
LTE network.

Modify Bearer [0,+∞) Numb Number of Modify UGW9810

Failures er Bearer failures of a VIP V900R011C01 or
subscriber on the LTE later version
network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 806

Parameter Range Unit Description Supported NE

Version

Modify Bearer [0.00,100.00] % Success ratio of the UGW9810

Success Ratio Modify Bearer V900R011C01 or
procedures of a VIP later version
subscriber on the LTE
network.
Modify Bearer Success
Ratio = (1 - Number of
Modify Bearer failures/
Number of Modify
Bearer requests) x
100%

SAE-GW/Bearer Modification/Update Bearer

Parameter Range Unit Description Supported NE
Version

Update Bearer [0,+∞) Numbe Number of Update UGW9810

Requests r Bearer procedures of a V900R011C01
VIP subscriber on the or later version
LTE network.

Update Bearer [0,+∞) Numbe Number of Update UGW9810

Failures r Bearer failures of a VIP V900R011C01
subscriber on the LTE or later version
network.

Update Bearer [0.00,100.00] % Success ratio of the UGW9810

Success Ratio Update Bearer V900R011C01
procedures of a VIP or later version
subscriber on the LTE
network.
Update Bearer Success
Ratio = (1 - Number of
Update Bearer failures/
Number of Update
Bearer requests) x 100%

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 807

SAE-GW/Bearer Modification/Modify Bearer Command

Parameter Range Unit Description Supported NE
Version

Modify Bearer [0,+∞) Numbe Number of Modify UGW9810

Command r Bearer Command V900R011C01
Requests procedures of a VIP or later version
subscriber on the LTE
network.

Modify Bearer [0,+∞) Numbe Number of Modify UGW9810

Command r Bearer Command V900R011C01
Failures failures of a VIP or later version
subscriber on the LTE
network.

Modify Bearer [0.00,100.00] % Success ratio of the UGW9810

Command Modify Bearer V900R011C01
Success Ratio Command procedures or later version
of a VIP subscriber on
the LTE network.
Modify Bearer
Command Success
Ratio = (1 - Number of
Modify Bearer
Command failures/
Number of Modify
Bearer Command
requests) x 100%

SAE-GW/Bearer Modification/Bearer Resource Command

Parameter Range Unit Description Supported NE
Version

Bearer Resource [0,+∞) Number Number of Bearer UGW9810

Command Resource Command V900R011C01
Requests procedures of a VIP or later version
subscriber on the LTE
network.

Bearer Resource [0,+∞) Number Number of Bearer UGW9810

Command Resource Command V900R011C01
Failures failures of a VIP or later version
subscriber on the LTE
network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 808

Parameter Range Unit Description Supported NE

Version

Bearer Resource [0.00,100.00] % Success ratio of the UGW9810

Command Bearer Resource V900R011C01
Success Ratio Command procedures or later version
of a VIP subscriber on
the LTE network.
Bearer Resource
Command Success
Ratio = (1 - Number of
Bearer Resource
Command failures/
Number of Bearer
Resource Command
requests) x 100%

Parameters for Viewing PS Core VIP Analysis - Voice CSFB Results

This section describes the parameters for querying PS Core VIP analysis voice CSFB results.
You can refer to the description when querying PS Core VIP analysis voice CSFB results.

Common
Parameter Rang Unit Description Supported NE Version
e

Deep N/A N/A ·When the dimension is USN9810 V900R011C01

Analysis Group, this parameter is or later version
used to switch from the
analysis results of a VIP
group to those of the VIP
subscribers in this group.
·When the dimension is
User, this parameter is used
to switch from the analysis
results of counters to those
of the calls.

Group N/A N/A Name of a VIP group. USN9810 V900R011C01

Name or later version

IMSI N/A N/A IMSI information of a USN9810 V900R011C01

subscriber. or later version
Note: Only when you have
the "User Identity" right,
you can view the IMSI
information.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 809

Parameter Rang Unit Description Supported NE Version

MSISDN N/A N/A MSISDN information of a USN9810 V900R011C01

subscriber. or later version
Note: Only when you have
the "User Identity" right,
you can view the MSISDN
information.

IMEI-TAC N/A N/A International mobile USN9810 V900R011C01

equipment identity-type or later version
allocation code (IMEI-
TAC) of the terminal used
by a VIP subscriber.

User ID N/A N/A ID of a VIP subscriber. USN9810 V900R011C01

or later version

Alias N/A N/A Alias of a VIP subscriber. USN9810 V900R011C01

You can obtain the user or later version
name in the VIP Group
Management window based
on the IMSI of the VIP
subscriber.

Terminal N/A N/A Type of the terminal used by USN9810 V900R011C01

Model a VIP subscriber. You can or later version
obtain the terminal type in
the Terminal Type
Management window based
on the IMEI-TAC of the
terminal used by the VIP
subscriber.

Total [0, Number Indicates the number of USN9810 V900R011C01

Reports +∞) records generated for all or later version
service types during the
network access of a
subscriber.

Service N/A N/A Service type for a following USN9810 V900R011C01

Type counter. or later version

Number of [0, Number Number of abnormal USN9810 V900R011C01

Abnormal +∞) counters in all counter sets or later version
KPIs determined based on the
result thresholds set when
engineers create a task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 810

MME/Accessability/Attach
Parameter Range Unit Description Supported NE
Version

Combined [0,+∞) Numb Number of times that a USN9810

Attach Requests er VIP subscriber initiates V900R013C00 or
the Combined Attach later version
procedure on the LTE
network.

Combined [0,+∞) Numb Number of times that the USN9810

Attach CS er Combined Attach V900R013C00 or
Failures procedure initiated by a later version
VIP subscriber on the
LTE network fails.

Combined [0.00,100. % Success ratio of the USN9810

Attach CS 00] Combined Attach V900R013C00 or
Success Ratio procedure, which is later version
initiated by a VIP
subscriber on the LTE
network, in the CS
domain.
Combined Attach CS
Success Ratio = (1 -
Number of failed
Combined Attach
requests in the CS
domain/Number of
Combined Attach
requests) x 100%

Combined [0,+∞) ms Average delay of the USN9810

Attach Delay Combined Attach V900R013C00 or
procedure initiated by a later version
VIP subscriber on the
LTE network.

Overlong [0,+∞) Numb Number of times that the USN9810

Combined er delay of the Combined V900R013C00 or
Attach Delays Attach procedure initiated later version
by a VIP subscriber on the
LTE network exceeds a
predefined exception
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 811

MME/Accessability/Paging
Parameter Range Unit Description Supported NE
Version

SGs CS Paging [0,+∞) Numbe Number of times that a USN9810

Requests r VIP subscriber initiates V900R013C00 or
the SGs CS Paging later version
procedure on the LTE
network.
The SGs CS Paging
procedure includes:
SGs Paging

SGs CS Paging [0,+∞) Numbe Number of times that the USN9810

Failures r SGs CS Paging procedure V900R013C00 or
initiated by a VIP later version
subscriber on the LTE
network fails.

SGs CS Paging [0.00,100 % Success ratio of the SGs USN9810

Success Ratio .00] CS Paging procedure V900R013C00 or
initiated by a VIP later version
subscriber on the LTE
network.
SGs CS Paging Success
Ratio = (1 - Number of
failed SGs CS Paging
requests/Number of SGs
CS Paging requests) x
100%

SGs CS Paging [0,+∞) ms Average delay of the SGs USN9810

Delay CS Paging procedure V900R013C00 or
initiated by a VIP later version
subscriber on the LTE
network.

Overlong SGs [0,+∞) Numbe Number of times that the USN9810

CS Paging r delay of the SGs CS V900R013C00 or
Delays Paging procedure later version
initiated by a VIP
subscriber on the LTE
network exceeds a
predefined exception
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 812

Parameter Range Unit Description Supported NE

Version

S1 CS Paging [0,+∞) Numbe Number of times that a USN9810

Requests r VIP subscriber initiates V900R012C00 or
the S1 CS Paging later version
procedure on the LTE
network.
The S1 CS Paging
procedure includes:
Paging

S1 CS Paging [0,+∞) Numbe Number of times that the USN9810

Failures r S1 CS Paging procedure V900R012C00 or
initiated by a VIP later version
subscriber on the LTE
network fails.

S1 CS Paging [0.00,100 % Success ratio of the S1 CS USN9810

Success Ratio .00] Paging procedure V900R012C00 or
initiated by a VIP later version
subscriber on the LTE
network.
S1 CS Paging Success
Ratio = (1 - Number of
failed S1 CS Paging
requests/Number of S1
CS Paging requests) x
100%

S1 CS Paging [0,+∞) ms Average delay of the S1 USN9810

Delay CS Paging procedure V900R012C00 or
initiated by a VIP later version
subscriber on the LTE
network.

Overlong S1 CS [0,+∞) Numbe Number of times that the USN9810

Paging Delays r delay of the S1 CS Paging V900R012C00 or
procedure initiated by a later version
VIP subscriber on the
LTE network exceeds a
predefined exception
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 813

MME/Accessability/Service Req
Parameter Range Unit Description Supported NE
Version

Extended [0,+∞) Numbe Number of times that a VIP USN9810

Service Req r subscriber initiates the V900R012C00 or
Requests Extended Service Req later version
procedure on the LTE
network.
The Extended Service Req
procedure includes:
Extended Service Request

Extended [0,+∞) Numbe Number of times that the USN9810

Service Req r Extended Service Req V900R012C00 or
Failures procedure initiated by a VIP later version
subscriber on the LTE
network fails.

Extended [0.00,1 % Success ratio of the USN9810

Service Req 00.00] Extended Service Req V900R012C00 or
Success Ratio procedure initiated by a VIP later version
subscriber on the LTE
network.
Extended Service Req
Success Ratio = (1 - Number
of failed Extended Service
Req requests/Number of
Extended Service Req
requests) x 100%

Extended [0,+∞) ms Average delay of the USN9810

Service Req Extended Service Req V900R012C00 or
Delay procedure initiated by a VIP later version
subscriber on the LTE
network.

Overlong [0,+∞) Numbe Number of times that the USN9810

Extended r delay of the Extended V900R012C00 or
Service Req Service Req procedure later version
Delays initiated by a VIP subscriber
on the LTE network exceeds
a predefined exception
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 814

MME/Mobility/TAU
Parameter Range Unit Description Supported NE
Version

Intra Combined [0,+∞) Number Number of times that a USN9810

TAU Requests VIP subscriber initiates V900R012C00SP
the Intra Combined C300 or later
TAU procedure on the version
LTE network.
The Intra Combined
TAU procedure
includes:
Intra USN Intra E-
UTRAN Combined
TAU
Intra USN GERAN to E-
UTRAN Inter RAT
Combined TAU
Intra USN UTRAN to E-
UTRAN Inter RAT
Combined TAU

Intra Combined [0,+∞) Number Number of times that the USN9810

TAU CS Intra Combined TAU V900R012C00SP
Failures procedure initiated by a C300 or later
VIP subscriber on the version
LTE network fails.

Intra Combined [0.00,100.0 % Success ratio of the Intra USN9810

TAU CS 0] Combined TAU V900R012C00SP
Success Ratio procedure initiated by a C300 or later
VIP subscriber on the version
LTE network.
Intra Combined TAU
CS Success Ratio = (1 -
Number of failed Intra
Combined TAU
requests/Number of
Intra Combined TAU
requests) x 100%

Intra Combined [0,+∞) ms Average delay of the USN9810

TAU Delay Intra Combined TAU V900R012C00SP
procedure initiated by a C300 or later
VIP subscriber on the version
LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 815

Parameter Range Unit Description Supported NE

Version

Overlong Intra [0,+∞) Number Number of times that the USN9810

Combined TAU delay of the Intra V900R012C00SP
Delays Combined TAU C300 or later
procedure initiated by a version
VIP subscriber on the
LTE network exceeds a
predefined exception
threshold.

Inter Combined [0,+∞) Number Number of times that a USN9810

TAU Requests VIP subscriber initiates V900R012C00SP
the Inter Combined C300 or later
TAU procedure on the version
LTE network.
The Inter Combined
TAU procedure
includes:
Inter USN Intra E-
UTRAN Combined
TAU
Inter USN GERAN/
UTRAN to E-UTRAN
Combined TAU

Inter Combined [0,+∞) Number Number of times that the USN9810

TAU CS Inter Combined TAU V900R012C00SP
Failures procedure initiated by a C300 or later
VIP subscriber on the version
LTE network fails.

Inter Combined [0.00,100.0 % Success ratio of the Inter USN9810

TAU CS 0] Combined TAU V900R012C00SP
Success Ratio procedure initiated by a C300 or later
VIP subscriber on the version
LTE network.
Inter Combined TAU
CS Success Ratio = (1 -
Number of failed Inter
Combined TAU
requests/Number of
Inter Combined TAU
requests) x 100%

Inter Combined [0,+∞) ms Average delay of the USN9810

TAU Delay Inter Combined TAU V900R012C00SP
procedure initiated by a C300 or later
VIP subscriber on the version
LTE network.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 816

Parameter Range Unit Description Supported NE

Version

Overlong Inter [0,+∞) Number Number of times that the USN9810

Combined TAU delay of the Inter V900R012C00SP
Delays Combined TAU C300 or later
procedure initiated by a version
VIP subscriber on the
LTE network exceeds a
predefined exception
threshold.

MME/Mobility/Handover
Parameter Range Unit Description Supported NE
Version

CSFB PS [0,+∞) Number Number of times that a USN9810

Handover VIP subscriber initiates V900R013C00
Requests the CSFB PS Handover or later version
procedure on the LTE
network.
The CSFB PS Handover
procedure includes:
Intra USN E-UTRAN to
UTRAN Iu mode Inter
RAT handover
Inter USN E-UTRAN to
UTRAN Iu mode Inter
RAT handover

CSFB PS [0,+∞) Number Number of times that the USN9810

Handover CSFB PS Handover V900R013C00
Failures procedure initiated by a or later version
VIP subscriber on the
LTE network fails.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 817

Parameter Range Unit Description Supported NE

Version

CSFB PS [0.00,100.0 % Success ratio of the CSFB USN9810

Handover 0] PS Handover procedure V900R013C00
Success Ratio initiated by a VIP or later version
subscriber on the LTE
network.
CSFB PS Handover
Success Ratio = (1 -
Number of failed CSFB
PS Handover requests/
Number of CSFB PS
Handover requests) x
100%

CSFB PS [0,+∞) ms Average delay of the USN9810

Handover Delay CSFB PS Handover V900R013C00
procedure initiated by a or later version
VIP subscriber on the
LTE network.

Overlong CSFB [0,+∞) Number Number of times that the USN9810

PS Handover delay of the CSFB PS V900R013C00
Delays Handover procedure or later version
initiated by a VIP
subscriber on the LTE
network exceeds a
predefined exception
threshold.

3.9.9 FAQ: How Do I Set the LTE All-Signaling Switch to On?

This section describes how to set the LTE all-signaling switch to on by using the application
subscription function of the Nastar.

Prerequisites
Relationships between HSSs and eNodeBs have been configured. For detailed operations, see
2.3.8 Configuring Relationships Between HSSs and eNodeBs (Optional).

Procedure
Step 1 In the Data Subscription Management window, click the LTE FDD or LTE TDD tab.

Step 2 Select NEs in the navigation tree.

Step 3 On the VIP analysis tab page, select Group Level and click Open.

Step 4 Select a VIP group containing important VIP subscribers and select NEs. Then, click OK.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 818

NOTE

The number in the brackets following the name of a VIP group indicates the number of important VIP
subscribers contained in the VIP group. For example, abc:[2] indicates that the VIP group whose name is
abc contains two important VIP subscribers.

Step 5 In the displayed dialog box (asking whether you want to query the unique trace reference number
of each VIP subscriber from the HSS), click Confirm. Then, the Nastar queries the trace
reference numbers of the VIP subscribers from the corresponding HSS.

If... Then...

The trace reference The User Level tab page is automatically displayed for you to
number of a VIP view the trace reference number (which is available on the HSS)
subscriber is available on and all-signaling switch status of the VIP subscriber.
the HSS

The trace reference The User Level tab page is automatically displayed. The Nastar
number of a VIP randomly assigns a trace reference number, which is unique in
subscriber is unavailable the Nastar system, to the VIP subscriber.
on the HSS
The Nastar regards that the all-signaling switch of this VIP
subscriber has never been set to on by default.

Step 6 On the User Level tab page, click Open.

Step 7 Select eNodeB interfaces whose all-signaling switches need to be set to on. All eNodeB
interfaces are selected by default.

Step 8 Select VIP subscribers whose all-signaling switches need to be set to on.
l You are allowed only to select VIP subscribers whose trace reference numbers are available
and whose all-signaling switches have never been set to on.
l You can select one VIP subscriber at a time through a check box. Alternatively, you can
right-click anywhere in the table area and choose HSS Name from the shortcut menu to select
all VIP subscribers served by the selected HSS.

Step 9 Click Confirm.

Check that the data switch is successfully turned on by viewing the displayed information in the
Log Info area.

----End

3.10 Complaint Analysis Support

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 819

Context
l The key information of the complaint subscriber includes International Mobile Subscriber
Identity (IMSI), MSISDN number, or peer MSISDN of the complaint subscriber. All the
networks support the analysis through the IMSI; only the PS Core network supports the
analysis through the MSISDN; and only the GSM CS network supports the analysis through
the peer MSISDN.
l This function can be used to quickly locate and resolve problems. Normally there is no way
to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will
be used during the troubleshooting. However, this function provides an anonymous data
processing method. You are obligated to take considerable measures, in compliance with
the laws of the countries concerned and the user privacy policies of your company, to ensure
that the personal data of users is fully protected.

3.10.1 Basics of Complaint Analysis Support

This section describes the basics of complaint analysis support, including the function and
technical specification. The basic knowledge helps you perform complaint analysis support and
optimization. You are recommended to read this section before performing complaint analysis
support.

Functions of Complaint Analysis Support

This section describes how to use the Nastar to perform complaint analysis support based on
call records of subscribers before and after complaints. This helps to locate and solve complaint
problems.

Function Description
The Nastar obtains the call event records of complaining subscribers, and then filters, aggregates,
and analyzes data based on a specified history period and detailed call records of subscribers in
a specified area. This can assist you in locating and solving problems. The complaint analysis
support function consists of the aggregation and analysis of cause types in call reports of
complaining subscribers, aggregation and analysis of information about call reports of
complaining subscribers, analysis of detailed information about call reports of complaining
subscribers, analysis of procedure before signaling release in call reports of complaining
subscribers, analysis of active cells in call reports of complaining subscribers, and so on.

The function supports the following analysis type:

l Supports the complaint analysis support of one network.
l Supports the combined complaint analysis support between the networks on the RAN side,
including GSM/UMTS, and LTE FDD/LTE TDD.
l Supports the combined complaint analysis support between the networks on the RAN side
and the networks on the PS Core side.

For details about the detailed function, see Table 3-32.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 820

Table 3-32 Function description of complaint analysis support

Function Type Description Supported

Network

Aggregation and Helps network engineers filter and aggregate call GSM/
analysis of cause reports based on exception causes. UMTS/
types in call reports LTE/PS
of complaining Core
subscribers

Summary and Provide an information overview about all the filtered GSM/
analysis of call call records. The information includes the information UMTS/
reports of such as access time, access cell, release time, release LTE/PS
complaining cell, service duration, and so on. This function helps Core
subscribers network engineers quickly identify abnormal call
records (for example, too-short-time call records) and
preliminarily learn the situation of complaining
subscribers.

Analysis of detailed Provides the detailed information about all the filtered GSM/
call reports of call records. The information includes the subscriber UMTS/
complaining information, call access information, call release LTE/PS
subscribers information, and handover information. This function Core
helps network engineers learn the key events that occur
during calls, service usage, and measurement reports
(MRs) before signaling release, accurately and quickly
assisting in problem location.

Analysis of Provides the detailed procedure before signaling GSM/

procedure before release of all the filtered subscribers. This function UMTS/LTE
signaling release in helps network engineers locate problems based on the
call reports of information before signaling release.
complaining
subscribers

Analysis of Provides MR details and trend charts of measurement GSM

measurement counters, including TA, DLRxLevel, DLRxQuality/
reports (MRs) on Level, ULRxQuality/Level, MS/BTS Power, and VQI.
calls of complaint The VQI indicates the voice quality during services and
subscribers before helps network engineers more accurately locate voice
call release quality problems.

Provides information about the serving cells of UMTS/LTE

subscribers before call release and the neighboring
cells. This helps engineers analyze and locate
problems.

Mobility analysis Provides handover information of a terminal and helps GSM/

network engineers to learn about all cells that are UMTS/LTE
recorded in abnormal call records.

Service analysis Analyzes RAB-related counters and provides network UMTS/LTE

quality information about a service.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 821

Function Type Description Supported

Network

Analysis results Geographically displays the cells to which GSM/

displayed through complaining subscribers have gained access and the UMTS/LTE
geographic cells from which complaining subscribers have been
observation released.

Principles of Complaint Analysis Support

This section describes the data source and the function principles of the complaint analysis
support.

NOTE

l On the GSM network, if you want to view the comprehensive measurement report information or the VQI,
you need to obtain the MR data on the RAN side. The information in the original MR data can replace the
measurement report information in the CHR data, so that measurement report information more
comprehensively and the voice quality analysis more accurately.
l On the LTE network, the CHR data includes the eNodeB CHR data and the MME CHR data. The MME
CHR data provides the IMSI and IMEI information.
l On the PS Core network, the CHR data includes the SGSN/MME CHR data and the GGSN/SAE-GW CHR
data.
l The CHR flow control function has been available since BSC6900 V900R016C00 and BSC6910
V100R016C00. When the SPU CPU load on an UMTS RNC exceeds a predefined threshold, the RNC
restricts the output of CHR event blocks, which affects the correctness of counters in Nastar analysis results.
For details about the CHR flow control policies, see the related NE product documentation.

Function Principles
Figure 3-49 shows the principles for collecting, importing, and analyzing data on the Nastar.
For detailed operations, see Table 3-33.

NOTE

This section describes how the function is implemented when the Nastar is deployed using the direct networking
scheme.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 822

Figure 3-49 Principle for analysis function

Table 3-33 Description of complaint analysis support

User Scen Proce Sour Desti Purpose

Oper e dure ce nation
ation

1. GSM Issue a Nasta eSAU To turn on the data source switch on the NE
Subscr / basic r side. After a user enables the basic data
ibe to UM data Serve subscription function (GSM complaint
basic TS subscri r analysis support or UMTS complaint analysis
data netw ption support) on the Nastar client, the Nastar issues
ork comma a basic data subscription command to the
nd eSAU.

Issue eSA U2000 To issue an MML command to the U2000/

an U / M2000.
MML M2000
comma
nd

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 823

User Scen Proce Sour Desti Purpose

Oper e dure ce nation
ation

Forwar U200 BSC/ To forward the MML command to the NE

d the 0/ RNC through the U2000/M2000, requesting the NE
MML M20 to generate raw data.
comma 00
nd

Upload BSC/ SAU To upload the raw data to the SAU.

raw RNC
data

PS Issue a Nasta eSAU To turn on the data source switch on the NE

Core basic r side. After a user enables the basic data
netw data Serve subscription function (PS Core complaint
ork subscri r analysis support) on the Nastar client, the
ption Nastar issues a basic data subscription
comma command to the eSAU.
nd

Issue eSA U2000 To issue an MML command to the U2000/

an U / M2000.
MML M2000
comma
nd

Forwar U200 SGSN/ To forward the MML command to the NE,

d the 0/ MME requesting the NE to generate raw data.
MML M20
comma 00
nd

Upload SGS PS To upload the raw data to the PS SAU.

raw N/ SAU NOTE
data MM The generation and transmission of the GGSN/
E/ SAE-GW CHR data is not triggered by the Nastar
GGS subscription command. The GGSN/SAE-GW CHR
data will be uploaded to the PS SAU through
N/
Huawei internal protocols in real time after the CHR
SAE- data switch is enabled.
GW

LTE Issue a Nasta eSAU To turn on the data source switch on the NE
netw basic r side. After a user enables the basic data
ork data Serve subscription function (LTE complaint analysis
subscri r support) on the Nastar client, the Nastar issues
ption a basic data subscription command to the
comma eSAU.
nd

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 824

User Scen Proce Sour Desti Purpose

Oper e dure ce nation
ation

Issue a eSA U2000 To issue a subscription command to the

subscri U / U2000/M2000.
ption M2000
comma
nd

Forwar U200 eNode To forward the subscription command to the

d the 0/ B NE, requesting the NE to generate raw data.
subscri M20
ption 00
comma
nd

Upload eNod Trace l To collect the data from Trace Server after
raw eB/ Server/ uploading the raw data (eNodeB CHR)
data MM LTE from the eNodeB to the Trace Server.
E SAU l To upload the raw data (MME CHR) from
the MME to the LTE SAU directly.
NOTE
The generation and transmission of the MME
CHR data is not triggered by the Nastar
subscription command. The MME CHR data
will be uploaded to the LTE SAU through
Huawei internal protocols in real time after the
CHR data reporting values are configured and
the CHR data transmission switch is enabled.

2. - Deliver Nasta SAU/ To deliver a data-preprocessing request to the

Create a data- r LTE SAU/LTE SAU/PS SAU through the eSAU,
and prepro Serve SAU/ requesting the SAU/LTE SAU/PS SAU to start
execut cessing r PS the data-preprocessing task.
e an task SAU
analys (direct)
is task
Upload SAU/ eSAU To upload preprocessed data to the eSAU.
prepro LTE
cessed SAU/
data PS
(direct) SAU

Upload eSA Nastar To aggregate the data reported by SAU/LTE

data U Server SAU/PS SAU, generate data analysis results,
analysi and upload the data analysis results to the
s Nastar server.
results

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 825

User Scen Proce Sour Desti Purpose

Oper e dure ce nation
ation

3. - Displa - Nastar To display analysis results on the Nastar client.

View y Server
analys analysi
is s
results results

Technical Specifications for Complaint Analysis Support

This section describes the technical specifications, including the analysis ability and the range
of analysis time.

Item Service Specifications

Execution type One-time task

Network scale for one <= Maximum management capacity of the Nastar
analysis task NOTE
One PS Core complaint analysis support task supports a maximum of
20,000 non-traffic xDRs. This specification does not apply to traffic xDRs.

Number of subscribers l <= 2,000 complaining subscribers (for all networks when
allowed in one analysis IMSIs are used for analysis; the value is the sum of values of
task all networks.)
l <= 2,000 complaining subscribers (only for PS Core network
when MSISDNs are used for analysis)
l <= 200 complaining subscribers (only for GSM CS network
when peer MSISDNs are used for analysis)

Number of allowed <= 500 (for all RATs)

analysis tasks

Time range for data in Last 7 days (GSM/UMTS/LTE/PS Core/ hybrid networking)
one analysis task

Duration of one analysis GSM/UMTS/LTE/PS Core: <= 210 minutes

task

Default duration for l GSM: 7 days

storing analysis data l UMTS: 7 days
l LTE: 7 days
l PS Core: 30 days

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 826

Item Service Specifications

Maximum duration for l GSM: 7 days

storing analysis data l UMTS: 7 days
l LTE: 7 days
l PS Core
– RH2288 server: When the used disk space exceeds 10 TB,
the system automatically deletes the earliest complaint call
details data. In addition, complaint call details files can be
stored for a maximum of 30 days based on the standard
traffic model.
– ATAE cluster system: Complaint call details files can be
stored for a maximum of 3 days in the standard
configuration and for a maximum of 15 days in the
enhanced configuration based on the default traffic model.

3.10.2 Preparations for Complaint Analysis Support

Before running a complaint analysis task, you must check and prepare the basic information to
ensure that the complaint analysis task can be performed successfully. You must read this section
before performing complaint analysis support.

Before running a complaint analysis support task, you must check and prepare the following
information:
l Checking the License Information and User Rights
l Preparing Basic Data
l Checking the Data Source Environment

Checking the License Information and User Rights

Check that you have loaded a valid license for complaint analysis support to the Nastar system,
and the login users have had the related rights. For details, see Table 3-34.

Functio Required license Required rights (Security > Security Management

n > User)

Commo - To control the User identity right, otherwise, you can not
n view the integrated IMSI information.
Function operation rights: Operation Rights > Select >
Operation > Nastar Security Information
Management > User Identity

Preparing Basic Data

Before analyzing, prepare the following basic data described in Table 3-35 for performing the
task successfully.

Table 3-35 Required basic data of complaint analysis support

Data Function Operation

Type

Configur The configuration data of If the OSS information has been already configured,
ation the NE corresponding to the Nastar automatically and periodically collects
Data a complaint location and imports the configuration data after the OSS
(Mandato allows users to correctly and NE information is configured. You can also
ry) obtain the data of manually collect the configuration data before the
complaining subscribers specified time period starts. After the configuration
from the network and data is imported, you can choose Maintenance >
analyze the cell Data Maintenance Management to check
information in MRs and whether the configuration data is available in the
the information about the Nastar database. For detailed information about
following cells: cells to collecting, importing, and checking, see 2.5.2
which subscribers have Checking the Integrity of Configuration Data.
gained access, cells After the configuration data has been successfully
which subscribers have imported, you are advised to check the validity of
released, and cells to the configuration data. The purpose is to avoid
which subscribers have expiration of configuration data due to network
handed over. adjustment. Expired configuration data may cause
NOTE incorrect cell information in the analysis result. For
If you only perform the PS detailed operations, see Checking Engineering
Core complaint analysis
Parameters and Configuration Data.
support, you do not need
the configuration data.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 832

Data Function Operation

Type

Complain l Time Enter the complaining subscriber information when

ing The Nastar only creating complaint analysis support.
Subscribe analyzes complaints NOTE
r that occurred in the The Nastar provides sufficient protection for service data
Informati latest seven days. used by this function, such as IMSI and IMEI information,
on to ensure personal data security. For details about the
l Place service data and protection policies, seeDescriptions >
(Mandato The NE information Nastar Security Description > Application Security >
ry) that the problem Protecting Private Subscriber Data.
occurs, including one The Nastar provides an anonymization mechanism for
or multiple NEs. The processing personal data, such as the IMSI, IMEI,
Nastar can analyze MSISDN, and IMEISV. After this mechanism is used, the
complaints that occur Nastar no longer allows you to enter the plaintext IMSI
and MSISDN. In this situation, you need to contact
on the whole network
telecom operators to obtain the encrypted IMSI. The
(The network can Nastar does not support the encrypted MSISDN. Telecom
involve multiple operators can contact the Huawei technical support
OSSs). It does not engineers to visit http://support.huawei.com and choose
require the precise Support > Software > Global Service > Managing
information about the Customer Experience Service-SmartCare > Network
Optimization Service > GENEX Mobile Manager >
complaining place.
HMACUtil.
However, it is
You have checked whether the subscriber identity
recommended that
anonymization switch or the encryption key is changed.
you locate the If the subscriber identity anonymization switch or the
complaining place to encryption key is changed, see 2.12.3 Troubleshooting
the base station Problems Caused by Change of the Subscriber
controller level or cell Identity Anonymization Switch or the Encryption
level to ensure Key.
performance of the If the number of complaining subscribers to be
complaint analysis analyzed is large, you can save the IMSI, STMSI,
support function. MSISDN or peer MSISDN information in the files
l IMSI, STMSI, in .xls/.xlsx/.csv format.
MSISDN, or peer NOTE
MSISDN The IMSI or MSISDN information stores a maximum of
2,000 records. Each IMSI must contain 15 digits. The peer
– IMSI: Supported MSISDN information stores a maximum of 200 records.
by every network.
– STMSI: Only
supported by the
LTE network.
– MSISDN: Only
supported by the
PS Core network.
– Peer MSISDN:
Only supported by
the GSM network
when choosing the
CS service.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 833

Data Function Operation

Type

– You can obtain

either the above
information of a
complaining
subscriber for
analysis when
supporting multi
information.

Engineeri The engineering In the navigation tree of the Analysis Task

ng parameters for a specific Management window, choose System Function >
Paramete area are used for the Engineering Parameter Management. Then
rs geographic observation double-click Engineering Parameter
(Optional of the analysis result. You Management to check whether engineering
) do not need to prepare the parameters have been imported. If the parameters
engineering parameters if are unavailable, you must import the engineering
the geographic display of parameter template. The Nastar can import the
the analysis result is not engineering parameter files in .csv, .xls, and .xlsx
required. format, but engineering parameter fields must be set
correctly. For details about the fields and templates
supported by the Nastar, see Appendix:
Engineering Parameter Templates.
After the engineering parameters are successfully
imported, you are advised to check whether the
engineering parameters are consistent with the
configuration data and whether the engineering
parameters are correct. For example, if the cell
identification information in the engineering
parameters is not consistent with the configuration
data, the TOP cell will be repeated in the network
geographic observation function.

Map File The map file for a specific You can import the map files in wor, tab, or sxwu
(Optional area displays the analysis format to the Nastar. If the PC is connected to the
) result geographically. Internet, you can view analysis results on the
You do not need to Google Earth. For details, see 2.5.4 Preparing the
prepare the map file if you Map File (Optional).
do not want to view the
analysis result on the
map.

Checking the Data Source Environment

Before analyzing, check that the used NE versions and U2000/M2000 versions are consistent
with those described in Table 3-36.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 834

Table 3-36 Description of the data source environment

Net Description
wor
k

GSM l GSM RAN CS analysis: Check that the matching U2000/M2000 version is
V200R012C00 (or later), and the NE version is BSC6900 V900R014C00 (or later)
or BSC6910 V100R014C00 (or later).
l GSM RAN PS analysis: Check that the matching U2000/M2000 version is
V200R012C00 (or later), and the NE version is BSC6900 V900R014C00 (or
later), and BSC6910 V100R014C00 (or later).
l Check that the user identity information (IMSI and IMEI) reporting switch has
been turned on. For detailed operations, see Commissioning the Function of
Obtaining the Data > Preparing for Obtaining Data > Preparing for
Obtaining Data(GSM) > Turning On the User Identity Information
Reporting Switch (GSM) in Nastar Commissioning Guide.
l (Optional) Only calculating the counters related to speech quality, you need to
manually turn on the switches for reporting uplink and downlink speech quality
information in MR data. For detailed operations, see Commissioning the
Function of Obtaining the Data > Preparing for Obtaining Data > Preparing
for Obtaining Data(GSM) > Turning On the Switches for Reporting Speech
Quality Information in MR Data (GSM Complaint Analysis Support,
Optional) in Nastar Commissioning Guide.
l (Optional) If you want to view the counters about the PS measurement
information, check that the PS network control mode is set. For detailed
operations, see Commissioning the Function of Obtaining the Data >
Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) >
Setting the PS Network Control Mode in Nastar Commissioning Guide.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 835

Net Description
wor
k

LTE l Check that the matching U2000/M2000 version is U2000/M2000

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 836

3.10.3 Process of Complaint Analysis Support

This section describes the process of complaint analysis support and the steps of each procedure.

This section includes the following information:

l Prerequisites
l Procedure
l Subscription Task Parameters
l Analysis Task Parameters

Prerequisites
You have finished the preparation of complaint analysis support, such as checking the operation
rights, preparing the basic data, and so on. For details, see 3.10.2 Preparations for Complaint
Analysis Support.

Procedure
Figure 3-50 shows the process of complaint analysis support. For details, see Table 3-37.

Figure 3-50 Flowchart for complaint analysis support

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 837

Table 3-37 Description of complaint analysis support procedures

No. Proced Description Reference

ure for Detailed
Operations

(1) LTE NOTE For details

Periodic For LTE analysis themes, you must set this parameter before about
basic subscription. Otherwise, the Nastar uses the current value
MR parameters,
of this parameter to perform basic subscription.
Period see LTE
Setting Navigation path: Choose Maintenance > LTE Periodic MR
Periodic MR Period Setting Period
Procedure: Setting
1. In the LTE Periodic MR Period Setting window, Parameters
set Periodic MR Period and Number of Sampled
Users.
2. Click Configure.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 838

No. Proced Description Reference

ure for Detailed
Operations

Subscrib NOTE 2.6

e to The basic data subscription function has high security Subscribing
requirements. You are advised to contact the administrator who
analysis to Analysis
is authorized to subscribe to basic data to turn on the data switch.
data Data
(basic) Navigation path: Choose Maintenance > Data
Subscription Management
Procedure:
1. In the Data Subscription Management window,
click *** tab.
*** indicates the network.
2. In the left navigation tree, select the NEs to be
configured.
3. On the Basic Subscription Settings tab page, click
Set.
4. In the displayed Basic Subscription Settings dialog
box, set complaint analysis support data to ON.
l In the GSM network, the switch names are
Complaint Analysis Support Data(CHR-CS),
Complaint Analysis Support Data(CHR-PS),
and Complaint Analysis Support Data(MR-
CS) for subscribing to the CHR-CS, CHR-PS
data, and MR data of the GSM network.
If you have obtained the MR data, you can view
the comprehensive measurement report
information, and assess business voice quality
through VQI accurately. If not, you can only view
a small number of measurement reports, and
assess voice quality generally.
l In the UMTS network, the switch name is
Complaint Analysis Support Data(CHR) for
subscribing to the CHR data of the UMTS
network.
l In the LTE FDD, and LTE TDD network, the
switch name is Complaint Analysis Support
Data(CHR).
l In the PS Core network, the switch name is
Complaint Analysis Support Data(SGSN/
MME-CHR).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 839

No. Proced Description Reference

ure for Detailed
Operations
NOTE
l The Nastar cannot issue all MML commands to
network elements (NEs) by using the basic
subscription function. To obtain data, confirm that
you have manually issued the CHR enabled
operation. For details, see 3.10.2 Preparations for
Complaint Analysis Support.
l Disable procedures (such as the Service Request
procedure and the PDP MOD procedure) that
involve all signaling information on the CN side.
Otherwise, a large amount of data is collected from
the CN and consequently the SGSN or MME cannot
upload the data in time. As a result, certain data
required by the Nastar is missing or delayed being
reported.
5. Click Confirm.
Check that the data switch is successfully turned on
by viewing the displayed information in the Log
Info area.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 840

No. Proced Description Reference

ure for Detailed
Operations

(2) Create a Navigation path: Choose Theme Function > User l For
complai Assurance > Complaint Analysis Support in the details,
nt navigation tree of the Analysis Task Management see 2.8
analysis window. Creating
support Procedure: an
task Analysis
1. Double-click the Complaint Analysis Support Task.
node.
l For
2. Set the task name and task remarks. Click Next. details
3. On the Set Analysis Type tab page, set a net type and about the
a data type. parameter
4. On the Select NE(s) tab page, click Select to select s, see
the NEs located in an area where subscribers Analysis
complained about. Task
Paramete
5. On the Select Complaining User tab page, click
rs.
Add or Import to set the IMSI information (user
alias, IMSI, and remark), STMSI, MSISDN, or peer
MSISDN of the complaining subscriber.
l IMSI: Supported by every network.
l STMSI: Only supported by the LTE network.
l MSISDN: Only supported by the PS Core
network.
l Peer MSISDN: Only supported by the GSM
network when choosing the CS service.
l You can obtain either the above information of a
complaining subscriber for analysis when
supporting multi information.
6. On the Set KPI Threshold tab page, set the abnormal
threshold of each KPI. Click Next.
7. Choose an analysis time segment. The Nastar obtains
the relevant analysis data in the time period.
NOTE
To obtain accurate subscriber information, you are advised
to set Execute on to 1 hour.
8. Click Finish.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 841

No. Proced Description Reference

ure for Detailed
Operations

(3) View Navigation path: In the upper right area of the Analysis l For
complai Task Management window, select an analysis task in details,
nt the Finished state. In the lower right of the Task see 2.9
analysis Result area, select a result record of the task. Querying
support Procedure: Analysis
results Results.
1. Double-click an analysis result of the task.
l For
2. In the displayed Complaint Analysis Support details on
window, view the complaint analysis support results the
interface
descriptio
n, see
3.10.4
Referenc
e for
Complai
nt
Analysis
Support
Interface
.

(4) Export Navigation path: Click the icon on the toolbar in the l For
complai upper left part of each analysis results window. details,
nt Procedure: see 2.11
analysis Exportin
support 1. Click the export icon on the toolbar. g
reports 2. Specify the export path and export format. Analysis
3. Click Save. Reports.
l For
details on
the
interface
descriptio
n, see
3.10.4
Referenc
e for
Complai
nt
Analysis
Support
Interface
.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 842

LTE Periodic MR Period Setting Parameters

Parameter Description

Number of Specify the number of sampled subscribers in periodic MRs. A larger

Number of Specify the number of MRs times in periodic.

Times MRs l The value of this parameter can be 16, Unbounded.
Are Reported
l The default value is 16.

Subscription Task Parameters

Basic Subscription

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 843

RA Parameter Description
T

GS Complaint Switch for enabling or disabling the reporting of CS CHR data. You
M Analysis can retain the default state of the switch.
Support
Data (CHR- You can click to set the following advanced parameters:
CS) l Service: specifies the service types for which CS CHR data is to be
reported. The service types include call, short message service
(SMS), and location update (LU). You can select all or none of the
service types or retain the existing settings.
l Error: specifies the types of information contained in reported CS
CHR data. If you select All, all CS CHR data containing normal
and abnormal service procedures is reported.
l Event Block: specifies that GSM does not support event blocks.
l All Signaling: specifies the types of all signaling messages
contained in reported CS CHR data. For details, see the SET
GCSCHRCTRL command in the related NE product
documentation. You can select all or none of the types or retain the
existing settings.
l HQI Threshold: specifies the method of calculating the HQI
threshold during CS CHR tracing. For details, see the SET
BSCEXSOFTPARA command in the related NE product
documentation. You can set this parameter to a value ranging from
0 to 6 or retain the existing settings.
NOTE
HQI Threshold applies only to BSC6900 V900R015C00 (and later
versions) and BSC6910 V100R015C00 (and later versions).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 844

RA Parameter Description
T

Complaint Switch for enabling or disabling the reporting of PS CHR data. You
Analysis can retain the default state of the switch.
Support
Data (CHR- You can click to set the following advanced parameters:
PS) l Event Block: specifies that GSM does not support event blocks.
l Service Type Information Report Switch: specifies whether to
report information about the service types contained in PS CHRs.
For details, see the SET GPSCHRCTRL command in the related
NE product documentation.
l Judge Delay-Related Services: For details, see the SET
GPSCHRCTRL command in the related NE product
documentation.
l Overlong DL PDU Sending Delay Threshold for Delay-Related
Services: For details, see the SET GPSCHRCTRL command in
the related NE product documentation.
l Overlong UL PDU Receiving Delay Threshold for Delay-Related
Services: For details, see the SET GPSCHRCTRL command in
the related NE product documentation.
l Abnormal UL/DL PDU Interval Threshold for Delay-Related
Services: For details, see the SET GPSCHRCTRL command in
the related NE product documentation.
l UL PDU Response Waiting Threshold for Delay-Related Services:
For details, see the SET GPSCHRCTRL command in the related
NE product documentation.
l Overlong DL PDU Sending Delay Threshold for Rate-Related
Services: For details, see the SET GPSCHRCTRL command in
the related NE product documentation.
l Overlong UL PDU Receiving Delay Threshold: For details, see the
SET GPSCHRCTRL command in the related NE product
documentation.

Complaint Switch for enabling or disabling the reporting of CS MR data. You can
Analysis retain the default state of the switch.
Support
Data (MR- You can click to set the following advanced parameters:
CS) l Collection Switch: For details, see the SET GMRCTRL command
in the related NE product documentation.
l Original Sampling Rate: For details, see the SET GMRCTRL
command in the related NE product documentation.
l Preprocessed Sampling Rate: For details, see the SET
GMRCTRL command in the related NE product documentation.
l MRLOG Neighboring Cell Format: For details, see the SET
GMRCTRL command in the related NE product documentation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 845

RA Parameter Description
T

UM Complaint Switch for enabling or disabling the reporting of CHR data. You can
TS Analysis retain the default state of the switch.
Support
Data (CHR) You can click to set the following advanced parameters:
l Domain: specifies whether to report CS or PS CHR data. This
parameter is unavailable.
l Service Type: specifies that CHR data for all service types is
reported. This parameter is unavailable.
l Error: specifies that all CHR data containing normal and abnormal
service procedures is reported. This parameter is unavailable.
l Event Block: specifies the types of event blocks contained in
reported CHR data. For details, see the SET
UEVENTCHRCTRL command in the related NE product
documentation. You can select all or none of the types or retain the
existing settings.
l All Signaling: specifies the types of all signaling messages
contained in reported CHR data. For details, see the SET
UEVENTCHRCTRL command in the related NE product
documentation. You can select all or none of the types or retain the
existing settings.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 846

RA Parameter Description
T

LTE Complaint Switch for enabling or disabling the reporting of eNodeB CHR data.
FD Analysis You can retain the default state of the switch.
D/ Support
LTE Data (CHR) You can click to set the following advanced parameters:
TD l Common tab page: Set Trace Event Block Type. The selected
D type of event block will be traced and recorded in CHRs. The details
about various types of event blocks are as follows:
– PERIOD INTRA FREQ MEASUREMENT, periodic intra-
frequency measurement
– PERIOD UE MEASUREMENT, periodic user-defined
measurement
– PERIOD THROUGHPUT MEASUREMENT, periodic
throughput measurement
– PERIOD LOGGED MDT MEASUREMENT, log-type MDT
measurement
– PERIOD UE POSITIONING, UE location measurement
– PERIOD INTRA FREQ MR MDT, intra-frequency MDT
measurement
– PERIOD UE MEASUREMENT MDT, user-defined MDT
measurement
– INTRA RAT HO OUT, outgoing intra-RAT handover
– INTER RAT HO OUT, outgoing inter-RAT handover
– HO IN, incoming handover
– RLF REPORT, radio link error report
– MEASUREMENT REPORT, event measurement
– UE CAPABILITY INFORMATION, UE capability
measurement
– RRC CONNECTION SETUP, RRC connection setup
– ERAB SETUP, eRAB setup
– UE CONTEXT SETUP, UE context setup
– UE CONTEXT RELEASE, UE context release
– ERAB RELEASE, eRAB release
– RRC CONNECTION RELEASE, RRC connection release
– VOICE STATISTIC, voice quality statistics
– RRC REEST, RRC connection re-setup
– CSFB PREP, CSFB
l Periodic Event Block Parameter Settings tab page:
– Trace Event Block: Specify the type of event to be traced. The
value of this parameter can be
PERIOD_LOGGED_MDT_MEASUREMENT.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 847

RA Parameter Description
T

– Measurement Report Period: Specify the measurement report

period for periodic events. The value of this parameter can be
1280(ms), 2560(ms), 5120(ms), 10240(ms), 20480(ms), 30720
(ms), 40960(ms), or 61440(ms).
The measurement period varies according to different services.
For example, the measurement period for intra-frequency MRs
needs to be minimized during the analysis of intra-frequency
network coverage problems. Mobile subscribers' experience in
data services will be noticeably decreased after the reporting of
MRs and inter-RAT MRs is enabled, and therefore you are
advised to enable the reporting of such MRs once only when it
is necessary. In addition, you are advised not to enable the
reporting of such MRs based on a short measurement period
frequently within a long period of time.
– MDT Measurement Duration: Specify the measurement
duration for MDT events. The value of this parameter can be
600(s), 1200(s), 2400(s), 3600(s), 5400(s), or 7200(s). The
default value is 600(s).
NOTE
Before subscribing to log data, you need to set mappings between TCE IP
addresses and TCE IDs on the CME. If the CME is unavailable, you need to set
the mappings manually through the OSS and ensure that the mappings for all
eNodeBs of the same telecom operator are the same.

PS Complaint Switch for enabling or disabling the reporting of SGSN/MME CHR

Core Analysis data. You can retain the default state of the switch.
Support
Data
(SGSN/
MME-
CHR)

Analysis Task Parameters

Basic task information

Parameter Description

Task Name Name of an analysis task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 848

Parameter Description

Task Type Type of an analysis task to be created.

Remarks Description of the task.

Value range: The name contains a maximum of 200 characters.

Parameter information

Parameter Description

Set Analysis Set the analysis type:

Analysi Scene l Only support the data on the RAN side
s Type
l Only support the data on the PS Core side, that is on CN side
l Support the data both on the RAN side and PS Core side, for
the combined complaint analysis support.

Access Set the RAT for an NE. The system supports the following RATs:
Network Type l Support the single-RAT complaint analysis support: GSM,
UMTS, LTE FDD, LTE TDD.
l Support the combined complaint analysis support: GSM/
UMTS, LTE FDD/LTE TDD.

Data Type 1 Both access methods can be chosen.

Set the data type on the RAN side.
l RAN CS Data Access: Analyzes the CS service based on the
CS-related data on the RAN side. The LTE network does not
involve this parameter.
l RAN PS Data Access: Analyzes the PS service based on the
PS-related data on the RAN side.
Both access methods can be chosen.
NOTE
l If you set the analysis scene to PS Core, you do not need to set the
data type, because it only supports the PS data on the PS Core.
l For UMTS NEs, the CS and PS service information is recorded in one
CHR. The SAU cannot filter CHRs by service type. Therefore, after
a complaint analysis support task is created, all service information
is displayed in the analysis results even though only the CS or PS is
selected.

Data Type 2 The system supports the following data on the CS domain and the
PS domain:
Control Plane: analyze the service based on the control plane data
on the RAN side and the CN side.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 849

Parameter Description

PS Core SDR The following options are available if you select PS Core when
Type creating a complaint analysis support task.
l Abnormal process: Only the call records about abnormal
services are reported and only the analysis results of abnormal
services are displayed. This option is selected by default.
l Normal process: Only the call records about normal services
are reported and only the analysis results of normal services
are displayed.
l Normal process: Only the traffic call records are reported and
only the traffic analysis results are displayed.
NOTE
l The Nastar can obtain a maximum of 20,000 latest call records about
normal and abnormal services, which means the total number of call
records about normal and abnormal services cannot exceed 20,000.
By contrast, call records about abnormal services are more useful than
call records about normal services. Therefore, you are advised select
only the Abnormal process option.
l The number of traffic data records is not restricted. Therefore, all
traffic data will be reported after you select the Traffic data option.

Select RAN NE Click Select to select an NE. The lowest level is the base station
NE(s) controller level.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 850

Parameter Description

Select IMSI Add or import the user alias, the IMSIs, and remarks of
Compla complaining users.
ining NOTE
User When selecting an import mode to import an IMSI in .csv format, confirm
that the IMSI displayed in the IMSI column is in correct format, such as
123231213424124 before importing the IMSI. If the IMSI displayed in
the IMSI column is in 4.6E+14 format, convert the IMSI into a text format
before importing the IMSI.
Subscriber alias value range:
l The name contains a maximum of 8 numbers.
l Only numbers are allowed.
l The name cannot be empty.
l The name is case sensitive.
l The name can be duplicate. Therefore, one subscriber can
have multiple MSISDNs.
IMSI value range:
l When the anonymous policy is disabled on the network where
the Nastar is deployed, enter the IMSI of a VIP subscriber.
Value range: a 15-digit numeric string composed of 0-9.
l When the anonymous policy is enabled on the network where
the Nastar is deployed, obtain the encrypted IMSI of a VIP
subscriber from the telecom operator and then enter the
encrypted IMSI.
Value range: a 15-digit alphanumeric string composed of 0-9,
a-f, and A-F.
NOTICE
If the input IMSI of a complaining subscriber is the same as the VIP
subscriber in the VIP group management function, and you does not have
the operation rights to operate the VIP subscriber, you are not allowed to
create the complaint analysis support task about the IMSI.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 851

Parameter Description

STMSI Add or import the user alias, the STMSIs, and remarks of
complaining users.
NOTE
When selecting an import mode to import an STMSI in .csv format,
confirm that the STMSI displayed in the STMSI column is in correct
format, such as 1233242344 before importing the STMSI.
Subscriber alias value range:
l The name contains a maximum of 8 numbers.
l Only numbers are allowed.
l The name cannot be empty.
l The name is case sensitive.
l The name can be duplicate. Therefore, one subscriber can
have multiple MSISDNs.
STMSI value range:
l When the anonymous policy is disabled on the network where
the Nastar is deployed, enter the STMSI of a subscriber.
Value range: a 10-digit alphanumeric string composed of 0-9,
a-f, and A-F.

MSISDN Add or export MSISDNs of complaining subscribers.

l It is only supported by the PS Core network.
l When the anonymization policy is not implemented on the
network where the Nastar system is deployed, enter the real
MSISDN of the subscriber.
Value range: The country code is empty, or is a number
consisting of one to three digits (0 through 9). The national
mobile number is a number consisting of one to 16 digits (0
through 9).
l When the anonymization policy is implemented on the
network where the Nastar system is deployed, obtain the
anonymized MSISDN of the subscriber from the telecom
operator, and then enter the anonymized MSISDN.
Value range: The country code is empty, or is a character
string consisting of one to three digits (0 through 9) and
uppercase letters (A through F). The national mobile number
is a character string consisting of one to 16 digits (0 through
9) and uppercase letters (A through F).
l The total number of digits and characters contained in the
MSISDN (country code plus national mobile number) cannot
exceed 16.
NOTICE
If the input MSISDN of a complaining subscriber is the same as the VIP
subscriber in the VIP group management function, and you does not have
the operation rights to operate the VIP subscriber, you are not allowed to
create the complaint analysis support task about the MSISDN.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 852

Parameter Description

Peer MSISDN Add or export peer MSISDNs of complaining subscribers.

l It is only supported by the GSM network when choosing the
CS service.
l When the anonymization policy is not implemented on the
network where the Nastar system is deployed, enter the real
MSISDN of the subscriber.
Value range: The country code is empty, or is a number
consisting of one to three digits (0 through 9). The national
mobile number is a number consisting of one to 16 digits (0
through 9).
l When the anonymous policy is enabled on the network where
the Nastar is deployed, the Nastar does not support analyzing
using the MSISDN.
NOTICE
If the input peer MSISDN of a complaining subscriber is the same as the
VIP subscriber in the VIP group management function, and you does not
have the operation rights to operate the VIP subscriber, you are not
allowed to create the complaint analysis support task about the peer
MSISDN.

Set KPI Network Indicates the RAT of an NE.

Thresh
old Domain Indicates the domain of an NE. Domains include signaling plane-
CS, signaling plane-PS, signaling plane-integration.

Service Type l When only the RAN data is analyzed, the parameter is
or Flow Type displayed as Service Type that indicates the service type of the
KPIs, such as NET, Call, and so on.
or Service/
Flow Type l When only the PS Core data is analyzed, the parameter is
displayed as Flow Type that indicates the flow type of the
KPIs, such as SGSN procedure, MME procedure, and so on.
NOTE
The Nastar allows you to set KPI thresholds only after you set PS
Core SDR Type to Normal process.
l When the RAN data and PS Core data are both analyzed, the
parameter is displayed as Service/Flow Type that indicates the
service type or flow type of the KPIs.

Indicator Indicates the name of a KPI.

Name

Operator Indicates the relationship between the KPI value and KPI
threshold.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 853

Parameter Description

Threshold Indicates the abnormal threshold of a KPI.

In the analysis report of the corresponding task, if the KPI value
of a subscriber reaches the threshold, this KPI is considered as a
problematic KPI or deteriorating KPI.
Click the unit and enter the KPI abnormal threshold value. This
parameter can be empty. That is, no threshold value is provided.

Time information of one-time task

Parameter Description

Duration Time period of a task. When the task is executed, only the data generated
within the time period is analyzed.
The start time must precede the end time.

3.10.4 Reference for Complaint Analysis Support Interface

This section describes the interface for complaint analysis support. Before performing relevant
operations, familiarize yourself with the functions of each area on the interface.

Interface Description: GSM Complaint Analysis Support

This section describes the interface for GSM complaint analysis support. Before performing
relevant operations, familiarize yourself with the functions of each area on the interface.

Opening the Window

You can enter GSM complaint analysis support interface in two modes:
l Select an executed GSM complaint analysis support task, and double-click an analysis
result of the task in the Task Result area.
l Select an executed GSM complaint analysis support task, and double-click an analysis
result of the task in the Task Result area. Right-click an analysis result of a task and choose
View Analysis Result from the shortcut menu.

Main Window
The complaint analysis support results can be displayed in tables, such as call report overview
table, subscriber information table, call access information table, call release information table,
and handover information table, as shown in Figure 3-51.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 854

Figure 3-51 Complaint analysis support interface

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 855

No. Parame Description

ter

1 Button Provides entries to three functions:

area
l : Displays the complaint analysis support results geographically.
For details, see Map Interface.

l : Exports overview reports.

The following three types of reports are exported. Each type has one
report. The default format is .xlsx format.
– The first type of reports lists the statistics result when the summary
mode is User ID: Alias-Cause type in the summary navigation tree.
The naming convention is Overview tree_User ID: Alias-Cause
type.file format.
– The second type of reports lists the statistics result when the summary
mode is Cause type-User ID: Alias in the overview tree. The naming
convention is Overview tree_Cause type-User ID: Alias.file
format.
– The third type of reports lists the summary result of overview
information of complaint analysis support. The naming convention is
Overview Table_Summary.file format.

l : Exports data reports.

The following two types of reports are exported. Each type has one report.
The default format is .xlsx format.
– Information Table_Details_GSM_CS.file format. The exported
data includes information about overview tables, subscribers, call
accesses, call releases, call handovers and so on. Alternatively, right-
click in area 3 and choose Export Data Report to obtain this type of
reports.
– Information Table_Details_GSM_PS.file format. The exported
data includes information about overview tables, subscribers,
accesses, releases and so on. Alternatively, right-click in area 3 and
choose Export Data Report to obtain this type of reports.
– Overview Table_Summary.file format. The same information with
Overview Table_Summary.file format exported from overview
reports.
NOTE
If you have the "User Identity" right, the IMSI column is added to the analysis result
page.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 856

No. Parame Description

ter

2 Overvie l Upper part: Displays the service types. You can select the service types.
w tree of l Middle part: Call records of multiple subscribers are displayed by cause
the call type in the navigation tree mode. (N) after each node indicates the number
report of call reports under the node.
cause
type l Lower part: Select the display mode in the drop-down combo box after
overvie Tree aggregation for the navigation tree.
w of – In Cause type-User ID: Alias mode, all filtered call records are
complai classified by cause type and the call records of each cause type are
nt then classified by User ID: Alias.
subscrib – In User ID: Alias-Cause type mode, all filtered call records are
ers classified by User ID: Alias and the call records of each User ID:
Alias are then classified by cause type.
NOTE
If you have the "User Identity" right, "User ID: Alias" will display "IMSI" directly, that
is, the true IMSI information.
When users filter CHRs through the service type tree and the exception tree, abnormal
CHRs of other service types rather than the selected service type may exist under the
Non-exception node.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 857

No. Parame Description

ter

3 Call The table contains the overview information of the filtered call reports. The
report information includes the information such as access time, access cell, release
overvie time, release cell, service duration, and call status.
w table
of Each row indicates one call record.
complai
l : Indicates that the call record in the row is abnormal.
nt
subscrib
ers l : Indicates that the call record in the row belongs to the call record
node with the Other cause type in the overview tree and its exception is
unknown.
l : Indicates that the service detail record is a combined one.
The Nastar supports combining inter-BSC call history records. If an inter-
BSC handover occurs in one call process, the Nastar combines several
call records for one call and displays the combined service detail record.
Double-click a combined record. On the displayed tab page, the original
multiple records that comprise the combined record are listed out. The
naming convention for the tab page is ***_Serial Number. *** indicates
the user.

Click the column header to resort this table.

NOTE
If you have the "User Identity" right, the IMSI column is added to the analysis result
page.
For some columns (such as User ID: Alias), the system only centralized display the
same content, but there is no display order after resorting.

4 Signalin Displays detailed signaling process about all filtered subscribers.

g
procedu For details, see Description of Signaling Procedure Before Call Release
re area Tab Page.

5 Theme Displays detailed signaling process and MR information about all filtered
analysis subscribers. The Nastar analyzes the mobility and service of those
area subscribers.

For details, see Description of Measurement Information Before Call

Release Tab Page, Description of Mobility Analysis Tab Page.
NOTE
If you have the "User Identity" right, the IMSI column is added to the analysis result
page.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 858

No. Parame Description

ter

6 Call Displays detailed information about the selected subscriber in area 2,

report including user information, call access information, call release information.
overvie
For details about parameters, see 3.10.5 Reference for Complaint Analysis
w table
Support Parameters (GSM).
of
complai When the window is opened initially, the area hidden by default.
nt
NOTE
subscrib
ers Detailed records of VIP subscribers are saved for seven days by default, which is also
the longest saving duration.

Description of Signaling Procedure Before Call Release Tab Page

Figure 3-52 shows the signaling process before call release. The table describes the signaling
process.

Figure 3-52 Signaling process before call release tab page

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 859

No. Parameter Description

Double-click one call record in the table or in the chart. The Signal
Detail Information dialog box is displayed. The detailed signaling
information is an explanation field tree. It displays in tree mode the
implication of fields represented by specific bytes, and automatically
parses the variant values represented by fields in a message according
to protocols.
NOTE
For BSC6900 V900R016 or BSC6910 V100R016 and later versions,
subscriber information displayed in the Signal Detail Information dialog box
may be inconsistent with that displayed in the other areas. The reason is as
follows: CHR Signalling Area User ID Anonymized on the NE side is used
for anonymizing subscriber information displayed in the Signal Detail
Information dialog box, whereas g_ucAnonymSwitch on the NE side is used
for anonymizing subscriber information displayed in the other areas. If the
two switches are in different states, information inconsistency occurs.

(2) Signaling The flowchart shows the interactions between signaling of NEs
flowchart during a call. The chart displays the corresponding information when
you select the information in the table.

l The time for each signaling is displayed on the left. Its format is
hh:mm:ss.ms (hours:minutes:seconds.milliseconds).
l NEs are displayed on the upper part.
l Words in the figure are names and numbers of each signaling.
The dashed line indicates the signaling. The arrow indicates the
direction of signaling transmission.

For details about the signaling, see related protocols. No explanation

is given in this document.

Description of Measurement Information Before Call Release Tab Page

Before call release, measurement information in the GSM complaint analysis support window
includes detailed MR information tables and the change trend chart of measurement counters
values.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 860

NOTE

l If you have subscribed the MR data of compliant analysis support, the tab page will display the
comprehensive measurement report information.
l If you have not subscribed the MR data of compliant analysis support, the system uses the MR information
in the CHR data to replace the original MR data, the tab page will display a small number of measurement
reports.

Figure 3-53 shows the measurement information before call release.

Figure 3-53 Measurement information before call release tab page

No. Parameter Description

(1) Detailed MR Lists detailed MR information before call release. The information
information includes time, measurement object type, and detailed counter
table information.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 861

No. Parameter Description

(2) Change trend The change trend of measurement counter values is displayed in
chart of charts.
measurement
counter values Each trend chart consists of four parts. They are as follows from left
to right:
l Title
l Y-axis, displaying the maximum and minimum values.
l Counter change trend chart, displaying the change of counter
values for a maximum of 20 MRs on the interface by default. You
can view the more MRs through the scroll bar.
l Legend

Table 3-38 describes the change trend of each measurement

counters.

Table 3-38 Description of measurement counter change trend chart

Counter Statistic Indication Description

TA Helps identify abnormal releases Displayed as a bar chart. The value

caused by poor coverage. ranges from 0 to 63.

DLRxLevel Displayed as a broken line graph. The

value ranges from -47 to -110.

DLRxQuality Helps identify abnormal releases RxQuality: displayed as a bar chart.

/Level caused by uplink or downlink The value ranges from 0 to 7.
interference. RxLevel: displayed as a broken line
graph. The value ranges from -47 to
-110.

ULRxQuality RxQuality: displayed as a bar chart.

/Level The value ranges from 0 to 7.
RxLevel: displayed as a broken line
graph. The value ranges from -47 to
-110

MS/BTS Helps identify abnormal releases BTS Power: displayed as a bar chart.
Power caused by unbalanced uplink and The value ranges from 0 to 15. MS
downlink by analyzing this KPI with Power: displayed as a broken line
DLRxQuality/Level and graph. The value ranges from 0 to 30.
ULRxQuality/Level.

VQI Displays voice quality changes in the UL VQI: displayed as a bar chart.
process, help evaluate the quality The value ranges from 0 to 50. DL
accurately. VQI: displayed as a broken line
graph. The value ranges from 0 to 50.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 862

Description of Mobility Analysis Tab Page

Figure 3-54 shows handover information of the terminal through the mobility analysis.

Figure 3-54 Mobility analysis tab page

For details about parameters, see 3.10.5 Reference for Complaint Analysis Support
Parameters (GSM).

Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in
Figure 3-55.

Figure 3-55 Map interface

No. Feature Description

(1) Button area Entry for basic operations in the map window. For details about the
icons, see 2.2.3 Interface Description: Geographic Observation
Results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 863

No. Feature Description

(2) Navigation l Site Layer: displays site information. You can set the display
tree in the effect through the shortcut menu. The site information is
map window displayed on the condition that the engineering parameters have
been imported to the Nastar database and site information have
been loaded in map window.
NOTE
If you need to delete all sites in a network system, click Remove through
the layer management function.
l Complaint Analysis Support: Node for the complaint analysis
support theme.
– A level-2 node under the node indicates a task name. A
level-3 node under the node indicates a KPI, such as access/
release cell KPI.
– If multiple complaint analysis support results windows are
open, only one of the windows can be displayed on the map
window simultaneously.
– If a analysis result window is closed, the node for the window
in the navigation tree is deleted accordingly. In addition, the
rendered layer of the corresponding theme is deleted.

(3) Geographic Analysis results are displayed as icons in different colors.

observation
area

(4) Grid detail This area is empty for complaint analysis support.
area

(6) Information l In the geographic observation area, select an icon of a cell and
area the details about this cell is displayed in the information area.
l If the engineering parameters of a cell is not imported, the
system displays a message in this area.

Interface Description: UMTS Complaint Analysis Support

This section describes the interface for UMTS complaint analysis support. Before performing
relevant operations, familiarize yourself with the functions of each area on the interface.

Opening the Window

You can enter UMTS complaint analysis support interface in two modes:
l Select an executed UMTS complaint analysis support task, and double-click an analysis
result of the task in the Task Result area.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 864

l Select an executed UMTS complaint analysis support task, and double-click an analysis
result of the task in the Task Result area. Right-click an analysis result of a task and choose
View Analysis Result from the shortcut menu.

For UMTS NEs, the CS and PS service information is recorded in one CHR. The SAU cannot filter CHRs by
service type. Therefore, after a complaint analysis support task is created, all service information is displayed
in the analysis results even though only the CS or PS is selected.

Figure 3-56 Complaint analysis support interface

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 865

No. Parame Description

ter

1 Button Provides entries to four functions:

area
l : displays the complaint analysis support results geographically.
For details, see Map Interface.

l : Exports overview reports.

l : exports data reports.

The following two types of reports are exported. Each type has one report.
The default format is .xlsx format.
– Information Table_Details_UMTS.file format. The exported data
includes information about summary information, user information,
access information, release information, and statistical information.
Alternatively, right-click in area 3 and choose Export Data Report
to obtain this type of reports.
– Overview Table_Summary.file format. The same information with
Overview Table_Summary.file format exported from overview
reports.

l provides the abnormal cause statistics function of the service. For

details, see Common Statistics Interface.
NOTE
If you have the "User Identity" right, the IMSI column is added to the analysis result
page.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 866

No. Parame Description

ter

2 Overvie l Upper part: Displays the service types. You can select the service types.
w tree of NOTE
the call If users select only a service type node (such as NET, CS domain, and PS domain),
report the Nastar filters only the abnormal or normal CHRs of the selected service type.
cause l Middle part: Call records of multiple subscribers are displayed by cause
type type in the navigation tree mode. (N) after each node indicates the number
overvie of call reports under the node.
w of
l Lower part: Select the display mode in the drop-down combo box after
complai
Tree aggregation for the navigation tree.
nt
subscrib – In Cause type-User ID: Alias mode, all filtered call records are
ers classified by cause type and the call records of each cause type are
then classified by User ID: Alias.
– In User ID: Alias-Cause type mode, all filtered call records are
classified by User ID: Alias and the call records of each User ID:
Alias are then classified by cause type.
NOTE
If you have the "User Identity" right, "User ID: Alias" will display "IMSI" directly, that
is, the true IMSI information.
When users filter CHRs through the service type tree and the exception tree, abnormal
CHRs of other service types rather than the selected service type may exist under the
Non-exception node.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 867

No. Parame Description

ter

3 Call The table contains the overview information of the filtered call reports. The
report information includes the information such as access time, access cell, release
overvie time, release cell, service duration, and call status.
w table
of Each row indicates one call record.
complai
l : Indicates that the call record in the row is abnormal.
nt
subscrib
ers l : Indicates that the call record in the row belongs to the call record
node with the Other cause type in the overview tree and its exception is
unknown.
l : Indicates that the service detail record is a combined one.
The Nastar supports combining inter-RNC call history records. If an inter-
RNC handover occurs in one call process, the Nastar combines several
call records for one call and displays the combined service detail record.
Double-click a combined record. On the displayed tab page, the original
multiple records that comprise the combined record are listed out. The
naming convention for the tab page is ***_Serial Number. *** indicates
the user.

Click the column header to resort this table.

4 Signalin Displays detailed signaling process about all filtered subscribers.

g
procedu For details, see Description of the Signaling Procedure Before Call
re area Release Tab Page.

5 Theme Displays detailed signaling process and MR information about all filtered
analysis subscribers. The Nastar analyzes the mobility and service of those
area subscribers.

For details, see Description of the Measurement Information Before Call

Release Tab Page, Description of Mobility Analysis Tab Page, and
Description of Service Analysis Tab Page.
NOTE
If you have the "User Identity" right, the IMSI column is added to the analysis result
page.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 868

No. Parame Description

ter

6 Call Displays detailed information about the selected subscriber in area 2,

report including user information, call access information, call release information,
overvie and statistical information.
w table
of For details about parameters, see 3.10.6 Reference for Complaint Analysis
complai Support Parameters (UMTS).
nt When the window is opened initially, the area hidden by default.
subscrib
ers NOTE
Detailed records of VIP subscribers are saved for seven days by default, which is also
the longest saving duration.

Description of the Signaling Procedure Before Call Release Tab Page

Figure 3-57 shows the signaling process before call release. The table describes the signaling
process.

Figure 3-57 Signaling process before call release tab page

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 869

No. Parameter Description

(1) Signaling Lists all the interactive signaling information between NEs in the call
information process, including the time, direction, type, and content. The chart
table displays the corresponding information when you select the
information in the table.
NOTE
l Only subscribe to the all signaling data, you can see all of the signaling
information about the subscribed interface; otherwise, only can view part
of the signaling information.
l After subscribing to the all signaling data, double-click one call record in
the table or in the chart. The Signal Detail Information dialog box is
displayed. The detailed signaling information is an explanation field tree.
It displays in tree mode the implication of fields represented by specific
bytes, and automatically parses the variant values represented by fields in
a message according to protocols.
l If you have set the system through other methods so that all the signaling
messages of an important VIP subscriber, who is not managed by the
Nastar, are reported, this area also displays all the signaling messages of
this subscriber.

(2) Signaling The flowchart shows the interactions between signaling of NEs
flowchart during a call. The chart displays the corresponding information when
you select the information in the table.

For details about the signaling, see related protocols. No explanation

is given in this document.

Description of the Measurement Information Before Call Release Tab Page

Before call release, measurement information in the UMTS complaint analysis support window
includes detailed MR information tables and the change trend chart of measurement counters
values.

NOTE

Figure 3-58 shows the measurement information before call release.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 870

Figure 3-58 Measurement information before call release tab page

No. Parameter Description

(1) Detailed MR Lists detailed MR information before call release. The information
information includes time, measurement object type, and detailed counter
table information.

Table 3-39 describes the change trend of each measurement

counters.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 871

Table 3-39 Description of measurement counter change trend chart

Counter Statistic Indication Description

Ec/No Indicates the change trend of the Displayed as a broken line chart.
signal intensity according to the
received cells of the UE.

RSCP Indicates the change trend of the Displayed as a broken line chart.
signal level according to the received
cells of the UE.

RSSI Indicates the change trend of the Displayed as a broken line chart.
RSSI according to the received inter-
cells of the UE.

RSRP Indicates the change trend of the Displayed as a broken line chart.
RSRP according to the received LTE
cells of the UE.

RSRQ Indicates the change trend of the Displayed as a broken line chart.
RSRQ according to the received
inter-cells of the UE.

UE Tx Power Indicates the change trend of the Displayed as a broken line chart.
transmit power of the UE.

Description of Mobility Analysis Tab Page

Figure 3-59 shows handover information of the terminal through the mobility analysis.

Figure 3-59 Description of mobility analysis tab page

For details, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS).

Description of Service Analysis Tab Page

The service analysis includes RAB analysis.
l Figure 3-60 shows the items about the RAB service through the RAB analysis.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 872

– Double-click one result, or right-click one result, and choose Detail Service
Information, view the detailed service counters of CS domain or PS domain.
– Right-click one result, and choose Trend Analysis, view the throughput and throughput
rate of the RAB on the uplink and downlink at the different time.
For details, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS).

Figure 3-60 Description of service analysis tab page (RAB)

Common Statistics Interface

The common statistics function allows the Nastar to collect statistics on the abnormal cause and
abnormal sub-cause generated for a specified user or service, including the number of abnormal
services and the proportion.

Click in the button area. In the displayed Common Statistics dialog box, select an object
from the navigation tree and click Confirm. Details about the abnormal causes are displayed in
the right pane.

Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in
Figure 3-61.

Figure 3-61 Map interface

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 873

No. Feature Description

(1) Button area Entry for basic operations in the map window. For details about the
icons, see 2.2.3 Interface Description: Geographic Observation
Results.

(3) Geographic Analysis results are displayed as icons in different colors.

observation
area

(4) Grid detail This area is empty for complaint analysis support.
area

(6) Information l In the geographic observation area, select an icon of a cell and
area the details about this cell is displayed in the information area.
l If the engineering parameters of a cell is not imported, the
system displays a message in this area.

Interface Description: LTE Complaint Analysis Support

This section describes the interface for LTE complaint analysis support. Before performing
relevant operations, familiarize yourself with the functions of each area on the interface.

Opening the Window

You can enter LTE complaint analysis support interface in two modes:

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 874

l Select an executed LTE complaint analysis support task, and double-click an analysis result
of the task in the Task Result area.
l Select an executed LTE complaint analysis support task, and double-click an analysis result
of the task in the Task Result area. Right-click an analysis result of a task and choose View
Analysis Result from the shortcut menu.

Figure 3-62 Complaint analysis support interface

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 875

No. Parame Description

ter

1 Button Provides entries to three functions:

area
l : Displays the complaint analysis support results geographically.
For details, see Map Interface.

l : Exports overview reports.

l : Exports data reports.

The following two types of reports are exported. Each type has one report.
The default format is .xlsx format.
– Information Table_Details_LTE.file format. The exported data
includes information about overview tables, subscribers, accesses,
releases, and handovers. Alternatively, right-click in area 3 and choose
Export Data Report to obtain this type of reports.
– Overview Table_Summary.file format. The same information with
Overview Table_Summary.file format exported from overview
reports.
NOTE
If you have the "User Identity" right, the IMSI column is added to the analysis result
page.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 876

No. Parame Description

ter

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 877

No. Parame Description

ter

3 Call The table contains the overview information of the filtered call reports. The
report information includes the information such as access time, access cell, release
overvie time, release cell, service duration, and call status.
w table
of Each row indicates one call record.
complai
l : Indicates that the call record in the row is abnormal.
nt
subscrib
ers l : Indicates that the call record in the row belongs to the call record
node with the Other cause type in the overview tree and its exception is
unknown.
l : Indicates that the service detail record is a combined one.
The Nastar supports combining inter-eNodeB call history records. If an
inter-eNodeB handover occurs in one call process, the Nastar combines
several call records for one call and displays the combined service detail
record. Double-click a combined record. On the displayed tab page, the
original multiple records that comprise the combined record are listed out.
The naming convention for the tab page is ***_Serial Number. ***
indicates the user.

Click the column header to resort this table.

4 Signalin Displays detailed signaling process about all filtered subscribers.

g
procedu For details, see Description of the Signaling Procedure Before Call
re area Release Tab Page.

5 Theme Displays detailed signaling process and MR information about all filtered
analysis subscribers. The Nastar analyzes the mobility and service of all filtered
area subscribers.

For details, see Description of the Measurement Information Page,

Description of the E-RAB Analysis Tab Page and Description of the
Mobility Analysis Tab Page.
NOTE
If you have the "User Identity" right, the IMSI column is added to the analysis result
page.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 878

No. Parame Description

ter

6 Call Displays detailed information about the selected subscriber in area 2,

report including user information, call access information, call release information.
overvie
For details about parameters, see 3.10.7 Reference for Complaint Analysis
w table
Support Parameters (LTE).
of
complai When the window is opened initially, the area hidden by default.
nt
NOTE
subscrib
ers Detailed records of VIP subscribers are saved for seven days by default, which is also
the longest saving duration.

Description of the Signaling Procedure Before Call Release Tab Page

Figure 3-63 shows the signaling process before call release. The table describes the signaling
process.

Figure 3-63 Signaling process before call release tab page

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 879

No. Parameter Description

(2) Signaling The flowchart shows the interactions between signaling of NEs
flowchart during a call. The chart displays the corresponding information when
you select the information in the table.

For details about the signaling, see related protocols. No explanation

is given in this document.

Description of the Measurement Information Page

Before call release, measurement information in the LTE complaint analysis support window
includes detailed MR information tables and the change trend chart of measurement counters
values, as shown in Figure 3-64.

Figure 3-64 Measurement information tab page

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 880

No. Parameter Description

(1) Detailed MR Lists detailed MR information. The information includes time,

information measurement object type, and detailed counter information.
table

For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).

Description of the E-RAB Analysis Tab Page

The results are used for analyzing the counters of the E-RAB before the E-RAB service releases
for analyzing the network quality, as shown in Figure 3-65.

Figure 3-65 E-RAB analysis tab page

l Right-click one E-RAB, choose Detail E-RAB Information from the shortcut menu, view
the detailed information of the selected service bearer.
l Right-click one E-RAB, choose Trend Analysis from the shortcut menu, view the service
process trend of the selected service bearer for analyzing the network quality of the service
process.
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).

Description of the Mobility Analysis Tab Page

Figure 3-66 shows handover information of the terminal through the mobility analysis.

Figure 3-66 Mobility analysis tab page

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 881

For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).

Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in
Figure 3-67.

Figure 3-67 Map interface

No. Feature Description

(1) Button area Entry for basic operations in the map window. For details about the
icons, see 2.2.3 Interface Description: Geographic Observation
Results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 882

No. Feature Description

(3) Geographic Analysis results are displayed as icons in different colors.

observation
area

(4) Grid detail This area is empty for complaint analysis support.
area

(6) Information l In the geographic observation area, select an icon of a cell and
area the details about this cell is displayed in the information area.
l If the engineering parameters of a cell is not imported, the
system displays a message in this area.

Interface Description: PS Core Complaint Analysis Support

This section describes the interface that displays PS core complaint analysis support results.
Before performing related operations, familiarize yourself with functions of each area on the
interface.

Navigation Path
Use either of the following methods to open the interface that displays PS core complaint analysis
support results:

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 883

l Select a finished PS core complaint analysis support task, and double-click a result record
in the Task Result area.
l Right-click a result record of the task and choose View Analysis Result from the shortcut
menu.

Interface
PS core complaint analysis support results can be displayed in tables to show summary
information, CHR base information, user information, and procedure information, as shown in
Figure 3-68.

Figure 3-68 Interface for PS core complaint analysis support results

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 884

No. Item Description

1 Button Provides entries to three functions:

area
l : Exports overview reports.
The following three types of reports are exported. Each type has one
report. The default format is .xlsx format.
– The first type of reports lists the statistics result when the summary
mode is User ID: Alias-Cause type in the summary navigation tree.
The naming convention is Overview tree_User ID: Alias-Cause
type.file format.
– The second type of reports lists the statistics result when the summary
mode is Cause type-User ID: Alias in the overview tree. The naming
convention is Overview tree_Cause type-User ID: Alias.file
format.
– The third type of reports lists the summary result of overview
information. The naming convention is Overview
table_Summary.file format.

l : Exports data reports.

The exported data includes information about overview information, and
detailed information (such as CHR base information, user information,
procedure information).
Alternatively, right-click in area 3 and choose Export Data Report to
obtain this type of reports.

l provides the traffic statistics function. For details, see Traffic

Statistics on the Interface.
NOTE
l If you have the "User Identity" right, the IMSI column is added to the analysis result
page.
l If you have the "User Identity" right, "MSISDN" will display the true MSISDN
information instead of the scrambled information with *.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 885

No. Item Description

2 Navigati l Upper part: Displays the service types. You can select the service types.
on tree l Middle part (upper): Displays the procedure types. You can select the
of the procedure types. The content in brackets after the SGSN and GGSN
CHR indicates the RAT.
cause
type l Middle part (lower): Based on the selected service type and the procedure,
summar the call records of multiple subscribers are displayed by cause type in the
y of navigation tree mode.
complai l Lower part: Select the display mode in the drop-down combo box after
ning Tree aggregation for the navigation tree.
subscrib – In Cause type-User ID: Alias mode, all filtered call records are
ers classified by cause type and the call records of each cause type are
then classified by User ID: Alias.
– In User ID: Alias-Cause type mode, all filtered call records are
classified by User ID: Alias and the call records of each User ID:
Alias are then classified by cause type.
– The displayed mode of the User ID: Alias node is as follows: User
ID: Alias(MSISDN1: MSISDN2...):(N). The displayed mode of the
Cause type node is as follwos: Cause type(N). (N) after each node
indicates the number of call records under the node.
NOTE
If you have the "User Identity" right, "User ID: Alias" will display "IMSI" directly, that
is, the true IMSI information.
When users filter CHRs through the service type tree and the exception tree, abnormal
CHRs of other service types rather than the selected service type may exist under the
Non-exception node.

3 Summar Displays an overview of all filtered records, such as time, cell, procedure,
y table and exception cause.
of
complai Each row indicates one call record. indicates that the call record in the
ning row is abnormal.
subscrib
er Click the column header to resort this table.
records NOTE
l If you have the "User Identity" right, the IMSI column is added to the analysis result
page.
l If you have the "User Identity" right, "MSISDN" will display the true MSISDN
information instead of the scrambled information with *.
l For some columns (such as User ID: Alias), the system only centralized display the
same content, but there is no display order after resorting.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 886

No. Item Description

4 Solution Displays the solution to the exception that causes an abnormal CHR after you
to a select this CHR in area 3.
specifie
d
abnorma
l CHR

5 Details Displays the subscriber details corresponding to the records selected in area
table of 2.
complai
ning For details about the parameters, see 3.10.8 Reference for Complaint
subscrib Analysis Support Parameters (PS Core).
er The table is hidden by default when you initially open the window.
records
NOTE
l If you have the "User Identity" right, the IMSI column is added to the analysis result
page.
l If you have the "User Identity" right, "MSISDN" will display the true MSISDN
information instead of the scrambled information with *.

Traffic Statistics on the Interface

The traffic statistics function allows the Nastar to collect statistics on the total, uplink, and
downlink traffic generated within a specified time period for a specified NE or complaining
subscriber.

1. Click in the button area. The Common Statistics dialog box is displayed.
2. Select an object from the navigation tree and click Confirm. Details about the traffic
generated for the selected object are displayed in the right pane, as shown in Figure
3-69.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 887

Figure 3-69 Common statistics dialog box

NOTE

To view details about the traffic generated at a specific time by subscriber, perform the following operations:
1. In the navigation tree on the interface that displays complaint analysis support results, select Data under
Service Type, and select Traffic under Procedure Type.
Traffic subnodes are displayed under Root.
2. Select a Traffic subnode to view traffic information by subscriber.

Interface Description: Combined Complaint Analysis Support

This section describes the interface that displays combined complaint analysis support results.
Before performing related operations, familiarize yourself with functions of each area on the
interface.

Function Description
The Nastar allows you to perform complaint analysis support based on the data collected from
different types of networks simultaneously. It also allows you to perform complaint analysis
support based on the data collected from the RAN and the PS core network simultaneously.
Therefore, the Nastar supports combined complaint analysis support in the following
combinations:
l Only RAN side
– LTE-FDD+LTE TDD
– GSM+UMTS
– GSM+LTE-FDD/TDD

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 888

– GSM+LTE-TDD
– UMTS+LTE-FDD/TDD
– GSM+UMTS+LTE-FDD/TDD
l RAN and PS Core side combined
– GSM+PS Core
– UMTS+PS Core
– LTE FDD/TDD+PS Core
– GSM+UMTS+PS Core
– GSM+LTE-FDD/TDD+PS Core
– GSM+LTE-TDD+PS Core
– UMTS+LTE-FDD/TDD+PS Core
– GSM+UMTS+LTE-FDD/TDD+PS Core

Navigation Path
Use either of the following methods to open the interface that displays combined complaint
analysis support results:
l Select a finished combined complaint analysis support task, and double-click a result record
in the Task Result area.
l Right-click a result record of the task and choose View Analysis Result from the shortcut
menu.

Interface description
The interface that displays the combined complaint analysis support results of multiple RATs
is generally the same as the interface that displays the complaint analysis support results of a
single RAT:

Figure 3-70 Combined Complaint Analysis Support(Using LTE and PS Core as an example)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 889

l The service types displayed in the navigation tree (area 1) are combinations of the service
types for the complaint analysis support of involved RATs.
l The cause types displayed in the navigation tree (area 2) are combinations of the cause
types for the complaint analysis support of involved RATs.
The description of the exception causes provides the mapping between service types and
cause types. For details, see Appendix: Exception Cause Classification (Combined
Analysis).
l The information displayed in the middle and right areas on the interface varies according
to the call history record (CHR) that you select in the navigation tree.
– The summary results (area 3) of combined complaint analysis support are slightly
different from those of single-RAT complaint analysis support. For details, see 3.10.9
Reference for Complaint Analysis Support Parameters (Combined Analysis).
– In other results, one xDR belongs only to one RAT in most cases. Therefore, for details
about the related interfaces and parameters, see descriptions about the interfaces and
parameters for complaint analysis support of the corresponding RAT.
NOTE

l For the GSM/UMTS combined complaint analysis support, Peer MSISDN in the summary table is
only available for the GSM CS network, that is, appears only when the GSM CS task is created
independently. To view the peer information of the UMTS network, see the Service Analysis
(RAB) tab page.
l For an analysis theme that involves LTE CSFB, you must have applied for a valid license for CSFB
on the RAN side and one for CSFB on the PS Core network side. xDRs used in such an analysis theme
are generated by combining xDRs collected from the RAN and PS Core network sides. You can click
under Combined to view information about each xDR before the combination.

3.10.5 Reference for Complaint Analysis Support Parameters

(GSM)
This section describes the parameters for GSM complaint analysis support.

Parameters for Viewing GSM Complaint Analysis Support Results - RAN CS

Acces Non-SMS message from a N/A Cause of a signaling access. BSC6900

s mobile-originated VIP V900R014C00
Cause subscriber (or later) or
(AC_ORIGIN_CALL_N BSC6910
O_SMS) V100R014C00
SMS message from a (or later)
mobile-originated VIP
subscriber
(AC_ORIGIN_CALL_S
MS)
Answer to paging
(AC_ANSWER_TO_PA
GING)
Call re-setup
(AC_CALL_RE_ES-
TABLISH)
Emergency call
(AC_EMERGENCY_CA
LL)
Location update
(AC_LOCATION_UP-
DATE)
IMSI detachment
(AC_IMSI_DETACH)
Data service
(AC_PACKET_CALL)
LMU service
(AC_LMU_ESTAB-
LISH)
SS service
(AC_SS_ESTABLISH)
VGCS service
(AC_VGCS_ESTAB-
LISH)
VBS service
(AC_VBCS_ESTAB-
LISH)
LCS service
(AC_LCS_ESTABLISH)
Any other service
(AC_RESERVED)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 893

Para Range Uni Description Supported NE

mete t Version
r

Incoming inter-BSC
handover
(AC_IN_BSC_HO)
Response to notification
(AC_NOTIFICATION_R
SP)
Immediate setup
(AC_IMM_SET_UP)
RR initialization
(AC_RR_INITIALISATI
ON_REQ)
Indication from talker
(AC_TALKER_INDICA-
TION)
VGCS access
(AC_VGCS_VBS_VPCS
)
Non-SMS message from a
mobile-terminated VIP
subscriber
(AC_ANSWER_TO_PA
GING_CALL)
SMS message from a
mobile-terminated VIP
subscriber
(AC_ANSWER_TO_PA
GING_CALL)
Normal location update
(AC_LOCATION_UPD
ATE_NORMAL)
Periodic location update
(AC_LOCATION_UPD
ATE_PERIODIC)
IMSI attachment
(AC_LOCATION_UPD
ATE_ATTACH)

Acces N/A N/A Signaling access time for a BSC6900

s call, namely, the time when a V900R014C00
Time MS sends the Channel (or later) or
Request message. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 894

Para Range Uni Description Supported NE

mete t Version
r

Acces 1 to 64 characters N/A Name of the cell in which a BSC6900

s Cell MS sends the Channel V900R014C00
Request message. (or later) or
The parameter is displayed in BSC6910
the following format: BSC V100R014C00
Name: Cell Name (BSC (or later)
OPC: ID of the cell). You can
obtain the names of the BSC
and the cell from the
configuration data. The
names are not displayed if
they are not available.
In the preceding format, BSC
OPC is the originating
signaling point configured
on the BSC side.

Relea N/A N/A Signaling release time for a BSC6900

se call, V900R014C00
Time namely, the time when a MS (or later) or
receives the Channel Release BSC6910
message. V100R014C00
(or later)

Relea 1 to 64 characters N/A Name of the cell in which a BSC6900

se MS receives the Channel V900R014C00
Cell Release message. (or later) or
The parameter is displayed in BSC6910
the following format: BSC V100R014C00
Name: Cell Name (BSC (or later)
OPC: ID of the cell). You can
obtain the names of the BSC
and the cell from the
configuration data. The
names are not displayed if
they are not available.

User N/A N/A ·User ID, which is created by BSC6900

ID:Al the system when creating the V900R014C00
ias task. (or later) or
·Alias, which is created by BSC6910
the user when creating the V100R014C00
task. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 895

Para Range Uni Description Supported NE

mete t Version
r

IMSI N/A N/A IMSI information of a BSC6900

subscriber. V900R014C00
Note: Only when you have (or later) or
the "User Identity" right, you BSC6910
can view the IMSI V100R014C00
information. (or later)

IMEI 00000000-99999999 N/A International mobile BSC6900

-TAC equipment identity-type V900R014C00
allocation code (IMSI-TAC) (or later) or
of a VIP subscriber, which is BSC6910
the first eight digits in the V100R014C00
IMEI of a UE. (or later)

Mode N/A N/A Type of a MS. BSC6900

l You can obtain the IMEI- V900R014C00
TACs of the UE from the MS (or later) or
type management function. BSC6910
V100R014C00
(or later)

Peer N/A N/A Mobile station international BSC6900

MSIS ISDN number (MSISDN) of V900R014C00
DN a peer subscriber. (or later) or
BSC6910
V100R014C00
(or later)

Durat [0,+∞) Sec Service duration covering BSC6900

ion ond the call duration and the V900R014C00
signaling setup duration. (or later) or
Service duration = Release BSC6910
time - Access time V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 896

Para Range Uni Description Supported NE

mete t Version
r

CS [0,+∞) Sec Call duration. BSC6900

Servi ond Call duration = Time stamp V900R014C00
ce of the Disconnect message - (or later) or
Durat Time stamp of the Connect BSC6910
ion Acknowledge message V100R014C00
(or later)
Note: For an inter-BSC
combined CHR, the value of
this counter is the sum of the
durations in all CHRs that are
combined into this CHR if
this CHR is incomplete. This
means that the value of this
counter does not indicate the
actual service duration.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 897

Para Range Uni Description Supported NE

mete t Version
r

Call Following are criteria N/A Network access result for a BSC6900
Setup indicating a proper call mobile-originated call. The V900R014C00
Resul setup: result indicates a proper call (or later) or
t 1. Normal: The called setup or an abnormal call BSC6910
subscriber receives the setup. V100R014C00
Connect ACK message The call setup result is (or later)
and proper call displayed in the following
communication is format: Call Release Result/
established between the Cause of Abnormal Call
calling and called Release/Sub-Cause of
subscribers. Abnormal Call Release.
2. The calling subscriber (You can obtain the
receives the Disconnect preceding three parameters
message and termination in the Call Release
of the call is triggered by Information window.)
the peer subscriber.
3. Connection is released
due to an outgoing inter-
BSC handover.
Following are criteria
indicating an abnormal
call setup:
1. The connection is
released abnormally
before a call is connected.
2. The CN rejects the
access request.
3. TCH assignment fails.
4. The signaling channel is
released abnormally.
5. The traffic channel is
released abnormally.
6. The call setup duration
exceeds the predefined
threshold.
7. The BSS rejects the
immediate assignment
request.
8. The BSC releases
channel resources.
9. The MSC releases
channel resources
abnormally.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 898

Para Range Uni Description Supported NE

mete t Version
r

10 The VLR rejects the

access request.
11. Authentication fails.
12 The CN rejects the
access request due to an
incorrect Cipher Mode.
13. An incoming inter-
BSC handover fails.

Call Following are criteria N/A Network release result for a BSC6900
Relea indicating a proper call mobile-originated call. The V900R014C00
se release: result indicates a proper call (or later) or
Resul 1. Normal: The subscriber release or an abnormal call BSC6910
t receives the Disconnect release. V100R014C00
message and starts (or later)
releasing channel
resources.
2. The BSS receives the
Clear Command message
from the MSC and the
proper call release is
triggered by the network
or the calling or called
subscriber.
3. An outgoing inter-BSC
handover or inter-RAT
handover is triggered and
completed.
Following are criteria
indicating an abnormal
release of traffic channel
during a call:
1. An outgoing inter-BSC
handover fails.
2. An intra-BSC handover
fails.
3. The BSC releases
channel resources.
4. The MSC releases
channel resources.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 899

User Information
Parame Range Unit Description Supported NE
ter Version

User N/A N/A ·User ID, which is created by BSC6900

ID:Alias the system when creating the V900R014C00 (or later)
task. or BSC6910
·Alias, which is created by V100R014C00 (or later)
the user when creating the
task.

IMSI N/A N/A IMSI information of a BSC6900

subscriber. V900R014C00 (or later)
Note: Only when you have or BSC6910
the "User Identity" right, you V100R014C00 (or later)
can view the IMSI
information.

IMEI- 00000000-9 N/A Refer to "IMEI-TAC" in the BSC6900

TAC 9999999 Summary area. V900R014C00 (or later)
or BSC6910
V100R014C00 (or later)

Model N/A N/A Refer to "Model" in the BSC6900

Summary area. V900R014C00 (or later)
or BSC6910
V100R014C00 (or later)

MS N/A N/A Capability of the MS. BSC6900

Capabili V900R014C00 (or later)
ty or BSC6910
V100R014C00 (or later)

>Suppor ·Yes N/A Whether a MS supports the BSC6900

t ·No UtranFDD. V900R014C00 (or later)
UtranFD or BSC6910
D V100R014C00 (or later)

>Suppor ·Yes N/A Whether a MS supports the BSC6900

t ·No UtranTDD. V900R014C00 (or later)
UtranT or BSC6910
DD V100R014C00 (or later)

>Suppor ·Yes N/A Whether a MS supports the BSC6900

t ·No VAMOS. V900R014C00 (or later)
VAMO VAMOS, voice services or BSC6910
S over adaptive multi-user V100R014C00 (or later)
channels on one slot.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 900

Parame Range Unit Description Supported NE

ter Version

>Suppor ·Yes N/A Whether a MS supports the BSC6900

t U900 ·No U900. V900R014C00 (or later)
Frequen That is, whether a MS or BSC6910
cy Band supports accessing to the 3G V100R014C00 (or later)
network using the 900 MHz/
850 MHz band of the 2G
network.

Peer N/A N/A Refer to "MSISDN" in the BSC6900

MSISD Summary area. V900R014C00 (or later)
N or BSC6910
V100R014C00 (or later)

Call Access Information

Parame Range Unit Description Supported NE
ter Version

Access N/A N/A Refer to "Access Time" in the BSC6900

Time Summary area. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Access 1 to 64 N/A Refer to "Access Cell" in the BSC6900

Cell characters Summary area. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Access [0,71] N/A Information about the carrier BSC6900

Carrier frequency at which a MS sends a V900R014C00 (or
Channel Request message, later) or BSC6910
namely, the number of the carrier V100R014C00 (or
frequency. later)

Access [0,7] N/A Information about the channel BSC6900

Channel through which a MS sends a V900R014C00 (or
Channel Request message, later) or BSC6910
namely, the number of the V100R014C00 (or
channel. later)

Access N/A N/A Cause carried in an access BSC6900

Cause request message. V900R014C00 (or
See Access Type in General later) or BSC6910
Evaluation. V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 901

Parame Range Unit Description Supported NE

ter Version

Access ·Inter- N/A According to the access causes to BSC6900

Flag system identify the user's current V900R014C00 (or
(Inter- ·Intra- business is accessed from intra- later) or BSC6910
system/ system system or from inter-system. V100R014C00 (or
Intra- later)
system)

Access ·MOC N/A According to the access causes to BSC6900

Flag ·MTC identify the user's current V900R014C00 (or
(MOC/ business is accessed by MTC or later) or BSC6910
MTC) MOC. V100R014C00 (or
later)

Access ·SMS N/A According to the access causes to BSC6900

Flag ·Voice identify the user's current V900R014C00 (or
(SMS/ business is accessed by SMS or later) or BSC6910
Voice) Voice. V100R014C00 (or
later)

Call N/A N/A Network access result for a BSC6900

Setup mobile-originated call. V900R014C00 (or
Result See the level-1 cause, Call Setup later) or BSC6910
Result, in Call Setup Result/ V100R014C00 (or
Cause of Abnormal Call Setup/ later)
Sub-Cause of Abnormal Call
Setup in General Evaluation.

Cause of N/A N/A Cause of an abnormal signaling BSC6900

abnorma access for a call. V900R014C00 (or
l call See the level-2 cause, Cause of later) or BSC6910
setup Abnormal Call Setup, in Call V100R014C00 (or
Setup Result/Cause of Abnormal later)
Call Setup/Sub-Cause of
Abnormal Call Setup in General
Evaluation.

Subcaus N/A N/A Detailed cause of an abnormal BSC6900

e of signaling access for a call. V900R014C00 (or
abnorma See the level-3 cause, Sub-Cause later) or BSC6910
l call of Abnormal Call Setup, in Call V100R014C00 (or
setup Setup Result/Cause of Abnormal later)
Call Setup/Sub-Cause of
Abnormal Call Setup in General
Evaluation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 902

Parame Range Unit Description Supported NE

ter Version

Access N/A N/A Access delay estimation when BSC6900

Delay the UE accesses the network. V900R014C00 (or
Estimati later) or BSC6910
on V100R014C00 (or
later)

>ASSIG N/A N/A Time when the assignment is BSC6900

NMENT finished after initiating a call and V900R014C00 (or
COMPL accessing the network. later) or BSC6910
ETE V100R014C00 (or
Message later)
Timesta
mp

>Access [0,+∞) Secon Access delay time of the service. BSC6900

Delay d Access Delay = Time of V900R014C00 (or
ASSIGNMENT COMPLETE - later) or BSC6910
Time of CHANNEL REQUEST V100R014C00 (or
later)
="ASSIGNMENT COMPLETE
Message Timestamp"-"Access
Time"

>Overlo ·Yes N/A Whether the abnormal of BSC6900

ng ·No overlong access delay is V900R014C00 (or
Access occurred. later) or BSC6910
Delay The abnormal threshold is set V100R014C00 (or
when creating tasks. later)

>Alertin N/A N/A Time when a VIP subscriber BSC6900

g Time hears the alerting after initiating V900R014C00 (or
a call. later) or BSC6910
V100R014C00 (or
later)

>Call [0,+∞) Secon Call completion delay time of the BSC6900

Complet d service. V900R014C00 (or
ion Call Completion Delay(Alerting) later) or BSC6910
Delay = Time of ALERTING - Time of V100R014C00 (or
(Alertin CHANNEL REQUEST later)
g)
=Alerting Time - Access Time

>Overlo ·Yes N/A Whether the abnormal of BSC6900

ng Call ·No overlong call completion delay V900R014C00 (or
Complet (Alerting) is occurred. later) or BSC6910
ion The abnormal threshold is set V100R014C00 (or
Delay when creating tasks. later)
(Alertin
g)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 903

Parame Range Unit Description Supported NE

ter Version

>Connec N/A N/A Time when a VIP subscriber BSC6900

t hears the voice of the peer V900R014C00 (or
Acknow subscriber after initiating a call. later) or BSC6910
ledge V100R014C00 (or
Time later)

>Call [0,+∞) Secon Call completion delay time of the BSC6900

Complet d service. V900R014C00 (or
ion Call Completion Delay(Connect later) or BSC6910
Delay Ack) = Time of CONNECK V100R014C00 (or
(Connec ACK - Time of CHANNEL later)
t Ack) REQUES REQUEST
=Connect Acknowledge Time -
Access Time

>Overlo ·Yes N/A Whether the abnormal of BSC6900

ng Call ·No overlong call completion delay V900R014C00 (or
Complet (Connect Ack) is occurred. later) or BSC6910
ion The abnormal threshold is set V100R014C00 (or
Delay when creating tasks. later)
(Connec
t Ack)

Measure N/A N/A Measurement information when BSC6900

ment a MS accesses to the network. V900R014C00 (or
Informat later) or BSC6910
ion On V100R014C00 (or
Access later)

>TA [0,63] N/A Value of the TA when a MS BSC6900

accesses to the network. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

>Abnor ·Yes N/A Whether the abnormal that TA is BSC6900

mal TA ·No too large when accessing to the V900R014C00 (or
network is occurred. later) or BSC6910
The abnormal threshold is set V100R014C00 (or
when creating tasks. later)

>RACH [-110,-47] dBm Value of the RACH level when a BSC6900

Level MS accesses to the network. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 904

Parame Range Unit Description Supported NE

ter Version

>Abnor ·Yes N/A Whether the abnormal that BSC6900

mal ·No RACH Level is too small is V900R014C00 (or
RACH occurred. later) or BSC6910
Level The abnormal threshold is set V100R014C00 (or
when creating tasks. later)

Call Release Information

Parame Range Unit Description Supported NE
ter Version

Release N/A N/A Refer to "Release Time" in the BSC6900

Time Summary area. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Duration [0,+∞) Secon Refer to "Duration" in the BSC6900

d Summary area. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Release 1 to 64 N/A Refer to "Release Cell" in the BSC6900

Cell characters Summary area. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Release N/A N/A Information about the carrier BSC6900

Carrier frequency at which a MS sends a V900R014C00 (or
signaling release message. later) or BSC6910
V100R014C00 (or
later)

Call N/A N/A Network release result for a BSC6900

Release mobile-originated call. V900R014C00 (or
Result See the level-1 cause, Call later) or BSC6910
Release Result, in Call Release V100R014C00 (or
Result/Cause of Abnormal Call later)
Release/Sub-Cause of Abnormal
Call Release in General
Evaluation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 905

Parame Range Unit Description Supported NE

ter Version

Cause of N/A N/A Cause of an abnormal signaling BSC6900

abnorma release during a call. V900R014C00 (or
l call See the level-2 cause, Cause of later) or BSC6910
completi Abnormal Call Release, in Call V100R014C00 (or
on Release Result/Cause of later)
Abnormal Call Release/Sub-
Cause of Abnormal Call Release
in General Evaluation.

Subcaus N/A N/A Detailed cause of an abnormal BSC6900

e of signaling release during a call. V900R014C00 (or
abnorma See the level-3 cause, Sub-Cause later) or BSC6910
l call of Abnormal Call Release, in V100R014C00 (or
completi Call Release Result/Cause of later)
on Abnormal Call Release/Sub-
Cause of Abnormal Call Release
in General Evaluation.

Location N/A N/A Refer to the location group where BSC6900

Group a terminal is located when the V900R015C00 or
Number signaling is released. This later version
parameter is valid only for the
multi-RRU serving a cell feature.

CS Service Information
Parame Range Unit Description Supported NE
ter Version

Service N/A N/A Delay estimation for service BSC6900

Process process. V900R014C00
Delay (or later) or
Estimati BSC6910
on V100R014C00
(or later)

>Intra- N/A N/A Timestamp of intra-BSC channel BSC6900

BSC release. V900R014C00
Channel (or later) or
Release BSC6910
Timesta V100R014C00
mp (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 906

Parame Range Unit Description Supported NE

ter Version

>Calling [0,+∞) Secon Calling Duration = Time of BSC6900

Duration d DISCONNECT - Time of V900R014C00
CONNECT ACK (or later) or
=Intra-BSC Channel Release BSC6910
Timestamp - CONNECT ACK V100R014C00
Timestamp (or later)

>Short ·Yes N/A Whether the abnormal of short call BSC6900

Call ·No is occurred. V900R014C00
The abnormal threshold is set when (or later) or
creating tasks. BSC6910
V100R014C00
(or later)

Service N/A N/A Service quality estimation for BSC6900

Quality service process. V900R014C00
Estimati (or later) or
on for BSC6910
Service V100R014C00
Process (or later)

>Uplink ·Yes N/A Whether uplink one-way audio BSC6900

One- ·No occurs during a call. V900R014C00
way The one-way audio test can only (or later) or
Audio detect the one-way audio BSC6910
During a exceptions related to the channels V100R014C00
Call within the BSS (BTS<->TC) (or later)
instead of those related to the Um
and A interfaces.
Principle for detecting uplink one-
way audio: The DSP in the TC of
the BSC performs periodic statistics
on the bad frame rate based on
uplink TRAU frames. When the bad
frame rate reaches the predefined
threshold, the BSS determines that
primary uplink one-way audio
occurs, and starts the mechanism for
confirming the occurrence of
primary uplink one-way audio.
During this process, the BSC sends
a message to the BTS demanding
that the BTS send a test TRAU
frame to the TC. If the TC fails to
receive the test TRAU frame from
the BTS within a specified time
period, one-way audio occurs on the
uplink voice channel.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 907

Parame Range Unit Description Supported NE

ter Version

>Downli ·Yes N/A Whether downlink one-way audio BSC6900

nk One- ·No occurs during a call. V900R014C00
way The one-way audio test can only (or later) or
Audio detect the one-way audio BSC6910
During a exceptions related to the channels V100R014C00
Call within the BSS (BTS<->TC) (or later)
instead of those related to the Um
and A interfaces.
Principle for detecting downlink
one-way audio: The DSP in the
DTRU of the BTS performs
periodic statistics on the bad frame
rate based on downlink TRAU
frames. When the bad frame rate
reaches the predefined threshold,
the BSS determines that primary
downlink one-way audio occurs,
and starts the mechanism for
confirming the occurrence of
primary downlink one-way audio.
During this process, the BSC sends
a message to the TC demanding that
the TC send a test TRAU frame to
the BTS. If the BTS fails to receive
the test TRAU frame from the TC
within a specified time period, one-
way audio occurs on the downlink
voice channel.

>Uplink ·Yes N/A Whether uplink crosstalk occurs BSC6900

Call ·No during a call. V900R014C00
Crosstal The crosstalk test can only detect (or later) or
k the crosstalk exceptions related to BSC6910
the channels within the BSS (BTS<- V100R014C00
>TC) instead of those related to the (or later)
Um and A interfaces.
Principle for detecting uplink
crosstalk: The DSP of the BTS
inserts the unique identifier of a call
into the free bits of uplink voice
TRAU frames. The DSP of the TC
decodes the unique call identifiers
and checks their consistency. If
inconsistency in the unique call
identifiers is detected within the test
period, uplink crosstalk occurs.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 908

Parame Range Unit Description Supported NE

>Bad ·Yes N/A Whether the abnormal of bad BSC6900

Downlin ·No downlink HQI is occurred of call V900R014C00
k HQI setups that include the HQIs before (or later) or
and after the call setup is successful. BSC6910
The abnormal threshold is set when V100R014C00
creating tasks. (or later)

>Uplink [0.00,5.00] N/A Average value for the uplink voice BSC6900
Call VQI quality indicators (VQIs) of V900R014C00
successful call setups. (or later) or
VQI is the Mean Opinion Score BSC6910
(MOS) and indicates the voice V100R014C00
quality of a call. The value of the (or later)
voice quality ranges from 0 to 5.
The larger the value is, the better the
voice quality is.
Average value for the uplink VQIs
of successful call setups =
Aggregated value of uplink VQIs/
Total number of uplink VQI tests

>Bad ·Yes N/A Whether the abnormal of bad uplink BSC6900

Uplink ·No VQI is occurred. V900R014C00
VQI The abnormal threshold is set when (or later) or
creating tasks. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 911

Parame Range Unit Description Supported NE

ter Version

>Downli [0.00,5.00] N/A Average value for the downlink BSC6900

nk Call voice quality indicators (VQIs) of V900R014C00
VQI successful call setups. (or later) or
VQI is the Mean Opinion Score BSC6910
(MOS) and indicates the voice V100R014C00
quality of a call. The value of the (or later)
voice quality ranges from 0 to 5.
The larger the value is, the better the
voice quality is.
Average value for the downlink
VQIs of successful call setups =
Aggregated value of downlink
VQIs/Total number of downlink
VQI tests

>Bad ·Yes N/A Whether the abnormal of bad BSC6900

Downlin ·No downlink VQI is occurred. V900R014C00
k VQI The abnormal threshold is set when (or later) or
creating tasks. BSC6910
V100R014C00
(or later)

Measure N/A N/A Measurement information on BSC6900

ment service process. V900R014C00
Informat (or later) or
ion On BSC6910
Service V100R014C00
Process (or later)

>Averag [-110,-47] dBm Average uplink level on service BSC6900

e Uplink process. V900R014C00
Level (or later) or
BSC6910
V100R014C00
(or later)

>Averag [-110,-47] dBm Average downlink level on service BSC6900

e process. V900R014C00
Downlin (or later) or
k Level BSC6910
V100R014C00
(or later)

>Averag [0,7] N/A Average uplink quality on service BSC6900

e Uplink process. V900R014C00
Quality (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 912

Parame Range Unit Description Supported NE

ter Version

>Averag [0,7] N/A Average downlink quality on BSC6900

e service process. V900R014C00
Downlin (or later) or
k BSC6910
Quality V100R014C00
(or later)

Signaling Procedure Before Call Release

Parame Range Unit Description Supported NE
ter Version

Number [1,+∞) N/A Unique number for the signaling BSC6900

message that a VIP subscriber V900R014C00 (or
sends and receives during the later) or BSC6910
signaling procedure. V100R014C00 (or
later)

Signalin N/A N/A Time when a signaling message BSC6900

g Time is sent or received. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Signalin Uplink N/A Direction in which a signaling BSC6900

g Direct Downlink message is sent or received. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Signalin N/A N/A Type of a signaling message BSC6900

g Type transmitted on the A or Abis V900R014C00 (or
interface during the signaling later) or BSC6910
procedure. For example, the V100R014C00 (or
parameter can be a Channel later)
Request message.

Signalin N/A N/A Content of a signaling message. BSC6900

g You can obtain the content of a V900R014C00 (or
Content signaling message by viewing later) or BSC6910
the related tree structure. V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 913

Measurement Information Before Call Release

Parame Range Unit Description Supported NE
ter Version

Number [1,+∞) N/A Unique number of a signaling BSC6900

message carrying a V900R014C00 (or
measurement report. later) or BSC6910
V100R014C00 (or
later)

Measure N/A N/A Time when a measurement BSC6900

ment report is submitted. V900R014C00 (or
Time later) or BSC6910
V100R014C00 (or
later)

Serial N/A N/A Serial number for a reported BSC6900

Number measurement report. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Measure Server N/A Type of a measurement object, BSC6900

ment Nbr1~6 reported in a measurement V900R014C00 (or
Object report. later) or BSC6910
Type For example, if the parameter is V100R014C00 (or
Server, the measurement object later)
is a serving cell; if the parameter
is Nbr1, the measurement object
is neighboring cell 1.

Measure N/A N/A Name of a measurement object BSC6900

ment reported in a measurement V900R014C00 (or
Object report. later) or BSC6910
The parameter is displayed in the V100R014C00 (or
following format: Name of the later)
BSC: Name of the cell.

BCCH [0,1023] N/A Broadcast control channel BSC6900

(BCCH) of a neighboring cell, V900R014C00 (or
reported in a measurement later) or BSC6910
report. V100R014C00 (or
later)

BSIC [0,77] N/A Base transceiver Station Identity BSC6900

Code (BSIC) of a neighboring V900R014C00 (or
cell, reported in a measurement later) or BSC6910
report. V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 914

Parame Range Unit Description Supported NE

ter Version

TA [0,63] N/A TA of a serving cell, reported in BSC6900

a measurement report. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

RxLevel [-110,-47] dBm Downlink RxLevel of a serving BSC6900

(Downli cell and that of a neighboring V900R014C00 (or
nk) cell, reported in a measurement later) or BSC6910
report. V100R014C00 (or
later)

RxLevel [-110,-47] dBm Uplink RxLevel of a serving BSC6900

(Uplink) cell, reported in a measurement V900R014C00 (or
report. later) or BSC6910
V100R014C00 (or
later)

RxQualit [0,7] N/A Downlink RxQuality of a BSC6900

y serving cell, reported in a V900R014C00 (or
(Downli measurement report. later) or BSC6910
nk) V100R014C00 (or
later)

RxQualit [0,7] N/A Uplink RxQuality of a serving BSC6900

y cell, reported in a measurement V900R014C00 (or
(Uplink) report. later) or BSC6910
V100R014C00 (or
later)

BTS [0,15] N/A BTS power of a serving cell, BSC6900

Power reported in a measurement V900R014C00 (or
report. later) or BSC6910
V100R014C00 (or
later)

MS [0,31] N/A MS power of a serving cell, BSC6900

Power reported in a measurement V900R014C00 (or
report. later) or BSC6910
V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 915

Mobility Analysis
Parame Range Unit Description Supported NE
ter Version

Number [1,+∞) Numb Number for a handover triggered BSC6900

er during a call. V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Abnorm N/A N/A Whether a record indicates an BSC6900

al abnormal handover. V900R014C00 (or
The record indicates an later) or BSC6910
abnormal handover if a red V100R014C00 (or
exclamation mark is displayed. later)

Abnorm · N/A Whether a handover succeeds, BSC6900

al Cause Communicat and the cause of a handover V900R014C00 (or
ion resumes failure. later) or BSC6910
on the The cause is displayed as V100R014C00 (or
original Normal if a handover succeeds. later)
channel after
a handover Possible causes of a handover
failure failure include the following:
communication resumes on the
·the BSC original channel after a handover
releases failure; the BSC releases
channel channel resources; the MSC is
resources faulty.
·the MSC is
faulty

Type ·Intra-BSC N/A Type of a handover BSC6900

handover V900R014C00 (or
·Outgoing later) or BSC6910
cell handover V100R014C00 (or
later)
·Incoming
inter-BSC
handover
·Outgoing
inter-BSC
handover
·Outgoing
inter-RAT
handover

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 916

Parame Range Unit Description Supported NE

ter Version

Begin N/A N/A Time when a handover is BSC6900

Time initiated, V900R014C00 (or
namely, the time when the BSC later) or BSC6910
sends the Handover CMD V100R014C00 (or
message. later)

Duration [0,+∞) N/A Duration = End time - Start time BSC6900

V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Overlon ·Yes N/A ·The first case: "Handover Type" BSC6900

g ·No is "Outgoing inter-BSC V900R014C00 (or
Duration handover" later) or BSC6910
If the duration is more than V100R014C00 (or
"Outgoing BSC Handover later)
Interval", it displays "Yes"; If
not, it displays "No".
·The second case: "Handover
Type" is "Outgoing inter-RAT
handover"
If the duration is more than
"Outgoing System Handover
Interval", it displays "Yes"; If
not, it displays "No". ·The other
case: displays null.
"Outgoing BSC Handover
Interval" and "Outgoing System
Handover Interval" is set when
creating tasks.

End N/A N/A End time of a handover. BSC6900

Time V900R014C00 (or
later) or BSC6910
V100R014C00 (or
later)

Handove N/A N/A Cause of a handover. BSC6900

r V900R014C00 (or
Triggeri later) or BSC6910
ng Cause V100R014C00 (or
later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 917

Parame Range Unit Description Supported NE

ter Version

Source N/A N/A Name of the source cell to be BSC6900

cell handed over. V900R014C00 (or
The parameter is displayed in the later) or BSC6910
following format: Name of the V100R014C00 (or
BSC: Name of the cell (BSC later)
OPC: ID of the cell). You can
obtain the names of the BSC and
the cell from the configuration
data. The names are not
displayed if they are not
available.
In the preceding format, BSC
OPC is the originating signaling
point configured on the BSC
side.

Source N/A N/A Number of source location BSC6900

Location group. V900R014C00 (or
Group later) or BSC6910
No. V100R014C00 (or
later)

Target N/A N/A Name of the target cell to which BSC6900

cell a handover is to be performed. V900R014C00 (or
The parameter is displayed in the later) or BSC6910
following format: Name of the V100R014C00 (or
BSC: Name of the cell (BSC later)
OPC: ID of the cell). You can
obtain the names of the BSC and
the cell from the configuration
data.

Parameters for Viewing GSM Complaint Analysis Support Results - RAN PS

This section describes the parameters for querying GSM PS complaint analysis support results.
You can refer to the description when querying GSM PS complaint analysis support results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 918

Summary
Param Range Unit Description Supported NE
eter Version

Serial [1,2^31-1) N/A Serial number of a CHR in BSC6900

Number General Evaluation. Serial V900R014C00
number is the key word of a CHR (or later) or
by which you can identify this BSC6910
unique CHR. It is also an internal V100R014C00
identifier provided by Nastar. (or later)

Combin N/A N/A Whether a CHR is a combined BSC6900

ed one. V900R014C00
By Nastar, information about a (or later) or
call is obtained from both the BSC6910
mobile-originated BSC and the V100R014C00
mobile-terminated BSC and then (or later)
is combined into one CHR. A
CHR is a combined one if a
yellow icon is displayed.

Status N/A N/A Whether a CHR is abnormal. BSC6900

A CHR is abnormal if a red V900R014C00
exclamation mark is displayed. (or later) or
BSC6910
The cause type of a call is Other V100R014C00
and the exception status of the (or later)
call is unknown if a yellow
question mark is displayed.

Abnorm For details, see N/A Cause of the exception carried in BSC6900
al Cause "Appendix: an Access Request message. V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Key Signaling V100R014C00
(GSM)". (or later)

Networ GSM-CS, GSM- N/A Network that a VIP subscriber BSC6900

k PS accesses to initiate a call. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 919

Param Range Unit Description Supported NE

eter Version

Access Non-SMS N/A Cause of a signaling access. BSC6900

Type message from a V900R014C00
mobile-originated (or later) or
VIP subscriber BSC6910
(AC_ORIGIN_C V100R014C00
ALL_NO_SMS) (or later)
SMS message
from a mobile-
originated VIP
subscriber
(AC_ORIGIN_C
ALL_SMS)
Answer to paging
(AC_ANSWER_
TO_PAGING)
Call re-setup
(AC_CALL_RE_
ESTABLISH)
Emergency call
(AC_EMERGEN
CY_CALL)
Location update
(AC_LOCATION
_UPDATE)
IMSI detachment
(AC_IMSI_DET
ACH)
Data service
(AC_PACKET_C
ALL)
LMU service
(AC_LMU_EST
ABLISH)
SS service
(AC_SS_ESTAB
LISH)
VGCS service
(AC_VGCS_EST
ABLISH)
VBS service
(AC_VBCS_EST
ABLISH)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 920

Param Range Unit Description Supported NE

eter Version

LCS service
(AC_LCS_ESTA
BLISH)
Any other service
(AC_RESERVE
D)
Incoming inter-
BSC handover
(AC_IN_BSC_H
O)
Response to
notification
(AC_NOTIFICA
TION_RSP)
Immediate setup
(AC_IMM_SET_
UP)
RR initialization
(AC_RR_INITIA
LISATION_REQ
)
Indication from
talker
(AC_TALKER_I
NDICATION)
VGCS access
(AC_VGCS_VBS
_VPCS)
Non-SMS
message from a
mobile-
terminated VIP
subscriber
(AC_ANSWER_
TO_PAGING_C
ALL)
SMS message
from a mobile-
terminated VIP
subscriber
(AC_ANSWER_
TO_PAGING_C
ALL)
Normal location
update

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 921

Param Range Unit Description Supported NE

eter Version

(AC_LOCATION
_UPDATE_NOR
MAL)
Periodic location
update
(AC_LOCATION
_UPDATE_PERI
ODIC)
IMSI attachment
(AC_LOCATION
_UPDATE_ATT
ACH)

Access N/A N/A Signaling access time for a call, BSC6900

Time namely, the time when a MS V900R014C00
sends the Channel Request (or later) or
message. BSC6910
V100R014C00
(or later)

Access 1 to 64 characters N/A Name of the cell in which a MS BSC6900

Cell sends the Channel Request V900R014C00
message. (or later) or
The parameter is displayed in the BSC6910
following format: BSC Name: V100R014C00
Cell Name (Cell ID). You can (or later)
obtain the names of the BSC and
the cell from the configuration
data. The names are not
displayed

Release N/A N/A Signaling release time for a call, BSC6900

Time namely, the time when a MS V900R014C00
receives the Channel Release (or later) or
message. BSC6910
V100R014C00
(or later)

Release 1 to 64 characters N/A Name of the cell in which a MS BSC6900

Cell receives the Channel Release V900R014C00
message. (or later) or
The parameter is displayed in the BSC6910
following format: BSC Name: V100R014C00
Cell Name (Cell ID). You can (or later)
obtain the names of the BSC and
the cell from the configuration
data. The names are not display

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 922

Param Range Unit Description Supported NE

eter Version

User N/A N/A ·User ID, which is created by the BSC6900

ID:Alia system when creating the task. V900R014C00
s ·Alias, which is created by the (or later) or
user when creating the task. BSC6910
V100R014C00
(or later)

IMSI N/A N/A IMSI information of a BSC6900

subscriber. V900R014C00
Note: Only when you have the (or later) or
"User Identity" right, you can BSC6910
view the IMSI information. V100R014C00
(or later)

IMEI- 00000000-999999 N/A International mobile equipment BSC6900

TAC 99 identity-type allocation code V900R014C00
(IMSI-TAC) of a VIP subscriber, (or later) or
which is the first eight digits in BSC6910
the IMEI of a UE. V100R014C00
(or later)

Model N/A N/A Type of a MS. BSC6900

You can obtain the IMEI-TACs V900R014C00
of the UE from the MS type (or later) or
management function. BSC6910
V100R014C00
(or later)

Peer N/A N/A Mobile station international BSC6900

MSISD ISDN number (MSISDN) of a V900R014C00
N peer subscriber. (or later) or
BSC6910
V100R014C00
(or later)

Duratio [0,+∞) Seco Service duration covering the BSC6900

n nd call duration and the signaling V900R014C00
setup duration. (or later) or
Service duration = Release time BSC6910
- Access time V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 923

User Information
Param Range Unit Description Supported NE
eter Version

User N/A N/A ·User ID, which is created by the BSC6900

ID:Alia system when creating the task. V900R014C00
s ·Alias, which is created by the (or later) or
user when creating the task. BSC6910
V100R014C00
(or later)

IMSI N/A N/A IMSI information of a BSC6900

subscriber. V900R014C00
Note: Only when you have the (or later) or
"User Identity" right, you can BSC6910
view the IMSI information. V100R014C00
(or later)

IMEI- 00000000-99999 N/A Refer to "IMEI-TAC" in the BSC6900

TAC 999 Summary area. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Model N/A N/A Refer to "Model" in the BSC6900

Summary area. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

MS N/A N/A Capability of the MS. BSC6900

Capabil V900R014C00
ity (or later) or
BSC6910
V100R014C00
(or later)

>Suppo ·Support N/A Whether a Terminal supports BSC6900

rt GPRS ·Unsupport GPRS. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>Suppo N/A N/A GPRS Multislot Class of a BSC6900

rt GPRS Terminal. V900R014C00
Multi- (or later) or
Slot BSC6910
Class V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 924

Param Range Unit Description Supported NE

eter Version

>Suppo ·Support N/A Whether a Terminal supports BSC6900

rt ·Unsupport EGPRS. V900R014C00
EGPRS (or later) or
BSC6910
V100R014C00
(or later)

>Suppo N/A N/A EGPRS Multislot Class of a BSC6900

rt Terminal. V900R014C00
EGPRS (or later) or
Multi- BSC6910
Slot V100R014C00
Class (or later)

>Suppo ·Support N/A Whether a Terminal supports the BSC6900

rt 900M ·Unsupport E-GSM900 band. V900R014C00
E (or later) or
Frequen BSC6910
cy Band V100R014C00
(or later)

>Suppo ·Support N/A Whether a Terminal supports the BSC6900

rt ·Unsupport E-GSM1800 band. V900R014C00
1800M (or later) or
Frequen BSC6910
cy Band V100R014C00
(or later)

>Suppo ·Support N/A Whether a Terminal supports BSC6900

rt G-TD ·Unsupport both GSM and TD-SCDMA. V900R014C00
Dual- (or later) or
Mode BSC6910
V100R014C00
(or later)

>Suppo ·Support N/A Whether a Terminal supports BSC6900

rt G-U ·Unsupport both GSM and UMTS. V900R014C00
Dual- (or later) or
Mode BSC6910
V100R014C00
(or later)

>Suppo ·Support N/A Whether a Terminal supports BSC6900

rt DTM ·Unsupport DTM. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 925

Param Range Unit Description Supported NE

eter Version

>Suppo ·Support N/A Whether a Terminal supports BSC6900

rt PS ·Unsupport handovers in the PS domain. V900R014C00
Handov (or later) or
er BSC6910
V100R014C00
(or later)

Insuffic ·Yes N/A The capability of a Terminal is BSC6900

ient ·No insufficient in the case of the V900R014C00
Termin following: (or later) or
al ·The Terminal supports GPRS BSC6910
Capabil but not EGPRS. V100R014C00
ity (or later)
·The Terminal supports EGPRS
but the EGPRS multislot class is
below 10.

Subscri N/A N/A Parameters related to the service BSC6900

ber that a VIP subscriber subscribes V900R014C00
Registra to when opening an account. (or later) or
tion BSC6910
Paramet V100R014C00
er (or later)

>Reliab N/A N/A For details about the parameter, BSC6900

ility see see 3GPP TS 23.107. V900R014C00
Level (or later) or
BSC6910
V100R014C00
(or later)

>Subscr N/A N/A For details about the parameter, BSC6900

iption see see 3GPP TS 23.107. V900R014C00
Rate (or later) or
BSC6910
V100R014C00
(or later)

Abnorm ·Yes N/A An account-opening exception BSC6900

al ·No occurs in the case of the V900R014C00
Subscri following: (or later) or
ber ·The reliability class of a VIP BSC6910
Registra subscriber is not 3, namely, the V100R014C00
tion reliability class is not the RLC (or later)
acknowledged mode.
·The subscription rate is lower
than the predefined exception
threshold (which is set by
engineers when creating tasks).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 926

Peer Information
Param Rang Unit Description Supported NE
eter e Version

Number N/A N/A Total number of the server applications that BSC6900
of a VIP subscriber accesses when attempting V900R014C00
Server to use a data service. (or later) or
Applica BSC6910
tions V100R014C00
(or later)

List of N/A N/A The list of applications that the server BSC6900
Servers supports. V900R014C00
and (or later) or
Applica BSC6910
tions V100R014C00
(or later)

>IP N/A N/A IP address of the server that a VIP subscriber BSC6900
Address accesses when attempting to use a data V900R014C00
service. (or later) or
BSC6910
V100R014C00
(or later)

>Server N/A N/A Name of the server that a VIP subscriber BSC6900
Name accesses when attempting to use a data V900R014C00
service. You can obtain the name of a server (or later) or
by choosing System Function > Data BSC6910
Service Server Management in the V100R014C00
navigation tree of Nastar based on the IP (or later)
address of the serve

>Port [0,65 N/A Port number of the server that a VIP BSC6900
535) subscriber accesses when attempting to use V900R014C00
a data service. (or later) or
BSC6910
V100R014C00
(or later)

>Applic N/A N/A name of the application that a VIP BSC6900

ation subscriber accesses when attempting to use V900R014C00
a data service. You can obtain the name of (or later) or
an application by choosing System Function BSC6910
> Data Service Server Management in the V100R014C00
navigation tree of Nastar based on the port (or later)
number

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 927

Access and Release Information

Param Ran Uni Description Supported NE
eter ge t Version

Access N/A N/A Access time for a VIP subscriber to use a data BSC6900
Time service. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

TA [0,63 N/A Value of the TA when a Terminal sends the BSC6900

upon ] Channel Request message for a VIP subscriber V900R014C00
Access to use a data service. It indicates the distance (or later) or
between the Terminal and its serving cell to BSC6910
some extent. V100R014C00
(or later)

RxQual [0,7] N/A Value of the RxQuality when a Terminal sends BSC6900
ity upon the Channel Request message for a VIP V900R014C00
Access subscriber to use a data service. It indicates the (or later) or
signal quality during the initial access of the BSC6910
Terminal. V100R014C00
(or later)

GMSK [0,31 N/A Information about the GMSK MEAN BEP BSC6900
MEAN ] when a Terminal sends the Channel Request V900R014C00
BEP message. (or later) or
upon BSC6910
Access V100R014C00
(or later)

8PSK [0,31 N/A Information about the 8PSK MEAN BEP BSC6900
MEAN ] when a Terminal sends the Channel Request V900R014C00
BEP message. (or later) or
upon BSC6910
Access V100R014C00
(or later)

Access 1 to N/A Name of the cell in which a MS sends the BSC6900

Cell 64 Channel Request message. V900R014C00
chara The parameter is displayed in the following (or later) or
cters format: BSC Name: Cell Name (Cell ID). You BSC6910
can obtain the names of the BSC and the cell V100R014C00
from the configuration data. The names are not (or later)
displayed

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 928

Param Ran Uni Description Supported NE

eter ge t Version

Release N/A N/A Time when a VIP subscriber releases a data BSC6900
Time service. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Service [0, Sec Duration of the data service used by a VIP BSC6900
Duratio +∞) ond subscriber. V900R014C00
n (or later) or
BSC6910
V100R014C00
(or later)

Release 1 to N/A Cell in which a VIP subscriber releases a data BSC6900

Cell 64 service. In a GSM network, a cell reselection V900R014C00
chara always triggers the release of data service. (or later) or
cters Therefore, the release cell is always the access BSC6910
cell. V100R014C00
(or later)

Uplink [0, Nu Number of access requests on the RACH BSC6900

Signalin +∞) mbe (uplink CCCH) during the whole process for V900R014C00
g r a subscriber to use a data service. (or later) or
Access BSC6910
Times V100R014C00
(or later)

Mobility Manager Information

Param Ran Uni Description Supported NE
eter ge t Version

Attach [0, Nu Number of the Attach Request messages that BSC6900

Request +∞) mbe a VIP subscriber sends during the whole V900R014C00
Times r process of using a data service. (or later) or
BSC6910
V100R014C00
(or later)

Attach [0, Nu Number of the Attach Accept messages that a BSC6900

Accept +∞) mbe VIP subscriber receives during the whole V900R014C00
Times r process of using a data service. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 929

Param Ran Uni Description Supported NE

eter ge t Version

Attach [0, Nu Number of the Attach Reject messages that a BSC6900

Reject +∞) mbe VIP subscriber receives during the whole V900R014C00
Times r process of using a data service. (or later) or
BSC6910
V100R014C00
(or later)

Detach [0, Nu Number of the Detach Request messages that BSC6900

Request +∞) mbe a VIP subscriber sends during the whole V900R014C00
Times r process of using a data service. (or later) or
BSC6910
V100R014C00
(or later)

Detach [0, Nu Number of the Detach Accept messages that a BSC6900

Accept +∞) mbe VIP subscriber receives during the whole V900R014C00
Times r process of using a data service. (or later) or
BSC6910
V100R014C00
(or later)

PDP [0, Nu Number of the PDP Active Request messages BSC6900

Active +∞) mbe that a VIP subscriber sends during the whole V900R014C00
Request r process of using a data service. (or later) or
Times BSC6910
V100R014C00
(or later)

PDP [0, Nu Number of the PDP Active Accept messages BSC6900

Active +∞) mbe that a VIP subscriber receives during the whole V900R014C00
Accept r process of using a data service. (or later) or
Times BSC6910
V100R014C00
(or later)

PDP [0, Nu Number of the PDP Active Reject messages BSC6900

Active +∞) mbe that a VIP subscriber receives during the whole V900R014C00
Reject r process of using a data service. (or later) or
Times BSC6910
V100R014C00
(or later)

RA [0, Nu Number of the RA Update Request messages BSC6900

Update +∞) mbe that a VIP subscriber sends during the whole V900R014C00
Request r process of using a data service. (or later) or
Times BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 930

Param Ran Uni Description Supported NE

eter ge t Version

RA [0, Nu Number of the RA Update Accept messages BSC6900

Update +∞) mbe that a VIP subscriber receives during the whole V900R014C00
Accept r process of using a data service. (or later) or
Times BSC6910
V100R014C00
(or later)

RA [0, Nu Number of the RA Update Reject messages BSC6900

Update +∞) mbe that a VIP subscriber receives during the whole V900R014C00
Reject r process of using a data service. (or later) or
Times BSC6910
V100R014C00
(or later)

Suspen [0, Nu Number of Suspends during the whole process BSC6900

d Times +∞) mbe for a VIP subscriber to use a data service. V900R014C00
r (or later) or
BSC6910
V100R014C00
(or later)

RAN Abnormal Information

Param Rang Unit Description Supported NE
eter e Version

Times [0, Num Number of TBF setup failures on the BSC6900

of +∞) ber downlink. V900R014C00
Downli (or later) or
nk TBF BSC6910
Setup V100R014C00
Failure (or later)

>Cause N/A N/A Cause of a TBF setup failure on the downlink. BSC6900
s of V900R014C00
Downli (or later) or
nk TBF BSC6910
Setup V100R014C00
Failure (or later)

>Carrie N/A N/A Carrier of a TBF setup failure on the BSC6900

r Index downlink. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 931

Param Rang Unit Description Supported NE

eter e Version

>BCCH N/A N/A BCCH of a TBF setup failure on the BSC6900

downlink. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Times N/A Num Number of TBF setup failures on the uplink. BSC6900
of ber V900R014C00
Uplink (or later) or
TBF BSC6910
Setup V100R014C00
Failure (or later)

>Cause N/A N/A Cause of a TBF setup failure on the uplink. BSC6900
s of V900R014C00
Uplink (or later) or
TBF BSC6910
Setup V100R014C00
Failure (or later)

>Carrie N/A N/A Carrier of a TBF setup failure on the uplink. BSC6900
r Index V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>BCCH N/A N/A BCCH of a TBF setup failure on the uplink. BSC6900
V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Times [0, Num Number of abnormal TBF releases on the BSC6900

of +∞) ber downlink. V900R014C00
Abnor (or later) or
mal BSC6910
Downli V100R014C00
nk TBF (or later)
Release

>Cause N/A N/A Cause of an abnormal TBF release on the BSC6900

s of downlink. V900R014C00
Abnor (or later) or
mal BSC6910
Downli V100R014C00
nk TBF (or later)
Release

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 932

Param Rang Unit Description Supported NE

eter e Version

>Carrie N/A N/A Carrier of an abnormal TBF release on the BSC6900

r Index downlink. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>BCCH N/A N/A BCCH of an abnormal TBF release on the BSC6900

downlink. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Times [0, Num Number of abnormal TBF releases on the BSC6900

of +∞) ber uplink. V900R014C00
Abnor (or later) or
mal BSC6910
Uplink V100R014C00
TBF (or later)
Release

>Cause N/A N/A Cause of an abnormal TBF release on the BSC6900

s of uplink. V900R014C00
Abnor (or later) or
mal BSC6910
Uplink V100R014C00
TBF (or later)
Release

>Carrie N/A N/A Carrier of an abnormal TBF release on the BSC6900

r Index uplink. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>BCCH N/A N/A BCCH of an abnormal TBF release on the BSC6900

uplink. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 933

Latency Sensitivity Information

Param Rang Unit Description Supported NE
eter e Version

Downli N/A N/A Information about the downlink PDU. BSC6900

nk PDU V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>Sent [0, Byte Size of the data transmitted by using the BSC6900
Bytes +∞) downlink PDU. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>Maxi [0, Seco Maximum duration for data transmission by BSC6900

mum +∞) nd using the downlink PDU. V900R014C00
Duratio (or later) or
n on BSC6910
Sendin V100R014C00
g PDU (or later)

>Total [0, Seco Overall duration for data transmission by BSC6900

Duratio +∞) nd using the downlink PDU. V900R014C00
n on (or later) or
Sendin BSC6910
g PDU V100R014C00
(or later)

>Sent [0, Num Total number of the blocks transmitted by BSC6900

Count +∞) ber using the downlink PDU. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>Avera [0, Seco Average duration for data transmission by BSC6900

ge +∞) nd using the downlink PDU. V900R014C00
Duratio (or later) or
n on BSC6910
Sendin V100R014C00
g PDU (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 934

Param Rang Unit Description Supported NE

eter e Version

>Sendi [0, Num Number of times that the duration for data BSC6900
ng +∞) ber transmission by using the downlink PDU V900R014C00
Timeou exceeds the predefined threshold. (or later) or
t Times A device is configured to directly check BSC6910
whether the duration for data transmission by V100R014C00
using the PDU exceeds the predefined (or later)
threshold.

Uplink N/A N/A Information about the uplink PDU. BSC6900

PDU V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>Recei [0, Byte Size of the data transmitted by using the BSC6900
ved +∞) uplink PDU. V900R014C00
Bytes (or later) or
BSC6910
V100R014C00
(or later)

>Maxi [0, Seco Maximum duration for data transmission by BSC6900

mum +∞) nd using the uplink PDU. V900R014C00
Duratio (or later) or
n on BSC6910
Receivi V100R014C00
ng PDU (or later)

>Total [0, Seco Overall duration for data transmission by BSC6900

Duratio +∞) nd using the uplink PDU. V900R014C00
n on (or later) or
Receivi BSC6910
ng PDU V100R014C00
(or later)

>Recei [0, Num Total number of the blocks transmitted by BSC6900

ved +∞) ber using the uplink PDU. V900R014C00
Count (or later) or
BSC6910
V100R014C00
(or later)

>Avera [0, Seco Average duration for data transmission by BSC6900

ge +∞) nd using the uplink PDU. V900R014C00
Duratio (or later) or
n on BSC6910
Receivi V100R014C00
ng PDU (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 935

Param Rang Unit Description Supported NE

eter e Version

>Recei [0, Num Number of times that the duration for data BSC6900
ving +∞) ber transmission by using the uplink PDU V900R014C00
Timeou exceeds the predefined threshold. (or later) or
t Times A device is configured to directly check BSC6910
whether the duration for data transmission by V100R014C00
using the PDU exceeds the predefined (or later)
threshold.

Uplink/ N/A N/A Information about the uplink and downlink BSC6900
Downli PDUs, namely, the information about the V900R014C00
nk PDU incoming and outgoing data transmission on (or later) or
the PDU GB interfaces. BSC6910
V100R014C00
(or later)

>Maxi [0, Seco Maximum interval for data transmission BSC6900

mum +∞) nd between the uplink and downlink PDUs. V900R014C00
Interval (or later) or
Duratio BSC6910
n V100R014C00
(or later)

>Total [0, Seco Aggregated interval of all the intervals for BSC6900
Interval +∞) nd data transmission between every two data- V900R014C00
Duratio transmission time points on the uplink and (or later) or
n downlink PDUs. BSC6910
V100R014C00
(or later)

>Numb [0, Num Number of times that an interval for data BSC6900
er of +∞) ber transmission between the uplink and V900R014C00
Interval downlink PDUs is available. (or later) or
s BSC6910
V100R014C00
(or later)

>Avera [0, Seco Average interval for data transmission BSC6900

ge +∞) nd between the uplink and downlink PDUs. V900R014C00
Interval (or later) or
Duratio BSC6910
n V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 936

Param Rang Unit Description Supported NE

eter e Version

>Numb [0, Num Number of times that the interval for data BSC6900
er of +∞) ber transmission between the uplink and V900R014C00
Interval downlink PDUs exceeds the predefined (or later) or
Timeou threshold. BSC6910
ts A device is configured to directly check V100R014C00
whether the interval for data transmission (or later)
between the uplink and downlink PDUs
exceeds the predefined threshold.

>Uplin [0, Num Number of times that the uplink PDU carries BSC6900
k Data +∞) ber data but downlink PDU does not. V900R014C00
Availab A device is configured to directly check (or later) or
le and whether the uplink PDU carries data while BSC6910
Downli the downlink PDU does not. V100R014C00
nk Data (or later)
Unavail
able
Occurre
nce
Times

Numbe [0, Num Number of times that no service interaction BSC6900

r of No +∞) ber responses. V900R014C00
Service If the number of times that the uplink PDU (or later) or
Interact carries data but downlink PDU does not BSC6910
ion exceeds the exception threshold 1 for the V100R014C00
Timeou response to service interaction, and, (or later)
t Times
at the same time, the value of A, which is
obtained by using the following formula, is
larger than the exception threshold 2 for the
response to service interaction,
the number of times that no response to
service interaction is made indicates a value
of 1; otherwise, it indicates a value of 0.(A =
Number of times that the uplink PDU carries
data but the downlink PDU does not).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 937

Param Rang Unit Description Supported NE

eter e Version

Numbe [0, Num Number of exceptions where the response to BSC6900

r of +∞) ber service interaction is overdue during the V900R014C00
Service whole process for a VIP subscriber to use a (or later) or
Interact data service. BSC6910
ion Number of Service Interaction Timeout V100R014C00
Timeou Times = Number of Timeout Times on (or later)
t Times sending PDUs at Downlink + Number of
Timeout Times on sending PDUs at Uplink +
Number of Number of Interval Timeouts for
data transmission between the uplink and
downlink PDUs.

Averag [0, Num Average duration for the response to service BSC6900
e +∞) ber interaction during the whole process for a V900R014C00
Duratio VIP subscriber to use a data service. (or later) or
n on Average duration for the response to service BSC6910
Service interaction = Average duration for data V100R014C00
Interact transmission by using the downlink PDU + (or later)
ion Average duration for data reception by using
Respon the uplink PDU + Average duration for data
se transmission between the uplink and
downlink PDUs.

Overlo ·Yes N/A Number of exceptions where the average BSC6900

ng ·No duration for the response to service V900R014C00
Averag interaction exceeds the predefined threshold (or later) or
e during the whole process for a subscriber to BSC6910
Duratio use a data service. V100R014C00
n on If the average duration for the response to (or later)
Service service interaction is above the upper
Interact threshold for the average duration for the
ion response to service interaction, the average
Respon duration for the response to service
se interaction overlong.
The threshold is set by engineers during
analysis task creation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 938

Speed Sensitivity Information

Param Ran Unit Description Supported NE
eter ge Version

Statistic N/A N/A Information about the statistics on downlink BSC6900

s on rate-sensitive services. V900R014C00
Downli (or later) or
nk- BSC6910
Rate- V100R014C00
Sensitiv (or later)
e
Service
s

>PDU [0, Byte Size of the data transmitted by using the BSC6900
Bytes +∞) downlink PDU. V900R014C00
Sent at (or later) or
Downli BSC6910
nk V100R014C00
(or later)

>Durati [0, Secon Overall duration for data transmission by BSC6900

on for +∞) d using the downlink PDU. V900R014C00
Sendin (or later) or
g PDU BSC6910
at V100R014C00
Downli (or later)
nk

>PDU [0, Byte Size of the data received by using the uplink BSC6900
Bytes +∞) PDU. V900R014C00
Receive (or later) or
d at BSC6910
Uplink V100R014C00
(or later)

>Down [0, kbit/s Average download rate during the whole BSC6900
load +∞) process for a subscriber to use a data service. V900R014C00
Speed Download rate = Number of bytes (or later) or
(kbit/s) transmitted by using the downlink PDU/ BSC6910
Duration for data transmission by using the V100R014C00
downlink PDU (or later)

>Low ·Yes N/A Number of low download rate exceptions BSC6900

Downlo ·No during the whole process for a subscriber to V900R014C00
ad use a data service. (or later) or
Speed If a download rate is lower than the lower BSC6910
threshold for download rate, V100R014C00
(or later)
the download rate is low.
The threshold is set by engineers when
creating tasks.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 939

Param Ran Unit Description Supported NE

eter ge Version

>Numb [0, Num Number of exceptions where downlink NU BSC6900

er of +∞) ber disorder occurs. V900R014C00
Downli (or later) or
nk NU BSC6910
Out-of- V100R014C00
Order (or later)
Times

>Numb [0, Num Number of exceptions where downlink TCP BSC6900

er of +∞) ber disorder occurs during the whole process for V900R014C00
Downli a subscriber to use a data service. (or later) or
nk TCP BSC6910
Out-of- V100R014C00
Order (or later)
Times

>Avera [1,6] Num Number of timeslots occupied during BSC6900

ge ber downlink data transmission. V900R014C00
Occupi (or later) or
ed BSC6910
Downli V100R014C00
nk Slots (or later)

>Down [0.00, % Multislot satisfaction ratio on the downlink = BSC6900

load 100.0 Average number of timeslots occupied by the V900R014C00
Multi- 0] downlink/Multislot Class of a Terminal x (or later) or
Slot 100% BSC6910
Statisfa The method for calculating the multislot class V100R014C00
ction of a Terminal is as follows: (or later)
Ratio
If Rate-Sensitive Information/Statistics on
Downlink Rate-Sensitive Service/EGDE
Service Flag indicates a valid value, namely,
the EDGE service is available,
you can obtain the multislot class of a
Terminal from Information About the VIP
Subscriber/Capability of the Terminal/
Multislot Class of the Terminal When
Supporting EGPRS.
Otherwise, you can obtain the multislot class
of a Terminal from Information About the
VIP Subscriber/Capability of the Terminal/
Multislot Class of the Terminal When
Supporting GPRS.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 940

Param Ran Unit Description Supported NE

eter ge Version

>Trans [0, Num Number of transmission resources requested BSC6900

mission +∞) ber for the encoding of downlink blocks. V900R014C00
Resour (or later) or
ces BSC6910
Require V100R014C00
d for (or later)
Code
Request
ed by
Downli
nk
Block

>Trans [0, Num Number of transmission resources actually BSC6900

mission +∞) ber used for the encoding of downlink blocks. V900R014C00
Resour (or later) or
ces BSC6910
Used by V100R014C00
Code (or later)
Assigne
d to
Downli
nk
Block

>Resou [0.00, % Transmission-resource satisfaction ratio at BSC6900

rce 100.0 the average downlink single-slot throughput V900R014C00
Statisfa 0] = Number of the transmission resources (or later) or
ction actually used for the encoding of downlink BSC6910
Ratio of blocks/Number of the transmission resources V100R014C00
Downli requested for the encoding of downlink (or later)
nk blocks x 100%
Averag
e
Single-
Slot
Throug
hput
(%)

>GPRS N/A N/A Information about the data service that a VIP BSC6900
Service subscriber uses through GPRS. V900R014C00
Flag (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 941

Param Ran Unit Description Supported NE

eter ge Version

>>Num [0, Num Total number of the blocks, and that of the BSC6900
ber of +∞) ber valid blocks, transmitted on the downlink by V900R014C00
Downli using channel coding schemes CS-1 through (or later) or
nk CS-4. BSC6910
CS1~4 V100R014C00
Blocks/ (or later)
Valid
Blocks

>>Num [0, Num Total number of the blocks transmitted on the BSC6900
ber of +∞) ber downlink V900R014C00
Total = Total number of the blocks transmitted on (or later) or
Blocks the downlink by using various channel BSC6910
Sent at coding schemes V100R014C00
Downli (or later)
nk = Number of the blocks transmitted on the
downlink by using CS-1 +……+ Number of
the blocks transmitted on the downlink by
using CS-4

>>Num [0, Num Total number of the valid blocks transmitted BSC6900
ber of +∞) ber on the downlink V900R014C00
Total = Total number of the valid blocks (or later) or
Valid transmitted on the downlink by using various BSC6910
Blocks channel coding schemes V100R014C00
Sent at (or later)
Downli = Number of the valid blocks transmitted on
nk the downlink by using CS-1 +……+ Number
of the valid blocks transmitted on the
downlink by using CS-4

>>Total [0, Byte Total number of the bytes contained in the BSC6900
Bytes +∞) valid blocks transmitted on the downlink V900R014C00
of Valid = Number of the valid blocks transmitted on (or later) or
Blocks the downlink by using various channel BSC6910
Sent at coding schemes x Number of the bytes V100R014C00
Downli contained in one valid block (or later)
nk
= Number of the valid blocks transmitted on
the downlink by using CS-1 x Number of the
bytes contained in one valid block + …… +
Number of the valid blocks transmitted on the
downlink by using CS-4 x Number of the
bytes contained in one valid block
For details about the relation between a
specific channel coding scheme and the
number of bytes contained in one valid block
transmitted by using this scheme, see 3GPP
TS 44.060-10.2.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 942

Param Ran Unit Description Supported NE

eter ge Version

>>Dow [0.00, % Downlink data-retransmission ratio = Total BSC6900

nlink 100.0 number of the valid blocks transmitted on the V900R014C00
Retrans 0] downlink/Total number of the blocks (or later) or
mission transmitted on the downlink BSC6910
Ratio V100R014C00
(or later)

>>Dow [0.00, N/A Downlink timeslot reuse = Overall duration BSC6900

nlink +∞) for data transmission by using the downlink V900R014C00
Reuse PDU x Average number of the timeslots (or later) or
Ratio occupied by the downlink/2/Total number of BSC6910
the blocks transmitted on the downlink V100R014C00
(or later)

>EGDE N/A N/A Information about the data service that a VIP BSC6900
Service subscriber uses through EGDE. V900R014C00
Flag (or later) or
BSC6910
V100R014C00
(or later)

>>Num [0, Num Total number of the blocks, and that of the BSC6900
ber of +∞) ber valid blocks, transmitted on the downlink by V900R014C00
Downli using modulation and coding schemes (or later) or
nk MCS-1 through MCS-9. BSC6910
MCS1~ V100R014C00
9 (or later)
Blocks/
Valid
Blocks

>>Num [0, Num Total number of the blocks transmitted on the BSC6900
ber of +∞) ber downlink V900R014C00
Total = Total number of the blocks transmitted on (or later) or
Blocks the downlink by using various modulation BSC6910
Sent at and coding schemes V100R014C00
Downli (or later)
nk = Number of the blocks transmitted on the
downlink by using MCS-1 +……+ Number
of the blocks transmitted on the downlink by
using MCS-9

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 943

Param Ran Unit Description Supported NE

eter ge Version

>>Num [0, Num Total number of the valid blocks transmitted BSC6900
ber of +∞) ber on the downlink V900R014C00
Total = Total number of the valid blocks (or later) or
Valid transmitted on the downlink by using various BSC6910
Blocks modulation and coding schemes V100R014C00
Sent at (or later)
Downli = Number of the valid blocks transmitted on
nk the downlink by using MCS-1 +……+
Number of the valid blocks transmitted on the
downlink by using MCS-9

>>Total [0, Byte Total number of the bytes contained in the BSC6900
Bytes +∞) valid blocks transmitted on the downlink V900R014C00
of Valid = Number of the valid blocks transmitted on (or later) or
Blocks the downlink by using various modulation BSC6910
Sent at and coding schemes x Number of the bytes V100R014C00
Downli contained in one valid block (or later)
nk
= Number of the valid blocks transmitted on
the downlink by using MCS-1 x Number of
the bytes contained in one valid block + ……
+ Number of the valid blocks transmitted on
the downlink by using MCS-9 x Number of
the bytes contained in one valid block
For details about the relation between a
specific modulation and coding scheme and
the number of bytes contained in one valid
block transmitted by using this scheme, see
3GPP TS 44.060-10.3.

>>Dow [0.00, % Downlink data-retransmission ratio = Total BSC6900

>>Dow [0,31 N/A Average downlink GMSK BEP. BSC6900

nlink ] V900R014C00
Averag (or later) or
e BSC6910
GMSK V100R014C00
BEP (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 944

Param Ran Unit Description Supported NE

eter ge Version

>>Dow [0,31 N/A Average downlink 8PSK BEP. BSC6900

nlink ] V900R014C00
Averag (or later) or
e 8PSK BSC6910
BEP V100R014C00
(or later)

>>Dow [0,31 N/A 1. If both the average downlink GMSK BEP BSC6900
nlink ] and the average downlink 8PSK BEP are V900R014C00
Averag valid, (or later) or
e BEP use the average downlink GMSK BEP with a BSC6910
higher order. V100R014C00
(or later)
2. If either the average downlink GMSK BEP
or the average downlink 8PSK BEP is valid,
use the one with a valid value as the average
downlink BEP.

>>Dow N/A kbit/s You can obtain the maximum single-slot rate, BSC6900
nlink namely, the average downlink single-slot V900R014C00
Averag throughput, in BEP-Coding Scheme-Rate (or later) or
e Mapping Table based on the average BSC6910
Single- downlink BEP. V100R014C00
Slot The BEP-Coding Scheme-Rate Mapping (or later)
Throug Table is generated by an NE.
hput

>>Um [0.00, % Um-interface quality satisfaction ratio at the BSC6900

Quality 100.0 average downlink single-slot throughput = V900R014C00
Satisfac 0] MIN (Average downlink single-slot (or later) or
tion throughput/Target single-slot throughput x BSC6910
Ratio of 100%, 100%) V100R014C00
Downli The target single-slot throughput is a (or later)
nk customized algorithm parameter.
Averag
e
Single-
Slot
Throug
hput

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 945

Param Ran Unit Description Supported NE

eter ge Version

>>Poor Yes N/A If the average downlink BEP is higher than BSC6900
Transm No the BEP required by the lowest-level coding, V900R014C00
ission and at the same time, the downlink data- (or later) or
Quality retransmission rate is higher than the upper BSC6910
Indicate threshold for downlink data-retransmission V100R014C00
d by rate, (or later)
Downli the transmission quality at the average
nk downlink single-slot throughput is poor.
Averag
e The BEP required by the lowest-level coding
Single- and the upper threshold for downlink data-
Slot retransmission rate are customized algorithm
Throug parameters.
hput

>>Dow [0.00, N/A Downlink timeslot reuse = Overall duration BSC6900

nlink +∞) for data transmission by using the downlink V900R014C00
Reuse PDU x Average number of downlink (or later) or
Ratio timeslots/2/Total number of the blocks BSC6910
transmitted on the downlink V100R014C00
(or later)

Statistic N/A N/A Information about the statistics on uplink BSC6900

s on rate-sensitive services. V900R014C00
Uplink- (or later) or
Rate- BSC6910
Sensitiv V100R014C00
e (or later)
Service
s

>PDU [0, Byte Size of the data received by using the uplink BSC6900
Bytes +∞) PDU. V900R014C00
Receive (or later) or
d at BSC6910
Uplink V100R014C00
(or later)

>Durati [0, Secon Overall duration for data transmission by BSC6900

on for +∞) d using the uplink PDU. V900R014C00
Receivi (or later) or
ng PDU BSC6910
at V100R014C00
Uplink (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 946

Param Ran Unit Description Supported NE

eter ge Version

>PDU [0, Byte Size of the data transmitted by using the BSC6900
Bytes +∞) downlink PDU. V900R014C00
Sent at (or later) or
Downli BSC6910
nk V100R014C00
(or later)

>Uploa [0, kbit/s Average upload rate during the whole process BSC6900
d Speed +∞) for a subscriber to use a data service. V900R014C00
(kbit/s) Upload rate = Number of bytes transmitted (or later) or
by using the uplink PDU/Duration for data BSC6910
transmission by using the uplink PDU V100R014C00
(or later)

>Low Yes N/A Number of low upload rate exceptions during BSC6900
Upload No the whole process for a subscriber to use a V900R014C00
Speed data service. (or later) or
If an upload rate is lower than the lower BSC6910
threshold for upload rate, V100R014C00
(or later)
the upload rate is low.
The threshold is set by engineers when
creating tasks.

>Numb [0, Num Number of exceptions where uplink NU BSC6900

er of +∞) ber disorder occurs. V900R014C00
Uplink (or later) or
NU BSC6910
Out-of- V100R014C00
Order (or later)
Times

>Numb [0, Num Number of exceptions where uplink TCP BSC6900

er of +∞) ber disorder occurs. V900R014C00
Uplink (or later) or
TCP BSC6910
Out-of- V100R014C00
Order (or later)
Times

>Avera [1,6] Num Number of timeslots occupied during uplink BSC6900

ge ber data transmission. V900R014C00
Occupi (or later) or
ed BSC6910
Uplink V100R014C00
Slots (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 947

Param Ran Unit Description Supported NE

eter ge Version

>Uplin [0.00, % Uplink multislot-satisfaction ratio = Average BSC6900

k Multi- 100.0 number of timeslots occupied by the uplink/ V900R014C00
Slot 0] Multislot Class of a Terminal x 100% (or later) or
Statisfa The method for calculating the multislot class BSC6910
ction of a Terminal is as follows: V100R014C00
Ratio (or later)
If Rate-Sensitive Information/Statistics on
Uplink Rate-Sensitive Service/EGDE
Service Flag indicates a valid value, namely,
the EDGE service is available,
you can obtain the multislot class of a
Terminal from Information About the VIP
Subscriber/Capability of the Terminal/
Multislot Class of the Terminal When
Supporting EGPRS.
Otherwise, you can obtain the multislot class
of a Terminal from Information About the
VIP Subscriber/Capability of the Terminal/
Multislot Class of the Terminal When
Supporting GPRS.

>Trans [0, Num Number of transmission resources requested BSC6900

mission +∞) ber for the encoding of uplink blocks. V900R014C00
Resour (or later) or
ces BSC6910
Require V100R014C00
d for (or later)
Code
Request
ed by
Uplink
Block

>Trans [0, Num Number of transmission resources actually BSC6900

mission +∞) ber used for the encoding of uplink blocks. V900R014C00
Resour (or later) or
ces BSC6910
Used by V100R014C00
Code (or later)
Assigne
d to
Uplink
Block

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 948

Param Ran Unit Description Supported NE

eter ge Version

>Resou [0.00, % Transmission-resource satisfaction ratio at BSC6900

rce 100.0 the average uplink single-slot throughput V900R014C00
Statisfa 0] = Number of transmission resources actually (or later) or
ction used for the encoding of uplink blocks/ BSC6910
Ratio of Number of transmission resources requested V100R014C00
Uplink for the encoding of uplink blocks x 100% (or later)
Averag
e
Single-
Slot
Throug
hput
(%)

>Durati [0, Secon Maximum duration for data transmission by BSC6900

on for +∞) d using the downlink PDU. V900R014C00
Sendin (or later) or
g PDU BSC6910
at V100R014C00
Downli (or later)
nk

>Total [0, Secon Overall duration for data transmission by BSC6900

Duratio +∞) d using the downlink PDU. V900R014C00
n for (or later) or
Sendin BSC6910
g PDU V100R014C00
at (or later)
Downli
nk

>PDUs [0, Num Total number of the blocks transmitted by BSC6900

Sent at +∞) ber using the downlink PDU. V900R014C00
Downli (or later) or
nk BSC6910
V100R014C00
(or later)

>Timeo [0, Num Number of times that the duration for data BSC6900
ut +∞) ber transmission by using the downlink PDU V900R014C00
Times exceeds the predefined threshold. (or later) or
on A device is configured to directly check BSC6910
sending whether the duration for data transmission by V100R014C00
PDUs using the PDU exceeds the predefined (or later)
at threshold.
Downli
nk

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 949

Param Ran Unit Description Supported NE

eter ge Version

>GPRS N/A N/A Information about the data service that a VIP BSC6900
Service subscriber uses through GPRS. V900R014C00
Flag (or later) or
BSC6910
V100R014C00
(or later)

>>Num [0, Num Total number of the blocks, and that of the BSC6900
ber of +∞) ber valid blocks, transmitted on the uplink by V900R014C00
Uplink using channel coding schemes CS-1 through (or later) or
CSN CS-4. BSC6910
(1~4) V100R014C00
Blocks/ (or later)
Valid
Blocks

>>Num [0, Num Total number of the blocks transmitted on the BSC6900
ber of +∞) ber uplink V900R014C00
Total = Total number of the blocks transmitted on (or later) or
Blocks the uplink by using various channel coding BSC6910
Receive schemes V100R014C00
d at (or later)
Uplink = Number of the blocks transmitted on the
uplink by using CS-1 +……+ Number of the
blocks transmitted on the uplink by using
CS-4

>>Num [0, Num Total number of the valid blocks transmitted BSC6900
ber of +∞) ber on the uplink V900R014C00
Total = Total number of the valid blocks (or later) or
Valid transmitted on the uplink by using various BSC6910
Blocks channel coding schemes V100R014C00
Receive (or later)
d at = Number of the valid blocks transmitted on
Uplink the uplink by using CS-1 +……+ Number of
the valid blocks transmitted on the uplink by
using CS-4

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 950

Param Ran Unit Description Supported NE

eter ge Version

>>Total [0, Byte Total number of the bytes contained in the BSC6900
Bytes +∞) valid blocks transmitted on the uplink V900R014C00
of Valid = Number of the valid blocks transmitted on (or later) or
Blocks the uplink by using various channel coding BSC6910
Receive schemes x Number of the bytes contained in V100R014C00
d at one valid block (or later)
Uplink
= Number of the valid blocks transmitted on
the uplink by using CS-1 x Number of the
bytes contained in one valid block + …… +
Number of the valid blocks transmitted on the
uplink by using CS-4 x Number of the bytes
contained in one valid block
For details about the relation between a
specific channel coding scheme and the
number of bytes contained in one valid block
transmitted by using this scheme, see 3GPP
TS 44.060-10.2.

>>Upli [0.00, kbit/s Uplink single-slot throughput (Actual) BSC6900

nk 100.0 Uplink single-slot throughput = Total number V900R014C00
Single- 0] of the bytes contained the valid blocks (or later) or
Slot received on the uplink x 8 x 50/1000/Total BSC6910
Throug number of the blocks received on the uplink V100R014C00
hput (or later)
(Actual
)

>>Upli [0.00, N/A Uplink timeslot reuse = Overall duration for BSC6900
nk +∞) data reception by using the uplink PDU x V900R014C00
Reuse Average number of the timeslots occupied by (or later) or
Ratio the uplink/2/Total number of the blocks BSC6910
received on the uplink V100R014C00
(or later)

>EGDE N/A N/A Information about the data service that a VIP BSC6900
Service subscriber uses through EGDE. V900R014C00
Flag (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 951

Param Ran Unit Description Supported NE

eter ge Version

>>Num [0, Num Total number of the blocks, and that of the BSC6900
ber of +∞) ber valid blocks, transmitted on the uplink by V900R014C00
Uplink using modulation and coding schemes (or later) or
MCS1~ MCS-1 through MCS-9. BSC6910
9 V100R014C00
Blocks/ (or later)
Valid
Blocks

>>Num [0, Num Total number of the blocks transmitted on the BSC6900
ber of +∞) ber uplink V900R014C00
Total = Total number of the blocks transmitted on (or later) or
Blocks the uplink by using various modulation and BSC6910
Receive coding schemes V100R014C00
d at (or later)
Uplink = Number of the blocks transmitted on the
uplink by using MCS-1 +……+ Number of
the blocks transmitted on the uplink by using
MCS-9

>>Num [0, Num Total number of the valid blocks transmitted BSC6900
ber of +∞) ber on the uplink V900R014C00
Total = Total number of the valid blocks (or later) or
Valid transmitted on the uplink by using various BSC6910
Blocks modulation and coding schemes V100R014C00
Receive (or later)
d at = Number of the valid blocks transmitted on
Uplink the uplink by using MCS-1 +……+ Number
of the valid blocks transmitted on the uplink
by using MCS-9

>>Total [0, Num Total number of the bytes contained in the BSC6900
Bytes +∞) ber valid blocks transmitted on the uplink V900R014C00
of Valid = Number of the valid blocks transmitted on (or later) or
Blocks the uplink by using various modulation and BSC6910
Receive coding schemes x Number of the bytes V100R014C00
d at contained in one valid block (or later)
Uplink
= Number of the valid blocks transmitted on
the uplink by using MCS-1 x Number of the
bytes contained in one valid block + …… +
Number of the valid blocks transmitted on the
uplink by using MCS-9 x Number of the bytes
contained in one valid block
For details about the relation between a
specific modulation and coding scheme and
the number of bytes contained in one valid
block transmitted by using this scheme, see
3GPP TS 44.060-10.3.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 952

Param Ran Unit Description Supported NE

eter ge Version

>>Upli [0.00, % Uplink data-retransmission ratio = Total BSC6900

nk 100.0 number of the valid blocks transmitted on the V900R014C00
Receive 0] uplink/Total number of the blocks (or later) or
Retrans transmitted on the uplink BSC6910
mission V100R014C00
Ratio (or later)
(%)

>>Upli [0,31 N/A Average uplink GMSK BEP. BSC6900

nk ] V900R014C00
Averag (or later) or
e BSC6910
GMSK V100R014C00
BEP (or later)

>>Upli [0,31 N/A Average uplink 8PSK BEP. BSC6900

nk ] V900R014C00
Averag (or later) or
e 8PSK BSC6910
BEP V100R014C00
(or later)

>>Upli [0,31 N/A 1. If both the average uplink GMSK BEP and BSC6900
nk ] the average uplink 8PSK BEP are valid, V900R014C00
Averag use the average uplink GMSK BEP with a (or later) or
e BEP higher order. BSC6910
V100R014C00
2. If either the average uplink GMSK BEP or (or later)
the average uplink 8PSK BEP is valid,
use the one with a valid value as the average
uplink BEP.

>>Upli [0.00, kbit/s Average uplink single-slot throughput BSC6900

nk 100.0 required to achieve a specific quality level on V900R014C00
Averag 0] the Um interface. (or later) or
e You can obtain the maximum single-slot rate, BSC6910
Single- namely, the average uplink single-slot V100R014C00
Slot throughput, in BEP-Coding Scheme-Rate (or later)
Throug Mapping Table based on the average uplink
hput BEP.
Require
d for The BEP-Coding Scheme-Rate Mapping
Um Table is generated by an NE.
Quality

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 953

Param Ran Unit Description Supported NE

eter ge Version

>>Um [0, Num 1 Obtain a coding scheme from BEP-Coding BSC6900

Quality +∞) ber Scheme-Rate Mapping Table based on the V900R014C00
Unsatis average uplink BEP. Then record it as (or later) or
faction Average coding scheme_Average uplink BSC6910
Times BEP. V100R014C00
of Obtain the coding scheme used for collecting (or later)
Downli the total number of the blocks actually
nk received on the uplink, based on the total
Averag number of the blocks received on the uplink.
e Then record it as Average coding
Single- scheme_Number of the blocks actually
Slot received on the uplink.
Throug
hput Average coding scheme_Number of the
blocks actually received on the uplink =
(MCS-1 x Number of the blocks received on
the uplink by MCS-1 + MCS-2 x Number of
the blocks received on the uplink by MCS-2
+……+ MCS-9 x Number of the blocks
received on the uplink by MCS-9)/(Number
of the blocks received on the uplink by
MCS-1 + Number of the blocks received on
the uplink by MCS-2 +……+ Number of the
blocks received on the uplink by MCS-9)
3. If the average uplink single-slot throughput
is smaller than the target single-slot
throughput, and,
at the same time, the value of B, which is
obtained by using the following formula, is
larger than the threshold for Um-interface
quality satisfaction rate at the average uplink
single-slot throughput, the quality on the Um
interface does not meet the requirements.
B = Average coding scheme_average uplink
BEP/Average coding scheme_Number of the
blocks actually received on the uplink.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 954

Param Ran Unit Description Supported NE

eter ge Version

>>Poor ·Yes N/A If the average uplink BEP is higher than the BSC6900
Transm ·No BEP required by the lowest-level coding, V900R014C00
ission and, (or later) or
Quality at the same time, the uplink data- BSC6910
Indicate retransmission rate is higher than the upper V100R014C00
d by threshold for uplink data-retransmission rate, (or later)
Uplink
Averag the transmission quality at the average
e downlink single-slot throughput is poor.
Single- The BEP required by the lowest-level coding
Slot and the upper threshold for uplink data-
Throug reception-and-retransmission rate are
hput customized algorithm parameters.

>>Upli [0,10 % Uplink single-slot throughput (Actual) BSC6900

nk 0] Uplink single-slot throughput = Total number V900R014C00
Single- of the bytes contained the valid blocks (or later) or
Slot received on the uplink x 8 x 50/1000/Total BSC6910
Throug number of the blocks received on the uplink V100R014C00
hput (or later)
(Actual
)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 955

Summary Information
Param Ran Unit Description Supported NE
eter ge Version

Total [0, Byte Total downlink traffic during the whole BSC6900
Traffic +∞) process for a subscriber to use a data service. V900R014C00
at Total downlink traffic = Delay-Sensitive (or later) or
Downli Information/Total Number of the Bytes BSC6910
nk Transmitted by Using the Downlink PDU V100R014C00
(or later)
+ Rate-Sensitive Information/Statistics on
Downlink Rate-Sensitive Service/Number of
the Bytes Transmitted by Using the
Downlink PDU
+ Rate-Sensitive Information/Statistics on
Uplink Rate-Sensitive Service/Number of
the Bytes Transmitted by Using the
Downlink PDU

Total [0, Byte Total uplink traffic during the whole process BSC6900
Traffic +∞) for a subscriber to use a data service. V900R014C00
at Total uplink traffic = Delay-Sensitive (or later) or
Uplink Information/Total Number of the Bytes BSC6910
Transmitted by Using the Uplink PDU V100R014C00
(or later)
+ Rate-Sensitive Information/Statistics on
Uplink Rate-Sensitive Service/Number of
the Bytes Transmitted by Using the Uplink
PDU
+ Rate-Sensitive Information/Statistics on
Downlink Rate-Sensitive Service/Number of
the Bytes Transmitted by Using the Uplink
PDU

Signaling Procedure Before Call Release

Param Ran Unit Description Supported NE
eter ge Version

Number [1, N/A Unique number for the signaling message that BSC6900
+∞) a VIP subscriber sends and receives during V900R014C00
the signaling procedure. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 956

Param Ran Unit Description Supported NE

eter ge Version

Signali N/A N/A Time when a signaling message is sent or BSC6900

ng Time received. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Signali · N/A Direction in which a signaling message is sent BSC6900

ng Uplin or received. V900R014C00
Direct k (or later) or
· BSC6910
Dow V100R014C00
nlink (or later)

Signali N/A N/A Type of a signaling message transmitted on BSC6900

ng Type the A, Abis, GB, or PTP interface during the V900R014C00
signaling procedure. For example, the (or later) or
parameter can be an Immediate Assignment BSC6910
message. V100R014C00
(or later)

Signali N/A N/A Content of a signaling message. You can BSC6900

ng obtain the content of a signaling message by V900R014C00
Content viewing the related tree structure. (or later) or
BSC6910
V100R014C00
(or later)

Measurement Information
Parame Rang Unit Description Supported NE
ter e Version

Number [1, N/A Unique number of a signaling message BSC6900

+∞) carrying a measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Time N/A N/A Time when a measurement report is BSC6900

submitted. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 957

Parame Rang Unit Description Supported NE

ter e Version

MR ·2G N/A Type of a measurement report. BSC6900

Type NC V900R014C00
MR (or later) or
·3G BSC6910
MR V100R014C00
(or later)
·E-
UTRA
N MR

Measure Server N/A Type of a measurement object reported in a BSC6900

ment Nbr1~ measurement report. V900R014C00
Object 6 For example, if the parameter is Server, the (or later) or
Type measurement object is a serving cell; if the BSC6910
parameter is Nbr1, the measurement object V100R014C00
is neighboring cell 1. (or later)

Measure N/A N/A name of a measurement object reported in BSC6900

ment a measurement report. V900R014C00
Object The parameter is displayed in the following (or later) or
format: name of the BSC: name of the cell. BSC6910
V100R014C00
(or later)

BCCH [0,102 N/A BCCH of a neighboring cell on 2G network, BSC6900

3] reported in a measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

BSIC [0,77] N/A BSIC of a neighboring cell on 2G network, BSC6900

reported in a measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RxLevel [-110,- dBm Downlink RxLevel of a serving cell and that BSC6900
(DL) 47] of a neighboring cell on 2G network, V900R014C00
reported in a measurement report. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 958

Parame Rang Unit Description Supported NE

ter e Version

Frequen [0,102 N/A Frequency on 3G network, reported in a BSC6900

cy 3] measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

P-SC [0,512 N/A Primary scrambling code on 3G networkl, BSC6900

] reported in a measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RSCP [-116,- dBm RSCP on 3G networkl, reported in a BSC6900

25] measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Frequen [0,102 N/A Frequency on LTE network, reported in a BSC6900

cy 3] measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

PCI [0,503 N/A Primary scrambling code on LTE networkl, BSC6900

] reported in a measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

RSRP [-140,- dBm RSCP on LTE networkl, reported in a BSC6900

43] measurement report. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 959

Mobility Analysis
Parame Range Unit Description Supported NE
ter Version

Number [1, N/A Number. BSC6900

+∞) V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Abnorm N/A N/A If the time interval is above the exception BSC6900
al threshold for cell reselection, V900R014C00
the cell reselection fails and an exclamation (or later) or
mark ! is displayed. BSC6910
V100R014C00
The threshold is set by engineers when (or later)
creating tasks.

Abnorm Overlo N/A If the time interval is above the exception BSC6900
al Cause ng threshold for cell reselection, it displays V900R014C00
time of "Overlong time of cell reselection (or later) or
cell (Duration)". BSC6910
reselec V100R014C00
tion (or later)
(Durati
on)

Type ·Cell N/A Type of a mobility analysis, namely, cell BSC6900

Resele reselection. V900R014C00
ction (or later) or
BSC6910
V100R014C00
(or later)

End N/A N/A Time when a cell reselection ends. BSC6900

Time V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Source N/A N/A Source cell for a cell reselection. BSC6900

Cell The parameter is displayed in the following V900R014C00
format: BSC Name: Cell Name (Cell ID). (or later) or
BSC6910
You can obtain the names of the BSC and V100R014C00
the cell based on the internal ID of the BSC (or later)
and the ID of the cell. The names are not
displayed if they are not available.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 960

Parame Range Unit Description Supported NE

ter Version

Reselect [0,7] N/A RxQulity of the source cell for a cell BSC6900
RxQuali reselection. V900R014C00
ty (or later) or
BSC6910
V100R014C00
(or later)

Reselect [0,31] N/A GMSK MEAN BEP of the source cell for a BSC6900
GMSK cell reselection. V900R014C00
MEAN (or later) or
BEP BSC6910
V100R014C00
(or later)

Reselect [0,31] N/A 8PSK MEAN BEP of the source cell for a BSC6900
8PSK cell reselection. V900R014C00
MEAN (or later) or
BEP BSC6910
V100R014C00
(or later)

Target N/A N/A Target cell for a cell reselection. BSC6900

Access [0,7] N/A RxQulity of the target cell for a cell BSC6900
RxQuali reselection. V900R014C00
ty (or later) or
BSC6910
V100R014C00
(or later)

Access [0,31] N/A GMSK MEAN BEP of the target cell for a BSC6900
GMSK cell reselection. V900R014C00
MEAN (or later) or
BEP BSC6910
V100R014C00
(or later)

Access [0,31] N/A 8PSK MEAN BEP of the target cell for a BSC6900
8PSK cell reselection. V900R014C00
MEAN (or later) or
BEP BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 961

3.10.6 Reference for Complaint Analysis Support Parameters

(UMTS)
This section describes the parameters for querying UMTS complaint analysis support results.
You can refer to the description when querying UMTS complaint analysis support results.

Summary
Param Range Uni Description Supported
eter t NE Version

Serial [1,2^31-1) N/A Serial number of a CHR in the Overview BSC6900

Numbe Table. Serial number is a keyword of a V900R014C00
r call record. It is an internal identification (or later) or
in the Nastar and can uniquely identify BSC6910
a call record. V100R014C00
(or later)

Combi N/A N/A Whether a CHR is combined. BSC6900

ned The Nastar supports the combination of V900R014C00
inter-RNC CHRs. If a yellow icon is (or later) or
displayed in this column, the CHR is BSC6910
combined. V100R014C00
(or later)

Status ·! N/A Whether a call record is abnormal. BSC6900

·Blank If a red exclamation mark is displayed V900R014C00
in this column, the call record is (or later) or
abnormal. BSC6910
V100R014C00
If a yellow question mark is displayed in (or later)
this column, the exception type of this
call record in the navigation tree is Other
and the exception status is unknown.

Abnor For details, N/A Exception cause of a call. BSC6900

mal see Remark: For the access counters such as V900R014C00
Cause "Appendix: TP, Ec/No, RSCP, if the active set (or later) or
Exception contains multiple cells during access, BSC6910
Cause only the counters for the first cell in this V100R014C00
Classificatio active set are analyzed. (or later)
n/
Enumeration The Nastar collects statistics on the
Values of number of each of the following types
Failure Cause of exceptions occuring during calls:
(UMTS)". uplink one-way audio, downlink one-
way audio, and garble noise.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 962

Param Range Uni Description Supported

eter t NE Version

Networ UMTS N/A Network that a call accesses. BSC6900

k V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Access ·Static reloc N/A Same as Access Information -> RRC BSC6900
Type in Setup Type. V900R014C00
·HHO reloc (or later) or
in BSC6910
V100R014C00
·Cell update (or later)
reloc in
·Inter RAT
handover in
·RRC setup
without DRD
·RRC setup
with DRD

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 963

Param Range Uni Description Supported

eter t NE Version

Access ·Originating N/A Same as Access Information -> RRC BSC6900

Cause Conversation Setup Cause. V900R014C00
al Call (or later) or
·Originating BSC6910
Streaming V100R014C00
Call (or later)

·Originating
Interactive
Call
·Originating
Background
Call
·Originating
Subscribed
traffic Call
·Terminating
Conversation
al Call
·Terminating
Streaming
Call
·Terminating
Interactive
Call
·Terminating
Background
Call
·Emergency
Call
·Inter-RAT
cell re-
selection
·Inter-RAT
cell change
order
·Registration
·Detach
·Originating
High Priority
Signaling
·Originating
Low Priority
Signaling

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 964

Param Range Uni Description Supported

eter t NE Version

·Call re-
establishmen
t
·Terminating
High Priority
Signaling
·Terminating
Low Priority
Signaling
·Terminating
- cause
unknown
·MBMS
reception
·MBMS ptp
RB request

Access N/A N/A Same as Access Information -> RRC BSC6900

Time Request Time. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Access 1 to 64 N/A Same as Access Information -> Cell on BSC6900

Cell characters RRC Setup. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Release N/A N/A Same as Release Information -> RRC BSC6900

Time Release Time V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Release 1 to 64 N/A Same as Release Information -> RRC BSC6900

Cell characters Release Cell V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 965

Param Range Uni Description Supported

eter t NE Version

User N/A N/A ·User ID, which is created by the system BSC6900
ID:Alia when creating the task. V900R014C00
s ·Alias, which is created by the user when (or later) or
creating the task. BSC6910
V100R014C00
(or later)

IMSI N/A N/A IMSI information of a subscriber. BSC6900

Note: Only when you have the "User V900R014C00
Identity" right, you can view the IMSI (or later) or
information. BSC6910
V100R014C00
(or later)

IMEI- 00000000-99 N/A First eight digits in the IMEI of a UE. BSC6900
TAC 999999 IMEI is international mobile equipment V900R014C00
identity for short and TAC is type (or later) or
approval code for short. BSC6910
V100R014C00
(or later)

al The UE model can be queried V900R014C00
Model using terminal type management (or later) or
based on the IMEI-TAC of the BSC6910
UE. V100R014C00
(or later)

UE N/A N/A Capability of a UE. BSC6900

Capabil V900R014C00
ity (or later) or
BSC6910
V100R014C00
(or later)

>Proto ·REL-99 N/A 3GPP version with which a UE BSC6900

col ·REL-4 ~ REL-20 complies. V900R014C00
Versio (or later) or
n ·later than REL-20 BSC6910
V100R014C00
(or later)

>Power [1,4] N/A Power class of a UE. BSC6900

Class For details, see "A UE with UE V900R014C00
power class 3bis signals the (or later) or
value 3" under "UE Radio BSC6910
Transmission and Reception V100R014C00
(FDD)" in 3GPP TS 25.101. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 969

Param Range Uni Description Supported

eter t NE Version

>Suppo ·Band I N/A Universal Terrestrial Radio BSC6900

rt ·Band II Access (UTRA) frequency V900R014C00
UTRA bands supported by a UE. (or later) or
Band ·Band III BSC6910
For details, see Table 5.0
·Band IV "UTRA FDD frequency bands" V100R014C00
·Band V under "UE Radio Transmission (or later)
·Band VI and Reception (FDD)" in 3GPP
TS 25.101.
·Band VII
·Band VIII
·Band IX
·Band X
·Band XI
·Band XII
·Band XIII
·Band XIV
·Band XV
·Band XVI
·Band XVII
·Band XVIII
·Band XIX
·Band XX
·Band XXI
·Band XXII
·Reserved

>HSPA N/A N/A HSPA capability of a UE. BSC6900

Capabil V900R014C00
ity (or later) or
BSC6910
V100R014C00
(or later)

>>HS- [1,64] N/A HSDPA capability of a UE. A BSC6900

DSCH larger value of this parameter V900R014C00
Capabil indicates larger HSDPA (or later) or
ity capability. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 970

Param Range Uni Description Supported

eter t NE Version

>>E- [1,16] N/A HSUPA capability of a UE. A BSC6900

DCH larger value of this parameter V900R014C00
Capabil indicates larger HSUPA (or later) or
ity capability. BSC6910
V100R014C00
(or later)

>>Sup ·supported N/A Whether a UE supports E- BSC6900

port E- ·unsupported RACH. V900R014C00
RACH (or later) or
BSC6910
V100R014C00
(or later)

>>Sup ·supported N/A Whether a UE supports E- BSC6900

port E- ·unsupported FACH. V900R014C00
FACH (or later) or
BSC6910
V100R014C00
(or later)

>>Sup ·supported N/A Whether a UE supports BSC6900

port ·unsupported discontinuous transmission V900R014C00
DTXD (DTX) and discontinuous (or later) or
RX reception (DRX). BSC6910
V100R014C00
(or later)

>>Sup ·supported N/A Whether a UE supports HS- BSC6900

port ·unsupported SCCH. V900R014C00
HS- (or later) or
SCCH BSC6910
Less V100R014C00
Operati (or later)
on

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 971

Param Range Uni Description Supported

eter t NE Version

>Mobil ·Support of GSM N/A Mobility capability of a UE. For BSC6900

ity ·GSM450 example, "Support of Inter-RAT V900R014C00
Capabil PS handover" indicates whether (or later) or
ity ·GSM480 a UE supports inter-RAT BSC6910
·GSM850 handover in the PS domain. V100R014C00
·GSM900P (or later)
·GSM900E
·GSM1800
·GSM1900
·Support of Inter-
RAT PS handover
·Support for lossless
SRNS relocation
·Support of E-UTRA
FDD
·Support of Inter-
RAT PS Handover to
E-UTRA FDD
·Support of UTRAN
to GERAN NACC
·Support of Handover
to GAN
·Support of PS
Handover to GAN
·Reserved

>Suppo ·Support Band 1 N/A Evolved Universal Terrestrial BSC6900

rt E- ...... Radio Access (E-UTRA) V900R014C00
UTRA frequency bands supported by a (or later) or
Band ·Support Band 64 UE. BSC6910
Capabil V100R014C00
ity (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 972

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 976

RRC N/A N/A Cause of RRC setup failure. BSC6900

Setup V900R014C00
Failure (or later) or
Cause BSC6910
V100R014C00
(or later)

>Error For details, see N/A Error Type. BSC6900

Type "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

>Error For details, see N/A Error Reason. BSC6900

Reason "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 979

Param Range Uni Description Supported

eter t NE Version

RRC N/A N/A Time information on RRC setup. BSC6900

Setup V900R014C00
Time (or later) or
Info BSC6910
V100R014C00
(or later)

>RRC [0,+∞) Seco Delay on RRC setup. The BSC6900

Setup nd statistical points are as follows: V900R014C00
Delay ·RRC setup: Timestamp in the (or later) or
RRC CONNECTION REQUEST BSC6910
message - Timestamp in the RRC V100R014C00
CONNECTION SETUP (or later)
COMPLETE message.
·Incoming migration: Timestamp
in the RELOCATION REQUEST
message - Timestamp in the UE
CAPABILITY INFORMATION
CONFIRM message.
·Inter-RAT handover: Timestamp
in the RELOCATION REQUEST
message - Timestamp in the
UTRAN MOBILITY
INFORMATION CONFIRM
message.

>Overl ·Yes N/A Overlong RRC setup delay occurs BSC6900

ong ·No when the RRC setup delay V900R014C00
RRC exceeds the overlong delay (or later) or
Setup threshold limit. BSC6910
Delay The abnormal threshold is set by V100R014C00
engineers during analysis task (or later)
creation.

Measur N/A N/A Measurement information on BSC6900

ement RRC setup. V900R014C00
Info on (or later) or
RRC BSC6910
Setup V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 980

Param Range Uni Description Supported

eter t NE Version

>Cell N/A N/A Cell on which RAB setup is BSC6900

requested. V900R014C00
The parameter value is displayed (or later) or
in the following format: RNC BSC6910
name:cell name (RNCID:cell ID). V100R014C00
The RNC name and cell name can (or later)
be obtained from configuration
data. If the RNC name and cell
name cannot be queried, they are
not displayed.

>TP [0,3069 ] N/A Time Propagation (TP) is a term BSC6900

defined by Huawei to indicate V900R014C00
time propagation delay during UE (or later) or
access. BSC6910
V100R014C00
(or later)

>TP ·Yes N/A If "TP" is larger than "TP BSC6900

Abnor ·No abnormal threshold", it indicators V900R014C00
mal that the TP is abnormal on RRC (or later) or
setup. BSC6910
Abnormal threshold is set when V100R014C00
creating tasks. (or later)

Remark: If the active set contains

multiple cells during access, the
counters for all the cells in this
active set are analyzed.

>Ec/ [-24,0] dB Ec/No of the serving cell on RRC BSC6900

NO setup. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>Ec/ ·Yes N/A If "Ec/No" is smaller than "Ec/No BSC6900

NO ·No abnormal threshold on RRC V900R014C00
Abnor setup", it indicators that the Ec/No (or later) or
mal is abnormal on RRC setup. BSC6910
Abnormal threshold is set when V100R014C00
creating tasks. (or later)

Remark: If the active set contains

multiple cells during access, the
counters for all the cells in this
active set are analyzed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 981

Param Range Uni Description Supported

eter t NE Version

>RSCP [-116,-25] dBm RSCP of the serving cell on RRC BSC6900

setup. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>RSCP ·Yes N/A If "RSCP" is smaller than "RSCP BSC6900

Abnor ·No abnormal threshold on RRC V900R014C00
mal setup", it indicators that the RSCP (or later) or
is abnormal on RRC setup. BSC6910
Abnormal threshold is set when V100R014C00
creating tasks. (or later)

Remark: If the active set contains

multiple cells during access, the
counters for all the cells in this
active set are analyzed.

Release Information
Param Range Unit Description Supported
eter NE Version

RRC N/A N/A Release time of RRC connection. BSC6900

Release That is, timestamp in the RRC V900R014C00
Time CONNECTION RELEASE (or later) or
message. BSC6910
V100R014C00
(or later)

Duratio [0,+∞) Seco Duration of a call. BSC6900

n nd Call duration = RRC release time V900R014C00
- RRC setup request time (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 982

Param Range Unit Description Supported

eter NE Version

RRC 1 to 64 characters N/A Name of the cell from which BSC6900

Release signaling is released. V900R014C00
Cell The parameter value is displayed (or later) or
in the following format: RNC BSC6910
name:cell name (RNCID: cellID). V100R014C00
The RNC name and cell name can (or later)
be obtained from configuration
data. If the RNC name and cell
name cannot be queried, they are
not displayed.

RRC ·Successful N/A RRC release results. BSC6900

Release ·Failed V900R014C00
Result (or later) or
BSC6910
V100R014C00
(or later)

IU N/A N/A Release cause carried in the last IU BSC6900

Release RELEASE COMMAND message V900R014C00
Cause received by an RNC. (or later) or
BSC6910
V100R014C00
(or later)

>Cause N/A N/A Failure cause. BSC6900

value For details, see 3GPP V900R014C00
25.413-9.2.1.4. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 983

Statistical Information
Param Range Unit Description Supported
eter NE Version

Soft N/A N/A Soft handover information. BSC6900

Handov V900R014C00
er Info (or later) or
BSC6910
V100R014C00
(or later)

>Soft [0,+∞) Num Number of soft handover requests, BSC6900

Handov ber including soft handover requests V900R014C00
er and softer handover requests. (or later) or
Request BSC6910
s V100R014C00
(or later)

>Succe [0,+∞) Num Number of successful soft BSC6900

ssful ber handovers, including successful V900R014C00
Soft soft handovers and successful (or later) or
Handov softer handovers. BSC6910
ers V100R014C00
(or later)

>Softer [0,+∞) Num Number of softer handover BSC6900

Handov ber requests. V900R014C00
er (or later) or
Request BSC6910
s V100R014C00
(or later)

>Succe [0,+∞) Num Number of successful softer BSC6900

ssful ber handovers. V900R014C00
Softer (or later) or
Handov BSC6910
ers V100R014C00
(or later)

Hard N/A N/A Hard handover information. BSC6900

Handov V900R014C00
er Info (or later) or
BSC6910
V100R014C00
(or later)

>Intra- [0,+∞) Num Number of intra-frequency hard BSC6900

Freq ber handover requests. V900R014C00
Handov (or later) or
er BSC6910
Request V100R014C00
s (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 984

Param Range Unit Description Supported

eter NE Version

>Succe [0,+∞) Num Number of successful intra- BSC6900

ssful ber frequency hard handovers. V900R014C00
Intra- (or later) or
Freq BSC6910
Handov V100R014C00
ers (or later)

>Inter- [0,+∞) Num Number of inter-frequency hard BSC6900

Freq ber handover requests. V900R014C00
Handov (or later) or
er BSC6910
Request V100R014C00
s (or later)

>Succe [0,+∞) Num Number of successful inter- BSC6900

ssful ber frequency hard handovers. V900R014C00
Inter- (or later) or
Freq BSC6910
Handov V100R014C00
ers (or later)

Inter- N/A N/A Inter-RAT handover information BSC6900

RAT V900R014C00
Handov (or later) or
er Info BSC6910
V100R014C00
(or later)

>Inter- [0,+∞) Num Number of CS domain outgoing BSC6900

System ber inter-RAT handover requests. V900R014C00
Outgoin (or later) or
g BSC6910
Handov V100R014C00
er (or later)
Request
s(CS)

>Inter- [0,+∞) Num Number of PS domain outgoing BSC6900

System ber inter-RAT handover requests. V900R014C00
Outgoin (or later) or
g BSC6910
Handov V100R014C00
er (or later)
Request
s(PS)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 985

Param Range Unit Description Supported

eter NE Version

>Succe [0,+∞) Num Number of successful outgoing BSC6900

ssful ber inter-RAT handovers. V900R014C00
Inter- (or later) or
System BSC6910
Outgoin V100R014C00
g (or later)
Handov
ers

>Inter- [0,+∞) Num Number of incoming inter-RAT BSC6900

System ber handover requests. V900R014C00
Incomi (or later) or
ng BSC6910
Handov V100R014C00
er (or later)
Request
s

>Succe [0,+∞) Num Number of successful incoming BSC6900

ssful ber inter-RAT handovers. V900R014C00
Inter- (or later) or
System BSC6910
Incomi V100R014C00
ng (or later)
Handov
ers

DCCC N/A N/A DCCC information. BSC6900

Info V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>DCCC [0,+∞) Num Number of DCCC speed increase BSC6900

Speed ber initializations during a call. V900R014C00
Increas (or later) or
e BSC6910
Initializ V100R014C00
ation (or later)
Times

>DCCC [0,+∞) Num Number of successful DCCC BSC6900

Speed ber speed increases during a call. V900R014C00
Increas (or later) or
e BSC6910
Success V100R014C00
Times (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 986

Param Range Unit Description Supported

>CS [0,+∞) Num CS plus PS multi-RAB PS BSC6900

plus PS ber abnormal release times. V900R014C00
multi- (or later) or
RAB PS BSC6910
abnorm V100R014C00
al (or later)
release
times

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 990

Param Range Unit Description Supported

eter NE Version

>Setup [0,+∞) Num Setup attempts of combined BSC6900

Attempt ber service(PS + PS). V900R014C00
s of (or later) or
Combin BSC6910
ed V100R014C00
Service (or later)
(PS +
PS)

>Succe [0,+∞) Num Successful setups of combined BSC6900

ssful ber service(PS + PS). V900R014C00
Setups (or later) or
of BSC6910
Combin V100R014C00
ed (or later)
Service
(PS +
PS)

>Norm [0,+∞) Num Normal releases of combined BSC6900

al ber service(PS + PS). V900R014C00
Release (or later) or
s of BSC6910
Combin V100R014C00
ed (or later)
Service
(PS +
PS)

>Abnor [0,+∞) Num Abnormal releases of combined BSC6900

mal ber service(PS + PS). V900R014C00
Release (or later) or
s of BSC6910
Combin V100R014C00
ed (or later)
Service
(PS +
PS)

Statistic N/A N/A Statistics on voice quality in CS BSC6900

s of domain. V900R014C00
Voice (or later) or
Quality BSC6910
in CS V100R014C00
Domain (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 991

Param Range Unit Description Supported

eter NE Version

>One- [0,+∞) Num Number of times that one-way BSC6900

Way- ber audio occurs. V900R014C00
Audio (or later) or
Times BSC6910
V100R014C00
(or later)

>Noise [0,+∞) Num Number of times that noise occurs. BSC6900

Times ber V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

CS RAB Service Information

Param Range Unit Description Supported
eter NE Version

RAB N/A N/A RAB setup information. BSC6900

Setup RAB is radio access bearer for V900R014C00
Info short. (or later) or
BSC6910
V100R014C00
(or later)

>Multi ·1CS N/A Information about the setup of BSC6900

RAB ·1CS + 1PS combined RABs. V900R014C00
info (or later) or
·1CS + 2PS BSC6910
·1CS + 3PS V100R014C00
·2CS (or later)
·2CS + 1PS
·2CS + 2PS
·1PS
·2PS
·3PS
·4PS…

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 992

Param Range Unit Description Supported

eter NE Version

>RAB Traffic class: N/A RAB request service type consists BSC6900
Request ·conversational of two parts: Traffic class and V900R014C00
Service Traffic type. (or later) or
Type ·streaming BSC6910
The parameter value is displayed
·interactive in the format of Traffic class/ V100R014C00
·background … Traffic type. (or later)
Traffic type: For details about Traffic class, see
·CS_AMR 3GPP 25.413.
·CS_VP Traffic type is a service type
defined by Huawei in terms of
·CS_OTHER
radio access bearer (RAB).
·PS_GENERAL
·PS_HSDPA
·PS_HSUPA
·PS_HSPA ...

>RAB N/A N/A Time when RAB setup is BSC6900

Request requested. The statistical points V900R014C00
Time are as follows: (or later) or
·RAB setup: Timestamp in the BSC6910
RAB ASSIGNMENT REQUEST V100R014C00
message. (or later)

·Incoming migration: Timestamp

in the RELOCATION
COMPLETE message.
·Inter-RAT handover: Timestamp
in the HANDOVER TO UTRAN
COMPLETE message.

>Cell N/A N/A Cell on which RAB setup is BSC6900

on RAB requested. V900R014C00
Setup The parameter value is displayed (or later) or
Request in the following format: RNC BSC6910
name:cell name (cell ID). The V100R014C00
RNC name and cell name can be (or later)
obtained from configuration data.
If the RNC name and cell name
cannot be queried, they are not
displayed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 993

Param Range Unit Description Supported

eter NE Version

>RAB [0,+∞) Seco Time when RAB setup completes. BSC6900

Comple nd The statistical points are as V900R014C00
tion follows: (or later) or
Time ·RAB setup: Timestamp in the BSC6910
RAB ASSIGNMENT V100R014C00
RESPONSE message. (or later)

·Incoming migration: The time is

not recorded.
·Inter-RAT handover: The time is
not recorded.

>Best N/A N/A Best cell on which RAB setup BSC6900

Cell on completes. V900R014C00
RAB The parameter value is displayed (or later) or
Setup in the following format: RNC BSC6910
Comple name:cell name (cell ID). The V100R014C00
tion RNC name and cell name can be (or later)
obtained from configuration data.
If the RNC name and cell name
cannot be queried, they are not
displayed.

>Servin N/A N/A Service cell on which RAB setup BSC6900

g Cell completes. V900R014C00
on RAB The parameter value is displayed (or later) or
Setup in the following format: RNC BSC6910
Comple name:cell name (cell ID). The V100R014C00
tion RNC name and cell name can be (or later)
obtained from configuration data.
If the RNC name and cell name
cannot be queried, they are not
displayed.

>DRD N/A N/A Information about DRDs during BSC6900

Info RAB setup, recording the last three V900R014C00
DRDs at most. (or later) or
BSC6910
V100R014C00
(or later)

>DRD N/A N/A The N DRD record. BSC6900

Info:N V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 994

>RAB ·Successful N/A RAB setup results. BSC6900

Setup ·Failed V900R014C00
Result (or later) or
BSC6910
V100R014C00
(or later)

>RAB N/A N/A Time when RAB setup fails. BSC6900

Setup V900R014C00
Failure (or later) or
Time BSC6910
V100R014C00
(or later)

>RAB N/A N/A Cause of RAB setup failure. BSC6900

Setup V900R014C00
Failure (or later) or
Cause BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 997

Param Range Unit Description Supported

eter NE Version

>>Error For details, see N/A Error type. BSC6900

Type "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

>>Error For details, see N/A Error reason. BSC6900

Reason "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

>RAB N/A N/A Delay estimation on RRC setup. BSC6900

Setup V900R014C00
Delay (or later) or
Estimat BSC6910
ion V100R014C00
(or later)

>>RAB [0,+∞) Seco RAB setup delay = Time when BSC6900

Setup nd RAB setup completes - Time when V900R014C00
Delay RAB setup is requested. (or later) or
BSC6910
V100R014C00
(or later)

>>Over Yes N/A Overlong RAB setup delay occurs BSC6900

long No when the RAB setup delay exceeds V900R014C00
RAB the overlong delay threshold limit. (or later) or
Setup The overlong delay threshold is set BSC6910
Delay by engineers during analysis task V100R014C00
creation. (or later)

>>Call [0,+∞) Seco Call setup delay = Time when BSC6900

Setup nd RAB setup completes - Time when V900R014C00
Delay RRC setup is requested. (or later) or
Call setup delay = RAB setup BSC6910
delay + RRC setup delay. V100R014C00
(or later)
Note that this parameter is
applicable only to the first RAB
after RRC setup.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 998

>RAB N/A N/A Process information of RAB setup. BSC6900

Setup This parameter is used with RAB V900R014C00
Process Setup Failure Cause to analyze (or later) or
problems. BSC6910
V100R014C00
(or later)

>>Queu ·False N/A TRUE(1) indicates that queuing BSC6900

ing ·True occurs. V900R014C00
Indicato (or later) or
r BSC6910
V100R014C00
(or later)

>>Intra ·False N/A TRUE(1) indicates that intra- BSC6900

-system ·True system DRD occurs. V900R014C00
DRD (or later) or
Indicato BSC6910
r V100R014C00
(or later)

>>Inter ·False N/A TRUE(1) indicates that inter- BSC6900

-system ·True system DRD occurs. V900R014C00
DRD (or later) or
Indicato BSC6910
r V100R014C00
(or later)

>RAB N/A N/A Information about the latest radio BSC6900

Resourc resource congestion during RAB V900R014C00
e setup. This parameter is used with (or later) or
Congest RAB Setup Failure Cause to BSC6910
ion analyze problems. V100R014C00
Informa (or later)
tion on
RAB
Setup

>>Cong N/A N/A Time when radio resource BSC6900

estion congestion occurs. V900R014C00
Time (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1002

Param Range Unit Description Supported

eter NE Version

>>Cong N/A N/A Cell where radio resource BSC6900

estion congestion occurs. V900R014C00
Cell ID (or later) or
BSC6910
V100R014C00
(or later)

>>Cong ·Code N/A Cause of radio resource BSC6900

estion ·DL CE congestion. V900R014C00
Status (or later) or
·UL CE BSC6910
·UL DL CE V100R014C00
·DL IUB band (or later)
·UL IUB band
·UL DL IUB band
·UL power
·DL power
·UL DL power
·HSDPA user
number
·HSUPA user
number
·HSPA user
number

RAB N/A N/A Information about RAB release. BSC6900

Release V900R014C00
Info (or later) or
BSC6910
V100R014C00
(or later)

>Multi ·1CS N/A Information about the release of BSC6900

RAB ·1CS + 1PS combined RABs. V900R014C00
info (or later) or
·1CS + 2PS BSC6910
·1CS + 3PS V100R014C00
·2CS (or later)
·2CS + 1PS
·2CS + 2PS
·1PS
·2PS
·3PS
·4PS…

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1003

Param Range Unit Description Supported

eter NE Version

>Single ·False N/A TRUE(1) indicates single-RAB BSC6900

-RAB ·True abnormal release. V900R014C00
Abnor (or later) or
mal BSC6910
Release V100R014C00
Indicato (or later)
r

>Multip ·False N/A TRUE(1) indicates multiple-RAB BSC6900

le-RAB ·True abnormal release. V900R014C00
Abnor (or later) or
mal BSC6910
Release V100R014C00
Indicato (or later)
r

>RAB N/A N/A Time when RAB release BSC6900

Release completes. The statistical points
V900R014C00
Time are as follows: (or later) or
·Normal release and CN abnormal BSC6910
release: RAB release time = V100R014C00
Timestamp in the IU RELEASE (or later)
COMMAND or RAB
ASSIGNMENT REQUEST
message.

>RAB [0,+∞) Seco ·RAB duration = RAB release time BSC6900

Duratio nd - RAB setup time. V900R014C00
n (or later) or
BSC6910
V100R014C00
(or later)

>RAB ·Yes N/A If "RAB Duration" is smaller than BSC6900

Duratio ·No "RAB Duration shorter threshold", V900R014C00
n it indicators that the RAB duration (or later) or
Shorter is too shorter. BSC6910
Abnormal threshold is set when V100R014C00
creating tasks. (or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1004

Param Range Unit Description Supported

eter NE Version

>Best N/A N/A Best cell before RAB release. BSC6900

Cell The parameter value is displayed V900R014C00
Before in the following format: RNC (or later) or
RAB name:cell name (cell ID). The BSC6910
Release RNC name and cell name can be V100R014C00
obtained from configuration data. (or later)
If the RNC name and cell name
cannot be queried, they are not
displayed.

>Servin N/A N/A Serving cell before RAB release. BSC6900

g Cell The parameter value is displayed V900R014C00
Before in the following format: RNC (or later) or
RAB name:cell name (cell ID). The BSC6910
Release RNC name and cell name can be V100R014C00
obtained from configuration data. (or later)
If the RNC name and cell name
cannot be queried, they are not
displayed.

>UL/ DL transport N/A Type of an uplink or downlink data BSC6900

DL channel type: transmission channel before RAB V900R014C00
Channe ·DCH release. The channel types are (or later) or
l Types defined by Huawei. BSC6910
·FACH V100R014C00
·RACH (or later)
·HSDSCH
·EDCH
·PCH
·EFACH
·ERACH
·EPCH
UL transport
channel type:
·DCH
·FACH
·RACH
·HSDSCH
·EDCH
·PCH
·EFACH
·ERACH
·EPCH

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1005

Param Range Unit Description Supported

eter NE Version

>UL/ [0,+∞) kbit/s Uplink and downlink RB rate after BSC6900

DL RB RAB setup and before RAB V900R014C00
Rate release. The parameter value is (or later) or
displayed in the format of UL RB BSC6910
bitrate after RAB setup/DL RB V100R014C00
bitrate after RAB setup. (or later)
In which,
·When UL is carried on RACH,
UL RB bitrate after RAB setup =
8000 bit/s.
·When UL is carried on PCH, UL
RB bitrate after RAB setup = 0 bit/
s.
·When UL is carried on the other
channels, UL RB bitrate after RAB
setup varies according to site
conditions.
·When DL is carried on FACH, DL
RB bitrate after RAB setup = 8000
bit/s.
·When DL is carried on PCH, DL
RB bitrate after RAB setup = 0 bit/
s.
·When DL is carried on the other
channels, DL RB bitrate after RAB
setup varies according to site
conditions.

>Disco N/A N/A Cause carried in the BSC6900

nnect DISCONNECT message. For V900R014C00
Cause details, see 3GPP (or later) or
24.008-10.5.4.11. BSC6910
V100R014C00
(or later)

>Disco ·from UE N/A Direction for sending the BSC6900

nnect ·from CN DISCONNECT message. V900R014C00
Directio (or later) or
n BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1006

Param Range Unit Description Supported

eter NE Version

>RAB N/A N/A Cause of abnormal RAB release. BSC6900

Release V900R014C00
Failure (or later) or
Cause BSC6910
V100R014C00
(or later)

>>Error For details, see N/A Error type. BSC6900

Type "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

>>Error For details, see N/A Error reason. BSC6900

Reason "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

>RAB N/A N/A Time when RAB release fails. BSC6900

Release That is, when the system receives V900R014C00
Failure the following timestamp: (or later) or
Time ·IU RELEASE REQUEST BSC6910
V100R014C00
·RAB RELEASE REQUEST (or later)

RAB N/A N/A RAB process information. BSC6900

Process V900R014C00
Info (or later) or
BSC6910
V100R014C00
(or later)

>RAB N/A N/A Delay estimation on RAB setup. BSC6900

Setup V900R014C00
Delay (or later) or
Estimat BSC6910
ion V100R014C00
(or later)

>>Disc N/A N/A Time when a call completes. BSC6900

onnect Statistical point: timestamp in the V900R014C00
time DISCONNECT message. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1007

Param Range Unit Description Supported

eter NE Version

>>Servi [0,+∞) Seco Service duration = Disconnect BSC6900

ce nd time - Connect Ack time. V900R014C00
Duratio (or later) or
n BSC6910
V100R014C00
(or later)

>>Short ·N/A N/A 1.The parameter value is Yes in the BSC6900

Call ·Yes following conditions: V900R014C00
·When the current RAB is not the (or later) or
·No BSC6910
first RAB after RRC setup and Call
duration < Short call threshold. V100R014C00
(or later)
·The current RAB is the first RAB
after RRC setup.
RRC Setup Flag(MOC/MTC) is
MOC.
Call duration < Short call threshold
(MOC).
·The current RAB is the first RAB
after RRC setup.
RRC Setup Flag(MOC/MTC) is
MTC.
Call duration < Short call threshold
(MTC).
2.The parameter value is No in the
other conditions.
The short call threshold, short call
threshold (MOC), and short call
threshold (MTC) are set by
engineers during task creation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1008

Param Range Unit Description Supported

eter NE Version

>SQI N/A N/A Statistics on SQIs BSC6900

Statistic 1. Signal quality indicator (SQI) V900R014C00
s indicates signal quality on the (or later) or
uplink to show voice quality BSC6910
during a call. The SQI statistics are V100R014C00
collected by the RNC. When the (or later)
statistical period is less than 9.6
seconds, the value of SQI is 0. The
value range is [0,500]. A larger
value indicates better signal
quality.
2. The RNC can statistics based on
the average SQI value and divides
signal quality into different levels
according to SQI values:
·RAN14.0: Excellent (SQI<=
(400,500]), Good (SQI<=
(300,400]), Accept (SQI<=
(200,300]), Poor (SQI<=
(100,200]), Bad (SQI<=[0,100]).
·RAN13.0 and earlier: Good (SQI
<= (300,500]), Accept (SQI <=
(200,300]), Bad (SQI <=(0,200]).
The segment intervals of levels can
be modified by running the SET
USQICOUNT command on the
RNC.

>>Aver [0,500] N/A Average SQI value during a call. BSC6900

age SQI V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>>Abn ·Yes N/A If SQI average < Abnormal SQI BSC6900

ormal ·No threshold, V900R014C00
SQI The value of this parameter is Yes. (or later) or
Otherwise, the value is No. BSC6910
V100R014C00
The abnormal SQI threshold is set (or later)
by engineers during task creation.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1009

Param Range Unit Description Supported

>>Occu N/A N/A Cell when uplink one-way audio BSC6900

rrence occurs. V900R014C00
Cell (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1012

Param Range Unit Description Supported

eter NE Version

>DL N/A N/A Statistics on downlink one-way BSC6900

Silence audio. The downlink one-way V900R014C00
Statistic audio problems fall into two types: (or later) or
Info 1. The RNC records a downlink BSC6910
one-way audio problem when it V100R014C00
detects any error packet or a large (or later)
packet loss rate at the downlink
IUUP layer. The RNC records a
maximum of the first two
downlink one-way audio problems
during each call of a UE.
2. The RNC records a downlink
one-way audio problem when it
detects a large BLER value. This
function is available only when a
VIP subscriber enables periodic
DL BLER reporting. The RNC
records a maximum of the first
three downlink one-way audio
problems during each call of a UE.

>>Occu N/A N/A Time when a downlink one-way BSC6900

rrence audio problem occurs. V900R014C00
Time (or later) or
BSC6910
V100R014C00
(or later)

>>Occu N/A N/A Cell when a downlink one-way BSC6900

rrence audio problem occurs. V900R014C00
Cell (or later) or
BSC6910
V100R014C00
(or later)

>>Nois N/A N/A Statistics on noises. BSC6900

e 1. The RNC records a noise V900R014C00
Statistic problem. (or later) or
s BSC6910
2. The RNC records only the first V100R014C00
one noise problem during each call (or later)
of a UE.

>>Occu N/A N/A Time when a noise problem BSC6900

rrence occurs. V900R014C00
Time (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1013

Param Range Unit Description Supported

eter NE Version

>>Occu N/A N/A Cell when a noise problem occurs. BSC6900

rrence V900R014C00
Cell (or later) or
BSC6910
V100R014C00
(or later)

PS RAB Service Information

Param Range Unit Description Supported
eter NE Version

RAB N/A N/A RAB setup information. BSC6900

Setup RAB is radio access bearer for V900R014C00
Info short. (or later) or
BSC6910
V100R014C00
(or later)

>Multi ·1CS N/A Information about the setup of BSC6900

RAB ·1CS + 1PS combined RABs. V900R014C00
info (or later) or
·1CS + 2PS BSC6910
·1CS + 3PS V100R014C00
·2CS (or later)
·2CS + 1PS
·2CS + 2PS
·1PS
·2PS
·3PS
·4PS…

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1014

Param Range Unit Description Supported

eter NE Version

>RAB Traffic class: N/A There are two RAB request BSC6900
Request ·conversational service types: Traffic class and V900R014C00
Service Traffic type. (or later) or
Type ·streaming BSC6910
The parameter value is displayed
·interactive in the format of Traffic class/ V100R014C00
·background … Traffic type. (or later)
Traffic type: For details about Traffic class, see
·CS_AMR 3GPP 25.413.
·CS_VP Traffic type is a service type
defined by Huawei in terms of
·CS_OTHER
radio access bearer (RAB).
·PS_GENERAL
·PS_HSDPA
·PS_HSUPA
·PS_HSPA ...

>RAB N/A N/A Time for requesting RAB setup. BSC6900

Request The statistical points are as V900R014C00
Time follows: (or later) or
·RAB setup: Timestamp in the BSC6910
RAB ASSIGNMENT REQUEST V100R014C00
message. (or later)

·Incoming migration: Timestamp

in the RELOCATION
COMPLETE message.
·Inter-RAT handover: Timestamp
in the HANDOVER TO UTRAN
COMPLETE message.

>Cell N/A N/A Cell on which RAB setup is BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1015

Param Range Unit Description Supported

eter NE Version

>RAB [0,+∞) Seco Time when RAB setup completes. BSC6900

Comple nd The statistical points are as V900R014C00
tion follows: (or later) or
Time ·RAB setup: Timestamp in the BSC6910
RAB ASSIGNMENT V100R014C00
RESPONSE message. (or later)

·Incoming migration: The time is

not recorded.
·Inter-RAT handover: The time is
not recorded.

>Cell N/A N/A Best cell on which RAB setup BSC6900

on RAB completes. V900R014C00
Setup The parameter value is displayed (or later) or
Comple in the following format: RNC BSC6910
tion name:cell name (cell ID). The V100R014C00
RNC name and cell name can be (or later)
obtained from configuration data.
If the RNC name and cell name
cannot be queried, they are not
displayed.

Serving N/A N/A Serving cell on which RAB setup BSC6900

Cel on completes. V900R014C00
RAB The parameter value is displayed (or later) or
Setup in the following format: RNC BSC6910
Comple name:cell name (cell ID). The V100R014C00
tion RNC name and cell name can be (or later)
obtained from configuration data.
If the RNC name and cell name
cannot be queried, they are not
displayed.

>DRD N/A N/A Information about DRDs during BSC6900

Info RAB setup, recording the last V900R014C00
three DRDs at most. (or later) or
BSC6910
V100R014C00
(or later)

>DRD N/A N/A The N DRD record. BSC6900

Info:N V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1016

Param Range Unit Description Supported

eter NE Version

>>>DR N/A N/A Target cell of the current DRD. BSC6900

>>>DR ·CS_AMR N/A Traffic type when the current BSC6900

D ·CS_VP DRD occurs. V900R014C00
traffic (or later) or
type ·CS_OTHER BSC6910
·PS_GENERAL V100R014C00
·PS_HSDPA (or later)
·PS_HSUPA
·PS_HSPA ...

>>>DR N/A N/A DRD failure cause. BSC6900

D For details, see the Failure Cause V900R014C00
Failure tab page. (or later) or
Cause BSC6910
V100R014C00
(or later)

>>>>Er For details, see N/A Error type. BSC6900

ror "Appendix: V900R014C00
Type Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)"

>>>>Er For details, see N/A Error reason. BSC6900

ror "Appendix: V900R014C00
Reason Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1017

Param Range Unit Description Supported

eter NE Version

>UL/ DL transport N/A Type of an uplink or downlink BSC6900

DL channel type: data transmission channel after V900R014C00
Channe ·DCH RAB setup. The channel types are (or later) or
l Types defined by Huawei. BSC6910
After ·FACH V100R014C00
RAB ·RACH (or later)
Setup ·HSDSCH
·EDCH
·PCH
·EFACH
·ERACH
·EPCH
UL transport
channel type:
·DCH
·FACH
·RACH
·HSDSCH
·EDCH
·PCH
·EFACH
·ERACH
·EPCH

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1018

Param Range Unit Description Supported

eter NE Version

>UL/ [0,+∞) bps DL/UL RB rate after RAB setup. BSC6900

DL RB The parameter value is displayed V900R014C00
Rate in the format of UL RB bitrate (or later) or
after RAB setup/DL RB bitrate BSC6910
after RAB setup. V100R014C00
(or later)
In which,
·If UL is carried on RACH, UL RB
bitrate after RAB setup = 8000 bit/
s.
·If UL is carried on PCH, UL RB
bitrate after RAB setup = 0 bit/s.
·When UL is carried on the other
channels, UL RB bitrate after
RAB setup varies according to site
conditions.
·When DL is carried on FACH,
DL RB bitrate after RAB setup =
8000 bit/s.
·When DL is carried on PCH, DL
RB bitrate after RAB setup = 0 bit/
s.
·When DL is carried on the other
channels, DL RB bitrate after
RAB setup varies according to site
conditions.

>UL/ [0,+∞) bps UL/DL RAB negotiated rate. BSC6900

DL V900R014C00
RAB (or later) or
Negotia BSC6910
ted Rate V100R014C00
(or later)

Overlo ·Yes N/A If "Overlow UL RAB Negotiated BSC6900

w UL ·No Rate" is smaller than "Overlow V900R014C00
RAB UL RAB Negotiated Rate (or later) or
Negotia Threshold", the record has the BSC6910
ted Rate problem that the overlow UL RAB V100R014C00
vegotiated rate is too small. (or later)
The abnormal threshold is set
when creating tasks.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1019

Param Range Unit Description Supported

eter NE Version

Overlo ·Yes N/A If "Overlow DL RAB Negotiated BSC6900

w DL ·No Rate" is smaller than "Overlow V900R014C00
RAB DL RAB Negotiated Rate (or later) or
Negotia Threshold", the record has the BSC6910
ted Rate problem that the overlow DL RAB V100R014C00
vegotiated rate is too small. (or later)
The abnormal threshold is set
when creating tasks.

>RAB ·Successful N/A Results of RRC setup. BSC6900

Setup ·Failed V900R014C00
Result (or later) or
BSC6910
V100R014C00
(or later)

>RAB N/A N/A Time when RAB setup fails. BSC6900

Setup V900R014C00
Failure (or later) or
Time BSC6910
V100R014C00
(or later)

>RAB N/A N/A Cause of RAB setup failure. BSC6900

Setup V900R014C00
Failure (or later) or
Cause BSC6910
V100R014C00
(or later)

>>Error For details, see N/A Error type. BSC6900

Type "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

>>Error For details, see N/A Error reason. BSC6900

Reason "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1020

Param Range Unit Description Supported

eter NE Version

>RAB N/A N/A Delay estimation on RAB setup. BSC6900

Setup V900R014C00
Delay (or later) or
Estimat BSC6910
ion V100R014C00
(or later)

>>RAB [0,+∞) Seco RAB setup delay = Time when BSC6900

Setup nd RAB setup completes - Time V900R014C00
Delay when RAB setup is requested. (or later) or
BSC6910
V100R014C00
(or later)

>>Over Yes N/A Overlong RAB setup delay occurs BSC6900

long No when the RAB setup delay V900R014C00
RAB exceeds the overlong delay (or later) or
Setup threshold limit. BSC6910
Delay The overlong delay threshold is V100R014C00
set by engineers during analysis (or later)
task creation.

>>Call [0,+∞) Seco 1.When the following scene BSC6900

Connec nd occurs, it displays "N/A". V900R014C00
tion ·Scene: the first RAB after the (or later) or
Delay RAB (Non-RRC) setup. BSC6910
V100R014C00
2.When the following scene (or later)
occurs, it displays the result value.
·Scene: the first RAB after the
RAB (RRC) setup.
Call connection delay = Time
when RAB setup completes -
Time when RRC setup is
requested.
Call connection delay = RAB
setup delay + RRC setup delay.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1021

Param Range Unit Description Supported

eter NE Version

>>Over ·Yes N/A 1.When the following scene BSC6900

long ·No occurs, it displays "N/A". V900R014C00
Call ·Scene: the first RAB after the (or later) or
Connec RAB (Non-RRC) setup. BSC6910
tion V100R014C00
Delay 2.When the following scenes (or later)
occur, it displays the result value.
·Scene: the first RAB after the
RAB (RRC) setup; and "RRC
Setup Flag(MOC/MTC)" is
"MOC"; and "Call Setup Delay" is
larger than "Latency on Call
Connection (MOC) ".
·Scene: the first RAB after the
RAB (RRC) setup; and "RRC
Setup Flag(MOC/MTC)" is
"MTC"; and "Call Setup Delay" is
smaller than "Latency on Call
Connection (MTC) ".
3.When the other scene occurs, it
displays "No".
The threshold is set by engineers
during analysis task creation.

>>CM N/A N/A Service request time, that is, the BSC6900
Service timestamp of "CM Service V900R014C00
Request Request" message. (or later) or
Time BSC6910
V100R014C00
(or later)

>>Uu [0,+∞) Seco Uu delay. The statistical points are BSC6900

delay nd as follows: V900R014C00
(ms) ·RB setup: Timestamp in the (or later) or
RADIO BEARER SETUP BSC6910
COMPLETE message - V100R014C00
Timestamp in the RADIO (or later)
BEARER SETUP message.
·RB reconfiguration: Timestamp
in the RADIO BEARER
RECONFIGURATION
COMPLETE message -
Timestamp in the RADIO
BEARER
RECONFIGURATION message.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1022

Param Range Unit Description Supported

eter NE Version

>Sched N/A N/A Scheduling priority during RAB BSC6900

uling setup. V900R014C00
Priority (or later) or
BSC6910
V100R014C00
(or later)

>>Allo N/A N/A Allocation/retention priority. For BSC6900

cation/ details, see 3GPP 25.413-9.2.1.3. V900R014C00
Retenti (or later) or
on BSC6910
Priority V100R014C00
(or later)

>>>Pri [0,15] N/A Priority level in the allocation and BSC6900

ority retention of RABs. V900R014C00
Level The value range is [0,15]. A larger (or later) or
value indicates lower priority. BSC6910
V100R014C00
·0: Spare, which indicates that a (or later)
logical error occurs.
·1: Highest, which indicates the
highest priority.
·14: Lowest, which indicates the
lowest priority.
·15: No Priority: which indicates
no priority.

>>>Pre ·Shall not trigger N/A Whether the current RAB can BSC6900
- pre-emption preempt resources of other RABs. V900R014C00
emptio ·May trigger pre- (or later) or
n emption BSC6910
Capabil V100R014C00
ity (or later)

>>>Pre ·Not pre-emptable N/A Whether resources of the current BSC6900

- ·Pre-emptable RAB can be preempted by other V900R014C00
emptio RABs. (or later) or
n BSC6910
Vulnera V100R014C00
bility (or later)

>>>Qu ·Queuing not N/A Whether the current RAB can be BSC6900
euing allowed queued for resource scheduling. V900R014C00
Allowe ·Queuing allowed (or later) or
d BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1023

Param Range Unit Description Supported

eter NE Version

>>Traff [0,15] N/A Priority level in the allocation and BSC6900

ic retention of system resources. For V900R014C00
Handlin details, see 3GPP (or later) or
g 25.433-9.2.1.1A. BSC6910
Priority The value range is [0,15]. A larger V100R014C00
value indicates lower priority. (or later)

·0: Spare, which indicates that a

logical error occurs.
·1: Highest, which indicates the
highest priority.
·14: Lowest, which indicates the
lowest priority.
·15: No Priority: which indicates
no priority.

>>Sche [0,15] N/A HS-DSCH scheduling priority. BSC6900

duling For details, see 3GPP V900R014C00
Priority 25.433-9.2.1.53H. (or later) or
Indicato The value range is [0,15]. A larger BSC6910
r value indicates higher priority. V100R014C00
(or later)

RAB N/A N/A Information about RAB release. BSC6900

Release V900R014C00
Info (or later) or
BSC6910
V100R014C00
(or later)

>Multi ·1CS N/A Information about the release of BSC6900

RAB ·1CS + 1PS combined RABs. V900R014C00
info (or later) or
·1CS + 2PS BSC6910
·1CS + 3PS V100R014C00
·2CS (or later)
·2CS + 1PS
·2CS + 2PS
·1PS
·2PS
·3PS
·4PS…

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1024

Param Range Unit Description Supported

eter NE Version

>Single ·False N/A TRUE(1) indicates single-RAB BSC6900

-RAB ·True abnormal release. V900R014C00
Abnor (or later) or
mal BSC6910
Release V100R014C00
Indicato (or later)
r

>Multi ·False N/A TRUE(1) indicates multiple-RAB BSC6900

ple- ·True abnormal release. V900R014C00
RAB (or later) or
Abnor BSC6910
mal V100R014C00
Release (or later)
Indicato
r

>RAB N/A N/A Time when RAB release BSC6900

Release completes. The statistical points V900R014C00
Time are as follows: (or later) or
·Normal release and CN abnormal BSC6910
release: RAB release time = V100R014C00
Timestamp in the IU RELEASE (or later)
COMMAND or RAB
ASSIGNMENT REQUEST
message.

>RAB [0,+∞) s ·RAB duration = RAB release BSC6900

Duratio time - RAB setup time. V900R014C00
n (or later) or
BSC6910
V100R014C00
(or later)

>Best N/A N/A Best cell before RAB release. BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1025

Param Range Unit Description Supported

eter NE Version

>Servin N/A N/A Serving cell before RAB release. BSC6900

>UL/ UL transport N/A Type of an uplink or downlink BSC6900

DL channel type: data transmission channel before V900R014C00
Channe ·DCH RAB release. The channel types (or later) or
l Types are defined by Huawei. BSC6910
·FACH V100R014C00
·RACH (or later)
·HSDSCH
·EDCH
·PCH
·EFACH
·ERACH
·EPCH
DL transport
channel type:
·DCH
·FACH
·RACH
·HSDSCH
·EDCH
·PCH
·EFACH
·ERACH
·EPCH

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1026

Param Range Unit Description Supported

eter NE Version

>UL/ [0,+∞) kbit/s UL/DL RB rate after RAB setup BSC6900

DL RB and before RAB release. V900R014C00
Rate The parameter value is displayed (or later) or
in the format of UL RB bitrate BSC6910
after RAB setup/DL RB bitrate V100R014C00
after RAB setup. (or later)

In which,
·If UL is carried on RACH, UL RB
bitrate after RAB setup = 8000 bit/
s.
·If UL is carried on PCH, UL RB
bitrate after RAB setup = 0 bit/s.
·When UL is carried on the other
channels, UL RB bitrate after
RAB setup varies according to site
conditions.
·When DL is carried on FACH,
DL RB bitrate after RAB setup =
8000 bit/s.
·When DL is carried on PCH, DL
RB bitrate after RAB setup = 0 bit/
s.
·When DL is carried on the other
channels, DL RB bitrate after
RAB setup varies according to site
conditions.

>DP N/A N/A Cause carried by the Deactivate BSC6900

Deactiv PDP context request message. For V900R014C00
ate details, see 3GPP 24.008-10.5.6.6 (or later) or
Cause SM cause. BSC6910
V100R014C00
(or later)

>RAB N/A N/A Cause of abnormal RAB release. BSC6900

Release V900R014C00
Failure (or later) or
Cause BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1027

Param Range Unit Description Supported

eter NE Version

>>Error For details, see N/A Error type. BSC6900

Type "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

>>Error For details, see N/A Error reason. BSC6900

Reason "Appendix: V900R014C00
Exception Cause (or later) or
Classification / BSC6910
Enumeration V100R014C00
Values of Failure (or later)
Cause (UMTS)".

>RAB N/A N/A Time when RAB release fails. BSC6900

Release That is, when the system receives V900R014C00
Failure the following timestamp: (or later) or
Time ·IU RELEASE REQUEST BSC6910
V100R014C00
·RAB RELEASE REQUEST (or later)

RAB N/A N/A RAB process information. BSC6900

Process V900R014C00
Info (or later) or
BSC6910
V100R014C00
(or later)

>PDP N/A N/A Timestamp in the PDP BSC6900

Activat ACTIVIATE REQUEST V900R014C00
e message. (or later) or
Request BSC6910
Time V100R014C00
(or later)

>PDP N/A N/A Timestamp in the PDP BSC6900

Activat ACTIVIATE ACKNOWLEDGE V900R014C00
e Ack message. (or later) or
Time BSC6910
V100R014C00
(or later)

>PDP N/A N/A Timestamp in the DEACTIVATE BSC6900

Deactiv PDP CONTEXT REQUEST V900R014C00
ate message. (or later) or
Time BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1028

Param Range Unit Description Supported

eter NE Version

>BLER N/A N/A Statistical information about BSC6900

Statistic BLERs. V900R014C00
Info 1. Block error rate (BLER) (or later) or
indicates signal quality on the BSC6910
uplink during a call. The BLER V100R014C00
statistics are collected by the (or later)
RNC. The value range is
[0.00,100.00]. A larger value
indicates worse signal quality.
2. The CS services are divided into
six levels in terms of BLER. The
segment intervals of these levels
are:
0-0.78%, 0.78%-1.56%,
1.56%-3.12%, 3.12%-6.24%,
6.24%-12.48%, above 12.48%.

>>Time [0,+∞) Num N/A BSC6900

s UL ber V900R014C00
Service (or later) or
BLER BSC6910
Falls V100R014C00
into (or later)
Levels
1 to 6

>Statist N/A N/A Statistics on received blocks BSC6900

ics on before link release. V900R014C00
Last The statistical period is 2.56 (or later) or
Receive seconds. BSC6910
d V100R014C00
Blocks (or later)

>>Num [0,+∞) Num Total number of UL blocks BSC6900

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1029

Param Range Unit Description Supported

eter NE Version

>>Num [0,+∞) Num Number of UL error blocks BSC6900

Signaling Procedure Before Call Release

Param Range Unit Description Supported
eter NE Version

Numbe [1,+∞) N/A Number that uniquely identifies a BSC6900

r sent and received signaling V900R014C00
message. (or later) or
BSC6910
V100R014C00
(or later)

Signali N/A N/A Time when a signaling message is BSC6900

ng sent or received. V900R014C00
Time (or later) or
BSC6910
V100R014C00
(or later)

Signali ·to CN N/A Direction for sending or receiving BSC6900

ng ·from CN a signaling message. V900R014C00
Direct (or later) or
·to other RNC BSC6910
·from other RNC V100R014C00
·to NODEB (or later)
·from NODEB
·to UE
·from UE
·to SAS
·from SAS

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1030

Param Range Unit Description Supported

eter NE Version

Signali N/A N/A Type of a signaling message that BSC6900

ng Type complies with any protocol and is V900R014C00
transmitted over the Iu, Iur, Iub, or (or later) or
Uu interface. BSC6910
For example, RRC CONNECT V100R014C00
REQUEST is a signaling type. (or later)

Signali N/A N/A Content of a signaling message. BSC6900

ng The content is displayed in a tree V900R014C00
Content structure. (or later) or
BSC6910
V100R014C00
(or later)

Measurement Information
Param Range Unit Description Supported
eter NE Version

Number [1,+∞) N/A Number that uniquely identifies a BSC6900

measurement report (MR). V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Measur N/A N/A Time when an MR is reported. BSC6900

ement V900R014C00
Time (or later) or
BSC6910
V100R014C00
(or later)

MR ·Intra-freq N/A MR type. BSC6900

Type measurement V900R014C00
type (or later) or
·Inter-freq BSC6910
measurement V100R014C00
type (or later)

·Inter-RAT
measurement
type
·Event MR, such
as E1A and so on

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1031

Param Range Unit Description Supported

eter NE Version

Measur ·Best cell N/A Type of a measurement object BSC6900

ement ·Active set cell reported in an MR. V900R014C00
Object (or later) or
Type ·Monitor set cell BSC6910
V100R014C00
(or later)

Measur N/A N/A Name of a measurement object BSC6900

ement reported in an MR. V900R014C00
Object The parameter value is displayed (or later) or
in the following format: RNC BSC6910
name:cell name (cell ID). V100R014C00
(or later)
The NE name can be obtained
from configuration data based on
the cell ID in the MR . If the NE
name cannot be queried, the cell
ID in the MR is displayed.

P-SC [0,512] N/A Scrambling code in an MR. BSC6900

V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Ec/NO [-24,0] dB Ratio of energy per modulating bit BSC6900

(dB) to the noise spectral density (Ec/ V900R014C00
No). For details, see 3GPP 25.331. (or later) or
BSC6910
V100R014C00
(or later)

RSCP [-116,-25] dBm Received signal code power BSC6900

(RSCP). For details, see 3GPP V900R014C00
25.331. (or later) or
In the complaint analysis support BSC6910
theme, the first result in the V100R014C00
measurement report information (or later)
area before the call release is the
measurement results upon call
setup rather than the MR results.
Therefore, either RSCP or EcNo is
displayed according to the
protocol requirements.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1032

Param Range Unit Description Supported

eter NE Version

Inter- N/A dBm Received signal strength indicator BSC6900

RAT (RSSI) of a GSM carrier. For V900R014C00
Carrier details, see 3GPP TS 45.008. (or later) or
RSSI BSC6910
(dBm) V100R014C00
(or later)

RSRP [0,97] dBm Reference signal received power BSC6900

(RSRP). For details, see 3GPP V900R014C00
36.133. (or later) or
BSC6910
V100R014C00
(or later)

RSRQ [0,33] dB Reference signal received quality BSC6900

(RSRQ). For details, see 3GPP V900R014C00
36.133. (or later) or
BSC6910
V100R014C00
(or later)

UE TX N/A N/A Transmit power of a UE. BSC6900

Power V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Mobility Analysis
Param Range Unit Description Supported
eter NE Version

Number [1,+∞) N/A Number of a handover during a BSC6900

call. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Abnorm ·! N/A Whether a handover is abnormal. BSC6900

al ·Blank If a red exclamation mark is V900R014C00
displayed in this column, the (or later) or
handover is abnormal. BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1033

Param Range Unit Description Supported

eter NE Version

Type ·Softer N/A Type of mobility analysis. BSC6900

handover Currently, the system supports the V900R014C00
·Soft handover following mobility analysis types: (or later) or
·Soft handover BSC6910
·Intra-freq hard V100R014C00
handover ·Hard handover (or later)
·Inter-freq hard ·Incoming inter-RAT handover
handover ·Outgoing inter-RAT handover
·Inter-system ·Incoming migration
incoming
handover ·Outgoing migration

·Inter-system ·Cell update

outgoing ·Channel handover
handover/CS
system
handover
·Inter-system
outgoing
handover/Cell
change order PS
system
handover
·Inter-system
outgoing
handover/
Enhanced PS
system
handover
·Inter-system
outgoing
handover/CS
and PS system
handover
·Inter-system
outgoing
handover/UE
generated
·Incoming
migration/
Static reloc in
·Incoming
migration/HHO
reloc in

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1034

Measur ·Active Set N/A Measurement type. BSC6900

e Type V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Source N/A N/A The parameter value is displayed in BSC6900

Cell the following format: cell name V900R014C00
(cell ID).The NE name can be (or later) or
obtained from configuration data BSC6910
based on the cell ID in the MR . If V100R014C00
the NE name cannot be queried, the (or later)
cell ID in the MR is displayed.

Source [-24,0] dB Ratio of energy per modulating bit BSC6900

Ec/NO to the noise spectral density (Ec/ V900R014C00
(dB) No). For details, see 3GPP 25.331. (or later) or
BSC6910
V100R014C00
(or later)

Source [-116,-25] dBm Received signal code power BSC6900

RSCP (RSCP). For details, see 3GPP V900R014C00
(dBm) 25.331. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1037

Param Range Unit Description Supported

eter NE Version

UL RB [0,+∞) kbit/s UL RB rate when occuring the BSC6900

Rate channel handover. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

DL RB [0,+∞) bps DL RB rate when occuring the BSC6900

Rate channel handover. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Target N/A N/A Indicates the RAT of the target BSC6900

System network after an outgoing or V900R014C00
incoming inter-RAT handover. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1038

Param Range Unit Description Supported

eter NE Version

Target N/A N/A Name of target cell. The parameter BSC6900

Cell value is displayed in the following V900R014C00
format: RNC name:cell name (cell (or later) or
ID).The NE name can be obtained BSC6910
from configuration data based on V100R014C00
the cell ID in the MR . If the NE (or later)
name cannot be queried, the cell ID
in the MR is displayed.

Target [-24,0] dB Ratio of energy per modulating bit BSC6900

Ec/NO to the noise spectral density (Ec/ V900R014C00
(dB) No) of 3G target cell. For details, (or later) or
see 3GPP 25.331. BSC6910
V100R014C00
(or later)

Target [-116,-25] dBm Received signal code power BSC6900

RSCP (RSCP) of 3G target cell. For V900R014C00
(dBm) details, see 3GPP 25.331. (or later) or
BSC6910
V100R014C00
(or later)

Target ·RL ADD N/A Target cell operation of the 3G BSC6900

Target ·RL DEL target cell when occuring the soft V900R014C00
Cell handover. (or later) or
Operati BSC6910
on V100R014C00
(or later)

Target N/A N/A Target cell operation time of the BSC6900

Target 3G target cell when occuring the V900R014C00
Cell soft handover. (or later) or
Operati BSC6910
on Time V100R014C00
(or later)

Inter- N/A dBm Received signal strength indicator BSC6900

RAT (RSSI) of a GSM carrier of 2G V900R014C00
carrier target cell. For details, see 3GPP (or later) or
RSSI TS 45.008. BSC6910
(dBm) V100R014C00
(or later)

RSRP [-140,-43] dBm Reference signal received power BSC6900

(RSRP) of LTE target cell. For V900R014C00
details, see 3GPP 36.133. (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1039

Param Range Unit Description Supported

eter NE Version

RSRQ [-19.5,-2.5] dB Reference signal received quality BSC6900

(RSRQ) of LTE target cell. For V900R014C00
details, see 3GPP 36.133. (or later) or
BSC6910
V100R014C00
(or later)

UL RB [0,+∞) bps UL RB rate when occuring the BSC6900

Rate channel handover. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

DL RB [0,+∞) bps DL RB rate when occuring the BSC6900

Rate channel handover. V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1040

Param Range Unit Description Supported

eter NE Version

Fail N/A N/A Failure cause. BSC6900

Cause V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

>Error For details, see N/A Error type. BSC6900

Type "Appendix: V900R014C00
Exception (or later) or
Cause BSC6910
Classification / V100R014C00
Enumeration (or later)
Values of
Failure Cause
(UMTS)".

>Error For details, see N/A Error reason. BSC6900

Reason "Appendix: V900R014C00
Exception (or later) or
Cause BSC6910
Classification / V100R014C00
Enumeration (or later)
Values of
Failure Cause
(UMTS)".

Service Analysis(RAB)
Param Range Unit Description Supported NE
eter Version

Numbe [1,+∞) N/A Record number of RAB service. BSC6900

r V900R014C00
(or later) or
BSC6910
V100R014C00
(or later)

Abnor ·! N/A Whether a servive record is BSC6900

mal ·Blank abnormal. V900R014C00
If a red exclamation mark is (or later) or
displayed in this column, the record BSC6910
is abnormal. V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1041

Param Range Unit Description Supported NE

eter Version

RAB ·! N/A Whether a servive record of RAB BSC6900

Setup ·Blank setup is abnormal. V900R014C00
Abnor If a red exclamation mark is (or later) or
mal displayed in this column, the record BSC6910
is abnormal. V100R014C00
(or later)

RAB For details, see N/A Cause when RAB setup fails. BSC6900
Setup "Appendix: V900R014C00
Failure Exception (or later) or
Cause Cause BSC6910
Classification / V100R014C00
Enumeration (or later)
Values of
Failure Cause
(UMTS)".

RAB ·CS_AMR N/A Service type of RAB request. BSC6900

Request ·CS_VP V900R014C00
Service (or later) or
Type ·CS_OTHER BSC6910
· V100R014C00
PS_GENERAL (or later)
·PS_HSDPA
·PS_HSUPA
·PS_HSPA …

RAB N/A N/A Time when RAB is requested. BSC6900

Request V900R014C00
Time (or later) or
BSC6910
V100R014C00
(or later)

Cell on N/A N/A Cell when RAB is requested. BSC6900

RRC V900R014C00
Request (or later) or
BSC6910
V100R014C00
(or later)

RAB N/A N/A Time of RAB setup. BSC6900

Setup V900R014C00
Time (or later) or
BSC6910
V100R014C00
(or later)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1042

Param Range Unit Description Supported NE

eter Version

Best N/A N/A Best cell on RAB setup. BSC6900

Cell on V900R014C00
RAB (or later) or
Setup BSC6910
V100R014C00
(or later)

Serving N/A N/A Serving cell on RAB setup. BSC6900

Averag [0,+∞) kbit/s Average uplink throughput. BSC6900

e ·If the service is RAB on CS domain, V900R014C00
Uplink it displays N/A (that is not (or later) or
Throug involved). BSC6910
hput V100R014C00
·If the service is RAB on PS domain, (or later)
it displays average throughput on
uplink of RAB process.
Average uplink throughput = Total
uplink throughput/Total uplink
transmission duration

Overlo ·Yes N/A If "Average Uplink Throughput" is BSC6900

w ·No smaller than "Average Uplink V900R014C00
Averag Throughput Threshold", the record (or later) or
e has the problem that the average BSC6910
Uplink uplink throughput is too small. V100R014C00
Throug The abnormal threshold is set when (or later)
hput creating tasks.

Total [0,+∞) Byte Total downlink throughput. BSC6900

Downli ·If the service is RAB on CS domain, V900R014C00
nk it displays N/A (that is not (or later) or
Throug involved). BSC6910
hput V100R014C00
·If the service is RAB on PS domain, (or later)
it displays total throughput on
downlink of RAB process.

Total [0,+∞) Seco Total downlink transmission BSC6900

Downli nd duration. V900R014C00
nk ·If the service is RAB on CS domain, (or later) or
Transm it displays N/A (that is not BSC6910
ission involved). V100R014C00
Duratio (or later)
n ·If the service is RAB on PS domain,
it displays total transmission
duration on downlink of RAB
process.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1046

Param Range Unit Description Supported NE

eter Version

Averag [0,+∞) kbit/s Average downlink throughput. BSC6900

e ·If the service is RAB on CS domain, V900R014C00
Downli it displays N/A (that is not (or later) or
nk involved). BSC6910
Throug V100R014C00
hput ·If the service is RAB on PS domain, (or later)
it displays average throughput on
downlink of RAB process.
Average downlink throughput =
Total downlink throughput/Total
downlink transmission duration

Overlo ·Yes N/A If "Average Downlink Throughput" BSC6900

w ·No is smaller than "Average Downlink V900R014C00
Averag Throughput Threshold", the record (or later) or
e has the problem that the average BSC6910
Downli downlink throughput is too small. V100R014C00
nk The abnormal threshold is set when (or later)
Throug creating tasks.
hput

3.10.7 Reference for Complaint Analysis Support Parameters (LTE)

This section describes the parameters for querying LTE Complaint Analysis Support results.
You can refer to the description when querying LTE complaint analysis support results.

Summary
Parameter Range Unit Description Supported
NE Version

Serial N/A N/A Serial number of a CHR. It LTE3900

Number uniquely identifies a call record. V100R005C00
or later version

Combined N/A N/A Whether a CHR is a combined LTE3900

one. V100R005C00
By Nastar, information about a or later version
call is obtained from both the
mobile-originated and mobile-
terminated eNodeBs and then is
combined into one CHR. A CHR
is a combined one if a yellow icon
is displayed.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1047

Parameter Range Unit Description Supported

NE Version

Status N/A N/A Whether a call record is LTE3900

abnormal. V100R005C00
If a red exclamation mark is or later version
displayed in this column, the call
record is abnormal.

Abnormal N/A N/A Cause of an abnormal call record, LTE3900

Cause which is displayed in the format V100R005C00
of Exception type (number of or later version
exception types)/Exception
cause (number of exception
causes). The exception types
include access failure, call drop,
and handover failure.

Network ·LTE FDD N/A Network technology type. LTE3900

·LTE TDD V100R005C00
or later version

Access ·Intra-RAT N/A Access type, based on which LTE3900

Type RRC Access subscriber access types can be V100R005C00
·Incoming defined. or later version
HO/Intra-
RAT
Incoming
HO
·Incoming
HO/UTRAN
Incoming
HO
·Incoming
HO/GERAN
Incoming
HO
·Incoming
HO

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1048

Parameter Range Unit Description Supported

NE Version

CSFB on · N/A Access type of CSFB. LTE3900

Access CSFB:VOIC V100R005C00
E- or later version
Emergency
call
·
CSFB:VOIC
E-Non-
emergency
call
·CSFB:LCS-
Non-
emergency
call

Access N/A N/A Time when a UE accesses a cell LTE3900

Time at the beginning of a call. V100R005C00
or later version

Access Cell 1 to 64 N/A Cell that a UE accesses at the LTE3900

characters beginning of a call. V100R005C00
The parameter value is in the or later version
following format: eNodeB
name:cell name (eNodeB ID:cell
ID).

Release N/A N/A Time when the link is released at LTE3900

Time the end of a call. V100R005C00
or later version

Release 1 to 64 N/A Cell from which a UE is released LTE3900

Cell characters at the end of a call. V100R005C00
The parameter value is in the or later version
following format: eNodeB
name:cell name (eNodeB ID:cell
ID).

User N/A N/A ·User ID, which is created by the LTE3900

ID:Alias system when creating the task. V100R005C00
·Alias, which is created by the or later version
user when creating the task.

IMSI N/A N/A IMSI information of a subscriber. LTE3900

NOTE V100R005C00
Only when you have the "User or later version
Identity" right, you can view the
IMSI information.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1049

Parameter Range Unit Description Supported

NE Version

STMSI N/A N/A STMSI information of a LTE3900

subscriber. V100R005C00
NOTE or later version
STMSI is displayed only when the
EPC is not interconnected.

IMEI-TAC 00000000-99 N/A First eight digits in the IMEI of a LTE3900

999999 UE. V100R005C00
IMEI is international mobile or later version
equipment identity for short and
TAC is type approval code for
short.

Terminal N/A N/A Model of a UE. LTE3900

Model V100R005C00
or later version

Duration [0,+∞) Second Duration of a call, which is LTE3900

displayed in the format of V100R005C00
hh:mm:ss.nnn. or later version
Call duration = Release time -
Access time.

User Information
Parameter Range Unit Description Supported
NE Version

User ID:Alias N/A N/A ·User ID, which is created by LTE3900

the system when creating the V100R005C00
task. or later version
·Alias, which is created by the
user when creating the task.

IMSI N/A N/A IMSI information of a LTE3900

subscriber. V100R005C00
NOTE or later version
Only when you have the "User
Identity" right, you can view the
IMSI information.

STMSI N/A N/A STMSI information of a LTE3900

subscriber. V100R005C00
NOTE or later version
STMSI is displayed only when
the EPC is not interconnected.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1050

Parameter Range Unit Description Supported

NE Version

MMEC BIT STRING bit MME code. LTE3900

(SIZE (8)) V100R005C00
or later version

mTMSI BIT STRING bit mTMSI information of a LTE3900

(SIZE (32)) subscriber. V100R005C00
or later version

eNodeB UE [0,2^32-1] N/A ID that uniquely identifies a LTE3900

S1AP ID UE on an eNodeB. V100R005C00
or later version

MME UE [0,2^32-1] N/A ID that uniquely identifies a LTE3900

S1AP ID UE on an MME. V100R005C00
or later version

IMEI-TAC 00000000-9999 N/A First eight digits in the IMEI LTE3900

9999 of a UE. V100R005C00
IMEI is international mobile or later version
equipment identity for short
and TAC is type approval
code for short.

Terminal N/A N/A Model of a UE. LTE3900

Model V100R005C00
or later version

UE Capability N/A N/A Access capability of a UE in LTE3900

terms of RAT support, V100R005C00
protocol version support, or later version
GERAN PS handover
support, device type, and
terminal type.

>FGI N/A N/A Specifies the FGI capability LTE3900

of UE. V100R005C00
or later version

>>Capability Support N/A Specifies whether the LTE3900

Related to capability of non-periodically V100R005C00
PUSCH Non- reporting CQIs, PMIs, or RIs or later version
Periodic CQI/ over the PUSCH is supported.
PMI/RI
Reporting

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1051

Parameter Range Unit Description Supported

NE Version

>>Capability Support N/A Specifies whether the LTE3900

Related to capability of periodically V100R005C00
PUSCH reporting CQIs, PMIs, or RIs or later version
Periodic CQI/ over the PUSCH is supported.
PMI/RI
Reporting

>>Support Support N/A Specifies whether the UM LTE3900

UM Mode at mode is supported at the RLC V100R005C00
RLC Layer layer and so on. or later version

>>Short- Support N/A Specifies whether short-term LTE3900

Period DRX DKX control is supported. V100R005C00
or later version

>>Long- Support N/A Specifies whether DRX LTE3900

Period DRX control is supported by the V100R005C00
and Support long-term DRX and at the or later version
DRX Control MAC layer.
at MAC Layer

>>Prioritized Support N/A Specifies whether the LTE3900

Bit Rate prioritized bit rate is V100R005C00
supported. or later version

>>Support Support N/A Specifies whether the UM LTE3900

UM Mode at mode is supported at the RLC V100R005C00
RLC Layer layer. or later version

>>PS-to- Support N/A Specifies whether the LTE3900

UTRAN HO capability of handing over V100R005C00
Capability from PS to UTRAN is or later version
supported.

>>GERAN Support N/A Specifies whether the LTE3900

HO Capability capability of handing over V100R005C00
Using SRVCC from SRVCC to GERAN is or later version
supported.

>>CCO/ Support N/A Specifies whether the CCO/ LTE3900

NACC NACC capability is V100R005C00
Capability supported. or later version

>>HO to Support N/A Specifies whether the LTE3900

1xRTT CS capability of handing over V100R005C00
Using SRVCC from SRVCC to 1xRTT CS is or later version
supported.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1052

Parameter Range Unit Description Supported

NE Version

>>Active HO Support N/A Specifies whether the LTE3900

from EUTRA capability of actively handing V100R005C00
RRC_CONN over from the EUTRA or later version
ECTED to RRC_CONNECTED mode
CDMA2000 to the CDMA2000 HRPD
HRPD mode is supported.

>>Inter- Support N/A Specifies whether the inter- LTE3900

Frequency HO frequency handover V100R005C00
Capability capability is supported. or later version

>>Intra-RAT Support N/A Specifies whether the intra- LTE3900

A4/A5 RAT A4/A5 measurement V100R005C00
Measurement capability is supported. or later version
Capability

>>Inter-RAT Support N/A Specifies whether the inter- LTE3900

B1 RAT B1 measurement V100R005C00
Measurement capability is supported. or later version
Capability

>>Periodic Support N/A Specifies whether periodic LTE3900

Measurements measurement, including V100R005C00
Including intra-frequency or later version
Intra- measurement, inter-
Frequency, frequency measurement, and
Inter- inter-RAT measurement, is
Frequency, supported.
and Inter-RAT
Measurements

>>Intra- Support N/A Specifies whether the intra- LTE3900

Frequency frequency ANR function is V100R005C00
ANR supported. or later version

>>Inter- Support N/A Specifies whether the inter- LTE3900

Frequency frequency ANR function is V100R005C00
ANR supported. or later version

>>Inter-RAT Support N/A Specifies whether the inter- LTE3900

ANR RAT ANR function is V100R005C00
supported. or later version

>>Capability Support N/A Specifies whether the AM or LTE3900

of Supporting UM mode supported by the V100R005C00
AM or UM DRB is supported. or later version
Mode by DRB

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1053

Parameter Range Unit Description Supported

NE Version

>>Intra- or Support N/A Specifies whether the intra- LTE3900

Inter- or inter-subframe frequency V100R005C00
Subframe FH hopping capability is or later version
Capability supported.

>>UTRAN Support N/A Specifies whether the LTE3900

B2 UTRAN B2 measurement V100R005C00
Measurement capability is supported. or later version
Capability

>>GERAN Support N/A Specifies whether the LTE3900

B2 GERAN B2 measurement V100R005C00
Measurement capability is supported. or later version
Capability

>>1xRTT B2 Support N/A Specifies whether the 1xRTT LTE3900

Measurement B2 measurement capability is V100R005C00
Capability supported. or later version

>>Inter- Support N/A Specifies whether inter- LTE3900

Frequency frequency measurement, V100R005C00
Measurement including measurement or later version
Capability between TDD and FDD
(Including frequencies, is supported.
Measurement
Capability
Between TDD
and FDD)

>>HRPD B2 Support N/A Specifies whether the HRPD LTE3900

Measurement B2 measurement capability is V100R005C00
Capability supported. or later version

>>UTRAN Support N/A Specifies whether the LTE3900

CS HO capability of handing over V100R005C00
Capability from SRVCC to UTRAN CS or later version
Using SRVCC is supported.

>>Capability Support N/A Specifies whether the LTE3900

Related to TTI capability related to TTI V100R005C00
Bunding Bunding is supported. or later version

>>Capability Support N/A Specifies whether the LTE3900

Related to capability related to half- V100R005C00
Half-Static static scheduling is or later version
Scheduling supported.

>>HO Support N/A Specifies whether the LTE3900

Between FDD capability of handing over V100R005C00
and TDD between FDD and TDD is or later version
supported.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1054

Parameter Range Unit Description Supported

NE Version

>>UTRAN Support N/A Specifies whether the LTE3900

IRAT ANR UTRAN IRAT ANR V100R005C00
Capability capability is supported. or later version

>>GERAN Support N/A Specifies whether the LTE3900

IRAT ANR GERAN IRAT ANR V100R005C00
Capability capability is supported. or later version

>>1xRTT/ Support N/A Specifies whether the LTE3900

2xRTT IRAT 1xRTT/2xRTT IRAT ANR V100R005C00
ANR capability is supported. or later version
Capability

>>HRPD Support N/A Specifies whether the HRPD LTE3900

IRAT ANR IRAT ANR capability is V100R005C00
Capability supported. or later version

>Support ·EUTRAN N/A RATs supported by a UE. LTE3900

RAT ·UTRAN V100R005C00
or later version
·GERAN CS
·GERAN PS
·CDMA2000 1X

>Supported ·REL-8 N/A Protocol versions supported LTE3900

Protocol ·REL-9 by a UE. V100R005C00
Version or later version
Number ·REL-10

>Support ·Yes N/A Whether a UE supports inter- LTE3900

Handover to ·No RAT handover to GERAN V100R005C00
GERAN PS PS. or later version
domain ·The UE does not
report capability
indicator
information.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1055

Parameter Range Unit Description Supported

NE Version

>Device Type N/A N/A Whether a UE supports LTE3900

battery consumption V100R005C00
optimization. or later version
If the parameter is zero, it
indicates that the device can
foresee to particularly benefit
from NW-based battery
consumption optimization;
If the parameter is not zero, it
indicates that the device does
not foresee to particularly
benefit from NW-based
battery consumption
optimization.
If the parameter is invalid, it
indicates that The UE does
not report capability indicator
information.

>Capability ·Category 1 N/A Uplink and downlink LTE3900

Class ·Category 2 capability of UE. V100R005C00
or later version
·Category 3
·Category 4
·Category 5

>Uplink N/A N/A Uplink physical layer LTE3900

Physical parameter related to UE V100R005C00
Layer category. or later version
Parameter

>>Maximum N/A N/A Maximum number of UL- LTE3900

Number of SCH transport block bits V100R005C00
Uplink-SCH transmitted within a TTI. or later version
Transport
Block Bits
Transmitted
within a TTI

>>Maximum N/A N/A Maximum number of bits of LTE3900

Number of an UL-SCH transport block V100R005C00
Bits of an transmitted within a TTI. or later version
Uplink-SCH
Transport
Block
Transmitted
within a TTI

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1056

Parameter Range Unit Description Supported

NE Version

>>Support for ·Yes N/A Whether support for 64QAM LTE3900

64QAM in ·No in UL. V100R005C00
Uplink or later version

>Downlink N/A N/A Downlink physical layer LTE3900

Physical parameter related to UE V100R005C00
Layer category. or later version
Parameter

>>Maximum N/A N/A Maximum number of DL- LTE3900

Number of SCH transport block bits V100R005C00
Downlink- received within a TTI. or later version
SCH
Transport
Block Bits
Received
within a TTI

>>Maximum N/A N/A Maximum number of bits of a LTE3900

Number of DL-SCH transport block V100R005C00
Bits of a received within a TTI. or later version
Downlink-
SCH
Transport
Block
Received
within a TTI

>>Maximum 1 N/A Maximum number of LTE3900

Number of 2 supported layers for spatial V100R005C00
Supported multiplexing in DL. or later version
Layers for 4
Spatial 8
Multiplexing 2 or 4
in Downlink

Access Information
Parameter Range Unit Description Supported
NE Version

Access Time N/A N/A Time when a UE accesses a LTE3900

cell at the beginning of a call. V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1057

Parameter Range Unit Description Supported

NE Version

Access Cell 1 to 64 N/A Cell that a UE accesses at the LTE3900

characters beginning of a call. V100R005C
The parameter value is in the 00 or later
following format: eNodeB version
name:cell name (eNodeB
ID:cell ID).

Access TA [0,1314] 16*Ts=0.5 Time advance (TA) during the LTE3900

2 ms access of a call. V100R005C
00 or later
version

Access Uplink [-150,-30] dBm Reference signal received LTE3900

RSRP power (RSRP) on the uplink V100R005C
during the access of a call. 00 or later
version

Access Uplink [-15,35] dB RSRQ on the uplink during the LTE3900

RSRQ access of a call. V100R005C
00 or later
version

Access Type ·Intra- N/A Access type, based on which LTE3900

RAT subscriber access types can be V100R005C
RRC defined. 00 or later
Access version
·Incoming
HO/Intra-
RAT
Incoming
HO
·Incoming
HO/
UTRAN
Incoming
HO
·Incoming
HO/
GERAN
Incoming
HO
·Incoming
HO

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1058

Parameter Range Unit Description Supported

NE Version

Access Cause · N/A Cause in the RRC setup LTE3900

Emergenc request message. V100R005C
y 00 or later
·High version
Priority
Access
·Mt-
Access
·Mo-
Signaling
·Mo-Data
·N/A

Access N/A N/A Complete time during the LTE3900

Complete Time access of a call. V100R005C
00 or later
version

Access Delay N/A N/A The delay time between the LTE3900
Time time of access request and the V100R005C
time of access completion. 00 or later
version

Release Information
Parameter Range Unit Description Supported
NE Version

Release Time N/A N/A Time when the link is released at the LTE3900
end of a call. V100R005C
00 or later
version

Release Cell 1 to 64 N/A Cell from which a UE is released at LTE3900

character the end of a call. V100R005C
s The parameter value is in the 00 or later
following format: eNodeB name:cell version
name (eNodeB ID:cell ID).

CSFB N/A N/A CSFB information. LTE3900

V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1059

Parameter Range Unit Description Supported

NE Version

>CSFB · N/A The triggering cause indicated by a LTE3900

Trigging Cause CSFB:V CSFB. V100R005C
OICE- 00 or later
Emergen version
cy call
·
CSFB:V
OICE-
Non-
emergen
cy call
·
CSFB:L
CS-Non-
emergen
cy call

>CSFB · N/A Indicates whether an eNodeB LTE3900

Response Respons successfully responds to the CSFP V100R005C
e indication from the MME. 00 or later
·No version
response

RRC Release ·Load N/A Release cause based on RRC of a LTE3900

Cause balancin call. V100R005C
g TAU 00 or later
·Other version

·CS
Rollback
to High
Priority

UE Context N/A N/A Release cause based on UE context LTE3900

Release Cause release of a call. V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1060

Parameter Range Unit Description Supported

NE Version

Handover · N/A Release cause based on the last LTE3900

Release Cause Handove handover release of a call. V100R005C
r based 00 or later
on the version
distance
·
Handove
r based
on the
coverage
·
Handove
r based
on the
load
balancin
g

Release N/A N/A Cause of a failed release. LTE3900

Information V100R005C
00 or later
version

>Release Type N/A N/A Type of the cause of a failed release. LTE3900
V100R005C
00 or later
version

>Release N/A N/A Details about the cause of a failed LTE3900

Reason release. V100R005C
00 or later
version

Signaling Flow Analysis

Parameter Range Unit Description Supported
NE Version

No. [1,+∞) N/A Number that uniquely identifies LTE3900

a sent and received signaling V100R005C
message. 00 or later
version

Signaling Time N/A N/A Time when a signaling message LTE3900

is sent or received. V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1061

Parameter Range Unit Description Supported

NE Version

Signaling Direct No N/A Direction for sending or LTE3900

direction receiving a signaling message. V100R005C
Uplink 00 or later
version
Downlink

Signaling Type N/A N/A Type of a signaling message that LTE3900

complies with any protocol and is V100R005C
transmitted over the S1-MME or 00 or later
Uu interface. version
For example, RRC CONNECT
REQUEST is a signaling type.

Signaling N/A N/A Content for sending or receiving LTE3900

Content a signaling message. V100R005C
Note: it will display the contents 00 or later
only for the all-signaling version
analysis.

Measurement Report Analysis

Parameter Range Unit Description Supported
NE Version

No. [1,+∞) N/A Number that is added LTE3900

sequentially from 1. V100R005C0
0 or later
version

Measurement N/A N/A Local time on the eNodeB LTE3900

Time when an MR is generated. V100R005C0
0 or later
version

MR Type ·EVENT_MR N/A The type of MR including LTE3900

· event MR, intra-frequency V100R005C0
PRE_INTRA_F MR of periodic MR, and 0 or later
REQ_MR private UE MR of periodic version
MR.
·PRE_UE_MR

Access Type ·EUTRAN N/A RAT type of an MR for LTE3900

·UTRAN inter-RAT measurement. V100R005C0
0 or later
·GERAN version
·CDMA2000
·TD-SCDMA

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1062

Parameter Range Unit Description Supported

NE Version

Measurement ·Serving cell N/A Type of a measurement LTE3900

Object Type ·Neighboring object in an MR. V100R005C0
cell 1 0 or later
version
·Neighboring
cell 2
·Neighboring
cell ...

Measure Object N/A N/A Indicates the measure cell LTE3900

information of MR, which V100R005C0
displays as eNodeBID: 0 or later
CellID. version

EARFCN/ LTE:[0,65535] N/A Indicates the cell ARFCNs LTE3900

ARFCN TD-SCDMA: of the LTE, GSM, or TD- V100R005C0
[0,65535] SCDMA network. 0 or later
version
GSM:[0,1023]

PCI/P-SC/ LTE:[0,503] N/A Indicates the physical LTE3900

BSIC/PN UMTS:[0,511] identify code of the cell. V100R005C0
LTE: PCI 0 or later
TD-SCDMA: version
[0,127] UMTS/TD-SCDMA: P-SC
GSM:[00,77] GSM: BSIC
CDMA:[0,511] CDMA: PN

RSRP/RSCP/ LTE:[-150,-30] dBm Indicates the signal strength LTE3900

RSSI/Pilot UMTS/TD- of the cell. V100R005C0
Strength SCDMA: LTE: RSRP 0 or later
[-116,-25] version
UMTS/TD-SCDMA:
GSM/CDMA: RSCP
[0,63] GSM: RSSI
CDMA: Pilot Strength

RSRQ/EcNo LTE: dB Indicates the signal quality LTE3900

[-19.5,-2.5] of the cell. V100R005C0
UMTS:[-24,0] LTE: RSRQ 0 or later
version
UMTS: Ec/No

Frequency Band ·DCS1800 N/A Frequency band indicator of LTE3900

Indicator ·PCS1900 a neighboring cell when the V100R005C0
measurement type is inter- 0 or later
RAT and the RAT is version
GERAN in an MR.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1063

Parameter Range Unit Description Supported

NE Version

UL DM RSRP [-150,-30] dBm Indicates the RSRP of LTE3900

uplink DMRS. V100R005C0
0 or later
version

UL DM SINR [-15,35] dB Indicates the SINR of LTE3900

downlink DMRS. V100R005C0
0 or later
version

UL IBLER [0.00,100.00] % Indicates the block error LTE3900

ratio on the uplink. V100R005C0
0 or later
version

DL IBLER(0) [0.00,100.00] % Indicates the block error LTE3900

ratio of the code 0 on the V100R005C0
downlink. 0 or later
version

UL SINR [-15,35] dB Indicates the SINR on the LTE3900

uplink. V100R005C0
0 or later
version

DL CQI(0) [0,26] N/A Indicates the CQI of the LTE3900

code 0 on all bandwidth of V100R005C0
the downlink. 0 or later
version

UL MIMO ·1T1R N/A Indicates the MIMO mode LTE3900

Mode ·1T2R on the uplink. V100R005C0
0 or later
·2T2R version
VIRTUAL
MIMO
·1T4R
·2T4R
VIRTUAL
MIMO
·1T8R BEAM
FORMING
·2T28R BEAM
FORMING

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1064

Parameter Range Unit Description Supported

NE Version

DL MIMO · N/A Indicates the MIMO mode LTE3900

Mode TX_MODE_SI on the downlink. V100R005C0
NGLE_ANT_P 0 or later
ORT_0 version
·
TX_MODE_T
RANS_DIV
·
TX_MODE_O
PEN_LOOP_M
IMO
·
TX_MODE_C
LOSED_LOOP
_MIMO
·
TX_MODE_M
ULTI_USER_
MIMO
·
TX_MODE_C
LOSED_LOOP
_RANK_1
·
TX_MODE_SI
NGLE_ANT_P
ORT_5
·
TX_MODE_B
EANFORMIN
G

RANK ·RANK1 N/A Indicates the RANK value LTE3900

·RANK2 reported by the UE at the V100R005C0
last time. 0 or later
version

UL RB Use [0,4294967295] N/A Indicates the total use times LTE3900

Times of the RB on the uplink. V100R005C0
0 or later
version

DL RB Use [0,4294967295] N/A Indicates the total use times LTE3900

Times of the RB on the downlink. V100R005C0
0 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1065

Parameter Range Unit Description Supported

NE Version

Initial [0,+∞) Numbe Number of times that a LTE3900

Transmission r downlink UE is scheduled V100R005C0
DL Grant during initial transmission. 0 or later
version

UL Grant [0,+∞) Numbe Number of times that an LTE3900

r uplink UE is scheduled, V100R005C0
including initial 0 or later
transmissions and version
retransmissions.

Proportion of [0.00,100.00] % Proportion of dual LTE3900

Dual codewords during initial V100R005C0
Codewords in transmission. 0 or later
Initial version
Transmission

UL [0.00,100.00] % Uplink retransmission ratio. LTE3900

Retransmission V100R005C0
Ratio 0 or later
version

DL [0.00,100.00] % Downlink retransmission LTE3900

Retransmission ratio. V100R005C0
Ratio 0 or later
version

Mobility Management Information

Parameter Range Unit Description Supported
NE Version

No. [1,+∞) N/A Number that is added LTE3900

sequentially from 1. V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1066

Parameter Range Unit Description Supported

NE Version

Abnormal ·! N/A Field indicating an abnormal LTE3900

·Blank handover. V100R005C
The value of this field is ! if 00 or later
the value of Handover Result version
is either of the following:
·HO Preparation Succeeded/
HO Failure
·HO Preparation Failure/
NULL
Otherwise, the value of this
field is blank.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1067

Parameter Range Unit Description Supported

NE Version

Handover ·Based on N/A The triggered cause of a LTE3900

Triggering distance handover. V100R005C
Cause ·Based on 00 or later
coverage area version

·Based on bearer
·Based on
service
·Based on
uplink quality
·Based on
frequency
priority
·Based on CSFB
·Based on
HPLMN return
·Based on other
causes
·Based on
distance_non-
emergency call
·Based on
coverage
area_non-
emergency call
·Based on
bearer_non-
emergency call
·Based on
service_non-
emergency call
·Based on
uplink
quality_non-
emergency call
·Based on
frequency
priority_non-
emergency call
·Based on
CSFB_non-
emergency call

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1068

Parameter Range Unit Description Supported

NE Version

·Based on
CSFB_emergen
cy call
·Based on
HPLMN
return_non-
emergency call
·Based on other
causes_non-
emergency call
·Based on other
causes_emerge
ncy call

HO Type Voice ·NON_SRVCC N/A Handover type during a voice LTE3900

· service. V100R005C
CS_ONLY_SR 00 or later
VCC version

·
CS_AND_PS_
SRVCC

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1069

Parameter Range Unit Description Supported

NE Version

Handover Type Intra-RAT N/A Handover type during a call. LTE3900

outgoing V100R005C
handover/Intra- 00 or later
frequency version
handover
Intra-RAT
outgoing
handover/Inter-
frequency
handover
Inter-RAT
outgoing
handover/
Handover to
UMTS
Inter-RAT
outgoing
handover/
Handover to
TD-SCDMA
Inter-RAT
outgoing
handover/
Handover to
CDMA2000
Inter-RAT
outgoing
handover/
Handover to
GERAN
Incoming
handover

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1070

Parameter Range Unit Description Supported

NE Version

Handover The handover N/A Interface types involved in a LTE3900

Interface Type interface types handover during a call. V100R005C
of intra-RAT 00 or later
handover are the version
following:
intra-eNodeB
handover
handover based
on the X2
interface;
handover based
on the S1
interface.
The handover
interface types
of inter-RAT
handover are the
following:
handover based
on the S1
interface.

Begin Time N/A s Preparation time for initiating LTE3900

an incoming or outgoing intra- V100R005C
RAT or inter-RAT handover 00 or later
during a call. version

Interval [0,+∞) s Interval = Start time - End LTE3900

time. V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1071

Parameter Range Unit Description Supported

NE Version

Overlong Yes N/A If the interval exceeds the LTE3900

Interval No overlong xxx delay threshold, V100R005C
the value of this parameter is 00 or later
Yes. Otherwise, the value of version
this parameter is No.
The overlong xxx delay
threshold is set by engineers
during task creation. The
threshold types are as follows:
· Overlong intra-RAT
outgoing handover delay
threshold;
· Overlong inter-RAT
outgoing handover delay
threshold;
· Overlong intra-RAT
incoming handover delay
threshold.

End Time N/A N/A End time. LTE3900

V100R005C
00 or later
version

Source Cell N/A N/A Source cell from which a call LTE3900
is handed over. V100R005C
The parameter value is in the 00 or later
following format: eNodeB version
name:cell name (eNodeB
ID:cell ID).

Source Cell [-150,-30] dBm RSRP of the serving cell on LTE3900

RSRP the uplink during the V100R005C
handover of a call. 00 or later
version

Source Cell [-15,35] dB RSRQ of the serving cell on LTE3900

RSRQ the uplink during the V100R005C
handover of a call. 00 or later
version

Target Cell N/A N/A Target cell to which a call is LTE3900

handed over. V100R005C
The parameter value is in the 00 or later
following format: eNodeB version
name:cell name (eNodeB
ID:cell ID).

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1072

Parameter Range Unit Description Supported

NE Version

Target Cell [-150,-30] dBm RSRP/RSCP/RSSI of the LTE3900

RSRP/RSCP/ serving cell during the V100R005C
RSSI handover of a call. 00 or later
version

Target Cell [-19.5,-2.5] dB RSRQ/EcNo of the serving LTE3900

RSRQ/EcNo cell during the handover of a V100R005C
call. 00 or later
version

Handover ·Radio Network N/A Triggering cause of the LTE3900

Preparation Layer preparation of an outgoing V100R005C
Triggering ·Transport handover during a call. The 00 or later
Cause Layer preparation triggering cause version
of an incoming handover is
·NAS Layer empty.
·Protocol Layer
·Miscellaneous

Handover ·Handover N/A Cause of a failed outgoing LTE3900

Preparation preparation to handover during a call. The V100R005C
Failure Cause target cell cause of a failed incoming 00 or later
failure handover is empty. version
·UE no answer
·UE handover
back to source
cell
·handover
canceled
·E-RAB setup
failure caused
by the target cell
refuse access
·E-RAB setup
failure caused
by the SGW
releases of the
incoming
handover

Cancel ·Yes N/A Whether the HANDOVER LTE3900

Handover ·No CANCEL message is received V100R005C
during the handover of a call. 00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1073

Parameter Range Unit Description Supported

NE Version

Reason for ·Radio Network N/A Protocol cause initiated due to LTE3900
Canceling HO Layer Cause a canceled handover. For V100R005C
·Transport details, see 9.2.1.3 and 9.2.6 in 00 or later
Layer Cause 3GPPTS36.413 version
specifications.
·NAS Layer
Cause
·Protocol Layer
Cause
·Other Cause

With Data ·Yes N/A Indicates whether data is LTE3900

Transmission ·No transmitted during the V100R005C
handover of a call. 00 or later
version

Handover ·HO Preparation N/A Handover result of a call, LTE3900

Result Succeed/HO including the handover V100R005C
Execution preparation result and 00 or later
Succeed handover execution result. version
·HO Preparation
Succeed/HO
Execution
Failure
·HO Preparation
Failure/NULL

TA upon [0,1314] 16*T Time advance (TA) during the LTE3900

Handover s=0.5 handover of a call. V100R005C
2 ms 00 or later
version

ULRSRP upon [-150,-30] dBm Reference signal received LTE3900

Handover power (RSRP) on the UL V100R005C
during the handover of a call. 00 or later
version

ULSINR upon [-15,35] dB SINR on the UL during the LTE3900

Handover handover of a call. V100R005C
00 or later
version

E-RAB ID [0,15] N/A ID of the E-RAB that is LTE3900

handed over. V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1074

Parameter Range Unit Description Supported

NE Version

E-RAB QCI ·GBR(QCI1) N/A Service type for which E- LTE3900

·GBR(QCI2) RAB is handed over. The V100R005C
parameter values are as 00 or later
·GBR(QCI3) follows: version
·GBR(QCI4) GBR (QCIN): GBR service
·Non GBR with high QoS. N = 1, 2, 3, or
(QCI5) 4. QCI is QoS class identifier
·Non GBR for short and GBR is
(QCI6) guaranteed bit rate for short.
·Non GBR Non GBR (QCIN): non-GBR
(QCI7) service with low QoS. N = 5,
6, 7, 8, or 9.
·Non GBR
(QCI8)
·Non GBR
(QCI9)

E-RAB ·Succeed N/A Result of accessing an E-RAB LTE3900

Handover ·Failure during an incoming handover. V100R005C
Preparation 00 or later
Result version

E-RAB Analysis
Parameter Range Unit Description Supported
NE
Version

No. [1,+∞) N/A Serial number of an E-RAB LTE3900

ID. It uniquely identifies an E- V100R005C
RAB ID. 00 or later
version

Abnormal ·! N/A Indicates whether an E-RAB LTE3900

·Blank is abnormal. V100R005C
00 or later
version

E-RAB Setup ! N/A Setup result of an E-RAB LTE3900

Abnormal Blank setup request. V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1075

Parameter Range Unit Description Supported

NE
Version

E-RAB Setup ·Radio Network N/A Cause of failed E-RAB setup. LTE3900
Cause Layer The parameter value also V100R005C
·Transport includes detailed causes. 00 or later
Layer version

·NAS Layer
·Protocol Layer
·Miscellaneous

E-RAB Request ·GBR(QCI1) N/A QCI level on E-RAB setup. LTE3900

Service Type ·GBR(QCI2) The parameter values are as V100R005C
(QCI) on E- follows: 00 or later
RAB Setup ·GBR(QCI3) version
·GBR(QCI4) GBR (QCIN): GBR service
with high QoS. N = 1, 2, 3, 4.
·Non GBR QCI is QoS class identifier for
(QCI5) short and GBR is guaranteed
·Non GBR bit rate for short.
(QCI6) Non GBR (QCIN): non-GBR
·Non GBR service with low QoS. N = 5,
(QCI7) 6, 7, 8, or 9.
·Non GBR
(QCI8)
·Non GBR
(QCI9)

E-RAB Request N/A N/A Time when E-RAB is LTE3900

Time requested. V100R005C
00 or later
version

Cell on E-RAB N/A N/A Cell when E-RAB is LTE3900

Request requested. V100R005C
00 or later
version

E-RAB Setup N/A N/A Time of RAB setup. LTE3900

Time V100R005C
00 or later
version

TA on E-RAB [0,1314] 16*Ts Time advance (TA) during the LTE3900

Setup =0.52 E-RAB setup of a call. V100R005C
ms 00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1076

Parameter Range Unit Description Supported

NE
Version

ULRSRP on E- [-150,-30] dBm Reference signal received LTE3900

RAB Setup power (RSRP) on the uplink V100R005C
during the E-RAB setup of a 00 or later
call. version

ULSINR on E- [-15,35] dB SINR on the uplink during the LTE3900

RAB Setup E-RAB setup of a call. V100R005C
00 or later
version

E-RAB Release ! N/A Release result of an E-RAB. LTE3900

Abnormal Blank V100R005C
00 or later
version

E-RAB Release E-RAB N/A Cause of E-RAB release. LTE3900

Cause abnormal V100R005C
release triggered 00 or later
by MME version
E-RAB
abnormal
release triggered
by eNodeB
E-RAB
abnormal
release triggered
by outgoing HO
execution
failure

E-RAB Data on ·Yes N/A Identifier indicating whether LTE3900

E-RAB Release ·No data is being transmitted when V100R005C
an E-RAB is released. 00 or later
If no data is being transmitted version
when the E-RAB is released,
the subscriber cannot perceive
the exception.

E-RAB Request ·GBR[1,4] N/A QCI level on E-RAB release. LTE3900

Service Type ·Non GBR[5,9] GBR (QCIN): GBR service V100R005C
(QCI) on E- with high QoS. N = 1, 2, 3, 4. 00 or later
RAB Release QCI is QoS class identifier for version
short and GBR is guaranteed
bit rate for short.
Non GBR (QCIN): non-GBR
service with low QoS. N = 5,
6, 7, 8, or 9.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1077

Parameter Range Unit Description Supported

NE
Version

E-RAB Release N/A N/A Time when an E-RAB is LTE3900

Time released. V100R005C
00 or later
version

Cells Released 1 to 64 N/A Cell from which an E-RAB is LTE3900

for E-RAB characters released. V100R005C
00 or later
version

TA on E-RAB [0,1314] 16*Ts Time advance (TA) during the LTE3900

Release =0.52 E-RAB release of a call. V100R005C
ms 00 or later
version

ULRSRP on E- [-150,-30] dBm Reference signal received LTE3900

RAB Release power (RSRP) on the uplink V100R005C
during the E-RAB release of a 00 or later
call. version

ULSINR on E- [-15,35] dB SINR on the uplink during the LTE3900

RAB Release E-RAB release of a call. V100R005C
00 or later
version

E-RAB Setup [0,+∞) Secon Setup delay of E-RAB. LTE3900

Delay d E-RAB Setup Delay = E-RAB V100R005C
Setup Time - E-RAB Request 00 or later
Time. version

E-RAB [0,+∞) Secon Duration of E-RAB. LTE3900

Duration d E-RAB Duration = E-RAB V100R005C
Release Time - E-RAB Setup 00 or later
Time version

Uplink Traffic (0.0,+∞) MB Total volume of uplink traffic LTE3900

Volume generated from an RAB in an V100R005C
eNodeB. 00 or later
version

Uplink (0.000,+∞) s Total duration of transmitting LTE3900

Transmission uplink data for an RAB in an V100R005C
Duration eNodeB. 00 or later
version

Average Uplink [0.000,+∞) kbit/s Average uplink throughput LTE3900

Throughput for an RAB in an eNodeB. V100R005C
00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1078

Parameter Range Unit Description Supported

NE
Version

Downlink (0.0,+∞) MB Total volume of downlink LTE3900

Traffic Volume traffic generated from an RAB V100R005C
in an eNodeB. 00 or later
version

Downlink (0.000,+∞) s Total duration of transmitting LTE3900

Transmission downlink data for an RAB in V100R005C
Duration an eNodeB. 00 or later
version

Average [0.000,+∞) kbit/s Average downlink throughput LTE3900

Downlink for an RAB in an eNodeB. V100R005C
Throughput 00 or later
version

Uplink VQI [0.0,5.0] N/A Average VQI value for uplink LTE3900
voice services borne by an V100R005C
RAB in an eNodeB. 00 or later
version

Downlink VQI [0.0,5.0] N/A Average VQI value for LTE3900

downlink voice services borne V100R005C
by an RAB in an eNodeB. 00 or later
version

Detail E-RAB Information(QCI2 to QCI9)

Parameter Range Unit Description Supported
NE
Version

E-RAB ID N/A N/A E-RAB ID. LTE3900

V100R005
C00 or later
version

E-RAB Setup N/A N/A The information during the E- LTE3900

Info RAB setup of a call. V100R005
C00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1079

Parameter Range Unit Description Supported

NE
Version

>E-RAB ·GBR(QCI1) N/A QCI level on E-RAB setup. LTE3900

Request Service ·GBR(QCI2) The parameter values are as V100R005
Type(QCI) on follows: C00 or later
E-RAB Setup ·GBR(QCI3) version
·GBR(QCI4) GBR (QCIN): GBR service
with high QoS. N = 1, 2, 3, 4.
·Non GBR QCI is QoS class identifier for
(QCI5) short and GBR is guaranteed
·Non GBR bit rate for short.
(QCI6) Non GBR (QCIN): non-GBR
·Non GBR service with low QoS. N = 5,
(QCI7) 6, 7, 8, or 9.
·Non GBR
(QCI8)
·Non GBR
(QCI9)

>E-RAB N/A N/A Time when E-RAB is LTE3900

Request Time requested. V100R005
C00 or later
version

>Cell on E- N/A N/A Cell when E-RAB is LTE3900

RAB Request requested. V100R005
C00 or later
version

>E-RAB Setup N/A N/A Time of RAB setup. LTE3900

Time V100R005
C00 or later
version

>E-RAB Setup ·Succeed N/A Setup result of an E-RAB LTE3900

Result ·Failure setup request. V100R005
C00 or later
version

>E-RAB Setup ·Radio Network N/A Cause of E-RAB setup. The LTE3900
Cause Layer parameter value also includes V100R005
·Transport detailed causes. C00 or later
Layer version

·NAS Layer
·Protocol Layer
·Miscellaneous

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1080

Parameter Range Unit Description Supported

NE
Version

>E-RAB Setup N/A N/A Delay information about the LTE3900

Delay setup of an E-RAB. V100R005
Estimation C00 or later
version

>>E-RAB [0,+∞) Second Setup delay of E-RAB. LTE3900

Setup Delay E-RAB Setup Delay = E- V100R005
RAB Setup Time - E-RAB C00 or later
Request Time. version

>>Long E-RAB ·Yes N/A Used for determining LTE3900

Setup Delay ·No whether an E-RAB setup V100R005
delay is exceedingly long. C00 or later
An E-RAB setup delay is version
exceedingly long if it is
greater than or equal to the
threshold for long E-RAB
setup delay.

>MR N/A N/A MR information during the E- LTE3900

Information on RAB setup of a call. V100R005
E-RAB Setup C00 or later
version

>>TA [0,1314] 16*Ts Time advance (TA) during LTE3900

=0.52 the E-RAB setup of a call. V100R005
ms C00 or later
version

>>UL RSRP [-150,-30] dBm Reference signal received LTE3900

power (RSRP) on the uplink V100R005
during the E-RAB setup of a C00 or later
call. version

>>UL SINR [-15,35] dB SINR on the uplink during the LTE3900

E-RAB setup of a call. V100R005
C00 or later
version

>E-RAB N/A N/A Priority information of an E- LTE3900

Priority RAB. V100R005
C00 or later
version

>>Priority ·High-priority N/A Priority of a setup E-RAB. LTE3900

·medium- V100R005
priority C00 or later
version
·low-priority

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1081

Parameter Range Unit Description Supported

NE
Version

>>E-RAB ·Shall not N/A Preempting capability of a LTE3900

Active trigger pre- setup E-RAB. V100R005
Preemptability emption C00 or later
·May trigger version
pre-emption

>>E-RAB ·Not pre- N/A Preempted capability of a LTE3900

Passive emptable setup E-RAB. V100R005
Preemptability ·Pre-emptable C00 or later
version

>E-RAB Rate N/A N/A Rate information of an E- LTE3900

Information RAB. V100R005
C00 or later
version

>>Maximum E- [0, 10,000,000] kbit/s Maximum downlink rate of a LTE3900

RAB DL Rate setup E-RAB. V100R005
C00 or later
version

>>Assured E- [0, 10,000,000] kbit/s Assured downlink rate of a LTE3900

RAB DL Rate setup E-RAB. V100R005
C00 or later
version

>>Maximum E- [0, 10,000,000] kbit/s Maximum uplink rate of a LTE3900

RAB UL Rate setup E-RAB. V100R005
C00 or later
version

>>Assured E- [0, 10,000,000] kbit/s Assured uplink rate of a setup LTE3900

RAB UL Rate E-RAB. V100R005
C00 or later
version

E-RAB Release N/A N/A The information during the E- LTE3900

Information RAB release of a call. V100R005
C00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1082

Parameter Range Unit Description Supported

NE
Version

>E-RAB ·GBR[1,4] N/A QCI level on E-RAB release. LTE3900

Request Service ·Non GBR[5,9] GBR (QCIN): GBR service V100R005
Type(QCI) on with high QoS. N = 1, 2, 3, 4. C00 or later
E-RAB Release QCI is QoS class identifier for version
short and GBR is guaranteed
bit rate for short.
Non GBR (QCIN): non-GBR
service with low QoS. N = 5,
6, 7, 8, or 9.

>E-RAB N/A N/A Time when an E-RAB release LTE3900

Release Request request is started. V100R005
Time C00 or later
version

>E-RAB N/A N/A Time when an E-RAB is LTE3900

Release released. V100R005
Complete Time C00 or later
version

>E-RAB [0,+∞) Second Duration of E-RAB. LTE3900

Duration E-RAB Duration = E-RAB V100R005
Release Time - E-RAB Setup C00 or later
Time version

>Cells Released 1 to 64 N/A Cell from which an E-RAB is LTE3900

for E-RAB characters released. V100R005
C00 or later
version

>E-RAB E-RAB N/A Cause of E-RAB release. LTE3900

Release Cause abnormal V100R005
release C00 or later
triggered by version
MME
E-RAB
abnormal
release
triggered by
eNodeB
E-RAB
abnormal
release
triggered by
outgoing HO
execution
failure

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1083

Parameter Range Unit Description Supported

NE
Version

>Initiating Party ·MME N/A End where an E-RAB is LTE3900

of E-RAB ·eNodeB released. V100R005
Release C00 or later
version

>E-RAB Data ·Yes N/A Identifier indicating whether LTE3900

on E-RAB ·No data is being transmitted V100R005
Release when an E-RAB is released. C00 or later
If no data is being transmitted version
when the E-RAB is released,
the subscriber cannot
perceive the exception.

>MR N/A N/A MR information during the E- LTE3900

Information on RAB release of a call. V100R005
E-RAB Release C00 or later
version

>>TA [0,1314] 16*Ts Time advance (TA) during LTE3900

=0.52 the E-RAB release of a call. V100R005
ms C00 or later
version

>>UL RSRP [-150,-30] dBm Reference signal received LTE3900

power (RSRP) on the uplink V100R005
during the E-RAB release of C00 or later
a call. version

>>UL SINR [-15,35] dB SINR on the uplink during the LTE3900

E-RAB release of a call. V100R005
C00 or later
version

E-RAB Process N/A N/A Information about the setup LTE3900

Information of an E-RAB. V100R005
C00 or later
version

>Statistics of N/A N/A Statistics on data LTE3900

Data transmission. V100R005
Transmission C00 or later
version

>>Total Uplink (0.0,+∞) MB Total volume of uplink traffic LTE3900

Traffic Volume generated from an RAB in an V100R005
eNodeB. C00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1084

Parameter Range Unit Description Supported

NE
Version

>>Total Uplink (0.000,+∞) s Total duration of transmitting LTE3900

Transmission uplink data for an RAB in an V100R005
Duration eNodeB. C00 or later
version

>>Average [0,+∞) kbit/s Average uplink throughput LTE3900

Uplink for an RAB in an eNodeB. V100R005
Throughput C00 or later
version

>>Low Average ·Yes N/A Indicates whether the average LTE3900

Uplink ·No uplink throughput for an V100R005
Throughput RAB in an eNodeB is less C00 or later
than the threshold for low version
average uplink throughput.

>>Total (0.0,+∞) MB Total volume of downlink LTE3900

Downlink traffic generated from an V100R005
Traffic Volume RAB in an eNodeB. C00 or later
version

>>Total (0.000,+∞) s Total duration of transmitting LTE3900

Downlink downlink data for an RAB in V100R005
Transmission an eNodeB. C00 or later
Duration version

>>Average [0,+∞) kbit/s Average uplink throughput LTE3900

Downlink for an RAB in an eNodeB. V100R005
Throughput C00 or later
version

>>Low Average ·Yes N/A Indicates whether the average LTE3900

Downlink ·No downlink throughput for an V100R005
Throughput RAB in an eNodeB is less C00 or later
than the threshold for low version
average downlink
throughput.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1085

Detail E-RAB Information(QCI1)

Parameter Range Unit Description Supported
NE
Version

E-RAB ID N/A N/A E-RAB ID. LTE3900

V100R005
C00 or later
version

E-RAB Setup N/A N/A The information during the E- LTE3900

Info RAB setup of a call. V100R005
C00 or later
version

>E-RAB ·GBR(QCI1) N/A QCI level on E-RAB setup. LTE3900

>E-RAB N/A N/A Time when E-RAB is LTE3900

Request Time requested. V100R005
C00 or later
version

>Cell on E-RAB N/A N/A Cell when E-RAB is LTE3900

Request requested. V100R005
C00 or later
version

>E-RAB Setup N/A N/A Time of RAB setup. LTE3900

Time V100R005
C00 or later
version

>E-RAB Setup ·Succeed N/A Setup result of an E-RAB LTE3900

Result ·Failure setup request. V100R005
C00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1086

Parameter Range Unit Description Supported

NE
Version

>E-RAB Setup ·Radio Network N/A Cause of E-RAB setup. The LTE3900
Cause Layer parameter value also includes V100R005
·Transport detailed causes. C00 or later
Layer version

·NAS Layer
·Protocol Layer
·Miscellaneous

>E-RAB Setup N/A N/A Delay information about the LTE3900

Delay setup of an E-RAB. V100R005
Estimation C00 or later
version

>>E-RAB [0,+∞) Secon Setup delay of E-RAB. LTE3900

Setup Delay d E-RAB Setup Delay = E-RAB V100R005
Setup Time - E-RAB Request C00 or later
Time. version

>>Long E-RAB ·Yes N/A Used for determining whether LTE3900

Setup Delay ·No an E-RAB setup delay is V100R005
exceedingly long. C00 or later
An E-RAB setup delay is version
exceedingly long if it is greater
than or equal to the threshold
for long E-RAB setup delay.

>MR N/A N/A MR information during the E- LTE3900

Information on RAB setup of a call. V100R005
E-RAB Setup C00 or later
version

>>TA [0,1314] 16*Ts Time advance (TA) during the LTE3900

=0.52 E-RAB setup of a call. V100R005
ms C00 or later
version

>>UL RSRP [-150,-30] dBm Reference signal received LTE3900

power (RSRP) on the uplink V100R005
during the E-RAB setup of a C00 or later
call. version

>>UL SINR [-15,35] dB SINR on the uplink during the LTE3900

E-RAB setup of a call. V100R005
C00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1087

Parameter Range Unit Description Supported

NE
Version

>E-RAB N/A N/A Priority information of an E- LTE3900

Priority RAB. V100R005
C00 or later
version

>>Priority ·High-priority N/A Priority of a setup E-RAB. LTE3900

·medium- V100R005
priority C00 or later
version
·low-priority

>>E-RAB ·Shall not N/A Preempting capability of a LTE3900

Active trigger pre- setup E-RAB. V100R005
Preemptability emption C00 or later
·May trigger version
pre-emption

>>E-RAB ·Not pre- N/A Preempted capability of a LTE3900

Passive emptable setup E-RAB. V100R005
Preemptability ·Pre-emptable C00 or later
version

>E-RAB Rate N/A N/A Rate information of an E- LTE3900

Information RAB. V100R005
C00 or later
version

>>Maximum E- [0, 10,000,000] kbit/s Maximum downlink rate of a LTE3900

RAB DL Rate setup E-RAB. V100R005
C00 or later
version

>>Assured E- [0, 10,000,000] kbit/s Assured downlink rate of a LTE3900

RAB DL Rate setup E-RAB. V100R005
C00 or later
version

>>Maximum E- [0, 10,000,000] kbit/s Maximum uplink rate of a LTE3900

RAB UL Rate setup E-RAB. V100R005
C00 or later
version

>>Assured E- [0, 10,000,000] kbit/s Assured uplink rate of a setup LTE3900

RAB UL Rate E-RAB. V100R005
C00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1088

Parameter Range Unit Description Supported

NE
Version

E-RAB Release N/A N/A The information during the E- LTE3900

Information RAB release of a call. V100R005
C00 or later
version

>E-RAB ·GBR[1,4] N/A QCI level on E-RAB release. LTE3900

>E-RAB N/A N/A Time when an E-RAB release LTE3900

Release Request request is started. V100R005
Time C00 or later
version

>E-RAB N/A N/A Time when an E-RAB is LTE3900

Release released. V100R005
Complete Time C00 or later
version

>E-RAB [0,+∞) Secon Duration of E-RAB. LTE3900

Duration d E-RAB Duration = E-RAB V100R005
Release Time - E-RAB Setup C00 or later
Time version

>Cells Released 1 to 64 N/A Cell from which an E-RAB is LTE3900

for E-RAB characters released. V100R005
C00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1089

Parameter Range Unit Description Supported

NE
Version

>E-RAB E-RAB N/A Cause of E-RAB release. LTE3900

Release Cause abnormal V100R005
release triggered C00 or later
by MME version
E-RAB
abnormal
release triggered
by eNodeB
E-RAB
abnormal
release triggered
by outgoing HO
execution
failure

>Initiating Party ·MME N/A End where an E-RAB is LTE3900

of E-RAB ·eNodeB released. V100R005
Release C00 or later
version

>E-RAB Data ·Yes N/A Identifier indicating whether LTE3900

on E-RAB ·No data is being transmitted when V100R005
Release an E-RAB is released. C00 or later
If no data is being transmitted version
when the E-RAB is released,
the subscriber cannot perceive
the exception.

>MR N/A N/A MR information during the E- LTE3900

Information on RAB release of a call. V100R005
E-RAB Release C00 or later
version

>>TA [0,1314] 16*Ts Time advance (TA) during the LTE3900

=0.52 E-RAB release of a call. V100R005
ms C00 or later
version

>>UL RSRP [-150,-30] dBm Reference signal received LTE3900

power (RSRP) on the uplink V100R005
during the E-RAB release of a C00 or later
call. version

>>UL SINR [-15,35] dB SINR on the uplink during the LTE3900

E-RAB release of a call. V100R005
C00 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1090

Parameter Range Unit Description Supported

NE
Version

E-RAB Process N/A N/A Information about the setup of LTE3900

Information an E-RAB. V100R005
C00 or later
version

>Statistics of N/A N/A Statistics on the voice quality LTE3900

Voice Quality for an RAB in an eNodeB. V100R005
C00 or later
version

>>UL VQI [0.0,5.0] N/A Average VQI value for uplink LTE3900
voice services borne by an V100R005
RAB in an eNodeB. C00 or later
version

>>UL VQI as [0,65535] Numb Number of times that the LTE3900

Excellent Times er average VQI value for uplink V100R005
voice services borne by an C00 or later
RAB in an eNodeB is greater version
than 4.

>>UL VQI as [0,65535] Numb Number of times that the LTE3900

Good Times er average VQI value for uplink V100R005
voice services borne by an C00 or later
RAB in an eNodeB is greater version
than 3.6 but is less than or
equal to 4.

>>UL VQI as [0,65535] Numb Number of times that the LTE3900

Accept Times er average VQI value for uplink V100R005
voice services borne by an C00 or later
RAB in an eNodeB is greater version
than 3.1 but is less than or
equal to 3.6.

>>UL VQI as [0,65535] Numb Number of times that the LTE3900

Poor Times er average VQI value for uplink V100R005
voice services borne by an C00 or later
RAB in an eNodeB is greater version
than 2.6 but is less than or
equal to 3.1.

>>UL VQI as [0,65535] Numb Number of times that the LTE3900

Bad Times er average VQI value for uplink V100R005
voice services borne by an C00 or later
RAB in an eNodeB is less than version
or equal to 2.6.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1091

Parameter Range Unit Description Supported

NE
Version

>>Poor Uplink ·Yes N/A Indicates whether the average LTE3900

VQI ·No VQI value for uplink voice V100R005
services borne by an RAB in C00 or later
an eNodeB is less than the version
threshold for poor uplink VQI.

>>Uplink Voice [0,1000] N/A Average frame deletion rate LTE3900

Frame Error (covering error packets and V100R005
Rate (Including delayed packets) for uplink C00 or later
Error Packets voice services borne by an version
and Delay RAB in an eNodeB.
Packets)

>>DL VQI [0.0,5.0] N/A Average VQI value for LTE3900

downlink voice services borne V100R005
by an RAB in an eNodeB. C00 or later
version

>>DL VQI as [0,65535] Numb Number of times that the LTE3900

Excellent Times er average VQI value for V100R005
downlink voice services borne C00 or later
by an RAB in an eNodeB is version
greater than 4.

>>DL VQI as [0,65535] Numb Number of times that the LTE3900

Good Times er average VQI value for V100R005
downlink voice services borne C00 or later
by an RAB in an eNodeB is version
greater than 3.6 but is less than
or equal to 4.

>>DL VQI as [0,65535] Numb Number of times that the LTE3900

Accept Times er average VQI value for V100R005
downlink voice services borne C00 or later
by an RAB in an eNodeB is version
greater than 3.1 but is less than
or equal to 3.6.

>>DL VQI as [0,65535] Numb Number of times that the LTE3900

Poor Times er average VQI value for V100R005
downlink voice services borne C00 or later
by an RAB in an eNodeB is version
greater than 2.6 but is less than
or equal to 3.1.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1092

Parameter Range Unit Description Supported

NE
Version

>>DL VQI as [0,65535] N/A Number of times that the LTE3900

Bad Times average VQI value for V100R005
downlink voice services borne C00 or later
by an RAB in an eNodeB is version
less than or equal to 2.6.

>>Poor ·Yes N/A Indicates whether the average LTE3900

Downlink VQI ·No VQI value for downlink voice V100R005
services borne by an RAB in C00 or later
an eNodeB is less than the version
threshold for poor downlink
VQI.

>>Downlink [0,1000] N/A Average frame deletion rate LTE3900

Voice Frame (covering error packets and V100R005
Error Rate delayed packets) for downlink C00 or later
(Including Error voice services borne by an version
Packets and RAB in an eNodeB.
Delay Packets)

>Statistics of N/A N/A Statistics on data LTE3900

Data transmission. V100R005
Transmission C00 or later
version

>>Uplink (0.0,+∞) MB Total volume of uplink traffic LTE3900

Traffic Volume generated from an RAB in an V100R005
eNodeB. C00 or later
version

>>Uplink (0.000,+∞) s Total duration of transmitting LTE3900

Transmission uplink data for an RAB in an V100R005
Duration eNodeB. C00 or later
version

>>Average [0,+∞) kbit/s Average uplink throughput for LTE3900

Uplink an RAB in an eNodeB. V100R005
Throughput C00 or later
version

>>Low Average ·Yes N/A Indicates whether the average LTE3900

Uplink ·No uplink throughput for an RAB V100R005
Throughput in an eNodeB is less than the C00 or later
threshold for low average version
uplink throughput.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1093

Parameter Range Unit Description Supported

NE
Version

>>Downlink (0.0,+∞) MB Total volume of downlink LTE3900

Traffic Volume traffic generated from an RAB V100R005
in an eNodeB. C00 or later
version

>>Downlink (0.000,+∞) s Total duration of transmitting LTE3900

Transmission downlink data for an RAB in V100R005
Duration an eNodeB. C00 or later
version

>>Average [0,+∞) kbit/s Average uplink throughput for LTE3900

Downlink an RAB in an eNodeB. V100R005
Throughput C00 or later
version

>>Low Average ·Yes N/A Indicates whether the average LTE3900

Downlink ·No downlink throughput for an V100R005
Throughput RAB in an eNodeB is less than C00 or later
the threshold for low average version
downlink throughput.

Trend Analysis-Process Traffic Statistics

Parameter Range Unit Description Supported
NE Version

No. N/A N/A Serial number of a record. LTE3900

V100R005C0
0 or later
version

Cell N/A N/A Information about a cell in LTE3900

which traffic is consumed. V100R005C0
0 or later
version

Record Time N/A N/A Period within which traffic LTE3900

is consumed. V100R005C0
0 or later
version

UL MCS N/A N/A Uplink MCS. LTE3900

V100R005C0
0 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1094

Parameter Range Unit Description Supported

NE Version

DL MCS N/A N/A Downlink MCS. LTE3900

V100R005C0
0 or later
version

E-RAB ID N/A N/A ID of an E-RAB. LTE3900

V100R005C0
0 or later
version

E-RAB QCI ·GBR(QCI1) N/A QCI of an E-RAB. The LTE3900

·GBR(QCI2) parameter values are as V100R005C0
follows: 0 or later
·GBR(QCI3) version
GBR (QCIN): GBR service
·GBR(QCI4) with high QoS. N = 1, 2, 3,
·Non GBR or 4. QCI is QoS class
(QCI5) identifier for short and
·Non GBR GBR is guaranteed bit rate
(QCI6) for short.
·Non GBR Non GBR (QCIN): non-
(QCI7) GBR service with low QoS.
N = 5, 6, 7, 8, or 9.
·Non GBR
(QCI8)
·Non GBR
(QCI9)

Uplink Traffic (0.0,+∞) MB Total uplink traffic volume LTE3900

Volume within a period. V100R005C0
0 or later
version

Uplink (0.000,+∞) s Total duration of LTE3900

Transmission transmitting uplink data V100R005C0
Duration within a period. 0 or later
version

Average Uplink [0,+∞) kbit/s Average uplink throughput LTE3900

Throughput within a period. V100R005C0
0 or later
version

Downlink (0.0,+∞) MB Total downlink traffic LTE3900

Traffic Volume volume within a period. V100R005C0
0 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1095

Parameter Range Unit Description Supported

NE Version

Downlink (0.000,+∞) s Total duration of LTE3900

Transmission transmitting downlink data V100R005C0
Duration within a period. 0 or later
version

Average [0,+∞) kbit/s Average downlink LTE3900

Downlink throughput within a period. V100R005C0
Throughput 0 or later
version

Trend Analysis-Cell-Process Voice Statistics

Paramet Range Unit Description Supported
er NE Version

No. N/A N/A Serial number of a record. LTE3900

V100R005C00
or later version

Record N/A N/A Time when a voice service is LTE3900

Time recorded. V100R005C00
or later version

Cell N/A N/A Information about a cell in which LTE3900

a voice service is used. V100R005C00
or later version

E-RAB N/A N/A ID of an E-RAB. LTE3900

ID V100R005C00
or later version

E-RAB ·GBR(QCI1) N/A QCI of an E-RAB. The parameter LTE3900

QCI ·GBR(QCI2) values are as follows: V100R005C00
GBR (QCIN): GBR service with or later version
·GBR(QCI3)
high QoS. N = 1, 2, 3, or 4. QCI
·GBR(QCI4) is QoS class identifier for short
·Non GBR(QCI5) and GBR is guaranteed bit rate
·Non GBR(QCI6) for short.
·Non GBR(QCI7) Non GBR (QCIN): non-GBR
service with low QoS. N = 5, 6,
·Non GBR(QCI8)
7, 8, or 9.
·Non GBR(QCI9)

UL VQI [0.0,5.0] N/A Average VQI value for uplink LTE3900

voice services. V100R005C00
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1096

Paramet Range Unit Description Supported

er NE Version

UL VQI [0,65535] Num Number of times that the VQI LTE3900

as ber value for uplink voice services is V100R005C00
Excellent greater than 4. or later version
Times

UL VQI [0,65535] Num Number of times that the VQI LTE3900

as Good ber value for uplink voice services is V100R005C00
Times greater than 3.6 but is equal to or or later version
less than 4.

UL VQI [0,65535] Num Number of times that the VQI LTE3900

as Accept ber value for uplink voice services is V100R005C00
Times greater than 3.1 but is equal to or or later version
less than 3.6.

UL VQI [0,65535] Num Number of times that the VQI LTE3900

as Poor ber value for uplink voice services is V100R005C00
Times greater than 2.6 but is equal to or or later version
less than 3.1.

UL VQI [0,65535] Num Number of times that the VQI LTE3900

as Bad ber value for uplink voice services is V100R005C00
Times equal to or less than 2.6. or later version

UL FER [0,1000] N/A Average frame deletion rate LTE3900

(covering error packets and V100R005C00
delayed packets) for uplink voice or later version
services.

DL VQI [0.0,5.0] N/A Average VQI value for downlink LTE3900

voice services. V100R005C00
or later version

DL VQI [0,65535] Num Number of times that the VQI LTE3900

as ber value for downlink voice services V100R005C00
Excellent is greater than 4. or later version
Times

DL VQI [0,65535] Num Number of times that the VQI LTE3900

as Good ber value for downlink voice services V100R005C00
Times is greater than 3.6 but is equal to or later version
or less than 4.

DL VQI [0,65535] Num Number of times that the VQI LTE3900

as Accept ber value for downlink voice services V100R005C00
Times is greater than 3.1 but is equal to or later version
or less than 3.6.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1097

Paramet Range Unit Description Supported

er NE Version

DL VQI [0,65535] Num Number of times that the VQI LTE3900

as Poor ber value for downlink voice services V100R005C00
Times is greater than 2.6 but is equal to or later version
or less than 3.1.

DL VQI [0,65535] Num Number of times that the VQI LTE3900

as Bad ber value for downlink voice services V100R005C00
Times is equal to or less than 2.6. or later version

DL FER [0,1000] N/A Average frame deletion rate LTE3900

(covering error packets and V100R005C00
delayed packets) for downlink or later version
voice services.

3.10.8 Reference for Complaint Analysis Support Parameters (PS

Core)
This section describes the parameters for PS Core complaint analysis support.

Parameters for Querying PS Core Complaint Analysis Support Results - Summary

This section describes the parameters for querying PS Core complaint analysis support
(summary) results. You can refer to the description when querying PS Core complaint analysis
support (summary) results.

Summary
Parameter Range Unit Description Supported NE
Version

Serial [1,2^31-1) N/A Serial number of a CHR in the USN9810

Number Summary Table. Serial number V900R011C01 or
is a keyword of a call record. It is later version
an internal identification in the
Nastar and can uniquely identify
a call record.

Combined N/A N/A The field in the PS core USN9810

complaint analysis support is V900R011C01 or
empty. later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1098

Parameter Range Unit Description Supported NE

Version

Status N/A N/A Indicates whether a call record is USN9810

abnormal. V900R011C01 or
If a red exclamation mark is later version
displayed in this column, the call
record is abnormal.
If a yellow question mark is
displayed in this column, the
exception type of this call record
in the navigation tree is Other and
the exception status is unknown.

Abnormal N/A N/A Cause of the exception carried in USN9810

Cause an Access Request message. V900R011C01 or
For details, see "Appendix: later version
Exception Cause Classification /
Key Signaling".

Access N/A N/A Start time of the signaling USN9810

Time procedure. V900R011C01 or
later version

Release N/A N/A End time of the signaling USN9810

Time procedure. V900R011C01 or
later version

IMSI N/A N/A IMSI information of a USN9810

subscriber. V900R011C01 or
Note: Only when you have the later version
"User Identity" right, you can
view the IMSI information.

User ID: N/A N/A ·User ID, which is created by the USN9810
Alias system when creating the task. V900R011C01 or
·Alias, which is created by the later version
user when creating the task.

MSISDN N/A N/A MSISDN information of a USN9810

subscriber. V900R011C01 or
Note: Only when you have the later version
"User Identity" right, you can
view the MSISDN information.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1099

Parameter Range Unit Description Supported NE

Version

CSFB ·Yes N/A Access type of CSFB. USN9810

·No V900R011C01 or
later version
·N/A

NE Type N/A N/A Core network (CN) NE types for USN9810

the signaling procedure. This V900R011C01 or
parameter can be any of the later version
following:
·SGSN
·MME
·GGSN
·SGW
·PGW
·SGW+PGW

NE Name N/A N/A Name of a CN NE. USN9810

V900R011C01 or
later version

Procedure N/A N/A Name of a signaling procedure. USN9810

Type For details, see "Appendix: V900R011C01 or
Exception Cause Classification / later version
Key Signaling".

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1100

Parameter Range Unit Description Supported NE

Version

RAI/TAI N/A N/A Indicates the routing area where USN9810

an SGSN signaling procedure is V900R011C01 or
initiated. later version
Indicates the tracking area where
an MME signaling procedure is
initiated.

Cell N/A N/A Name of the cell where signaling USN9810

accesses. V900R011C01 or
later version

APN N/A N/A APN involved in the session for USN9810

the SM procedure. V900R011C01 or
The field does not apply to the later version
MM procedure.

Procedure 0-65535 ms Delay of a signaling procedure. USN9810

Delay Time V900R011C01 or
later version

Parameters for Viewing PS Core Complaint Analysis Support Results - SGSN SM

This section describes the parameters for querying PS Core complaint analysis support (SGSN
SM) results. You can refer to the description when querying PS Core complaint analysis support
(SGSN SM) results.

Base Information
Parameter Range Unit Description Supported NE
Version

SN [1,2^32-1) N/A SN of a reported USN9810

CHR. The SN V900R011C01 or
accumulates on an later version
NE.

Access Time N/A N/A Start time of the USN9810

signaling procedure. V900R011C01 or
later version

Release Time N/A N/A End time of the USN9810

signaling procedure. V900R011C01 or
later version

Procedure 0-65535 ms Delay of a signaling USN9810

Delay Time procedure. V900R011C01 or
later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1101

Parameter Range Unit Description Supported NE

Version

NE Type N/A N/A CN NE types for the USN9810

signaling procedure. V900R011C01 or
This parameter can be later version
any of the following:
·SGSN
·MME

NE Name N/A N/A Name of a CN NE. USN9810

V900R011C01 or
later version

Board Subrack 0-255 N/A Subrack number of USN9810

No. the device that V900R011C01 or
generates CHRs. later version

Board Slot No. 0-255 N/A Slot number of the USN9810

device that generates V900R011C01 or
a CHR. later version

User Information
Parameter Range Unit Description Supported NE
Version

IMSI N/A N/A IMSI information of aUSN9810

subscriber. V900R011C01 or
Note: Only when you later version
have the "User
Identity" right, you
can view the IMSI
information.

User ID: Alias N/A N/A ·User ID, which is USN9810

created by the system V900R011C01 or
when creating the later version
task.
·Alias, which is
created by the user
when creating the
task.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1102

Parameter Range Unit Description Supported NE

Version

MSISDN N/A N/A MSISDN USN9810

information of a V900R011C01 or
subscriber. later version
Note: Only when you
have the "User
Identity" right, you
can view the
MSISDN
information.

IMEI-TAC 00000000-9999 N/A IMEI-TAC of the USN9810

9999 terminal that initiates V900R011C01 or
a service. later version

Terminal Model N/A N/A Model of the terminal USN9810

that initiates a V900R011C01 or
service. later version

MS Network N/A N/A Indicates the GRRS- USN9810

Capability related terminal V900R013C00 or
capability. later version

>GEA/1 0/1 N/A Indicates whether the USN9810

encryption GEA/1 encryption V900R013C00 or
algorithm algorithm is later version
supported.
0 not supported
1 supported

>SM 0/1 N/A Indicates whether the USN9810

capabilities via dedicated-channel- V900R013C00 or
dedicated based SM capability later version
channels is supported.
0 not supported
1 supported

>SM 0/1 N/A Indicates whether the USN9810

capabilities via GPRS-channel-based V900R013C00 or
GPRS channels SM capability is later version
supported.
0 not supported
1 supported

>UCS2 support 0/1 N/A Indicates whether USN9810

UCS2 is supported. V900R013C00 or
0 not supported later version

1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1103

Parameter Range Unit Description Supported NE

Version

>SS Screening 0/1 N/A Indicates whether the USN9810

Indicator string SS screening V900R013C00 or
(2) indicator is later version
supported.
0 not supported
1 supported

>SoLSA 0/1 N/A Indicates whether the USN9810

Capability SoLSA capability is V900R013C00 or
supported. later version
0 not supported
1 supported

>Revision level 0/1 N/A Indicates whether the USN9810

indicator (R99 revision-level V900R013C00 or
or later versions indicator is supported later version
of the protocol (by protocols in
support) 3GPP Specifications
Release 99 or later).
0 not supported
1 supported

>PFC feature 0/1 N/A Indicates whether the USN9810

mode(BSS PFC feature mode V900R013C00 or
packet flow (BSS data packet later version
procedures flow procedure) is
support) supported.
0 not supported
1 supported

>GEA/2 0/1 N/A Indicates whether the USN9810

encryption GEA/2 encryption V900R013C00 or
algorithm algorithm is later version
supported.
0 not supported
1 supported

>GEA/3 0/1 N/A Indicates whether the USN9810

encryption GEA/3 encryption V900R013C00 or
algorithm algorithm is later version
supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1104

Parameter Range Unit Description Supported NE

Version

>GEA/4 0/1 N/A Indicates whether the USN9810

encryption GEA/4 encryption V900R013C00 or
algorithm algorithm is later version
supported.
0 not supported
1 supported

>GEA/5 0/1 N/A Indicates whether the USN9810

encryption GEA/5 encryption V900R013C00 or
algorithm algorithm is later version
supported.
0 not supported
1 supported

>GEA/6 0/1 N/A Indicates whether the USN9810

encryption GEA/6 encryption V900R013C00 or
algorithm algorithm is later version
supported.
0 not supported
1 supported

>GEA/7 0/1 N/A Indicates whether the USN9810

encryption GEA/7 encryption V900R013C00 or
algorithm algorithm is later version
supported.
0 not supported
1 supported

>LCS VA 0/1 N/A Indicates whether the USN9810

capability LCS VA capability is V900R013C00 or
supported. later version
0 not supported
1 supported

>PS inter-RAT 0/1 N/A Indicates whether the USN9810

HO from inter-PS handover V900R013C00 or
GERAN to (GERAN to UTRAN later version
UTRAN Iu handover) capability
mode capability is supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1105

Parameter Range Unit Description Supported NE

Version

>PS inter-RAT 0/1 N/A Indicates whether the USN9810

HO from inter-PS handover V900R013C00 or
GERAN to E- (GERAN to E- later version
UTRAN S1 UTRAN handover)
mode capability capability is
supported.
0 not supported
1 supported

>EMM 0/1 N/A Indicates whether the USN9810

Combined EMM combined V900R013C00 or
procedures procedure capability later version
Capability is supported.
0 not supported
1 supported

>ISR support 0/1 N/A Indicates whether USN9810

ISR is supported. V900R013C00 or
0 not supported later version

1 supported

>SRVCC to 0/1 N/A Indicates whether the USN9810

GERAN/ SRVCC-to-GERAN/ V900R013C00 or
UTRAN UTRAN handover later version
capability capability is
supported.
0 not supported
1 supported

>EPC capability 0/1 N/A Indicates whether the USN9810

EPC capability is V900R013C00 or
supported. later version
0 not supported
1 supported

>NF capability 0/1 N/A Indicates whether the USN9810

NF capability is V900R013C00 or
supported. later version
0 not supported
1 supported

UE Network N/A N/A Indicates the UE- USN9810

Capability related terminal V900R013C00 or
capability. later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1106

Parameter Range Unit Description Supported NE

Version

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00 or
algorithm EEA0 algorithm EEA0 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00 or
algorithm 128- algorithm 128-EEA1 later version
EEA1 is supported.
supported 0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00 or
algorithm 128- algorithm 128-EEA2 later version
EEA2 is supported.
supported 0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00 or
algorithm EEA3 algorithm EEA3 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00 or
algorithm EEA4 algorithm EEA4 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00 or
algorithm EEA5 algorithm EEA5 is later version
supported supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1107

Parameter Range Unit Description Supported NE

Version

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00 or
algorithm EEA6 algorithm EEA6 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00 or
algorithm EEA7 algorithm EEA7 is later version
supported supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA0 EPS integrity V900R013C00 or
supported algorithm EIA0 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm 128- EPS integrity V900R013C00 or
EIA1 supported algorithm 128-EIA1 later version
is supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm 128- EPS integrity V900R013C00 or
EIA2 supported algorithm 128-EIA2 later version
is supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA3 EPS integrity V900R013C00 or
supported algorithm EIA3 is later version
supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1108

Parameter Range Unit Description Supported NE

Version

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA4 EPS integrity V900R013C00 or
supported algorithm EIA4 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA5 EPS integrity V900R013C00 or
supported algorithm EIA5 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA6 EPS integrity V900R013C00 or
supported algorithm EIA6 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA7 EPS integrity V900R013C00 or
supported algorithm EIA7 is later version
supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00 or
algorithm algorithm UEA0 is later version
UEA0 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00 or
algorithm algorithm UEA1 is later version
UEA1 supported.
supported 0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1109

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00 or
algorithm algorithm UEA2 is later version
UEA2 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00 or
algorithm algorithm UEA3 is later version
UEA3 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00 or
algorithm algorithm UEA4 is later version
UEA4 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00 or
algorithm algorithm UEA5 is later version
UEA5 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00 or
algorithm algorithm UEA6 is later version
UEA6 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00 or
algorithm algorithm UEA7 is later version
UEA7 supported.
supported 0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1110

User Index N/A N/A Index number of a USN9810

subscriber. V900R012C00 or
later version

User Home N/A N/A PLMN in the IMSI of USN9810

PLMN a subscriber. This V900R013C00 or
parameter is used for later version
personal data
anonymization.

Authentication ·NoAuth N/A Indicates whether a USN9810

Flag ·FirAuth procedure requires V900R011C01 or
authentication. later version
·SecAuth

IMEI Check N/A N/A Indicates whether a USN9810

Flag procedure requires V900R011C01 or
IMEI check. later version

P-TMSI N/A N/A Indicates whether a USN9810

Reallocation procedure requires P- V900R011C01 or
Flag TMSI reallocation. later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1113

Access Information
Parameter Range Unit Description Supported NE
Version

Type N/A N/A Type of the signaling USN9810

procedure. This V900R011C01 or later
parameter can be any of version
the following:
·SM
·MM

Procedure Type N/A N/A Name of a signaling USN9810

procedure. V900R011C01 or later
version

Procedure Init N/A N/A Procedure initiating party USN9810

Cause (UE or MME) and cause. V900R011C01 or later
For details, see the version
Description of Procedure
Initiating Causes in the
appendix.

Access Network N/A N/A Description of the access USN9810

Description network. V900R011C01 or later
version

>Inter CN Node N/A N/A Radio access network USN9810

Type (RAN) type for the V900R011C01 or later
signaling procedure. This version
parameter can be any of
the following:
·GPRS
·UMTS(W/TD)
·LTE

Access BSC/ N/A N/A Description of an NE that USN9810

RNC gains access to the RAN. V900R011C01 or later
Description version

>BSC/RNC N/A N/A PLMN serving a BSC or USN9810

PLMN RNC. V900R013C00 or later
version

>BSC/RNC ID N/A N/A ID of a BSC or RNC. USN9810

V900R013C00 or later
version

>CGI N/A N/A Cell where a procedure is USN9810

initiated. V900R011C01 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1114

Parameter Range Unit Description Supported NE

Version

>Cell Name [0,200] N/A Cell where a procedure is USN9810

initiated. V900R011C01 or later
version

PS Core N/A N/A Description of an NE that USN9810

Description gains access to the CN. V900R011C01 or later
version

>GGSN or N/A N/A IP address of the GGSN USN9810

PGW Address signaling plane. V900R011C01 or later
for Signalling version

>GGSN N/A N/A IP address of the GGSN USN9810

Address for user plane. V900R011C01 or later
User Traffic version

Mobility N/A N/A Information about USN9810

Information mobility analysis. V900R011C01 or later
version

>Old SGSN IP N/A N/A If a procedure involves USN9810

two SGSNs, the field V900R011C01 or later
indicates the IP address of version
the old SGSN.

>SM Procedure N/A N/A Information about the SM USN9810

Information procedure. V900R011C01 or later
version

>PDP Type In N/A N/A Type of the PDP used by USN9810

Used an MS. The values of this V900R013C00 or later
parameter are as follows: version
·IPv4
·IPv6
·BOTH(IPV4 & IPV6)
·PPP
·Empty

>PDP Type N/A N/A Type of the PDP USN9810

Request By MS requested by a MS. This V900R011C01 or later
parameter can be any of version
the following:
·IPv4
·IPv6
·BOTH(IPV4 & IPV6)
·PPP
·Empty

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1115

Parameter Range Unit Description Supported NE

Version

>PDP Address N/A N/A IP address of the PDP USN9810

Request By MS requested by a MS. V900R013C00 or later
version

>PDP Address N/A N/A Activated PDP IP USN9810

in Use address. V900R011C01 or later
version

>APN Request N/A N/A Name of the access point USN9810

By MS requested by an MS. V900R013C00 or later
version

>Access APN N/A N/A Access point name. USN9810

V900R011C01 or later
version

>APN Selection N/A N/A APN selection mode. USN9810

Mode This parameter can be V900R011C01 or later
any of the following: version
·MS & Network Verified
·MS not Verified
·Network not Verified

QoS N/A N/A Information about the USN9810

QoS. V900R011C01 or later
version

>Allocation/ N/A N/A Allocation/retention USN9810

Retention priority. This parameter V900R011C01 or later
Priority can be any of the version
following:
·High priority
·Normal priority
·Low priority

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1116

Parameter Range Unit Description Supported NE

Version

>Reliability N/A N/A Subscribed reliability USN9810

Class class. This parameter can V900R011C01 or later
be any of the following: version
·Unused. If received, it
shall be interpreted as
'010' (Note)
·Unacknowledged GTP;
Acknowledged LLC and
RLC, Protected data
·Unacknowledged GTP
and LLC; Acknowledged
RLC, Protected data
·Unacknowledged GTP,
LLC, and RLC, Protected
data
·Unacknowledged GTP,
LLC, and RLC,
Unprotected data

>Delay Class N/A N/A Subscribed delay class. USN9810

This parameter can be V900R011C01 or later
any of the following: version
·Subscribed delay class
·Delay class 1
·Delay Class 2
·Delay Class 3
·Delay Class 4 (best
effort)
·Reserved

>Precedence N/A N/A Subscribed precedence. USN9810

Class This parameter can be V900R011C01 or later
any of the following: version
·Subscribed precedence
·High priority
·Normal priority
·Low priority
·Reserved

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1117

Parameter Range Unit Description Supported NE

Version

>Peak N/A N/A Subscribed peak USN9810

Throughput throughput. This V900R011C01 or later
parameter can be any of version
the following:
·Subscribed peak
throughput
·Up to 1,000 octet/s
·Up to 2,000 octet/s
·Up to 4,000 octet/s
·Up to 8,000 octet/s
·Up to 16,000 octet/s
·Up to 32,000 octet/s
·Up to 64,000 octet/s
·Up to 128,000 octet/s
·Up to 256,000 octet/s

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1118

Parameter Range Unit Description Supported NE

Version

>Mean N/A N/A Subscribed mean USN9810

Throughput throughput. This V900R011C01 or later
parameter can be any of version
the following:
·Subscribed mean
throughput
·100 octet/h
·200 octet/h
·500 octet/h
·1 000 octet/h
·2 000 octet/h
·5 000 octet/h
·10 000 octet/h
·20 000 octet/h
·50 000 octet/h
·100 000 octet/h
·200 000 octet/h
·500 000 octet/h
·1 000 000 octet/h
·2 000 000 octet/h
·5 000 000 octet/h
·10 000 000 octet/h
·20 000 000 octet/h
·50 000 000 octet/h
·Reserved
·Best effort

>Delivery of N/A N/A Subscribed delivery of USN9810

Erroneous SDU erroneous SDUs. This V900R011C01 or later
parameter can be any of version
the following:
·No detect('-')
·Erroneous SDUs are
delivered('yes')
·Erroneous SDUs are not
delivered ('no')

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1119

Parameter Range Unit Description Supported NE

Version

>Delivery N/A N/A Subscribed delivery USN9810

Order order. This parameter can V900R011C01 or later
be any of the following: version
·With delivery order
('yes')
·Without delivery order
('no')

>Traffic Class N/A N/A Subscribed traffic class. USN9810

This parameter can be V900R011C01 or later
any of the following: version
·Conversational class
·Streaming class
·Interactive class
·Background class

>Traffic N/A N/A Subscribed traffic USN9810

Handling handling priority. This V900R011C01 or later
Priority parameter can be any of version
the following:
·Priority level 1
·Priority level 2
·Priority level 3

>Maximum 0-255 byte Maximum SDU length. USN9810

SDU Size V900R011C01 or later
version

>Maximum Bit 0-8640 bps Maximum uplink rate. USN9810

Rate for Uplink V900R011C01 or later
version

>Maximum Bit 0-2560 bps Maximum downlink rate. USN9810

Rate for 00 V900R011C01 or later
Downlink version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1120

Parameter Range Unit Description Supported NE

Version

>Residual BER N/A N/A Subscribed residual BER. USN9810

This parameter can be V900R011C01 or later
any of the following: version
·Subscribed residual BER
·5*10^2
·1*10^2
·5*10^3
·4*10^3
·1*10^3
·1*10^4
·1*10^5
·1*10^6
·6*10^8

>SDU Error N/A N/A Subscribed SDU error USN9810

Ratio ratio. This parameter can V900R011C01 or later
be any of the following: version
·Subscribed SDU error
ratio
·1*10^2
·7*10^3
·1*10^3
·1*10^4
·1*10^5
·1*10^6
·1*10^1

>Transfer Delay 0-255 ms Transfer delay. USN9810

V900R011C01 or later
version

>Guaranteed 0-8640 bps Guaranteed uplink rate. USN9810

Bit Rate for V900R011C01 or later
Uplink version

>Guaranteed 0-2560 bps Guaranteed downlink USN9810

Bit Rate for 00 rate. V900R011C01 or later
Downlink version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1121

Parameter Range Unit Description Supported NE

Version

GTP Tunnel N/A N/A GTP tunnel version. This USN9810

Version parameter can be any of V900R011C01 or later
the following: version
·GTPv0
·GTPv1

Result Information
Parameter Range Unit Description Supported NE
Version

Protocol Cause N/A N/A Cause value USN9810

provided in a V900R011C01 or
protocol. later version

Protocol Cause N/A N/A Description of a USN9810

Description protocol cause. V900R011C01 or
later version

Huawei's Cause N/A N/A Procedure result and USN9810

failure cause. V900R011C01 or
For details, see the later version
Description of
Exception Cause
Fields in the
appendix.

Huawei's Cause N/A N/A Description of a USN9810

Description cause according to V900R011C01 or
Huawei's knowledge later version
base.

Process Information
Parameter Range Unit Description Supported NE
Version

Traffic N/A N/A Information about the USN9810

Information traffic. V900R011C01 or
later version

>Uplink Data [0,+∞) Byte The traffic on the USN9810

Volume uplink. V900R012C00SPC3
08 or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1122

Parameter Range Unit Description Supported NE

Version

>Downlink [0,+∞) Byte The traffic on the USN9810

Data Volume downlink. V900R012C00SPC3
08 or later version

>Data Tunnel ·Yes N/A Tunnel type, USN9810

Type ·No including RNC- V900R012C00SPC3
SGSN-GGSN or 08 or later version
RNC-GGSN.
Yes indicates Direct
Tunnel(BSC/RNC-
GGSN), the
transmission
efficiency is higher.
No indicates Un-
Direct Tunnel(BSC/
RNC-SGSN-
GGSN).

Charging N/A N/A Information about the USN9810

Information charging. V900R011C01 or
later version

>Charging ID [1,2^32-1) N/A SN of a CHR that is USN9810

from GGSN sent to the billing V900R011C01 or
center. later version

>Charging N/A N/A Charging attribute of USN9810

Characteristics a UE. This parameter V900R011C01 or
can be any of the later version
following:
·Unspecified
·Hot billing Charging
·Flat rate Charging
·Prepaid Charging
·Normal Charging

Parameters for Viewing PS Core Complaint Analysis Support Results - SGSN MM

This section describes the parameters for querying PS Core complaint analysis support (SGSN
MM) results. You can refer to the description when querying PS Core complaint analysis support
(SGSN MM) results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1123

Base Information
Parameter Range Unit Description Supported NE
Version

SN [1,2^31-1 N/A SN of a reported CHR. USN9810

) The SN accumulates on V900R011C01 or later
an NE. version

Access Time N/A N/A Start time of the USN9810

signaling procedure. V900R011C01 or later
version

Release Time N/A N/A End time of the USN9810

signaling procedure. V900R011C01 or later
version

Procedure 0-65535 ms Delay of a signaling USN9810

Delay Time procedure. V900R011C01 or later
version

NE Type N/A N/A CN NE types for the USN9810

signaling procedure. V900R011C01 or later
This parameter can be version
any of the following:
·SGSN
·MME

NE Name N/A N/A Name of a CN NE. USN9810

V900R011C01 or later
version

Board Subrack 0-255 N/A Subrack number of the USN9810

No. device that generates V900R011C01 or later
CHRs. version

Board Slot No. 0-255 N/A Slot number of the USN9810

device that generates a V900R011C01 or later
CHR. version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1124

User Information
Parameter Range Unit Description Supported NE
Version

IMSI N/A N/A IMSI information of USN9810

a subscriber. V900R011C01 or
Note: Only when later version
you have the "User
Identity" right, you
can view the IMSI
information.

User ID: Alias N/A N/A ·User ID, which is USN9810

created by the V900R011C01 or
system when later version
creating the task.
·Alias, which is
created by the user
when creating the
task.

MSISDN N/A N/A MSISDN USN9810

information of a V900R011C01 or
subscriber. later version
Note: Only when
you have the "User
Identity" right, you
can view the
MSISDN
information.

IMEI-TAC 00000000-9999 N/A IMEI-TAC of the USN9810

9999 terminal that initiates V900R011C01 or
a service. later version

Terminal Model N/A N/A Model of the USN9810

terminal that initiates V900R011C01 or
a service. later version

MS Network N/A N/A Indicates the GRRS- USN9810

Capability related terminal V900R013C00 or
capability. later version

>GEA/1 0/1 N/A Indicates whether USN9810

encryption the GEA/1 V900R013C00 or
algorithm encryption algorithm later version
is supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1125

Parameter Range Unit Description Supported NE

Version

>SM 0/1 N/A Indicates whether USN9810

capabilities via the dedicated- V900R013C00 or
dedicated channel-based SM later version
channels capability is
supported.
0 not supported
1 supported

>SM 0/1 N/A Indicates whether USN9810

capabilities via the GPRS-channel- V900R013C00 or
GPRS channels based SM capability later version
is supported.
0 not supported
1 supported

>UCS2 support 0/1 N/A Indicates whether USN9810

UCS2 is supported. V900R013C00 or
0 not supported later version

1 supported

>SS Screening 0/1 N/A Indicates whether USN9810

Indicator string the SS screening V900R013C00 or
(2) indicator is later version
supported.
0 not supported
1 supported

>SoLSA 0/1 N/A Indicates whether USN9810

Capability the SoLSA V900R013C00 or
capability is later version
supported.
0 not supported
1 supported

>Revision level 0/1 N/A Indicates whether USN9810

indicator (R99 the revision-level V900R013C00 or
or later versions indicator is later version
of the protocol supported (by
support) protocols in 3GPP
Specifications
Release 99 or later).
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1126

Parameter Range Unit Description Supported NE

Version

>PFC feature 0/1 N/A Indicates whether USN9810

mode(BSS the PFC feature V900R013C00 or
packet flow mode (BSS data later version
procedures packet flow
support) procedure) is
supported.
0 not supported
1 supported

>GEA/2 0/1 N/A Indicates whether USN9810

encryption the GEA/2 V900R013C00 or
algorithm encryption algorithm later version
is supported.
0 not supported
1 supported

>GEA/3 0/1 N/A Indicates whether USN9810

encryption the GEA/3 V900R013C00 or
algorithm encryption algorithm later version
is supported.
0 not supported
1 supported

>GEA/4 0/1 N/A Indicates whether USN9810

encryption the GEA/4 V900R013C00 or
algorithm encryption algorithm later version
is supported.
0 not supported
1 supported

>GEA/5 0/1 N/A Indicates whether USN9810

encryption the GEA/5 V900R013C00 or
algorithm encryption algorithm later version
is supported.
0 not supported
1 supported

>GEA/6 0/1 N/A Indicates whether USN9810

encryption the GEA/6 V900R013C00 or
algorithm encryption algorithm later version
is supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1127

Parameter Range Unit Description Supported NE

Version

>GEA/7 0/1 N/A Indicates whether USN9810

encryption the GEA/7 V900R013C00 or
algorithm encryption algorithm later version
is supported.
0 not supported
1 supported

>LCS VA 0/1 N/A Indicates whether USN9810

capability the LCS VA V900R013C00 or
capability is later version
supported.
0 not supported
1 supported

>PS inter-RAT 0/1 N/A Indicates whether USN9810

HO from the inter-PS V900R013C00 or
GERAN to handover (GERAN later version
UTRAN Iu to UTRAN
mode capability handover) capability
is supported.
0 not supported
1 supported

>PS inter-RAT 0/1 N/A Indicates whether USN9810

HO from the inter-PS V900R013C00 or
GERAN to E- handover (GERAN later version
UTRAN S1 to E-UTRAN
mode capability handover) capability
is supported.
0 not supported
1 supported

>EMM 0/1 N/A Indicates whether USN9810

Combined the EMM combined V900R013C00 or
procedures procedure capability later version
Capability is supported.
0 not supported
1 supported

>ISR support 0/1 N/A Indicates whether USN9810

ISR is supported. V900R013C00 or
0 not supported later version

1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1128

Parameter Range Unit Description Supported NE

Version

>SRVCC to 0/1 N/A Indicates whether USN9810

GERAN/ the SRVCC-to- V900R013C00 or
UTRAN GERAN/UTRAN later version
capability handover capability
is supported.
0 not supported
1 supported

>EPC capability 0/1 N/A Indicates whether USN9810

the EPC capability is V900R013C00 or
supported. later version
0 not supported
1 supported

>NF capability 0/1 N/A Indicates whether USN9810

the NF capability is V900R013C00 or
supported. later version
0 not supported
1 supported

UE Network N/A N/A Indicates the UE- USN9810

Capability related terminal V900R013C00 or
capability. later version

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA0 algorithm EEA0 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm 128- algorithm 128-EEA1 later version
EEA1 is supported.
supported 0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm 128- algorithm 128-EEA2 later version
EEA2 is supported.
supported 0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1129

Parameter Range Unit Description Supported NE

Version

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA3 algorithm EEA3 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA4 algorithm EEA4 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA5 algorithm EEA5 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA6 algorithm EEA6 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA7 algorithm EEA7 is later version
supported supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA0 the EPS integrity V900R013C00 or
supported algorithm EIA0 is later version
supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1130

Parameter Range Unit Description Supported NE

Version

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm 128- the EPS integrity V900R013C00 or
EIA1 supported algorithm 128-EIA1 later version
is supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm 128- the EPS integrity V900R013C00 or
EIA2 supported algorithm 128-EIA2 later version
is supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA3 the EPS integrity V900R013C00 or
supported algorithm EIA3 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA4 the EPS integrity V900R013C00 or
supported algorithm EIA4 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA5 the EPS integrity V900R013C00 or
supported algorithm EIA5 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA6 the EPS integrity V900R013C00 or
supported algorithm EIA6 is later version
supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1131

Parameter Range Unit Description Supported NE

Version

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA7 the EPS integrity V900R013C00 or
supported algorithm EIA7 is later version
supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption algorithm later version
UEA0 UEA0 is supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption algorithm later version
UEA1 UEA1 is supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption algorithm later version
UEA2 UEA2 is supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption algorithm later version
UEA3 UEA3 is supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption algorithm later version
UEA4 UEA4 is supported.
supported 0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1132

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption algorithm later version
UEA5 UEA5 is supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption algorithm later version
UEA6 UEA6 is supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption algorithm later version
UEA7 UEA7 is supported.
supported 0 not supported
1 supported

>UCS2 support 0/1 N/A Indicates whether USN9810

(UCS2) UCS2 is supported. V900R013C00 or
0 not supported later version

1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA1 algorithm UIA1 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA2 algorithm UIA2 is later version
supported supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1133

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA3 algorithm UIA3 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA4 algorithm UIA4 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA5 algorithm UIA5 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA6 algorithm UIA6 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA7 algorithm UIA7 is later version
supported supported.
0 not supported
1 supported

>NF capability 0/1 N/A Indicates whether USN9810

the NF capability is V900R013C00 or
supported. later version
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1134

Parameter Range Unit Description Supported NE

Version

>1xSRVCC 0/1 N/A Indicates whether USN9810

capability the 1xSRVCC V900R013C00 or
capability is later version
supported.
0 not supported
1 supported

>Location 0/1 N/A Indicates whether USN9810

services (LCS) the LCS notification V900R013C00 or
notification mechanism later version
mechanisms capability is
capability supported.
0 not supported
1 supported

>LTE 0/1 N/A Indicates whether USN9810

Positioning the LPP capability is V900R013C00 or
Protocol (LPP) supported. later version
capability 0 not supported
1 supported

>Access class 0/1 N/A Indicates whether USN9810

control for the CSFB-access- V900R013C00 or
CSFB (ACC- level control later version
CSFB) capability is
capability supported.
0 not supported
1 supported

MS P-TMSI [1,2^31-1) N/A P-TMSI received USN9810

from a terminal V900R011C01 or
when a procedure is later version
initiated.

Allocated P- [1,2^31-1) N/A P-TMSI that the USN9810

TMSI network allocates to V900R011C01 or
a terminal. later version

User Index N/A N/A Index number of a USN9810

subscriber. V900R012C00 or
later version

User Home N/A N/A PLMN in the IMSI of USN9810

PLMN a subscriber. This V900R013C00 or
parameter is used for later version
personal data
anonymization.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1135

>RAI N/A N/A ·If a procedure does USN9810

not involve two V900R011C01 or
routing areas, the later version
field indicates the
routing area where
the procedure is
initiated.
·If a procedure
involves two routing
areas, the field
indicates the new
routing area.

>Old RAI N/A N/A If a procedure does USN9810

not involve two V900R011C01 or
routing areas, the later version
field indicates the
routing area where
the procedure is
initiated. Otherwise,
the field is empty.

>BSC/RNC N/A N/A PLMN serving a BSC USN9810

PLMN or RNC. V900R013C00 or
later version

>BSC/RNC ID N/A N/A ID of a BSC or RNC. USN9810

V900R013C00 or
later version

>CGI N/A N/A Cell where a USN9810

procedure is initiated. V900R011C01 or
later version

>Cell Name [0,200] N/A Name of a cell. USN9810

V900R011C01 or
later version

Mobility N/A N/A Information about USN9810

Information mobility analysis. V900R011C01 or
later version

Old SGSN IP N/A N/A If a procedure USN9810

involves two SGSNs, V900R011C01 or
the field indicates the later version
IP address of the old
SGSN. Otherwise,
the field is empty.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1138

Result Information
Parameter Range Unit Description Supported NE
Version

Attach Result N/A N/A Helps identify the USN9810

result of the V900R013C00 or
combined attach later version
procedure. The
values of this
parameter are as
follows:
·GPRS only attached
·Combined GPRS/
IMSI attached

Update Result N/A N/A Helps identify the USN9810

result of the V900R013C00 or
combined RAU later version
procedure. The
values of this
parameter are as
follows:
·RA updated
·combined RA/LA
updated
·RA updated and ISR
activated
·combined RA/LA
updated and ISR
activated

Protocol Cause N/A N/A Cause value USN9810

provided in a V900R011C01 or
protocol. later version

Protocol Cause N/A N/A Description of a USN9810

Description protocol cause. V900R011C01 or
later version

Huawei's Cause N/A N/A Procedure result and USN9810

failure cause. V900R011C01 or
For details, see the later version
Description of
Exception Cause
Fields in the
appendix.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1139

Parameter Range Unit Description Supported NE

Version

Huawei's Cause N/A N/A Description of a USN9810

Description cause according to V900R011C01 or
Huawei's knowledge later version
base.

Parameters for Viewing PS Core Complaint Analysis Support Results - MME SM

This section describes the parameters for querying PS Core complaint analysis support (MME
SM) results. You can refer to the description when querying PS Core complaint analysis support
(MME SM) results.

Base Information
Parameter Range Unit Description Supported NE
Version

SN [1,2^31-1) N/A SN of a reported USN9810

CHR. The SN V900R011C01 or
accumulates on an later version
NE.

Access Time N/A N/A Start time of the USN9810

signaling procedure. V900R011C01 or
later version

Release Time N/A N/A End time of the USN9810

signaling procedure. V900R011C01 or
later version

Procedure 0-65535 ms Delay of a signaling USN9810

Delay Time procedure. V900R011C01 or
later version

NE Type N/A N/A CN NE types for the USN9810

signaling procedure. V900R011C01 or
This parameter can later version
be any of the
following:
·SGSN
·MME

NE Name N/A N/A Name of a CN NE. USN9810

V900R011C01 or
later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1140

Parameter Range Unit Description Supported NE

Version

Board Subrack 0-255 N/A Subrack number of USN9810

No. the device that V900R011C01 or
generates CHRs. later version

Board Slot No. 0-255 N/A Slot number of the USN9810

device that generates V900R011C01 or
a CHR. later version

Board Proc No. 0-65535 N/A Number of the USN9810

process that V900R011C01 or
generates a CHR. later version

User Information
Parameter Range Unit Description Supported NE
Version

IMSI N/A N/A IMSI information of USN9810

a subscriber. V900R011C01 or
Note: Only when later version
you have the "User
Identity" right, you
can view the IMSI
information.

User ID: Alias N/A N/A ·User ID, which is USN9810

created by the V900R011C01 or
system when later version
creating the task.
·Alias, which is
created by the user
when creating the
task.

MSISDN N/A N/A MSISDN USN9810

information of a V900R011C01 or
subscriber. later version
Note: Only when
you have the "User
Identity" right, you
can view the
MSISDN
information.

IMEI-TAC 00000000-9999 N/A IMEI-TAC of the USN9810

9999 terminal that initiates V900R011C01 or
a service. later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1141

Parameter Range Unit Description Supported NE

Version

Terminal Model N/A N/A Model of the USN9810

terminal that initiates V900R011C01 or
a service. later version

MS Network N/A N/A Indicates the GRRS- USN9810

Capability related terminal V900R013C00 or
capability. later version

>GEA/1 0/1 N/A Indicates whether USN9810

encryption the GEA/1 V900R013C00 or
algorithm encryption later version
algorithm is
supported.
0 not supported
1 supported

>SM 0/1 N/A Indicates whether USN9810

capabilities via the dedicated- V900R013C00 or
dedicated channel-based SM later version
channels capability is
supported.
0 not supported
1 supported

>SM 0/1 N/A Indicates whether USN9810

capabilities via the GPRS-channel- V900R013C00 or
GPRS channels based SM capability later version
is supported.
0 not supported
1 supported

>UCS2 support 0/1 N/A Indicates whether USN9810

UCS2 is supported. V900R013C00 or
0 not supported later version

1 supported

>SS Screening 0/1 N/A Indicates whether USN9810

Indicator string the SS screening V900R013C00 or
(2) indicator is later version
supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1142

Parameter Range Unit Description Supported NE

Version

>SoLSA 0/1 N/A Indicates whether USN9810

Capability the SoLSA V900R013C00 or
capability is later version
supported.
0 not supported
1 supported

>Revision level 0/1 N/A Indicates whether USN9810

>PFC feature 0/1 N/A Indicates whether USN9810

mode(BSS the PFC feature V900R013C00 or
packet flow mode (BSS data later version
procedures packet flow
support) procedure) is
supported.
0 not supported
1 supported

>GEA/2 0/1 N/A Indicates whether USN9810

encryption the GEA/2 V900R013C00 or
algorithm encryption later version
algorithm is
supported.
0 not supported
1 supported

>GEA/3 0/1 N/A Indicates whether USN9810

encryption the GEA/3 V900R013C00 or
algorithm encryption later version
algorithm is
supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1143

Parameter Range Unit Description Supported NE

Version

>GEA/4 0/1 N/A Indicates whether USN9810

encryption the GEA/4 V900R013C00 or
algorithm encryption later version
algorithm is
supported.
0 not supported
1 supported

>GEA/5 0/1 N/A Indicates whether USN9810

encryption the GEA/5 V900R013C00 or
algorithm encryption later version
algorithm is
supported.
0 not supported
1 supported

>GEA/6 0/1 N/A Indicates whether USN9810

encryption the GEA/6 V900R013C00 or
algorithm encryption later version
algorithm is
supported.
0 not supported
1 supported

>GEA/7 0/1 N/A Indicates whether USN9810

encryption the GEA/7 V900R013C00 or
algorithm encryption later version
algorithm is
supported.
0 not supported
1 supported

>LCS VA 0/1 N/A Indicates whether USN9810

capability the LCS VA V900R013C00 or
capability is later version
supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1144

Parameter Range Unit Description Supported NE

Version

>PS inter-RAT 0/1 N/A Indicates whether USN9810

HO from the inter-PS V900R013C00 or
GERAN to handover (GERAN later version
UTRAN Iu to UTRAN
mode capability handover) capability
is supported.
0 not supported
1 supported

>PS inter-RAT 0/1 N/A Indicates whether USN9810

HO from the inter-PS V900R013C00 or
GERAN to E- handover (GERAN later version
UTRAN S1 to E-UTRAN
mode capability handover) capability
is supported.
0 not supported
1 supported

>EMM 0/1 N/A Indicates whether USN9810

Combined the EMM combined V900R013C00 or
procedures procedure capability later version
Capability is supported.
0 not supported
1 supported

>ISR support 0/1 N/A Indicates whether USN9810

ISR is supported. V900R013C00 or
0 not supported later version

1 supported

>SRVCC to 0/1 N/A Indicates whether USN9810

GERAN/ the SRVCC-to- V900R013C00 or
UTRAN GERAN/UTRAN later version
capability handover capability
is supported.
0 not supported
1 supported

>EPC capability 0/1 N/A Indicates whether USN9810

the EPC capability is V900R013C00 or
supported. later version
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1145

Parameter Range Unit Description Supported NE

Version

>NF capability 0/1 N/A Indicates whether USN9810

the NF capability is V900R013C00 or
supported. later version
0 not supported
1 supported

UE Network N/A N/A Indicates the UE- USN9810

Capability related terminal V900R013C00 or
capability. later version

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA0 algorithm EEA0 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm 128- algorithm 128- later version
EEA1 EEA1 is supported.
supported 0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm 128- algorithm 128- later version
EEA2 EEA2 is supported.
supported 0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA3 algorithm EEA3 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA4 algorithm EEA4 is later version
supported supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1146

Parameter Range Unit Description Supported NE

Version

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA5 algorithm EEA5 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA6 algorithm EEA6 is later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether USN9810

encryption the EPS encryption V900R013C00 or
algorithm EEA7 algorithm EEA7 is later version
supported supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA0 the EPS integrity V900R013C00 or
supported algorithm EIA0 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm 128- the EPS integrity V900R013C00 or
EIA1 supported algorithm 128-EIA1 later version
is supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm 128- the EPS integrity V900R013C00 or
EIA2 supported algorithm 128-EIA2 later version
is supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1147

Parameter Range Unit Description Supported NE

Version

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA3 the EPS integrity V900R013C00 or
supported algorithm EIA3 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA4 the EPS integrity V900R013C00 or
supported algorithm EIA4 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA5 the EPS integrity V900R013C00 or
supported algorithm EIA5 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA6 the EPS integrity V900R013C00 or
supported algorithm EIA6 is later version
supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether USN9810

algorithm EIA7 the EPS integrity V900R013C00 or
supported algorithm EIA7 is later version
supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption later version
UEA0 algorithm UEA0 is
supported supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1148

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption later version
UEA1 algorithm UEA1 is
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption later version
UEA2 algorithm UEA2 is
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption later version
UEA3 algorithm UEA3 is
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption later version
UEA4 algorithm UEA4 is
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption later version
UEA5 algorithm UEA5 is
supported supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1149

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption later version
UEA6 algorithm UEA6 is
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

encryption the UMTS V900R013C00 or
algorithm encryption later version
UEA7 algorithm UEA7 is
supported supported.
0 not supported
1 supported

>UCS2 support 0/1 N/A Indicates whether USN9810

(UCS2) UCS2 is supported. V900R013C00 or
0 not supported later version

1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA1 algorithm UIA1 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA2 algorithm UIA2 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA3 algorithm UIA3 is later version
supported supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1150

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA4 algorithm UIA4 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA5 algorithm UIA5 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA6 algorithm UIA6 is later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether USN9810

integrity the UMTS integrity V900R013C00 or
algorithm UIA7 algorithm UIA7 is later version
supported supported.
0 not supported
1 supported

>NF capability 0/1 N/A Indicates whether USN9810

the NF capability is V900R013C00 or
supported. later version
0 not supported
1 supported

>1xSRVCC 0/1 N/A Indicates whether USN9810

capability the 1xSRVCC V900R013C00 or
capability is later version
supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1151

Parameter Range Unit Description Supported NE

Version

>Location 0/1 N/A Indicates whether USN9810

services (LCS) the LCS notification V900R013C00 or
notification mechanism later version
mechanisms capability is
capability supported.
0 not supported
1 supported

>LTE 0/1 N/A Indicates whether USN9810

Positioning the LPP capability is V900R013C00 or
Protocol (LPP) supported. later version
capability 0 not supported
1 supported

>Access class 0/1 N/A Indicates whether USN9810

control for the CSFB-access- V900R013C00 or
CSFB (ACC- level control later version
CSFB) capability is
capability supported.
0 not supported
1 supported

User Index N/A N/A Index number of a USN9810

subscriber. V900R012C00 or
later version

User Home N/A N/A PLMN in the IMSI USN9810

PLMN of a subscriber. This V900R011C02 or
parameter is used for later version
personal data
anonymization.

Access Information
Parameter Range Unit Description Supported NE
Version

Type N/A N/A Type of the signaling USN9810

procedure. This V900R011C01 or later
parameter can be any of version
the following:
·SM
·MM

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1152

Parameter Range Unit Description Supported NE

Version

Procedure Type N/A N/A Name of a signaling USN9810

procedure. V900R011C01 or later
version

Procedure Init N/A N/A Procedure initiating party USN9810

Cause (UE or MME) and cause. V900R011C01 or later
For details, see the version
Description of Procedure
Initiating Causes in the
appendix.

Access eNodeB N/A N/A Information of the USN9810

Information eNodeB where a UE V900R011C01 or later
accesses. version

>eNodeB N/A N/A PLMN of the eNodeB USN9810

PLMN where a UE is located V900R011C01 or later
when a signaling version
procedure is initiated.

>eNodeB ID [1,2^31 N/A ID of the eNodeB where USN9810

-1) a UE is located when a V900R011C01 or later
signaling procedure is version
initiated.

MME UE S1AP [1,2^31 N/A UES1AP connection USN9810

ID -1) identification allocated V900R011C01 or later
by an MME in a traffic version
procedure.

MME S1AP ID N/A N/A Time when the UES1AP USN9810

Time connection identification V900R011C01 or later
is allocated by an MME version
in a traffic procedure.

Current TAC N/A N/A Tracking area where a USN9810

terminal is located when V900R011C01 or later
a signaling procedure is version
initiated.

PDN Type N/A N/A Requested PDN type in a USN9810

traffic procedure. This V900R011C01 or later
parameter can be any of version
the following:
·IPV4
·IPV6
·both(IPV4 & IPV6)
·unused

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1153

Parameter Range Unit Description Supported NE

Version

PDN Type In N/A N/A Used PDN type in a USN9810

Used traffic procedure. This V900R013C00 or later
parameter can be any of version
the following:
·IPV4
·IPV6
·both(IPV4 & IPV6)
·unused

PDN Address In IPv4, N/A Used PDN address in a USN9810

Used IPv6 traffic procedure. V900R013C00 or later
version

APN N/A N/A Requested APN in a USN9810

traffic procedure. V900R011C01 or later
version

APN In Used N/A N/A Requested APN in a USN9810

traffic procedure. V900R013C00 or later
version

Serving N/A N/A IP address of the Serving USN9810

Gateway Gateway in a signaling V900R011C01 or later
Address procedure. version

PDN Gateway N/A N/A IP address of the PDN USN9810

Address Gateway in a signaling V900R011C01 or later
procedure. version

PDN Gateway N/A N/A Domain name of the USN9810

Host Name PDN Gateway in a V900R011C01 or later
signaling procedure. version

QoS N/A N/A Information about the USN9810

QoS. V900R011C01 or later
version

>QCI 0-255 N/A QCI information USN9810

allocated by a session. V900R011C01 or later
version

>ARP 0-255 N/A ARP information USN9810

allocated by a session. V900R011C01 or later
version

>UE Uplink [1,2^31 bit/s Maximum UE-level USN9810

Max Bandwidth -1) uplink bandwidth V900R011C01 or later
allocated by a session. version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1154

Parameter Range Unit Description Supported NE

Version

>UE Downlink [1,2^31 bit/s Maximum UE-level USN9810

Max Bandwidth -1) downlink bandwidth V900R011C01 or later
allocated by a session. version

>APN Uplink [1,2^31 bit/s Maximum APN-level USN9810

Max Bandwidth -1) uplink bandwidth V900R011C01 or later
allocated by a session. version

>APN [1,2^31 bit/s Maximum APN-level USN9810

Downlink Max -1) downlink bandwidth V900R011C01 or later
Bandwidth allocated by a session. version

>GBR Uplink [1,2^31 bit/s Maximum bearer-level USN9810

-1) uplink bandwidth V900R011C01 or later
allocated by a session. version

>GBR [1,2^31 bit/s Maximum bearer-level USN9810

Downlink -1) downlink bandwidth V900R011C01 or later
allocated by a session. version

>MBR Uplink [1,2^31 bit/s Guaranteed bearer-level USN9810

-1) uplink bandwidth V900R011C01 or later
allocated by a session. version

>MBR [1,2^31 bit/s Guaranteed bearer-level USN9810

Downlink -1) downlink bandwidth V900R011C01 or later
allocated by a session. version

IMS Flag 0/1 N/A Identity of an IMS. The USN9810

(enumerated) values of V900R013C00 or later
this parameter are as version
follows:
0: non-IMS PDN
1: IMS PDN

Result Information
Parameter Range Unit Description Supported NE
Version

Protocol Cause N/A N/A Negotiated cause in a USN9810

procedure result. V900R011C01 or later
version

Protocol Cause N/A N/A Description of a USN9810

Description protocol cause. V900R011C01 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1155

Parameter Range Unit Description Supported NE

Version

Huawei's Cause N/A N/A Procedure result and USN9810

failure cause. V900R011C01 or later
version

Huawei's Cause N/A N/A Description of a cause USN9810

Description according to Huawei's V900R011C01 or later
knowledge base. version

Parameters for Viewing PS Core Complaint Analysis Support Results - MME MM

This section describes the parameters for querying PS Core complaint analysis support (MME
MM) results. You can refer to the description when querying PS Core complaint analysis support
(MME MM) results.

Base Information
Parameter Range Unit Description Supported NE
Version

SN [1,2^31-1) N/A SN of a reported USN9810

CHR. The SN V900R011C01 or
accumulates on an later version
NE.

Access Time N/A N/A Begin time of the USN9810

signaling V900R011C01 or
procedure. later version

Release Time N/A N/A End time of the USN9810

signaling V900R011C01 or
procedure. later version

Procedure 0-65535 ms Delay of a signaling USN9810

Delay Time procedure. V900R011C01 or
later version

NE Type N/A N/A CN NE types for the USN9810

signaling V900R011C01 or
procedure. This later version
parameter can be
any of the
following:
·SGSN
·MME

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1156

Parameter Range Unit Description Supported NE

Version

NE Name N/A N/A Name of a CN NE. USN9810

V900R011C01 or
later version

Board Subrack 0-255 N/A Subrack number of USN9810

No. the device that V900R011C01 or
generates CHRs. later version

Board Slot No. 0-255 N/A Slot number of the USN9810

device that V900R011C01 or
generates a CHR. later version

Board Proc No. 0-65535 N/A Number of the USN9810

process that V900R011C01 or
generates a CHR. later version

User Information
Parameter Range Unit Description Supported NE
Version

IMSI N/A N/A IMSI information of a USN9810

subscriber. V900R011C01
Note: Only when you or later version
have the "User Identity"
right, you can view the
IMSI information.

User ID: Alias N/A N/A ·User ID, which is USN9810

created by the system V900R011C01
when creating the task. or later version
·Alias, which is created
by the user when
creating the task.

MSISDN N/A N/A MSISDN information of USN9810

a subscriber. V900R011C01
Note: Only when you or later version
have the "User Identity"
right, you can view the
MSISDN information.

IMEI-TAC 00000000-9999 N/A IMEI-TAC of the USN9810

9999 terminal that initiates a V900R011C01
service. or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1157

Parameter Range Unit Description Supported NE

Version

Terminal Model N/A N/A Model of the terminal USN9810

that initiates a service. V900R011C01
or later version

MS Network N/A N/A Indicates the GRRS- USN9810

Capability related terminal V900R013C00
capability. or later version

>GEA/1 0/1 N/A Indicates whether the USN9810

encryption GEA/1 encryption V900R013C00
algorithm algorithm is supported. or later version
0 not supported
1 supported

>SM 0/1 N/A Indicates whether the USN9810

capabilities via dedicated-channel- V900R013C00
dedicated based SM capability is or later version
channels supported.
0 not supported
1 supported

>SM 0/1 N/A Indicates whether the USN9810

capabilities via GPRS-channel-based V900R013C00
GPRS channels SM capability is or later version
supported.
0 not supported
1 supported

>UCS2 support 0/1 N/A Indicates whether UCS2 USN9810

is supported. V900R013C00
0 not supported or later version

1 supported

>SS Screening 0/1 N/A Indicates whether the SS USN9810

Indicator string screening indicator is V900R013C00
(2) supported. or later version
0 not supported
1 supported

>SoLSA 0/1 N/A Indicates whether the USN9810

Capability SoLSA capability is V900R013C00
supported. or later version
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1158

Parameter Range Unit Description Supported NE

Version

>Revision level 0/1 N/A Indicates whether the USN9810

indicator (R99 revision-level indicator V900R013C00
or later versions is supported (by or later version
of the protocol protocols in 3GPP
support) Specifications Release
99 or later).
0 not supported
1 supported

>PFC feature 0/1 N/A Indicates whether the USN9810

mode(BSS PFC feature mode (BSS V900R013C00
packet flow data packet flow or later version
procedures procedure) is supported.
support) 0 not supported
1 supported

>GEA/2 0/1 N/A Indicates whether the USN9810

encryption GEA/2 encryption V900R013C00
algorithm algorithm is supported. or later version
0 not supported
1 supported

>GEA/3 0/1 N/A Indicates whether the USN9810

encryption GEA/3 encryption V900R013C00
algorithm algorithm is supported. or later version
0 not supported
1 supported

>GEA/4 0/1 N/A Indicates whether the USN9810

encryption GEA/4 encryption V900R013C00
algorithm algorithm is supported. or later version
0 not supported
1 supported

>GEA/5 0/1 N/A Indicates whether the USN9810

encryption GEA/5 encryption V900R013C00
algorithm algorithm is supported. or later version
0 not supported
1 supported

>GEA/6 0/1 N/A Indicates whether the USN9810

encryption GEA/6 encryption V900R013C00
algorithm algorithm is supported. or later version
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1159

Parameter Range Unit Description Supported NE

Version

>GEA/7 0/1 N/A Indicates whether the USN9810

encryption GEA/7 encryption V900R013C00
algorithm algorithm is supported. or later version
0 not supported
1 supported

>LCS VA 0/1 N/A Indicates whether the USN9810

capability LCS VA capability is V900R013C00
supported. or later version
0 not supported
1 supported

>PS inter-RAT 0/1 N/A Indicates whether the USN9810

HO from inter-PS handover V900R013C00
GERAN to (GERAN to UTRAN or later version
UTRAN Iu handover) capability is
mode capability supported.
0 not supported
1 supported

>PS inter-RAT 0/1 N/A Indicates whether the USN9810

HO from inter-PS handover V900R013C00
GERAN to E- (GERAN to E-UTRAN or later version
UTRAN S1 handover) capability is
mode capability supported.
0 not supported
1 supported

>EMM 0/1 N/A Indicates whether the USN9810

Combined EMM combined V900R013C00
procedures procedure capability is or later version
Capability supported.
0 not supported
1 supported

>ISR support 0/1 N/A Indicates whether ISR is USN9810

supported. V900R013C00
0 not supported or later version

1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1160

Parameter Range Unit Description Supported NE

Version

>SRVCC to 0/1 N/A Indicates whether the USN9810

GERAN/ SRVCC-to-GERAN/ V900R013C00
UTRAN UTRAN handover or later version
capability capability is supported.
0 not supported
1 supported

>EPC capability 0/1 N/A Indicates whether the USN9810

EPC capability is V900R013C00
supported. or later version
0 not supported
1 supported

>NF capability 0/1 N/A Indicates whether the NF USN9810

capability is supported. V900R013C00
0 not supported or later version

1 supported

UE Network N/A N/A Indicates the UE-related USN9810

Capability terminal capability. V900R013C00
or later version

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00
algorithm EEA0 algorithm EEA0 is or later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00
algorithm 128- algorithm 128-EEA1 is or later version
EEA1 supported.
supported 0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00
algorithm 128- algorithm 128-EEA2 is or later version
EEA2 supported.
supported 0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1161

Parameter Range Unit Description Supported NE

Version

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00
algorithm EEA3 algorithm EEA3 is or later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00
algorithm EEA4 algorithm EEA4 is or later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00
algorithm EEA5 algorithm EEA5 is or later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00
algorithm EEA6 algorithm EEA6 is or later version
supported supported.
0 not supported
1 supported

>EPS 0/1 N/A Indicates whether the USN9810

encryption EPS encryption V900R013C00
algorithm EEA7 algorithm EEA7 is or later version
supported supported.
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA0 EPS integrity algorithm V900R013C00
supported EIA0 is supported. or later version
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1162

Parameter Range Unit Description Supported NE

Version

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm 128- EPS integrity algorithm V900R013C00
EIA1 supported 128-EIA1 is supported. or later version
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm 128- EPS integrity algorithm V900R013C00
EIA2 supported 128-EIA2 is supported. or later version
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA3 EPS integrity algorithm V900R013C00
supported EIA3 is supported. or later version
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA4 EPS integrity algorithm V900R013C00
supported EIA4 is supported. or later version
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA5 EPS integrity algorithm V900R013C00
supported EIA5 is supported. or later version
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA6 EPS integrity algorithm V900R013C00
supported EIA6 is supported. or later version
0 not supported
1 supported

>EPS integrity 0/1 N/A Indicates whether the USN9810

algorithm EIA7 EPS integrity algorithm V900R013C00
supported EIA7 is supported. or later version
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1163

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00
algorithm algorithm UEA0 is or later version
UEA0 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00
algorithm algorithm UEA1 is or later version
UEA1 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00
algorithm algorithm UEA2 is or later version
UEA2 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00
algorithm algorithm UEA3 is or later version
UEA3 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00
algorithm algorithm UEA4 is or later version
UEA4 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00
algorithm algorithm UEA5 is or later version
UEA5 supported.
supported 0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1164

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00
algorithm algorithm UEA6 is or later version
UEA6 supported.
supported 0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

encryption UMTS encryption V900R013C00
algorithm algorithm UEA7 is or later version
UEA7 supported.
supported 0 not supported
1 supported

>UCS2 support 0/1 N/A Indicates whether UCS2 USN9810

(UCS2) is supported. V900R013C00
0 not supported or later version

1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

integrity UMTS integrity V900R013C00
algorithm UIA1 algorithm UIA1 is or later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

integrity UMTS integrity V900R013C00
algorithm UIA2 algorithm UIA2 is or later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

integrity UMTS integrity V900R013C00
algorithm UIA3 algorithm UIA3 is or later version
supported supported.
0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1165

Parameter Range Unit Description Supported NE

Version

>UMTS 0/1 N/A Indicates whether the USN9810

integrity UMTS integrity V900R013C00
algorithm UIA4 algorithm UIA4 is or later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

integrity UMTS integrity V900R013C00
algorithm UIA5 algorithm UIA5 is or later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

integrity UMTS integrity V900R013C00
algorithm UIA6 algorithm UIA6 is or later version
supported supported.
0 not supported
1 supported

>UMTS 0/1 N/A Indicates whether the USN9810

integrity UMTS integrity V900R013C00
algorithm UIA7 algorithm UIA7 is or later version
supported supported.
0 not supported
1 supported

>NF capability 0/1 N/A Indicates whether the NF USN9810

capability is supported. V900R013C00
0 not supported or later version

1 supported

>1xSRVCC 0/1 N/A Indicates whether the USN9810

capability 1xSRVCC capability is V900R013C00
supported. or later version
0 not supported
1 supported

>Location 0/1 N/A Indicates whether the USN9810

services (LCS) LCS notification V900R013C00
notification mechanism capability is or later version
mechanisms supported.
capability 0 not supported
1 supported

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1166

Parameter Range Unit Description Supported NE

Version

>LTE 0/1 N/A Indicates whether the USN9810

Positioning LPP capability is V900R013C00
Protocol (LPP) supported. or later version
capability 0 not supported
1 supported

>Access class 0/1 N/A Indicates whether the USN9810

control for CSFB-access-level V900R013C00
CSFB (ACC- control capability is or later version
CSFB) supported.
capability 0 not supported
1 supported

MS P-TMSI 0-2^32-1 N/A P-TMSI received from a USN9810

terminal when a V900R011C01
procedure is initiated. or later version

Allocated P- 0-2^32-1 N/A P-TMSI that the network USN9810

TMSI allocates to a terminal. V900R011C01
or later version

User Index N/A N/A Index number of a USN9810

subscriber. V900R012C00
or later version

User Home N/A N/A PLMN in the IMSI of a USN9810

PLMN subscriber. This V900R011C02
parameter is used for or later version
personal data
anonymization.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1167

Parameter Range Unit Description Supported NE

Version

Special Service N/A N/A Indication of a special USN9810

Indication service. The values of V900R012C00
this parameter are as or later version
follows:
·
MPS_USER_SUBSCRI
BER_DATA_CHECK_
FAILED
·MPS_USER_SUCC
·
EMERGENCY_USER_
AUTHENTICATION_
FAIL
·
EMERGENCY_USER_
RESTRICTION_FAIL
·
EMERGENCY_USER_
AUTHENTICATION_
SUCC_RESTRICTION
_SUCC
·
NON_SPECIAL_USER

VLR No. N/A N/A Number of a VLR. USN9810

V900R012C00
or later version

Authentication ·NoAuth N/A Indicates whether an USN9810

Flag ·FirAuth MM procedure requires V900R011C01
authentication. or later version
·SecAuth

IMEI Check Yes/No N/A Indicates whether an USN9810

Flag MM procedure requires V900R011C01
IMEI check. or later version

P-TMSI Yes/No N/A Indicates whether an USN9810

Reallocation MM procedure requires V900R011C01
Flag P-TMSI reallocation. or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1168

Access Information
Parameter Ran Unit Description Supported NE
ge Version

Type N/A N/A Type of the signaling procedure. USN9810

This parameter can be any of the V900R011C01
following: or later version
·SM
·MM

Procedure Type N/A N/A Name of a signaling procedure. USN9810

V900R011C01
or later version

Procedure Init N/A N/A Procedure initiating party (UE or USN9810

Cause MME) and cause. V900R011C01
For details, see the Description of or later version
Procedure Initiating Causes in the
appendix.

Access Network N/A N/A Description of the access network. USN9810

Description V900R011C01
or later version

>Inter CN Node 0/1 N/A Access network type of the source USN9810
Type or target node in the Inter RAU or V900R013C00
Inter Relocation procedure. or later version

>Access Type N/A N/A Radio access network (RAN) type USN9810
for the signaling procedure. This V900R011C01
parameter can be any of the or later version
following:
·GPRS
·UMTS(W/TD)
·LTE

>Source Access N/A N/A Works together with Inter CN Node USN9810
Net Type Type. This parameter is valid only V900R013C00
when Inter CN Node Type is set to or later version
new indicating the access network
type on the source node. This
parameter is blank in all the other
cases.

>Target Access N/A N/A Works together with Inter CN Node USN9810
Net Type Type. This parameter is valid only V900R013C00
when Inter CN Node Type is set to or later version
old indicating the access network
type on the target node. This
parameter is blank in all the other
cases.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1169

Parameter Ran Unit Description Supported NE

ge Version

SGW Change 0/1 N/A Indicates whether the S-GW has USN9810
Flag been changed in the TAU/HO V900R013C00
procedure. or later version

Access eNodeB N/A N/A Information about the eNodeB that USN9810
Information serves a terminal when a signaling V900R011C01
procedure is initiated. or later version

>eNodeB N/A N/A PLMN of the eNodeB where a UE USN9810

PLMN is located when a signaling V900R011C01
procedure is initiated. or later version

>eNodeB ID 0-2^ N/A ID of the eNodeB that serves a UE USN9810

32-1 when a signaling procedure is V900R011C01
initiated. or later version

MME UE S1AP 0-2^ N/A UES1AP connection identification USN9810

ID 32-1 allocated by an MME in a traffic V900R011C01
procedure. or later version

MME UE S1AP N/A N/A Time when the UES1AP USN9810

ID Time connection identification is V900R011C01
allocated by an MME in a traffic or later version
procedure.

Current TAC N/A N/A Tracking area where a terminal is USN9810

located when a signaling procedure V900R011C01
is initiated. or later version

New GUTI N/A N/A PLMN of GUTI allocated by the USN9810

PLMN network in a traffic procedure. V900R011C01
or later version

New GUTI 0-65 N/A MME Group Id of GUTI allocated USN9810

MMEGI 535 by the network in a traffic V900R011C01
procedure. or later version

New GUTI 0-25 N/A MME CODE of GUTI allocated by USN9810

MMEC 5 the network in a traffic procedure. V900R011C01
or later version

New GUTI 0-2^ N/A M-TMSI of GUTI allocated by the USN9810

MTMSI 32-1 network in a traffic procedure. V900R011C01
or later version

Old GUTI N/A N/A PLMN of GUTI received from a UE USN9810

PLMN in a traffic procedure. V900R011C01
or later version

Old GUTI 0-65 N/A MME Group Id of GUTI received USN9810

MMEGI 535 from a UE in a traffic procedure. V900R011C01
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1170

Parameter Ran Unit Description Supported NE

ge Version

Old GUTI 0-25 N/A MME CODE of GUTI received USN9810

MMEC 5 from a UE in a traffic procedure. V900R011C01
or later version

Old GUTI 0-2^ N/A M-TMSI of GUTI received from a USN9810

MTMSI 32-1 UE in a traffic procedure. V900R011C01
or later version

Old TAC N/A N/A ID of the old tracking area in a USN9810

signaling procedure that involves V900R011C01
more than one tracking area. or later version

Target eNodeB N/A N/A Information about the target USN9810

Information eNodeB in an inter-eNodeB V900R011C01
signaling procedure. or later version

>Target ID N/A N/A PLMN of the target eNodeB in a USN9810

PLMN signaling procedure that involves V900R011C01
more than one eNodeB. or later version

>Target ID 0-2^ N/A ID of the target eNodeB in a USN9810

32-1 signaling procedure that involves V900R011C01
more than one eNodeB. or later version

Target TAC N/A N/A ID of the target tracking area in a USN9810

signaling procedure that involves V900R011C01
more than one tracking area. or later version

Serving N/A N/A IP address of the Serving Gateway USN9810

Gateway in a signaling procedure. V900R011C01
Address or later version

Serving N/A N/A Domain name of the Serving USN9810

Gateway Host Gateway in a signaling procedure. V900R011C01
Name or later version

GU RAI N/A N/A If a UE is handed over from a LTE USN9810

network to a 2G/3G network or the V900R011C01
location of the UE is updated, the or later version
field is the RAC of the target routing
area. Otherwise, the field is empty.

GU Cell N/A N/A If a UE is handed over from a LTE USN9810

network to a 2G/3G network or the V900R011C01
location of the UE is updated, the or later version
field is the CGI of the target cell.
Otherwise, the field is empty.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1171

Parameter Ran Unit Description Supported NE

ge Version

GU Old RAI N/A N/A If a UE is handed over from a 2G/ USN9810

3G network to a LTE network or the V900R011C01
location of the UE is updated, the or later version
field is the RAC of the old routing
area. Otherwise, the field is empty.

Mobility N/A N/A Information about mobility USN9810

Information analysis. V900R011C01
or later version

>Old SGSN IP N/A N/A If a procedure involves two SGSNs, USN9810

the field indicates the IP address of V900R011C01
the old SGSN. or later version

Result Information
Parameter Range Unit Description Supported NE
Version

EPS Attach N/A N/A Helps identify the USN9810

Result result of the combined V900R013C00 or
attach procedure. later version
EPS only
combined EPS/IMSI
attach

EPS Update N/A N/A Helps identify the USN9810

Result result of the combined V900R013C00 or
RAU procedure. The later version
values of this
parameter are as
follows:
TA updated
combined TA/LA
updated
TA updated and ISR
activated (NOTE)
combined TA/LA
updated and ISR
activated (NOTE)

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1172

Parameter Range Unit Description Supported NE

Version

Additional N/A N/A Result of the USN9810

Update Result additional update V900R013C00 or
procedure. The values later version
of this parameter are
as follows:
no additional
information
CS Fallback not
preferred
SMS only
reserved

VoIMS Bear N/A N/A Status of a voice USN9810

Status bearer (with a leve-1 V900R013C00 or
QCI) before and after later version
the procedure is
executed.

Protocol Cause N/A N/A Protocol cause value USN9810

in a procedure result. V900R011C01 or
later version

Protocol Cause N/A N/A Description of a USN9810

Description protocol cause. V900R011C01 or
later version

Huawei's Cause N/A N/A Procedure result and USN9810

failure cause value. V900R011C01 or
later version

Huawei's Cause N/A N/A Description of a cause USN9810

Description according to Huawei's V900R011C01 or
knowledge base. later version

Parameters for Viewing PS Core Complaint Analysis Support Results - GGSN/

SAE-GW
This section describes the parameters for querying PS Core complaint analysis support (GGSN/
SAE-GW) results. You can refer to the description when querying PS Core complaint analysis
support (GGSN/SAE-GW) results.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1173

Base Information
Parameter Range Unit Description Supported NE
Version

CHR SN [1,2^31-1 N/A SN of a reported CHR. The SN UGW9810

) accumulates on an NE. V900R011C01 or
later version

Release Time N/A N/A End time of the signaling UGW9810

procedure. V900R011C01 or
later version

NE Type ·GGSN N/A CN NE types for the signaling UGW9810

·SGW procedure. V900R011C01 or
later version
·PGW
·SGW
+PGW

NE Name N/A N/A Name of a CN NE. UGW9810

V900R011C01 or
later version

User Information
Parameter Ran Unit Description Supported NE
ge Version

IMSI N/A N/A IMSI information of a subscriber. UGW9810

Note: Only when you have the V900R011C01 or
"User Identity" right, you can view later version
the IMSI information.

User ID: Alias N/A N/A ·User ID, which is created by the UGW9810
system when creating the task. V900R011C01 or
·Alias, which is created by the user later version
when creating the task.

MSISDN N/A N/A MSISDN information of a UGW9810

subscriber. V900R011C01 or
Note: Only when you have the later version
"User Identity" right, you can view
the MSISDN information.

Terminal Model N/A N/A Model of the terminal that initiates UGW9810
a service. V900R011C01 or
later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1174

Parameter Ran Unit Description Supported NE

ge Version

IMEI-TAC 0000 N/A IMEI-TAC of the terminal that UGW9810

0000 initiates a service. V900R011C01 or
-999 later version
9999
9

Procedure Information-Common
Parameter Range Unit Description Supported
NE Version

Procedure Type N/A N/A Name of a signaling UGW9810

procedure. V900R011C01
or later version

APN N/A N/A Requested APN in a traffic UGW9810

procedure. V900R011C01
or later version

Access Net ·NA N/A Type of the RAN involved in UGW9810

Type ·UTRAN the signaling procedure V900R011C01
or later version
·GERAN
·WLAN
·GAN
·HSPA
Evolution
·EUTRAN

Abnormal N/A N/A Cause of the exception UGW9810

Cause carried in an Access V900R011C01
message. or later version
For details, see the
Description of Exception
Cause in the appendix.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1175

Procedure Information-Create PDP

Parameter Range Unit Description Supported
NE Version

PDP Type ·X25 N/A Type of the PDP when the UGW9810
·PPP context is activated V900R011C0
1 or later
· version
OSP_IHOS
S
·IPV4
·IPV6
·IPV4V6

MS IP V4 N/A N/A IPv4 address allocated to the UGW9810

subscriber's MS V900R011C0
1 or later
version

MS IP V6 N/A N/A IPv6 address allocated to the UGW9810

subscriber's MS V900R011C0
1 or later
version

SGSN Address N/A N/A IPv4 address for configuring the UGW9810
for Signaling control plane of the SGSN that V900R011C0
the subscriber's MS accesses 1 or later
version

SGSN IPv6 N/A N/A IPv6 address for configuring the UGW9810
Address for control plane of the SGSN that V900R011C0
Signaling the subscriber's MS accesses 1 or later
version

SGSN Address N/A N/A IPv4 address for configuring the UGW9810
for Data user plane of the SGSN that the V900R011C0
subscriber's MS accesses 1 or later
version

SGSN IPv6 N/A N/A IPv6 address for configuring the UGW9810
Address for user plane of the SGSN that the V900R011C0
Data subscriber's MS accesses 1 or later
version

GGSN Address N/A N/A IPv4 address for configuring the UGW9810
for Signaling control plane of the GGSN that V900R011C0
the subscriber's MS accesses 1 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1176

Parameter Range Unit Description Supported

NE Version

GGSN IPv6 N/A N/A IPv6 address for configuring the UGW9810
Address for control plane of the GGSN that V900R011C0
Signaling the subscriber's MS accesses 1 or later
version

GGSN Address N/A N/A IPv4 address for configuring the UGW9810
for Data user plane of the GGSN that the V900R011C0
subscriber's MS accesses 1 or later
version

GGSN IPv6 N/A N/A IPv6 address for configuring the UGW9810
Address for user plane of the GGSN that the V900R011C0
Data subscriber's MS accesses 1 or later
version

Protocol ·GTPv0 N/A Version of the GTP protocol UGW9810

Version ·GTPv1 V900R011C0
1 or later
·GTPv2 version

Cause N/A N/A Cause value carried in the UGW9810

response message for creating V900R011C0
the PDP context. For details, see 1 or later
7.7.1 in 3GPP 29.060. version

SGSN PLMN N/A N/A Information about the PLMN UGW9810

served by the access SGSN V900R011C0
1 or later
version

LAC N/A N/A Location area where the UGW9810

signaling procedure is triggered V900R011C0
1 or later
version

RAC N/A N/A Routing area where the UGW9810

signaling procedure is triggered V900R011C0
1 or later
version

SAC N/A N/A Serving area where the UGW9810

signaling procedure is triggered V900R011C0
1 or later
version

CI N/A N/A Cell where the signaling UGW9810

procedure is triggered V900R011C0
1 or later
version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1177

Parameter Range Unit Description Supported

NE Version

NSAPI N/A N/A Identity of the service access UGW9810

point (SAP) in the network V900R011C0
layer 1 or later
version

Activation Type ·First N/A Identifies whether an activation UGW9810

activation is a first or second activation V900R011C0
·Second 1 or later
activation version

·Unknown

TEID-C N/A N/A Identity of the GTP-C tunneling UGW9810

protocol V900R011C0
1 or later
version

Charging Unspecifie N/A Marks different charging UGW9810

Characteristics d characteristics. V900R011C0
Hot billing For detailed characteristic 1 or later
Charging description, see UGW product version

Flat rate documentation.

Charging
Prepaid
Charging
Normal
Charging

Procedure Information-Update PDP/Delete PDP

Parameter Range Unit Description Supported
NE Version

PDP Type ·X25 N/A Type of the PDP when the UGW9810
·PPP context is activated V900R011C01
or later version
·OSP_IHOSS
·IPV4
·IPV6
·IPV4V6

MS IP V4 N/A N/A IPv4 address allocated to UGW9810

the subscriber's MS V900R011C01
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1178

Parameter Range Unit Description Supported

NE Version

MS IP V6 N/A N/A IPv6 address allocated to UGW9810

the subscriber's MS V900R011C01
or later version

SGSN Address N/A N/A IPv4 address for UGW9810

for Signaling configuring the control V900R011C01
plane of the SGSN that the or later version
subscriber's MS accesses

SGSN IPv6 N/A N/A IPv6 address for UGW9810

Address for configuring the control V900R011C01
Signaling plane of the SGSN that the or later version
subscriber's MS accesses

SGSN Address N/A N/A IPv4 address for UGW9810

for Data configuring the user plane V900R011C01
of the SGSN that the or later version
subscriber's MS accesses

SGSN IPv6 N/A N/A IPv6 address for UGW9810

Address for configuring the user plane V900R011C01
Data of the SGSN that the or later version
subscriber's MS accesses

GGSN Address N/A N/A IPv4 address for UGW9810

for Signaling configuring the control V900R011C01
plane of the GGSN that the or later version
subscriber's MS accesses

GGSN IPv6 N/A N/A IPv6 address for UGW9810

Address for configuring the control V900R011C01
Signaling plane of the GGSN that the or later version
subscriber's MS accesses

GGSN Address N/A N/A IPv4 address for UGW9810

for Data configuring the user plane V900R011C01
of the GGSN that the or later version
subscriber's MS accesses

GGSN IPv6 N/A N/A IPv6 address for UGW9810

Address for configuring the user plane V900R011C01
Data of the GGSN that the or later version
subscriber's MS accesses

Protocol ·GTPv0 N/A Version of the GTP UGW9810

Version ·GTPv1 protocol V900R011C01
or later version
·GTPv2

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1179

Parameter Range Unit Description Supported

NE Version

Procedure ·SSGN N/A Initiator of the signaling UGW9810

Organizer ·MME procedure recorded in the V900R011C01
CHR. or later version
·GGSN
·SGW
·PGW
·SGW+PGW

Cause N/A N/A Cause value carried in the UGW9810

response message for V900R011C01
creating the PDP context. or later version
For details, see 7.7.1 in
3GPP 29.060.

SGSN PLMN N/A N/A Information about the UGW9810

PLMN served by the access V900R011C01
SGSN or later version

LAC N/A N/A Location area where the UGW9810

signaling procedure is V900R011C01
triggered or later version

RAC N/A N/A Routing area where the UGW9810

signaling procedure is V900R011C01
triggered or later version

SAC N/A N/A Serving area where the UGW9810

signaling procedure is V900R011C01
triggered or later version

CI N/A N/A Cell where the signaling UGW9810

procedure is triggered V900R011C01
or later version

NSAPI N/A N/A Identity of the service UGW9810

access point (SAP) in the V900R011C01
network layer or later version

TEID-C N/A N/A Identity of the GTP-C UGW9810

tunneling protocol V900R011C01
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1180

Parameter Range Unit Description Supported

NE Version

Charging Unspecified N/A Marks different charging UGW9810

Characteristics Hot billing characteristics. V900R011C01
Charging For detailed characteristic or later version

Flat rate description, see UGW

Charging product documentation.

Prepaid
Charging
Normal
Charging

Procedure Information-Create Session

Parameter Range Unit Description Supported
NE Version

User Whole [1,2^31- N/A Unique ID of the whole procedure UGW9810

Procedure ID 1) for a subscriber to use a web V900R011C01
service through the MS. This or later version
parameter distinguishes between
the multiple web service
procedures for the same subscriber.

Procedure NO. [1,2^31- N/A Unique No. of each service UGW9810

1) procedure in the whole procedure V900R011C01
for a subscriber or later version

Message ·SSGN N/A Initiator of the signaling message UGW9810

Organizer ·MME recorded in the CHR V900R011C01
or later version
·GGSN
·SGW
·PGW
·SGW
+PGW

Slot N/A N/A Logical board No. of the device UGW9810

that processes the CHR V900R011C01
or later version

CPU N/A N/A Logical CPU No. of the device that UGW9810
processes the CHR V900R011C01
or later version

SPU Group N/A N/A SPU group No. of the device that UGW9810
processes the CHR V900R011C01
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1181

Parameter Range Unit Description Supported

NE Version

SPU Instance N/A N/A SPU instance No. of the device that UGW9810
processes the CHR V900R011C01
or later version

Serving N/A N/A MCC and MNC of the subscriber's UGW9810

Network serving network V900R011C01
or later version

CI N/A N/A CGI information, including MCC, UGW9810

MNC, LAC, and CI V900R011C01
or later version

SAC N/A N/A SAI information, including MCC, UGW9810

MNC, LAC, and SAC V900R011C01
or later version

RAC N/A N/A RAI information, including MCC, UGW9810

MNC, LAC, and RAC V900R011C01
or later version

TAC N/A N/A TAI information, including MCC, UGW9810

MNC, and TAC V900R011C01
or later version

ECI N/A N/A ECGI information, including UGW9810

MCC, MNC, and ECI V900R011C01
or later version

LAC N/A N/A LAI information, including MCC, UGW9810

MNC, and LAC V900R011C01
or later version

MS IP V4 N/A N/A IPv4 address allocated to the UGW9810

subscriber's MS V900R011C01
or later version

MS IP V6 N/A N/A IPv6 address allocated to the UGW9810

subscriber's MS V900R011C01
or later version

Peer IPV4 N/A N/A IPv4 address for configuring the UGW9810
Address for control plane of the CN NE V900R011C01
Signaling interconnected to this NE or later version

Peer IPV4 N/A N/A IPv4 address for configuring the UGW9810
Address for user plane of the CN NE V900R011C01
Data interconnected to this NE or later version

Local IPV4 N/A N/A IPv4 address for configuring the UGW9810
Address for control plane of the NE V900R011C01
Signaling or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1182

Parameter Range Unit Description Supported

NE Version

Local IPV4 N/A N/A IPv4 address for configuring the UGW9810
Address for user plane of the NE V900R011C01
Data or later version

Peer IPV6 N/A N/A IPv6 address for configuring the UGW9810
Address for control plane of the CN NE V900R011C01
Signaling interconnected to this NE or later version

Peer IPV6 N/A N/A IPv6 address for configuring the UGW9810
Address for user plane of the CN NE V900R011C01
Data interconnected to this NE or later version

Local IPV6 N/A N/A IPv6 address for configuring the UGW9810
Address for control plane of the NE V900R011C01
Signaling or later version

Local IPV6 N/A N/A IPv6 address for configuring the UGW9810
Address for user plane of the NE V900R011C01
Data or later version

Selection Mode ·MS or N/A APN selection mode UGW9810

network V900R011C01
provided or later version
APN,
subscrib
ed
verified
·MS
provided
APN,
subscrip
tion not
verified
·
Network
provided
APN,
subscrip
tion not
verified

PDN Type ·IPv4 N/A Type of the PDN, including IPv4, UGW9810
·IPv6 IPv6, and IPv4v6 V900R011C01
or later version
·IPv4v6

Linked EPS N/A N/A ID of the default bearer. This UGW9810

Bearer ID parameter can also be used to V900R011C01
identify the PDN connection. or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1183

Parameter Range Unit Description Supported

NE Version

EPS Bearer ID N/A N/A ID of all bearers (including the UGW9810

default bearer) for the PDN V900R011C01
connection or later version

Bearer QoS PCI N/A N/A PCI in the Bearer QoS parameter UGW9810
V900R011C01
or later version

Bearer QoS PL N/A N/A PL in the Bearer QoS parameter UGW9810

V900R011C01
or later version

Bearer QoS PVI N/A N/A PVI in the Bearer QoS parameter UGW9810
V900R011C01
or later version

Bearer QoS QCI N/A N/A QCI in the Bearer QoS parameter UGW9810
V900R011C01
or later version

Bearer QoS N/A N/A MBRU in the Bearer QoS UGW9810

MBRU parameter V900R011C01
or later version

Bearer QoS N/A N/A MBRD in the Bearer QoS UGW9810

MBRD parameter V900R011C01
or later version

Bearer QoS N/A N/A GBRU in the Bearer QoS UGW9810

GBRU parameter V900R011C01
or later version

Bearer QoS N/A N/A GBRD in the Bearer QoS UGW9810

GBRD parameter V900R011C01
or later version

UE Time Zone N/A N/A Time zone information of the UE UGW9810

V900R011C01
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1184

Parameter Range Unit Description Supported

NE Version

Charging Unspeci N/A Marks different charging UGW9810

Characteristics fied characteristics. V900R011C01
Hot For detailed characteristic or later version
billing description, see UGW product
Chargin documentation.
g
Flat rate
Chargin
g
Prepaid
Chargin
g
Normal
Chargin
g

Protocol Cause N/A N/A Standard cause value carried in the UGW9810
response message V900R011C01
or later version

Procedure Information-Delete Session

Parameter Range Unit Description Supported NE
Version

User Whole [1,2^31-1) N/A Unique ID of the UGW9810

Procedure ID whole V900R011C01
procedure for a or later version
subscriber to use
a web service
through the MS.
This parameter
distinguishes
between the
multiple web
service
procedures for
the same
subscriber.

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1185

Parameter Range Unit Description Supported NE

Version

Procedure NO. [1,2^31-1) N/A Unique No. of UGW9810

each service V900R011C01
procedure in the or later version
whole
procedure for a
subscriber

Message ·SSGN N/A Initiator of the UGW9810

Organizer ·MME signaling V900R011C01
message or later version
·GGSN recorded in the
·SGW CHR
·PGW
·SGW+PGW

Slot N/A N/A Logical board UGW9810

No. of the V900R011C01
device that or later version
processes the
CHR

CPU N/A N/A Logical CPU UGW9810

No. of the V900R011C01
device that or later version
processes the
CHR

SPU Group N/A N/A SPU group No. UGW9810

of the device V900R011C01
that processes or later version
the CHR

SPU Instance N/A N/A SPU instance UGW9810

No. of the V900R011C01
device that or later version
processes the
CHR

Serving N/A N/A MCC and MNC UGW9810

Network of the V900R011C01
subscriber's or later version
serving network

CI N/A N/A CGI UGW9810

information, V900R011C01
including MCC, or later version
MNC, LAC, and
CI

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1186

Parameter Range Unit Description Supported NE

Version

SAC N/A N/A SAI UGW9810

information, V900R011C01
including MCC, or later version
MNC, LAC, and
SAC

RAC N/A N/A RAI UGW9810

information, V900R011C01
including MCC, or later version
MNC, LAC, and
RAC

TAC N/A N/A TAI UGW9810

information, V900R011C01
including MCC, or later version
MNC, and TAC

ECI N/A N/A ECGI UGW9810

information, V900R011C01
including MCC, or later version
MNC, and ECI

LAC N/A N/A LAI UGW9810

information, V900R011C01
including MCC, or later version
MNC, and LAC

Linked EPS N/A N/A ID of the default UGW9810

Bearer ID bearer. This V900R011C01
parameter can or later version
also be used to
identify the
PDN
connection.

EPS Bearer ID N/A N/A ID of all bearers UGW9810

(including the V900R011C01
default bearer) or later version
for the PDN
connection

UE Time Zone N/A N/A Time zone UGW9810

information of V900R011C01
the UE or later version

Protocol Cause N/A N/A Standard cause UGW9810

value carried in V900R011C01
the response or later version
message

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1187

Procedure Information-Create Bearer/Modify Bearer/Update Bearer

Parameter Range Unit Description Supported
NE Version

User Whole [1,2^31- N/A Unique ID of the whole UGW9810

Procedure ID 1) procedure for a subscriber to use V900R011C01
a web service through the MS. or later version
This parameter distinguishes
between the multiple web
service procedures for the same
subscriber.

Procedure No. [1,2^31- N/A Unique No. of each service UGW9810

1) procedure in the whole V900R011C01
procedure for a subscriber or later version

Message ·SSGN N/A Initiator of the signaling UGW9810

Organizer ·MME message recorded in the CHR V900R011C01
or later version
·GGSN
·SGW
·PGW
·SGW
+PGW

Slot N/A N/A Logical board No. of the device UGW9810

that processes the CHR V900R011C01
or later version

CPU N/A N/A Logical CPU No. of the device UGW9810

that processes the CHR V900R011C01
or later version

SPU Group N/A N/A SPU group No. of the device that UGW9810
processes the CHR V900R011C01
or later version

SPU Instance N/A N/A SPU instance No. of the device UGW9810
that processes the CHR V900R011C01
or later version

Serving N/A N/A MCC and MNC of the UGW9810

Network subscriber's serving network V900R011C01
or later version

CI N/A N/A CGI information, including UGW9810

MCC, MNC, LAC, and CI V900R011C01
or later version

SAC N/A N/A SAI information, including UGW9810

MCC, MNC, LAC, and SAC V900R011C01
or later version

Issue 05 (2015-02-14) Huawei Proprietary and Confidential 1188

Parameter Range Unit Description Supported

NE Version

RAC N/A N/A RAI information, including UGW9810

MCC, MNC, LAC, and RAC V900R011C01
or later version

TAC N/A N/A TAI information, including UGW9810

MCC, MNC, and TAC V900R011C01
or later version

ECI N/A N/A ECGI information, including UGW9810

MCC, MNC, and ECI V900R011C01
or later version

LAC N/A N/A LAI information, including UGW9810

MCC, MNC, and LAC V900R011C01
or later version